3GPP TSG-RAN WG1 Meeting #121																										R1-2503279
St Julian’s, Malta, May 19th – 23rd, 2025

Agenda Item:	9.15.2
Source:	Huawei, HiSilicon
Title:	UE features for NR MIMO Phase 5
Document for:	Discussion and Decision

Conclusions
This contribution presents our views on Rel-19 UE features for NR MIMO evolution, which can be found in above for detailed comments and suggestions. Further discussion and consolidation in RAN1 are required. 

3GPP TSG RAN WG1 Meeting #121 																																										R1-2503305
St Julian’s, Malta, May 19th – 23rd, 2025

Agenda Item: 9.15.2
Source: MediaTek Inc.
Title: 	UE features for NR MIMO Phase 5
Document for: Discussion and Decision

Conclusion
Based on the discussion, we made the following proposals:
Enhancements for UE-initiated/event-driven beam management
Proposal 1: Support all FGs related to UE-initiated/event-driven beam management can be applicable for FR1 and FR2. 
Proposal 2: Support FG 59-1-3 with the following changes:
Proposal 3: Introduce the following separate FG for Event-1: 
Proposal 4: Support FG 59-1-4 with the following changes:
Proposal 5: Support FG 59-1-5 with the following changes:
Proposal 6: Introduce the following new FG according to RAN1 agreement: 

CSI enhancements
Proposal 7: Introduce the following new FGs for Rel-19 Type-I SP codebook refinement for 48, 64, and 128 CSI-RS ports with RI=5-8: 
Proposal 8: Support “per band per BC” as the capability granularity for FG 59-2-X series except FG59-2-4 and FG59-2-1-8.

Enhancement for asymmetric DL sTRP/UL mTRP scenarios
Proposal 9: Introduce separate FG 59-4-1c PL offset for Type 1 PHR calculation as follows:
Proposal 10: FG23-1-1 should be the prerequisite FG for FG59-4-3.
Proposal 11: FG59-4-4a and FG59-4-4b should be the prerequisite FG for FG59-4-5.
Proposal 12: FG59-4-1a, FG59-4-1b, FG59-4-2a and FG59-4-2b should be the prerequisite FG for FG59-4-6.
Proposal 13: Support the following modifications for FG 59-4-9a and FG 59-4-9b:

3GPP TSG RAN WG1 #121			R1- 2503386
St Julian’s, Malta, May 19th – 23th, 2025

Source: 	vivo
Title:	Discussion on UE features for NR MIMO Phase 5
Agenda Item:	9.15.2
Document for:	Discussion and Decision

Conclusion
In this contribution we provide updates on UE features for NR MIMO Phase 5 based on the FGs provided in [1].
Adopt the updates in section 2.

3GPP TSG RAN WG1 #121	R1-2503400
Malta, 19 – 23 May 2025

Agenda item:		9.15.2
Source:	Nokia
Title:	Views on NR MIMO Phase 5 UE features
Document for:		Discussion and Decision

Conclusion
In this contribution, we presented our views, suggestions, and proposals on UE features for NR MIMO Phase 5, and we have made the following proposals:
Proposal 1: Adopt the proposed changes and new FGs in Table 1 to UE-initiated/event-driven beam management
Proposal 2: Adopt the proposed changes and new FGs in Table 2 to CSI support for up to 128 CSI-RS ports.
Proposal 3: Adopt the proposed changes in Table 3 for CSI -Extension of CRI(s)-based CSI reporting for hybrid beamforming.
Proposal 4: Adopt the proposed changes in Table 4 to enhancements for CJT deployments under non-ideal synchronization and backhaul.
Proposal 5: Adopt the proposed changes in Table 5 and confirm the yellow highlighted text to enhancement for other rel 19 CSI issues
Proposal 6: Adopt the proposed changes in Table 6 to UL 3TX enhancements.
Proposal 7: Adopt the proposed changes in Table 7 for Asymmetric DL sTRP UL mTRP scenarios
 

3GPP TSG RAN WG1 #121		                                    R1-2503592
St Julian’s, Malta, May 19th – 23th, 2025
Agenda item:		9.15.2
Source:			Samsung
Title:			UE features for NR MIMO Phase 5
Document for:		Discussion and decision

Conclusion





In this contribution, the following observation and proposals are given:

