RedCap: Overview of RF Impact and Requirements Discussion

The document discusses various aspects of RedCap technology implementation, focusing on RF impact, UE power class, Rx and Tx requirements, and RRM considerations. It provides insights on UE RF requirements, switching times, and potential impacts on network performance. Feedback from industry players like Vivo, Nokia, Huawei, and Ericsson is highlighted, indicating ongoing discussions and work plans for RedCap integration.

• RedCap
• RF impact
• UE requirements
• RRM considerations
• Network performance

cleo Follow

Uploaded on Apr 19, 2024 | 5 Views

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. Download presentation by click this link. If you encounter any issues during the download, it is possible that the publisher has removed the file from their server.

Presentation Transcript

1. R4-210xxxx 3GPP TSG-RAN WG4 Meeting # 99-e Electronic Meeting, May 19-27, 2021 WF on RedCap Ericsson

2. RedCap: General issues RedCap bands: Any FDD (except for n91, n92, n93, and n94) or TDD band could support RedCap. Note: It doesn t mean SUL is excluded from this WI scope. RedCap UE Power Class Existing PC per band could be considered. PC3 should be prioritized if needed.

3. RedCap: BS RF impact No BS RF impact is expecting when introducing RedCap.

4. RedCap: Rx branch for RedCap UE FR1 Minimum # of Rx branch to be specified: 1 Additional # of Rx branch to be specified: 2 FR2: FFS Clarification from RAN plenary on the WID scope of this aspect is needed. Operators are encouraged to provide feedback on use case of RedCap UE in FR2 for next meeting, e,g Power class, frequency band etc.

5. RedCap: UE Tx-Rx and Rx-Tx switching time Tx-Rx switching time: 13 s Tx-Rx switching time: FFS Companies are encouraged to provide their analysis justifying any longer switching time than 13 s. Following question should be answered: Why the TX PLL can not be turned on in advance in the receiving symbols so such power saving can be hidden from the system impact.? Study network performance impact and trade-off with UE power savings

6. RedCap: UE RF impact Tx requirements NR UE Tx single carrier requirements except for UL CA and DC could be reused for RedCap (except the UE transmit power in FR1 and FR2) Transmit power in FR1 and FR2: depend on the RedCap PC and frequency band. Rx requirements: Specify REFSENS: For one Rx branch. For 2 Rx branches for bands where legacy NR UE is required with 4 Rx antenna ports. re-use existing single carrier requirement for 2 Rx branches, FFS on HD-FDD mode. Other requirements: FFS Specification structure: Define new suffix G for RedCap UE RF requirement at least in TS 38.101-1.

7. RedCap: RRM eDRX RF No impact on eDRX RF

8. References 1. R4-2109675, General views on Redcap UE RF requirements, Vivo 2. R4-2109683, Discussion and reply LS on Half-duplex FDD switching time for RedCap UE, Vivo 3. R4-2109747, On the scope of work on RF core requirements Redcap, Nokia, Nokia Shanghai Bell 4. R4-2109879, Draft Reply LS on Half-duplex FDD switching time for RedCap UE, Huawei, HiSilicon 5. R4-2109880, General discussion for RedCap UE, Huawei, HiSilicon 6. R4-2111196, RAN4 RF WI work plan for RedCap, Ericsson 7. R4-2111197, RF impact analysis on R17 RedCap, Ericsson 8. R4-2111198, Reply LS to Half-duplex FDD switching for RedCap UE, Ericsson 9. R4-2111424, RedCap RF Issues, Qualcomm