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

Abstract

The present invention relates to one or more non-transitory computer readable media having instructions stored thereon which, when executed by one or more processors, cause a user equipment (UE) to send a first message for transmission on a first carrier according to a carrier aggregation. and one or more ratios that cause encoding a second message for transmission on a second carrier and, for transmission to a next-generation Node B (gNB), an indication of a timing difference between transmissions on the first carrier and the second carrier. It relates to a transitory computer readable medium.

Description

Rate-matching resources for physical downlink shared channel (PDSCH) transmissions and multiplexing of uplink transmissions with different timings

<Cross Reference to Related Applications>

This application claims International Application No. PCT/CN2020/103765, filed Jul. 23, 2020, U.S. Provisional Patent Application No. 63/055,519, filed Jul. 23, 2020, and Sep. 16, 2020. Priority is claimed to US Provisional Patent Application Serial No. 63/079,025, filed at .

<Technical field>

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

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

1 illustrates physical downlink shared channel (PDSCH) rate-matching around a control resource set (CORESET), in accordance with various embodiments.
2 illustrates a long PDSCH transmission duration, according to various embodiments.
3 illustrates a rate-matching resource based on CORESET, in accordance with various embodiments.
4 illustrates a gap around a synchronization signal block (SSB) transmission, in accordance with various embodiments.
5 illustrates an indication of whether a subset of physical downlink control channel (PDCCH) monitoring occasions are activated or deactivated, in accordance with various embodiments.
6 illustrates a PDCCH transmitted in one code block (CB) or code block group (CBG) within a PDSCH transmission duration, according to various embodiments.
7 illustrates the use of a demodulation reference signal (DMRS) to indicate whether a PDCCH monitoring occasion is activated or deactivated, according to various embodiments.
8 illustrates a PDSCH with multiple CBGs when not colliding with rate-matching resources activated, according to various embodiments.
9 illustrates a first option for PDSCH resource allocation when colliding with one or more activated rate-matching resources, according to various embodiments.
10 illustrates PDSCH resource allocation when colliding with one or more deactivated rate-matching resources, according to various embodiments.
11 illustrates a second option for PDSCH resource allocation when colliding with one or more activated rate-matching resources, according to various embodiments.
12 illustrates a third option for PDSCH resource allocation when colliding with one or more activated rate-matching resources, according to various embodiments.
13 illustrates a procedure of overlapping check based on a time difference of two carriers reported by a UE, according to various embodiments.
14 illustrates another procedure for an overlap check based on a time difference of two carriers reported by a UE, according to various embodiments.
15 illustrates a procedure for overlap checking by logical timing and offset, according to various embodiments.
16 illustrates an example of an overlap check by logical timing and offset, in accordance with various embodiments.
17 illustrates an example of an overlap check with logical timing and a granularity of four symbols, in accordance with various embodiments.
18 illustrates a relatively short slot duration with a relatively larger subcarrier spacing, in accordance with various embodiments.
19 illustrates a network according to various embodiments.
20 schematically illustrates a wireless network according to various embodiments.
21 illustrates some exemplary instructions capable of reading instructions from a machine-readable or computer-readable medium (eg, a non-transitory machine-readable storage medium) and performing any one or more of the methodologies discussed herein. It is a block diagram illustrating components, according to embodiments.
22-25 show example procedures for practicing various embodiments discussed herein.

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 specific structure, architectures, interfaces, techniques, etc. to provide a thorough understanding of various aspects of various embodiments. However, it will be apparent to those skilled in the art having the benefit of this disclosure that various aspects of the various embodiments may be practiced in other instances 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 purposes of this 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.

PDSCH for transmissions rate -Matching resources

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

In addition, the rate-matching resource may be configured through a bitmap indicating time and frequency resources having a specific periodicity, or may be configured as a control resource set (CORESET). In the latter case, the scheduled PDSCH is rate-matched around the CORESET as shown in FIG.

Systems operating at carrier frequencies above 52.6 GHz, particularly for Terahertz communications, are expected to require larger subcarrier spacing to avoid significant phase noise. In cases where a larger subcarrier spacing is employed, such as eg 1.92 MHz or 3.84 MHz, the slot duration may be very short. For example, for a 1.92 MHz subcarrier spacing, the duration of one slot is approximately 7.8 μs. This very short slot duration may not be sufficient for higher layer processing including Medium Access Layer (MAC) and Radio Link Control (RLC) and the like. To address this issue, next-generation NodeBs (gNBs) schedule downlink (DL) or uplink (UL) data transmissions across slot boundaries with long transmission durations. can do. In other words, when scheduling data transmission, the concept of slots may not be needed. 2 illustrates an example of a long PDSCH transmission duration.

When the scheduled PDSCH transmission duration is relatively long and the PDCCH monitoring occasion is relatively short, the UE may need to monitor the PDCCH within the PDSCH transmission duration and perform blind decoding of the PDCCHs. In some cases where there is no additional traffic to the UE, PDCCH monitoring within a PDSCH transmission may not be needed to reduce UE power consumption. In addition, corresponding CORESET or configured rate-matching resources may be allocated for PDSCH transmission, which may help improve spectral efficiency. Thus, certain mechanisms may need to be defined to allow a UE to skip PDCCH monitoring occasions or monitor only a subset of PDCCH occasions during a PDSCH transmission.

Among other things, embodiments of the present disclosure relate to Physical Downlink Shared Channel (PDSCH) transmissions using rate-matching resources. In particular, some embodiments may provide signaling details for dynamic activation of a subset of rate-matching resources, as well as PDSCH resource allocation using rate-matching resources.

rate - for dynamic activation of a subset of matching resources signaling details

As mentioned above, systems operating at carrier frequencies above 52.6 GHz, particularly for terahertz communications, are expected to require larger subcarrier spacing to avoid significant phase noise. For example, if a larger subcarrier spacing such as 1.92 MHz or 3.84 MHz is employed, the slot duration may be very short. For example, for a 1.92 MHz subcarrier spacing, the duration of one slot is approximately 7.8 μs. This very short slot duration may not be sufficient for higher layer processing including Medium Access Layer (MAC) and Radio Link Control (RLC), etc. To address this issue, gNBs can schedule DL or UL data transmissions across slot boundaries with long transmission durations.

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

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

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

In another embodiment, when a CORESET is configured as a rate-matching resource, only CORESET resources in the time domain are needed for the rate-matching resource. In particular, the time-domain resource includes controlResourceSetId or ControlResourceSetZero , as well as the time-domain resource of search-space-set zero configured by searchSpaceZero associated with the higher-layer parameters monitoringSlotPeriodicityAndOffset , duration and monitoringSymbolsWithinSlot and CORESET of all searchspace -sets configured by SearchSpace . Determined by the CORESET duration configured by the ControlResourceSet with

In another embodiment, when CORESET is configured as a rate-matching resource, some gaps may be required before and/or after CORESET for beam switching. In this case, the rate-matching resource includes CORESET and gaps before and/or after CORESET.

