DE112021002593T5 - RATE ADJUSTMENT RESOURCES FOR TRANSMISSIONS ON A DOWNLINK PHYSICAL SHARED CHANNEL (PDSCH) AND MULTIPLEXES OF UPLINK TRANSMISSIONS WITH DIFFERENT TIMINGS - Google Patents

Abstract

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

Description

CROSS REFERENCE TO RELATED APPLICATION

The present application claims priority from International Application No. PCT/ CN2020/103765 , filed July 23, 2020, the preliminary U.S. Patent Application No. 63/055,519 , filed on July 23, 2020 and the preliminary U.S. Patent Application No. 63/079,025 , filed September 16, 2020.

AREA

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

BACKGROUND

Various embodiments may relate generally to the field of wireless communications. Mobile communications have evolved significantly from early voice systems to today's highly complex integrated communications platform. The next generation wireless communication system, 5G, or New Radio (NR) will allow access to information and sharing of data anywhere and anytime by different users and applications. NR is expected to be a unified network/system aiming to meet very different and sometimes conflicting performance dimensions and services. Such diverse multi-dimensional needs are driven by different services and applications. In general, NR will continue to evolve based on 3GPP-LTE-Advanced with additional potential new Radio Access Technologies (RATs: Radio Access Technologies) to enrich people's lives with better, simple and seamless wireless connectivity solutions. NR enables everything to be connected wirelessly and will deliver fast, rich content and services.

character list

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

DETAILED DESCRIPTION

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

Various embodiments provide rate matching resource techniques for transmissions on a downlink physical shared channel (PDSCH). In addition, embodiments provide techniques for multiplexing uplink transmissions on multiple carriers with different uplink transmission timings.

RATE ADJUSTMENT RESOURCES FOR PDSCH TRANSMISSIONS

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

Furthermore, the rate adaptation resource can be configured via a bitmap indicating time and frequency resources with some periodicity, or configured as a control resource set (CORESET). In the latter case, a planned PDSCH is rate-adjusted around the CORESET, as in 1 shown.

For systems operating above a carrier frequency of 52.6 GHz, particularly for terahertz communications, it is considered that a larger subcarrier spacing is needed to combat severe phase noise. In cases where a larger subcarrier spacing, e.g. B. 1.92 MHz or 3.84 MHz, is used, the slot duration can be very short. For example, for a subcarrier spacing of 1.92 MHz, the slot duration is approximately 7.8 µs. This extremely short slot duration may not be enough for processing higher layers, including Medium Access Layer (MAC) and Radio Link Control (RLC), etc. To solve this problem, a next-generation NodeB (gNB) can use the Downlink (DL) or uplink (UL) data transmission via plan a slot limit with a long transmission time. In other words, a slot concept may not be needed when planning data transfer. 2 illustrates an example of a long PDSCH transmission time.

When a planned PDSCH transmission period is relatively long and a PDCCH monitoring opportunity is relatively short, the UE may need to monitor a PDCCH and perform blind decoding of PDCCHs within the PDSCH transmission period. For some cases where there is no additional traffic for the UE, PDCCH monitoring within a PDSCH transmission may not be needed, so UE power consumption is reduced. Furthermore, appropriate CORESET or configured rate adaptation resources can be allocated for a PDSCH transmission, which can help improve spectrum efficiency. Therefore, certain mechanisms may need to be defined to allow the UE to skip the PDCCH monitoring opportunity or only monitor a subset of PDCCH opportunities during a PDSCH transmission.

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

Signaling details about dynamic activation of a subset of rate adaptation resources

As mentioned above, for systems operating above a carrier frequency of 52.6 GHz, particularly for terahertz communications, it is considered that a larger subcarrier spacing is needed to combat severe phase noise. In a case where a larger subcarrier pitch, e.g. B. 1.92 MHz or 3.84 MHz, is used, the slot duration can be very short. For example, for a subcarrier spacing of 1.92 MHz, the slot duration is approximately 7.8 µs. This extremely short slot duration may not be sufficient for higher layer processing including Media Access Layer (MAC: Medium Access Layer) and Radio Link Control (RLC: Radio Link Control) etc. To solve this problem, a gNB can use DL or UL data transmission planning over a slot boundary with a long transmission time.

When a planned PDSCH transmission period is relatively long and a PDCCH monitoring opportunity is relatively short, a UE may need to monitor a PDCCH and perform blind decoding of PDCCHs within the PDSCH transmission period. For some cases where there is no additional traffic for the UE, PDCCH monitoring within a PDSCH transmission may not be needed, so UE power consumption is reduced. Furthermore, appropriate CORESET or configured rate adaptation resources can be allocated for a PDSCH transmission, which can help improve spectrum efficiency. Therefore, certain mechanisms may need to be defined to allow the UE to skip the PDCCH monitoring opportunity or only monitor a subset of PDCCH opportunities during a PDSCH transmission. Embodiments of the present disclosure may provide signaling details about dynamic activation of a subset of rate adaptation resources, as described in more detail below.

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

Furthermore, when a rate adaptation resource is configured as a cell level, if enabled or configured, the entire resource in the system bandwidth is used for PDSCH rate adaptation. When the Rate Adaptation Resource is configured as Bandwidth Share (BWP) level, if enabled or configured, the entire resource in BWP is used for PDSCH Rate Adaptation.

In another embodiment, when CORESET is configured as a rate adjustment resource, only one CORESET resource is needed in the time domain for the rate adjustment resource. In particular, a time domain res source by higher layer parameters monitoringSlotPeriodicityAndOffset, duration and monitoringSymbolsWithinSlot of all searchspace-sets configured by SearchSpace, and a time-domain resource of search-space-set zero set-zero) configured by searchSpaceZero associated with the CORESET, as well as a CORESET duration configured by ControlResourceSet (ControlResourceSet) with controlResourceSetld (ControlResourceSetId) or ControlResourceSetZero (ControlResourceSetNull).

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

The gap or K-symbols can be additionally configured by higher layers via Minimum System Information (MSI), Remaining Minimum System Information (RMSI), Other System Information (OSI) or dedicated Radio Resource Control (RRC) signalling. This may also depend on UE capability at beam switching time.

3 illustrates a rate adjustment resource based on CORESET. As shown, a symbol gap 1 is inserted before and after CORESET as the rate adaptation resource.

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

When other DL channels or signals including PDCCH, channel state information reference signal (CSI-RS), phase tracking reference signal (PT-RS), etc. overlap with the symbols containing the SSB transmission, the UE assumes that the OFDM - Symbols containing the SSB transmission are not available for another DL channel transmission. In particular, the UE may not monitor the PDCCH candidate if it overlaps with the symbols containing the SSB transmission. Likewise, CSI-RS and/or PT-RS is dropped on the symbols containing the SSB transmission.

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

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

In one option, an indication of whether PDSCH can be carried on a symbol alongside the symbols for CORESET/PDCCH or SSB transmission with one or more SSB indices can be configured by higher layers via RRC signalling. When configured, the UE can transmit PDSCH and CORESET/PDCCH or SSB transmission with one or more SSB indices on consecutive symbols or the same symbols.

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

In another embodiment, if the same Tx beam is used for the transmission of PDCCH and PDSCH or SSB and PDSCH will end, it may be possible for PDSCH and PDCCH or SSB to be multiplexed in a TDM manner before DFT operation. In this case, if the same QCL assumption is applied for PDSCH and PDCCH/CORESET or SSB and if PDSCH overlaps with PDCCH/CORESET or SSB in a same symbol, PDSCH can be rate matched by the temporal samples before DFT operation that contain the PDCCH/CORESET or SSB transmission in the same symbol.

In one option, an indication of whether a PDSCH can be rate-matched around the resource allocated for CORESET/PDCCH or SSB transmission with one or more SSB indices can be configured by higher layers via RRC signalling . When configured, the UE can assume that the PDSCH is rate-matched around the temporal samples before the DFT operation containing the PDCCH/CORESET or SSB transmission in the same symbol.

In another option, whether a PDSCH can be rate matched around the resource allocated for CORESET/PDCCH or SSB transmission with one or more SSB indices can be derived by the TCI state for the PDSCH. According to the TCI state, if the PDSCH undergoes a QCL with a CORESET/PDCCH or an SSB, the UE can assume that the PDSCH will be rate adjusted by the samples in the time before the DFT operation that the PDCCH/CORESET or contain the SSB transmission in the same symbol.

In another embodiment, a field in the DCI for scheduling the PDSCH may be used to indicate that a subset of PDCCH monitoring opportunities are activated during the PDSCH transmission period. Herein, the set of PDCCH monitoring opportunities refers to all PDCCH monitoring opportunities configured by a high-layer parameter SearchSpace that overlap the scheduled PDSCH. If the subset of PDCCH monitoring opportunities is disabled during a PDSCH transmission, the UE can skip the PDCCH monitoring and does not have to perform PDCCH blind decoding on the subset of PDCCH monitoring opportunities.

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

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

In another example, a field in the DCI can be used to indicate whether a first or second half of PDCCH monitoring opportunities are activated during the PDSCH transmission period. In particular, bit '1' can be used to indicate that a first half of PDCCH monitoring opportunities are activated during the PDSCH transmission period; while bit '0' can be used to indicate that a second half of PDCCH monitoring opportunities are activated during the PDSCH transmission period.

5 Figure 12 illustrates an example of an indication of whether a subset of PDCCH monitoring opportunities is enabled or disabled. In the example, a field is used in the DCI for scheduling the PDSCH to indicate that a first PDCCH monitoring opportunity is disabled and the UE can skip the PDCCH monitoring on the disabled PDCCH monitoring opportunity.

