RAN4 UE Capabilities and BCS Proposals for 3GPP TSG-RAN4 Meeting #96-e
Explore the discussions and proposals relating to UE capabilities and Bandwidth Configuration Sequences (BCS) in the context of 3GPP TSG-RAN4 Meeting #96-e. Issues like interpreting UE capabilities and creating new BCSs are addressed through various proposals to ensure smooth implementation and compatibility for T-Mobile USA.
Download Presentation
Please find below an Image/Link to download the presentation.
The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author. If you encounter any issues during the download, it is possible that the publisher has removed the file from their server.
You are allowed to download the files provided on this website for personal or commercial use, subject to the condition that they are used lawfully. All files are the property of their respective owners.
The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author.
E N D
Presentation Transcript
3GPP TSG-RAN4 Meeting #96-e Online, , 17th - 28th Aug 2020 R4-20xxxxx Way Forward on BCSs T-Mobile USA
Observations Observation 1: There has been some confusion in RAN2 about how to interpret the UE capabilities when there is a discrepancy, for instance if the UE does not support a channel bandwidth for a band that is included as a channel bandwidth in the BCS. Observation 2: If RAN4 needs to create a new BCS each time a new channel bandwidth is added to a legacy band, there will be a lot of work and the tables in the specs will grow significantly.
Clarifications related to Proposal 1 Channel BWs per band are either optional, mandatory or mandatory with capability signalling. This proposal does not change that. We believe that Proposal 1 is in line with the current understanding in RAN2, but it would be best to have formal agreement within RAN4 on how to interpret the reported UE capabilites. This may be seen as more of an observation than a proposal, but RAN 4 agreement on this point will help avoid any potential confusion
Proposals Proposal 1: RAN4 acknowledges that when a UE reports the channel bandwidths that it supports for each NR band, a BCS that it supports for a given band combination, and the maximum channel bandwidth for each band in the bandwidth combination, the network must consider all of those factors to determine what bandwidth combinations the UE supports for the band combination. It is possible that not all of the entries in the BCS are supported because of the information in the other UE capability parameters. Proposal 2: By agreeing to proposal 1, RAN4 agrees that it does not need to create new BCSs to cover UE implementation scenarios where a UE does not support all of the channel bandwidths in a BCS because that can be signalled using a combination of the existing UE capabilities including BCS, the channel bandwidths supported per band, and the maximum channel bandwidth for each band in the combination.
Proposals (cont.) Proposal 3: In order to avoid the need for many new BCSs for inter-band NR-CA, NR-DC, or NR-SUL, the signalling of BCS4 shall indicate that for the band combination the UE supports all of the possible combinations of bandwidths based on the bandwidths the UE supports for each band and the maximum bandwidth for the band in the band combination as indicated in the UE capabilities. The BCS table does not need to fill in the channel bandwidths for BCS4. No additional BCSs will be allowed for NR-CA, NR-DC of NR-SUL combinations. Proposal 4: In support of Proposal 3, any CRs for inter-band NR-CA, NR-DC, or NR- SUL combinations from RAN 96e onwards should not include any new BCSs, even if the BCSs were in the band combination request. Also, new inter-band NR-CA, NR-DC, or NR-SUL band combination requests should not contain any BSSs Proposal 5: RAN4 should agree a CR based on the draft in: https://www.3gpp.org/ftp/tsg_ran/WG4_Radio/TSGR4_96_e/Inbox/Drafts/%5B1 44%5D%20BC_simplification/Draft_R4-120xxxxx_CR_38101-1-g40_BCS4.docx