A gap or K symbols are minimum system information (MSI), remaining minimum system information (RMSI), other system information (OSI) or dedicated radio resource control (radio It may be additionally configured by higher layers through resource control (RRC) signaling. It may also depend on the UE capabilities for beam switching time.

3 illustrates rate-matching resources based on CORESET. As shown, one symbol gap is inserted before and after CORESET as a rate-matching resource.

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

SSB transmission other DL channels or signals including PDCCH, channel state information-reference signal (CSI-RS), phase tracking reference signal (PT-RS), etc. When overlapping with symbols containing , the UE assumes that OFDM symbols containing SSB transmissions are not available for other DL channel transmissions. In particular, the UE may not monitor PDCCH candidates when they overlap with symbols containing SSB transmissions. Similarly, CSI-RS and/or PT-RS are dropped in symbols containing SSB transmissions.

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

4 illustrates an example of a gap configured around an SSB transmission. In the example, a one symbol gap is inserted before and after the symbols containing the 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 is possible that PDSCH and CORESET/PDCCH or SSB and PDSCH can be transmitted in consecutive symbols without any gaps. can In this case, additional beam switching time may not be required.

Optionally, an indication of whether PDSCH can be transmitted in a symbol following CORESET/PDCCH or symbols for SSB transmission with one or more SSB indexes can be configured by higher layers via RRC signaling. When configured, the UE can transmit PDSCH and CORESET/PDCCH or SSB with one or more SSB indexes in consecutive symbols or in the same symbols.

In another option, whether the PDSCH can be transmitted in the symbol following the symbols for CORESET/PDCCH or SSB can be derived by the Transmission Configuration Indicator (TCI) state for the PDSCH. Depending on the TCI state, if PDSCH is Quasi Co-Location (QCL) with CORESET/PDCCH or SSB, the UE can transmit PDSCH and CORESET/PDCCH or SSB in consecutive symbols or in the same symbols. there is.

In another embodiment, when the same Tx beam is applied to transmission of PDCCH and PDSCH, or SSB and PDSCH, it may be possible to multiplex PDSCH and PDCCH or SSB in a TDM manner before a DFT operation. In this case, when the same QCL assumptions apply for PDSCH and PDCCH/CORESET or SSB, and if PDSCH overlaps with PDCCH/CORESET or SSB in the same symbol, PDSCH is a DFT operation involving PDCCH/CORESET or SSB transmission in the same symbol. It can be rate-matched around previous time samples.

Optionally, an indication of whether the PDSCH can be rate-matched around resources allocated for SSB transmission with CORESET/PDCCH or one or more SSB indexes can be configured by higher layers via RRC signaling. When configured, the UE may assume that the PDSCH is rate-matched around samples in time prior to the DFT operation involving PDCCH/CORESET or SSB transmission in the same symbol.

In another option, whether a PDSCH can be rate-matched around resources allocated for CORESET/PDCCH or SSB transmission with one or more SSB indices can be derived by the TCI state for the PDSCH. Depending on the TCI state, if PDSCH is QCL with CORESET/PDCCH or SSB, the UE may assume that PDSCH is rate-matched around samples in time prior to the DFT operation involving PDCCH/CORESET or SSB transmission in the same symbol. .

In another embodiment, one field of the DCI for scheduling the PDSCH may be used to indicate that a subset of PDCCH monitoring occasions are active during the PDSCH transmission duration. Here, the set of PDCCH monitoring occasions refers to all PDCCH monitoring occasions configured by a higher layer parameter SearchSpace overlapping with a scheduled PDSCH. If a subset of PDCCH monitoring occasions is inactive during PDSCH transmission, the UE can skip PDCCH monitoring and does not need to perform PDCCH blind decoding for the subset of PDCCH monitoring occasions.

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

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

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

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

In another embodiment, a subset of PDCCH monitoring occasions that are active during the PDSCH transmission duration are predefined or configured by higher layer signaling. Here, the set of PDCCH monitoring occasions refers to all PDCCH monitoring occasions configured by a higher layer parameter SearchSpace overlapping with a scheduled PDSCH. If a subset of PDCCH monitoring occasions is inactive during PDSCH transmission, the UE can skip PDCCH monitoring and does not need to perform PDCCH blind decoding for the subset of PDCCH monitoring occasions.

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

In another option, a subset of PDCCH monitoring occasions may be predefined in the specification. In one example, all even positions of PDCCH monitoring occasions are active during the PDSCH transmission duration. PDCCH monitoring occasions overlapping with the scheduled PDSCH are numbered sequentially, or PDCCH monitoring occasions are numbered according to reference timing, for example, symbol 0 in SFN 0. In another example, PDCCH monitoring occasion(s) overlapping with the second half of the scheduled PDSCH are activated during the duration of the PDSCH transmission. In another example, only the last N PDCCH monitoring occasion(s) overlapping a scheduled PDSCH are active during the PDSCH transmission duration, where N is equal to or greater than 1. N may be predefined or configured by higher layer signaling.

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

Also, in one option, when the 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 the timer can be configured by higher layers via MSI, RMSI (SIB1), OSI or RRC signaling.

In another option, the UE monitors the PDCCH in the second group of search space sets for the duration of the PDSCH transmission. Also, when the PDSCH scheduled by the PDCCH ends, the UE may switch from the second group of search space sets back to the first group of search space sets. In this case, the lower density of the second group of search spaces may be configured to help the UE reduce PDCCH monitoring within a PDSCH transmission and thus reduce UE power consumption.

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

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

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

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

In one option, the DMRS in the second set of DMRS resources may also be used for channel estimation for PDCCH decoding in an activated PDCCH monitoring occasion. In addition, the PDCCH transmitted in the activated PDCCH monitoring occasion may be k-symbols after the DMRS in the second set of DMRS resources, where k is predefined in the specification or MSI, RMSI (SIB1), OSI or RRC signaling It can be configured by higher layers through.

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

rate -Using matching resources PDSCH resource allocation

In the case of a PDSCH with a long duration, multiple numbers with different transport blocks (TB) or multiple code blocks (CB) or code block groups (CBG). One DCI may be used to schedule PDSCHs. Also, each CB or CBG may be aligned on a symbol boundary, and the same length may be applied for transmission of each CB or CBG. Similarly, for multi-PDSCH scheduling, each PDSCH may span the same number of symbols.

8 illustrates an example of a PDSCH with multiple CBGs when the PDSCH is activated or does not collide with configured rate-matching resources. In the example, PDSCH includes 8 CBGs with contiguous resource allocation. Also, each CBG spans 4 symbols.

When a PDSCH transmission collides with a rate-matching resource during the PDSCH transmission duration, specific mechanisms need to be defined for PDSCH resource allocation or transmission of each PDSCH or transmission of each CB or CBG in case of multi-PDSCH scheduling. there is. The following embodiments apply in the case of one PDSCH transmission including one or more CBs or CBGs, but the embodiments can be simply adopted in the case of multi-PDSCH transmission or PDSCH with slot aggregation. Note that Embodiments of PDSCH resource allocation using rate-matching resources are described in more detail below.

In one embodiment, a PDSCH containing one or more CBs or CBGs is allocated according to a starting symbol and length indicator (SLIV) indicated in the DCI for scheduling the PDSCH. This may be denoted as nominal resource allocation. In particular, the first CB/CBG or the first PDSCH is allocated according to the start symbol and duration. Subsequent CBGs and PDSCHs are assigned with the same duration as the first CB/CBG or PDSCH and in consecutive symbols after the first CB/CBG or PDSCH.

Also, when a PDSCH transmission containing one or more CB/CBG collides with an activated rate-matching resource, e.g., a CORESET or activated PDCCH monitoring occasion or SSB block, the CB/CBG or PDSCH is the activated rate-matching resource. Not sent from matching resources. In addition, the affected CB/CBG or PDSCH is rate-matched or punctured around activated rate-matching resources. Note that this may be denoted as an actual resource allocation.

Note that the transport block size (TBS) is determined according to the duration or nominal resource allocation of the first CB/CBG or PDSCH. The determined TBS applies to other CB/CBGs or PDSCHs regardless of whether they collide with active rate-matching resources.

Alternatively, the TBS on CB/CBGs or PDSCHs affected when colliding with activated rate-matching resources is dependent on the actual number of symbols or resources other than the activated rate-matching resources or actual resource allocation. can be determined

9 illustrates one option of PDSCH resource allocation when colliding with an activated rate-matching resource. For this option, 5 symbols are allocated to each CBG, and CBG#3 collides with an activated rate-matching resource spanning 2 symbols. In this case, CBG#3 is rate-matched around the activated rate-matching resource with the TBS determined according to the nominal assignment.

Also, when a PDSCH transmission containing one or more CB/CBG collides with a deactivated rate-matching resource, the CB/CBG or PDSCH continues to be mapped to the deactivated rate-matching resources.

10 illustrates one option of PDSCH resource allocation when colliding with deactivated rate-matching resources. For this option, 5 symbols are allocated to each CBG, and CBG#3 collides with an inactive rate-matching resource spanning 2 symbols. In this case, CBG#3 and subsequent CBGs are allocated to consecutive symbols without considering deactivated rate-matching resources.

In another embodiment, when a PDSCH transmission containing one or more CB/CBG collides with an active rate-matching resource, e.g., a CORESET or inactive PDCCH monitoring occasion or SSB block, the CB/CBG or PDSCH is active. It is not transmitted on an assigned rate-matching resource. Additionally, the affected CB/CBG or PDSCH continues to be transmitted after the activated rate-matching resource, spanning the indicated number of symbols in the DCI. In this option, the actual resource allocation of CB/CBG or PDSCH is the same as the nominal resource allocation indicated in DCI.

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

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

In the second step, in the case of a configured rate-matching resource that is not activated, a CB/CBG or PDSCH prior to the deactivated rate-matching resource is mapped to the deactivated rate-matching resource.

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

different uplink Multiple with transmit timings in carriers uplink Multiplexing of Transmissions

For systems operating at carrier frequencies above 52.6 GHz, to account for increased phase noise, the subcarrier spacing (SCS) may be relatively large, for example 1.92 MHz or 3.84 MHz. In this case, the symbol length may be very short. For example, for a 1.92 MHz subcarrier spacing, the symbol length is about 0.56 us. As shown in FIG. 18, a slot with 14 symbols is approximately 7.8 μs.

In carrier aggregation (CA), component carriers can belong to different timing advance groups (TAGs). When carriers have the same TAG, they are exactly synchronized. On the other hand, when carriers have different TAGs, there may be a time difference between downlink (DL) reception and uplink (UL) transmission at the UE side. The exact value of the time difference is affected by synchronization errors and propagation delays. In the case of the UL time difference between the two carriers, it is also affected by the TA values of the two carriers. Because of the very short symbol length at frequencies above 52.6 GHz, the time difference may be on the scale of one or more symbols. For this problem, the impact this may have on the multiplexing of UL signals/channels is an issue that needs to be addressed.

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

In a CA system, two UL carriers can belong to different TAGs, so even if the reception timing at the gNB is precisely aligned to the two UL carriers, the two carriers can have different UL transmission timings. The difference in UL transmission timings depends on a number of factors. The UL transmission timing of the UL carrier is determined by the DL reception timing and TA value of the associated DL carrier. The DL transmission timings of the two associated DL carriers may not be ideally aligned. The propagation delay between the gNB and the UE may be different for the two DL carriers. For example, the base stations (BSs) of the two DL carriers may be in different locations, so the distances between the two BSs and the UE may be different. Even when the two BSs are co-located, the propagation delay may be different because of the different frequencies of the two DL carriers. Specifically, the two DL carriers may belong to different frequency ranges (FR) with very different propagation characteristics. As a result, the DL reception timings for the two DL carriers may be different at the UE. Also, DL reception timings at the UE are not accurately known by the gNB. A timing advance (TA) value is obtained by initial access and may be adjusted by TA commands. Also, gNBs and UEs may not have exactly the same information about TA values. Therefore, the gNB may not know the exact difference between the UL transmission timings of the two UL carriers of a particular UE.

For systems operating at carrier frequencies above 52.6 GHz, the subcarrier spacing (SCS) can be quite large, resulting in very short symbol lengths. For example, in case of SCS 1.92MHz, it is about 0.56us. Meanwhile, a time difference between two UL carriers may be several microseconds or more. When carrier aggregation of a carrier of FR1 and another carrier with a frequency of more than 52.6 GHz is considered, the time difference between the two UL carriers can be much larger. From the above analysis, the time difference of two UL carriers may correspond to several or tens of symbols. As a result, two UL channels overlapping on the UE side can be separated on the gNB side, or two UL channels separated on the UE side can overlap on the gNB side. Also, if the gNB does not know the exact difference of the UL transmission timings, the gNB cannot know whether the two UL transmissions in the two UL carriers overlap at the UE side.

Based on the NR system design operating in CA, the UE can multiplex multiple UL information on one carrier when multiple channels carrying multiple information overlap. Meanwhile, when multiple channels do not overlap, the UE may separately transmit multiple UL channels. Determination of whether multiple channels overlap may be based on logical timing. Logical timing is defined as the transmit timing for a number of channels assuming that the following are all zeros: (1) DL-to-DL timing differences between CCs; (2) UL-to-UL timing differences across different TAGs; (3) UL TA. Thus, the logical timing of multiple channels corresponds to the case where the frame timing is aligned. However, due to timing differences of multiple symbols at the UE, the two channels may be separated by multiple symbols when viewed as overlapping with logical timing. On the other hand, the two channels may overlap in multiple symbols when considered as non-overlapping with logical timing.

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

The reported timing difference may be an absolute time value. Alternatively, the reported timing difference may be quantized using a granularity of one symbol length or a fraction of the symbol length relative to the reference SCS. The reference SCS may be configured by higher layer signaling. Alternatively, the reference SCS may be the highest SCS of the active UL BWPs of the two UL carriers. Alternatively, the reference SCS may be the highest SCS of active UL BWPs of UL carriers in the two TAGs. Alternatively, the reference SCS may be the highest SCS of active UL BWPs of all UL carriers. Alternatively, the reference SCS may be the maximum value of the lowest subcarrier spacing configuration among subcarrier spacings given by higher-layer parameters SCS — SpecificCarrierList configured for two UL carriers. Alternatively, the reference SCS may be the maximum value of the lowest subcarrier spacing configuration among the subcarrier spacings given by the configured higher-layer parameters SCS — SpecificCarrierList for UL carriers in the two TAGs. Alternatively, the reference SCS may be the maximum value of the lowest subcarrier spacing configuration among the subcarrier spacings given by the configured higher-layer parameters SCS -SpecificCarrierList for all UL carriers. SCS - SpecificCarrierList is a higher-layer parameter that defines the SCS for a carrier in NR.

, 예를 들어, c=0.5에 의해 심볼들의 수(a number of symbols)로 양자화될 수 있으며, 여기서, T는 심볼의 길이이다. 이 스킴(scheme)에 의해, 2개의 UL 채널이 중첩으로서 간주되는 경우, 2개의 UL 채널은 실제로는 적어도 절반의 심볼만큼 중첩된다. 2개의 UL 채널이 비-중첩으로서 간주되는 경우, 2개의 UL 채널은 최대 절반의 심볼만큼 중첩될 수 있다.In one option, denote the actual time difference as t, where t is

, eg, can be quantized to a number of symbols by c=0.5, where T is the length of a symbol. By this scheme, if two UL channels are regarded as overlapping, the two UL channels actually overlap by at least half a symbol. If two UL channels are considered non-overlapping, the two UL channels can overlap by at most half symbols.

The UE may periodically report the timing difference to the gNB. Alternatively, the UE may report timing differences under certain conditions. For example, if the UE identifies that the timing difference changes by a value greater than a threshold, the UE reports the new timing difference to the gNB. The above threshold can be a fraction, one or multiple symbol durations. Alternatively, the gNB may transmit a trigger for reporting on demand. When the trigger is received, the UE reports the delta between the current timing difference or the updated timing difference and the previous timing difference to the gNB.

A report of the timing difference may be included in a measurement report of higher layer signaling. Alternatively, the reporting of the timing difference may be carried in a Medium Access Control-Control Element (MAC CE) on the Physical Uplink Shared Channel (PUSCH). Alternatively, reporting of timing differences may be performed at the physical layer. For example, a periodic or semi-persistent scheduling (SPS) based Physical Uplink Control Channel (PUCCH) or PUSCH resource may be configured to allow UEs to report timing differences periodically. Alternatively, the downlink control channel (DCI) may be used to trigger an aperiodic report of timing difference in PUSCH.

In one embodiment, whether two UL channels overlap is determined by the logical timing of the two UL carriers. If the two UL channels are regarded as overlapping by logical timing at the UE side, the UL information associated with the two UL channels is, for example, Rel- Multiplexed or dropped according to current specifications defined in 15 and Rel-16 NR. On the other hand, if two UL channels are regarded as non-overlapping by logical timing, however, the two UL channels may overlap in time. Since this case can be regarded as an error case, it is up to the gNB to prevent such an error case. Alternatively, the UE may drop the UL channel with lower priority completely or only in overlapping symbols. For example, the priority order may be based on the priority of uplink control information (UCI) types. UCI priority can be defined as HARQ-ACK > SR > CSI part 1 > CSI part 2. Alternatively, it is up to the UE how to handle the two overlapping UL channels.

In one embodiment, the UE reports the actual transmission timing difference d between the two TAGs or the two UL carriers to the gNB, and based on the actual transmission timings of the two UL carriers, the two UL channels on the two UL carriers You can decide whether they overlap or not. Meanwhile, the gNB may determine whether the two UL channels on the two UL carriers are overlapping based on the logical timings of the two UL channels and the reported timing difference d. If the two UL channels have at least one overlapping symbol, after applying the timing difference d to the logical timings, the UL information associated with the two UL channels is, for example, in Rel-15 and Rel-16 NR Multiplexed or dropped according to the current specifications defined. Otherwise, the two UL channels are transmitted separately. With this scheme, the gNB and UE can have a common understanding of whether to multiplex or drop one or more of the multiple UL channels/how to multiplex or drop them.

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

In one embodiment, the UE reports the actual transmission timing difference d between the two TAGs or the two UL carriers to the gNB, and based on the logical timings of the two UL channels and the reported timing difference d, on the two UL carriers It can be determined whether the two UL channels are overlapping. Meanwhile, the gNB may also determine whether the two UL channels on the two UL carriers overlap based on the logical timings of the two UL channels and the reported timing difference d. If the two UL channels have at least one overlapping symbol, after applying the timing difference d to the logical timings, the UL information associated with the two UL channels is, for example, in Rel-15 and Rel-16 NR Multiplexed or dropped according to the current specifications defined. Otherwise, the two UL channels are transmitted separately. With this scheme, the gNB and UE can have a common understanding of whether to multiplex or drop one or more of the multiple UL channels/how to multiplex or drop them.

14 illustrates another procedure of overlapping check based on the time difference between two carriers reported by the UE.

이고, 슬롯 s'의 새로운 심볼 인덱스는

이다. 새로운 인덱스 s' 및 l'가 중첩 체크에 사용된다. 2개의 UL 채널이, 논리적 타이밍들에 오프셋을 적용한 후에, 적어도 하나의 중첩된 심볼을 갖는 경우, 2개의 UL 채널과 연관된 UL 정보는, 예를 들어, Rel-15 및 Rel-16 NR에 정의된 현재 사양에 따라 멀티플렉싱되거나 드롭된다. 그렇지 않으면, 2개의 UL 채널은 별도로 송신된다. 이 스킴에 의하면, gNB 및 UE는 다수의 UL 채널들 중 하나 이상을 멀티플렉싱할지 또는 드롭할지/이를 멀티플렉싱 또는 드롭하는 방법에 대해 공통된 이해를 갖는다.In one embodiment, the logical timings of the two UL channels, adjusted by offset, are used to determine whether the two UL channels overlap. The offset reflects the time difference between two TAGs or two UL carriers. For example, in a symbol with logical timing of symbol index l in slot s, after applying offset d, the new slot index is

, and the new symbol index of slot s' is

am. The new indices s' and l' are used for overlap checking. If the two UL channels have at least one overlapping symbol, after applying an offset to the logical timings, the UL information associated with the two UL channels is, for example, defined in Rel-15 and Rel-16 NR Multiplexed or dropped depending on the current specification. Otherwise, the two UL channels are transmitted separately. With this scheme, the gNB and UE have a common understanding of whether to multiplex or drop/how to multiplex or drop one or more of the multiple UL channels.

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

4 illustrates an example of an overlap check by logical timing and offset. Since the two carriers have the same SCS, they are assumed to have the same symbol length. The transmission timing of carrier 1 is ahead of carrier 2 by 3 symbols. Thus, the gNB can configure a left offset of 3 symbols for carrier 1. On the other hand, carrier 2 is a criterion for defining an offset, for example, the offset for carrier 2 is 0. From Figure 16, the symbol indices for UL channel 1 are 8 to 12 (411). The shifted indices of UL channel 1 are 5-9 after applying an offset of value -3 (412). Whether UL channel 1 overlaps with UL channel on carrier 2 is done by checking the symbol indices of UL channel 412 and the UL channel on carrier 2.

UL channel 2 421 is considered as overlapping with UL channel 1 since it has common symbol indices 6, 7, 8 and 9. In fact, some symbol indices of UL channel 411 before applying offset -3 are also the same as UL channel 2.

The symbol indices of UL channel 411 before applying offset -3 are different from UL channel 3, but have common symbol indices 5 and 6, so UL channel 3 422 is considered as overlapping with UL channel 1 .

The symbol indexes of the UL channel 411 before applying the offset -3 have common symbol indexes 11 and 12 with the UL channel 4, but do not have common symbol indexes, so the UL channel 4 423 has no common symbol indexes with the UL channel 1 -Considered as nested.

UL channel 5 424 is still considered non-overlapping with UL channel 1 because it does not have common symbol indices after applying the offset.

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

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

In one embodiment, whether multiple UL channels are overlapping is checked by the logical timing of the two UL carriers with greater granularity. Granularity can be defined as the length of X symbols with the reference SCS, where X≥1. The reference SCS may be configured by higher layer signaling. Alternatively, the reference SCS may be the highest SCS of the active UL BWPs of the two UL carriers. Alternatively, the reference SCS may be the highest SCS of active UL BWPs of UL carriers in the two TAGs. Alternatively, the reference SCS may be the highest SCS of active UL BWPs of all UL carriers. Alternatively, the reference SCS may be the maximum value of the lowest subcarrier spacing configuration among subcarrier spacings given by higher-layer parameters SCS-SpecificCarrierList configured for two UL carriers. Alternatively, the reference SCS may be the maximum value of the lowest subcarrier spacing configuration among the subcarrier spacings given by the configured higher-layer parameters SCS — SpecificCarrierList for UL carriers in the two TAGs. Alternatively, the reference SCS may be the maximum value of the lowest subcarrier spacing configuration among the subcarrier spacings given by the configured higher-layer parameters SCS — SpecificCarrierList for all UL carriers.

17 shows an example of an overlap check with logical timing and a granularity of 4 symbols. Since the two carriers have the same subcarrier spacing (SCS), they are assumed to have the same symbol length. The transmission timing of carrier 1 is ahead of carrier 2 by 3 symbols. That is, UL channel 1 (511) on carrier 1 actually overlaps with UL channel 2 (521) on carrier 2, after accounting for the 3-symbol left offset. By defining a granularity of four symbols, the logical timing is divided into units 501, 502, 503 and 504. UL channel 1 512 is mapped to units 502 and 503. UL channel 2 is mapped to units 501 and 502. UL channel 1 and UL channel 2 are considered overlapping because they both map to unit 502 .

In one embodiment, for a PUSCH scheduled by a UL grant, the UL grant indicates which UL control channel(s) may be multiplexed to the PUSCH/which UL control channel(s) may be multiplexed to the PUSCH. Since there may be confusion about whether PUCCH overlaps with PUSCH, the indicator in the UL grant helps the UE know if UCI multiplexed to PUSCH needs to be performed to have aligned operation as a gNB. If there are multiple non-overlapping PUCCHs, the indicator of the UL grant may further distinguish one or multiple PUCCHs that need to be multiplexed to the PUSCH. Whether the two PUCCH or PUSCH channels overlap is determined by the actual transmission timing of the two UL carriers at the UE side, or by the logical timing of the two UL carriers, or by the offset of the time difference between the two UL carriers. It can be determined by logical timing.

Systems and Implementations

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

19 illustrates a network 1900 according to various embodiments. Network 1900 may operate in a manner consistent with 3GPP technical specifications for LTE or 5G/NR systems. However, the exemplary embodiments are not limited in this respect, and the described embodiments may be applied to other networks that benefit from the principles described herein, such as future 3GPP systems.

Network 1900 may include UE 1902, which may include any mobile or non-mobile computing device designed to communicate with RAN 1904 via an over-the-air connection. can UE 1902 can be communicatively coupled with RAN 1904 by a Uu interface. The UE 1902 is 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, dashboard mobile equipment, mobile data terminal, electronic engine management system, electronic/engine control unit, electronic/engine control module, embedded system , sensors, microcontrollers, control modules, engine management systems, networked appliances, machine-type communication devices, M2M or D2D devices, IoT devices, etc., but are not limited thereto.

In some embodiments, network 1900 may include a plurality of UEs that are directly coupled to each other via a sidelink interface. 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, UE 1902 may additionally communicate with AP 1906 via an over-the-air connection. AP 1906 may manage a WLAN connection, which may serve to offload some/all network traffic from RAN 1904. The connection between UE 1902 and AP 1906 may conform to any IEEE 802.11 protocol, where AP 1906 may be a wireless fidelity (Wi-Fi®) router. In some embodiments, UE 1902 , RAN 1904 , and AP 1906 may utilize cellular-WLAN aggregation (eg, LWA/LWIP). Cellular-WLAN aggregation may involve UE 1902 configured by RAN 1904 to utilize both cellular radio resources and WLAN resources.

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

In embodiments where RAN 1904 includes multiple ANs, they couple to each other via an X2 interface (if RAN 1904 is an LTE RAN) or an Xn interface (if RAN 1904 is a 5G RAN). can be ringed X2/Xn interfaces, which in some embodiments can be separated into control/user plane interfaces, allow ANs to communicate information related to handovers, data/context transfers, mobility, load management, interference coordination, etc. can be allowed

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

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

In V2X scenarios, UE 1902 or AN 1908 may be or act as an RSU, which may refer to any transport infrastructure entity used for V2X communications. The RSU may be implemented in or by a suitable AN or stationary (or relatively stationary) UE. An RSU implemented in or by a UE may be referred to as a "UE-type RSU", an RSU implemented in or by an eNB may be referred to as an "eNB-type RSU", and an RSU implemented in or by a gNB An implemented RSU may be referred to as a "gNB-type RSU", and so forth. In one example, an RSU is a computing device coupled with roadside located radio frequency circuitry that provides connectivity support for 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 for sensing and controlling on-going vehicular and pedestrian traffic. The RSU can provide very low latency communications required for high-speed events such as collision avoidance, traffic alerts, and the like. Additionally or alternatively, the RSU may provide other cellular/WLAN communication services. The components of the RSU may be packaged in a weatherproof enclosure suitable for outdoor installation and may include a traffic signaling controller or network interface controller to provide wired connectivity (eg Ethernet) to a backhaul network.

In some embodiments, RAN 1904 can be an LTE RAN 1910 with eNBs, eg, eNB 1912. LTE RAN 1910 may provide an LTE air interface with the following characteristics: SCS at 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 includes CSI-RS for CSI acquisition and beam management; PDSCH/PDCCH DMRS for PDSCH/PDCCH demodulation; and cell search and initial acquisition for coherent demodulation/detection at the UE, channel quality measurements, and CRS for channel estimation. The LTE air interface may operate in sub-6 GHz bands.

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

In some embodiments, the NG interface is two parts: an NG user plane (NG-U) interface that carries traffic data between nodes of the NG-RAN 1914 and the UPF 1948 ( For example, the N3 interface), and the NG control plane (NG-C) interface, which is the signaling interface between the nodes of the NG-RAN 1914 and the AMF 1944 (eg, the N2 interface) can be split into

NG-RAN 1914 may provide a 5G-NR air interface with the following characteristics: flexible SCS; CP-OFDM for DL, CP-OFDM for UL and DFT-s-OFDM; 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. 5G-NR air interface may not use CRS, PBCH DMRS for PBCH demodulation; PTRS for phase tracking for PDSCH; and a tracking reference signal for time tracking. The 5G-NR air interface can operate in FR1 bands including bands below 6 GHz or FR2 bands including bands from 24.25 GHz to 52.6 GHz. The 5G-NR air interface may include SSB, which is an area of a downlink resource grid including 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 SCS. For example, UE 1902 may be configured with multiple BWPs where each BWP configuration has a different SCS. When the UE 1902 is indicated to change the BWP, the SCS of the transmission is also changed. Another example use case for BWP is related to power saving. In particular, multiple BWPs can be configured for UE 1902 with different amounts of frequency resources (eg, PRBs) to support data transmission under different traffic loading scenarios. A BWP with fewer PRBs can be used for data transmission with less traffic load while allowing power savings in the UE 1902 and in some cases the gNB 1916 . A BWP with a larger number of PRBs can be used in scenarios with higher traffic load.

The RAN 1904 is communicatively coupled to a CN 1920 that includes network elements for providing various functions supporting data and communication services to customers/subscribers (e.g., users of UE 1902). ring Components of CN 1920 may be implemented on 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 CN 1920 into physical computing/storage resources such as servers, switches, etc. . A logical instantiation of CN 1920 may be referred to as a network slice, and a logical instantiation of a portion of CN 1920 may be referred to as a network sub-slice.

In some embodiments, CN 1920 may be LTE CN 1922, which may also be referred to as EPC. LTE CN 1922 includes MME 1924, SGW 1926, SGSN 1928, HSS 1930, PGW 1932, and PCRF 1934. The functions of the elements of the LTE CN 1922 can be briefly introduced as follows.

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

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

SGSN 1928 may track the location of UE 1902 and perform security functions and access control. SGSN 1928 also provides inter-EPC node signaling for mobility between different RAT networks; PDN and S-GW selection specified by MME 1924; MME selection for handovers, etc. may be performed. 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.

HSS 1930 may include a database for network users, including subscription-related information to support the handling of communication sessions of network entities. The HSS 1930 may provide support for routing/roaming, authentication, authorization, naming/addressing resolution, location dependencies, and the like. there is. An S6a reference point between HSS 1930 and MME 1924 may enable transmission of subscription and authentication data to authenticate/authorize user access to LTE CN 1920 .

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

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

In some embodiments, CN 1920 may be 5GC 1940. 5GC 1940 includes AUSF 1942, AMF 1944, SMF 1946, UPF 1948, NSSF 1950, which are coupled to each other via interfaces (or "reference points") as shown. NEF 1952 , NRF 1954 , PCF 1956 , UDM 1958 , and AF 1960 . The functions of the elements of 5GC 1940 can be briefly introduced as follows.

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

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

SMF 1946 includes SM (eg, session establishment, tunnel management between UPF 1948 and AN 1908); UE IP address allocation and management (including discretionary authorization); selection and control of UP functions; Configure traffic steering in UPF 1948 to route traffic to proper destination; termination of interfaces to policy control functions; partial control of policy enforcement, charging, and QoS; Legitimate intercept (for interface to SM events and LI system); End of SM parts of NAS messages; downlink data notification; Initiation of AN specific SM information transmitted via AMF 1944 to AN 1908 via N2; and determining the SSC mode of the session. SM can refer to the management of PDU sessions, and a PDU session or “session” can refer to a PDU concatenation service that provides or enables the exchange of PDUs between UE 1902 and data network 1936 .

UPF 1948 is an anchor point for intra-RAT and inter-RAT mobility, an external PDU session point of interconnect to data network 1936, and a branch to support multi-homed PDU sessions. It can act as a branching point. UPF 1948 also performs packet routing and forwarding, performs packet inspection, enforces the user plane portion of policy rules, intercepts packets (UP collections) legitimately, performs traffic usage reporting, and Perform QoS handling for the plane (e.g. packet filtering, gating, UL/DL rate enforcement), perform uplink traffic verification (e.g. SDF-to-QoS flow mapping), It is also possible to perform transport level packet marking in link and downlink, downlink packet buffering and downlink data notification triggering. UPF 1948 may include an uplink classifier to assist in routing traffic flows to the data network.

NSSF 1950 may select a set of network slice instances serving UE 1902 . NSSF 1950 may also determine the mapping for allowed NSSAIs and subscribed S-NSSAIs, if necessary. NSSF 1950 may also determine a list of candidate AMFs based on the set of AMFs used to serve UE 1902, or a suitable configuration, and possibly querying NRF 1954. Selection of a set of network slice instances for UE 1902 may be triggered by AMF 1944, whereby UE 1902 interacts with and registers with NSSF 1950, which may lead to changes in AMF. there is. NSSF 1950 can interact with AMF 1944 via the N22 reference point and communicate with other NSSFs in the visited network via the N31 reference point (not shown). Additionally, NSSF 1950 may represent a Nnssf service-based interface.

NEF (1952) is a third party, internal exposure/re-exposure, AFs (e.g., AF (1960)), edge computing or fog computing system. systems) and the like to securely expose services and capabilities provided by 3GPP network functions. In these embodiments, NEF 1952 may authenticate, authorize, or throttle AFs. NEF 1952 may also translate information exchanged with AF 1960 and information exchanged with internal network functions. For example, NEF 1952 can translate between AF-Service-Identifier and internal 5GC information. NEF 1952 may also receive information from other NFs based on their exposed capabilities. This information may be stored in the NEF 1952 as structured data or stored in the 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, NEF 1952 may represent a Nnef service-based interface.

