Tdoc List
2020-06-10 08:53
| Agenda | Topic | TDoc | Title | Source | Type | For | Avail | Treated | Decision | Wdrn | Replaced-by | Replaces |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 | Opening of the meeting | R5‑201300 | Agenda - opening session | WG Chairman | agenda | Information | Yes |
YesRAN5#87 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-201300.
| approved | No | ||
| R5‑201301 | RAN5#87 E-Meeting Timelines, Scope, Process | WG Chairman | agenda | Information | Yes |
Yes
| revised | No | R5‑202512 | |||
| R5‑202512 | RAN5#87 E-Meeting Timelines, Scope, Process | WG Chairman | agenda | Information | Yes |
Yesis endorsed.
| endorsed | No | R5‑201301 | |||
| 2 | Reports | |||||||||||
| 2.1 | Live Reports | R5‑201302 | RAN5 Leadership Team | WG Chairman | other | Information | Yes |
Yes
| noted | No | ||
| R5‑201303 | RAN5#86-e WG Minutes | ETSI Secretariat | report | Approval | Yes |
Yes
| approved | No | ||||
| R5‑201304 | RAN5#86-e WG Action Points | ETSI Secretariat | report | Information | Yes |
Yes
| noted | No | ||||
| R5‑201305 | Latest RAN Plenary notes | WG Chairman | report | Information | Yes |
Yes
| noted | No | ||||
| R5‑201306 | Latest RAN Plenary draft Report | WG Chairman | report | Information | Yes |
Yes
| noted | No | ||||
| R5‑201307 | Post Plenary Active Work Item update | ETSI Secretariat | other | Information | Yes |
Yes
| noted | No | ||||
| R5‑201568 | MCC TF160 Status Report | MCC TF160 | report | Approval | Yes |
Yesto be revised
| revised | No | R5‑202521 | |||
| 2.2 | General Reports for information | R5‑201308 | RAN5 SR to RP#87-e | WG Chairman | report | Information | Yes |
Yes
| noted | No | ||
| R5‑201309 | TF160 SR to RP#87-e | WG Chairman | report | Information | Yes |
Yes
| noted | No | ||||
| R5‑201549 | GCF 3GPP TCL after GCF CAG#62 | Ericsson | report | Information | Yes |
Yes
| noted | No | ||||
| R5‑201551 | 3GPP RAN5 CA status list (pre-RAN5#87-e meeting) | Ericsson | other | Information | Yes |
Yes
| noted | No | ||||
| 3 | Incoming Liaison Statements | R5‑201315 | Reply LS on support for eCall over NR | TSG SA | LS in | Action | Yes |
YesQualcomm clarified work to be done in CT1 and RAN2 under TEI16, RAN5 will wait for this to conclude
| noted | No | ||
| R5‑201316 | LS on publication of TS.51 V1.0 | GSMA TSG IoTOTA | LS in | Action | Yes |
Yes
| noted | No | ||||
| R5‑201319 | Reply LS on support for eCall over NR | TSG WG SA2 | LS in | Information | Yes |
Yes
| noted | No | ||||
| R5‑201594 | LS Announcing the publication of GSMA TS.48 Generic eUICC Test Profile for Device Testing version 2.0 | GSMA TSG eSIMTP | LS in | Information | Yes |
Yes
| noted | No | ||||
| 4 | RAN5 General Issues | R5‑201380 | Addition of new NR TC 11.3.9-UAC Operator Defined Access Category | Huawei, Hisilicon | CR | Agreement | Yes |
Yesr2
| revised | No | R5‑202669 | |
| R5‑202669 | Addition of new NR TC 11.3.9-UAC Operator Defined Access Category | Huawei, Hisilicon | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201380 | |||
| 4.1 | New Work Item proposals - for intro only | R5‑201474 | New WID on UE conformance test aspects for NR mobility enhancements | Huawei, Hisilicon, China Telecom | WID new | Approval | Yes |
Yes
| revised | No | R5‑202513 | |
| R5‑202513 | New WID on UE conformance test aspects for NR mobility enhancements | Huawei, Hisilicon, China Telecom | WID new | Approval | Yes |
YesR&S asked to be added.
WI is endorsed.
| endorsed | No | R5‑201474 | |||
| R5‑201475 | New WID on UE conformance test aspects for 5G V2X with NR sidelink | Huawei, Hisilicon | WID new | Approval | Yes |
Yes
| revised | No | R5‑202514 | |||
| R5‑202514 | New WID on UE conformance test aspects for 5G V2X with NR sidelink | Huawei, Hisilicon | WID new | Approval | Yes |
YesR&S asked to be added.
WI is endorsed.
| endorsed | No | R5‑201475 | |||
| R5‑201630 | New WID – Optimisations on UE radio capability signalling - NR/E-UTRA Aspects | Qualcomm CDMA Technologies | WID new | Approval | Yes |
Yes
| revised | No | R5‑202515 | |||
| R5‑202515 | New WID – Optimisations on UE radio capability signalling - NR/E-UTRA Aspects | Qualcomm CDMA Technologies | WID new | Approval | Yes |
Yesis endorsed.
| endorsed | No | R5‑201630 | |||
| R5‑201631 | New WID - Private Network Support for NG-RAN | Qualcomm CDMA Technologies | WID new | Approval | Yes |
Yes
| revised | No | R5‑202516 | |||
| R5‑202516 | New WID - Private Network Support for NG-RAN | Qualcomm CDMA Technologies | WID new | Approval | Yes |
Yesis endorsed.
| endorsed | No | R5‑201631 | |||
| R5‑201720 | New WID - UE Conformance Aspects – Even further mobility enhancement in E-UTRAN | China Telecom | WID new | Endorsement | Yes |
Yes
| revised | No | R5‑202517 | |||
| R5‑202517 | New WID - UE Conformance Aspects – Even further mobility enhancement in E-UTRAN | China Telecom | WID new | Endorsement | Yes |
Yesis endorsed.
| endorsed | No | R5‑201720 | |||
| R5‑201863 | New WI proposal for Rel-16 Enhancements on MIMO for NR(NR_eMIMO) | Huawei, HiSilicon, Samsung | WID new | Endorsement | Yes |
Yes
| revised | No | R5‑202518 | |||
| R5‑202518 | New WI proposal for Rel-16 Enhancements on MIMO for NR(NR_eMIMO) | Huawei, HiSilicon, Samsung | WID new | Endorsement | Yes |
Yesis endorsed.
| endorsed | No | R5‑201863 | |||
| R5‑201918 | New WID - UE Conformance Aspects - Support of NR Industrial Internet of Things (IoT) | CMCC, Nokia | WID new | Approval | Yes |
Yes
| revised | No | R5‑202519 | |||
| R5‑202519 | New WID - UE Conformance Aspects - Support of NR Industrial Internet of Things (IoT) | CMCC, Nokia | WID new | Approval | Yes |
Yesis endorsed.
R&S asked to be added.
| endorsed | No | R5‑201918 | |||
| R5‑202164 | New WID - UE Conformance Aspects - UE Power Saving in NR | CATT | WID new | Endorsement | Yes |
Yes
| revised | No | R5‑202520 | |||
| R5‑202520 | New WID - UE Conformance Aspects - UE Power Saving in NR | CATT | WID new | Endorsement | Yes |
Yesis endorsed.
| endorsed | No | R5‑202164 | |||
| 4.2 | General Discussion Papers | |||||||||||
| 4.2.1 | 5GS | R5‑201569 | Feature priority inputs for the RAN5 5GS work plan | MCC TF160 | discussion | Information | Yes |
YesOrange was wondering whether there is there any spec which is doing the work which we're doing here.
Ericsson: there is only RAN4 with the base stations.
| noted | No | ||
| R5‑201706 | Proposing new test cases for small TEI-16 WIs - inter-RAT HO from NR to EN-DC | China Telecommunications, China Unicom, Vodafone, China Mobile, NTT Docomo | discussion | Endorsement | Yes |
Yesproposal was accepted to add the test cases.
| noted | No | ||||
| R5‑201955 | Check List for adding new NR bands and for new channel bandwidth to existing NR bands | Ericsson | other | Endorsement | Yes |
Yes
| revised | No | R5‑202536 | |||
| R5‑202536 | Check List for adding new NR bands and for new channel bandwidth to existing NR bands | Ericsson | other | Endorsement | Yes |
Yes
| noted | No | R5‑201955 | |||
| R5‑202169 | Proposing new test cases for small TEI-16 WIs - voice fallback indication | CATT | discussion | Endorsement | Yes |
YesMotorola Mobility commented it shall be TS 38.331.
Proposal is noted and endorsed.
| noted | No | ||||
| 4.2.2 | All other topics | R5‑202023 | Issues with BeiDou GNSS scenarios | Spirent Communications | discussion | Discussion | Yes |
Yesin the next meeting the BeiDou scenarios need fixing.
Offline email thread with Rohde&Schwarz, CATT et al.
Affects SIG+RF.
Deferred.
r1
| revised | No | R5‑202553 | |
| 4.3 | RAN5 PRDs/Templates | R5‑201311 | RAN5#87-e LS Template | WG Chairman | other | Information | Yes |
Yes
| noted | No | ||
| 4.4 | Meeting schedule for 2020-21 | R5‑201312 | Meeting schedule for 2020 | WG Chairman | other | Information | Yes |
Yes
| noted | No | ||
| 4.5 | Tdocs for mid-week joint session | |||||||||||
| 4.5.1 | RF group docs for WG review/verdict - original A.I. retained | |||||||||||
| 4.5.2 | Sig group docs for WG review/verdict - original A.I. retained | |||||||||||
| 4.5.3 | Other open issues from joint sessions - original A.I. retained | |||||||||||
| 4.5.4 | UE Application Layer Data Throughput Performance TEI11_Test / TEI15_Test (TR 37.901) | |||||||||||
| 4.5.5 | GCF Test Optimisation | |||||||||||
| 4.5.6 | 5GS | |||||||||||
| 4.5.7 | Other | |||||||||||
| 5 | RF Functional Area | |||||||||||
| 5.1 | Review action points (fm A.I. 2.1) | |||||||||||
| 5.2 | Review incoming LS (fm A.I. 3) & new subject discussion papers | R5‑201310 | LS to RAN5 on NR DL RMC configuration for UE ACS tests | TSG WG RAN4 | LS in | Information | Yes |
YesMoved to RF.
No CR's addressing the actions in RAn5#87e .
LS author company (MTK ) , FR1 and FR2 ACS clause 7.5x test case author(s) (KEYS, Huawei, China Telecom, CMCC), to take this up in future RAN5 meetings to address the action to RAN5
| noted | No | ||
| R5‑201317 | Over-the-Air Radiated Performance Testing for 5G mm-Wave (FR2) UserEquipment | CTIA Certification Program Working Group - 5G Millimeter Wave Sub-Working Group | LS in | Information | Yes |
Yesmoved to RF.
Presented by Keysight USA.
Associated tdoc R5-202434(disc paper), R5-202435(CR), R5-202374(disc paper), R5-201846(CR), R5-201924(CR), R5-201853(CR), R5-201923(CR)
response LS will be decided during the RAN5#87e RF sessions
| noted | No | ||||
| R5‑201318 | LS on requirement in Power Class 2 for UL MIMO Test cases | GCF CAG | LS in | Action | Yes |
Yesmoved to RF.
Presented by Qualcomm.
Related discussion R5-202434. Related CR R5-20435.
| noted | No | ||||
| R5‑202505 | Reply LS from CTIA CCLLC OTA WG to the GCF SG Concerning Antenna Performance Assessments | CTIA Certification Program Working Group | LS in | Information | Yes |
Yesmoved to RF.
Presented by AT&T.
| noted | No | ||||
| 5.3 | Open Work Items | |||||||||||
| 5.3.1 | Rel-14 LTE CA configurations (UID - 720098) LTE_CA_R14-UEConTest | |||||||||||
| 5.3.1.1 | TS 36.508 | |||||||||||
| 5.3.1.2 | TS 36.521-1 | R5‑201481 | Addition of CA_48C and CA_48D to 36.521-1 Table 7.6.2A.5.5-2 | C Spire Wireless | CR | Agreement | Yes |
Yesno cl. aff.
r1
| revised | No | R5‑202705 | |
| R5‑202705 | Addition of CA_48C and CA_48D to 36.521-1 Table 7.6.2A.5.5-2 | C Spire Wireless | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201481 | |||
| R5‑201694 | Update REFSENS of some CA combinations in 7.3A.5 | Huawei, HiSilicon | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| 5.3.1.3 | TS 36.521-2 | R5‑201696 | Addition of Rel-14 capabilities of multiple CA in 36.521-2 | Huawei, HiSilicon | CR | Agreement | Yes |
YesRel14
r1
| revised | No | R5‑202818 | |
| R5‑202818 | Addition of Rel-14 capabilities of multiple CA in 36.521-2 | Huawei, HiSilicon | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201696 | |||
| 5.3.1.4 | TS 36.521-3 | |||||||||||
| 5.3.1.5 | TS 37.571-1 | |||||||||||
| 5.3.1.6 | TS 37.571-3 | |||||||||||
| 5.3.1.7 | TS 37.571-5 | |||||||||||
| 5.3.1.8 | TR 36.903 (E-UTRAN RRM TT analyses) | |||||||||||
| 5.3.1.9 | TR 36.904 (E-UTRAN Radio Reception TT analyses) | |||||||||||
| 5.3.1.10 | TR 36.905 (E-UTRAN Test Points Radio Transmission and Reception ) | R5‑201724 | Addition of TP analysis for CA_1A-7A-7A to 36.905 | Huawei, HiSilicon | CR | Agreement | Yes |
YesRel14
r1
| revised | No | R5‑202706 | |
| R5‑202706 | Addition of TP analysis for CA_1A-7A-7A to 36.905 | Huawei, HiSilicon | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201724 | |||
| R5‑201725 | Addition of TP analysis for CA_1A-7A-28A BW set2 to 36.905 | Huawei, HiSilicon | CR | Agreement | Yes |
YesRel14
r1
| revised | No | R5‑202707 | |||
| R5‑202707 | Addition of TP analysis for CA_1A-7A-28A BW set2 to 36.905 | Huawei, HiSilicon | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201725 | |||
| R5‑201726 | Addition of TP analysis for CA_3C-20A to 36.905 | Huawei, HiSilicon | CR | Agreement | Yes |
YesRel14
r1
| revised | No | R5‑202819 | |||
| R5‑202819 | Addition of TP analysis for CA_3C-20A to 36.905 | Huawei, HiSilicon | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201726 | |||
| 5.3.1.11 | Discussion Papers / Work Plan / TC lists | |||||||||||
| 5.3.2 | 5G system with NR and LTE (UID - 760087) 5GS_NR_LTE-UEConTest | |||||||||||
| 5.3.2.1 | TS 38.508-1 | R5‑201337 | Correction to Table 7.3.1-7 NZP-CSI-RS-Resource for TRS | Huawei, Hisilicon | CR | Agreement | Yes |
Yes
| agreed | No | ||
| R5‑201595 | TRS - PowerControlOffset correction for UE RF testing | Keysight Technologies UK Ltd | CR | Agreement | Yes |
Yes16.3.0
r1
| revised | No | R5‑202708 | |||
| R5‑202708 | TRS - PowerControlOffset correction for UE RF testing | Keysight Technologies UK Ltd | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201595 | |||
| R5‑201604 | Clarifications on the QoQZ validation procedure for RRM | ROHDE & SCHWARZ | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202703 | |||
| R5‑202703 | Clarifications on the QoQZ validation procedure for RRM | ROHDE & SCHWARZ | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201604 | |||
| R5‑201627 | Correction to PDCCH-ConfigCommon Table 4.6.3-96 for IE searchSpaceOtherSystemInformation | Qualcomm Finland RFFE Oy | CR | Agreement | Yes |
Yesoverlapping with R5-201571.
| withdrawn | Yes | ||||
| R5‑201731 | Addition of NR SUL connection diagram in A.3.1.4 | Huawei,Hisilicon | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑201844 | Updating DCI related messages | Huawei, HiSilicon | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202878 | |||
| R5‑202878 | Updating DCI related messages | Huawei, HiSilicon | CR | Agreement | Yes |
Yes
| revised | No | R5‑202962 | R5‑201844 | ||
| R5‑202962 | Updating DCI related messages | Huawei, HiSilicon | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202878 | |||
| R5‑202084 | Addition of Quiet Zone size above 30cm to TS 38.508-1 | ROHDE & SCHWARZ | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
| R5‑202123 | CR to 38.508-1 to clarify the test zone/quiet zone | Keysight Technologies UK Ltd | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑202160 | Addition of BW to Table 4.6.3-33 | Qualcomm Finland RFFE Oy | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202879 | |||
| R5‑202879 | Addition of BW to Table 4.6.3-33 | Qualcomm Finland RFFE Oy | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202160 | |||
| R5‑202203 | Clarification of disabling Tx diversity for FR2 UE | Huawei, HiSilicon | CR | Agreement | Yes |
Yes16.3.0
r4
| revised | No | R5‑202880 | |||
| R5‑202880 | Clarification of disabling Tx diversity for FR2 UE | Huawei, HiSilicon | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202203 | |||
| R5‑202210 | Corrections on test frequencies for inter-band EN-DC configurations within FR1 for five bands in 38.508-1 | ZTE Corporation | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑202239 | Addition of PUCCH-ResourceId for CQI reporting test case | Qualcomm Wireless GmbH | CR | Agreement | No |
Yeslate doc
contents are captured in doc 2243.
| withdrawn | Yes | ||||
| R5‑202241 | Restructuring 38.508-1 message contents for Demod and CSI reporting test cases | Qualcomm Wireless GmbH | CR | Agreement | Yes |
Yesr3
| revised | No | R5‑202881 | |||
| R5‑202881 | Restructuring 38.508-1 message contents for Demod and CSI reporting test cases | Qualcomm Wireless GmbH | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202241 | |||
| R5‑202243 | Update of PUCCH-ResourceId for Demod test cases | Qualcomm Wireless GmbH | CR | Agreement | Yes |
Yesr2
| revised | No | R5‑202882 | |||
| R5‑202882 | Update of PUCCH-ResourceId for Demod test cases | Qualcomm Wireless GmbH | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202243 | |||
| R5‑202244 | Correction to nrofRBs under TRS CSI-FrequencyOccupation for Demod test cases with 10 MHz CBW | Qualcomm Wireless GmbH | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑202246 | Update to default value of PDSCH-to-HARQ_feedback timing indicator (k1) | Qualcomm Wireless GmbH | CR | Agreement | Yes |
Yeslate doc
r2
pending RAN4 verdict of R4-2007279 (agreed).
| revised | No | R5‑202967 | |||
| R5‑202967 | Update to default value of PDSCH-to-HARQ_feedback timing indicator (k1) | Qualcomm Wireless GmbH | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202246 | |||
| R5‑202255 | Configuration of p-ZP-CSI-RS-ResourceSet for PDSCH Demod test cases | Qualcomm Wireless GmbH | CR | Agreement | Yes |
Yesr2
| revised | No | R5‑202883 | |||
| R5‑202883 | Configuration of p-ZP-CSI-RS-ResourceSet for PDSCH Demod test cases | Qualcomm Wireless GmbH | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202255 | |||
| R5‑202284 | Correction to configuration bwp-id parameter in TCI-State IE | Anritsu | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑202285 | Correction to PRB-Id for secondHopPRB | Anritsu | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202820 | |||
| R5‑202820 | Correction to PRB-Id for secondHopPRB | Anritsu | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202285 | |||
| R5‑202409 | Update PDCCH-ControlResourceSet for RRM testing | Keysight Technologies UK Ltd | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑202410 | Addition Physical Layer Parameter section for RRM testing | Keysight Technologies UK Ltd | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑202449 | Correction of test frequencies for DC n71AA | ROHDE & SCHWARZ | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑202451 | Correction of test frequencies for Band n79 | ROHDE & SCHWARZ | CR | Agreement | Yes |
Yesconflict with E\\ CR R5-201984.
| withdrawn | Yes | ||||
| 5.3.2.2 | TS 38.508-2 | R5‑202108 | Updates on UE capability for Rel-15 NR CA configuration | NTT DOCOMO INC. | CR | Agreement | Yes |
Yes
| agreed | No | ||
| R5‑202224 | Update ICS proforma tables for UE implementation types in A.4.1 of 38.508-2 | ZTE Corporation | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202709 | |||
| R5‑202709 | Update ICS proforma tables for UE implementation types in A.4.1 of 38.508-2 | ZTE Corporation | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202224 | |||
| R5‑202226 | Update NR intra-band contiguous CA implementation capabilities in 38.508-2 | ZTE Corporation | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑202228 | Update RF baseline implementation capabilities in 38.508-2 | ZTE Corporation | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑202286 | Introducing new condition on UE reported parameter in txDirectCurrentLocation | Anritsu | CR | Agreement | Yes |
Yes"Associated discussion R5-202417
Author confirmed no overlap
Depends on the outcome of discussion 2417 during the meeting, may not needed
RAN5 RF decided to use option2 prop1 of 2417 hence this can be w/drawn"
| withdrawn | Yes | ||||
| R5‑202446 | Addition of EN-DC configurations DC_41C_n41A and DC_41D_n41A | ROHDE & SCHWARZ | CR | Agreement | Yes |
Yeslate doc
| agreed | No | ||||
| 5.3.2.3 | TS 38.509 | R5‑202118 | CR to 38.509 to clarify UBF for Intra-Band Carrier Aggregation | Keysight Technologies UK Ltd | CR | Agreement | Yes |
YesR5-xx
r1
| revised | No | R5‑202884 | |
| R5‑202884 | CR to 38.509 to clarify UBF for Intra-Band Carrier Aggregation | Keysight Technologies UK Ltd | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202118 | |||
| 5.3.2.4 | TS 38.521-1 | |||||||||||
| 5.3.2.4.1 | Tx Requirements (Clause 6) | R5‑201598 | Correction of lower limit for test ID 55 in test 6.2.3 | Keysight Technologies UK Ltd | CR | Agreement | Yes |
Yes
| agreed | No | ||
| R5‑201599 | Correction on how to modify P-Max in test 6.2.4 and 6.2D.4 | Keysight Technologies UK Ltd | CR | Agreement | Yes |
Yesnot strictly needed.
| withdrawn | Yes | ||||
| R5‑201732 | Update of Test requirement of NS_100 in NR test case 6.2.3 A-MPR | Huawei,Hisilicon | CR | Agreement | Yes |
YesRAN4 may submit a CR to clarify this in next meeting.
| withdrawn | Yes | ||||
| R5‑201733 | Update of NR test case 6.2A.3 AMPR for CA | Huawei,Hisilicon | CR | Agreement | Yes |
Yesr2
| revised | No | R5‑202710 | |||
| R5‑202710 | Update of NR test case 6.2A.3 AMPR for CA | Huawei,Hisilicon | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201733 | |||
| R5‑201734 | Addition of NR test case 6.3C.1 Minimum output power for SUL | Huawei,Hisilicon | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑201735 | Addition of NR test case 6.3C.2 Transmit OFF power for SUL | Huawei,Hisilicon | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑201736 | Addition of NR test case 6.3C.3 Transmit ON/OFF time mask for SUL | Huawei,Hisilicon | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑201737 | Addition of NR test case 6.3C.4.1-Absolute power tolerance for SUL | Huawei,Hisilicon | CR | Agreement | Yes |
Yesr2
| revised | No | R5‑202711 | |||
| R5‑202711 | Addition of NR test case 6.3C.4.1-Absolute power tolerance for SUL | Huawei,Hisilicon | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201737 | |||
| R5‑201738 | Addition of NR test case 6.3C.4.2 Power Control Relative power tolerance for SUL | Huawei,Hisilicon | CR | Agreement | Yes |
Yesr2
| revised | No | R5‑202712 | |||
| R5‑202712 | Addition of NR test case 6.3C.4.2 Power Control Relative power tolerance for SUL | Huawei,Hisilicon | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201738 | |||
| R5‑201739 | Addition of NR test case 6.3C.4.3 Aggregate power tolerance for SUL | Huawei,Hisilicon | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑201740 | Update of NR test case 6.5.2.4 ACLR | Huawei,Hisilicon | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202713 | |||
| R5‑202713 | Update of NR test case 6.5.2.4 ACLR | Huawei,Hisilicon | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201740 | |||
| R5‑201741 | Update of NR test case 6.5C.3.3-Additional spurious emissions for SUL | Huawei,Hisilicon | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑201763 | Aligning A-MPR clause with TS 38.101-1 Rel-15 | Ericsson | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202886 | |||
| R5‑202886 | Aligning A-MPR clause with TS 38.101-1 Rel-15 | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201763 | |||
| R5‑201766 | Update of test case 6.2.3 UE A_MPR, NS_40 | Ericsson | CR | Agreement | Yes |
Yesr2
| revised | No | R5‑202821 | |||
| R5‑202821 | Update of test case 6.2.3 UE A_MPR, NS_40 | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201766 | |||
| R5‑201768 | Update of test case 6.2.3 UE A_MPR, NS_41 | Ericsson | CR | Agreement | Yes |
Yesr3
| revised | No | R5‑202822 | |||
| R5‑202822 | Update of test case 6.2.3 UE A_MPR, NS_41 | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201768 | |||
| R5‑201770 | Update of test case 6.2.3 UE A_MPR, NS_42 | Ericsson | CR | Agreement | Yes |
Yesr2
| revised | No | R5‑202714 | |||
| R5‑202714 | Update of test case 6.2.3 UE A_MPR, NS_42 | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201770 | |||
| R5‑201833 | Update of Refsense requirements for n79 | Rohde & Schwarz | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑201845 | Editorial correction of 6.2.1 test requirements | Huawei, HiSilicon | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑201846 | Updating 6.2.1 to add test method for UEs with 2 Tx antennas | Huawei, HiSilicon | CR | Agreement | Yes |
YesOPPO agreed with Huawei that single port cannot be included in the UL MIMO case. The codebook using in UL MIMO case is applied for 2-layer UL MIMO transmission which is impossible to use with only one antenna port. Better capture this requirement in 6.2.1.
Qualcomm: this CR is addressing Transmit Diversity: We agreeo that measurements are per port, but when you use two connectors mapped to one port and sum powers => Transmit diversity (TxD), for which there are no RAN 4 requirements. So the request is to please allow RAN 4 to figure out Transmit diversity requirements, and it could be discussed and support your TxD proposals for 38.521-1 -> 6.2.1. Otherwise it will generate confusion, especially if RAN 4 eventually agrees on something else after we prematurely forced something in RAN 5 spec. Therefore requesting to withdraw the CR.
| not pursued | No | ||||
| R5‑201847 | Updating 6.3.4.3 alternating sub-test | Huawei, HiSilicon | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑201935 | Updates to test case 6.2.2 UE maximum output power reduction | Ericsson | CR | Agreement | Yes |
YesBased on offline discussions this CR is not agreeable.
| withdrawn | Yes | ||||
| R5‑201936 | Updates to test case 6.5.2.4.1, NR ACLR | Ericsson | CR | Agreement | Yes |
Yesr3
| revised | No | R5‑202940 | |||
| R5‑202940 | Updates to test case 6.5.2.4.1, NR ACLR | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201936 | |||
| R5‑201937 | Updates to test case 6.5.2.2, Spectrum Emission Mask | Ericsson | CR | Agreement | Yes |
Yesr2
| revised | No | R5‑202765 | |||
| R5‑202765 | Updates to test case 6.5.2.2, Spectrum Emission Mask | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201937 | |||
| R5‑202110 | NS_05 corrections related to n65 | Dish Network | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202887 | |||
| R5‑202887 | NS_05 corrections related to n65 | Dish Network | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202110 | |||
| R5‑202172 | correction 6.5.3.1.3 general spurious emission limits | T-Mobile USA Inc. | CR | Agreement | Yes |
YesR5
Content is included in R5-202431.
| withdrawn | Yes | ||||
| R5‑202188 | Corrections on network signalling value abbreviation in 38.521-1 | ZTE Corporation | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202888 | |||
| R5‑202888 | Corrections on network signalling value abbreviation in 38.521-1 | ZTE Corporation | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202188 | |||
| R5‑202206 | Corrections on NS signalling label for band n39 in 38.521-1 | ZTE Corporation, Ericsson, Qualcomm, China Unicom, Bureau Veritas, Huawei, Hisilicon | CR | Agreement | Yes |
Yesr3
| revised | No | R5‑202889 | |||
| R5‑202889 | Corrections on NS signalling label for band n39 in 38.521-1 | ZTE Corporation, Ericsson, Qualcomm, China Unicom, Bureau Veritas, Huawei, Hisilicon | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202206 | |||
| R5‑202211 | Correct power window size to 6.4.2.2 | Guangdong OPPO Mobile Telecom. | CR | Agreement | Yes |
Yesmerged into R5-202420.
| withdrawn | Yes | ||||
| R5‑202217 | Corrections on transmitter power for CA in 38.521-1 | ZTE Corporation | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑202287 | Correction on txDirectCurrentLocation in FR1 SA tests | Anritsu | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202890 | |||
| R5‑202890 | Correction on txDirectCurrentLocation in FR1 SA tests | Anritsu | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202287 | |||
| R5‑202420 | Update Uplink power control window size for SA TX TCs | QUALCOMM Europe Inc. - Italy, OPPO | CR | Agreement | Yes |
Yesr1
Merge changes in R5-202211.
| revised | No | R5‑202715 | |||
| R5‑202715 | Update Uplink power control window size for SA TX TCs | QUALCOMM Europe Inc. - Italy, OPPO | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202420 | |||
| R5‑202427 | Update for 6.5.3.3 Additional spurious emissions | QUALCOMM Europe Inc. - Italy | CR | Agreement | Yes |
Yesr4
| revised | No | R5‑202823 | |||
| R5‑202823 | Update for 6.5.3.3 Additional spurious emissions | QUALCOMM Europe Inc. - Italy | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202427 | |||
| R5‑202431 | Update for 6.5.3.1 General spurious emissions | QUALCOMM Europe Inc. - Italy, T-Mobile USA | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202716 | |||
| R5‑202716 | Update for 6.5.3.1 General spurious emissions | QUALCOMM Europe Inc. - Italy, T-Mobile USA | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202431 | |||
| R5‑202435 | Updated MOP UL MIMO test case to include steps for per port testing | QUALCOMM JAPAN LLC. | CR | Agreement | Yes |
YesQualcomm: we address UL MIMO & SISO Power class consistency: Huawei's points w.r.t to QC's newly added step 4 in this CR are valid. Perhaps we need some corrections. Two other options are possible.
r2
| revised | No | R5‑202891 | |||
| R5‑202891 | Updated MOP UL MIMO test case to include steps for per port testing | QUALCOMM JAPAN LLC. | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202435 | |||
| 5.3.2.4.2 | Rx Requirements (Clause 7) | R5‑201597 | Correction of 4RX Reference requirement for n77 high range in 7.3.2 | Keysight Technologies UK Ltd | CR | Agreement | Yes |
Yes
| agreed | No | ||
| R5‑201742 | Update test description of NR test case 7.6.3-Out-of-band blocking | Huawei,Hisilicon | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑201743 | Addition of NR test case 7.6C.2-Inband Blocking for SUL | Huawei,Hisilicon | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202717 | |||
| R5‑202717 | Addition of NR test case 7.6C.2-Inband Blocking for SUL | Huawei,Hisilicon | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201743 | |||
| R5‑201744 | Addition of NR test case 7.6C.3 Out-of-band blocking for SUL | Huawei,Hisilicon | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑201841 | Skipping 2Rx testing on bands where UE support 4Rx for SA test cases | Huawei, HiSilicon, CAICT, OPPO, Samsung, Bureau Veritas | CR | Agreement | Yes |
YesDish did not agree to this interpretation, 2Rx antenna port testing is required, and furthermore, this is a RAN4 required change.
r3
| revised | No | R5‑202941 | |||
| R5‑202941 | Skipping 2Rx testing on bands where UE support 4Rx for SA test cases | Huawei, HiSilicon, CAICT, OPPO, Samsung, Bureau Veritas | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201841 | |||
| R5‑201848 | Updating REFSENS to add several R15 CA configurations | Huawei, HiSilicon | CR | Agreement | Yes |
Yesr1
to be withdrawn and merged into 2377r1.
| revised | No | R5‑202875 | |||
| R5‑202875 | Updating REFSENS to add several R15 CA configurations | Huawei, HiSilicon | CR | Agreement | Yes |
Yes
| withdrawn | Yes | R5‑201848 | |||
| R5‑202109 | Correction to n70 asymmetric test points in Rx tests | Dish Network | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑202377 | Re-organization of CA refsens test cases | Ericsson, WE Certification, DISH | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202942 | |||
| R5‑202942 | Re-organization of CA refsens test cases | Ericsson, WE Certification, DISH | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202377 | |||
| R5‑202380 | Update of UL configuration in REFSENS | Huawei, HiSilicon, Guangdong OPPO Mobile Telecom | CR | Agreement | Yes |
Yesr1
revision includes changes in R5-202426.
r2
| revised | No | R5‑202718 | |||
| R5‑202718 | Update of UL configuration in REFSENS | Huawei, HiSilicon, Guangdong OPPO Mobile Telecom | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202380 | |||
| R5‑202394 | Diversity Characteristics requirements alignment | Samsung R&D Institute UK | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202719 | |||
| R5‑202719 | Diversity Characteristics requirements alignment | Samsung R&D Institute UK | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202394 | |||
| R5‑202426 | Update for 7.3.2 Ref sensitivity power level | QUALCOMM Europe Inc. - Italy | CR | Agreement | Yes |
Yesmerged into Huawei's R5-202380.
| withdrawn | Yes | ||||
| 5.3.2.4.3 | Clauses 1-5 / Annexes | R5‑201452 | Updates of MU and TT in TS 38.521_1 | NTT DOCOMO INC. | CR | Agreement | No |
Yes
| withdrawn | Yes | ||
| R5‑201455 | Updates of MU and TT in TS 38.521-1 | NTT DOCOMO INC. | CR | Agreement | 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‑201596 | Correction and clarifications of default DL physical channels power in annex C | Keysight Technologies UK Ltd | CR | Agreement | Yes |
Yesr2
| revised | No | R5‑202892 | |||
| R5‑202892 | Correction and clarifications of default DL physical channels power in annex C | Keysight Technologies UK Ltd | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201596 | |||
| R5‑201745 | Update of Annex F.3.2 and F.3.3 | Huawei,Hisilicon | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑201801 | Update of clause 5 to TS 38.521-1 in R15 | China Unicom | CR | Agreement | Yes |
Yesr1
| agreed | No | ||||
| R5‑201834 | Correction of FR1 PUCCH EVM definition | Rohde & Schwarz | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑202405 | Receiver characteristics testing update to 38.521-1 | Samsung R&D Institute UK | CR | Agreement | Yes |
Yes
| revised | No | R5‑202807 | |||
| R5‑202807 | Receiver characteristics testing update to 38.521-1 | Samsung R&D Institute UK | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202405 | |||
| R5‑202422 | Update F.1.2 with Relative Uplink power measurement uncertainty as 6.3.4.3 | QUALCOMM Europe Inc. - Italy | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑202503 | CR on EVM Window Centre Timing Definition in FR1 | Skyworks Solutions Inc. | CR | Agreement | Yes |
Yeslate doc
| agreed | No | ||||
| 5.3.2.5 | TS 38.521-2 | R5‑202119 | CR to 38.521-2 to correct Clenshaw-Curtis Weights at the Poles for CDF/CCDF | Keysight Technologies UK Ltd, Verizon, ETS-Lindgren Europe | CR | Agreement | Yes |
Yesr1
changes over changes.
r2
| revised | No | R5‑202720 | |
| R5‑202720 | CR to 38.521-2 to correct Clenshaw-Curtis Weights at the Poles for CDF/CCDF | Keysight Technologies UK Ltd, Verizon, ETS-Lindgren Europe | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202119 | |||
| R5‑202120 | CR to 38.521-2 to correct Clenshaw-Curtis Weight Equations | Keysight Technologies UK Ltd, Verizon, ETS-Lindgren Europe | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑202121 | CR to 38.521-2 to properly define Link and Meas Angles | Keysight Technologies UK Ltd | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202721 | |||
| R5‑202721 | CR to 38.521-2 to properly define Link and Meas Angles | Keysight Technologies UK Ltd | CR | Agreement | Yes |
Yeswrong Tdoc# on cover.
| revised | No | R5‑203117 | R5‑202121 | ||
| R5‑203117 | CR to 38.521-2 to properly define Link and Meas Angles | Keysight Technologies UK Ltd | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202721 | |||
| R5‑202122 | CR to 38.521-2 to clarify the applicability of QoQZ validation | Keysight Technologies UK Ltd | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑202381 | CR to 38.521-2: On the order of test steps for output power dynamics test cases | Keysight Technologies UK Ltd | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202943 | |||
| R5‑202943 | CR to 38.521-2: On the order of test steps for output power dynamics test cases | Keysight Technologies UK Ltd | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202381 | |||
| 5.3.2.5.1 | Tx Requirements (Clause 6) | R5‑201328 | Add n261 to FR2 ACLR requirements | Qualcomm Finland RFFE Oy | CR | Agreement | Yes |
Yes
| agreed | No | ||
| R5‑201329 | Add NS 202 requirements to FR2 additional spurious emission test case | Qualcomm Finland RFFE Oy | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202885 | |||
| R5‑202885 | Add NS 202 requirements to FR2 additional spurious emission test case | Qualcomm Finland RFFE Oy | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201329 | |||
| R5‑201330 | Update to UBF command implementation for Relative power sub tests | Qualcomm Finland RFFE Oy | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑201795 | Introduction of New TC 6.4A.2.2.4 Carrier leakage for 5UL CA | LG Electronics | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑201796 | Introduction of New TC 6.4A.2.2.5 Carrier leakage for 6UL CA | LG Electronics | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑201797 | Introduction of New TC 6.4A.2.2.6 Carrier leakage for 7UL CA | LG Electronics | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑201811 | Introduction of New TC 6.4A.2.2.7 Carrier leakage for 8UL CA | LG Electronics | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑201812 | Introduction of New TC 6.4A.2.3.2 In-band emissions for 3UL CA | LG Electronics | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑201813 | Introduction of New TC 6.4A.2.3.3 In-band emissions for 4UL CA | LG Electronics | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑201814 | Introduction of New TC 6.4A.2.3.4 In-band emissions for 5UL CA | LG Electronics | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑201815 | Introduction of New TC 6.4A.2.3.5 In-band emissions for 6UL CA | LG Electronics | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑201849 | Updating common uplink allocation for PC1 | Huawei, HiSilicon | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑201850 | Cleaning up references to common uplink configuration | Huawei, HiSilicon | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑201851 | Updating test requirements of 6.2.3 AMPR for NS_201 | Huawei, HiSilicon | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑202028 | Beam correspondence - SRS configuration corrections in section 6.6.1 | Keysight Technologies UK Ltd | CR | Agreement | Yes |
YesOverlapping with R5-202408.
r1
R4-2008014 was not agreed because more time was requested for further study so conclusion is to postpone further discussion to Aug meeting.
| revised | No | R5‑202995 | |||
| R5‑202995 | Beam correspondence - SRS configuration corrections in section 6.6.1 | Keysight Technologies UK Ltd | CR | Agreement | No |
Yeswithdrawn after the meeting based on RAN4 outcome.
| withdrawn | Yes | R5‑202028 | |||
| R5‑202045 | Correction of test metric in minimum conformace requirements and some test style in 6.3.2 of SA FR2 R15 | CAICT | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑202083 | Addition of Quiet Zone size above 30cm to TS 38.521-2 | ROHDE & SCHWARZ | CR | Agreement | Yes |
YesAuthor confirmed no conflict,
: based on outcome of discussion paper, propose to mark this CR as ""Not Pursued""."
| not pursued | No | ||||
| R5‑202130 | Editorial correction of test case 6.5.1 Occupied bandwidth to align with core spec | KTL | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202893 | |||
| R5‑202893 | Editorial correction of test case 6.5.1 Occupied bandwidth to align with core spec | KTL | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202130 | |||
| R5‑202131 | Editorial correction of Tx test cases for Out of band emission to align with core spec | KTL | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202894 | |||
| R5‑202894 | Editorial correction of Tx test cases for Out of band emission to align with core spec | KTL | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202131 | |||
| R5‑202132 | Update to test case 6.5A.1.1 Occupied bandwidth for 2UL CA | KTL, NTT DOCOMO INC. | CR | Agreement | Yes |
Yesr2
| revised | No | R5‑202824 | |||
| R5‑202824 | Update to test case 6.5A.1.1 Occupied bandwidth for 2UL CA | KTL, NTT DOCOMO INC. | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202132 | |||
| R5‑202133 | Update to 6 test cases 6.5A.1.x Occupied bandwidth for 3 to 8 UL CA | KTL | CR | Agreement | Yes |
Yes"Version inconsistency, Release inconsistency
-3GU: 15.3.0 / CR coversheet: 16.3.0
-3GU: Rel-15 / CR coversheet: Rel-16"
reissued as R5-202501 because of wrong Rel and version
| withdrawn | Yes | ||||
| R5‑202501 | Update to 6 test cases 6.5A.1.x Occupied bandwidth for 3 to 8 UL CA | KTL, NTT DOCOMO INC. | CR | Agreement | Yes |
Yesr2
| revised | No | R5‑202827 | |||
| R5‑202827 | Update to 6 test cases 6.5A.1.x Occupied bandwidth for 3 to 8 UL CA | KTL, NTT DOCOMO INC. | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202501 | |||
| R5‑202134 | Update to test case 6.5A.2.1.1 Spectrum Emission Mask for 2UL CA | KTL, NTT DOCOMO INC. | CR | Agreement | Yes |
Yesr2
| revised | No | R5‑202825 | |||
| R5‑202825 | Update to test case 6.5A.2.1.1 Spectrum Emission Mask for 2UL CA | KTL, NTT DOCOMO INC. | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202134 | |||
| R5‑202135 | Update to 6 test cases 6.5A.2.1.x Spectrum Emission Mask for 3 to 8 UL CA | KTL | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑202136 | Update to test case 6.5A.2.2.1 Adjacent channel leakage ratio for 2UL CA | KTL, NTT DOCOMO INC. | CR | Agreement | Yes |
Yesr2
| revised | No | R5‑202826 | |||
| R5‑202826 | Update to test case 6.5A.2.2.1 Adjacent channel leakage ratio for 2UL CA | KTL, NTT DOCOMO INC. | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202136 | |||
| R5‑202137 | Update to 6 test cases 6.5A.2.2.x Adjacent channel leakage ratio for 3 to 8 UL CA | KTL | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑202199 | Clarification of disabling Tx diversity for FR2 UE for SA FR2 testing | Huawei, HiSilicon | CR | Agreement | Yes |
Yesr2
| revised | No | R5‑202895 | |||
| R5‑202895 | Clarification of disabling Tx diversity for FR2 UE for SA FR2 testing | Huawei, HiSilicon | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202199 | |||
| R5‑202209 | Updates of Test Points of Tx CA test cases | NTT DOCOMO INC. | CR | Agreement | Yes |
Yesr2
| revised | No | R5‑202896 | |||
| R5‑202896 | Updates of Test Points of Tx CA test cases | NTT DOCOMO INC. | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202209 | |||
| R5‑202288 | Correction on txDirectCurrentLocation in FR2 SA tests | Anritsu | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202897 | |||
| R5‑202897 | Correction on txDirectCurrentLocation in FR2 SA tests | Anritsu | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202288 | |||
| R5‑202396 | Additions to Initial Conditions and Messages for SRS time mask with UL MIMO | Samsung R&D Institute UK | CR | Agreement | Yes |
Yesr1 was prooduced to remove the overlap with Ericsson’s CR in R5-201939.
| revised | No | R5‑202722 | |||
| R5‑202722 | Additions to Initial Conditions and Messages for SRS time mask with UL MIMO | Samsung R&D Institute UK | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202396 | |||
| R5‑202408 | Addition to Beam Correspondence test | Samsung R&D Institute UK | CR | Agreement | Yes |
Yesconflict with Keysight's R5-202028
| withdrawn | Yes | ||||
| R5‑202450 | Correction of Spectrum Emission Mask CA test cases | ROHDE & SCHWARZ | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑202456 | Update on transmit modulation quality test cases | ROHDE & SCHWARZ | CR | Agreement | Yes |
Yeslate doc
r1
| revised | No | R5‑202898 | |||
| R5‑202898 | Update on transmit modulation quality test cases | ROHDE & SCHWARZ | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202456 | |||
| 5.3.2.5.2 | Rx Requirements (Clause 7) | R5‑201938 | Aligning test procedure for Rx beam peak direction | Ericsson | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202723 | |
| R5‑202723 | Aligning test procedure for Rx beam peak direction | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201938 | |||
| R5‑201939 | Updating SRS config table in test case 6.3D.3.4 | Ericsson | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202828 | |||
| R5‑202828 | Updating SRS config table in test case 6.3D.3.4 | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201939 | |||
| R5‑202046 | Correction of uplink configuration table number in minimum conformace requirements and test requirement table of 7.4 of SA FR2 R15 | CAICT | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑202289 | Update to SA FR2 Receiver Spurious Emission Test Case | Anritsu | CR | Agreement | Yes |
Yesr2
| revised | No | R5‑202899 | |||
| R5‑202899 | Update to SA FR2 Receiver Spurious Emission Test Case | Anritsu | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202289 | |||
| R5‑202447 | Editorial correction to the test requirement of in-band blocking | ROHDE & SCHWARZ | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| 5.3.2.5.3 | Clauses 1-5 / Annexes | R5‑201453 | Updates of MU and TT in TS 38.521-2 | NTT DOCOMO INC. | CR | Agreement | Yes |
Yesmerged into R5-202290
| withdrawn | Yes | ||
| R5‑201835 | Correction of FR2 PUCCH EVM definition | Rohde & Schwarz | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑202027 | Beam correspondence - SRS configuration corrections in annex K.1.1 | Keysight Technologies UK Ltd | CR | Agreement | Yes |
YesR4-2008014 was not agreed because more time was requested for further study so conclusion is to postpone further discussion to Aug meeting.
Withdrawn after the meeting based on RAN4 outcome.
| withdrawn | Yes | ||||
| R5‑202044 | Alignment of section 3 and 5 with core spec of SA FR2 R15 | CAICT | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202724 | |||
| R5‑202724 | Alignment of section 3 and 5 with core spec of SA FR2 R15 | CAICT | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202044 | |||
| R5‑202245 | Core spec alignment of k1 value for RF test cases | Qualcomm Wireless GmbH | CR | Agreement | Yes |
Yesr1
pending RAN4 verdict of R4-2007279 (agreed).
| revised | No | R5‑202968 | |||
| R5‑202968 | Core spec alignment of k1 value for RF test cases | Qualcomm Wireless GmbH | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202245 | |||
| R5‑202290 | Updates of FR2 MU and TT in TS 38.521-2 | Anritsu, NTT DOCOMO INC. | CR | Agreement | Yes |
Yescl. aff.
r4
| revised | No | R5‑202900 | |||
| R5‑202900 | Updates of FR2 MU and TT in TS 38.521-2 | Anritsu, NTT DOCOMO INC. | CR | Agreement | Yes |
Yesfirst agreed, then a conflict with KTL's R5-202894 was spotted concerning Step 3.
| revised | No | R5‑202990 | R5‑202290 | ||
| R5‑202990 | Updates of FR2 MU and TT in TS 38.521-2 | Anritsu, NTT DOCOMO INC. | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202900 | |||
| R5‑202406 | Receiver characteristics testing update to 38.521-2 | Samsung R&D Institute UK | CR | Agreement | Yes |
Yes
| revised | No | R5‑202808 | |||
| R5‑202808 | Receiver characteristics testing update to 38.521-2 | Samsung R&D Institute UK | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202406 | |||
| R5‑202453 | CR to TR 38.521-2 on DUT alignment options | ROHDE & SCHWARZ | CR | Agreement | Yes |
YesKeysight could not agree to limiting the tablet positioning to a single alignment option. We cannot make assumptions on antenna placements for laptops and since the re-positioning concept is an integral aspect of NR FR2 UE RF testing including QoQZ, we cannot agree not to include this concept for laptops.
KEYS, R&S comment to the CR
no agreement, w/draw or not pursued
R&S: preference is not pursued"
| not pursued | No | ||||
| R5‑202504 | CR on EVM Window Centre Timing Definition in FR2 | Skyworks Solutions Inc. | CR | Agreement | Yes |
Yeslate doc
| agreed | No | ||||
| 5.3.2.6 | TS 38.521-3 | |||||||||||
| 5.3.2.6.1 | Tx Requirements (Clause 6) | R5‑201601 | Correction on the channel bandwidth to use in section 6.5B.3.3 | Keysight Technologies UK Ltd | CR | Agreement | Yes |
Yesr2
| revised | No | R5‑202725 | |
| R5‑202725 | Correction on the channel bandwidth to use in section 6.5B.3.3 | Keysight Technologies UK Ltd | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201601 | |||
| R5‑201602 | Setting p-MaxEUTRA to avoid limiting NR power in section 6.5B | Keysight Technologies, OPPO Mobile Telecom | CR | Agreement | Yes |
Yesr2
| revised | No | R5‑202726 | |||
| R5‑202726 | Setting p-MaxEUTRA to avoid limiting NR power in section 6.5B | Keysight Technologies, OPPO Mobile Telecom | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201602 | |||
| R5‑201836 | Correction to TC 6.2B.4.1.3 | Rohde & Schwarz | CR | Agreement | Yes |
Yesr1
remove overlap with R5-201858.
| revised | No | R5‑202727 | |||
| R5‑202727 | Correction to TC 6.2B.4.1.3 | Rohde & Schwarz | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201836 | |||
| R5‑201842 | Skipping 2Rx testing on bands where UE support 4Rx for NSA test cases | Huawei, HiSilicon, Samsung, Bureau Veritas | CR | Agreement | Yes |
YesDish did not agree to this interpretation, 2Rx antenna port testing is required, and furthermore, this is a RAN4 required change.
r2
| revised | No | R5‑202944 | |||
| R5‑202944 | Skipping 2Rx testing on bands where UE support 4Rx for NSA test cases | Huawei, HiSilicon, Samsung, Bureau Veritas | CR | Agreement | Yes |
YesAs per offline discussion on topic of skipping 2Rx testing, it was agreed with an approach of adding a NOTE in every configuration table. This approach is implemented in R5-202941 for TS 38.521-1, but in R5-202944 for TS 38.521-3 there was no time to do it. Will bring a CR for 38.521-3 for next meeting.
| withdrawn | Yes | R5‑201842 | |||
| R5‑201853 | Updating 6.2B.1.1 MOP for intra-band contiguous EN-DC | Huawei, HiSilicon | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202945 | |||
| R5‑202945 | Updating 6.2B.1.1 MOP for intra-band contiguous EN-DC | Huawei, HiSilicon | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201853 | |||
| R5‑201854 | Updating 6.2B.1.2 MOP for intra-band non-contiguous EN-DC | Huawei, HiSilicon | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202946 | |||
| R5‑202946 | Updating 6.2B.1.2 MOP for intra-band non-contiguous EN-DC | Huawei, HiSilicon | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201854 | |||
| R5‑201855 | Update of 6.2B.1.3 MOP for inter-band EN-DC | Huawei, HiSilicon, Samsung | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑201858 | Updating 6.2B.4.x configured output power test cases for FR1 EN-DC | Huawei, HiSilicon, Samsung | CR | Agreement | Yes |
Yes"Title inconsistency
-3G 6.2B.4.missing!
r1
| revised | No | R5‑202728 | |||
| R5‑202728 | Updating 6.2B.4.x configured output power test cases for FR1 EN-DC | Huawei, HiSilicon, Samsung | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201858 | |||
| R5‑201859 | Updating A-SE to align test points with A-MPR | Huawei, HiSilicon | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑201870 | Update of test configuration in 6.5B.3.3.2 for UE co-existence | Huawei,Hisilicon | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑201908 | Addition of 6.2B.1.3A UE Maximum Output Power for inter-band NE-DC | Huawei,Hisilicon | CR | Agreement | Yes |
YesRAN5 plan for Option 4,5 and 7 is still under discussion, and the referenced NE-DC configuration (DC_n1A_28A) have not been assigned to any company.
| withdrawn | Yes | ||||
| R5‑201909 | Addition of 6.2B.4.1.3A Configured Output Power level for inter-band NE-DC | Huawei,Hisilicon | CR | Agreement | Yes |
Yessame as R5-201908
| withdrawn | Yes | ||||
| R5‑201910 | Addition of 6.2B.1.5D UE Maximum Output Power for Inter-Band EN-DC including both FR1 and FR2 for UL-MIMO | Huawei,Hisilicon | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202829 | |||
| R5‑202829 | Addition of 6.2B.1.5D UE Maximum Output Power for Inter-Band EN-DC including both FR1 and FR2 for UL-MIMO | Huawei,Hisilicon | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201910 | |||
| R5‑201911 | Addition of 6.2B.5.1.1 Configured Output Power Level for Inter-band NR-DC between FR1 and FR2 | Huawei,Hisilicon | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202830 | |||
| R5‑202830 | Addition of 6.2B.5.1.1 Configured Output Power Level for Inter-band NR-DC between FR1 and FR2 | Huawei,Hisilicon | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201911 | |||
| R5‑201946 | Updates to 6.2B.2.1, UE Maximum Output Power reduction for Intra-Band Contiguous EN-DC | Ericsson | CR | Agreement | Yes |
Yesr2
| revised | No | R5‑202947 | |||
| R5‑202947 | Updates to 6.2B.2.1, UE Maximum Output Power reduction for Intra-Band Contiguous EN-DC | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201946 | |||
| R5‑201947 | Updates to 6.5B.2.1.1, Spectrum emissions mask for intra-band contiguous EN-DC | Ericsson | CR | Agreement | Yes |
Yesr3
| revised | No | R5‑202948 | |||
| R5‑202948 | Updates to 6.5B.2.1.1, Spectrum emissions mask for intra-band contiguous EN-DC | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201947 | |||
| R5‑201948 | Updates to 6.5B.2.1.3, Adjacent channel leakage ratio for intra-band contiguous EN-DC | Ericsson | CR | Agreement | Yes |
Yesr2
| revised | No | R5‑202949 | |||
| R5‑202949 | Updates to 6.5B.2.1.3, Adjacent channel leakage ratio for intra-band contiguous EN-DC | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201948 | |||
| R5‑202173 | correction 6.3B.1.3 to include anchor agnostic approach applies | T-Mobile USA Inc. | CR | Agreement | Yes |
YesR5
r1
| revised | No | R5‑202729 | |||
| R5‑202729 | correction 6.3B.1.3 to include anchor agnostic approach applies | T-Mobile USA Inc. | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202173 | |||
| R5‑202200 | Clarification of disabling Tx diversity for FR2 UE for NSA FR2 testing | Huawei, HiSilicon | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202730 | |||
| R5‑202730 | Clarification of disabling Tx diversity for FR2 UE for NSA FR2 testing | Huawei, HiSilicon | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202200 | |||
| R5‑202207 | Updation of 6.5B.3.3.1 | Guangdong OPPO Mobile Telecom. | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202731 | |||
| R5‑202731 | Updation of 6.5B.3.3.1 | Guangdong OPPO Mobile Telecom. | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202207 | |||
| R5‑202208 | Updation of 6.5B.3.3.2 | Guangdong OPPO Mobile Telecom. | CR | Agreement | Yes |
Yesmerged into R5-201602.
| withdrawn | Yes | ||||
| R5‑202216 | Updates of Tx test cases for EN-DC including FR2 | NTT DOCOMO INC. | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202959 | |||
| R5‑202959 | Updates of Tx test cases for EN-DC including FR2 | NTT DOCOMO INC. | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202216 | |||
| R5‑202230 | Update to configured output power relaxation due to inter-band EN-DC in 38.521-3 | ZTE Corporation | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202964 | |||
| R5‑202964 | Update to configured output power relaxation due to inter-band EN-DC in 38.521-3 | ZTE Corporation | CR | Agreement | Yes |
YesAgreed after the meeting.
| agreed | No | R5‑202230 | |||
| R5‑202292 | Correction on txDirectCurrentLocation in NSA tests | Anritsu | CR | Agreement | Yes |
Yesfocus on single carrier and inter-band EN-DC(anchor agnostic applies) as a start point
Anritsu feedback :as I focus on single carrier and inter-band EN-DC(anchor agnostic applies) as a start point.
not necessary to have this change can be w/drawn"
| withdrawn | Yes | ||||
| R5‑202294 | Correction to Frequency error for Intra-band contiguous EN-DC | Anritsu | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑202295 | Correction to PRACH configuration for intra-band EN-DC tests | Anritsu | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑202395 | Power control for EN-DC | Samsung R&D Institute UK | CR | Agreement | Yes |
Yesr2
| revised | No | R5‑202901 | |||
| R5‑202901 | Power control for EN-DC | Samsung R&D Institute UK | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202395 | |||
| R5‑202421 | Update Uplink power control window size for NSA TX TCs | QUALCOMM Europe Inc. - Italy | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑202476 | Addition of UL-MIMO EN-DC tests in Clause 6 | Qualcomm Austria RFFE GmbH | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202732 | |||
| R5‑202732 | Addition of UL-MIMO EN-DC tests in Clause 6 | Qualcomm Austria RFFE GmbH | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202476 | |||
| R5‑202478 | Common updates across tests in Clause 6 | Qualcomm Austria RFFE GmbH | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202733 | |||
| R5‑202733 | Common updates across tests in Clause 6 | Qualcomm Austria RFFE GmbH | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202478 | |||
| 5.3.2.6.2 | Rx Requirements (Clause 7) | R5‑201783 | Updated structure for RefSens for EN-DC within FR1 more than 2CCs | Bureau Veritas, Huawei, HiSilicon | CR | Agreement | Yes |
Yesr2
| revised | No | R5‑202902 | |
| R5‑202902 | Updated structure for RefSens for EN-DC within FR1 more than 2CCs | Bureau Veritas, Huawei, HiSilicon | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201783 | |||
| R5‑201860 | Updating REFSENS for 1A_n78A and 3A_n78A | Huawei, HiSilicon | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202903 | |||
| R5‑202903 | Updating REFSENS for 1A_n78A and 3A_n78A | Huawei, HiSilicon | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201860 | |||
| R5‑201912 | Addition of 7.4B.3A Maximum Input Level for inter-band NE-DC | Huawei,Hisilicon | CR | Agreement | Yes |
Yessame as R5-201908
| withdrawn | Yes | ||||
| R5‑202030 | Completion of TC 7.6B.3.3 OOBB Inter-band EN-DC 2CCs within FR1 R15 | CAICT | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202991 | |||
| R5‑202991 | Completion of TC 7.6B.3.3 OOBB Inter-band EN-DC 2CCs within FR1 R15 | CAICT | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202030 | |||
| R5‑202031 | Completion of TC 7.7B.3 Spurious Response Inter-band EN-DC 2CCs within FR1 R15 | CAICT | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202992 | |||
| R5‑202992 | Completion of TC 7.7B.3 Spurious Response Inter-band EN-DC 2CCs within FR1 R15 | CAICT | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202031 | |||
| R5‑202032 | Correction of Initial condition for OOBB intra-band contiguous EN-DC 2 CCs in FR1 in TC 7.6B.3.1 R15 | CAICT | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑202033 | Alignment of requirements in 7.6B and 7.7B with core spec for Intra-band contiguous EN-DC in FR1 R15 | CAICT | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202993 | |||
| R5‑202993 | Alignment of requirements in 7.6B and 7.7B with core spec for Intra-band contiguous EN-DC in FR1 R15 | CAICT | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202033 | |||
| R5‑202112 | Introduction of Rx test cases for EN-DC within FR1 3CCs | NTT DOCOMO INC. | CR | Agreement | Yes |
Yes() in Word name
r1
| revised | No | R5‑202904 | |||
| R5‑202904 | Introduction of Rx test cases for EN-DC within FR1 3CCs | NTT DOCOMO INC. | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202112 | |||
| R5‑202204 | Updating REFSENS for several 3CC configurations | Huawei, HiSilicon | CR | Agreement | Yes |
Yesmerged into R5-202428.
| withdrawn | Yes | ||||
| R5‑202219 | Introduction of Spurious Emissions for inter-band EN-DC including FR2 2CCs | NTT DOCOMO INC. | CR | Agreement | Yes |
Yes()
overlapped with Anritsu's R5-202296.
| withdrawn | Yes | ||||
| R5‑202231 | Update to REFSENS relaxation due to inter-band EN-DC in 38.521-3 | ZTE Corporation | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202965 | |||
| R5‑202965 | Update to REFSENS relaxation due to inter-band EN-DC in 38.521-3 | ZTE Corporation | CR | Agreement | Yes |
Yesagreed after the meeting.
| agreed | No | R5‑202231 | |||
| R5‑202293 | Correction to 7.3B.2.3 test configuration for EN-DC 26_n79 | Anritsu | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑202296 | Update to NSA FR2 Receiver Spurious Emission Test Case | Anritsu, NTT DOCOMO INC. | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202905 | |||
| R5‑202905 | Update to NSA FR2 Receiver Spurious Emission Test Case | Anritsu, NTT DOCOMO INC. | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202296 | |||
| R5‑202428 | Add 7.3B.2.3_1.2 Reference sensitivity for EN-DC within FR1v - 4 CCs | QUALCOMM Europe Inc. - Italy | CR | Agreement | Yes |
Yes()
r2
| revised | No | R5‑202906 | |||
| R5‑202906 | Add 7.3B.2.3_1.2 Reference sensitivity for EN-DC within FR1v - 4 CCs | QUALCOMM Europe Inc. - Italy | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202428 | |||
| R5‑202429 | Update for 7.3A.3 for CA without EN-DC | QUALCOMM Europe Inc. - Italy | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑202477 | Addition of UL-MIMO EN-DC tests in Clause 7 | Qualcomm Austria RFFE GmbH | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202734 | |||
| R5‑202734 | Addition of UL-MIMO EN-DC tests in Clause 7 | Qualcomm Austria RFFE GmbH | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202477 | |||
| R5‑202479 | Common updates across tests in Clause 7 | Qualcomm Austria RFFE GmbH | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202735 | |||
| R5‑202735 | Common updates across tests in Clause 7 | Qualcomm Austria RFFE GmbH | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202479 | |||
| 5.3.2.6.3 | Clauses 1-5 / Annexes | R5‑201454 | Updates of MU and TT in TS 38.521-3 | NTT DOCOMO INC. | CR | Agreement | Yes |
Yesmerged into R5-202291
| withdrawn | Yes | ||
| R5‑201600 | LTE Channel BW clarification in case of LTE CA in EN-DC FR2 test cases | Keysight Technologies UK Ltd | CR | Agreement | Yes |
Yesis not needed.
(no more than 1 EUTRA CC will be needed)
| withdrawn | Yes | ||||
| R5‑201721 | Update Annex F.4 Uplink Power window explanation | ANRITSU LTD | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑201787 | Updated to EN-DC Rel-16 band information in clause 5 | Bureau Veritas | CR | Agreement | No |
Yes
| withdrawn | Yes | ||||
| R5‑202291 | Updates of FR2 MU and TT in TS 38.521-3 | Anritsu, NTT DOCOMO INC. | CR | Agreement | Yes |
Yescl. aff.
r2
| revised | No | R5‑202907 | |||
| R5‑202907 | Updates of FR2 MU and TT in TS 38.521-3 | Anritsu, NTT DOCOMO INC. | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202291 | |||
| R5‑202393 | Addition of Intra-band non-contiguous EN-DC combination | Samsung R&D Institute UK | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑202407 | Receiver characteristics testing update to 38.521-3 | Samsung R&D Institute UK | CR | Agreement | Yes |
Yes
| revised | No | R5‑202809 | |||
| R5‑202809 | Receiver characteristics testing update to 38.521-3 | Samsung R&D Institute UK | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202407 | |||
| R5‑202475 | TS 38.521-3 Section 1-5 and Annex updates to align with core specification | Qualcomm Austria RFFE GmbH | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| 5.3.2.7 | TS 38.521-4 | |||||||||||
| 5.3.2.7.1 | Conducted Demod Performance and CSI Reporting Requirements (Clauses 5&6) | R5‑201816 | Correction to TC 5.2.3.1.1_4 4Rx FDD FR1 PDSCH mapping Type A performance | LG Electronics | CR | Agreement | Yes |
Yes
| agreed | No | ||
| R5‑202240 | Configuration of p-ZP-CSI-RS-ResourceSet for PDSCH Demod test cases | Qualcomm Wireless GmbH | CR | Agreement | No |
Yeslate doc
changes are captured in doc 2255
| withdrawn | Yes | ||||
| R5‑202242 | Clarification of propagation condition for Demod test cases during call setup | Qualcomm Wireless GmbH | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑202248 | Message exception correction for Demod test cases | Qualcomm Wireless GmbH | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202736 | |||
| R5‑202736 | Message exception correction for Demod test cases | Qualcomm Wireless GmbH | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202248 | |||
| R5‑202297 | Correction to 4Rx FDD FR1 periodic CQI reporting under AWGN conditions for both SA and NSA | Anritsu | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑202298 | Correction to 4Rx TDD FR1 RI reporting | Anritsu | CR | Agreement | Yes |
Yesr2
| revised | No | R5‑202831 | |||
| R5‑202831 | Correction to 4Rx TDD FR1 RI reporting | Anritsu | CR | Agreement | Yes |
Yesagreed, but uploaded with wrong contents, so revised again.
| revised | No | R5‑202979 | R5‑202298 | ||
| R5‑202979 | Correction to 4Rx TDD FR1 RI reporting | Anritsu | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202831 | |||
| R5‑202300 | Correction to CSI reporting test cases missing MIMO correlation matrixes | Anritsu | CR | Agreement | Yes |
Yesr2
R4-2006541 was revised to R4-2008752 and agreed.
| revised | No | R5‑202980 | |||
| R5‑202980 | Correction to CSI reporting test cases missing MIMO correlation matrixes | Anritsu | CR | Agreement | Yes |
YesAgreed after the meeting.
| agreed | No | R5‑202300 | |||
| R5‑202301 | Correction to FR1 aperiodic subband CQI reporting under fading conditions | Anritsu | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202737 | |||
| R5‑202737 | Correction to FR1 aperiodic subband CQI reporting under fading conditions | Anritsu | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202301 | |||
| R5‑202302 | Correction to FR1 Single PMI with 8Tx TypeI - SinglePanel codebook for both SA and NSA | Anritsu | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202738 | |||
| R5‑202738 | Correction to FR1 Single PMI with 8Tx TypeI - SinglePanel codebook for both SA and NSA | Anritsu | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202302 | |||
| R5‑202305 | Correction to frequencyDomainAllocation for PDSCH demod test cases | Anritsu | CR | Agreement | Yes |
Yescovered by R5-202248r1 (Qualcomm).
| withdrawn | Yes | ||||
| R5‑202306 | Correction to message exception and test description in RI tests | Anritsu | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202739 | |||
| R5‑202739 | Correction to message exception and test description in RI tests | Anritsu | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202306 | |||
| R5‑202307 | Editorial correction on the table numbers for Minimum Test Time | Anritsu | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑202308 | Editorial correction to 4x4 MIMO PDSCH demodulation tests | Anritsu | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑202448 | Addition of message exceptions for PDSCH test cases | ROHDE & SCHWARZ | CR | Agreement | Yes |
Yesr3
| revised | No | R5‑202832 | |||
| R5‑202832 | Addition of message exceptions for PDSCH test cases | ROHDE & SCHWARZ | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202448 | |||
| 5.3.2.7.2 | Radiated Demod Performance and CSI Reporting Requirements (Clauses 7&8) | R5‑201949 | Updates to 8.2.2.2.2.1, 2Rx TDD FR2 aperiodic CQI reporting under fading performance for both SA and NSA | Ericsson | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202989 | |
| R5‑202989 | Updates to 8.2.2.2.2.1, 2Rx TDD FR2 aperiodic CQI reporting under fading performance for both SA and NSA | Ericsson | CR | Agreement | Yes |
YesAgreed after the meeting.
| agreed | No | R5‑201949 | |||
| R5‑202201 | Clarification of disabling Tx diversity for FR2 UE for FR2 Demod testing | Huawei, HiSilicon | CR | Agreement | Yes |
Yesr2
| revised | No | R5‑202908 | |||
| R5‑202908 | Clarification of disabling Tx diversity for FR2 UE for FR2 Demod testing | Huawei, HiSilicon | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202201 | |||
| R5‑202247 | Update to FR2 PDSCH Demod test case | Qualcomm Wireless GmbH, Anritsu | CR | Agreement | Yes |
Yesr2
| revised | No | R5‑202740 | |||
| R5‑202740 | Update to FR2 PDSCH Demod test case | Qualcomm Wireless GmbH, Anritsu | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202247 | |||
| R5‑202299 | Correction to 7.2.2.2.1_1 FR2 PDSCH demodulation test | Anritsu | CR | Agreement | Yes |
Yescovered by R5-202247.
| withdrawn | Yes | ||||
| R5‑202303 | Correction to FR2 CQI reporting tests | Anritsu | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202981 | |||
| R5‑202981 | Correction to FR2 CQI reporting tests | Anritsu | CR | Agreement | Yes |
YesAgreed after the meeting.
| agreed | No | R5‑202303 | |||
| R5‑202304 | Correction to FR2 PDCCH demodulation tests | Anritsu | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑202310 | Introduction of 8.4.2.2.1 2Rx TDD FR2 RI reporting for both SA and NSA | Anritsu | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202741 | |||
| R5‑202741 | Introduction of 8.4.2.2.1 2Rx TDD FR2 RI reporting for both SA and NSA | Anritsu | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202310 | |||
| 5.3.2.7.3 | Interworking Demod Performance and CSI Reporting Requirements (Clauses 9&10) | |||||||||||
| 5.3.2.7.4 | Clauses 1-4 / Annexes | R5‑201945 | Updated to Annex A and B for performance tests | Bureau Veritas | CR | Agreement | Yes |
Yes
| agreed | No | ||
| R5‑202309 | Editorial correction to Annex C.2 | Anritsu | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202742 | |||
| R5‑202742 | Editorial correction to Annex C.2 | Anritsu | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202309 | |||
| R5‑202311 | Updates of FR2 MU and TT in TS 38.521-4 | Anritsu | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202766 | |||
| R5‑202766 | Updates of FR2 MU and TT in TS 38.521-4 | Anritsu | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202311 | |||
| R5‑202412 | Update Wireless isolation procedure | Keysight Technologies UK Ltd | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202743 | |||
| R5‑202743 | Update Wireless isolation procedure | Keysight Technologies UK Ltd | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202412 | |||
| 5.3.2.8 | TS 38.522 | R5‑201755 | Correction to applicability of RF EN-DC FR1 and FR2 TCs | Tejet | CR | Agreement | Yes |
Yesmerged into R5-201786.
| withdrawn | Yes | ||
| R5‑201786 | TP updated to applicability table | Bureau Veritas, Samsung, TTA, Huawei, HiSilicon, Ericsson, Sporton, CMCC, Rohde & Schwarz, Guangdong OPPO Mobile Telecom, Tejet, CAICT, Qualcomm, Anritsu | CR | Agreement | Yes |
Yesr1
merged content from R5-201755, R5-202260, R5-201830.
r3
| revised | No | R5‑202960 | |||
| R5‑202960 | TP updated to applicability table | Bureau Veritas, Samsung, TTA, Huawei, HiSilicon, Ericsson, Sporton, CMCC, Rohde & Schwarz, Guangdong OPPO Mobile Telecom, Tejet, CAICT, Qualcomm, Anritsu | CR | Agreement | Yes |
Yesremove Additional information to FR1 TC6.2.1/6.2.2 for UL MIMO support since test case CR is not agreed yet
Add an editor’s note for future handling of ‘tested bands’ column and ‘branch’ column.
Understanding is handling of “Branch“ mentioned in proposals1/2 in R5-202919 is not endorsed and will be revisited in future meeting."
First agreed, then revised further.
| revised | No | R5‑203114 | R5‑201786 | ||
| R5‑203114 | TP updated to applicability table | Bureau Veritas, Samsung, TTA, Huawei, HiSilicon, Ericsson, Sporton, CMCC, Rohde & Schwarz, Guangdong OPPO Mobile Telecom, Tejet, CAICT, Qualcomm, Anritsu | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202960 | |||
| R5‑201823 | Correction of SS-SINR applicability | ROHDE & SCHWARZ | CR | Agreement | No |
Yes
| withdrawn | Yes | ||||
| R5‑201830 | Correction of SS-SINR applicability | ROHDE & SCHWARZ | CR | Agreement | Yes |
Yes"Correction NR completed test case
overlap with 201786 addressed by w/drawing 201786
pending overlap with R5-202262 (Anritsu)
BV: offline discussion, intention to have the 1830 agreed in principle and then merge TS38.522 combo CR 1786
R&S: withdrawn and content merged into 1786"
| withdrawn | Yes | ||||
| R5‑201843 | Skipping 2Rx testing on bands where UE support 4Rx | Huawei, HiSilicon, Samsung | CR | Agreement | Yes |
YesDish did not agree to this interpretation, 2Rx antenna port testing is required, and furthermore, this is a RAN4 required change.
r1
| revised | No | R5‑202810 | |||
| R5‑202810 | Skipping 2Rx testing on bands where UE support 4Rx | Huawei, HiSilicon, Samsung | CR | Agreement | Yes |
Yes
| withdrawn | Yes | R5‑201843 | |||
| R5‑202260 | Update of table 4.1.3-1 | Guangdong OPPO Mobile Telecom. | CR | Agreement | Yes |
Yesmerged into R5-201786.
| withdrawn | Yes | ||||
| R5‑202262 | Correction to test case applicability regarding txDirectCurrentLocation | Anritsu | CR | Agreement | Yes |
Yes"Associated discussion R5-202417
Author confirmed no overlap
Depends on the outcome of discussion 2417 during the meeting, may not needed
RAN5 RF decided to use option2 prop1 of 2417 hence this can be w/drawn"
| withdrawn | Yes | ||||
| 5.3.2.9 | TS 38.533 | R5‑202142 | Correction to Test Applicability for 4.6.1.3 EN-DC FR1 event-triggered reporting with gap in non-DRX | Qualcomm Finland RFFE Oy | CR | Agreement | Yes |
Yes
| revised | No | R5‑202812 | |
| R5‑202812 | Correction to Test Applicability for 4.6.1.3 EN-DC FR1 event-triggered reporting with gap in non-DRX | Qualcomm Finland RFFE Oy | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202142 | |||
| R5‑202143 | Correction to Test Applicability for 4.6.1.4 EN-DC FR1 event-triggered reporting with gap in DRX | Qualcomm Finland RFFE Oy | CR | Agreement | Yes |
Yes
| available | No | R5‑202813 | |||
| R5‑202813 | Correction to Test Applicability for 4.6.1.4 EN-DC FR1 event-triggered reporting with gap in DRX | Qualcomm Finland RFFE Oy | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202143 | |||
| R5‑202144 | Correction to Test Applicability & Message Exception for 4.6.1.6 EN-DC FR1 event-triggered reporting with gap in non-DRX with SSB time index detection | Qualcomm Finland RFFE Oy | CR | Agreement | Yes |
Yes
| revised | No | R5‑202814 | |||
| R5‑202814 | Correction to Test Applicability & Message Exception for 4.6.1.6 EN-DC FR1 event-triggered reporting with gap in non-DRX with SSB time index detection | Qualcomm Finland RFFE Oy | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202144 | |||
| R5‑202145 | Correction to Test Applicability for 6.6.1.3 NR SA FR1 event-triggered reporting with gap in non-DRX | Qualcomm Finland RFFE Oy | CR | Agreement | Yes |
Yes
| revised | No | R5‑202815 | |||
| R5‑202815 | Correction to Test Applicability for 6.6.1.3 NR SA FR1 event-triggered reporting with gap in non-DRX | Qualcomm Finland RFFE Oy | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202145 | |||
| R5‑202146 | Correction to Test Applicability for 6.6.1.4 NR SA FR1 event-triggered reporting with gap in DRX | Qualcomm Finland RFFE Oy | CR | Agreement | Yes |
Yes
| revised | No | R5‑202816 | |||
| R5‑202816 | Correction to Test Applicability for 6.6.1.4 NR SA FR1 event-triggered reporting with gap in DRX | Qualcomm Finland RFFE Oy | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202146 | |||
| R5‑202147 | Correction to Test Applicability and Message Exception for 6.6.1.6 NR SA FR1 event-triggered reporting with gap in non-DRX with SSB index reading | Qualcomm Finland RFFE Oy | CR | Agreement | Yes |
Yesmeetg date
| revised | No | R5‑202961 | |||
| R5‑202961 | Correction to Test Applicability and Message Exception for 6.6.1.6 NR SA FR1 event-triggered reporting with gap in non-DRX with SSB index reading | Qualcomm Finland RFFE Oy | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202147 | |||
| R5‑202148 | Correction to Message Exception for 4.6.1.5 EN-DC FR1 event-triggered reporting without gap in non-DRX with SSB time index detection | Qualcomm Finland RFFE Oy | CR | Agreement | No |
Yeslate doc
| withdrawn | Yes | ||||
| R5‑202149 | Correction to Message Exception for 6.6.1.6 NR SA FR1 event-triggered reporting with gap in non-DRX with SSB time index detection | Qualcomm Finland RFFE Oy | CR | Agreement | Yes |
Yes"Corrections to already completed / validated RRM test cases
Author requested to withdraw due to overlap"
| withdrawn | Yes | ||||
| R5‑202150 | Correction to Message Exception for 4.6.2.5 EN-DC FR1-FR1 event-triggered reporting in non-DRX with SSB time index detection | Qualcomm Finland RFFE Oy | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202950 | |||
| R5‑202950 | Correction to Message Exception for 4.6.2.5 EN-DC FR1-FR1 event-triggered reporting in non-DRX with SSB time index detection | Qualcomm Finland RFFE Oy | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202150 | |||
| R5‑202151 | Correction to Message Exception for 4.6.2.6 EN-DC FR1-FR1 event-triggered reporting in DRX with SSB time index detection | Qualcomm Finland RFFE Oy | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202951 | |||
| R5‑202951 | Correction to Message Exception for 4.6.2.6 EN-DC FR1-FR1 event-triggered reporting in DRX with SSB time index detection | Qualcomm Finland RFFE Oy | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202151 | |||
| R5‑202152 | Correction to Message Exception for 6.6.2.5 NR SA FR1-FR1 event-triggered reporting in non-DRX with SSB time index detection | Qualcomm Finland RFFE Oy | CR | Agreement | Yes |
YesQC: No overlap, but might need to WITHDRAW R5-202152, as per some discussion ongoing"
| withdrawn | Yes | ||||
| R5‑202153 | Correction to Message Exception for 6.6.2.6 NR SA FR1-FR1 event-triggered reporting in DRX with SSB time index detection | Qualcomm Finland RFFE Oy | CR | Agreement | Yes |
Yes"Corrections to already completed / validated RRM test cases
Author requested to withdraw"
| withdrawn | Yes | ||||
| R5‑202154 | Correction to Test Requirements in 4.4.1.1, Table 4.4.1.1.5-5 to include TT values from Annex F | Qualcomm Finland RFFE Oy | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202909 | |||
| R5‑202909 | Correction to Test Requirements in 4.4.1.1, Table 4.4.1.1.5-5 to include TT values from Annex F | Qualcomm Finland RFFE Oy | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202154 | |||
| R5‑202155 | Correction to Test Requirements in 6.4.1.1, Table 6.4.1.1.5-5 to include TT values from Annex F | Qualcomm Finland RFFE Oy | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202910 | |||
| R5‑202910 | Correction to Test Requirements in 6.4.1.1, Table 6.4.1.1.5-5 to include TT values from Annex F | Qualcomm Finland RFFE Oy | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202155 | |||
| R5‑202156 | Correction to SMTC pattern and Message Exception in 4.7.1.2.1 | Qualcomm Finland RFFE Oy | CR | Agreement | Yes |
Yesr2
"Revised from: R5-202156r1.
r2: Corrected the typo in RAN4 CR number from R4-2001679 to R4-2006179, also corrected the meeting end date to May29th.
offline discussion, may withdrawn and merged content into 1825r2
Revised to: R5-202873.
"
| revised | No | R5‑202873 | |||
| R5‑202873 | Correction to SMTC pattern and Message Exception in 4.7.1.2.1 | Qualcomm Finland RFFE Oy | CR | Agreement | No |
Yes
| withdrawn | Yes | R5‑202156 | |||
| R5‑202157 | Correction to SMTC pattern and Message Exception in 4.7.1.2.2 | Qualcomm Finland RFFE Oy | CR | Agreement | No |
Yeslate doc
| withdrawn | Yes | ||||
| R5‑202158 | Correction to SMTC pattern and Message Exception in 4.7.2.2.1 | Qualcomm Finland RFFE Oy | CR | Agreement | Yes |
Yes"CR # inconsistency
-3GU: 0701 / CR coversheet: 701"
r2
"Revised from: R5-202158r1.
r2: Corrected CR number on cover page (701) to match with 3GU (0701), and also correctde the RAN4 CR typo, corrected it from R4-2001679 to R4-2006179. Also corrected the end date of meeting on cover page.
Check for overlap
offline discussion, may withdrawn and merged content into 1827r2
Revised to: R5-202874.
"
| revised | No | R5‑202874 | |||
| R5‑202874 | Correction to SMTC pattern and Message Exception in 4.7.2.2.1 | Qualcomm Finland RFFE Oy | CR | Agreement | No |
Yes
| withdrawn | Yes | R5‑202158 | |||
| R5‑202159 | Correction to SMTC pattern and Message Exception in 4.7.2.2.2 | Qualcomm Finland RFFE Oy | CR | Agreement | No |
Yeslate doc
| withdrawn | Yes | ||||
| R5‑202418 | Update 6.5.1.1 and CSI-ReportConfig in Annex H | Keysight Technologies UK Ltd | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑202437 | Correction to Test Requirement for 4.4.3.1 by updating TT values from Annex F | Qualcomm Finland RFFE Oy | CR | Agreement | Yes |
Yes
| revised | No | R5‑202817 | |||
| R5‑202817 | Correction to Test Requirement for 4.4.3.1 by updating TT values from Annex F | Qualcomm Finland RFFE Oy | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202437 | |||
| R5‑202438 | Correction to Test Requirement for 4.4.3.1 by updating TT values from Annex F. | Qualcomm Finland RFFE Oy | CR | Agreement | No |
Yes
| withdrawn | Yes | ||||
| R5‑202439 | Correction to Test Requirement for 6.4.3.1 by updating TT values from Annex F | Qualcomm Finland RFFE Oy | CR | Agreement | Yes |
Yeswrong meeting date.
r1
| revised | No | R5‑202911 | |||
| R5‑202911 | Correction to Test Requirement for 6.4.3.1 by updating TT values from Annex F | Qualcomm Finland RFFE Oy | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202439 | |||
| R5‑202440 | Annex I RRM OTA procedures update to add RSRPB based UE Positioning Method for FR2 | Qualcomm Finland RFFE Oy | CR | Agreement | Yes |
YesTdoc #
r1
| revised | No | R5‑202912 | |||
| R5‑202912 | Annex I RRM OTA procedures update to add RSRPB based UE Positioning Method for FR2 | Qualcomm Finland RFFE Oy | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202440 | |||
| 5.3.2.9.1 | EN-DC with all NR cells in FR1 (Clause 4) | R5‑201666 | Update FR1 Test Tolerance of 4.5.2.5 E-UTRAN SCC in sync | Huawei, HiSilicon | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202996 | |
| R5‑202996 | Update FR1 Test Tolerance of 4.5.2.5 E-UTRAN SCC in sync | Huawei, HiSilicon | CR | Agreement | Yes |
YesAgreed after the meeting.
| agreed | No | R5‑201666 | |||
| R5‑201667 | Update FR1 Test Tolerance of 4.5.2.6 E-UTRAN SCC in async | Huawei, HiSilicon | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202997 | |||
| R5‑202997 | Update FR1 Test Tolerance of 4.5.2.6 E-UTRAN SCC in async | Huawei, HiSilicon | CR | Agreement | Yes |
YesAgreed after the meeting.
| agreed | No | R5‑201667 | |||
| R5‑201668 | Update FR1 Test Tolerance of 4.5.3.1 SCell activation 160ms | Huawei, HiSilicon | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202998 | |||
| R5‑202998 | Update FR1 Test Tolerance of 4.5.3.1 SCell activation 160ms | Huawei, HiSilicon | CR | Agreement | Yes |
YesAgreed after the meeting.
| agreed | No | R5‑201668 | |||
| R5‑201669 | Update FR1 Test Tolerance of 4.5.3.2 SCell activation 320ms | Huawei, HiSilicon | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202999 | |||
| R5‑202999 | Update FR1 Test Tolerance of 4.5.3.2 SCell activation 320ms | Huawei, HiSilicon | CR | Agreement | Yes |
YesAgreed after the meeting.
| agreed | No | R5‑201669 | |||
| R5‑201670 | Update FR1 Test Tolerance of 4.5.3.3 unknown SCell activation | Huawei, HiSilicon | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑203000 | |||
| R5‑203000 | Update FR1 Test Tolerance of 4.5.3.3 unknown SCell activation | Huawei, HiSilicon | CR | Agreement | Yes |
YesAgreed after the meeting.
| agreed | No | R5‑201670 | |||
| R5‑201678 | Correction to TC 4.7.2.2.1 for some typos | Huawei, HiSilicon | CR | Agreement | Yes |
Yesoverlapped with R&S R5-201827, R5-201616.
| withdrawn | Yes | ||||
| R5‑201685 | Update of 4.5.3.0 minimum requirements for Scell activation | Huawei, HiSilicon | CR | Agreement | Yes |
Yesr2
| revised | No | R5‑203091 | |||
| R5‑203091 | Update of 4.5.3.0 minimum requirements for Scell activation | Huawei, HiSilicon | CR | Agreement | Yes |
YesAgreed after the meeting.
| agreed | No | R5‑201685 | |||
| R5‑201821 | Correction of SS-SINR applicability -NSA | ROHDE & SCHWARZ | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑201824 | Corrections to 4.7.1.1 | ROHDE & SCHWARZ | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑201825 | Corrections to 4.7.1.2 | ROHDE & SCHWARZ | CR | Agreement | Yes |
Yesr2
| revised | No | R5‑202977 | |||
| R5‑202977 | Corrections to 4.7.1.2 | Rohde & Schwarz, Qualcomm Finland RFFE Oy | CR | Agreement | Yes |
Yesagreed after the meeting
| agreed | No | R5‑201825 | |||
| R5‑201826 | Corrections to 4.7.2.1 | ROHDE & SCHWARZ | CR | Agreement | Yes |
Yesr2
| revised | No | R5‑202969 | |||
| R5‑202969 | Corrections to 4.7.2.1 | ROHDE & SCHWARZ | CR | Agreement | Yes |
Yesagreed after the meeting
| agreed | No | R5‑201826 | |||
| R5‑201827 | Corrections to 4.7.2.2 | ROHDE & SCHWARZ | CR | Agreement | Yes |
Yesr2
| revised | No | R5‑202978 | |||
| R5‑202978 | Corrections to 4.7.2.2 | Rohde & Schwarz, Qualcomm Finland RFFE Oy | CR | Agreement | Yes |
Yesagreed after the meeting
| agreed | No | R5‑201827 | |||
| R5‑201828 | Corrections to 4.7.3.1 | ROHDE & SCHWARZ | CR | Agreement | Yes |
Yesr2
| revised | No | R5‑202970 | |||
| R5‑202970 | Corrections to 4.7.3.1 | ROHDE & SCHWARZ | CR | Agreement | Yes |
Yesagreed after the meeting
| agreed | No | R5‑201828 | |||
| R5‑201829 | Corrections to 4.7.3.2 | ROHDE & SCHWARZ | CR | Agreement | Yes |
Yesr2
| revised | No | R5‑202971 | |||
| R5‑202971 | Corrections to 4.7.3.2 | ROHDE & SCHWARZ | CR | Agreement | Yes |
Yesagreed after the meeting
| agreed | No | R5‑201829 | |||
| R5‑202263 | Core alignment in 4.6.1.5 and 4.6.1.6 Event Triggered Reporting with SSB time index detection | Anritsu | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑202265 | Correction on EN-DC FR1 radio link monitoring out-of-sync test | Anritsu | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑202267 | Correction to EN-DC FR1 radio link monitoring tests | Anritsu | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202744 | |||
| R5‑202744 | Correction to EN-DC FR1 radio link monitoring tests | Anritsu | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202267 | |||
| R5‑202269 | Correction to FR1 UE transmit timing accuracy | Anritsu | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202982 | |||
| R5‑202982 | Correction to FR1 UE transmit timing accuracy | Anritsu | CR | Agreement | Yes |
YesAgreed after the meeting.
| agreed | No | R5‑202269 | |||
| R5‑202271 | Correction to Message Exception for FR1 Event Triggered Reporting tests | Anritsu | CR | Agreement | Yes |
Yeschange is not needed.
| withdrawn | Yes | ||||
| R5‑202390 | Addition of new RRM Test Case 4.5.4.1 | Samsung R&D Institute UK | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202700 | |||
| R5‑202700 | Addition of new RRM Test Case 4.5.4.1 | Samsung R&D Institute UK | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202390 | |||
| R5‑202413 | Update 4.5.1.3 and 4.5.1.4 test procedure | Keysight Technologies UK Ltd | CR | Agreement | Yes |
Yesincluded in R5-202267 (Anritsu).
| withdrawn | Yes | ||||
| R5‑202414 | Clarification cell2 SS-RSRP in 4.7.1.2.1 | Keysight Technologies UK Ltd | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202745 | |||
| R5‑202745 | Clarification cell2 SS-RSRP in 4.7.1.2.1 | Keysight Technologies UK Ltd | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202414 | |||
| R5‑202495 | Correction of RRM Test Case 4.6.2.1 | MediaTek Inc. | CR | Agreement | Yes |
YesHuawei CR R5-201676 also fixed the issue
| withdrawn | Yes | ||||
| R5‑202499 | Correction of RRM Test Case 4.6.2.2 | MediaTek Inc. | CR | Agreement | Yes |
YesHuawei CR R5-201676 also fixed the issue
| withdrawn | Yes | ||||
| 5.3.2.9.2 | EN-DC with at least 1 NR Cell in FR2 (Clause5) | R5‑201392 | Addition of minimum conformance requirements 5.7.1.0 - EN-DC FR2 SS-RSRP accuracy | Huawei, HiSilicon | CR | Agreement | Yes |
Yesoverlapped with R&S R5-202063.
| withdrawn | Yes | ||
| R5‑201405 | Addition to minimum coformance requirement 5.5.5.0.3 - scheduling restriction for BFD and CBD | Huawei, HiSilicon | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑201406 | Addition to NR test case 5.5.5.5 scheduling avaliable restriction | Huawei, HiSilicon | CR | Agreement | Yes |
YesTdoc #
r1
| revised | No | R5‑202746 | |||
| R5‑202746 | Addition to NR test case 5.5.5.5 scheduling avaliable restriction | Huawei, HiSilicon | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201406 | |||
| R5‑201407 | Addition to minimum coformance requirement 5.5.8.0 - TCI-state switch | Huawei, HiSilicon | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑201408 | Addition to NR test case 5.5.8.1 MAC-CE based TCI switch | Huawei, HiSilicon | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑201409 | Addition to NR test case 5.5.8.2 RRC based TCI switch | Huawei, HiSilicon | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑201679 | Update of TC 5.6.1.1 event-triggered without gap non-DRX | Huawei, HiSilicon | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑201680 | Update of TC 5.6.1.2 event-triggered without gap DRX | Huawei, HiSilicon | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑201681 | Update of TC 5.6.1.3 event-triggered with gap non-DRX | Huawei, HiSilicon | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑201682 | Update of TC 5.6.1.4 event-triggered with gap DRX | Huawei, HiSilicon | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑202063 | Minimum requirements SS-RSRP NSA FR2 | ROHDE & SCHWARZ | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑202064 | Addition 5.7.1.1 | ROHDE & SCHWARZ | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑202065 | Addition 5.7.1.2 | ROHDE & SCHWARZ | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑202066 | Addition 5.7.1.3 | ROHDE & SCHWARZ | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑202067 | Minimum requirements SS-RSRQ NSA FR2 | ROHDE & SCHWARZ | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑202068 | Addition 5.7.2.1 | ROHDE & SCHWARZ | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑202069 | Addition 5.7.2.2 | ROHDE & SCHWARZ | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑202070 | Minimum requirements SS-SINR NSA FR2 | ROHDE & SCHWARZ | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑202071 | Addition 5.7.3.1 | ROHDE & SCHWARZ | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑202072 | Addition 5.7.3.2 | ROHDE & SCHWARZ | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑202095 | Correction of AoA configuration for FR2 SA Inter-freq measurement test cases in clause 5.6.2 | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑202268 | Correction to EN-DC FR2 RRC-based DL active BWP switch in non-DRX in synchronous ENDC | Anritsu | CR | Agreement | Yes |
Yesr2
R4-2006079 was withdrawn for further discussion for next RAN4 meeting.
| revised | No | R5‑202983 | |||
| R5‑202983 | Correction to EN-DC FR2 RRC-based DL active BWP switch in non-DRX in synchronous ENDC | Anritsu | CR | Agreement | Yes |
YesAgreed after the meeting.
| agreed | No | R5‑202268 | |||
| R5‑202270 | Correction to FR2 UE transmit timing accuracy | Anritsu | CR | Agreement | Yes |
Yesr2
| revised | No | R5‑202984 | |||
| R5‑202984 | Correction to FR2 UE transmit timing accuracy | Anritsu | CR | Agreement | Yes |
YesAgreed after the meeting.
| agreed | No | R5‑202270 | |||
| R5‑202277 | Editorial Correction to FR2 Interruption test cases | Anritsu | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑202415 | Alignment 5.4.1.1 test procedure with 4.4.1.1 | Keysight Technologies UK Ltd | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| 5.3.2.9.3 | NR Standalone in FR1 (Clause 6) | R5‑201410 | Addition to NR test case 6.3.2.1.3 FR1-FR1 RRC re-establishment without serving cell timing | Huawei, HiSilicon | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202833 | |
| R5‑202833 | Addition to NR test case 6.3.2.1.3 FR1-FR1 RRC re-establishment without serving cell timing | Huawei, HiSilicon | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201410 | |||
| R5‑201614 | Corrections to 6.7.1.2 and core spec alignment | ROHDE & SCHWARZ | CR | Agreement | Yes |
Yesr2
| revised | No | R5‑202972 | |||
| R5‑202972 | Corrections to 6.7.1.2 and core spec alignment | ROHDE & SCHWARZ | CR | Agreement | Yes |
Yesagreed after the meeting
| agreed | No | R5‑201614 | |||
| R5‑201615 | Corrections to 6.7.2.1 and core spec alignment | ROHDE & SCHWARZ | CR | Agreement | Yes |
Yesr2
| revised | No | R5‑202973 | |||
| R5‑202973 | Corrections to 6.7.2.1 and core spec alignment | ROHDE & SCHWARZ | CR | Agreement | Yes |
Yesagreed after the meeting
| agreed | No | R5‑201615 | |||
| R5‑201616 | Corrections to 6.7.2.2 and core spec alignment | ROHDE & SCHWARZ | CR | Agreement | Yes |
Yesr2
| revised | No | R5‑202974 | |||
| R5‑202974 | Corrections to 6.7.2.2 and core spec alignment | ROHDE & SCHWARZ | CR | Agreement | Yes |
Yesagreed after the meeting
| agreed | No | R5‑201616 | |||
| R5‑201617 | Corrections to 6.7.3.1 and core spec alignment | ROHDE & SCHWARZ | CR | Agreement | Yes |
Yesr2
| revised | No | R5‑202975 | |||
| R5‑202975 | Corrections to 6.7.3.1 and core spec alignment | ROHDE & SCHWARZ | CR | Agreement | Yes |
Yesagreed after the meeting
| agreed | No | R5‑201617 | |||
| R5‑201618 | Corrections to 6.7.3.2 and core spec alignment | ROHDE & SCHWARZ | CR | Agreement | Yes |
Yesr2
| revised | No | R5‑202976 | |||
| R5‑202976 | Corrections to 6.7.3.2 and core spec alignment | ROHDE & SCHWARZ | CR | Agreement | Yes |
Yesagreed after the meeting
| agreed | No | R5‑201618 | |||
| R5‑201619 | Corrections to 6.7.1.1 | ROHDE & SCHWARZ | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑201671 | Addition FR1 Test Tolerance of 6.5.5.1 SSB BFD non-DRX | Huawei, HiSilicon | CR | Agreement | Yes |
Yesr2
| revised | No | R5‑203095 | |||
| R5‑203095 | Addition FR1 Test Tolerance of 6.5.5.1 SSB BFD non-DRX | Huawei, HiSilicon | CR | Agreement | Yes |
YesAgreed after the meeting.
| agreed | No | R5‑201671 | |||
| R5‑201672 | Addition FR1 Test Tolerance of 6.5.5.2 SSB BFD DRX | Huawei, HiSilicon | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑203096 | |||
| R5‑203096 | Addition FR1 Test Tolerance of 6.5.5.2 SSB BFD DRX | Huawei, HiSilicon | CR | Agreement | Yes |
YesAgreed after the meeting.
| agreed | No | R5‑201672 | |||
| R5‑201673 | Update FR1 Test Tolerance of 6.5.5.3 CSI-RS BFD non-DRX | Huawei, HiSilicon | CR | Agreement | Yes |
Yesr2
| revised | No | R5‑203097 | |||
| R5‑203097 | Update FR1 Test Tolerance of 6.5.5.3 CSI-RS BFD non-DRX | Huawei, HiSilicon | CR | Agreement | Yes |
YesAgreed after the meeting.
| agreed | No | R5‑201673 | |||
| R5‑201674 | Update FR1 Test Tolerance of 6.5.5.4 CSI-RS BFD DRX | Huawei, HiSilicon | CR | Agreement | Yes |
Yesr2
| revised | No | R5‑203098 | |||
| R5‑203098 | Update FR1 Test Tolerance of 6.5.5.4 CSI-RS BFD DRX | Huawei, HiSilicon | CR | Agreement | Yes |
YesAgreed after the meeting.
| agreed | No | R5‑201674 | |||
| R5‑201675 | Update FR1 Test Tolerance of 6.5.4.1 UL carrier RRC reconfiguration delay | Huawei, HiSilicon | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑203092 | |||
| R5‑203092 | Update FR1 Test Tolerance of 6.5.4.1 UL carrier RRC reconfiguration delay | Huawei, HiSilicon | CR | Agreement | Yes |
YesAgreed after the meeting.
| agreed | No | R5‑201675 | |||
| R5‑201676 | Correction to inter-freq measurement TCs for SSB configuration | Huawei, HiSilicon | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑201677 | Correction to TC 6.3.2.3.1 for the test procedure | Huawei, HiSilicon | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑201822 | Correction of SS-SINR applicability -SA | ROHDE & SCHWARZ | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑202264 | Core alignment in 6.6.1.2 NR SA FR1 event-triggered reporting without gap in DRX | Anritsu | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202985 | |||
| R5‑202985 | Core alignment in 6.6.1.2 NR SA FR1 event-triggered reporting without gap in DRX | Anritsu | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202264 | |||
| R5‑202266 | Correction on NR SA FR1 - E-UTRAN event-triggered reporting tests | Anritsu | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202747 | |||
| R5‑202747 | Correction on NR SA FR1 - E-UTRAN event-triggered reporting tests | Anritsu | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202266 | |||
| R5‑202272 | Correction to NR E-UTRA reselection tests | Anritsu | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202986 | |||
| R5‑202986 | Correction to NR E-UTRA reselection tests | Anritsu | CR | Agreement | Yes |
YesAgreed after the meeting.
| agreed | No | R5‑202272 | |||
| R5‑202273 | Correction to NR SA FR1 - E-UTRA RRC Connection release with redirection | Anritsu | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑202274 | Correction to NR SA FR1 handover test cases | Anritsu | CR | Agreement | Yes |
Yesr2
R4-2006071 was revised to R4-2008539 and agreed.
| revised | No | R5‑202987 | |||
| R5‑202987 | Correction to NR SA FR1 handover test cases | Anritsu | CR | Agreement | Yes |
YesAgreed after the meeting.
| agreed | No | R5‑202274 | |||
| R5‑202275 | Correction to SA event triggered reporting tests with per-UE gaps | Anritsu | CR | Agreement | Yes |
Yesr1
R4-2006073 was withdrawn for further discussion for next RAN4 meeting.
| revised | No | R5‑202988 | |||
| R5‑202988 | Correction to SA event triggered reporting tests with per-UE gaps | Anritsu | CR | Agreement | Yes |
Yeswithdrawn after the meeting.
| withdrawn | Yes | R5‑202275 | |||
| R5‑202416 | Alignment 6.4.1.1 test procedure with 4.4.1.1 | Keysight Technologies UK Ltd | CR | Agreement | Yes |
Yesincluded in R5-202269 (Anritsu).
| withdrawn | Yes | ||||
| R5‑202419 | Update 6.5.1.2 message content exception and test procedure | Keysight Technologies UK Ltd | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202748 | |||
| R5‑202748 | Update 6.5.1.2 message content exception and test procedure | Keysight Technologies UK Ltd | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202419 | |||
| R5‑202489 | Correction of RRM Test Case 6.1.1.1 | MediaTek Inc. | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202749 | |||
| R5‑202749 | Correction of RRM Test Case 6.1.1.1 | MediaTek Inc. | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202489 | |||
| R5‑202490 | Correction of RRM Test Case 6.1.1.2 | MediaTek Inc. | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202750 | |||
| R5‑202750 | Correction of RRM Test Case 6.1.1.2 | MediaTek Inc. | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202490 | |||
| R5‑202496 | Correction of RRM Test Case 6.4.1.1 | MediaTek Inc. | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| 5.3.2.9.4 | NR standalone with at least one NR cell in FR2 (Clause7) | R5‑201393 | Addition of minimum conformance requirements 7.7.1.0 - SA FR2 SS-RSRP accuracy | Huawei, HiSilicon | CR | Agreement | Yes |
Yesoverlapped with R&S R5-202073.
| withdrawn | Yes | ||
| R5‑201394 | Correction to NR test case 7.7.1.3.1 SA FR2 SS-RSRP absolute accuracy | Huawei, HiSilicon | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202834 | |||
| R5‑202834 | Correction to NR test case 7.7.1.3.1 SA FR2 SS-RSRP absolute accuracy | Huawei, HiSilicon | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201394 | |||
| R5‑201395 | Correction to NR test case 7.7.1.3.2 SS-RSRP relative accuracy | Huawei, HiSilicon | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑201411 | Addition to NR test case 7.3.2.1.3 FR2-FR2 RRC re-establishment without serving cell timing | Huawei, HiSilicon | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202835 | |||
| R5‑202835 | Addition to NR test case 7.3.2.1.3 FR2-FR2 RRC re-establishment without serving cell timing | Huawei, HiSilicon | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201411 | |||
| R5‑201412 | Addition to minimum conformance requirements 7.5.1.0.5 - Scheduling restriction for RLM | Huawei, HiSilicon | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑201413 | Addition to NR test case 7.5.1.9 FR2 RLM scheduling restrictions | Huawei, HiSilicon | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202836 | |||
| R5‑202836 | Addition to NR test case 7.5.1.9 FR2 RLM scheduling restrictions | Huawei, HiSilicon | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201413 | |||
| R5‑201414 | Addition to minimum Conformance Requirements 7.5.6.1.0 - DCI-based DL active BWP switch | Huawei, HiSilicon | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑201415 | Addition to NR test case 7.5.6.1.3 FR2 DCI-based DL active BWP switch non-DRX | Huawei, HiSilicon | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑201683 | Update of TC 7.1.1.1 intra-freq cell re-selection | Huawei, HiSilicon, MediaTek Inc. | CR | Agreement | Yes |
Yesr2
| revised | No | R5‑202751 | |||
| R5‑202751 | Update of TC 7.1.1.1 intra-freq cell re-selection | Huawei, HiSilicon, MediaTek Inc. | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201683 | |||
| R5‑201684 | Update of TC 7.1.1.2 inter-freq cell re-selection | Huawei, HiSilicon, MediaTek Inc. | CR | Agreement | Yes |
Yesr2
| revised | No | R5‑202752 | |||
| R5‑202752 | Update of TC 7.1.1.2 inter-freq cell re-selection | Huawei, HiSilicon, MediaTek Inc. | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201684 | |||
| R5‑202073 | Minimum requirements SS-RSRP SA FR2 | ROHDE & SCHWARZ | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑202074 | Addition 7.7.1.1 | ROHDE & SCHWARZ | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑202075 | Addition 7.7.1.2 | ROHDE & SCHWARZ | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑202076 | Minimum requirements SS-RSRQ SA FR2 | ROHDE & SCHWARZ | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑202077 | Addition 7.7.2.1 | ROHDE & SCHWARZ | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑202078 | Addition 7.7.2.2 | ROHDE & SCHWARZ | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑202079 | Minimum requirements SS-SINR SA FR2 | ROHDE & SCHWARZ | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑202080 | Addition 7.7.3.1 | ROHDE & SCHWARZ | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑202081 | Addition 7.7.3.2 | ROHDE & SCHWARZ | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑202096 | Correction of RRM Test Case 7.6.2.1 | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑202097 | Correction of RRM Test Case 7.6.2.2 | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑202098 | Correction of RRM Test Case 7.6.2.3 | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑202099 | Correction of RRM Test Case 7.6.2.4 | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑202100 | Correction of RRM Test Case 7.6.2.5 | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑202101 | Correction of RRM Test Case 7.6.2.6 | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑202102 | Correction of RRM Test Case 7.6.2.7 | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑202103 | Correction of RRM Test Case 7.6.2.8 | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑202202 | Clarification of disabling Tx diversity for FR2 UE for FR2 RRM testing | Huawei, HiSilicon | CR | Agreement | Yes |
Yesr2
| revised | No | R5‑202913 | |||
| R5‑202913 | Clarification of disabling Tx diversity for FR2 UE for FR2 RRM testing | Huawei, HiSilicon | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202202 | |||
| R5‑202402 | Addition of new RRM Test Cases in clause 7.5.3 | Samsung R&D Institute UK | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202753 | |||
| R5‑202753 | Addition of new RRM Test Cases in clause 7.5.3 | Samsung R&D Institute UK | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202402 | |||
| R5‑202403 | Addition of new RRM Test Cases in clause 7.5.7 | Samsung R&D Institute UK | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202754 | |||
| R5‑202754 | Addition of new RRM Test Cases in clause 7.5.7 | Samsung R&D Institute UK | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202403 | |||
| R5‑202491 | Correction of RRM Test Case 7.1.1.1 | MediaTek Inc. | CR | Agreement | Yes |
Yesmerged into Hauewei's R5-201683
| withdrawn | Yes | ||||
| R5‑202492 | Correction of RRM Test Case 7.1.1.2 | MediaTek Inc. | CR | Agreement | Yes |
Yesmerged into Hauewei's R5-201684
| withdrawn | Yes | ||||
| R5‑202493 | Correction of RRM Test Case 7.1.1.2 | MediaTek Inc. | CR | Agreement | No |
Yeslate doc
| withdrawn | Yes | ||||
| R5‑202494 | Correction of RRM Test Case 7.1.1.2 | MediaTek Inc. | CR | Agreement | No |
Yeslate doc
| withdrawn | Yes | ||||
| 5.3.2.9.5 | E-UTRA – NR Inter-RAT with E-UTRA serving cell (Clause 8) | R5‑201396 | Correction to NR test case 8.2.1.1 higher priority NR cell reselection | Huawei, HiSilicon | CR | Agreement | Yes |
Yes
| agreed | No | ||
| R5‑201397 | Correction to NR test case 8.3.1.1 handover to known cell | Huawei, HiSilicon | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202837 | |||
| R5‑202837 | Correction to NR test case 8.3.1.1 handover to known cell | Huawei, HiSilicon | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201397 | |||
| R5‑201398 | Correction to NR test case 8.4.1.1 SFTD non-DRX | Huawei, HiSilicon | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑201399 | Correction to NR test case 8.4.1.2 SFTD DRX | Huawei, HiSilicon | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑201400 | Correction to NR test case 8.4.2.1 event-triggered without SSB index non-DRX | Huawei, HiSilicon | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑201401 | Correction to NR test case 8.4.2.2 event-triggered without SSB index DRX | Huawei, HiSilicon | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑201402 | Correction to NR test case 8.4.2.3 event-triggered with SSB index non-DRX | Huawei, HiSilicon | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑201403 | Correction to NR test case 8.4.2.4 event-triggered with SSB index DRX | Huawei, HiSilicon | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑201404 | Correction to NR test case 8.5.1.1 SFTD accuracy | Huawei, HiSilicon | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑201686 | Update of TC 8.4.2.5 FR2 event-triggered without SSB index non-DRX | Huawei, HiSilicon | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑201687 | Update of TC 8.4.2.6 FR2 event-triggered without SSB index DRX | Huawei, HiSilicon | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑201688 | Update of TC 8.4.2.7 FR2 event-triggered with SSB index non-DRX | Huawei, HiSilicon | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑201689 | Update of TC 8.4.2.8 FR2 event-triggered with SSB index DRX | Huawei, HiSilicon | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑202054 | Minimum Requirements SS-RSRP iRAT | ROHDE & SCHWARZ | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑202055 | Addition 8.5.2.1.1 | ROHDE & SCHWARZ | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑202056 | Addition 8.5.2.1.2 | ROHDE & SCHWARZ | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑202057 | Minimum Requirements SS-RSRQ iRAT | ROHDE & SCHWARZ | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑202058 | Addition 8.5.2.2.1 | ROHDE & SCHWARZ | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑202059 | Addition 8.5.2.2.2 | ROHDE & SCHWARZ | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑202060 | Minimum Requirements SS-SINR iRAT | ROHDE & SCHWARZ | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑202061 | Addition 8.5.2.3.1 | ROHDE & SCHWARZ | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑202062 | Addition 8.5.2.3.2 | ROHDE & SCHWARZ | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| 5.3.2.9.6 | Clauses 1-3 / Annexes | R5‑201416 | Addition of Default Configuration in Annex H | Huawei, HiSilicon | CR | Agreement | Yes |
Yes1417; cl. aff.
r1
| revised | No | R5‑202838 | |
| R5‑202838 | Addition of Default Configuration in Annex H | Huawei, HiSilicon | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201416 | |||
| R5‑201690 | Update of Annex D.4.1.1 for parameters of BFD with 4RX | Huawei, HiSilicon | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202839 | |||
| R5‑202839 | Update of Annex D.4.1.1 for parameters of BFD with 4RX | Huawei, HiSilicon | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201690 | |||
| R5‑201691 | Update of FR1 Test Tolerance in Annex F | Huawei, HiSilicon | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑203093 | |||
| R5‑203093 | Update of FR1 Test Tolerance in Annex F | Huawei, HiSilicon | CR | Agreement | Yes |
YesAgreed after the meeting.
| agreed | No | R5‑201691 | |||
| R5‑201692 | Update of Cell mapping in Annex E | Huawei, HiSilicon | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202840 | |||
| R5‑202840 | Update of Cell mapping in Annex E | Huawei, HiSilicon | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201692 | |||
| R5‑201693 | Update of OCGN configuration in Annex A | Huawei, HiSilicon | CR | Agreement | Yes |
Yesoverlapped with E///'s R5-202091.
| withdrawn | Yes | ||||
| R5‑201820 | Add auxiliary bands for RRM inter-frequency SA tests | ROHDE & SCHWARZ | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202841 | |||
| R5‑202841 | Add auxiliary bands for RRM inter-frequency SA tests | ROHDE & SCHWARZ | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201820 | |||
| R5‑202052 | Add information on the AoA change during test for RRM FR2 tests | ROHDE & SCHWARZ | CR | Agreement | Yes |
Yes"Anritsu comment to the CR
Author requested to withdraw, to come back during the next meeting RAN5 #88-e. The reason for this is to allow more time to discuss and come up with the proper wording"
| withdrawn | Yes | ||||
| R5‑202091 | Correction of OCNG configurations and CSI-RS for tracking in Annex A | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑202092 | Cell configuration for SA FR2 event-triggered reporting test cases | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑202093 | Correction of MeasGapConfig in Annex H | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑202094 | Editorial correction of RRM TT in Annex F | Ericsson | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202701 | |||
| R5‑202701 | Editorial correction of RRM TT in Annex F | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202094 | |||
| R5‑202276 | Correction to TRS configuration | Anritsu | CR | Agreement | Yes |
Yes
| withdrawn | Yes | ||||
| R5‑202278 | Updates of FR2 MU and TT in TS 38.533 | Anritsu | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202914 | |||
| R5‑202914 | Updates of FR2 MU and TT in TS 38.533 | Anritsu | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202278 | |||
| R5‑202385 | Addition of RRM Cell configuration mapping table for EN-DC FR1 Test Case 4.5.4.1 | Samsung R&D Institute UK | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑202387 | Addition of RRC message content exceptions for UE UL Carrier Reconfiguration Delay | Samsung R&D Institute UK | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑202389 | Addition of RRM Test Case 4.5.4.1 in Annex F | Samsung R&D Institute UK | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑202488 | Correction to the simulated cell for cell-reselection test cases | MediaTek Inc. | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑202497 | Title Correction of Annex D.4.2.4 | MediaTek Inc. | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| 5.3.2.10 | TS 36.508 | |||||||||||
| 5.3.2.11 | TS 36.521-3 | |||||||||||
| 5.3.2.12 | TS 37.571-1 | |||||||||||
| 5.3.2.13 | TS 37.571-3 | |||||||||||
| 5.3.2.14 | TS 37.571-5 | |||||||||||
| 5.3.2.15 | TR 38.903 ((NR MU & TT analyses) | R5‑201606 | MU contributors for RRM FR2 TC 7.7.1.1 | ROHDE & SCHWARZ | CR | Agreement | Yes |
Yesr3
| revised | No | R5‑202915 | |
| R5‑202915 | MU contributors for RRM FR2 TC 7.7.1.1 | ROHDE & SCHWARZ | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201606 | |||
| R5‑201662 | FR1 Test tolerance analysis for interruptions deactivated E-UTRAN SCC | Huawei, HiSilicon | CR | Agreement | Yes |
Yesdependent on R4-2007665, revised to R4-2008542 and agreed.
was agreed after the meeting.
| agreed | No | ||||
| R5‑201663 | FR1 Test tolerance analysis for SCell activation | Huawei, HiSilicon | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑203094 | |||
| R5‑203094 | FR1 Test tolerance analysis for SCell activation | Huawei, HiSilicon | CR | Agreement | Yes |
YesAgreed after the meeting.
| agreed | No | R5‑201663 | |||
| R5‑201664 | FR1 Test tolerance analysis for SSB based BFR | Huawei, HiSilicon | CR | Agreement | Yes |
Yes"Coordinator: Won’t be agreed this meeting
Author requested to withdraw as the RAN4 parameters need to be further checked"
| withdrawn | Yes | ||||
| R5‑201665 | FR1 Test tolerance analysis for CSI-RS based BFR | Huawei, HiSilicon | CR | Agreement | Yes |
Yes"Coordinator: Won’t be agreed this meeting
Author requested to withdraw as the RAN4 parameters need to be further checked"
| withdrawn | Yes | ||||
| R5‑201713 | FR2 TT analysis for 38.533 5.7.1.1+7.7.1.1 Intra-freq SS-RSRP | ANRITSU LTD | discussion | Endorsement | Yes |
Yes3GU WIC allocation does not match AI allocation!!!
3GU allocation: 5GS_NR_LTE-UEConTest / AI allocation: NR_CADC_NR_LTE_DC_R16-UEConTest.
noted and proposals endorsed. Serves as template for RAN5#88e FR2 RRM TT analysis framework
Agenda Allocation was changed: [5.3.8.9]->[5.3.2.15].
"
| noted | No | ||||
| R5‑201714 | FR2 TT analysis for 38.533 5.7.1.2+7.7.1.2 Inter-freq SS-RSRP | ANRITSU LTD | discussion | Endorsement | Yes |
Yes3GU WIC allocation does not match AI allocation!!!
3GU allocation: 5GS_NR_LTE-UEConTest / AI allocation: NR_CADC_NR_LTE_DC_R16-UEConTest
noted and proposals endorsed. Serves as template for RAN5#88e FR2 RRM TT analysis framework
Agenda Allocation was changed: [5.3.8.9]->[5.3.2.15].
"
| noted | No | ||||
| R5‑201716 | Addition of Test Tolerance analysis for FR2 Tx Timing Test cases | ANRITSU LTD | CR | Agreement | Yes |
Yes+ in Word name
r1
| revised | No | R5‑202876 | |||
| R5‑202876 | Addition of Test Tolerance analysis for FR2 Tx Timing Test cases | ANRITSU LTD | CR | Agreement | No |
Yes
| withdrawn | Yes | R5‑201716 | |||
| R5‑202085 | Addition of Quiet Zone size above 30cm to TR 38.903 | ROHDE & SCHWARZ | CR | Agreement | Yes |
Yes"Associated discussion paper in R5-202082
based on outcome of discussion paper, propose to mark this CR as ""Not Pursued""."
| not pursued | No | ||||
| R5‑202104 | Test tolerance correction for event triggered measurement test cases | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑202105 | Test tolerance correction for CSI-RS-based L1-RSRP measurement test cases | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑202125 | CR to 38.903 to introduce PC1 MU Tables | Keysight Technologies UK Ltd | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202916 | |||
| R5‑202916 | CR to 38.903 to introduce PC1 MU Tables | Keysight Technologies UK Ltd | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202125 | |||
| R5‑202128 | CR to 38.903 to introduce baseline Demod MU tables | Keysight Technologies UK Ltd | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202769 | |||
| R5‑202769 | CR to 38.903 to introduce baseline Demod MU tables | Keysight Technologies UK Ltd | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202128 | |||
| R5‑202279 | Update to FR2 Measurement Uncertainties | Anritsu | CR | Agreement | Yes |
Yesr2
| revised | No | R5‑202917 | |||
| R5‑202917 | Update to FR2 Measurement Uncertainties | Anritsu | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202279 | |||
| R5‑202384 | Addition of EIRP to Transmit OFF power MU analysis | Samsung R&D Institute UK | CR | Agreement | Yes |
Yesr1
MU web conference call comments from R&S and Keysight.
r3
| revised | No | R5‑202938 | |||
| R5‑202938 | Addition of EIRP to Transmit OFF power MU analysis | Samsung R&D Institute UK | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202384 | |||
| R5‑202391 | Test Tolerance analysis TC 4.5.4 and 6.5.4 RRC reconfiguration delay | Samsung R&D Institute UK | CR | Agreement | Yes |
Yes+
r1
| revised | No | R5‑202702 | |||
| R5‑202702 | Test Tolerance analysis TC 4.5.4 and 6.5.4 RRC reconfiguration delay | Samsung R&D Institute UK | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202391 | |||
| 5.3.2.16 | TR 38.905 (NR Test Points Radio Transmission and Reception ) | R5‑201456 | Discussion on Test Point analysis for NR FR2 Frequency Error CA test cases | NTT DOCOMO INC. | discussion | Endorsement | No |
Yes
| withdrawn | Yes | ||
| R5‑201457 | Test Point analysis for FR2 Frequency Error for CA | NTT DOCOMO INC. | CR | Agreement | Yes |
Yesr2
| revised | No | R5‑202918 | |||
| R5‑202918 | Test Point analysis for FR2 Frequency Error for CA | NTT DOCOMO INC. | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201457 | |||
| R5‑201566 | Test Point analysis for FR2 Spectrum Emission Mask for CA | NTT DOCOMO INC. | CR | Agreement | Yes |
Yesoverlapping with R5-202134, R5-202135, R5-202136 and R5-202137.
| withdrawn | Yes | ||||
| R5‑201567 | Test Point analysis for FR2 Adjacent channel leakage ratio for CA | NTT DOCOMO INC. | CR | Agreement | Yes |
Yesoverlapping with R5-202134, R5-202135, R5-202136 and R5-202137.
| withdrawn | Yes | ||||
| R5‑201746 | Addition of Number of test points for FR1 in SUL test cases | Huawei,Hisilicon | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑201747 | Addition of TP analysis for FR1 A-MPR for CA | Huawei,Hisilicon | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑201767 | Test points analysis for NS_40 A_MPR FR1 test case | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑201769 | Test points analysis for NS_41 A_MPR FR1 test case | Ericsson | CR | Agreement | Yes |
Yesr2
| revised | No | R5‑202755 | |||
| R5‑202755 | Test points analysis for NS_41 A_MPR FR1 test case | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201769 | |||
| R5‑201771 | Test points analysis for NS_42 A_MPR FR1 test case | Ericsson | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202756 | |||
| R5‑202756 | Test points analysis for NS_42 A_MPR FR1 test case | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201771 | |||
| R5‑201856 | Updating TP of MOP for intra-band contiguous EN-DC | Huawei, HiSilicon | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202952 | |||
| R5‑202952 | Updating TP of MOP for intra-band contiguous EN-DC | Huawei, HiSilicon | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201856 | |||
| R5‑201857 | Updating TP of MOP for intra-band non-contiguous EN-DC | Huawei, HiSilicon | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202953 | |||
| R5‑202953 | Updating TP of MOP for intra-band non-contiguous EN-DC | Huawei, HiSilicon | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201857 | |||
| R5‑201871 | Update of test points analysis in UE co-existence for inter-band EN-DC | Huawei,Hisilicon | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑201872 | Update of Test Point Analysis for UE Co-existence for DC_5A-n66A | Huawei,Hisilicon | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑201873 | Update of Test Point Analysis for UE Co-existence for DC_5A-n78A | Huawei,Hisilicon | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑201874 | Update of Test Point Analysis for UE Co-existence for DC_66A-n5A | Huawei,Hisilicon | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑201875 | Update of Test Point Analysis for UE Co-existence for DC_66A-n78A | Huawei,Hisilicon | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑201929 | Cleanup in 38.905 | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑201930 | Combined TP analysis for MPR, NR ACLR and SEM FR1 test cases | Ericsson, Keysight Technologies, Huawei, CAICT | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202954 | |||
| R5‑202954 | Combined TP analysis for MPR, NR ACLR and SEM FR1 test cases | Ericsson, Keysight Technologies, Huawei, CAICT | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201930 | |||
| R5‑201931 | Combined TP analysis for MPR, ACLR and SEM intra-band contiguous EN-DC test cases | Ericsson, Keysight Technologies | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑202029 | Introduction of test point analysis for 2CCs EN-DC TCs in FR1 in 7.6B Blocking characteristics for DC and 7.7B Spurious response for DC | CAICT | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑202111 | NS_24 TP analysis to TR 38.905 | Dish Network | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑202376 | Updated TP analysis for 7.3A Reference sensitivity for CA | Ericsson, WE Certification, DISH | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202955 | |||
| R5‑202955 | Updated TP analysis for 7.3A Reference sensitivity for CA | Ericsson, WE Certification, DISH | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202376 | |||
| R5‑202432 | TP_analysis_6.5.3.3_TX_Additional_SpurEmission_NS_05 | QUALCOMM Europe Inc. - Italy | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202757 | |||
| R5‑202757 | TP_analysis_6.5.3.3_TX_Additional_SpurEmission_NS_05 | QUALCOMM Europe Inc. - Italy | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202432 | |||
| R5‑202433 | TP_analysis_6.5.3.3_TX_Additional_SpurEmission_NS_05 | QUALCOMM Europe Inc. - Italy | CR | Agreement | Yes |
Yesr1
title change! -> 43!
| revised | No | R5‑202523 | |||
| R5‑202523 | TP_analysis_6.5.3.3_TX_Additional_SpurEmission_NS_05 | QUALCOMM Europe Inc. - Italy | CR | Agreement | No |
Yesreissued as R5-202524 because of title change.
| withdrawn | Yes | R5‑202433 | |||
| R5‑202524 | TP_analysis_6.5.3.3_TX_Additional_SpurEmission_NS_43 | QUALCOMM Europe Inc. - Italy | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| 5.3.2.17 | Discussion Papers / Work Plan / TC lists | R5‑201327 | Discussion on AP 85.25 ACLR metric change | Qualcomm Finland RFFE Oy | discussion | Discussion | Yes |
Yesr1
| revised | No | R5‑202842 | |
| R5‑202842 | Discussion on AP 85.25 ACLR metric change | Qualcomm Finland RFFE Oy | discussion | Discussion | Yes |
Yesproposals Endorsed .Proposal incorporated in CR R5-202290(Anritsu)
| noted | No | R5‑201327 | |||
| R5‑201468 | MBR impact on testability | NTT DOCOMO, INC. | discussion | Endorsement | Yes |
YesKeysight Spain wondered about the purpose of the paper regarding FR2a and 2b.
Qualcomm: we should wait for RAN4.
Apple: same point as Qualcomm. There could be a conflict between RAN5 and RAN4.
Keysight Spain: there would be a MU calculation per band.
AT&T: problematic if MBR values ae not update.
NTT DOCOMO: the Rel-15 core requirement is not good.
Ericsson: can improve testability, can lower the MU impact.
AT&T: it will be intersting to see what RAN4 is doing concerning Rel-15.
| noted | No | ||||
| R5‑201476 | MU and TT for MOP spherical coverage for Intra-band contiguous CA | NTT DOCOMO INC. | discussion | Endorsement | Yes |
Yes
| noted | No | ||||
| R5‑201603 | On the QoQZ validation procedure for enhanced IFF | ROHDE & SCHWARZ | discussion | Endorsement | Yes |
Yesr1
| revised | No | R5‑202704 | |||
| R5‑202704 | On the QoQZ validation procedure for enhanced IFF | ROHDE & SCHWARZ | discussion | Endorsement | Yes |
Yes"Revised from: R5-201603r1.
noted and proposal is endorsed and implemented in R5-201604
"
| noted | No | R5‑201603 | |||
| R5‑201605 | RRM FR2 MU: Representative test case 7.7.1.1 | ROHDE & SCHWARZ | discussion | Endorsement | Yes |
YesKeysight Spain agreed with Anritsu on EVM.
r1
| revised | No | R5‑202843 | |||
| R5‑202843 | RRM FR2 MU: Representative test case 7.7.1.1 | ROHDE & SCHWARZ | discussion | Endorsement | Yes |
YesProposals endorsed
| noted | No | R5‑201605 | |||
| R5‑201818 | Review on test point analysis | NTT DOCOMO, INC. | discussion | Endorsement | Yes |
Yesis endorsed.
| noted | No | ||||
| R5‑201819 | On RRM inter-frequency tests in narrow NR bands | ROHDE & SCHWARZ | CR | Agreement | No |
Yes
| withdrawn | Yes | ||||
| R5‑201839 | On RRM inter-frequency tests in narrow NR bands | ROHDE & SCHWARZ | discussion | Endorsement | Yes |
YesDish recommended sending an LS.
Orange agreed, and wondered why we cannot take not 10 MHz.
R&S: we need 2 cells, so it doesn't fit.
| noted | No | ||||
| R5‑201840 | Discussion on testing of 4Rx vs 2Rx in FR1 | Huawei, CAICT, OPPO, Samsung, Bureau Veritas, Sporton, Ericsson, Anritsu, AT&T, Keysight, CMCC, Dish, Telecom Italia, Orange, Rohde&Schwarz | discussion | Discussion | Yes |
Yesr1
Dish raised concerns with Proposal 1.
AT&T: testability issue for 2Rx, maybe skip the test.
Qualcomm: OEM's guidance on 2Rx.
CMCC: guidelines from RAN4 is desirable.
r2
| revised | No | R5‑202811 | |||
| R5‑202811 | Discussion on testing of 4Rx vs 2Rx in FR1 | Huawei, CAICT, OPPO, Samsung, Bureau Veritas, Sporton, Ericsson, Anritsu, AT&T, Keysight, CMCC, Dish, Telecom Italia, Orange, Rohde&Schwarz | discussion | Discussion | Yes |
Yes
| noted | No | R5‑201840 | |||
| R5‑201852 | On ACLR test metric for FR2 related to AP 85.25 | Huawei, HiSilicon | discussion | Discussion | Yes |
YesKeysight Spain: cannot measure with that assumption, it is a matter of stability.
Orange agreed to have less testing time. Adding the 2. beam can be damaging.
Keysight Spain: 10% of the test points could be affected by the noise.
Qualcomm suggested to be conservative and choose 1dB.
Keysight: need to further discuss for the 2. beam.
Orange: from regulatory point of view we have to make sure 1 EIRP is the righ measurement to do.
Further offline discussion.
r1
| revised | No | R5‑202844 | |||
| R5‑202844 | On ACLR test metric for FR2 related to AP 85.25 | Huawei, HiSilicon | discussion | Discussion | Yes |
YesProposals endorsed
Proposal incorporated in CR R5-202290(Anritsu)
| noted | No | R5‑201852 | |||
| R5‑201869 | Discussion on test point analysis for spurious emission UE co-existence per EN-DC configuration | Huawei,Hisilicon | discussion | Discussion | Yes |
Yes"test cases CR's R5-201871-5
proposals to include TP analysis for completed Coex tests as well as future ENDC configs
the proposal is not scaleable for covering all the ENDC configs ,
Huawei- covers the TP analysis for 2CC only and is necessary to have to meet the test purpose
QC: do we consider all the spurs point analysis in the TP analysis across the test params
noted proposal endorsed and implemented in 201871-1875"
| noted | No | ||||
| R5‑201919 | Discussion on how to update TS 38.522 | China Mobile, Bureau Veritas, Huawei, Hisilicon, TTA, Sporton | discussion | Endorsement | Yes |
Yesr1
Dish agreed with E// comments that 2Rx and 4Rx not needed to be handled.
r3
| revised | No | R5‑202919 | |||
| R5‑202919 | Discussion on how to update TS 38.522 | China Mobile, Bureau Veritas, Huawei, Hisilicon, TTA, Sporton, Ericsson, CAICT, Qualcomm, R&S | discussion | Endorsement | Yes |
Yes"Revised from: R5-201919r3.
noted prop3,4,5,6 endorsed
handling of “Branch“ mentioned in proposals1/2 is not endorsed and will be revisited in future meeting."
| noted | No | R5‑201919 | |||
| R5‑202082 | Discussion on size of Quiet Zone above 30cm | ROHDE & SCHWARZ | discussion | Endorsement | Yes |
Yesnoted. proposals not endorsed. APs created to collect operator and manufacturer feedback.
| noted | No | ||||
| R5‑202115 | On Beam Peak Searches for different test configurations | Keysight Technologies UK Ltd | discussion | Endorsement | Yes |
Yesr1
"Revised from: R5-202115.
HW: provide proposal4 wording form ""100MHz CBW"" to ""a certain CBW""
R&S: In one of your previous emails you wrote that the loss of performance due to beam peak search reuse is totally the burden of OEMs. We think that there is also a risk for operators. Therefore, this declaration should only be applied when it does not matter which CBW is used for the beam peak search. As a logical consequence, 100 MHz CBW can be applied for the declaration which is our strong preference.
Orange: since there is a risk to not ensure the same performance from re-use beam I would prefer to keep the highest CBW as a declaration
R&S: Our strong preference is to apply 100 MHz CBW in order to minimize risk for all parties. The technical argument is that performing the beam peak search at a middle frequency reduces possible deviations of the beam peak at the other CBWs.
Applying the highest CBW will result in larger possible performance deviations at mid and low CHBW.
Are UEs scheduled always with highest CBW in the real life network operation?
Orange: In the real life the scheduling of the UE depends on the scheduler and the traffic at time t, so can be the lowest as well as highest CBW. Since there is a risk of the beam peak deviation even in the middle, I would prefer to increase the test numbers and make the declaration for low,mid and high.
If the declaration is the same , the lab performs the test only once
QC: Yes, P1-P3 seems agreeable to all parties.
For P4, Qualcomm is ok with highest or 100MHz. Qualcomm is not ok with choose any. If we can agree to P4 with a fixed value (Pending Hajer? & Chunying? to confirm) then good or else we can leave it open for next meeting
Orange: defer P4 to other meeting
KS: Definitely no consensus for Proposal 4. Given this situation, we will prepare a CR for the next meeting on vendor declarations for the other test configurations and require BP searches for every CBW until we have experience and maybe look into this again for Rel-16
HW: ok with endorsing P1-3
noted and prop1-3 endorsed, prop4 not endorsed
Revised to: R5-202939.
"
| revised | No | R5‑202939 | |||
| R5‑202939 | On Beam Peak Searches for different test configurations | Keysight Technologies UK Ltd | discussion | Endorsement | Yes |
Yes"Revised from: R5-202115r1.
noted and prop1-3 endorsed, prop4 not endorsed
"
| noted | No | R5‑202115 | |||
| R5‑202116 | On Beam Peak Searches for Intra-Band Contiguous CA | Keysight Technologies UK Ltd | discussion | Endorsement | Yes |
Yesr1
"Revised from: R5-202116.
ongoing discussions
could be noted with a final tdoc and proposal endorsed
Framework for UE vendor declaration along with test case CR implementing the proposal is planned in next RAN5 meet
Revised to: R5-202920.
"
| revised | No | R5‑202920 | |||
| R5‑202920 | On Beam Peak Searches for Intra-Band Contiguous CA | Keysight Technologies UK Ltd | discussion | Endorsement | Yes |
Yes"Revised from: R5-202116r1.
noted and proposal endorsed
"
| noted | No | R5‑202116 | |||
| R5‑202117 | On UBF for Intra-Band Carrier Aggregation | Keysight Technologies UK Ltd | discussion | Endorsement | Yes |
Yesassociated TS38.509 CR R5-202118.
Keysight confirmed upon the RAN5 Vice Chair's comment that this is beyond Rel-15.
"This contribution is discussing the need to further clarify the UBF, defined in 38.509, and the need to augment the applicability of the UBF for Carrier Aggregation (CA).
Associated CR R5-202118 (KEYS)
R&S: no change in 38.509 is needed , since the understanding is already assumed for prop1
for Rel15 Intraband CA whether this change is OK
for beyond rel15 ( interband CA) there is no solution but this may need to be revisited for interband CA combos once such band combos come up in RAN4.
Huawei : 38.521-2 has an editors note indicating UBF is FFS for intraband CA as such prop1 cannot be assumed.
For 117/118 KEYS to initiate the discussion on Ran5#87e main reflector and then we conclude in the approrpirate AI
ongoing discussions
noted and prop2 endorsed to be implemented in 202118
"
| noted | No | ||||
| R5‑202124 | On PC1 MUs | Keysight Technologies UK Ltd | discussion | Endorsement | Yes |
Yesr2
| revised | No | R5‑202845 | |||
| R5‑202845 | On PC1 MUs | Keysight Technologies UK Ltd | discussion | Endorsement | Yes |
YesProposals endorsed
| noted | No | R5‑202124 | |||
| R5‑202126 | On the order of test steps for output power dynamics test cases | Keysight Technologies UK Ltd | discussion | Endorsement | Yes |
YesTest case CR R5-202381 (implementing prop1&2)
minor validation impact , test needs to be revalidated with reason 7
Anritsu : needs more time to check the proposals
noted , proposals endorsed and implemented in 202381r1"
| noted | No | ||||
| R5‑202127 | On NR FR2 Demodulation MUs | Keysight Technologies UK Ltd | discussion | Endorsement | Yes |
YesAnritsu agreed to Mode 2, but not Mode 3. Proposal 1 Mode 1 this cannot be applied. Proposal 2 and 3 are ok. P5 is applicable for both.
r1
| revised | No | R5‑202846 | |||
| R5‑202846 | On NR FR2 Demodulation MUs | Keysight Technologies UK Ltd | discussion | Endorsement | Yes |
YesP1, P3, and P4 endorsed.
| noted | No | R5‑202127 | |||
| R5‑202163 | Discussion about power configuration for spurious emission for inter-band EN-DC | Guangdong OPPO Mobile Telecom. | discussion | Endorsement | Yes |
YesHuawei: the Pmax UTRA is configured to be not present, this is not aligned to RAN1. Agree to the proposal.
"CR is R5-202207 and R5-202208
impact to existing validations need to be accounted in the discussion. per Oppo the proposals is needed to verify the goal of the test
TEV need more time to check the validations
ATT: how does the prop fix the issue for UE supporting dynamic power sharing
BV: confirms there are existing validations
Huawei: the current RAN5 spec test configuration Pmax EUTRA is not present and not aligned to RAN1. prop1 addresses this misalignment
noted , proposals are implemented in R5-202731 & R5-202726
"
| noted | No | ||||
| R5‑202312 | DL Absolute Level Uncertainty for FR2 RRM | Anritsu | discussion | Endorsement | Yes |
YesKeysight Spain: would like to know on which test cases the MU is not critical.
Anritsu: 6dB is not a final value, it can be revised later.
r2
| revised | No | R5‑202847 | |||
| R5‑202847 | DL Absolute Level Uncertainty for FR2 RRM | Anritsu | discussion | Endorsement | Yes |
YesProposal is endorsed
| noted | No | R5‑202312 | |||
| R5‑202313 | FR2 receiver spurious emission uncertainties | Anritsu | discussion | Endorsement | Yes |
Yesnoted and proposals endorsed
| noted | No | ||||
| R5‑202314 | FR2 RRM timing measurement uncertainty | Anritsu | discussion | Endorsement | Yes |
YesR&S: need more time.
r1
| revised | No | R5‑202921 | |||
| R5‑202921 | FR2 RRM timing measurement uncertainty | Anritsu | discussion | Endorsement | Yes |
Yes"Revised from: R5-202314r1.
noted and proposals are endorsed
"
| noted | No | R5‑202314 | |||
| R5‑202315 | FR2 SNR Uncertainty | Anritsu | discussion | Endorsement | Yes |
Yesr1
| revised | No | R5‑202922 | |||
| R5‑202922 | FR2 SNR Uncertainty | Anritsu | discussion | Endorsement | Yes |
Yes"Revised from: R5-202315r1.
noted and proposals are endorsed
"
| noted | No | R5‑202315 | |||
| R5‑202316 | Noise impact for FR2 TRx test cases | Anritsu | discussion | Endorsement | Yes |
Yesr1
| revised | No | R5‑202848 | |||
| R5‑202848 | Noise impact for FR2 TRx test cases | Anritsu | discussion | Endorsement | Yes |
YesProposal is endorsed.
| noted | No | R5‑202316 | |||
| R5‑202317 | On FR2 ACLR MUs | Anritsu | discussion | Endorsement | Yes |
Yesr1
| revised | No | R5‑202849 | |||
| R5‑202849 | On FR2 ACLR MUs | Anritsu | discussion | Endorsement | Yes |
YesProposals 1 and 4 are endorsed.
| noted | No | R5‑202317 | |||
| R5‑202318 | On FR2 OBW MU | Anritsu | discussion | Endorsement | Yes |
YesProposals not endorsed
| noted | No | ||||
| R5‑202319 | On FR2 TRx testability and MU for PC1 device | Anritsu | discussion | Endorsement | Yes |
Yesr1
| revised | No | R5‑202850 | |||
| R5‑202850 | On FR2 TRx testability and MU for PC1 device | Anritsu | discussion | Endorsement | Yes |
YesProposal 4 endorsed
| noted | No | R5‑202319 | |||
| R5‑202320 | On frequency flatness uncertainty for FR2 RRM and Performance tests | Anritsu | discussion | Endorsement | Yes |
Yesr1
| revised | No | R5‑202851 | |||
| R5‑202851 | On frequency flatness uncertainty for FR2 RRM and Performance tests | Anritsu | discussion | Endorsement | Yes |
YesProposals not endorsed
| noted | No | R5‑202320 | |||
| R5‑202321 | On the FR2 ACLR Testability | Anritsu | discussion | Endorsement | Yes |
YesOrange: it should be made sure that only 1 beam is considered as an interference.
Anritsu: if we test a 2. beam we test more than required by the core requirement.
Proposals endorsed
| noted | No | ||||
| R5‑202374 | Discussion on requirements for power class 2 UE in EN-DC MOP test case | Ericsson | discussion | Endorsement | Yes |
Yesthe RAN4 discussion was not so clear.
Nokia agreed to the proposal. There is still work to be done in RAN4. An LS should be sent.
T-Mobile USA also agreed.
OPPO disagreed. RAN4 has not yet agreed.
Samsung wondered about misalignment if RAN4 can't change the spec.
"no test case CR
QC: there are discussons R5-202434 CR R5-202435, the papers are aligned would be good to furhter decide within RAN5 before approaching RAN4
Huawei: does not agree with observations in the paper
Nokia: agrees with the observations in this paper
ATT: RAN4 needs specific action to address rel15 items
TMO: supports E/// proposals
Oppo: does not agree with E/// proposals
Email discussion is ongoing
HW request to flag for more offline discussion
QC: suggest brief meeting among interested parties to expedite this topic, open for after 5PM CEST or around 3AM CEST next week Monday/Tuesday
Prop1&2 endorsed"
| noted | No | ||||
| R5‑202375 | Discussion on Testpoint analysis and testing of lower order fallback in NR Rx CA test cases | Ericsson, WE Certification, DISH | discussion | Endorsement | Yes |
Yes"discussion on AP#85.21 , conference call set up for May26th
related CR 2376, 2377
proposals cover FR1 SA , ( addressing some of the open items that were LTE for this topic), ie completion rate of CA configs is slow due to this reason and also there is incorrect test config in LTE. CC is needed since it has impact to test case structure for 38.521-1 FR1 spec
E/// This can be noted since all the proposals are implemented in the CR to TR38.905 in 2376
noted and proposals are endorsed and implemented in R5-202376/7"
| noted | No | ||||
| R5‑202379 | Discussion on clarification of disabling of Tx diversity in FR2 testing | Huawei, HiSilicon | discussion | Discussion | Yes |
YesConclusion of offline discussion:
The UE under test shall be pre-configured with UL Tx diversity schemes disabled to account for single polarization System Simulator (SS) in the test environment. The UE under test is allowed to dual polarized transmit.
r2
| revised | No | R5‑202923 | |||
| R5‑202923 | Discussion on clarification of disabling of Tx diversity in FR2 testing | Huawei, HiSilicon | discussion | Discussion | Yes |
Yes
| noted | No | R5‑202379 | |||
| R5‑202382 | Discussion on FR2 EIRP Tx OFF power MU for test cases usage | Samsung R&D Institute UK | discussion | Discussion | Yes |
Yesr1
MU web conference call comments from R&S and Keysight.
r2
| revised | No | R5‑202872 | |||
| R5‑202872 | Discussion on FR2 EIRP Tx OFF power MU for test cases usage | Samsung R&D Institute UK | discussion | Discussion | Yes |
YesProposals endorsed
| noted | No | R5‑202382 | |||
| R5‑202392 | Discussion on Beam Correspondence measurement procedure | Samsung R&D Institute UK | discussion | Discussion | Yes |
Yes
| noted | No | ||||
| R5‑202397 | Discussion on SCell activation and deactivation delay | Samsung R&D Institute UK | discussion | Discussion | Yes |
Yestest case CR R5-202402, observation in this paper will be handled FR2 RRM TT in futhre RAN5 meetings
| noted | No | ||||
| R5‑202398 | Discussion on UE PSCell addition and release delay | Samsung R&D Institute UK | discussion | Discussion | Yes |
Yestest case CR R5-202402 , , observation in this paper will be handled FR2 RRM TT in future RAN5 meetings
| noted | No | ||||
| R5‑202417 | On txDirectCurrentLocation | Anritsu | discussion | Endorsement | Yes |
Yesr1
| revised | No | R5‑202924 | |||
| R5‑202924 | On txDirectCurrentLocation | Anritsu | discussion | Endorsement | Yes |
Yes
| noted | No | R5‑202417 | |||
| R5‑202434 | Discussion on per port testing for FR1 UL MIMO devices | QUALCOMM JAPAN LLC. | discussion | Discussion | Yes |
Yesopen topics of handling PC2 testing of UL-MIMO tests and relates to CAG LS in R5-201318
impacts proposals in R5-202374(E///)
Associated CR R5-202435(QC)
Huawei reqsted to flag the discussion paper along with CR 2435 need more offline discussion."
| noted | No | ||||
| R5‑202452 | DUT alignment for form factors other than smartphones | ROHDE & SCHWARZ | discussion | Endorsement | Yes |
YesDUT positioning guidelines for device types other than small handhelds
proposals not agreeable noted or not pursued?
R&S: preference is noted"
| noted | No | ||||
| R5‑202454 | On the MU for ALCR | ROHDE & SCHWARZ | discussion | Endorsement | Yes |
YesProposals endorsed
| noted | No | ||||
| R5‑202455 | Discussion on the power level for transmit modulation quality test cases | ROHDE & SCHWARZ | discussion | Endorsement | Yes |
Yesr1
| revised | No | R5‑202852 | |||
| R5‑202852 | Discussion on the power level for transmit modulation quality test cases | ROHDE & SCHWARZ | discussion | Endorsement | Yes |
YesProposals endorsed
| noted | No | R5‑202455 | |||
| R5‑202457 | Discussion on testability of ACS and IBB for CA | ROHDE & SCHWARZ | discussion | Endorsement | Yes |
Yesnoted and proposals endorsed
| noted | No | ||||
| R5‑202458 | On the MU of FR2 OBW | ROHDE & SCHWARZ | discussion | Endorsement | Yes |
YesProposals endorsed
| noted | No | ||||
| R5‑202459 | On the SNR for FR2 TRx test cases | ROHDE & SCHWARZ | discussion | Endorsement | Yes |
Yesdifferent values, but R&S can compromise with Anritsu.
Keysight: can discuss on the ACLR, but need more time on the spurious.
| noted | No | ||||
| R5‑202460 | On FR2 OBW MU | Keysight Technologies UK Ltd | discussion | Endorsement | Yes |
Yes P1 and P2 endorsed.
| noted | No | ||||
| R5‑202461 | On FR2 ACLR MU | Keysight Technologies UK Ltd | discussion | Endorsement | No |
Yes
| withdrawn | Yes | ||||
| R5‑202462 | On FR2 Spurious coexistence MU | Keysight Technologies UK Ltd | discussion | Endorsement | No |
Yes
| withdrawn | Yes | ||||
| R5‑202463 | On FR2 EVM MU | Keysight Technologies UK Ltd | discussion | Endorsement | No |
Yes
| withdrawn | Yes | ||||
| R5‑202464 | On FR2 Minimum Output power MU | Keysight Technologies UK Ltd | discussion | Endorsement | No |
Yes
| withdrawn | Yes | ||||
| 5.3.3 | Rel-15 LTE CA configurations (UID - 770064) LTE_CA_R15-UEConTest | |||||||||||
| 5.3.3.1 | TS 36.508 | |||||||||||
| 5.3.3.2 | TS 36.521-1 | R5‑201695 | Update REFSENS of CA_38A-40C BCS1 configuration in 7.3A.5 | Huawei, HiSilicon | CR | Agreement | Yes |
Yes
| agreed | No | ||
| R5‑201803 | Introduction of TDD FDD 6 DL CA PDSCH Closed Loop Multi Layer Spatial Multiplexing 4x2 for FDD PCell | LG Electronics | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑201804 | Introduction of TDD FDD 6 DL CA PDSCH Closed Loop Multi Layer Spatial Multiplexing 4x2 for TDD PCell | LG Electronics | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑201805 | Introduction of TDD FDD 7 DL CA PDSCH Open Loop Spatial Multiplexing 2x2 for FDD PCell | LG Electronics | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑201806 | Introduction of TDD FDD 7 DL CA PDSCH Open Loop Spatial Multiplexing 2x2 for TDD PCell | LG Electronics | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑201807 | Introduction of TDD FDD 7 DL CA PDSCH Single Antenna Port Performance for FDD PCell | LG Electronics | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑201808 | Introduction of TDD FDD 7 DL CA PDSCH Single Antenna Port Performance for TDD PCell | LG Electronics | CR | Agreement | Yes |
YesR5-201776
| agreed | No | ||||
| R5‑201809 | Update to TDD FDD 6 DL CA PDSCH Open Loop Spatial Multiplexing 2x2 for FDD PCell | LG Electronics | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑201810 | Update to TDD FDD 6 DL CA PDSCH Open Loop Spatial Multiplexing 2x2 for TDD PCell | LG Electronics | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑202174 | Addition of new TC 8.7.1.1_A.7 | SRTC | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑202175 | Addition of new TC 8.7.1.1_H.7 | SRTC | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑202176 | Addition of new TC 8.7.2.1_A.7 | SRTC | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑202177 | Addition of new TC 8.7.2.1_H.7 | SRTC | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| 5.3.3.3 | TS 36.521-2 | R5‑201698 | Addition of Rel-15 capabilities of multiple CA in 36.521-2 | Huawei, HiSilicon | CR | Agreement | Yes |
YesWIC Rel15
r2
| revised | No | R5‑202853 | |
| R5‑202853 | Addition of Rel-15 capabilities of multiple CA in 36.521-2 | Huawei, HiSilicon | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201698 | |||
| R5‑202180 | Adding applicability for RF test cases 8.7.1.1_A.7,8.7.1.1_H.7,8.7.2.1_A.7 and 8.7.2.1_H.7 | SRTC | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| 5.3.3.4 | TS 36.521-3 | |||||||||||
| 5.3.3.5 | TS 37.571-1 | |||||||||||
| 5.3.3.6 | TS 37.571-3 | |||||||||||
| 5.3.3.7 | TS 37.571-5 | |||||||||||
| 5.3.3.8 | TR 36.903 (E-UTRAN RRM TT analyses) | |||||||||||
| 5.3.3.9 | TR 36.904 (E-UTRAN Radio Reception TT analyses) | |||||||||||
| 5.3.3.10 | TR 36.905 (E-UTRAN Test Points Radio Transmission and Reception ) | R5‑201727 | Addition of TP analysis for CA_38A-40C BCS1 to 36.905 | Huawei, HiSilicon | CR | Agreement | Yes |
YesRel15
r1
| revised | No | R5‑202854 | |
| R5‑202854 | Addition of TP analysis for CA_38A-40C BCS1 to 36.905 | Huawei, HiSilicon | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201727 | |||
| 5.3.3.11 | Discussion Papers / Work Plan / TC lists | |||||||||||
| 5.3.4 | Add UE Power Class 2 to band 41 intra-band contiguous LTE Carrier Aggregation (UID - 780065) LTE_CA_C_B41_PC2-UEConTest | |||||||||||
| 5.3.4.1 | TS 36.521-1 | R5‑201776 | correction of references in tc 6.2.3A.1_3 Maximum Power Reduction (MPR) for CA (intra-band contiguous DL CA and UL CA) for HPUE | T-Mobile USA Inc. | CR | Agreement | Yes |
YesR5
r1
| revised | No | R5‑202758 | |
| R5‑202758 | correction of references in tc 6.2.3A.1_3 Maximum Power Reduction (MPR) for CA (intra-band contiguous DL CA and UL CA) for HPUE | T-Mobile USA Inc. | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201776 | |||
| R5‑201777 | Addition of new test case 6.2.4A.1_3 Additional Maximum Power Reduction (A-MPR) for CA (intra-band contiguous DL CA and UL CA) for HPUE | T-Mobile USA Inc. | CR | Agreement | Yes |
YesR5
r1
| revised | No | R5‑202759 | |||
| R5‑202759 | Addition of new test case 6.2.4A.1_3 Additional Maximum Power Reduction (A-MPR) for CA (intra-band contiguous DL CA and UL CA) for HPUE | T-Mobile USA Inc. | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201777 | |||
| R5‑201778 | Addition of new test case 6.2.5A.1_3 Configured UE transmitted Output Power for CA (intra-band contiguous DL CA and UL CA) for HPUE | T-Mobile USA Inc. | CR | Agreement | Yes |
YesR5
r1
| revised | No | R5‑202760 | |||
| R5‑202760 | Addition of new test case 6.2.5A.1_3 Configured UE transmitted Output Power for CA (intra-band contiguous DL CA and UL CA) for HPUE | T-Mobile USA Inc. | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201778 | |||
| R5‑201779 | Addition of new test case 6.6.2.3A.1_3 Adjacent Channel Leakage power Ratio for CA (intra-band contiguous DL CA and UL CA) for HPUE | T-Mobile USA Inc. | CR | Agreement | Yes |
YesR5
r1
| revised | No | R5‑202761 | |||
| R5‑202761 | Addition of new test case 6.6.2.3A.1_3 Adjacent Channel Leakage power Ratio for CA (intra-band contiguous DL CA and UL CA) for HPUE | T-Mobile USA Inc. | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201779 | |||
| R5‑202171 | correction in 6.2.2A.1_3 MOP for CA and HPUE (intra-band contiguous DL CA and UL CA) | T-Mobile USA Inc. | CR | Agreement | Yes |
YesR5
r1
| revised | No | R5‑202762 | |||
| R5‑202762 | correction in 6.2.2A.1_3 MOP for CA and HPUE (intra-band contiguous DL CA and UL CA) | T-Mobile USA Inc. | CR | Agreement | Yes |
Yes
| revised | No | R5‑202877 | R5‑202171 | ||
| R5‑202877 | correction in 6.2.2A.1_3 MOP for CA and HPUE (intra-band contiguous DL CA and UL CA) | T-Mobile USA Inc. | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202762 | |||
| R5‑202399 | Addition of new test case 6.6.2.1A.1_3 spectrum mission mask for CA and HPUE (intra-band contiguous DC CA and UL CA) | T-Mobile USA Inc. | CR | Agreement | No |
Yeslate doc
| withdrawn | Yes | ||||
| R5‑202400 | Addition of new test case 6.6.2.2A.1_3 Additional Spectrum Emission Mask for CA and HPUE (intra-band contiguous DL CA and UL CA) | T-Mobile USA Inc. | CR | Agreement | No |
Yeslate doc
| withdrawn | Yes | ||||
| R5‑202401 | Addition of new test case 6.6.3.1A.1_3 Transmitter Spurious emissions for CA and HPUE (intra-band contiguous DL CA and UL CA) | T-Mobile USA Inc. | CR | Agreement | No |
Yes
| withdrawn | Yes | ||||
| R5‑202425 | Addition of new test case 6.6.3.3A.1_3 Additional Spurious emissions for CA and HPUE (intra-band contiguous DL CA and UL CA) | T-Mobile USA Inc. | CR | Agreement | No |
Yeslate doc
| withdrawn | Yes | ||||
| 5.3.4.2 | TS 36.521-2 | R5‑201780 | Addition of applicability for MOP, MPR, A-MPR & ACLR for CA HPUE | T-Mobile USA Inc. | CR | Agreement | Yes |
Yes"Invalid file name
Invalid characters in file name
Source to TSG (R5) missing"
r1
| revised | No | R5‑20 | |
| R5‑202763 | Addition of applicability for MOP, MPR, A-MPR & ACLR for CA HPUE | T-Mobile USA Inc. | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201780 | |||
| 5.3.4.3 | TR 36.905 (E-UTRAN Test Points Radio Transmission and Reception ) | R5‑201781 | Addition of test points for A-MPR for CA HPUE | T-Mobile USA Inc. | CR | Agreement | Yes |
Yeslate doc
r1
| revised | No | R5‑202764 | |
| R5‑202764 | Addition of test points for A-MPR for CA HPUE | T-Mobile USA Inc. | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201781 | |||
| 5.3.4.4 | Discussion Papers / Work Plan / TC lists | |||||||||||
| 5.3.5 | Rel-16 CA configurations (UID - 810061) LTE_CA_R16-UEConTest | |||||||||||
| 5.3.5.1 | TS 36.508 | |||||||||||
| 5.3.5.2 | TS 36.521-1 | |||||||||||
| 5.3.5.3 | TS 36.521-2 | |||||||||||
| 5.3.5.4 | TS 36.521-3 | |||||||||||
| 5.3.5.5 | TS 37.571-1 | |||||||||||
| 5.3.5.6 | TS 37.571-3 | |||||||||||
| 5.3.5.7 | TS 37.571-5 | |||||||||||
| 5.3.5.8 | TR 36.903 (E-UTRAN RRM TT analyses) | |||||||||||
| 5.3.5.9 | TR 36.904 (E-UTRAN Radio Reception TT analyses) | |||||||||||
| 5.3.5.10 | TR 36.905 (E-UTRAN Test Points Radio Transmission and Reception ) | |||||||||||
| 5.3.5.11 | Discussion Papers / Work Plan / TC lists | |||||||||||
| 5.3.6 | Shortened TTI and processing time for LTE (UID - 820064) LTE_sTTIandPT-UEConTest | |||||||||||
| 5.3.6.1 | TS 36.508 | |||||||||||
| 5.3.6.2 | TS 36.521-1 | R5‑201889 | Addition of 6.2.2_s UE Maximum Output Power for short TTI | Huawei,Hisilicon | CR | Agreement | Yes |
Yesr2
| revised | No | R5‑202855 | |
| R5‑202855 | Addition of 6.2.2_s UE Maximum Output Power for short TTI | Huawei,Hisilicon | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201889 | |||
| R5‑201890 | Addition of 6.2.3_s UE Maximum Power Reduction for short TTI | Huawei,Hisilicon | CR | Agreement | Yes |
Yes
| revised | No | R5‑203090 | |||
| R5‑203090 | Addition of 6.2.3_s UE Maximum Power Reduction for short TTI | Huawei,Hisilicon | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201890 | |||
| R5‑201891 | Addition of 6.2.4_s UE Additional Maximum Power Reduction for short TTI | Huawei,Hisilicon | CR | Agreement | Yes |
Yes"Title inconsistency
-3GU: Addition of 6.2.4_s UE Additional Maximum Power -Reduction for short TTI / CR coversheet: Addition of 6.2.4_s UE Additional Maximum +Output Power for short TTI"
r2
| revised | No | R5‑202856 | |||
| R5‑202856 | Addition of 6.2.4_s UE Additional Maximum Power Reduction for short TTI | Huawei,Hisilicon | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201891 | |||
| R5‑201892 | Addition of 6.2.5_s Configured UE Transmitted Output Power for short TTI | Huawei,Hisilicon | CR | Agreement | Yes |
Yesall 'Normal'.
r1
| revised | No | R5‑202767 | |||
| R5‑202767 | Addition of 6.2.5_s Configured UE Transmitted Output Power for short TTI | Huawei,Hisilicon | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201892 | |||
| R5‑201893 | Addition of 6.3.4.1_s General ON/OFF time mask for short TTI | Huawei,Hisilicon | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202768 | |||
| R5‑202768 | Addition of 6.3.4.1_s General ON/OFF time mask for short TTI | Huawei,Hisilicon | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201893 | |||
| R5‑201894 | Addition of 6.5.2.1_s Error Vector Magnitude for short TTI | Huawei,Hisilicon | CR | Agreement | Yes |
Yesr2
| revised | No | R5‑202857 | |||
| R5‑202857 | Addition of 6.5.2.1_s Error Vector Magnitude for short TTI | Huawei,Hisilicon | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201894 | |||
| R5‑201895 | Addition of calculation of averaged EVM for short TTI | Huawei,Hisilicon | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑201896 | Addition of 8.14.1.1.1 FDD sPDSCH Open Loop Spatial Multiplexing Performance | Huawei,Hisilicon | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202770 | |||
| R5‑202770 | Addition of 8.14.1.1.1 FDD sPDSCH Open Loop Spatial Multiplexing Performance | Huawei,Hisilicon | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201896 | |||
| R5‑201897 | Addition of 8.14.1.1.2 FDD sPDSCH Closed Loop Spatial Multiplexing Performance | Huawei,Hisilicon | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202771 | |||
| R5‑202771 | Addition of 8.14.1.1.2 FDD sPDSCH Closed Loop Spatial Multiplexing Performance | Huawei,Hisilicon | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201897 | |||
| R5‑201898 | Addition of 8.14.1.2.1 TDD sPDSCH Open Loop Spatial Multiplexing Performance | Huawei,Hisilicon | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202772 | |||
| R5‑202772 | Addition of 8.14.1.2.1 TDD sPDSCH Open Loop Spatial Multiplexing Performance | Huawei,Hisilicon | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201898 | |||
| R5‑201899 | Addition of 8.14.1.2.2 TDD sPDSCH Closed Loop Spatial Multiplexing Performance | Huawei,Hisilicon | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202773 | |||
| R5‑202773 | Addition of 8.14.1.2.2 TDD sPDSCH Closed Loop Spatial Multiplexing Performance | Huawei,Hisilicon | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201899 | |||
| R5‑201900 | Addition of 8.14.2.1 FDD sPDCCH Transmit diversity performance | Huawei,Hisilicon | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202774 | |||
| R5‑202774 | Addition of 8.14.2.1 FDD sPDCCH Transmit diversity performance | Huawei,Hisilicon | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201900 | |||
| R5‑201901 | Addition of 8.14.2.2 TDD sPDCCH Transmit diversity performance | Huawei,Hisilicon | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202775 | |||
| R5‑202775 | Addition of 8.14.2.2 TDD sPDCCH Transmit diversity performance | Huawei,Hisilicon | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201901 | |||
| R5‑201902 | Addition of 9.12.1.1 FDD CQI Reporting under fading conditions based on CRS for short TTI | Huawei,Hisilicon | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202776 | |||
| R5‑202776 | Addition of 9.12.1.1 FDD CQI Reporting under fading conditions based on CRS for short TTI | Huawei,Hisilicon | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201902 | |||
| R5‑201903 | Addition of 9.12.1.2 TDD CQI Reporting under fading conditions based on CRS for short TTI | Huawei,Hisilicon | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202777 | |||
| R5‑202777 | Addition of 9.12.1.2 TDD CQI Reporting under fading conditions based on CRS for short TTI | Huawei,Hisilicon | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201903 | |||
| R5‑201904 | Addition of 9.12.2.1 FDD CQI Reporting under fading conditions based on CSI-RS for short TTI | Huawei,Hisilicon | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202778 | |||
| R5‑202778 | Addition of 9.12.2.1 FDD CQI Reporting under fading conditions based on CSI-RS for short TTI | Huawei,Hisilicon | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201904 | |||
| R5‑201905 | Addition of 9.12.2.2 TDD CQI Reporting under fading conditions based on CSI-RS for short TTI | Huawei,Hisilicon | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202779 | |||
| R5‑202779 | Addition of 9.12.2.2 TDD CQI Reporting under fading conditions based on CSI-RS for short TTI | Huawei,Hisilicon | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201905 | |||
| R5‑201906 | Addition of Reference Measurement Channels for short TTI | Huawei,Hisilicon | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202780 | |||
| R5‑202780 | Addition of Reference Measurement Channels for short TTI | Huawei,Hisilicon | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201906 | |||
| R5‑201907 | Update of Annex C.3.2 Downlink Physical Channels for short TTI | Huawei,Hisilicon | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202858 | |||
| R5‑202858 | Update of Annex C.3.2 Downlink Physical Channels for short TTI | Huawei,Hisilicon | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201907 | |||
| 5.3.6.3 | TS 36.521-2 | |||||||||||
| 5.3.6.4 | TS 36.521-3 | |||||||||||
| 5.3.6.5 | TR 36.903 (E-UTRAN RRM TT analyses) | |||||||||||
| 5.3.6.6 | TR 36.905 (E-UTRAN Test Points Radio Transmission and Reception ) | |||||||||||
| 5.3.6.7 | Discussion Papers / Work Plan / TC lists | |||||||||||
| 5.3.7 | Enhancing LTE CA Utilization (UID - 820066) LTE_euCA-UEConTest | |||||||||||
| 5.3.7.1 | TS 36.508 | |||||||||||
| 5.3.7.2 | TS 36.521-2 | |||||||||||
| 5.3.7.3 | TS 36.521-3 | |||||||||||
| 5.3.7.4 | TR 36.903 (E-UTRAN RRM TT analyses) | |||||||||||
| 5.3.7.5 | Discussion Papers / Work Plan / TC lists | |||||||||||
| 5.3.8 | REL-16 NR CA and DC; and NR and LTE DC Configurations (UID-830083) NR_CADC_NR_LTE_DC_R16-UEConTest | |||||||||||
| 5.3.8.1 | TS 38.508-1 | R5‑202106 | Updates on FR2 inter-band EN-DC configurations for test frequencies in 38.508-1 | NTT DOCOMO INC., Ericsson | CR | Agreement | Yes |
Yesr2
| revised | No | R5‑202859 | |
| R5‑202859 | Updates on FR2 inter-band EN-DC configurations for test frequencies in 38.508-1 | NTT DOCOMO INC., Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202106 | |||
| 5.3.8.2 | TS 38.508-2 | R5‑201756 | Introduction of several new NR 2CA and 3CA combinations | WE Certification Oy, DISH Network | CR | Agreement | Yes |
YesTF160 reommended cover fix.
r1
| revised | No | R5‑202871 | |
| R5‑202871 | Introduction of several new NR 2CA and 3CA combinations | WE Certification Oy, DISH Network | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201756 | |||
| 5.3.8.3 | TS 38.521-1 | |||||||||||
| 5.3.8.3.1 | Tx Requirements (Clause 6) | R5‑202482 | Update of Spurious emission for UE co-existence for CA_n1-n78 | China Unicom | CR | Agreement | Yes |
YesR5
r1
| revised | No | R5‑202860 | |
| R5‑202860 | Update of Spurious emission for UE co-existence for CA_n1-n78 | China Unicom | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202482 | |||
| 5.3.8.3.2 | Rx Requirements (Clause 7) | R5‑201758 | Adding several new 2CA and 3CA combinations to 7.3A and corrections to 7.3A.1 | WE Certification Oy, DISH Network | CR | Agreement | Yes |
YesDISH Network disagreed.
r1
| revised | No | R5‑202781 | |
| R5‑202781 | Adding several new 2CA and 3CA combinations to 7.3A and corrections to 7.3A.1 | WE Certification Oy, DISH Network | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201758 | |||
| 5.3.8.3.3 | Clauses 1-5 / Annexes | R5‑201723 | Update Annex F.4 Uplink Power window explanation | ANRITSU LTD | CR | Agreement | No |
Yes
| withdrawn | Yes | ||
| R5‑201757 | Introduction of several new NR 2CA and 3CA combinations | WE Certification Oy, DISH Network | CR | Agreement | Yes |
Yesfully covered in R5-201934.
| withdrawn | Yes | ||||
| R5‑201934 | Update of Operating bands and Channel arrangement to TS 38.521-1 for R16 CADC configurations | China Unicom, WE Certification, DISH Network, Huawei | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| 5.3.8.4 | TS 38.521-2 | |||||||||||
| 5.3.8.4.1 | Tx Requirements (Clause 6) | |||||||||||
| 5.3.8.4.2 | Rx Requirements (Clause 7) | |||||||||||
| 5.3.8.4.3 | Clauses 1-5 / Annexes | |||||||||||
| 5.3.8.5 | TS 38.521-3 | |||||||||||
| 5.3.8.5.1 | Tx Requirements (Clause 6) | R5‑202423 | Update Tx TC for 5 Rel_16_DC_combos | QUALCOMM Europe Inc. - Italy | CR | Agreement | Yes |
Yesoverlap with R5- 201924.
r1
| revised | No | R5‑202925 | |
| R5‑202925 | Update Tx TC for 5 Rel_16_DC_combos | QUALCOMM Europe Inc. - Italy | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202423 | |||
| 5.3.8.5.2 | Rx Requirements (Clause 7) | R5‑202187 | Corrections on delta RIB due to Rel-16 EN-DC combinations in 38.521-3 | ZTE Corporation | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202966 | |
| R5‑202966 | Corrections on delta RIB due to Rel-16 EN-DC combinations in 38.521-3 | ZTE Corporation | CR | Agreement | No |
Yeswithdrawn after the meeting.
| withdrawn | Yes | R5‑202187 | |||
| R5‑202424 | Update Rx TC for 5 Rel_16_DC_combos | QUALCOMM Europe Inc. - Italy | CR | Agreement | Yes |
Yes24242
r1
| revised | No | R5‑202782 | |||
| R5‑202782 | Update Rx TC for 5 Rel_16_DC_combos | QUALCOMM Europe Inc. - Italy | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202424 | |||
| 5.3.8.5.3 | Clauses 1-5 / Annexes | R5‑201942 | Updated to EN-DC Rel-16 band information in clause 5 | Bureau Veritas, Qualcomm | CR | Agreement | Yes |
Yes
| agreed | No | ||
| 5.3.8.6 | TS 38.521-4 | |||||||||||
| 5.3.8.6.1 | Conducted Demod Performance and CSI Reporting Requirements (Clauses 5&6) | |||||||||||
| 5.3.8.6.2 | Radiated Demod Performance and CSI Reporting Requirements (Clauses 7&8) | |||||||||||
| 5.3.8.6.3 | Interworking Demod Performance and CSI Reporting Requirements (Clauses 9&10) | |||||||||||
| 5.3.8.6.4 | Clauses 1-4 / Annexes | |||||||||||
| 5.3.8.7 | TS 38.522 | |||||||||||
| 5.3.8.8 | TS 38.533 | |||||||||||
| 5.3.8.9 | TR 38.903 (NR MU & TT analyses) | |||||||||||
| 5.3.8.10 | TR 38.905 (NR Test Points Radio Transmission and Reception) | R5‑202483 | Addition of TPanalysis 6.5A.3.2.1_SECoex for CA_n1A-n78A | China Unicom | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202926 | |
| R5‑202926 | Addition of TPanalysis 6.5A.3.2.1_SECoex for CA_n1A-n78A | China Unicom | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202483 | |||
| 5.3.8.11 | Discussion Papers / Work Plan / TC lists | R5‑201917 | Discussion on how to introduce Rel-16/15 NR CADC band combinations/new bands/new BWs into TS 38.521-1/-2/-3 | CMCC, China Unicom, Huawei, Hisilicon, Bureau Veritas, Ericsson, CAICT, Qualcomm, ZTE | discussion | Endorsement | Yes |
Yes"Agenda Allocation was changed: [5.2]->[5.3.8.11].
any RAN5#87e CR's not following the guidelines
any changes needed to the proposals before endorsement
CMCC:R5-202424(Kevin@QC) has failed to follow the guidelines and the issue has been fixed in 2424r1
noted and proposals endorsed
"
| noted | No | ||
| 5.3.9 | Enhancements on Full-Dimension (FD) MIMO for LTE (UID - 830085) LTE_eFDMIMO-UEConTest | |||||||||||
| 5.3.9.1 | TS 36.508 | |||||||||||
| 5.3.9.2 | TS 36.521-1 | |||||||||||
| 5.3.9.3 | TS 36.521-2 | |||||||||||
| 5.3.9.4 | TR 36.904 (E-UTRAN Radio Reception TT analyses) | |||||||||||
| 5.3.9.5 | TR 36.905 (E-UTRAN Test Points Radio Transmission and Reception ) | |||||||||||
| 5.3.9.6 | Discussion Papers / Work Plan / TC lists | |||||||||||
| 5.3.10 | Study on 5G NR User Equipment (UE) Application Layer Data Throughput Performance (UID - 840090) FS_UE_5GNR_App_Data_Perf | |||||||||||
| 5.3.10.1 | TR 37.901-5 (pCRs only) | R5‑202053 | Text proposal to add A.8.1.1 | ROHDE & SCHWARZ | pCR | Agreement | Yes |
Yes
| approved | No | ||
| R5‑202469 | Text Proposal to update Clause 5.5 - Test Environment | Qualcomm Austria RFFE GmbH | pCR | Approval | Yes |
Yes
| approved | No | ||||
| R5‑202470 | Text Proposal to update Clause 5.9 - Test Tolerances | Qualcomm Austria RFFE GmbH | pCR | Approval | Yes |
Yes
| approved | No | ||||
| R5‑202471 | Text Proposal to update VRC based App tput sections in TR 37.901-5 | Qualcomm Austria RFFE GmbH | pCR | Approval | Yes |
Yesr1
| revised | No | R5‑202861 | |||
| R5‑202861 | Text Proposal to update VRC based App tput sections in TR 37.901-5 | Qualcomm Austria RFFE GmbH | pCR | Approval | Yes |
Yes
| approved | No | R5‑202471 | |||
| R5‑202472 | Text Proposal to update TC A.7.1.1.1 | Qualcomm Austria RFFE GmbH | pCR | Approval | Yes |
Yes
| approved | No | ||||
| R5‑202473 | Text Proposal to update TC A.9.1.1.1 | Qualcomm Austria RFFE GmbH | pCR | Approval | Yes |
Yes
| approved | No | ||||
| R5‑202474 | Text Proposal to update TC A.8.1 | Qualcomm Austria RFFE GmbH | pCR | Approval | Yes |
Yes
| approved | No | ||||
| 5.3.10.2 | Discussion Papers / Work Plan / TC lists | R5‑202465 | Discussion Paper onVRC based App Tput tests in TR 37.901-5 | Qualcomm Austria RFFE GmbH | discussion | Agreement | Yes |
Yesr1
| revised | No | R5‑202862 | |
| R5‑202862 | Discussion Paper onVRC based App Tput tests in TR 37.901-5 | Qualcomm Austria RFFE GmbH | discussion | Agreement | Yes |
Yesproposals endorsed
| noted | No | R5‑202465 | |||
| 5.3.11 | LTE Advanced high power TDD UE (power class 2) for Rel-15 (UID - 850061) LTE_TDD_HPUE_R15-UEConTest | |||||||||||
| 5.3.11.1 | TS 36.521-1 | R5‑201700 | Update of 6.2.2_1 MOP for HPUE | Huawei, HiSilicon | CR | Agreement | Yes |
Yes
| agreed | No | ||
| R5‑201701 | Update of 6.2.3_1 MPR for HPUE | Huawei, HiSilicon | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑201702 | Update of 6.2.4_1 AMPR for HPUE | Huawei, HiSilicon | CR | Agreement | No |
Yeslate doc
| withdrawn | Yes | ||||
| 5.3.11.2 | TS 36.521-2 | |||||||||||
| 5.3.11.3 | TR 36.905 (E-UTRAN Test Points Radio Transmission and Reception ) | |||||||||||
| 5.3.11.4 | Discussion Papers / Work Plan / TC lists | |||||||||||
| 5.3.12 | New Rel-16 NR bands and extension of existing NR bands (UID - 850062) NR_bands_BW_R16-UEConTest | |||||||||||
| 5.3.12.1 | TS 38.508-1 | R5‑201837 | Update of test channel bandwidths for band n48 | Rohde & Schwarz | CR | Agreement | Yes |
Yesresolve overlaps with R5-201862 and R5-202404.
"Updated to TS38.508-1 clause 1-4
R&S: R5-201837 will be withdrawn to resolve overlaps with R5-201862 and R5-202404 once modified R5-201862 will have been agreed
R&S: overlap part already removed in 1862r2, would like to maintain this CR and not withdraw, even in case R5-201862r2 gets agreed. no overlap with 2404"
| agreed | No | ||
| R5‑201862 | Update of default test channel BW | Huawei, HiSilicon, Rohde & Schwaz, China Unicom, CAICT | CR | Agreement | Yes |
Yesr1
DISH: It is not true that “UE always only supports part of channels BWs that 38.101 defines” however, it’s true that Rel-16 CH BWs (new) are not mandatory in RAN4 and therefore, identifying what CH BWs the UE supports for testing is problematic. Future proof applicability handling per TC (especially for RF) should be considered.
Further, r1 is not acceptable as the mathematical equation brings back undesired mid CH BWs for certain bands as discussed when the tables were created.
r4
| revised | No | R5‑202956 | |||
| R5‑202956 | Update of default test channel BW | Huawei, HiSilicon, China Unicom, CAICT | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201862 | |||
| R5‑202186 | Addition of locationAndBandwidth in BWP for FR1 in 38.508-1 | ZTE Corporation | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑202404 | Addition of R16 new channel bandwidths for n1 in 38.508-1 | China Unicom, Ericsson | CR | Agreement | Yes |
Yesr1
presented in the midweek joint.
related to R5-201961.
| revised | No | R5‑202531 | |||
| R5‑202531 | Addition of R16 new channel bandwidths for n1 in 38.508-1 | China Unicom, Ericsson | CR | Agreement | Yes |
Yesto be implemented after R5-201961.
| agreed | No | R5‑202404 | |||
| 5.3.12.2 | TS 38.508-2 | |||||||||||
| 5.3.12.3 | TS 38.521-1 | |||||||||||
| 5.3.12.3.1 | Tx Requirements (Clause 6) | R5‑201764 | Adding NS_27 A_MPR and Emission Requirements for band n48 | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||
| R5‑201772 | Adding NS_47 A_MPR and Emission Requirements for band n41 | Ericsson, SoftBank Corp. | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| 5.3.12.3.2 | Rx Requirements (Clause 7) | R5‑201861 | Addition of asymmetric BW combination set 1 of n66 | Huawei, HiSilicon, Dish | CR | Agreement | Yes |
Yes
| agreed | No | ||
| R5‑202012 | Adding REFSENS requirements for 30 MHz channel bandwidth in band n41 | Ericsson, SoftBank Corp. | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202783 | |||
| R5‑202783 | Adding REFSENS requirements for 30 MHz channel bandwidth in band n41 | Ericsson, SoftBank Corp. | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202012 | |||
| R5‑202013 | Adding receiver requirements for band n48 | Ericsson | CR | Agreement | Yes |
Yesoverlap with R5-202430 (Qualcomm).
| withdrawn | Yes | ||||
| R5‑202430 | Add Reference sensitivity requirement for n48 | QUALCOMM Europe Inc. - Italy | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑202484 | Update of Reference sensitivity power level for R16 new CBW of n1 | China Unicom | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| 5.3.12.3.3 | Clauses 1-5 / Annexes | R5‑201933 | Update of Operating bands and Channel arrangement to TS 38.521-1 for R16 new bands and CBWs | China Unicom, Huawei, Hisilicon, Dish | CR | Agreement | Yes |
Yesr2
| revised | No | R5‑202927 | |
| R5‑202927 | Update of Operating bands and Channel arrangement to TS 38.521-1 for R16 new bands and CBWs | China Unicom, Huawei, Hisilicon, Dish | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201933 | |||
| 5.3.12.4 | TS 38.521-2 | |||||||||||
| 5.3.12.4.1 | Tx Requirements (Clause 6) | |||||||||||
| 5.3.12.4.2 | Rx Requirements (Clause 7) | |||||||||||
| 5.3.12.4.3 | Clauses 1-5 / Annexes | |||||||||||
| 5.3.12.5 | TS 38.521-4 | |||||||||||
| 5.3.12.5.1 | Conducted Demod Performance and CSI Reporting Requirements (Clauses 5&6) | |||||||||||
| 5.3.12.5.2 | Radiated Demod Performance and CSI Reporting Requirements (Clauses 7&8) | |||||||||||
| 5.3.12.5.3 | Interworking Demod Performance and CSI Reporting Requirements (Clauses 9&10) | |||||||||||
| 5.3.12.5.4 | Clauses 1-4 / Annexes | |||||||||||
| 5.3.12.6 | TS 38.533 | |||||||||||
| 5.3.12.7 | TS 37.571-1 | |||||||||||
| 5.3.12.8 | TR 38.903 ((NR MU & TT analyses) | |||||||||||
| 5.3.12.9 | TR 38.905 (NR Test Points Radio Transmission and Reception) | R5‑201765 | Test points analysis for NS_27 A_MPR FR1 test case | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||
| R5‑201773 | Test points analysis for NS_47 A_MPR FR1 test case | Ericsson, SoftBank Corp. | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| 5.3.12.10 | Discussion Papers / Work Plan / TC lists | |||||||||||
| 5.3.13 | Addition of Power Class 2 UE for LTE bands 31 and 72 (UID – 860030) LTE_PC2_B31_B72-UEConTest | |||||||||||
| 5.3.13.1 | TS 36.521-1 | |||||||||||
| 5.3.13.2 | TS 36.521-2 | |||||||||||
| 5.3.13.3 | Discussion Papers / Work Plan / TC lists | |||||||||||
| 5.3.14 | Further NB-IoT enhancements (UID – 860031) NB_IOTenh2-UEConTest | |||||||||||
| 5.3.14.1 | TS 36.508 | R5‑202196 | Addition of NB-IoT test frequencies of TDD band 41 | Huawei, HiSilicon | CR | Agreement | Yes |
YesAdditon
r1
| revised | No | R5‑202784 | |
| R5‑202784 | Addition of NB-IoT test frequencies of TDD band 41 | Huawei, HiSilicon | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202196 | |||
| 5.3.14.2 | TS 36.521-1 | R5‑201514 | Adding test band for UE Maximum Output Power for category NB1 and NB2 | Sporton International Inc. | CR | Agreement | Yes |
Yesrev #
r2
| revised | No | R5‑202863 | |
| R5‑202863 | Adding test band for UE Maximum Output Power for category NB1 and NB2 | Sporton International Inc. | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201514 | |||
| R5‑201515 | Adding test band for UE Maximum Output Power for category NB1 and NB2 Power Class 6 | Sporton International Inc. | CR | Agreement | Yes |
Yesrev #
r2
| revised | No | R5‑202864 | |||
| R5‑202864 | Adding test band for UE Maximum Output Power for category NB1 and NB2 Power Class 6 | Sporton International Inc. | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201515 | |||
| R5‑201516 | Adding test band for Reference sensitivity level without repetitions for category NB1 and NB2 | Sporton International Inc. | CR | Agreement | Yes |
Yesrev #
r2
| revised | No | R5‑202865 | |||
| R5‑202865 | Adding test band for Reference sensitivity level without repetitions for category NB1 and NB2 | Sporton International Inc. | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201516 | |||
| R5‑201517 | Adding test band for Out-of-band blocking for category NB1 and NB2 | Sporton International Inc. | CR | Agreement | Yes |
Yesrev #
r2
| revised | No | R5‑202866 | |||
| R5‑202866 | Adding test band for Out-of-band blocking for category NB1 and NB2 | Sporton International Inc. | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201517 | |||
| R5‑201518 | Update for each NB1 and NB2 test cases in Annex F | Sporton International Inc. | CR | Agreement | Yes |
Yesrev #
r1
| revised | No | R5‑202785 | |||
| R5‑202785 | Update for each NB1 and NB2 test cases in Annex F | Sporton International Inc. | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201518 | |||
| R5‑201717 | Adding test band for ON OFF time mask for category NB1 and NB2 | Sporton International Inc | CR | Agreement | Yes |
Yesrev #
r2
| revised | No | R5‑202867 | |||
| R5‑202867 | Adding test band for ON OFF time mask for category NB1 and NB2 | Sporton International Inc | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201717 | |||
| R5‑201788 | Updated to clause 5 information for Rel-15 NB-IoT | Bureau Veritas | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑202197 | Cleaning up NB-IOT Tx test cases to allow testing on TDD bands | Huawei, HiSilicon | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202786 | |||
| R5‑202786 | Cleaning up NB-IOT Tx test cases to allow testing on TDD bands | Huawei, HiSilicon | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202197 | |||
| R5‑202198 | Addition of RMC for TDD NB-IOT testing | Huawei, HiSilicon | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| 5.3.14.3 | TS 36.521-2 | R5‑202161 | Adding test applicability for Rel-15 NB1 and NB2 Test Cases | Sporton International Inc., Huawei, HiSilicon | CR | Agreement | Yes |
Yes"Spec # inconsistency, CR revision inconsistency
-3GU: 36.521-2 / CR coversheet: 36.521-1
-3GU: / CR coversheet:
| revised | No | R5‑202868 | |
| R5‑202868 | Adding test applicability for Rel-15 NB1 and NB2 Test Cases | Sporton International Inc., Huawei, HiSilicon | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202161 | |||
| 5.3.14.4 | TS 36.521-3 | R5‑201789 | Updated to Annexes for Rel-15 NB-IoT test configuration | Bureau Veritas | CR | Agreement | Yes |
Yes
| agreed | No | ||
| R5‑202192 | Addition of 4.2.35 NB-IOT TDD-TDD Intra frequency cell reselection in normal coverage | Huawei, HiSilicon | CR | Agreement | Yes |
YesAdditon
r1
| revised | No | R5‑202787 | |||
| R5‑202787 | Addition of 4.2.35 NB-IOT TDD-TDD Intra frequency cell reselection in normal coverage | Huawei, HiSilicon | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202192 | |||
| R5‑202193 | Addition of 4.2.36 NB-IOT TDD-TDD Intra frequency cell reselection in enhanced coverage | Huawei, HiSilicon | CR | Agreement | Yes |
YesAdditon
r1
| revised | No | R5‑202788 | |||
| R5‑202788 | Addition of 4.2.36 NB-IOT TDD-TDD Intra frequency cell reselection in enhanced coverage | Huawei, HiSilicon | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202193 | |||
| R5‑202194 | Addition of 4.2.37 NB-IOT TDD-TDD Inter frequency cell reselection in normal coverage | Huawei, HiSilicon | CR | Agreement | Yes |
Yesreissued as R5-202500 because of title change
| withdrawn | Yes | ||||
| R5‑202500 | Addition of 4.2.37 NB-IOT TDD-TDD Inter frequency cell reselection in enhanced coverage | Huawei, HiSilicon | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202790 | |||
| R5‑202790 | Addition of 4.2.37 NB-IOT TDD-TDD Inter frequency cell reselection in enhanced coverage | Huawei, HiSilicon | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202500 | |||
| R5‑202195 | Addition of 4.2.38 NB-IOT HD-FDD Intra frequency cell reselection in normal coverage with RRM measurement relaxation | Huawei, HiSilicon | CR | Agreement | Yes |
YesAdditon
r1
| revised | No | R5‑202789 | |||
| R5‑202789 | Addition of 4.2.38 NB-IOT HD-FDD Intra frequency cell reselection in normal coverage with RRM measurement relaxation | Huawei, HiSilicon | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202195 | |||
| 5.3.14.5 | TS 37.571-1 | |||||||||||
| 5.3.14.6 | TS 37.571-3 | |||||||||||
| 5.3.14.7 | TS 37.571-5 | |||||||||||
| 5.3.14.8 | TR 36.903 (E-UTRAN RRM TT analyses) | |||||||||||
| 5.3.14.9 | TR 36.904 (E-UTRAN Radio Reception TT analyses) | |||||||||||
| 5.3.14.10 | TR 36.905 (E-UTRAN Test Points Radio Transmission and Reception ) | |||||||||||
| 5.3.14.11 | Discussion Papers / Work Plan / TC lists | |||||||||||
| 5.3.15 | Even further enhanced MTC for LTE (UID – 860032) LTE_eMTC4-UEConTest | |||||||||||
| 5.3.15.1 | TS 36.508 | |||||||||||
| 5.3.15.2 | TS 36.521-1 | R5‑201950 | New RMCs for efeMTC | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||
| R5‑202324 | efeMTC updates in test case 8.11.1.1.3.1 | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| 5.3.15.3 | TS 36.521-2 | |||||||||||
| 5.3.15.4 | TS 36.521-3 | |||||||||||
| 5.3.15.5 | TS 37.571-1 | |||||||||||
| 5.3.15.6 | TS 37.571-3 | |||||||||||
| 5.3.15.7 | TS 37.571-5 | |||||||||||
| 5.3.15.8 | TR 36.903 (E-UTRAN RRM TT analyses) | |||||||||||
| 5.3.15.9 | TR 36.904 (E-UTRAN Radio Reception TT analyses) | |||||||||||
| 5.3.15.10 | TR 36.905 (E-UTRAN Test Points Radio Transmission and Reception ) | |||||||||||
| 5.3.15.11 | Discussion Papers / Work Plan / TC lists | |||||||||||
| 5.3.16 | RF requirements for NR frequency range 1 (FR1) (UID-870061) NR_RF_FR1-UEConTest | |||||||||||
| 5.3.16.1 | TS 38.508-1 | |||||||||||
| 5.3.16.2 | TS 38.508-2 | |||||||||||
| 5.3.16.3 | TS 38.521-1 | |||||||||||
| 5.3.16.3.1 | Tx Requirements (Clause 6) | R5‑201748 | Update of NR test case 6.2.2 UE maximum output power reduction | Huawei,Hisilicon | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202957 | |
| R5‑202957 | Update of NR test case 6.2.2 UE maximum output power reduction | Huawei,Hisilicon | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201748 | |||
| 5.3.16.3.2 | Rx Requirements (Clause 7) | R5‑201749 | Update of NR test case 7.4A.1 Maximum input level for 2DL CA | Huawei,Hisilicon | CR | Agreement | Yes |
Yes
| agreed | No | ||
| R5‑201750 | Addition of NR test case 7.4A.2 Maximum input level for 3DL CA | Huawei,Hisilicon | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑201751 | Update for NR test case 7.6A.2.1 Inband Blocking for 2DL CA | Huawei,Hisilicon | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202928 | |||
| R5‑202928 | Update for NR test case 7.6A.2.1 Inband Blocking for 2DL CA | Huawei,Hisilicon | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201751 | |||
| R5‑201752 | Addition of NR test case 7.6A.2.2 IBB for 3DL CA | Huawei,Hisilicon | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑201838 | Update of general clause 7.1 | Rohde & Schwarz | CR | Agreement | Yes |
YesHuawei: wrong WIC and AI.
r1
| revised | No | R5‑202791 | |||
| R5‑202791 | Update of general clause 7.1 | Rohde & Schwarz | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201838 | |||
| R5‑202034 | Addition of new test case 7.6A.3.2 Out-of-band blocking for CA 3DL CA R16 | CAICT | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑202035 | Addition of new test case 7.6A.3.3 Out-of-band blocking for CA 4DL CA R16 | CAICT | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑202036 | Addition of new test case 7.6A.4.2 Narrow band blocking for CA 3DL CA R16 | CAICT | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑202037 | Addition of new test case 7.6A.4.3 Narrow band blocking for CA 4DL CA R16 | CAICT | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑202038 | Addition of new test case 7.8A.2.2 Wide band Intermodulation for CA 3DL CA R16 | CAICT | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202929 | |||
| R5‑202929 | Addition of new test case 7.8A.2.2 Wide band Intermodulation for CA 3DL CA R16 | CAICT | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202038 | |||
| R5‑202039 | Addition of new test case 7.8A.2.3 Wide band Intermodulation for CA 4DL CA R16 | CAICT | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑202040 | Correction of CW interference setting for OOBB Inter-band 2DL CA in TC 7.6A.3.1 R16 | CAICT | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202930 | |||
| R5‑202930 | Correction of CW interference setting for OOBB Inter-band 2DL CA in TC 7.6A.3.1 R16 | CAICT | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202040 | |||
| R5‑202041 | Correction of test procedure and some typos in 7.6A.4.1 Narrow band blocking for CA 2DL CA R16 | CAICT | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑202042 | Correction of test procedure and test requirement in 7.8A.2.1 R16 | CAICT | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑202043 | Alignment of minimum conformance requirements in 7.6A.3.0 and 7.8A.2.0 with core spec R16 | CAICT | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202931 | |||
| R5‑202931 | Alignment of minimum conformance requirements in 7.6A.3.0 and 7.8A.2.0 with core spec R16 | CAICT | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202043 | |||
| 5.3.16.3.3 | Clauses 1-5 / Annexes | |||||||||||
| 5.3.16.4 | TS 38.521-3 | |||||||||||
| 5.3.16.4.1 | Tx Requirements (Clause 6) | |||||||||||
| 5.3.16.4.2 | Rx Requirements (Clause 7) | |||||||||||
| 5.3.16.4.3 | Clauses 1-5 / Annexes | |||||||||||
| 5.3.16.5 | TS 38.522 | |||||||||||
| 5.3.16.6 | TS 38.533 | |||||||||||
| 5.3.16.7 | TR 38.903 (NR MU & TT analyses) | |||||||||||
| 5.3.16.8 | TR 38.905 (NR Test Points Radio Transmission and Reception) | R5‑201753 | Addition of TP analysis for FR1 Maximum input level for 3DL CA | Huawei,Hisilicon | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202932 | |
| R5‑202932 | Addition of TP analysis for FR1 Maximum input level for 3DL CA | Huawei,Hisilicon | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201753 | |||
| R5‑201754 | Addition of TP analysis for FR1 In-band blocking for 3DL CA | Huawei,Hisilicon | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202933 | |||
| R5‑202933 | Addition of TP analysis for FR1 In-band blocking for 3DL CA | Huawei,Hisilicon | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201754 | |||
| 5.3.16.9 | TS 36.521-3 | |||||||||||
| 5.3.16.10 | TR 36.903 (E-UTRAN RRM TT analyses) | |||||||||||
| 5.3.16.11 | Discussion Papers / Work Plan / TC lists | |||||||||||
| 5.3.17 | High power UE (power class 2) for EN-DC (1 LTE TDD band + 1 NR TDD band) (UID-870062) ENDC_UE_PC2_TDD_TDD-UEConTest | |||||||||||
| 5.3.17.1 | TS 38.508-1 | |||||||||||
| 5.3.17.2 | TS 38.508-2 | R5‑201923 | Addition of TDD-TDD PC2 inter-band EN-DC UE RF Baseline implementation Capabilities declaration | CMCC | CR | Agreement | Yes |
Yes"CMCC: R5-201923 has no dependence on UL MIMO or PC2 discussion. 202374/202434 relate to the ambiguty of R15 PC2 UE definition in RAN4. However, R5-201923 is the addition of R16 TDD-TDD PC2 inter-band EN-DC UE capability declaration into 38.508-2. Different releases and no matter what the discussion conclusion could be, the TDD-TDD PC2 UE capability still can be added into 38.508-2
"
| agreed | No | ||
| 5.3.17.3 | TS 38.521-3 | |||||||||||
| 5.3.17.3.1 | Tx Requirements (Clause 6) | R5‑201924 | Addition of TDD-TDD PC2 inter-band EN-DC | CMCC | CR | Agreement | Yes |
Yesoverlap with R5- 202423.
r1
| revised | No | R5‑202934 | |
| R5‑202934 | Addition of TDD-TDD PC2 inter-band EN-DC | CMCC | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201924 | |||
| 5.3.17.3.2 | Rx Requirements (Clause 7) | |||||||||||
| 5.3.17.3.3 | Clauses 1-5 / Annexes | |||||||||||
| 5.3.17.4 | TS 38.522 | R5‑201925 | R16 TDD ENDC PC2 TP for TS 38.522 | CMCC | CR | Agreement | Yes |
Yesr2
| revised | No | R5‑202958 | |
| R5‑202958 | R16 TDD ENDC PC2 TP for TS 38.522 | CMCC | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201925 | |||
| 5.3.17.5 | TR 38.905 (NR Test Points Radio Transmission and Reception) | |||||||||||
| 5.3.17.6 | Discussion Papers / Work Plan / TC lists | |||||||||||
| 5.4 | Routine Maintenance for LTE only TEIx_Test | |||||||||||
| 5.4.1 | LTE RF | |||||||||||
| 5.4.1.1 | TS 36.508 | R5‑201612 | Addition of NB-IOT test frequencies for band 73 | ROHDE & SCHWARZ | CR | Agreement | Yes |
Yes"Spec # inconsistency
-3GU: 36.508 / CR coversheet: 36.521-3"
r2
| revised | No | R5‑202792 | |
| R5‑202792 | Addition of NB-IOT test frequencies for band 73 | ROHDE & SCHWARZ | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201612 | |||
| R5‑201613 | Correction LTE EARFCNs for band 73 | ROHDE & SCHWARZ | CR | Agreement | Yes |
Yes"Spec # inconsistency
-3GU: 36.508 / CR coversheet: 36.521-3".
covered by R5-202441.
| withdrawn | Yes | ||||
| R5‑202441 | Correction of Test Frequencies for Band 73 | ROHDE & SCHWARZ | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| 5.4.1.2 | TS 36.521-1 | R5‑201927 | Addition of B40 into UE Category 1bis and Addition of Power Class 2 into B41 UE Category 1bis | CMCC | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202935 | |
| R5‑202935 | Addition of B40 into UE Category 1bis and Addition of Power Class 2 into B41 UE Category 1bis | CMCC | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201927 | |||
| 5.4.1.2.1 | Tx Requirements (Clause 6) | R5‑201784 | Correction to test applicability of NB-IoT tests | Bureau Veritas Huawei, HiSilicon | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202793 | |
| R5‑202793 | Correction to test applicability of NB-IoT tests | Bureau Veritas Huawei, HiSilicon | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201784 | |||
| R5‑201832 | Update to NS_05 Requirements | Rohde & Schwarz | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202794 | |||
| R5‑202794 | Update to NS_05 Requirements | Rohde & Schwarz | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201832 | |||
| R5‑202189 | Adding NB-IOT ACLR for PC6 | Huawei, HiSilicon, Bureau Veritas | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202795 | |||
| R5‑202795 | Adding NB-IOT ACLR for PC6 | Huawei, HiSilicon, Bureau Veritas | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202189 | |||
| R5‑202191 | Updated to NB-IOT TC 6.2.3FA | Huawei, HiSilicon, Bureau Veritas | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202796 | |||
| R5‑202796 | Updated to NB-IOT TC 6.2.3FA | Huawei, HiSilicon, Bureau Veritas | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202191 | |||
| R5‑202282 | Editorial correction to spurious emission UE-coexistence tests for Cat-M1 | Anritsu | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑202283 | Editorial correction to spurious emission UE-coexistence tests for UL CA | Anritsu | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| 5.4.1.2.2 | Rx Requirements (Clause 7) | R5‑201831 | Update of inband blocking requirements | Rohde & Schwarz | CR | Agreement | Yes |
Yes
| agreed | No | ||
| R5‑201868 | Moving test case 7.6.1EA In-band blocking for UE category M1 to correct place | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑201928 | Cleanup in category M2 test cases | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑202047 | Skipping 2Rx REFSENS testing on bands where UE support 4Rx | CAICT | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑202280 | Cleaning up DL CA Rx Test Cases | Anritsu | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑202281 | Correction to reference sensitivity CA_38A-40A-40A | Anritsu | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑202442 | Corrections to Reference Sensitivity for CA | ROHDE & SCHWARZ | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑202445 | Editorial corrections to Reference Sensitivity for CA | ROHDE & SCHWARZ | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| 5.4.1.2.3 | Clauses 1-5 / 8-10 / Annexes | R5‑201728 | Correction to TC 9.2.1.7 and 9.2.1.8 for minimum requirements | Huawei, HiSilicon | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202869 | |
| R5‑202869 | Correction to TC 9.2.1.7 and 9.2.1.8 for minimum requirements | Huawei, HiSilicon | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201728 | |||
| R5‑201729 | Addition of performance TC 8.2.1.10 intra-band contiguous CA with minimum channel spacing | Huawei, HiSilicon | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202870 | |||
| R5‑202870 | Addition of performance TC 8.2.1.10 intra-band contiguous CA with minimum channel spacing | Huawei, HiSilicon | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201729 | |||
| R5‑201730 | Update of Tolerance for 8.2.1.10 in Annex F | Huawei, HiSilicon | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| 5.4.1.3 | TS 36.521-2 | R5‑201512 | Addition of TS36.521-2 CA Band 5A-29A and 2A-5A-29A | Sporton International Inc. | CR | Agreement | Yes |
YesTEI-
r1
| revised | No | R5‑202936 | |
| R5‑202936 | Addition of TS36.521-2 CA Band 5A-29A and 2A-5A-29A | Sporton International Inc. | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201512 | |||
| R5‑201705 | Correction to tables of UE categories in TS36.521-2 | Tejet | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑201710 | Update to tables of UE Power Class implementation Capabilities | Tejet | CR | Agreement | Yes |
Yesmerged into R5-201785r1
| withdrawn | Yes | ||||
| R5‑201785 | Correction to applicability table of NB-IoT tests | Bureau Veritas Huawei, HiSilicon, Sporton, Tejet | CR | Agreement | Yes |
Yesr1
TEI13!!
merged conflicted content from R5-202161 and R5-201710.
r2
| revised | No | R5‑202797 | |||
| R5‑202797 | Correction to applicability table of NB-IoT tests | Bureau Veritas Huawei, HiSilicon, Sporton, Tejet | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201785 | |||
| R5‑201926 | Correction of UE Category 1bis test case applicability | CMCC | CR | Agreement | Yes |
Yesr3
| revised | No | R5‑202937 | |||
| R5‑202937 | Correction of UE Category 1bis test case applicability | CMCC | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201926 | |||
| R5‑202162 | Update additional information for test applicability for skipping 2RX Test cases | Sporton International Inc. | CR | Agreement | Yes |
Yes"CR revision inconsistency
-3GU: / CR coversheet:
| revised | No | R5‑202798 | |||
| R5‑202798 | Update additional information for test applicability for skipping 2RX Test cases | Sporton International Inc. | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202162 | |||
| R5‑202190 | Adding test applicability of NB-IOT ACLR for PC6 | Huawei, HiSilicon, Bureau Veritas | CR | Agreement | Yes |
Yes"TC in R5-202189
Author requested to withdrawn, content merged into 2161r2"
| withdrawn | Yes | ||||
| R5‑202232 | Addition of UE applicability for TC 8.2.1.10 in 36.521-2 | Huawei, HiSilicon | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑202444 | Correction of the CA configuration exception for CA_3A-7B | ROHDE & SCHWARZ | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| 5.4.1.4 | TS 36.521-3 | R5‑201607 | Correction 4.2.18 PCID selection | ROHDE & SCHWARZ | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202799 | |
| R5‑202799 | Correction 4.2.18 PCID selection | ROHDE & SCHWARZ | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201607 | |||
| R5‑201608 | Correction SIB5-NB 4.2.24 | ROHDE & SCHWARZ | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑201609 | Correction RSRP-Threshold TC 6.2.16 | ROHDE & SCHWARZ | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑201610 | Align eMTC RLM test cases to core spec | ROHDE & SCHWARZ | CR | Agreement | Yes |
Yesr2
R4-2007424 was revised and agreed as R4-2008656.
| revised | No | R5‑202994 | |||
| R5‑202994 | Align eMTC RLM test cases to core spec | ROHDE & SCHWARZ | CR | Agreement | Yes |
Yeswas agreed after the meeting.
| agreed | No | R5‑201610 | |||
| R5‑201611 | Correctly add evaluation limits 9.1.1.2_2 | ROHDE & SCHWARZ | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑202086 | Editiorial correction of clause 8.7A title | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑202087 | Test Tolerances for RRM feMTC Test Cases in Annex F | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑202088 | Correction of RRM feMTC Test Cases 8.3.12 to 8.3.19 with TT | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑202254 | Correction of message contents to e-MTC Intra-frequency Handover | Qualcomm Technologies Int | CR | Agreement | Yes |
YesR5
r1
| revised | No | R5‑202800 | |||
| R5‑202800 | Correction of message contents to e-MTC Intra-frequency Handover | Qualcomm Technologies Int | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202254 | |||
| R5‑202378 | Alignment of In-band NB-1 cell reselection test case | Qualcomm Technologies Int | CR | Agreement | No |
Yeslate doc
| withdrawn | Yes | ||||
| 5.4.1.5 | RRM Test & Radio Reception Test Tolerances | |||||||||||
| 5.4.1.5.1 | TR 36.903 (E-UTRAN RRM TT analyses) | R5‑202089 | Test Tolerance analysis for E-UTRAN FDD inter-frequency event triggered reporting in CEModeA test cases | Ericsson | CR | Agreement | Yes |
Yes'+' in Word name
r1
| revised | No | R5‑202801 | |
| R5‑202801 | Test Tolerance analysis for E-UTRAN FDD inter-frequency event triggered reporting in CEModeA test cases | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202089 | |||
| R5‑202090 | Test Tolerance analysis for E-UTRAN FDD inter-frequency event triggered reporting in CEModeB test cases | Ericsson | CR | Agreement | Yes |
Yes'+' in Word name
r1
| revised | No | R5‑202802 | |||
| R5‑202802 | Test Tolerance analysis for E-UTRAN FDD inter-frequency event triggered reporting in CEModeB test cases | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202090 | |||
| 5.4.1.5.2 | TR 36.904 (E-UTRAN Radio Reception TT analyses) | |||||||||||
| 5.4.1.5.3 | TR 36.905 (E-UTRAN Test Points Radio Transmission and Reception ) | R5‑202443 | Update of Test Point Analysis for CA_3A-7B | ROHDE & SCHWARZ | CR | Agreement | Yes |
Yes
| agreed | No | ||
| 5.4.1.6 | TS 34.121-1 | |||||||||||
| 5.4.1.7 | TS 34.121-2 | |||||||||||
| 5.4.1.8 | TS 34.122 | |||||||||||
| 5.4.1.9 | TS 34.108 | |||||||||||
| 5.4.1.10 | TR 34.902 (UTRAN RRM Test Tolerance analyses) | |||||||||||
| 5.4.1.11 | Discussion Papers / Work Plan / TC lists | |||||||||||
| 5.5 | Other Routine Maintenance TEIx_Test | |||||||||||
| 5.5.1 | TS 34.108 | |||||||||||
| 5.5.2 | TS 34.121-1 All sections other than annexes | |||||||||||
| 5.5.3 | TS 34.121-1 Annexes only | |||||||||||
| 5.5.4 | TS 34.121-2 | |||||||||||
| 5.5.5 | TS 34.122 | |||||||||||
| 5.5.6 | TS 34.171 | |||||||||||
| 5.5.7 | TS 34.172 | |||||||||||
| 5.5.8 | TS 34.114 | |||||||||||
| 5.5.9 | TS 37.571-1 | R5‑201325 | 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 | Yes |
Yes"Clauses affected missing
Source to TSG (R5) missing"
r1
| revised | No | R5‑202803 | |
| R5‑202803 | 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 | Yes |
Yes
| agreed | No | R5‑201325 | |||
| 5.5.10 | TS 37.571-3 | |||||||||||
| 5.5.11 | TS 37.571-5 | |||||||||||
| 5.5.12 | TS 51.010-1 (RF/Performance) | |||||||||||
| 5.5.13 | TS 51.010-2 (RF/Performance) | |||||||||||
| 5.5.14 | TS 51.010-7 (RF/Performance) | |||||||||||
| 5.5.15 | TS 37.544 | |||||||||||
| 5.5.16 | Discussion Papers / Work Plan / TC lists | |||||||||||
| 5.6 | Outgoing liaison statements for provisional approval | R5‑202804 | LS on structure of NR CA reference sensitivity requirements in 38.101-1 | TSG WG RAN5 | LS out | Approval | Yes |
Yesr1
| revised | No | R5‑202963 | |
| R5‑202963 | LS on structure of NR CA reference sensitivity requirements in 38.101-1 | TSG WG RAN5 | LS out | Approval | Yes |
Yes
| approved | No | R5‑202804 | |||
| R5‑202806 | LS on RF testing of 4Rx capable UE | TSG WG RAN5 | LS out | Approval | Yes |
Yes
| approved | No | ||||
| R5‑202805 | LS on ambiguity in output power requirements for power class 2 UE for EN-DC | TSG WG RAN5 | LS out | Approval | Yes |
Yesdraft v4 was presented.
| approved | No | ||||
| 5.7 | AOB | |||||||||||
| 6 | Signalling Protocol Functional Area | |||||||||||
| 6.1 | Review action points (fm A.I. 2.1) | |||||||||||
| 6.2 | Review incoming LS (fm A.I. 3) & new subject discussion papers | R5‑202498 | LS on suitability of validation transfers across 5G FR1 and FR2 and vice versa | PTCRB PVG | LS in | Information | Yes |
Yesmoved to SIG.
RAN5 cannot provide guidance on validation but can share information on rules applied in verification. Response LS to be drafted by Qualcomm with support from TF160 PM.
| noted | No | ||
| 6.3 | Open Work Items | |||||||||||
| 6.3.1 | Rel-14 LTE CA configurations (UID - 720098) LTE_CA_R14-UEConTest | |||||||||||
| 6.3.1.1 | TS 36.508 | |||||||||||
| 6.3.1.2 | TS 36.523-1 | |||||||||||
| 6.3.1.3 | TS 36.523-2 | R5‑201480 | Addition of CA_48C and CA_48D to 36.523-2 proforma Table A.4.3.3.1-3 | C Spire Wireless | CR | Agreement | Yes |
Yesno cl. aff.
r1
| revised | No | R5‑202559 | |
| R5‑202559 | Addition of CA_48C and CA_48D to 36.523-2 proforma Table A.4.3.3.1-3 | C Spire Wireless | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201480 | |||
| R5‑201697 | Addition of Rel-14 capabilities of multiple CA in 36.523-2 | Huawei, HiSilicon | CR | Agreement | Yes |
YesRel14
r1
| revised | No | R5‑202560 | |||
| R5‑202560 | Addition of Rel-14 capabilities of multiple CA in 36.523-2 | Huawei, HiSilicon | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201697 | |||
| 6.3.1.4 | TS 36.523-3 | |||||||||||
| 6.3.1.5 | Discussion Papers / Work Plan / TC lists | |||||||||||
| 6.3.2 | 5G system with NR and LTE (UID - 760087) 5GS_NR_LTE-UEConTest | |||||||||||
| 6.3.2.1 | TS 38.508-1 | R5‑201320 | Update IE CellGroupConfig | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||
| R5‑201321 | Update IE default content for control resource set establishment and common search space mapping | Ericsson | CR | Agreement | Yes |
Yesr1
Merged with R5-201571.
| revised | No | R5‑202561 | |||
| R5‑202561 | Update IE default content for control resource set establishment and common search space mapping | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201321 | |||
| R5‑201322 | Update of default value of frequencyDomainResources in ControlResourceSet IE | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑201331 | Correction to Table 4.9.6.1-1-Switch off in Idle | Huawei, Hisilicon | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑201332 | Update to 4.9.6.3 Switch off Power off procedure in RRC_CONNECTED | Huawei, Hisilicon, Rohde & Schwarz, TF 160, Qualcomm, Keysight | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202562 | |||
| R5‑202562 | Update to 4.9.6.3 Switch off Power off procedure in RRC_CONNECTED | Huawei, Hisilicon, Rohde & Schwarz, TF 160, Qualcomm, Keysight | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201332 | |||
| R5‑201333 | Addition of 4.9.6.3A Switch off Power off procedure in RRC_CONNECTED with T3540 started | Huawei, Hisilicon, Rohde & Schwarz, TF 160, Qualcomm, Keysight, | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑201334 | Correction to Table 4.9.7.2.3-1-Tracking Area Update Request | Huawei, HiSilicon, Datang Linktester, Keysight Technologies UK Ltd | CR | Agreement | Yes |
Yesr2
| revised | No | R5‑202563 | |||
| R5‑202563 | Correction to Table 4.9.7.2.3-1-Tracking Area Update Request | Huawei, HiSilicon, Datang Linktester, Keysight Technologies UK Ltd | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201334 | |||
| R5‑201335 | Update to USIM config 6.4.1-1 | Huawei, Hisilicon | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑201336 | Update to USIM Table 6.4.1-10 | Huawei, Hisilicon | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑201446 | Fixing wrong reference for RRC_CONNECTED state on WLAN access | ROHDE & SCHWARZ | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑201470 | Correction to Table 4.5.2.2-2-Adding second SMC procedure for Selected EPS NAS security algorithms IE | Huawei, Hisilicon | CR | Agreement | Yes |
Yesr2
| revised | No | R5‑202564 | |||
| R5‑202564 | Correction to Table 4.5.2.2-2-Adding second SMC procedure for Selected EPS NAS security algorithms IE | Huawei, Hisilicon | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201470 | |||
| R5‑201479 | Clarification to ROUND for negative Threshold values in SIB1 and SIB4 | Anritsu Ltd, Keysight Technologies UK | CR | Agreement | No |
Yes
| withdrawn | Yes | ||||
| R5‑201482 | Clarification to ROUND for negative Threshold values in SIB1 and SIB4 | Anritsu Ltd, Keysight Technologies UK | CR | Agreement | Yes |
YesCR coversheet: 38.523-1, 16.3.0.
r1
| revised | No | R5‑202565 | |||
| R5‑202565 | Clarification to ROUND for negative Threshold values in SIB1 and SIB4 | Anritsu Ltd, Keysight Technologies UK | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201482 | |||
| R5‑201483 | Correction to NR RRC_IDLE procedure in case of r pc_noOf_PDUsNewConnection > 0 | ANRITSU LTD | CR | Agreement | Yes |
YesproseCR is not needed for associated TTCN CR.
| withdrawn | Yes | ||||
| R5‑201487 | Adding generic procedure E-UTRA RRC_IDLE with unrestricted number of PDN connections | Samsung | CR | Agreement | Yes |
Yesr2
| revised | No | R5‑202566 | |||
| R5‑202566 | Adding generic procedure E-UTRA RRC_IDLE with unrestricted number of PDN connections | Samsung | CR | Agreement | Yes |
YesThe CR was technically endorsed (see discussion on R5-201486)
| not pursued | No | R5‑201487 | |||
| R5‑201488 | Adding procedure for establishment of multiple additional PDN connections in EPS (S1 mode) | Samsung | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202567 | |||
| R5‑202567 | Adding procedure for establishment of multiple additional PDN connections in EPS (S1 mode) | Samsung | CR | Agreement | Yes |
YesThe CR was technically endorsed (see discussion on R5-201486)
| not pursued | No | R5‑201488 | |||
| R5‑201489 | Update of PDU SESSION ESTABLISHMENT ACCEPT for multi PDU-PDN handling | Samsung | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202568 | |||
| R5‑202568 | Update of PDU SESSION ESTABLISHMENT ACCEPT for multi PDU-PDN handling | Samsung | CR | Agreement | Yes |
YesThe CR was technically endorsed (see discussion on R5-201486)
| not pursued | No | R5‑201489 | |||
| R5‑201490 | Updates to Test procedure for UE for Tracking area updating / Inter-system change from N1 mode to S1 mode in 5GMM/EMM-IDLE mode | Samsung | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202569 | |||
| R5‑202569 | Updates to Test procedure for UE for Tracking area updating / Inter-system change from N1 mode to S1 mode in 5GMM/EMM-IDLE mode | Samsung | CR | Agreement | Yes |
YesThe CR was technically endorsed (see discussion on R5-201486)
| not pursued | No | R5‑201490 | |||
| R5‑201491 | Updates to Test procedure for UE for Tracking area updating / Inter-system change from S1 mode to N1 mode in 5GMM/EMM-IDLE mode | Samsung | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202570 | |||
| R5‑202570 | Updates to Test procedure for UE for Tracking area updating / Inter-system change from S1 mode to N1 mode in 5GMM/EMM-IDLE mode | Samsung | CR | Agreement | Yes |
YesThe CR was technically endorsed (see discussion on R5-201486)
| not pursued | No | R5‑201491 | |||
| R5‑201492 | Update of 4.5A.2 UE-requested PDU session establishment procedure | Samsung | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202571 | |||
| R5‑202571 | Update of 4.5A.2 UE-requested PDU session establishment procedure | Samsung | CR | Agreement | Yes |
YesThe CR was technically endorsed (see discussion on R5-201486)
| not pursued | No | R5‑201492 | |||
| R5‑201493 | Updates Procedure for UE-requested PDU session modification after the first S1 to N1 mode change | Samsung | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202572 | |||
| R5‑202572 | Updates Procedure for UE-requested PDU session modification after the first S1 to N1 mode change | Samsung | CR | Agreement | Yes |
YesThe CR was technically endorsed (see discussion on R5-201486)
| not pursued | No | R5‑201493 | |||
| R5‑201494 | Void 4.9.14 Procedure for UE-requested PDU session modification after the first S1 to N1 mode change | Samsung | CR | Agreement | Yes |
YesDependent on outcome of discussion on handling multi PDUs and PDNs
| withdrawn | Yes | ||||
| R5‑201498 | Correction to TAU request message contents on N1->S1 transition | Keysight Technologies UK | CR | Agreement | Yes |
Yesmerged into R5-201334.
| withdrawn | Yes | ||||
| R5‑201510 | Add IEs ARFCN-ValueUTRA-FDD, AvailabilityCombinationsPerCell, AvailabilityIndicator-r16, AvailableRB-SetPerCell and BAP-Routing-ID | Ericsson | CR | Agreement | Yes |
YesMCC TF160 recommended offline to not update TS 38.508-1 based on NR ASN.1 TS 38.331 version 16.0.0.
| withdrawn | Yes | ||||
| R5‑201511 | Add IE BeamFailureRecoverySCellConfig | Ericsson | CR | Agreement | Yes |
Yes
| withdrawn | Yes | ||||
| R5‑201548 | Add IEs BH-RLC-ChannelConfig, BH-LogicalChannelIdentity and BH-LogicalChannelIdentity-Ext | Ericsson | CR | Agreement | Yes |
YesMCC TF160 recommended offline to not update TS 38.508-1 based on NR ASN.1 TS 38.331 version 16.0.0.
| withdrawn | Yes | ||||
| R5‑201570 | Updates to test frequency definitions for SDL NR bands | MCC TF160, Ericsson | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202573 | |||
| R5‑202573 | Updates to test frequency definitions for SDL NR bands | MCC TF160, Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201570 | |||
| R5‑201571 | Updates to PDCCH-ConfigCommon | MCC TF160, Ericsson, Qualcomm Finland RFFE Oy, Anritsu | CR | Agreement | Yes |
Yesr2
| revised | No | R5‑202554 | |||
| R5‑202554 | Updates to PDCCH-ConfigCommon | MCC TF160, Ericsson, Qualcomm Finland RFFE Oy, Anritsu | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201571 | |||
| R5‑201572 | Corrections to default content of DCI messages | MCC TF160, Qualcomm | CR | Agreement | Yes |
Yesconflict with Qualcomm CR R5-202446.
Agreed in closing joint.
| agreed | No | ||||
| R5‑201640 | Correction to condition SRB_NR_PDCP in RadioBearerConfig | Qualcomm CDMA Technologies, Anritsu | CR | Agreement | Yes |
Yesoffline comments from TF160.
r1?
| revised | No | R5‑202574 | |||
| R5‑202574 | Correction to condition SRB_NR_PDCP in RadioBearerConfig | Qualcomm CDMA Technologies, Anritsu | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201640 | |||
| R5‑201655 | Correction to IE SearchSpace | Qualcomm CDMA Technologies, MCC TF160 | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑201656 | Correction to PDCCH-ConfigCommon for CA | Qualcomm CDMA Technologies, Anritsu | CR | Agreement | Yes |
Yesmerged with MCCTF160, Ericsson CR R5-201571.
| withdrawn | Yes | ||||
| R5‑201657 | Correction to UECapabilityEnquiry in case of EN-DC interband CA | Qualcomm CDMA Technologies, Anritsu | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202575 | |||
| R5‑202575 | Correction to UECapabilityEnquiry in case of EN-DC interband CA | Qualcomm CDMA Technologies, Anritsu | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201657 | |||
| R5‑201712 | Add IE BeamFailureRecoverySCellConfig | Ericsson | CR | Agreement | Yes |
YesMCC TF160 recommended offline to not update TS 38.508-1 based on NR ASN.1 TS 38.331 version 16.0.0.
| withdrawn | Yes | ||||
| R5‑201715 | Updates to PDCP-Config | MCC TF160 | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202576 | |||
| R5‑202576 | Updates to PDCP-Config | MCC TF160 | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201715 | |||
| R5‑201718 | Add IE CGI-InfoEUTRALogging | Ericsson | CR | Agreement | Yes |
YesMCC TF160 recommended offline to not update TS 38.508-1 based on NR ASN.1 TS 38.331 version 16.0.0.
| withdrawn | Yes | ||||
| R5‑201722 | Add IEs CGI-Info-Logging, CGI-Info-LoggingDetailed and CLI-RSSI-Range | Ericsson | CR | Agreement | Yes |
YesMCC TF160 recommended offline to not update TS 38.508-1 based on NR ASN.1 TS 38.331 version 16.0.0.
| withdrawn | Yes | ||||
| R5‑201792 | Removal of USIM configuration 14 | Keysight Technologies UK | CR | Agreement | No |
Yes
| withdrawn | Yes | ||||
| R5‑201794 | Removal of USIM configuration 14 | Keysight Technologies UK | CR | Agreement | Yes |
Yesver.
| revised | No | R5‑202534 | |||
| R5‑202534 | Removal of USIM configuration 14 | Keysight Technologies UK | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201794 | |||
| R5‑201800 | Addition of USIM configuration for TC 6.3.1.8 and TC 6.3.1.9 | Huawei, Hisilicon | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑201932 | Removing brackets from mid test channel BWs for FR2 | Ericsson | CR | Agreement | Yes |
Yesconflict wih R5-201862r1.
Deferred.
| agreed | No | ||||
| R5‑201940 | Add IEs CommonLocationInfo, CondConfigId, CondConfigToAddModList and ConditionalReconfiguration | Ericsson | CR | Agreement | Yes |
YesMCC TF160 recommended offline to not update TS 38.508-1 based on NR ASN.1 TS 38.331 version 16.0.0.
| withdrawn | Yes | ||||
| R5‑201956 | Correction of clause 4.4.2 on simulated cells | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑201957 | Clarifications of Annex C on calculation of test frequencies | Ericsson | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202577 | |||
| R5‑202577 | Clarifications of Annex C on calculation of test frequencies | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201957 | |||
| R5‑201958 | Correction to Annex C on calculation of kSSB to align SSB and RMSI subcarriers | Ericsson, Keysight | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑201959 | Removal of definition of frequencyDomainResources value dependent on CORESET#0 configuration in Annex C. | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑201960 | Update SIG test frequencies in clause 6.2.3.x | Ericsson, TF160 | CR | Agreement | Yes |
Yesr3
| revised | No | R5‑202578 | |||
| R5‑202578 | Update SIG test frequencies in clause 6.2.3.x | Ericsson, TF160 | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201960 | |||
| R5‑201961 | Correction of test frequency tables for NR band n1 | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑201962 | Correction of test frequency tables for NR band n2 | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑201963 | Correction of test frequency tables for NR band n3 | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑201964 | Correction of test frequency tables for NR band n5 | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑201965 | Correction of test frequency tables for NR band n7 | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑201966 | Correction of test frequency tables for NR band n8 | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑201967 | Correction of test frequency tables for NR band n12 | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑201968 | Correction of test frequency tables for NR band n20 | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑201969 | Correction of test frequency tables for NR band n25 | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑201970 | Correction of test frequency tables for NR band n28 | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑201971 | Correction of test frequency tables for NR band n34 | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑201972 | Correction of test frequency tables for NR band n38 | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑201973 | Correction of test frequency tables for NR band n39 | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑201974 | Correction of test frequency tables for NR band n40 | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑201975 | Correction of test frequency tables for NR band n41 | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑201976 | Correction of test frequency tables for NR band n50 | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑201977 | Correction of test frequency tables for NR band n51 | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑201978 | Correction of test frequency tables for NR band n66 | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑201979 | Correction of test frequency tables for NR band n70 | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑201980 | Correction of test frequency tables for NR band n71 | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑201981 | Correction of test frequency tables for NR band n74 | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑201982 | Correction of test frequency tables for NR band n77 | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑201983 | Correction of test frequency tables for NR band n78 | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑201984 | Correction of test frequency tables for NR band n79 | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑201985 | Correction of test frequency tables for NR band n257 | Ericsson | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202579 | |||
| R5‑202579 | Correction of test frequency tables for NR band n257 | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201985 | |||
| R5‑201986 | Correction of test frequency tables for NR band n258 | Ericsson | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202580 | |||
| R5‑202580 | Correction of test frequency tables for NR band n258 | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201986 | |||
| R5‑201987 | Correction of test frequency tables for NR band n260 | Ericsson | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202581 | |||
| R5‑202581 | Correction of test frequency tables for NR band n260 | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201987 | |||
| R5‑201988 | Correction of test frequency tables for NR band n261 | Ericsson | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202582 | |||
| R5‑202582 | Correction of test frequency tables for NR band n261 | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201988 | |||
| R5‑201989 | Corrections of test frequency tables for CA_n41C | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑201990 | Corrections of test frequency tables for CA_n78C | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑201991 | Editorial correction to test frequency clause numbering | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑201992 | Update and corrections of test frequency tables for NR Intra-Band Contiguous CA configurations for NR band n258 | Ericsson | CR | Agreement | No |
Yes
| withdrawn | Yes | ||||
| R5‑201993 | Update and corrections of test frequency tables for NR Intra-Band Contiguous CA configurations for NR band n260 | Ericsson | CR | Agreement | No |
Yes
| withdrawn | Yes | ||||
| R5‑201994 | Update and corrections of test frequency tables for NR Intra-Band Contiguous CA configurations for NR band n261 | Ericsson | CR | Agreement | No |
Yes
| withdrawn | Yes | ||||
| R5‑202003 | Corrections of test frequency tables for EN-DC configuration DC_(n)41AA | Ericsson | CR | Agreement | No |
Yeslate doc
deferred for RAN5-88e
| withdrawn | Yes | ||||
| R5‑202004 | Corrections of test frequency tables for EN-DC configuration DC_(n)71AA | Ericsson | CR | Agreement | No |
Yeslate doc
deferred for RAN5-88e
| withdrawn | Yes | ||||
| R5‑202005 | Introduction of protocol testing applicability for EN-DC inter-band, NR-CA inter-band and NR DC test frequency tables | Ericsson | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202583 | |||
| R5‑202583 | Introduction of protocol testing applicability for EN-DC inter-band, NR-CA inter-band and NR DC test frequency tables | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202005 | |||
| R5‑202011 | Add IEs ConfiguredGrantConfigIndex, ConfiguredGrantConfigIndexMAC and ConfiguredGrantConfigList | Ericsson | CR | Agreement | Yes |
YesMCC TF160 recommended offline to not update TS 38.508-1 based on NR ASN.1 TS 38.331 version 16.0.0.
| withdrawn | Yes | ||||
| R5‑202020 | Alignment of test sequences for generic test procedures | Ericsson | CR | Agreement | Yes |
YesTF160 request to 'flag'
| withdrawn | Yes | ||||
| R5‑202021 | Updates to Generic Test Procedure for IMS MO speech call establishment | Ericsson | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑203078 | |||
| R5‑203078 | Updates to Generic Test Procedure for IMS MO speech call establishment | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202021 | |||
| R5‑202022 | Update NR-DC in chapter 4 | Ericsson | CR | Agreement | Yes |
YesTF160 disagreed: The change in Table 4.8.1-4: RadioBearerConfig-SRB2-DRB (n, m) does not work, it breaks the logic of conditions.
r1
| revised | No | R5‑202584 | |||
| R5‑202584 | Update NR-DC in chapter 4 | Ericsson | CR | Agreement | Yes |
Yesno rev 1
| revised | No | R5‑203079 | R5‑202022 | ||
| R5‑203079 | Update NR-DC in chapter 4 | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202584 | |||
| R5‑202024 | Update IE PDCP-Config | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑202129 | Correction to Reference QoS rules | Qualcomm CDMA Technologies | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202585 | |||
| R5‑202585 | Correction to Reference QoS rules | Qualcomm CDMA Technologies | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202129 | |||
| R5‑202212 | Corrections of test frequency tables for CA_n257x | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑202213 | Corrections of test frequency tables for CA_n258x | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑202214 | Corrections of test frequency tables for CA_n260x | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑202215 | Corrections of test frequency tables for CA_n261x | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑202249 | Add IE InvalidSymbolPattern | Ericsson | CR | Agreement | Yes |
YesMCC TF160 recommended offline to not update TS 38.508-1 based on NR ASN.1 TS 38.331 version 16.0.0.
| withdrawn | Yes | ||||
| R5‑202252 | Updates to Generic Test Procedure for IMS MT speech call establishment | Ericsson | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202586 | |||
| R5‑202586 | Updates to Generic Test Procedure for IMS MT speech call establishment | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202252 | |||
| R5‑202253 | Updates to Generic Test Procedure for IMS MO call release | Ericsson | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202587 | |||
| R5‑202587 | Updates to Generic Test Procedure for IMS MO call release | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202253 | |||
| R5‑202257 | Aligning the tabular representation of ASN.1 with PRD13 section 4.6 | Samsung, MCC TF160 | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202588 | |||
| R5‑202588 | Aligning the tabular representation of ASN.1 with PRD13 section 4.6 | Samsung, MCC TF160 | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202257 | |||
| R5‑202486 | Correction to content of EF5GSN3GPPLOCI | MediaTek Inc. | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑202487 | Update the default USIM configurations | MediaTek Inc. | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202589 | |||
| R5‑202589 | Update the default USIM configurations | MediaTek Inc. | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202487 | |||
| R5‑202525 | Correction to System Information Combination for PWS | ANRITSU LTD, Qualcomm | CR | Agreement | Yes |
Yeslate doc
| agreed | No | ||||
| R5‑202542 | Addition of Generic procedure to check user plane connectivity for CA tests | Qualcomm CDMA Technologies | CR | Agreement | Yes |
Yeslate doc
r2
| revised | No | R5‑202590 | |||
| R5‑202590 | Addition of Generic procedure to check user plane connectivity for CA tests | Qualcomm CDMA Technologies | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202542 | |||
| 6.3.2.2 | TS 38.508-2 | R5‑201495 | Removing multi PDU/PDN relevant ICS from UE implementation capabilities | Samsung | CR | Agreement | Yes |
Yes
| withdrawn | Yes | ||
| R5‑202049 | Additions and corrections to PICS | Motorola Mobility, Qualcomm, Huawei, Hisilcon | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202591 | |||
| R5‑202591 | Additions and corrections to PICS | Motorola Mobility, Qualcomm, Huawei, Hisilcon | CR | Agreement | Yes |
Yesfirst agreed, then revised further
| revised | No | R5‑203113 | R5‑202049 | ||
| R5‑203113 | Additions and corrections to PICS | Motorola Mobility, Qualcomm, Huawei, Hisilcon | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202591 | |||
| R5‑202541 | Adding new ICS for handling inter-system change S1-N1 and aligning PDN and PDU handling | Samsung | CR | Agreement | Yes |
Yeslate doc
The CR was technically endorsed (see discussion on R5-201486)
| not pursued | No | ||||
| 6.3.2.3 | TS 38.509 | |||||||||||
| 6.3.2.4 | TS 38.523-1 | |||||||||||
| 6.3.2.4.1 | Clauses 1 - 5 | R5‑202256 | Adding generic test parameters references to section 5.3 | Samsung | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202592 | |
| R5‑202592 | Adding generic test parameters references to section 5.3 | Samsung | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202256 | |||
| 6.3.2.4.2 | Idle Mode (Clause 6) | R5‑201338 | Correction to NR TC 6.1.1.1-PLMN selection Automatic mode | Huawei, Hisilicon | CR | Agreement | Yes |
Yesr2
| revised | No | R5‑202593 | |
| R5‑202593 | Correction to NR TC 6.1.1.1-PLMN selection Automatic mode | Huawei, Hisilicon | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201338 | |||
| R5‑201339 | Correction to NR TC 6.1.1.5-PLMN selection with Automatic mode and user reselection | Huawei, Hisilicon | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202594 | |||
| R5‑202594 | Correction to NR TC 6.1.1.5-PLMN selection with Automatic mode and user reselection | Huawei, Hisilicon | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201339 | |||
| R5‑201340 | Correction to NR TC 6.1.2.18-Cell reselection with Sintrasearch and Snonintrasearch | Huawei, Hisilicon, Datang Linktester | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑201341 | Correction to NR TC 6.1.2.19-N2N Speed dependent cell reselection | Huawei, Hisilicon, Datang Linktester | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑201342 | Correction to NR TC 6.2.1.1-Inter-RAT PLMN Selection | Huawei, Hisilicon, Datang Linktester | CR | Agreement | No |
Yes
| withdrawn | Yes | ||||
| R5‑201343 | Correction to NR TC 6.2.3.3-From NR RRC_IDLE to E-UTRA_IDLE | Huawei, HiSilicon, Keysight Technologies | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202595 | |||
| R5‑202595 | Correction to NR TC 6.2.3.3-From NR RRC_IDLE to E-UTRA_IDLE | Huawei, HiSilicon, Keysight Technologies | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201343 | |||
| R5‑201344 | Correction to NR TC 6.2.3.9-N2L Speed dependent cell reselection | Huawei, Hisilicon, Datang Linktester | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑201345 | Correction to NR TC 6.3.1.1-Security check successful using List Type 1 | Huawei, Hisilicon, ZTE Corporation | CR | Agreement | Yes |
Yesr1
R5-201417 has been merged with this CR.
| revised | No | R5‑202596 | |||
| R5‑202596 | Correction to NR TC 6.3.1.1-Security check successful using List Type 1 | Huawei, Hisilicon, ZTE Corporation | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201345 | |||
| R5‑201346 | Correction to NR TC 6.3.1.2-ACK has NOT been requested | Huawei, Hisilicon | CR | Agreement | Yes |
Yes
| withdrawn | Yes | ||||
| R5‑201347 | Correction to NR TC 6.3.1.3-Security check unsuccessful automatic mode | Huawei, Hisilicon | CR | Agreement | Yes |
Yes
| withdrawn | Yes | ||||
| R5‑201348 | Correction to NR TC 6.3.1.4-Security check unsuccessful manual mode | Huawei, Hisilicon, ZTE Corporation | CR | Agreement | Yes |
Yesr1
CR R5-201420 has been merged with this CR.
r2
| revised | No | R5‑202597 | |||
| R5‑202597 | Correction to NR TC 6.3.1.4-Security check unsuccessful manual mode | Huawei, Hisilicon, ZTE Corporation | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201348 | |||
| R5‑201349 | Correction to NR TC 6.4.1.1-PLMN selection Automatic mode in RRC_INACTIVE state | Huawei, Hisilicon | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑201417 | Corrections to Idle Mode SoR Test Case 6.3.1.1 | ZTE Corporation | CR | Agreement | Yes |
Yesmerged into R5-201345r1.
| withdrawn | Yes | ||||
| R5‑201418 | Corrections to Idle Mode SoR Test Case 6.3.1.2 | ZTE Corporation, Huawei, HiSilicon | CR | Agreement | Yes |
Yesr1
Merged with R5-201346 and revised with the comments from Huawei and TF160.
r2
| revised | No | R5‑202598 | |||
| R5‑202598 | Corrections to Idle Mode SoR Test Case 6.3.1.2 | ZTE Corporation, Huawei, HiSilicon | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201418 | |||
| R5‑201419 | Corrections to Idle Mode SoR Test Case 6.3.1.3 | ZTE Corporation, Huawei, HiSilicon | CR | Agreement | Yes |
Yesr1
Merged with R5-201347 and revised with the comments from Huawei and TF160.
r2
| revised | No | R5‑202599 | |||
| R5‑202599 | Corrections to Idle Mode SoR Test Case 6.3.1.3 | ZTE Corporation, Huawei, HiSilicon | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201419 | |||
| R5‑201420 | Corrections to Idle Mode SoR Test Case 6.3.1.4 | ZTE Corporation | CR | Agreement | Yes |
Yesmerged into R5-201348r1.
| withdrawn | Yes | ||||
| R5‑201421 | Addition of Idle Mode SoR Test Case 6.3.1.5 | ZTE Corporation, MediaTek Inc. | CR | Agreement | Yes |
Yesr1
Revised with the comments from Huawei and TF160.
r2
| revised | No | R5‑202600 | |||
| R5‑202600 | Addition of Idle Mode SoR Test Case 6.3.1.5 | ZTE Corporation, MediaTek Inc. | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201421 | |||
| R5‑201422 | Addition of Idle Mode SoR Test Case 6.3.1.7 | ZTE Corporation | CR | Agreement | Yes |
Yesr1
Revised with the comments from Huawei and TF160.
r2
| revised | No | R5‑202601 | |||
| R5‑202601 | Addition of Idle Mode SoR Test Case 6.3.1.7 | ZTE Corporation | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201422 | |||
| R5‑201423 | Corrections to Idle Mode SoR Test Case 6.3.1.8 | ZTE Corporation | CR | Agreement | Yes |
Yesmerged into R5-201798r1.
| withdrawn | Yes | ||||
| R5‑201424 | Corrections to Idle Mode SoR Test Case 6.3.1.9 | ZTE Corporation | CR | Agreement | Yes |
Yesmerged into R5-201799r1.
| withdrawn | Yes | ||||
| R5‑201425 | Correction to NR TC 6.1.2.7-Cell reselection with Equivalent PLMN | Huawei, Hisilicon | CR | Agreement | Yes |
Yes
| withdrawn | Yes | ||||
| R5‑201440 | Correction to NR TC 6.1.2.2-Qqualmin Serving Cell non-suitable | Huawei, Hisilicon | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑201441 | Correction to NR TC 6.2.1.2-Selection of correct RAT for UPLMN | Huawei, Hisilicon | CR | Agreement | No |
Yes
| withdrawn | Yes | ||||
| R5‑201442 | Correction to NR TC 6.2.1.3-Selection of correct PLMN and RAT in shared network environment | Huawei, Hisilicon | CR | Agreement | No |
Yes
| withdrawn | Yes | ||||
| R5‑201471 | Addition of NR TC 6.2.2.1-N2L Serving cell becomes non-suitable | Huawei, Hisilicon | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑201472 | Addition of NR TC 6.2.2.2-L2N Serving cell becomes non-suitable | Huawei, Hisilicon | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202602 | |||
| R5‑202602 | Addition of NR TC 6.2.2.2-L2N Serving cell becomes non-suitable | Huawei, Hisilicon | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201472 | |||
| R5‑201477 | Correction to FR1 power level table for several test cases to not to assign beyond maximum power level -78 | ANRITSU LTD | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑201499 | Correction to NR Idle mode test case 6.1.2.5 | Keysight Technologies UK | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑201500 | Correction to NR idle mode test case 6.4.2.2 | Keysight Technologies UK, HiSilicon, Huawei | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑201628 | Correction of NR test case 6.4.3.1-Inter-RAT cell reselection in RRC_INACTIVE | StarPoint,Huawei, HiSilicon | CR | Agreement | Yes |
YesWithdrawn as R5-201470 is agreed - no need to add the Security Mode procedure in test case
| withdrawn | Yes | ||||
| R5‑201647 | Correction to NR5G Idle Mode TC 6.4.2.1 | Qualcomm CDMA Technologies | CR | Agreement | No |
Yeslate doc
| withdrawn | Yes | ||||
| R5‑201653 | Correction to NR5G Idle Mode TC 6.1.2.11 | Qualcomm CDMA Technologies, Keysight Technologies | CR | Agreement | Yes |
Yesr2
| revised | No | R5‑202603 | |||
| R5‑202603 | Correction to NR5G Idle Mode TC 6.1.2.11 | Qualcomm CDMA Technologies, Keysight Technologies | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201653 | |||
| R5‑201703 | Correction to NR TC 6.2.3.7-N2L cell reselection | Huawei, Hisilicon | CR | Agreement | No |
Yes
| withdrawn | Yes | ||||
| R5‑201790 | Correction to NR idle mode test case 6.4.2.1 | Keysight Technologies UK, HiSilicon, Huawei | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑201791 | Correction to NR5GC IRAT test case 6.2.3.1 | Keysight Technologies UK | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑201793 | Removal of requirement of USIM confguration 14 from 5GMM Idle mode test cases | Keysight Technologies UK | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑201798 | Correction to NR TC 6.3.1.8-SoR after registration Automatic mode | Huawei, Hisilicon, CATT, TDIA, , ZTE Corporation | CR | Agreement | Yes |
Yesr1
CR R5-201423 has been merged with this CR.
r2
| revised | No | R5‑202604 | |||
| R5‑202604 | Correction to NR TC 6.3.1.8-SoR after registration Automatic mode | Huawei, Hisilicon, CATT, TDIA, , ZTE Corporation | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201798 | |||
| R5‑201799 | Correction to NR TC 6.3.1.9-SoR after registration Manual mode | Huawei, Hisilicon, CATT, TDIA, ZTE Corporation | CR | Agreement | Yes |
Yesr1
CR R5-201424 has been merged with this CR.
r2
| revised | No | R5‑202605 | |||
| R5‑202605 | Correction to NR TC 6.3.1.9-SoR after registration Manual mode | Huawei, Hisilicon, CATT, TDIA, ZTE Corporation | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201799 | |||
| R5‑201943 | Correction to NR TC 6.2.3.4-inter-RAT reselection | Huawei, Hisilicon | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑201952 | Correction to NR Idle mode test case 6.2.3.5 | Keysight Technologies UK | CR | Agreement | Yes |
Yesnot needed due to change in the RRC_IDLE mode generic procedure proposed in R5-201470.
| withdrawn | Yes | ||||
| R5‑202170 | Correction to NR test case 6.2.3.5 | StarPoint,Huawei, HiSilicon | CR | Agreement | Yes |
YesCould be withdrawn if R5-201470 is agreed
| withdrawn | Yes | ||||
| R5‑202178 | Correction to 5G test case 6.2.1.2 | TDIA, CATT | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑202185 | Correction to 5G test case 6.2.1.3 | TDIA, CATT | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑202205 | Correction to 5G test case 6.2.1.4 | TDIA, CATT | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑202218 | Correction to test case 6.1.2.23 | TDIA, CATT | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202606 | |||
| R5‑202606 | Correction to test case 6.1.2.23 | TDIA, CATT | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202218 | |||
| R5‑202537 | Correction to NR RRC IDLE testcase 6.1.2.1 | Anritsu Ltd | CR | Agreement | Yes |
Yeslate doc
| agreed | No | ||||
| 6.3.2.4.3 | Layer 2 | |||||||||||
| 6.3.2.4.3.1 | NR Layer 2 | |||||||||||
| 6.3.2.4.3.1.1 | Common Test Case Specific Values for Layer 2 (Clause 7.1.0) | |||||||||||
| 6.3.2.4.3.1.2 | MAC | R5‑201443 | Correction to NR TC 7.1.1.4.1.x-TBS ambiguity of DL | Huawei, Hisilicon | CR | Agreement | Yes |
YesOffline comments from Motorola Mobility and Keysight UK. May not be able to get all the {Imcs, Nprb, L} combinations leading to ambiguity.
Deferred.
Conclusion: not able to get the specific {Imcs, Nprb, L} combinations for 3824.0 < Ninfo < 3825.0
| withdrawn | Yes | ||
| R5‑201444 | Correction to NR TC 7.1.1.4.2.x-TBS ambiguity of UL | Huawei, Hisilicon | CR | Agreement | Yes |
YesConflict with R5-201503.
Offline comments from Motorola Mobility and Keysight UK. May not be able to get all the {Imcs, Nprb, L} combinations leading to ambiguity.
Deferred.
Conclusion: not able to get the specific {Imcs, Nprb, L} combinations for 3824.0 < Ninfo < 3825.0
r1
| revised | No | R5‑202607 | |||
| R5‑202607 | Correction to NR TC 7.1.1.4.2.x-TBS ambiguity of UL | Huawei, Hisilicon | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201444 | |||
| R5‑201501 | Correction to NR MAC test case 7.1.1.1.1a | Keysight Technologies UK | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑201502 | Correction to BWP Dependent Parameters for RA type 0 in MAC testcases | Keysight Technologies UK | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑201503 | Correction to NR MAC test case 7.1.1.4.2.3 | Keysight Technologies UK, Huawei, HiSilicon | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202608 | |||
| R5‑202608 | Correction to NR MAC test case 7.1.1.4.2.3 | Keysight Technologies UK, Huawei, HiSilicon | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201503 | |||
| R5‑201519 | Corrections to MAC test cases for Logical Channel ID | MCC 160, Motorola Mobility | CR | Agreement | Yes |
Yes"Title inconsistency
-3GU: LCID Correction in MAC test cases / CR coversheet: Corrections to MAC test cases for Logical Channel ID"
"Hard coding of LCID is creating problems in SA test cases for support of multi PDN's.
CR title different from 3GU"
| agreed | No | ||||
| R5‑201637 | Corrections to NR5G MAC TC 7.1.1.3.1 | Qualcomm CDMA Technologies, Anritsu | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑201660 | Correction to NR TC 7.1.1.3.1 | Starpoint, TDIA | CR | Agreement | Yes |
Yesmerged into Keysight's R5-201954.
| withdrawn | Yes | ||||
| R5‑201954 | Correction to NR MAC test case 7.1.1.3.1 | Keysight Technologies UK, Starpoint | CR | Agreement | Yes |
YesR5-201660 was merged into here.
| revised | No | R5‑202543 | |||
| R5‑202543 | Correction to NR MAC test case 7.1.1.3.1 | Keysight Technologies UK, Starpoint | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201954 | |||
| R5‑202025 | Corrections to NR DRX Test Cases | Motorola Mobility, MCC TF160 | CR | Agreement | Yes |
Yesoffline comments by Keysight.
Deferred.
r2
| revised | No | R5‑202609 | |||
| R5‑202609 | Corrections to NR DRX Test Cases | Motorola Mobility, MCC TF160 | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202025 | |||
| R5‑202026 | Corrections to NR MAC Test Case 7.1.1.3.2b | Motorola Mobility, MCC TF160 | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑202107 | Editorial Corrections to NR5G MAC TC 7.1.1.1.2 | Qualcomm CDMA Technologies | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑202140 | Addition of new DRX TC 7.1.1.5.5 for short DRX configured and Long DRX command MAC CE is received | NTT DOCOMO INC. | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑202225 | Corrections to MAC TBS test cases with dynamicSwitch | Motorola Mobility, Qualcomm, MCC TF160 | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202610 | |||
| R5‑202610 | Corrections to MAC TBS test cases with dynamicSwitch | Motorola Mobility, Qualcomm, MCC TF160 | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202225 | |||
| R5‑202229 | Addition of new MAC NR-DC test cases | Motorola Mobility | CR | Agreement | No |
Yeslate doc
| withdrawn | Yes | ||||
| R5‑202485 | Correction to NR MAC CA Test Case | Motorola Mobility, MCC TF160 | CR | Agreement | Yes |
Yeslate doc
r1
| revised | No | R5‑202611 | |||
| R5‑202611 | Correction to NR MAC CA Test Case | Motorola Mobility, MCC TF160 | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202485 | |||
| R5‑202538 | Correction to the ENDC testcase 7.1.1.3.7 | Anritsu Ltd | CR | Agreement | Yes |
Yeslate doc
| agreed | No | ||||
| R5‑202539 | Correction to NR MAC test case 7.1.1.3.3 | Keysight Technologies UK | CR | Agreement | Yes |
Yeslate doc
| agreed | No | ||||
| 6.3.2.4.3.1.3 | RLC | R5‑201484 | Correction 7.1.2.3.7 to use downlink timing reference for scheduling less than 100ms timing gap | ANRITSU LTD | CR | Agreement | Yes |
Yes
| agreed | No | ||
| R5‑201504 | Correction to NR RLC test case 7.1.2.3.4 | Keysight Technologies UK | CR | Agreement | Yes |
Yes"Request by author
R5-201625 proposes an optimized version of the affected test case 7.1.2.3.4 to reduce the test execution time"
| withdrawn | Yes | ||||
| R5‑201573 | Editorial corrections to NR RLC test cases 7.1.2.3.x | MCC TF160 | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202612 | |||
| R5‑202612 | Editorial corrections to NR RLC test cases 7.1.2.3.x | MCC TF160 | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201573 | |||
| R5‑201574 | Updates to NR RLC test case 7.1.2.3.11 | MCC TF160, Anritsu | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑201625 | Correction to 7.1.2.3.3 and 7.1.2.3.4 to reduce test execution time | Anritsu Ltd, Qualcomm | CR | Agreement | Yes |
YesKeysight UK: failure reason seem to be mismatch in the loopback PDU SN.
r4
| revised | No | R5‑202613 | |||
| R5‑202613 | Correction to 7.1.2.3.3 and 7.1.2.3.4 to reduce test execution time | Anritsu Ltd, Qualcomm | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201625 | |||
| 6.3.2.4.3.1.4 | PDCP | R5‑201427 | Correction to ENDC TC 7.1.3.2.1-Correct functionality of Integrity algorithm SNOW3G | Huawei, Hisilicon | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202614 | |
| R5‑202614 | Correction to ENDC TC 7.1.3.2.1-Correct functionality of Integrity algorithm SNOW3G | Huawei, Hisilicon | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201427 | |||
| R5‑201428 | Correction to ENDC TC 7.1.3.2.2-Correct functionality of Integrity algorithm AES | Huawei, Hisilicon | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202615 | |||
| R5‑202615 | Correction to ENDC TC 7.1.3.2.2-Correct functionality of Integrity algorithm AES | Huawei, Hisilicon | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201428 | |||
| R5‑201429 | Correction to ENDC TC 7.1.3.2.3-Correct functionality of Integrity algorithm ZUC | Huawei, Hisilicon | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202616 | |||
| R5‑202616 | Correction to ENDC TC 7.1.3.2.3-Correct functionality of Integrity algorithm ZUC | Huawei, Hisilicon | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201429 | |||
| R5‑201430 | Correction to ENDC TC 7.1.3.3.1-Correct functionality of encryption algorithm SNOW3G | Huawei, Hisilicon | CR | Agreement | Yes |
Yes
| revised | No | R5‑202617 | |||
| R5‑202617 | Correction to ENDC TC 7.1.3.3.1-Correct functionality of encryption algorithm SNOW3G | Huawei, Hisilicon | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201430 | |||
| R5‑201431 | Correction to ENDC TC 7.1.3.3.2-Correct functionality of encryption algorithm AES | Huawei, Hisilicon | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑201432 | Correction to ENDC TC 7.1.3.3.3-Correct functionality of encryption algorithm ZUC | Huawei, Hisilicon | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑201575 | Enhancement of NR PDCP test case 7.1.3.1.1 | MCC TF160 | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑201642 | Corrections to NR5G PDCP TC 7.1.3.4.1 and 7.1.3.4.2 | Qualcomm CDMA Technologies, Anritsu | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202618 | |||
| R5‑202618 | Corrections to NR5G PDCP TC 7.1.3.4.1 and 7.1.3.4.2 | Qualcomm CDMA Technologies, Anritsu | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201642 | |||
| R5‑202113 | Correction to PDCP test case 7.1.3.4.1 to udpate the security | ANRITSU LTD, MediaTek | CR | Agreement | Yes |
Yeschanges are same as R5-201642
| withdrawn | Yes | ||||
| R5‑202506 | Correction to NR PDCP test case 7.1.3.5.5 | ANRITSU LTD, MC TF160 | CR | Agreement | Yes |
Yeslate doc
| agreed | No | ||||
| 6.3.2.4.3.1.5 | SDAP | R5‑201650 | Corrections to NR5G SDAP TC 7.1.4.2 | Qualcomm CDMA Technologies, Keysight Technologies | CR | Agreement | Yes |
Yes
| agreed | No | ||
| 6.3.2.4.4 | RRC | |||||||||||
| 6.3.2.4.4.1 | NR RRC | |||||||||||
| 6.3.2.4.4.2 | MR-DC RRC | |||||||||||
| 6.3.2.4.4.1.1 | RRC Connection Management Procedures (clause 8.1.1) | R5‑201350 | Correction to NR TC 8.1.1.2.1-T300 expiry | Huawei, Hisilicon, ZTE | CR | Agreement | Yes |
YesQualcomm needed more time to review.
r2
| revised | No | R5‑202619 | |
| R5‑202619 | Correction to NR TC 8.1.1.2.1-T300 expiry | Huawei, Hisilicon, ZTE | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201350 | |||
| R5‑201351 | Correction to NR TC 8.1.1.3.2-Redirection from NR to E-UTRA | Huawei, Hisilicon, Datang Linktester | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202620 | |||
| R5‑202620 | Correction to NR TC 8.1.1.3.2-Redirection from NR to E-UTRA | Huawei, Hisilicon, Datang Linktester | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201351 | |||
| R5‑201352 | Correction to NR TC 8.1.1.3.4-RRC connection release | Huawei, Hisilicon, StarPoint | CR | Agreement | Yes |
Yesmerged into R5-201436r1
| withdrawn | Yes | ||||
| R5‑201433 | Correction to test case 8.1.1.2.1 | ZTE | CR | Agreement | Yes |
Yesr1
coverd by R5-201350 from HuaWei.
| revised | No | R5‑202511 | |||
| R5‑202511 | Correction to test case 8.1.1.2.1 | ZTE | CR | Agreement | Yes |
Yes
| withdrawn | Yes | R5‑201433 | |||
| R5‑201434 | Correction to test case 8.1.1.3.1 | ZTE | CR | Agreement | Yes |
Yesno cl. aff.
r1
| revised | No | R5‑202621 | |||
| R5‑202621 | Correction to test case 8.1.1.3.1 | ZTE | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201434 | |||
| R5‑201435 | Correction to test case 8.1.1.3.3 | ZTE | CR | Agreement | Yes |
Yesno cl. aff.
r1
| revised | No | R5‑202622 | |||
| R5‑202622 | Correction to test case 8.1.1.3.3 | ZTE | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201435 | |||
| R5‑201436 | Correction to test case 8.1.1.3.4 | ZTE, Huawei, HiSilicon, StarPoint | CR | Agreement | Yes |
Yesno cl. aff.
r1
| revised | No | R5‑202623 | |||
| R5‑202623 | Correction to test case 8.1.1.3.4 | ZTE, Huawei, HiSilicon, StarPoint | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201436 | |||
| R5‑201437 | Correction to test case 8.1.1.4.1 | ZTE | CR | Agreement | Yes |
Yesno cl. aff.
r1
| revised | No | R5‑202624 | |||
| R5‑202624 | Correction to test case 8.1.1.4.1 | ZTE | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201437 | |||
| R5‑201438 | Correction to test case 8.1.1.4.2 | ZTE | CR | Agreement | Yes |
Yesno cl. aff.
r1
| revised | No | R5‑202625 | |||
| R5‑202625 | Correction to test case 8.1.1.4.2 | ZTE | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201438 | |||
| R5‑201636 | Corrections to NR5G RRC TC 8.2.2.6.1 | Qualcomm CDMA Technologies, Anritsu | CR | Agreement | Yes |
Yesoffline comments from TF160.
r1
| revised | No | R5‑202627 | |||
| R5‑202627 | Corrections to NR5G RRC TC 8.2.2.6.1 | Qualcomm CDMA Technologies, Anritsu | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201636 | |||
| R5‑201641 | Corrections to NR5G RRC TC 8.1.1.2.1 | Qualcomm CDMA Technologies | CR | Agreement | No |
Yes
| withdrawn | Yes | ||||
| R5‑201646 | Corrections to NR5G RRC TC 8.1.1.4.1 | Qualcomm CDMA Technologies | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑202436 | Corrections to EN-DC RRC TC 8.2.2.7.1 | Qualcomm CDMA Technologies | CR | Agreement | Yes |
YesRel-15
r1
| revised | No | R5‑202629 | |||
| R5‑202629 | Corrections to EN-DC RRC TC 8.2.2.7.1 | Qualcomm CDMA Technologies | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202436 | |||
| 6.3.2.4.4.1.2 | RRC Reconfiguration (clause 8.1.2) | R5‑201353 | Correction to NR TC 8.1.2.1.4-RRC reconfiguration Dedicated RLF timer | Huawei, Hisilicon | CR | Agreement | Yes |
Yes
| agreed | No | ||
| R5‑201439 | Correction to test case 8.1.2.1.1 | ZTE | CR | Agreement | Yes |
Yesno cl. aff.
r1
| revised | No | R5‑202626 | |||
| R5‑202626 | Correction to test case 8.1.2.1.1 | ZTE | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201439 | |||
| 6.3.2.4.4.2.1 | RRC UE Capability / Others (clause 8.2.1) | R5‑201761 | Correction to NR UE Capability test case 8.2.1.1.1 | Qualcomm Incorporated | CR | Agreement | Yes |
Yes
| agreed | No | ||
| 6.3.2.4.4.1.2 | RRC Reconfiguration (clause 8.1.2) | R5‑202236 | Update RRC TC 8.1.2.1.5 | Ericsson | CR | Agreement | Yes |
YesTF160 mamager: need to align RRC WP and 38.523-1.
r3
| revised | No | R5‑202628 | |
| R5‑202628 | Update RRC TC 8.1.2.1.5 | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202236 | |||
| 6.3.2.4.4.1.3 | RRC Measurement Configuration Control and Reporting (clause 8.1.3) | R5‑201354 | Correction to NR TC 8.1.3.1.11-Two RSRQ event A3 | Huawei, Hisilicon | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202630 | |
| R5‑202630 | Correction to NR TC 8.1.3.1.11-Two RSRQ event A3 | Huawei, Hisilicon | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201354 | |||
| R5‑201355 | Correction to NR TC 8.1.3.1.16-Intra NR measurements with Whitelisting | Huawei, Hisilicon, Datang Linktester | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202631 | |||
| R5‑202631 | Correction to NR TC 8.1.3.1.16-Intra NR measurements with Whitelisting | Huawei, Hisilicon, Datang Linktester | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201355 | |||
| R5‑201356 | Correction to NR TC 8.1.3.1.23-Continuation of the measurements after RRC Resume | Huawei, Hisilicon | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑201357 | Correction to NR TC 8.1.3.2.3-RSRQ event B2 | Huawei, Hisilicon | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202632 | |||
| R5‑202632 | Correction to NR TC 8.1.3.2.3-RSRQ event B2 | Huawei, Hisilicon | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201357 | |||
| R5‑201358 | Correction to NR TC 8.1.3.3.1-NR CGI | Huawei, Hisilicon, Datang Linktester | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202633 | |||
| R5‑202633 | Correction to NR TC 8.1.3.3.1-NR CGI | Huawei, Hisilicon, Datang Linktester | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201358 | |||
| R5‑201359 | Correction to NR TC 8.1.3.3.2-LTE CGI | Huawei, Hisilicon, Datang Linktester | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202634 | |||
| R5‑202634 | Correction to NR TC 8.1.3.3.2-LTE CGI | Huawei, Hisilicon, Datang Linktester | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201359 | |||
| 6.3.2.4.4.2.2 | RRC Radio Bearer (clause 8.2.2) | R5‑201362 | Correction to NR TC 8.2.2.4.1-SCG DRB | Huawei, Hisilicon | CR | Agreement | No |
Yes
| withdrawn | Yes | ||
| R5‑201363 | Correction to NR TC 8.2.2.5.1-Split DRB | Huawei, Hisilicon | CR | Agreement | No |
Yes
| withdrawn | Yes | ||||
| R5‑201364 | Correction to NR TC 8.2.2.6.1-MCG DRB | Huawei, Hisilicon | CR | Agreement | No |
Yes
| withdrawn | Yes | ||||
| R5‑201478 | Correction to 8.2.2.8.1 not to check reception of RRCReconfigurationComplete if RRCReconfiguration is not sent | Anritsu Ltd, Qualcomm | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202645 | |||
| R5‑202645 | Correction to 8.2.2.8.1 not to check reception of RRCReconfigurationComplete if RRCReconfiguration is not sent | Anritsu Ltd, Qualcomm | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201478 | |||
| R5‑201506 | Correction to EN-DC RRC test case 8.2.2.7.1 | Keysight Technologies UK, MediaTek | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202646 | |||
| R5‑202646 | Correction to EN-DC RRC test case 8.2.2.7.1 | Keysight Technologies UK, MediaTek | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201506 | |||
| 6.3.2.4.4.1.3 | RRC Measurement Configuration Control and Reporting (clause 8.1.3) | R5‑201576 | Corrections to NR measurement test cases 8.1.3.x | MCC TF160 | CR | Agreement | Yes |
Yesr2
| revised | No | R5‑202635 | |
| R5‑202635 | Corrections to NR measurement test cases 8.1.3.x | MCC TF160 | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201576 | |||
| R5‑201577 | Correction to NR test case 8.1.3.1.15A | MCC TF160, Datang Linktester, HiSilicon | CR | Agreement | Yes |
YesChanges covered in R5-201704r2
| withdrawn | Yes | ||||
| R5‑201578 | Correction to NR test cases 8.1.3.1.13 and 8.1.3.1.14A | MCC TF160, Anritsu | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| 6.3.2.4.4.2.2 | RRC Radio Bearer (clause 8.2.2) | R5‑201580 | Corrections to EN-DC test case 8.2.2.3.1 | MCC TF160 | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202647 | |
| R5‑202647 | Corrections to EN-DC test case 8.2.2.3.1 | MCC TF160 | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201580 | |||
| R5‑201635 | Corrections to NR5G RRC TC 8.2.3.1.1 | Qualcomm CDMA Technologies | CR | Agreement | No |
Yes
| withdrawn | Yes | ||||
| 6.3.2.4.4.1.3 | RRC Measurement Configuration Control and Reporting (clause 8.1.3) | R5‑201639 | Corrections to NR5G RRC TC 8.1.3.1.15A | Qualcomm CDMA Technologies | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202636 | |
| R5‑202636 | Corrections to NR5G RRC TC 8.1.3.1.15A | Qualcomm CDMA Technologies | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201639 | |||
| 6.3.2.4.4.2.2 | RRC Radio Bearer (clause 8.2.2) | R5‑201648 | Addition of NRDC RRC TC 8.2.2.4.2 | Qualcomm CDMA Technologies | CR | Agreement | Yes |
YesTitle inconsistency
-3G NR-DC
r1
| revised | No | R5‑202648 | |
| R5‑202648 | Addition of NRDC RRC TC 8.2.2.4.2 | Qualcomm CDMA Technologies | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201648 | |||
| R5‑201649 | Addition of NRDC RRC TC 8.2.2.5.2 | Qualcomm CDMA Technologies | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202649 | |||
| R5‑202649 | Addition of NRDC RRC TC 8.2.2.5.2 | Qualcomm CDMA Technologies | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201649 | |||
| 6.3.2.4.4.1.3 | RRC Measurement Configuration Control and Reporting (clause 8.1.3) | R5‑201704 | Correction to NR TC 8.1.3.1.15a-Intra NR measurements with Blacklisting | Huawei, HiSilicon, Datang Linktester, MCC TF 160 | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202637 | |
| R5‑202637 | Correction to NR TC 8.1.3.1.15a-Intra NR measurements with Blacklisting | Huawei, HiSilicon, Datang Linktester, MCC TF 160 | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201704 | |||
| R5‑201944 | Correction to NR TC 8.1.3.2.4-SINR event B2 | Huawei, Hisilicon | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202638 | |||
| R5‑202638 | Correction to NR TC 8.1.3.2.4-SINR event B2 | Huawei, Hisilicon | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201944 | |||
| R5‑202183 | Editorial update to NR measurements test case 8.1.3.1.2 | Qualcomm Incorporated | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| 6.3.2.4.4.2.2 | RRC Radio Bearer (clause 8.2.2) | R5‑202411 | Correction to EN-DC RRC test case 8.2.2.1.1 | Keysight Technologies UK, Mediatek Inc | CR | Agreement | Yes |
Yes
| agreed | No | ||
| 6.3.2.4.4.1.3 | RRC Measurement Configuration Control and Reporting (clause 8.1.3) | R5‑202530 | Correction to NR CA RRC test cases 8.1.3.1.18.x | Keysight Technologies UK | CR | Agreement | Yes |
Yeslate doc
| agreed | No | ||
| 6.3.2.4.4.1.4 | RRC Handover (clause 8.1.4) | R5‑201360 | Correction to NR TC 8.1.4.2.2.1-L2N handover | Huawei, Hisilicon, StarPoint, China Telecom | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202639 | |
| R5‑202639 | Correction to NR TC 8.1.4.2.2.1-L2N handover | Huawei, Hisilicon, StarPoint, China Telecom | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201360 | |||
| 6.3.2.4.4.2.3 | RRC Measurement / Handovers (clause 8.2.3) | R5‑201368 | Addition of NR TC 8.2.3.16.1-MeasConfig via SRB3 | Huawei, Hisilicon | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202650 | |
| R5‑202650 | Addition of NR TC 8.2.3.16.1-MeasConfig via SRB3 | Huawei, Hisilicon | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201368 | |||
| 6.3.2.4.4.1.4 | RRC Handover (clause 8.1.4) | R5‑201505 | Correction to NR5GC IRAT test case 8.1.4.2.1.1 | Keysight Technologies UK, China Telecom | CR | Agreement | Yes |
Yesr1
incorporated comments from MCC TF160.
| revised | No | R5‑202640 | |
| R5‑202640 | Correction to NR5GC IRAT test case 8.1.4.2.1.1 | Keysight Technologies UK, China Telecom | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201505 | |||
| 6.3.2.4.4.2.3 | RRC Measurement / Handovers (clause 8.2.3) | R5‑201579 | Corrections to NR measurement test cases 8.2.3.x | MCC TF160 | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202651 | |
| R5‑202651 | Corrections to NR measurement test cases 8.2.3.x | MCC TF160 | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201579 | |||
| R5‑201632 | Corrections to RRC TCs 8.2.3.1.1, 8.2.3.2.1, 8.2.3.3.1 and 8.2.3.12.1 | Qualcomm CDMA Technologies, Keysight Technologies, Anritsu | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| 6.3.2.4.4.1.4 | RRC Handover (clause 8.1.4) | R5‑201638 | Corrections to NR5G RRC TC 8.1.4.2.1.1 | Qualcomm CDMA Technologies | CR | Agreement | Yes |
Yes
| agreed | No | ||
| R5‑201645 | Corrections to NR5G RRC TC 8.1.4.1.2 | Qualcomm CDMA Technologies, Keysight Technologies | CR | Agreement | Yes |
Yeschanges are handled in Anritsu's CR R5-202114
| withdrawn | Yes | ||||
| R5‑201661 | Correction to inter-RAT handover test case 8.1.4.2.1.1 | China Telecommunications | CR | Agreement | Yes |
Yesr1
merged into R5-201360r1 from Huawei.
| revised | No | R5‑202527 | |||
| R5‑202527 | Correction to inter-RAT handover test case 8.1.4.2.1.1 | China Telecommunications | CR | Agreement | Yes |
Yes
| withdrawn | Yes | R5‑201661 | |||
| 6.3.2.4.4.2.3 | RRC Measurement / Handovers (clause 8.2.3) | R5‑201802 | Update of RRC TC 8.2.3.12.1 | Intertek | CR | Agreement | Yes |
Yes
| agreed | No | ||
| 6.3.2.4.4.1.4 | RRC Handover (clause 8.1.4) | R5‑201941 | Correction to inter-RAT handover test case 8.1.4.2.1.2 | China Telecommunications | CR | Agreement | Yes |
Yesr1
contains TC 2.2.1!
Coversheet fixes. Merged into Keys202156r2ight's R5-201505r1.
| revised | No | R5‑202528 | |
| R5‑202528 | Correction to inter-RAT handover test case 8.1.4.2.1.2 | China Telecommunications | CR | Agreement | Yes |
Yes
| withdrawn | Yes | R5‑201941 | |||
| 6.3.2.4.4.2.3 | RRC Measurement / Handovers (clause 8.2.3) | R5‑202048 | Corrections to EN-DC test case 8.2.3.12.1 | MCC TF160 | CR | Agreement | Yes |
Yes
| agreed | No | ||
| 6.3.2.4.4.1.4 | RRC Handover (clause 8.1.4) | R5‑202114 | Correction to NR RRC test case 8.1.4.1.2 to udpate the security | ANRITSU LTD, Qualcomm | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202641 | |
| R5‑202641 | Correction to NR RRC test case 8.1.4.1.2 to udpate the security | ANRITSU LTD, Qualcomm | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202114 | |||
| 6.3.2.4.4.2.3 | RRC Measurement / Handovers (clause 8.2.3) | R5‑202540 | Correction to NR TC 8.2.3.2.1 | StarPoint,Huawei, HiSilicon | CR | Agreement | Yes |
Yeslate doc
| agreed | No | ||
| 6.3.2.4.4.2.4 | RRC Carrier Aggregation (clause 8.2.4) | R5‑201326 | Correction to EN-DC Carrier Aggregation test case 8.2.4.1.1.1 | Keysight Technologies UK Ltd, Qualcomm Incorporated | CR | Agreement | Yes |
Yes
| agreed | No | ||
| 6.3.2.4.4.1.5 | RRC Others (clause 8.1.5) | R5‑201361 | Correction to NR TC 8.1.5.4.1-Reception of CounterCheck message by the UE | Huawei, HiSilicon, Keysight Technologies | CR | Agreement | Yes |
Yes
| agreed | No | ||
| R5‑201366 | Addition of NR TC 8.1.5.7.1-MCG RLC failure | Huawei, Hisilicon | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202642 | |||
| R5‑202642 | Addition of NR TC 8.1.5.7.1-MCG RLC failure | Huawei, Hisilicon | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201366 | |||
| R5‑201367 | Addition of NR TC 8.1.5.8.1-Connected state latency check | Huawei, Hisilicon | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| 6.3.2.4.4.2.4 | RRC Carrier Aggregation (clause 8.2.4) | R5‑201445 | Correction to NR TC 8.2.4.2.1.x-CA release | Huawei, Hisilicon | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202652 | |
| R5‑202652 | Correction to NR TC 8.2.4.2.1.x-CA release | Huawei, Hisilicon | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201445 | |||
| 6.3.2.4.4.1.5 | RRC Others (clause 8.1.5) | R5‑201473 | Addition of NR TC 8.1.5.2.3-On-demand SIB | Huawei, Hisilicon | CR | Agreement | Yes |
Yesmerged into R5-201563.
| withdrawn | Yes | ||
| R5‑201623 | Updates on RRC others TC 8.1.5.2.2 | TEOCO | CR | Agreement | Yes |
YesIncorrect Word file type, Clauses affected missing
Not '.doc' Word file
Source to TSG (R5) missing"
Offline comments from TF160.
r2
| revised | No | R5‑202643 | |||
| R5‑202643 | Updates on RRC others TC 8.1.5.2.2 | TEOCO | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201623 | |||
| R5‑201651 | Corrections to NR5G RRC TC 8.1.5.4.1 | Qualcomm CDMA Technologies, Keysight Technologies | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| 6.3.2.4.4.2.4 | RRC Carrier Aggregation (clause 8.2.4) | R5‑201719 | Corrections to EN-DC test case 8.2.4.3.1.1 | MCC TF160 | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202653 | |
| R5‑202653 | Corrections to EN-DC test case 8.2.4.3.1.1 | MCC TF160 | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201719 | |||
| 6.3.2.4.4.1.5 | RRC Others (clause 8.1.5) | R5‑201817 | Corrections to NR5G RRC TC 8.1.5.5.1 | Qualcomm CDMA Technologies | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202644 | |
| R5‑202644 | Corrections to NR5G RRC TC 8.1.5.5.1 | Qualcomm CDMA Technologies | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201817 | |||
| R5‑201913 | Update of RRC TC 8.1.5.6.5.1 | Intertek | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| 6.3.2.4.4.2.5 | RRC Reconfiguration / Radio Link Failure (clause 8.2.5) | |||||||||||
| 6.3.2.4.4.2.6 | RRC Others (clause 8.2.6) | R5‑201369 | Addition of NR TC 8.2.6.1.1-RLC failure | Huawei, Hisilicon | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202654 | |
| R5‑202654 | Addition of NR TC 8.2.6.1.1-RLC failure | Huawei, Hisilicon | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201369 | |||
| 6.3.2.4.5 | 5GS Mobility Management | |||||||||||
| 6.3.2.4.5.1 | MM Primary authentication and key agreement (clause 9.1.1) | R5‑201370 | Correction to NR TC 9.1.1.3-EAP abnormal | Huawei, Hisilicon | CR | Agreement | Yes |
Yesmerged into ZTE's R5-201951.
| withdrawn | Yes | ||
| R5‑201951 | Corrections to 5GC Test Case 9.1.1.3 | ZTE, CMCC, Huawei, Hisilicon | CR | Agreement | Yes |
Yesr1
merge with CR R5-201370.
| revised | No | R5‑202655 | |||
| R5‑202655 | Corrections to 5GC Test Case 9.1.1.3 | ZTE, CMCC, Huawei, Hisilicon | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201951 | |||
| 6.3.2.4.5.2 | MM Security mode control / Identification & Generic UE configuration update (clauses 9.1.2 / 9.1.3 & 9.1.4) | R5‑201507 | Correction to 5GMM test case 9.1.2.1 | Keysight Technologies UK | CR | Agreement | Yes |
Yesr1
Alternative change based on comments from MCC TF160.
| revised | No | R5‑202656 | |
| R5‑202656 | Correction to 5GMM test case 9.1.2.1 | Keysight Technologies UK | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201507 | |||
| R5‑201508 | Correction to 5GMM test case 9.1.4.1 | Keysight Technologies UK | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202657 | |||
| R5‑202657 | Correction to 5GMM test case 9.1.4.1 | Keysight Technologies UK | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201508 | |||
| 6.3.2.4.5.3 | MM Registration & De-registration (clauses 9.1.5 & 9.1.6) | R5‑201371 | Correction to NR TC 9.1.5.1.3-NSSAI handling | Huawei, Hisilicon, Datang Linktester | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202658 | |
| R5‑202658 | Correction to NR TC 9.1.5.1.3-NSSAI handling | Huawei, Hisilicon, Datang Linktester | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201371 | |||
| R5‑201372 | Correction to NR TC 9.1.5.1.2-Equivalent PLMN list handling | Huawei, Hisilicon | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑201373 | Correction to NR TC 9.1.5.1.9-Change of cell into a new tracking area | Huawei, Hisilicon | CR | Agreement | Yes |
Yesr2
| revised | No | R5‑202659 | |||
| R5‑202659 | Correction to NR TC 9.1.5.1.9-Change of cell into a new tracking area | Huawei, Hisilicon | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201373 | |||
| R5‑201626 | Correction to NR TC 9.1.6.1.3-Deregistration in new TA | Starpoint, TDIA | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202660 | |||
| R5‑202660 | Correction to NR TC 9.1.6.1.3-Deregistration in new TA | Starpoint, TDIA | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201626 | |||
| R5‑201643 | Corrections to NR5G NAS TC 9.1.6.1.3 | Qualcomm CDMA Technologies, Keysight Technologies | CR | Agreement | Yes |
YesMerged into R5-201626
| withdrawn | Yes | ||||
| R5‑201644 | Corrections to NR5G NAS TC 9.1.6.1.4 | Qualcomm CDMA Technologies, Keysight Technologies | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑201654 | Corrections to NR5G NAS TC 9.1.5.2.8 | Qualcomm CDMA Technologies, Rohde & Schwarz | CR | Agreement | Yes |
YesHuawei disagreed.
| withdrawn | Yes | ||||
| 6.3.2.4.5.4 | MM Service Request (clause 9.1.7) | R5‑201652 | Corrections to NR5G NAS TC 9.1.7.2 | Qualcomm CDMA Technologies, Keysight Technologies | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202661 | |
| R5‑202661 | Corrections to NR5G NAS TC 9.1.7.2 | Qualcomm CDMA Technologies, Keysight Technologies | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201652 | |||
| R5‑201953 | Correction to 5GMM test case 9.1.7.2 | Keysight Technologies UK | CR | Agreement | Yes |
Yesmerged in Qualcomm’s CR R5-201652.
| withdrawn | Yes | ||||
| R5‑202261 | Correction to test case 9.1.7.1 | MediaTek Inc. | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202662 | |||
| R5‑202662 | Correction to test case 9.1.7.1 | MediaTek Inc. | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202261 | |||
| R5‑202322 | Correction to test case 9.1.7.2 | MediaTek Inc. | CR | Agreement | Yes |
Yesmerged into R5-201652
| withdrawn | Yes | ||||
| 6.3.2.4.5.5 | MM SMS Over NAS (clause 9.1.8) | R5‑201509 | Correction to 5GMM SMS test case 9.1.8.1 | Keysight Technologies UK | CR | Agreement | No |
Yes
| withdrawn | Yes | ||
| R5‑202222 | Addition to 5GC SMS test case 9.1.8.2 | CATT, TDIA | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202663 | |||
| R5‑202663 | Addition to 5GC SMS test case 9.1.8.2 | CATT, TDIA | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202222 | |||
| 6.3.2.4.5.6 | Inter-system Mobility (clause 9.3) | R5‑201374 | Correction to NR TC 9.3.1.1-5GC to EPC | Huawei, Hisilicon, Datang Linktester | CR | Agreement | No |
Yes
| withdrawn | Yes | ||
| R5‑201375 | Correction to NR TC 9.3.1.3-Handling of EPC relevant parameters | Huawei, Hisilicon, Datang Linktester, MediaTek Inc. | CR | Agreement | Yes |
Yes
| revised | No | R5‑202535 | |||
| R5‑202535 | Correction to NR TC 9.3.1.3-Handling of EPC relevant parameters | Huawei, Hisilicon, Datang Linktester, MediaTek Inc. | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201375 | |||
| R5‑202323 | Correction to test case 9.3.1.3 | MediaTek Inc. | CR | Agreement | Yes |
Yesmerged into R5-201375.
| withdrawn | Yes | ||||
| 6.3.2.4.6 | 5GS Session Management | |||||||||||
| 6.3.2.4.6.1 | SM PDU session authentication and authorization (clause 10.1.1) | |||||||||||
| 6.3.2.4.6.2 | SM Network-requested PDU session modification & release (clauses 10.1.2 & 10.1.3) | R5‑201376 | Correction to NR TC 10.1.3.1-Reactivation Required | Huawei, Hisilicon | CR | Agreement | No |
Yes
| withdrawn | Yes | ||
| R5‑201629 | Correction to 5GC TC 10.1.3.2 | CAICT | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑202221 | Removal of 5GC test case 10.1.3.1 | CATT, TDIA, Huawei, Hisilicon | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| 6.3.2.4.6.3 | SM UE-requested PDU session establishment / modification & release (clauses 10.1.4 / 10.1.5 & 10.1.6) | R5‑201377 | Correction to NR TC 10.1.4.1-T3580 expiry | Huawei, Hisilicon, CATT, Rohde & Schwarz | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202664 | |
| R5‑202664 | Correction to NR TC 10.1.4.1-T3580 expiry | Huawei, Hisilicon, CATT, Rohde & Schwarz | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201377 | |||
| 6.3.2.4.7 | EN-DC Session Management | |||||||||||
| 6.3.2.4.8 | 5GS Multilayer and Services | |||||||||||
| 6.3.2.4.8.1 | EPS Fallback | R5‑201459 | Update of multilayer test case 11.1.5 | ZTE | CR | Agreement | Yes |
Yesno cl. aff.
r3
| revised | No | R5‑202665 | |
| R5‑202665 | Update of multilayer test case 11.1.5 | ZTE | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201459 | |||
| R5‑201460 | Update of multilayer test case 11.1.6 | ZTE | CR | Agreement | Yes |
Yesno cl. aff.
r2
| revised | No | R5‑202666 | |||
| R5‑202666 | Update of multilayer test case 11.1.6 | ZTE | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201460 | |||
| R5‑201469 | Update of multilayer test case 11.1.2 | ZTE | CR | Agreement | Yes |
Yesno cl. aff.
r1
| revised | No | R5‑202667 | |||
| R5‑202667 | Update of multilayer test case 11.1.2 | ZTE | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201469 | |||
| 6.3.2.4.8.2 | RAT Fallback | |||||||||||
| 6.3.2.4.8.3 | Unified Access Control (UAC) | R5‑201378 | Addition of new NR TC 11.3.1-UAC AI0-MTSI MO speech call-SMSoIP-Uplink User data transfer | Huawei, Hisilicon | CR | Agreement | Yes |
YesTF160: MO SMS is triggered in step 32, but is not admitted at this moment. After Sysinfo changeMO SMS is assumed without triggering again. How long will the trigger continue to live ? Do we have to trigger again ? Not in steps 35-42.
In step 34 'Short Message' should be used instead of 'Paging'. As in other such steps of the test case.
r1
| revised | No | R5‑202668 | |
| R5‑202668 | Addition of new NR TC 11.3.1-UAC AI0-MTSI MO speech call-SMSoIP-Uplink User data transfer | Huawei, Hisilicon | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201378 | |||
| R5‑201379 | Addition of new NR TC 11.3.5-UAC AI1-accessibility AC5-MMTEL-Video call | Huawei, Hisilicon | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑201633 | Addition of NR5G UAC TC 11.3.7 | Qualcomm CDMA Technologies | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑201634 | Addition of NR5G UAC TC 11.3.8 | Qualcomm CDMA Technologies | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202670 | |||
| R5‑202670 | Addition of NR5G UAC TC 11.3.8 | Qualcomm CDMA Technologies | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201634 | |||
| R5‑202220 | Update to UAC test case 11.3.4 | CATT, TDIA | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202671 | |||
| R5‑202671 | Update to UAC test case 11.3.4 | CATT, TDIA | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202220 | |||
| 6.3.2.4.8.4 | Emergency Services | R5‑202006 | Corrections to IMS Emergency Services TC 11.4.2 | Samsung | CR | Agreement | Yes |
Yescover date.
r1
| revised | No | R5‑202550 | |
| R5‑202550 | Corrections to IMS Emergency Services TC 11.4.2 | Samsung | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202006 | |||
| R5‑202007 | Introduction of new IMS Emergency TC 11.4.9 5GMM-DEREGISTERED.LIMITED-SERVICE No suitable cells in tracking area call | Samsung | CR | Agreement | Yes |
Yescover date.
r1
| revised | No | R5‑202551 | |||
| R5‑202551 | Introduction of new IMS Emergency TC 11.4.9 5GMM-DEREGISTERED.LIMITED-SERVICE No suitable cells in tracking area call | Samsung | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202007 | |||
| R5‑202008 | Introduction of new IMS emergency TC 11.4.10 5GMM-REGISTERED.NORMAL-SERVICE N26 interface not supported N1 to S1 | Samsung | CR | Agreement | Yes |
Yesoffline coments from TF160, the emergency number to dial is not anymore explicitly to be specified (not required by the TP).
r1
| revised | No | R5‑202672 | |||
| R5‑202672 | Introduction of new IMS emergency TC 11.4.10 5GMM-REGISTERED.NORMAL-SERVICE N26 interface not supported N1 to S1 | Samsung | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202008 | |||
| 6.3.2.5 | TS 38.523-2 | R5‑201381 | Addition of applicability for NR Idle TCs | Huawei, Hisilicon | CR | Agreement | Yes |
Yes
| agreed | No | ||
| R5‑201382 | Addition of applicability for NR RRC TCs | Huawei, Hisilicon | CR | Agreement | Yes |
Yesr2
| revised | No | R5‑202673 | |||
| R5‑202673 | Addition of applicability for NR RRC TCs | Huawei, Hisilicon | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201382 | |||
| R5‑201383 | Addition of applicability for NR Multi Layer TCs | Huawei, Hisilicon | CR | Agreement | Yes |
YesTF 160 wondered whether features such as MTSI MO speech call, MMTEL-Video call are mandatory for all 5GC UEs to support. Maybe applicability is incorrect.
r1
| revised | No | R5‑202674 | |||
| R5‑202674 | Addition of applicability for NR Multi Layer TCs | Huawei, Hisilicon | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201383 | |||
| R5‑201759 | Update of 5G-NR test cases applicability | Qualcomm Incorporated, ZTE, MediaTek Inc, ROHDE & SCHWARZ, CATT, TDIA, Motorola Mobility, MCC TF160 | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202675 | |||
| R5‑202675 | Update of 5G-NR test cases applicability | Qualcomm Incorporated, ZTE, MediaTek Inc, ROHDE & SCHWARZ, CATT, TDIA, Motorola Mobility, MCC TF160 | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201759 | |||
| R5‑202009 | Introduction of applicability for new 5G IMS emergency test cases and corrections | Samsung | CR | Agreement | Yes |
Yesoffline coments from TF160, add IR.92
r1
| revised | No | R5‑202676 | |||
| R5‑202676 | Introduction of applicability for new 5G IMS emergency test cases and corrections | Samsung | CR | Agreement | Yes |
Yesfirst agreed, then TC number fix needed.
| revised | No | R5‑203120 | R5‑202009 | ||
| R5‑203120 | Introduction of applicability for new 5G IMS emergency test cases and corrections | Samsung | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202676 | |||
| R5‑202141 | Addition of new test applicability for DRX TC 7.1.1.5.5 | NTT DOCOMO INC. | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| 6.3.2.6 | TS 38.523-3 | R5‑201496 | Adding IXIT for multiple PDN/PDU | Samsung | CR | Agreement | Yes |
YesDependent on outcome of discussion on handling multi PDUs and PDNs
| withdrawn | Yes | ||
| R5‑201581 | 5G Test Models updates | MCC TF160 | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202677 | |||
| R5‑202677 | 5G Test Models updates | MCC TF160 | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201581 | |||
| 6.3.2.7 | TS 34.229-1 | |||||||||||
| 6.3.2.8 | TS 34.229-2 | |||||||||||
| 6.3.2.9 | TS 34.229-3 | |||||||||||
| 6.3.2.10 | TS 34.229-5 (pCRs only) | R5‑201384 | Addition of NR TC 6.5-IMS Registration with refreshed ISIM parameter | Huawei, Hisilicon | pCR | Agreement | Yes |
Yesr1
| revised | No | R5‑202678 | |
| R5‑202678 | Addition of NR TC 6.5-IMS Registration with refreshed ISIM parameter | Huawei, Hisilicon | pCR | Agreement | Yes |
Yes
| approved | No | R5‑201384 | |||
| R5‑201385 | Addition of NR TC 6.6-IMS Re-registration after UE capability update | Huawei, Hisilicon | pCR | Agreement | Yes |
Yesr1
| revised | No | R5‑202679 | |||
| R5‑202679 | Addition of NR TC 6.6-IMS Re-registration after UE capability update | Huawei, Hisilicon | pCR | Agreement | Yes |
Yes
| approved | No | R5‑201385 | |||
| R5‑201386 | Addition of NR TC 6.7-IMS Registration_invalid MAC parameter | Huawei, Hisilicon | pCR | Agreement | Yes |
Yesr1
| revised | No | R5‑202680 | |||
| R5‑202680 | Addition of NR TC 6.7-IMS Registration_invalid MAC parameter | Huawei, Hisilicon | pCR | Agreement | Yes |
Yes
| approved | No | R5‑201386 | |||
| R5‑201387 | Addition of NR TC 6.8-IMS Registration_invalid Security-Server&SQN | Huawei, Hisilicon | pCR | Agreement | Yes |
Yesr1
| revised | No | R5‑202681 | |||
| R5‑202681 | Addition of NR TC 6.8-IMS Registration_invalid Security-Server&SQN | Huawei, Hisilicon | pCR | Agreement | Yes |
Yes
| approved | No | R5‑201387 | |||
| R5‑201388 | Addition of NR TC 6.9-IMS Subscription_503 Service Unavailable | Huawei, Hisilicon | pCR | Agreement | Yes |
Yesr2
| revised | No | R5‑202682 | |||
| R5‑202682 | Addition of NR TC 6.9-IMS Subscription_503 Service Unavailable | Huawei, Hisilicon | pCR | Agreement | Yes |
Yes
| approved | No | R5‑201388 | |||
| R5‑201389 | Addition of NR TC 7.5-MTSI MO Voice Call without preconditions | Huawei, Hisilicon | pCR | Agreement | Yes |
Yesr1
| revised | No | R5‑202683 | |||
| R5‑202683 | Addition of NR TC 7.5-MTSI MO Voice Call without preconditions | Huawei, Hisilicon | pCR | Agreement | Yes |
Yes
| approved | No | R5‑201389 | |||
| R5‑201390 | Addition of NR TC 7.6-MTSI MT Voice Call with preconditions | Huawei, Hisilicon | pCR | Agreement | Yes |
Yesr1
| revised | No | R5‑202684 | |||
| R5‑202684 | Addition of NR TC 7.6-MTSI MT Voice Call with preconditions | Huawei, Hisilicon | pCR | Agreement | Yes |
Yes
| approved | No | R5‑201390 | |||
| R5‑201391 | Addition of NR TC 7.7-MTSI MT Voice Call without preconditions | Huawei, Hisilicon | pCR | Agreement | Yes |
Yesr1
| revised | No | R5‑202685 | |||
| R5‑202685 | Addition of NR TC 7.7-MTSI MT Voice Call without preconditions | Huawei, Hisilicon | pCR | Agreement | Yes |
Yes
| approved | No | R5‑201391 | |||
| R5‑201461 | Re-writing test case 6.1 to follow PRD 13 | ROHDE & SCHWARZ | pCR | Approval | Yes |
Yesr1
| revised | No | R5‑202686 | |||
| R5‑202686 | Re-writing test case 6.1 to follow PRD 13 | ROHDE & SCHWARZ | pCR | Approval | Yes |
Yes
| approved | No | R5‑201461 | |||
| R5‑201462 | New optimized test case for initial IMS registration failures | ROHDE & SCHWARZ | pCR | Approval | Yes |
Yesr1
| revised | No | R5‑202687 | |||
| R5‑202687 | New optimized test case for initial IMS registration failures | ROHDE & SCHWARZ | pCR | Approval | Yes |
Yes
| approved | No | R5‑201462 | |||
| R5‑201463 | New optimized test case for IMS re-registration scenarios | ROHDE & SCHWARZ | pCR | Approval | Yes |
Yesr2
| revised | No | R5‑202688 | |||
| R5‑202688 | New optimized test case for IMS re-registration scenarios | ROHDE & SCHWARZ | pCR | Approval | Yes |
Yes
| approved | No | R5‑201463 | |||
| R5‑201464 | New optimized test case for IMS de-registration scenarios | ROHDE & SCHWARZ | pCR | Approval | Yes |
Yesr2
| revised | No | R5‑202689 | |||
| R5‑202689 | New optimized test case for IMS de-registration scenarios | ROHDE & SCHWARZ | pCR | Approval | Yes |
Yes
| approved | No | R5‑201464 | |||
| R5‑201465 | Addition of new test case 7.4 for MO Voice Call with preconditions at both originating and terminating UE | ROHDE & SCHWARZ | pCR | Approval | Yes |
Yesr2
| revised | No | R5‑202690 | |||
| R5‑202690 | Addition of new test case 7.4 for MO Voice Call with preconditions at both originating and terminating UE | ROHDE & SCHWARZ | pCR | Approval | Yes |
Yes
| approved | No | R5‑201465 | |||
| R5‑201466 | Corrections and extensions of the generic procedures for MO voice call over 5GS | ROHDE & SCHWARZ | pCR | Approval | Yes |
Yesr1
| revised | No | R5‑202691 | |||
| R5‑202691 | Corrections and extensions of the generic procedures for MO voice call over 5GS | ROHDE & SCHWARZ | pCR | Approval | Yes |
Yes
| approved | No | R5‑201466 | |||
| R5‑201467 | Addition of generic procedures for MT voice call over 5GS | ROHDE & SCHWARZ | pCR | Approval | Yes |
Yesr1
| revised | No | R5‑202692 | |||
| R5‑202692 | Addition of generic procedures for MT voice call over 5GS | ROHDE & SCHWARZ | pCR | Approval | Yes |
Yes
| approved | No | R5‑201467 | |||
| R5‑201760 | Adding references | ROHDE & SCHWARZ | pCR | Approval | Yes |
Yesr1
| revised | No | R5‑202693 | |||
| R5‑202693 | Adding references | ROHDE & SCHWARZ | pCR | Approval | Yes |
Yes
| approved | No | R5‑201760 | |||
| 6.3.2.11 | TS 36.508 | R5‑201426 | Correction to Table 4.4.3.3-20-SIB24 of LTE | Huawei, Hisilicon | CR | Agreement | Yes |
Yes
| agreed | No | ||
| R5‑201485 | Update table 4.6.6-8A | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑201497 | Updates to RRCConnectionReconfiguration for NR SCell addition, modification and release | Keysight Technologies UK, Qualcomm Incorporated | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑201658 | Correction to UECapabilityEnquiry in case of EN-DC interband CA | Qualcomm CDMA Technologies, Anritsu | CR | Agreement | Yes |
Yeschanges are redundant with R5-201657.
| withdrawn | Yes | ||||
| R5‑201659 | Correction to mobility control information elements | China Telecommunications | CR | Agreement | Yes |
Yesr2
| revised | No | R5‑202694 | |||
| R5‑202694 | Correction to mobility control information elements | China Telecommunications | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201659 | |||
| R5‑202227 | Addition of Default configuration of IE ReportConfigInterRAT for SFTD measurement | Huawei, Hisilicon | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑202695 | |||
| R5‑202695 | Addition of Default configuration of IE ReportConfigInterRAT for SFTD measurement | Huawei, Hisilicon | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202227 | |||
| 6.3.2.12 | TS 36.509 | |||||||||||
| 6.3.2.13 | TS 36.523-1 | |||||||||||
| 6.3.2.14 | TS 36.523-2 | |||||||||||
| 6.3.2.15 | TS 36.523-3 | |||||||||||
| 6.3.2.16 | TS 37.571-2 | |||||||||||
| 6.3.2.17 | TS 37.571-3 | |||||||||||
| 6.3.2.18 | TS 37.571-4 | |||||||||||
| 6.3.2.19 | TS 37.571-5 | |||||||||||
| 6.3.2.20 | Discussion Papers / Work Plan / TC lists | R5‑201486 | Discussion on handling multi PDUs and PDNs | Samsung | discussion | Discussion | Yes |
Yesr2
| revised | No | R5‑202696 | |
| R5‑202696 | Discussion on handling multi PDUs and PDNs | Samsung | discussion | Discussion | Yes |
YesRAN5 accepted updated proposals 1 & 2 with PICS based solution put forward in CRs - R5-202566, 2567 (Proposal 1); R5-202568, 2569, 2570, 2571, 2572 (Propsal 2). These CRs are technically endorsed by RAN5#87-e meeting. TF160 shall implement these technically endorsed CRs during summer and make TTCN available for SS vendors to execute and iron out any issues before agreeing them in RAN5#88.
Issue of current test definition not able to handle PDU/PND types with QoS different than those used for IMS and/or Internet hasn't been addressed in the updated proposals.Extensive IXIT provisions based mechanism proposed not acceptable to the meeting.Simpler solution needed. Samsung to lead post meeting offline discussion among interested companies. Aim is to find a flexible solution which can incorporate future services' test requirements without the need of complicated re-work of the test specs. Need a solution soon to minimize impact."
| noted | No | R5‑201486 | |||
| 6.3.3 | Rel-15 CA configurations (UID - 770064) LTE_CA_R15-UEConTest | |||||||||||
| 6.3.3.1 | TS 36.508 | |||||||||||
| 6.3.3.2 | TS 36.523-1 | |||||||||||
| 6.3.3.3 | TS 36.523-2 | R5‑201699 | Addition of Rel-15 capabilities of multiple CA in 36.523-2 | Huawei, HiSilicon | CR | Agreement | Yes |
YesWIC Rel15
r1
| revised | No | R5‑202697 | |
| R5‑202697 | Addition of Rel-15 capabilities of multiple CA in 36.523-2 | Huawei, HiSilicon | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201699 | |||
| 6.3.3.4 | TS 36.523-3 | |||||||||||
| 6.3.3.5 | Discussion Papers / Work Plan / TC lists | |||||||||||
| 6.3.4 | Add UE Power Class 2 to band 41 intra-band contiguous LTE Carrier Aggregation (UID - 780065) LTE_CA_C_B41_PC2-UEConTest | |||||||||||
| 6.3.4.1 | TS 36.523-1 | |||||||||||
| 6.3.4.2 | TS 36.523-2 | |||||||||||
| 6.3.4.3 | TS 36.523-3 | |||||||||||
| 6.3.4.4 | Discussion Papers / Work Plan / TC lists | |||||||||||
| 6.3.5 | Mission Critical Improvements (UID - 790052) MCImp-UEConTest | |||||||||||
| 6.3.5.1 | TS 36.579-1 | R5‑202357 | MCDATA Payload and Protected Payload Defaults | NIST | CR | Agreement | Yes |
Yes"Version inconsistency, WI code inconsistency
-3GU: 14.6.0 / CR coversheet: 14.6
-3GU: MCImp-UEConTest / CR coversheet: MCImp_UEConTest"
content was included into R5-201586r1.
| withdrawn | Yes | ||
| R5‑202358 | MCDATA FD Signalling Payload Defaults | NIST | CR | Agreement | Yes |
Yes"Version inconsistency, WI code inconsistency
-3GU: 14.6.0 / CR coversheet: 14.6
-3GU: MCImp-UEConTest / CR coversheet: MCImp_UEConTest"
content was included into R5-201586r1.
| withdrawn | Yes | ||||
| R5‑202359 | MSRP Messages for MCData | NIST | CR | Agreement | Yes |
Yes"Version inconsistency, WI code inconsistency
-3GU: 14.6.0 / CR coversheet: 14.6
-3GU: MCImp-UEConTest / CR coversheet: MCImp_UEConTest"
content was included into R5-201586r1.
| withdrawn | Yes | ||||
| R5‑202360 | SDP updates for MCVideo and MCData | NIST | CR | Agreement | Yes |
Yes"Version inconsistency, WI code inconsistency
-3GU: 14.6.0 / CR coversheet: 14.6
-3GU: MCImp-UEConTest / CR coversheet: MCImp_UEConTest"
r2
| revised | No | R5‑202698 | |||
| R5‑202698 | SDP updates for MCVideo and MCData | NIST | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202360 | |||
| R5‑202361 | SIP MESSAGE default updates | NIST | CR | Agreement | Yes |
Yes"Version inconsistency, WI code inconsistency
-3GU: 14.6.0 / CR coversheet: 14.6
-3GU: MCImp-UEConTest / CR coversheet: MCImp_UEConTest"
content was included into R5-201586r1.
| withdrawn | Yes | ||||
| R5‑202362 | MCData-Info Updates | NIST | CR | Agreement | Yes |
Yes"Version inconsistency, WI code inconsistency
-3GU: 14.6.0 / CR coversheet: 14.6
-3GU: MCImp-UEConTest / CR coversheet: MCImp_UEConTest"
content was included into R5-201586r1.
| withdrawn | Yes | ||||
| R5‑202363 | Default MCVideo Transmission Control Messages | NIST | CR | Agreement | Yes |
Yes"Version inconsistency, WI code inconsistency
-3GU: 14.6.0 / CR coversheet: 14.6
-3GU: MCImp-UEConTest / CR coversheet: MCImp_UEConTest"
r2
| revised | No | R5‑202699 | |||
| R5‑202699 | Default MCVideo Transmission Control Messages | NIST | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202363 | |||
| R5‑202364 | SIP 202 (Accepted) message default | NIST | CR | Agreement | Yes |
Yes"Version inconsistency, WI code inconsistency
-3GU: 14.6.0 / CR coversheet: 14.6
-3GU: MCImp-UEConTest / CR coversheet: MCImp_UEConTest"
r2
| revised | No | R5‑203001 | |||
| R5‑203001 | SIP 202 (Accepted) message default | NIST | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202364 | |||
| 6.3.5.2 | TS 36.579-2 | R5‑201709 | Broadcast calls over pre-established sessions | UPV/EHU, NEMERGENT | CR | Agreement | Yes |
Yes
| revised | No | R5‑202386 | |
| R5‑202367 | New MCPTT Test Case - 5.5 | NIST | CR | Agreement | Yes |
Yes"Version inconsistency, WI code inconsistency
-3GU: 14.6.0 / CR coversheet: 14.6
-3GU: MCImp-UEConTest / CR coversheet: MCImp_UEConTest"
| revised | No | R5‑202558 | |||
| R5‑202558 | New MCPTT Test Case - 5.5 | NIST | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202367 | |||
| R5‑202386 | Broadcast calls over pre-established sessions | UPV/EHU, NEMERGENT | CR | Agreement | Yes |
Yes"TDOC inconsistency, Version inconsistency
-3GU: R5-202368 / CR coversheet: R5-XXXXXX
-3GU: 14.6.0 / CR coversheet: 14.6"
| agreed | No | R5‑201709 | |||
| 6.3.5.3 | TS 36.579-3 | |||||||||||
| 6.3.5.4 | TS 36.579-4 | R5‑201711 | Update to applicability | UPV/EHU, NEMERGENT | CR | Agreement | Yes |
Yes
| revised | No | R5‑202388 | |
| R5‑202388 | Update to applicability | UPV/EHU, NEMERGENT | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑203002 | R5‑201711 | ||
| R5‑203002 | Update to applicability | UPV/EHU, NEMERGENT | CR | Agreement | Yes |
YesFirst agreed, then revised because wrong doc uploaded.
| revised | No | R5‑203112 | R5‑202388 | ||
| R5‑203112 | Update to applicability | UPV/EHU, NEMERGENT | CR | Agreement | Yes |
Yes
| agreed | No | R5‑203002 | |||
| 6.3.5.5 | TS 36.579-5 | |||||||||||
| 6.3.5.6 | TS 36.579-6 | R5‑201520 | MCVideo Test Case - 6.1.1.1 | NIST | pCR | Agreement | Yes |
Yesr1
| revised | No | R5‑203003 | |
| R5‑203003 | MCVideo Test Case - 6.1.1.1 | NIST | pCR | Agreement | Yes |
Yes
| approved | No | R5‑201520 | |||
| R5‑201521 | MCVideo Test Case - 6.1.1.2 | NIST | pCR | Agreement | Yes |
Yesr2
| revised | No | R5‑203004 | |||
| R5‑203004 | MCVideo Test Case - 6.1.1.2 | NIST | pCR | Agreement | Yes |
Yes
| approved | No | R5‑201521 | |||
| R5‑201522 | MCVideo Test Case - 6.1.1.3 | NIST | pCR | Agreement | Yes |
Yesr2
| revised | No | R5‑203005 | |||
| R5‑203005 | MCVideo Test Case - 6.1.1.3 | NIST | pCR | Agreement | Yes |
Yes
| approved | No | R5‑201522 | |||
| R5‑201523 | MCVideo Test Case - 6.1.1.4 | NIST | pCR | Agreement | Yes |
Yesr2
| revised | No | R5‑203006 | |||
| R5‑203006 | MCVideo Test Case - 6.1.1.4 | NIST | pCR | Agreement | Yes |
Yes
| approved | No | R5‑201523 | |||
| R5‑201524 | MCVideo Test Case - 6.1.1.5 | NIST | pCR | Agreement | Yes |
Yesr1
| revised | No | R5‑203007 | |||
| R5‑203007 | MCVideo Test Case - 6.1.1.5 | NIST | pCR | Agreement | Yes |
Yes
| approved | No | R5‑201524 | |||
| R5‑201525 | MCVideo Test Case - 6.1.1.6 | NIST | pCR | Agreement | Yes |
Yesr2
| revised | No | R5‑203008 | |||
| R5‑203008 | MCVideo Test Case - 6.1.1.6 | NIST | pCR | Agreement | Yes |
Yes
| approved | No | R5‑201525 | |||
| R5‑201526 | MCVideo Test Case - 6.1.1.7 | NIST | pCR | Agreement | Yes |
Yesr1
| revised | No | R5‑203009 | |||
| R5‑203009 | MCVideo Test Case - 6.1.1.7 | NIST | pCR | Agreement | Yes |
Yes
| approved | No | R5‑201526 | |||
| R5‑201527 | MCVideo Test Case - 6.1.1.8 | NIST | pCR | Agreement | Yes |
Yesr2
| revised | No | R5‑203010 | |||
| R5‑203010 | MCVideo Test Case - 6.1.1.8 | NIST | pCR | Agreement | Yes |
Yes
| approved | No | R5‑201527 | |||
| R5‑201528 | MCVideo Test Case - 6.1.1.9 | NIST | pCR | Agreement | Yes |
Yesr1
| revised | No | R5‑203011 | |||
| R5‑203011 | MCVideo Test Case - 6.1.1.9 | NIST | pCR | Agreement | Yes |
Yes
| approved | No | R5‑201528 | |||
| R5‑201529 | MCVideo Test Case - 6.1.1.10 | NIST | pCR | Agreement | Yes |
Yesr1
| revised | No | R5‑203012 | |||
| R5‑203012 | MCVideo Test Case - 6.1.1.10 | NIST | pCR | Agreement | Yes |
Yes
| approved | No | R5‑201529 | |||
| R5‑201530 | MCVideo Test Case - 6.1.1.11 | NIST | pCR | Agreement | Yes |
Yesr2
| revised | No | R5‑203013 | |||
| R5‑203013 | MCVideo Test Case - 6.1.1.11 | NIST | pCR | Agreement | Yes |
Yes
| approved | No | R5‑201530 | |||
| R5‑201531 | MCVideo Test Case - 6.1.1.12 | NIST | pCR | Agreement | Yes |
YesTest cases removed from WP
| withdrawn | Yes | ||||
| R5‑201532 | MCVideo Test Case - 6.1.1.13 | NIST | pCR | Agreement | Yes |
YesTest cases removed from WP
| withdrawn | Yes | ||||
| R5‑201533 | MCVideo Test Case - 6.1.2.1 | NIST | pCR | Agreement | Yes |
Yesr2
| revised | No | R5‑203014 | |||
| R5‑203014 | MCVideo Test Case - 6.1.2.1 | NIST | pCR | Agreement | Yes |
Yes
| approved | No | R5‑201533 | |||
| R5‑201534 | MCVideo Test Case - 6.1.2.2 | NIST | pCR | Agreement | Yes |
Yesr2
| revised | No | R5‑203015 | |||
| R5‑203015 | MCVideo Test Case - 6.1.2.2 | NIST | pCR | Agreement | Yes |
Yes
| approved | No | R5‑201534 | |||
| R5‑201535 | MCVideo Test Case - 6.1.2.3 | NIST | pCR | Agreement | Yes |
Yes
| revised | No | R5‑203100 | |||
| R5‑203100 | MCVideo Test Case - 6.1.2.3 | NIST | pCR | Agreement | Yes |
Yes
| approved | No | R5‑201535 | |||
| R5‑201536 | MCVideo Test Case - 6.1.2.4 | NIST | pCR | Agreement | Yes |
YesTest cases removed from WP
| withdrawn | Yes | ||||
| R5‑201537 | MCVideo Test Case - 6.1.2.5 | NIST | pCR | Agreement | Yes |
Yesr2
| revised | No | R5‑203016 | |||
| R5‑203016 | MCVideo Test Case - 6.1.2.5 | NIST | pCR | Agreement | Yes |
Yes
| approved | No | R5‑201537 | |||
| R5‑201538 | MCVideo Test Case - 6.2.1 | NIST | pCR | Agreement | Yes |
Yesr2
| revised | No | R5‑203017 | |||
| R5‑203017 | MCVideo Test Case - 6.2.1 | NIST | pCR | Agreement | Yes |
Yes
| approved | No | R5‑201538 | |||
| R5‑201539 | MCVideo Test Case - 6.2.2 | NIST | pCR | Agreement | Yes |
Yesr2
| revised | No | R5‑203018 | |||
| R5‑203018 | MCVideo Test Case - 6.2.2 | NIST | pCR | Agreement | Yes |
Yes
| approved | No | R5‑201539 | |||
| R5‑201540 | MCVideo Test Case - 6.2.3 | NIST | pCR | Agreement | Yes |
Yesr1
| revised | No | R5‑203019 | |||
| R5‑203019 | MCVideo Test Case - 6.2.3 | NIST | pCR | Agreement | Yes |
Yes
| approved | No | R5‑201540 | |||
| R5‑201541 | MCVideo Test Case - 6.2.4 | NIST | pCR | Agreement | Yes |
Yesr1
| revised | No | R5‑203020 | |||
| R5‑203020 | MCVideo Test Case - 6.2.4 | NIST | pCR | Agreement | Yes |
Yes
| approved | No | R5‑201541 | |||
| R5‑201542 | MCVideo Test Case - 6.2.5 | NIST | pCR | Agreement | Yes |
Yesr1
| revised | No | R5‑203021 | |||
| R5‑203021 | MCVideo Test Case - 6.2.5 | NIST | pCR | Agreement | Yes |
Yes
| approved | No | R5‑201542 | |||
| R5‑201543 | MCVideo Test Case - 6.2.6 | NIST | pCR | Agreement | Yes |
Yesr1
| revised | No | R5‑203022 | |||
| R5‑203022 | MCVideo Test Case - 6.2.6 | NIST | pCR | Agreement | Yes |
Yes
| approved | No | R5‑201543 | |||
| R5‑201544 | MCVideo Test Case - 6.2.7 | NIST | pCR | Agreement | Yes |
Yesr1
| revised | No | R5‑203023 | |||
| R5‑203023 | MCVideo Test Case - 6.2.7 | NIST | pCR | Agreement | Yes |
Yes
| approved | No | R5‑201544 | |||
| R5‑201545 | MCVideo Test Case - 6.2.8 | NIST | pCR | Agreement | Yes |
Yesr2
| revised | No | R5‑203024 | |||
| R5‑203024 | MCVideo Test Case - 6.2.8 | NIST | pCR | Agreement | Yes |
Yes
| approved | No | R5‑201545 | |||
| R5‑201546 | MCVideo Test Case - 6.3.1 | NIST | pCR | Agreement | Yes |
Yesr1
| revised | No | R5‑203025 | |||
| R5‑203025 | MCVideo Test Case - 6.3.1 | NIST | pCR | Agreement | Yes |
Yes
| approved | No | R5‑201546 | |||
| R5‑201547 | MCVideo Test Case - 6.3.2 | NIST | pCR | Agreement | Yes |
YesTest cases removed from WP
| withdrawn | Yes | ||||
| R5‑202349 | MCVideo Test Case - 5.1 | NIST | pCR | Agreement | Yes |
Yesr1
| revised | No | R5‑203026 | |||
| R5‑203026 | MCVideo Test Case - 5.1 | NIST | pCR | Agreement | Yes |
Yes
| approved | No | R5‑202349 | |||
| R5‑202350 | MCVideo Test Case - 5.2 | NIST | pCR | Agreement | Yes |
Yesr1
| revised | No | R5‑203027 | |||
| R5‑203027 | MCVideo Test Case - 5.2 | NIST | pCR | Agreement | Yes |
Yes
| approved | No | R5‑202350 | |||
| R5‑202351 | MCVideo Test Case - 5.3 | NIST | pCR | Agreement | Yes |
Yesr1
| revised | No | R5‑203028 | |||
| R5‑203028 | MCVideo Test Case - 5.3 | NIST | pCR | Agreement | Yes |
Yes
| approved | No | R5‑202351 | |||
| R5‑202352 | MCVideo Test Case - 5.4 and Removal of 5.5 | NIST | pCR | Agreement | Yes |
Yesr2
| revised | No | R5‑203029 | |||
| R5‑203029 | MCVideo Test Case - 5.4 and Removal of 5.5 | NIST | pCR | Agreement | Yes |
Yes
| approved | No | R5‑202352 | |||
| R5‑202366 | MCVideo Off-network Section Update | NIST | pCR | Agreement | Yes |
Yesr1
| revised | No | R5‑203030 | |||
| R5‑203030 | MCVideo Off-network Section Update | NIST | pCR | Agreement | Yes |
Yes
| approved | No | R5‑202366 | |||
| 6.3.5.7 | TS 36.579-7 | R5‑202325 | MCDATA TC 6.1.1 | NIST | pCR | Agreement | Yes |
Yes
| revised | No | R5‑203101 | |
| R5‑203101 | MCDATA TC 6.1.1 | NIST | pCR | Agreement | Yes |
Yes
| approved | No | R5‑202325 | |||
| R5‑202326 | MCDATA TC 6.1.2 | NIST | pCR | Agreement | Yes |
Yes
| revised | No | R5‑203102 | |||
| R5‑203102 | MCDATA TC 6.1.2 | NIST | pCR | Agreement | Yes |
Yes
| approved | No | R5‑202326 | |||
| R5‑202327 | MCDATA TC 6.1.3 | NIST | pCR | Agreement | Yes |
Yes
| revised | No | R5‑203103 | |||
| R5‑203103 | MCDATA TC 6.1.3 | NIST | pCR | Agreement | Yes |
Yes
| approved | No | R5‑202327 | |||
| R5‑202328 | MCDATA TC 6.1.4 | NIST | pCR | Agreement | Yes |
Yes
| revised | No | R5‑203104 | |||
| R5‑203104 | MCDATA TC 6.1.4 | NIST | pCR | Agreement | Yes |
Yes
| approved | No | R5‑202328 | |||
| R5‑202329 | MCDATA TC 6.1.5 | NIST | pCR | Agreement | Yes |
Yes
| revised | No | R5‑203105 | |||
| R5‑203105 | MCDATA TC 6.1.5 | NIST | pCR | Agreement | Yes |
Yes
| approved | No | R5‑202329 | |||
| R5‑202330 | MCDATA TC 6.1.6 | NIST | pCR | Agreement | Yes |
Yes
| revised | No | R5‑203106 | |||
| R5‑203106 | MCDATA TC 6.1.6 | NIST | pCR | Agreement | Yes |
Yes
| approved | No | R5‑202330 | |||
| R5‑202331 | MCDATA TC 6.1.7 | NIST | pCR | Agreement | Yes |
Yes
| revised | No | R5‑203107 | |||
| R5‑203107 | MCDATA TC 6.1.7 | NIST | pCR | Agreement | Yes |
Yes
| approved | No | R5‑202331 | |||
| R5‑202332 | MCDATA TC 6.1.8 | NIST | pCR | Agreement | Yes |
Yes
| revised | No | R5‑203108 | |||
| R5‑203108 | MCDATA TC 6.1.8 | NIST | pCR | Agreement | Yes |
Yes
| approved | No | R5‑202332 | |||
| R5‑202333 | MCDATA TC 6.1.9 | NIST | pCR | Agreement | Yes |
Yes
| revised | No | R5‑203109 | |||
| R5‑203109 | MCDATA TC 6.1.9 | NIST | pCR | Agreement | Yes |
Yes
| approved | No | R5‑202333 | |||
| R5‑202334 | MCDATA TC 6.1.10 | NIST | pCR | Agreement | Yes |
Yes
| revised | No | R5‑203110 | |||
| R5‑203110 | MCDATA TC 6.1.10 | NIST | pCR | Agreement | Yes |
Yes
| approved | No | R5‑202334 | |||
| R5‑202335 | MCDATA TC 6.1.11 | NIST | pCR | Agreement | Yes |
Yes
| revised | No | R5‑203111 | |||
| R5‑203111 | MCDATA TC 6.1.11 | NIST | pCR | Agreement | Yes |
Yes
| approved | No | R5‑202335 | |||
| R5‑202336 | MCDATA TC 6.1.12 | NIST | pCR | Agreement | Yes |
Yesr2
| revised | No | R5‑203031 | |||
| R5‑203031 | MCDATA TC 6.1.12 | NIST | pCR | Agreement | Yes |
Yes
| approved | No | R5‑202336 | |||
| R5‑202337 | MCDATA TC 6.2.1 | NIST | pCR | Agreement | Yes |
Yesr2
| revised | No | R5‑203032 | |||
| R5‑203032 | MCDATA TC 6.2.1 | NIST | pCR | Agreement | Yes |
Yes
| approved | No | R5‑202337 | |||
| R5‑202338 | MCDATA TC 6.2.2 | NIST | pCR | Agreement | Yes |
Yesr2
| revised | No | R5‑203033 | |||
| R5‑203033 | MCDATA TC 6.2.2 | NIST | pCR | Agreement | Yes |
Yes
| approved | No | R5‑202338 | |||
| R5‑202339 | MCDATA TC 6.2.3 | NIST | pCR | Agreement | Yes |
Yesr2
| revised | No | R5‑203034 | |||
| R5‑203034 | MCDATA TC 6.2.3 | NIST | pCR | Agreement | Yes |
Yes
| approved | No | R5‑202339 | |||
| R5‑202340 | MCDATA TC 6.2.4 | NIST | pCR | Agreement | Yes |
Yesr2
| revised | No | R5‑203035 | |||
| R5‑203035 | MCDATA TC 6.2.4 | NIST | pCR | Agreement | Yes |
Yes
| approved | No | R5‑202340 | |||
| R5‑202341 | MCDATA TC 6.2.5 | NIST | pCR | Agreement | Yes |
Yesr2
| revised | No | R5‑203036 | |||
| R5‑203036 | MCDATA TC 6.2.5 | NIST | pCR | Agreement | Yes |
Yes
| approved | No | R5‑202341 | |||
| R5‑202342 | MCDATA TC 6.2.6 | NIST | pCR | Agreement | Yes |
Yesr2
| revised | No | R5‑203037 | |||
| R5‑203037 | MCDATA TC 6.2.6 | NIST | pCR | Agreement | Yes |
Yes
| approved | No | R5‑202342 | |||
| R5‑202343 | MCDATA TC 6.2.7 | NIST | pCR | Agreement | Yes |
Yesr2
| revised | No | R5‑203038 | |||
| R5‑203038 | MCDATA TC 6.2.7 | NIST | pCR | Agreement | Yes |
Yes
| approved | No | R5‑202343 | |||
| R5‑202344 | MCDATA TC 6.2.8 | NIST | pCR | Agreement | Yes |
Yesr2
| revised | No | R5‑203039 | |||
| R5‑203039 | MCDATA TC 6.2.8 | NIST | pCR | Agreement | Yes |
Yes
| approved | No | R5‑202344 | |||
| R5‑202345 | MCDATA TC 6.2.9 | NIST | pCR | Agreement | Yes |
Yesr2
| revised | No | R5‑203040 | |||
| R5‑203040 | MCDATA TC 6.2.9 | NIST | pCR | Agreement | Yes |
Yes
| approved | No | R5‑202345 | |||
| R5‑202346 | MCDATA TC 6.2.10 | NIST | pCR | Agreement | Yes |
Yesr2
| revised | No | R5‑203041 | |||
| R5‑203041 | MCDATA TC 6.2.10 | NIST | pCR | Agreement | Yes |
Yes
| approved | No | R5‑202346 | |||
| R5‑202347 | MCDATA TC 6.2.11 | NIST | pCR | Agreement | Yes |
Yesr2
| revised | No | R5‑203042 | |||
| R5‑203042 | MCDATA TC 6.2.11 | NIST | pCR | Agreement | Yes |
Yes
| approved | No | R5‑202347 | |||
| R5‑202348 | MCDATA TC 6.2.12 | NIST | pCR | Agreement | Yes |
Yesr2
| revised | No | R5‑203043 | |||
| R5‑203043 | MCDATA TC 6.2.12 | NIST | pCR | Agreement | Yes |
Yes
| approved | No | R5‑202348 | |||
| R5‑202353 | MCDATA TC 5.1 | NIST | pCR | Agreement | Yes |
Yesr2
| revised | No | R5‑203044 | |||
| R5‑203044 | MCDATA TC 5.1 | NIST | pCR | Agreement | Yes |
Yes
| approved | No | R5‑202353 | |||
| R5‑202354 | MCDATA TC 5.2 | NIST | pCR | Agreement | Yes |
Yesr2
| revised | No | R5‑203045 | |||
| R5‑203045 | MCDATA TC 5.2 | NIST | pCR | Agreement | Yes |
Yes
| approved | No | R5‑202354 | |||
| R5‑202355 | MCDATA TC 5.3 | NIST | pCR | Agreement | Yes |
Yesr2
| revised | No | R5‑203046 | |||
| R5‑203046 | MCDATA TC 5.3 | NIST | pCR | Agreement | Yes |
Yes
| approved | No | R5‑202355 | |||
| R5‑202356 | MCDATA TC 5.4 | NIST | pCR | Agreement | Yes |
Yesr2
| revised | No | R5‑203047 | |||
| R5‑203047 | MCDATA TC 5.4 | NIST | pCR | Agreement | Yes |
Yes
| approved | No | R5‑202356 | |||
| R5‑202365 | MCData Off-network Section Update | NIST | pCR | Agreement | Yes |
Yesr1
| revised | No | R5‑203048 | |||
| R5‑203048 | MCData Off-network Section Update | NIST | pCR | Agreement | Yes |
Yes
| approved | No | R5‑202365 | |||
| 6.3.5.8 | TS 36.508 | |||||||||||
| 6.3.5.9 | TS 36.509 | |||||||||||
| 6.3.5.10 | TS 36.523-1 | |||||||||||
| 6.3.5.11 | TS 36.523-2 | |||||||||||
| 6.3.5.12 | TS 36.523-3 | |||||||||||
| 6.3.5.13 | Discussion Papers / Work Plan / TC lists | |||||||||||
| 6.3.6 | Rel-16 LTE CA configurations (UID - 810061) LTE_CA_R16-UEConTest | |||||||||||
| 6.3.6.1 | TS 36.508 | |||||||||||
| 6.3.6.2 | TS 36.523-1 | |||||||||||
| 6.3.6.3 | TS 36.523-2 | |||||||||||
| 6.3.6.4 | TS 36.523-3 | |||||||||||
| 6.3.6.5 | Discussion Papers / Work Plan / TC lists | |||||||||||
| 6.3.7 | Shortened TTI and processing time for LTE (UID - 820064) LTE_sTTIandPT-UEConTest | |||||||||||
| 6.3.7.1 | TS 36.508 | R5‑201888 | Addition of Common Test Environment for short TTI and short processing time | Huawei,Hisilicon | CR | Agreement | Yes |
Yesr2
| revised | No | R5‑203049 | |
| R5‑203049 | Addition of Common Test Environment for short TTI and short processing time | Huawei,Hisilicon | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201888 | |||
| 6.3.7.2 | TS 36.509 | |||||||||||
| 6.3.7.3 | TS 36.523-1 | R5‑201876 | Addition of 7.1.3.18 Correct DL HARQ handling for short TTI | Huawei,Hisilicon | CR | Agreement | Yes |
Yes
| revised | No | R5‑203080 | |
| R5‑203080 | Addition of 7.1.3.18 Correct DL HARQ handling for short TTI | Huawei,Hisilicon | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201876 | |||
| R5‑201877 | Addition of 7.1.3.19 HARQ sharing between PDSCH and sPDSCH | Huawei,Hisilicon | CR | Agreement | Yes |
Yes
| revised | No | R5‑203081 | |||
| R5‑203081 | Addition of 7.1.3.19 HARQ sharing between PDSCH and sPDSCH | Huawei,Hisilicon | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201877 | |||
| R5‑201878 | Addition of 7.1.3.20 Multiplexing of sPDCCH and sPDSCH | Huawei,Hisilicon | CR | Agreement | Yes |
Yes
| revised | No | R5‑203082 | |||
| R5‑203082 | Addition of 7.1.3.20 Multiplexing of sPDCCH and sPDSCH | Huawei,Hisilicon | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201878 | |||
| R5‑201879 | Addition of 7.1.3.21 Correct DL assignment with DMRS sharing for short TTI | Huawei,Hisilicon | CR | Agreement | Yes |
Yes
| revised | No | R5‑203083 | |||
| R5‑203083 | Addition of 7.1.3.21 Correct DL assignment with DMRS sharing for short TTI | Huawei,Hisilicon | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201879 | |||
| R5‑201880 | Addition of 7.1.3.22 Correct DL HARQ handling with short processing time | Huawei,Hisilicon | CR | Agreement | Yes |
Yesr2
| revised | No | R5‑203050 | |||
| R5‑203050 | Addition of 7.1.3.22 Correct DL HARQ handling with short processing time | Huawei,Hisilicon | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201880 | |||
| R5‑201881 | Addition of 7.1.4.37 Correct UL HARQ handling with short processing time | Huawei,Hisilicon | CR | Agreement | Yes |
Yesr2
| revised | No | R5‑203051 | |||
| R5‑203051 | Addition of 7.1.4.37 Correct UL HARQ handling with short processing time | Huawei,Hisilicon | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201881 | |||
| R5‑201882 | Addition of 7.1.4.38 Correct UL HARQ handling for short TTI | Huawei,Hisilicon | CR | Agreement | Yes |
Yes
| revised | No | R5‑203084 | |||
| R5‑203084 | Addition of 7.1.4.38 Correct UL HARQ handling for short TTI | Huawei,Hisilicon | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201882 | |||
| R5‑201883 | Addition of 7.1.4.39 Correct UL assignment with DMRS sharing for short TTI | Huawei,Hisilicon | CR | Agreement | Yes |
Yesr2
| revised | No | R5‑203052 | |||
| R5‑203052 | Addition of 7.1.4.39 Correct UL assignment with DMRS sharing for short TTI | Huawei,Hisilicon | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201883 | |||
| R5‑201884 | Addition of 7.1.4.40 Scheduling requests on sPUCCH | Huawei,Hisilicon | CR | Agreement | Yes |
Yes
| revised | No | R5‑203085 | |||
| R5‑203085 | Addition of 7.1.4.40 Scheduling requests on sPUCCH | Huawei,Hisilicon | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201884 | |||
| R5‑201885 | Addition of 7.1.4.41 HARQ sharing between PUSCH and sPUSCH | Huawei,Hisilicon | CR | Agreement | Yes |
Yesr2
| revised | No | R5‑203053 | |||
| R5‑203053 | Addition of 7.1.4.41 HARQ sharing between PUSCH and sPUSCH | Huawei,Hisilicon | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201885 | |||
| R5‑201886 | Addition of 8.2.2.11 Aperiodic SRS with short processing time | Huawei,Hisilicon | CR | Agreement | Yes |
Yes
| revised | No | R5‑203086 | |||
| R5‑203086 | Addition of 8.2.2.11 Aperiodic SRS with short processing time | Huawei,Hisilicon | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201886 | |||
| R5‑201887 | Addition of 8.2.2.12 Aperiodic SRS for short TTI | Huawei,Hisilicon | CR | Agreement | Yes |
Yesr2
| revised | No | R5‑203054 | |||
| R5‑203054 | Addition of 8.2.2.12 Aperiodic SRS for short TTI | Huawei,Hisilicon | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201887 | |||
| 6.3.7.4 | TS 36.523-2 | R5‑202526 | Addition of test applicability for short TTI test cases | Huawei, Hisilicon | CR | Agreement | Yes |
Yeslate doc
r1
| revised | No | R5‑203055 | |
| R5‑203055 | Addition of test applicability for short TTI test cases | Huawei, Hisilicon | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202526 | |||
| 6.3.7.5 | TS 36.523-3 | |||||||||||
| 6.3.7.6 | Discussion Papers / Work Plan / TC lists | |||||||||||
| 6.3.8 | Enhancing LTE CA Utilization (UID - 820066) LTE_euCA-UEConTest | |||||||||||
| 6.3.8.1 | TS 36.508 | |||||||||||
| 6.3.8.2 | TS 36.523-1 | |||||||||||
| 6.3.8.3 | TS 36.523-2 | |||||||||||
| 6.3.8.4 | Discussion Papers / Work Plan / TC lists | |||||||||||
| 6.3.9 | REL-16 NR CA and DC; and NR and LTE DC Configurations (UID-830083) NR_CADC_NR_LTE_DC_R16-UEConTest | |||||||||||
| 6.3.9.1 | TS 38.508-1 | R5‑201995 | Correction of test frequency tables for CA_n66B | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||
| R5‑201996 | Introduction of test frequencies for Rel-16 NR CA configuration CA_n66B and CA_n66(2A) in cl 6.2.3.4 | Ericsson | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑203056 | |||
| R5‑203056 | Introduction of test frequencies for Rel-16 NR CA configuration CA_n66B and CA_n66(2A) in cl 6.2.3.4 | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201996 | |||
| R5‑201998 | Introduction of test frequencies for NR band 26 for protocol testing | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| 6.3.9.2 | TS 38.508-2 | |||||||||||
| 6.3.9.3 | TS 38.523-1 | |||||||||||
| 6.3.9.4 | TS 38.523-2 | |||||||||||
| 6.3.9.5 | TS 38.523-3 | |||||||||||
| 6.3.9.6 | Discussion Papers / Work Plan / TC lists | |||||||||||
| 6.3.10 | LTE Advanced high power TDD UE (power class 2) for Rel-15 (UID - 850061) LTE_TDD_HPUE_R15-UEConTest | |||||||||||
| 6.3.10.1 | TS 36.523-1 | |||||||||||
| 6.3.10.2 | TS 36.523-2 | |||||||||||
| 6.3.10.3 | TS 36.523-3 | |||||||||||
| 6.3.10.4 | Discussion Papers / Work Plan / TC lists | |||||||||||
| 6.3.11 | New Rel-16 NR bands and extension of existing NR bands (UID - 850062) NR_bands_BW_R16-UEConTest | |||||||||||
| 6.3.11.1 | TS 38.508-1 | R5‑201997 | Introduction of test frequencies for NR band n26 | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||
| R5‑201999 | Correction of test frequency tables for NR band n29 | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑202000 | Correction of test frequency tables for NR band n48 | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑202001 | Correction of test frequency tables for NR band n65 | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑202002 | Addition of test frequencies for additional channel bandwidths for NR band n66 | Ericsson | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑203057 | |||
| R5‑203057 | Addition of test frequencies for additional channel bandwidths for NR band n66 | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202002 | |||
| 6.3.11.2 | TS 38.508-2 | |||||||||||
| 6.3.11.3 | TS 38.523-3 | |||||||||||
| 6.3.11.4 | Discussion Papers / Work Plan / TC lists | |||||||||||
| 6.3.12 | Further NB-IoT enhancements (UID – 860031) NB_IOTenh2-UEConTest | |||||||||||
| 6.3.12.1 | TS 36.508 | |||||||||||
| 6.3.12.2 | TS 36.509 | |||||||||||
| 6.3.12.3 | TS 36.523-1 | |||||||||||
| 6.3.12.4 | TS 36.523-2 | |||||||||||
| 6.3.12.5 | TS 36.523-3 | |||||||||||
| 6.3.12.6 | Discussion Papers / Work Plan / TC lists | |||||||||||
| 6.3.13 | Even further enhanced MTC for LTE (UID – 860032) LTE_eMTC4-UEConTest | |||||||||||
| 6.3.13.1 | TS 36.508 | |||||||||||
| 6.3.13.2 | TS 36.509 | |||||||||||
| 6.3.13.3 | TS 36.523-1 | R5‑202016 | Addition of new TC 23.1.3 CIoT Optimization / Control Plane / EDT | Ericsson | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑203058 | |
| R5‑203058 | Addition of new TC 23.1.3 CIoT Optimization / Control Plane / EDT | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202016 | |||
| 6.3.13.4 | TS 36.523-2 | R5‑202017 | Addition of applicability for eMTC4 | Ericsson | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑203059 | |
| R5‑203059 | Addition of applicability for eMTC4 | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202017 | |||
| 6.3.13.5 | TS 36.523-3 | |||||||||||
| 6.3.13.6 | Discussion Papers / Work Plan / TC lists | |||||||||||
| 6.3.14 | RF requirements for NR frequency range 1 (FR1) (UID-870061) NR_RF_FR1-UEConTest | |||||||||||
| 6.3.14.1 | TS 38.508-1 | |||||||||||
| 6.3.14.2 | TS 38.508-2 | |||||||||||
| 6.3.14.3 | TS 38.523-1 | |||||||||||
| 6.3.14.4 | TS 38.523-2 | |||||||||||
| 6.3.14.5 | TS 38.523-3 | |||||||||||
| 6.3.14.6 | Discussion Papers / Work Plan / TC lists | |||||||||||
| 6.4 | Routine Maintenance for TS 36 Series TEIx_Test | |||||||||||
| 6.4.1 | Routine Maintenance for TS 36.508 | |||||||||||
| 6.4.2 | Routine Maintenance for TS 36.509 | |||||||||||
| 6.4.3 | Routine Maintenance for TS 36.523-1 | |||||||||||
| 6.4.3.1 | Idle Mode | |||||||||||
| 6.4.3.2 | Layer 2 | |||||||||||
| 6.4.3.2.1 | MAC | |||||||||||
| 6.4.3.2.2 | RLC | |||||||||||
| 6.4.3.2.3 | PDCP | |||||||||||
| 6.4.3.3 | RRC | |||||||||||
| 6.4.3.3.1 | RRC Part 1 (clauses 8.1 and 8.5) | R5‑202545 | Addition of new RRC TC for checking extended / spare field handling in SI | NTT DOCOMO, INC. | CR | Agreement | Yes |
Yeslate doc
r3
| revised | No | R5‑203060 | |
| R5‑203060 | Addition of new RRC TC for checking extended / spare field handling in SI | NTT DOCOMO, INC. | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202545 | |||
| 6.4.3.3.2 | RRC Part 2 (clause 8.2) | R5‑202250 | Correction to LTE test case 8.2.4.1 for CAT-M1 UEs | ROHDE & SCHWARZ | CR | Agreement | Yes |
Yescomments from TF160.
Deferred.
r1
| revised | No | R5‑203061 | |
| R5‑203061 | Correction to LTE test case 8.2.4.1 for CAT-M1 UEs | ROHDE & SCHWARZ | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202250 | |||
| R5‑202251 | Correction to LTE test case 8.2.4.5 for Cat-M1 UEs | ROHDE & SCHWARZ | CR | Agreement | Yes |
Yescomments from TF160.
Deferred.
r1
| revised | No | R5‑203062 | |||
| R5‑203062 | Correction to LTE test case 8.2.4.5 for Cat-M1 UEs | ROHDE & SCHWARZ | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202251 | |||
| 6.4.3.3.3 | RRC Part 3 (clause 8.3) | R5‑201365 | Correction to LTE TC 8.3.3.1-LTE CGI | Huawei, Hisilicon | CR | Agreement | Yes |
Yeswrong WIC, is TEI_Test
r1
| revised | No | R5‑203063 | |
| R5‑203063 | Correction to LTE TC 8.3.3.1-LTE CGI | Huawei, Hisilicon | CR | Agreement | Yes |
YesWIC shall be TEI8!
| revised | No | R5‑203116 | R5‑201365 | ||
| R5‑203116 | Correction to LTE TC 8.3.3.1-LTE CGI | Huawei, Hisilicon | CR | Agreement | Yes |
Yes
| agreed | No | R5‑203063 | |||
| 6.4.3.3.4 | Inter-RAT (clauses 8.4 & 8.4A) | |||||||||||
| 6.4.3.3.5 | RRC LTE MDT (clause 8.6) | |||||||||||
| 6.4.3.3.6 | RRC ANR for UTRAN (clause 8.7) | |||||||||||
| 6.4.3.4 | EPS Mobility Management | R5‑201583 | Correction to LTE test case 9.2.1.1.7b | MCC TF160 | CR | Agreement | Yes |
Yes
| agreed | No | ||
| R5‑202139 | Modification of EMM Attach TC 9.2.1.1.1 for ignoring of spare and extended fields | NTT DOCOMO INC. | CR | Agreement | Yes |
Yes"CR accompanying discussion paper R5-202138.
During handling of R5-202138 RAN5 concluded update of NAS is not suitable to provide requested test coverage
DoCoMo to lead offline discussion on alternative solution and late tdoc to be issued once concluded"
| withdrawn | Yes | ||||
| R5‑202179 | Editorial update to EMM test case 9.2.1.1.1a | Qualcomm Incorporated | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑202181 | Editorial update to EMM test case 9.3.1.4 | Qualcomm Incorporated | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| 6.4.3.5 | EPS Session Management | |||||||||||
| 6.4.3.6 | General Tests | R5‑201584 | Updates to SMS over SGs test cases 11.1.5 and 11.1.6 | MCC TF160 | CR | Agreement | Yes |
Yes
| agreed | No | ||
| 6.4.3.7 | Interoperability Radio Bearers | |||||||||||
| 6.4.3.8 | Multilayer Procedures | R5‑202238 | Correction to LTE test case 13.3.1.3 for CAT-M1 UEs | ROHDE & SCHWARZ | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑203064 | |
| R5‑203064 | Correction to LTE test case 13.3.1.3 for CAT-M1 UEs | ROHDE & SCHWARZ | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202238 | |||
| 6.4.3.9 | PWS - ETWS / CMAS | |||||||||||
| 6.4.3.10 | Non-3GPP | |||||||||||
| 6.4.3.11 | Others (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...) | R5‑201582 | Correction to LTE Aerial UE test cases 8.9.4a and 8.9.5a | MCC TF160 | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑203065 | |
| R5‑203065 | Correction to LTE Aerial UE test cases 8.9.4a and 8.9.5a | MCC TF160 | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201582 | |||
| R5‑201762 | Specific message content update to NB-IoT test case 22.5.17 | Qualcomm Incorporated | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑202182 | Editorial update to NB-IoT test case 22.3.2.4 | Qualcomm Incorporated | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑202233 | Correction to NB-IoT test case 22.3.1.8 | ROHDE & SCHWARZ | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑202234 | Correction to NB-IoT test case 22.4.14 | ROHDE & SCHWARZ | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑202235 | Correction to NB-IoT test case 22.4.5 | ROHDE & SCHWARZ | CR | Agreement | Yes |
YesTF160 manager: there is already a NOTE 4.
r1
| revised | No | R5‑203066 | |||
| R5‑203066 | Correction to NB-IoT test case 22.4.5 | ROHDE & SCHWARZ | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202235 | |||
| R5‑202237 | Correction to NB-IoT test case 22.5.17 | ROHDE & SCHWARZ | CR | Agreement | Yes |
YesR5
covered in Qualcomm’s CR R5-201762.
| withdrawn | Yes | ||||
| R5‑202546 | Addition of new NB-IoT RRC TC for checking extended / spare field handling in SI | NTT DOCOMO, INC. | CR | Agreement | Yes |
Yeslate doc
r2
| revised | No | R5‑203067 | |||
| R5‑203067 | Addition of new NB-IoT RRC TC for checking extended / spare field handling in SI | NTT DOCOMO, INC. | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202546 | |||
| 6.4.4 | Routine Maintenance for TS 36.523-2 | R5‑201513 | Addition of TS36.523-2 CA Band 5A-29A and 2A-5A-29A | Sporton International Inc. | CR | Agreement | Yes |
YesTEI-
r1
| revised | No | R5‑203068 | |
| R5‑203068 | Addition of TS36.523-2 CA Band 5A-29A and 2A-5A-29A | Sporton International Inc. | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201513 | |||
| R5‑202019 | Updates to legacy TC applicability for feMTC | Ericsson | CR | Agreement | Yes |
Yesr1
TEI15->14.
| revised | No | R5‑203069 | |||
| R5‑203069 | Updates to legacy TC applicability for feMTC | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202019 | |||
| R5‑202184 | Addition of new PICs for UP-CIOT capability in NB-IoT with impact on applicability of TCs 22.3.3.5, 22.4.15 and 22.4.16 | Qualcomm Incorporated, Rohde & Schwarz | CR | Agreement | Yes |
Yesr2
| revised | No | R5‑203070 | |||
| R5‑203070 | Addition of new PICs for UP-CIOT capability in NB-IoT with impact on applicability of TCs 22.3.3.5, 22.4.15 and 22.4.16 | Qualcomm Incorporated, Rohde & Schwarz | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202184 | |||
| R5‑202547 | Addition of new RRC TC for checking extended / spare field handling in SI | NTT DOCOMO, INC. | CR | Agreement | Yes |
Yeslate doc
r1
| revised | No | R5‑203071 | |||
| R5‑203071 | Addition of new RRC TC for checking extended / spare field handling in SI | NTT DOCOMO, INC. | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202547 | |||
| R5‑202548 | Addition of new NB-IoT RRC TC for checking extended / spare field handling in SI | NTT DOCOMO, INC. | CR | Agreement | Yes |
Yeslate doc
r1
| revised | No | R5‑203072 | |||
| R5‑203072 | Addition of new NB-IoT RRC TC for checking extended / spare field handling in SI | NTT DOCOMO, INC. | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202548 | |||
| 6.4.5 | Routine Maintenance for TS 36.523-3 | |||||||||||
| 6.4.6 | Discussion Papers / Work Plan / TC lists | R5‑201621 | TS 36.523-1 Status before RAN5#87-e | Rapporteur (BlackBerry) | other | Information | Yes |
Yes
| noted | No | ||
| R5‑201622 | TS 36.523-1 Status after RAN5#87-e | Rapporteur (BlackBerry) | other | Information | Yes |
Yes
| noted | No | ||||
| R5‑202018 | Discussion paper on applicability of legacy test cases for Cat-M2 | Ericsson | discussion | Endorsement | Yes |
Yes"In Rel-14 test cases that are made applicable for both CAT M1 and CAT M2 may need prose update (TF!60)
Rel-14 applicability is dependent on FGI Bit (Qualcomm)
Above points need to be addressed before CR can be agreed"
| noted | No | ||||
| R5‑202138 | Discussion paper on the need for testing UE handling of extended and spare fields in SI | NTT DOCOMO INC. | discussion | Discussion | Yes |
YesProposal 1 accepted, exact solution to be worked out among RAN5 interested companies
Same requirement exists in NR so test coverage needed there as well. DoCoMo to work with Qualcomm on this
| noted | No | ||||
| 6.5 | Other Maintenance TEIx_Test | |||||||||||
| 6.5.1 | Routine Maintenance for TDD (HCR & LCR) | |||||||||||
| 6.5.1.1 | TS 34.108 | |||||||||||
| 6.5.1.2 | TS 34.123-1 | |||||||||||
| 6.5.1.3 | TS 34.123-2 | |||||||||||
| 6.5.1.4 | TS 34.123-3 | |||||||||||
| 6.5.1.5 | Discussion Papers / Work Plan / TC list & CR summary | |||||||||||
| 6.5.2 | Routine Maintenance for TS 34.108 | |||||||||||
| 6.5.3 | Routine Maintenance for TS 34.109 | |||||||||||
| 6.5.4 | Routine Maintenance for TS 34.123 | |||||||||||
| 6.5.4.1 | TS 34.123-1 | |||||||||||
| 6.5.4.2 | TS 34.123-2 | |||||||||||
| 6.5.4.3 | TS 34.123-3 | |||||||||||
| 6.5.5 | Discussion Papers / Work Plan / TC lists | |||||||||||
| 6.5.6 | Routine Maintenance for TS 34.229 | |||||||||||
| 6.5.6.1 | TS 34.229-1 | R5‑201447 | Adding Allow headers indicating support of UPDATE in Session Timer test cases | ROHDE & SCHWARZ, HiSilicon | CR | Agreement | Yes |
Yes
| agreed | No | ||
| R5‑201448 | Fixing mix-up of UE and SS in IMS test case 22.5 | ROHDE & SCHWARZ | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑201449 | Corrections to IMS Session Timer test case 22.7 | ROHDE & SCHWARZ, Samsung | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑201450 | Correction to the Request-URI of the ACK method | ROHDE & SCHWARZ, Samsung | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑201451 | Corrections for re-registration on V-PLMN and UTRAN | ROHDE & SCHWARZ, Qualcomm, Anritsu | CR | Agreement | No |
Yes
| withdrawn | Yes | ||||
| R5‑202165 | Update of speech call test case title | NTT DOCOMO INC., Rohde&Schwarz | CR | Agreement | Yes |
Yesadded R&S.
| revised | No | R5‑202532 | |||
| R5‑202532 | Update of speech call test case title | NTT DOCOMO INC., Rohde&Schwarz | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202165 | |||
| R5‑202223 | Corrections to XCAP test cases regarding rule elements | Qualcomm Incorporated | CR | Agreement | Yes |
Yes"Version inconsistency
-3GU: 15.3.0 / CR coversheet: 16.3.0"
reissued as R5-202502 because of wrong Rel.
R&S: Setting the active attribute to true in what the SS sends defeats the test purpose to request the UE to activate the service.
| withdrawn | Yes | ||||
| R5‑202502 | Corrections to XCAP test cases regarding rule elements | Qualcomm Incorporated | CR | Agreement | Yes |
Yes"Replaces 2223
R&S - Setting the active attribute to true in what the SS sends defeats the test purpose to request the UE to activate the service.
R&S notified 'flag' withdrawal"
| agreed | No | ||||
| 6.5.6.2 | TS 34.229-2 | R5‑202166 | Update test aplicability to reflect the change of test case title | NTT DOCOMO INC. | CR | Agreement | Yes |
Yesadded R&S
| revised | No | R5‑202533 | |
| R5‑202533 | Update test aplicability to reflect the change of test case title | NTT DOCOMO INC. | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202166 | |||
| 6.5.6.3 | TS 34.229-3 | R5‑201585 | Routine maintenance for TS 34.229-3 | MCC TF160 | CR | Agreement | Yes |
Yes
| agreed | No | ||
| 6.5.6.4 | TS 34.229-4 | |||||||||||
| 6.5.6.5 | Discussion Papers / Work Plan / TC lists | |||||||||||
| 6.5.7 | Routine Maintenance for TS 37.571 | |||||||||||
| 6.5.7.1 | TS 37.571-2 | |||||||||||
| 6.5.7.2 | TS 37.571-3 | R5‑201624 | Addition of missing ICS for OTDOA Measurements and E-CID Measurements | PCTEST Engineering Lab | CR | Agreement | Yes |
Yes
| agreed | No | ||
| 6.5.7.3 | TS 37.571-4 | |||||||||||
| 6.5.7.4 | TS 37.571-5 | |||||||||||
| 6.5.7.5 | Discussion Papers / Work Plan / TC lists | |||||||||||
| 6.5.8 | Routine Maintenance for TS 51.010 | |||||||||||
| 6.5.8.1 | TS 51.010-1 (Signalling) | |||||||||||
| 6.5.8.2 | TS 51.010-2 (Signalling) | |||||||||||
| 6.5.8.3 | TS 51.010-5 (Signalling) | |||||||||||
| 6.5.8.4 | TS 51.010-7 (Signalling) | |||||||||||
| 6.5.8.5 | Discussion Papers / Work Plan / TC list & CR summary | |||||||||||
| 6.5.9 | Routine Maintenance for MCPTT | |||||||||||
| 6.5.9.1 | TS 36.579-1 | R5‑201586 | Updates to MCX generic test procedures and default message contents | MCC TF160, UPV/EHU, Nemergent Solutions, NIST | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑203073 | |
| R5‑203073 | Updates to MCX generic test procedures and default message contents | MCC TF160, UPV/EHU, Nemergent Solutions, NIST | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201586 | |||
| R5‑201587 | Updates to generic test procedure for MCPTT Authorization/Configuration and Key Generation | MCC TF160 | CR | Agreement | Yes |
Yesr2
| revised | No | R5‑203074 | |||
| R5‑203074 | Updates to generic test procedure for MCPTT Authorization/Configuration and Key Generation | MCC TF160 | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201587 | |||
| R5‑202010 | Correcting core spec reference for APN requirements | Samsung | CR | Agreement | Yes |
Yescover date.
r1
| revised | No | R5‑202552 | |||
| R5‑202552 | Correcting core spec reference for APN requirements | Samsung | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202010 | |||
| 6.5.9.2 | TS 36.579-2 | R5‑201588 | Correction to MCPTT test case 5.1 | MCC TF160 | CR | Agreement | Yes |
YesCR coversheet: Corrections to MCPTT test case 5.1"
r1
| revised | No | R5‑203075 | |
| R5‑203075 | Correction to MCPTT test case 5.1 | MCC TF160 | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201588 | |||
| R5‑201589 | Correction to MCPTT test case 5.2 | MCC TF160 | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑201590 | Correction to MCPTT test case 6.1.1.7 | MCC TF160 | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑201591 | Correction to MCPTT test case 6.1.1.14 | MCC TF160 | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| R5‑201707 | Corrections to test case 6.1.1.1 | NEMERGENT | CR | Agreement | Yes |
Yes
| revised | No | R5‑202383 | |||
| R5‑201708 | Update to test case 6.1.1.2 | UPV/EHU, NEMERGENT | CR | Agreement | Yes |
Yesr1
| revised | No | R5‑203076 | |||
| R5‑203076 | Update to test case 6.1.1.2 | UPV/EHU, NEMERGENT | CR | Agreement | Yes |
YesFirst agreed, then revised because wrong doc uploaded.
| revised | No | R5‑203115 | R5‑201708 | ||
| R5‑203115 | Update to test case 6.1.1.2 | UPV/EHU, NEMERGENT | CR | Agreement | Yes |
Yes
| agreed | No | R5‑203076 | |||
| R5‑202368 | Updates for MCPTT Test Case 5.1 | NIST | CR | Agreement | Yes |
Yesthe content was included in R5-201588r1.
| withdrawn | Yes | ||||
| R5‑202383 | Corrections to test case 6.1.1.1 | NEMERGENT | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201707 | |||
| 6.5.9.3 | TS 36.579-3 | |||||||||||
| 6.5.9.4 | TS 36.579-4 | |||||||||||
| 6.5.9.5 | TS 36.579-5 | R5‑201592 | Routine maintenance for TS 36.579-5 | MCC TF160 | CR | Agreement | Yes |
Yesr2
| revised | No | R5‑203077 | |
| R5‑203077 | Routine maintenance for TS 36.579-5 | MCC TF160 | CR | Agreement | Yes |
Yes
| agreed | No | R5‑201592 | |||
| 6.5.9.6 | Other Specs | |||||||||||
| 6.5.9.7 | Discussion Papers / Work Plan / TC lists | R5‑201323 | Issues related to MCX initial registration: MCPTT user authentication | MCC TF160 | discussion | Endorsement | Yes |
Yes
| noted | No | ||
| R5‑201324 | Analysis of the MCPTT Service Authorization and Key Generation procedure | MCC TF160 | discussion | Endorsement | Yes |
Yes
| noted | No | ||||
| R5‑201593 | Test case verification using the IP-based Test Model | MCC TF160 | discussion | Endorsement | No |
Yeswas not produced.
| withdrawn | Yes | ||||
| 6.6 | Outgoing liaison statements for provisional approval | |||||||||||
| 6.7 | AOB | |||||||||||
| 7 | Closing Joint Session | |||||||||||
| 7.1 | Pointer CRs | |||||||||||
| 7.2 | Open Issues | |||||||||||
| 7.2.1 | RF group docs still requiring WG verdict/confirmation - original A.I. retained | |||||||||||
| 7.2.2 | Sig group docs still requiring WG verdict/confirmation - original A.I. retained | R5‑202258 | Aligning the tabular representation of ASN.1 with PRD13 sections 4.8 and 5 | Samsung, MCC TF160 | CR | Agreement | Yes |
YesSIG+RF!
cover date.
r1
| revised | No | R5‑202549 | |
| R5‑202549 | Aligning the tabular representation of ASN.1 with PRD13 sections 4.8 and 5 | Samsung, MCC TF160 | CR | Agreement | Yes |
Yes
| agreed | No | R5‑202258 | |||
| 7.2.3 | Other open issues from joint sessions - original A.I. retained | R5‑202553 | Issues with BeiDou GNSS scenarios | Spirent Communications | discussion | Discussion | Yes |
Yesway forward is accepted.
| noted | No | R5‑202023 | |
| 7.2.4 | UE Application Layer Data Throughput Performance - original A.I. retained | |||||||||||
| 7.2.5 | Other | R5‑202556 | RAN5 5G NR WAY FORWARD SA option 5 and NSA options 4 and 7 | RAN5 5GS WI leadership | discussion | discussion | Yes |
Yesway forward is endorsed
Will be included in the 5GS planning.
| noted | No | ||
| 7.3 | iWD/PRD Updates | R5‑201620 | PRD-17 on Guidance to Work Item Codes, version 3.20 (post RAN#88-e version) | Rapporteur (BlackBerry) | other | Approval | No |
Yespost meeting doc
| noted | No | ||
| R5‑202259 | Update of RAN5 PRD13 | Samsung | other | Approval | Yes |
Yesr1
| revised | No | R5‑202555 | |||
| R5‑202555 | Update of RAN5 PRD13 | Samsung | other | Approval | Yes |
Yes
| approved | No | R5‑202259 | |||
| 7.4 | Work Items/ Study Items | |||||||||||
| 7.4.1 | Final version of Work Item Proposals | |||||||||||
| 7.4.2 | Active Work Items/ Study Item: work plans (wp), status reports (sr), Work Item Descriptions (wid) | R5‑201313 | WI Progress and Target Completion Date Review | WG Chairman | other | Information | No |
Yes
| noted | No | ||
| R5‑201553 | WP UE Conformance Test Aspects - Rel-14 LTE CA configurations | Ericsson | Work Plan | Information | Yes |
Yes
| revised | No | R5‑203118 | |||
| R5‑203118 | WP UE Conformance Test Aspects - Rel-14 LTE CA configurations | Ericsson | Work Plan | Information | Yes |
Yes
| noted | No | R5‑201553 | |||
| R5‑201554 | SR UE Conformance Test Aspects - Rel-14 LTE CA configurations | Ericsson | WI status report | Information | Yes |
Yes
| revised | No | R5‑203119 | |||
| R5‑203119 | SR UE Conformance Test Aspects - Rel-14 LTE CA configurations | Ericsson | WI status report | Information | Yes |
Yes
| noted | No | R5‑201554 | |||
| R5‑201555 | WP UE Conformance Test Aspects - Rel-15 LTE CA configurations | Ericsson | Work Plan | Information | Yes |
Yes
| noted | No | ||||
| R5‑201556 | SR UE Conformance Test Aspects - Rel-15 LTE CA configurations | Ericsson | WI status report | Information | Yes |
Yes
| noted | No | ||||
| R5‑201557 | WP UE Conformance Test Aspects - Rel-16 LTE CA configurations | Ericsson | Work Plan | Information | Yes |
Yes
| noted | No | ||||
| R5‑201558 | SR UE Conformance Test Aspects - Rel-16 LTE CA configurations | Ericsson | WI status report | Information | Yes |
Yes
| noted | No | ||||
| R5‑201559 | WP UE Conformance Test Aspects - 5G system with NR and LTE | Ericsson | Work Plan | Information | No |
No
| reserved | No | ||||
| R5‑201560 | SR UE Conformance Test Aspects - 5G system with NR and LTE | Ericsson | WI status report | Information | No |
No
| reserved | No | ||||
| R5‑201563 | WP UE Conformance Test Aspects - New Rel-16 NR bands and extension of existing NR bands | Ericsson | Work Plan | Information | Yes |
Yes
| noted | No | ||||
| R5‑201564 | SR UE Conformance Test Aspects - New Rel-16 NR bands and extension of existing NR bands | Ericsson | WI status report | Information | Yes |
Yes
| noted | No | ||||
| R5‑201565 | Revised WID - New Rel-16 NR bands and extension of existing NR bands | Ericsson | SID revised | Information | Yes |
Yes
| endorsed | No | ||||
| R5‑201774 | SR - UE Conformance Test Aspects - Add UE Power Class 2 to band 41 intra-band contiguous LTE Carrier Aggregation | T-Mobile USA Inc. | WI status report | Endorsement | Yes |
Yes
| noted | No | ||||
| R5‑201775 | WP - UE Conformance Test Aspects - Add UE Power Class 2 to band 41 intra-band contiguous LTE Carrier Aggregation | T-Mobile USA Inc. | Work Plan | Endorsement | Yes |
Yes
| noted | No | ||||
| R5‑201864 | WP - Shortened TTI and processing time for LTE - Status after RAN5#87-e | Huawei, HiSilicon | Work Plan | Information | Yes |
Yes
| noted | No | ||||
| R5‑201865 | SR - Shortened TTI and processing time for LTE - Status after RAN5#87-e | Huawei, HiSilicon | WI status report | Information | Yes |
Yes
| noted | No | ||||
| R5‑201866 | WP - Rel-16 RF requirements for NR frequency range 1 - Status after RAN5#87-e | Huawei, HiSilicon | Work Plan | Information | No |
No
| reserved | No | ||||
| R5‑201867 | SR - Rel-16 RF requirements for NR frequency range 1 - Status after RAN5#87-e | Huawei, HiSilicon | WI status report | Information | No |
No
| reserved | No | ||||
| R5‑201914 | SR - NR_Rel-16_CA_DC after RAN5#87-e | CMCC | WI status report | Yes |
Yes
| noted | No | |||||
| R5‑201915 | WP - NR_Rel-16_CA_DC after RAN5#87-e | CMCC | Work Plan | Yes |
Yes
| noted | No | |||||
| R5‑201916 | Revised WID on UE Conformance Test Aspects - Rel-16 NR CA and DC; and NR and LTE DC Configurations | CMCC, Ericsson, China Unicom | WID revised | Approval | Yes |
Yesr1
| revised | No | R5‑202557 | |||
| R5‑202557 | Revised WID on UE Conformance Test Aspects - Rel-16 NR CA and DC; and NR and LTE DC Configurations | CMCC, Ericsson, China Unicom | WID revised | Approval | Yes |
Yesis endorsed.
| endorsed | No | R5‑201916 | |||
| R5‑201920 | SR - ENDC_UE_PC2_TDD_TDD after RAN5#87-e | CMCC | WI status report | Information | Yes |
Yes
| noted | No | ||||
| R5‑201921 | WP - ENDC_UE_PC2_TDD_TDD after RAN5#87-e | CMCC | Work Plan | Information | Yes |
Yes
| noted | No | ||||
| R5‑201922 | Revised WID ENDC_UE_PC2_TDD_TDD-UEConTest | CMCC | WID revised | Approval | Yes |
Yesis endorsed.
| approved | No | ||||
| R5‑202014 | WP UE Conformance Test Aspects - Even further enhanced MTC for LTE | Ericsson | Work Plan | Information | Yes |
Yes
| noted | No | ||||
| R5‑202015 | SR UE Conformance Test Aspects - Even further enhanced MTC for LTE | Ericsson | WI status report | Information | Yes |
Yes
| noted | No | ||||
| R5‑202167 | WP UE Conformance Test Aspects - Further NB-IoT enhancements | CATT | Work Plan | Information | Yes |
Yes
| noted | No | ||||
| R5‑202168 | SR UE Conformance Test Aspects - Further NB-IoT enhancements | CATT | WI status report | Information | Yes |
Yes
| noted | No | ||||
| R5‑202369 | SR - UE Conformance Test Aspects - Mission Critical Improvements (UID - 790052) MCImp-UEConTest | NIST | WI status report | Information | Yes |
Yes
| noted | No | ||||
| R5‑202370 | WP - UE Conformance Test Aspects - Mission Critical Improvements (UID - 790052) MCImp-UEConTest | NIST | Work Plan | Information | Yes |
Yes
| noted | No | ||||
| R5‑202371 | Revised WID - UE Conformance Test Aspects - Mission Critical Improvements (UID - 790052) MCImp-UEConTest | NIST | WID revised | Approval | No |
Yesnot needed for extension.
| withdrawn | Yes | ||||
| R5‑202372 | WP UE Conformance Test Aspects – Rel14 Enhanced Full Dimension MIMO for LTE | Ericsson | Work Plan | Information | Yes |
Yes
| noted | No | ||||
| R5‑202373 | SR UE Conformance Test Aspects – Rel14 Enhanced Full Dimension MIMO for LTE | Ericsson | WI status report | Information | Yes |
Yes
| noted | No | ||||
| R5‑202466 | Work Plan for TR 37.901-5 | Qualcomm Austria RFFE GmbH | Work Plan | Agreement | Yes |
Yes
| noted | No | ||||
| R5‑202467 | Status Report - Study on 5G NR UE Application Layer Data Throughput Performance | Qualcomm Austria RFFE GmbH | WI status report | Agreement | Yes |
Yes
| noted | No | ||||
| R5‑202480 | SR of Enhancing LTE CA Utilization WI for RAN5_87e | Nokia, Nokia Shanghai Bell | WI status report | Information | Yes |
Yes
| noted | No | ||||
| R5‑202481 | WP of Enhancing LTE CA Utilization WI for RAN5_87e | Nokia, Nokia Shanghai Bell | WI status report | Information | Yes |
Yes
| noted | No | ||||
| R5‑202507 | SR - Addition of Power Class 2 UE for LTE bands 31 and 72 | Airbus | WI status report | Information | Yes |
Yes
| noted | No | ||||
| R5‑202508 | WP - Addition of Power Class 2 UE for LTE bands 31 and 72 | Airbus | Work Plan | Information | Yes |
Yes
| noted | No | ||||
| R5‑202509 | WP - R15 TDD HPUE – Status after RAN5#87-e | Huawei, HiSilicon | Work Plan | Information | Yes |
Yes
| noted | No | ||||
| R5‑202510 | SR - R15 TDD HPUE – Status after RAN5#87-e | Huawei, HiSilicon | WI status report | Endorsement | Yes |
Yes
| noted | No | ||||
| 7.4.3 | Work Plan updates of recently closed work items | |||||||||||
| 7.5 | Docs still needing agreement/endorsement/approval (e.g. Outgoing LS, Reports, New Specs, Info for certification bodies etc.) | R5‑201458 | draft TS 34.229-5 v0.3.0 | ROHDE & SCHWARZ | draft TS | Approval | No |
Noavailable next week for review.
| for email approval | No | ||
| R5‑201550 | RAN5#87-e summary of changes to RAN5 test cases with potential impact on GCF and PTCRB | Ericsson, Samsung | report | Information | No |
Yes
| noted | No | ||||
| R5‑201552 | 3GPP RAN5 CA status list (post-RAN5#87-e meeting) | Ericsson | other | Information | Yes |
Yes
| noted | No | ||||
| R5‑201561 | 5GS progress report RAN5#87-e | Ericsson | WI status report | Information | No |
Yes
| noted | No | ||||
| R5‑201562 | Update of RAN5 5G NR phases and target update RAN5#87-e | Ericsson | discussion | Endorsement | No |
Yes
| noted | No | ||||
| R5‑202521 | MCC TF160 Status Report | MCC TF160 | report | Approval | No |
No
| reserved | No | R5‑201568 | |||
| R5‑201782 | FR2 Measurement Uncertainty (MU) / Test Tolerances (TT) Target Completion Update | AT&T | discussion | Discussion | Yes |
Yesis noted and forms part of the 5G NR WI progress report.
| noted | No | ||||
| R5‑202050 | draft TS 36.579-6 v0.3.0 | NIST | draft TS | Approval | No |
Nodeadline 20.6. 15:00
| reserved | No | ||||
| R5‑202051 | draft TS 36.579-7 v0.3.0 | NIST | draft TS | Approval | No |
Nodeadline 20.6. 15:00
| reserved | No | ||||
| R5‑202468 | draft TR 37.901-5 v1.2.0 | Qualcomm Austria RFFE GmbH | draft TR | Approval | No |
Yesdeadline 12.6. 15:00
| for email approval | No | ||||
| 7.6 | Confirmation of Future RAN5 Matters | R5‑201314 | Review deadlines for next quarter | WG Chairman | other | Information | Yes |
Yes
| noted | No | ||
| R5‑202522 | Critical prose CRs list for protocol test cases at RAN5#87-e | TSG WG RAN5 | LS out | Approval | No |
Yes(Olivier)
deadline 11.6. 15:00.
| for email approval | No | ||||
| R5‑202529 | Reply LS on suitability of validation transfers across 5G FR1 and FR2 and vice versa | TSG WG RAN5 | LS out | Approval | No |
Yesdeadline 12.6. 17:00
| for email approval | No | ||||
| 7.7 | AOB |