WO2022020060A1 - Rate-matching resources for physical downlink shared channel (pdsch) transmissions and multiplexing uplink transmissions with different timings - Google Patents

Abstract

The invention relates to one or more non-transitory computer-readable media having instructions, stored thereon, that when executed by one or more processors cause a user equipment (UE) to: encode a first message for transmission on a first carrier and a second message for transmission on a second carrier in accordance with carrier aggregation; and encode, for transmission to a next generation Node B (gNB), an indication of a timing difference of the transmission on the first carrier and the second carrier.

Description

RATE-MATCHING RESOURCES FOR PHYSICAL DOWNLINK SHARED CHANNEL (PDSCH) TRANSMISSIONS AND MULTIPLEXING UPLINK TRANSMISSIONS WITH DIFFERENT TIMINGS

CROSS REFERENCE TO RELATED APPLICATION

The present application claims priority to International Application No. PCT/CN2020/103765, which was filed July 23, 2020, U.S. Provisional Patent Application No. 63/055,519, which was filed July 23, 2020 and U.S. Provisional Patent Application No. 63/079,025, which was filed September 16, 2020.

FIELD

Various embodiments generally may relate to the field of wireless communications.

BACKGROUND

Various embodiments generally may relate to the field of wireless communications. Mobile communication has evolved significantly from early voice systems to today’s highly sophisticated integrated communication platform. The next generation wireless communication system, 5G, or new radio (NR) will provide access to information and sharing of data anywhere, anytime by various users and applications. NR is expected to be a unified network/system that targets to meet vastly different and sometime conflicting performance dimensions and services. Such diverse multi-dimensional requirements are driven by different services and applications. In general, NR will evolve based on 3GPP LTE-Advanced with additional potential new Radio Access Technologies (RATs) to enrich people lives with better, simple and seamless wireless connectivity solutions. NR will enable everything connected by wireless and deliver fast, rich content and services.

BRIEF DESCRIPTION OF THE FIGURES

Figure 1 illustrates physical downlink shared channel (PDSCH) rate-matching around a control resource set (CORESET), in accordance with various embodiments.

Figure 2 illustrates a long PDSCH transmission duration, in accordance with various embodiments.

Figure 3 illustrates a rate-matching resource based on a CORESET, in accordance with various embodiments.

Figure 4 illustrates a gap around synchronization signal block (SSB) transmission, in accordance with various embodiments.

Figure 5 illustrates an indication of whether a subset of physical downlink control channel (PDCCH) monitoring occasions is activated or deactivated, in accordance with various embodiments.

Figure 6 illustrates a PDCCH transmitted in one code block (CB) or code block group (CBG) within a PDSCH transmission duration, in accordance with various embodiments.

Figure 7 illustrates using a demodulation reference signal (DMRS) to indicate whether a PDCCH monitoring occasion is activated or deactivated, in accordance with various embodiments.

Figure 8 illustrates a PDSCH with multiple CBGs when not colliding with activated rate-matching resources, in accordance with various embodiments.

Figure 9 illustrates a first option for a PDSCH resource allocation when colliding with one or more activated rate-matching resources, in accordance with various embodiments.

Figure 10 illustrates a PDSCH resource allocation when colliding with one or more deactivated rate-matching resources, in accordance with various embodiments.

Figure 11 illustrates a second option for a PDSCH resource allocation when colliding with one or more activated rate-matching resources, in accordance with various embodiments.

Figure 12 illustrates a third option for a PDSCH resource allocation when colliding with one or more activated rate-matching resources, in accordance with various embodiments.

Figure 13 illustrates a procedure of overlapping check based on UE reported time difference of two carriers, in accordance with various embodiments.

Figure 14 illustrates another procedure of overlapping check based on UE reported time difference of two carriers, in accordance with various embodiments.

Figure 15 illustrates a procedure for overlap checking by logical timing and offset, in accordance with various embodiments.

Figure 16 illustrates an example of overlap checking by logical timing with offset, in accordance with various embodiments.

Figure 17 illustrates an example of overlap checking with logical timing and granularity of 4 symbols, in accordance with various embodiments.

Figure 18 illustrates a relatively short slot duration with relatively larger subcarrier spacing, in accordance with various embodiments.

Figure 19 illustrates a network in accordance with various embodiments.

Figure 20 schematically illustrates a wireless network in accordance with various embodiments.

Figure 21 is a block diagram illustrating components, according to some example embodiments, able to read instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and perform any one or more of the methodologies discussed herein.

Figures 22-25 depict example procedures for practicing the various embodiments discussed herein.

DETAILED DESCRIPTION

The following detailed description refers to the accompanying drawings. The same reference numbers may be used in different drawings to identify the same or similar elements. In the following description, for purposes of explanation and not limitation, specific details are set forth such as particular structures, architectures, interfaces, techniques, etc. in order to provide a thorough understanding of the various aspects of various embodiments. However, it will be apparent to those skilled in the art having the benefit of the present disclosure that the various aspects of the various embodiments may be practiced in other examples that depart from these specific details. In certain instances, descriptions of well-known devices, circuits, and methods are omitted so as not to obscure the description of the various embodiments with unnecessary detail. For the purposes of the present document, the phrases “A or B” and “A/B” mean (A), (B), or (A and B).

Various embodiments provide techniques for rate-matching resources for physical downlink shared channel (PDSCH) transmissions. Additionally, embodiments provide techniques for multiplexing uplink transmissions on multiple carriers with different uplink transmission timings.

RATE-MATCHING RESOURCES FOR PDSCH TRANSMISSIONS

In New Radio (NR), to ensure forward compatibility and achieve seamless coexistence with other radio access technology, e.g., 4G (LTE), multiple rate-matching resources can be configured for a user equipment (UE), where a physical downlink shared channel (PDSCH) can be rate-matched around the rate-matched resources. More specifically, rate-matching resource can be semi-statically configured by higher layers or dynamically activated/deactivated via downlink control information (DCI) carried by a physical downlink control channel (PDCCH). In the latter case, up to two groups of rate-matching resources can be configured for a UE, and one field in the DCI can be used to indicate whether one group of rate-matching resources is activated or not.

Further, rate-matching resource can be configured via bitmap, which indicates time and frequency resources with certain periodicity, or configured as control resource set (CORESET). In the latter case, scheduled PDSCH is rate-matched around the CORESET as shown in Figure E

For systems operating above a 52.6GHz carrier frequency, especially for Terahertz communication, it is envisioned that a larger subcarrier spacing is needed to combat severe phase noise. In cases when a larger subcarrier spacing, e.g., 1.92MHz or 3.84MHz is employed, the slot duration can be very short. For instance, for 1.92MHz subcarrier spacing, one slot duration is approximately 7.8ps. This extremely short slot duration may not be sufficient for higher layer processing, including Medium Access Layer (MAC) and Radio Link Control (RLC), etc. In order to address this issue, a next-generation NodeB (gNB) may schedule the downlink (DL) or uplink (UL) data transmission across a slot boundary with long transmission duration. In other words, a slot concept may not be needed when scheduling data transmission. Figure 2 illustrates one example of long PDSCH transmission duration.

When a scheduled PDSCH transmission duration is relatively long and PDCCH monitoring occasion is relatively short, UE may need to monitor PDCCH and perform blind decoding of PDCCHs within the PDSCH transmission duration. For some cases when there is no additional traffic for the UE, PDCCH monitoring within PDSCH transmission may not be needed so as to reduce UE power consumption. Further, corresponding CORESET or configured rate-matching resources may be allocated for PDSCH transmission, which can help in improving spectrum efficiency. Hence, certain mechanisms may need to be defined to allow UE to skip the PDCCH monitoring occasions or only monitor a subset of PDCCH occasions during PDSCH transmission.

Among other things, embodiments of the present disclosure are directed to physical downlink shared channel (PDSCH) transmissions with rate-matching resource. In particular, some embodiments may provide signaling details on dynamic activation of a subset of rate matching resources, as well as PDSCH resource allocation with rate-matching resources.

Signaling details on dynamical activation of a subset of rate-matching resources

As mentioned above, for systems operating above 52.6GHz carrier frequency, especially for Terahertz communication, it is envisioned that a larger subcarrier spacing is needed to combat severe phase noise. In case when a larger subcarrier spacing, e.g., 1.92MHz or 3.84MHz is employed, the slot duration can be very short. For instance, for 1.92MHz subcarrier spacing, one slot duration is approximately 7.8ps. This extremely short slot duration may not be sufficient for higher layer processing, including Medium Access Layer (MAC) and Radio Link Control (RLC), etc. In order to address this issue, gNB may schedule the DL or UL data transmission across slot boundary with long transmission duration.

When a scheduled PDSCH transmission duration is relatively long and PDCCH monitoring occasion is relatively short, a UE may need to monitor PDCCH and perform blind decoding of PDCCHs within the PDSCH transmission duration. For some cases when there is no additional traffic for the UE, PDCCH monitoring within PDSCH transmission may not be needed so as to reduce UE power consumption. Further, corresponding CORESET or configured rate-matching resources may be allocated for PDSCH transmission, which can help in improving spectrum efficiency. Hence, certain mechanisms may need to be defined to allow UE to skip the PDCCH monitoring occasions or only monitor a subset of PDCCH occasions during PDSCH transmission. Embodiments of the present disclosure may provide signaling details on dynamical activation of a subset of rate-matching resources as described in more detail below.

In one embodiment, a rate-matching resource is configured only in time domain. More specifically, resource block level bitmap in the frequency domain may not be needed as part of configuration for rate-matching resource. This is due to the fact that for system operating above 52.6GHz carrier frequency, it is expected that single carrier waveform including Discrete Fourier Transform-spread-OFDM (DFT-s-OFDM) is used for DL channels/signals in order to mitigate issues including low power amplifier (PA) efficiency and large phase noise. In this case, PDSCH and other physical channels/signals can be multiplexed in the time division multiplexing (TDM) manner.

Further, when a rate-matching resource is configured as cell level, if activated or configured, all the resource in system bandwidth is used for PDSCH rate-matching. When rate matching resource is configured as bandwidth part (BWP) level, if activated or configured, all the resource in BWP is used for PDSCH rate-matching.

In another embodiment, when CORESET is configured as rate-matching resource, only CORESET resource in time domain is needed for rate-matching resource. In particular, time domain resource is determined by the higher layer parameters monitoringSlotPeriodicityAndOffset, duration and monitoringSymbolsWithinSlot of all searchspace-sets configured by SearchSpace and time domain resource of search-space-set zero configured by searchSpaceZero associated with the CORESET as well as CORESET duration configured by ControlResourceSet with controlResourceSetld or ControlResourceSetZero. In another embodiment, when CORESET is configured as rate-matching resource, some gaps before and/or after CORESET may be needed for beam switching. In this case, rate matching resource includes the CORESET and the gap before and/or after CORESET.

The gap or K symbols can be additionally configured by higher layers via minimum system information (MSI), remaining minimum system information (RMSI), other system information (OSI) or dedicated radio resource control (RRC) signalling. This may also depend on UE capability on beam switching time.

Figure 3 illustrates rate-matching resource based on CORESET. As shown, 1 symbol gap is inserted before and after CORESET as the rate-matching resource.

In another embodiment, if PDSCH resource allocation overlaps with the symbols which contain synchronization signal block (SSB) transmission, UE shall assume that the OFDM symbols containing SSB transmission are not available for PDSCH transmission. The SSB transmission in time may be configured by higher layers via ssb-PositionsInBurst in SIB1 or ssb-PositionsInBurst in ServingCellConfigCommon. Note that this indicates that SSB transmission and other DL channels/signals may not be multiplexed in a same OFDM symbol if DFT-s-OFDM waveform is applied for DL transmission.

When other DL channels or signals, including PDCCH, channel state information- reference signal (CSI-RS), phase tracking reference signal (PT-RS), etc., overlaps with the symbols which contains SSB transmission, UE assume that the OFDM symbols containing SSB transmission are not available for other DL channel transmission. In particular, UE may not monitor the PDCCH candidate when overlapping with the symbols which contain SSB transmission. Similarly, CSI-RS and/or PT-RS is dropped on the symbols which contain SSB transmission.

As a further extension, a gap may be inserted before and/or after the OFDM symbols for SSB transmission, which can be used for beam switching time. The size of gap can be additionally configured by higher layers via MSI, RMSI (SIB1), OSI or RRC signalling.

Figure 4 illustrates one example of configured gap around SSB transmission. In the example, 1 symbol gap is inserted before and after the symbols which contain SSB transmission.

In another embodiment, when the same Tx beam is applied for the transmission of CORESET/PDCCH and PDSCH, or SSB and PDSCH, it may be possible that PDSCH and CORESET/PDCCH or SSB and PDSCH can be transmitted on consecutive symbols without any gap. In this case, additional beam switching time may not be needed. In an option, an indication of whether PDSCH can be transmitted on a symbol next to the symbols for CORESET/PDCCH or SSB transmission with one or more SSB indexes may be configured by higher layers via RRC signalling. When configured, UE may transmit the PDSCH and CORESET/PDCCH or SSB transmission with one or more SSB indexes on consecutive symbols or the same symbols.

In another option, whether PDSCH can be transmitted on a symbol next to the symbols for CORESET/PDCCH or SSB may be derived by the Transmission Configuration Indicator (TCI) state for the PDSCH. According the TCI state, if the PDSCH is Quasi Co-Location (QCL)’ed with a CORESET/PDCCH or an SSB, UE may transmit the PDSCH and CORESET/PDCCH or SSB on consecutive symbols or the same symbols.

In another embodiment, when same Tx beam is applied for the transmission of PDCCH and PDSCH, or SSB and PDSCH, it may be possible that PDSCH and PDCCH or SSB are multiplexed in a TDM manner prior to DFT operation. In this case, when same QCL assumption is applied for PDSCH and PDCCH/CORESET or SSB and if PDSCH overlaps with PDCCH/CORESET or SSB in a same symbol, PDSCH may be rate-matched around the samples in time prior to DFT operation which contain PDCCH/CORESET or SSB transmission in the same symbol.

In an option, an indication on whether PDSCH can be rate-matched around the resource allocated for CORESET/PDCCH or SSB transmission with one or more SSB indexes may be configured by higher layers via RRC signalling. When configured, UE may assume that PDSCH is rate-matched around the samples in time prior to DFT operation which contain PDCCH/CORESET or SSB transmission in the same symbol.

In another option, whether PDSCH can be rate-matched around the resource allocated for CORESET/PDCCH or SSB transmission with one or more SSB indexes may be derived by the TCI state for the PDSCH. According the TCI state, if the PDSCH is QCL’ed with a CORESET/PDCCH or a SSB, UE may assume that the PDSCH is rate-matched around the samples in time prior to DFT operation which contain the PDCCH/CORESET or the SSB transmission in the same symbol.

In another embodiment, one field in the DCI for scheduling PDSCH can be used to indicate that a subset of PDCCH monitoring occasions is activated during PDSCH transmission duration. Herein, the set of PDCCH monitoring occasions refers to all PDCCH monitoring occasions which are configured by high layer parameter SearchSpace that overlap with the scheduled PDSCH. In case when the subset of PDCCH monitoring occasions is deactivated during PDSCH transmission, UE can skip the PDCCH monitoring and does not need perform PDCCH blind decoding on the subset of PDCCH monitoring occasions.

In one option, a set of PDCCH monitoring occasion patterns within a PDSCH transmission duration can be configured by higher layers, where one field in the DCI for scheduling PDSCH can be used to indicate which PDCCH monitoring occasion pattern is used within the PDSCH transmission duration, and UE may perform PDSCH rate-matching around CORESET or detected PDCCH on the activated PDCCH monitoring occasion. A PDCCH monitoring occasion pattern includes a subset of PDCCH monitoring occasions.