Proposal 1. support to remove the brackets from [for Event-2 and Mode A]

Proposal 2. Add the following two separate rows related to Mode-B for Event-1 and Event-7, respectively


Proposal 3. Support the following updates in red for FGs 59-1-4 and 59-1-5.



Proposal 4. Support the following list of UE capabilities for Rel-19 UL 3TX.

3GPP TSG RAN WG1 #121		R1-2503673
St Julian’s, Malta, May 19th – 23rd, 2025

Source:	ZTE Corporation, Sanechips
Title:	Discussion on UE features for NR MIMO Phase 5
Agenda Item:	9.15.2
Document for:	Discussion and Decision

Conclusion
In this contribution, we provide our views on Rel-19 UE features for each of sub-agendas for NR MIMO evolution. The detailed proposals can be found in the corresponding sections. 

3GPP TSG RAN WG1 #121	  																		R1-2503741
St Julian, Malta, May 19th – 23rd, 2025

Agenda item:	9.15.2
Source: 	Ofinno
Title: 	Views on UE features for NR MIMO Phase 5
Document for:	Discussion/Decision

Views on UE features for NR MIMO Phase 5
In this contribution, we present our views on UE features for NR MIMO Phase 5. We propose:
[Asymmetric DL sTRP/UL mTRP scenarios]
Proposal#1: Regarding FG 59-4-2a and FG 59-4-2b, include the following UE capability as a prerequisite for each FG with updating the definition to cover asymmetric TRP operation as:


Proposal#2: Add FG for SSB reception from UL TRP at least to determine Path Loss on PDCCH-order PRACH based on the agreement in RAN1#119 as shown above related agreement(s).

Proposal#3: Regarding Rel-19 2 TAGs in asymmetric TRP operation, consider the following two options as a starting point:
Option 1: Update the definition of the existing UE capability (i.e. spCell-TAG-Ind-r18) to cover asymmetric TRP operation.
Option 2: Introduce a new UE capability that indicates support of indicating one of two TAG IDs configured in the SpCell via absolute TA command MAC CE in asymmetric TRPs.


Proposal#4: Regarding the maximum number of TAGs across all CCs in a band combination, consider the following two options as a starting point:
Option 1: Update the definition of the existing UE capability (i.e. maxNumberTAG-AcrossCC-r18) to cover asymmetric TRP operation.
Option 2: Introduce a new UE capability for indicating a maximum number of TAGs across all CCs in a band combination.

TDoc file conclusion not found

3GPP TSG-RAN WG1 Meeting #121	Tdoc R1-2503754
St Julian’s, Malta, May 19th – May 23rd, 2025
Agenda Item:	9.15.2
Source:	Ericsson
Title:	UE features for NR MIMO Phase 5
Document for:	Discussion, Decision

Conclusion
In this contribution we provided our views on CSI enhancements and 3 Tx UE features for Rel-19 NR MIMO. 
We made the following observations: 
Observation 1	There does not seem to be a benefit to reduce the maximum number of SRS resources for non-codebook based operation below the 4 supported in Rel-15. Supporting a maximum of 3 resources would instead limit the potential for diversity gain, and be less consstent with the principle of allowing a maximum layer capability that is less than the number of SRS resources.
Observation 2	Based on the discussion regarding the S-TRP non-codebook case and to maintain the consistency between S-TRP and M-TRP non-codebook schemes, the supported number of SRS resources in one SRS resource set should include the value of 4 in Component 4 of FG 59-3-4a and 59-3-5a.
Observation 3	The existing UE capability reporting 4 ports in an SRS resource with port 1003 disabled can create potential ambiguity regarding the correct scaling factor for codebook based PUSCH.
Observation 4	Updating TS 38.214 to clarify that the maximum number of ports supported by the UE in an SRS resource, for scaling of transmission power as described in clause 7.1 of TS 38.213, is calculated using 3, if [UE feature 59-3-2] is supported as well as the maximum number(s) of SRS ports supported by the UE in one SRS resource, would help ensure correct Rel-15 power-scaling behavior for 3Tx codebook based PUSCH.
Observation 5	Alternatively, adding a note under FG 59-3-2 to specify that when transmitting according to Component 4, the number of ports supported by the UE for transmission in an SRS resource is 3 may help to clarify the correct Rel-15 power-scaling behavior for 3Tx codebook-based PUSCH, but could confuse readers since ‘number of SRS ports for transmission’ is used for 3 Tx, while the ‘number of SRS ports’ is used for 2, 4, and 8 Tx.
Observation 6	Defining a procedure for how the maximum number of SRS ports is calculated for the purpose of PUSCH power-scaling seems to be needed to avoid the ambiguity on the number of SRS ports when port 1003 is disabled. Since behavior should not be defined in UE apability specifications, this calculation does not seem appropriate to add as a note to 38.306, but instead should be defined in a procedural specification such as 38.214.