The NRF 1954 may support service discovery functions, receive NF discovery requests from NF instances, and provide information on discovered NF instances to 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 can refer to the creation of an instance, and “instance” means, for example, of program code. It can refer to specific occurrences of objects that may occur during execution. Additionally, NRF 1954 may represent a Nnrf service-based interface.

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

UDM 1958 may handle subscription-related information to support handling of communication sessions of network entities and may store subscription data of UE 1902 . For example, subscription data may be communicated over N8 reference points between UDM 1958 and AMF 1944. UDM 1958 may include two parts: an application front end and a UDR. UDR includes subscription data and policy data for UDM 1958 and PCF 1956, and/or structured data for exposure and application data for NEF 1952 (PFDs for application detection, multiple UEs ( 1902) may be stored. The Nudr service-based interface accesses the specific set of data stored by UDM 1958, PCF 1956, and NEF 1952 by UDR 221, as well as reading, updating notifications of related data changes in the UDR. (e.g. add, edit), delete, and subscribe. The UDM may include a UDM-FE responsible for credential processing, location management, subscription management, and the like. 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 NFs via reference points as shown, UDM 1958 may represent a Nudm service-based interface.

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

In some embodiments, 5GC 1940 may enable edge computing by selecting operator/third party services to be geographically close to the point at which UE 1902 attaches to the network. This can reduce the load and latency of the network. To provide edge-computing implementations, 5GC 1940 selects UPF 1948 close to UE 1902 and provides traffic steering from UPF 1948 to data network 1936 via N6 interface. can run This may be based on UE subscription data, UE location, and information provided by AF 1960 . In this way, AF 1960 can influence UPF (re)selection and traffic routing. Based on the operator deployment, when AF 1960 is considered a trusted entity, the network operator may authorize AF 1960 to directly interact with the associated NFs. Additionally, AF 1960 may represent a Naf service-based interface.

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 .

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

UE 2002 can be communicatively coupled with AN 2004 via connection 2006 . Connection 2006 is illustrated as an air interface enabling communication coupling, and may conform to cellular communication protocols such as mmWave or LTE protocol or 5G NR protocol operating at frequencies below 6 GHz.

UE 2002 can include a host platform 2008 coupled with a modem platform 2010 . The host platform 2008 can include application processing circuitry 2012 that can be coupled with the protocol processing circuitry 2014 of the modem platform 2010 . Application processing circuitry 2012 can run various applications on UE 2002 that source/sink application data. Application processing circuitry 2012 may further implement one or more layer operations to send/receive application data to/from a data network. These layer operations may include transport (eg UDP) and Internet (eg IP) operations.

Protocol processing circuitry 2014 may implement one or more of the layer operations to facilitate sending or receiving data over connection 2006 . Layer operations implemented by protocol processing circuitry 2014 may include, for example, MAC, RLC, PDCP, RRC and NAS operations.

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

Modem platform 2010 includes an RF front end (RFFE) that may include or connect to transmit circuitry 2018, receive circuitry 2020, RF circuitry 2022, and one or more antenna panels 2026. (2024) may be further included. Briefly, transmit circuitry 2018 may include digital-to-analog converters, mixers, intermediate frequency (IF) components, and the like, and receive circuitry 2020 may include analog-to-digital converters, mixers, and IF components. etc., the RF circuitry 2022 can include low-noise amplifiers, power amplifiers, power tracking components, etc., and the RFFE 2024 can include filters (e.g., surface/bulk acoustic wave ( surface/bulk acoustic wave filters), switches, antenna tuners, beamforming components (eg, phased-array antenna components), and the like. selection of components (generally referred to as “transmit/receive components”) of transmit circuitry 2018, receive circuitry 2020, RF circuitry 2022, RFFE 2024, and antenna panels 2026; and The arrangement may be specific to particular implementation details, such as whether the communication is TDM or FDM, for example at mmWave or sub-6 gHz frequencies. In some embodiments, the transmit/receive components may be arranged in multiple parallel transmit/receive chains and may be disposed in the same or different chips/modules, etc.

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

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

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

Similar to UE 2002 , AN 2004 may include a host platform 2028 coupled with a modem platform 2030 . Host platform 2028 can include application processing circuitry 2032 coupled with protocol processing circuitry 2034 of 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. Components of AN 2004 may be similar to and substantially interchangeable with like-named components of UE 2002 . In addition to performing data transmission/reception as described above, the components of AN 2008 may also perform RNC functions such as radio bearer management, uplink and downlink dynamic radio resource management, and data packet scheduling, for example. It can perform various logical functions, including

21 illustrates some exemplary instructions capable of reading instructions from a machine-readable or computer-readable medium (eg, a non-transitory machine-readable storage medium) and performing any one or more of the methodologies discussed herein. A block diagram illustrating components, according to embodiments. Specifically, FIG. 21 shows a schematic 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. and each of these may be communicatively coupled via bus 2140 or other interface circuitry. For embodiments in which node virtualization (eg, NFV) is utilized, hypervisor 2102 may be implemented to provide an execution environment for one or more network slices/sub-slices to utilize hardware resources 2100. there is.

Processors 2110 may include, for example, processor 2112 and processor 2114 . The processors 2110 may include, 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, It may be an ASIC, FPGA, radio-frequency integrated circuit (RFIC), other processor (including those discussed herein), or any suitable combination thereof.

Memory/storage devices 2120 may include main memory, disk storage, or any suitable combination thereof. The memory/storage devices 2120 may include dynamic random access memory (DRAM), static random access memory (SRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), and flash memory. memory), solid-state storage, and the like, any type of volatile, non-volatile, or semi-volatile memory, but is not limited thereto.

Communications resources 2130 may be interconnection or network interface controllers, components, or other components for communicating with one or more peripheral devices 2104 or with one or more databases 2106 or other network elements over network 2108. Suitable devices may be included. For example, communication resources 2130 may include wired communication components (eg, 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 be software, programs, applications, applets, apps, or programs for causing at least any of processors 2110 to perform any one or more of the methodologies discussed herein. May contain other executable code. Instructions 2150 may be fully or partially within at least one of processors 2110 (e.g., within the processor's cache memory), memory/storage devices 2120, or any suitable combination thereof. can reside as Also, any portion of instructions 2150 may be sent to hardware resources 2100 from any combination of peripheral devices 2104 or databases 2106 . Accordingly, memory of processors 2110, memory/storage devices 2120, peripheral devices 2104, and databases 2106 are examples of computer-readable and machine-readable media.

Exemplary Procedures

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

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

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

DCI may include various types of information. For example, in some embodiments, the DCI includes an indication of activation of a configured rate-matching resource at the bandwidth part (BWP) level. In some embodiments, the DCI is further to indicate that a subset of physical downlink control channel (PDCCH) monitoring occasions are active during a PDSCH transmission. In some embodiments, the DCI is further to indicate the PDCCH monitoring pattern used within the PDSCH transmission. In some embodiments, the DCI is further to indicate the position of an active PDCCH monitoring occasion during PDSCH transmission. In some embodiments, the DCI is further to indicate a subset of PDCCH monitoring occasions that are active during a 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.

24 illustrates another process 2400 according to various embodiments. Process 2400 can include encoding a first channel for transmission on a first carrier and a second channel for transmission on a second carrier according to carrier aggregation, at step 2402 .

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

In some embodiments, process 2400 may be performed by a UE or part thereof. An indication of the timing difference may be used by the UE and/or gNB to determine if the first and second channels overlap. If it is determined that the first and second channels overlap, 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 do not overlap, uplink control information associated with the first and second channels may be transmitted separately.

25 illustrates another process according to various embodiments. At step 2502 , the process may include receiving a first channel from the UE on a first carrier and a second channel from the UE on a second carrier according to the carrier aggregation.

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

At step 2506, process 2500 may further include processing the first and second channels based on the indicated transmit timing difference. In some embodiments, processing includes identifying and/or processing uplink control information (eg, HARQ feedback or other information) associated with the first and/or second channels based on the indicated transmission timing difference. steps may be included.

In some embodiments, process 2500 may be performed by a gNB or part thereof. An indication of the timing difference may be used by the UE and/or gNB to determine if the first and second channels overlap. If it is determined that the first and second channels overlap, 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 do not overlap, 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 presented 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 Examples section below. For example, the baseband circuitry described above in connection with one or more of the previous figures may be configured to operate according to one or more of the examples presented below. For another example, circuitry associated with a UE, base station, network element, etc., as described above with respect to one or more of the previous figures, may be configured to operate according to one or more of the examples set forth below in the Examples section.

examples

Example 1 is a wireless communication method for a 5th generation (5G) or new radio (NR) system,

configuring, by a Next Generation NodeB (gNB), rate-matching resources for a Physical Downlink Shared Channel (PDSCH) in time domain; and

Activating, by the gNB, a subset of configured rate-matching resources via downlink control information (DCI)

It may include a method including.

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

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

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

Example 5 may include the method of Example 1 or some other example herein, wherein when CORESET is configured as a rate-matching resource, some gaps before and/or after CORESET may include Minimum System Information (MSI), It can be configured through residual 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 of the DCI for scheduling the PDSCH indicates that a subset of PDCCH monitoring occasions are active during the PDSCH transmission duration. can be used to

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

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

Example 9 may include the method of Example 1 or some other example herein, wherein the subset of PDCCH monitoring occasions that are activated during the PDSCH transmission duration are predefined or configured by higher layer signaling.

Example 10 may include the method of Example 1 or some other example herein, wherein more than one group of search space sets may be configured for PDCCH monitoring; When two groups of search space sets are configured for PDCCH monitoring, when the PDCCH of the first group of search space sets is detected, the UE moves from the first group of search space sets to the second group of search space sets. will switch

Example 11 may include the method of example 1 or some other example herein, wherein when the UE receives the PDCCH in the first group of search space sets, the UE will start or restart a timer; When the timer expires, the UE will 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 examples herein, wherein, within a PDSCH transmission, one or more code blocks (CBs) or code block groups (CBGs) or PDSCHs may be assigned to a PDCCH carrying a DCI. can be replaced by

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

Example 14 may include the method of example 1 or some other examples herein, wherein a PDSCH transmission comprising one or more CB/CBG is activated rate-matching resource, eg, CORESET or activated PDCCH monitoring. When colliding with an occasion or SSB block, CB/CBG or PDSCH is not transmitted on an activated rate-matching resource.

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

Example 16 may include the method of example 14 or some other example herein, wherein TBS on CB/CBGs or PDSCHs affected when colliding with activated rate-matching resources is activated rate-matching resources. It may be determined according to the actual number of symbols or resources excluding matching resources or actual resource allocation.

Example 17 may include the method of Example 1 or some other examples herein, wherein a PDSCH transmission comprising one or more CB/CBG is activated rate-matching resource, eg, CORESET or deactivated PDCCH monitoring. When colliding with an occasion or SSB block, CB/CBG or PDSCH is not transmitted on an activated rate-matching resource; The affected CB/CBG or PDSCH continues to be transmitted after the activated rate-matching resource, spanning the indicated number of symbols in the DCI.

Example 18 may include the method of Example 1 or some other examples herein, wherein the PDSCH allocation is first configured within a start and length indicator value (SLIV) indicated in the DCI and a PDSCH transmission duration of a rate-matching resource. based on; When one CB/CBG or PDSCH collides with the configured rate-matching resource, the CB/CBG or PDSCH continues to be mapped after the configured rate-matching resource, spanning the indicated number of symbols via SLIV.

Example 19 may include the method of example 1 or some other examples herein, wherein if the PDSCH resource allocation overlaps symbols comprising a synchronization signal block (SSB) transmission, the UE may include the SSB transmission. It will be assumed that OFDM symbols are not available for PDSCH transmission.

Example 20 may include the method of Example 1 or some other examples herein, where other parameters including a PDCCH, a channel state information-reference signal (CSI-RS), a phase tracking reference signal (PT-RS), etc. When DL channels or signals overlap symbols containing SSB transmissions, the UE assumes that OFDM symbols containing SSB transmissions are not available for other DL channel transmissions.

Example 21 may include the method of example 1 or some other example herein, wherein the PDSCH may be transmitted in a symbol following the CORESET/PDCCH or symbols for SSB transmission with one or more SSB indices. Indication can be configured by higher layers via RRC signaling.

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

Example 23 is a method,

determining downlink control information (DCI) including an indication of activation or deactivation of a rate-matching resource for physical downlink shared channel (PDSCH) transmission; and

Encoding a message comprising a DCI for transmission to a user equipment (UE).

Including a method that includes.

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 the cell level.

Example 26 includes the method of example 25 or some other example herein, wherein the DCI includes an indication of activation of the configured rate-matching resource at a bandwidth part (BWP) level.

Example 27 includes the method of example 23 or some other examples herein, wherein the rate-matching resource is based on a control resource set (CORESET) or synchronization signal block (SSB).

Example 28 includes the method of Example 27 or some other example herein, wherein the 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 the gap for beam switching is determined based on CORESET or SSB.

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

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

Example 32 includes the method of Example 23 or some other examples herein, wherein the DCI is further to indicate a position of a PDCCH monitoring occasion activated during a 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 a 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 a portion thereof.

Example 36 is a method comprising:

receiving a downlink control information (DCI) message that includes an indication of activation or deactivation of a rate-matching resource for physical downlink shared channel (PDSCH) transmission; and

Monitoring for a physical downlink control channel (PDCCH) transmission during PDSCH transmission based on the DCI message.

Including a method that includes.

Example 37 includes the method of example 36 or some other examples herein, wherein the one or more Orthogonal Frequency Division Multiplexing (OFDM) symbols of a synchronization signal block (SSB) transmission is configured to transmit the PDSCH resource allocation based on an overlap between the SSB transmission. Further comprising determining that it is not available for transmission.

Example 38 includes the method of Example 36 or some other examples herein, wherein the one or more Orthogonal Frequency Division Multiplexing (OFDM) symbols of the synchronization signal block (SSB) transmission are subject to overlap between the downlink (DL) signal and the SSB transmission. and determining that it is not available for DL transmission based on the

Example 39 includes the method of example 38 or some other examples herein, wherein the DL signal comprises a 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 a portion thereof.

Example 41 may include a wireless communication method for multiplexing 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 the UE reports an actual transmission timing difference d between two TAGs or two carriers to the gNB.

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

Example 44 may include the method of example 42 or some other example herein, wherein the timing difference is periodically reported 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 the UE determines whether two UL channels on the two UL carriers overlap based on actual transmission timings of the two UL carriers. Decide. The gNB determines whether the two UL channels on the two UL carriers are overlapping based on the logical timing 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 the UE and the gNB transmit two ULs on two UL carriers based on the logical timing of the two UL channels and the reported timing difference d. Determines whether channels overlap.

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

Example 49 may include the method of example 48 or some other example herein, wherein the two UL channels, after applying the offset to the logical timings, have at least one overlapping symbol, the two UL channels UL information associated with a channel is 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, wherein whether two UL channels overlap 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 for deriving UL transmission timings is used for multiple TAGs.

Example 52 may include the method of example 41 or some other example herein, wherein whether multiple UL channels overlap is checked by logical timing of two UL carriers and a greater granularity.

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

Example 54 is a method comprising:

encoding a first channel for transmission on a first carrier and a second channel for transmission on a second carrier according to carrier aggregation; and

encoding, for transmission, an indication of a timing difference of transmissions on the first carrier and the second carrier;

It may include a method including.

Example 55 may include the method of example 54 or some other examples 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). Included, 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 examples 54 or 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 examples 54-56 or some other examples herein, wherein the indication of the timing difference is a granule of one symbol length or a fraction of a symbol length relative to a reference subcarrier spacing (SCS). It is quantized using rarity.

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

Example 59 may include the method of examples 54-58 or some other examples herein, further comprising determining the triggering event, where 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, where the triggering event is a request received from the gNB.

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

Example 62 may include the method of examples 54-61 or some other examples herein, determining whether the first channel and the second channel overlap based on respective transmission timings of the first channel and the second channel. It further includes the step of determining.

Example 63 may include the method of example 62 or some other example herein, wherein the determination of whether the first channel and the second channel overlap depends on the respective logical timings of the first channel and the second channel. based on additional

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

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

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

Example 67 may include the method of examples 62-66 or some other examples herein, wherein when it is determined that the first and second channels do not overlap, an uplink associated with the first and second channels. Control information is transmitted separately.

Example 68 may include the method of examples 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 examples 54-68 or some other examples herein, wherein the first channel is scheduled by an uplink grant, and the uplink grant determines that the control channel(s) is the first channel. multiplexed to and/or which control channel(s) are multiplexed to the first channel.

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

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

Example 72 is a method comprising:

receiving a first channel from a UE in a first carrier and a second channel from a UE in a second carrier according to carrier aggregation; and

Receiving, from the UE, an indication of a transmission timing difference of transmissions on the first carrier and the second carrier.

It may include a method including.

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 examples 72 or 72a or some other examples 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), and 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 examples 72 or 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 examples 72 through 74 or some other examples herein, wherein the indication of the transmission timing difference is one symbol length relative to a reference subcarrier spacing (SCS) or a fraction of a symbol length. It is quantized using granularity.

Example 76 may include the method of examples 72-75 or some other examples herein, wherein the indication of the transmission timing difference is received periodically from the UE.

Example 77 may include the method of examples 72-76 or some other examples herein, wherein the indication of the transmission timing difference is received based on the triggering event.

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

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

Example 80 may include the method of examples 72-79 or some other examples herein, further comprising determining whether the first channel and the second channel overlap 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 of whether the first channel and the second channel overlap depends on the respective logical timings of the first channel and the second channel. based on additional

Example 82 may include the method of examples 72-81 or some other examples herein, based on whether the logical timings of the first and second channels, adjusted by the offset, have at least one overlapping symbol. Further comprising determining if the first channel and the second channel overlap.

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

Example 84 may include the method of examples 80-83 or some other examples herein, wherein the uplink control information associated with the first and second channels based on the determination that the first and second channels overlap is and determining whether multiplexed or dropped.

Example 85 may include the method of examples 80-84 or some other examples herein, wherein the uplink control information associated with the first and second channels based on the determination that the first and second channels do not overlap. and determining that is transmitted separately.

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

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

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

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

Example 90 may include an apparatus that includes means for performing 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 is one or more non-transitory computer readable media containing instructions that cause an electronic device, upon execution of the instructions by one or more processors of the electronic device, to be described in or equivalent to any of Examples 1-89. It may include one or more non-transitory computer readable media that cause the performance of one or more elements of a related method or any other method or process described herein.

Example 92 includes 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. It may include a device that

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

Example 94 is an apparatus comprising one or more computer readable media comprising one or more processors and instructions that, when executed by the one or more processors, cause the one or more processors to: , or an apparatus that causes the performance of a method, technique, or process described in or related to parts thereof.

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

Example 96 is a datagram, packet, frame, segment, protocol data unit (a It may include a protocol data unit (PDU), or a message.

Example 97 may include a signal encoded with data described in or related to any of Examples 1-89, or portions or portions thereof, or otherwise described in this disclosure.

Example 98 is a datagram, packet, frame, segment, protocol data unit (a PDU), or a signal encoded into a message.

Example 99 is an electromagnetic signal carrying computer readable instructions, wherein execution of the computer readable instructions by the one or more processors causes the one or more processors to: An electromagnetic signal that causes a method, technique, or process related thereto to be performed.

Example 100 is a computer program comprising instructions wherein execution of the program by a processing element causes the processing element to use a method, technique, or technique described in or related to any of Examples 1-89, or portions thereof. It may include a computer program that causes the process to be performed.

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

Example 102 may include a method of communication 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.

Unless explicitly stated otherwise, any of the examples described above may be combined with any other example (or combination of examples). The foregoing description of one or more implementations provides illustration and description, but is not intended to be exhaustive or limiting the scope of the 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 coincide with terms, definitions, and abbreviations defined in 3GPP TR 21.905 v16.0.0 (2019-06). For purposes of this document, the following abbreviations may apply to the examples and embodiments discussed herein.

3GPP Third Generation Partnership Project

4G Fourth Generation

5G Fifth Generation

5GC 5G Core network

ACK Acknowledgment

AF Application Function

AM Acknowledged Mode

AMBR Aggregate Maximum Bit Rate

AMF Access and Mobility Management Function

AN Access Network

ANR Automatic Neighbor Relation

AP Application Protocol, Antenna Port, Access Point

API Application Programming Interface

APNs Access Point Name

ARP Allocation and Retention Priority

ARQ Automatic Repeat Request

AS Access Stratum

ASN.1 Abstract Syntax Notation One

AUSF Authentication Server Function

AWGN Additive White Gaussian Noise

BAP Backhaul Adaptation Protocol

BCH Broadcast Channel

BER Bit Error Ratio

BFD Beam Failure Detection

BLER Block Error Rate

BPSK Binary Phase Shift Keying

BRAS Broadband Remote Access Server

BSS Business Support System

BS Base Station

BSR Buffer Status Report

BW Bandwidth

BWP Bandwidth Part

C-RNTI Cell Radio Network Temporary Identity

CA Carrier Aggregation, Certification Authority

CAPEX CAPital EXpenditure

CBRA Contention Based Random Access

CC Component Carrier, Country Code, Cryptographic Checksum

CCA Clear Channel Assessment

CCE Control Channel Element

CCCH Common Control Channel

CE Coverage Enhancement

CDM Content Delivery Network

CDMA Code-Division Multiple Access

CFRA Contention Free Random Access

CG Cell Group

CI Cell Identity

CID Cell-ID (eg, positioning method)

CIM Common Information Model

CIR Carrier to Interference Ratio

C.K. Cipher Key

CM Connection Management, Conditional Mandatory

CMAS Commercial Mobile Alert Service

CMD Command

CMS Cloud Management System

CO Conditional Optional

CoMP Coordinated Multi-Point

CORESET Control Resource Set

COTS Commercial Off-The-Shelf

CP Control Plane, Cyclic Prefix, Connection Point

CPD Connection Point Descriptor

CPE Customer Premise Equipment

CPICH Common Pilot Channel

CQI Channel Quality Indicator

CPU CSI processing unit, Central Processing Unit

C/R Command/Response field bit

CRAN Cloud Radio Access Network, Cloud RAN

CRB Common Resource Block

CRC Cyclic Redundancy Check

CRI Channel-State Information Resource Indicator, CSI-RS Resource Indicator

C-RNTI Cell RNTI

CS Circuit Switched

CSAR Cloud Service Archive

CSI Channel-State Information

CSI-IM CSI Interference Measurement

CSI-RS CSI Reference Signal

CSI-RSRP CSI reference signal received power

CSI-RSRQ CSI reference signal received quality

CSI-SINR CSI signal-to-noise and interference ratio

CSMA Carrier Sense Multiple Access

CSMA/CA CSMA with collision avoidance

CSS Common Search Space, Cell-specific Search Space

CTS Clear-to-Send

CW Codeword

CWS Contention Window Size

D2D Device-to-Device

DC Dual Connectivity, Direct Current

DCI Downlink Control Information

DF Deployment Flavor

DL Downlink

DMTF Distributed Management Task Force

DPDK Data Plane Development Kit

DM-RS, DMRS Demodulation Reference Signal

DN Data network

DRB Data Radio Bearer

DRS Discovery Reference Signal

DRX Discontinuous Reception

DSL Domain Specific Language. Digital Subscriber Line

DSLAM DSL Access Multiplexer

DwPTS Downlink Pilot Time Slot

E-LAN Ethernet Local Area Network

E2E End-to-End

ECCA Extended clear channel assessment (extended CCA)

ECCE Enhanced Control Channel Element, Enhanced CCE

ED Energy Detection

EDGE Enhanced Datarates for GSM Evolution

EGMF Exposure Governance Management Function

EGPRS Enhanced GPRS

EIR Equipment Identity Register

eLAA Enhanced Licensed Assisted Access, enhanced LAA

EM Element Manager

eMBB Enhanced Mobile Broadband

EMS Element Management System

eNB Evolved NodeB, E-UTRAN Node B

EN-DC E-UTRA-NR Dual Connectivity

EPC Evolved Packet Core

EPDCCH Enhanced PDCCH, Enhanced Physical Downlink Control Channel

EPRE Energy per resource element

EPS Evolved Packet System

EREG Enhanced REG, enhanced resource element groups

ETSI European Telecommunications Standards Institute

ETWS Earthquake and Tsunami Warning System

eUICC Embedded UICC (embedded UICC), embedded universal integrated circuit card (embedded universal integrated circuit card)

E-UTRA Evolved UTRA

E-UTRAN Evolved UTRAN (Evolved UTRAN)

EV2X Enhanced V2X

F1AP F1 Application Protocol

F1-C F1 Control plane interface

F1-U F1 User plane interface

FACCH Fast Associated Control CHannel

FACCH/F Fast Associated Control Channel/Full rate

FACCH/H Fast Associated Control Channel/Half rate

FACH Forward Access Channel

FAUSCH Fast Uplink Signaling Channel

FB Functional Block

FBI Feedback Information

FCC Federal Communications Commission

FCCH Frequency Correction CHannel

FDD Frequency Division Duplex

FDM Frequency Division Multiplex

FDMA Frequency Division Multiple Access

FE Front End

FEC Forward Error Correction

FFS For Further Study

FFT Fast Fourier Transformation

feLAA further enhanced licensed access Assisted Access), further enhanced LAA

FN Frame Number

FPGA Field-Programmable Gate Array

FR Frequency Range

G-RNTI GERAN Radio Network Temporary Identity

GERAN GSM EDGE RAN, GSM EDGE Radio Access Network

GGSN Gateway GPRS Support Node

GLONASS GLOBal'naya NAvigatsionnaya Sputnikovaya Sistema (English: Global Navigation Satellite System)

gNB Next Generation NodeB

gNB-CU gNB-centralized unit, Next Generation NodeB centralized unit

gNB-DU gNB-distributed unit, Next Generation NodeB distributed unit

GNSS Global Navigation Satellite System

GPRS General Packet Radio Service

cial Mobile)Global System for Mobile Communications (GSM)