In another option, the subset of PDCCH monitoring occasions can be predefined in the specification. In one example, one field in the DCI can be used to indicate whether even or odd positions of PDCCH monitoring occasions are activated during PDSCH transmission duration. In particular, bit ‘1’ may be used to indicate that even positions of PDCCH monitoring occasions are activated during PDSCH transmission duration; while bit ‘0’ may be used to indicate that odd positions of PDCCH monitoring occasions are activated during PDSCH transmission duration.

In another example, one field in the DCI can be used to indicate whether first or second half of PDCCH monitoring occasions are activated during PDSCH transmission duration. In particular, bit ‘1’ may be used to indicate that first half of PDCCH monitoring occasions are activated during PDSCH transmission duration; while bit ‘0’ may be used to indicate that second half of PDCCH monitoring occasions are activated during PDSCH transmission duration.

Figure 5 illustrates one example of indication whether a subset of PDCCH monitoring occasions is activated or deactivated. In the example, in the DCI for scheduling PDSCH, one field is used to indicate that first PDCCH monitoring occasion is deactivated and UE can skip the PDCCH monitoring in the deactivated PDCCH monitoring occasion.

In another embodiment, a subset of PDCCH monitoring occasions that is activated during PDSCH transmission duration is predefined or configured by high layer signaling. Herein, the set of PDCCH monitoring occasions refers to all PDCCH monitoring occasions which are configured by high layer parameter SearchSpace that overlap with the scheduled PDSCH. In case when the subset of PDCCH monitoring occasions is deactivated during PDSCH transmission, UE can skip the PDCCH monitoring and does not need perform PDCCH blind decoding on the subset of PDCCH monitoring occasions.

In one option, the subset of PDCCH monitoring occasion patterns within PDSCH transmission duration can be configured by higher layers. The UE may perform PDSCH rate- matching around CORESET or detected PDCCH on the activated PDCCH monitoring occasion.

In another option, the subset of PDCCH monitoring occasion can be predefined in the specification. In one example, all the even positions of PDCCH monitoring occasions are activated during PDSCH transmission duration. The PDCCH monitoring occasion overlapped with the scheduled PDSCH are numbered serially, or the PDCCH monitoring occasions are numbered according to a reference timing, e.g. symbol 0 in SFN 0. In another example, the PDCCH monitoring occasion(s) overlapped with the second half of scheduled PDSCH are activated during PDSCH transmission duration. In another example, only the last N PDCCH monitoring occasion(s) overlapped with the scheduled PDSCH are activated during PDSCH transmission duration, N equals to 1 or is larger than 1. N could be predefined or configured by high layer signaling.

In another embodiment, more than one groups of search space sets may be configured for PDCCH monitoring. In case when two groups of search space sets are configured for PDCCH monitoring, when the PDCCH in first group of search space sets is detected, UE may switch from the first group of search space sets to the second group of search space sets. In one option, UE starts from the first symbol for scheduled PDSCH transmission for PDCCH monitoring occasions in the second group of search space sets. In another option, UE starts from N symbols after the detected PDCCH for PDCCH monitoring occasions in the second group of search space sets. N is predefined or configured by high layer. N may be determined by the UE capability of processing time between PDCCH and PDSCH.

Further, in one option, when a UE receives the PDCCH in the first group of search space sets, the UE may start or restart a timer. When the timer expires, the UE may switch from the second group of search space sets back to the first group of search space sets. Note that the duration of timer can be configured by higher layers via MSI, RMSI (SIB1), OSI or RRC signalling.

In another option, the UE monitors the PDCCH in the second group of search space sets during PDSCH transmission duration. Further, when the scheduled PDSCH by the PDCCH is ended, UE may switch from the second group of search space sets back to the first group of search space sets. In this case, the low density of the second group of search spaces can be configured for a UE to help reduce the PDCCH monitoring within PDSCH transmission and hence reduce UE power consumption.

In another embodiment, within PDSCH transmission, one or more CB/CBG or PDSCH may be replaced by a PDCCH carrying DCI. The one or more CB/CBG or PDSCH may overlap with configured/activated PDCCH monitoring occasion within PDSCH transmission duration. In this case, same encoding procedure or different encoding procedure may be applied for the transmission of PDCCH and PDSCH.

Figure 6 illustrates one example of transmitting PDCCH in one CB within PDSCH transmission duration. In the example, PDCCH is transmitted in the first CB within CBG#4. Note that PDCCH monitoring occasion collides with CBG#4 within PDSCH transmission duration.

In another embodiment, demodulation reference signal (DMRS) associated with PDSCH or PDCCH may be used to indicate the activation or deactivation of PDCCH monitoring occasions within a PDSCH transmission duration.

In particular, a DMRS within a first set of DMRS resources can be associated with PDSCH transmissions, while a DMRS within a second set of DMRS resources can be used to indicate the activation or deactivation of PDCCH monitoring occasions within the PDSCH transmission duration. Note that a DMRS resource may consist of DMRS sequence and/or cyclic shifts and/or scrambling IDs applied to it and/or DMRS antenna port. Further, the first and second set of DMRS resources may be configured by dedicated RRC signalling or dynamically indicated by DCI or a combination thereof.

In one option, the DMRS in the 2^nd set of DMRS resource can also be used for the channel estimation for PDCCH decoding in the activated PDCCH monitoring occasion. Further, the PDCCH transmitted in the activated PDCCH monitoring occasion can be k-symbol after the DMRS in the 2^nd set of DMRS resource, where k can be predefined in the specification or configured by higher layers via MSI, RMSI (SIB1), OSI or RRC signalling.

Figure 7 illustrates one example of using DMRS to indicate whether PDCCH monitoring occasion is activated or deactivated. In the example, DMRS in the second set of DMRS resources is used to indicate that the PDCCH monitoring occasion after the DMRS is activated. In this case, UE needs to perform PDCCH blind decoding in the activated PDCCH monitoring occasion.

PDSCH resource allocation with rate-matching resources

For PDSCH with a long duration, one DCI may be used to schedule multiple PDSCHs with different transport blocks (TB) or multiple code blocks (CB) or code block groups (CBG). Further, each CB or CBG may be aligned with symbol boundary and same length can be applied for the transmission of each CB or CBG. Similarly, in case of multi-PDSCH scheduling, each PDSCH may span same number of symbols. Figure 8 illustrates one example of PDSCH with multiple CBGs when the PDSCH does not collide with activated or configured rate-matching resources. In the example, the PDSCH includes 8 CBGs with continuous resource allocation. Further, each CBG spans 4 symbols.

When a PDSCH transmission collides with rate-matching resource during PDSCH transmission duration, certain mechanisms need to be defined for PDSCH resource allocation or the transmission of each PDSCH in case of multi-PDSCH scheduling or the transmission of each CB or CBG. Note that although in the embodiments as follows are applied for the case of one PDSCH transmission which includes one or more CB or CBGs, the embodiments can be straightforwardly employed for the case of multi-PDSCH transmission or PDSCH with slot aggregation. Embodiments directed to PDSCH resource allocation with rate-matching resources are described in more detail below.

In one embodiment, PDSCH including one or more CB or CBGs is allocated in accordance with the starting symbol and length indicator (SLIV) indicated in the DCI for scheduling PDSCH. This can be indicated as nominal resource allocation. In particular, first CB/CBG or first PDSCH is allocated in accordance with the starting symbol and duration. The subsequent CBGs and PDSCHs are allocated with same duration as the first CB/CBG or first PDSCH and in consecutive symbols after the first CB/CBG or PDSCH.

Further, when a PDSCH transmission including one or more CB/CBGs collides activated rate-matching resource, e.g., CORESET or activated PDCCH monitoring occasion or SSB block, CB/CBG or the PDSCH is not transmitted on the activated rate-matching resource. Further, impacted CB/CBG or the PDSCH is rate-matched around or puncturing the activated rate-matching resources. Note this can be indicated as actual resource allocation.

Note that transport block size (TBS) is determined in accordance with the duration of first CB/CBG or PDSCH or nominal resource allocation. The determined TBS is also applied for other CB/CBGs or PDSCHs regardless of whether the CB/CBGs and PDSCHs collide with activated rate-matching resources.

Alternatively, the TBS on the impacted CB/CBGs or PDSCHs when colliding with activated rate-matching resources can be determined in accordance with actual number of symbols or resources excluding the activated rate-matching resources or actual resource allocation.

Figure 9 illustrates one option of PDSCH resource allocation when colliding with activated rate-matching resources. For this option, each CBG is allocated with 5 symbols and CBG#3 collides with activated rate-matching resource which spans two symbols. In this case, CBG#3 is rate-matched around the activated rate-matching resource with the TBS determined in accordance with the nominal allocation.

Further, when PDSCH transmission including one or more CB/CBGs collides with deactivated rate-matching resource, CB/CBG or PDSCH continues to map on the deactivated rate-matching resources.

Figure 10 illustrates one option of PDSCH resource allocation when colliding with deactivated rate-matching resources. For this option, each CBG is allocated with 5 symbols and CBG#3 collides with deactivated rate-matching resource which spans two symbols. In this case, CBG#3 and subsequent CBGs are allocated in consecutive symbols without considering deactivated rate-matching resources.

In another embodiment, when PDSCH transmission including one or more CB/CBGs collides activated rate-matching resource, e.g., CORESET or deactivated PDCCH monitoring occasion or SSB block, CB/CBG or the PDSCH is not transmitted on the activated rate matching resource. Further, impacted CB/CBG or PDSCH continues to be transmitted after the activated rate-matching resource, and spans the number of symbols as indicated in the DCI. In this option, the actual resource allocation of CB/CBG or PDSCH is same as the nominal resource allocation which is indicated in the DCI.

Figure 11 illustrates another option of PDSCH resource allocation when colliding with activated rate-matching resources. For this option, each CBG is allocated with 5 symbols and CBG#3 collides with activated rate-matching resource which spans two symbols. In this case, CBG#3 continues to be transmitted after the activated rate-matching resources and spans 5 symbols as indicated in the DCI.

In another embodiment, PDSCH allocation is first based on the SLIV indicated in the DCI and configured rate-matching resource within PDSCH transmission duration. In particular, when one CB/CBG or PDSCH collides with configured rate-matching resource, the CB/CBG or PDSCH continues to be mapped after the configured rate-matching resource and spans indicated number of symbols via SLIV.

In the second step, for the configured rate-matching resource which is not activated, the CB/CBG or PDSCH before the deactivated rate-matching resource is mapped on the deactivated rate-matching resource.

Figure 12 illustrates another option of PDSCH resource allocation when colliding with activated rate-matching resources. In the example, each CBG is allocated with 5 symbols. Further, 2 configured rate-matching resources collide with PDSCH within PDSCH transmission duration, where the first one is activated and the second is deactivated. In this case, CBG#3 is mapped to the second rate-matching resource which is deactivated.

MULTIPLEXING UPLINK TRANSMISSIONS ON MULTIPLE CARRIERS WITH DIFFERENT UPLINK TRANSMISSION TIMINGS

For system operating above 52.6GHz carrier frequency, to account for the increased phase noise, subcarrier spacing (SCS) could be relatively large, e.g., 1.92MHz or 3.84MHz. In this case, symbol length can be very short. For instance, for 1.92MHz subcarrier spacing, the symbol length is about 0.56us. As shown in Figure 18, a slot with 14 symbols is approximately 7.8ps.

In carrier aggregation (CA), the component carriers may belong to different timing advance group (TAG). When the carriers have the same TAG, they are exactly synchronized. On the other hand, when the carriers have different TAGs, there could be a time difference between downlink (DL) reception and uplink (UL) transmission at UE side. The exact value of time difference is impacted by the synchronization error, and the propagation delay. For UL time difference between two carriers, it is also impacted by the TA values of the two carriers. Due to the extreme short symbol length in above 52.6GHz frequency, the time difference could be in scale of one or more symbols. For this matter, the impact that this could have on the multiplexing of UL signals/channels is an issue that should be solved.

Various embodiments herein provide techniques to multiplex UL transmissions on multiple carriers with different uplink transmission timings.

In a CA system, two UL carriers may belong to different TAGs, so that the two carriers have different UL transmission timings, even for the case that the reception timing at gNB are exactly aligned for the two UL carriers. The difference of UL transmission timings depends on multiple factors. UL transmission timing of a UL carrier is determined by the DL reception timing of the associated DL carrier and the TA value. The DL transmission timings of the two associated DL carriers may not be ideally aligned. The propagation delay between gNB and UE may be different for the two DL carriers. For instance, the base station (BS)s of the two DL carriers may be in different locations, so that the distances between the two BSs and the UE are different. Even in case the two BSs are co-located, the propagation delay can be different due to the different frequency of the two DL carriers. Specifically, the two DL carriers may belong to different frequency range (FR) which has much different propagation properties. As a result, the DL reception timings for the two DL carriers can be different at UE. Further, the DL reception timings at the UE are not exactly known by the gNB. The timing advance (TA) value is obtained by initial access and can also be adjusted by the TA command. Furthermore, a gNB and a UE may not have exactly the same knowledge of the TA value. Therefore, a gNB may not know the exact difference of UL transmission timings of two UL carriers of a specific UE.

For system operating above 52.6GHz carrier frequency, the subcarrier spacing (SCS) could be quite large which results in very short symbol length. For example, it is about 0.56us for SCS 1.92MHz. On the other hand, the time difference between two UL carriers may be several microseconds or more. If carrier aggregation of a carrier in FR1 and another carrier in above 52.6GHz frequency is considered, the time difference of the two UL carriers can be even higher. From the above analysis, the time difference of the two UL carriers may correspond to several or tens of symbols. Consequently, two UL channels that are overlapped at the UE side may be separated at gNB side, or two UL channels that are separated at UE side may be overlapped at the gNB side. Further, if the gNB doesn’t know the exact difference of UL transmission timings, a gNB cannot know if two UL transmissions on the two UL carriers are overlapped or not at UE side.

Based on the NR system design operating in CA, the UE may multiplex multiple UL information on one carrier if the multiple channels carrying the multiple information are overlapped. On the other hand, if the multiple channels are not overlapped, a UE could transmit the multiple UL channels separately. The determination on whether the multiple channels are overlapped may be based on the logical timing. The logical timing is defined as the transmission timing for the multiple channels assuming all the following are zero: (1) DL-to- DL timing differences between CCs; (2) UL-to-UL timing differences across different TAGs; (3) UL TA. Therefore, logical timing of the multiple channels corresponds to the case with aligned frame timing. However, due to the timing difference of multiple symbols at the UE, two channels may be separated by multiple symbols when it is considered as overlap following logical timing. On the other hand, two channels may be overlapped in multiple symbols when it is considered as non-overlap following logical timing.

In one embodiment, UE could report the actual transmission timing difference between the two TAGs or two carriers to gNB.

The reported timing difference could be the absolute time value. Alternatively, the reported timing difference could be quantized using a granularity of one or a fraction of the symbol length with a reference SCS. The reference SCS could be configured by high layer signaling. Alternatively, the reference SCS can be the highest SCS of the active UL BWP of the two UL carriers. Alternatively, the reference SCS can be the highest SCS of the active UL BWP of the UL carriers in the two TAGs. Alternatively, the reference SCS can be the highest SCS of the active UL BWP of all UL carriers. Alternatively, the reference SCS can be the maximum of the lowest subcarrier spacing configuration among the subcarrier spacings given by the higher-layer parameters SCS-SpecificCarrierList configured for the two UL carriers. Alternatively, the reference SCS can be the maximum of the lowest subcarrier spacing configuration among the subcarrier spacings given by the higher-layer parameters SCS- SpecificCarrierList configured for the UL carriers in the two TAGs. Alternatively, the reference SCS can be the maximum of the lowest subcarrier spacing configuration among the subcarrier spacings given by the higher-layer parameters SCS-SpecificCarrierList configured for all UL carriers. SCS-SpecificCarrierList is the high layer parameter defining SCS for a carrier in NR.