Based on the discussion in the previous sections we propose the following:
Proposal 1	Support ‘per band’ reporting for the following FGs:
	FGs related to Single panel Type I codebooks (i.e., FGs 59-2-1-1, 59-2-1-1a, 59-2-1-1b, 59-2-1-1c, 59-2-1-1d, 59-2-1-1e)
	FGs related to Multi panel Type I codebooks (i.e., 59-2-1-2, 59-2-1-2a, 59-2-1-2b)
Proposal 2	For FGs 59-2-1-3, 59-2-1-3a, and 59-2-1-3b, support the same reporting type as Rel-16 eType-II codebook.
Proposal 3	For FGs 59-2-1-4 and 59-2-1-4a, support the same reporting type as Rel-17 FeType-II codebook.
Proposal 4	For FGs 59-2-1-5, 59-2-1-5a, and 59-2-1-5b, support the same reporting type as Rel-18 eType-II Doppler codebook.
Proposal 5	Support only aperiodic CSI-RS in FG 59-2-1-6.
Proposal 6	For FG 59-2-1-7, the pre-requisites should be one of 59-2-1-1/1a/1b, or one of 59-2-1-1c/1d/1e.
Proposal 7	For FG 59-2-1-7, the reporting type should be ‘per band’.
Proposal 8	Support maxNumberSRS-ResourcePerSet = 4 for Rel-19 3 Tx non-codebook based operation.
Proposal 9	Support the value of 4 for the maximum number of SRS resources in one SRS resource set for Rel-19 3 Tx non-codebook based M-TRP operations.
Proposal 10	Update TS 38.214 to calculate the maximum number of ports supported by the UE in an SRS resource, for scaling of PUSCH transmission power as described in clause 7.1 of [6, TS 38.213], using 3, if [UE feature 59-3-2] is supported, and the maximum number(s) of SRS ports supported by the UE in one SRS resource.
Proposal 11	Include a set of antenna switching capabilities {t1r1, t2r2, t1r2, t3r3, t2r4, t1r4, t2r6, t1r6, t3r6} for Component 1 of FG 59-3-3 and update the name to include ‘for > 4 Rx’.
Proposal 12	Introduce a component in 59-4-4b to indicate UE capability to apply reference timing indicated in PDCCH
Proposal 13	Introduce a FG, e.g., FG 59-4-10, to support indicate PL-RS for PDCCH-order PRACH for inter-cell.
 

TDoc file reading error

3GPP TSG RAN WG1 #121	                   	                                     R1-2503851
St Julian's, Malta, 19 - 23 May, 2025

Source: 	CMCC
Title:	Discussion on UE features for NR MIMO Phase 5
Agenda item:	9.15.2
Document for:	Discussion & Decision

Conclusions
In this contribution, we discuss Rel-19 UE features for NR MIMO evolution, and the following proposals are made.
Proposal 1: Take the following modification (in red) for the feature of Rel-19 UE-initiated/event-driven beam management.
Proposal 2: Take the following modification (in red) for the feature of Rel-19 extended codebook for up to 128 ports:
Proposal 3: Take the following modification (in red) for the feature of Rel-19 extended Type-II Doppler codebook for up to 128 ports:
Proposal 4: Take the following modification (in red) of Rel-19 3-antenna-port codebook-based transmissions:
Proposal 5: Take the following modification (in red) for the feature of Rel-19 asymmetric DL sTRP/UL mTRP scenarios:

3GPP TSG RAN WG1 #121                                                     R1-2503901
St Julian’s, Malta, May 19th – 23rd, 2025

Agenda Item:	9.15.2
Source:	Xiaomi
Title:	Discussion on UE features for NR MIMO Phase 5
Document for:	Discussion

Conclusion
Based on the discussion, we propose the FGs need to be supported in above sections.