cial Mobile)

GTP GPRS Tunneling Protocol

GTP-U GPRS Tunneling Protocol for User Plane

GTS Go To Sleep Signal (WUS Related)

GUMMEI Globally Unique MME Identifier

GUTI Globally Unique Temporary UE Identity

HARQ Hybrid ARQ, Hybrid Automatic Repeat Request

HANDO Handover

HFN HyperFrame Number

HHO Hard Handover

HLR Home Location Register

HN Home Network

HO Handover

HPLMN Home Public Land Mobile Network

HSDPA High Speed Downlink Packet Access

HSN Hopping Sequence Number

HSPA High Speed Packet Access

HSS Home Subscriber Server

HSUPA High Speed Uplink Packet Access

HTTP Hyper Text Transfer Protocol

HTTPS Hyper Text Transfer Protocol Secure (https is SSL i.e. http/1.1 over port 443)

I-Block Information Block

ICCID Integrated Circuit Card Identification

IAB Integrated Access and Backhaul

ICIC Inter-Cell Interference Coordination

ID Identity, identifier

IDFT Inverse Discrete Fourier Transform

IE Information element

IBE In-Band Emission

IEEE Institute of Electrical and Electronics Engineers

IEI Information Element Identifier

IEIDL Information Element Identifier Data Length