In one option, denote the actual time difference as t, t could be quantized into a number of symbols by

+ c , e. g. c = 0.5, where T is the length of a symbol. By this scheme, if two UL channels are considered as overlap, the two UL channels are actually overlapped by at least half symbol. If two UL channels are considered as non-overlap, the two UL channels may overlap by at most half symbol.

UE may periodically report the timing difference to gNB. Alternatively, UE may report the timing difference under certain condition. For example, if UE identifies that the timing difference is changed by a value which is larger than a threshold, UE report the new timing difference to gNB. The above threshold can be a fraction, one or multiple symbol duration. Alternatively, gNB may send a trigger for the report on demand. Once the trigger is received, UE reports the current timing difference or the delta between updated timing difference and old timing difference to gNB.

The report of the timing difference may be included in a measurement report of high layer signaling. Alternatively, the report of the timing difference could be carried in a medium access control - control element (MAC CE) on physical uplink shared channel (PUSCH). Alternatively, the report of the timing difference could be done in physical layer. For example, aperiodic or semi-persistent scheduling (SPS) based physical uplink control channel (PUCCH) or PUSCH resource may be configuration so that UE can report the timing difference periodically. Or, a downlink control channel (DCI) may be used to trigger aperiodic report of the timing difference on a PUSCH.

In one embodiment, whether two UL channels are overlapped or not is determined by the logical timing of the two UL carriers. If two UL channels are considered as overlapping with logical timing at UE side, the UL information associated with the two UL channels are multiplexed or dropped, e.g. in accordance with current specification as defined in Rel-15 and Rel-16 NR, even for the case that the two UL channels are not overlapped from UE point of view. On the other hand, if two UL channels are considered as non-overlapping with logical timing, however, the two UL channels may be overlapped in time. This case could be considered as an error case hence it is up to gNB to avoid such error case. Alternatively, UE may drop the UL channel with lower priority completely or only in the overlapped symbols. For instance, the priority order can be based on the priority of uplink control information (UCI) type. The UCI priority can be defined as HARQ-ACK > SR > CSI part 1 > CSI part 2. Alternatively, it is up to UE to how to handle the two overlapped UL channels.

In one embodiment, UE could report the actual transmission timing difference d between the two TAGs or the two UL carriers to gNB and determine whether two UL channels on the two UL carriers are overlapped or not based on the actual transmission timings of the two UL carriers. On the other hand, the gNB could determine whether two UL channels on the two UL carriers are overlapping or not based on the logical timings of the two UL channels and the reported timing difference d. If the two UL channels, after applying the timing difference d to the logical timings, have at least one symbol overlapped, the UL information associated with the two UL channels are multiplexed or dropped, e.g. in accordance with current specification as defined in Rel-15 and Rel-16 NR. Otherwise, the two UL channels are transmitted separately. With this scheme, gNB and UE could have common understanding on whether/how to multiplex or drop one or more of the multiple UL channels.

Figure 13 illustrates a procedure of overlapping check based on UE reported time difference of two carriers.

In one embodiment, UE could report the actual transmission timing difference d between the two TAGs or the two UL carriers to gNB, and determine whether two UL channels on the two UL carriers are overlapping or not based on the logical timings of the two UL channels and the reported timing difference d. On the other hand, the gNB could determine whether two UL channels on two UL carriers are overlapped or not based on the logical timings of the two UL channels and the reported timing difference d too. If the two UL channels, after applying the timing difference d to the logical timings, have at least one symbol overlapped, the UL information associated with the two UL channels are multiplexed or dropped, e.g. in accordance with current specification as defined in Rel-15 and Rel-16 NR. Otherwise, the two UL channels are transmitted separately. With this scheme, gNB and UE could have common understanding on whether/how to multiplex or drop one or more of the multiple UL channels. Figure 14 illustrates a procedure of overlapping check based on UE reported time difference of two carriers.

In one embodiment, the logical timings of two UL channels, adjusted by an offset, are used to determine whether the two UL channels are overlap or not. The offset reflects the time difference between the two TAGs or the two UL carriers. For example, a symbol with logical timing of symbol index / in slot s, after applying an offset d, the new slot index is s' =

the new symbol index in the slot s' is V = mod(L · s + l — d, L). The new indexes s'and V are used in overlap checking. If the two UL channels, after applying the offset to the logical timings, have at least one symbol overlapped, the UL information associated with the two UL channels are multiplexed or dropped, e.g. in accordance with current specification as defined in Rel-15 and Rel-16 NR. Otherwise, the two UL channels are transmitted separately. With this scheme, gNB and UE have common understanding on whether/how to multiplex or drop one or more of the multiple UL channels.

The offset used by a UE can be configured by gNB. For example, gNB may select an offset value based on TA values of the UE. Alternatively, as shown in Figure 15, UE may report a value of time difference between two TAGs or two carriers to gNB, and gNB could configures an offset to the logical timing to the UE. For the configuration of an offset, gNB may use the reported value of time difference by UE, or it is up to gNB to configure a value of the offset to UE. The configured offset may be same as or different from the time difference reported by UE.

Figure 4 illustrates an example of overlap checking by the logical timing with offset. It is assumed that the two carriers have same SCS hence same symbol length. The transmission timing of carrier 1 is earlier by 3 symbols than carrier 2. Therefore, gNB can configure a left offset of 3 symbols for carrier 1. On the other hand, carrier 2 is the reference to define an offset, e.g. the offset is 0 for carrier 2. From Figure 16, the symbol indexes for UL channel 1 are 8 to 12 (411). The shifted indexes of UL channel 1 are 5-9 after applying the offset of value -3 (412). Whether UL channel 1 is overlapped with a UL channel on carrier 2 is done by checking the symbol indexes of UL channel 412 and the UL channel on carrier 2.

UL channel 2 (421) is considered as overlap with UL channel 1 since they have common symbol indexes 6, 7, 8 and 9. In fact, some symbol indexes of UL channel 411 before applying offset -3 are also same as UL channel 2. • UL channel 3 (422) is considered as overlap with UL channel 1 since they have common symbol indexes 5 and 6, though the symbol indexes of UL channel 411 before applying offset -3 are different from UL channel 3.

• UL channel 4 (423) is considered as non-overlap with UL channel 1 since they do not have common symbol indexes, though the symbol indexes of UL channel 411 before applying offset -3 have common symbol indexes 11 and 12 with UL channel 4.

• UL channel 5 (424) is still considered as non-overlap with UL channel 1 since they do not have common symbol indexes even after applying an offset.

In one embodiment, a single DL time reference to derive UL transmission timings is used for the multiple TAGs. For example, DL reception timing of PCell is the reference for all UL carriers. For dual connectivity (DC), DL reference timing for master cell group (MCG) and secondary CG (SCG) could be determined as PCell and PSCell respectively. Since all the carriers in CA use the same DL reference, gNB can derive the time difference of UL transmission timings of the multiple TAGs based on the TA value of the multiple TAGs. Consequently, both gNB and UE can check if two UL channels are overlapped considering the difference of transmission timings.

In one embodiment, whether multiple UL channels are overlap or not are checked by actual transmission timing of the two UL carriers at UE side. It is up to gNB implementation to guarantee that gNB and UE have the same understanding on whether the multiple UL channels are overlapping or not. For example, the UE could report the timing difference of the two TAGs which helps the gNB to have the same understanding of channel overlapping as the UE.

In one embodiment, whether multiple UL channels are overlapping or not are checked by the logical timing of the two UL carriers with a larger granularity. The granularity could be defined as the length of X symbols with a reference SCS, where X > 1. The reference SCS could be configured by high layer signaling. Alternatively, the reference SCS can be the highest SCS of the active UL BWP of the two UL carriers. Alternatively, the reference SCS can be the highest SCS of the active UL BWP of the UL carriers in the two TAGs. Alternatively, the reference SCS can be the highest SCS of the active UL BWP of all UL carriers. Alternatively, the reference SCS can be the maximum of the lowest subcarrier spacing configuration among the subcarrier spacings given by the higher-layer parameters SCS-SpecificCarrierList configured for the two UL carriers. Alternatively, the reference SCS can be the maximum of the lowest subcarrier spacing configuration among the subcarrier spacings given by the higher- layer parameters SCS-SpecificCarrierList configured for the UL carriers in the two TAGs. Alternatively, the reference SCS can be the maximum of the lowest subcarrier spacing configuration among the subcarrier spacings given by the higher-layer parameters SCS- SpecificCarrierList configured for all UL carriers. .

Figure 17 illustrates an example of overlap checking with logical timing and granularity of 4 symbols. It is assumed that the two carriers have same subcarrier space (SCS) hence same symbol length. The transmission timing of carrier 1 is earlier by 3 symbols than carrier 2. That is, UL channel 1 (511) on carrier 1 after considering the 3-symbol left offset is actually overlapped with UL channel 2 (521) on carrier 2. By defining granularity of 4 symbols, the logical timing is divided into unit 501, 502, 503 and 504. The UL channel 1 (512) is mapped to unit 502 and 503. The UL channel 2 is mapped to unit 501 and 502. Since they are both mapped to unit 502, UL channel 1 and UL channel 2 are considered as overlap.

In one embodiment, for a PUSCH that is scheduled by a UL grant, the UL grant indicates whether/which UL control channel(s) can be multiplexed on the PUSCH. Since there may exist confusion whether a PUCCH is overlapped with the PUSCH, the indicator in the UL grant help UE to know whether UCI multiplexed on PUSCH needs to be performed to have aligned operation as gNB. For the case that there are multiple non-overlap PUCCHs, the indicator in the UL grant can further differentiate the one or multiple PUCCHs that needs to be multiplexed on the PUSCH. Whether two PUCCH or PUSCH channels are overlapped or not could be determined by the actual transmission timing of the two UL carriers at UE side, or by the logical timing of the two UL carriers, or by the logical timings of two UL carriers which is adjusted by an offset of time difference.

SYSTEMS AND IMPLEMENTATIONS

Figures 19-21 illustrate various systems, devices, and components that may implement aspects of disclosed embodiments.

Figure 19 illustrates a network 1900 in accordance with various embodiments. The network 1900 may operate in a manner consistent with 3GPP technical specifications for LTE or 5G/NR systems. However, the example embodiments are not limited in this regard and the described embodiments may apply to other networks that benefit from the principles described herein, such as future 3GPP systems, or the like.

The network 1900 may include a UE 1902, which may include any mobile or non- mobile computing device designed to communicate with a RAN 1904 via an over-the-air connection. The UE 1902 may be communicatively coupled with the RAN 1904 by a Uu interface. The UE 1902 may be, but is not limited to, a smartphone, tablet computer, wearable computer device, desktop computer, laptop computer, in-vehicle infotainment, in-car entertainment device, instrument cluster, head-up display device, onboard diagnostic device, dashtop mobile equipment, mobile data terminal, electronic engine management system, electronic/engine control unit, electronic/engine control module, embedded system, sensor, microcontroller, control module, engine management system, networked appliance, machine- type communication device, M2M or D2D device, IoT device, etc.

In some embodiments, the network 1900 may include a plurality of UEs coupled directly with one another via a sidebnk interface. The UEs may be M2M/D2D devices that communicate using physical sidelink channels such as, but not limited to, PSBCH, PSDCH, PSSCH, PSCCH, PSFCH, etc.

In some embodiments, the UE 1902 may additionally communicate with an AP 1906 via an over-the-air connection. The AP 1906 may manage a WLAN connection, which may serve to offload some/all network traffic from the RAN 1904. The connection between the UE 1902 and the AP 1906 may be consistent with any IEEE 802.11 protocol, wherein the AP 1906 could be a wireless fidelity (Wi-Fi®) router. In some embodiments, the UE 1902, RAN 1904, and AP 1906 may utilize cellular- WLAN aggregation (for example, LWA/LWIP). Cellular- WLAN aggregation may involve the UE 1902 being configured by the RAN 1904 to utilize both cellular radio resources and WLAN resources.

The RAN 1904 may include one or more access nodes, for example, AN 1908. AN 1908 may terminate air-interface protocols for the UE 1902 by providing access stratum protocols including RRC, PDCP, RLC, MAC, and LI protocols. In this manner, the AN 1908 may enable data/voice connectivity between CN 1920 and the UE 1902. In some embodiments, the AN 1908 may be implemented in a discrete device or as one or more software entities running on server computers as part of, for example, a virtual network, which may be referred to as a CRAN or virtual baseband unit pool. The AN 1908 be referred to as a BS, gNB, RAN node, eNB, ng-eNB, NodeB, RSU, TRxP, TRP, etc. The AN 1908 may be a macrocell base station or a low power base station for providing femtocells, picocells or other like cells having smaller coverage areas, smaller user capacity, or higher bandwidth compared to macrocells.

In embodiments in which the RAN 1904 includes a plurality of ANs, they may be coupled with one another via an X2 interface (if the RAN 1904 is an LTE RAN) or an Xn interface (if the RAN 1904 is a 5G RAN). The X2/Xn interfaces, which may be separated into control/user plane interfaces in some embodiments, may allow the ANs to communicate information related to handovers, data/context transfers, mobility, load management, interference coordination, etc.

The ANs of the RAN 1904 may each manage one or more cells, cell groups, component carriers, etc. to provide the UE 1902 with an air interface for network access. The UE 1902 may be simultaneously connected with a plurality of cells provided by the same or different ANs of the RAN 1904. For example, the UE 1902 and RAN 1904 may use carrier aggregation to allow the UE 1902 to connect with a plurality of component carriers, each corresponding to a Pcell or Scell. In dual connectivity scenarios, a first AN may be a master node that provides an MCG and a second AN may be secondary node that provides an SCG. The first/second ANs may be any combination of eNB, gNB, ng-eNB, etc.

The RAN 1904 may provide the air interface over a licensed spectrum or an unlicensed spectrum. To operate in the unlicensed spectrum, the nodes may use LAA, eLAA, and/or feLAA mechanisms based on CA technology with PCells/Scells. Prior to accessing the unlicensed spectrum, the nodes may perform medium/carrier-sensing operations based on, for example, a listen-before-talk (LBT) protocol.

In V2X scenarios the UE 1902 or AN 1908 may be or act as a RSU, which may refer to any transportation infrastructure entity used for V2X communications. An RSU may be implemented in or by a suitable AN or a stationary (or relatively stationary) UE. An RSU implemented in or by: a UE may be referred to as a “UE-type RSU”; an eNB may be referred to as an “eNB-type RSU”; a gNB may be referred to as a “gNB-type RSU”; and the like. In one example, an RSU is a computing device coupled with radio frequency circuitry located on a roadside that provides connectivity support to passing vehicle UEs. The RSU may also include internal data storage circuitry to store intersection map geometry, traffic statistics, media, as well as applications/software to sense and control ongoing vehicular and pedestrian traffic. The RSU may provide very low latency communications required for high speed events, such as crash avoidance, traffic warnings, and the like. Additionally or alternatively, the RSU may provide other cellular/WLAN communications services. The components of the RSU may be packaged in a weatherproof enclosure suitable for outdoor installation, and may include a network interface controller to provide a wired connection (e.g., Ethernet) to a traffic signal controller or a backhaul network.

In some embodiments, the RAN 1904 may be an LTE RAN 1910 with eNBs, for example, eNB 1912. The LTE RAN 1910 may provide an LTE air interface with the following characteristics: SCS of 15 kHz; CP-OFDM waveform for DL and SC-FDMA waveform for UL; turbo codes for data and TBCC for control; etc. The LTE air interface may rely on CSI- RS for CSI acquisition and beam management; PDSCH/PDCCH DMRS for PDSCH/PDCCH demodulation; and CRS for cell search and initial acquisition, channel quality measurements, and channel estimation for coherent demodulation/detection at the UE. The LTE air interface may operating on sub-6 GHz bands.