In another embodiment, a subset of PDCCH monitoring opportunities activated during the PDSCH transmission period is predefined or configured by high layer signaling. Herein, the set of PDCCH monitoring opportunities refers to all PDCCH monitoring opportunities configured by a high-layer parameter SearchSpace that overlap with the planned PDSCH. If the subset of PDCCH monitoring opportunities is disabled during a PDSCH transmission, the UE can use the PDCCH Skip monitoring and need not perform PDCCH blind decoding on the subset of PDCCH monitoring opportunities.

In one option, the subset of PDCCH supervision opportunity patterns can be configured within a PDSCH transmission period by higher layers. The UE can perform PDSCH rate adaptation around CORESET or the detected PDCCH on the activated PDCCH monitoring opportunity.

In another option, the subset of PDCCH monitoring opportunities can be predefined in the specification. In one example, all even positions of PDCCH monitoring opportunities are activated during the PDSCH transmission period. The PDCCH monitoring opportunities overlapping the scheduled PDSCH are numbered serially or the PDCCH monitoring opportunities are scheduled according to a reference timing, e.g. B. Symbol 0 in SFN 0, numbered. In another example, the PDCCH monitoring opportunity(s) that overlap the second half of the scheduled PDSCH are activated during the PDSCH transmission duration. In another example, only the last N PDCCH monitoring opportunity(s) that overlap the scheduled PDSCH are activated during the PDSCH transmission period, where N is equal to 1 or greater than 1. N could be predefined or configured by high layer signalling.

In another embodiment, more than one set 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 is detected in a first group of search space sets, the UE can switch from the first group of search space sets to the second group of search space sets. In one option, the UE starts from the first symbol for a planned PDSCH transmission for PDCCH surveillance opportunities in the second group of search space sets. In another option, the UE starts from N symbols after the detected PDCCH for PDCCH surveillance opportunities in the second group of search space sets. N is predefined or configured by a high layer. N can be determined by the UE's ability to process the time between PDCCH and PDSCH.

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

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

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

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

In another embodiment, a Demodulation Reference Signal (DMRS) associated with PDSCH or PDCCH may be used to indicate activation or deactivation of PDCCH monitoring opportunities within a PDSCH transmission period.

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

In an option, the DMRS in the 2nd set of DMRS resource can also be used for channel estimation for PDCCH decoding on the activated PDCCH monitoring opportunity. Furthermore, the PDCCH transmitted on the activated PDCCH monitoring opportunity may be a k-symbol after the DMRS in the 2nd set of DMRS resources, where k is predefined in the specification or by higher layers via MSI-, RMSI(SIB1 ), OSI or RRC signaling can be configured.

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

PDSCH resource allocation with rate adaptation resources

For a PDSCH with a long duration, a DCI can be used to schedule multiple PDSCHs with different Transport Blocks (TB) or multiple Code Blocks (CB) or Code Block Groups (CBG). Furthermore, each CB or CBG can be aligned with a symbol boundary and the same length can be applied to the transmission of each CB or CBG. Similarly, in the case of multiple PDSCH scheduling, each PDSCH can span the same number of symbols.

8th illustrates an example of PDSCH with multiple CBGs when the PDSCH does not collide with enabled or configured rate adaptation resources. In the example, the PDSCH includes 8 CBGsS with continuous resource allocation. Furthermore, each CBG spans 4 symbols.

If a PDSCH transmission collides with a rate adaptation resource during the PDSCH transmission period, certain mechanisms for PDSCH resource allocation or transmission of each PDSCH in case of multiple PDSCH scheduling or transmission of each CB or CBG must be defined. It is noted that although the following embodiments are applied to the case of a PDSCH transmission involving one or more CBs or CBGs, the embodiments are easily applied to the case of a multiple PDSCH transmission or a PDSCH with slot aggregation can become. Embodiments directed to PDSCH resource allocation with rate adaptation resources are described in more detail below.

In one embodiment, a PDSCH including one or more CBs or one or more CBGs is assigned according to the start symbol and length indicator (SLIV) specified in the DCI for planning the PDSCH. This can be specified as a nominal resource allocation. In particular, the first CB/CBG or the first PDSCH is assigned 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.

Furthermore, when a PDSCH transmission including one or more CB/CBGs with an activated rate adaptation resource, e.g. B. CORESET, or an activated PDCCH monitoring opportunity or an SSB block, the CB/CBG or the PDSCH will not be transmitted on the activated rate adaptation resource. Furthermore, the affected CB/CBG or PDSCH is rate adjusted or punctured around the activated rate adaptation resources. Note that this can be specified as an actual resource allocation.

It is noted that the transport block size (TBS) is determined according to the duration of the first CB/CBG or the PDSCH or the nominal resource allocation. The determined TBS is also applied for other CB/CBGs or PDSCHs regardless of whether the CB/CBGs and PDSCHs with activated rate adaptation resources collide.

Alternatively, when colliding with activated rate matching resources, the TBS on the affected CB/CBGs or PDSCHs may be determined according to an actual number of symbols or resources other than the activated rate matching resources or the actual resource allocation.

9 Figure 12 illustrates an option of PDSCH resource allocation when colliding with enabled rate adaptation resources. For this option, each CBG is allocated 5 symbols and the CBG#3 collides with the activated rate matching resource spanning two symbols. In this case, CBG#3 will be charged by the activated rate adaptation resource rate matched with the TBS determined according to the nominal allocation.

Furthermore, if a PDSCH transmission including one or more CB/CBGs collides with a disabled rate adaptation resource, CB/CBG or PDSCH continues to map onto the disabled rate adaptation resources.

10 Figure 12 illustrates an option of PDSCH resource allocation when colliding with disabled rate adaptation resources. For this option, each CBG is allocated 5 symbols and the CBG#3 collides with the disabled rate matching resource spanning two symbols. In this case, the CBG#3 and subsequent CBGs are allocated in consecutive symbols without considering deactivated rate adaptation resources.

In another embodiment, when a PDSCH transmission including one or more CB/CBGs with an activated rate adaptation resource, e.g. B. CORESET, or a disabled PDCCH monitoring opportunity or an SSB block, the CB/CBG or the PDSCH will not be transmitted on the enabled rate adaptation resource. Furthermore, the affected CB/CBG or PDSCH continues to be transmitted after the activated rate adaptation resource and spans the number of symbols as specified in the DCI. With this option, the actual resource allocation of CB/CBG or PDSCH is the same as the nominal resource allocation specified in the DCI.

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

In another embodiment, the PDSCH allocation is based first on the SLIV specified in the DCI and a configured rate adaptation resource within the PDSCH transmission period. In particular, when a CB/CBG or PDSCH collides with a configured rate matching resource, the CB/CBG or PDSCH is further mapped after the configured rate matching resource and spans the specified number of symbols over SLIV.

In the second step, for the configured rate adaptation resource that is not activated, the CB/CBG or PDSCH in front of the deactivated rate adaptation resource is mapped to the deactivated rate adaptation resource.

12 Figure 12 illustrates another option of PDSCH resource allocation when colliding with enabled rate adaptation resources. In the example, each CBG is assigned 5 symbols. Furthermore, 2 configured rate adaptation resources collide with the PDSCH within the PDSCH transmission period, the first being enabled and the second being disabled. In this case, CBG#3 is mapped to the second rate matching resource, which is disabled.

MULTIPLEXING UPLINK TRANSMISSIONS ON MULTIPLE CARRIERS WITH DIFFERENT UPLINK TRANSMISSION TIMINGS

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

In carrier aggregation (CA: carrier aggregation), the component carriers can belong to a different timing advance group (TAG). If the carriers have the same TAG, they are exactly synchronized. On the other hand, if the bearers have different TAGs, there might be a time difference between downlink (DL) reception and uplink (UL) transmission on the UE side. The exact value of the time difference is affected by the synchronization error and the propagation delay. For a UL time difference between two carriers, it is also affected by the TA values of the two carriers. Due to the extremely short symbol length in the frequency above 52.6 GHz, the time difference could be of the order of one or more symbols. To this end, the impact this could have on the multiplexing of UL signals/channels is a problem that should be solved.

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 the two carriers have different UL transmission timings, even in case the reception timing at the gNB is exactly aligned for the two UL carriers. The difference in UL transmission timings depends on several factors. The UL transmission timing of a UL carrier is determined by the DL reception timing of the associated DL carrier and the TA value. The DL transmission timings of the two associated DL carriers may not be ideally aligned. The propagation delay between gNB and UE can 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 are different. Even if the two BSs are co-located, the propagation delay may differ due to the different frequency of the two DL carriers. In particular, the two DL carriers may belong to a different frequency range (FR) that has much different propagation properties. As a result, the DL reception timings for the two DL carriers at the UE may be different. Furthermore, the DL reception timings at the UE are not exactly known by the gNB. The Timing Advance (TA) value is obtained through an initial access and can also be adjusted through the TA instruction. Furthermore, a gNB and a UE may not have exactly the same knowledge about the TA value. Therefore, a gNB may not know the exact difference of UL transmission timings of two UL carriers of a specific UE.

For a system operating above a carrier frequency of 52.6 GHz, the subcarrier spacing (SCS) could be quite large, resulting in a very short symbol length. For example, it is about 0.56 µs for the 1.92 MHz SCS. On the other hand, the time difference between two UL carriers can be a few microseconds or more. If carrier aggregation of a carrier at FR1 and another carrier in a frequency above 52.6 GHz is taken into account, the time difference of the two UL carriers can be even higher. From the above analysis, the time difference of the two UL carriers can correspond to several or tens of symbols. Consequently, two UL channels overlapping on the UE side may be separated on the gNB side, or two UL channels separated on the UE side may overlap on the gNB side. Furthermore, if the gNB does not know the exact difference of the UL transmission timings, a gNB cannot know whether two UL transmissions on the two UL carriers on the UE side overlap or not.

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

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

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