IETF Internet Engineering Task Force

IF Infrastructure

IM Interference Measurement, Intermodulation, IP Multimedia

IMC IMS Credentials

IMEI International Mobile Equipment Identity

IMGI International mobile group identity

IMPI IP Multimedia Private Identity

IMPU IP Multimedia Public identity

IMS IP Multimedia Subsystem

IMSI International Mobile Subscriber Identity

IoT Internet of Things

IP Internet Protocol

Ipsec IP Security, Internet Protocol Security

IP-CAN IP-Connectivity Access Network

IP-M IP Multicast

IPv4 Internet Protocol Version 4

IPv6 Internet Protocol Version 6

IR Infrared

IS In Sync

IRP Integration Reference Point

ISDN Integrated Services Digital Network

ISIM IM Services Identity Module

ISO International Organization for Standardization

ISP Internet Service Provider

IWF Interworking-Function

I-WLAN Interworking WLAN

Constraint length of the convolutional code, USIM Individual key

kB Kilobyte (1000 bytes)

kbps kilo-bits per second

Kc Ciphering key

Ki Individual subscriber authentication key

KPIs Key Performance Indicator

KQI Key Quality Indicator

KSI Key Set Identifier

ksps kilo-symbols per second

KVM Kernel Virtual Machine

L1 Layer 1 (physical layer)