In some embodiments, the RAN 1904 may be an NG-RAN 1914 with gNBs, for example, gNB 1916, or ng-eNBs, for example, ng-eNB 1918. The gNB 1916 may connect with 5G-enabled UEs using a 5GNR interface. The gNB 1916 may connect with a 5G core through an NG interface, which may include an N2 interface or an N3 interface. The ng-eNB 1918 may also connect with the 5G core through an NG interface, but may connect with a UE via an LTE air interface. The gNB 1916 and the ng-eNB 1918 may connect with each other over an Xn interface.

In some embodiments, the NG interface may be split into two parts, an NG user plane (NG-U) interface, which carries traffic data between the nodes of the NG-RAN 1914 and a UPF 1948 (e.g., N3 interface), and an NG control plane (NG-C) interface, which is a signaling interface between the nodes of the NG-RAN1914 and an AMF 1944 (e.g., N2 interface).

The NG-RAN 1914 may provide a 5G-NR air interface with the following characteristics: variable SCS; CP-OFDM for DL, CP-OFDM and DFT-s-OFDM for UL; polar, repetition, simplex, and Reed-Muller codes for control and LDPC for data. The 5G-NR air interface may rely on CSI-RS, PDSCH/PDCCH DMRS similar to the LTE air interface. The 5G-NR air interface may not use a CRS, but may use PBCH DMRS for PBCH demodulation; PTRS for phase tracking for PDSCH; and tracking reference signal for time tracking. The 5G- NR air interface may operating on FR1 bands that include sub-6 GHz bands or FR2 bands that include bands from 24.25 GHz to 52.6 GHz. The 5G-NR air interface may include an SSB that is an area of a downlink resource grid that includes PSS/SSS/PBCH.

In some embodiments, the 5G-NR air interface may utilize BWPs for various purposes. For example, BWP can be used for dynamic adaptation of the SCS. For example, the UE 1902 can be configured with multiple BWPs where each BWP configuration has a different SCS. When a BWP change is indicated to the UE 1902, the SCS of the transmission is changed as well. Another use case example of BWP is related to power saving. In particular, multiple BWPs can be configured for the UE 1902 with different amount of frequency resources (for example, PRBs) to support data transmission under different traffic loading scenarios. A BWP containing a smaller number of PRBs can be used for data transmission with small traffic load while allowing power saving at the UE 1902 and in some cases at the gNB 1916. A BWP containing a larger number of PRBs can be used for scenarios with higher traffic load. The RAN 1904 is communicatively coupled to CN 1920 that includes network elements to provide various functions to support data and telecommunications services to customers/subscribers (for example, users of UE 1902). The components of the CN 1920 may be implemented in one physical node or separate physical nodes. In some embodiments, NFV may be utilized to virtualize any or all of the functions provided by the network elements of the CN 1920 onto physical compute/storage resources in servers, switches, etc. A logical instantiation of the CN 1920 may be referred to as a network slice, and a logical instantiation of a portion of the CN 1920 may be referred to as a network sub-slice.

In some embodiments, the CN 1920 may be an LTE CN 1922, which may also be referred to as an EPC. The LTE CN 1922 may include MME 1924, SGW 1926, SGSN 1928, HSS 1930, PGW 1932, and PCRF 1934 coupled with one another over interfaces (or “reference points”) as shown. Functions of the elements of the LTE CN 1922 may be briefly introduced as follows.

The MME 1924 may implement mobility management functions to track a current location of the UE 1902 to facilitate paging, bearer activation/deactivation, handovers, gateway selection, authentication, etc.

The SGW 1926 may terminate an SI interface toward the RAN and route data packets between the RAN and the LTE CN 1922. The SGW 1926 may be a local mobility anchor point for inter-RAN node handovers and also may provide an anchor for inter-3GPP mobility. Other responsibilities may include lawful intercept, charging, and some policy enforcement.

The SGSN 1928 may track a location of the UE 1902 and perform security functions and access control. In addition, the SGSN 1928 may perform inter-EPC node signaling for mobility between different RAT networks; PDN and S-GW selection as specified by MME 1924; MME selection for handovers; etc. The S3 reference point between the MME 1924 and the SGSN 1928 may enable user and bearer information exchange for inter-3GPP access network mobility in idle/active states.

The HSS 1930 may include a database for network users, including subscription-related information to support the network entities’ handling of communication sessions. The HSS 1930 can provide support for routing/roaming, authentication, authorization, naming/addressing resolution, location dependencies, etc. An S6a reference point between the HSS 1930 and the MME 1924 may enable transfer of subscription and authentication data for authenti eating/ authorizing user access to the LTE CN 1920.

The PGW 1932 may terminate an SGi interface toward a data network (DN) 1936 that may include an application/content server 1938. The PGW 1932 may route data packets between the LTE CN 1922 and the data network 1936. The PGW 1932 may be coupled with the SGW 1926 by an S 5 reference point to facilitate user plane tunneling and tunnel management. The PGW 1932 may further include anode for policy enforcement and charging data collection (for example, PCEF). Additionally, the SGi reference point between the PGW 1932 and the data network 1936 may be an operator external public, a private PDN, or an intra operator packet data network, for example, for provision of IMS services. The PGW 1932 may be coupled with a PCRF 1934 via a Gx reference point.

The PCRF 1934 is the policy and charging control element of the LTE CN 1922. The PCRF 1934 may be communicatively coupled to the app/content server 1938 to determine appropriate QoS and charging parameters for service flows. The PCRF 1932 may provision associated rules into a PCEF (via Gx reference point) with appropriate TFT and QCI.

In some embodiments, the CN 1920 may be a 5GC 1940. The 5GC 1940 may include an AUSF 1942, AMF 1944, SMF 1946, UPF 1948, NSSF 1950, NEF 1952, NRF 1954, PCF 1956, UDM 1958, and AF 1960 coupled with one another over interfaces (or “reference points”) as shown. Functions of the elements of the 5GC 1940 may be briefly introduced as follows.

The AUSF 1942 may store data for authentication of UE 1902 and handle authentication-related functionality. The AUSF 1942 may facilitate a common authentication framework for various access types. In addition to communicating with other elements of the 5GC 1940 over reference points as shown, the AUSF 1942 may exhibit an Nausf service-based interface.

The AMF 1944 may allow other functions of the 5GC 1940 to communicate with the UE 1902 and the RAN 1904 and to subscribe to notifications about mobility events with respect to the UE 1902. The AMF 1944 may be responsible for registration management (for example, for registering UE 1902), connection management, reachability management, mobility management, lawful interception of AMF-related events, and access authentication and authorization. The AMF 1944 may provide transport for SM messages between the UE 1902 and the SMF 1946, and act as a transparent proxy for routing SM messages. AMF 1944 may also provide transport for SMS messages between UE 1902 and an SMSF. AMF 1944 may interact with the AUSF 1942 and the UE 1902 to perform various security anchor and context management functions. Furthermore, AMF 1944 may be a termination point of a RAN CP interface, which may include or be an N2 reference point between the RAN 1904 and the AMF 1944; and the AMF 1944 may be a termination point of NAS (Nl) signaling, and perform NAS ciphering and integrity protection. AMF 1944 may also support NAS signaling with the UE 1902 over an N3 IWF interface.

The SMF 1946 may be responsible for SM (for example, session establishment, tunnel management between UPF 1948 and AN 1908); UE IP address allocation and management (including optional authorization); selection and control of UP function; configuring traffic steering at UPF 1948 to route traffic to proper destination; termination of interfaces toward policy control functions; controlling part of policy enforcement, charging, and QoS; lawful intercept (for SM events and interface to LI system); termination of SM parts of NAS messages; downlink data notification; initiating AN specific SM information, sent via AMF 1944 over N2 to AN 1908; and determining SSC mode of a session. SM may refer to management of a PDU session, and a PDU session or “session” may refer to a PDU connectivity service that provides or enables the exchange of PDUs between the UE 1902 and the data network 1936.

The UPF 1948 may act as an anchor point for intra-RAT and inter-RAT mobility, an external PDU session point of interconnect to data network 1936, and a branching point to support multi -homed PDU session. The UPF 1948 may also perform packet routing and forwarding, perform packet inspection, enforce the user plane part of policy rules, lawfully intercept packets (UP collection), perform traffic usage reporting, perform QoS handling for a user plane (e.g., packet filtering, gating, UL/DL rate enforcement), perform uplink traffic verification (e.g., SDF-to-QoS flow mapping), transport level packet marking in the uplink and downlink, and perform downlink packet buffering and downlink data notification triggering. UPF 1948 may include an uplink classifier to support routing traffic flows to a data network.

The NSSF 1950 may select a set of network slice instances serving the UE 1902. The NSSF 1950 may also determine allowed NSSAI and the mapping to the subscribed S-NSSAIs, if needed. The NSSF 1950 may also determine the AMF set to be used to serve the UE 1902, or a list of candidate AMFs based on a suitable configuration and possibly by querying the NRF 1954. The selection of a set of network slice instances for the UE 1902 may be triggered by the AMF 1944 with which the UE 1902 is registered by interacting with the NSSF 1950, which may lead to a change of AMF. The NSSF 1950 may interact with the AMF 1944 via an N22 reference point; and may communicate with another NSSF in a visited network via an N31 reference point (not shown). Additionally, the NSSF 1950 may exhibit an Nnssf service-based interface.

The NEF 1952 may securely expose services and capabilities provided by 3GPP network functions for third party, internal exposure/re-exposure, AFs (e.g., AF 1960), edge computing or fog computing systems, etc. In such embodiments, the NEF 1952 may authenticate, authorize, or throttle the AFs. NEF 1952 may also translate information exchanged with the AF 1960 and information exchanged with internal network functions. For example, the NEF 1952 may translate between an AF-Service-Identifier and an internal 5GC information. NEF 1952 may also receive information from other NFs based on exposed capabilities of other NFs. This information may be stored at the NEF 1952 as structured data, or at a data storage NF using standardized interfaces. The stored information can then be re exposed by the NEF 1952 to other NFs and AFs, or used for other purposes such as analytics. Additionally, the NEF 1952 may exhibit an Nnef service-based interface.

The NRF 1954 may support service discovery functions, receive NF discovery requests from NF instances, and provide the information of the discovered NF instances to the NF instances. NRF 1954 also maintains information of available NF instances and their supported services. As used herein, the terms “instantiate,” “instantiation,” and the like may refer to the creation of an instance, and an “instance” may refer to a concrete occurrence of an object, which may occur, for example, during execution of program code. Additionally, the NRF 1954 may exhibit the Nnrf service-based interface.

The PCF 1956 may provide policy rules to control plane functions to enforce them, and may also support unified policy framework to govern network behavior. The PCF 1956 may also implement a front end to access subscription information relevant for policy decisions in a UDR of the UDM 1958. In addition to communicating with functions over reference points as shown, the PCF 1956 exhibit an Npcf service-based interface.

The UDM 1958 may handle subscription-related information to support the network entities’ handling of communication sessions, and may store subscription data of UE 1902. For example, subscription data may be communicated via an N8 reference point between the UDM 1958 and the AMF 1944. The UDM 1958 may include two parts, an application front end and a UDR. The UDR may store subscription data and policy data for the UDM 1958 and the PCF 1956, and/or structured data for exposure and application data (including PFDs for application detection, application request information for multiple UEs 1902) for the NEF 1952. The Nudr service-based interface may be exhibited by the UDR 221 to allow the UDM 1958, PCF 1956, and NEF 1952 to access a particular set of the stored data, as well as to read, update (e.g., add, modify), delete, and subscribe to notification of relevant data changes in the UDR. The UDM may include a UDM-FE, which is in charge of processing credentials, location management, subscription management and so on. Several different front ends may serve the same user in different transactions. The UDM-FE accesses subscription information stored in the UDR and performs authentication credential processing, user identification handling, access authorization, registration/mobility management, and subscription management. In addition to communicating with other NF s over reference points as shown, the UDM 1958 may exhibit the Nudm service-based interface.

The AF 1960 may provide application influence on traffic routing, provide access to NEF, and interact with the policy framework for policy control.

In some embodiments, the 5GC 1940 may enable edge computing by selecting operator/3^rd party services to be geographically close to a point that the UE 1902 is attached to the network. This may reduce latency and load on the network. To provide edge-computing implementations, the 5GC 1940 may select a UPF 1948 close to the UE 1902 and execute traffic steering from the UPF 1948 to data network 1936 via the N6 interface. This may be based on the UE subscription data, UE location, and information provided by the AF 1960. In this way, the AF 1960 may influence UPF (re)selection and traffic routing. Based on operator deployment, when AF 1960 is considered to be a trusted entity, the network operator may permit AF 1960 to interact directly with relevant NFs. Additionally, the AF 1960 may exhibit an Naf service-based interface.

The data network 1936 may represent various network operator services, Internet access, or third party services that may be provided by one or more servers including, for example, application/ content server 1938.

Figure 20 schematically illustrates a wireless network 2000 in accordance with various embodiments. The wireless network 2000 may include a UE 2002 in wireless communication with an AN 2004. The UE 2002 and AN 2004 may be similar to, and substantially interchangeable with, like-named components described elsewhere herein.

The UE 2002 may be communicatively coupled with the AN 2004 via connection 2006. The connection 2006 is illustrated as an air interface to enable communicative coupling, and can be consistent with cellular communications protocols such as an LTE protocol or a 5GNR protocol operating at mmWave or sub-6GHz frequencies.

The UE 2002 may include a host platform 2008 coupled with a modem platform 2010. The host platform 2008 may include application processing circuitry 2012, which may be coupled with protocol processing circuitry 2014 of the modem platform 2010. The application processing circuitry 2012 may run various applications for the UE 2002 that source/sink application data. The application processing circuitry 2012 may further implement one or more layer operations to transmit/receive application data to/from a data network. These layer operations may include transport (for example UDP) and Internet (for example, IP) operations The protocol processing circuitry 2014 may implement one or more of layer operations to facilitate transmission or reception of data over the connection 2006. The layer operations implemented by the protocol processing circuitry 2014 may include, for example, MAC, RLC, PDCP, RRC and NAS operations.

The modem platform 2010 may further include digital baseband circuitry 2016 that may implement one or more layer operations that are “below” layer operations performed by the protocol processing circuitry 2014 in a network protocol stack. These operations may include, for example, PHY operations including one or more of HARQ-ACK functions, scrambling/descrambling, encoding/decoding, layer mapping/de-mapping, modulation symbol mapping, received symbol/bit metric determination, multi-antenna port precoding/decoding, which may include one or more of space-time, space-frequency or spatial coding, reference signal generation/detection, preamble sequence generation and/or decoding, synchronization sequence generation/detection, control channel signal blind decoding, and other related functions.

The modem platform 2010 may further include transmit circuitry 2018, receive circuitry 2020, RF circuitry 2022, and RF front end (RFFE) 2024, which may include or connect to one or more antenna panels 2026. Briefly, the transmit circuitry 2018 may include a digital -to-analog converter, mixer, intermediate frequency (IF) components, etc.; the receive circuitry 2020 may include an analog-to-digital converter, mixer, IF components, etc.; the RF circuitry 2022 may include a low-noise amplifier, a power amplifier, power tracking components, etc.; RFFE 2024 may include filters (for example, surface/bulk acoustic wave filters), switches, antenna tuners, beamforming components (for example, phase-array antenna components), etc. The selection and arrangement of the components of the transmit circuitry 2018, receive circuitry 2020, RF circuitry 2022, RFFE 2024, and antenna panels 2026 (referred generically as “transmit/receive components”) may be specific to details of a specific implementation such as, for example, whether communication is TDM or FDM, in mmWave or sub-6 gHz frequencies, etc. In some embodiments, the transmit/receive components may be arranged in multiple parallel transmit/receive chains, may be disposed in the same or different chips/modules, etc.