quantisiert werden, wobei T die Länge eines Symbols ist. Bei diesem Schema werden, falls zwei UL-Kanäle als überlappend angesehen werden, die zwei UL-Kanäle tatsächlich durch mindestens ein Halbsymbol überlappt. Falls zwei UL-Kanäle als nicht überlappend angesehen werden, können sich die zwei UL-Kanäle mit höchstens einem Halbsymbol überlappen.In an option where the actual time difference is denoted as t, t could be broken down into a number of symbols $\mathrm{i.e}=flOO\mathrm{right}\left(\frac{t}{T}+c\right),e.G.c=0.5$

are quantized, where T is the length of a symbol. With this scheme, if two UL channels are considered to be overlapping, the two UL channels are actually overlapped by at least one half symbol. If two UL channels are considered non-overlapping, the two UL channels can overlap by at most one half symbol.

The UE can periodically report the timing difference to the gNB. Alternatively, the UE may report the timing difference under a certain condition. For example, if the UE identifies that the timing difference is changed by an amount greater than a threshold, the UE reports the new timing difference to the gNB. The above threshold can be fractional, single or multi-symbol duration. Alternatively, the gNB can send a trigger for the report if required. Once the trigger is received, the UE reports the current timing difference or the delta between the updated timing difference and the old timing difference to the gNB.

The timing difference report may be included in a high layer signaling measurement report. Alternatively, the reporting of the timing difference could be maintained in a Media Access Control Control Element (MAC-CE) on an Uplink Physical Shared Channel (PUSCH). Alternatively, the reporting of the timing difference could be done at the physical layer. For example, an uplink physical control channel (PUCCH) or PUSCH resource based on periodic or semi-persistent scheduling (SPS) may be configured such that the UE may report the timing difference periodically. Or a downlink control channel (DCI) can be used to trigger an aperiodic report of the timing difference on a PUSCH.

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

In one embodiment, the UE could report the actual transmission timing difference d between the two TAGs or the two UL carriers to the gNB and determine whether two UL channels overlap on the two UL carriers based on the actual transmission timings of the two UL carriers or not. On the other hand, the gNB could determine whether or not two UL channels overlap on the two UL channels 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 multiplexed or dropped, e.g. B. according to the current specification as defined in Rel-15 and Rel-16-NR. Otherwise the two UL channels are transmitted separately. With this scheme, the gNB and the UE could have a common understanding on whether/how to multiplex or drop one or more of the multiple UL channels.

13 illustrates a procedure of overlap checking based on a UE reported time difference of two carriers.

In one embodiment, the UE could report 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 determine whether two UL channels on the two UL carriers intersect or not. On the other hand, the gNB could determine whether or not two UL channels overlap on two UL carriers based on the logical timings of the two UL channels and also 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 multiplexed or dropped, e.g. B. according to the current specification as defined in Rel-15 and Rel-16-NR. Otherwise the two UL channels are transmitted separately. With this scheme, the gNB and the UE could have a common understanding on whether/how to multiplex or drop one or more of the multiple UL channels.

14 illustrates a procedure of overlap checking based on a UE reported time difference of two carriers.