3GPP TSG RAN WG1 #121		        						 R1-2504232
St Julian’s, Malta, May 19th – 23rd, 2025
						    		

Source:	OPPO
Title:	UE features for NR MIMO Phase 5
Agenda Item:	9.15.2
Document for:	Discussion and Decision

Conclusion
In this contribution, we discuss the potential UE features for Rel-19 MIMO with the following proposals:
Proposal 1: The pre-requisite for FG 59-1-1, 59-1-4 and 59-1-5 is FG of supporting the unified TCI framework.
  
Proposal 2: Updating the UE features of UEI beam reporting as follows:







Proposal 3: The FGs for up to 128 ports codebook enhancement can be updated as:

Proposal 4: The FGs for CJT calibration (CJTC) reporting can be updated as:

Proposal 5: The FGs for SRS port grouping can be updated as: 


Proposal 6: The following UE features can be supported for 3Tx uplink transmission:

3GPP TSG RAN WG1 #121																			R1-2504353
St Julian’s, Malta, May 19th – 23th, 2025

Agenda item:	9.15.2
Source: 	Apple Inc.
Title: 	Views on UE features for NR MIMO Phase 5
Document for:	Discussion/Decision

1. Views on UE features for Rel-19 NR MIMO Phase 5
In this contribution, we present our high level views on UE features for Rel-19 NR MIMO Phase 5 based on the endorsed feature list in R1-2502977 from RAN1#120bis with track change on. At high level, the FGs are organized in the following way to handle different objectives/agendas in NR Rel-19 MIMO Phase 5. 
FG59-1x covers the enhancement for UE-initiated/event driven beam management 
FG59-2x covers the CSI enhancement
FG59-3x covers the 3Tx UL operation 
FG59-4x covers the enhancement for asymmetric DL sTRP/UL mTRP scenarios 

Enhancements for UE-initiated/event-driven beam management 

CSI enhancements

3Tx UL operation 

Enhancement for asymmetric DL sTRP/UL mTRP scenarios

2. Reference
[1] R1-2502977, Updated RAN1 UE features list for Rel-19 NR after RAN1 #120bis, Moderators (AT&T, NTT DOCOMO, INC.), 3GPP TSG RAN WG1 #120bis, Wuhan, China, April 7th – 11th, 2025

TDoc file conclusion not found

3GPP TSG RAN WG1 #121                                   					       												                                    R1-2504370
St Julian’s, Malta, May 19th – 23th, 2025

Agenda Item:	9.15.2
Source:	Moderator (AT&T)
Title:	Summary of UE features for NR MIMO Phase 5
Document for:	Discussion/Decision

Conclusion
Agreements reached during RAN1 #121 as part of this agenda item are summarized in [17]. 

3GPP TSG RAN WG1 #121			R1-2504420
St Julian’s, Malta, May 19th – 23rd, 2025
Agenda item:		9.15.2
Source: 	Qualcomm Incorporated
Title: 	UE features for NR MIMO phase 5
Document for:	Discussion/Decision

TDoc file conclusion not found

3GPP TSG RAN WG1 #121																		R1-2504524
St Julian, Malta, May 19th – 23rd, 2025

Source:	NTT DOCOMO, INC.
Title:	Discussion on MIMO UE features
Agenda Item:	9.15.2
Document for: 	Discussion and Decision

Summary
In this contribution, we discussed UE features for Rel-19 MIMO. Our views are provided in each session above.

3GPP TSG RAN WG1 #121	                                   					       												                                   R1-2504926
St Julian’s, Malta, May 19th – 23th, 2025

Source:	Ad-Hoc Chair (AT&T)
Title:	Session Notes of AI 9.15.2
Agenda Item:	9.15.2
Document for: 	Endorsement

9.15.2 UE features for NR MIMO Phase 5


Agreement: Adopt the following changes highlighted in chromatic fonts, while keeping the yellow highlighting, if any, as shown


Agreement: Adopt the following changes highlighted in chromatic fonts, while keeping the yellow highlighting, if any, as shown


Agreement: Adopt the following changes highlighted in chromatic fonts, while keeping the yellow highlighting, if any, as shown


Agreement: Adopt the following changes highlighted in chromatic fonts, while keeping the yellow highlighting, if any, as shown


Agreement: Adopt the following changes highlighted in chromatic fonts, while keeping the yellow highlighting, if any, as shown