In some embodiments, the protocol processing circuitry 2014 may include one or more instances of control circuitry (not shown) to provide control functions for the transmit/receive components.

A UE reception may be established by and via the antenna panels 2026, RFFE 2024, RF circuitry 2022, receive circuitry 2020, digital baseband circuitry 2016, and protocol processing circuitry 2014. In some embodiments, the antenna panels 2026 may receive a transmission from the AN 2004 by receive-beamforming signals received by a plurality of antennas/antenna elements of the one or more antenna panels 2026.

A UE transmission may be established by and via the protocol processing circuitry 2014, digital baseband circuitry 2016, transmit circuitry 2018, RF circuitry 2022, RFFE 2024, and antenna panels 2026. In some embodiments, the transmit components of the UE 2004 may apply a spatial filter to the data to be transmitted to form a transmit beam emitted by the antenna elements of the antenna panels 2026.

Similar to the UE 2002, the AN 2004 may include a host platform 2028 coupled with a modem platform 2030. The host platform 2028 may include application processing circuitry 2032 coupled with protocol processing circuitry 2034 of the modem platform 2030. The modem platform may further include digital baseband circuitry 2036, transmit circuitry 2038, receive circuitry 2040, RF circuitry 2042, RFFE circuitry 2044, and antenna panels 2046. The components of the AN 2004 may be similar to and substantially interchangeable with like- named components of the UE 2002. In addition to performing data transmission/reception as described above, the components of the AN 2008 may perform various logical functions that include, for example, RNC functions such as radio bearer management, uplink and downlink dynamic radio resource management, and data packet scheduling.

Figure 21 is a block diagram illustrating components, according to some example embodiments, able to read instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and perform any one or more of the methodologies discussed herein. Specifically, Figure 21 shows a diagrammatic representation of hardware resources 2100 including one or more processors (or processor cores) 2110, one or more memory /storage devices 2120, and one or more communication resources 2130, each of which may be communicatively coupled via a bus 2140 or other interface circuitry. For embodiments where node virtualization (e.g., NFV) is utilized, a hypervisor 2102 may be executed to provide an execution environment for one or more network slices/sub-slices to utilize the hardware resources 2100.

The processors 2110 may include, for example, a processor 2112 and a processor 2114. The processors 2110 may be, for example, a central processing unit (CPU), a reduced instruction set computing (RISC) processor, a complex instruction set computing (CISC) processor, a graphics processing unit (GPU), a DSP such as a baseband processor, an ASIC, an FPGA, a radio-frequency integrated circuit (RFIC), another processor (including those discussed herein), or any suitable combination thereof. The memory /storage devices 2120 may include main memory, disk storage, or any suitable combination thereof. The memory /storage devices 2120 may include, but are not limited to, any type of volatile, non-volatile, or semi-volatile memory such as dynamic random access memory (DRAM), static random access memory (SRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), Flash memory, solid-state storage, etc.

The communication resources 2130 may include interconnection or network interface controllers, components, or other suitable devices to communicate with one or more peripheral devices 2104 or one or more databases 2106 or other network elements via a network 2108. For example, the communication resources 2130 may include wired communication components (e.g., for coupling via USB, Ethernet, etc.), cellular communication components, NFC components, Bluetooth® (or Bluetooth® Low Energy) components, Wi-Fi® components, and other communication components.

Instructions 2150 may comprise software, a program, an application, an applet, an app, or other executable code for causing at least any of the processors 2110 to perform any one or more of the methodologies discussed herein. The instructions 2150 may reside, completely or partially, within at least one of the processors 2110 (e.g., within the processor’s cache memory), the memory /storage devices 2120, or any suitable combination thereof. Furthermore, any portion of the instructions 2150 may be transferred to the hardware resources 2100 from any combination of the peripheral devices 2104 or the databases 2106. Accordingly, the memory of processors 2110, the memory /storage devices 2120, the peripheral devices 2104, and the databases 2106 are examples of computer-readable and machine-readable media.

EXAMPLE PROCEDURES

In some embodiments, the electronic device(s), network(s), system(s), chip(s) or component(s), or portions or implementations thereof, of Figures 19-21, or some other figure herein, may be configured to perform one or more processes, techniques, or methods as described herein, or portions thereof. One such process 2200 is depicted in Figure X-l. For example, the process 2200 may include, at 2202, determining downlink control information (DCI) that includes an indication of activation or deactivation of a rate-matching resource for a physical downlink shared channel (PDSCH) transmission. The process 2200 further includes, at 2204, encoding a message that includes the DCI for transmission to a user equipment (UE).

Figure 23 illustrates another process 2300 in accordance with various embodiments. The process 2300 may include, at 2302, receiving downlink control information (DCI) that includes an indication of activation or deactivation of one or more rate-matching resources for a physical downlink shared channel (PDSCH) transmission. The process 2300 further includes, at 2304, monitoring for a physical downlink control channel (PDCCH) transmission during the PDSCH transmission based on the indication.

For the processes 2200 and 2300, the rate-matching resource may have a variety of configurations. For example, the rate-matching resource may be time-domain configured.

In some embodiments, the rate-matching resource is configured at a cell level. In some embodiments, the rate-matching resource is based on a control resource set (CORESET). For example, a time domain resource may be determined based on one or more parameters of the CORESET. In some embodiments, a gap for beam switching is determined based on the CORESET.

The DCI may include a variety of information. For example, in some embodiments, the DCI includes an indication of an activation of the rate-matching resource configured at a bandwidth part (BWP) level. In some embodiments, the DCI is further to indicate that a subset of physical downlink control channel (PDCCH) monitoring occasions is activated during the PDSCH transmission. In some embodiments, the DCI is further to indicate a PDCCH monitoring pattern used within the PDSCH transmission. In some embodiments, the DCI is further to indicate a position of a PDCCH monitoring occasion activated during the PDSCH transmission. In some embodiments, the DCI is further to indicate a subset of PDCCH monitoring occasions activated during the PDSCH transmission. In some embodiments, the DCI is further to indicate one or more groups of search space sets for PDCCH monitoring by the UE.

Figure 24 illustrates another process 2400 in accordance with various embodiments. The process 2400 may include, at 2402, encoding a first channel for transmission on a first carrier and a second channel for transmission on a second carrier in accordance with carrier aggregation.

At 2404, the process 2400 may further include encoding, for transmission to a gNB, an indication of a timing difference of the transmission on the first carrier and the second carrier.

In some embodiments, the process 2400 may be performed by a UE or a portion thereof. The indication of the timing difference may be used by the UE and/or the gNB to determine whether the first and second channels are overlapped. If the first and second channels are determined to be overlapped, uplink control information associated with the first and second channels may be multiplexed or dropped. If it is determined that the first and second channels are not overlapped, then uplink control information associated with the first and second channels may be transmitted separately.

Figure 25 illustrates another process in accordance with various embodiments. At 2502, the process may include receiving a first channel from a UE on a first carrier and a second channel from the UE on a second carrier in accordance with carrier aggregation.

At 2504, the process 2500 may further include receiving, from the UE, an indication of a transmission timing difference of the transmission on the first carrier and the second carrier.

At 2506, the process 2500 may further include processing the first and second channels based on the indicated transmission timing difference. In some embodiments, the processing may include identifying and/or processing uplink control information (e.g.,

HARQ feedback or other information) associated with the first and/or second channels based on the indicated transmission timing difference.

In some embodiments, the process 2500 may be performed by a gNB or a portion thereof. The indication of the timing difference may be used by the UE and/or the gNB to determine whether the first and second channels are overlapped. If the first and second channels are determined to be overlapped, uplink control information associated with the first and second channels may be multiplexed or dropped. If it is determined that the first and second channels are not overlapped, then uplink control information associated with the first and second channels may be transmitted separately.

For one or more embodiments, at least one of the components set forth in one or more of the preceding figures may be configured to perform one or more operations, techniques, processes, and/or methods as set forth in the example section below. For example, the baseband circuitry as described above in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth below. For another example, circuitry associated with a UE, base station, network element, etc. as described above in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth below in the example section.

EXAMPLES

Example 1 may include a method of wireless communication for a fifth generation (5G) or new radio (NR) system, the method comprising: configuring, by a next-generation NodeB (gNB), rate-matching resources for physical downlink shared channel (PDSCH) in a time domain; and activating, by the gNB, a subset of the configured rate-matching resources via downlink control information (DCI).

Example 2 may include the method of example 1 or some other example herein, wherein a resource block level bitmap in the frequency domain may not be needed as part of configuration for rate-matching resource.

Example 3 may include the method of example 2 or some other example herein, wherein when rate-matching resource is configured as cell level, if activated or configured, all the resource in system bandwidth is used for PDSCH rate-matching; wherein when rate matching resource is configured as bandwidth part (BWP) level, if activated or configured, all the resource in BWP is used for PDSCH rate-matching.

Example 4 may include the method of example 1 or some other example herein, wherein when control resource set (CORESET) is configured as rate-matching resource, only CORESET resource in time domain is needed for rate-matching resource.

Example 5 may include the method of example 1 or some other example herein, wherein when CORESET is configured as rate-matching resource, some gaps before and/or after CORESET may be configured via minimum system information (MSI), remaining minimum system information (RMSI), other system information (OSI) or dedicated radio resource control (RRC) signaling.

Example 6 may include the method of example 1 or some other example herein, wherein one field in the DCI for scheduling PDSCH can be used to indicate that a subset of PDCCH monitoring occasions is activated during PDSCH transmission duration.

Example 7 may include the method of example 1 or some other example herein, wherein a set of PDCCH monitoring occasion pattern within PDSCH transmission duration can be configured by higher layers, where one field in the DCI for scheduling PDSCH can be used to indicate which PDCCH monitoring occasion pattern is used within the PDSCH transmission duration, and UE shall perform PDSCH rate-matching around CORESET or detected PDCCH on the activated PDCCH monitoring occasion.

Example 8 may include the method of example 1 or some other example herein, wherein the subset of PDCCH monitoring occasion can be predefined in the specification. In one example, one field in the DCI can be used to indicate whether even or odd positions of PDCCH monitoring occasions are activated during PDSCH transmission duration.

Example 9 may include the method of example 1 or some other example herein, wherein a subset of PDCCH monitoring occasions that is activated during PDSCH transmission duration is predefined or configured by high layer signaling. Example 10 may include the method of example 1 or some other example herein, wherein more than one groups of search space sets may be configured for PDCCH monitoring; wherein when two groups of search space sets are configured for PDCCH monitoring, when the PDCCH in first group of search space sets is detected, UE shall switch from the first group of search space sets to the second group of search space sets.

Example 11 may include the method of example 1 or some other example herein, wherein when UE receives the PDCCH in the first group of search space sets, UE shall start or restart a timer; wherein When the timer expires, UE shall switch from the second group of search space sets back to the first group of search space sets.

Example 12 may include the method of example 1 or some other example herein, wherein within PDSCH transmission, one or more code block (CB) or code block group (CBG) or PDSCH may be replaced by a PDCCH carrying DCI.

Example 13 may include the method of example 1 or some other example herein, wherein demodulation reference signal (DMRS) associated with PDSCH or PDCCH may be used to indicate the activation or deactivation of PDCCH monitoring occasions within a PDSCH transmission duration.

Example 14 may include the method of example 1 or some other example herein, wherein when PDSCH transmission including one or more CB/CBGs collides activated rate matching resource, e.g., CORESET or activated PDCCH monitoring occasion or SSB block, CB/CBG or the PDSCH is not transmitted on the activated rate-matching resource.

Example 15 may include the method of example 14 or some other example herein, wherein transport block size (TBS) is determined in accordance with the duration of first CB/CBG or PDSCH or nominal resource allocation.

Example 16 may include te method of example 14 or some other example herein, wherein the TBS on the impacted CB/CBGs or PDSCHs when colliding with activated rate matching resources can be determined in accordance with actual number of symbols or resources excluding the activated rate-matching resources or actual resource allocation.

Example 17 may include the method of example 1 or some other example herein, wherein when PDSCH transmission including one or more CB/CBGs collides activated rate matching resource, e.g., CORESET or deactivated PDCCH monitoring occasion or SSB block, CB/CBG or the PDSCH is not transmitted on the activated rate-matching resource; wherein impacted CB/CBG or PDSCH continues to be transmitted after the activated rate matching resource, and spans the number of symbols as indicated in the DCI. Example 18 may include the method of example 1 or some other example herein, wherein PDSCH allocation is first based on the starting and length indicator value (SLIV) indicated in the DCI and configured rate-matching resource within PDSCH transmission duration; wherein when one CB/CBG or PDSCH collides with configured rate-matching resource, the CB/CBG or PDSCH continues to be mapped after the configured rate-matching resource and spans indicated number of symbols via SLIV.

Example 19 may include the method of example 1 or some other example herein, wherein if PDSCH resource allocation overlaps with the symbols which contain synchronization signal block (SSB) transmission, UE shall assume that the OFDM symbols containing SSB transmission are not available for PDSCH transmission;

Example 20 may include the method of example 1 or some other example herein, wherein When other DL channels or signals, including PDCCH, channel state information- reference signal (CSI-RS), phase tracking reference signal (PT-RS), etc., overlaps with the symbols which contains SSB transmission, UE assume that the OFDM symbols containing SSB transmission are not available for other DL channel transmission.

Example 21 may include the method of example 1 or some other example herein, wherein an indication on whether PDSCH can be transmitted on a symbol next to the symbols for CORESET/PDCCH or SSB transmission with one or more SSB indexes may be configured by higher layers via RRC signalling

Example 22 may include the method of example 1 or some other example herein, wherein whether PDSCH can be transmitted on a symbol next to the symbols for CORESET/PDCCH or SSB may be derived by the TCI state for the PDSCH.

Example 23 includes a method comprising: determining downlink control information (DCI) that includes an indication of activation or deactivation of a rate-matching resource for a physical downlink shared channel (PDSCH) transmission; and encoding a message that includes the DCI for transmission to a user equipment (UE).

Example 24 includes the method of example 23 or some other example herein, wherein the rate-matching resource is time-domain configured.

Example 25 includes the method of example 23 or some other example herein, wherein the rate-matching resource is configured at a cell level.

Example 26 includes the method of example 25 or some other example herein, wherein the DCI includes an indication of an activation of the rate-matching resource configured at a bandwidth part (BWP) level. Example 27 includes the method of example 23 or some other example herein, wherein the rate-matching resource is based on a control resource set (CORESET) or a synchronization signal block (SSB).

Example 28 includes the method of example 27 or some other example herein, wherein a time domain resource is determined based on one or more parameters of the CORESET or SSB.

Example 29 includes the method of example 23 or some other example herein, wherein a gap for beam switching is determined based on the CORESET or SSB.

Example 30 includes the method of example 23 or some other example herein, wherein the DCI is further to indicate that a subset of physical downlink control channel (PDCCH) monitoring occasions is activated during the PDSCH transmission.

Example 31 includes the method of example 30 or some other example herein, wherein the DCI is further to indicate a PDCCH monitoring pattern used within the PDSCH transmission.

Example 32 includes the method of example 23 or some other example herein, wherein the DCI is further to indicate a position of a PDCCH monitoring occasion activated during the PDSCH transmission.

Example 33 includes the method of example 23 or some other example herein, wherein the DCI is further to indicate a subset of PDCCH monitoring occasions activated during the PDSCH transmission.

Example 34 includes the method of example 23 or some other example herein, wherein the DCI is further to indicate one or more groups of search space sets for PDCCH monitoring by the UE.

