Tdoc List

2020-03-09 18:23

TDoc Title Source Type For Agenda Avail Treated Decision Wdrn Replaced-by Replaces
R5‑200000 Agenda WG Chairman agenda Information
1Opening of the meeting
Yes
YesRAN5#86 Electronic Meeting has full decision power. Review of the IPR obligations, Antitrust and US EAR regulations - please refer to the ‘Reminder for IPR Declaration’ (page 15); ‘Antitrust Guidance’ (page 15) and ‘Statement on US EAR’ (page 16) in R5-200000.
approved No    
R5‑200001 Agenda - mid week session WG Chairman agenda Information
1Opening of the meeting
No
Yes
withdrawn Yes    
R5‑200002 Agenda - closing session WG Chairman agenda Information
1Opening of the meeting
No
Yes
withdrawn Yes    
R5‑200003 RAN5#86 E-meeting Timeline, Scope, Process WG Chairman agenda Information
1Opening of the meeting
Yes
Yes
endorsed No    
R5‑200004 RAN5 Leadership Team WG Chairman other Information
2.1Live Reports
Yes
Yes
noted No    
R5‑200005 RAN5#85 WG Minutes ETSI Secretariat report Approval
2.1Live Reports
Yes
Yesopen until Fri.
approved No    
R5‑200006 RAN5#85 WG Action Points ETSI Secretariat report Information
2.1Live Reports
Yes
Yes
noted No    
R5‑200007 Latest RAN Plenary notes WG Chairman report Information
2.1Live Reports
Yes
Yes
noted No    
R5‑200008 Latest RAN Plenary draft Report WG Chairman report Information
2.1Live Reports
Yes
Yes
noted No    
R5‑200009 Post Plenary Active Work Item update ETSI Secretariat other Information
2.1Live Reports
Yes
Yesopen until Fri. Sprint: pls. update the WP table.
revised No R5‑200896  
R5‑200010 RAN5 SR to RP#86 WG Chairman report Information
2.2General Reports for information
Yes
Yes
noted No    
R5‑200011 TF160 SR to RP#86 WG Chairman report Information
2.2General Reports for information
Yes
Yes
noted No    
R5‑200012 RAN Chair Report to SA#86 WG Chairman report Information
2.2General Reports for information
Yes
Yes
noted No    
R5‑200013 RAN5#86 LS Template WG Chairman other Information
4.3RAN5 PRDs/Templates
Yes
Yes
noted No    
R5‑200014 Meeting schedule for 2020 WG Chairman other  
4.4Meeting schedule for 2020-21
Yes
Yes
noted No    
R5‑200015 WI Progress and Target Completion Date Review WG Chairman other Information
7.4.2Active Work Items/ Study Item: work plans (wp) / status reports (sr) / Work Item Descriptions (wid)
No
No
reserved No    
R5‑200016 Review deadlines for next quarter WG Chairman other Information
7.6Confirmation of Future RAN5 Matters
Yes
Yes
noted No    
R5‑200017 Reply LS on MOP for intra-band EN-DC TSG WG RAN4 LS in Information
3Incoming Liaison Statements
Yes
YesRAN5 Vice Chair RF: deferred until 20.2. Huawei: all the actions in RAN5 LS seem to have been taken care effectively, no further clarification is needed from RAN4. No reply LS needed.
noted No    
R5‑200018 Reply LS on 5G-NR FR2 Transmitter & Receiver Testability Issues MSG TFES LS in Information
3Incoming Liaison Statements
Yes
Yesconclusion upfront postponed to RP#87.
withdrawn Yes    
R5‑200019 dummy LS2 ETSI LS in Information
3Incoming Liaison Statements
No
Yes
withdrawn Yes    
R5‑200020 IFF DFF Hybrid setup for FR2 RRM 2AoA Test Anritsu discussion Endorsement
5.3.2.17Discussion Papers / Work Plan / TC lists
Yes
Yesr1 was produced. Outcome of offline discussion among MU crews.
revised No R5‑201154  
R5‑200021 Update SIB1 Ericsson CR Agreement
6.3.2.1TS 38.508-1
Yes
Yescoversheet revision.
revised No R5‑200930  
R5‑200022 Updates of MU and TT in TS 38.521-1 NTT DOCOMO, INC. CR Agreement
5.3.2.4.3Clauses 1-5 / Annexes
Yes
YesThere is no agreement for -1 MU and TT during this meeting except for Huawei’s papers (0392_Dp, 0393_CR)
withdrawn Yes    
R5‑200023 Updates of MU and TT in TS 38.521-2 NTT DOCOMO, INC. CR Agreement
5.3.2.5.3Clauses 1-5 / Annexes
Yes
Yesr1 was produced. 1) Brackets of Rx Spur (band n257, 34 to 40 GHz) was removed based on the endorsement of R5-201034. 2) Editor’s note in OFF power was removed based on the MU completion of R5-200744r2 (TR 38.902 CR). 3) Editor’s note and offset value of General Spurious was updated based on the R5-200744r2. 4) Some missing test cases for UL CA are introduced to the Annex F.
revised No R5‑201192  
R5‑200024 Updates of MU and TT in TS 38.521-3 NTT DOCOMO, INC. CR Agreement
5.3.2.6.3Clauses 1-5 / Annexes
Yes
Yesr1 was produced.1) Editor’s note (FR2 Spurious tests) was updated since corresponding SA test cases were updated. 2) Some missing test cases are introduced into Annex F. 3) Editor’s note (FR2 SC) was removed since this test case was already completed at the last RAN5#85. r2 was produced. OFF power (Inter-FR2, 2CCs), which is not implemented to the latest spec was introduced in this version.
revised No R5‑201193  
R5‑200025 Update CounterCheck Ericsson CR Agreement
6.3.2.1TS 38.508-1
Yes
Yescoversheet revision. r1 was produced.
revised No R5‑200931  
R5‑200026 Editorial update DLInformationTransfer Ericsson CR Agreement
6.3.2.1TS 38.508-1
Yes
Yescoversheet revision.
revised No R5‑200932  
R5‑200027 Editorial update FailureInformation Ericsson CR Agreement
6.3.2.1TS 38.508-1
Yes
Yescoversheet revision.
revised No R5‑200933  
R5‑200028 Editorial update MeasurementReport Ericsson CR Agreement
6.3.2.1TS 38.508-1
Yes
Yescoversheet revision.
revised No R5‑200934  
R5‑200029 Editorial update MobilityFromNRCommand Ericsson CR Agreement
6.3.2.1TS 38.508-1
Yes
Yescoversheet revision.
revised No R5‑200935  
R5‑200030 Editorial update Paging Ericsson CR Agreement
6.3.2.1TS 38.508-1
Yes
Yescoversheet revision.
revised No R5‑200936  
R5‑200031 SR - NR_Rel-16_CA_DC after RAN5#86 CMCC WI status report Information
7.4.2Active Work Items/ Study Item: work plans (wp) / status reports (sr) / Work Item Descriptions (wid)
Yes
Yes
noted No    
R5‑200032 WP - NR_Rel-16_CA_DC after RAN5#86 CMCC Work Plan Information
7.4.2Active Work Items/ Study Item: work plans (wp) / status reports (sr) / Work Item Descriptions (wid)
Yes
Yes
noted No    
R5‑200033 New WID on UE Conformance Test Aspects – EN-DC PC2 TDD-TDD UE CMCC WID new Approval
7.4.1Final version of Work Item Proposals
Yes
Yesr1 was produced. Header update.
revised No R5‑200897  
R5‑200034 Additional UE Power Class declaration CMCC, Bureau Veritas CR Agreement
7.2.1RF group docs still requiring WG verdict/confirmation - original A.I. retained
Yes
Yesr1 was produced: coversheet header. r2 was produced.
revised No R5‑200903  
R5‑200035 Discussion on how to update Clause 4.1 in TS 38521-1-2-3-4 CMCC, Huawei, Hisilicon, Telecom Italia, China Unicom, CAICT discussion Endorsement
5.3.2.17Discussion Papers / Work Plan / TC lists
Yes
Yesr1 was produced. Editorial wording changes.
revised No R5‑200919  
R5‑200036 Correction of reference numbers in TS 38.521-1 CMCC CR Agreement
5.3.2.4.1Tx Requirements (Clause 6)
Yes
Yesr1 was produced. r2 was produced.
revised No R5‑200971  
R5‑200037 Update of TC 7.7A.1 CMCC, Huawei, Hisilicon CR Agreement
5.3.2.4.2Rx Requirements (Clause 7)
Yes
Yesr1 was produced. The test procedure has been updated to fix the overlap with R5-200727. The header has been changed into e-meeting format. The Source of the coversheet have been changed.
revised No R5‑200907  
R5‑200038 Update of Clause 4 in TS 38.521-1 CMCC, Telecom Italia, Huawei, Hisilicon, CAICT CR Agreement
5.3.2.4.3Clauses 1-5 / Annexes
Yes
Yesr1 was produced. Editorial wording changes.
revised No R5‑200908  
R5‑200039 Correction of reference numbers in TS 38.521-2 CMCC CR Agreement
5.3.2.5TS 38.521-2
Yes
Yescoversheet spec + data r1 was produced.
revised No R5‑200980  
R5‑200040 Update of Clause 4 in TS 38.521-2 CMCC, Telecom Italia, Huawei, Hisilicon, CAICT CR Agreement
5.3.2.5.3Clauses 1-5 / Annexes
Yes
Yesr1 was produced. Editorial wording changes. Associated supporting paper R5-200046r1.
revised No R5‑200911  
R5‑200041 Addition of Clause 7.5B.0.3a CMCC CR Agreement
5.3.2.6.2Rx Requirements (Clause 7)
Yes
Yesr1 was produced.
revised No R5‑200984  
R5‑200042 Update of Clause 4 in TS 38.521-3 CMCC, Telecom Italia, Huawei, Hisilicon, CAICT CR Agreement
5.3.2.6.3Clauses 1-5 / Annexes
Yes
Yesr1 was produced. Editorial wording changes.
revised No R5‑200913  
R5‑200043 Update of TC 7.5B.1 ACS for for intra-band contiguous EN-DC 2CCs CMCC CR Agreement
5.3.2.6.2Rx Requirements (Clause 7)
Yes
Yesr1 was produced.
revised No R5‑200964  
R5‑200044 Update of TC 7.5B.2 ACS for for intra-band non-contiguous EN-DC 2CCs CMCC CR Agreement
5.3.2.6.2Rx Requirements (Clause 7)
Yes
Yescover: add +non-! wrong data. r1 was produced. r2 was produced.
revised No R5‑200963  
R5‑200045 Update of Clause 4 in TS 38.521-4 CMCC, Telecom Italia, Huawei, Hisilicon, CAICT CR Agreement
5.3.2.7.4Clauses 1-4 / Annexes
Yes
Yesr1 was produced. Editorial wording changes.
revised No R5‑200915  
R5‑200046 Discussion on how to update TS 38.522 CMCC, Bureau Veritas, Huawei, Hisilicon, China Unicom, CAICT, TEJET, SRTC, Sporton discussion Endorsement
5.3.2.17Discussion Papers / Work Plan / TC lists
Yes
YesRRM rapporteur Adrian's proposal of removing the original proposal 3 has also been accepted before the meeting. Deadline 21.2. for endorsement. Long discussion with Samsung. • R&S suggestion to remove Proposal 3--Accepted. Proposal 3 has been removed from R5-200046 already before the e-meeting started. • E///: some further confirmations are needed from Vijay. And the potential needed actions can be taken in the 38.522 Jumbo CR (R5-200145) directly without impacts on the paper (R5-200046). • Samsung: help to further clarify the problems/observations/suggestions. Problem/Observation 1, 2 and 3 have been addressed by implementing Proposal 1 and 2 in the Jumbo CR (R5-200145) already. -> ONLY Proposal 1 and 2 can be endorsed. r1 was produced. As per the offline discussion, consensus has been reached on Proposal 3. Due to the objection from Samsung, there are no consensus on Proposal 1 or 2.
revised No R5‑201017  
R5‑200047 Update TPanalysis of TC 7.5B.1 ACS for for intra-band contiguous EN-DC within FR1 2CCs CMCC CR Agreement
5.3.2.16TR 38.905 (NR Test Points Radio Transmission and Reception )
No
Yeslate doc
withdrawn Yes    
R5‑200048 Correction to NR RLC test case 7.1.2.3.5 Keysight Technologies UK Ltd CR Agreement
6.3.2.4.3.1.3RLC
Yes
Yescoversheet revision.
revised No R5‑200999  
R5‑200049 Editorial update RRCReestablishment Ericsson CR Agreement
6.3.2.1TS 38.508-1
Yes
Yescoversheet revision.
revised No R5‑200937  
R5‑200050 Update RRCReconfiguration Ericsson CR Agreement
6.3.2.1TS 38.508-1
Yes
Yesr1 was produced. Missing condition EN-DC added. Condition to add SCG (NR-DC) rephrased. r2 was produced.
revised No R5‑201221  
R5‑200051 Editorial update RRCReconfigurationComplete Ericsson CR Agreement
6.3.2.1TS 38.508-1
Yes
Yescoversheet revision.
revised No R5‑200938  
R5‑200052 Editorial changes to TS 37.571-X titles to remove references to individual RATs Rapporteur CR Agreement
5.5.9TS 37.571-1
Yes
Yescoversheet revision.
revised No R5‑201013  
R5‑200053 Editorial changes to TS 37.571-X titles to remove references to individual RATs Rapporteur CR Agreement
6.5.7.1TS 37.571-2
Yes
Yescoversheet revision.
revised No R5‑201012  
R5‑200054 Editorial changes to TS 37.571-X titles to remove references to individual RATs Rapporteur CR Agreement
5.5.10TS 37.571-3
Yes
Yescoversheet revision.
revised No R5‑201014  
R5‑200055 Editorial changes to TS 37.571-X titles to remove references to individual RATs Rapporteur CR Agreement
5.5.11TS 37.571-5
Yes
Yescoversheet revision.
revised No R5‑201015  
R5‑200056 Editorial update RRCReject Ericsson CR Agreement
6.3.2.1TS 38.508-1
Yes
Yescoversheet revision.
revised No R5‑200939  
R5‑200057 Removal of technical content in 34.121-1 v15.3.0 and substitution with pointer to the next Release ETSI Secretariat CR Agreement
7.1Pointer CRs
Yes
Yesblock agreed during email agreement
agreed No    
R5‑200058 Removal of technical content in 34.123-3 v14.5.0 and substitution with pointer to the next Release ETSI Secretariat CR Agreement
7.1Pointer CRs
Yes
Yesblock agreed during email agreement
agreed No    
R5‑200059 Removal of technical content in 34.229-1 v14.7.0 and substitution with pointer to the next Release ETSI Secretariat CR Agreement
7.1Pointer CRs
Yes
Yesblock agreed during email agreement
agreed No    
R5‑200060 Removal of technical content in 34.229-2 v14.7.0 and substitution with pointer to the next Release ETSI Secretariat CR Agreement
7.1Pointer CRs
Yes
Yesblock agreed during email agreement
agreed No    
R5‑200061 Removal of technical content in 34.229-3 v14.5.0 and substitution with pointer to the next Release ETSI Secretariat CR Agreement
7.1Pointer CRs
Yes
Yesblock agreed during email agreement
agreed No    
R5‑200062 Removal of technical content in 36.508 v15.5.0 and substitution with pointer to the next Release ETSI Secretariat CR Agreement
7.1Pointer CRs
Yes
Yesblock agreed during email agreement
agreed No    
R5‑200063 Removal of technical content in 36.521-1 v15.5.0 and substitution with pointer to the next Release ETSI Secretariat CR Agreement
7.1Pointer CRs
Yes
Yesblock agreed during email agreement
agreed No    
R5‑200064 Removal of technical content in 36.521-2 v15.5.0 and substitution with pointer to the next Release ETSI Secretariat CR Agreement
7.1Pointer CRs
Yes
Yesblock agreed during email agreement
agreed No    
R5‑200065 Removal of technical content in 36.521-3 v15.5.0 and substitution with pointer to the next Release ETSI Secretariat CR Agreement
7.1Pointer CRs
Yes
Yesblock agreed during email agreement
agreed No    
R5‑200066 Removal of technical content in 36.523-1 v15.5.0 and substitution with pointer to the next Release ETSI Secretariat CR Agreement
7.1Pointer CRs
Yes
Yesblock agreed during email agreement
agreed No    
R5‑200067 Removal of technical content in 36.523-2 v15.5.0 and substitution with pointer to the next Release ETSI Secretariat CR Agreement
7.1Pointer CRs
Yes
Yesblock agreed during email agreement
agreed No    
R5‑200068 Removal of technical content in 36.523-3 v15.3.0 and substitution with pointer to the next Release ETSI Secretariat CR Agreement
7.1Pointer CRs
Yes
Yesblock agreed during email agreement
agreed No    
R5‑200069 Removal of technical content in 36.579-1 v13.2.0 and substitution with pointer to the next Release ETSI Secretariat CR Agreement
7.1Pointer CRs
Yes
Yesblock agreed during email agreement
agreed No    
R5‑200070 Removal of technical content in 36.579-2 v13.2.0 and substitution with pointer to the next Release ETSI Secretariat CR Agreement
7.1Pointer CRs
Yes
Yesblock agreed during email agreement
agreed No    
R5‑200071 Removal of technical content in 36.579-4 v13.1.0 and substitution with pointer to the next Release ETSI Secretariat CR Agreement
7.1Pointer CRs
Yes
Yesblock agreed during email agreement
agreed No    
R5‑200072 Removal of technical content in 36.903 v14.3.0 and substitution with pointer to the next Release ETSI Secretariat CR Agreement
7.1Pointer CRs
Yes
Yesblock agreed during email agreement
agreed No    
R5‑200073 Removal of technical content in 36.905 v15.4.0 and substitution with pointer to the next Release ETSI Secretariat CR Agreement
7.1Pointer CRs
Yes
Yesblock agreed during email agreement
agreed No    
R5‑200074 Removal of technical content in 37.571-1 v15.5.0 and substitution with pointer to the next Release ETSI Secretariat CR Agreement
7.1Pointer CRs
Yes
Yesblock agreed during email agreement
agreed No    
R5‑200075 Removal of technical content in 37.571-2 v15.5.0 and substitution with pointer to the next Release ETSI Secretariat CR Agreement
7.1Pointer CRs
Yes
Yesblock agreed during email agreement
agreed No    
R5‑200076 Removal of technical content in 37.571-3 v15.5.0 and substitution with pointer to the next Release ETSI Secretariat CR Agreement
7.1Pointer CRs
Yes
Yesblock agreed during email agreement
agreed No    
R5‑200077 Removal of technical content in 37.571-4 v14.4.0 and substitution with pointer to the next Release ETSI Secretariat CR Agreement
7.1Pointer CRs
Yes
Yesblock agreed during email agreement
agreed No    
R5‑200078 Removal of technical content in 37.571-5 v15.5.0 and substitution with pointer to the next Release ETSI Secretariat CR Agreement
7.1Pointer CRs
Yes
Yesblock agreed during email agreement
agreed No    
R5‑200079 Editorial update RRCRelease Ericsson CR Agreement
6.3.2.1TS 38.508-1
Yes
Yescoversheet revision.
revised No R5‑200940  
R5‑200080 Editorial update RRCResumeComplete Ericsson CR Agreement
6.3.2.1TS 38.508-1
Yes
Yescoversheet revision.
revised No R5‑200941  
R5‑200081 Editorial update RRCSetup Ericsson CR Agreement
6.3.2.1TS 38.508-1
Yes
Yescoversheet revision.
revised No R5‑200942  
R5‑200082 Update RRCSystemInfoRequest Ericsson CR Agreement
6.3.2.1TS 38.508-1
Yes
YesR&S: The proposal from the TF160 manager would be to move to Rel-16 Jun 2020 baseline in Aug as part of 20wk32 ATS release? Please consider deferring these changes until the baseline move is planned, i.e for next May meeting. Coversheet revision.
revised No R5‑201174  
R5‑200083 Editorial update SCGFailureInformation Ericsson CR Agreement
6.3.2.1TS 38.508-1
Yes
Yescoversheet revision.
revised No R5‑200943  
R5‑200084 Correction to Inter-frequency Cell reselection test case 6.1.2.20 Keysight Technologies UK Ltd, Huawei, HiSilicon CR Agreement
6.3.2.4.2Idle Mode (Clause 6)
Yes
Yesr1 was produced.
revised No R5‑201208  
R5‑200085 Correction to NR Idle mode test case 6.1.2.9 Keysight Technologies UK Ltd, Huawei, HiSilicon CR Agreement
6.3.2.4.2Idle Mode (Clause 6)
Yes
Yesr1 was produced. Merged R5-200689. • Merged R5-200689 • Added the delays for FR2 • Added a note explaining the delay calculations
revised No R5‑201209  
R5‑200086 Correction to NR MAC test case 7.1.1.1.2 Keysight Technologies UK Ltd CR Agreement
6.3.2.4.3.1.2MAC
Yes
Yesr1 was produced. • Added back the existing spec text which was removed without track change. • Clarified the text in Step 5 to distinguish the frame numbers for FR1 FDD, FR1 TDD and FR2.
revised No R5‑201210  
R5‑200087 Correction to NR RLC test case 7.1.2.2.6 Keysight Technologies UK Ltd CR Agreement
6.3.2.4.3.1.3RLC
Yes
Yesr1 was produced.
revised No R5‑201211  
R5‑200088 Correction to NR PDCP test case 7.1.3.4.1 Keysight Technologies UK Ltd CR Agreement
6.3.2.4.3.1.4PDCP
Yes
Yesmerged into R5-200252.
withdrawn Yes    
R5‑200089 Correction to NR SDAP test case 7.1.4.2 Keysight Technologies UK Ltd CR Agreement
6.3.2.4.3.1.5SDAP
Yes
Yescoversheet revision.
revised No R5‑201001  
R5‑200090 Correction to NR RRC test case 8.1.1.4.1 Keysight Technologies UK Ltd CR Agreement
6.3.2.4.4.1.1RRC Connection Management Procedures (clause 8.1.1)
Yes
Yesr2 was produced.
revised No R5‑201212  
R5‑200091 Correction to NR RRC test case 8.1.1.3.3 Keysight Technologies UK Ltd CR Agreement
6.3.2.4.4.1.1RRC Connection Management Procedures (clause 8.1.1)
No
Yeslate doc
withdrawn Yes    
R5‑200092 Correction to NR5GC IRAT test case 8.1.3.2.1 Keysight Technologies UK Ltd CR Agreement
6.3.2.4.4.1.3RRC Measurement Configuration Control and Reporting (clause 8.1.3)
Yes
Yesr1 was produced. • Used the condition NR_MEAS in Table 8.1.3.2.1.3.3-1, removed the 2 newly added tables. This is to specify the same contents in a more compact way. • Updated the conformance requirement to remove gapFR1 and gapFR2 references as it is not needed
revised No R5‑201213  
R5‑200093 Correction to NR5GC IRAT test case 8.1.4.2.1.1 Keysight Technologies UK Ltd CR Agreement
6.3.2.4.4.1.4RRC Handover (clause 8.1.4)
Yes
Yesr1 was produced. r2 was produced.• Corrected the indentations of the IEs in Table 8.1.4.2.1.1.3.3-1 • Corrected the value of targetRAT-MessageContainer to align with core specifications
revised No R5‑201215  
R5‑200094 Correction to EN-DC RRC test cases 8.2.3.8.1a and 8.2.3.8.1b Keysight Technologies UK Ltd CR Agreement
6.3.2.4.4.2.3RRC Measurement / Handovers (clause 8.2.3)
Yes
Yesmerged into R5-200619.
withdrawn Yes    
R5‑200095 Correction to 5GMM test case 9.1.2.1 Keysight Technologies UK Ltd CR Agreement
6.3.2.4.5.2MM Security mode control / Identification & Generic UE configuration update (clauses 9.1.2 / 9.1.3 & 9.1.4)
No
Yeslate doc
withdrawn Yes    
R5‑200096 Correction to 5GMM test case 9.1.5.1.8 Keysight Technologies UK Ltd CR Agreement
6.3.2.4.5.3MM Registration & De-registration (clauses 9.1.5 & 9.1.6)
Yes
Yescoversheet revision.
revised No R5‑201002  
R5‑200097 Correction to 5GMM test case 9.1.5.2.1 Keysight Technologies UK Ltd CR Agreement
6.3.2.4.5.3MM Registration & De-registration (clauses 9.1.5 & 9.1.6)
Yes
Yes
withdrawn Yes    
R5‑200098 Correction to NR5GC test case 9.1.6.1.2 Keysight Technologies UK Ltd CR Agreement
6.3.2.4.5.3MM Registration & De-registration (clauses 9.1.5 & 9.1.6)
Yes
Yesmerged into Huawei's R5-200207.
withdrawn Yes    
R5‑200099 Editorial update SecurityMode Ericsson CR Agreement
6.3.2.1TS 38.508-1
Yes
Yes
revised No R5‑200944  
R5‑200100 Correction to NR RLC test case 7.1.2.3.7 Keysight Technologies UK Ltd CR Agreement
6.3.2.4.3.1.3RLC
Yes
Yesmerged into R&S R5-200220r1.
withdrawn Yes    
R5‑200101 ECID test cases deleted for NR Test Configuration B up to and including LPP Rel-15 Spirent Communications CR Agreement
6.3.2.16TS 37.571-2
Yes
Yescoversheet revision.
revised No R5‑201010  
R5‑200102 Applicabilities for ECID signalling test cases deleted for NR Test Configuration B Spirent Communications CR Agreement
6.3.2.17TS 37.571-3
Yes
Yescoversheet revision.
revised No R5‑201011  
R5‑200103 Update of the Note 1 in the Power level and satellite allocation tables for the Sensitivity Coarse time assistance requirements and tests for E-UTRA and NR. Spirent Communications CR Agreement
5.5.9TS 37.571-1
Yes
Yesout of scope of e-meeting, Spirent agreed to withdraw
withdrawn Yes    
R5‑200104 Update SystemInformation Ericsson CR Agreement
6.3.2.1TS 38.508-1
Yes
Yescoversheet revision.
revised No R5‑200945  
R5‑200105 Corrections to IMS test case 22.2 ROHDE & SCHWARZ, Qualcomm CR Agreement
6.5.6.1TS 34.229-1
Yes
Yesr1 was produced. r2 was produced. Meeting header.
revised No R5‑201120  
R5‑200106 Editorial update UEAssistanceInformation Ericsson CR Agreement
6.3.2.1TS 38.508-1
Yes
Yescoversheet revision.
revised No R5‑200946  
R5‑200107 Editorial update UECapability Ericsson CR Agreement
6.3.2.1TS 38.508-1
Yes
Yescoversheet revision.
revised No R5‑200947  
R5‑200108 Correction to NR5GC RRC test case 8.1.3.1.2 Keysight Technologies UK Ltd CR Agreement
6.3.2.4.4.1.3RRC Measurement Configuration Control and Reporting (clause 8.1.3)
Yes
Yesr1 was produced. • Reverted the change to remove reportQuantityCell in Table 8.1.3.1.2.3.3-4 based on MCC TF160 comment. • Updated Table 8.1.3.1.2.3.3-1 to specify it in a more compact way with the usage of NR_MEAS condition
revised No R5‑201214  
R5‑200109 Correction to NR PDCP test case 7.1.3.5.3 Keysight Technologies UK Ltd CR Agreement
6.3.2.4.3.1.4PDCP
Yes
Yescoversheet revision.
revised No R5‑201000  
R5‑200110 Editorial update ULInformation Ericsson CR Agreement
6.3.2.1TS 38.508-1
Yes
Yescoversheet revision.
revised No R5‑200948  
R5‑200111 Editorial update IE PUSCH-TimeDomainResourceAllocationList Ericsson CR Agreement
6.3.2.1TS 38.508-1
Yes
Yesr1 was produced. Samsung: The CR does not follow the PRD13 recommendations on how to specify multiple entries in a SEQUENCE.
revised No R5‑201122  
R5‑200112 Editorial update IE RLC-BearerConfig Ericsson CR Agreement
6.3.2.1TS 38.508-1
Yes
Yescoversheet revision.
revised No R5‑200949  
R5‑200113 Editorial update IE PUCCH-Config Ericsson CR Agreement
6.3.2.1TS 38.508-1
Yes
Yescoversheet revision. Samsung disagreed: The off-line discussion related to the CR suggesting alignment of how RRC 'SEQUENCE of structures (e.g. IEs)' are defined in 38.508-1. The suggested alignment however contradicts what we have in PRD13 on this topic which has already been used in multiple places in TS 38.508-1 and what we use in TS 38.508. For reference, this is the so called in 38.508-1 one or many "entries" which in PRD13 are referred to as "pools/records" and are addressed in subclause 7.2.1.5 introductory text, and, Example 3. We still have many places in 38.508-1 where RRC messages are defined in a way contradicting PRD13. Samsung suggests to raise an AP for the next meeting (RAN5#87) for an update of 38.508 to comply with PRD13: AP#86.03: Align TS 38.508-1 RRC IE/messages definitions with the PRD13 rule on "How to specify SEQUENCE of structures (e.g. IEs); the so called one or many "entries/pools/records" as specified in subclause 7.2.1.5 text and Example 3. If necessary, update PRD13 with more examples clarifying the rule. On: Samsung, Ericsson, TF160
revised No R5‑200950  
R5‑200114 Update IE MeasObjectNR Ericsson CR Agreement
6.3.2.1TS 38.508-1
Yes
Yes
withdrawn Yes    
R5‑200115 Updates of test parameter for MOP and Spurious co-existence NTT DOCOMO, INC. CR Agreement
5.3.2.6.1Tx Requirements (Clause 6)
Yes
YesRelated/Conflicted CRs (0400, 0447) are still under discussion however this CR is covered by the other CRs in any case.
withdrawn Yes    
R5‑200116 On testability issue for FR2 NTT DOCOMO, INC. discussion Endorsement
5.3.2.17Discussion Papers / Work Plan / TC lists
Yes
Yesr1 was produced. Concrete relaxation value is proposed according to submissions in this e-meeting.
revised No R5‑201034  
R5‑200117 Review on test point for FR1 TRx NTT DOCOMO, INC. discussion Endorsement
5.3.2.17Discussion Papers / Work Plan / TC lists
No
Yes
withdrawn Yes    
R5‑200118 Test Tolerance of Band n259 NTT DOCOMO, INC. discussion Endorsement
5.3.14.10Discussion Papers / Work Plan / TC lists
Yes
Yesr1 was produced. Proposed MU and Ratio values are updated based on the contributions for RAN5#86-e (0316, 0736, 0816). r2 was produced. Addressing Apple's concern, Wisuit’s concern, NOTE for NTC (Normal Temperature Condition) is added.
revised No R5‑201035  
R5‑200119 Updated WF on Band n259 NTT DOCOMO, INC. discussion Endorsement
5.3.14.10Discussion Papers / Work Plan / TC lists
No
YesLate document to capture endorsements during RAN5#86. Updated (Revised) WF will be applied based on the existing WF endorsed in previous meeting (R5-198071).
withdrawn Yes    
R5‑200120 Update IE RLF-TimersAndConstants Ericsson CR Agreement
6.3.2.1TS 38.508-1
Yes
Yessee R5-200082. Coversheet revision.
revised No R5‑201175  
R5‑200121 Update IE SCS-SpecificCarrier Ericsson CR Agreement
6.3.2.1TS 38.508-1
Yes
Yessee R5-200082. Coversheet revision.
revised No R5‑201176  
R5‑200122 Add IE TDD-UL-DL-ConfigDedicated Ericsson CR Agreement
6.3.2.1TS 38.508-1
Yes
Yescoversheet revision.
revised No R5‑200951  
R5‑200123 Update chapter 4.6.0 Ericsson CR Agreement
6.3.2.1TS 38.508-1
Yes
Yesr1 was produced. Condition names rephrased. r2 was produced. Based on R&S's comment Table name and explanation rephrased. Coversheet revision.
revised No R5‑201177  
R5‑200124 Update IE ServingCellConfigCommon Ericsson CR Agreement
6.3.2.1TS 38.508-1
Yes
Yesr1 was produced. Comments from TF160 manager. ssb-PositionsInBurst update postponed to next mtg. Comments from R&S, Motorola Mobility. r2 was produced. Condition explanation updated. TF160: update to No_UL definition. Coversheet revision.
revised No R5‑201178  
R5‑200125 Update IE ServingCellConfig Ericsson CR Agreement
6.3.2.1TS 38.508-1
Yes
Yescoversheet revision. TF160: Update to No_UL definition. r1 was produced. Condition explanation updated.
revised No R5‑200952  
R5‑200126 Update IE ServingCellConfigCommonSIB Ericsson CR Agreement
6.3.2.1TS 38.508-1
Yes
Yescoversheet revision.
revised No R5‑200953  
R5‑200127 Update IE DMRS-DownlinkConfig Ericsson CR Agreement
6.3.2.1TS 38.508-1
Yes
Yescoversheet revision.
revised No R5‑200954  
R5‑200128 Update IE FrequencyInfoUL Ericsson CR Agreement
6.3.2.1TS 38.508-1
Yes
Yescoversheet revision.
revised No R5‑200955  
R5‑200129 Update IE MeasObjectNR Ericsson CR Agreement
6.3.2.1TS 38.508-1
Yes
Yes
withdrawn Yes    
R5‑200130 Update IE MeasObjectNR Ericsson CR Agreement
6.3.2.1TS 38.508-1
Yes
Yessee R5-200082. Coversheet revision.
revised No R5‑201179  
R5‑200131 Update IE TDD-UL-DL-Config Ericsson CR Agreement
6.3.2.1TS 38.508-1
Yes
YesTF160 manager: With this CR, you are changing the TDD UL/DL configuration in a significant way. It has a big impact on the SIG test model and on all the TDD SIG test case verifications done to date. The initial TDD-UL-DL-ConfigCommon configuration was provided by NTT DOCOMO in R5-187669 at RAN5#81, and we believe it is technically correct. So we do not agree to your CR in its current form. Qualcomm agreed to this. r1 was produced. SIG and RF specific values added. SCS condition rephrased.
revised No R5‑201173  
R5‑200132 Corrections to NSSAI Test messages Qualcomm Technologies Int CR Agreement
6.3.2.3TS 38.509
Yes
Yes
withdrawn Yes    
R5‑200133 Update chapter 4.5.1 General Ericsson CR Agreement
6.3.2.1TS 38.508-1
Yes
Yescoversheet revision. TF160 disagreed: - to the addition of the new row “Split”. In our opinion it is unnecessary because we already have the Bearers->”MCG(s) and split” that can be used for that purpose. - In the (flagged) e-mail thread on this CR, our questions have remained unanswered by the CR author. - At the start of RAN5#86-e meeting it had been agreed by the RAN5 Leadership that CRs on NR-DC were in scope, “condition being included are they can be agreed without any contentious discussion”. I believe this criteria is not fulfilled here. - Underlying procedures/default messages for use of the split option are still FFS at the end of RAN5#86-e, so there is no urgency at RAN5#86-e to conclude on the ‘split’ aspect of R5-200133. - Beyond the addition of the ‘Split’ row, which is the contentious point, the rest of the R5-200133 is editorial. We can continue discussions on whether and how to update 38.508-1 subclause 4.5.1 up to and at RAN5#87. First withdrawn, then agreed.
revised No R5‑200956  
R5‑200134 Update chapter 4.5.4 RRC_CONNECTED Ericsson CR Agreement
6.3.2.1TS 38.508-1
Yes
Yes
withdrawn Yes    
R5‑200135 Removal of Correction to SIG OTA UE Orientation procedure ETSI CR Agreement
6.3.2.1TS 38.508-1
Yes
Yes
agreed No    
R5‑200136 Update IE CellGroupConfig Ericsson CR Agreement
6.3.2.1TS 38.508-1
Yes
Yesr1 was produced. TF160 disagreed. r2 was produced.
revised No R5‑201222  
R5‑200137 Update chapter 4.5.4 RRC_CONNECTED Ericsson CR Agreement
6.3.2.1TS 38.508-1
Yes
Yescoversheet revision.
revised No R5‑200957  
R5‑200138 Updates to NR FR1 and LTE Power levels in OTA ANRITSU LTD CR Agreement
6.3.2.1TS 38.508-1
Yes
Yesr1 was produced. Based on feedback from TF160, the revision includes additional changes to consider LTE OTA uncalibrated link in case of NR5GC and editorial updates.
revised No R5‑201092  
R5‑200139 Correction to PUCCH-Config for Format1 and Format2 ANRITSU LTD CR Agreement
6.3.2.1TS 38.508-1
Yes
Yescoversheet revision.
revised No R5‑200996  
R5‑200140 Update IE CellGroupId Ericsson CR Agreement
6.3.2.1TS 38.508-1
Yes
Yescoversheet revision. r1 was produced. Condition to add SCG (NR-DC) rephrased based on comments received from MCC TF160.
revised No R5‑200958  
R5‑200141 Update IE ServCellIndex Ericsson CR Agreement
6.3.2.1TS 38.508-1
Yes
Yescoversheet revision. r1 was produced. Condition to add SCG (NR-DC) rephrased Based on the comments received from MCC TF160. r2 was produced. Editorial.
revised No R5‑200959  
R5‑200142 Update IE SK-Counter Ericsson CR Agreement
6.3.2.1TS 38.508-1
Yes
Yescoversheet revision.
revised No R5‑200960  
R5‑200143 Update IE SDAP-Config Ericsson CR Agreement
6.3.2.1TS 38.508-1
Yes
Yescoversheet revision. TF160 disagreed: when we run an NR-DC test case, defaultDRB will be set to false for all DRBs. This is technically incorrect. Later TF160 commented that the wording “at most” seems to enable such configuration, and agreed.
revised No R5‑200961  
R5‑200144 Correction to EN-DC RRC Test case 8.2.3.2.1 ANRITSU LTD CR Agreement
6.3.2.4.4.2.3RRC Measurement / Handovers (clause 8.2.3)
Yes
Yescoversheet revision.
revised No R5‑200997  
R5‑200145 TP and format updated for TS 38.522 Bureau Veritas, CMCC, Ericsson, Huawei, ROHDE & SCHWARZ, Sporton, Qualcomm, CAICT CR Agreement
5.3.2.8TS 38.522
Yes
Yesr1 was produced. Based on the outcome of R5-200046 discussion. r2 was produced. - updated D004 to include n65; - removed PC2 standalone TC based on R5-200396 CR outcome; - RRM TC branch condition updated; - Completed SA FR1 TCs removed NOTE 1 r3 was produced. - summary change of 10 included for TS38.521-3 completed TCs; - Removed TS38.521-3 NOTE 5 for non LTE anchor agnostic TCs; - removed HPUE condition since no longer needed; - TS38.521-3 TC 7.6B.3.3 and 7.7B.3 are not completed yet, NOTE1 is added; - summary change of 11 included for TS38.521-4 completed TCs; - More completed SUL list in TS38.521-1
revised No R5‑201036  
R5‑200146 Update to PDCP-Config MediaTek Inc. CR Agreement
6.3.2.1TS 38.508-1
Yes
Yesdiscussion with Mediatek and TF160. Ericsson disagreed. r1 was produced. TF160 agreed. new condition added for split SRB.
revised No R5‑201203  
R5‑200147 Update to USIM config 6.4.1-11 MediaTek Inc. CR Agreement
6.3.2.1TS 38.508-1
Yes
Yes
agreed No    
R5‑200148 Correction to test case 6.1.1.6 MediaTek Inc. CR Agreement
6.3.2.4.2Idle Mode (Clause 6)
Yes
Yes
agreed No    
R5‑200149 Correction to test case 6.4.2.1 MediaTek Inc. CR Agreement
6.3.2.4.2Idle Mode (Clause 6)
Yes
Yesmerged into R5-200176.
withdrawn Yes    
R5‑200150 Correction to test case 8.1.3.1.16 MediaTek Inc. CR Agreement
6.3.2.4.4.1.3RRC Measurement Configuration Control and Reporting (clause 8.1.3)
Yes
Yes
agreed No    
R5‑200151 Update to test case 8.2.2.2.1 MediaTek Inc. CR Agreement
6.3.2.4.4.2.2RRC Radio Bearer (clause 8.2.2)
Yes
Yesr1 was produced. - corrected SRB2->SRB1 - checking properly that RRC message has been duplicated in UL on split SRB: o Added separate steps to stop and re-start RLC ACK on split SRB o Added a not to clarify that the UE RLC might re-transmit the UL RRC PDUs (with RRC messages) while DL RLC ACK is stopped r2 was produced. - align the name of the condition in table 8.2.2.2.1.3.3-5 with CR1254 (R5-200146)
revised No R5‑201204  
R5‑200152 Update to test case 8.2.2.3.1 MediaTek Inc. CR Agreement
6.3.2.4.4.2.2RRC Radio Bearer (clause 8.2.2)
No
Yes
withdrawn Yes    
R5‑200153 Correction to NBIOT testcase 22.5.7b ROHDE & SCHWARZ CR Agreement
6.4.3.11Others (TS 36.523-1 clauses not covered by other AIs under AI 6.4.3 / e.g. eMBMS / Home (e)NB / MBMS in LTE / D2D / SC-PTM / NB-IoT / CIoT...)
Yes
Yescl aff.! r1 was produced.
revised No R5‑201205  
R5‑200154 Corrections to SSNITZ test cases ROHDE & SCHWARZ CR Agreement
6.5.4.1TS 34.123-1
Yes
Yes
agreed No    
R5‑200155 Correction to test case 9.1.7.2 MediaTek Inc. CR Agreement
6.3.2.4.5.4MM Service Request (clause 9.1.7)
Yes
Yesmerged into R5-200209.
withdrawn Yes    
R5‑200156 Update of RAN5_PRD13va0 Samsung R&D Institute India other Approval
7.2.3Other open issues from joint sessions - original A.I. retained
Yes
Yes
approved No    
R5‑200157 Discussion paper on NR test frequencies for PCells to achieve full bandwidth testing of NR bands Ericsson discussion Endorsement
4.2.15GS
Yes
YesAll proposals accepted. r1 was produced. Based on comments from Rohde & Schwarz. The changes is editorial to correct duplicated clause numbers and the associated references in the discussion paper.
revised No R5‑201004  
R5‑200158 Update of Annex C on calculation of test frequencies to achieve full bandwidth testing of NR bands Ericsson CR Agreement
6.3.2.1TS 38.508-1
Yes
Yesr1 was produced. r2 was produced. Additional comments from R&S. 1. Corrected formulas for High range test frequencies (missing opening paranthese in the Floor function) 2. Corrected formulas for UL test frequencies (FTx-Rx_separation to be substracted from associated DL test freqeuncy not added); and updated description for parameter FTx-Rx_separation to not refer to TS 38.101-2, clause 5.4.4 as the clause does not exist in TS 38.101-2 (all FR2 bands are TDD Bands for which FTx-Rx_separation = 0).
revised No R5‑201005  
R5‑200159 FR2 RRM MU and choice of test cases to evaluate ANRITSU LTD discussion Endorsement
5.3.2.17Discussion Papers / Work Plan / TC lists
Yes
Yesr1 was produced.
revised No R5‑201155  
R5‑200160 FR2 TT analysis for 38.533 5.7.1.1+7.7.1.1 Intra-freq SS-RSRP ANRITSU LTD discussion Endorsement
5.3.2.17Discussion Papers / Work Plan / TC lists
Yes
Yesnoted and proposals endorsed
noted No    
R5‑200161 FR2 TT analysis for 38.533 5.7.1.2+7.7.1.2 Inter-freq SS-RSRP ANRITSU LTD discussion Endorsement
5.3.2.17Discussion Papers / Work Plan / TC lists
Yes
Yesnoted and proposals endorsed
noted No    
R5‑200162 Correction to 5GC TC 10.1.3.2 CAICT CR Agreement
6.3.2.4.6.2SM Network-requested PDU session modification & release (clauses 10.1.2 & 10.1.3)
Yes
Yesr1 was produced.
revised No R5‑201107  
R5‑200163 Add Annex A.2 handling of common Test Tolerance Topics for FR2 ANRITSU LTD CR Agreement
5.3.2.15TR 38.903 ((NR MU & TT analyses)
Yes
Yes
agreed No    
R5‑200164 Correction to NR TC 6.1.1.1-PLMN selection with Automatic mode Huawei, HiSilicon, Datang Linktester, CATT CR Agreement
6.3.2.4.2Idle Mode (Clause 6)
Yes
Yesr1 was produced. Correct the reference generic procedure for registration. r2 was produced. Correct conditional branches and their steps numbering according to comments from Samsung.
revised No R5‑201206  
R5‑200165 Correction to NR TC 6.1.1.2-PLMN selection of Other PLMN Huawei, HiSilicon, Datang Linktester, CATT CR Agreement
6.3.2.4.2Idle Mode (Clause 6)
Yes
Yesr1 was produced. Editorial changes.
revised No R5‑201125  
R5‑200166 Correction to NR TC 6.1.1.4-PLMN selection in shared network environment with Automatic mode Huawei, HiSilicon, Datang Linktester, CATT CR Agreement
6.3.2.4.2Idle Mode (Clause 6)
Yes
Yesr1 was produced.
revised No R5‑201126  
R5‑200167 Correction to NR TC 6.1.1.5-PLMN selection with Automatic mode and user reselection Huawei, HiSilicon, Datang Linktester, CATT CR Agreement
6.3.2.4.2Idle Mode (Clause 6)
Yes
Yestitle: no user resel.! r1 was produced. Motorola Mobility: The only way forward to make progress looks we need to allow both Rel-15 and Rel-16 behavior, this being an e-meeting. If RAN5 feels necessary, an LS to CT1 can be drafted, and continue discussion in RAN5 in RAN5#87. The branching can be done based on 5GS registration type in Registration Request, no need to define a PICS. r2 was produced. Correct the reference generic procedure for registration. RAN5 Chair: Thanks for finding a way forward by catering for both Rel-15 and Rel-16 behaviours in the test definition and implementation. This is a common practice followed in RAN5 when core spec makes clarification/improvement of core requirements in a later release (in this case Rel-16) version of the spec but leaves older version (in this case Rel-15) as it is. It is important from RAN5 perspective to make sure conformant UE doesn’t incorrectly fail a conformance test case applied in certification. From what we understand CT1 didn’t update Rel-15 version as it wasn’t deemed as an essential correction rather as an improvement/optimization, so we have to assume no interoperability issues in expected in real network operation. Unlike in the case of RAN Groups where explicit statement about improvement/optimization in later release to be allowed in earlier release is captured in the CR cover page or meeting minutes, CT1 doesn’t follow this practice. However it is widely understood and expected device may implement later release behaviour which should be catered by the network. Based on this there wouldn't be a compelling reason to send a LS to CT1 on this topic. Needs more discussion. r3 was produced. Correct conditional branches and their steps numbering according to comments from Samsung. Mediatek suggested to assign an action point for RAN5#87 to update affected test cases and make sure that Rel-16 UEs follow the Rel-16 spec.
revised No R5‑201127  
R5‑200168 Correction to NR TC 6.1.1.6-Periodic PLMN reselection with MinimumPeriodicSearchTimer Huawei,Hisilicon CR Agreement
6.3.2.4.2Idle Mode (Clause 6)
Yes
Yesr1 was produced. Correct the PLMN settings and coversheet. Already taken care of by Samsung’s CR R5-200225.
revised No R5‑201003  
R5‑200169 Correction to NR TC 6.1.2.21-Cell reselection Huawei,Hisilicon CR Agreement
6.3.2.4.2Idle Mode (Clause 6)
Yes
Yesupdate cover page
revised No R5‑201112  
R5‑200170 Correction to NR TC 6.1.2.22-Inter frequency cell reselection based on common priority information Huawei, HiSilicon, Datang Linktester, CATT CR Agreement
6.3.2.4.2Idle Mode (Clause 6)
Yes
Yesr1 was produced. WIC _ r2 was produced. Reason for change.
revised No R5‑201128  
R5‑200171 Correction to NR TC 6.2.3.2-Inter-RAT cell reselection L2N Huawei,Hisilicon CR Agreement
6.3.2.4.2Idle Mode (Clause 6)
Yes
Yesr1 was produced. Cover. r2 was produced. Add NOTE at step 11 to align with R5-200790r1.
revised No R5‑201129  
R5‑200172 Correction to NR TC 6.2.3.5-Inter-RAT cell reselection N2L by dedicated signalling Huawei,Hisilicon CR Agreement
6.3.2.4.2Idle Mode (Clause 6)
Yes
Yesr1 was produced. WIC _ r2 was produced.
revised No R5‑201130  
R5‑200173 Correction to NR TC 6.2.3.6-Inter-RAT cell reselection Huawei,Hisilicon CR Agreement
6.3.2.4.2Idle Mode (Clause 6)
Yes
Yesr1 was produced. Add NOTE at step 3 to align with R5-200790r1.
revised No R5‑201131  
R5‑200174 Correction to NR TC 6.2.3.8-Inter-RAT cell reselection L2N Snonintrasearch Huawei,Hisilicon CR Agreement
6.3.2.4.2Idle Mode (Clause 6)
Yes
Yesr1 was produced. Add NOTE at step 2 to align with R5-200790r1.
revised No R5‑201132  
R5‑200175 Correction to NR TC 6.2.3.9-Speed Dependent Cell Reselection N2L Huawei,Hisilicon CR Agreement
6.3.2.4.2Idle Mode (Clause 6)
Yes
Yes
agreed No    
R5‑200176 Correction to NR TC 6.4.2.1-Inactive-Reselection Huawei, HiSilicon, StarPoint, MediaTek CR Agreement
6.3.2.4.2Idle Mode (Clause 6)
Yes
Yesr1 was produced.
revised No R5‑201133  
R5‑200177 Correction to NR TC 7.1.1.1.4-Beam Failure Huawei,Hisilicon CR Agreement
6.3.2.4.3.1.2MAC
Yes
Yesr1 was produced. r2 was produced. 1. RLM-RS is explicitly configured in Table 7.1.1.1.4.3.3-7 to simplify message contents. 2. Configuration of PDCCH TCI-state is removed from PDCCH-Config in step 8 and 17 to simplify message contents. 3. Typos are corrected.
revised No R5‑201134  
R5‑200178 Correction to NR TC 7.1.1.9.1-MAC reset Huawei,Hisilicon CR Agreement
6.3.2.4.3.1.2MAC
Yes
YesMotorola Mobility: the proposed change is not needed, rather will pass a non-conformant UE.
withdrawn Yes    
R5‑200179 Correction to NR TC 8.1.1.3.1-Redirection Huawei,Hisilicon CR Agreement
6.3.2.4.4.1.1RRC Connection Management Procedures (clause 8.1.1)
Yes
Yesr1 was produced. r2 was produced. • Index of DRB and PDU session are changed to the more generic description; • Message contents are updated accordingly.
revised No R5‑201135  
R5‑200180 Correction to NR TC 8.1.1.3.3-With priority information of NR Cell Huawei,Hisilicon CR Agreement
6.3.2.4.4.1.1RRC Connection Management Procedures (clause 8.1.1)
Yes
Yesr1 was produced. r2 was produced. Set the NR Cell 3 power level as -94 dB. • Power level for NR Cell 3 and Cell 6 in T1/T2 is updated according to comments received; r3 was produced. • Test steps are renumbered. • Formats are corrected. • Index of DRB and PDU session is updated for sake of generality. • RadioBearerConfig and CellGroupConfig in table Table 8.1.1.3.3.3.3-5 are updated accordingly
revised No R5‑201136  
R5‑200181 Correction to NR TC 8.1.1.3.4-With priority information of LTE Cell Huawei,Hisilicon CR Agreement
6.3.2.4.4.1.1RRC Connection Management Procedures (clause 8.1.1)
Yes
Yesr1 was produced. Data path verification for NR cell is added. TF160/Keysight: expected you to add the IP check when the UE moves back to the NR cell during the expected sequence -i.e. after step 5. I don't think there's any need to add the check before the UE moves anywhere. r2 was produced. r3 was produced??????????
revised No R5‑201137  
R5‑200182 Correction to NR TC 8.1.2.1.2-uplinkTxDirectCurrentList Huawei,Hisilicon CR Agreement
6.3.2.4.4.1.2RRC Reconfiguration (clause 8.1.2)
Yes
Yes
agreed No    
R5‑200183 Correction to NR TC 8.1.3.3.1-NR CGI Huawei,Hisilicon CR Agreement
6.3.2.4.4.1.3RRC Measurement Configuration Control and Reporting (clause 8.1.3)
Yes
Yesr1 was produced. 1. resultsSSB-Cell for serving cell in step 7 is set to Not Checked. 2. reportConfigId for CGI report is corrected.
revised No R5‑201138  
R5‑200184 Correction to NR TC 8.1.3.3.2-LTE CGI Huawei,Hisilicon CR Agreement
6.3.2.4.4.1.3RRC Measurement Configuration Control and Reporting (clause 8.1.3)
Yes
Yesr1 was produced. resultsSSB-Cell for serving cell in step 7 is set to Not Checked.
revised No R5‑201139  
R5‑200185 Correction to NR TC 8.1.4.1.6-Handover Failure Huawei, HiSilicon, StarPoint CR Agreement
6.3.2.4.4.1.4RRC Handover (clause 8.1.4)
Yes
Yes
agreed No    
R5‑200186 Correction to NRTC 8.1.4.1.7.1-PCell Change and SCell addition Intra-band Contiguous CA Huawei,Hisilicon CR Agreement
6.3.2.4.4.1.4RRC Handover (clause 8.1.4)
Yes
Yesr1 was produced. r2 was produced. discussion with TF160. r3 was produced. • sCellConfigDedicated is explictly configured in Table 8.1.4.1.7.1.3.3-4 to avoid clash with other CRs according to the comments from TF160; r4 was produced. • Data path verification on SCell is removed; • Test steps and message contents are updated accordingly.
revised No R5‑201140  
R5‑200187 Correction to NR TC 8.1.4.1.8.1-SCell no change Intra-band Contiguous CA Huawei,Hisilicon CR Agreement
6.3.2.4.4.1.4RRC Handover (clause 8.1.4)
Yes
Yes
agreed No    
R5‑200188 Correction to NR TC 8.1.4.2.2.1-L2N Handover Huawei,Hisilicon CR Agreement
6.3.2.4.4.1.4RRC Handover (clause 8.1.4)
Yes
Yes
agreed No    
R5‑200189 Correction to NR TC 8.2.1.1.1-UE Capability Huawei,Hisilicon CR Agreement
6.3.2.4.4.2.1RRC UE Capability / Others (clause 8.2.1)
Yes
Yesr1 was produced.
revised No R5‑201141  
R5‑200190 Correction to ENDC TC 8.2.2.2.1-Split SRB Huawei,Hisilicon CR Agreement
6.3.2.4.4.2.2RRC Radio Bearer (clause 8.2.2)
Yes
YesSTF160 offline comments.
withdrawn Yes    
R5‑200191 Correction to ENDC TC 8.2.2.3.1-SRB3 and Split SRB Huawei,Hisilicon CR Agreement
6.3.2.4.4.2.2RRC Radio Bearer (clause 8.2.2)
Yes
YesSTF160 offline comments.
withdrawn Yes    
R5‑200192 Correction to NR TC applicaibility-Split SRB Huawei,Hisilicon CR Agreement
6.3.2.5TS 38.523-2
Yes
Yesr1 was produced. 1. Comment column in test case table for TC 8.2.2.2.1 and 8.2.2.3.1 is also corrected, Thanks to TF160 manager's comments. 2. It is found that UL CA related capability is needed for TC 8.1.4.1.7.1/2/3 during the email discussion with TF160/Keysight, So I also use R5-200192 to capture the needed changes of Test case Selection Expression for TC 8.1.4.1.7.1/2/3 Need more discussion. r2 was produced. • Undone the changes to TC 8.1.4.1.7.1/2/3 is removed since there is mismatch with the CR title according to comments from TF160; r4 was produced? Motorola Mobility and TF160 agreed.
revised No R5‑201147  
R5‑200193 Correction to SS-RSRPB reporting Huawei,Hisilicon CR Agreement
6.3.2.3TS 38.509
No
Yes
withdrawn Yes    
R5‑200194 Correction to NR TC PICs Huawei,Hisilicon CR Agreement
6.3.2.2TS 38.508-2
Yes
Yesr1 was produced. 1. Change to to the name of PIC pc_pusch_256QAM_FR1 is cancelled, and its Implementation Capabilities is changed to “Support 256QAM for PUSCH for at least one NR FR1 band” 2. A new PIC pc_pusch_256QAM_FR2 is added to cover FR2 case.
revised No R5‑201123  
R5‑200195 Correction to NR TC 9.1.1.1-EAP-AKA related procedures Huawei,Hisilicon CR Agreement
6.3.2.4.5.1MM Primary authentication and key agreement (clause 9.1.1)
Yes
Yes
agreed No    
R5‑200196 Correction to NR TC 9.1.1.2-Authentication Reject Huawei,Hisilicon, ZTE CR Agreement
6.3.2.4.5.1MM Primary authentication and key agreement (clause 9.1.1)
Yes
Yesr1 was produced. Merged R5-200747 into it after discussion with ZTE. r2 was produced. r3 was produced.
revised No R5‑201142  
R5‑200197 Correction to NR TC 9.1.1.6-5G AKA abnormal Huawei,Hisilicon CR Agreement
6.3.2.4.5.1MM Primary authentication and key agreement (clause 9.1.1)
Yes
Yesr1 was produced. Offline discussion with Samsung.
revised No R5‑201084  
R5‑200198 Correction to NR TC 9.1.2.2-Initial NAS msg ciphering Huawei,Hisilicon CR Agreement
6.3.2.4.5.2MM Security mode control / Identification & Generic UE configuration update (clauses 9.1.2 / 9.1.3 & 9.1.4)
Yes
Yesr1 was produced. Included discussion result with TF160.
revised No R5‑201085  
R5‑200199 Correction to NR TC 9.1.4.1-Generic UE configuration update Huawei,Hisilicon CR Agreement
6.3.2.4.5.2MM Security mode control / Identification & Generic UE configuration update (clauses 9.1.2 / 9.1.3 & 9.1.4)
Yes
Yesr1 was produced. Add NR-4 to be broardcasted. Add step 48A to Release RRC connection. r2 was produced. Change for incorporating both initial and mobile registration. r3 was produced. Changed the branch description and step numbering according to Samsung's comments.
revised No R5‑201143  
R5‑200200 Correction to NR TC 9.1.5.1.2-Equivalent PLMN list handling Huawei,Hisilicon, Keysight CR Agreement
6.3.2.4.5.3MM Registration & De-registration (clauses 9.1.5 & 9.1.6)
Yes
Yesr1 was produced. Incorporated discussion result with TF160.
revised No R5‑201086  
R5‑200201 Correction to NR TC 9.1.5.1.3-Registration Request NSSAI Huawei,Hisilicon CR Agreement
6.3.2.4.5.3MM Registration & De-registration (clauses 9.1.5 & 9.1.6)
No
Yes
withdrawn Yes    
R5‑200202 Correction to NR TC 9.1.5.1.3a-Valid USIM NSSAI Huawei,Hisilicon CR Agreement
6.3.2.4.5.3MM Registration & De-registration (clauses 9.1.5 & 9.1.6)
No
Yes
withdrawn Yes    
R5‑200203 Correction to NR TC 9.1.5.1.9-Change of cell into a new tracking area Huawei, HiSilicon, CATT, MCC TF160, StartPoint CR Agreement
6.3.2.4.5.3MM Registration & De-registration (clauses 9.1.5 & 9.1.6)
Yes
Yesr1 was produced. Offline discussions. Comments from Samsung about TC title, step 1 Cell B to be 'Non-suitable cell', and step 29, not checking here RRC. Qualcomm was removed. r3 was produced. Change the description of RRCReconfiguration-HO and add related message contents.
revised No R5‑201087  
R5‑200204 Correction to NR TC 9.1.5.1.14-RegisterReject 22 and T3346 Huawei,Hisilicon, ZTE CR Agreement
6.3.2.4.5.3MM Registration & De-registration (clauses 9.1.5 & 9.1.6)
Yes
Yesr1 was produced. Comments from TF160/Keysight and Samsung about how to test that a registration is for Emergency services. Need more discussion.
revised No R5‑201144  
R5‑200205 Correction to NR TC 9.1.5.2.2-Periodic Register T3512 Huawei,Hisilicon CR Agreement
6.3.2.4.5.3MM Registration & De-registration (clauses 9.1.5 & 9.1.6)
Yes
Yes
agreed No    
R5‑200206 Correction to NR TC 9.1.5.2.8-Registration Reject 10 Huawei,Hisilicon CR Agreement
6.3.2.4.5.3MM Registration & De-registration (clauses 9.1.5 & 9.1.6)
Yes
Yes
agreed No    
R5‑200207 Correction to NR TC 9.1.6.1.2-UE initialed deregistration procedure Huawei, HiSilicon, Datang Linktester, CATT, Keysight CR Agreement
6.3.2.4.5.3MM Registration & De-registration (clauses 9.1.5 & 9.1.6)
Yes
Yesr1 was produced. Merged Keysight's R5-200098.
revised No R5‑201145  
R5‑200208 Correction to NR TC 9.1.6.1.3-Deregistration in new TA Huawei, HiSilicon, Starpoint, Qualcomm CR Agreement
6.3.2.4.5.3MM Registration & De-registration (clauses 9.1.5 & 9.1.6)
Yes
YesQualcomm's R5-200582 was merged into.
agreed No    
R5‑200209 Correction to NR TC 9.1.7.2-Service Request Huawei, HiSilicon, Datang Linktester, CATT, MediaTek, MCC TF160 CR Agreement
6.3.2.4.5.4MM Service Request (clause 9.1.7)
Yes
Yesr1 was produced. Merged Mediatek's R5-200155 and comments from TF160. r2 was produced. Changed DRB 1 to DRB n according to comments from TF160/Keysight.
revised No R5‑201088  
R5‑200210 Correction to NR TC 9.1.8.1-SMS Huawei,Hisilicon, MCC TF160 CR Agreement
6.3.2.4.5.5MM SMS Over NAS (clause 9.1.8)
Yes
Yesr1 was produced. We merge R5-200255 after discussion with MCC TF160.
revised No R5‑201089  
R5‑200211 Correction to NR TC 9.3.1.1-5GC to EPC Huawei,Hisilicon CR Agreement
6.3.2.4.5.6Inter-system Mobility (clause 9.3)
Yes
Yes
agreed No    
R5‑200212 Correction to NR TC 9.3.1.2-Inter-system mobility registration update EPC to 5GC Huawei,Hisilicon CR Agreement
6.3.2.4.5.6Inter-system Mobility (clause 9.3)
Yes
Yesr1 was produced. Change to align with latest R5-200790.
revised No R5‑201200  
R5‑200213 Correction to NR TC 10.1.1.1-Authentication during PDU establish Huawei,Hisilicon CR Agreement
6.3.2.4.6.1SM PDU session authentication and authorization (clause 10.1.1)
Yes
Yes
agreed No    
R5‑200214 Correction to NR TC 10.1.1.2-Authentication after PDU establish Huawei,Hisilicon CR Agreement
6.3.2.4.6.1SM PDU session authentication and authorization (clause 10.1.1)
Yes
Yes
agreed No    
R5‑200215 Correction to NR TC 10.1.2.2-PDU modify Huawei,Hisilicon CR Agreement
6.3.2.4.6.2SM Network-requested PDU session modification & release (clauses 10.1.2 & 10.1.3)
Yes
YesR5-200417 covers everything.
withdrawn Yes    
R5‑200216 Correction to NR TC 10.1.4.1-T3580 Huawei,Hisilicon CR Agreement
6.3.2.4.6.3SM UE-requested PDU session establishment / modification & release (clauses 10.1.4 / 10.1.5 & 10.1.6)
Yes
Yesr2 was produced. r3 was produced?
revised No R5‑201146  
R5‑200217 Addition of NR TC 11.3.1-UAC AI0 MTSI MO speech call SMSoIP Uplink data transfer Huawei,Hisilicon CR Agreement
6.3.2.4.8.3Unified Access Control (UAC)
No
Yes
withdrawn Yes    
R5‑200218 Addition of NR TC 11.3.5-UAC AI1 AC5 MMTEL Video call Huawei,Hisilicon CR Agreement
6.3.2.4.8.3Unified Access Control (UAC)
No
Yes
withdrawn Yes    
R5‑200219 Addition of NR TC 11.3.9-UAC Operator Defined Access Category Huawei,Hisilicon CR Agreement
6.3.2.4.8.3Unified Access Control (UAC)
Yes
YesRapporteur: is not an immediate priority.
withdrawn Yes    
R5‑200220 Correction to NR RLC testcase 7.1.2.3.7 ROHDE & SCHWARZ, TF160, Qualcomm CR Agreement
6.3.2.4.3.1.3RLC
Yes
Yesr1 was produced. Comments from TF160 and Qulacomm added as co-source r1 updates Steps 10 /step 36 /39 to clarify the UL grant bits. r2 was produced.
revised No R5‑201153  
R5‑200221 Correction to NR RLC testcase 7.1.2.3.10 ROHDE & SCHWARZ, Qualcomm CR Agreement
6.3.2.4.3.1.3RLC
Yes
Yes
agreed No    
R5‑200222 Correction to test case 8.2.4.3 for CAT-M1 UEs ROHDE & SCHWARZ CR Agreement
6.4.3.3.2RRC Part 2 (clause 8.2)
Yes
Yes
agreed No    
R5‑200223 Correction to TC 6.3.4.4 Aggregate power tolerance LG Electronics CR Agreement
5.3.2.5.1Tx Requirements (Clause 6)
Yes
Yesr1 was produced. Offline discussion with Ericsson. r2 was produced. - Alignment to latest Core Spec - The scheduling pattern is modified in figure 6.3.4.4.4.2-1 for RAN4 alignment(R4-2000003). - The power window is modified in test procedure from E///’s comments.
revised No R5‑200894  
R5‑200224 Introduction of New TC 6.4A.2.3.2 In-band emissions for 3UL CA LG Electronics CR Agreement
5.3.2.5.1Tx Requirements (Clause 6)
No
Yes
withdrawn Yes    
R5‑200225 Adding generic test parameters references and updating subclause 5 Samsung, MCC TF160 CR Agreement
6.3.2.4.1Clauses 1 - 5
Yes
Yesr1 was produced. Typo.
revised No R5‑201031  
R5‑200226 Adding core specs to section References Samsung CR Agreement
6.3.2.4.1Clauses 1 - 5
Yes
Yes
agreed No    
R5‑200227 Corrections to IMS Emergency Services TC 11.4.1 Samsung CR Agreement
6.3.2.4.8.4Emergency Services
Yes
Yes
agreed No    
R5‑200228 Update to IMS Emergency Services TC 11.4.1 for adding new TPs Samsung CR Agreement
6.3.2.4.8.4Emergency Services
Yes
Yesr1 was produced. Comments from TFC160 for a possible improvement of the step sequence to avoid a redundant from the TP's point of view set up and release of the IMS emergency call.
revised No R5‑201032  
R5‑200229 Corrections to IMS Emergency Services TC 11.4.2 Samsung, MCC TF160 CR Agreement
6.3.2.4.8.4Emergency Services
Yes
Yes
agreed No    
R5‑200230 Corrections to IMS Emergency Services TC 11.4.4 Samsung CR Agreement
6.3.2.4.8.4Emergency Services
Yes
Yes
agreed No    
R5‑200231 Update of TC 11.4.4 5G Emergency Services to add a new TP Samsung CR Agreement
6.3.2.4.8.4Emergency Services
Yes
Yesr1 was produced. Comments from R&S for the need of improvement of the text in one of the steps.
revised No R5‑201033  
R5‑200232 Corrections to IMS Emergency Services TC 11.4.6 Samsung CR Agreement
6.3.2.4.8.4Emergency Services
Yes
Yes
agreed No    
R5‑200233 Introduction of new TC 11.4.7 Handling of Local and extended emergency numbers / Mobility Samsung CR Agreement
6.3.2.4.8.4Emergency Services
Yes
Yes
agreed No    
R5‑200234 Introduction of new TC 11.4.8 Handling of Local and extended emergency numbers / Switch-off and maximum local numbers storage Samsung CR Agreement
6.3.2.4.8.4Emergency Services
Yes
Yes
agreed No    
R5‑200235 Adding and modifying test applicability IMS Emergency Services Samsung CR Agreement
6.3.2.5TS 38.523-2
Yes
Yes
agreed No    
R5‑200236 Update of RAN5_PRD18v20 Samsung other Approval
7.2.3Other open issues from joint sessions - original A.I. retained
Yes
Yes
approved No    
R5‑200237 Addition of Rel-16 inter-band CA and EN-DC FR1 two bands test configurations CMCC, Huawei, Hisilicon, Ericsson, CATT CR Agreement
7.2.1RF group docs still requiring WG verdict/confirmation - original A.I. retained
Yes
Yesr1 was produced.
revised No R5‑200921  
R5‑200238 GCF 3GPP TCL after GCF CAG#61 Ericsson other Information
2.2General Reports for information
Yes
Yes
noted No    
R5‑200239 Correction to SS-RSRPB reporting Huawei,Hisilicon CR Agreement
7.2.2Sig group docs still requiring WG verdict/confirmation - original A.I. retained
Yes
Yesr1 was produced. R&S disagreed: You are justifying the update of the definition of UE SS-RSRPB per receiver branch reporting by that RAN1 has received an LS from RAN4. However, in the current version of TS 38.215 (V16.0.1) the definition has not been updated. Thus, agreeing to your CR will create a misalignment between RAN1 and RAN5 specifications. Can you clarify if there is an agreed RAN1 CR to TS 38.215 capturing the update of the definition, please? If such a CR is not existing, it is premature to update the definition UE SS-RSRPB per receiver branch in RAN5 specification since RAN5 cannot anticipate decision of RAN1. Qualcomm also disagreed. RAN1 has not yet updated 38.215 spec with the changes proposed. r2 was produced. Need more discussion. r3 was produced. Qualcomm and R&S agreed.
revised No R5‑201124  
R5‑200240 Addition of applicability for test cases Huawei,Hisilicon CR Agreement
6.3.2.5TS 38.523-2
Yes
YesAddtion depending from R5-200219.
withdrawn Yes    
R5‑200241 Discussion of ambiguity of Ninfo in TBS calculation Huawei,Hisilicon discussion Approval
4.2.15GS
Yes
YesQualcomm and Motorola Mobility commented. Huawei: prefer to go with option 2 a little bit if this is not too difficult for TTCN implementation. By option 1, strictly speaking we don’t have a full TBS test, and we don’t know when RAN1 can make a choice, that may need a long time. ZTE: The following conclusion made in last RAN1 meeting clearly states that there is no consensus in RAN1 to address this issue in Rel-15. Conclusion On the issue of ambiguity with regards to the definition of N_info, there is no consensus in RAN1 to make specificiation change in Rel-15. For further discussion on whether to fix this in Rel-16 In the RAN1 email reflector, RAN1 is discussing whether the CR R1-2000558 should be treated in the upcoming e-meeting. The proposal from the Chair is not to treat this issue in this e-meeting because of the above RAN1 conclusion. " Issue #26(R1-2000558, Nokia): Based on the comments so far, I propose we do not take this issue for email discussion." And RAN2 also has no plan to define any mechanism to report UE behavior on it. So from our understanding, it is a proper assumption to assume that a real network will skip the "abnormal" cases by implementation. Therefore, we support Option 1 ( skip the specific TBS size) so that it is more aligned with this assumption. RAN5 Chair: no consensus on a way forward. There seems to be the following views expressed to date: 1. Wait for RAN1 to conclude at their current e-meeting and revisit this topic again in RAN5#87. 2. Accept and proceed with option 1 - skip the specific TBS size Will be postponed to the next RAN5#87 meeting. Impact on TC 7.1.1.4.2.3. ->proposal for RAN5 to go ahead with Option 1: skip the specific TBS size. Conclusion: RAN5 accepted the solution 'skip the specific TBS size'. Proponents to submit CRs to RAN5#87 meeting to introduce this solution into test specifications. TTCN implementation shall be dependent on prose update.
noted No    
R5‑200242 Correction to NR TC 6.1.2.4-Cell Reselection for interband operation Huawei, HiSilicon, Datang Linktester, CATT CR Agreement
6.3.2.4.2Idle Mode (Clause 6)
Yes
Yesupdate cover page
revised No R5‑201113  
R5‑200243 Correction to NR TC 6.1.2.5-Cell reselection for interband operation Between FDD and TDD Huawei,Hisilicon CR Agreement
6.3.2.4.2Idle Mode (Clause 6)
Yes
Yesupdate cover page
revised No R5‑201114  
R5‑200244 Correction to nAndPagingFrameOffset ROHDE & SCHWARZ CR Agreement
6.3.2.1TS 38.508-1
Yes
Yes
agreed No    
R5‑200245 Feature priority inputs for the RAN5 5GS work plan MCC TF160 discussion Information
4.2.15GS
Yes
Yeslate doc. Ericsson: defer until RAN5#87? Conclusion: Noted with information collected to be used for 5GS Phase planning.
noted No    
R5‑200246 RAN5 PRD12 version 6.2 MCC TF160 other Approval
7.2.3Other open issues from joint sessions - original A.I. retained
Yes
Yes
approved No    
R5‑200247 Updates to default SSB index of intra-frequency NR cells MCC TF160 CR Agreement
6.3.2.1TS 38.508-1
Yes
Yesr1 was produced. The SSB Index for NR Cell 489 (used only by RRM) is changed from 1 to 0. The reason for this change is that we have RRM measurement accuracy tests, where the two intra-frequency cells are NR Cell 1 and NR Cell 489. We would need to have different Cell Indexes in these two. Since NR Cell 1 has SSB Index 1 and is used also by SIG, changing NR Cell 489 is easier.
revised No R5‑201148  
R5‑200248 Update to NR MAC test case 7.1.1.1.5 MCC TF160 CR Agreement
6.3.2.4.3.1.2MAC
Yes
Yesr1 was produced. The trigger for the UE to start the Random Access procedure has been simplified to be solely based on SR-TransMax being reached. r2 was produced. Removed the note from step 5 that had been added in r1, upon request from Motorola Mobility.
revised No R5‑201149  
R5‑200249 Corrections to NR RLC test case 7.1.2.3.6 MCC TF160 CR Agreement
6.3.2.4.3.1.3RLC
No
Yeslate doc not needed
withdrawn Yes    
R5‑200250 Corrections to NR RLC test case 7.1.2.3.8 MCC TF160 CR Agreement
6.3.2.4.3.1.3RLC
Yes
Yes
agreed No    
R5‑200251 Enhancement of NR PDCP test cases 7.1.3.1.x MCC TF160 CR Agreement
6.3.2.4.3.1.4PDCP
Yes
YesNR PDCP missing. r1 was produced. Removed requirement of sending a PDCP PDUSs in MAC PDU is out of the scope of the test purpose. CR title aligned with 3GU.
revised No R5‑201218  
R5‑200252 Corrections to NR PDCP test case 7.1.3.4.1 MCC TF160, Qualcomm, Keysight CR Agreement
6.3.2.4.3.1.4PDCP
Yes
Yesr1 was produced. Keysight CR R5-200088 has been merged into this CR.
revised No R5‑201219  
R5‑200253 Corrections to EN-DC test case 8.2.2.3.1 MCC TF160 CR Agreement
6.3.2.4.4.2.2RRC Radio Bearer (clause 8.2.2)
Yes
Yes
agreed No    
R5‑200254 Corrections to 5GC test case 9.1.5.1.1 MCC TF160 CR Agreement
6.3.2.4.5.3MM Registration & De-registration (clauses 9.1.5 & 9.1.6)
Yes
Yes
agreed No    
R5‑200255 Corrections to 5GC test case 9.1.8.1 MCC TF160 CR Agreement
6.3.2.4.5.5MM SMS Over NAS (clause 9.1.8)
Yes
Yesmerged into R5-200210r1
withdrawn Yes    
R5‑200256 5G Test Models updates MCC TF160 CR Agreement
6.3.2.6TS 38.523-3
Yes
Yesr1 was produced. R5-200244 (Correction to nAndPagingFrameOffset) has got impact
revised No R5‑201150  
R5‑200257 IMS over NR/5GC: Initial Test Model MCC TF160 CR Agreement
6.3.2.9TS 34.229-3
Yes
Yes
agreed No    
R5‑200258 Routine maintenance for TS 36.523-3 MCC TF160 CR Agreement
6.4.5Routine Maintenance for TS 36.523-3
Yes
Yes
agreed No    
R5‑200259 Corrections to SMS test case 18.1b MCC TF160 CR Agreement
6.5.6.1TS 34.229-1
Yes
Yes
agreed No    
R5‑200260 Routine maintenance for TS 34.229-3 MCC TF160 CR Agreement
6.5.6.3TS 34.229-3
Yes
YesComment from R&S.
agreed No    
R5‑200261 Routine maintenance for TS 37.571-4 MCC TF160 CR Agreement
6.5.7.3TS 37.571-4
Yes
Yes
agreed No    
R5‑200262 Editorial changes to TS 37.571-X titles to remove references to individual RATs MCC TF160 (Rapporteur) CR Agreement
6.5.7.3TS 37.571-4
Yes
Yes
agreed No    
R5‑200263 Corrections to MCPTT UE registration procedures MCC TF160 CR Agreement
6.5.9.1TS 36.579-1
Yes
Yesr1 was produced. Editorial corrections to comply to RAN5 PRD13, following review comments from Samsung.
revised No R5‑201220  
R5‑200264 Corrections to default SIP message and other information elements MCC TF160 CR Agreement
6.5.9.1TS 36.579-1
Yes
Yes
agreed No    
R5‑200265 Addition of further references MCC TF160 CR Agreement
6.5.9.1TS 36.579-1
Yes
Yes
agreed No    
R5‑200266 Addition of further references MCC TF160 CR Agreement
6.5.9.2TS 36.579-2
Yes
Yes
agreed No    
R5‑200267 Corrections to MCPTT test case 5.1 MCC TF160 CR Agreement
6.5.9.2TS 36.579-2
Yes
Yesr1 was produced. Test case main behaviour table has been updated following review comments from Samsung.
revised No R5‑201151  
R5‑200268 Routine maintenance for TS 36.579-5 MCC TF160 CR Agreement
6.5.9.5TS 36.579-5
Yes
Yesr1 was produced.
revised No R5‑201152  
R5‑200269 Correction to SS-RSRPB REPORT RESPONSE ROHDE & SCHWARZ CR Agreement
6.3.2.3TS 38.509
Yes
Yesalready covered in R5-200239 from Huawei,Hisilicon
withdrawn Yes    
R5‑200270 Correction to NSSAI DELETE REQUEST ROHDE & SCHWARZ, Qualcomm CR Agreement
6.3.2.3TS 38.509
Yes
Yesr1 was produced.
revised No R5‑201207  
R5‑200271 Update to Demod TC 5.2.3.2.1_1 Qualcomm Technologies Int CR Agreement
5.3.2.7.1Conducted Demod Performance and CSI Reporting Requirements (Clauses 5&6)
Yes
Yes
agreed No    
R5‑200272 Test tolerance analysis inter-frequency SS-RSRP and intra-frequency SS-SINR ROHDE & SCHWARZ CR Agreement
5.3.2.15TR 38.903 ((NR MU & TT analyses)
Yes
Yesr1 was produced. r2 was produced?
revised No R5‑201037  
R5‑200273 Test tolerance analysis SS-RSRQ and inter-frequency SS-SINR ROHDE & SCHWARZ CR Agreement
5.3.2.15TR 38.903 ((NR MU & TT analyses)
Yes
Yesdifferent title: inter-frequency SS-RSRP!!! r1 was produced. r2 was produced?
revised No R5‑201038  
R5‑200274 Test tolerance update inter-frequency SS-RSRP NSA ROHDE & SCHWARZ CR Agreement
5.3.2.9.1EN-DC with all NR cells in FR1 (Clause 4)
Yes
Yesr1 was produced.
revised No R5‑201039  
R5‑200275 Test tolerance update intra-frequency SS-RSRQ NSA ROHDE & SCHWARZ CR Agreement
5.3.2.9.1EN-DC with all NR cells in FR1 (Clause 4)
Yes
Yesr1 was produced. Correction in the Highest allowed reported value for Test 3 for NC and EC, as pointed out by Ericsson as part of the TT analysis review.
revised No R5‑201040  
R5‑200276 Test tolerance update inter-frequency SS-RSRQ NSA ROHDE & SCHWARZ CR Agreement
5.3.2.9.1EN-DC with all NR cells in FR1 (Clause 4)
Yes
Yesr1 was produced. RAN4 dependent: R4-2001373. for email agreement Email agreed.
agreed No    
R5‑200277 Test tolerance update intra-frequency SS-SINR NSA ROHDE & SCHWARZ CR Agreement
5.3.2.9.1EN-DC with all NR cells in FR1 (Clause 4)
Yes
Yes
agreed No    
R5‑200278 Test tolerance update inter-frequency SS-SINR NSA ROHDE & SCHWARZ CR Agreement
5.3.2.9.1EN-DC with all NR cells in FR1 (Clause 4)
Yes
Yes
agreed No    
R5‑200279 Test tolerance update inter-frequency SS-RSRP SA ROHDE & SCHWARZ CR Agreement
5.3.2.9.3NR Standalone in FR1 (Clause 6)
Yes
Yes
agreed No    
R5‑200280 Test tolerance update intra-frequency SS-RSRQ SA ROHDE & SCHWARZ CR Agreement
5.3.2.9.3NR Standalone in FR1 (Clause 6)
Yes
Yesr1 was produced. Correction in the Highest allowed reported value for Test 3 for NC and EC, as pointed out by Ericsson as part of the TT analysis review.
revised No R5‑201041  
R5‑200281 Test tolerance update inter-frequency SS-RSRQ SA ROHDE & SCHWARZ CR Agreement
5.3.2.9.3NR Standalone in FR1 (Clause 6)
Yes
Yes
agreed No    
R5‑200282 Test tolerance update intra-frequency SS-SINR SA ROHDE & SCHWARZ CR Agreement
5.3.2.9.3NR Standalone in FR1 (Clause 6)
Yes
Yes
agreed No    
R5‑200283 Test tolerance update inter-frequency SS-SINR SA ROHDE & SCHWARZ CR Agreement
5.3.2.9.3NR Standalone in FR1 (Clause 6)
Yes
Yes
agreed No    
R5‑200284 Test tolerance update measurement tests Annex F ROHDE & SCHWARZ CR Agreement
5.3.2.9.6Clauses 1-3 / Annexes
Yes
YesRAN4 dependency R4-2001565 for email agreement Email agreed.
agreed No    
R5‑200285 Updates on inter-band EN-DC configurations for test frequencies in FR1 and FR2 in 38.508-1 NTT DOCOMO INC. CR Agreement
7.2.1RF group docs still requiring WG verdict/confirmation - original A.I. retained
Yes
Yes+FR1 . Agreed. After the meeting CMCC commented that most of the band combos are inactive. Withdrawn.
withdrawn Yes    
R5‑200286 Update TS38.508-2 Table A.4.3.2B.2.3.12-1 CGC Inc. CR Agreement
4.5.2Sig group docs for WG review/verdict - original A.I. retained
No
Yeslate doc
withdrawn Yes    
R5‑200287 Update TS38.522 Table 4.1.2-1a CGC Inc. CR Agreement
5.3.2.8TS 38.522
Yes
Yesalready considered in the TS38.522 jumbo CR R5-2000145.
withdrawn Yes    
R5‑200288 PRD-17 on Guidance to Work Item Codes, version 3.19 (post RAN#87-e version) Rapporteur (BlackBerry) other Approval
7.3iWD/PRD Updates
No
Yespost meeting doc
noted No    
R5‑200289 TS 36.523-1 Status before RAN5#86-e Rapporteur (BlackBerry) other Information
6.4.6Discussion Papers / Work Plan / TC lists
Yes
Yes
noted No    
R5‑200290 TS 36.523-1 Status after RAN5#86-e Rapporteur (BlackBerry) other Information
6.4.6Discussion Papers / Work Plan / TC lists
No
Yespost meeting doc.
postponed No    
R5‑200291 Addition of new test case 8.11.1.2.3.2, TDD PDSCH 2 Tx Antenna Port supporting wideband transmission for UE category M2 Ericsson CR Agreement
5.3.4.2TS 36.521-1
Yes
Yes
agreed No    
R5‑200292 Addition of new test case 8.11.1.2.3.2_1, TDD PDSCH 2 Tx Antenna Port supporting wideband transmission for UE category M2 (CEModeB) Ericsson CR Agreement
5.3.4.2TS 36.521-1
Yes
Yes
agreed No    
R5‑200293 WP UE Conformance Test Aspects – Further enhanced MTC for LTE Ericsson Work Plan Information
7.4.2Active Work Items/ Study Item: work plans (wp) / status reports (sr) / Work Item Descriptions (wid)
Yes
Yes
noted No    
R5‑200294 SR UE Conformance Test Aspects – Further enhanced MTC for LTE Ericsson WI status report Information
7.4.2Active Work Items/ Study Item: work plans (wp) / status reports (sr) / Work Item Descriptions (wid)
Yes
Yes
noted No    
R5‑200295 Updates to condition for UEs indicating support of N1 Ericsson CR Agreement
6.3.2.11TS 36.508
Yes
Yestypo RR5!
revised No R5‑201008  
R5‑200296 Addition of generic procedure for IMS MO speech setup Ericsson CR Agreement
6.3.2.1TS 38.508-1
Yes
Yes
agreed No    
R5‑200297 Addition of generic procedure for IMS MT speech setup Ericsson CR Agreement
6.3.2.1TS 38.508-1
Yes
Yes
agreed No    
R5‑200298 Addition of generic procedure for IMS MO call release Ericsson CR Agreement
6.3.2.1TS 38.508-1
Yes
Yes
agreed No    
R5‑200299 Addition of generic procedure for IMS MT call release Ericsson CR Agreement
6.3.2.1TS 38.508-1
Yes
Yes
agreed No    
R5‑200300 Adding test case 8.11.1.2.3.2 and 8.11.1.2.3.2_1 to applicability Ericsson CR Agreement
5.3.4.3TS 36.521-2
Yes
Yesr1 was produced. Based on comment by R&S, C316y has been introduced in Table 4.1-1a. r2 was produced. Comment for test case 8.11.1.2.3.2 is corrected.
revised No R5‑200991  
R5‑200301 Corrections to default HTTP message and other information elements MCC TF160 CR Agreement
6.5.9.1TS 36.579-1
Yes
Yes
agreed No    
R5‑200302 Correction of applicability of L1-RSRP measurements for beam reporting test cases Ericsson CR Agreement
5.3.2.8TS 38.522
Yes
Yesmerged to R5-200145.
withdrawn Yes    
R5‑200303 Test Tolerance analysis for CSI-RS-Based L1-RSRP measurement test cases Ericsson CR Agreement
5.3.2.15TR 38.903 ((NR MU & TT analyses)
Yes
Yeswrong WIC or AI???? r1 was produced. Several corections. This CR is RAN4 dependant. r3 was produced. includes further editorial corrections of .xls.
revised No R5‑201042  
R5‑200304 Test Tolerance analysis for SSB-Based L1-RSRP measurement test cases Ericsson CR Agreement
5.3.2.15TR 38.903 ((NR MU & TT analyses)
Yes
Yeswrong WIC or AI? r1 was produced. Several corections. This CR is RAN4 dependant. r2 was produced. includes further editorial corrections of .xls.
revised No R5‑201043  
R5‑200305 Test Tolerance and Measurement Uncertainty in Annex F for L1-RSRP measurement test cases Ericsson CR Agreement
5.3.2.9.6Clauses 1-3 / Annexes
Yes
Yesr1 was produced. Changes after offline discussion with the TT reviewing company (Anritsu) affect also annex F.
revised No R5‑201044  
R5‑200306 Reference SSB configuration correction Ericsson CR Agreement
5.3.2.9.6Clauses 1-3 / Annexes
Yes
Yes
agreed No    
R5‑200307 Correction of Cell configuration mapping table for SA FR2 RRM Ericsson CR Agreement
5.3.2.9.6Clauses 1-3 / Annexes
Yes
YesRAN4 dependency R4-2001396 and R4-2001398 for email agreement Email agreed.
agreed No    
R5‑200308 Correction of RRM Test Case 4.6.3.1 including FR1 Test Tolerance Ericsson CR Agreement
5.3.2.9.1EN-DC with all NR cells in FR1 (Clause 4)
Yes
Yesr1 was produced. Changes after offline discussion with the TT reviewing company (Anritsu). Changes are related to correction of applied offset to Es/Noc. r2 was produced.
revised No R5‑201045  
R5‑200309 Correction of RRM Test Case 4.6.3.2 including FR1 Test Tolerance Ericsson CR Agreement
5.3.2.9.1EN-DC with all NR cells in FR1 (Clause 4)
Yes
Yesr1 was produced. Changes after offline discussion with the TT reviewing company (Anritsu). Changes are related to correction of applied offset to Es/Noc. r2 was produced.
revised No R5‑201046  
R5‑200310 Correction of RRM Test Case 4.6.3.3 including FR1 Test Tolerance Ericsson CR Agreement
5.3.2.9.1EN-DC with all NR cells in FR1 (Clause 4)
Yes
Yesr1 was produced. Changes after offline discussion with the TT reviewing company (Anritsu). Changes are related to correction of applied offset to Es/Noc. r2 was produced.
revised No R5‑201047  
R5‑200311 Correction of RRM Test Case 4.6.3.4 including FR1 Test Tolerance Ericsson CR Agreement
5.3.2.9.1EN-DC with all NR cells in FR1 (Clause 4)
Yes
Yesr1 was produced. Changes after offline discussion with the TT reviewing company (Anritsu). Changes are related to correction of applied offset to Es/Noc. This CR is RAN4 dependant. r2 was produced.
revised No R5‑201048  
R5‑200312 Correction of RRM Test Case 6.6.4.1 including FR1 Test Tolerance Ericsson CR Agreement
5.3.2.9.3NR Standalone in FR1 (Clause 6)
Yes
Yesr1 was produced. Changes after offline discussion with the TT reviewing company (Anritsu). Changes are related to correction of applied offset to Es/Noc. CR is RAN4 dependant. r2 was produced.
revised No R5‑201049  
R5‑200313 Correction of RRM Test Case 6.6.4.2 including FR1 Test Tolerance Ericsson CR Agreement
5.3.2.9.3NR Standalone in FR1 (Clause 6)
Yes
Yesr1 was produced. Changes after offline discussion with the TT reviewing company (Anritsu). Changes are related to correction of applied offset to Es/Noc. r2 was produced.
revised No R5‑201050  
R5‑200314 Correction of RRM Test Case 6.6.4.3 including FR1 Test Tolerance Ericsson CR Agreement
5.3.2.9.3NR Standalone in FR1 (Clause 6)
Yes
Yesr1 was produced. Changes after offline discussion with the TT reviewing company (Anritsu). Changes are related to correction of applied offset to Es/Noc. r2 was produced.
revised No R5‑201051  
R5‑200315 Correction of RRM Test Case 6.6.4.4 including FR1 Test Tolerance Ericsson CR Agreement
5.3.2.9.3NR Standalone in FR1 (Clause 6)
Yes
Yes36.533 typo. weird bar. r1 was produced. Changes after offline discussion with the TT reviewing company (Anritsu). Changes are related to correction of applied offset to Es/Noc. r2 was produced.
revised No R5‑201052  
R5‑200316 On AP#85.28: n259 MU Estimate Keysight Technologies UK Ltd discussion Endorsement
5.3.2.17Discussion Papers / Work Plan / TC lists
Yes
YesNoted. Any agreeable aspects were consolidated in R5-200118. noted no proposals endorsed
noted No    
R5‑200317 On Beam Peak Searches for different test configurations Keysight Technologies UK Ltd discussion Endorsement
5.3.2.17Discussion Papers / Work Plan / TC lists
Yes
Yes"This contribution addresses the need to perform TX and RX beam peak searches for different test configurations document out of scope scope of e-meeting , no associated CR KEYS agreed to withdraw"
withdrawn Yes    
R5‑200318 CDF/PDF Scaling Factor Keysight Technologies UK Ltd discussion Endorsement
5.3.2.17Discussion Papers / Work Plan / TC lists
Yes
Yesnoted and proposals endorsed
noted No    
R5‑200319 CR to 38.521-2 on CDF/PDF Scaling Factor Keysight Technologies UK Ltd CR Agreement
5.3.2.5.3Clauses 1-5 / Annexes
Yes
Yes
agreed No    
R5‑200320 CR to 38.521-2: Correction to TRP grid Keysight Technologies UK Ltd CR Agreement
5.3.2.5.3Clauses 1-5 / Annexes
Yes
Yes
agreed No    
R5‑200321 NR FR2 Demodulation MU Table Keysight Technologies UK Ltd discussion Endorsement
5.3.2.17Discussion Papers / Work Plan / TC lists
Yes
Yesr1 was produced. Offline discussions with Qualcomm, Anritsu, and R&S.
revised No R5‑201156  
R5‑200322 CR to 38.521-4 to introduce isolation procedure Keysight Technologies UK Ltd CR Agreement
5.3.2.7TS 38.521-4
Yes
Yes
agreed No    
R5‑200323 End-to-End System Simulations for Min. Isolation Requirements Keysight Technologies UK Ltd discussion Endorsement
5.3.2.17Discussion Papers / Work Plan / TC lists
Yes
Yesr1 was produced. changes were based on feedback from R&S and Qualcomm.
revised No R5‑201157  
R5‑200324 On PC1 MUs Keysight Technologies UK Ltd discussion Endorsement
5.3.2.17Discussion Papers / Work Plan / TC lists
Yes
Yes"This contribution reviews the MU elements and values for PC1 devices. PC1 FR2 MU out of scope of e-meeting, KEYS agreed to withdraw"
withdrawn Yes    
R5‑200325 On NR FR2 Demodulation MUs Keysight Technologies UK Ltd discussion Endorsement
5.3.2.17Discussion Papers / Work Plan / TC lists
No
Yeslate doc. document not produced before meeting start
withdrawn Yes    
R5‑200326 Quality of Quiet Zone MU and XPD MU for Spurious Emissions Keysight Technologies UK Ltd discussion Endorsement
5.3.2.17Discussion Papers / Work Plan / TC lists
Yes
Yesr1 was produced. Following offline discussions with TE vendors, it was agreed to adopt the QoQZ values proposed in R5-200735 instead.
revised No R5‑200998  
R5‑200327 On the MU Element “Uncertainty of an absolute gain of the calibration antenna” for Spurious Emissions Keysight Technologies UK Ltd discussion Endorsement
5.3.2.17Discussion Papers / Work Plan / TC lists
Yes
Yes
noted No    
R5‑200328 On XPD Verification Keysight Technologies UK Ltd discussion Endorsement
5.3.2.17Discussion Papers / Work Plan / TC lists
Yes
Yes
noted No    
R5‑200329 CR to 38.903 on XPD Verification Keysight Technologies UK Ltd CR Agreement
5.3.2.15TR 38.903 ((NR MU & TT analyses)
Yes
Yes
agreed No    
R5‑200330 On RRM MUs including AP#85.22 Keysight Technologies UK Ltd discussion Endorsement
5.3.2.17Discussion Papers / Work Plan / TC lists
Yes
Yesr1 was produced. With regards to P2, based on additional discussions and feedback received, more time is needed for a framework for 1 AoA TC MUs and whether this should be a function of the 2 AoA test system or not. The goal is to revisit this discussion in the next meeting. Close the official AP#85.22. r2 was produced.
revised No R5‑201053  
R5‑200331 CR to 38.508-1 to introduce DFF Range Length Keysight Technologies UK Ltd CR Agreement
5.3.2.1TS 38.508-1
Yes
Yesno cl. aff. r1 was produced. Comments from R&S for the need of improvement of the text in one of the steps.
revised No R5‑200899  
R5‑200332 CR to 38.521-2 to properly define Link and Meas Angles Keysight Technologies UK Ltd CR Agreement
5.3.2.5TS 38.521-2
Yes
Yesdependent on a RAN4 CR R4-2000198. for email agreement RAN4 CR had to be revised to R4-2002734 to make small editorial changes. Not pursued.
not pursued No    
R5‑200333 Configuring dualConnectivityPHR IE for EN-DC scenarios Qualcomm Technologies Int CR Agreement
7.2.1RF group docs still requiring WG verdict/confirmation - original A.I. retained
Yes
Yesr1 was produced.
revised No R5‑200989  
R5‑200334 Addition of FR2 Demod sustained data rate test case Qualcomm Technologies Int CR Agreement
5.3.2.7.3Interworking Demod Performance and CSI Reporting Requirements (Clauses 9&10)
Yes
Yesr1 was produced. Added editor’s note for pending MU/TT analysis. r2 was produced.
revised No R5‑201180  
R5‑200335 Addition of MU table for FR2 Demod test cases Qualcomm Technologies Int CR Agreement
5.3.2.15TR 38.903 ((NR MU & TT analyses)
No
Yeslate doc Addition of MU table for FR2 Demod scenarios depends on the FR2 MU elements discussion for mode 1/2 Document not produced before meeting start.
withdrawn Yes    
R5‑200336 Update to Common Coreset RB IE and section 5-6 Demod message contents Qualcomm Technologies Int CR Agreement
7.2.1RF group docs still requiring WG verdict/confirmation - original A.I. retained
Yes
Yesoffline discussion among interested companies on moving some of the contents of this Demod CR (R5-200336) to common section of 38.508-1. r1 was produced. Moved the changes related to Common CORESET to section 4 of 38.508-1 instead of just restricting the changes to DEMOD specific section.
revised No R5‑201194  
R5‑200337 Update of clause 5 to TS 38.521-1 in R15 China Unicom CR Agreement
5.3.2.4.3Clauses 1-5 / Annexes
Yes
Yesr1 was produced: Removed band combos n77D/n78D/n79D and n77E/n78E/n79E from Table 5.5A.1-1 to align with core spec TS38.101-1.
revised No R5‑200909  
R5‑200338 Correction to NR TC 6.1.1.3-Cell reselection of ePLMN in manual mode Huawei,Hisilicon CR Agreement
6.3.2.4.2Idle Mode (Clause 6)
Yes
Yes
agreed No    
R5‑200339 Correction to NR TC 6.4.1.2-Cell reselection of ePLMN in manual mode INACTIVE Huawei,Hisilicon CR Agreement
6.3.2.4.2Idle Mode (Clause 6)
Yes
Yes
agreed No    
R5‑200340 Correction to NR TC 6.1.2.18-Cell reselection with parameters Sintrasearch and Snonintrasearch Huawei, HiSilicon, Datang Linktester, CATT CR Agreement
6.3.2.4.2Idle Mode (Clause 6)
Yes
Yesupdate cover page
revised No R5‑201115  
R5‑200341 Correction to NR TC 8.1.3.1.17.1-Event A6 Huawei,Hisilicon CR Agreement
6.3.2.4.4.1.3RRC Measurement Configuration Control and Reporting (clause 8.1.3)
Yes
Yes
agreed No    
R5‑200342 Update of new R16 CADC combos to clause 5 in TS 38.521-1 China Unicom CR Agreement
5.3.10.3.3Clauses 1-5 / Annexes
No
YesCommon part alignment for R16 active CADC combos
withdrawn Yes    
R5‑200343 Update of R16 new bands and CBWs to TS 38.521-1 clause 5 China Unicom CR Agreement
5.3.14.3.3Clauses 1-5 / Annexes
Yes
Yesr1 was produced. Several changes. r2 was produced. Added Note 11 to indicate “this UE channel bandwidth is not applicable in R15” for newly introduced R16 CBW in Table 5.3.5-1.
revised No R5‑201054  
R5‑200344 Corrections to TC 6.3A.3 transmit On OFF time mask for CA FR1 China Unicom CR Agreement
5.3.2.4.1Tx Requirements (Clause 6)
Yes
Yesr1 was produced. The Po_NominalWithGrant should set to -106dBm because only even value for Po_NominalWithGrant is allowed (step size 2) in TS38.311. The associated discussion paper is R5-200478r1.
revised No R5‑200962  
R5‑200345 Correction to NR test case 7.1.2.3.6 Starpoint CR Agreement
6.3.2.4.3.1.3RLC
Yes
Yesr1 was produced. Comments from TF160: Configured default uplink grants in step 14.
revised No R5‑201117  
R5‑200346 Correction to NR test case 8.1.3.2.2 Starpoint CR Agreement
6.3.2.4.4.1.3RRC Measurement Configuration Control and Reporting (clause 8.1.3)
Yes
Yesr1 was produced. Deleted references to gapFR1 and gapFR2 from the conformance requirements to avoid confusion.
revised No R5‑201118  
R5‑200347 Correction to NR test case 8.1.5.2.1 StarPoint, Huawei, HiSilicon CR Agreement
6.3.2.4.4.1.5RRC Others (clause 8.1.5)
Yes
Yes
agreed No    
R5‑200348 Correction to NR test case 9.1.5.2.6 StarPoint, Huawei, HiSilicon CR Agreement
6.3.2.4.5.3MM Registration & De-registration (clauses 9.1.5 & 9.1.6)
Yes
Yesr1 was produced. fix changes over changes.
revised No R5‑201119  
R5‑200349 Correction to frequencyBandList in SIB4 StarPoint, Qualcomm CR Agreement
6.3.2.1TS 38.508-1
Yes
Yes
agreed No    
R5‑200350 Correction to EUTRA-AllowedMeasBandwidth Starpoint,Huawei, HiSilicon CR Agreement
6.3.2.1TS 38.508-1
Yes
Yesr1 was produced. 1. Use a different way to define allowedmeasBandwidth. 2 Modify Table 4.6.3-74 to harmonize. r2 was produced.
revised No R5‑201108  
R5‑200351 Updated to EN-DC band information Rel-16 Bureau Veritas CR Agreement
5.3.10.5.3Clauses 1-5 / Annexes
Yes
Yes
agreed No    
R5‑200352 Correction to NR RRC measurement Test cases 8.1.3.1.13 and 8.1.3.1.14A ANRITSU LTD CR Agreement
6.3.2.4.4.1.3RRC Measurement Configuration Control and Reporting (clause 8.1.3)
Yes
Yescomment from TF160. r1 was produced. editorial change to Table 8.1.3.1.13.3.3-1. r2 was produced.
revised No R5‑201170  
R5‑200353 Correction to 5G RRC test case 8.2.4.3.1 TDIA, CATT CR Agreement
6.3.2.4.4.2.4RRC Carrier Aggregation (clause 8.2.4)
Yes
Yesr1 was produced. Comments from MCC160.
revised No R5‑201224  
R5‑200354 Correction to 5G RRC test case 8.1.1.2.3 TDIA, CATT CR Agreement
6.3.2.4.4.1.1RRC Connection Management Procedures (clause 8.1.1)
Yes
Yes
agreed No    
R5‑200355 Correction to 5G RRC test case 8.1.1.4.1 TDIA, CATT CR Agreement
6.3.2.4.4.1.1RRC Connection Management Procedures (clause 8.1.1)
Yes
Yes
agreed No    
R5‑200356 Correction to 5G UAC test case 11.3.6 TDIA, MCC TF160, Huawei, HiSilicon, CATT CR Agreement
6.3.2.4.8.3Unified Access Control (UAC)
Yes
Yesr1 was produced. Comments from R&S.
revised No R5‑201227  
R5‑200357 Correction to 5G UAC test case 11.3.3 CATT, TDIA CR Agreement
6.3.2.4.8.3Unified Access Control (UAC)
Yes
Yes
agreed No    
R5‑200358 Correction to 5G UAC test case 11.3.4 CATT, TDIA CR Agreement
6.3.2.4.8.3Unified Access Control (UAC)
Yes
Yes
agreed No    
R5‑200359 Update of 5G Idle test case 6.1.2.23 CATT, TDIA, Huawei, HiSilicon CR Agreement
6.3.2.4.2Idle Mode (Clause 6)
Yes
Yesr1 was produced. The revision is adding step 75A to complete the inter band test purpose which is based on comments from MCC TF160, and correcting the wait time for performing cell reselection for merging R5-200691 from Huawei.
revised No R5‑201223  
R5‑200360 Update of 5GC test case 10.1.3.1 CATT, TDIA CR Agreement
6.3.2.4.6.2SM Network-requested PDU session modification & release (clauses 10.1.2 & 10.1.3)
Yes
Yes
agreed No    
R5‑200361 Addition of new 5GC test case 10.1.2.3 CATT, TDIA CR Agreement
6.3.2.4.6.2SM Network-requested PDU session modification & release (clauses 10.1.2 & 10.1.3)
Yes
Yesfurther technical discussion is needed.
withdrawn Yes    
R5‑200362 WP UE Conformance Test Aspects - Further NB-IoT enhancements CATT Work Plan Information
7.4.2Active Work Items/ Study Item: work plans (wp) / status reports (sr) / Work Item Descriptions (wid)
Yes
Yes
noted No    
R5‑200363 SR UE Conformance Test Aspects - Further NB-IoT enhancements CATT other Information
7.4.2Active Work Items/ Study Item: work plans (wp) / status reports (sr) / Work Item Descriptions (wid)
Yes
Yes
noted No    
R5‑200364 Correction to NR test case 6.2.3.1 Starpoint,Huawei, HiSilicon CR Agreement
6.3.2.4.2Idle Mode (Clause 6)
Yes
Yeschanges over changes. r1 was produced.
revised No R5‑201171  
R5‑200365 Updates of MU and TT in TS 38.521-2 for Rel-16 NTT DOCOMO, INC. CR Agreement
5.3.14.4.3Clauses 1-5 / Annexes
Yes
Yes5GS WIC cover. r1 was produced. offline discussions: Need to include outcome from MU discussion papers.
revised No R5‑200992  
R5‑200366 Correction of NR test case 6.4.3.1-Inter-RAT cell reselection in RRC_INACTIVE StarPoint, Huawei, Hisilicon CR Agreement
6.3.2.4.2Idle Mode (Clause 6)
Yes
Yes
agreed No    
R5‑200367 Update test applicability for 5GC test cases CATT, TDIA CR Agreement
6.3.2.5TS 38.523-2
Yes
Yes
withdrawn Yes    
R5‑200368 Addition of new test case 6.3A.1.4 Minimum output power for 5UL CA in FR2 TTA CR Agreement
5.3.2.5.1Tx Requirements (Clause 6)
Yes
Yes
agreed No    
R5‑200369 Addition of new test case 6.3A.1.5 Minimum output power for 6UL CA in FR2 TTA CR Agreement
5.3.2.5.1Tx Requirements (Clause 6)
Yes
Yes
agreed No    
R5‑200370 Introduction of n95 SUL band test cases CMCC, Ericsson CR Agreement
5.3.14.3.1Tx Requirements (Clause 6)
Yes
Yeswas wrong AI r1 was produced.
revised No R5‑200895  
R5‑200371 Introduction of UE capabilities for n95 SUL band CMCC CR Agreement
7.2.1RF group docs still requiring WG verdict/confirmation - original A.I. retained
Yes
Yeswas wrong AI r1 was produced. Moved n95 from Table A.4.3.1-6 to Table A.4.3.1-5.
revised No R5‑200923  
R5‑200372 Addition of new test case 6.3A.1.6 Minimum output power for 7UL CA in FR2 TTA CR Agreement
5.3.2.5.1Tx Requirements (Clause 6)
Yes
Yes
agreed No    
R5‑200373 Updates on UE capabilities for Rel-16 EN-DC configurations NTT DOCOMO INC. CR Agreement
7.2.1RF group docs still requiring WG verdict/confirmation - original A.I. retained
Yes
Yesr1 was produced. Editorial correction according to R5-200592.
revised No R5‑201158  
R5‑200374 Addition of new test case 6.3A.1.7 Minimum output power for 8UL CA in FR2 TTA CR Agreement
5.3.2.5.1Tx Requirements (Clause 6)
Yes
Yes
agreed No    
R5‑200375 Addition of new test case 6.4A.2.1.4 Error vector magnitude for 5UL CA in FR2 TTA CR Agreement
5.3.2.5.1Tx Requirements (Clause 6)
Yes
Yes
agreed No    
R5‑200376 Addition of new test case 6.4A.2.1.5 Error vector magnitude for 6UL CA in FR2 TTA CR Agreement
5.3.2.5.1Tx Requirements (Clause 6)
Yes
Yes
agreed No    
R5‑200377 Addition of new test case 6.4A.2.1.6 Error vector magnitude for 7UL CA in FR2 TTA CR Agreement
5.3.2.5.1Tx Requirements (Clause 6)
Yes
Yes
agreed No    
R5‑200378 Addition of TS36.521-2 CA Band 5A-29A and 2A-5A-29A Sporton International Inc. CR Agreement
5.4.1.3TS 36.521-2
Yes
YesWIC -13 ! is not in the scope of the meeting.
withdrawn Yes    
R5‑200379 Addition of TS36.523-2 CA Band 5A-29A and 2A-5A-29A Sporton International Inc. CR Agreement
6.4.4Routine Maintenance for TS 36.523-2
Yes
YesWIC -13 ! RAN5 chair: is outside the scope.
withdrawn Yes    
R5‑200380 Clarification of UEsetting for FR2 in TS38.521-2 Conformance test Sporton International Inc. CR Agreement
5.3.2.5.1Tx Requirements (Clause 6)
Yes
Yesoutside of meeting scope.
withdrawn Yes    
R5‑200381 Clarification of UEsetting for FR2 in TS38.521-3 Conformance test Sporton International Inc. CR Agreement
5.3.2.6.1Tx Requirements (Clause 6)
Yes
Yesoutside of meeting scope.
withdrawn Yes    
R5‑200382 Addition of new test case 6.4A.2.1.7 Error vector magnitude for 8UL CA in FR2 TTA CR Agreement
5.3.2.5.1Tx Requirements (Clause 6)
Yes
Yes
agreed No    
R5‑200383 Update of test cases for Error vector magnitude for CA in FR2 TTA CR Agreement
5.3.2.5.1Tx Requirements (Clause 6)
Yes
Yes
agreed No    
R5‑200384 MCC TF160 Status Report MCC TF160 report Approval
7.5Docs still needing agreement/endorsement/approval (e.g. Outgoing LS, Reports, New Specs, Info for certification bodies etc.)
No
Yespost meeting doc
noted No    
R5‑200385 Corrections to default MCPTT configuration management messages and other information elements MCC TF160 CR Agreement
6.5.9.1TS 36.579-1
Yes
Yes
agreed No    
R5‑200386 Update of clause 5 for Rel-16 EN-DC configurations in 38.521-3 NTT DOCOMO INC. CR Agreement
5.3.10.5.3Clauses 1-5 / Annexes
Yes
YesAll the band combos included in this CR are still in “pending” status in WP.
withdrawn Yes    
R5‑200387 Corrections for re-registration on V-PLMN and UTRAN ROHDE & SCHWARZ, Qualcomm, Anritsu CR Agreement
6.5.6.1TS 34.229-1
Yes
Yesr1 was produced. r2 was produced. Title correction.
revised No R5‑201121  
R5‑200388 Adding missing R15 IEs into RRCConnectionReconfiguration Huawei, HiSilicon CR Agreement
7.2.1RF group docs still requiring WG verdict/confirmation - original A.I. retained
Yes
Yesr1 was produced: as per TF160’s comment, the unused IEs are removed in r1, only nonCriticalExtension is kept with release information in ‘comment’ entry. r2 was produced. Release information is added to all the nonCriticalExtension belonging to RRCConnectionReconfiguration, and redundant ‘::=’ is removed in several places.
revised No R5‑200917  
R5‑200389 Discussion on PDSCH to HARQ-ACK feedback timing and related PUCCH configuration Huawei, HiSilicon discussion Discussion
7.2.1RF group docs still requiring WG verdict/confirmation - original A.I. retained
Yes
YesQualcomm: Instead of specifying one common HARQ-ACK feedback timing for all scenarios, our preference is to specify per scenario. So for SCS 60 KHz with dmrs-additionalPosition pos 1, specify PUCCH HARQ-ACK to be transmitted with 20 symbol gap. Similarly for SCS 120 KHz with dmrs-additionalPosition pos1, it will be 24 symbols which is symbol 10 and 11 of the UL slot. Samsung: not sure. noted no proposals endorsed
noted No    
R5‑200390 Update of DCI 1_0 and DCI_1_1 configuration Huawei, HiSilicon CR Agreement
7.2.1RF group docs still requiring WG verdict/confirmation - original A.I. retained
Yes
YesQualcomm would like to specify the HARQ-ACK timing per scenario instead of a common value proposed by Huawei. r1 was produced. r2 was produced. Qualcomm agreed.
revised No R5‑201195  
R5‑200391 Adding statistical testing condition in Annex H for CA testing Huawei, HiSilicon CR Agreement
5.3.2.4.3Clauses 1-5 / Annexes
Yes
Yesr1 was produced.
revised No R5‑200924  
R5‑200392 Discussion on MU and TT of FR1 CA Rx test cases Huawei, HiSilicon discussion Discussion
5.3.2.17Discussion Papers / Work Plan / TC lists
Yes
YesNoted and proposal endorsed and implmented in CR 0393.
noted No    
R5‑200393 Adding MU and TT for FR1 Rx CA test cases Huawei, HiSilicon CR Agreement
5.3.2.4.3Clauses 1-5 / Annexes
Yes
Yes
agreed No    
R5‑200394 Discussion on FR1 MOP testing for PC2 UE Huawei, HiSilicon, CMCC discussion Discussion
5.3.2.17Discussion Papers / Work Plan / TC lists
Yes
YesKeysight disagreed. Noted and no proposal endorsed
noted No    
R5‑200395 Discussion on handling of HP-UE requirements in FR1 Huawei, HiSilicon, CMCC discussion Discussion
5.3.2.17Discussion Papers / Work Plan / TC lists
Yes
Yesr1 was produced. noted and proposal endorsed
revised No R5‑201181  
R5‑200396 Cleaning up of power class 2 test cases in FR1 Huawei, HiSilicon, CMCC CR Agreement
5.3.2.4.1Tx Requirements (Clause 6)
Yes
Yesr2 was produced. Keysight: R5-200396 is also addressing the topic of the UE Tx Diversity in the proposed HPUE tests. However, my understanding is that there is not yet RAN4 consensus and response to “R5-198688 - LS on the testability of FR1 Tx diversity” so meanwhile only 1 UE Tx antenna should still be considered. Huawei: RAN4’s ongoing discussion is limited to MIMO mode with one layer and two antenna ports. That’s not the same as whats in this CR. For MOP testing it’s reasonable to measure the sum of power on both antenna connectors. This problem faces urgent industry need and we need to figure out a way forward in this meeting. Without clearly defining the test method, the validation and conformance testing of UE with 2 Tx antennas will be blocked. Ericsson and R&S agreed with Keysight. Probably withdrawn.
revised No R5‑201196  
R5‑200397 Updating power configuration for PRACH time mask Huawei, HiSilicon CR Agreement
5.3.2.4.1Tx Requirements (Clause 6)
Yes
Yes
agreed No    
R5‑200398 On ACLR test metric for FR2 Huawei, HiSilicon discussion Discussion
5.3.2.17Discussion Papers / Work Plan / TC lists
Yes
YesNo proposals endorsed. Noted.
noted No    
R5‑200399 Adding common uplink configuration of E-UTRA carrier for EN-DC testing Huawei, HiSilicon CR Agreement
5.3.2.6.1Tx Requirements (Clause 6)
Yes
Yesr1 was produced.
revised No R5‑200925  
R5‑200400 Updating MOP for inter-band EN-DC Huawei, HiSilicon CR Agreement
5.3.2.6.1Tx Requirements (Clause 6)
Yes
Yesr1 was produced. r2 was produced. Revision is based on the understanding that SA MOP requirements would apply to non-overlapping transmission. r3 was produced. Removed ‘The test case is incomplete’ from Editor’s note so that the case remains complete based on 38.101-3 rapporteur’s comment. The test case has already fulfilled coverage of core requirements. Any further investigation of additional scenario can be carried without changing the test case back to incomplete.
revised No R5‑201055  
R5‑200401 Updating configured output power for inter-band EN-DC Huawei, HiSilicon CR Agreement
5.3.2.6.1Tx Requirements (Clause 6)
Yes
Yesr1 was produced. r2 was produced. Similar changes as in R5-200405r2.
revised No R5‑200926  
R5‑200402 Updating TP of MOP for inter-band EN-DC Huawei, HiSilicon CR Agreement
5.3.2.16TR 38.905 (NR Test Points Radio Transmission and Reception )
Yes
Yes
agreed No    
R5‑200403 Updating TP of configured output power for inter-band EN-DC Huawei, HiSilicon CR Agreement
5.3.2.16TR 38.905 (NR Test Points Radio Transmission and Reception )
Yes
Yesr1 was produced. The structure of TP analysis is updated. Analysis of P-max selection is added. The number of test points is updated.
revised No R5‑201182  
R5‑200404 Updating MOP for intra-band contiguous EN-DC Huawei, HiSilicon CR Agreement
5.3.2.6.1Tx Requirements (Clause 6)
Yes
Yesr1 was produced. SA MOP requirements apply to non-overlapping transmission.
revised No R5‑201183  
R5‑200405 Updating configured output power for intra-band contiguous EN-DC Huawei, HiSilicon CR Agreement
5.3.2.6.1Tx Requirements (Clause 6)
Yes
Yesr1 was produced. r2 was produced. r3 was produced. The test procedure step 3 is updated to cover all scenarios in a more general way.
revised No R5‑200927  
R5‑200406 Updating TP of MOP for intra-band contiguous EN-DC Huawei, HiSilicon CR Agreement
5.3.2.16TR 38.905 (NR Test Points Radio Transmission and Reception )
Yes
Yesfor email agreement Ericsson disagreed. See R5-201183.
withdrawn Yes    
R5‑200407 Updating TP of configured output power for intra-band contiguous EN-DC Huawei, HiSilicon CR Agreement
5.3.2.16TR 38.905 (NR Test Points Radio Transmission and Reception )
Yes
Yesr1 was produced. The structure of TP analysis is updated. The analysis of (n)71AA is corrected. The number of test points is updated. r2 was produced.
revised No R5‑201184  
R5‑200408 Updating MOP for intra-band non-contiguous EN-DC Huawei, HiSilicon CR Agreement
5.3.2.6.1Tx Requirements (Clause 6)
Yes
Yesr1 was produced. SA MOP requirements apply to non-overlapping transmission.
revised No R5‑201185  
R5‑200409 Updating configured output power for intra-band non-contiguous EN-DC Huawei, HiSilicon CR Agreement
5.3.2.6.1Tx Requirements (Clause 6)
Yes
Yesr1 was produced. r2 was produced. Similar changes are captured as R5-200405r2.
revised No R5‑200928  
R5‑200410 Updating TP of MOP for intra-band non-contiguous EN-DC Huawei, HiSilicon CR Agreement
5.3.2.16TR 38.905 (NR Test Points Radio Transmission and Reception )
Yes
YesRAN4 dependency R4-2001316 for email agreement Ericsson disagreed. See R5-201183.
withdrawn Yes    
R5‑200411 Updating TP of configured output power for intra-band non-contiguous EN-DC Huawei, HiSilicon CR Agreement
5.3.2.16TR 38.905 (NR Test Points Radio Transmission and Reception )
Yes
Yesr1 was produced. The structure of TP analysis is updated. Analysis of P-max selection is added. The number of test points is updated. r2 was produced.
revised No R5‑201186  
R5‑200412 Editorial change of replacing zip file of FR2 6.3.1 by v2 Huawei, HiSilicon CR Agreement
5.3.2.16TR 38.905 (NR Test Points Radio Transmission and Reception )
Yes
Yes
agreed No    
R5‑200413 Addition of a few R16 EN-DC configurations Huawei, HiSilicon CR Agreement
5.3.10.5.1Tx Requirements (Clause 6)
Yes
Yesr1 was produced. Missing test configurations for DC_12A-n78A exceptional requirements are added based on Qualcomm.
revised No R5‑201187  
R5‑200414 New WID on: UE Conformance Test Aspects for RF requirements for NR frequency range 1 (FR1) Huawei, HiSilicon, China Telecom WID new Approval
7.4.1Final version of Work Item Proposals
Yes
YesChina Unicom is added as co-rapporteur, Ericsson, dish are added as supporting company.
revised No R5‑200898  
R5‑200415 WP - Shortened TTI and processing time for LTE - Status after RAN5#85 Huawei, HiSilicon Work Plan Information
7.4.2Active Work Items/ Study Item: work plans (wp) / status reports (sr) / Work Item Descriptions (wid)
Yes
Yes
noted No    
R5‑200416 SR - Shortened TTI and processing time for LTE - Status after RAN5#85 Huawei, HiSilicon WI status report Endorsement
7.4.2Active Work Items/ Study Item: work plans (wp) / status reports (sr) / Work Item Descriptions (wid)
Yes
Yes
noted No    
R5‑200417 Correction to 5GC test case 10.1.2.2 CATT, TDIA CR Agreement
6.3.2.4.6.2SM Network-requested PDU session modification & release (clauses 10.1.2 & 10.1.3)
Yes
Yesr1 was produced. Correcting the format of reference [TS 24.501, clause 7.3.2] in conformance requirements part based the comments from Huawei.
revised No R5‑201226  
R5‑200418 Update of Operating bands and Channel arrangement of SA FR2 R15 CAICT CR Agreement
5.3.2.5.3Clauses 1-5 / Annexes
Yes
Yes
agreed No    
R5‑200419 Update of test point analysis for 7.6A.3 Out-of-band blocking for CA CAICT CR Agreement
5.3.2.16TR 38.905 (NR Test Points Radio Transmission and Reception )
Yes
Yes
agreed No    
R5‑200420 Core alignment for event-triggered reporting test cases Anritsu CR Agreement
5.3.2.9.3NR Standalone in FR1 (Clause 6)
Yes
Yesr1 was produced. Empty cells in Table 6.3.1.5.5-1 are removed. (Editorial correction). RAN4 dependency : R4-2000166
revised No R5‑200986  
R5‑200421 Correction to Active UL BWP for intra-frequency event triggered reporting with gap Anritsu CR Agreement
5.3.2.9.3NR Standalone in FR1 (Clause 6)
Yes
YesRAN4 dependency : R4-2000161 for email agreement RAN4 CR was agreed in RAN4#94-e. Email agreed.
agreed No    
R5‑200422 Correction to EN-DC FR1 event-triggered reporting test cases Anritsu CR Agreement
5.3.2.9.1EN-DC with all NR cells in FR1 (Clause 4)
Yes
Yes
agreed No    
R5‑200423 Correction to FR1 NR SA E-UTRA cell re-selection test cases Anritsu CR Agreement
5.3.2.9.3NR Standalone in FR1 (Clause 6)
Yes
YesRAN4 dependency : R4-2000163 for email agreement RAN4 CR was agreed in RAN4#94-e. Email agreed.
agreed No    
R5‑200424 Correction to message contents in 6.6.1.5 and 6.6.1.6 Anritsu CR Agreement
5.3.2.9.3NR Standalone in FR1 (Clause 6)
Yes
Yesr1 was produced. Editorial.
revised No R5‑201056  
R5‑200425 Correction to NR SA FR1 SS-RSRP measurement accuracy tests Anritsu CR Agreement
5.3.2.9.3NR Standalone in FR1 (Clause 6)
Yes
Yes
agreed No    
R5‑200426 Correction to test description of RRM TC 4.6.1.3 and 4.6.1.6 Anritsu CR Agreement
5.3.2.9.1EN-DC with all NR cells in FR1 (Clause 4)
Yes
Yesr1 was produced. Editorial.
revised No R5‑201057  
R5‑200427 Correction to the simulated cell for cell-reselection test cases Anritsu CR Agreement
5.3.2.9.6Clauses 1-3 / Annexes
Yes
Yes
agreed No    
R5‑200428 Correction to UE transmit timing accuracy test case Anritsu CR Agreement
5.3.2.9.1EN-DC with all NR cells in FR1 (Clause 4)
Yes
YesRAN4 dependency : R4-2000168 for email agreement Email agreed.
agreed No    
R5‑200429 Update of maximum test system uncertainty for FR1 RRM Test Anritsu CR Agreement
5.3.2.9.6Clauses 1-3 / Annexes
Yes
Yesr1 was produced. Offline comments from Ericsson, R&S.
revised No R5‑201058  
R5‑200430 Correction to CORESET and search space configuration Anritsu, Qualcomm Technologies Inc CR Agreement
7.2.1RF group docs still requiring WG verdict/confirmation - original A.I. retained
Yes
Yesr1 was produced. RF changes only, based on offline discussion with Ericsson, MCC TF160. r2 was produced. Offline discussion with Qualcomm and E///.
revised No R5‑200965  
R5‑200431 Correction to CSI-FrequencyOccupation Anritsu CR Agreement
7.2.1RF group docs still requiring WG verdict/confirmation - original A.I. retained
Yes
YesRAN4 dependency, R4 spec correction needed as TRS config in R4 spec 38.101-1/2 causes TRS and SSB to collide in the same slot RAN4 dependency for email agreement Anritsu: changes in R5-200431 are independent from R4-2002735, then no revision is required, can be agreed as is. Email agreed.
agreed No    
R5‑200432 Correction to default setting of additionalPmax Anritsu CR Agreement
7.2.1RF group docs still requiring WG verdict/confirmation - original A.I. retained
Yes
Yes
agreed No    
R5‑200433 Correction to powerControlOffset for performance tests Anritsu CR Agreement
5.3.2.1TS 38.508-1
Yes
Yes
agreed No    
R5‑200434 Correction to RACH configuration for RRM tests Anritsu CR Agreement
5.3.2.1TS 38.508-1
Yes
Yes
agreed No    
R5‑200435 Correction to TDD UL-DL Config for performance test cases Anritsu CR Agreement
5.3.2.1TS 38.508-1
Yes
Yes
agreed No    
R5‑200436 Correction to test frequencies for n257 intra-band contiguous CA Anritsu, NTT DOCOMO INC., Ericsson CR Agreement
7.2.1RF group docs still requiring WG verdict/confirmation - original A.I. retained
Yes
Yesr1 was produced. Test frequencies specified in accordance to CR 1131 (Ericsson) to Annex C of 38.508-1, clause 2.4.2. r2 was produced????
revised No R5‑201159  
R5‑200437 Correction to TRS configuration for RRM tests Anritsu, Keysight Technologies CR Agreement
5.3.2.1TS 38.508-1
Yes
Yesr1 was produced. - Merge changes from R5-200871(KS) - Added n NZP-CSI-RS-Resources for NZP CRI RS. Added entries are conditioned with CRS_RS_RMC. - Added Keysight as co-source company.
revised No R5‑201197  
R5‑200438 Clarification of measurement interval of frequency error in FR1 Anritsu CR Agreement
5.3.2.4.1Tx Requirements (Clause 6)
Yes
Yes
agreed No    
R5‑200439 Correction to 6.2.3 A-MPR test case Anritsu CR Agreement
5.3.2.4.1Tx Requirements (Clause 6)
Yes
Yesr1 was produced. Corrected the test ID numbering in test requirement Tables in 6.2.3.5-4, 6.2.3.5-5. ericsson: Some changes conflict with R5-200767. r2 was produced.
revised No R5‑200972  
R5‑200440 Correction to 6.3.4.3 Power Control Relative power tolerance Anritsu CR Agreement
5.3.2.4.1Tx Requirements (Clause 6)
Yes
Yes
agreed No    
R5‑200441 Correction to SEM and ACLR test cases Anritsu CR Agreement
5.3.2.4.1Tx Requirements (Clause 6)
Yes
Yes
agreed No    
R5‑200442 Correction to transmit modulation quality test in FR1 Anritsu CR Agreement
5.3.2.4.1Tx Requirements (Clause 6)
Yes
Yesr1 was produced. Place of new paragraph regarding DC location in SUL test is corrected from 6.4C.2.1 to 6.4C.2.
revised No R5‑200973  
R5‑200443 Correction to UL power window description for 6.3.4.4 Anritsu CR Agreement
5.3.2.4.1Tx Requirements (Clause 6)
Yes
Yes
agreed No    
R5‑200444 Clarification of measurement interval of frequency error in FR2 Anritsu CR Agreement
5.3.2.5.1Tx Requirements (Clause 6)
Yes
Yes
agreed No    
R5‑200445 Correction to transmit modulation quality tests in FR2 Anritsu CR Agreement
5.3.2.5.1Tx Requirements (Clause 6)
Yes
Yesadding the same sentence from core requirement in general section will not provide enough clarity in each test case. Will come back in next meeting
withdrawn Yes    
R5‑200446 Correction to FR1 EN-DC Spurious Test Case Anritsu CR Agreement
5.3.2.6.1Tx Requirements (Clause 6)
Yes
Yes
agreed No    
R5‑200447 Correction to FR1 Inter-band EN-DC tests with exceptional requirement Anritsu CR Agreement
5.3.2.6.1Tx Requirements (Clause 6)
Yes
Yes
withdrawn Yes    
R5‑200448 Correction to LTE specialSubframePatterns in Maximum Output Power Test Case Anritsu CR Agreement
5.3.2.6.1Tx Requirements (Clause 6)
Yes
Yes
agreed No    
R5‑200449 Correction to tdm-PatternConfig in FR1 EN-DC Maximum Output Power Test Case Anritsu CR Agreement
5.3.2.6.1Tx Requirements (Clause 6)
Yes
Yes
agreed No    
R5‑200450 Addition of message exceptions for Type2 QCL information Anritsu CR Agreement
5.3.2.7.1Conducted Demod Performance and CSI Reporting Requirements (Clauses 5&6)
Yes
Yes
agreed No    
R5‑200451 Core alignment for FR2 demod test case Anritsu CR Agreement
5.3.2.7.4Clauses 1-4 / Annexes
Yes
Yesr1 was produced. Changes in Annex B is removed to solve overlap with R5-200672(BV).
revised No R5‑200985  
R5‑200452 Core alignment to 4Rx PDCCH Demod Test Cases Anritsu CR Agreement
5.3.2.7.1Conducted Demod Performance and CSI Reporting Requirements (Clauses 5&6)
Yes
YesRAN4 dependency : R4-2000081->2447 for email agreement r1 was produced.
revised No R5‑201245  
R5‑200453 Correction to FR1 2Rx PDSCH demodulation test cases Anritsu CR Agreement
5.3.2.7.1Conducted Demod Performance and CSI Reporting Requirements (Clauses 5&6)
Yes
Yes
agreed No    
R5‑200454 Correction to FR1 4Rx PDSCH demodulation test cases Anritsu CR Agreement
5.3.2.7.1Conducted Demod Performance and CSI Reporting Requirements (Clauses 5&6)
Yes
Yesr1 was produced. Recovering the hierachical structure of 5.4.3.3 and updating the wording of 5.4.3.2.
agreed No    
R5‑200455 Correction to measurement uncertainty and test tolerance for CQI test cases Anritsu CR Agreement
5.3.2.7.1Conducted Demod Performance and CSI Reporting Requirements (Clauses 5&6)
Yes
Yes
agreed No    
R5‑200456 Correction to PDCCH demod TCs Anritsu CR Agreement
5.3.2.7.1Conducted Demod Performance and CSI Reporting Requirements (Clauses 5&6)
Yes
Yes
agreed No    
R5‑200457 Corrections to Via header in PRACK, UPDATE, and BYE ROHDE & SCHWARZ, MCC TF160 CR Agreement
6.5.6.1TS 34.229-1
Yes
Yes
agreed No    
R5‑200458 Corrections to Contact header in UPDATE ROHDE & SCHWARZ, MCC TF160 CR Agreement
6.5.6.1TS 34.229-1
Yes
Yes
agreed No    
R5‑200459 Update of test point analysis for 7.6A.4 Narrow band blocking for CA CAICT CR Agreement
5.3.2.16TR 38.905 (NR Test Points Radio Transmission and Reception )
Yes
Yes
agreed No    
R5‑200460 Update of test point analysis for 7.8A Wide band Intermodulation for CA CAICT CR Agreement
5.3.2.16TR 38.905 (NR Test Points Radio Transmission and Reception )
Yes
Yes
agreed No    
R5‑200461 Update of 7.6A.3.1 Out-of-band blocking for 2DL CA CAICT CR Agreement
5.3.2.4.2Rx Requirements (Clause 7)
Yes
Yes
agreed No    
R5‑200462 Update of 7.6A.4.1 Narrow band blocking for 2DL CA CAICT CR Agreement
5.3.2.4.2Rx Requirements (Clause 7)
Yes
Yes
agreed No    
R5‑200463 Update of 7.8A.2.1 Wide band Intermodulation for 2DL CA CAICT CR Agreement
5.3.2.4.2Rx Requirements (Clause 7)
Yes
Yes
agreed No    
R5‑200464 Editorial update of Beamlock deactivation Huawei, HiSilicon CR Agreement
7.2.1RF group docs still requiring WG verdict/confirmation - original A.I. retained
Yes
Yesr1 was produced.
revised No R5‑200904  
R5‑200465 Update of rx beampeak search Huawei, HiSilicon CR Agreement
5.3.2.5.3Clauses 1-5 / Annexes
Yes
Yesr1 was produced. .docx
revised No R5‑201059  
R5‑200466 Update of FR2 REFSENS Huawei, HiSilicon CR Agreement
5.3.2.5.2Rx Requirements (Clause 7)
Yes
YesCovered by R5-200602 from Qualcomm.
withdrawn Yes    
R5‑200467 Update of absolute power tolerance for test point 3 Huawei, HiSilicon CR Agreement
5.3.2.5.1Tx Requirements (Clause 6)
Yes
Yesr1 was produced. .docx
revised No R5‑201060  
R5‑200468 Addition of a few R16s inter-band EN-DC FR1 test configurations Huawei, HiSilicon CR Agreement
7.2.1RF group docs still requiring WG verdict/confirmation - original A.I. retained
Yes
Yesr1 was produced. .docx
revised No R5‑201061  
R5‑200469 Introduction of UE capabilities for Rel-16 EN-DC configurations Huawei, HiSilicon CR Agreement
7.2.1RF group docs still requiring WG verdict/confirmation - original A.I. retained
Yes
Yesr1 was produced. .docx
revised No R5‑201062  
R5‑200470 FR1 Test tolerance analysis for interruptions deactivated NR SCC Huawei, HiSilicon CR Agreement
5.3.2.15TR 38.903 ((NR MU & TT analyses)
Yes
YesRAN4 dependency: R4-2001596 for email agreement Email agreed.
agreed No    
R5‑200471 FR1 Test tolerance analysis for interruptions deactivated E-UTRAN SCC Huawei, HiSilicon CR Agreement
5.3.2.15TR 38.903 ((NR MU & TT analyses)
Yes
Yesproblems have not been resolved in RAN4 and RAN5.
withdrawn Yes    
R5‑200472 Update FR1 Test Tolerance of 4.5.2.3 interruptions on NR SCC in sync Huawei, HiSilicon CR Agreement
5.3.2.9.1EN-DC with all NR cells in FR1 (Clause 4)
Yes
Yesr1 was produced. 1.SCell addition procedure was added in step3 2.Message exceptions to configure “sCellToAddModList” and “SMTC” were added 3. Corrected some editorial errors.
revised No R5‑201063  
R5‑200473 Update FR1 Test Tolerance of 4.5.2.4 interruptions on NR SCC in async Huawei, HiSilicon CR Agreement
5.3.2.9.1EN-DC with all NR cells in FR1 (Clause 4)
Yes
Yesr1 was produced. 1.SCell addition procedure was added in step3 2.Message exceptions to configure “sCellToAddModList” and “SMTC” were added 3. Corrected some editorial errors.
revised No R5‑201064  
R5‑200474 Update FR1 Test Tolerance of 4.5.2.5 E-UTRAN SCC in sync Huawei, HiSilicon CR Agreement
5.3.2.9.1EN-DC with all NR cells in FR1 (Clause 4)
Yes
Yesproblems have not been resolved in RAN4 and RAN5.
withdrawn Yes    
R5‑200475 Update FR1 Test Tolerance of 4.5.2.6 E-UTRAN SCC in async Huawei, HiSilicon CR Agreement
5.3.2.9.1EN-DC with all NR cells in FR1 (Clause 4)
Yes
Yesproblems have not been resolved in RAN4 and RAN5.
withdrawn Yes    
R5‑200476 Update of FR1 Test Tolerance in Annex F Huawei, HiSilicon CR Agreement
5.3.2.9.6Clauses 1-3 / Annexes
Yes
Yesr1 was produced. 1. Removed the rows for 4.5.2.5 and 4.5.2.6, because the related TT analysis was withdrawn.
revised No R5‑201169  
R5‑200477 Update to Registration REQ and Authentication Response message ROHDE & SCHWARZ, Anritsu CR Agreement
6.3.2.1TS 38.508-1
Yes
YesFalsely withdrawn by Anritsu after offline discussion with DCM/Huawei/E///. Re-agreed after the meeting.
agreed No    
R5‑200478 Discussion on FR1 UL CA power calculation for TC transmit on off time mask China Unicom discussion Discussion
5.3.2.17Discussion Papers / Work Plan / TC lists
Yes
Yesr1 was produced. In Proposal 1. It is proposed to select PO_NominalWithGrant=-106dBm/180kHz for PCC and SCC in TC 6.3A.3.1. Becasue PO_NominalWithGrant value can only set to even ( step size 2) • Updated Table 2.1-1 for power calculation of transmit ON/OFF time mask for 2UL CA. The discussion paper is about recalculate the transmit on power for 2UL CA by reduce 6dB for PO_NominalWithGrant in Single carrier TC, to avoid impact of MPR on transmit on power. The associated CR is R5-200344r1.
revised No R5‑200920  
R5‑200479 3GPP RAN5 CA status list (pre-RAN5#86-e meeting) Ericsson other Information
2.2General Reports for information
No
Yes
withdrawn Yes    
R5‑200480 3GPP RAN5 CA status list (post-RAN5#86-e meeting) Ericsson other Information
7.5Docs still needing agreement/endorsement/approval (e.g. Outgoing LS, Reports, New Specs, Info for certification bodies etc.)
No
Yesno contributions or changes to the list of LTE CA at RAN5#86-e meeting.
withdrawn Yes    
R5‑200481 RAN5#86-e summary of changes to RAN5 test cases with potential impact on GCF and PTCRB Ericsson, Samsung report Information
7.5Docs still needing agreement/endorsement/approval (e.g. Outgoing LS, Reports, New Specs, Info for certification bodies etc.)
No
No
reserved No    
R5‑200482 WP UE Conformance Test Aspects - Rel-13 LTE CA configurations Ericsson Work Plan Information
7.4.2Active Work Items/ Study Item: work plans (wp) / status reports (sr) / Work Item Descriptions (wid)
No
Yeswas already finished.
withdrawn Yes    
R5‑200483 SR UE Conformance Test Aspects - Rel-13 LTE CA configurations Ericsson WI status report Information
7.4.2Active Work Items/ Study Item: work plans (wp) / status reports (sr) / Work Item Descriptions (wid)
No
Yeswas already finished.
withdrawn Yes    
R5‑200484 WP UE Conformance Test Aspects - Rel-14 LTE CA configurations Ericsson Work Plan Information
7.4.2Active Work Items/ Study Item: work plans (wp) / status reports (sr) / Work Item Descriptions (wid)
Yes
Yes
noted No    
R5‑200485 SR UE Conformance Test Aspects - Rel-14 LTE CA configurations Ericsson WI status report Information
7.4.2Active Work Items/ Study Item: work plans (wp) / status reports (sr) / Work Item Descriptions (wid)
Yes
Yes
noted No    
R5‑200486 WP UE Conformance Test Aspects - Rel-15 LTE CA configurations Ericsson Work Plan Information
7.4.2Active Work Items/ Study Item: work plans (wp) / status reports (sr) / Work Item Descriptions (wid)
Yes
Yes
noted No    
R5‑200487 SR UE Conformance Test Aspects - Rel-15 LTE CA configurations Ericsson WI status report Information
7.4.2Active Work Items/ Study Item: work plans (wp) / status reports (sr) / Work Item Descriptions (wid)
Yes
Yes
noted No    
R5‑200488 WP UE Conformance Test Aspects - Rel-16 LTE CA configurations Ericsson Work Plan Information
7.4.2Active Work Items/ Study Item: work plans (wp) / status reports (sr) / Work Item Descriptions (wid)
Yes
Yes
noted No    
R5‑200489 SR UE Conformance Test Aspects - Rel-16 LTE CA configurations Ericsson WI status report Information
7.4.2Active Work Items/ Study Item: work plans (wp) / status reports (sr) / Work Item Descriptions (wid)
Yes
Yes
noted No    
R5‑200490 WP UE Conformance Test Aspects - 5G system with NR and LTE Ericsson Work Plan Information
7.4.2Active Work Items/ Study Item: work plans (wp) / status reports (sr) / Work Item Descriptions (wid)
Yes
No
available No    
R5‑200491 SR UE Conformance Test Aspects - 5G system with NR and LTE Ericsson WI status report Information
7.4.2Active Work Items/ Study Item: work plans (wp) / status reports (sr) / Work Item Descriptions (wid)
Yes
No
available No    
R5‑200492 5GS progress report RAN5#86-e Ericsson WI status report Information
7.5Docs still needing agreement/endorsement/approval (e.g. Outgoing LS, Reports, New Specs, Info for certification bodies etc.)
Yes
No
available No    
R5‑200493 Update of RAN5 5G NR phases and target update RAN5#86-e Ericsson discussion Endorsement
7.5Docs still needing agreement/endorsement/approval (e.g. Outgoing LS, Reports, New Specs, Info for certification bodies etc.)
No
No
reserved No    
R5‑200494 WP UE Conformance Test Aspects - New Rel-16 NR bands and extension of existing NR bands Ericsson Work Plan Information
7.4.2Active Work Items/ Study Item: work plans (wp) / status reports (sr) / Work Item Descriptions (wid)
Yes
Yes
noted No    
R5‑200495 SR UE Conformance Test Aspects - New Rel-16 NR bands and extension of existing NR bands Ericsson WI status report Information
7.4.2Active Work Items/ Study Item: work plans (wp) / status reports (sr) / Work Item Descriptions (wid)
Yes
Yes
noted No    
R5‑200496 Revised WID - New Rel-16 NR bands and extension of existing NR bands Ericsson WID revised Information
7.4.2Active Work Items/ Study Item: work plans (wp) / status reports (sr) / Work Item Descriptions (wid)
Yes
Yesis endorsed.
endorsed No    
R5‑200497 Update SIG test frequencies in clause 6.2.3.x Ericsson CR Agreement
6.3.2.1TS 38.508-1
Yes
Yesr1 was produced. The revision is based on that R5-200497 required update of SIG test frequency table values based on the updated procedure to calculate test frequencies in R5-200157 and a need to update the CR cover sheet. r2 was produced. Adding test frequencies for protocol testing and CA configurations CA_n260G and CA_n261G to clause 6.2.3.4.
revised No R5‑201020  
R5‑200498 Editorial correction to test frequency tables for multiple NR bands Ericsson CR Agreement
6.3.2.1TS 38.508-1
No
Yeslate doc
withdrawn Yes    
R5‑200499 Correction of test frequency tables for NR band n1 Ericsson CR Agreement
6.3.2.1TS 38.508-1
Yes
Yes
agreed No    
R5‑200500 Correction of test frequency tables for NR band n2 Ericsson CR Agreement
6.3.2.1TS 38.508-1
Yes
Yes
agreed No    
R5‑200501 Correction of test frequency tables for NR band n3 Ericsson CR Agreement
6.3.2.1TS 38.508-1
Yes
Yes
agreed No    
R5‑200502 Correction of test frequency tables for NR band n7 Ericsson CR Agreement
6.3.2.1TS 38.508-1
Yes
Yes
agreed No    
R5‑200503 Correction of test frequency tables for NR band n25 Ericsson CR Agreement
6.3.2.1TS 38.508-1
Yes
Yes
agreed No    
R5‑200504 Correction of test frequency tables for NR band n28 Ericsson, Sony Mobile CR Agreement
6.3.2.1TS 38.508-1
Yes
Yes
agreed No    
R5‑200505 Correction of test frequency tables for NR band n34 Ericsson CR Agreement
6.3.2.1TS 38.508-1
Yes
Yes
agreed No    
R5‑200506 Correction of test frequency tables for NR band n38 Ericsson CR Agreement
6.3.2.1TS 38.508-1
Yes
Yes
agreed No    
R5‑200507 Correction of test frequency tables for NR band n39 Ericsson CR Agreement
6.3.2.1TS 38.508-1
Yes
Yes
agreed No    
R5‑200508 Correction of test frequency tables for NR band n40 Ericsson CR Agreement
6.3.2.1TS 38.508-1
Yes
Yes
agreed No    
R5‑200509 Correction of test frequency tables for NR band n41 Ericsson CR Agreement
6.3.2.1TS 38.508-1
Yes
Yesr1 was produced. Comment from Rohde & Schwarz to add indication of ?FRaster used in test frequency calculations for n41 as the band has two possible values (60kHz or 120kHz).
revised No R5‑201021  
R5‑200510 Correction of test frequency tables for NR band n50 Ericsson CR Agreement
6.3.2.1TS 38.508-1
Yes
Yes
agreed No    
R5‑200511 Correction of test frequency tables for NR band n66 Ericsson CR Agreement
6.3.2.1TS 38.508-1
Yes
Yes
agreed No    
R5‑200512 Correction of test frequency tables for NR band n70 Ericsson CR Agreement
6.3.2.1TS 38.508-1
Yes
Yes
agreed No    
R5‑200513 Correction of test frequency tables for NR band n71 Ericsson CR Agreement
6.3.2.1TS 38.508-1
Yes
Yes
agreed No    
R5‑200514 Correction of test frequency tables for NR band n74 Ericsson CR Agreement
6.3.2.1TS 38.508-1
Yes
Yes
agreed No    
R5‑200515 Correction of test frequency tables for NR band n75 Ericsson CR Agreement
6.3.2.1TS 38.508-1
Yes
Yes
agreed No    
R5‑200516 Correction of test frequency tables for NR band n77 Ericsson CR Agreement
6.3.2.1TS 38.508-1
Yes
Yesr1 was produced. Comment from Rohde & Schwarz to add indication of ?FRaster used in test frequency calculations for n77 as the band has two possible values (60kHz or 120kHz).
revised No R5‑201022  
R5‑200517 Correction of test frequency tables for NR band n78 Ericsson CR Agreement
6.3.2.1TS 38.508-1
Yes
Yesr1 was produced. Comment from Rohde & Schwarz to add indication of ?FRaster used in test frequency calculations for n78 as the band has two possible values (60kHz or 120kHz).
revised No R5‑201023  
R5‑200518 Correction of test frequency tables for NR band n79 Ericsson CR Agreement
6.3.2.1TS 38.508-1
Yes
Yesr1 was produced. Comment from Rohde & Schwarz to add indication of ?FRaster used in test frequency calculations for n79 as the band has two possible values (60kHz or 120kHz).
revised No R5‑201024  
R5‑200519 Correction of test frequency tables for NR band n257 Ericsson CR Agreement
6.3.2.1TS 38.508-1
Yes
Yesr1 was produced. Comment from Rohde & Schwarz to add indication of ?FRaster used in test frequency calculations for n257 as the band has two possible values (60kHz or 120kHz).
revised No R5‑201025  
R5‑200520 Correction of test frequency tables for NR band n258 Ericsson CR Agreement
6.3.2.1TS 38.508-1
Yes
Yesr1 was produced. Comment from Rohde & Schwarz to add indication of ?FRaster used in test frequency calculations for n258 as the band has two possible values (60kHz or 120kHz).
revised No R5‑201026  
R5‑200521 Correction of test frequency tables for NR band n260 Ericsson CR Agreement
6.3.2.1TS 38.508-1
Yes
Yesr1 was produced. Comment from Rohde & Schwarz to add indication of ?FRaster used in test frequency calculations for n260 as the band has two possible values (60kHz or 120kHz).
revised No R5‑201027  
R5‑200522 Correction of test frequency tables for NR band n261 Ericsson CR Agreement
6.3.2.1TS 38.508-1
Yes
Yesr1 was produced. Comment from Rohde & Schwarz to add indication of ?FRaster used in test frequency calculations for n261 as the band has two possible values (60kHz or 120kHz).
revised No R5‑201028  
R5‑200523 Corrections of test frequency tables for NR Intra-Band Contiguous CA configuration n41C Ericsson CR Agreement
6.3.2.1TS 38.508-1
No
Yeslate doc
withdrawn Yes    
R5‑200524 Corrections of test frequency tables for NR Intra-Band Contiguous CA configuration n78C Ericsson CR Agreement
6.3.2.1TS 38.508-1
No
Yeslate doc
withdrawn Yes    
R5‑200525 Update and corrections of test frequency tables for NR Intra-Band Contiguous CA configurations for NR band n257 Ericsson CR Agreement
6.3.2.1TS 38.508-1
No
Yeslate doc
withdrawn Yes    
R5‑200526 Update and corrections of test frequency tables for NR Intra-Band Contiguous CA configurations for NR band n258 Ericsson CR Agreement
6.3.2.1TS 38.508-1
No
Yeslate doc
withdrawn Yes    
R5‑200527 Update and corrections of test frequency tables for NR Intra-Band Contiguous CA configurations for NR band n260 Ericsson CR Agreement
6.3.2.1TS 38.508-1
No
Yeslate doc
withdrawn Yes    
R5‑200528 Update and corrections of test frequency tables for NR Intra-Band Contiguous CA configurations for NR band n261 Ericsson CR Agreement
6.3.2.1TS 38.508-1
No
Yeslate doc
withdrawn Yes    
R5‑200529 Corrections of test frequency tables for NR Intra-Band Contiguous CA configuration n66B Ericsson CR Agreement
6.3.11.1TS 38.508-1
No
Yeslate doc
withdrawn Yes    
R5‑200530 Introduction of test frequencies for Rel-16 NR CA configuration CA_n66(2A) in cl 6.2.3 Ericsson CR Agreement
6.3.11.1TS 38.508-1
No
Yeslate doc
withdrawn Yes    
R5‑200531 Correction of test frequency tables for NR band n29 Ericsson CR Agreement
6.3.13.1TS 38.508-1
Yes
Yes
agreed No    
R5‑200532 Correction of test frequency tables for NR band n48 Ericsson CR Agreement
6.3.13.1TS 38.508-1
Yes
Yes
agreed No    
R5‑200533 Correction of test frequency tables for NR band n65 Ericsson CR Agreement
6.3.13.1TS 38.508-1
Yes
Yes
agreed No    
R5‑200534 Update of clause 4.4.2 on simulated cells Ericsson CR Agreement
6.3.2.1TS 38.508-1
Yes
Yesr1 was produced. According to comment from TF160 removed brackets in the reference in Note 1 in Table 4.4.2-1.
revised No R5‑201029  
R5‑200535 Applicability of RRM feMTC Test Cases Ericsson CR Agreement
5.3.4.3TS 36.521-2
Yes
Yes
agreed No    
R5‑200536 Correction of definitions of Bandwidth-reduced Low-complexity or Coverage Enhanced UE Ericsson CR Agreement
5.3.4.4TS 36.521-3
Yes
Yes
agreed No    
R5‑200537 Cell configuration mapping for RRM feMTC Test Cases Ericsson CR Agreement
5.3.4.4TS 36.521-3
Yes
Yes
agreed No    
R5‑200538 Addition of a new RRM feMTC Test Case 5.1.28 Ericsson CR Agreement
5.3.4.4TS 36.521-3
Yes
Yes
agreed No    
R5‑200539 Addition of a new RRM feMTC Test Case 5.1.34 Ericsson CR Agreement
5.3.4.4TS 36.521-3
Yes
Yes
agreed No    
R5‑200540 Addition of a new RRM feMTC Test Case 6.1.18 Ericsson CR Agreement
5.3.4.4TS 36.521-3
Yes
Yes
agreed No    
R5‑200541 Addition of a new RRM feMTC Test Case 7.3.69 Ericsson CR Agreement
5.3.4.4TS 36.521-3
Yes
Yes
agreed No    
R5‑200542 Correction of RRM feMTC Test Case 8.3.16 Ericsson CR Agreement
5.3.4.4TS 36.521-3
Yes
Yes
agreed No    
R5‑200543 Correction of RRM feMTC Test Case 8.3.17 Ericsson CR Agreement
5.3.4.4TS 36.521-3
Yes
Yes
agreed No    
R5‑200544 Correction of RRM feMTC Test Case 8.3.18 Ericsson CR Agreement
5.3.4.4TS 36.521-3
Yes
Yes
agreed No    
R5‑200545 Correction of RRM feMTC Test Case 8.3.19 Ericsson CR Agreement
5.3.4.4TS 36.521-3
Yes
Yes
agreed No    
R5‑200546 Correction of RRM feMTC Test Case 8.4.12 Ericsson CR Agreement
5.3.4.4TS 36.521-3
Yes
Yes
agreed No    
R5‑200547 Correction of RRM feMTC Test Case 8.4.13 Ericsson CR Agreement
5.3.4.4TS 36.521-3
Yes
Yes
agreed No    
R5‑200548 Correction of RRM feMTC Test Case 8.4.14 Ericsson CR Agreement
5.3.4.4TS 36.521-3
Yes
Yes
agreed No    
R5‑200549 Correction of RRM feMTC Test Case 8.4.15 Ericsson CR Agreement
5.3.4.4TS 36.521-3
Yes
Yes
agreed No    
R5‑200550 Correction to EN-DC RLC test case 7.1.2.3.11 ANRITSU LTD, MCC TF160 CR Agreement
6.3.2.4.3.1.3RLC
Yes
Yesr1 was produced. Additional changes received from TF160 which modifies RLC timers.
revised No R5‑201094  
R5‑200551 Correction to NR PDCP test case 7.1.3.5.5 ANRITSU LTD CR Agreement
6.3.2.4.3.1.4PDCP
Yes
Yes
agreed No    
R5‑200552 FR2 Measurement Uncertainty (MU) / Test Tolerances (TT) Target Completion Update PCTEST Engineering Lab discussion Endorsement
7.5Docs still needing agreement/endorsement/approval (e.g. Outgoing LS, Reports, New Specs, Info for certification bodies etc.)
Yes
Yesoffline discussions. Is a post-meeting doc.
noted No    
R5‑200553 Correction to NR PDCP Test cases 7.1.3.2.1, 7.1.3.2.2 and 7.1.3.2.3 Anritsu Ltd, Keysight Technologies CR Agreement
6.3.2.4.3.1.4PDCP
Yes
Yesr1 was produced. Editorial correction to table name.
revised No R5‑201096  
R5‑200554 Correction to NR RLC test case 7.1.2.3.11 ANRITSU LTD CR Agreement
6.3.2.4.3.1.3RLC
No
Yes
withdrawn Yes    
R5‑200555 Additions to Initial Conditions and Messages for SRS time mask with UL MIMO Samsung R&D Institute UK CR Agreement
5.3.2.5.1Tx Requirements (Clause 6)
Yes
Yes"Addition to SRS time mask with UL MIMO test case document was not treated since UL-MIMO out of scope of e-meeting"
not treated No    
R5‑200556 Discussion on FR2 absolute power control TP3 Samsung R&D Institute UK discussion Discussion
5.3.2.17Discussion Papers / Work Plan / TC lists
Yes
Yesnoted and proposal1 endorsed
noted No    
R5‑200557 Clarify absolute power tolerance for CA TP3 Samsung R&D Institute UK CR Agreement
5.3.2.5.1Tx Requirements (Clause 6)
Yes
Yes
agreed No    
R5‑200558 Beam Correspondence Mnemonic name update Samsung R&D Institute UK CR Agreement
7.2.1RF group docs still requiring WG verdict/confirmation - original A.I. retained
Yes
Yescommon impact.
agreed No    
R5‑200559 Beam correspondence TC message contents clarifications Samsung R&D Institute UK CR Agreement
5.3.2.5.1Tx Requirements (Clause 6)
Yes
Yesr1 was produced. Changed the derivation path in the additional message contents. r2 was produced.
revised No R5‑200910  
R5‑200560 Discussion on OFF Power for the SRS time mask with UL MIMO test case Samsung R&D Institute UK discussion  
5.3.2.17Discussion Papers / Work Plan / TC lists
Yes
Yes"Discussion on EIRP OFF power document not produced before FR2 MU pre-meeting deadline, and has reference to UL-MIMO which is out of scope of e-meeting."
not treated No    
R5‑200561 Addition of RRM Test Case 4.5.4.1 minimum requirements Samsung R&D Institute UK CR Agreement
5.3.2.9.1EN-DC with all NR cells in FR1 (Clause 4)
Yes
Yes"EN-DC with all NR cells in FR1 (Clause 4) Test case is not a GCF/PVG priority test and is not 100% complete , out of scope of e-meeting agenda "
not treated No    
R5‑200562 Addition of RRM Cell configuration mapping table for EN-DC FR1 Test Case 4.5.4.1 Samsung R&D Institute UK CR Agreement
5.3.2.9.6Clauses 1-3 / Annexes
Yes
Yes"EN EN-DC with all NR cells in FR1 (Clause 4) Test case is not a GCF/PVG priority test and is not 100% complete , out of scope of e-meeting agenda"
not treated No    
R5‑200563 Discussion on UE UL Carrier Reconfiguration Delay Samsung R&D Institute UK discussion  
5.3.2.9.1EN-DC with all NR cells in FR1 (Clause 4)
Yes
Yes"EN-DC with all NR cells in FR1 (Clause 4) Test case is not a GCF/PVG priority test and is not 100% complete , out of scope of e-meeting agenda "
not treated No    
R5‑200564 Correction to Statistical testing of delay and UE measurement performance in RRM tests Samsung R&D Institute UK CR Agreement
5.3.2.9.6Clauses 1-3 / Annexes
Yes
Yes
agreed No    
R5‑200565 Addition of RRC message content exceptions for UE UL Carrier Reconfiguration Delay Samsung R&D Institute UK CR Agreement
5.3.2.9.6Clauses 1-3 / Annexes
Yes
Yes"EN-DC with all NR cells in FR1 Test case is not a GCF/PVG priority test and is not 100% complete , out of scope of e-meeting agenda"
not treated No    
R5‑200566 Addition of NR SUL connection diagrams Huawei,Hisilicon CR Agreement
5.3.2.1TS 38.508-1
Yes
Yescover +NR r1 was produced. Comments from R&S. r2 was produced. i. Based on offline comments, update UE diagrams for SUL. Adding UE connection diagrams in which NR SUL and NR NUL transmitted on the same antenna.(Figure A.3.2.3.6 and A.3.2.3.8) ii. Adding Figure A.3.1.2.4: Test Equipment connection for NR SUL TX-tests with additional Spectrum Analyzer iii. Delete extra chapter title: A.3.1.2 Transmitter tests using Spectrum Analyser?
revised No R5‑200966  
R5‑200567 Update of test description for NR test case 6.2.2-MPR Huawei,Hisilicon CR Agreement
5.3.2.4.1Tx Requirements (Clause 6)
Yes
Yesmissed +"test description for"
withdrawn Yes    
R5‑200568 Update of test requirements for NR test case 6.5D.2.2 and 6.5D.2.4 Huawei,Hisilicon CR Agreement
5.3.2.4.1Tx Requirements (Clause 6)
Yes
Yesmissed +"test requirements for" r1 was produced. Cover update.
revised No R5‑200974  
R5‑200569 Update of NR SUL test cases Huawei,Hisilicon CR Agreement
5.3.2.4.1Tx Requirements (Clause 6)
Yes
Yes+ "test configurations for" r1 was produced.Correcting Title in the coversheet to solve 3GU issue. Adding content of table 6.4C.2.1.4-2 for PRACH message content in 6.4C.2. Correcting a mistake in the line above Table 6.4C.2.1.4-1. Based on offline comment, updating Test Channel bandwidth for Non-SUL carrier in Table 6.2C.3.4-1 to eliminate replication errors.
revised No R5‑200975  
R5‑200570 Update of NR test case 6.5.3.2-Spurious emission for UE co-existence Huawei,Hisilicon CR Agreement
5.3.2.4.1Tx Requirements (Clause 6)
Yes
YesSecoex
agreed No    
R5‑200571 Update of NR test case 7.4A Maximum input level for CA Huawei,Hisilicon CR Agreement
5.3.2.4.2Rx Requirements (Clause 7)
Yes
Yescorrected coversheet title from old: Update of NR test case 7.4A.1-MaxIL 2DL CA r1 was produced. Undone some changes to resolve overlapping with R5-200391 and R5-200727.
revised No R5‑200977  
R5‑200572 Update of NR test case 7.6A.2 Inband Blocking for CA Huawei,Hisilicon CR Agreement
5.3.2.4.2Rx Requirements (Clause 7)
Yes
Yesr1 was produced. Cover.
revised No R5‑200978  
R5‑200573 Update of 38.905 FR1 7.6A.2.1 Huawei,Hisilicon CR Agreement
5.3.2.16TR 38.905 (NR Test Points Radio Transmission and Reception )
Yes
Yescover title: Addition of TP analysis for FR1 In-band blocking for CA (2DL CA) Reissued as R5-200885 because of title change.
withdrawn Yes    
R5‑200574 Addition of Test point selection for FR1 in SUL test cases Huawei,Hisilicon CR Agreement
5.3.2.16TR 38.905 (NR Test Points Radio Transmission and Reception )
Yes
Yes
agreed No    
R5‑200575 Addition of test channel bandwidth for NR bands in 38.508-1 ZTE Corporation CR Agreement
7.2.1RF group docs still requiring WG verdict/confirmation - original A.I. retained
Yes
YesEricsson: WIC shall be NR_bands_BW_R16-UEConTest. r1 was produced. r2 was produced. Defined different low, mid, high test channel bandwidth for band n48 according to the restrictions to the channel bandwidth in different configurations.
revised No R5‑201065  
R5‑200576 Corrections on categories of NR CA physical layer capabilities in 38.508-2 ZTE Corporation, SGS Wireless CR Agreement
7.2.1RF group docs still requiring WG verdict/confirmation - original A.I. retained
Yes
Yesr1 was produced. Merged the content of R5-200733 into clause A.4.3.2A.3.2.
revised No R5‑200969  
R5‑200577 Correction to NSSAI Test Mode Command Qualcomm Technologies Int CR Agreement
6.3.2.3TS 38.509
No
Yes
withdrawn Yes    
R5‑200578 Corrections to RLC TC 7.1.2.3.5 and 7.1.2.2.5 Qualcomm Technologies Int CR Agreement
6.3.2.4.3.1.3RLC
No
Yeslate doc
withdrawn Yes    
R5‑200579 Corrections to RRC TC 8.2.2.7.1 Qualcomm Technologies Int CR Agreement