und der neue Symbolindex im Slot s' ist l' = mod(L · s + l · d, L). Die neuen Indizes s' und l' werden bei der Überlappungsprüfung verwendet. Wenn die zwei UL-Kanäle nach dem Anwenden des Offsets auf die logischen Timings mindestens ein überlappendes Symbol aufweisen, werden die mit den beiden UL-Kanälen assoziierten UL-Informationen gemultiplext oder fallen gelassen, z. B. gemäß der aktuellen Spezifikation, wie in Rel-15- und Rel-16-NR definiert. Andernfalls werden die zwei UL-Kanäle separat übertragen. Mit diesem Schema haben die gNB und der UE ein gemeinsames Verständnis darüber, ob/wie ein oder mehrere der mehreren UL-Kanäle gemultiplext oder fallen gelassen werden sollen.In one embodiment, the logical timings of two UL channels, adjusted by an offset, are used to determine whether or not the two UL channels overlap. The offset reflects the time difference between the two TAGs or the two UL carriers. For example, a logical timing symbol of symbol index I in slot s, after applying an offset d, is the new slot index $s\text{'}=flOO\mathrm{right}\left(\frac{L\cdot s+l-\mathrm{i.e}}{L}\right)$

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

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

• • Der UL-Kanal 2 (421) wird als mit dem UL-Kanal 1 überlappend angesehen, da sie gemeinsame Symbolindizes 6, 7, 8 und 9 aufweisen. Tatsächlich sind manche Symbolindizes des UL-Kanals 411 vor dem Anwenden des Offsets -3 auch das gleiche wie der UL-Kanal 2.
• • Der UL-Kanal 3 (422) wird als mit dem UL-Kanal 1 überlappend angesehen, da sie gemeinsame Symbolindizes 5 und 6 aufweisen, obwohl sich die Symbolindizes des UL-Kanals 411 vor dem Anwenden des Offsets -3 vom UL-Kanal 3 unterscheiden.
• • Der UL-Kanal 4 (423) wird als mit dem UL-Kanal 1 nicht überlappend betrachtet, da sie keine gemeinsamen Symbolindizes aufweisen, obwohl die Symbolindizes des UL-Kanals 411, bevor der Offset -3 angewendet wird, gemeinsame Symbolindizes 11 und 12 mit dem UL-Kanal 4 aufweisen.
• • Der UL-Kanal 5 (424) wird immer noch als nicht überlappend mit dem UL-Kanal 1 angesehen, da sie auch nach dem Anwenden eines Offsets keine gemeinsamen Symbolindizes aufweisen.

4 illustrates an example of overlap checking by logical timing with offset. It is assumed that the two carriers have the same SCS and hence the same symbol length. The transmission timing of carrier 1 is 3 symbols earlier than carrier 2. Therefore, the gNB can configure a left offset of 3 symbols for carrier 1. On the other hand, carrier 2 is the reference to define an offset, e.g. eg the offset is 0 for carrier 2. Off 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 the offset with value -3 (412). Whether UL channel 1 overlaps with a UL channel on carrier 2 is done by examining the symbol indices of UL channel 412 and the UL channel on carrier 2.

• • UL channel 2 (421) is considered to overlap with UL channel 1 since they share symbol indices 6, 7, 8 and 9 in common. In fact, before applying the -3 offset, some symbol indices of UL channel 411 are also the same as UL channel 2.
• • UL channel 3 (422) is considered to overlap with UL channel 1 because they share symbol indices 5 and 6 in common, although the symbol indices of UL channel 411 are different from UL channel 3 before applying the offset -3 differentiate.
• • UL channel 4 (423) is considered non-overlapping with UL channel 1 because they do not share symbol indices, although the symbol indices of UL channel 411 before the offset -3 is applied share symbol indices 11 and 12 with the UL channel 4.
• • UL channel 5 (424) is still considered non-overlapping with UL channel 1 since they do not share symbol indices even after applying an offset.

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

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

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

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

In one embodiment, the UL grant for a PUSCH scheduled by a UL grant indicates whether/which UL control channel(s) can be multiplexed on the PUSCH. Since there can be confusion whether a PUCCH overlaps the PUSCH, the indicator in the UL grant helps the UE to know whether UCI multiplexed on PUSCH needs to be performed in order to have aligned operation as a gNB. In the event that there are multiple non-overlapping PUCCHs, the indicator in the UL grant may further distinguish the one or more PUCCHs that need to be multiplexed onto the PUSCH. Whether two PUCCH or PUSCH channels overlap or not could be determined by the actual transmission timing of the two UL carriers on the UE side, or by the logical timing of the two UL carriers, or by the logical timings of two UL carriers transmitted around an offset of a time difference can be determined.

SYSTEMS AND IMPLEMENTATIONS

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

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

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

In some embodiments, the network 1900 may include multiple UEs that couple directly to each other over a sidelink interface are pelt. The UEs may be M2M/D2D devices communicating using physical sidelink channels such as PSBCH, PSDCH, PSSCH, PSCCH, PSFCH, etc., among others.

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

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

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

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

The RAN 1904 can provide the air interface over licensed spectrum or unlicensed spectrum. To operate in the unlicensed spectrum, the nodes can use LAA, eLAA and/or feLAA mechanisms based on CA technology with PCells/Scells. Before accessing the unlicensed spectrum, the nodes may perform medium/carrier acquisition operations based on, for example, a Listen Before Talk (LBT) protocol.

In V2X scenarios, the UE 1902 or AN 1908 may be or act as an RSU, which may refer to any transport infrastructure entity used for V2X communications. An RSU can be implemented in or by a suitable AN or a stationary (or relatively stationary) UE. An RSU may be implemented in or by: a UE may be referred to as a "UE-type RSU"; an eNB may be referred to as an "eNB-type RSU"; a gNB may be referred to as a "gNB-type RSU"; and the same. In one example, an RSU is a computing device coupled to radio frequency circuitry located at a roadside 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, and applications/software to capture and control ongoing vehicle and pedestrian traffic. The RSU can provide very low latency communications required for high speed events such as crash 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 network interface controller to provide a wired (e.g., Ethernet) connection to a traffic signal control or a backhaul network.

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

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

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

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

In some embodiments, the 5G NR air interface can use BWPs for different purposes. For example, BWP can be used to dynamically adjust the SCS. For example, the UE 1902 may be configured with multiple BWPs, with each BWP configuration having a different SCS. When a BWP change is indicated to the UE 1902, the SCS of the transmission is also changed. Another use case example for BWP is related to power conservation. In particular, multiple BWPs for the UE 1902 can be configured with a different amount of frequency resources (e.g., PRBs) to support data transmission under different traffic load scenarios. A BWP containing a reduced number of PRBs can be used for data transmission with low traffic load while allowing power savings at the UE 1902 and in some cases at the gNB 1916. A BWP containing a larger number of PRBs can be used for higher traffic load scenarios.

The RAN 1904 is communicatively coupled to the CN 1920, which includes network elements to provide various functions to support data and telecommunications services for customers/subscribers (e.g., users of the UE 1902). The components of the CN 1920 can be implemented in one physical node or separate physical nodes. In some embodiments, NFV can be used to virtualize any or all of the functions provided by the network elements of CN 1920 onto physical compute/storage resources in servers, switches, and so on. A logical instantiation of the CN 1920 may be referred to as a network slice, and a logical instantiation of a portion of the CN 1920 may be referred to as a network subslice.

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

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

The SGW 1926 can terminate an S1 interface towards the RAN and route data packets between the RAN and the LTE-CN 1922. The SGW 1926 can be a local mobility anchor for inter-RAN node handover and can also provide an anchor for inter-3GPP mobility. Other jurisdictions may include lawful interception, billing, and some policy enforcement.

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

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

The PGW 1932 may terminate an SGi interface to a data network (DN) 1936 that may include an application/content server 1938 . The PGW 1932 can route data packets between the LTE-CN 1922 and the data network 1936. The PGW 1932 may be coupled to the SGW 1926 through an S5 reference point to enable user-level tunneling and tunnel management. The PGW 1932 may also include a policy enforcement and billing data collection node (e.g., PCEF). Additionally, the SGi reference point between the PGW 1932 and the data network 1936 may be an off-carrier public, a private PDN, or an on-carrier packet data network, for example to provide IMS services. The PGW 1932 may be coupled to a PCRF 1934 via a Gx reference point.

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

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

The AUSF 1942 can store data for authentication of the UE 1902 and handle authentication related functionality. The AUSF 1942 can enable a common authentication framework for different access types. In addition to communicating with other elements of the 5GC 1940 via reference points as shown, the AUSF 1942 may have a NausF service-based interface.

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

The SMF 1946 may be responsible for SM (e.g. session establishment, tunnel management between the UPF 1948 and an AN 1908); UE IP address allocation and management (including optional authorization); selection and control of a UP function; configure traffic routing at the UPF 1948 to route traffic to an appropriate destination; completion of interfaces to policy control functions; Controlling some policy enforcement, billing, and QoS; lawful interception (for SM events and interface to LI system); Completion of SM parts of NAS messages; downlink data notification; initiating AN-specific SM information sent via AMF 1944 to AN 1908 via N2; and determining an SSC mode of a session. SM can refer to the management of a PDU session, and a PDU session or "session" can refer to a PDU connectivity service that provides or enables the exchange of PDUs between the UE 1902 and the data network 1936 .

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

The NSSF 1950 can select a set of network slice entities that serve the UE 1902. The NSSF 1950 can also determine permissible NSSAIs and the mapping to the subscribed S-NSSAIs, if necessary. The NSSF 1950 can also determine an AMF set to be used to serve the UE 1902 or a list of candidate AMFs based on appropriate configuration and possibly by querying the NRF 1954 . The selection of a set of network slice entities for the UE 1902 may be triggered by the AMF 1944 with which the UE 1902 is registered interacting with the NSSF 1950, which may result in a change in the AMF. The NSSF 1950 can interact with the AMF 1944 via an N22 reference point; and can communicate with another NSSF in a visited network via an N31 reference point (not shown). In addition, the NSSF 1950 may have a service-based Nnssf interface.

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

The NRF 1954 may support service discovery functions, receiving NF discovery requests from NF entities and providing the information of the discovered NF entities to the NF entities. The NRF 1954 also holds information of available NF entities and their supported services. As used herein, the terms "instantiate," "instantiation," and the like may refer to the creation of an instance, and an "instance" may refer to a tangible occurrence of an object that may occur, for example, during the execution of program code. In addition, the NRF 1954 may have a service-based Nrf interface.

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

The UDM 1958 may handle subscription related information to support the handling of communication sessions by the network entities and may store UE 1902 subscription data. For example, subscription data can be communicated between the UDM 1958 and the AMF 1944 via an N8 reference point. The UDM 1958 can include two parts, an application front end and a UDR. The UDR may store subscription data and policy data for the UDM 1958 and the PCF 1956 and/or structured data for discovery and application data (including PFDs for application detection, application request information for multiple UEs 1902) for the NEF 1952. The UDR 221 may have the service-based Nudr interface to allow the UDM 1958, the PCF 1956 and the NEF 1952 to access a specific set of stored data, as well as to read, update notification of relevant data changes in the UDR (e.g. add, modify), delete and subscribe. The UDM may include a UDM-FE responsible for credential processing, location management, subscription management, and so on. Several different frontends can supply 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, the UDM 1958 may have the Nudm service-based interface.

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

In some embodiments, the 5GC 1940 may enable edge computing by selecting the operator/third party services to be geographically close to a point where the UE 1902 is connected to the network. This can reduce latency and load on the network. To provide edge computing implementations, the 5GC 1940 can select a UPF 1948 near the UE 1902 and perform traffic routing from the UPF 1948 to the data network 1936 over the N6 interface. This may be based on the UE subscription data, UE location and information provided by the AF 1960. In this way, the AF 1960 can affect UPF (Re)selection and traffic routing. Based on the operator deployment, if the AF 1960 is considered a trusted entity, the network operator can allow the AF 1960 to directly interact with relevant NFs. In addition, the AF 1960 may have a service-based Naf 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 application/content server 1938, for example.

20 12 schematically illustrates a wireless network 2000 according to various embodiments. The 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.

The UE 2002 may be communicatively coupled to the AN 2004 via a link 2006 . Link 2006 is illustrated as an air interface to enable communicative coupling and may be cellular communication protocols such as an LTE protocol or a 5G NR protocol operating at mmWave or sub-6 GHz frequencies. be consistent.

The UE 2002 may include a host platform 2008 coupled to a modem platform 2010 . Host platform 2008 may include application processing circuitry 2012 that may be coupled to protocol processing circuitry 2014 of modem platform 2010 . The application processing circuitry 2012 may execute various applications for the UE 2002 that yield/ingest application data. The application processing circuitry 2012 may further implement one or more layer operations to transmit/receive application data to/from a data network. These layer operations may include transport (e.g. UDP) operations and Internet (e.g. IP) operations.

Protocol processing circuitry 2014 may implement one or more layer operations to enable transmission or reception of data over link 2006 . The layer operations implemented by the protocol processing circuitry 2014 may include MAC, RLC, PDCP, RRC, and NAS operations, for example.

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

Modem platform 2010 may further include transmit circuitry 2018, receive circuitry 2020, RF circuitry 2022, and RF front end (RFFE) 2024, which may include or be connected to one or more antenna panels 2026. Briefly, transmit circuitry 2018 may include a digital-to-analog converter, a mixer, intermediate frequency (IF) components, etc.; the receiving circuitry 2020 may include analog-to-digital converters, mixers, IF components, etc.; RF circuitry 2022 may include a low noise amplifier, a power amplifier, power tracking components, etc.; RFFE 2024 may include filters (e.g., surface/bulk acoustic wave filters), switches, antenna tuners, beamforming components (e.g., phased array antenna components), and so on. The selection and arrangement of the components of transmit circuitry 2018, receive circuitry 2020, RF circuitry 2022, RFFE 2024, and antenna panels 2026 (commonly referred to as "transmit/receive components") may be specific to details of a specific implementation, such as for Example, whether the communication is TDM or FDM, in mmWave or sub-6 GHz frequencies, etc. In some embodiments, the transmit/receive components may be arranged in multiple parallel transmit/receive chains, may be in the same or different chips/ be arranged in modules, etc.

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

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

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

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

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

The processors 2110 may include a processor 2112 and a processor 2114, for example. The processors 2110 can be, for example, a central processing unit (CPU), a RISC (Reduced Instruction Set Computing) processor, a CISC (Complex Instruction Set Computing) processor, a graphics processing unit (GPU), a DSP such as a baseband processor, an ASIC , an FPGA, a radio frequency integrated circuit (RFIC), other processor (including those discussed herein), or any suitable combination thereof.

Storage/storage devices 2120 may include main memory, disk storage, or any suitable combination thereof. The memory/storage devices 2120 may include any type of volatile, non-volatile, or semi-volatile memory, such as dynamic random access memory (DRAM), static random access memory (SRAM), erasable programmable read only memory (EPROM), electrically erasable programmable only, among others -Read-only memory (EEPROM), flash memory, solid-state storage, etc.

The communication resources 2130 may include interconnect or network interface controls, components, or other suitable devices for communicating with one or more peripheral devices 2104 or one or more databases 2106 or other network elements over a network 2108. For example, communication resources 2130 may include wired communication components (e.g., for coupling via USB, Ethernet, etc.), cellular communication components, NFC components, Bluetooth® (e.g., Bluetooth® Low Energy) components, WiFi® components, and contain other communication components.

Instructions 2150 may include software, a program, application, applet, app, or other executable code to cause at least any one of processors 2110 to perform one or more of the methodologies discussed herein. Instructions 2150 may reside in whole or in part within at least one of processors 2110 (e.g., within the processor's cache memory), memory/storage devices 2120, or any suitable combination thereof. Furthermore, any portion of instructions 2150 may be transferred 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) or portions or implementations thereof may be the 19-21 or any other figure herein may be configured to perform one or more processes, techniques, or methods as described herein, or portions thereof. Such a process 2200 is in X - 1 shown. For example, the process 2200 may include, at 2202, determining downlink control information (DCI) that includes an indication of activation or deactivation of a rate adaptation resource for transmission on a downlink physical shared channel (PDSCH). The process 2200 further includes, at 2204, encoding a message including the DCI for transmission to a user equipment (UE).

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

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

The DCI can contain a variety of information. For example, in some embodiments, the DCI includes an indication of an activation of the rate adaptation resource configured at a bandwidth sharing (BWP) level. In some embodiments, the DCI shall further indicate that a subset of downlink physical control channel (PDCCH) monitoring opportunities is activated during PDSCH transmission. In some embodiments, the DCI shall further indicate a PDCCH monitoring pattern used within the PDSCH transmission. In some embodiments, the DCI shall further indicate a position of a PDCCH monitoring opportunity that is activated during the PDSCH transmission. In some embodiments, the DCI shall further indicate a subset of PDCCH monitoring opportunities that are activated during PDSCH transmission. In some embodiments, the DCI shall further indicate one or more groups of search space sets for PDCCH monitoring by the UE.

24 FIG. 2 illustrates another process 2400 according to various embodiments. The process 2400 may include, at 2402, encoding a first channel for transmission on a first carrier and a second channel for transmission on a second carrier according to carrier aggregation.

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

In some embodiments, the process 2400 may be performed by a UE or a portion thereof. The indication of the timing difference can be used by the UE and/or the gNB to determine whether the first and second channels overlap. If the first and second channels are determined to 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, then uplink control information associated with the first and second channels may be transmitted separately.

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

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

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

In some embodiments, the process 2500 may be performed by a gNB or a portion thereof. The indication of the timing difference can be used by the UE and/or the gNB to determine whether the first and second channels overlap. If the first and second channels are determined to 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, then uplink control information associated with the first and second channels may be transmitted separately.

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

EXAMPLES

• Konfigurieren, durch eine NodeB der nächsten Generation (gNB), von Ratenanpassungsressourcen für einen physischen gemeinsam genutzten Downlink-Kanal (PDSCH) in einem Zeitbereich; und
• Aktivieren, durch die gNB, eines Teilsatzes der konfigurierten Ratenanpassungsressourcen über Downlink-Steuerinformationen (DCI).

Example 1 may include a method of wireless communication for a fifth generation (5G) or new radio (NR) system, the method comprising:

• configuring, by a next generation NodeB (gNB), rate adaptation resources for a downlink physical shared channel (PDSCH) in a time domain; and
• Activate, by the gNB, a subset of the configured rate adaptation resources via downlink control information (DCI).

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

Example 3 may include the method of Example 2 or any other example herein, wherein when the rate adaptation resource is configured as a cell level, the entire resource in the system bandwidth is used for PDSCH rate adaptation; wherein when the rate adaptation resource is configured as a Bandwidth Share (BWP) level, if enabled or configured, the entire resource in BWP is used for PDSCH rate adaptation.

Example 4 may include the method of Example 1 or another example herein, where when the control resource set (CORESET) is configured as a rate adjustment resource, only the CORESET resource is needed in the time domain for the rate adjustment resource.

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

Example 6 may include the method of example 1 or another example herein, where a field in the DCI for scheduling the PDSCH may be used to indicate that a subset of PDCCH monitoring opportunities is activated during the PDSCH transmission period.

Example 7 may include the method of example 1 or another example herein, wherein a set of a PDCCH monitoring opportunity pattern within a PDSCH transmission period may be configured by higher layers, wherein a field in the DCI for scheduling the PDSCH may be used to indicate which PDCCH monitoring opportunity pattern is used within the PDSCH transmission period, and the UE shall perform PDSCH rate adaptation around CORESET or the detected PDCCH on the activated PDCCH monitoring opportunity.

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

Example 9 may include the method of example 1 or another example herein, wherein a subset of PDCCH monitoring opportunities activated during the PDSCH transmission duration is predefined or configured by high layer signalling.

Example 10 may include the method of example 1 or any other example herein, wherein more than one set of search space sets may be configured for PDCCH monitoring; wherein if two groups of search space sets are configured for PDCCH monitoring, if the PDCCH is detected in a first group of search space sets, the UE shall switch from the first group of search space sets to the second group of search space sets.

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

Example 12 may include the method of Example 1 or any other example herein, wherein within a PDSCH transmission one or more Code Blocks (CB) or Code Block Groups (CBG) or a PDSCH may be replaced with a PDCCH carrying DCI.

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

Example 14 may include the method of example 1 or another example herein, wherein when a PDSCH transmission including one or more CB/one or more CBGs with an activated rate adaptation resource, e.g. B. CORESET or an activated PDCCH monitoring opportunity or an SSB block, the CB/the CBG or the PDSCH is not transmitted on the activated rate adaptation resource.

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

Example 16 may include the method of Example 14 or any other example herein, wherein the TBS on the affected CB/CBGs or PDSCHs when they collide with activated rate matching resources according to an actual number of symbols or resources other than the activated rate matching resources or the actual resource allocation can be determined.

Example 17 may include the method of example 1 or another example herein, wherein when a PDSCH transmission including one or more CB/one or more CBGs with an activated rate adaptation resource, e.g. B. CORESET or a disabled PDCCH monitoring opportunity or an SSB block, CB/CBG or the PDSCH is not transmitted on the enabled rate adaptation resource; where the affected CB/CBG or PDSCH continues to be transmitted after the activated rate adaptation resource and spanning the number of symbols as specified in the DCI.

Example 18 may include the method of Example 1 or another example herein, wherein the PDSCH assignment is based first on the start and length indicator value (SLIV) specified in the DCI and the configured rate adaptation resource within the PDSCH transmission duration; wherein if a CB/CBG or PDSCH collides with a configured rate matching resource, the CB/CBG or PDSCH is further mapped after the configured rate matching resource and spans the specified number of symbols across SLIV.

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

Example 20 may include the method of Example 1 or any other example herein, wherein when other DL channels or signals, including PDCCH, channel state information reference signal (CSI-RS), phase tracking reference signal (PT-RS), etc., with the symbols overlap containing the SSB transmission, the UE assumes that the OFDM symbols containing the SSB transmission are unavailable for another DL channel transmission.

Example 21 may include the method of Example 1 or any other example herein, with an indication of whether the PDSCH may be carried on a symbol alongside symbols for CORESET/PDCCH or SSB transmission with one or more SSB indices, can be configured by higher layers via RRC signalling.

Example 22 may include the method of example 1 or another example herein, where whether the PDSCH can be transmitted on a symbol adjacent to the symbols for CORESET/PDCCH or SSB can be inferred by the TCI state for the PDSCH.

• Bestimmen von Downlink-Steuerinformationen (DCI), die eine Angabe einer Aktivierung oder Deaktivierung einer Ratenanpassungsressource für eine Übertragung auf einem physischen gemeinsam genutzten Downlink-Kanal (PDSCH) beinhalten; und
• Codieren einer Nachricht, die die DCI beinhaltet, zur Übertragung an ein Benutzergerät (UE).

Example 23 includes a method that includes:

• determining downlink control information (DCI) including an indication of activation or deactivation of a rate adaptation resource for transmission on a downlink physical shared channel (PDSCH); and
• Encoding a message containing the DCI for transmission to a user equipment (UE).

Example 24 includes the method of example 23 or any other example herein where the rate adaptation resource is time domain configured.

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

Example 26 includes the method of example 25 or another example herein, wherein the DCI includes an indication of activation of the rate adaptation resource configured at a bandwidth sharing (BWP) level.

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

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

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

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

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

Example 32 includes the method of Example 23 or any other example herein, wherein the DCIs are to further indicate a location of a PDCCH monitoring opportunity that is activated during PDSCH transmission.

Example 33 includes the method of Example 23 or any other example herein, wherein the DCI shall further indicate a subset of PDCCH monitoring opportunities that are activated during PDSCH transmission.

Example 34 includes the method of example 23 or any other example herein, wherein the DCI are further configured to specify 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 any other example herein, wherein the method is performed by a Next Generation NodeB (gNB) or portion thereof.

• Empfangen einer Downlink-Steuerinformationen(DCI)-Nachricht, die eine Angabe einer Aktivierung oder Deaktivierung einer Ratenanpassungsressource für eine Übertragung auf einem physischen gemeinsam genutzten Downlink-Kanal (PDSCH) beinhalten; und
• Überwachen auf eine Übertragung auf einem physischen Downlink-Steuerkanal (PDCCH) während der PDSCH-Übertragung basierend auf der DCI-Nachricht.

Example 36 includes a method that includes:

• receiving a downlink control information (DCI) message including an indication of activation or deactivation of a rate adaptation resource for transmission on a downlink physical shared channel (PDSCH); and
• Monitoring for downlink physical control channel (PDCCH) transmission during PDSCH transmission based on the DCI message.

Example 37 includes the method of example 36 or another example herein, further comprising determining that one or more orthogonal frequency division multiplex (OFDM) symbols of a synchronization signal block (SSB) transmission are unavailable for the PDSCH transmission based on a Overlap between PDSCH resource allocation and SSB transmission.

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

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

Example 40 includes the method of any of Examples 36-39 or any other example herein, the method being performed by a user equipment (UE) or 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 another example herein, where the UE reports the actual transmission timing difference d between the two TAGs or two carriers to the gNB.

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

Example 44 may include the method of example 42 or any other example herein, where the timing difference is reported periodically or triggered by an event.

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

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

Example 47 may include the method of example 42 or another example herein, where the UE and the gNB determine whether two UL channels on the two UL carriers are aligning based on the logical timings of the two UL channels and the reported timing difference d overlap or not

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

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

Example 50 may include the method of example 41 or another example herein, where whether or not 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 any other example herein, using a single DL time reference to derive UL transmission timings for the multiple TAGs.

Example 52 may include the method of example 41 or another example herein, where whether or not multiple UL channels overlap is checked by the logical timing of the two UL carriers with a greater granularity.

Example 53 may include the method of Examples 42-52 or any other example herein, where for a PUSCH scheduled by a UL grant, the UL grant indicates whether/which UL control channel(s) is (are) multiplexed on the PUSCH.

• Codieren eines ersten Kanals zur Übertragung auf einem ersten Träger und eines zweiten Kanals zur Übertragung auf einem zweiten Träger gemäß Trägeraggregation; und
• Codieren, zur Übertragung, einer Angabe einer Timingdifferenz der Übertragung auf dem ersten Träger und dem zweiten Träger.

Example 54 may include a method comprising:

• encoding a first channel for transmission on a first carrier and a second channel for transmission on a second carrier according to carrier aggregation; and
• encoding, for transmission, an indication of a timing difference of transmission on the first carrier and the second carrier.

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

Example 56 may include the method of example 54-55 or any other example herein, where the timing difference indication is an absolute time value.

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

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

Example 59 may include the method of example 54-58 or any other example herein, further comprising determining a trigger events, with the timing difference indication being transmitted based on the determination.

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

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

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

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

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

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

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

Example 67 may include the method of examples 62-66 or any other example herein, wherein if it is determined that the first and second channels do not overlap, uplink control information associated with the first and second channels separately be transmitted.

Example 68 may include the method of examples 54-67 or any 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 any other example herein, wherein the first channel is scheduled by an uplink grant, and wherein the uplink grant indicates whether and/or which control channels are multiplexed on the first channel.

Example 70 may include the method of Examples 54-69 or any other example herein, wherein the first and/or second carrier has a frequency greater than 52.6 gigahertz (GHz).

Example 71 may include the method of Examples 54-70 or any other example herein, the method being performed by a UE or portion thereof.

• Empfangen eines ersten Kanals von einem UE auf einem ersten Träger und eines zweiten Kanals von dem UE auf einem zweiten Träger gemäß Trägeraggregation; und
• Empfangen, von dem UE, einer Angabe einer Übertragungstimingdifferenz der Übertragung auf dem ersten Träger und dem zweiten Träger.

Example 72 may include a method comprising:

• receiving a first channel from a UE on a first carrier and a second channel from the UE on a second carrier according to carrier aggregation; and
• receiving, from the UE, an indication of a transmission timing difference of the transmission on the first carrier and the second carrier.

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

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

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

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

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

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

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

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

Example 80 may include the method of example 72-79 or another example 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 another example herein, wherein the determination of whether the first channel and the second channel overlap is further based on respective logical timings of the first channel and the second channel.

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

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

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

Example 85 may include the method of example 80-84 or another example herein, further comprising determining that uplink control information associated with the first and second channels based on a determination that the first and second channels do not overlap be transferred separately.

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

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

Example 88 may include the method of Examples 72-87 or any other example herein, wherein the first and/or second carrier has a frequency greater than 52.6 gigahertz (GHz).

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

Example 90 may include apparatus having 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 , includes.

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

Example 92 may include apparatus comprising logic, modules, or circuitry 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 that/ described herein.

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

Example 94 may include an apparatus comprising: one or more processors; and one or more computer-readable media comprising instructions that, when executed by the one or more processors, the one or more processors for performing the method, the Techniques or the process as described in or related to any of Examples 1-89, or parts thereof.

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

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

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

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

Example 99 may include an electromagnetic signal carrying computer-readable instructions, execution of the computer-readable instructions by one or more processors to cause the one or more processors to perform the method, technique, or process as set forth in any of Examples 1- 89 described or related thereto, or perform parts thereof.

Example 100 may include a computer program comprising instructions, wherein execution of the program is to cause a processing element to perform the method, technique, or process described in or related to any of Examples 1-89, or execute parts of it.

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

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

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

Example 104 may include an apparatus for providing wireless communication as shown and described herein.

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

abbreviations

Unless otherwise used herein, terms, definitions and abbreviations may be consistent 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

Confirmation

AF

application function

AT THE

Confirmed mode AMBRA aggregated maximum bit rate

AMF

Access and mobility management function

AT

access network

NO

Automatic neighbor relationship

AP

Application protocol, antenna port, access point

API

application programming interface

APN

access point name

ARP

Allocation and Hold Priority

ARQ

Automatic retry request

AS

access stratum

ASN.1

Abstract Syntax Notation One

EXEC

authentication server function

AWGN

Additive white Gaussian noise

BAP

Backhaul Adjustment Protocol

BCH

broadcast channel

BER

Bit Error Ratio

BFD

beam failure detection

BLER

block error rate

BPSK

Binary phase shift keying

BRASS

Broadband remote access server

BSS

business support system

B.S

base station

BSR

Buffer Status Report

BW

bandwidth

BWP

bandwidth part

C-RNTI

Temporary cellular network identity

APPROX

Carrier aggregation, certification authority

CAPEX

capital expenditure

CBRA

Competitive Random Access

CC

Component carrier, country code, cryptographic checksum

CCA

Free Channel Rating

CCE

control channel element

CCCH

common control channel

CE

coverage improvement

CDM

content delivery network

CDMA

code division multiple access

CFRA

Non-competitive random access

cg

cell group

CI

cell identity

CID

Cell ID (e.g. positioning method)

CIM

Common information model

CIR

Carrier to Disturbance Ratio

CK

cipher key

CM

Connection management, conditionally mandatory

CMAS

Commercial mobile alert service

CMD

command

CMS

cloud management system

CO

Conditionally optional

CoMP

Coordinated multipoint CORESET control resource set

COTS

Ordinary commercial standard

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 status information

CSI IM

CSI noise measurement

CSI RS

CSI reference signal

CSI RSRP

CSI reference signal received power

CSI RSRQ

CSI reference signal reception quality

CSI SINR

CSI signal-to-noise-to-interference ratio

CSMA

Carrier Capture Multiple Access

CSMA/CA CSMA

with collision avoidance

CSS

Common search space, cell-specific search space

CTS

readiness to send

cw

code word

CWS

Competition window size

D2D

device-to-device

DC

Dual connectivity, DC

DCI

Downlink Control Information

DF

Use Flavor

DL

downlink

DMTF

Distributed Management Working Group

DPDK

Data plane development kit

DM RS,

DMRS demodulation reference signal

DN

data network

DRB

data carrier

DRS

Discovery reference signal

DRX

Discontinuous reception

broadband

Domain Specific Language Digital Subscriber Line

DSLAM

DSL access multiplexer

DwPTS

Downlink pilot time slot E-LANEthernet local area network

E2E

end-to-end

ECCA

Enhanced Free Channel Rating, Enhanced CCA

ECCE

Improved control channel element, improved CCE

ED

energy detection

EDGE

Improved data rates for GSM Evolution (GSM Evolution)

EGMF

Release Rules Management Function

EGPRS

improved

GPRS EIR

Equipment Identity Register

eLAA

Enhanced Licensed Assisted Access, Enhanced LAA

EM

element manager

eMBB

advanced mobile broadband

EMS

elements management system

eNB

Evolved NodeB, E-UTRAN NodeB

EN-DC

E-UTRA NR dual connectivity

EPC

Developed package core

EPDCCH

extended

PDCCH

extended downlink physical control channel

EPRE

Energy per resource element

EPS

Developed package system

EREG

Extended REG, extended resource element groups

ETSI

European Telecommunications Standards Institute

SOMETHING

Earthquake and tsunami warning system

eUICC

embedded

UICC,

embedded general purpose integrated circuit card

E-UTRA

evolved

UTRA E-UTRAN

evolved

UTRAN EV2X

Extended V2X

F1AP

F1 application log

F1-C

F1 control plane interface

F1-U

F1 user level interface

FACCH

Fast associated control channel

FACCH/F

Fast Associated Control Channel/Full Rate

FACCH/H

Fast Associated Control Channel/Half Rate

ACADEMIC SUBJECT

Forward Access Channel

FAUCH

Fast uplink signaling channel

FB

function block

FBI

feedback information

FCC

Federal Communications Commission

FCCH

frequency correction channel

FDD

frequency duplex

FDM

frequency division multiplex

FDMA

Frequency division multiple access

FE

front end

FEC

forward error correction

FFS

for further investigation

FFT

Fast Fourier Transform

feLAA

further enhanced licensed assisted access, further enhanced LAA

FN

frame number

FPGA

field programmable gate array

FR

frequency range

G-RNTI

Temporary GERAN radio network identity

GERAN GSM EDGE RAN, GSM EDGE

radio access network

GGSN

Gateway GPRS support node GLONASS

GLObal'naya

NAvigatsionnaya Sputnikovaya Sistema (Engl.: Global Navigation Satellite System)

gNB

Next-gen NodeB

gNB CU

gNB central processing unit, next-generation NodeB central processing unit

gNB-DU

distributed gNB unit, next generation distributed NodeB unit

GNSS

Global Navigation Satellite System

GPRS

General packet radio service

GSM

Global system for mobile communications, Groupe Special Mobile

GTP

GPRS tunnel protocol

GTP UGPRS

User-level tunneling protocol

GTS

Go To Sleep Signal (related to WUS) GUMMEI Globally unique MME identifier

GOOD

Globally unique temporary UE identity HARQ hybrid ARQ, hybrid automatic repeat request

HANDO

handover

HFN

HyperFrame number

HO

Hard handover

HLR

home location register

HN

home network

HO

handover

HPLMN

Public terrestrial mobile network

HSDPA

High speed downlink packet access

HSN

jump sequence number

HSPA

High Speed Packet Access

HSS

Home Subscriber Server

HSUPA

High speed uplink packet access

HTTP

Hypertext Transfer Protocol

HTTPS

Hypertext Transfer Protocol Secure (https is http/1.1 over SSL, i.e. port 443)

I block

information block

ICCID

Integrated circuit card identification

IAB

Integrated access and backhaul

ICIC

Inter-Cell Disorder 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 item identifier

IEIDL

Information elements identification data length

IETF

Internet Engineering Task Force

IF

infrastructure

IN THE

Interference measurement, intermodulation, IP multimedia

IMC

IMS Credentials

IMEI

International Mobile Identity

IMGI

International mobile group identity

IMPI

Private IP multimedia identity

IMPU

Public IP multimedia identity

IMs

IP multimedia subsystem

IMSI

International mobile subscriber identity

Internet of Things

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

Synchronous

IRP

integration reference point

ISDN

Digital network for integrated services

ISIM

IM service identity module

ISO

International Organization for Standardization

ISP

internet service provider

IMF

interworking function

I-WLAN

interworking

WIRELESS INTERNET ACCESS

Convolutional code constraint length, unique USIM key

kB

kilobytes (1000 bytes)

kbps

kilobits per second

Kc

encryption key

Ki

Individual subscriber authentication key

KPI

key performance indicator

KQI

key quality indicator

ASI

key set identifier

ksps

Kilo symbols per second

KVM

Virtual kernel machine

L1

Layer 1 (physical layer) L1-RSRP Layer 1 reference signal reception power

L2

Layer 2 (data link layer)

L3

Layer 3 (network layer)

LAA

Licensed Assisted Access

LAN

local network

LBT

Listen Before Talk

LCM

life cycle management

LCR

low chip rate

LCS

location services

LCID

Logic Channel ID

LI

shift indicator

LLC

Logic link control, low layer compatibility

LPLMN

local

PLMN LPP LTE

positioning log

LSB

Least Significant Bit

LTE

Long Term Evolution

LWA

LTE WiFi Aggregation

LWIP

LTE/WLAN radio level integration with IPsec tunnel

LTE

Long Term Evolution

M2M

machine-to-machine

MAC

Media Access Control(Protocol Layer Context)

MAC

Message authentication code (security/encryption context)

MAC-A

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

MAC IMAC

on data integrity of signaling messages (context TSG T WG3)

MANO

management and orchestration

MBMS

Multimedia broadcast and multicast service

MBSFN

Multimedia broadcast multicast service single frequency network

MCC

Cellular Country Code

MCG

Master cell group MCOT Maximum channel occupation time

MCS

Modulation and Coding Scheme

MDAF

Management data analysis function

MDAs

Management Data Analysis Service

MDT

Drive test minimization

ME

mobile device

MeNB

Master eNB

MER

message error ratio

MGL

measurement gap length

MRP

Measurement gap repeat 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

MON

Measurement object, mobile origin

MPBCH

Physical MTC broadcast channel

MPDCCH

MTC downlink physical control channel

MPDSCH

Physical MTC downlink shared channel

MPRACH

Physical MTC random access channel

MPUSCH

Physical shared MTC uplink channel

MPLS

Multi-protocol label switching

MS

mobile station

MSB

Most Significant Bit

MSC

mobile exchange

MSI

Minimum system information, MCH planning information

MSID

mobile station identifier

MSIN

mobile station identification number

MSISDN

Mobile subscriber ISDN number

MT

Mobile completed, mobile completed

MTC

Machine type communication mMTCMassive MTC, massive machine type communication

MU-MIMO

Multi-user MIMO

MWUS

MTC wake-up signal, MTC-WUS NACK Negative acknowledgment

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 Discovery

NE-DC

NR-E-UTRA dual connectivity

NEF

Network Discovery Feature

NF

network function

NFP

network forwarding path

NFPD

Network forwarding path descriptor

NFV

Network Function 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

Physical narrowband broadcast

channel

NPDCCH Physical Narrowband Downlink Control Channel

NPDSCH

Narrowband downlink physical shared channel

NPRACH

Narrowband physical random access channel

NPUSCH

Narrowband physical shared uplink channel

NPSS

Narrowband primary synchronization signal

NSSS

Narrowband secondary synchronization signal

NO

New radio, neighborhood relationship

NRF

NF repository function

NRS

narrowband reference signal

NS

network service

NSA

Non-standalone mode of operation

NSD

network service descriptor

NSR

Network Service Recording

NSSAI

Network Slice Selection Assist Information

S-NSSAI

Individual NSSAI

NSSF

Network slice selection function

NW

network

WUS

NWUS narrowband wake-up signal, narrowband

NZP

non-zero performance

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 operational costs

OSI

Other system information

OSS

operational support system

OTA

Over the Air

PAPR

Peak-to-average power ratio

PAR

Peak to Average Ratio

PBCH

Physical broadcast channel

personal computer

Power Control, Personal Computer

PCC

Primary component carrier, primary CC

PCell

primary cell

PCI

Physical Cell ID, Physical Cell Identity

PCEF

Policy and billing enforcement capability

PCF

policy control function

PCRF

Policy control and billing rules feature

PDCP

Packet data convergence protocol, packet data convergence protocol layer

PDCCH

Downlink physical control channel

PDCP

packet data convergence protocol

PDN

Packet data network, public data network

PDSCH

Downlink physical shared channel

PDU

log 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 terrestrial mobile network

pin code

Personal identification number

p.m

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

hp

parcel 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 landline

PT RS

phase tracking reference signal

PTT

Push to talk

PUCCH

Uplink physical control channel

PUSH

Physical shared uplink channel

QAM

quadrature amplitude modulation

QCI

QoS class of identifier

QCL

quasi-colocalization

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

RAB

Radio access bearer, random access burst

RACH

random access channel

RADIUS

Remote Authentication Dial-In User Service

RAN

radio access network

EDGE

Random number (used for authentication)

RARE

random access response

ADVICE

radio access technology

ROUGH

Routing area update

RB

Resource block, radio bearer

RBG

resource block group

REG

resource item group

rel

Release

REQ

Requirement

RF

high frequency

RI

rank indicator

RIV

Resource indicator value

RL

wireless link

RLC

Radio link control, radio link control layer

RLC AM

RLC Confirmed 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 minimum system information

RN

relay node

RNC

wireless network control

RNL

wireless network layer

RNTI

Temporary wireless network 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 reception quality

RSSI

Received signal strength indicator

RSU

roadside unit

RSTD

reference signal time difference

RTP

real-time log

RTS

readiness to send

RTT

orbital period

Rx

Receiving, receiving, receiver

S1AP

S1 application protocol

S1 MME

S1 for the control plane

S1-U

S1 for the user level

S-GW

Serving gateway

S-RNTI

Temporary SRNC radio network identity

S-TMSI

Temporary SAE mobile station identifier

SA

Stand alone mode of operation

SAE

System architecture development

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

Additional downlink

SDNF

Network function with structured data storage

SDP

Session Description Protocol

SDSF

Function for structured data storage

SDU

service data unit

SEAF

safety anchor function

SeNB

Secondary eNB

SEPP

Security Edge Protection Proxy

SFI

slot format specification

SFTD

Spatial 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

S.I

system information

SI RNTI

System Information RNTI

SIB

system information block

SIM

subscriber identity module

SIP

Session-Initiated Protocol

SIP

System in Package

SL

side link

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

SUN

self-organizing of the network

SpCell

special cell

SP-CSI-RNTI

Semi-persistent CSI RNTI

SPS

Semi-persistent scheduling

SQN

sequence number

SR

planning requirement

SRB

signaling radio bearer

SRS

probing reference signal

ss

synchronization signal

SSB

SS block SSBRI SSB resource indicator

SSC

Session and Service Continuity

SS RSRP

Synchronization signal-based reference signal reception power

SS RSRQ

Synchronization signal-based reference signal reception quality

SS SINR

Synchronization signal-based signal-to-noise-and-interference ratio

SSS

secondary synchronization signal

SSSG

search space set group

SSIF

search space set indicator

SST

Slice/Service Types

SU MIMO

Single-user MIMO

SUL

additional uplink

TA

Timing advance, tracking range

TAC

tracking area code

DAY

Timing Advance Group

DEW

tracking area update

TB

transport block

TBS

transport block size

TBD

Still to define

TCI

Transmission configuration indicator

TCP

transmission communication protocol

TDD

time duplex

TDM

time division

TDMA

Time Division Multiple Access

TE

end device

TEID

tunnel endpoint identifier

TFT

Traffic Flow Template

TMSI

Temporary Mobile Subscriber Identity

TNL

network transport layer

TPC

transmission 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

Temporary

UTRAN

wireless network identity

UART

Universal asynchronous receiver and transmitter

UCI

Uplink Control Information

UE

user device

UDM

Uniform data management

UDP

User Datagram Log

UDR

Unified data repository

UDSF

Network function for unstructured data storage

UICC

Universal integrated circuit card

UL

uplink

AROUND

Unconfirmed mode

UML

Uniform modeling language

UMTS

Universal mobile telecommunications system

UP

user level

UPF

user level function

URI

Uniform resource identifier

URL

Unified resource locator

URLLC

Ultra reliable and low latency

USB

Universal serial bus

USIM

Universal Subscriber Identity Module

USS

UE specific search space

UTRA

terrestrial

UTRA

radio access

UTRAN

Universal terrestrial radio access network

UwPTS

Uplink pilot time slot

V2I

vehicle-to-infrastructure

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

VNFM manager

VOIP

Voice over IP, Voice over Internet Protocol

VPLMN

Visited public terrestrial mobile network

VPN

Virtual Private Network

VRB

Virtual resource block

WiMAX

Worldwide Interoperability for Microwave Access

WLANID

wireless local area network

WMAN

Wireless urban network

WPAND

wireless personal network

X2-C

X2 control plane

X2-U

X2 user level

XML

Extensible Markup Language

XRES

Expected User Response

XOR

Exclusive OR

ZC

Zadoff-Chu

ZP

zero power

terminology

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

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

The term "processor circuitry" as used herein refers to, is a part of, or includes circuitry that is capable of sequentially and automatically performing a sequence of arithmetic or logical operations or recording, storing, and/or transmitting digital data . The 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" may refer to one or more application processors, one or more baseband processors, a physical central processing unit (CPU), a single-core processor, a dual-core processor, a three-core processor, a quad-core processor, and/or any other device capable of doing so is to execute or otherwise operate computer-executable instructions, such as program code, software modules and/or functional processes. The processing circuitry may include other hardware accelerators, which may be microprocessors, programmable processing devices, or the like. The one or more hardware accelerators may include, for example, computer vision (CV) and/or deep learning (DL) accelerators. The terms "application circuitry" and/or "baseband circuitry" may be considered synonymous with "processor circuitry" and may be referred to as such.

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

The term "user equipment" or "UE" as used herein refers to a device with radio communication capabilities and may describe a remote user of network resources on a communication network. The term "user equipment" or "UE" can be used as a synonym for client, handset, mobile device, mobile terminal, user equipment, mobile unit, mobile station, mobile user, subscriber, user, remote station, access agent, user agent, receiver, radio, reconfigurable radio, reconfigurable mobile device, etc. be considered and identified as such. Furthermore, the term "user equipment" or "UE" may include any type of wireless/wired device or any computing device with a wireless communication interface.

The term "network element" as used herein refers to a physical or virtualized device and/or physical or virtualized infrastructure used to provide wired or wireless communication network services. The term "network element" can be used as a synonym for a networked computer, networking hardware, network device, network node, router, switch, hub, bridge, radio network controller, RAN device, RAN node, gateway, server, virtualized VNF , an NFVI and/or the like and/or designated as such.

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

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

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 particular device, such as computing devices, mechanical devices, storage space, processor /CPU time, processor/CPU usage, processor and accelerator loads, hardware time or usage, electrical power, input/output operations, ports or network sockets, channel/link allocation, throughput, memory usage, storage, network , database and applications, workload units and/or the like. A "hardware resource" may refer to compute, storage, and/or network resources provided by one or more physical hardware elements. A "virtualized resource" may refer to compute, storage, and/or network resources provided by virtualization infrastructure for an application, device, system, etc. The term "network resource" or "communications resource" may refer to resources that computing devices/systems can access over a communications network. The term "system resources" may refer to any type of shared entity to provide services and may include computing and/or network resources. System resources can be viewed as a set of coherent functions, network data objects, or services accessible by a server, where such system resources reside on a single host or multiple hosts and are uniquely identifiable.

The term "channel" as used herein refers to any tangible or intangible transmission medium used to communicate data or a data stream. The term "channel" may be synonymous with and/or equivalent to "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 denoting a path or medium over which data is communicated. Also, as used herein, the term "link" refers to a connection between two devices via a RAT for the purpose of transmitting and receiving information.

The terms "instantiate," "instantiation," and the like, as used herein, refer to the creation of an instance. An "instance" also refers to a concrete occurrence of an object that can occur, for example, during the execution of program code.

The terms "coupled," "communicatively coupled," along with derivatives thereof, are used herein. The term "coupled" can mean that two or more elements are in direct physical or electrical contact with each other, that two or more elements contact each other indirectly but still co-operate or interact with each other, and/or can mean that one or more others Elements interposed, coupled, or connected between elements that are deemed to be coupled together. The term "directly coupled" can mean that two or more elements are in direct contact with each other. The term "communicatively coupled" may mean that two or more elements may be in contact with one another through a means of communication, including a wire or other interconnect, a wireless communication channel or link, and/or the like.

The term "information element" refers to a structural element that contains one or more contains fields. The term "field" refers to individual contents of an information element or a data element that contains content.

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

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

The term "a primary cell" refers to the MCG cell operating on a primary frequency in which a UE either performs the initial connection establishment procedure or initiates the connection re-establishment procedure.

The term "primary SCG cell" refers to the SCG cell in which the UE performs random access when performing reconfiguration with the sync procedure for DC operation.

The term "secondary cell" refers to a cell that provides additional radio resources on a special cell for a UE configured with CA.

The term "secondary cell group" refers to a subset of serving cells that includes the PSCell and zero or more secondary cells for a UE configured with DC.

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

The term "secondary cell" or "secondary cell group" refers to a set of cells that includes the special cell(s) and all secondary cells for a UE in RRC _- CONNECTED configured with CA.

The term "special cell" refers to the MCG's PCell or the SCG's PSCell for DC operation; otherwise, the term "special cell" refers to the PCell.

QUOTES INCLUDED IN DESCRIPTION

This list of documents cited by the applicant was generated automatically and is included solely for the better information of the reader. The list is not part of the German patent or utility model application. The DPMA assumes no liability for any errors or omissions.

Patent Literature Cited

• CN2020103765 [0001]
• US63055519 [0001]
• US63079025 [0001]

Claims (25)

One or more non-transitory computer-readable media (NTCRM) having instructions stored thereon that, when executed by one or more processors, cause a user equipment (UE) to: encoding a first message for transmission on a first carrier and a second message for transmission on a second carrier according to carrier aggregation; and Encoding, for transmission to a Next Generation NodeB (gNB), an indication of a timing difference of the transmissions on the first carrier and the second carrier. One or more NTCRM after 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), the indication of the timing difference being the transmission timing difference between the first TAG and the second DAY indicates. One or more NTCRM after one of Claims 1 - 2 , where the timing difference indication is quantized using a granularity of a symbol length or a fraction of a symbol length with respect to a reference subcarrier spacing (SCS). One or more NTCRM after one of Claims 1 - 3 , whereby the indication of the timing difference is transmitted periodically or based on the occurrence of a triggering event. One or more NTCRM after claim 4 , where the triggering event is a request received from the gNB. One or more NTCRM after one of Claims 1 - 5 , where the indication of the timing difference is transmitted in a measurement report, a media access control (MAC) control element, an uplink physical shared channel (PUSCH) or an uplink physical control channel (PUCCH). One or more NTCRM after one of Claims 1 - 6 wherein the instructions, when executed, are to further cause the UE to determine whether the first message and the second message overlap based on whether logical timings of the first and second messages adjusted for the timing difference have at least one overlapping symbol exhibit. One or more NTCRM after claim 7 wherein if the first and second messages are determined to overlap, the instructions, when executed, further cause the UE to multiplex or drop uplink control information associated with at least one of the first and second messages . One or more non-transitory computer-readable media (NTCRM) having instructions stored thereon that, when executed by one or more processors, cause a next-generation NodeB (gNB) to: receiving 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; receiving, from the UE, an indication of a transmission timing difference of the transmissions on the first carrier and the second carrier; and Process the first and second channels based on the specified transmission timing difference. One or more NTCRM after 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), the indication of the transmission timing difference being the transmission timing difference between the first TAG and the second DAY indicates. One or more NTCRM after one of claims 9 - 10 , wherein the indication of the transmission timing difference is quantized using a granularity of a symbol length or a fraction of a symbol length with respect to a reference subcarrier spacing (SCS). One or more NTCRM after one of claims 9 - 11 , wherein the indication of the transmission timing difference is periodically received from the UE. One or more NTCRM after one of claims 9 - 12 wherein the instructions, when executed, are further to cause the gNB to encode, for transmission to the UE, a request for the transmission timing difference, wherein the indication of the transmission timing advance is received based on the request. One or more NTCRM after one of claims 9 - 13 wherein the indication of the transmission timing difference is received in a measurement report, a media access control (MAC) control element, an uplink physical shared channel (PUSCH), or an uplink physical control channel (PUCCH). One or more NTCRM after one of claims 9 - 14 , with the instructions if they are to be carried out, further to cause the gNB to determine whether the first channel and the second channel overlap based on whether logical timings of the first and second messages adjusted by the transmission timing difference have at least one overlapping symbol, with uplink control information associated with the first and/or second channel are multiplexed or dropped based on a determination that the first and second channels overlap. One or more NTCRM after one of claims 9 - 15 wherein the instructions, when executed, are further to cause the gNB to schedule transmission of the first channel through an uplink grant, the uplink grant indicating that control channels are multiplexed on the first channel. One or more non-transitory computer-readable media (NTCRM) having instructions stored thereon that, when executed by one or more processors, cause a user equipment (UE) to: receiving downlink control information (DCI) including an indication of activation or deactivation of a rate adaptation resource for transmission on a downlink physical shared channel (PDSCH); and Monitor for downlink physical control channel (PDCCH) transmission during PDSCH transmission based on the indication. One or more NTCRM after Claim 17 wherein the instructions, when executed, are to further cause the UE to determine that one or more orthogonal frequency division multiplex (OFDM) symbols of a synchronization signal block (SSB) transmission are unavailable for the PDSCH transmission, based on an overlap between a PDSCH resource allocation and the S SB transmission. One or more NTCRM after one of claims 17 - 18 , where the rate adaptation resource is time-domain configured. One or more NTCRM after one of claims 17 - 19 , wherein the rate adaptation resource is configured per cell or per bandwidth share (BWP). One or more NTCRM after one of claims 17 - 20 , wherein the rate adaptation resource is determined based on a control resource set (CORESET) or an SSB. One or more NTCRM after Claim 21 , wherein the instructions, when executed, shall further cause the UE to determine a gap for beam switching based on the CORESET or the SSB. One or more NTCRM after one of claims 17 - 22 , where the DCI shall indicate that a subset of PDCCH monitoring opportunities is activated during PDSCH transmission. One or more NTCRM after one of claims 17 - 23 , where the DCI shall further indicate a PDCCH monitoring pattern to be used within the PDSCH transmission. One or more NTCRM after one of claims 17 - 24 , wherein the DCI shall further indicate a position of a PDCCH monitoring opportunity activated during the PDSCH transmission.

Images