Agreement: Adopt the following changes highlighted in chromatic fonts, while keeping the yellow highlighting, if any, as shown


Agreement: Adopt the following changes highlighted in chromatic fonts, while keeping the yellow highlighting, if any, as shown


Agreement: Adopt the following changes highlighted in chromatic fonts, while keeping the yellow highlighting, if any, as shown


Agreement: Adopt the following changes highlighted in chromatic fonts, while keeping the yellow highlighting, if any, as shown


Agreement: Adopt the following changes highlighted in chromatic fonts, while keeping the yellow highlighting, if any, as shown


Agreement: Adopt the following changes highlighted in chromatic fonts, while keeping the yellow highlighting, if any, as shown


Agreement: Adopt the following changes highlighted in chromatic fonts, while keeping the yellow highlighting, if any, as shown


Agreement: Adopt the following changes highlighted in chromatic fonts, while keeping the yellow highlighting, if any, as shown


Agreement: Adopt the following changes highlighted in chromatic fonts, while keeping the yellow highlighting, if any, as shown


Agreement: Adopt the following changes highlighted in chromatic fonts, while keeping the yellow highlighting, if any, as shown


Agreement: Adopt the following changes highlighted in chromatic fonts, while keeping the yellow highlighting, if any, as shown


Agreement: Adopt the following changes highlighted in chromatic fonts, while keeping the yellow highlighting, if any, as shown


Agreement: Adopt the following changes highlighted in chromatic fonts, while keeping the yellow highlighting, if any, as shown


Agreement: Adopt the following changes highlighted in chromatic fonts, while keeping the yellow highlighting, if any, as shown


Agreement: Adopt the following changes highlighted in chromatic fonts, while keeping the yellow highlighting, if any, as show


Agreement: Adopt the following changes highlighted in chromatic fonts, while keeping the yellow highlighting, if any, as shown


Agreement: Delete the following row/FG


Agreement: Adopt the following changes highlighted in chromatic fonts, while keeping the yellow highlighting, if any, as shown
Note: Include in the LS to RAN2 that for each FG with “A list of supported combinations” the size of the list is 16

Agreement: Adopt the following changes highlighted in chromatic fonts, while keeping the yellow highlighting, if any, as shown


Agreement: Adopt the following changes highlighted in chromatic fonts, while keeping the yellow highlighting, if any, as shown


Agreement: Adopt the following changes highlighted in chromatic fonts, while keeping the yellow highlighting, if any, as shown


Agreement: Adopt the following changes highlighted in chromatic fonts, while keeping the yellow highlighting, if any, as shown


Agreement: Adopt the following changes highlighted in chromatic fonts, while keeping the yellow highlighting, if any, as shown


Agreement: Adopt the following changes highlighted in chromatic fonts, while keeping the yellow highlighting, if any, as shown


Agreement: Adopt the following changes highlighted in chromatic fonts, while keeping the yellow highlighting, if any, as shown


Agreement: Adopt the following changes highlighted in chromatic fonts, while keeping the yellow highlighting, if any, as shown


Agreement: Adopt the following changes highlighted in chromatic fonts, while keeping the yellow highlighting, if any, as shown


Agreement: Adopt the following changes highlighted in chromatic fonts, while keeping the yellow highlighting, if any, as shown


Agreement: Adopt the following changes highlighted in chromatic fonts, while keeping the yellow highlighting, if any, as shown


Agreement: Adopt the following changes highlighted in chromatic fonts, while keeping the yellow highlighting, if any, as shown


Agreement: Adopt the following changes highlighted in chromatic fonts, while keeping the yellow highlighting, if any, as shown


Agreement: Adopt the following changes highlighted in chromatic fonts, while keeping the yellow highlighting, if any, as shown


Agreement: Adopt the following changes highlighted in chromatic fonts, while keeping the yellow highlighting, if any, as shown


Agreement: Adopt the following changes highlighted in chromatic fonts, while keeping the yellow highlighting, if any, as shown


Agreement: Adopt the following changes highlighted in chromatic fonts, while keeping the yellow highlighting, if any, as shown


Agreement: Adopt the following changes highlighted in chromatic fonts, while keeping the yellow highlighting, if any, as shown


Agreement: Adopt the following changes highlighted in chromatic fonts, while keeping the yellow highlighting, if any, as shown