L1-RSRP Layer 1 reference signal received power

L2 Layer 2 (data link layer)

L3 Layer 3 (network layer)

LAA Licensed Assisted Access

LAN Local Area Network

LBT Listen Before Talk

LCM Lifecycle Management

LCR Low Chip Rate

LCS Location Services

LCID Logical Channel ID

LI Layer Indicator

LLC Logical Link Control, Low Layer Compatibility

LPLMN Local PLMN (Local PLMN)

LPP LTE Positioning Protocol

LSB Least Significant Bit

LTE Long Term Evolution

LWA LTE-WLAN aggregation

LWIP LTE/WLAN Radio Level Integration with IPsec Tunnel

LTE Long Term Evolution

M2M Machine-to-Machine

MAC Medium Access Control (protocol layering context)

MAC Message authentication code (security/encryption context)

MAC-A MAC used for authentication and key agreement (TSG T WG3 context)

MAC-I MAC used for data integrity of signaling messages (TSG T WG3 context)

MANO Management and Orchestration

MBMS Multimedia Broadcast and Multicast Service

MBSFN Multimedia Broadcast multicast service Single Frequency Network

MCC Mobile Country Code

MCG Master Cell Group

MCOT Maximum Channel Occupancy Time

MCS Modulation and coding scheme

MDAF Management Data Analytics Function