Example 35 includes the method of any of examples 23-34 or some other example herein, wherein the method is performed by a next-generation NodeB (gNB) or portion thereof.

Example 36 includes a method comprising: receiving a downlink control information (DCI) message that includes an indication of activation or deactivation of a rate-matching resource for a physical downlink shared channel (PDSCH) transmission; and monitoring for a physical downlink control channel (PDCCH) transmission during the PDSCH transmission based on the DCI message.

Example 37 includes the method of example 36 or some other example herein, further comprising determining that one or more orthogonal frequency division multiplexing (OFDM) symbols of a synchronization signal block (SSB) transmission are not available for the PDSCH transmission based on an overlap between a PDSCH resource allocation and the SSB transmission.

Example 38 includes the method of example 36 or some other example herein, further comprising determining that one or more orthogonal frequency division multiplexing (OFDM) symbols of a synchronization signal block (SSB) transmission are not available for downlink (DL) transmission based on an overlap between a DL signal and the SSB transmission.

Example 39 includes the method of example 38 or some other example herein, wherein the DL signal includes PDCCH, a channel state information-reference signal (CSI- RS), or a phase tracking reference signal (PT-RS).

Example 40 includes the method of any of examples 36-39 or some other example herein, wherein the method is performed by a user equipment (UE) or portion thereof.

Example 41 may include a method of wireless communication to multiplex UL transmissions on multiple carriers with different uplink transmission timings.

Example 42 may include the method of example 41 or some other example herein, wherein UE reports the actual transmission timing difference d between the two TAGs or two carriers to gNB.

Example 43 may include the method of example 42 or some other example herein, wherein the reported timing difference is the absolute time value, or, the reported timing difference is quantized using a granularity of one or a fraction of the symbol length with a reference SCS.

Example 44 may include the method of example 42 or some other example herein, wherein the timing difference is reported periodically, or event triggered.

Example 45 may include the method of example 42 or some other example herein, wherein the timing difference is reported in a measurement report, MAC CE, PUSCH or PUCCH.

Example 46 may include the method of example 42 or some other example herein, wherein UE determines whether two UL channels on the two UL carriers are overlapped or not based on the actual transmission timings of the two UL carriers. gNB determines whether two UL channels on the two UL carriers are overlapping or not based on the logical timings of the two UL channels and the reported timing difference d.

Example 47 may include the method of example 42 or some other example herein, wherein UE and gNB determines whether two UL channels on the two UL carriers are overlapped or not based on the logical timings of the two UL channels and the reported timing difference d.

Example 48 may include the method of example 41 or some other example herein, wherein the logical timings of two UL channels, adjusted by an offset, are used to determine whether the two UL channels are overlap or not. The offset reflects the time difference between the two TAGs or the two UL carriers.

Example 49 may include the method of example 48 or some other example herein, wherein if the two UL channels, after applying the offset to the logical timings, have at least one symbol overlapped, the UL information associated with the two UL channels are multiplexed or dropped. Otherwise, the two UL channels are transmitted separately.

Example 50 may include the method of example 41 or some other example herein, whether two UL channels are overlapped or not is determined by the logical timing of the two UL carriers.

Example 51 may include the method of example 41 or some other example herein, wherein a single DL time reference to derive UL transmission timings is used for the multiple TAGs.

Example 52 may include the method of example 41 or some other example herein, whether multiple UL channels are overlap or not are checked by the logical timing of the two UL carriers with a larger granularity.

Example 53 may include the method of examples 42 to 52 or some other example herein, wherein for a PUSCH that is scheduled by a UL grant, the UL grant indicates whether/which UL control channel(s) is multiplexed on the PUSCH.

Example 54 may include a method comprising: encoding a first channel for transmission on a first carrier and a second channel for transmission on a second carrier in accordance with carrier aggregation; and encoding, for transmission, an indication of a timing difference of the transmission on the first carrier and the second carrier.

Example 55 may include the method of example 54 or some other example herein, wherein the first carrier is included in a first timing advance group (TAG) and the second carrier is included in a second timing advance group (TAG), wherein the indication of the timing difference indicates the transmission timing difference between the first TAG and the second TAG.

Example 56 may include the method of example 54-55 or some other example herein, wherein the indication of the timing difference is an absolute time value. Example 57 may include the method of example 54-56 or some other example herein, wherein the indication of the timing difference is quantized using a granularity of one symbol length or a fraction of a symbol length with respect to a reference subcarrier spacing (SCS).

Example 58 may include the method of example 54-57 or some other example herein, wherein the indication of the timing difference is transmitted periodically.

Example 59 may include the method of example 54-58 or some other example herein, further comprising determining a triggering event, wherein the indication of the timing difference is transmitted based on the determination.

Example 60 may include the method of example 59 or some other example herein, wherein the triggering event is a request received from a gNB.

Example 61 may include the method of example 54-60 or some other example herein, wherein the indication of the timing difference is transmitted in a measurement report, a MAC CE, a PUSCH, or a PUCCH.

Example 62 may include the method of example 54-61 or some other example herein, further comprising determining whether the first channel and the second channel are overlapped based on respective transmission timings of the first channel and the second channel.

Example 63 may include the method of example 62 or some other example herein, wherein the determination whether the first channel and the second channel are overlapped is based further on respective logical timings of the first channel and the second channel.

Example 64 may include the method of example 54-63 or some other example herein, further comprising determining whether the first channel and the second channel are overlapped based on whether logical timings of the first and second channels, adjusted by an offset, have at least one symbol overlapped.

Example 65 may include the method of example 64 or some other example herein, wherein the offset corresponds to the timing difference.

Example 66 may include the method of example 62-65 or some other example herein, wherein if it is determined that the first and second channels are overlapped, uplink control information associated with the first and second channels are multiplexed or dropped.

Example 67 may include the method of example 62-66 or some other example herein, wherein if it is determined that the first and second channels are not overlapped, uplink control information associated with the first and second channels are transmitted separately. Example 68 may include the method of example 54-67 or some other example herein, further comprising determining transmission timings for the first and second channels based on a single downlink time reference.

Example 69 may include the method of example 54-68 or some other example herein, wherein the first channel is scheduled by an uplink grant, and wherein the uplink grant indicates whether and/or which control channels are multiplexed on the first channel.

Example 70 may include the method of example 54-69 or some other example herein, wherein at least one of the first or second carriers has a frequency of greater than 52.6 gigahertz (GHz).

Example 71 may include the method of example 54-70 or some other example herein, wherein the method is performed by a UE or a portion thereof.

Example 72 may include a method comprising: receiving a first channel from a UE on a first carrier and a second channel from the UE on a second carrier in accordance with carrier aggregation; and receiving, from the UE, an indication of a transmission timing difference of the transmission on the first carrier and the second carrier.

Example 72a may include the method of example 72 or some other example herein, further comprising processing the first and second channels based on the indication.

Example 73 may include the method of example 72-72a or some other example herein, wherein the first carrier is included in a first timing advance group (TAG) and the second carrier is included in a second timing advance group (TAG), wherein the indication of the transmission timing difference indicates the transmission timing difference between the first TAG and the second TAG.

Example 74 may include the method of example 72-73 or some other example herein, wherein the indication of the transmission timing difference is an absolute time value.

Example 75 may include the method of example 72-74 or some other example herein, wherein the indication of the transmission timing difference is quantized using a granularity of one symbol length or a fraction of a symbol length with respect to a reference subcarrier spacing (SCS).

Example 76 may include the method of example 72-75 or some other example herein, wherein the indication of the transmission timing difference is received from the UE periodically. Example 77 may include the method of example 72-76 or some other example herein, wherein the indication of the transmission timing difference is received based on a triggering event.

Example 78 may include the method of example 72-77 or some other example herein, further comprising encoding, for transmission to the UE, a request for the indication of the timing difference, wherein the indication of the transmission timing difference is received in response to the request.

Example 79 may include the method of example 72-78 or some other example herein, wherein the indication of the transmission timing difference is received in a measurement report, a MAC CE, a PUSCH, or a PUCCH.

Example 80 may include the method of example 72-79 or some other example herein, further comprising determining whether the first channel and the second channel are overlapped based on the indication of the transmission timing difference.

Example 81 may include the method of example 80 or some other example herein, wherein the determination whether the first channel and the second channel are overlapped is based further on respective logical timings of the first channel and the second channel.

Example 82 may include the method of example 72-81 or some other example herein, further comprising determining whether the first channel and the second channel are overlapped based on whether logical timings of the first and second channels, adjusted by an offset, have at least one symbol overlapped.

Example 83 may include the method of example 82 or some other example herein, wherein the offset corresponds to the transmission timing difference.

Example 84 may include the method of example 80-83 or some other example herein, further comprising determining that uplink control information associated with the first and second channels are multiplexed or dropped based on a determination that the first and second channels are overlapped,.

Example 85 may include the method of example 80-84 or some other example herein, further comprising determining that uplink control information associated with the first and second channels are transmitted separately based on a determination that the first and second channels are not overlapped.

Example 86 may include the method of example 84-85 or some other example herein, further comprising receiving the uplink control information based on the determination.

Example 87 may include the method of example 72-86 or some other example herein, further comprising scheduling transmission of the first channel by an uplink grant, and wherein the uplink grant indicates whether and/or which control channels are multiplexed on the first channel.

Example 88 may include the method of example 72-87 or some other example herein, wherein at least one of the first or second carriers has a frequency of greater than 52.6 gigahertz (GHz).

Example 89 may include the method of example 72-88 or some other example herein, wherein the method is performed by a gNB or a portion thereof.

Example 90 may include an apparatus comprising means to perform one or more elements of a method described in or related to any of examples 1-89, or any other method or process described herein.

Example 91 may include one or more non-transitory computer-readable media comprising instructions to cause an electronic device, upon execution of the instructions by one or more processors of the electronic device, to perform one or more elements of a method described in or related to any of examples 1-89, or any other method or process described herein.

Example 92 may include an apparatus comprising logic, modules, or circuitry to perform one or more elements of a method described in or related to any of examples 1-89, or any other method or process described herein.

Example 93 may include a method, technique, or process as described in or related to any of examples 1-89, or portions or parts thereof.

Example 94 may include an apparatus comprising: one or more processors and one or more computer-readable media comprising instructions that, when executed by the one or more processors, cause the one or more processors to perform the method, techniques, or process as described in or related to any of examples 1-89, or portions thereof.

Example 95 may include a signal as described in or related to any of examples 1-89, or portions or parts thereof.

Example 96 may include a datagram, packet, frame, segment, protocol data unit (PDU), or message as described in or related to any of examples 1-89, or portions or parts thereof, or otherwise described in the present disclosure.

Example 97 may include a signal encoded with data as described in or related to any of examples 1-89, or portions or parts thereof, or otherwise described in the present disclosure. Example 98 may include a signal encoded with a datagram, packet, frame, segment, protocol data unit (PDU), or message as described in or related to any of examples 1-89, or portions or parts thereof, or otherwise described in the present disclosure.

Example 99 may include an electromagnetic signal carrying computer-readable instructions, wherein execution of the computer-readable instructions by one or more processors is to cause the one or more processors to perform the method, techniques, or process as described in or related to any of examples 1-89, or portions thereof.

Example 100 may include a computer program comprising instructions, wherein execution of the program by a processing element is to cause the processing element to carry out the method, techniques, or process as described in or related to any of examples 1-89, or portions thereof.

Example 101 may include a signal in a wireless network as shown and described herein.

Example 102 may include a method of communicating in a wireless network as shown and described herein.

Example 103 may include a system for providing wireless communication as shown and described herein.

Example 104 may include a device for providing wireless communication as shown and described herein.

Any of the above-described examples may be combined with any other example (or combination of examples), unless explicitly stated otherwise. The foregoing description of one or more implementations provides illustration and description, but is not intended to be exhaustive or to limit the scope of embodiments to the precise form disclosed. Modifications and variations are possible in light of the above teachings or may be acquired from practice of various embodiments.

Abbreviations

Unless used differently herein, terms, definitions, and abbreviations may be consistent with terms, definitions, and abbreviations defined in 3GPP TR 21.905 vl6.0.0 (2019-06). For the purposes of the present document, the following abbreviations may apply to the examples and embodiments discussed herein. 3GPP Third Generation 35 ASN.1 Abstract Syntax CAPEX CAPital Partnership Notation One 70 Expenditure

Project AUSF Authentication CBRA Contention Based

4G Fourth Generation Server Function Random Access 5G Fifth Generation AWGN Additive CC Component 5GC 5G Core network 40 White Gaussian Carrier, Country ACK Noise 75 Code, Cryptographic

Acknowledgemen BAP Backhaul Checksum t Adaptation Protocol CCA Clear Channel

AF Application BCH Broadcast Assessment Function 45 Channel CCE Control Channel

AM Acknowledged BER Bit Error Ratio 80 Element Mode BFD Beam Failure CCCH Common Control

AMBRAggregate Detection Channel Maximum Bit Rate BLER Block Error Rate CE Coverage AMF Access and 50 BPSK Binary Phase Shift Enhancement Mobility Keying 85 CDM Content Delivery

Management BRAS Broadband Network

Function Remote Access CDMA Code-

AN Access Network Server Division Multiple ANR Automatic 55 BSS Business Support Access Neighbour Relation System 90 CFRA Contention Free AP Application BS Base Station Random Access Protocol, Antenna BSR Buffer Status CG Cell Group

Port, Access Point Report Cl Cell Identity API Application 60 BW Bandwidth CID Cell-ID (e g., Programming Interface BWP Bandwidth Part 95 positioning method) APN Access Point C-RNTI Cell Radio CIM Common Name Network Temporary Information Model

ARP Allocation and Identity CIR Carrier to Retention Priority 65 CA Carrier Interference Ratio

ARQ Automatic Repeat Aggregation, 100 CK Cipher Key Request Certification CM Connection

AS Access Stratum Authority Management, Conditional CRAN Cloud Radio CSMA/CA CSMA Mandatory Access Network, with collision avoidance CM AS Commercial 35 Cloud RAN CSS Common Search Mobile Alert Service CRB Common 70 Space, Cell- specific CMD Command Resource Block Search Space CMS Cloud CRC Cyclic CTS Clear-to-Send Management System Redundancy Check CW Codeword CO Conditional 40 CRI Channel-State CWS Contention Optional Information Resource 75 Window Size

CoMP Coordinated Indicator, CSI-RS D2D Device-to-Device

Multi-Point Resource DC Dual

CORESET Control Indicator Connectivity, Direct

Resource Set 45 C-RNTI Cell RNTI Current

COTS Commercial Off- CS Circuit Switched 80 DCI Downlink Control

The-Shelf CSAR Cloud Service Information

CP Control Plane, Archive DF Deployment Cyclic Prefix, CSI Channel-State Flavour

Connection Point 50 Information DL Downlink CPD Connection Point CSI-IM CSI 85 DMTF Distributed Descriptor Interference Management Task Force

CPE Customer Premise Measurement DPDK Data Plane Equipment CSI-RS CSI Development Kit

CPICHCommon Pilot 55 Reference Signal DM-RS, DMRS Channel CSI-RS RP CSI 90 Demodulation

CQI Channel Quality reference signal Reference Signal Indicator received power DN Data network

CPU CSI processing CSI-RSRQ CSI DRB Data Radio Bearer unit, Central Processing 60 reference signal DRS Discovery Unit received quality 95 Reference Signal C/R CSI-SINR CSI signal- DRX Discontinuous

Command/Respon to-noise and Reception se field bit interference ratio DSL Domain Specific 65 CSMA Carrier Sense Language. Digital Multiple Access 100 Subscriber Line DSLAM DSL 35 EMS Element E-UTRAN Evolved

