Tech-invite3GPPspaceIETFspace
21222324252627282931323334353637384‑5x

Content for  TR 38.844  Word version:  18.0.0

Top   Top   Up   Prev   Next
0…   6…   6.1.2…   6.1.2.2   6.1.2.3   6.1.2.4   6.1.3   6.2…   6.2.2…   6.2.3   6.3…   6.4…   6.5…   6.6…   6.7…   7…   A…

 

7  Conclusionp. 34

7.1  Comparison Between Different Schemesp. 34

This clause provides a comparison of the proposed schemes using different criteria.
The comparison between different schemes is summarized Table 7.1-1.
Comparison Criteria Overlapping CA (two cells) - described in clause 6.2.3 Combined UE CBW (One cell) - described in clause 6.2.2 Overlapping UE CBW - described in clause 6.2.1 Larger CBW (one cell) - described in clause 6.1
Regulatory requirementNo issueNo issueNo issuePotential issue on the BS side, gNB filters will be needed depending on BS implementation.
UE performance degradation relative to minimum requirementsPossible impact on Rx sensitivity vs regular CBW, if single carrier Tx-Rx separation is not maintained.Possible impact on Rx sensitivity vs regular CBW, if single carrier Tx-Rx separation is not maintained.No issueUE ACS and in-band blocking degradation.
Possible impact on Rx sensitivity vs regular CBW, if single carrier Tx-Rx separation is not maintained.
gNB complexitygNB has to support CA and schedule the data without collision in the two CC's overlapping PRBsgNB has to support splitting the signal into 2 RF carriers with a predefined phase relationship gNB has to support the irregular channel BW (can also be implemented through RF combining of 2 channels)No changes needed if the BS can meet regulatory requirements with the RF front end of the wider channel BW. Otherwise, gNB has to support the irregular channel BW
UE complexityUE has to support intra-band NC CA.
1 less CC can be supported when irregular BW is used in combination from other bands, or more total CCs needed.
UE has to support RF architecture as in intra-band NC CA.
Needs new capability to aggregate 2 RF channels in baseband.
Complexity higher than CA because the baseband will need a new "combiner" module.
1 less CC can be supported when irregular BW is used in combination from other bands, or more total CCs needed.
No changes needed, supported by legacy UEsNo changes needed, supported by legacy UE
UE throughputUEs supporting the feature can use the entire spectrum allocation, legacy UEs can use an already supported channel BWUEs supporting the feature can use the entire spectrum allocation, legacy UEs can use an already supported channel BWUE throughput based on existing channel BWs (5MHz for holdings <10MHz, 10MHz for holdings <15MHz, etc)UE throughput based on how many RBs can be used
Spectral utilizationChannel edge guardband based on the aggregated channel BW (5MHz for <10MHz, 10MHz for <15MHz, etc), 2 SSBs are neededChannel edge guardband based on the aggregated RF carrier BW (5MHz for <10MHz, 10MHz for <15MHz, etc), single SSB neededChannel edge guardband based on the actual holding (can be same as Overlapping CA), 2 SSBs are neededDepends on the usable number of RBs, single SSB needed
Cell Spectral utilizationEntire spectrum holding can be used even only with legacy UEsEntire spectrum holding can be used even only with legacy UEs for some scenarios depending on whether a single SSB can be used to configure legacy channels at both edges of the spectrum holding. Otherwise, entire spectrum can be used only by new UEs, all legacy UEs have to use the same regular channel BW part of the spectrum holding. Entire spectrum holding can be used even only with legacy UEsEntire spectrum holding, but with wider guard bands than in the other methods, can be used even only with legacy UEs
Network capacityEntire spectrum can be used by multiplexing different UEs(even legacy UEs)Entire spectrum can only be used for new UEs, whether legacy UEs can be multiplexed to cover entire channel depends on the configuration and bandwidthEntire spectrum can be used by multiplexing different UEs in the frequency domainEntire spectrum can be used by any UE
Legacy UE supportLegacy UEs supported, can use one of the aggregated CCsLegacy UEs can use part of the spectrum that contains the SSBLegacy UEs supportedLegacy UEs supported
RAN1/2/4 Specification impactRAN1/2 - new UE capabilities needed,
RAN4 - new band combinations, changes to channel spacing definition, Overlapping CA reqs applicability, new demod requirements for UEs
RAN2 - impact on new capability
RAN4 -core requirements equivalent to new channel BW for BS, new demod requirements for UEs
RAN4 - BS requirements for new channel BW RAN4 - BS requirements for new channel BW, possibly restrictions of the suitable scenarios.
New asymmetric bandwidth combinations for UE are needed. However these combinations would be "regular" BW combinations, so existing process.
Up

7.2  Study Item Conclusionsp. 36

The method of using a larger Channel BW than the licensed BW is based on blanking (not scheduling) PRBs within the larger BW but outside the irregular BW. If applied for the DL only, this method can be supported by specifying an asymmetric UE CHBW bandwidth configuration for band such that its UL CHBW is contained within the irregular UL block and the DL CHBW is larger than the irregular DL block. In this way UE unwanted emission requirement in the UL can be met by means of the regular UE CHBW. The larger DL UE CHBW implies a degraded UE adjacent channel selectivity and blocking performance when the interferer is close to the irregular DL block. However, the method can be supported by using existing UE architectures (since asymmetric bandwidths are supported by the current standard) in combination with new asymmetric CHBW combinations. The method works for both FDD and TDD.
Overlapping channels from the network perspective can be used to support irregular spectrum allocations. This method can provide the full network capacity improvement in DL and UL to a spectrum utilization ≥90 % of the irregular BW (at 15 kHz SCS). This method can be used with legacy UE, even Rel-15, not requiring any changes at the UE side. Since a UE is configured with standard channel bandwidth, there are no issues with UE performance degradation relative to minimum requirements and all the regulatory requirements can be met as per legacy operation. The ACS and the blocking performance are not affected, hence there will be no impact on the network planning. The gNB has to support the irregular channel BW because from the network perspective RBs are scheduled across the whole spectrum block. That might also require new BS requirements for new irregular channels. This method provides a fast, generic, safe, and efficient solution for FDD and TDD bands.
Up

Up   Top   ToC