MDAS Management Data Analytics Service

MDT Minimization of Drive Tests

ME Mobile Equipment

MeNB Master eNB

MER Message Error Ratio

MGL Measurement Gap Length

MGRP Measurement Gap Repetition Period

MIB Master Information Block, Management Information Base

MIMO Multiple Input Multiple Output

MLC Mobile Location Center

MM Mobility Management

MME Mobility Management Entity

MN Master Node

MnS Management Service

MO Measurement Object, Mobile Originated

MPBCH MTC Physical Broadcast CHannel

MPDCCH MTC Physical Downlink Control CHannel

MPDSCH MTC Physical Downlink Shared CHannel

MPRACH MTC Physical Random Access CHannel

MPUSCH MTC Physical Uplink Shared Channel

MPLS MultiProtocol Label Switching

MS Mobile Station

MSB Most Significant Bit

MSc Mobile Switching Center

MSI Minimum System Information, MCH Scheduling Information

MSID Mobile Station Identifier

MSIN Mobile Station Identification Number

MSISDN Mobile Subscriber ISDN Number

MT Mobile Terminated (Mobile Termination)

MTC Machine-Type Communications

mMTC Massive MTC, Massive Machine-Type Communications

MU-MIMO Multi User MIMO

MWUS MTC wake-up signal, MTC WUS

NACK Negative Acknowledgement

NAI Network Access Identifier

NAS Non-Access Stratum, Non-Access Stratum layer

NCT Network Connectivity Topology

NC-JT Non-Coherent Joint Transmission

NEC Network Capability Exposure

NE-DC NR-E-UTRA Dual Connectivity

NEF Network Exposure Function

NF Network Function

NFP Network Forwarding Path

NFPD Network Forwarding Path Descriptor

NFV Network Functions Virtualization

NFVI NFV Infrastructure

NFVO NFV Orchestrator

NG Next Generation (Next Gen)

NGEN-DC NG-RAN E-UTRA-NR Dual Connectivity

NM Network Manager

NMS Network Management System

N-PoP Network Point of Presence

NMIB, N-MIB Narrowband MIB

NPBCH Narrowband Physical Broadcast CHannel

NPDCCH Narrowband Physical Downlink Control CHannel

NPDSCH Narrowband Physical Downlink Shared CHannel

NPRACH Narrowband Physical Random Access CHannel

NPUSCH Narrowband Physical Uplink Shared CHannel

NPSS Narrowband Primary Synchronization Signal

NSSS Narrowband Secondary Synchronization Signal

NR New Radio, Neighbor Relation

NRF NF Repository Function

NRS Narrowband Reference Signal

NS Network Service

NSA Non-Standalone operation mode

NSD Network Service Descriptor

NSR Network Service Record

NSSAI Network Slice Selection Assistance Information

S-NNSAI Single-NSSAI

NSSF Network Slice Selection Function

NW Network

NWUS Narrowband wake-up signal, Narrowband WUS

NZP Non-Zero Power

O&M Operation and Maintenance

ODU2 Optical channel Data Unit - type 2

OFDM Orthogonal Frequency Division Multiplexing

OFDMA Orthogonal Frequency Division Multiple Access

OOB Out-of-band

OOS Out of Sync

OPEX Operating Expense

OSI Other System Information

OSS Operations Support System

OTA Over-the-air

PAPR Peak-to-Average Power Ratio

PAR Peak to Average Ratio

PBCH Physical Broadcast Channel

PC Power Control, Personal Computer

PCC Primary Component Carrier, Primary CC

PCell Primary Cell

PCI Physical Cell ID, Physical Cell Identity

PCEF Policy and Charging Enforcement Function

PCF Policy Control Function

PCRF Policy Control and Charging Rules Function

PDCP Packet Data Convergence Protocol, Packet Data Convergence Protocol layer

PDCCH Physical Downlink Control Channel

PDCP Packet Data Convergence Protocol

PDN Packet Data Network, Public Data Network

PDSCH Physical Downlink Shared Channel

PDUs Protocol Data Unit

PEI Permanent Equipment Identifiers

PFD Packet Flow Description

P-GW PDN Gateway

PHICH Physical hybrid-ARQ indicator channel

PHY Physical layer

PLMN Public Land Mobile Network

PIN Personal Identification Number

PM Performance Measurement

PMI Precoding Matrix Indicator

PNF Physical Network Function

PNFD Physical Network Function Descriptor

PNFR Physical Network Function Record

POC PTT over Cellular

PP, PTP Point-to-Point

PPP Point-to-Point Protocol

PRACH Physical RACH

PRB Physical resource block

PRG Physical resource block group

ProSe Proximity Services, Proximity-Based Service

PRS Positioning Reference Signal

PRR Packet Reception Radio

PS Packet Services

PSBCH Physical Sidelink Broadcast Channel

PSDCH Physical Sidelink Downlink Channel

PSCCH Physical Sidelink Control Channel

PSFCH Physical Sidelink Feedback Channel

PSSCH Physical Sidelink Shared Channel

PSCell Primary SCell

PSS Primary Synchronization Signal

PSTN Public Switched Telephone Network

PT-RS Phase-tracking reference signal

PTT Push-to-Talk

PUCCH Physical Uplink Control Channel

PUSCH Physical Uplink Shared Channel

QAM Quadrature Amplitude Modulation

QCI QoS class of identifier

QCL Quasi co-location

QFI QoS Flow ID, QoS Flow Identifier

QoS Quality of Service

QPSK Quadrature (Quaternary) Phase Shift Keying

QZSS Quasi-Zenith Satellite System

RA-RNTI Random Access RNTI (Random Access RNTI)

RAB Radio Access Bearer, Random Access Burst

RACH Random Access Channel

RADIUS Radius (Remote Authentication Dial In User Service)

RAN Radio Access Network

RAND RANDom number (used for authentication)

RAR Random Access Response

RAT Radio Access Technology

RAU Routing Area Update

RB Resource block, Radio Bearer

RBG Resource block group

REG Resource Element Group

Rel Release

REQ REQuest

RF Radio Frequency

RI Rank Indicator

RIV Resource indicator value

RL Radio Link

RLC Radio Link Control, Radio Link Control layer

RLC AM RLC Acknowledged Mode

RLC UM RLC Unacknowledged Mode

RLF Radio Link Failure

RLM Radio Link Monitoring

RLM-RS Reference Signal for RLM

RM Registration Management

RMC Reference Measurement Channel

RMSI Remaining MSI (Remaining MSI), Remaining Minimum System Information

RN Relay Node

RNC Radio Network Controller

RNL Radio Network Layer

RNTI Radio Network Temporary Identifier

ROHC RObust Header Compression

RRC Radio Resource Control, Radio Resource Control layer

RRM Radio Resource Management

RS Reference Signal

RSRP Reference Signal Received Power

RSRQ Reference Signal Received Quality

RSSI Received Signal Strength Indicator

RSU Road Side Unit

RSTD Reference Signal Time Difference

RTP Real Time Protocol

RTS Ready-To-Send

RTT Round Trip Time

Rx Reception, Receiving, Receiver

S1AP S1 Application Protocol

S1-MME S1 for the control plane

S1-U S1 for the user plane

S-GW Serving Gateway

S-RNTI SRNC Radio Network Temporary Identity

S-TMSI SAE Temporary Mobile Station Identifier

SA Standalone operation mode

SAE System Architecture Evolution

SAP Service Access Point

SAPD Service Access Point Descriptor

SAPI Service Access Point Identifier

SCC Secondary Component Carrier, Secondary CC

SCell Secondary Cell

SC-FDMA Single Carrier Frequency Division Multiple Access

SCG Secondary Cell Group

SCM Security Context Management

SCS Subcarrier Spacing

SCTP Stream Control Transmission Protocol

SDAP Service Data Adaptation Protocol, Service Data Adaptation Protocol layer

SDL Supplementary Downlink

SDNF Structured Data Storage Network Function

SDP Session Description Protocol

SDSF Structured Data Storage Function

SDU Service Data Unit

SEAF Security Anchor Function

SeNB Secondary eNB

SEPP Security Edge Protection Proxy

SFI Slot format indication

SFTD Space-frequency time diversity, SFN and frame timing difference

SFN System Frame Number or Single Frequency Network

SgNB Secondary gNB

SGSN Serving GPRS Support Node

S-GW Serving Gateway

SI System Information

SI-RNTI System Information RNTI (System Information RNTI)

SIB System Information Block

SIM Subscriber Identity Module

SIP Session Initiated Protocol

SiP System in Package

SL Sidelink

SLA Service Level Agreement

SM Session Management

SMF Session Management Function

SMS Short Message Service

SMSF SMS Function

SMTC SSB-based Measurement Timing Configuration

SN Secondary Node, Sequence Number

SoC System on Chip

SON Self-Organizing Network

SpCell Special Cell

SP-CSI-RNTI Semi-Persistent CSI RNTI (Semi-Persistent CSI RNTI)

SPS Semi-Persistent Scheduling

SQN Sequence number

SR Scheduling Request

SRB Signaling Radio Bearer

SRS Sounding Reference Signal

SS Synchronization Signal

SSB SS Block

SSBRI SSB Resource Indicator

SSC Session and Service Continuity

SS-RSRP Synchronization Signal based Reference Signal Received Power

SS-RSRQ Synchronization Signal based Reference Signal Received Quality

SS-SINR Synchronization Signal based Signal to Noise and Interference Ratio

SSS Secondary Synchronization Signal

SSSG Search Space Set Group

SSSIF Search Space Set Indicator

SST Slice/Service Types

SU-MIMO Single User MIMO

SUL Supplementary Uplink

TA Timing Advance, Tracking Area

TAC Tracking Area Code

TAG Timing Advance Group

TAU Tracking Area Update

TB Transport Block

TBS Transport Block Size

TBD To Be Defined

TCI Transmission Configuration Indicator

TCP Transmission Communication Protocol

TDD Time Division Duplex

TDM Time Division Multiplexing

TDMA Time Division Multiple Access

TE Terminal Equipment

TEID Tunnel End Point Identifier

TFT Traffic Flow Template

TMSI Temporary Mobile Subscriber Identity

TNL Transport Network Layer

TPC Transmit Power Control

TPMI Transmitted Precoding Matrix Indicator

TR Technical Report

TRP, TRxP Transmission Reception Point

TRS Tracking Reference Signal

TRx Transceiver

TS Technical Specifications, Technical Standard

TTI Transmission Time Interval

Tx Transmission, Transmitting, Transmitter

U-RNTI UTRAN Radio Network Temporary Identity

UART Universal Asynchronous Receiver and Transmitter

UCI Uplink Control Information

UE User Equipment

UDM Unified Data Management

UDP User Datagram Protocol

UDR Unified Data Repository

UDSF Unstructured Data Storage Network Function

UICC Universal Integrated Circuit Card

UL Uplink

UM Unacknowledged Mode

UML Unified Modeling Language

UMTS Universal Mobile Telecommunications System

UP User Plane

UPF User Plane Function

URI Uniform Resource Identifier

URL Uniform Resource Locator

URLLC Ultra-Reliable and Low Latency

USB Universal Serial Bus

USIM Universal Subscriber Identity Module

USS UE-specific search space

UTRA UMTS Terrestrial Radio Access

UTRAN Universal Terrestrial Radio Access Network

UwPTS Uplink Pilot Time Slot