Access Multiplexer Management System UTRAN DwPTS Downlink eNB evolved NodeB, 70 EV2X Enhanced V2X

Pilot Time Slot E-UTRAN Node B F1AP FI Application E-LAN Ethernet EN-DC E-UTRA- Protocol

Local Area Network 40 NR Dual Fl-C FI Control plane

E2E End-to-End Connectivity interface ECCA extended clear EPC Evolved Packet 75 Fl-U FI User plane channel Core interface assessment, EPDCCH enhanced FACCH Fast extended CCA 45 PDCCH, enhanced Associated Control ECCE Enhanced Control Physical CHannel Channel Element, Downlink Control 80 FACCH/F Fast

Enhanced CCE Cannel Associated Control ED Energy Detection EPRE Energy per Channel/Full rate EDGE Enhanced 50 resource element FACCH/H Fast Datarates for GSM EPS Evolved Packet Associated Control

Evolution (GSM System 85 Channel/Half rate Evolution) EREG enhanced REG, FACH Forward Access

EGMF Exposure enhanced resource Channel Governance 55 element groups FAUSCH Fast

Management ETSI European Uplink Signalling

Function Telecommunicatio 90 Channel

EGPRS Enhanced ns Standards Institute FB Functional Block

GPRS ETWS Earthquake and FBI Feedback

EIR Equipment 60 Tsunami Warning Information Identity Register System FCC Federal eLAA enhanced eUICC embedded UICC, 95 Communications Licensed Assisted embedded Universal Commission

Access, enhanced Integrated Circuit FCCH Frequency

LAA 65 Card Correction CHannel

EM Element Manager E-UTRA Evolved FDD Frequency eMBB Enhanced Mobile UTRA 100 Division Duplex Broadband FDM Frequency 35 Sputnikovaya GUTI Globally Unique Division Multiplex Sistema (Engl.: Temporary UE

FDM A F requency Global Navigation 70 Identity Division Multiple Satellite System) HARQ Hybrid ARQ,

Access gNB Next Generation Hybrid Automatic

FE Front End 40 NodeB Repeat Request FEC Forward Error gNB-CU gNB- HANDO Handover Correction centralized unit, Next 75 HFN HyperFrame

FFS For Further Study Generation NodeB Number FFT Fast Fourier centralized unit HHO Hard Handover

Transformation 45 gNB -DU gNB- HLR Home Location feLAA further enhanced distributed unit, Next Register Licensed Assisted Generation NodeB 80 HN Home Network

Access, further distributed unit HO Handover enhanced LAA GNSS Global Navigation HPLMN Home FN Frame Number 50 Satellite System Public Land Mobile FPGA Field- GPRS General Packet Network Programmable Gate Radio Service 85 HSDPA High Array GSM Global System for Speed Downlink

FR Frequency Range Mobile Packet Access G-RNTI GERAN 55 Communications, HSN Hopping

Radio Network Groupe Special Sequence Number

Temporary Mobile 90 HSPA High Speed

Identity GTP GPRS Tunneling Packet Access

GERAN Protocol HSS Home Subscriber

GSM EDGE 60 GTP-U GPRS Tunnelling Server RAN, GSM EDGE Protocol for User HSUPA High Radio Access Plane 95 Speed Uplink Packet Network GTS Go To Sleep Access

GGSN Gateway GPRS Signal (related to HTTP Hyper Text Support Node 65 WUS) Transfer Protocol

GLONASS GUMMEI Globally HTTPS Hyper

GLObal'naya Unique MME Identifier 100 Text Transfer Protocol

NAvigatsionnaya Secure (https is http/ 1.1 over SSL, 35 IMC IMS Credentials ISDN Integrated i.e. port 443) IMEI International Services Digital

I-Block Mobile Equipment Network

Information Block Identity 70 ISIM IM Services ICCID Integrated Circuit IMGI International Identity Module Card Identification 40 mobile group identity ISO International IAB Integrated Access IMPI IP Multimedia Organisation for and Backhaul Private Identity Standardisation ICIC Inter-Cell IMPU IP Multimedia 75 ISP Internet Service Interference PUblic identity Provider

Coordination 45 IMS IP Multimedia IWF Interworking- ID Identity, identifier Subsystem Function IDFT Inverse Discrete IMSI International I-WLAN Fourier Transform Mobile Subscriber 80 Interworking

IE Information Identity WLAN element 50 IoT Internet of Things Constraint length

IBE In-Band Emission IP Internet Protocol of the convolutional Ipsec IP Security, code, USIM Individual

IEEE Institute of Internet Protocol 85 key Electrical and Electronics Security kB Kilobyte (1000 Engineers 55 IP-CAN IP- bytes) IEI Information Connectivity Access kbps kilo-bits per

Element Identifier Network second

IEIDL Information IP-M IP Multicast 90 Kc Ciphering key Element Identifier IPv4 Internet Protocol Ki Individual

Data Length 60 Version 4 subscriber IETF Internet IPv6 Internet Protocol authentication key

Engineering Task Version 6 KPI Key Performance Force IR Infrared 95 Indicator

IF Infrastructure IS In Sync KQI Key Quality

IM Interference 65 IRP Integration Indicator

Measurement, Reference Point KSI Key Set Identifier

Intermodulation, ksps kilo-symbols per IP Multimedia 100 second KVM Kernel Virtual LTE Long Term MBSFN Machine 35 Evolution Multimedia

LI Layer 1 (physical LWA LTE-WLAN Broadcast multicast layer) aggregation 70 service Single Frequency

Ll-RSRP Layer 1 LWIP LTE/WLAN Network reference signal Radio Level Integration MCC Mobile Country received power 40 with IPsec Tunnel Code L2 Layer 2 (data link LTE Long Term MCG Master Cell Group layer) Evolution 75 MCOT Maximum

L3 Layer 3 (network M2M Machine-to- Channel Occupancy layer) Machine Time

LAA Licensed Assisted 45 MAC Medium Access MCS Modulation and Access Control (protocol coding scheme

LAN Local Area layering context) 80 MDAF Management Data Network MAC Message Analytics Function

LBT Listen Before authentication code MD AS Management Data Talk 50 (security/encryption Analytics Service

LCM LifeCycle context) MDT Minimization of Management MAC-A MAC used 85 Drive Tests LCR Low Chip Rate for authentication and ME Mobile Equipment LCS Location Services key agreement (TSG T MeNB master eNB LCID Logical 55 WG3 context) MER Message Error

Channel ID MAC-IMAC used for Ratio

LI Layer Indicator data integrity of 90 MGL Measurement Gap LLC Logical Link signalling messages (TSG Length Control, Low Layer T WG3 context) MGRP Measurement Gap Compatibility 60 MANO Repetition Period LPLMN Local Management and MIB Master PLMN Orchestration 95 Information Block,

LPP LTE Positioning MBMS Management Protocol Multimedia Information Base LSB Least Significant 65 Broadcast and Multicast MIMO Multiple Input Bit Service Multiple Output MLC Mobile Location 35 MSI Minimum System NC-JT Non- Centre Information, 70 Coherent Joint

MM Mobility MCH Scheduling Transmission Management Information NEC Network MME Mobility MSID Mobile Station Capability Exposure Management Entity 40 Identifier NE-DC NR-E- MN Master Node MSIN Mobile Station 75 UTRA Dual MnS Management Identification Connectivity Service Number NEF Network Exposure

MO Measurement MSISDN Mobile Function Object, Mobile 45 Subscriber ISDN NF Network Function

Originated Number 80 NFP Network MPBCH MTC MT Mobile Forwarding Path

Physical Broadcast Terminated, Mobile NFPD Network CHannel Termination Forwarding Path

MPDCCH MTC 50 MTC Machine-Type Descriptor

Physical Downlink Communications 85 NFV Network

Control CHannel mMTCmassive MTC, Functions MPDSCH MTC massive Machine- Virtualization

Physical Downlink Type Communications NFVI NFV

Shared CHannel 55 MU-MIMO Multi User Infrastructure MPRACH MTC MIMO 90 NFVO NFV Orchestrator

Physical Random MWUS MTC NG Next Generation,

Access CHannel wake-up signal, MTC Next Gen MPUSCH MTC wus NGEN-DC NG-RAN

Physical Uplink Shared 60 NACKNegative E-UTRA-NR Dual Channel Acknowledgement 95 Connectivity

MPLS Multiprotocol NAI Network Access NM Network Manager Label Switching Identifier NMS Network MS Mobile Station NAS Non-Access Management System MSB Most Significant 65 Stratum, Non- Access N-PoP Network Point of Bit Stratum layer 100 Presence

MSC Mobile Switching NCT Network NMIB, N-MIB Centre Connectivity Topology Narrowband MIB NPBCH 35 NS Network Service OSI Other System

Narrowband NSA Non-Standalone 70 Information Physical Broadcast operation mode OSS Operations

CHannel NSD Network Service Support System NPDCCH Descriptor OTA over-the-air

Narrowband 40 NSR Network Service PAPR Peak-to-Average Physical Downlink Record 75 Power Ratio

Control CHannel NSSAINetwork Slice PAR Peak to Average NPDSCH Selection Assistance Ratio

Narrowband Information PBCH Physical Physical Downlink 45 S-NNSAI Single- Broadcast Channel

Shared CHannel NSSAI 80 PC Power Control, NPRACH NSSF Network Slice Personal Computer

Narrowband Selection Function PCC Primary Physical Random NW Network Component Carrier,

Access CHannel 50 NWUS Narrowband Primary CC NPUSCH wake-up signal, 85 PCell Primary Cell

Narrowband Narrowband WUS PCI Physical Cell ID, Physical Uplink NZP Non-Zero Power Physical Cell

Shared CHannel O&M Operation and Identity NPSS Narrowband 55 Maintenance PCEF Policy and Primary ODU2 Optical channel 90 Charging

Synchronization Data Unit - type 2 Enforcement

Signal OFDM Orthogonal Function

NSSS Narrowband Frequency Division PCF Policy Control Secondary 60 Multiplexing Function

Synchronization OFDMA 95 PCRF Policy Control

Signal Orthogonal and Charging Rules

NR New Radio, Frequency Division Function Neighbour Relation Multiple Access PDCP Packet Data NRF NF Repository 65 OOB Out-of-band Convergence Protocol, Function OOS Out of Sync 100 Packet Data

NRS Narrowband OPEX OPerating Convergence Reference Signal EXpense Protocol layer PDCCH Physical 35 PNFR Physical Network PSSCH Physical

Downlink Control Function Record Sidelink Shared Channel POC PTT over Cellular 70 Channel

PDCP Packet Data PP, PTP Point-to- PSCell Primary SCell Convergence Protocol Point PSS Primary PDN Packet Data 40 PPP Point-to-Point Synchronization Network, Public Protocol Signal

Data Network PRACH Physical 75 PSTN Public Switched PDSCH Physical RACH Telephone Network

Downlink Shared PRB Physical resource PT-RS Phase-tracking Channel 45 block reference signal

PDU Protocol Data PRG Physical resource PTT Push-to-Talk Unit block group 80 PUCCH Physical

PEI Permanent ProSe Proximity Uplink Control Equipment Identifiers Services, Proximity- Channel PFD Packet Flow 50 Based Service PUSCH Physical Description PRS Positioning Uplink Shared P-GW PDN Gateway Reference Signal 85 Channel PHICH Physical PRR Packet Reception QAM Quadrature hybrid-ARQ indicator Radio Amplitude channel 55 PS Packet Services Modulation

PHY Physical layer PSBCH Physical QCI QoS class of PLMN Public Land Sidelink Broadcast 90 identifier Mobile Network Channel QCL Quasi co-location

PIN Personal PSDCH Physical QFI QoS Flow ID, Identification Number 60 Sidelink Downlink QoS Flow Identifier PM Performance Channel QoS Quality of Service Measurement PSCCH Physical 95 QPSK Quadrature PMI Precoding Matrix Sidelink Control (Quaternary) Phase Shift Indicator Channel Keying

PNF Physical Network 65 PSFCH Physical QZSS Quasi-Zenith Function Sidelink Feedback Satellite System

PNFD Physical Network Channel 100 RA-RNTI Random Function Descriptor Access RNTI RAB Radio Access RLC Radio Link RRM Radio Resource Bearer, Random Control, Radio Management

Access Burst 35 Link Control layer RS Reference Signal RACH Random Access RLC AM RLC 70 RSRP Reference Signal Channel Acknowledged Mode Received Power

RADIUS Remote RLC UM RLC RSRQ Reference Signal

Authentication Dial In Unacknowledged Mode Received Quality User Service 40 RLF Radio Link RSSI Received Signal RAN Radio Access Failure 75 Strength Indicator Network RLM Radio Link RSU Road Side Unit

RAND RANDom number Monitoring RSTD Reference Signal (used for RLM-RS Reference Time difference authentication) 45 Signal for RLM RTP Real Time RAR Random Access RM Registration 80 Protocol Response Management RTS Ready-To-Send

RAT Radio Access RMC Reference RTT Round Trip Time Technology Measurement Channel Rx Reception, RAU Routing Area 50 RMSI Remaining MSI, Receiving, Receiver Update Remaining Minimum 85 S1AP SI Application

RB Resource block, System Protocol Radio Bearer Information Sl-MME SI for the RBG Resource block RN Relay Node control plane group 55 RNC Radio Network Sl-U SI for the user

REG Resource Element Controller 90 plane Group RNL Radio Network S-GW Serving Gateway

Rel Release Layer S-RNTI SRNC REQ REQuest RNTI Radio Network Radio Network RF Radio Frequency 60 Temporary Identifier Temporary RI Rank Indicator ROHC RObust Header 95 Identity RIV Resource indicator Compression S-TMSI SAE value RRC Radio Resource Temporary Mobile

RL Radio Link Control, Radio Station Identifier 65 Resource Control SA Standalone layer 100 operation mode SAE System 35 SDP Session SiP System in Architecture Evolution Description Protocol 70 Package SAP Service Access SDSF Structured Data SL Sidelink Point Storage Function SLA Service Level

SAPD Service Access SDU Service Data Unit Agreement Point Descriptor 40 SEAF Security Anchor SM Session SAPI Service Access Function 75 Management Point Identifier SeNB secondary eNB SMF Session SCC Secondary SEPP Security Edge Management Function Component Carrier, Protection Proxy SMS Short Message Secondary CC 45 SFI Slot format Service SCell Secondary Cell indication 80 SMSF SMS Function SC-FDMA Single SFTD Space-Frequency SMTC SSB-based Carrier Frequency Time Diversity, SFN Measurement Timing

Division Multiple and frame timing Configuration

Access 50 difference SN Secondary Node,

SCG Secondary Cell SFN System Frame 85 Sequence Number Group Number or SoC System on Chip

SCM Security Context Single Frequency SON Self-Organizing Management Network Network SCS Subcarrier 55 SgNB Secondary gNB SpCell Special Cell Spacing SGSN Serving GPRS 90 SP-CSI-RNTISemi-

SCTP Stream Control Support Node Persistent CSI RNTI Transmission S-GW Serving Gateway SPS Semi-Persistent Protocol SI System Scheduling

SDAP Service Data 60 Information SQN Sequence number Adaptation Protocol, SI-RNTI System 95 SR Scheduling Service Data Adaptation Information RNTI Request Protocol layer SIB System SRB Signalling Radio SDL Supplementary Information Block Bearer Downlink 65 SIM Subscriber SRS Sounding

SDNF Structured Data Identity Module 100 Reference Signal Storage Network SIP Session Initiated SS Synchronization Function Protocol Signal SSB SS Block TA Timing Advance, TPC Transmit Power SSBRI SSB Resource 35 Tracking Area Control Indicator TAC Tracking Area 70 TP MI Transmitted

