
BCS4 Implementation Guidelines for T-Mobile USA and Ericsson
Explore the recommended approach for BCS4 deployment, including signaling options, mandatory vs. optional considerations, and representation in tables. Understand the implications for Release 15 and Release 17, with insights on new signaling requirements and future compatibility. Find a balanced solution to meet the diverse needs of stakeholders for optimal deployment strategies.
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
Way forward for general questions for BCS4 (excluding MSD) T-Mobile USA, [Ericsson],
Comments on Signalling If no new signalling (minimum channel BW) then BCS4 could be release independent to Rel-15 New signalling for minimum channel BW would be a new feature, and could only be introduced in Rel-17, so then not Release independent to Rel-15 If BCS4 is only available in Rel-17, then likely not available before 2023, so operators would need to request a lot of traditional BCSs.
Signalling (already agreed at the May 25th GTW) Option 1) No new signalling. Huawei, Ericsson Option 2) New signalling and BCS4 only Rel-17+, OPPO, Qualcomm, Xiaomi, Vivo, MediaTek Option 3) No new signalling for BCS4. Continue discussion for Rel-17 signalling w/BCS5, T-Mobile USA, Apple, Ericsson Option 4) No new signaling for BCS4, minimum channel BW per band in in the combination signaling in Rel- 17 w/BCS5. Comments: 5 companies want BCS4 without signalling Release independent to Re-15 (Option 1 and 3) 5 companies want BCS4 with signalling for Rel-17 Only one company opposed to any new signalling Given the split, the proposed Way Forward is to compromise and accept Option 4, where BCS4 is release independent with no new signalling, and new signalling is added in Rel-17 for BCS5. Option 4 was no company s top choice, so a compromise for everyone. But, it should meet the needs of everyone. Agreement from 25 May GTW: Introduce BCS4 release independent with no new signalling, and BCS5 with new signalling in Rel-17. BCS5 is the same as BCS4 except that there is new signaling for BCS5 for minimal channel bandwidth FFS BCS5 to indicate minimal channel bandwidth or CA bandwidth for UL and/or DL per CC per band and per band configurations FFS whether to send LS to RAN2 to ask them to evaluate the alternative solutions.
BCS4 Mandatory vs. Optional Option 1) Mandatory: T-Mobile, Ericsson Option 2) Optional: ZTE, OPPO, T-Mobile USA, Qualcomm, Apple, Vivo Proposal 2: BCS4 is optional for a given combination, allocated as requested
How to represent BCS4 in the tables Option 1 shows intra-band CA Option 2 shows only single band Option 3 shows single band and intra-band (ZTE) NR CA configur ation Uplink CA configur ation NR Ba nd Channel bandwidth (MHz) (NOTE 3) Bandwi dth combin ation set 5 10 15 20 25 30 40 50 60 70 80 90 10 0 CA_n1A- n3A CA_n1A- n3A n1 5 10 15 20 0 n3 5 10 15 20 25 30 See n1 and n3 channel bandwidths in Table 5.3.5-1 4 Proposal 3: Option 3 which covers inter-band and intra- band NR CA configuration Uplink CA co nfiguration NR Band Channel bandwidth (MHz) Bandwidt h combina tion set 5 10 15 20 25 30 40 50 60 70 80 90 100 CA_nXA-nYA CA_nXA- nYA nX 5 10 15 20 0 nY 5 10 15 20 25 30 See nX and nY channel bandwidths in Table 5.3.5-1 4 CA_nXA-nYC CA_nXA- nYA nX 5 10 15 20 0 nY 5 10 15 20 25 30 See nX channel bandwidths in Table 5.3.5-1 and nYC channel bandwidths in Table 5.5A.1-1. 4
How to indicate BCS4 for intra-band NR-CA Proposal 4: Continue discussions for how to represent BCS4 for intra- band NR-CA at RAN4#100.
Summary Proposal 1: N/A. (Agreement from Tuesday GTW is documented on slide 3) Proposal 2: BCS4 is optional for a given combination, allocated as requested Proposal 3: Option 3 which covers inter-band and intra-band Proposal 4: Continue discussions for how to represent BCS4 for intra-band NR-CA at RAN4#100.