V2I Vehicle-to-Infrastruction

V2P Vehicle-to-Pedestrian

V2V Vehicle-to-Vehicle

V2X Vehicle-to-everything

VIM Virtualized Infrastructure Manager

VL Virtual Link;

VLAN Virtual LAN, Virtual Local Area Network

VM Virtual Machine

VNF Virtualized Network Function

VNFFG VNF Forwarding Graph

VNFFGD VNF Forwarding Graph Descriptor

VNFM VNF Manager

VoIP Voice-over-IP, Voice-over-Internet Protocol

VPLMN Visited Public Land Mobile Network

VPN Virtual Private Network

VRB Virtual Resource Block

WiMAX WiMAX (Worldwide Interoperability for Microwave Access)

WLAN Wireless Local Area Network

WMAN Wireless Metropolitan Area Network

WPAN Wireless Personal Area Network

X2-C X2-Control plane

X2-U X2-User plane

XML Extensible Markup Language

XRES EXpected user RESponse

XOR Exclusive OR

ZC Zadoff-Chu

ZP Zero Power

Terms

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

As used herein, the term “circuitry” refers to electronic circuits, logic circuits, processors (shared, dedicated, or groups) and/or memory (shared, dedicated, or groups) configured to provide the described functions; ASIC (Application Specific Integrated Circuit), FPD (field-programmable device) (e.g., FPGA (field-programmable gate array), PLD (programmable logic device), CPLD (complex PLD), HCPLD (high-capacity PLD), Refers to, is part of, or includes hardware components such as structured ASICs, or programmable SoCs), digital signal processors (DSPs), and the like. 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 program code and one or more hardware elements (or a combination of circuits used in an electrical or electronic system) used to perform the function of the program code. In such embodiments, a combination of hardware elements and program code may be referred to as a particular type of circuitry.

As used herein, the term "processor circuitry" refers to circuitry that sequentially and automatically performs a sequence of arithmetic or logic operations, or that can record, store, and/or transmit digital data, or is part of, or includes Processing circuitry may include one or more processing cores for executing instructions and one or more memory structures for storing program and data information. The term “processor circuitry” refers to one or more applications 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 program code , software modules, and/or any other device capable of executing computer-executable instructions or otherwise operating, such as functional processes. Processing circuitry may include more hardware accelerators, which may be microprocessors, programmable processing devices, and 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 with “processor circuitry” and may be referred to as such.

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

As used herein, the term “user equipment” or “UE” refers to a device with radio communication capabilities and can describe a remote user of network resources of a communication network. The term “user equipment” or “UE” refers to a 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 ( radio equipment), reconfigurable radio equipment, reconfigurable mobile device, etc., and may be referred to as synonymous. Also, the term “user equipment” or “UE” can include any computing device or any type of wireless/wired device that includes a wireless communication interface.

As used herein, the term “network element” refers to physical or virtualized equipment and/or infrastructure used to provide wired or wireless communication network services. The term "network element" is considered synonymous with networked computers, networking hardware, network equipment, network nodes, routers, switches, hubs, bridges, radio network controllers, RAN devices, RAN nodes, gateways, servers, virtualized VNFs, NFVIs, etc. may be and/or may be referred to as such.

As used herein, the term "computer system" refers to any type of interconnected electronic devices, computer devices, or components thereof. Additionally, the terms “computer system” and/or “system” may refer to various components of a computer that are communicatively coupled to each other. Also, the terms “computer system” and/or “system” may refer to multiple computer devices and/or multiple computing systems that are communicatively coupled to each other and configured to share computing and/or networking resources.

As used herein, the terms "appliance", "computer appliance", and the like refer to a computer device or computer having program code (eg, software or firmware) specifically designed to provide specific computing resources. refers to the system A “virtual appliance” is a virtual machine image implemented by a hypervisor-equipped device that virtualizes or emulates a computer appliance or is otherwise dedicated to providing specific computing resources.

As used herein, the term “resource” 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 specific device, e.g., 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, etc. “Hardware resource” may refer to computing, storage, and/or network resources provided by physical hardware element(s). “Virtualized resource” may refer to computing, storage, and/or network resources provided by a virtualization infrastructure to applications, devices, systems, and the like. The term “network resource” or “communication resource” can refer to resources accessible by computer devices/systems over a communications network. The term “system resources” may refer to any kind of shared entities for providing services, and may include computing and/or network resources. System resources can be considered as a set of coherent functions, network data objects or services accessible through a server, where these system resources reside on a single host or multiple hosts and are explicitly identifiable

As used herein, the term “channel” refers to any transmission medium, tangible or intangible, used to communicate data or data streams. The term "channel" includes "communication channel", "data communication channel", "transmission channel", "data transmission channel", "access channel", "data access channel", "link", "data link", "carrier" , "radio frequency carrier", and/or any other similar term indicating a path or medium through which data is communicated and/or may be equivalent thereto. Additionally, the term “link” as used herein refers to a connection between two devices over a RAT for the purpose of transmitting and receiving information.

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

The terms "coupled" and "communicatively coupled", along with their derivatives, are used herein. The term “coupled” can mean that two or more elements are in direct physical or electrical contact with each other, can mean that two or more elements are in indirect contact with each other but still cooperate or interact with each other, and / Or it may mean that one or more other elements are coupled or connected between elements that are said to be coupled to each other. The term “directly coupled” may mean that two or more elements are in direct contact with each other. The term “communicatively coupled” can mean that two or more elements can be brought into contact with each other by communication, including through a wired or other interconnect connection, through a wireless communication channel or link, and the like.

The term “information element” refers to a structural element that includes one or more fields. The term "field" refers to the individual content of an information element, or a data element that contains content.

The term "SMTC" refers to SSB-based measurement timing configuration configured by SSB-MeasurementTimingConfiguration .

The term "SSB" refers to the SS/PBCH block.

The term “Primary Cell” refers to an MCG cell operating on a primary frequency, where a UE performs an initial connection establishment procedure or initiates a connection re-establishment procedure.

The term "primary SCG cell" refers to a SCG cell in which a UE performs random access when performing a Reconfiguration with Sync procedure for DC operation.

The term "Secondary Cell" refers to a cell that provides additional radio resources other than a special cell for a CA-configured UE.

The term "Secondary Cell Group" refers to a PSCell for a DC configured UE and a subset of serving cells that includes zero or more secondary cells.

The term "serving cell" refers to a primary cell for a UE of RRC_CONNECTED that is not configured with CA/DC, and there is only one serving cell including the primary cell.

The term “serving cell” or “serving cells” refers to a set of cells including the special cell(s) for a UE of RRC_CONNECTED configured with CA/ and all secondary cells.

The term "Special Cell" refers to the PCell of MCG or the PSCell of SCG for DC operation, otherwise the term "Special Cell" refers to the Pcell.

Claims (25)

one or more non-transitory computer-readable media (NTCRM) having stored thereon instructions,
The instructions, 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 according to carrier aggregation;
One or more NTCRMs to encode an indication of a timing difference of transmissions on the first carrier and the second carrier, for transmission to a next generation Node B (gNB). 2. The method 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), and the indication of the timing difference is one or more NTCRMs, indicating a transmission timing difference between the first TAG and the second TAG. The method of claim 1 or 2, wherein the indication of the timing difference uses a granularity of one symbol length or a fraction of the symbol length relative to a reference subcarrier spacing (SCS). One or more NTCRMs, quantized by 4. The one or more NTCRMs of claims 1-3, wherein the indication of the timing difference is transmitted periodically or based on the occurrence of a triggering event. 5. The one or more NTCRMs of claim 4, wherein the triggering event is a request received from the gNB. 6. The method of any one of claims 1 to 5, wherein the indication of the timing difference is a measurement report, a medium access control (MAC) control element (CE), a physical One or more NTCRMs, transmitted on the physical uplink shared channel (PUSCH), or physical uplink control channel (PUCCH). 7. The method according to any one of claims 1 to 6, wherein the instructions, when executed, further cause the UE to: logical timing of the first and second messages, adjusted by the timing difference; ) determine whether the first message and the second message overlap based on whether they have at least one overlapping symbol. 8. The method of claim 7, wherein if it is determined that the first and second messages overlap, the instructions, when executed, further cause the UE to perform an uplink associated with at least one of the first and second messages. One or more NTCRMs, which cause multiplexing or dropping of control information. one or more non-transitory computer readable media (NTCRM) having instructions stored thereon,
The instructions, 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 according to carrier aggregation;
Receive, from the UE, an indication of a transmission timing difference of transmissions on the first carrier and the second carrier;
and processing the first and second channels based on the indicated transmit timing difference. 10. The method 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), and the indication of the transmission timing difference is the first TAG. One or more NTCRMs, indicating a transmission timing difference between TAG and the second TAG. 11. The one or more NTCRMs of claim 9 or 10, wherein the indication of transmission timing difference is quantized using a granularity of one symbol length or fraction of a symbol length relative to a reference subcarrier spacing (SCS). 12. The one or more NTCRMs of claims 9-11, wherein the indication of the transmission timing difference is received periodically from the UE. 13. The method of any of claims 9-12, wherein the instructions, when executed, further cause the gNB to encode the request for transmission timing difference for transmission to the UE, wherein the One or more NTCRMs wherein the indication of the transmission timing advance is received based on a request. 14. The method of any one of claims 9 to 13, wherein the indication of the transmission timing difference is a measurement report, a medium access control (MAC) control element (CE), a physical uplink shared channel (PUSCH), or a physical uplink control One or more NTCRMs, received on a channel (PUCCH). 15. The method of any one of claims 9-14, wherein the instructions, when executed, further cause the gNB to determine that the logical timings of the first and second messages, adjusted by the transmission timing difference, are at least To determine whether the first channel and the second channel overlap based on whether they have one overlapping symbol, and determine whether the first and second channels overlap based on the determination that the first and second channels overlap. wherein uplink control information associated with at least one of the NTCRMs is multiplexed or dropped. 16. The method of any one of claims 9-15, wherein the instructions, when executed, further cause the gNB to schedule transmission of the first channel by means of an uplink grant; wherein the uplink grant indicates whether control channels are multiplexed on the first channel. One or more non-transitory computer readable media (NTCRM) having stored thereon instructions, which, when executed by one or more processors, cause a user equipment (UE) to:
Receive downlink control information (DCI) including an indication of activation or deactivation of a rate-matching resource for physical downlink shared channel (PDSCH) transmission let it,
one or more NTCRMs to monitor for a physical downlink control channel (PDCCH) transmission during the PDSCH transmission based on the indication. 18. The method of claim 17, wherein the instructions, when executed, further cause the UE to: one or more orthogonal frequency division multiplexing (OFDM) symbols of a synchronization signal block (SSB) transmission. to determine that it is not available for the PDSCH transmission based on an overlap between this PDSCH resource allocation and the SSB transmission. 19. The one or more NTCRMs of claim 17 or 18, wherein the rate-matching resources are time-domain configured. 20. The NTCRM of any one of claims 17 to 19, wherein the rate-matching resources are configured per cell or per bandwidth part (BWP). 21. The NTCRM of any one of claims 17 to 20, wherein the rate-matching resource is determined based on a control resource set (CORESET) or SSB. 22. The one or more NTCRMs of claim 21 wherein the instructions, when executed, further cause the UE to determine a gap for beam switching based on the CORESET or the SSB. 23. The one or more NTCRMs of claims 17-22, wherein the DCI indicates that a subset of PDCCH monitoring occasions are activated during the PDSCH transmission. 24. The one or more NTCRMs of claims 17-23, wherein the DCI further indicates a PDCCH monitoring pattern used within the PDSCH transmission. 25. The one or more NTCRMs of claims 17-24, wherein the DCI further indicates a position of an active PDCCH monitoring occasion during the PDSCH transmission.

Images