SSC Session and Code Precoding Matrix Service Continuity TAG Timing Advance Indicator SS-RSRP Group TR Technical Report

Synchronization 40 TAU Tracking Area TRP, TRxP Signal based Reference Update 75 Transmission Signal Received TB Transport Block Reception Point Power TBS Transport Block TRS Tracking SS-RSRQ Size Reference Signal

Synchronization 45 TBD To Be Defined TRx Transceiver Signal based Reference TCI Transmission 80 TS Technical Signal Received Configuration Indicator Specifications, Quality TCP Transmission Technical SS-SINR Communication Standard

Synchronization 50 Protocol TTI Transmission Signal based Signal to TDD Time Division 85 Time Interval Noise and Interference Duplex Tx Transmission, Ratio TDM Time Division Transmitting,

SSS Secondary Multiplexing Transmitter Synchronization 55 TDMATime Division U-RNTI UTRAN Signal Multiple Access 90 Radio Network

SSSG Search Space Set TE Terminal Temporary Group Equipment Identity

SSSIF Search Space Set TEID Tunnel End Point UART Universal Indicator 60 Identifier Asynchronous

SST Slice/Service TFT Traffic Flow 95 Receiver and Types Template Transmitter

SU-MIMO Single TMSI Temporary UCI Uplink Control User MIMO Mobile Subscriber Information SUL Supplementary 65 Identity UE User Equipment Uplink TNL Transport 100 UDM Unified Data Network Layer Management UDP User Datagram USS UE-specific VoIP Voice-over-IP, Protocol 35 search space Voice-over- Internet

UDR Unified Data UTRA UMTS Terrestrial Protocol Repository Radio Access VPLMN Visited

UDSF Unstructured Data UTRAN Universal 70 Public Land Mobile Storage Network Terrestrial Radio Network Function 40 Access Network VPN Virtual Private UICC Universal UwPTS Uplink Network Integrated Circuit Pilot Time Slot VRB Virtual Resource Card V2I Vehicle-to- 75 Block

UL Uplink Infrastruction WiMAX Worldwide

UM Unacknowledged 45 V2P Vehicle-to- Interoperability for

Mode Pedestrian Microwave Access

UML Unified Modelling V2V Vehicle-to- WLANWireless Local Language Vehicle 80 Area Network

UMTS Universal Mobile V2X Vehicle-to- WMAN Wireless Telecommunicatio 50 everything Metropolitan Area ns System VIM Virtualized Network UP User Plane Infrastructure Manager WPANWireless Personal

UPF User Plane VL Virtual Link, 85 Area Network Function VLAN Virtual LAN, X2-C X2-Control plane

URI Uniform Resource 55 Virtual Local Area X2-U X2-User plane Identifier Network XML extensible

URL Uniform Resource VM Virtual Machine Markup Language Locator VNF Virtualized 90 XRES EXpected user

URLLC Ultra- Network Function RESponse Reliable and Low 60 VNFFG VNF XOR exclusive OR Latency Forwarding Graph ZC Zadoff-Chu

USB Universal Serial VNFFGD VNF ZP Zero Power Bus Forwarding Graph

USIM Universal Descriptor Subscriber Identity 65 VNFM VNF Manager Module Terminology

For the purposes of the present document, the following terms and definitions are applicable to the examples and embodiments discussed herein.

The term “circuitry” as used herein refers to, is part of, or includes hardware components such as an electronic circuit, a logic circuit, a processor (shared, dedicated, or group) and/or memory (shared, dedicated, or group), an Application Specific Integrated Circuit (ASIC), a field-programmable device (FPD) (e.g., a field-programmable gate array (FPGA), a programmable logic device (PLD), a complex PLD (CPLD), a high-capacity PLD (HCPLD), a structured ASIC, or a programmable SoC), digital signal processors (DSPs), etc., that are configured to provide the described functionality. In some embodiments, the circuitry may execute one or more software or firmware programs to provide at least some of the described functionality. The term “circuitry” may also refer to a combination of one or more hardware elements (or a combination of circuits used in an electrical or electronic system) with the program code used to carry out the functionality of that program code. In these embodiments, the combination of hardware elements and program code may be referred to as a particular type of circuitry.

The term “processor circuitry” as used herein refers to, is part of, or includes circuitry capable of sequentially and automatically carrying out a sequence of arithmetic or logical operations, or recording, storing, and/or transferring digital data. Processing circuitry may include one or more processing cores to execute instructions and one or more memory structures to store program and data information. The term “processor circuitry” may refer to one or more application processors, one or more baseband processors, a physical central processing unit (CPU), a single-core processor, a dual-core processor, a triple-core processor, a quad-core processor, and/or any other device capable of executing or otherwise operating computer-executable instructions, such as program code, software modules, and/or functional processes. Processing circuitry may include more hardware accelerators, which may be microprocessors, programmable processing devices, or the like. The one or more hardware accelerators may include, for example, computer vision (CV) and/or deep learning (DL) accelerators. The terms “application circuitry” and/or “baseband circuitry” may be considered synonymous to, and may be referred to as, “processor circuitry.”

The term “interface circuitry” as used herein refers to, is part of, or includes circuitry that enables the exchange of information between two or more components or devices. The term “interface circuitry” may refer to one or more hardware interfaces, for example, buses, I/O interfaces, peripheral component interfaces, network interface cards, and/or the like.

The term “user equipment” or “UE” as used herein refers to a device with radio communication capabilities and may describe a remote user of network resources in a communications network. The term “user equipment” or “UE” may be considered synonymous to, and may be referred to as, client, mobile, mobile device, mobile terminal, user terminal, mobile unit, mobile station, mobile user, subscriber, user, remote station, access agent, user agent, receiver, radio equipment, reconfigurable radio equipment, reconfigurable mobile device, etc. Furthermore, the term “user equipment” or “UE” may include any type of wireless/wired device or any computing device including a wireless communications interface.

The term “network element” as used herein refers to physical or virtualized equipment and/or infrastructure used to provide wired or wireless communication network services. The term “network element” may be considered synonymous to and/or referred to as a networked computer, networking hardware, network equipment, network node, router, switch, hub, bridge, radio network controller, RAN device, RAN node, gateway, server, virtualized VNF, NFVI, and/or the like.

The term “computer system” as used herein refers to any type interconnected electronic devices, computer devices, or components thereof. Additionally, the term “computer system” and/or “system” may refer to various components of a computer that are communicatively coupled with one another. Furthermore, the term “computer system” and/or “system” may refer to multiple computer devices and/or multiple computing systems that are communicatively coupled with one another and configured to share computing and/or networking resources.

The term “appliance,” “computer appliance,” or the like, as used herein refers to a computer device or computer system with program code (e.g., software or firmware) that is specifically designed to provide a specific computing resource. A “virtual appliance” is a virtual machine image to be implemented by a hypervisor-equipped device that virtualizes or emulates a computer appliance or otherwise is dedicated to provide a specific computing resource.

The term “resource” as used herein refers to a physical or virtual device, a physical or virtual component within a computing environment, and/or a physical or virtual component within a particular device, such as computer devices, mechanical devices, memory space, processor/CPU time, processor/CPU usage, processor and accelerator loads, hardware time or usage, electrical power, input/output operations, ports or network sockets, channel/link allocation, throughput, memory usage, storage, network, database and applications, workload units, and/or the like. A “hardware resource” may refer to compute, storage, and/or network resources provided by physical hardware element(s). A “virtualized resource” may refer to compute, storage, and/or network resources provided by virtualization infrastructure to an application, device, system, etc. The term “network resource” or “communication resource” may refer to resources that are accessible by computer devices/systems via a communications network. The term “system resources” may refer to any kind of shared entities to provide services, and may include computing and/or network resources. System resources may be considered as a set of coherent functions, network data objects or services, accessible through a server where such system resources reside on a single host or multiple hosts and are clearly identifiable.

The term “channel” as used herein refers to any transmission medium, either tangible or intangible, which is used to communicate data or a data stream. The term “channel” may be synonymous with and/or equivalent to “communications channel,” “data communications channel,” “transmission channel,” “data transmission channel,” “access channel,” “data access channel,” “link,” “data link,” “carrier,” “radiofrequency carrier,” and/or any other like term denoting a pathway or medium through which data is communicated. Additionally, the term “link” as used herein refers to a connection between two devices through a RAT for the purpose of transmitting and receiving information.

The terms “instantiate,” “instantiation,” and the like as used herein refers to the creation of an instance. An “instance” also refers to a concrete occurrence of an object, which may occur, for example, during execution of program code.

The terms “coupled,” “communicatively coupled,” along with derivatives thereof are used herein. The term “coupled” may mean two or more elements are in direct physical or electrical contact with one another, may mean that two or more elements indirectly contact each other but still cooperate or interact with each other, and/or may mean that one or more other elements are coupled or connected between the elements that are said to be coupled with each other. The term “directly coupled” may mean that two or more elements are in direct contact with one another. The term “communicatively coupled” may mean that two or more elements may be in contact with one another by a means of communication including through a wire or other interconnect connection, through a wireless communication channel or link, and/or the like. The term “information element” refers to a structural element containing one or more fields. The term “field” refers to individual contents of an information element, or a data element that contains content.

The term “SMTC” refers to an SSB-based measurement timing configuration configured by SSB-MeasurementTimingConfiguration.

The term “SSB” refers to an SS/PBCH block.

The term “a “Primary Cell” refers to the MCG cell, operating on the primary frequency, in which the UE either performs the initial connection establishment procedure or initiates the connection re-establishment procedure. The term “Primary SCG Cell” refers to the SCG cell in which the UE performs random access when performing the Reconfiguration with Sync procedure for DC operation.

The term “Secondary Cell” refers to a cell providing additional radio resources on top of a Special Cell for a UE configured with CA.

The term “Secondary Cell Group” refers to the subset of serving cells comprising the PSCell and zero or more secondary cells for a UE configured with DC.

The term “Serving Cell” refers to the primary cell for a UE in RRC CONNECTED not configured with CA/DC there is only one serving cell comprising of the primary cell.

The term “serving cell” or “serving cells” refers to the set of cells comprising the Special Cell(s) and all secondary cells for a UE in RRC_CONNECTED configured with CA/. The term “Special Cell” refers to the PCell of the MCG or the PSCell of the SCG for

DC operation; otherwise, the term “Special Cell” refers to the Pcell.

Claims

CLAIMS What is claimed is:

1. One or more non-transitory computer-readable media (NTCRM) having instructions, stored thereon, that when executed by one or more processors cause a user equipment (UE) to: encode a first message for transmission on a first carrier and a second message for transmission on a second carrier in accordance with carrier aggregation; and encode, for transmission to a next generation Node B (gNB), an indication of a timing difference of the transmissions on the first carrier and the second carrier.

2. The one or more NTCRM of claim 1, wherein the first carrier is included in a first timing advance group (TAG) and the second carrier is included in a second timing advance group (TAG), wherein the indication of the timing difference indicates the transmission timing difference between the first TAG and the second TAG.

3. The one or more NTCRM of any one of claims 1-2, wherein the indication of the timing difference is quantized using a granularity of one symbol length or a fraction of a symbol length with respect to a reference subcarrier spacing (SCS).

4. The one or more NTCRM of any one of claims 1-3, wherein the indication of the timing difference is transmitted periodically or based on occurrence of a triggering event.

5. The one or more NTCRM of claim 4, wherein the triggering event is a request received from the gNB.

6. The one or more NTCRM of any one of claims 1-5, wherein the indication of the timing difference is transmitted in a measurement report, a medium access control (MAC) control element (CE), a physical uplink shared channel (PUSCH), or a physical uplink control channel (PUCCH).

7. The one or more NTCRM of any one of claims 1-6, wherein the instructions, when executed, are further to cause the UE to determine whether the first message and the second message are overlapped based on based on whether logical timings of the first and second messages, adjusted by the timing difference, have at least one symbol overlapped.

8. The one or more NTCRM of claim 7, wherein if it is determined that the first and second messages are overlapped, the instructions, when executed are further to cause the UE to multiplex or drop uplink control information associated with at least one of the first and second messages.

9. One or more non-transitory computer-readable media (NTCRM) having instructions, stored thereon, that when executed by one or more processors cause a next generation Node B (gNB) to: receive a first channel from a user equipment (UE) on a first carrier and a second channel from the UE on a second carrier in accordance with carrier aggregation; receive, from the UE, an indication of a transmission timing difference of the transmissions on the first carrier and the second carrier; and process the first and second channels based on the indicated transmission timing difference.

10. The one or more NTCRM of claim 9, wherein the first carrier is included in a first timing advance group (TAG) and the second carrier is included in a second timing advance group (TAG), wherein the indication of the transmission timing difference indicates the transmission timing difference between the first TAG and the second TAG.

11. The one or more NTCRM of any one of claims 9-10, wherein the indication of the transmission timing difference is quantized using a granularity of one symbol length or a fraction of a symbol length with respect to a reference subcarrier spacing (SCS).

12. The one or more NTCRM of any one of claims 9-11, wherein the indication of the transmission timing difference is received from the UE periodically.

13. The one or more NTCRM of any one of claims 9-12, wherein the instructions, when executed, are further to cause the gNB to encode, for transmission to the UE, a request for the transmission timing difference, wherein the indication of the transmission timing advance is received based on the request.

14. The one or more NTCRM of any one of claims 9-13, wherein the indication of the transmission timing difference is received in a measurement report, a medium access control (MAC) control element (CE), a physical uplink shared channel (PUSCH), or a physical uplink control channel (PUCCH).

15. The one or more NTCRM of any one of claims 9-14, wherein the instructions, when executed, are further to cause the gNB to determine whether the first channel and the second channel are overlapped based on based on based on whether logical timings of the first and second messages, adjusted by the transmission timing difference, have at least one symbol overlapped, wherein uplink control information associated with at least one of the first and second channels are multiplexed or dropped based on a determination that the first and second channels are overlapped,.

16. The one or more NTCRM of any one of claims 9-15, wherein the instructions, when executed, are further to cause the gNB to schedule transmission of the first channel by an uplink grant, wherein the uplink grant indicates control channels are multiplexed on the first channel.

17. One or more non-transitory computer-readable media (NTCRM) having instructions, stored thereon, that when executed by one or more processors cause a user equipment (UE) to: receive a downlink control information (DCI) that includes an indication of activation or deactivation of a rate-matching resource for a physical downlink shared channel (PDSCH) transmission; and monitor for a physical downlink control channel (PDCCH) transmission during the PDSCH transmission based on the indication.

18. The one or more NTCRM of claim 17, wherein the instructions, when executed, are further to cause the UE to determine that one or more orthogonal frequency division multiplexing (OFDM) symbols of a synchronization signal block (SSB) transmission are not available for the PDSCH transmission based on an overlap between a PDSCH resource allocation and the SSB transmission.

19. The one or more NTCRM of any one of claims 17-18, wherein the rate matching resource is time-domain configured.

20. The one or more NTCRM of any one of claims 17-19, wherein the rate matching resource is configured per cell or per bandwidth part (BWP).

21. The one or more NTCRM of any one of claims 17-20, wherein the rate matching resource is determined based on a control resource set (CORESET) or a SSB.

22. The one or more NTCRM of claim 21, wherein the instructions, when executed, are further to cause the UE to determine a gap for beam switching based on the CORESET or the SSB.

23. The one or more NTCRM of any one of claims 17-22, wherein the DCI is to indicate that a subset of PDCCH monitoring occasions are activated during the PDSCH transmission.

24. The one or more NTCRM of any one of claims 17-23, wherein the DCI is further to indicate a PDCCH monitoring pattern to be used within the PDSCH transmission.

25. The one or more NTCRM of any one of claims 17-24, wherein the DCI is further to indicate a position of a PDCCH monitoring occasion activated during the PDSCH transmission.