Agreement: Adopt the following changes highlighted in chromatic fonts, while keeping the yellow highlighting, if any, as shown


Agreement: Adopt the following changes highlighted in chromatic fonts, while keeping the yellow highlighting, if any, as shown


Agreement: Adopt the following changes highlighted in chromatic fonts, while keeping the yellow highlighting, if any, as shown


Agreement: Adopt the following changes highlighted in chromatic fonts, while keeping the yellow highlighting, if any, as shown


Agreement: Adopt the following changes highlighted in chromatic fonts, while keeping the yellow highlighting, if any, as shown


Agreement: Adopt the following changes highlighted in chromatic fonts, while keeping the yellow highlighting, if any, as shown


Agreement: Adopt the following changes highlighted in chromatic fonts, while keeping the yellow highlighting, if any, as shown


Agreement: Adopt the following changes highlighted in chromatic fonts, while keeping the yellow highlighting, if any, as shown


Agreement: Adopt the following changes highlighted in chromatic fonts, while keeping the yellow highlighting, if any, as shown


Agreement: Adopt the following changes highlighted in chromatic fonts, while keeping the yellow highlighting, if any, as shown


Agreement: Adopt the following changes highlighted in chromatic fonts, while keeping the yellow highlighting, if any, as shown


Agreement: Adopt the following changes highlighted in chromatic fonts, while keeping the yellow highlighting, if any, as shown


Agreement: Adopt the following changes highlighted in chromatic fonts, while keeping the yellow highlighting, if any, as shown


Agreement: Adopt the following changes highlighted in chromatic fonts, while keeping the yellow highlighting, if any, as shown


Agreement: Adopt the following changes highlighted in chromatic fonts, while keeping the yellow highlighting, if any, as shown


Agreement: Adopt the following changes highlighted in chromatic fonts, while keeping the yellow highlighting, if any, as shown


Agreement: Adopt the following changes highlighted in chromatic fonts, while keeping the yellow highlighting, if any, as shown


Agreement: Adopt the following changes highlighted in chromatic fonts, while keeping the yellow highlighting, if any, as shown


Agreement: Adopt the following changes highlighted in chromatic fonts, while keeping the yellow highlighting, if any, as shown


Agreement: Adopt the following changes highlighted in chromatic fonts, while keeping the yellow highlighting, if any, as shown


Agreement: Adopt the following changes highlighted in chromatic fonts, while keeping the yellow highlighting, if any, as shown


Agreement: Adopt the following changes highlighted in chromatic fonts, while keeping the yellow highlighting, if any, as show


Agreement: Introduce the following Rel. 19 UE FGs (yellow highlighting, if any, shows text that’s not yet agreed)


Agreement: Adopt the following changes highlighted in chromatic fonts, while keeping the yellow highlighting, if any, as shown


Agreement: Adopt the following changes highlighted in chromatic fonts, while keeping the yellow highlighting, if any, as shown





R1-2503279	UE features for NR MIMO Phase 5	Huawei, HiSilicon
R1-2503305	UE features for NR MIMO Phase 5	MediaTek Inc.
R1-2503386	Discussion on UE features for NR MIMO Phase 5	vivo
R1-2503400	NR MIMO Phase 5 UE features	Nokia
R1-2503592	UE features for NR MIMO Phase 5	Samsung
R1-2503673	Discussion on UE features for NR MIMO Phase 5	ZTE Corporation, Sanechips
R1-2503741	Views on UE features for NR MIMO Phase 5	Ofinno
R1-2503754	UE features for NR MIMO Phase 5	Ericsson
R1-2503782	Further discussion on UE features for NR MIMO Phase 5	CATT
R1-2503851	Discussion on UE features for NR MIMO Phase 5	CMCC
R1-2503901	Discussion on UE features for NR MIMO Phase 5	Xiaomi
R1-2504232	UE features for NR MIMO Phase 5	OPPO
R1-2504353	Views on UE features for NR MIMO Phase 5	Apple
R1-2504370	Summary of UE features for NR MIMO Phase 5	Moderator (AT&T)
R1-2504420	UE features for NR MIMO phase 5	Qualcomm Incorporated
R1-2504524	Discussion on UE features for NR MIMO Phase 5	NTT DOCOMO, INC.

TDoc file conclusion not found