3GPP TDocs (written contributions) at meeting
Meeting: R3-103 - 2019-02-25 to 2019-03-01, Athens
meeting id: R3-103 (click id for more info on this meeting)Click on the Tdoc to open its file.
TDoc | Title | Source | Remarks |
---|---|---|---|
R3‑190001 | RAN3#103 Meeting Agenda | Chairman (Ericsson) | imported from 3GU |
R3‑190002 | RAN3#102 Meeting report | ETSI MCC | imported from 3GU |
R3‑190003 | TR 30.531 v1.33.0 Work Plan and Working Procedures - RAN WG3 | ETSI MCC | imported from 3GU |
R3‑190004 | Cooperation on Generic Slice Template definition | GSMA | imported from 3GU |
R3‑190005 | Reply LS on inclusion of selected PLMN into the complete message | CT WG1 | imported from 3GU |
R3‑190006 | Reply LS on RAN triggered PDU session split | CT WG4 | imported from 3GU |
R3‑190007 | Reporting All Cell IDs in 5G | ETSI TC LI | imported from 3GU |
R3‑190008 | Response to LS on redundant transmission for URLLC | RAN WG1 | imported from 3GU |
R3‑190009 | Reply LS on RAN Impact analysis due to TSN | RAN WG1 | imported from 3GU |
R3‑190010 | Reply LS on TSN requirements evaluation | RAN WG1 | imported from 3GU |
R3‑190011 | Reply LS on UP Integrity Protection for Small Data in Early Data Transfer | RAN WG2 | imported from 3GU |
R3‑190012 | LS on NR V2X agreements | RAN WG2 | imported from 3GU |
R3‑190013 | Reply LS on redundant transmission for URLLC | RAN WG2 | imported from 3GU |
R3‑190014 | Reply LS on supporting low latency and low jitter during handover procedure | RAN WG2 | imported from 3GU |
R3‑190015 | LS on DRB Integrity Protection | RAN WG2 | imported from 3GU |
R3‑190016 | LS on RAT selection for SL | RAN WG2 | imported from 3GU |
R3‑190017 | Reply LS on Location Service exposure to NG-RAN | RAN WG2 | imported from 3GU |
R3‑190018 | Reply LS to SA2 on QoS monitoring | RAN WG2 | imported from 3GU |
R3‑190019 | Reply LS on Interim conclusions for SA2 study on Radio Capabilities Signalling Optimisations (FS_RACS) | RAN WG2 | imported from 3GU |
R3‑190020 | LS on PARLOS RAN impacts | TSG RAN | imported from 3GU |
R3‑190021 | LS on FR1 range | TSG RAN | imported from 3GU |
R3‑190022 | LS on RAN1 NR UE features | TSG RAN | imported from 3GU |
R3‑190023 | Reply LS on RAN related parameters collected from UE | TSG RAN | imported from 3GU |
R3‑190024 | LS on finalisation of "2 Rx exception for RX vehicle mounted UE" Study | TSG RAN | imported from 3GU |
R3‑190025 | Reply-LS on Location Service exposure to NG-RAN | SA WG1 | imported from 3GU |
R3‑190026 | Reply LS on TSN requirements evaluation | SA WG1 | imported from 3GU |
R3‑190027 | Interim conclusions for SA2 study on Radio Capabilities Signalling Optimisations (FS_RACS) | SA WG2 | imported from 3GU |
R3‑190028 | Reply LS on Tx Profiles Provisioning | SA WG2 | imported from 3GU |
R3‑190029 | Reply LS on rejected PDU sessions | SA WG2 | imported from 3GU |
R3‑190030 | LS on 5G_URLLC | SA WG2 | imported from 3GU |
R3‑190031 | LS on PARLOS RAN impacts | SA WG2 | imported from 3GU |
R3‑190032 | Reply LS on the Unified Access Control over NG interface | SA WG2 | imported from 3GU |
R3‑190033 | LS reply to Reply LS on Location Service exposure to NG-RAN | SA WG2 | imported from 3GU |
R3‑190034 | LS on RAN related parameters collected from UE | SA WG2 | imported from 3GU |
R3‑190035 | LS on Collection of Slice Related Data Analytics from UEs | SA WG2 | imported from 3GU |
R3‑190036 | Combinations of Uu QoS characteristics values for V2X services | SA WG2 | imported from 3GU |
R3‑190037 | LS on RAN Impact analysis due to TSN | SA WG2 | imported from 3GU |
R3‑190038 | LS on RAN Impact analysis due to NPN | SA WG2 | imported from 3GU |
R3‑190039 | LS on Signalling optimization for RRC Inactive N3 path switch | SA WG2 | imported from 3GU |
R3‑190040 | Transfer of Iuant interface specification from 25-series to 37-series | ETSI MCC, Huawei, Ericsson | imported from 3GU |
R3‑190041 | Transfer of Iuant interface specification from 25-series to 37-series | ETSI MCC, Huawei, Ericsson | imported from 3GU |
R3‑190042 | Transfer of Iuant interface specification from 25-series to 37-series | ETSI MCC, Huawei, Ericsson | imported from 3GU |
R3‑190043 | Transfer of Iuant interface specification from 25-series to 37-series | ETSI MCC, Huawei, Ericsson | imported from 3GU |
R3‑190044 | Transfer of Iuant interface specification from 25-series to 37-series | ETSI MCC, Huawei, Ericsson | imported from 3GU |
R3‑190045 | Transfer of Iuant interface specification from 25-series to 37-series | ETSI MCC, Huawei, Ericsson | imported from 3GU |
R3‑190046 | Transfer of Iuant interface specification from 25-series to 37-series | ETSI MCC, Huawei, Ericsson | imported from 3GU |
R3‑190047 | Transfer of Iuant interface specification from 25-series to 37-series | ETSI MCC, Huawei, Ericsson | imported from 3GU |
R3‑190048 | Transfer of Iuant interface specification from 25-series to 37-series | ETSI MCC, Huawei, Ericsson | imported from 3GU |
R3‑190049 | Transfer of Iuant interface specification from 25-series to 37-series | ETSI MCC, Huawei, Ericsson | imported from 3GU |
R3‑190050 | Transfer of Iuant interface specification from 25-series to 37-series | ETSI MCC, Huawei, Ericsson | imported from 3GU |
R3‑190051 | Transfer of Iuant interface specification from 25-series to 37-series | ETSI MCC, Huawei, Ericsson | imported from 3GU |
R3‑190052 | Transfer of Iuant interface specification from 25-series to 37-series | ETSI MCC, Huawei, Ericsson | imported from 3GU |
R3‑190053 | Transfer of Iuant interface specification from 25-series to 37-series | ETSI MCC, Huawei, Ericsson | imported from 3GU |
R3‑190054 | Transfer of Iuant interface specification from 25-series to 37-series | ETSI MCC, Huawei, Ericsson | imported from 3GU |
R3‑190055 | Transfer of Iuant interface specification from 25-series to 37-series | ETSI MCC, Huawei, Ericsson | imported from 3GU |
R3‑190056 | Transfer of Iuant interface specification from 25-series to 37-series | ETSI MCC, Huawei, Ericsson | imported from 3GU |
R3‑190057 | Transfer of Iuant interface specification from 25-series to 37-series | ETSI MCC, Huawei, Ericsson | imported from 3GU |
R3‑190058 | Transfer of Iuant interface specification from 25-series to 37-series | ETSI MCC, Huawei, Ericsson | imported from 3GU |
R3‑190059 | Transfer of Iuant interface specification from 25-series to 37-series | ETSI MCC, Huawei, Ericsson | imported from 3GU |
R3‑190060 | Transfer of Iuant interface specification from 25-series to 37-series | ETSI MCC, Huawei, Ericsson | imported from 3GU |
R3‑190061 | Transfer of Iuant interface specification from 25-series to 37-series | ETSI MCC, Huawei, Ericsson | imported from 3GU |
R3‑190062 | Transfer of Iuant interface specification from 25-series to 37-series | ETSI MCC, Huawei, Ericsson | imported from 3GU |
R3‑190063 | Transfer of Iuant interface specification from 25-series to 37-series | ETSI MCC, Huawei, Ericsson | imported from 3GU |
R3‑190064 | Transfer of Iuant interface specification from 25-series to 37-series | ETSI MCC, Huawei, Ericsson | imported from 3GU |
R3‑190065 | Transfer of Iuant interface specification from 25-series to 37-series | ETSI MCC, Huawei, Ericsson | imported from 3GU |
R3‑190066 | Transfer of Iuant interface specification from 25-series to 37-series | ETSI MCC, Huawei, Ericsson | imported from 3GU |
R3‑190067 | Transfer of Iuant interface specification from 25-series to 37-series | ETSI MCC, Huawei, Ericsson | imported from 3GU |
R3‑190068 | Transfer of Iuant interface specification from 25-series to 37-series | ETSI MCC, Huawei, Ericsson | imported from 3GU |
R3‑190069 | Transfer of Iuant interface specification from 25-series to 37-series | ETSI MCC, Huawei, Ericsson | imported from 3GU |
R3‑190070 | Transfer of Iuant interface specification from 25-series to 37-series | ETSI MCC, Huawei, Ericsson | imported from 3GU |
R3‑190071 | Transfer of Iuant interface specification from 25-series to 37-series | ETSI MCC, Huawei, Ericsson | imported from 3GU |
R3‑190072 | Iuant interface: General aspects and principles | ETSI MCC, Huawei, Ericsson | imported from 3GU |
R3‑190073 | Iuant interface: General aspects and principles | ETSI MCC, Huawei, Ericsson | imported from 3GU |
R3‑190074 | Iuant interface: General aspects and principles | ETSI MCC, Huawei, Ericsson | imported from 3GU |
R3‑190075 | Iuant interface: General aspects and principles | ETSI MCC, Huawei, Ericsson | imported from 3GU |
R3‑190076 | Iuant interface: General aspects and principles | ETSI MCC, Huawei, Ericsson | imported from 3GU |
R3‑190077 | Iuant interface: General aspects and principles | ETSI MCC, Huawei, Ericsson | imported from 3GU |
R3‑190078 | Iuant interface: General aspects and principles | ETSI MCC, Huawei, Ericsson | imported from 3GU |
R3‑190079 | Iuant interface: General aspects and principles | ETSI MCC, Huawei, Ericsson | imported from 3GU |
R3‑190080 | Iuant interface: Layer 1 | ETSI MCC, Huawei, Ericsson | imported from 3GU |
R3‑190081 | Iuant interface: Layer 1 | ETSI MCC, Huawei, Ericsson | imported from 3GU |
R3‑190082 | Iuant interface: Layer 1 | ETSI MCC, Huawei, Ericsson | imported from 3GU |
R3‑190083 | Iuant interface: Layer 1 | ETSI MCC, Huawei, Ericsson | imported from 3GU |
R3‑190084 | Iuant interface: Layer 1 | ETSI MCC, Huawei, Ericsson | imported from 3GU |
R3‑190085 | Iuant interface: Layer 1 | ETSI MCC, Huawei, Ericsson | imported from 3GU |
R3‑190086 | Iuant interface: Layer 1 | ETSI MCC, Huawei, Ericsson | imported from 3GU |
R3‑190087 | Iuant interface: Layer 1 | ETSI MCC, Huawei, Ericsson | imported from 3GU |
R3‑190088 | Iuant interface: Signalling transport | ETSI MCC, Huawei, Ericsson | imported from 3GU |
R3‑190089 | Iuant interface: Signalling transport | ETSI MCC, Huawei, Ericsson | imported from 3GU |
R3‑190090 | Iuant interface: Signalling transport | ETSI MCC, Huawei, Ericsson | imported from 3GU |
R3‑190091 | Iuant interface: Signalling transport | ETSI MCC, Huawei, Ericsson | imported from 3GU |
R3‑190092 | Iuant interface: Signalling transport | ETSI MCC, Huawei, Ericsson | imported from 3GU |
R3‑190093 | Iuant interface: Signalling transport | ETSI MCC, Huawei, Ericsson | imported from 3GU |
R3‑190094 | Iuant interface: Signalling transport | ETSI MCC, Huawei, Ericsson | imported from 3GU |
R3‑190095 | Iuant interface: Signalling transport | ETSI MCC, Huawei, Ericsson | imported from 3GU |
R3‑190096 | Iuant Interface: Application Part | ETSI MCC, Huawei, Ericsson | imported from 3GU |
R3‑190097 | Iuant Interface: Application Part | ETSI MCC, Huawei, Ericsson | imported from 3GU |
R3‑190098 | Iuant Interface: Application Part | ETSI MCC, Huawei, Ericsson | imported from 3GU |
R3‑190099 | Iuant Interface: Application Part | ETSI MCC, Huawei, Ericsson | imported from 3GU |
R3‑190100 | Iuant Interface: Application Part | ETSI MCC, Huawei, Ericsson | imported from 3GU |
R3‑190101 | Iuant Interface: Application Part | ETSI MCC, Huawei, Ericsson | imported from 3GU |
R3‑190102 | Iuant Interface: Application Part | ETSI MCC, Huawei, Ericsson | imported from 3GU |
R3‑190103 | Iuant Interface: Application Part | ETSI MCC, Huawei, Ericsson | imported from 3GU |
R3‑190104 | Presentation of Specifications to TSG: TS 37.460 v1.N.0, TS 37.461 v1.N.0, TS 37.462 v1.N.0, TS 37.466 v1.N.0 (N=8/9/a/b/c/d/e/f) | ETSI MCC, Huawei, Ericsson | imported from 3GU |
R3‑190105 | Completion of Study on Cellular IoT support and evolution for the 5G System | SA WG2 | imported from 3GU |
R3‑190106 | LS on slice related Data Analytics | SA WG2 | imported from 3GU |
R3‑190107 | LS reply on PARLOS RAN impacts | SA WG2 | imported from 3GU |
R3‑190108 | LS on E-RAB establishment during inter-system handover from 5G to 4G | SA WG2 | imported from 3GU |
R3‑190109 | Reply LS on Notification Control during Handover | SA WG2 | imported from 3GU |
R3‑190110 | LS Response on Enforcement of maximum supported data rate for integrity protection | SA WG2 | imported from 3GU |
R3‑190111 | Reply LS on Interim conclusions for SA2 study on Radio Capabilities Signalling Optimisations (FS_RACS) | SA WG2 | imported from 3GU |
R3‑190112 | LS on support of piggybacking of NAS message while configuring a DRB | SA WG2 | imported from 3GU |
R3‑190113 | Reply LS on RAT selection for SL | SA WG2 | imported from 3GU |
R3‑190114 | LS on providing information on SLA fulfilment to NG-RAN | SA WG2 | imported from 3GU |
R3‑190115 | LS Response on Security Result Exchange Between NG-RAN and SMF in DC | SA WG2 | imported from 3GU |
R3‑190116 | Reply LS to S2-1811543 on NSSAI in the Access Stratum | SA WG3 | imported from 3GU |
R3‑190117 | Reply to LS on Security Result Exchange Between NG-RAN and SMF in DC | SA WG3 | imported from 3GU |
R3‑190118 | LS to RAN2/3 on EDT data integrity protection | SA WG3 | imported from 3GU |
R3‑190119 | Reporting All Cell IDs in 5G | SA WG3LI | imported from 3GU |
R3‑190120 | Reply LS on Attributes for QoE measurement collection | SA WG4 | imported from 3GU |
R3‑190121 | LS on Collection of Slice Related Data Analytics from UEs | SA WG4 | imported from 3GU |
R3‑190122 | Reply LS on QoS monitoring | SA WG5 | imported from 3GU |
R3‑190123 | LS on the slicing terminology and the role of S-NSSAI parameter | SA WG5 | imported from 3GU |
R3‑190124 | Reply LS on Attributes for QoE measurement collection | SA WG5 | imported from 3GU |
R3‑190125 | LS reply on Collection of Slice Related Data Analytics from UEs | SA WG5 | imported from 3GU |
R3‑190126 | LS on Reply on Reply LS on Slice related Data Analytics | SA WG5 | imported from 3GU |
R3‑190127 | LS reply on Attributes for QoE measurement collection | SA WG5 | imported from 3GU |
R3‑190128 | LS on PDCP end user throughput measurements | SA WG5 | imported from 3GU |
R3‑190129 | Further Discussion on Direct DF between 4G and 5G | ZTE | imported from 3GU |
R3‑190130 | Discussion on Inter-Operatability between 4G/5G Direct and Indirect DF | ZTE | imported from 3GU |
R3‑190131 | DraftLS on Inter-Operatability between 4G/5G Direct and Indirect DF | ZTE | imported from 3GU |
R3‑190132 | Text Proposal on support of sidelink resource allocation | LG Electronics | imported from 3GU |
R3‑190133 | Text Proposal on Service Authorization | LG Electronics | imported from 3GU |
R3‑190134 | Stage2 Corrections of Data Volume Report | ZTE | imported from 3GU |
R3‑190135 | Text Proposal on UE sidelink AMBR | LG Electronics | imported from 3GU |
R3‑190136 | TP for TR38.821 NTN Miscellaneous Corrections | ZTE | imported from 3GU |
R3‑190137 | TP for TR38.821 NTN Miscellaneous Corrections | ZTE | imported from 3GU |
R3‑190138 | Further Clarification of NTN Architecture Aspects | ZTE | imported from 3GU |
R3‑190139 | Tracking Area Management and Paging Handling in NTN | ZTE | imported from 3GU |
R3‑190140 | Further Discussion on Satellite Mobility Impacts on NTN Interfaces | ZTE | imported from 3GU |
R3‑190141 | Further Discussion on UE Mobility Scenarios in NTN | ZTE | imported from 3GU |
R3‑190142 | NGAP Corrections for UP Security Handling in DC during PDU Session Lifetime | ZTE | imported from 3GU |
R3‑190143 | Correction to RRC transfer | imported from 3GU | |
R3‑190144 | Correction to RRC transfer | imported from 3GU | |
R3‑190145 | XnAP Corrections for UP Security Handling in DC during PDU Session Lifetime | ZTE | imported from 3GU |
R3‑190146 | NGAP Usage Clarification of Maximum Integrity Protected Data Rate | ZTE | imported from 3GU |
R3‑190147 | XnAP Usage Clarification of S-NG-RAN Node Maximum Integrity Protected Data Rate | ZTE | imported from 3GU |
R3‑190148 | XnAP Usage Clarification of S-NG-RAN Node Maximum Integrity Protected Data Rate | ZTE | imported from 3GU |
R3‑190149 | Further Discussion on Rel-15 Signaling Extensibility for Multi-Connectivity | ZTE | imported from 3GU |
R3‑190150 | XnAP Corrections of TNL Info for Cell Groups | ZTE | imported from 3GU |
R3‑190151 | PSCell information for Lawful Interception | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑190152 | Transfer of the PSCell information for LI purposes | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑190153 | Transfer of the PSCell information for LI purposes | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑190154 | Transfer of the PSCell information for LI purposes | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑190155 | Information about S-RLF type | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑190156 | Transfer of the S-RLF type | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑190157 | Transfer of the S-RLF type | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑190158 | TEID change in case of key change | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑190159 | Extending DC causes for EN-DC | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑190160 | Enabling using Dual Connectivity cause values in EN-DC | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑190161 | Confusing definition of the desired buffer size for the NR UP | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑190162 | Correction of the interpretation of the desired buffer size | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑190163 | Equivalent Cell solution for NG-RAN sharing. | InterDigital Germany GmbH | imported from 3GU |
R3‑190164 | CR38.423 for clarification on RAN initiated PDU session splitting | ZTE | imported from 3GU |
R3‑190165 | CR37.340 for Correction on Xn address Indication | ZTE | imported from 3GU |
R3‑190166 | CR38.413 for Correction on DL NG-U TNL address modification by RAN node | ZTE | imported from 3GU |
R3‑190167 | Discussion on In-order delivery for MR-DC | ZTE | imported from 3GU |
R3‑190168 | CR37.340 for In-order delivery for MR-DC | ZTE | imported from 3GU |
R3‑190169 | Consideration on UE Inactivity time transfer in MR-DC with 5GC | ZTE | imported from 3GU |
R3‑190170 | CR38.423 for UE Inactive Time transfer in MR-DC with 5GC | ZTE | imported from 3GU |
R3‑190171 | CR36.423 for Addition of MN (MeNB) cell ID to solve the PCI confusion in SN(SgNB) modifcation Request message | ZTE, Samsung | imported from 3GU |
R3‑190172 | CR38.423 for Addition of MN (MeNB) cell ID to solve the PCI confusion in SN(SgNB) modifcation Request message | ZTE, Samsung | imported from 3GU |
R3‑190173 | Clarification for SN status transfer | ZTE | imported from 3GU |
R3‑190174 | CR37.340 for Clarification for SN status transfer | ZTE | imported from 3GU |
R3‑190175 | Update on Connectivity Support for TS38.423 | ZTE | imported from 3GU |
R3‑190176 | NTN hand-over scenarios | THALES | imported from 3GU |
R3‑190177 | NTN multi connectivity | THALES | imported from 3GU |
R3‑190178 | NR-NTN: Tracking Area Management | Fraunhofer IIS, Fraunhofer HHI | imported from 3GU |
R3‑190179 | Missing causes for context retrieval failure | Qualcomm Incorporated | imported from 3GU |
R3‑190180 | Data volume reporting for MR-DC with 5GC | Qualcomm Incorporated, Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑190181 | Separate UL/DL limits for UE's maximum IP rate | Qualcomm Incorporated | imported from 3GU |
R3‑190182 | Separate UL/DL limits for UE's maximum IP rate | Qualcomm Incorporated | imported from 3GU |
R3‑190183 | Correction to behaviour of SN for integrity protection with options 4 and 7 | Qualcomm Incorporated | imported from 3GU |
R3‑190184 | Interaction between Suspend procedure and AS RAI | Qualcomm Incorporated | imported from 3GU |
R3‑190185 | Reply LS on Issues with AS Release Assistance Indicator | Qualcomm Incorporated | imported from 3GU |
R3‑190186 | Potential impacts of DL EDT on RAN3 specifications | Qualcomm Incorporated | imported from 3GU |
R3‑190187 | IAB WI workplan | Qualcomm Incorporated (Rapporteur) | imported from 3GU |
R3‑190188 | IAB baseline for 38401 | Qualcomm Incorporated | imported from 3GU |
R3‑190189 | IAB initial parent-node selection | Qualcomm Incorporated | imported from 3GU |
R3‑190190 | IAB DL flow control using NUPP | Qualcomm Incorporated | imported from 3GU |
R3‑190191 | NG-RAN Positioning Architecture and Procedures | Qualcomm Incorporated | imported from 3GU |
R3‑190192 | LTE-NR UE Level Resource Coordination | Qualcomm Incorporated, NTT DOCOMO, INC., T-Mobile USA | imported from 3GU |
R3‑190193 | XN-U Address Indication in RRC resume | Qualcomm Incorporated | imported from 3GU |
R3‑190194 | Delay measurement for URLLC and MMTel | Qualcomm Incorporated | imported from 3GU |
R3‑190195 | eNA interworking | Qualcomm Incorporated | imported from 3GU |
R3‑190196 | Discussion on SON in NR | Qualcomm Incorporated | imported from 3GU |
R3‑190197 | Providing Slice SLA Fulfilment information at NG-RAN | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑190198 | Reply LS on providing Information on SLA Fulfilment to NG-RAN | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑190199 | Conclusion on incoming LS on inclusion of NSSAI | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑190200 | Correction of stage 2 for slicing | Nokia, Nokia Shanghai Bell, NTT Docomo Inc. | imported from 3GU |
R3‑190201 | Reply LS on inclusion of NSSAI in RRC connection establishment procedure | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑190202 | Data Volume Report with 5GC | Nokia, Nokia Shanghai Bell, Qualcomm Incorporated, Huawei, Ericsson | imported from 3GU |
R3‑190203 | Data Volume Report with 5GC | Nokia, Nokia Shanghai Bell, Qualcomm Incorporated, Huawei, Ericsson | imported from 3GU |
R3‑190204 | Correction of EN-DC data volume reporting | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑190205 | Correction of EN-DC data volume reporting | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑190206 | Correction of PDU Session split at handover | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑190207 | Correction of PDU Session Split at Handover | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑190208 | Correction of PDU Session split at handover | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑190209 | Correction of EPS Voice Fallback | Nokia, Nokia Shanghai Bell, Qualcomm Incorporated | imported from 3GU |
R3‑190210 | Correction of slice support over NG | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑190211 | Correction of 5g to 4g mobility | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑190212 | Correction of 5g to 4g mobility | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑190213 | Correction of 5g to 4g mobility | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑190214 | Rapporteur updates for TS 38.413 | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑190215 | Correction of User Location Information IE presence in HANDOVER NOTIFY | Nokia, Nokia Shanghai Bell, Huawei | imported from 3GU |
R3‑190216 | RAN aspects of the TSN performance evaluation | Nokia, Nokia Shanghai Bell, Qualcomm Incorporated | imported from 3GU |
R3‑190217 | Selective duplication upon transmission failure | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑190218 | Duplication with multiple legs in SgNB | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑190219 | Correction of Handling PDCP SN during Data Forwarding | Nokia, Nokia Shanghai Bell, NTT Docomo Inc | imported from 3GU |
R3‑190220 | Correction of Data Forwarding over Xn | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑190221 | Correction of Network Instance | Nokia, Nokia Shanghai Bell, Orange, Huawei, China Unicom | imported from 3GU |
R3‑190222 | Correction of Network Instance | Nokia, Nokia Shanghai Bell, Orange, Huawei, China Unicom | imported from 3GU |
R3‑190223 | Correction of Network Instance | Nokia, Nokia Shanghai Bell, Orange, Huawei, China Unicom | imported from 3GU |
R3‑190224 | Introduction of direct data forwarding | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑190225 | Introduction of direct data forwarding | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑190226 | Introduction of direct data forwarding | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑190227 | Scope of RAN3 work for MTC Enhancements | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑190228 | Support of extended DRX for MTC | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑190229 | Reply LS on Completion of Study on Cellular IoT support and evolution for the 5G System | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑190230 | Impacts of accurate reference timing delivery on F1 interface | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑190231 | Correction of S-TMSI in Initial UE message | CATT | imported from 3GU |
R3‑190232 | Correction to RRC state report | CATT | imported from 3GU |
R3‑190233 | Establishment of E-RABs during inter system HO from 5G to 4G | CATT | imported from 3GU |
R3‑190234 | LS Response on E-RAB establishment during inter-system handover from 5G to 4G | CATT | imported from 3GU |
R3‑190235 | Correction on Data Forwarding Address | CATT | imported from 3GU |
R3‑190236 | Service Authorization for NR V2X | CATT | imported from 3GU |
R3‑190237 | UE Sidelink AMBR for NR V2X | CATT | imported from 3GU |
R3‑190238 | F1 issues for NR V2X | CATT | imported from 3GU |
R3‑190239 | Resource Co-ordination | CATT | imported from 3GU |
R3‑190240 | TSN integration | CATT | imported from 3GU |
R3‑190241 | Tracking Area and Paging | CATT | imported from 3GU |
R3‑190242 | Considerations on NTN mobility | CATT | imported from 3GU |
R3‑190243 | Discussion on Backhaul RLF recovery | CATT | imported from 3GU |
R3‑190244 | On CAG support for NR | China Telecommunications | imported from 3GU |
R3‑190245 | On signalling the configured slice information to NG-RAN | China Telecommunications | imported from 3GU |
R3‑190246 | Flow and congestion control for IAB | AT&T | imported from 3GU |
R3‑190247 | Route redundancy for IAB Nodes in NSA mode | AT&T | imported from 3GU |
R3‑190248 | Procedures for NSA mode node integration | AT&T | imported from 3GU |
R3‑190249 | Novel use cases for MDT measurements in NR | AT&T | imported from 3GU |
R3‑190250 | CU to DU RRC Info usage in UE Context Setup for handover | Google Inc. | imported from 3GU |
R3‑190251 | Correction to Intra-gNB-CU mobility | Google Inc. | imported from 3GU |
R3‑190252 | Correction to reconfiguration with sync for gNB-DU | Google Inc. | imported from 3GU |
R3‑190253 | Corrections on Cells to be Activated List | ZTE Corporation | imported from 3GU |
R3‑190254 | Clarification on SN Status Transfer | Google Inc. | imported from 3GU |
R3‑190255 | Multiple SCTP Associations Support over F1 Interface for TS38.472 | ZTE Corporation, HW | imported from 3GU |
R3‑190256 | Multiple SCTP Associations Support over F1 Interface for TS38.473 | ZTE Corporation, HW | imported from 3GU |
R3‑190257 | Energy Saving Support for NR in R15 for TS38.300 | ZTE, China Unicom, CMCC, China Telecom | imported from 3GU |
R3‑190258 | Energy Saving Support over F1 Interface | ZTE, China Telecom, CMCC, China Unicom | imported from 3GU |
R3‑190259 | Further discussion on primary path of CA-based SRB duplication | ZTE Corporation | imported from 3GU |
R3‑190260 | Corrections on SRB duplication for TS38.470 | ZTE Corporation | imported from 3GU |
R3‑190261 | Corrections on SRB duplication for TS38.473 | ZTE Corporation | imported from 3GU |
R3‑190262 | Consideration on CAG Support for NR | ZTE Corporation | imported from 3GU |
R3‑190263 | Coverage and Capacity optimization for NR | ZTE Corporation | imported from 3GU |
R3‑190264 | MLB/MRO for NR | ZTE Corporation | imported from 3GU |
R3‑190265 | CSI-RS configuration transfer over Xn | Huawei, Ericsson | imported from 3GU |
R3‑190266 | LS on CSI-RS configuration transfer over Xn | Huawei | imported from 3GU |
R3‑190267 | RAN paging failure handling in SN in case of MR-DC | Huawei, NEC | imported from 3GU |
R3‑190268 | CR to 38.423 for RAN paging failure handling in SN in case of MR-DC | Huawei, NEC | imported from 3GU |
R3‑190269 | Smart Grid Method for SON | ZTE Corporation | imported from 3GU |
R3‑190270 | Consideration on connection to 5GC for eMTC | ZTE | imported from 3GU |
R3‑190271 | Consideration on NB-IoT UE connected to 5G CN | ZTE | imported from 3GU |
R3‑190272 | User plane measurements for RAN centic data collection | ZTE Corporation | imported from 3GU |
R3‑190273 | NR MDT support with variant architectures | ZTE Corporation | imported from 3GU |
R3‑190274 | The performance evaluation on Delay critical GBR traffic | ZTE Corporation | imported from 3GU |
R3‑190275 | QoE measurement support in NR | ZTE Corporation | imported from 3GU |
R3‑190276 | PCI selection solution in NR | ZTE Corporation | imported from 3GU |
R3‑190277 | [draft] Reply LS on RAN related parameters collected from UE | ZTE Corporation | imported from 3GU |
R3‑190278 | Combined TNL Address Discovery solution in Option3 | ZTE Corporation | imported from 3GU |
R3‑190279 | Clarification of Additional QoS Flow Information IE Usage for Multiple Non-GBR QoS Flows | ZTE | imported from 3GU |
R3‑190280 | CR to 38.473 on Bearer type change indication | CATT | imported from 3GU |
R3‑190281 | Introduction of PH-InforSCG in DU to CU RRC Information | CATT | imported from 3GU |
R3‑190282 | CR to 38.473 on Measurement gap coordination | CATT | imported from 3GU |
R3‑190283 | CR to 38.423 on support of PDU session split during handover procedure | CATT,Huawei | imported from 3GU |
R3‑190284 | TP to 37.340 on support of PDU session split during handover procedure | CATT,Huawei | imported from 3GU |
R3‑190285 | Discussion on configuration of Scell status during Scell addition ^^procedure | CATT | imported from 3GU |
R3‑190286 | Discussion on fast recovery procedure | CATT | imported from 3GU |
R3‑190287 | Discussion on data forwarding for inter-RAT mobility | CATT | imported from 3GU |
R3‑190288 | LS on support of direct data forwarding for inter-rat handover | CATT | imported from 3GU |
R3‑190289 | Discussion on Mobility Robust Optimization in 5G system | CATT | imported from 3GU |
R3‑190290 | LS on UE RLF Report for 5G system | CATT | imported from 3GU |
R3‑190291 | Discussion on Mobilty Load Balance in 5G system | CATT | imported from 3GU |
R3‑190292 | Considerations on support of Energy Saving in NR | CATT | imported from 3GU |
R3‑190293 | Consideration on RAN network sharing | CATT | imported from 3GU |
R3‑190294 | CR for access control related information transfer over F1 | CATT | imported from 3GU |
R3‑190295 | Discussion on F1AP IEs for MR-DC coordination | CATT | imported from 3GU |
R3‑190296 | CR to 38.473 on MR-DC coordination | CATT | imported from 3GU |
R3‑190297 | Correction from Rapporteur for 38.401 | NEC | imported from 3GU |
R3‑190298 | Desired Activity Notification Level | NEC | imported from 3GU |
R3‑190299 | Condition for inclusion of the Dedicated SI Delivery Needed UE List IE | NEC, CATT | imported from 3GU |
R3‑190300 | Final Frame Indication in NR-UP | NEC | imported from 3GU |
R3‑190301 | Correction of the Transmission stop/restart indication | NEC | imported from 3GU |
R3‑190302 | Corrections related to Integrity Protection handling at the gNB-CU-UP | NEC | imported from 3GU |
R3‑190303 | RAN paging failure handling in case of CP-UP separation | NEC, Huawei | imported from 3GU |
R3‑190304 | Correction to RNAU without context relocation | NEC, Huawei, Qualcomm Incorporated | imported from 3GU |
R3‑190305 | Use case of URLLC Optimisation for RAN centric Data utilization | NEC | imported from 3GU |
R3‑190306 | XnAP Corrections of MN Initiated PDU Session Resource Modification | ZTE | imported from 3GU |
R3‑190307 | Proposal for network node interfaces related to UE radio capability transfer | KDDI Corporation, China Telecom | imported from 3GU |
R3‑190308 | Proposal for network node interfaces related to UE radio capability transfer | KDDI Corporation, China Telecom | imported from 3GU |
R3‑190309 | SgNB Release initiated by Re-establishment to other eNB | KDDI Corporation | imported from 3GU |
R3‑190310 | Support of RAN initiated multiple SCTP associations | Huawei, ZTE | imported from 3GU |
R3‑190311 | Correction on Multiple SCTP Associations | Huawei, ZTE | imported from 3GU |
R3‑190312 | Discussion of merged solution for ANR | Qualcomm Incorporated | imported from 3GU |
R3‑190313 | Introduction of TNL Address discovery for EN-DC | Qualcomm Incorporated | imported from 3GU |
R3‑190314 | Introduction of TNL Address discovery for EN-DC | Qualcomm Incorporated | imported from 3GU |
R3‑190315 | Introduction of TNL Address discovery for EN-DC | Qualcomm Incorporated | imported from 3GU |
R3‑190316 | Introduction of TNL Address discovery for EN-DC | Qualcomm Incorporated | imported from 3GU |
R3‑190317 | Data volume reporting for MR-DC with 5GC | Qualcomm Incorporated, Nokia, Nokia Shanghai Bell, Huawei, HiSilicon, Ericsson | imported from 3GU |
R3‑190318 | Potential impacts of CP-CIoT in 5GS on RAN3 specifications | Qualcomm Incorporated | imported from 3GU |
R3‑190319 | Potential impacts of eDRX in 5GS on RAN3 specifications | Qualcomm Incorporated | imported from 3GU |
R3‑190320 | On signalling optimizations for small data in RRC Inactive | Qualcomm Incorporated | imported from 3GU |
R3‑190321 | [DRAFT] Reply LS on Signalling optimization for RRC Inactive N3 path switch | Qualcomm Incorporated | imported from 3GU |
R3‑190322 | Correction of Network Instance | Huawei, Nokia, Nokia Shanghai Bell, China Unicom, China Telecom, Orange | imported from 3GU |
R3‑190323 | Slice availability for inactive UE | Huawei | imported from 3GU |
R3‑190324 | CR to 38.300 for slice availability for inactive UE | Huawei | imported from 3GU |
R3‑190325 | Stage 2 and stage 3 clean-up for support of data forwarding for reestablishment UE | Huawei | imported from 3GU |
R3‑190326 | CR to 38.423 for support of data forwarding for reestablishment UE | Huawei | imported from 3GU |
R3‑190327 | CR to 38.300 for support of data forwarding for RRC reestablishment UE | Huawei | imported from 3GU |
R3‑190328 | CR to 38.423 for adding AMF Set Information in XN SETUP RESPONSE | Huawei | imported from 3GU |
R3‑190329 | RRC re-establishment in case of no NG connection to serving AMF | Huawei | imported from 3GU |
R3‑190330 | CR to 38.300 for RRC re-establishment in case of no NG connection to serving AMF | Huawei | imported from 3GU |
R3‑190331 | Corrections on RAN/AMF Configuration Update | Huawei, NEC, Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑190332 | Corrections on gNB-CU-UP/gNB-DU-CP Configuration Update | Huawei, NEC | imported from 3GU |
R3‑190333 | Corrections on gNB-CU/gNB-DU Configuration Update | Huawei, NEC | imported from 3GU |
R3‑190334 | Correction of RAN triggered PDU session split | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑190335 | Correction of RAN triggered PDU session split | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑190336 | Correction of RAN triggered PDU session split | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑190337 | Correction of EPC interworking | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑190338 | Correction of EPC interworking | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑190339 | Correction of EPC interworking | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑190340 | Correction of Emergency Fallback | Nokia, Nokia Shanghai Bell, TMO US, Orange | imported from 3GU |
R3‑190341 | Correction of Emergency Fallback | Nokia, Nokia Shanghai Bell, TMO US, Orange | imported from 3GU |
R3‑190342 | Correction of slice support over Xn | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑190343 | Correction of slice support over Xn | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑190344 | RAN3 functions for MTC connected to 5GC | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑190345 | Scope of RAN3 work for NBIOT Enhancements | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑190346 | RAN3 functions for NBIOT connected to 5GC | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑190347 | Support of extended DRX for NBIOT | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑190348 | Reply LS on Completion of Study on Cellular IoT support and evolution for the 5G System | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑190349 | Two additional Scenarios for RAN Centric Data Collection SI | Vodafone España SA | imported from 3GU |
R3‑190350 | IAB Aspects in TS 38.401 | Ericsson | imported from 3GU |
R3‑190351 | CR TS 38.401 IAB Aspects | Ericsson | imported from 3GU |
R3‑190352 | IP Address Assignment for IAB Nodes | Ericsson | imported from 3GU |
R3‑190353 | QoS Mapping to Backhaul Bearers in IAB Networks | Ericsson | imported from 3GU |
R3‑190354 | IAB node Integration Procedure | Ericsson | imported from 3GU |
R3‑190355 | CR TS 38.401 IAB node Integration Procedure | Ericsson | imported from 3GU |
R3‑190356 | Backhaul Channel Setup and Modification Procedure for IAB Networks | Ericsson | imported from 3GU |
R3‑190357 | CR TS 38.401 Backhaul Channel Setup and Modification Procedure for IAB Networks | Ericsson | imported from 3GU |
R3‑190358 | Flow Control in IAB Networks | Ericsson | imported from 3GU |
R3‑190359 | IAB Node Authentication and Authorization | Ericsson | imported from 3GU |
R3‑190360 | Support for LTE Deployment at IAB Node Sites | Ericsson | imported from 3GU |
R3‑190361 | Minimizing CN Functionalities for IAB Networks | Ericsson | imported from 3GU |
R3‑190362 | Packet Forwarding in IAB Networks | Ericsson | imported from 3GU |
R3‑190363 | Recovery From Link Failure in IAB | Ericsson | imported from 3GU |
R3‑190364 | CR TS 38.401 Recovery From Link Failure in IAB | Ericsson | imported from 3GU |
R3‑190365 | Text Proposal for TR 37.816 | Vodafone España SA | imported from 3GU |
R3‑190366 | Energy saving use case and measurements | Orange | imported from 3GU |
R3‑190367 | On Small Data transmission without Path Switch (R3-190039/ S2-1813394) | InterDigital, Sony | imported from 3GU |
R3‑190368 | Consideration on Supporting RAN-LMF in NR Positioning | CATT | imported from 3GU |
R3‑190369 | Discussion on connecting to RAN-LMF via Xn | CATT | imported from 3GU |
R3‑190370 | Discussion on impacts of Higher Layer Multi-Connectivity | CATT | imported from 3GU |
R3‑190371 | Consideration on PDCP duplication status at network side | CATT | imported from 3GU |
R3‑190372 | CR to 38.473 on Notification Control during inter-DU HO | CATT | imported from 3GU |
R3‑190373 | CR to 37.340 on Notification Control during Secondary Node Change | CATT | imported from 3GU |
R3‑190374 | Core Network Type Restriction to EPC | Huawei | imported from 3GU |
R3‑190375 | Introduction of Core Network Type Restrictions to EPC | Huawei | imported from 3GU |
R3‑190376 | Introduction of Core Network Type Restrictions to EPC | Huawei | imported from 3GU |
R3‑190377 | Discussion on SON Information Exchange over NG interface | Huawei | imported from 3GU |
R3‑190378 | PCI Selection for NR cells | Huawei | imported from 3GU |
R3‑190379 | Discussion on RACH optimization in NR | Huawei | imported from 3GU |
R3‑190380 | Discussion on mobility optimization | Huawei | imported from 3GU |
R3‑190381 | Discussion on Load Balancing | Huawei | imported from 3GU |
R3‑190382 | Considerations on LTE V2X Optimization | Huawei | imported from 3GU |
R3‑190383 | Support of MDT in NG-RAN | Huawei | imported from 3GU |
R3‑190384 | CR to 36.300 for en-gNB TNL address discovery (option 2 only) | Huawei | imported from 3GU |
R3‑190385 | CR to 36.413 for en-gNB TNL address discovery (option 2 only) | Huawei | imported from 3GU |
R3‑190386 | CR to 36.423 for en-gNB TNL address discovery (option 2 only) | Huawei | imported from 3GU |
R3‑190387 | IP Version of Transport Layer Address | Huawei | imported from 3GU |
R3‑190388 | Considersion on Resource-Efficient PDCP Duplication | ZTE Corporation | imported from 3GU |
R3‑190389 | Correction on transport layer address | Huawei | imported from 3GU |
R3‑190390 | Further Discussion on Higher Layer Multi-Connectivity | ZTE Corporation | imported from 3GU |
R3‑190391 | Draft LS to SA2 on approved redundant transmission solution | ZTE Corporation | imported from 3GU |
R3‑190392 | Correction on transport layer address | Huawei | imported from 3GU |
R3‑190393 | Analysis on RAN impacts for TSN solutions | ZTE Corporation | imported from 3GU |
R3‑190394 | Correction on transport layer address | Huawei | imported from 3GU |
R3‑190395 | Discussion on Measurement Gap Configuration for MR-DC | ZTE Corporation | imported from 3GU |
R3‑190396 | XnAP Corrections of SN Initiated PDU Session Resource Modification | ZTE | imported from 3GU |
R3‑190397 | Correction on transport layer address | Huawei | imported from 3GU |
R3‑190398 | Correction on Measurement Gap Configuration for MR-DC for TS38.473 | ZTE Corporation | imported from 3GU |
R3‑190399 | Further discussion on PLMN information for RAN sharing | ZTE Corporation | imported from 3GU |
R3‑190400 | Clarification for PLMN specific interface in case of RAN sharing for TS36.300 | ZTE Corporation | imported from 3GU |
R3‑190401 | Transfer of the PSCell information to Core Network | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑190402 | Transfer of the PSCell information to Core Network | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑190403 | Clarification for PLMN specific interface in case of RAN sharing for TS38.300 | ZTE Corporation | imported from 3GU |
R3‑190404 | Release due to pre-emption | Nokia, Nokia Shanghai Bell, Verizon Wireless | imported from 3GU |
R3‑190405 | Update on NR Served Cell Information for TS36.423 | ZTE Corporation | imported from 3GU |
R3‑190406 | Handling of APID for the first returned message | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑190407 | IAB Node Integration Procedure | Huawei | imported from 3GU |
R3‑190408 | Update on NR Served Cell Information for TS38.423 | ZTE Corporation | imported from 3GU |
R3‑190409 | Update on NR Served Cell Information for TS38.473 | ZTE Corporation | imported from 3GU |
R3‑190410 | Adaptation Layer Configuration | Huawei | imported from 3GU |
R3‑190411 | Update on RRC Version for TS38.473 | ZTE Corporation | imported from 3GU |
R3‑190412 | Discussion on Load Management for SON | ZTE Corporation | imported from 3GU |
R3‑190413 | Cell capacity definition related to wideband carrier | ZTE Corporation | imported from 3GU |
R3‑190414 | IP Address Management of IAB Node | Huawei | imported from 3GU |
R3‑190415 | End-to-end flow control for congestion handling | LG Electronics Inc. | imported from 3GU |
R3‑190416 | XnAP Correction of PDU Session Resource Setup Response Info – MN terminated | ZTE | imported from 3GU |
R3‑190417 | QoS Management and Configuration of IAB Node | Huawei | imported from 3GU |
R3‑190418 | IAB-node migration between different IAB-donors | LG Electronics Inc. | imported from 3GU |
R3‑190419 | Load balancing considering NR feature | LG Electronics Inc. | imported from 3GU |
R3‑190420 | Support of Flow Control for IAB Network | Huawei | imported from 3GU |
R3‑190421 | Remaining issues of the UP protocol architecture | Huawei | imported from 3GU |
R3‑190422 | Direct Data forwarding for inter-system HO | Samsung | imported from 3GU |
R3‑190423 | Support of Direct Data forwarding for handover between 4G and 5G | Samsung | imported from 3GU |
R3‑190424 | Support of Direct Data forwarding for handover between 4G and 5G | Samsung | imported from 3GU |
R3‑190425 | LS on direct data forwarding for inter-system handover | Samsung | imported from 3GU |
R3‑190426 | Discussion for QoS Flow Mapping Indication | Samsung | imported from 3GU |
R3‑190427 | Correction of QoS Flow Mapping Indication | Samsung | imported from 3GU |
R3‑190428 | Correction of QoS Flow Mapping Indication | Samsung | imported from 3GU |
R3‑190429 | Correction of QoS Flow Mapping Indication | Samsung | imported from 3GU |
R3‑190430 | Discussion for RRC container in SN MODIFICATION CONFIRM message | Samsung | imported from 3GU |
R3‑190431 | Correction for RRC container in SN MODIFICATION CONFIRM message | Samsung | imported from 3GU |
R3‑190432 | Discussion for MDT configuration and reporting | Samsung | imported from 3GU |
R3‑190433 | Support for PDCP Duplication with More than 2 Copies | Samsung | imported from 3GU |
R3‑190434 | Overview on IAB node setup (SA) | Samsung | imported from 3GU |
R3‑190435 | Overview of flow control solutions | Samsung | imported from 3GU |
R3‑190436 | Overview on IAB node setup (NSA) | Samsung | imported from 3GU |
R3‑190437 | QoS framework in IAB network | Samsung | imported from 3GU |
R3‑190438 | Overview on IP routing in IAB network | Samsung | imported from 3GU |
R3‑190439 | Overview on IAB node reestablishment | Samsung | imported from 3GU |
R3‑190440 | Overview on IAB node mitigation | Samsung | imported from 3GU |
R3‑190441 | CR on DRX configuration setup | Samsung | imported from 3GU |
R3‑190442 | PWS system information segmentation over F1 | Samsung | imported from 3GU |
R3‑190443 | CR on PWS segmentation over F1 | Samsung | imported from 3GU |
R3‑190444 | RRC container transmission in UE Context modification request message | Samsung | imported from 3GU |
R3‑190445 | CR on RRC container in UE context modification request message | Samsung | imported from 3GU |
R3‑190446 | UE context modification refuse | Samsung | imported from 3GU |
R3‑190447 | CR on UE context modification refuse | Samsung | imported from 3GU |
R3‑190448 | NTN Network Identities | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑190449 | Tracking Area and UE position in NTN | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑190450 | Analysis on Interface management between satellite and network entity on ground | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑190451 | Analysis on CONNECTED mode mobility in Scenario D2 | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑190452 | Further consideration on Start end time stamp for data volume reporting | NTT DOCOMO, INC, Orange, China Mobile, KT Corp., Verizon Wireless, Deutsche Telekom | imported from 3GU |
R3‑190453 | CR for clarification on Start end time stamp in data volume reporting | NTT DOCOMO, INC, Orange, China Mobile, KT Corp., Verizon Wireless, Deutsche Telekom | imported from 3GU |
R3‑190454 | Necessity on path switch request for inter MN HO without SN change | NTT DOCOMO, INC. | imported from 3GU |
R3‑190455 | CR for clarification on path switch request for inter MN HO without SN change | NTT DOCOMO, INC. | imported from 3GU |
R3‑190456 | Way forward on initial UL RRC MESSAGE transfer over F1 | NTT DOCOMO, INC, Orange, KT Corp, Deutsche Telekom, TIM, China Mobile, China Unicom, Verizon Wireless | imported from 3GU |
R3‑190457 | How to achieve multiple interface over HLS | NTT DOCOMO, INC. | imported from 3GU |
R3‑190458 | Security protection of F1 over wireless backhaul | Huawei | imported from 3GU |
R3‑190459 | Support of multiple connectivity in IAB network | Huawei | imported from 3GU |
R3‑190460 | Discussion on System Information for W1 | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑190461 | Default Paging DRX in IDLE Mode | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑190462 | Default Paging DRX in IDLE Mode | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑190463 | CR to 38.413 on support of signalling the configured slice information to NG-RAN | China Telecommunication | imported from 3GU |
R3‑190464 | Discussion on Handover Preparation Information | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑190465 | [DRAFT] LS on utilization of HandoverPreparationInformation IE between gNB-CU and gNB-DU | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑190466 | Discussion on Paging Failure | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑190467 | Paging Failure | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑190468 | Discussion on MeasGapConfig | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑190469 | MeasGapConfig in CU to DU RRC Information container | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑190470 | Discussion on DRB to be Released | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑190471 | Corrrection for DRB to be Released | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑190472 | UE Context Setup and UE Context Modification Requests Handling | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑190473 | Discussion on uac-barringInfo | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑190474 | uac-BarringInfo | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑190475 | Discussion on UE Identification over E1 | Nokia, Nokia Shanghai Bell, Verizon Wireless, Samsung, KDDI | imported from 3GU |
R3‑190476 | UE Identification over E1 | Nokia, Nokia Shanghai Bell, Verizon Wireless, Samsung, KDDI | imported from 3GU |
R3‑190477 | Release due to pre-emption | Nokia, Nokia Shanghai Bell, Verizon Wireless | imported from 3GU |
R3‑190478 | Release due to pre-emption | Nokia, Nokia Shanghai Bell, Verizon Wireless | imported from 3GU |
R3‑190479 | PDCP Config corrections | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑190480 | Transaction ID in Error Indication procedure | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑190481 | Transaction ID in Error Indication procedure | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑190482 | F1 Served Cell Information | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑190483 | Consideration on SRI mobility | CATT | imported from 3GU |
R3‑190484 | Cells to be deactivated over F1 | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑190485 | XnAP Correction of PDU Session Resource Setup Complete Info – SN terminated | ZTE | imported from 3GU |
R3‑190486 | Corrrection for cells failed to be activated | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑190487 | Discussion on UL Data Split Threshold | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑190488 | Issues to be decided in IAB Stage2 design | KDDI Corporation | imported from 3GU |
R3‑190489 | UL Data Split Threshold | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑190490 | Consideration on routing management procedure | KDDI Corporation | imported from 3GU |
R3‑190491 | XnAP Additional Usage of RRC Config Indication | ZTE | imported from 3GU |
R3‑190492 | RAN3 Impact Analysis of IAB Usage in NSA network | Huawei | imported from 3GU |
R3‑190493 | Routing Address Design and Configuration | Huawei | imported from 3GU |
R3‑190494 | Routing Table Design and Configuration | Huawei | imported from 3GU |
R3‑190495 | Intra-Donor CU Topology Adaptation | Huawei | imported from 3GU |
R3‑190496 | Inter-Donor CU Topology Adaptation | Huawei | imported from 3GU |
R3‑190497 | Backhaul RLF Recovery | Huawei | imported from 3GU |
R3‑190498 | Analysis on IP address management | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑190499 | IAB Integration | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑190500 | Bearer Mapping in Donor-DU and IAB node | Huawei | imported from 3GU |
R3‑190501 | Congestion reporting and handling for IAB networks | Huawei | imported from 3GU |
R3‑190502 | Resource coordination between multi-hop BH links | Huawei | imported from 3GU |
R3‑190503 | Discussion on flow control in IAB | ZTE Corporation | imported from 3GU |
R3‑190504 | In-order delivery for MR-DC | Huawei | imported from 3GU |
R3‑190505 | Support of in-order delivery for MR-DC | Huawei | imported from 3GU |
R3‑190506 | Support of in-order delivery for MR-DC | Huawei | imported from 3GU |
R3‑190507 | Introduction of DC resource configuration | Huawei | imported from 3GU |
R3‑190508 | SN initiated QoS flow release for MN terminated SCG bearer | Huawei | imported from 3GU |
R3‑190509 | SN initiated QoS flow release for MN terminated SCG bearer | Huawei | imported from 3GU |
R3‑190510 | Clarification on Inter-node message for NE-DC | Huawei | imported from 3GU |
R3‑190511 | Discussion on DRB level offloading in MR-DC with 5GC | Huawei | imported from 3GU |
R3‑190512 | Clarification on DRB level offloading in MR-DC with 5GC | Huawei | imported from 3GU |
R3‑190513 | Clarification on DRB level offloading in MR-DC with 5GC | Huawei | imported from 3GU |
R3‑190514 | Discussion on the masked IMEISV | Huawei, Vodafone | imported from 3GU |
R3‑190515 | Introduction of IMEISV to Addition Request over X2 | Huawei, Vodafone | imported from 3GU |
R3‑190516 | Introduction of IMEISV to Addition Request over Xn | Huawei, Vodafone | imported from 3GU |
R3‑190517 | Support of security protection in Option 4&7 | Huawei | imported from 3GU |
R3‑190518 | Support of integrity protection for Option 4&7 | Huawei | imported from 3GU |
R3‑190519 | Support of integrity protection for Option 4&7 | Huawei | imported from 3GU |
R3‑190520 | Remaining issue on PDU session split | Huawei | imported from 3GU |
R3‑190521 | Clarification on PDU Session split initiated by RAN | Huawei | imported from 3GU |
R3‑190522 | Solutions for PDU session split during handover | Huawei | imported from 3GU |
R3‑190523 | PDU session split handling during handover Alt 1 | Huawei, CATT | imported from 3GU |
R3‑190524 | PDU session split handling during handover Alt 2 | Huawei | imported from 3GU |
R3‑190525 | Default DRB coordination for MR-DC | Huawei | imported from 3GU |
R3‑190526 | Default DRB coordination in MR-DC over Xn | Huawei | imported from 3GU |
R3‑190527 | Default DRB coordination in MR-DC over NG | Huawei | imported from 3GU |
R3‑190528 | Introduction of PDU session fail to be released list | Huawei | imported from 3GU |
R3‑190529 | Interaction between procedures for the release of PDU sessions | Huawei | imported from 3GU |
R3‑190530 | Clarification on the usage of TNL information | Huawei | imported from 3GU |
R3‑190531 | Clarification on the usage of TNL information | Huawei | imported from 3GU |
R3‑190532 | Overview of RAN3 impacts for DC and CA enhancement | Huawei | imported from 3GU |
R3‑190533 | Enabling fast SN change | Huawei | imported from 3GU |
R3‑190534 | Fast SN addition via early measurement reporting | Huawei | imported from 3GU |
R3‑190535 | Correction on partial reset | Huawei | imported from 3GU |
R3‑190536 | Considerations on high bit rate for EN-DC | Huawei | imported from 3GU |
R3‑190537 | Support of high bit rate for EN-DC | Huawei | imported from 3GU |
R3‑190538 | [DRAFT] LS on support of high bit rate for EN-DC | Huawei | imported from 3GU |
R3‑190539 | Clarification on the usage of coordination assistance information | Huawei | imported from 3GU |
R3‑190540 | Correction on TAI Support List | Huawei | imported from 3GU |
R3‑190541 | Discussion on IAB BH RLF handling | ZTE Corporation | imported from 3GU |
R3‑190542 | Discussion on network-controlled IAB migration handling | ZTE Corporation | imported from 3GU |
R3‑190543 | Control plane signaling delivery in NSA deployment | ZTE Corporation | imported from 3GU |
R3‑190544 | Consideration on IP Address Allocation in IAB | ZTE Corporation | imported from 3GU |
R3‑190545 | Consideration on routing in IAB | ZTE Corporation | imported from 3GU |
R3‑190546 | Discussion on BH RLC channel configuration in IAB network | ZTE Corporation | imported from 3GU |
R3‑190547 | Integration of IAB-node | Huawei | imported from 3GU |
R3‑190548 | Support of NR V2X in case of CU-DU split | ZTE Corporation | imported from 3GU |
R3‑190549 | Discussion paper to the LS on 5G_URLLC from SA2 | Huawei | imported from 3GU |
R3‑190550 | Reply LS on 5G_URLLC | Huawei | imported from 3GU |
R3‑190551 | Introduction of overall architecture for IAB | Huawei | imported from 3GU |
R3‑190552 | Discussion on performance measurements | CATT | imported from 3GU |
R3‑190553 | Test | ETSI MCC | imported from 3GU |
R3‑190554 | Considerations on the issues for MR-DC based NR V2X | LG Electronics | imported from 3GU |
R3‑190555 | Text proposal for the conclusion of TR 38.885 on RAN3 | LG Electronics | imported from 3GU |
R3‑190556 | Discussion on RAN paging failure in CP-UP separation | LG Electronics | imported from 3GU |
R3‑190557 | RAN paging failure in CP-UP separation_Stage 2 | LG Electronics | imported from 3GU |
R3‑190558 | RAN paging failure in CP-UP separation_Stage 3 | LG Electronics | imported from 3GU |
R3‑190559 | Discussion on authorization in NR V2X | ZTE Corporation | imported from 3GU |
R3‑190560 | Remaining RAN impacts for higher layer multi-connectivity in IIoT | LG Electronics | imported from 3GU |
R3‑190561 | Consideration on support for MT EDT | LG Electronics | imported from 3GU |
R3‑190562 | Intra Donor-DU topology adaptation procedure | Huawei | imported from 3GU |
R3‑190563 | TR 37.816 v0.1.0 | CMCC | imported from 3GU |
R3‑190564 | Work plan for study on RAN-centric data collection and utilization for LTE and NR | CMCC | imported from 3GU |
R3‑190565 | Report of offline coordination of uses cases for RAN-centric DCU | CMCC | imported from 3GU |
R3‑190566 | Text proposals for the agreed use case description | CMCC | imported from 3GU |
R3‑190567 | Text proposals for other potential use case description | CMCC | imported from 3GU |
R3‑190568 | Network aspects of MDT for NR | CMCC | imported from 3GU |
R3‑190569 | Text proposal for network aspects of MDT for NR | CMCC | imported from 3GU |
R3‑190570 | Considerations on NR positioning architecture enhancement | CMCC | imported from 3GU |
R3‑190571 | Load Balancing Optimization | CMCC | imported from 3GU |
R3‑190572 | Text proposal for Load Balancing Optimization | CMCC | imported from 3GU |
R3‑190573 | Considerations on V2X use cases and measurements | CMCC | imported from 3GU |
R3‑190574 | Support for Accurate Reference Timing Delivery | CMCC | imported from 3GU |
R3‑190575 | UE Specific Local RRM Policy Information Storage and Retrieval | CMCC | imported from 3GU |
R3‑190576 | Resource-efficient of multi-leg PDCP duplication | CMCC | imported from 3GU |
R3‑190577 | Use Case of Edge Computing | CMCC, Vodafone, CATT, TIM, T-Mobile, China Unicom | imported from 3GU |
R3‑190578 | Consideration of RACH optimization for the NR | CMCC | imported from 3GU |
R3‑190579 | IAB protocol stack options | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑190580 | Security aspects and considerations for IAB | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑190581 | Further discussions on RAN sharing | Huawei | imported from 3GU |
R3‑190582 | CR to 38.473 on corrections to common interface in case of RAN sharing | Huawei, Samsung | imported from 3GU |
R3‑190583 | CR to 38.423 on corrections to common interface in case of RAN sharing | Huawei, Samsung | imported from 3GU |
R3‑190584 | CR to 36.423 on corrections to common interface in case of RAN sharing | Huawei, Samsung | imported from 3GU |
R3‑190585 | pCR to 36.300 on clarifications for RAN sharing | Huawei | imported from 3GU |
R3‑190586 | CR to 38.401 on clarifications for RAN sharing | Huawei | imported from 3GU |
R3‑190587 | Further discussion on SRB duplication and LCID | Huawei | imported from 3GU |
R3‑190588 | CR to 38.473 on SRB duplicaiton and LCID | Huawei | imported from 3GU |
R3‑190589 | CR to 38.473 on enabling SRB duplicaiton through UE Context Modification procedure | Huawei | imported from 3GU |
R3‑190590 | Further discussion on cell management over F1 | Huawei | imported from 3GU |
R3‑190591 | CR to 38.473 on clarifications for cell management over F1 | Huawei | imported from 3GU |
R3‑190592 | CR to 38.401 on clarifications for cell management over F1 | Huawei | imported from 3GU |
R3‑190593 | CR to 38.463 on Integrity-check failure over E1 | Huawei | imported from 3GU |
R3‑190594 | Discussion on Delta RRC config support in gNB-CU | Huawei | imported from 3GU |
R3‑190595 | CR to 38473 on Delta RRC config support in gNB-CU | Huawei | imported from 3GU |
R3‑190596 | CR to 38.473 on the condition of gNB-DU provides C-RNTI | Huawei | imported from 3GU |
R3‑190597 | CR to 38.473 on inactivity monitoring request | Huawei | imported from 3GU |
R3‑190598 | CR to 38.473 on new cause value when entering RRC inactive | Huawei | imported from 3GU |
R3‑190599 | CR to 38.473 on corrections for removal of PDCP duplication for SRB | Huawei | imported from 3GU |
R3‑190600 | CR to TS 38.463 on inactivity timer over E1 | Huawei | imported from 3GU |
R3‑190601 | CR to 38.470 on for MSG1 based on-demand SI | Huawei | imported from 3GU |
R3‑190602 | Discussion on PPID for DTLS over SCTP | Huawei | imported from 3GU |
R3‑190603 | CR to 38.473 on the introduction of UE Context Modification Refuse message | Huawei | imported from 3GU |
R3‑190604 | CR to 38.473 on correction for MeasurementTimingConfiguration | Huawei | imported from 3GU |
R3‑190605 | Discussion on the gNB-DU behavior upon RLC failure | Huawei | imported from 3GU |
R3‑190606 | CR to 38.473 on the correction to RLC failure handling | Huawei | imported from 3GU |
R3‑190607 | CR to 38.473 on deconfiguring CA based PDCP duplication | Huawei | imported from 3GU |
R3‑190608 | CR to 38.463 on deconfiguring PDCP duplication | Huawei | imported from 3GU |
R3‑190609 | CR to 38.460 on inactivity notification over E1 | Huawei | imported from 3GU |
R3‑190610 | CR to 38.473 on transfering UEAssistanceInformation over F1 | Huawei | imported from 3GU |
R3‑190611 | Discussion on System Information handling by ng-eNB | Huawei, TIM, China Unicom | imported from 3GU |
R3‑190612 | Discussion on supporting of slice for ng-eNB CU-DU | Huawei, Orange, TIM, China Unicom | imported from 3GU |
R3‑190613 | Discussion of W1AP UE context management | Huawei, Orange, TIM, China Unicom | imported from 3GU |
R3‑190614 | Discussion on W1AP Paging procedures | Huawei, TIM, China Unicom | imported from 3GU |
R3‑190615 | Discussion of W1AP interface management procedures | Huawei, Orange, TIM, China Unicom | imported from 3GU |
R3‑190616 | Discussion of W1AP RRC message transfer procedures | Huawei, Orange, TIM, China Unicom | imported from 3GU |
R3‑190617 | pCR to 37.470 on W1AP functions and procedures | Huawei, TIM, China Unicom | imported from 3GU |
R3‑190618 | Discussion on RAN3 impacts of UP Integrity Protection for Small Data in Early Data Transfer | Huawei | imported from 3GU |
R3‑190619 | CR to 36.423 on UP Integrity Protection for Small Data in Early Data Transfer | Huawei | imported from 3GU |
R3‑190620 | [DRAFT] Reply LS on UP Integrity Protection for Small Data in Early Data Transfer | Huawei | imported from 3GU |
R3‑190621 | Access Control Information over F1 | Huawei | imported from 3GU |
R3‑190622 | Addition of UAC assistance information | Huawei | imported from 3GU |
R3‑190623 | NR V2X Service Authorization | Huawei | imported from 3GU |
R3‑190624 | UE Sidelink AMBR in NG-RAN | Huawei | imported from 3GU |
R3‑190625 | Principles for resource pool assignment | Huawei | imported from 3GU |
R3‑190626 | Rapporteur updates of 38.473 | Huawei | imported from 3GU |
R3‑190627 | Rapporteur updates | Huawei | imported from 3GU |
R3‑190628 | Correction on gNB-DU Resource Coordination | Huawei | imported from 3GU |
R3‑190629 | On slice SLA fulfilment | Huawei, CMCC | imported from 3GU |
R3‑190630 | [DRAFT] Reply LS Providing information on SLA fulfilment to NG-RAN | Huawei | imported from 3GU |
R3‑190631 | Correction of Desired Buffer Size | Ericsson | imported from 3GU |
R3‑190632 | CR TS 38.425 Correction of Desired Buffer Size | Ericsson | imported from 3GU |
R3‑190633 | Endpoint IP address and port | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑190634 | Correction to add paging origin IE | Intel Corporation | imported from 3GU |
R3‑190635 | Corrections for Rel-15 positioning | Intel Corporation | imported from 3GU |
R3‑190636 | Positioning methods support in gNB and ng-eNB | Intel Corporation | imported from 3GU |
R3‑190637 | RAN3 scope of the Positioning SI | Intel Corporation | imported from 3GU |
R3‑190638 | Addition and removal of multiple SCTP associations | Intel Corporation | imported from 3GU |
R3‑190639 | On the issue of N2 Mobility Request/Response procedure | Intel Corporation | imported from 3GU |
R3‑190640 | NTN feeder link and ISL performances | THALES | imported from 3GU |
R3‑190641 | NTN feeder link and ISL performances | THALES | imported from 3GU |
R3‑190642 | Revision of additional enhancements for NB-IoT work plan | Huawei | imported from 3GU |
R3‑190643 | Clarification on NTN GW | Huawei | imported from 3GU |
R3‑190644 | Interface issues in NTN | Huawei | imported from 3GU |
R3‑190645 | Handling of Network Identities in NTN | Huawei | imported from 3GU |
R3‑190646 | RAN3 conclusion on positioning NR Study | Huawei | imported from 3GU |
R3‑190647 | [DRAFT] LS on positioning NR Study conclusion | Huawei | imported from 3GU |
R3‑190648 | Discussion on NR Positioning Architecture | Huawei | imported from 3GU |
R3‑190649 | Discussion on RAN as LCS client | Huawei | imported from 3GU |
R3‑190650 | Discussion on NRPPa | Huawei | imported from 3GU |
R3‑190651 | Discussion on UL positioning technique | Huawei | imported from 3GU |
R3‑190652 | Discussion on DL positioning technique | Huawei | imported from 3GU |
R3‑190653 | Discussion on DL and UL based positioning technique | Huawei | imported from 3GU |
R3‑190654 | Introducing X2 TNL Address discovery for en-gNBs for EN-DC | Ericsson, Vodafone | imported from 3GU |
R3‑190655 | Capacity and Coverage Optimization: NR UL coverage aspects | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑190656 | PCI selection use case: handling of PCI confusion resolution | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑190657 | Proposals for the RACH optimization use case | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑190658 | Optimization of RAN Notification Areas | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑190659 | Management of System Information Area in NR | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑190660 | Mobility optimization solution | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑190661 | RACH optimization solution | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑190662 | Correction on AMF connectivity | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑190663 | Common or per-PLMN interface for network sharing | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑190664 | Common Xn link for network sharing | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑190665 | Common X2 instance between eNB and shared en-gNB | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑190666 | Introducing X2 TNL Address discovery for en-gNBs for EN-DC | Ericsson, Vodafone | imported from 3GU |
R3‑190667 | Multiple TNLA over F1 transport | Ericsson | imported from 3GU |
R3‑190668 | Multiple TNLA over E1 transport | Ericsson | imported from 3GU |
R3‑190669 | Indication that cells are only UL or DL on F1 | Ericsson | imported from 3GU |
R3‑190670 | Handling the case when asymmetric QoS flow to DRB mapping is not supported | Ericsson | imported from 3GU |
R3‑190671 | AMF intitiated UE Context Release failure cause | Ericsson | imported from 3GU |
R3‑190672 | Clarification on NRARFCN semantics | Ericsson | imported from 3GU |
R3‑190673 | Clarification on NRARFCN semantics | Ericsson | imported from 3GU |
R3‑190674 | Temporary Identifier usage at interworking | Ericsson | imported from 3GU |
R3‑190675 | Extending GUMMEI Type | Ericsson | imported from 3GU |
R3‑190676 | Correction of EN-DC related Causes | Ericsson | imported from 3GU |
R3‑190677 | Introduction of EN-DC | Ericsson | imported from 3GU |
R3‑190678 | Analysis of SA2 scenarios on SLA fulfilment at NG-RAN | Ericsson, AT&T | imported from 3GU |
R3‑190679 | [Draft] Reply LS on providing information on SLA fulfilment to NG-RAN | Ericsson | imported from 3GU |
R3‑190680 | Maximum Integrity Protected Data Rate | Ericsson | imported from 3GU |
R3‑190681 | Maximum Integrity Protected Data Rate | Ericsson | imported from 3GU |
R3‑190682 | Maximum Integrity Protected Data Rate | Ericsson | imported from 3GU |
R3‑190683 | Maximum Integrity Protected Data Rate | Ericsson | imported from 3GU |
R3‑190684 | On the incoming LS on NPN | Ericsson | imported from 3GU |
R3‑190685 | Draft Reply LS on RAN Impact analysis due to NPN | Ericsson | imported from 3GU |
R3‑190686 | Data volume reporting for MR-DC with 5GC | Ericsson | imported from 3GU |
R3‑190687 | Data volume reporting for MR-DC with 5GC | Ericsson, Qualcomm Incorporated, Nokia, Nokia Shanghai Bell, Huawei, HiSilicon | imported from 3GU |
R3‑190688 | Further discussion on issues with AS Release Assistance Indicator | Ericsson | imported from 3GU |
R3‑190689 | [Draft] Reply LS on Issues with AS Release Assistance Indicator | Ericsson | imported from 3GU |
R3‑190690 | Security Integrity protection of user data in UP-EDT | Ericsson | imported from 3GU |
R3‑190691 | Security Integrity protection of user data in UP-EDT | Ericsson | imported from 3GU |
R3‑190692 | Correction on Initial UE Message to include EDT for MTC | Ericsson | imported from 3GU |
R3‑190693 | Intra eNB CP Relocation for NB-IoT | Ericsson | imported from 3GU |
R3‑190694 | Correction on eNB CP Relocation | Ericsson | imported from 3GU |
R3‑190695 | Introducing X2 TNL Address discovery for en-gNBs for EN-DC | Ericsson, Vodafone | imported from 3GU |
R3‑190696 | Introducing X2 TNL Address discovery for en-gNBs for EN-DC | Ericsson, Vodafone | imported from 3GU |
R3‑190697 | Introducing NR Neighbour information in X2 Setup | Ericsson | imported from 3GU |
R3‑190698 | Introducing a target E-UTRA cell’s NCR towards an NR cell for performing EN-DC | Ericsson | imported from 3GU |
R3‑190699 | Introducing NR Neighbour information in X2 Setup | Ericsson | imported from 3GU |
R3‑190700 | Multiple SCTPs in NG-RAN | Ericsson | imported from 3GU |
R3‑190701 | Multiple TNLA over E1 initialization | Ericsson | imported from 3GU |
R3‑190702 | Associating an additional TNLA with the NG-C interface instance by means of the RAN Configuration Update procedure | Ericsson | imported from 3GU |
R3‑190703 | Multiple SCTP associations over F1AP | Ericsson | imported from 3GU |
R3‑190704 | Multiple SCTP associations over F1AP | Ericsson | imported from 3GU |
R3‑190705 | Support of RAN sharing with multiple Cell ID broadcast | Ericsson | imported from 3GU |
R3‑190706 | Capacity Information Transfer over E1 | Ericsson | imported from 3GU |
R3‑190707 | Further consideration on access class barring | Ericsson | imported from 3GU |
R3‑190708 | Addition of Network Access Rate Reduction message | Ericsson | imported from 3GU |
R3‑190709 | RAN UE Trace ID | Ericsson | imported from 3GU |
R3‑190710 | RAN UE Trace ID in RAN | Ericsson | imported from 3GU |
R3‑190711 | RAN UE Trace ID | Ericsson | imported from 3GU |
R3‑190712 | Support of SDAP mobility when re-mapping at source side is not yet finalised | Ericsson | imported from 3GU |
R3‑190713 | Support of ongoing re-mapping on source side during SDAP mobility | Ericsson | imported from 3GU |
R3‑190714 | Support of ongoing re-mapping on source side during SDAP mobility | Ericsson | imported from 3GU |
R3‑190715 | Support of ongoing re-mapping on source side during SDAP mobility | Ericsson | imported from 3GU |
R3‑190716 | Support of ongoing re-mapping on source side during SDAP mobility | Ericsson | imported from 3GU |
R3‑190717 | About indication that cells are only UL or DL on F1 | Ericsson | imported from 3GU |
R3‑190718 | About Cells Failed to be Activated IE in gNB-CU Configuration Update Ack | Ericsson | imported from 3GU |
R3‑190719 | About Cells Failed to be Activated IE | Ericsson | imported from 3GU |
R3‑190720 | About Cells Failed to be Activated IE in gNB-CU Configuration Update Ack | Ericsson | imported from 3GU |
R3‑190721 | Handling the case when asymmetric QoS flow to DRB mapping is not supported | Ericsson | imported from 3GU |
R3‑190722 | Handling the case when asymmetric QoS flow to DRB mapping is not supported | Ericsson | imported from 3GU |
R3‑190723 | Handling the case when asymmetric QoS flow to DRB mapping is not supported | Ericsson | imported from 3GU |
R3‑190724 | Handling the case when asymmetric QoS flow to DRB mapping is not supported | Ericsson | imported from 3GU |
R3‑190725 | NG Setup Correction | Ericsson | imported from 3GU |
R3‑190726 | NG Setup Correction | Ericsson | imported from 3GU |
R3‑190727 | NG Setup Correction and UE context retention | Ericsson | imported from 3GU |
R3‑190728 | UE AMBR handling in PDU Session Resource Setup procedure | Ericsson | imported from 3GU |
R3‑190729 | UE AMBR handling in PDU Session Resouce Setup procedure | Ericsson | imported from 3GU |
R3‑190730 | gNB-DU UE Aggregate Maximum Bit Rate Uplink correction | Ericsson | imported from 3GU |
R3‑190731 | Remove the second tunnel in the PDU session split, 5GC initiated | Ericsson | imported from 3GU |
R3‑190732 | Abnormal Conditions for PDU Session Resource establishment | Ericsson | imported from 3GU |
R3‑190733 | Abnormal Conditions for PDU Session Resource establishment | Ericsson | imported from 3GU |
R3‑190734 | When NG-RAN node fails to set up a QoS flow for IMS voice | Ericsson | imported from 3GU |
R3‑190735 | When NG-RAN node fails to set up a QoS flow for IMS voice | Ericsson | imported from 3GU |
R3‑190736 | Rapporteur updates on version 15.2.0 | Ericsson | imported from 3GU |
R3‑190737 | Rapporteur updates on version 15.4.0 | Ericsson | imported from 3GU |
R3‑190738 | Correction of MaxnoofBPLMNs for NR | Ericsson | imported from 3GU |
R3‑190739 | Discussion on UE associated signalling | Ericsson | imported from 3GU |
R3‑190740 | Available DU resources at handover | Ericsson | imported from 3GU |
R3‑190741 | RRC Reconfiguration Complete Indicator | Ericsson | imported from 3GU |
R3‑190742 | RRC Reconfiguration Complete Indicator | Ericsson | imported from 3GU |
R3‑190743 | RRC Reconfiguration failure | Ericsson | imported from 3GU |
R3‑190744 | Correction about value tag | Ericsson | imported from 3GU |
R3‑190745 | Node behaviour at reception of DU to CU RRC Information | Ericsson | imported from 3GU |
R3‑190746 | Node behaviour at reception of DU to CU RRC Information | Ericsson | imported from 3GU |
R3‑190747 | How to Support Positioning in F1AP | Ericsson | imported from 3GU |
R3‑190748 | Support for Positioning in F1AP | Ericsson | imported from 3GU |
R3‑190749 | Activity Notification Level in the Context Modification procedure - Discussion | Ericsson | imported from 3GU |
R3‑190750 | Activity Notification Level in the Context Modification procedure | Ericsson | imported from 3GU |
R3‑190751 | gNB-CU-UP Connection Status | Ericsson | imported from 3GU |
R3‑190752 | gNB-CU-UP Connection Status | Ericsson | imported from 3GU |
R3‑190753 | RAN Paging failure on E1 | Ericsson | imported from 3GU |
R3‑190754 | RAN Paging failure on E1 | Ericsson | imported from 3GU |
R3‑190755 | TS 38.463 Tabular clean up for Bearer Context messages | Ericsson | imported from 3GU |
R3‑190756 | TS 38.463 ASN.1 corrections | Ericsson | imported from 3GU |
R3‑190757 | Rapporteur corrections for TS 38.463 | Ericsson | imported from 3GU |
R3‑190758 | E1 Setup Request for virtualized CU-UPs | Ericsson | imported from 3GU |
R3‑190759 | E1 Setup Request for virtualized CU-UPs | Ericsson | imported from 3GU |
R3‑190760 | Clarification on new UL TEID request | Ericsson | imported from 3GU |
R3‑190761 | Clarification on new UL TEID request | Ericsson | imported from 3GU |
R3‑190762 | Correction E1 ASN.1 for Maximum Integrity Protected Data Rate | Ericsson | imported from 3GU |
R3‑190763 | Clarification on NRARFCN semantics – TP for XnAP | Ericsson | imported from 3GU |
R3‑190764 | Temporary Identifier usage at interworking | Ericsson | imported from 3GU |
R3‑190765 | Temporary Identifier usage at interworking | Ericsson | imported from 3GU |
R3‑190766 | Extending GUMMEI Type | Ericsson | imported from 3GU |
R3‑190767 | Correction of AMF set related statements | Ericsson | imported from 3GU |
R3‑190768 | Clarification of cardinality for the NG-RAN Architecture | Ericsson | imported from 3GU |
R3‑190769 | Clarification of cardinality for the NG-RAN Architecture | Ericsson | imported from 3GU |
R3‑190770 | Correction of EN-DC related Causes | Ericsson | imported from 3GU |
R3‑190771 | DRB ID co-ordination between MN and SN | Ericsson | imported from 3GU |
R3‑190772 | Correction on DRB ID co-ordination between MN and SN | Ericsson | imported from 3GU |
R3‑190773 | gNB-CU-UP ID | Ericsson | imported from 3GU |
R3‑190774 | NAS PDU in Initial Context Setup | Ericsson | imported from 3GU |
R3‑190775 | NAS PDU in Initial Context Setup | Ericsson | imported from 3GU |
R3‑190776 | NAS PDU order | Ericsson | imported from 3GU |
R3‑190777 | Adding Trace Messages in F1AP | Ericsson | imported from 3GU |
R3‑190778 | Adding Trace Messages in X2AP | Ericsson | imported from 3GU |
R3‑190779 | Change of Interfaces to Trace IE in S1AP | Ericsson | imported from 3GU |
R3‑190780 | Supporting Trace activation/Deactivation in E1AP | Ericsson | imported from 3GU |
R3‑190781 | Regarding support of UE Trace Activation/Deactivation | Ericsson | imported from 3GU |
R3‑190782 | Endianness for the Payload Protocol Identifier | Ericsson | imported from 3GU |
R3‑190783 | Endiannes for the Payload Protocol Identifier in S1 | Ericsson | imported from 3GU |
R3‑190784 | Endiannes for the Payload Protocol Identifier in X2 | Ericsson | imported from 3GU |
R3‑190785 | Endiannes for the Payload Protocol Identifier in Xw | Ericsson | imported from 3GU |
R3‑190786 | Endiannes for the Payload Protocol Identifier in NG | Ericsson | imported from 3GU |
R3‑190787 | Endiannes for the Payload Protocol Identifier in Xn | Ericsson | imported from 3GU |
R3‑190788 | Endiannes for the Payload Protocol Identifier in E1 | Ericsson | imported from 3GU |
R3‑190789 | Endiannes for the Payload Protocol Identifier in F1 | Ericsson | imported from 3GU |
R3‑190790 | Intersystem Data Forwarding – Current status of discussions and way forward | Ericsson | imported from 3GU |
R3‑190791 | [DRAFT] LS on data forwarding for intra and inter-system HO | Ericsson | imported from 3GU |
R3‑190792 | Introduction of direct and indirect data forwarding for inter-system HO between EPS and 5GS | Ericsson | imported from 3GU |
R3‑190793 | Support of Direct Data forwarding for handover between 4G and 5G | Ericsson | imported from 3GU |
R3‑190794 | WI work plan for Rel-16 LTE-MTC | Ericsson | imported from 3GU |
R3‑190795 | MT early data transmission options for LTE-M | Ericsson | imported from 3GU |
R3‑190796 | MT early data transmission indication in Msg4 for LTE-M | Ericsson | imported from 3GU |
R3‑190797 | UP solution for LTE-M MT EDT | Ericsson | imported from 3GU |
R3‑190798 | CP solution for LTE-M MT EDT | Ericsson | imported from 3GU |
R3‑190799 | Data Notification for CioT UEs (LTE-M) | Ericsson | imported from 3GU |
R3‑190800 | CR for Data Notification for CioT UEs (LTE-M) | Ericsson | imported from 3GU |
R3‑190801 | MT early data transmission options for NB-IoT | Ericsson | imported from 3GU |
R3‑190802 | MT early data transmission indication in Msg4 for NB-IoT | Ericsson | imported from 3GU |
R3‑190803 | UP solution for NB-IoT MT EDT | Ericsson | imported from 3GU |
R3‑190804 | CP solution for NB-IoT MT EDT | Ericsson | imported from 3GU |
R3‑190805 | Data Notification for CioT UEs (NB-IoT) | Ericsson | imported from 3GU |
R3‑190806 | Data Notification | Ericsson | imported from 3GU |
R3‑190807 | Enhancement on Intra eNB CP Relocation for NB-IoT | Ericsson | imported from 3GU |
R3‑190808 | Are Tracking Areas Stationary or Not? | Ericsson | imported from 3GU |
R3‑190809 | Correction of figures 5.2-3 and 5.2-4 | Ericsson | imported from 3GU |
R3‑190810 | Network Identities for Non-Terrestrial Networks | Ericsson | imported from 3GU |
R3‑190811 | Considerations on Mobility in Non-Terrestrial Networks | Ericsson | imported from 3GU |
R3‑190812 | Switching the Feeder Link Toward the Satellite | Ericsson | imported from 3GU |
R3‑190813 | DC and NTN - Xn terminated on the ground | Ericsson | imported from 3GU |
R3‑190814 | DC and NTN - Xn over ISL | Ericsson | imported from 3GU |
R3‑190815 | Effective duplication of PDCP PDU | Ericsson | imported from 3GU |
R3‑190816 | Multiple duplicate handling | Ericsson | imported from 3GU |
R3‑190817 | Further discussion on Higher Layer Multi-Connectivity related to the Key Issue 1 | Ericsson | imported from 3GU |
R3‑190818 | Discussion on NR V2X Work Item scope | Ericsson | imported from 3GU |
R3‑190819 | Signaling of UE sidelink AMBR in NG-RAN | Ericsson | imported from 3GU |
R3‑190820 | NR V2X Sidelink Resource pool configuration in NG-RAN | Ericsson | imported from 3GU |
R3‑190821 | Signalling of cross-RAT PC5 and PC5 control parameters in NG-RAN | Ericsson | imported from 3GU |
R3‑190822 | Resource coordination for cross-RAT V2X sidelink communication | Ericsson | imported from 3GU |
R3‑190823 | Scope of Study Item RAN centric Data Collection and Utilization | Ericsson | imported from 3GU |
R3‑190824 | Load sharing and load balancing optimization | Ericsson | imported from 3GU |
R3‑190825 | Enhancements to load sharing and load balance | Ericsson | imported from 3GU |
R3‑190826 | MDT Overview | Ericsson | imported from 3GU |
R3‑190827 | Scope of Coverage and Capacity Optimisation for NR | Ericsson | imported from 3GU |
R3‑190828 | Scope of Coverage and Capacity Optimisation Solution for NR | Ericsson | imported from 3GU |
R3‑190829 | On the challenges of TNL address discovery with the flexible gNB/en-gNB ID length | Ericsson | imported from 3GU |
R3‑190830 | Draft LS requesting for investigation on broadcasting gNB ID length in system information block | Ericsson | imported from 3GU |
R3‑190831 | Discussion on Energy Saving for RAN-centric DCU | Ericsson | imported from 3GU |
R3‑190832 | Mobility robustness optimization in NR | Ericsson | imported from 3GU |
R3‑190833 | Enhancements to radio link failure reporting in NR | Ericsson | imported from 3GU |
R3‑190834 | Reporting RLM related issues upon handover and access to the target cell | Ericsson | imported from 3GU |
R3‑190835 | Status Quo and way forward for UE RRM policy handling | Ericsson | imported from 3GU |
R3‑190836 | Positioning Server Functionality and the NG-RAN | Ericsson | imported from 3GU |
R3‑190837 | Positioning Client Functionality in NG-RAN | Ericsson | imported from 3GU |
R3‑190838 | [DRAFT] Reply LS on Location Service Exposure to NG-RAN | Ericsson | imported from 3GU |
R3‑190839 | Addition of procedural text for Warning Area Coordinates IE | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑190840 | Correction of ASN.1 for PDU Session Resource Modify Response | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑190841 | Correction of ASN.1 for PDU Session Resource Modify Response | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑190842 | Straighten-up SgNB’s request to release and add the same SN-terminated bearer with different DRB ID | Intel Corporation, Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑190843 | Clean-up PDCP SN Length IE and RLC Mode IE | Intel Corporation | imported from 3GU |
R3‑190844 | Clean-up PDCP SN Length IE in X2AP | Intel Corporation | imported from 3GU |
R3‑190845 | Clean-up PDCP SN Length IE in XnAP | Intel Corporation | imported from 3GU |
R3‑190846 | Clean-up PDCP SN Length IE and RLC Mode IE in F1AP | Intel Corporation | imported from 3GU |
R3‑190847 | Support for UL in-order delivery during QoS flow offloading | Intel Corporation | imported from 3GU |
R3‑190848 | Support for UL in-order delivery during QoS flow offloading in XnAP | Intel Corporation | imported from 3GU |
R3‑190849 | Support for UL in-order delivery during QoS flow offloading in stage-2 | Intel Corporation | imported from 3GU |
R3‑190850 | Security protection for Wireless backhaul in IAB | TCL Communication Ltd. | imported from 3GU |
R3‑190851 | Commencement of IEEE P1914.3a Amendment | IEEE 1914 Next Generation Fronthaul Interface (NGFI) Working Group, China Mobile | imported from 3GU |
R3‑190852 | Cause value in RRC fallback case | Huawei | imported from 3GU |
R3‑190853 | Cause value in RRC fallback case | Huawei | imported from 3GU |
R3‑190854 | [Draft] Reply LS on data volume reporting for 5GC | Huawei | imported from 3GU |
R3‑190855 | Data forwarding and QoS flow remapping | Huawei | imported from 3GU |
R3‑190856 | Data forwarding and QoS flow remapping | Huawei | imported from 3GU |
R3‑190857 | Data forwarding and QoS flow remapping | Huawei | imported from 3GU |
R3‑190858 | Data forwarding and QoS flow remapping | Huawei | imported from 3GU |
R3‑190859 | Resource efficient PDCP duplication | Huawei | imported from 3GU |
R3‑190860 | PDCP duplication with more than 2 copies | Huawei | imported from 3GU |
R3‑190861 | Higher layer duplication for IIoT | Huawei | imported from 3GU |
R3‑190862 | TSN synchronization requirements and scenarios | Huawei | imported from 3GU |
R3‑190863 | TSN synchronization solutions | Huawei | imported from 3GU |
R3‑190864 | Qos enhancement for IIoT | Huawei | imported from 3GU |
R3‑190865 | Enforcement of UP integrity protection | Huawei | imported from 3GU |
R3‑190866 | Enforcement of UP integrity protection | Huawei | imported from 3GU |
R3‑190867 | Clarfication on AMF Set | Huawei | imported from 3GU |
R3‑190868 | Correction on Unique 5G-TMSI | Huawei | imported from 3GU |
R3‑190869 | The GUAMI type for EPS/5GS interworking over NG | Huawei | imported from 3GU |
R3‑190870 | The GUAMI type for EPS/5GS interworking over NG | Huawei | imported from 3GU |
R3‑190871 | The GUMMEI order over S1 | Huawei | imported from 3GU |
R3‑190872 | The GUMMEI order over S1 | Huawei | imported from 3GU |
R3‑190873 | S-NSSAI update during EPS to 5GS handover | Huawei | imported from 3GU |
R3‑190874 | S-NSSAI update during EPS to 5GS handover | Huawei | imported from 3GU |
R3‑190875 | S-NSSAI update during EPS to 5GS handover | Huawei | imported from 3GU |
R3‑190876 | S-NSSAI update during EPS to 5GS handover | Huawei | imported from 3GU |
R3‑190877 | Direct data forwarding for inter system handover | Huawei | imported from 3GU |
R3‑190878 | Direct data forwarding for inter system handover | Huawei | imported from 3GU |
R3‑190879 | Direct data forwarding for inter system handover | Huawei | imported from 3GU |
R3‑190880 | Radio capability signalling procedures | Huawei | imported from 3GU |
R3‑190881 | Capability ID storage and usage in NG-RAN | Huawei | imported from 3GU |
R3‑190882 | Further questions on radio capability signalling optimization | Huawei | imported from 3GU |
R3‑190883 | [Draft] Reply LS on radio capability signalling optimization | Huawei | imported from 3GU |
R3‑190884 | Weight factor usage of primary TNL | Huawei | imported from 3GU |
R3‑190885 | Weight factor usage of primary TNL | Huawei | imported from 3GU |
R3‑190886 | QFI descriptions for inter-system handover | Huawei | imported from 3GU |
R3‑190887 | QFI descriptions for inter-system handover | Huawei | imported from 3GU |
R3‑190888 | RAN impact analysis of NPN | Huawei | imported from 3GU |
R3‑190889 | [Draft] Reply LS on RAN impact analysis of NPN | Huawei | imported from 3GU |
R3‑190890 | E-RAB establishment during inter-system handover | Huawei | imported from 3GU |
R3‑190891 | [Draft] Reply LS on E-RAB establishment during inter-system handover | Huawei | imported from 3GU |
R3‑190892 | Notification control during handover | Huawei | imported from 3GU |
R3‑190893 | GUAMI update in case of AMF change | Huawei | imported from 3GU |
R3‑190894 | GUAMI update in case of AMF change | Huawei | imported from 3GU |
R3‑190895 | The ownership of TS 37.461 | ETSI MCC | imported from 3GU |
R3‑190896 | Response to R3-190138 | THALES | imported from 3GU |
R3‑190897 | Response to R3-190644 | THALES | imported from 3GU |
R3‑190898 | Response to R3-190483 | THALES | imported from 3GU |
R3‑190899 | Response to R3-190808 | THALES | imported from 3GU |
R3‑190900 | Response to R3-190163 and R3-190705 | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑190901 | Response to R3-190764 | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑190902 | Response to R3-190680 | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑190903 | Enforcement of UL max IP Data Rate | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑190904 | Enforcement of UL max IP Data Rate | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑190905 | [Draft] Reply LS on RAN impact analysis of NPN | Huawei | imported from 3GU |
R3‑190906 | [DRAFT] Reply LS on Signalling optimization for RRC Inactive N3 path switch | Qualcomm Incorporated | imported from 3GU |
R3‑190907 | LS Response on E-RAB establishment during inter-system handover from 5G to 4G | CATT | imported from 3GU |
R3‑190908 | Workplan for the DC and CA enhancements WI | Ericsson | imported from 3GU |
R3‑190909 | Additional MTC Enhancements for LTE WI session report | Vice-chairman | imported from 3GU |
R3‑190910 | Additional Enhancements for NB-IoT WI session report | Vice-chairman | imported from 3GU |
R3‑190911 | Study on NR Industrial IoT session report | Vice-chairman | imported from 3GU |
R3‑190912 | Study on NR V2X session report | Vice-chairman | imported from 3GU |
R3‑190913 | Study on RAN-Centric Data Collection and Utilization for LTE and NR session report | Vice-chairman | imported from 3GU |
R3‑190914 | [Draft] Reply LS on providing information on SLA fulfilment to NG-RAN | Ericsson | imported from 3GU |
R3‑190915 | Separate UL/DL limits for UE's maximum IP rate | Qualcomm Incorporated | imported from 3GU |
R3‑190916 | Separate UL/DL limits for UE's maximum IP rate | Qualcomm Incorporated | imported from 3GU |
R3‑190917 | Support of integrity protection for Option 4&7 | Huawei | imported from 3GU |
R3‑190918 | Corrections related to Integrity Protection handling at the gNB-CU-UP | NEC | imported from 3GU |
R3‑190919 | NR and E-UTRA UE Radio Capability Signaling Optimizations SI session report | Vice-chairman | imported from 3GU |
R3‑190920 | Multiple TNLA over E1 initialization | Ericsson | imported from 3GU |
R3‑190921 | Transfer of the PSCell information for LI purposes | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑190922 | Transfer of the PSCell information for LI purposes | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑190923 | Transfer of the PSCell information for LI purposes | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑190924 | Transfer of the PSCell information to Core Network | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑190925 | Transfer of the PSCell information to Core Network | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑190926 | NGAP Corrections for UP Security Handling in DC during PDU Session Lifetime | ZTE | imported from 3GU |
R3‑190927 | (Draft) Reply LS on PDCP end user throughput measurements | Nokia | imported from 3GU |
R3‑190928 | Correction of stage 2 for slicing | Nokia, Nokia Shanghai Bell, NTT Docomo Inc. | imported from 3GU |
R3‑190929 | Reply LS on inclusion of NSSAI in RRC connection establishment procedure | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑190930 | Data volume reporting for MR-DC with 5GC | Nokia, Nokia Shanghai Bell, Qualcomm Incorporated, Huawei, Ericsson | imported from 3GU |
R3‑190931 | Data volume reporting for MR-DC with 5GC | Qualcomm Incorporated, Nokia, Nokia Shanghai Bell, Huawei, HiSilicon, Ericsson | imported from 3GU |
R3‑190932 | Data volume reporting for MR-DC with 5GC | Ericsson, Qualcomm Incorporated, Nokia, Nokia Shanghai Bell, Huawei, HiSilicon | imported from 3GU |
R3‑190933 | Stage2 Corrections of Data Volume Report | ZTE | imported from 3GU |
R3‑190934 | Data volume reporting for MR-DC with 5GC | Ericsson | imported from 3GU |
R3‑190935 | Reply LS on data volume reporting for 5GC | Huawei | imported from 3GU |
R3‑190936 | Reply LS on Issues with AS Release Assistance Indicator | Qualcomm Incorporated | imported from 3GU |
R3‑190937 | [DRAFT] Reply LS on UP Integrity Protection for Small Data in Early Data Transfer | Huawei | imported from 3GU |
R3‑190938 | Addition of procedural text for Warning Area Coordinates IE | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑190939 | Summary of offline discussion on TNL Address Discovery for option 3 | Qualcomm Incorporated | imported from 3GU |
R3‑190940 | Introducing NR Neighbour information in X2 Setup | Ericsson | imported from 3GU |
R3‑190941 | Addition and removal of multiple SCTP associations | Intel Corporation | imported from 3GU |
R3‑190942 | Multiple TNLA over E1 transport | Ericsson | imported from 3GU |
R3‑190943 | Multiple TNLA over E1 initialization | Ericsson | imported from 3GU |
R3‑190944 | Summary of offline discussion on multiple TNLAs for E1 and F1 | Ericsson | imported from 3GU |
R3‑190945 | Multiple TNLA over F1 transport | Ericsson | imported from 3GU |
R3‑190946 | Multiple SCTP associations over F1AP | Ericsson | imported from 3GU |
R3‑190947 | Summary of offline discussions on network sharing | InterDigital Communications | imported from 3GU |
R3‑190948 | UAC Summary of offline discussion | Ericsson | imported from 3GU |
R3‑190949 | Summary of offline on discussion on UE Identification over E1 | Nokia | imported from 3GU |
R3‑190950 | Issues to be decided in IAB Stage2 design | KDDI Corporation | imported from 3GU |
R3‑190951 | Correction to Data Forwarding Information IEs | CATT | imported from 3GU |
R3‑190952 | IAB architecture | Ericsson | imported from 3GU |
R3‑190953 | Correction of RAN triggered PDU session split | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑190954 | Correction of RAN triggered PDU session split | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑190955 | Summary of offline discussion on re-mapping during handover | Ericsson | imported from 3GU |
R3‑190956 | Indication that cells are only UL or DL on F1 | Ericsson | imported from 3GU |
R3‑190957 | LTE-NR UE Level Resource Coordination | Qualcomm Incorporated, NTT DOCOMO, INC., T-Mobile USA | imported from 3GU |
R3‑190958 | Clarification on the usage of coordination assistance information | Huawei | imported from 3GU |
R3‑190959 | About Cells Failed to be Activated IE | Ericsson | imported from 3GU |
R3‑190960 | About Cells Failed to be Activated IE in gNB-CU Configuration Update Ack | Ericsson | imported from 3GU |
R3‑190961 | Summary of offline disc (CB: # 31_CellsFailedtoActivateIE) | NEC | imported from 3GU |
R3‑190962 | Cells to be deactivated over F1 | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑190963 | Rapporteur updates for TS 38.413 | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑190964 | Correction of Emergency Fallback | Nokia, Nokia Shanghai Bell, TMO US, Orange | imported from 3GU |
R3‑190965 | Correction of EPS Voice Fallback | Nokia, Nokia Shanghai Bell, Qualcomm Incorporated | imported from 3GU |
R3‑190966 | When NG-RAN node fails to set up a QoS flow for IMS voice | Ericsson | imported from 3GU |
R3‑190967 | Release due to pre-emption | Nokia, Nokia Shanghai Bell, Verizon Wireless | imported from 3GU |
R3‑190968 | Release due to pre-emption | Nokia, Nokia Shanghai Bell, Verizon Wireless | imported from 3GU |
R3‑190969 | NG Setup Correction and UE context retention | Ericsson | imported from 3GU |
R3‑190970 | Remove the second tunnel in the PDU session split, 5GC initiated | Ericsson | imported from 3GU |
R3‑190971 | UE AMBR handling in PDU Session Resouce Setup procedure | Ericsson, Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑190972 | Summary of offline discussion | Ericsson | imported from 3GU |
R3‑190973 | RACH optimization in NR | Ericsson | imported from 3GU |
R3‑190974 | Introduction of direct and indirect data forwarding for inter-system HO between EPS and 5GS | Ericsson | imported from 3GU |
R3‑190975 | [DRAFT] LS on data forwarding for intra and inter-system HO | Ericsson | imported from 3GU |
R3‑190976 | pCR to 37.470 on W1AP functions and procedures | Huawei, TIM, China Unicom | imported from 3GU |
R3‑190977 | Correction to RRC state report | CATT | imported from 3GU |
R3‑190978 | Correction of EPC interworking | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑190979 | Correction of EPC interworking | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑190980 | GUAMI update in case of AMF change | Huawei | imported from 3GU |
R3‑190981 | S-NSSAI update during EPS to 5GS handover | Huawei | imported from 3GU |
R3‑190982 | S-NSSAI update during EPS to 5GS handover | Huawei | imported from 3GU |
R3‑190983 | S-NSSAI update during EPS to 5GS handover | Huawei | imported from 3GU |
R3‑190984 | [Draft LS] LS on N2 Mobility Request/Response procedure | Intel | imported from 3GU |
R3‑190985 | Cause value in RRC fallback case | Huawei | imported from 3GU |
R3‑190986 | Rapporteur updates on version 15.2.0 | Ericsson | imported from 3GU |
R3‑190987 | Correction on gNB-DU Resource Coordination | Huawei | imported from 3GU |
R3‑190988 | Endpoint IP address and port | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑190989 | Correction to reconfiguration with sync for gNB-DU | imported from 3GU | |
R3‑190990 | CR to 38.473 on SRB duplication and LCID | Huawei, ZTE | imported from 3GU |
R3‑190991 | CR to 38.473 on Measurement gap coordination | CATT, ZTE | imported from 3GU |
R3‑190992 | Introduction of PH-InforSCG in DU to CU RRC Information | CATT | imported from 3GU |
R3‑190993 | CR for TS 38.473 for MR-DC coordination | CATT | imported from 3GU |
R3‑190994 | Condition for inclusion of the Dedicated SI Delivery Needed UE List IE | NEC, CATT | imported from 3GU |
R3‑190995 | Correction of the Transmission stop/restart indication | NEC | imported from 3GU |
R3‑190996 | Corrections on gNB-CU-UP/gNB-DU-CP Configuration Update | Huawei, NEC | imported from 3GU |
R3‑190997 | Correction from Rapporteur for 38.401 | NEC | imported from 3GU |
R3‑190998 | CR on RRC container in UE context modification request message | Samsung | imported from 3GU |
R3‑190999 | CR on UE context modification refuse | Samsung | imported from 3GU |
R3‑191000 | Initial UL RRC MESSAGE transfer over F1 | Ericsson | imported from 3GU |
R3‑191001 | Support of IAB | Huawei | imported from 3GU |
R3‑191002 | Adding Trace Messages in F1AP | Ericsson | imported from 3GU |
R3‑191003 | Adding Trace Messages in X2AP | Ericsson | imported from 3GU |
R3‑191004 | Supporting Trace activation/Deactivation in E1AP | Ericsson | imported from 3GU |
R3‑191005 | gNB-DU UE Aggregate Maximum Bit Rate Uplink correction | Ericsson | imported from 3GU |
R3‑191006 | Summary of offline discussion on CB#55 IAB setup | Qualcomm | imported from 3GU |
R3‑191007 | LS on assistance information for TSN traffic flows | RAN2, Nokia | imported from 3GU |
R3‑191008 | Reply LS on RRC cause in RRC reestablishment fallback | RAN2, Intel | imported from 3GU |
R3‑191009 | Correction to RRC transfer | Google Inc. | imported from 3GU |
R3‑191010 | Correction to RRC transfer | Google Inc. | imported from 3GU |
R3‑191011 | Summary of offline discussion on Support for Functionality for Connection to 5GC | ZTE | imported from 3GU |
R3‑191012 | Summary of Discussion on NB-IoT | Huawei | imported from 3GU |
R3‑191013 | LS on responsibility over sections of 37.461 | Nokia | imported from 3GU |
R3‑191014 | TR 30.531 v1.34.0 Work Plan and Working Procedures - RAN WG3 | ETSI MCC | imported from 3GU |
R3‑191015 | CR to 38.473 on transfering UEAssistanceInformation over F1 | Huawei | imported from 3GU |
R3‑191016 | Correction to add paging origin IE | Intel Corporation | imported from 3GU |
R3‑191017 | RRC Reconfiguration failure | Ericsson | imported from 3GU |
R3‑191018 | Support for IAB | Nokia | imported from 3GU |
R3‑191019 | Node behaviour at reception of DU to CU RRC Information | Ericsson | imported from 3GU |
R3‑191020 | TS 38.463 ASN.1 corrections | Ericsson | imported from 3GU |
R3‑191021 | SoD for Data volume reporting clarification | NTT Docomo | imported from 3GU |
R3‑191022 | Summary of offline discussion on TEMP ID USAGE AT INTERWORKING | Ericsson | imported from 3GU |
R3‑191023 | TP for TR38.821 NTN Miscellaneous Corrections | ZTE | imported from 3GU |
R3‑191024 | pCR to 38.821: NTN transport protocol | THALES | imported from 3GU |
R3‑191025 | Clarification on NTN GW | Huawei | imported from 3GU |
R3‑191026 | Network Identities for Non-Terrestrial Networks | Ericsson | imported from 3GU |
R3‑191027 | Tracking Area Management and Paging Handling in NTN | ZTE, Sanechips | imported from 3GU |
R3‑191028 | LS on RAN2 conclusion for NR positioning SI | RAN2, intel | imported from 3GU |
R3‑191029 | Tracking Area and UE position in NTN | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑191030 | NR-NTN: Tracking Area Management | Fraunhofer IIS, Fraunhofer HHI, Ericsson, Thales | imported from 3GU |
R3‑191031 | Considerations on Mobility in Non-Terrestrial Networks | Ericsson | imported from 3GU |
R3‑191032 | NTN feeder link and ISL performances | THALES | imported from 3GU |
R3‑191033 | Correction of EPC interworking | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑191034 | Correction of EPC interworking | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑191035 | Correction of PDU Session Split at Handover | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑191036 | Correction of PDU Session split at handover | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑191037 | Extending GUMMEI Type | Ericsson | imported from 3GU |
R3‑191038 | Energy Saving Support for NR in R15 for TS38.300 | ZTE, China Unicom, CMCC, China Telecom | imported from 3GU |
R3‑191039 | Energy Saving Support over F1 Interface | ZTE, China Telecom, CMCC, China Unicom | imported from 3GU |
R3‑191040 | Proposal for network node interfaces related to UE radio capability transfer | KDDI Corporation, China Telecom | imported from 3GU |
R3‑191041 | Correction of QoS Flow Mapping Indication | Samsung | imported from 3GU |
R3‑191042 | Correction of QoS Flow Mapping Indication | Samsung | imported from 3GU |
R3‑191043 | Correction of QoS Flow Mapping Indication | Samsung | imported from 3GU |
R3‑191044 | Straighten-up SgNB’s request to release and add the same SN-terminated bearer with different DRB ID | Intel Corporation, Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑191045 | TEID change in case of key change | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑191046 | Load Balancing Optimization | CMCC | imported from 3GU |
R3‑191047 | Text proposal for Load Balancing Optimization | CMCC | imported from 3GU |
R3‑191048 | Correction to RRC transfer | Google Inc. | imported from 3GU |
R3‑191049 | Correction to RRC transfer | Google Inc. | imported from 3GU |
R3‑191050 | Desired Activity Notification Level | NEC | imported from 3GU |
R3‑191051 | Correction of Handling PDCP SN during Data Forwarding | Nokia, Nokia Shanghai Bell, NTT Docomo Inc | imported from 3GU |
R3‑191052 | RAN Paging failure on E1 | Ericsson | imported from 3GU |
R3‑191053 | Correction on TAI Support List | Huawei | imported from 3GU |
R3‑191054 | Correction on partial reset | Huawei | imported from 3GU |
R3‑191055 | Support of PDU session split during handover procedure | CATT,Huawei | imported from 3GU |
R3‑191056 | Support of PDU session split during handover procedure | CATT,Huawei | imported from 3GU |
R3‑191057 | Merged TP for V2X | Huawei | imported from 3GU |
R3‑191058 | Correction of AMF set related statements | Ericsson | imported from 3GU |
R3‑191059 | Correction on AMF connectivity | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑191060 | Potential agreements of V2X in RAN3#103 | LGE | imported from 3GU |
R3‑191061 | Missing causes for context retrieval failure | Qualcomm Incorporated | imported from 3GU |
R3‑191062 | Way forward concerning the Desired Buffer Size | Nokia | imported from 3GU |
R3‑191063 | Final Frame Indication in NR-UP | NEC | imported from 3GU |
R3‑191064 | Text proposals for the agreed use case description | CMCC | imported from 3GU |
R3‑191065 | Correction to Data Forwarding Information IEs | CATT | imported from 3GU |
R3‑191066 | Way forward on positioning NR Study | Huawei | imported from 3GU |
R3‑191067 | CR to TS 38.463 on inactivity timer over E1 | Huawei | imported from 3GU |
R3‑191068 | CR to 38.460 on inactivity notification over E1 | Huawei | imported from 3GU |
R3‑191069 | E1 Setup Request for virtualized CU-UPs | Ericsson | imported from 3GU |
R3‑191070 | LS response to SA2 on unicast, groupcast and broadcast in NR sidelink | RAN2, Huawei | imported from 3GU |
R3‑191071 | Merged TP for V2X | Huawei | imported from 3GU |
R3‑191072 | LS to RAN1 on RAN3 agreement on V2X | LGE | imported from 3GU |
R3‑191073 | XnAP Correction of PDU Session Resource Setup Response Info - MN terminated | ZTE | imported from 3GU |
R3‑191074 | XnAP Correction of PDU Session Resource Setup Complete Info - SN terminated | ZTE | imported from 3GU |
R3‑191075 | NAS PDU order | Ericsson | imported from 3GU |
R3‑191076 | IAB BL CR to 36.423 | Samsung | imported from 3GU |
R3‑191077 | RAN aspects of the TSN performance evaluation | Nokia, Nokia Shanghai Bell, Qualcomm Incorporated | imported from 3GU |
R3‑191078 | Support for IAB | Huawei | imported from 3GU |
R3‑191079 | Introduction of TNL Address discovery for EN-DC | Qualcomm Incorporated, Huawei, Nokia, Nokia Shanghai Bell, Ericsson, ZTE | imported from 3GU |
R3‑191080 | Introduction of TNL Address discovery for EN-DC (using new container) | Ericsson, Huawei, Nokia, Nokia Shanghai Bell, Qualcomm Incorporated, ZTE | imported from 3GU |
R3‑191081 | Introduction of TNL Address discovery for EN-DC (using legacy container) | Ericsson, Huawei, Nokia, Nokia Shanghai Bell, Qualcomm Incorporated, ZTE | imported from 3GU |
R3‑191082 | Introduction of TNL Address discovery for EN-DC (using new container) | Nokia, Nokia Shanghai Bell, ZTE, Ericsson, Qualcomm Incorporated, Huawei | imported from 3GU |
R3‑191083 | Introduction of TNL Address discovery for EN-DC (using legacy container) | Nokia, Nokia Shanghai Bell, ZTE, Ericsson, Qualcomm Incorporated, Huawei | imported from 3GU |
R3‑191084 | Introduction of TNL Address discovery for EN-DC (using new container) | Qualcomm Incorporated, Nokia, Nokia Shanghai Bell, Ericsson, Huawei, ZTE | imported from 3GU |
R3‑191085 | Introduction of TNL Address discovery for EN-DC (using legacy container) | Qualcomm Incorporated, Nokia, Nokia Shanghai Bell, Ericsson, Huawei, ZTE | imported from 3GU |
R3‑191086 | [DRAFT] LS on Completion of X2 TNL Address Discovery for EN-DC | Qualcomm Incorporated | imported from 3GU |
R3‑191087 | Resource efficient PDCP duplication | Huawei | imported from 3GU |
R3‑191088 | Discussion on impacts of Higher Layer Multi-Connectivity | CATT | imported from 3GU |
R3‑191089 | RAN3 conclusion on NR positionning study | Huawei | imported from 3GU |
R3‑191090 | Reply to: LS on RAN2 conclusion for NR positioning SI | Intel | imported from 3GU |
R3‑191091 | Reply LS on providing information on SLA fulfilment to NG-RAN | Ericsson | imported from 3GU |
R3‑191092 | Reply to: Reporting All Cell IDs in 5G | Nokia | imported from 3GU |
R3‑191093 | Adding the transfer of the PSCell information for LI purposes | Nokia | imported from 3GU |
R3‑191094 | UE Identification over E1 | Nokia, Nokia Shanghai Bell, Verizon Wireless, Samsung, KDDI. AT&T | imported from 3GU |
R3‑191095 | Common Xn link for network sharing | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑191096 | Common X2 instance between eNB and shared en-gNB | Nokia, Nokia Shanghai Bell, KDDI, China Telecom, Bell, CATT, ZTE, Huawei, Samsung | imported from 3GU |
R3‑191097 | F1 Served Cell Information | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑191098 | CR on RRC container in UE context modification request message | Samsung | imported from 3GU |
R3‑191099 | CR on UE context modification refuse | Samsung | imported from 3GU |
R3‑191100 | Report from offline discussions on inter-system direct data forwarding | Ericsson | imported from 3GU |
R3‑191101 | Reply LS on RAN impact analysis of NPN | Huawei | imported from 3GU |
R3‑191102 | Reply LS on Signalling optimization for RRC Inactive N3 path switch | Qualcomm Incorporated | imported from 3GU |
R3‑191103 | LS Response on E-RAB establishment during inter-system handover from 5G to 4G | CATT | imported from 3GU |
R3‑191104 | LS on Conclusion of NR V2X and Agreed TP for TR 38.885 | LGE | imported from 3GU |
R3‑191105 | Transfer of the PSCell information for LI purposes | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑191106 | Transfer of the PSCell information for LI purposes | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑191107 | Transfer of the PSCell information to Core Network | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑191108 | RAN3 conclusions for the NR_IIoT study item | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑191109 | Transfer of the PSCell information to Core Network | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑191110 | NAS PDU order | Ericsson | imported from 3GU |
R3‑191111 | Reply to: Reporting All Cell IDs in 5G | Nokia | imported from 3GU |
R3‑191112 | Common Xn link for network sharing | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑191113 | Common X2 instance between eNB and shared en-gNB | Nokia, Nokia Shanghai Bell, KDDI, China Telecom, Bell, CATT, ZTE, Huawei, Samsung, CMCC, LG elecronics | imported from 3GU |
R3‑191114 | F1 Served Cell Information | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑191115 | Correction of stage 2 for slicing | Nokia, Nokia Shanghai Bell, NTT Docomo Inc. | imported from 3GU |
R3‑191116 | Reply LS on UP Integrity Protection for Small Data in Early Data Transfer | Huawei | imported from 3GU |
R3‑191117 | Introduction of TNL Address discovery for EN-DC (using new container) | Nokia, Nokia Shanghai Bell, ZTE, Ericsson, Qualcomm Incorporated, Huawei | imported from 3GU |
R3‑191118 | Introduction of TNL Address discovery for EN-DC (using legacy container) | Nokia, Nokia Shanghai Bell, ZTE, Ericsson, Qualcomm Incorporated, Huawei | imported from 3GU |
R3‑191119 | [DRAFT] LS on Completion of X2 TNL Address Discovery for EN-DC | Qualcomm Incorporated | imported from 3GU |
R3‑191120 | Paging Failure | Nokia, Nokia Shanghai Bell, NEC, LG Electronics | imported from 3GU |
R3‑191121 | Correction of PDU Session split at handover | Nokia, Nokia Shanghai Bell, Huawei, ZTE | imported from 3GU |
R3‑191122 | Introduction of Core Network Type Restrictions to EPC | Huawei | imported from 3GU |
R3‑191123 | Summary of offline discussion on multiple SCTP for NG | Intel | imported from 3GU |
R3‑191124 | Introduction of TNL Address discovery for EN-DC (using new container) | Qualcomm Incorporated, Nokia, Nokia Shanghai Bell, Ericsson, Huawei, ZTE | imported from 3GU |
R3‑191125 | Introduction of TNL Address discovery for EN-DC (using legacy container) | Qualcomm Incorporated, Nokia, Nokia Shanghai Bell, Ericsson, Huawei, ZTE | imported from 3GU |
R3‑191126 | Cells to be deactivated over F1 | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑191127 | Introduction of direct and indirect data forwarding for inter-system HO between EPS and 5GS | Ericsson | imported from 3GU |
R3‑191128 | Multiple SCTPs in NG-RAN | Nokia | imported from 3GU |
R3‑191129 | TP for TR38.821 NTN Miscellaneous Corrections | ZTE | imported from 3GU |
R3‑191130 | NGAP Corrections for UP Security Handling in DC during PDU Session Lifetime | ZTE | imported from 3GU |
R3‑191131 | Correction of EPC interworking | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑191132 | Correction of EPC interworking | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑191133 | Correction of EPC interworking | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑191134 | Correction of EPC interworking | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑191135 | S-NSSAI update during EPS to 5GS handover | Huawei | imported from 3GU |
R3‑191136 | S-NSSAI update during EPS to 5GS handover | Huawei | imported from 3GU |
R3‑191137 | S-NSSAI update during EPS to 5GS handover | Huawei | imported from 3GU |
R3‑191138 | LS on N2 Mobility Request/Response procedure | Intel | imported from 3GU |
R3‑191139 | Support of IAB | Huawei | imported from 3GU |
R3‑191140 | Condition for inclusion of the Dedicated SI Delivery Needed UE List IE | NEC, CATT | imported from 3GU |
R3‑191141 | LS on RAN2 conclusion for NR positioning SI | Intel | imported from 3GU |
R3‑191142 | Corrections on gNB-CU-UP/gNB-DU-CP Configuration Update | Huawei, NEC | imported from 3GU |
R3‑191143 | Support of IAB | Huawei | imported from 3GU |
R3‑191144 | IAB BL CR to 36.423 | Samsung | imported from 3GU |
R3‑191145 | LS on responsibility over sections of 37.461 | Nokia | imported from 3GU |
R3‑191146 | pCR to 38.821: NTN transport protocol | THALES | imported from 3GU |
R3‑191147 | CR to 38.423 for adding AMF Set Information in XN SETUP RESPONSE | Huawei | imported from 3GU |
R3‑191148 | Energy Saving Support for NR in R15 for TS38.300 | ZTE, China Unicom, CMCC, China Telecom | imported from 3GU |
R3‑191149 | Correction of QoS Flow Mapping Indication | Samsung | imported from 3GU |
R3‑191150 | Correction of QoS Flow Mapping Indication | Samsung | imported from 3GU |
R3‑191151 | Correction of QoS Flow Mapping Indication | Samsung | imported from 3GU |
R3‑191152 | Adding Trace Messages in X2AP | Ericsson | imported from 3GU |
R3‑191153 | Correction to RRC transfer | Google Inc. | imported from 3GU |
R3‑191154 | Correction to RRC transfer | Google Inc. | imported from 3GU |
R3‑191155 | Support of integrity protection for Option 4&7 | Huawei | imported from 3GU |
R3‑191156 | NGAP Corrections for UP Security Handling in DC during PDU Session Lifetime | ZTE | imported from 3GU |
R3‑191157 | Separate UL/DL limits for UE's maximum IP rate | Qualcomm Incorporated, Nokia, Nokia Shanghai Bell, NEC | imported from 3GU |
R3‑191158 | Separate UL/DL limits for UE's maximum IP rate | Qualcomm Incorporated, Nokia, Nokia Shanghai Bell, NEC | imported from 3GU |
R3‑191159 | Addition and removal of multiple SCTP associations | Intel Corporation | imported from 3GU |
R3‑191160 | Correction of PDU Session split at handover | Nokia, Nokia Shanghai Bell, Huawei, ZTE | imported from 3GU |
R3‑191161 | Support of PDU session split during handover procedure | CATT,Huawei | imported from 3GU |
R3‑191162 | LTE-NR UE Level Resource Coordination | Qualcomm Incorporated, NTT DOCOMO, INC., T-Mobile USA | imported from 3GU |
R3‑191163 | pCR to 37.470 on W1AP functions and procedures | Huawei, TIM, China Unicom | imported from 3GU |
R3‑191164 | Multiple TNLA over F1 transport | Ericsson | imported from 3GU |
R3‑191165 | Multiple SCTP associations over F1AP | Ericsson, ZTE | imported from 3GU |
R3‑191166 | Multiple TNLA over E1 transport | Ericsson | imported from 3GU |
R3‑191167 | Draft TR 38.821 v | Thales | imported from 3GU |
R3‑191168 | Reply LS on RAN impact analysis of NPN | Huawei | imported from 3GU |
page generated from database: 2024-04-22 07:58:53