3GPP TDocs (written contributions) at meeting
Meeting: R3-103b - 2019-04-08 to 2019-04-12, Xi'an
meeting id: R3-103b (click id for more info on this meeting)Click on the Tdoc to open its file.
| TDoc | Title | Source | Remarks |
|---|---|---|---|
| R3‑191170 | RAN3#103Bis Meeting Agenda | Chairman (Ericsson) | imported from 3GU |
| R3‑191171 | RAN3#103 Meeting report | ETSI MCC | imported from 3GU |
| R3‑191172 | BL CR to 38.413: Support for IAB | Nokia Shanghai Bell | imported from 3GU |
| R3‑191173 | BL CR to 36.413: Support for IAB | Huawei | imported from 3GU |
| R3‑191174 | BL CR to 38.401: Support of IAB | Huawei | imported from 3GU |
| R3‑191175 | BL CR to 36.423: Support of IAB | Samsung | imported from 3GU |
| R3‑191176 | BL CR to 38.300: Introduction of direct and indirect data forwarding for inter-system HO between EPS and 5GS | Ericsson | imported from 3GU |
| R3‑191177 | LS on reporting all Cell IDs in 5G | 3GPP CT1, Qualcomm | imported from 3GU |
| R3‑191178 | Reply LS on PARLOS RAN impacts | 3GPP CT1, Motorola | imported from 3GU |
| R3‑191179 | Reply LS on Interim conclusions for SA2 study on Radio Capabilities Signalling Optimisations (FS_RACS) | 3GPP CT4, Huawei | imported from 3GU |
| R3‑191180 | Reply LS on Completion of X2 TNL Address Discovery for EN-DC | 3GPP CT4, Nokia | imported from 3GU |
| R3‑191181 | Reply LS on Completion of X2 TNL Address Discovery for EN-DC | 3GPP TSG CT, Orange | imported from 3GU |
| R3‑191182 | LS on completion of CLI-RIM in RAN1 | 3GPP RAN1, China Mobile | imported from 3GU |
| R3‑191183 | LS on UE-UE CLI measurement/reporting and Network coordination mechanism for CLI | 3GPP RAN1, LGE | imported from 3GU |
| R3‑191184 | LS on initial access SSB periodicity assumption for IAB MT | 3GPP RAN1, Qualcomm | imported from 3GU |
| R3‑191185 | Reply LS on RAN related parameters collected from UE | 3GPP RAN1, Huawei | imported from 3GU |
| R3‑191186 | Reply LS on RAN Impact analysis due to TSN | 3GPP RAN2, Ericsson | imported from 3GU |
| R3‑191187 | Reply LS on TSN integration in the 5G System | 3GPP RAN2, Nokia | imported from 3GU |
| R3‑191188 | Response LS on on eDRX cycles for CM-CONNECTED with RRC inactive | 3GPP RAN2, Qualcomm | imported from 3GU |
| R3‑191189 | Response LS on Completion of Study on Cellular IoT support and evolution for the 5G System | 3GPP RAN2, Qualcomm | imported from 3GU |
| R3‑191190 | Reply LS on EDT integrity protection | 3GPP RAN2, Huawei | imported from 3GU |
| R3‑191191 | Reply LS on RAT selection for SL | 3GPP RAN2, LGE | imported from 3GU |
| R3‑191192 | Reply LS on PARLOS RAN impacts | 3GPP RAN2, Nokia | imported from 3GU |
| R3‑191193 | Reply LS on Enforcement of maximum supported data rate for integrity protection | 3GPP RAN2, Intel | imported from 3GU |
| R3‑191194 | Reply LS on RAN Impact analysis due to NPN | 3GPP RAN2, Huawei | imported from 3GU |
| R3‑191195 | Response LS on inclusion of selected PLMN into the complete message | 3GPP RAN2, Vivo | imported from 3GU |
| R3‑191196 | Reply LS on UE capability ID related progress | 3GPP RAN2, Ericsson | imported from 3GU |
| R3‑191197 | LS on L1 and L2 measurements | 3GPP RAN2, Huawei | imported from 3GU |
| R3‑191198 | LS on UE feature list for NR | 3GPP RAN4, NTT Docomo | imported from 3GU |
| R3‑191199 | LS on FR1 range | 3GPP RAN4, Ericsson | imported from 3GU |
| R3‑191200 | LS on NG-RAN Network Sharing completion | 3GPP TSG RAN, Huawei | imported from 3GU |
| R3‑191201 | Reply LS on EPS Additional RRM Policy Index | 3GPP TSG RAN, Vodafone | imported from 3GU |
| R3‑191202 | Response LS on Completion of Study on Cellular IoT support and evolution for the 5G System, and LS on Signalling optimization for RRC Inactive N3 path switch | 3GPP TSG RAN, Qualcomm | imported from 3GU |
| R3‑191203 | LS reply on RRC cause in RRC reestablishment fallback | 3GPP SA2, Intel | imported from 3GU |
| R3‑191204 | LS on Transport Level Packet Marking | 3GPP SA2, Perspecta labs | imported from 3GU |
| R3‑191205 | LS reply on the slicing terminology and the role of S-NSSAI parameter | 3GPP SA2, Ericsson | imported from 3GU |
| R3‑191206 | LS on Completion of FS_RACS study | 3GPP SA2, Qualcomm | imported from 3GU |
| R3‑191207 | LS on QoS Support for eV2X over Uu interface | 3GPP SA2, Huawei | imported from 3GU |
| R3‑191208 | LS on Automatic Restoration of GFBR QOS | 3GPP SA2, Vodafone | imported from 3GU |
| R3‑191209 | LS on EPS Additional RRM Policy Index | 3GPP SA2, Vodafone | imported from 3GU |
| R3‑191210 | Discussion on AMF information | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑191211 | Correction on AMF connectivity | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑191212 | Some Residual Issues with PDU Session Split | ZTE | imported from 3GU |
| R3‑191213 | Use case for user position prediction based on RAN centric-data utilization | BUPT | imported from 3GU |
| R3‑191214 | Various Clean-ups for TS37.340 | ZTE | imported from 3GU |
| R3‑191215 | Further Discussion on RAN Initiated PDU Session Split | ZTE | imported from 3GU |
| R3‑191216 | Use case for user position prediction based on RAN centric-data utilization | BUPT | imported from 3GU |
| R3‑191217 | Introduction of PDU Session split with SN initiated SN modification procedure | ZTE | imported from 3GU |
| R3‑191218 | NTN feeder link performances justification | THALES | imported from 3GU |
| R3‑191219 | NTN multi connectivity | THALES | imported from 3GU |
| R3‑191220 | XnAP Alignment of MN Triggered PDU Session Split | ZTE | imported from 3GU |
| R3‑191221 | NGAP Further Clarification of S-NSSAI Update for EPS to 5GS HO | ZTE | imported from 3GU |
| R3‑191222 | XnAP Further Clarification of S-NSSAI Update for EPS to 5GS HO | ZTE | imported from 3GU |
| R3‑191223 | Selective DL PDCP duplication for URLLC | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑191224 | Correction of the RRC Config Indicator | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑191225 | Correction of the NR UP | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑191226 | Correction of the references to the GTP tunnel endpoint information | Nokia, Nokia Shanghai Bell, ZTE (rapporteur) | imported from 3GU |
| R3‑191227 | Correction of the interpretation of the desired buffer size | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑191228 | Logical Architecture and RAN Sharing | InterDigital Germany GmbH | imported from 3GU |
| R3‑191229 | Work Plan for NR Industrial IoT WI | Nokia (Rapporteur) | imported from 3GU |
| R3‑191230 | NGAP Clarification of Location Reporting Request Type | ZTE | imported from 3GU |
| R3‑191231 | NGAP Clarification of Location Reporting Request Type | ZTE | imported from 3GU |
| R3‑191232 | Some Potential Enhancement for ULI Report in MR-DC@5GC | ZTE | imported from 3GU |
| R3‑191233 | Discussion on TSC Pattern info transfer | CATT | imported from 3GU |
| R3‑191234 | Location based Paging procedure | CATT | imported from 3GU |
| R3‑191235 | Discussion on SRI change | CATT | imported from 3GU |
| R3‑191236 | Open Issue on Frequent Feeder Link Switch | CATT | imported from 3GU |
| R3‑191237 | Considerations on MT setup | CATT | imported from 3GU |
| R3‑191238 | IAB Backhaul RLF recovery | CATT | imported from 3GU |
| R3‑191239 | IAB BH RLF Indication | CATT | imported from 3GU |
| R3‑191240 | RACS work plan | CATT | imported from 3GU |
| R3‑191241 | TSC Deterministic QoS | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑191242 | CR to 38.413 on support of signalling the configured slice information to NG-RAN | China Telecommunication | imported from 3GU |
| R3‑191243 | CR37340 for correction on the usage of SN Reconfiguration Completion | ZTE | imported from 3GU |
| R3‑191244 | CR37340 for In-order delivery for MR-DC | ZTE, Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑191245 | Discussion on PDU Session Resource Modify Indication | ZTE | imported from 3GU |
| R3‑191246 | CR38413 for Correction on PDU Session Resource Modify Indication | ZTE | imported from 3GU |
| R3‑191247 | CR38413 for Clarification on PDU Session resource modify | ZTE | imported from 3GU |
| R3‑191248 | Discussion on PCI confusing in case of Pscell change due to Pcell change | ZTE, NEC | imported from 3GU |
| R3‑191249 | CR36423 for Addition of MN (MeNB) cell ID to solve the PCI confusion in SN(SgNB) modification Request messag | ZTE, Samsung, NEC | imported from 3GU |
| R3‑191250 | CR38423 for Addition of MN (MeNB) cell ID to solve the PCI confusion in SN(SgNB) modification Request message | ZTE, Samsung, NEC | imported from 3GU |
| R3‑191251 | On direct data forwarding for inter-RAT handover | China Telecommunication | imported from 3GU |
| R3‑191252 | XnAP Correction of PDU Session Resource Setup Response Info – MN terminated | ZTE | imported from 3GU |
| R3‑191253 | XnAP Correction of PDU Session Resource Setup Complete Info – SN terminated | ZTE | imported from 3GU |
| R3‑191254 | XnAP Corrections of S-NG-RAN node Maximum Integrity Protected Data Rate UL&DL | ZTE | imported from 3GU |
| R3‑191255 | XnAP Correction of Xn-U Address Indication Procedure | ZTE | imported from 3GU |
| R3‑191256 | Consideration on MT EDT supporting | Huawei | imported from 3GU |
| R3‑191257 | Introduction of CIoT CP solution | Huawei | imported from 3GU |
| R3‑191258 | Consideration on eDRX supporting | Huawei | imported from 3GU |
| R3‑191259 | Support of MO EDT in CP and UP solutions | Huawei | imported from 3GU |
| R3‑191260 | Support of Inter UE QoS | Huawei | imported from 3GU |
| R3‑191261 | Support of Enhanced Coverage | Huawei | imported from 3GU |
| R3‑191262 | Support of Expected UE Behavior information | Huawei | imported from 3GU |
| R3‑191263 | SON Supporting for Reporting | Huawei | imported from 3GU |
| R3‑191264 | Some Residual Issues with Secondary RAT DVR | ZTE | imported from 3GU |
| R3‑191265 | Stage2 Various Clarifications of DVR Behaviors | ZTE | imported from 3GU |
| R3‑191266 | Proceeding Clean-ups of Term-Secondary RAT Data Usage Report | ZTE | imported from 3GU |
| R3‑191267 | Proceeding Clean-ups of Term-Secondary RAT Data Usage Report | ZTE | imported from 3GU |
| R3‑191268 | Further Discussion on Rel-15 Signaling Extensibility for Multi-Connectivity | ZTE | imported from 3GU |
| R3‑191269 | CSI-RS configuration transfer over Xn | Huawei, Ericsson | imported from 3GU |
| R3‑191270 | LS on CSI-RS configuration transfer over Xn | Huawei | imported from 3GU |
| R3‑191271 | RAN paging failure handling in SN in case of MR-DC | Huawei, NEC | imported from 3GU |
| R3‑191272 | XnAP Corrections of TNL Info for Cell Groups | ZTE | imported from 3GU |
| R3‑191273 | TP for data_fw BL CR for TS 38.300 Further Stage2 Clarifications for Inter-System Direct DF | ZTE | imported from 3GU |
| R3‑191274 | Discussion on Inter-Operatability between 4G5G Direct and Indirect DF | ZTE | imported from 3GU |
| R3‑191275 | DraftLS on Inter-Operatability between 4G/5G Direct and Indirect DF | ZTE | imported from 3GU |
| R3‑191276 | pCR for TR38.821 Corrections of NTN Applicable Mobility Procedures | ZTE | imported from 3GU |
| R3‑191277 | Further Discussion on Satellite Mobility Impacts on NTN Interfaces | ZTE | imported from 3GU |
| R3‑191278 | Possible Dual Connectivity or Interworking without Xn Interface | ZTE | imported from 3GU |
| R3‑191279 | Consideration on Routing in IAB | ZTE Corporation, Sanechips | imported from 3GU |
| R3‑191280 | Consideration on IP Address Allocation in IAB | ZTE Corporation, Sanechips | imported from 3GU |
| R3‑191281 | Consideration on user plane solution for connection to 5GC | ZTE | imported from 3GU |
| R3‑191282 | Discussion on Presence of Paging DRX IE | NEC | imported from 3GU |
| R3‑191283 | Correction of Presence of Paging DRX IE | NEC | imported from 3GU |
| R3‑191284 | Xn Signalling for Bearer Type Selection at the SN | NEC | imported from 3GU |
| R3‑191285 | Bearer Type Selection for SN Terminated Bearers in MR-DC | NEC | imported from 3GU |
| R3‑191286 | Correction on UE Maximum Integrity Protected Data Rate | NEC | imported from 3GU |
| R3‑191287 | Correction on UE Maximum Integrity Protected Data Rate | NEC | imported from 3GU |
| R3‑191288 | Correction on Transaction ID in Error Indication Procedure | NEC | imported from 3GU |
| R3‑191289 | Correction on Transaction ID in Error Indication Procedure | NEC | imported from 3GU |
| R3‑191290 | Inter-gNB-DU mobility using MCG SRB procedure | NEC, NTT DOCOMO, INC. | imported from 3GU |
| R3‑191291 | Inter-gNB-DU mobility using MCG SRB procedure | NEC, NTT DOCOMO, INC. | imported from 3GU |
| R3‑191292 | RRC config indication behaviour | NEC, NTT DOCOMO, INC. | imported from 3GU |
| R3‑191293 | RRC config indication behaviour | NEC, NTT DOCOMO, INC. | imported from 3GU |
| R3‑191294 | Transferring of NR RRC message in MeNB | NEC | imported from 3GU |
| R3‑191295 | Transferring of NR RRC message in MeNB | NEC, Google Inc. | imported from 3GU |
| R3‑191296 | IAB node integration | ZTE,Sanechips | imported from 3GU |
| R3‑191297 | Control plane signaling delivery in NSA deployment | ZTE Corporation, Sanechips | imported from 3GU |
| R3‑191298 | Discussion on network-controlled IAB migration handling | ZTE Corporation, Sanechips | imported from 3GU |
| R3‑191299 | Discussion on BH RLC channel configuration in IAB network | ZTE Corporation, Sanechips | imported from 3GU |
| R3‑191300 | Discussion on flow control in IAB | ZTE Corporation, Sanechips | imported from 3GU |
| R3‑191301 | MR-DC resource coordination in F1 | Qualcomm Incorporated | imported from 3GU |
| R3‑191302 | XN-U Address Indication in RRC resume | Qualcomm Incorporated | imported from 3GU |
| R3‑191303 | TDD configuration exchange over Xn for CLI | Qualcomm Incorporated | imported from 3GU |
| R3‑191304 | TDD configuration exchange over F1 for CLI | Qualcomm Incorporated | imported from 3GU |
| R3‑191305 | Transparent Backhaul Coordination via CN | Qualcomm Incorporated | imported from 3GU |
| R3‑191306 | Transparent Backhaul Coordination via CN (38.413 CR) | Qualcomm Incorporated | imported from 3GU |
| R3‑191307 | Delay measurement | Qualcomm Incorporated | imported from 3GU |
| R3‑191308 | eNA interworking | Qualcomm Incorporated | imported from 3GU |
| R3‑191309 | Throughput measurement | Qualcomm Incorporated | imported from 3GU |
| R3‑191310 | Reuse R15 signal for energy saving | Qualcomm Incorporated | imported from 3GU |
| R3‑191311 | Mobility optimization | Qualcomm Incorporated | imported from 3GU |
| R3‑191312 | Discussion of MDT for RRC_INACTIVE | Qualcomm Incorporated | imported from 3GU |
| R3‑191313 | Discussion of UE consent in MDT | Qualcomm Incorporated | imported from 3GU |
| R3‑191314 | IAB WI workplan | Qualcomm Incorporated (Rapporteur) | imported from 3GU |
| R3‑191315 | Report email discussion 105#45 RAN2+3 IAB misc | Qualcomm Incorporated (Rapporteur) | imported from 3GU |
| R3‑191316 | IP routing between IAB and operator network | Qualcomm Incorporated | imported from 3GU |
| R3‑191317 | IAB IP address allocation | Qualcomm Incorporated | imported from 3GU |
| R3‑191318 | IAB-node indication to CN | Qualcomm Incorporated | imported from 3GU |
| R3‑191319 | OAM connectivity for IAB-node | Qualcomm Incorporated | imported from 3GU |
| R3‑191320 | Revisiting the functionality for UE’s maximum IP rate | Qualcomm Incorporated | imported from 3GU |
| R3‑191321 | Fine tuning of user plane security control in MR-DC | Qualcomm Incorporated | imported from 3GU |
| R3‑191322 | Correction to behaviour of SN for integrity protection with options 4 and 7 | Qualcomm Incorporated | imported from 3GU |
| R3‑191323 | Support for delivering UE band information in RAN paging | Qualcomm Incorporated | imported from 3GU |
| R3‑191324 | On User Plane Small Data Solution | Qualcomm Incorporated | imported from 3GU |
| R3‑191325 | Introduction of CP-CIoT support in NGAP | Qualcomm Incorporated | imported from 3GU |
| R3‑191326 | Potential impacts of idle mode eDRX in 5GS on RAN3 specifications | Qualcomm Incorporated | imported from 3GU |
| R3‑191327 | Further discussion on impacts of MT EDT on RAN3 specifications | Qualcomm Incorporated | imported from 3GU |
| R3‑191328 | Transmission Measurement Function for NG-RAN Positioning | Qualcomm Incorporated | imported from 3GU |
| R3‑191329 | Consideration on RAN3 impacts for MT EDT | ZTE | imported from 3GU |
| R3‑191330 | Correction of RAN triggered PDU session split | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑191331 | Correction of RAN triggered PDU session split | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑191332 | Correction of Core Network Type restriction | Nokia, Nokia Shanghai Bell, Huawei | imported from 3GU |
| R3‑191333 | Correction of Core Network Type restriction | Nokia, Nokia Shanghai Bell, Huawei | imported from 3GU |
| R3‑191334 | Correction of Core Network Type restriction | Nokia, Nokia Shanghai Bell, Huawei | imported from 3GU |
| R3‑191335 | Correction of handover 5g to 4g | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑191336 | Correction of handover 5g to 4g | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑191337 | Correction of NAS PDU | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑191338 | Correction of NAS PDU | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑191339 | Correction of NAS PDU | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑191340 | Correction of PDU Session Release | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑191341 | Correction of PDU Session Release | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑191342 | Correction of CN Assistance Information | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑191343 | Correction of CN Assistance Information | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑191344 | Correction of Network Instance | Nokia, Nokia Shanghai Bell, Huawei, Orange, China Unicom, China Telecom | imported from 3GU |
| R3‑191345 | Correction of Network Instance | Nokia, Nokia Shanghai Bell, Huawei, Orange, China Unicom, China Telecom | imported from 3GU |
| R3‑191346 | Correction of Network Instance | Nokia, Nokia Shanghai Bell, Huawei, Orange, China Unicom, China Telecom | imported from 3GU |
| R3‑191347 | (TP for data_fw BL CR for TS 38.300) Correction of direct data forwarding | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑191348 | LS on Handling of Direct Data Forwarding | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑191349 | Introduction of direct data forwarding in stage 3 | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑191350 | Introduction of direct data forwarding | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑191351 | Solutions for MT EDT use cases | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑191352 | RAN3 functions for MTC and NB-IOT connected to 5GC | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑191353 | Introduction of NB-IOT support to 5GC | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑191354 | CR TS 38.470 IAB General Aspects | Ericsson | imported from 3GU |
| R3‑191355 | CR TS 38.473 IAB General Aspects | Ericsson | imported from 3GU |
| R3‑191356 | IAB Node Release Procedure | Ericsson | imported from 3GU |
| R3‑191357 | (TP for NR-IAB BL CR for TS 38.401) IAB node Integration Procedure | Ericsson | imported from 3GU |
| R3‑191358 | QoS Mapping to Backhaul Bearers in IAB Networks | Ericsson | imported from 3GU |
| R3‑191359 | (TP for NR-IAB BL CR for TS 38.401) Backhaul Channel Setup and Modification Procedure for IAB Networks | Ericsson | imported from 3GU |
| R3‑191360 | Reuse of UE Context Management procedures for IAB-node (MT) contexts | Ericsson | imported from 3GU |
| R3‑191361 | CR TS 38.473 Reuse of UE Context Management Procedures for IAB-node (MT) Contexts | Ericsson | imported from 3GU |
| R3‑191362 | F1AP Stage-3 Aspects of IAB BH RLC Channel Management | Ericsson | imported from 3GU |
| R3‑191363 | Backhaul Link Identifier for Packet Forwarding in IAB Networks | Ericsson | imported from 3GU |
| R3‑191364 | IP Address Assignment for IAB Nodes | Ericsson | imported from 3GU |
| R3‑191365 | Flow Control in IAB Networks | Ericsson | imported from 3GU |
| R3‑191366 | UP Architecture Aspects of IAB nodes | Ericsson | imported from 3GU |
| R3‑191367 | On the Usage of NR DC for IAB Nodes | Ericsson | imported from 3GU |
| R3‑191368 | Support for LTE Deployment at IAB Node Sites | Ericsson | imported from 3GU |
| R3‑191369 | Minimizing CN Functionalities for IAB Networks | Ericsson | imported from 3GU |
| R3‑191370 | CP Architecture Aspects of IAB nodes | Ericsson | imported from 3GU |
| R3‑191371 | Packet Forwarding in IAB Networks | Ericsson | imported from 3GU |
| R3‑191372 | (TP for NR-IAB BL CR for TS 38.401): Recovery From Link Failure in IAB Networks | Ericsson | imported from 3GU |
| R3‑191373 | Security protection for Wireless backhaul in IAB | TCL Communication Ltd. | imported from 3GU |
| R3‑191374 | On Provisioning of UE Capability ID | Qualcomm Incorporated | imported from 3GU |
| R3‑191375 | Broadcast of Location Assistance Data by NG-RAN | Qualcomm Incorporated | imported from 3GU |
| R3‑191376 | Inter-gNB coordination for CLI management | Ericsson | imported from 3GU |
| R3‑191377 | CR TS 38.423 Inter-gNB coordination for CLI management | Ericsson | imported from 3GU |
| R3‑191378 | CR TS 38.473 Inter-gNB coordination for CLI management | Ericsson | imported from 3GU |
| R3‑191379 | Backhaul Signalling for Remote Interference Management | Ericsson | imported from 3GU |
| R3‑191380 | CR TS 38.413 Signalling for Remote Interference Management | Ericsson | imported from 3GU |
| R3‑191381 | CR TS 38.473 Signalling for Remote Interference Management | Ericsson | imported from 3GU |
| R3‑191382 | OAM Support for RIM Backhaul Signaling | Ericsson | imported from 3GU |
| R3‑191383 | NR-NTN Tracking Area Management | Fraunhofer IIS, Fraunhofer HHI | imported from 3GU |
| R3‑191384 | Introducing NGAP support for TSC deterministic QoS | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑191385 | Introducing XnAP support for TSC deterministic QoS | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑191386 | Draft LS to SA2 and SA5 on IAB impact to CN | Samsung R&D Institute UK | imported from 3GU |
| R3‑191387 | IAB Integration | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑191388 | Analysis on IP address management | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑191389 | IAB protocol stack options | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑191390 | Security aspects and considerations for IAB | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑191391 | Default Paging DRX in IDLE Mode | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑191392 | Default Paging DRX in IDLE Mode | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑191393 | Discussion on DRB to be Released | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑191394 | Corrrection for DRB to be Released | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑191395 | Discussion on UAC Barring Information | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑191396 | Clarify the support for multiple TNLAs for F1-C | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑191397 | UAC Barring | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑191398 | Clarify the support for multiple TNL Endpoints in the NG-RAN node | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑191399 | Clarify the AMF re-allocation | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑191400 | Discussion on System Information for W1 | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑191401 | Correction to Feature Set and Band Combination Indeces | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑191402 | Handling of UE Context Setup and UE Context Modification Requests | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑191403 | PLMN ID Change | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑191404 | PLMN ID Change | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑191405 | Bearer Context Release Request Cause | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑191406 | Bearer type change to SN terminated MCG bearer cause | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑191407 | UL Data Split | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑191408 | Clarification on Bearer Context Setup and Bearer Context Modification failures | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑191409 | Correction to Data Forwarding Information | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑191410 | Consideration on routing management | KDDI Corporation | imported from 3GU |
| R3‑191411 | Consideration on IAB setup procedure | KDDI Corporation | imported from 3GU |
| R3‑191412 | Consideration on Small Data transmission without Path Switch | ZTE | imported from 3GU |
| R3‑191413 | Slice availability for inactive UE | Huawei | imported from 3GU |
| R3‑191414 | Slice availability for inactive UE | Huawei | imported from 3GU |
| R3‑191415 | Corrections for support of data forwarding for reestablishment UE | Huawei | imported from 3GU |
| R3‑191416 | Corrections for support of data forwarding for reestablishment UE | Huawei | imported from 3GU |
| R3‑191417 | Corrections for support of data forwarding for reestablishment UE | Huawei | imported from 3GU |
| R3‑191418 | gNB behaviour clarification in case of RRC re-establishment | Huawei | imported from 3GU |
| R3‑191419 | gNB behaviour clarification in case of RRC re-establishment | Huawei | imported from 3GU |
| R3‑191420 | NG connectivity clarification in NG-flex | Huawei | imported from 3GU |
| R3‑191421 | NG connectivity clarification in NG-flex | Huawei | imported from 3GU |
| R3‑191422 | NG connectivity clarification in NG-flex | Huawei | imported from 3GU |
| R3‑191423 | Correction to DRB 5QI on E1 | Huawei | imported from 3GU |
| R3‑191424 | Necessity on path switch request for inter MN HO without SN change | NTT DOCOMO, INC. | imported from 3GU |
| R3‑191425 | CR for clarification on path switch request for inter MN HO without SN change | NTT DOCOMO, INC. | imported from 3GU |
| R3‑191426 | Discussion on PWS System Information Segmentation over F1 | ZTE Corporation | imported from 3GU |
| R3‑191427 | Further discussion on Measurement Gap Configuration over F1 for Multiple-DU Scenario | ZTE Corporation | imported from 3GU |
| R3‑191428 | Correction on Measurement Gap Configuration over F1 for TS38.473 (Option 1) | ZTE Corporation | imported from 3GU |
| R3‑191429 | Correction on Measurement Gap Configuration over F1 for TS38.473 (Option 2) | ZTE Corporation | imported from 3GU |
| R3‑191430 | Consideration onTarget Buffer Dwell Time to meet QOS requirement | ZTE Corporation | imported from 3GU |
| R3‑191431 | Corrections on QOS indication for TS38.425 | ZTE Corporation | imported from 3GU |
| R3‑191432 | Update on TNL Address discovery for EN-DC for TS36.300 | ZTE Corporation | imported from 3GU |
| R3‑191433 | Further Discussion on UAC for F1 interface | ZTE Corporation | imported from 3GU |
| R3‑191434 | Update on UAC for TS38.473 | ZTE Corporation | imported from 3GU |
| R3‑191435 | Discussion on the impact of common interface on network architecture | ZTE Corporation | imported from 3GU |
| R3‑191436 | Update of TNL Address discovery for EN-DC (using new container) for TS36.413 | ZTE Corporation | imported from 3GU |
| R3‑191437 | Failure case for EN-DC TNL address discovery | ZTE Corporation | imported from 3GU |
| R3‑191438 | Introduction failure case of TNL Address discovery for EN-DC for TS36.413 | ZTE Corporation | imported from 3GU |
| R3‑191439 | Clarification for PLMN specific interface in case of RAN sharing for TS36.300 | ZTE Corporation | imported from 3GU |
| R3‑191440 | Trace function support in R15 | ZTE Corporation, China Unicom | imported from 3GU |
| R3‑191441 | Trace function Support over F1 Interface for TS38.470 | ZTE Corporation, China Unicom | imported from 3GU |
| R3‑191442 | Clarification for PLMN specific interface in case of RAN sharing for TS38.300 | ZTE Corporation | imported from 3GU |
| R3‑191443 | Consideration on Time Sensitive Communication Related Enhancements for NR-IIoT | ZTE Corporation | imported from 3GU |
| R3‑191444 | Trace function Support over F1 Interface for TS38.473 | ZTE Corporation, China Unicom | imported from 3GU |
| R3‑191445 | Trace function Support over E1 Interface for TS38.460 | ZTE Corporation, China Unicom | imported from 3GU |
| R3‑191446 | Trace function Support over E1 Interface for TS38.463 | ZTE Corporation, China Unicom | imported from 3GU |
| R3‑191447 | GUAMI update for AMF planned removal | ZTE Corporation | imported from 3GU |
| R3‑191448 | CR for GUAMI update for AMF planned removal | ZTE Corporation | imported from 3GU |
| R3‑191449 | Consideration on desired buffer size | ZTE Corporation | imported from 3GU |
| R3‑191450 | Corrections on desired buffer size for TS38.425 | ZTE Corporation | imported from 3GU |
| R3‑191451 | Discussion on Load Management for SON | ZTE Corporation | imported from 3GU |
| R3‑191452 | Text Proposals for Load Management for SON | ZTE Corporation | imported from 3GU |
| R3‑191453 | Consideration on inter-RAT energy saving | ZTE Corporation | imported from 3GU |
| R3‑191454 | MLB/MRO for NR | ZTE Corporation | imported from 3GU |
| R3‑191455 | Smart Grid Method for SON | ZTE Corporation, CMCC | imported from 3GU |
| R3‑191456 | Work Plan for NR Positioning Work Item | Intel Corporation, Ericsson | imported from 3GU |
| R3‑191457 | Positioning methods support in gNB and ng-eNB | Intel Corporation | imported from 3GU |
| R3‑191458 | Resolution of the multiple SCTP associations issue | Intel Corporation | imported from 3GU |
| R3‑191459 | Associations removal using SCTP SHUTDOWN | Intel Corporation | imported from 3GU |
| R3‑191460 | Addition and removal of multiple SCTP associations | Intel Corporation | imported from 3GU |
| R3‑191461 | Correction of SCTP associations IE name | Intel Corporation | imported from 3GU |
| R3‑191462 | N2 mobility issue | Intel Corporation | imported from 3GU |
| R3‑191463 | N2 mobility issue - alternative 1 | Intel Corporation | imported from 3GU |
| R3‑191464 | N2 mobility issue - alternative 2 | Intel Corporation | imported from 3GU |
| R3‑191465 | Clarification on SN Status Transfer | Google Inc. | imported from 3GU |
| R3‑191466 | Correction to RRC Inactive transition | Google Inc. | imported from 3GU |
| R3‑191467 | Miscellaneous correction to F1AP | Google Inc. | imported from 3GU |
| R3‑191468 | Discussion on inter-node message usage for Inter-gNB-DU mobility | Google Inc. | imported from 3GU |
| R3‑191469 | [DRAFT] LS on Inter-node-message for Inter-gNB-DU mobility | Google Inc. | imported from 3GU |
| R3‑191470 | NG signalling design for RIM | Huawei | imported from 3GU |
| R3‑191471 | NG signalling design for RIM | Huawei | imported from 3GU |
| R3‑191472 | NG signalling design for RIM | Huawei | imported from 3GU |
| R3‑191473 | F1 signaling support for RIM | Huawei | imported from 3GU |
| R3‑191474 | OAM requirements for RIM | Huawei | imported from 3GU |
| R3‑191475 | LS on OAM requirements for RIM | Huawei | imported from 3GU |
| R3‑191476 | RAN3 impact to support URLLC Qos monitoring | Huawei | imported from 3GU |
| R3‑191477 | Reply LS on support URLLC Qos monitoring | Huawei | imported from 3GU |
| R3‑191478 | Discussion on L1 and L2 measurements | Huawei | imported from 3GU |
| R3‑191479 | Reply LS on L1 and L2 measurements | Huawei | imported from 3GU |
| R3‑191480 | Discuss on the gNB set ID | CATT | imported from 3GU |
| R3‑191481 | Discuss on the RIM solution | CATT | imported from 3GU |
| R3‑191482 | Consideration on Efficient PDCP Duplication | CATT | imported from 3GU |
| R3‑191483 | CR to 38.300 on NRIIOT Higher Layer Multi-Connectivity | CATT | imported from 3GU |
| R3‑191484 | discussion on Higher Layer Multi-Connectivity | CATT | imported from 3GU |
| R3‑191485 | Default DRB coordination for MR-DC | Huawei, OPPO | imported from 3GU |
| R3‑191486 | Discussion on extensions of NRPPa protocol for NR positioning | CATT | imported from 3GU |
| R3‑191487 | Supporting transport level packet marking provided by SMF | SAMSUNG | imported from 3GU |
| R3‑191488 | CR to 37.340 on Notification Control during Secondary Node Change | CATT | imported from 3GU |
| R3‑191489 | Transport level packet marking value provided by SMF | SAMSUNG | imported from 3GU |
| R3‑191490 | Default DRB coordination in MR-DC over Xn | Huawei, OPPO | imported from 3GU |
| R3‑191491 | Transport level packet marking value provided by SMF | SAMSUNG | imported from 3GU |
| R3‑191492 | CR to 38.473 on Notification Control during inter-DU HO | CATT | imported from 3GU |
| R3‑191493 | Transport level packet marking value provided by SMF | SAMSUNG | imported from 3GU |
| R3‑191494 | Default DRB coordination in MR-DC over NG | Huawei, OPPO | imported from 3GU |
| R3‑191495 | Transport level packet marking value provided by SMF | SAMSUNG | imported from 3GU |
| R3‑191496 | [Draft] Reply LS on Transport Level Packet Marking | SAMSUNG | imported from 3GU |
| R3‑191497 | Supporting two NG-U tunnels for a single PDU Session | SAMSUNG | imported from 3GU |
| R3‑191498 | CR to 38.473 on Bearer type change indication | CATT | imported from 3GU |
| R3‑191499 | Further Consideration on Access Control Related Information | CATT | imported from 3GU |
| R3‑191500 | CR for access control related information transfer over F1 | CATT | imported from 3GU |
| R3‑191501 | Discussion on direct data forwarding for inter-RAT mobility | CATT | imported from 3GU |
| R3‑191502 | Discussion on Mobility Robust Optimization in 5G system | CATT | imported from 3GU |
| R3‑191503 | LS on UE RLF Report for 5G system | CATT | imported from 3GU |
| R3‑191504 | Discussion on Mobilty Load Balance in 5G system | CATT | imported from 3GU |
| R3‑191505 | Consideration on performance measurements | CATT | imported from 3GU |
| R3‑191506 | Considerations on support of Energy Saving in NR | CATT | imported from 3GU |
| R3‑191507 | Discusstion on Automatic GBR service recovery | CATT | imported from 3GU |
| R3‑191508 | LS Response on Automatic Restoration of GFBR QOS | CATT | imported from 3GU |
| R3‑191509 | Discusstion on inter-MN handover without SN change | CATT | imported from 3GU |
| R3‑191510 | ( CR for TS 36.413) )Support of Inter-MN handover without SN change | CATT | imported from 3GU |
| R3‑191511 | ( CR for TS 38.413) )Support of Inter-MN handover without SN change | CATT | imported from 3GU |
| R3‑191512 | Mobility Optimization for MR-DC | ZTE | imported from 3GU |
| R3‑191513 | Cell capacity definition related to wideband carrier | ZTE | imported from 3GU |
| R3‑191514 | User plane measurements for RAN-centric data collection | ZTE | imported from 3GU |
| R3‑191515 | NR MDT support with variant architecture | ZTE | imported from 3GU |
| R3‑191516 | The performance evaluation on Delay critical GBR traffic | ZTE | imported from 3GU |
| R3‑191517 | QoE measurement support in NR | ZTE | imported from 3GU |
| R3‑191518 | NR RACH optimization | ZTE | imported from 3GU |
| R3‑191519 | NR RACH optimization-Text proposal for 37.816 | ZTE | imported from 3GU |
| R3‑191520 | PCI selection solution in NR | ZTE | imported from 3GU |
| R3‑191521 | Inter-node signalling for CLI | ZTE | imported from 3GU |
| R3‑191522 | Inter-set RIM backhaul signalling | ZTE | imported from 3GU |
| R3‑191523 | Stage3 signaling impact for RIM | ZTE | imported from 3GU |
| R3‑191524 | (TP for NR_CLI_RIM BL CR for TS 38.300)Support for RIM | ZTE | imported from 3GU |
| R3‑191525 | (TP for NR_CLI_RIM BL CR for TS 38.413)Support for RIM | ZTE | imported from 3GU |
| R3‑191526 | (TP for NR_CLI_RIM BL CR for TS 38.423)Support for RIM | ZTE | imported from 3GU |
| R3‑191527 | (TP for NR_CLI_RIM BL CR for TS 38.470)Support for RIM | ZTE | imported from 3GU |
| R3‑191528 | (TP for NR_CLI_RIM BL CR for TS 38.473)Support for RIM | ZTE | imported from 3GU |
| R3‑191529 | RIM OAM function | ZTE | imported from 3GU |
| R3‑191530 | (TP for NR_IAB BL CR for TS 38.401): Support of IP Address Configuration by OAM | ZTE Corporation, Sanechips | imported from 3GU |
| R3‑191531 | Work plan for CLI & RIM | LG Electronics, CMCC | imported from 3GU |
| R3‑191532 | Exchange of intended DL/UL configuration over Xn and F1 | LG Electronics | imported from 3GU |
| R3‑191533 | Issues on support of NSA for IAB | LG Electronics | imported from 3GU |
| R3‑191534 | Generating and delivering the time reference information in split NG-RAN architecture | SAMSUNG | imported from 3GU |
| R3‑191535 | Discussion on data forwarding and QoS flow remapping | LG Electronics | imported from 3GU |
| R3‑191536 | Support of direct data forwarding for inter-system HO between EPS and 5GS | CATT | imported from 3GU |
| R3‑191537 | CLI support on XnAP | LG Electronics | imported from 3GU |
| R3‑191538 | CLI support on F1AP | LG Electronics | imported from 3GU |
| R3‑191539 | Two NG-U tunnels for a single PDU Session: pCR for TS 38.413 | SAMSUNG | imported from 3GU |
| R3‑191540 | Two NG-U tunnels for a single PDU Session: pCR for TS 38.423 | SAMSUNG | imported from 3GU |
| R3‑191541 | CLI support on F1AP | LG Electronics | imported from 3GU |
| R3‑191542 | TP on small corrections on scenarios | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑191543 | Support of direct data forwarding for inter-system HO between EPS and 5GS | CATT | imported from 3GU |
| R3‑191544 | Analysis on Interface management between satellite and network entity on ground | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑191545 | Analysis on mobilitry due to interface change | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑191546 | (TP for NR_IAB BL CR for TS38.401) Further discussion on IAB node setup (SA) | Samsung | imported from 3GU |
| R3‑191547 | (TP for NR_IAB BL CR for TS38.401) Further discussion on IAB node setup (NSA) | Samsung | imported from 3GU |
| R3‑191548 | (TP for NR_IAB BL CR for TS36.423) Further discussion on IAB node setup (NSA) | Samsung | imported from 3GU |
| R3‑191549 | QoS framework in IAB network | Samsung | imported from 3GU |
| R3‑191550 | Further discussions on BH RLC CH configuration | Samsung | imported from 3GU |
| R3‑191551 | (TP for NR_IAB BL CR for TS38.401) Procedures for BH RLC CH configuration | Samsung | imported from 3GU |
| R3‑191552 | IP address management over IAB network | Samsung | imported from 3GU |
| R3‑191553 | Further discussion on UP protocol stack | Samsung | imported from 3GU |
| R3‑191554 | Overview of flow control solutions | Samsung | imported from 3GU |
| R3‑191555 | Discussion on PDCP-based security and IPSec-based security | Samsung | imported from 3GU |
| R3‑191556 | Overview on IAB node reestablishment | Samsung | imported from 3GU |
| R3‑191557 | Overview on IAB node migration | Samsung | imported from 3GU |
| R3‑191558 | CR on DRX configuration setup | Samsung | imported from 3GU |
| R3‑191559 | PWS system information segmentation over F1 | Samsung | imported from 3GU |
| R3‑191560 | CR on PWS segmentation over F1 | Samsung | imported from 3GU |
| R3‑191561 | Discussion on cell type over F1 | Samsung | imported from 3GU |
| R3‑191562 | CR on cell type over F1 | Samsung | imported from 3GU |
| R3‑191563 | Discussion on deduction of NG-RAN node ID length | Samsung | imported from 3GU |
| R3‑191564 | Discussion for MDT configuration and reporting | Samsung | imported from 3GU |
| R3‑191565 | Use case for Mobility Robustness Optimization in mobility scenarios | Samsung | imported from 3GU |
| R3‑191566 | Resource efficiency for redundant transmissions | Samsung | imported from 3GU |
| R3‑191567 | Discussion on RAN3 impacts for higher layer multiple-connectivity solution 1 | Samsung | imported from 3GU |
| R3‑191568 | NGAP impacts for higher layer multiple-connectivity solution 1 | Samsung | imported from 3GU |
| R3‑191569 | XnAP impacts for higher layer multiple-connectivity solution 1 | Samsung | imported from 3GU |
| R3‑191570 | Direct Data forwarding for inter-system HO | Samsung | imported from 3GU |
| R3‑191571 | Bearer ID issue for direct data forwarding | Samsung | imported from 3GU |
| R3‑191572 | (TP for data_fw BL CR for TS 38.300): Resolve open issues of direct data forwarding for handover between 4G and 5G | Samsung | imported from 3GU |
| R3‑191573 | Support of Direct Data forwarding for handover between 4G and 5G | Samsung | imported from 3GU |
| R3‑191574 | LS on direct data forwarding for inter-system handover | Samsung | imported from 3GU |
| R3‑191575 | Discussions on RIM scheme considering OAM connection | Samsung | imported from 3GU |
| R3‑191576 | The consideration of RIM Framework-2.1 | Samsung | imported from 3GU |
| R3‑191577 | CR for new IE on NR RIM over F1 | Samsung | imported from 3GU |
| R3‑191578 | CR for new message on NR RIM over F1 | Samsung | imported from 3GU |
| R3‑191579 | (TP for NR_IAB BL CR for TS 38.401): support for inter-gNB-DU IAB topology adaptation procedure | ZTE Corporation, Sanechips | imported from 3GU |
| R3‑191580 | Consideration RACH optimisation in DC scenario | CATT | imported from 3GU |
| R3‑191581 | Draft LS on RACH optimisation in DC scenario | CATT | imported from 3GU |
| R3‑191582 | Applicability of common F1 interface | CATT | imported from 3GU |
| R3‑191583 | (TP for NR_IAB BL CR for TS 38.401): Support of Using IP Address of IAB-MT Function for IAB node | ZTE Corporation, Sanechips | imported from 3GU |
| R3‑191584 | Further consideration for EN-DC support | ZTE | imported from 3GU |
| R3‑191585 | CR36423 for Addition of EN-DC support of eNB (as MN) | ZTE | imported from 3GU |
| R3‑191586 | SON Information Exchange over NG interface | Huawei | imported from 3GU |
| R3‑191587 | MRO use cases clarification | Huawei | imported from 3GU |
| R3‑191588 | Discussion on mobility optimization | Huawei | imported from 3GU |
| R3‑191589 | Discussion on RACH optimization in NR | Huawei | imported from 3GU |
| R3‑191590 | Discussion on Load Balancing | Huawei | imported from 3GU |
| R3‑191591 | PCI Selection for NR cells | Huawei | imported from 3GU |
| R3‑191592 | Support of AAS in CCO | Huawei | imported from 3GU |
| R3‑191593 | Discussion on MDT procedures | Huawei | imported from 3GU |
| R3‑191594 | CR to 38.410 Support Remote Interference Mitigation (RIM) function | CATT | imported from 3GU |
| R3‑191595 | Further considerations on security protection for MR-DC | Huawei | imported from 3GU |
| R3‑191596 | Support of ciphering protection for MR-DC | Huawei | imported from 3GU |
| R3‑191597 | Clarification on integrity protection for MR-DC | Huawei | imported from 3GU |
| R3‑191598 | Clarification on desired buffer size | Huawei | imported from 3GU |
| R3‑191599 | Discussion on UL user plane | Huawei | imported from 3GU |
| R3‑191600 | Introduction of uplink user data loss detection and retransmission mechanism | Huawei | imported from 3GU |
| R3‑191601 | Correction on the UL PDU session tunnel in RAN triggered PDU split | Huawei | imported from 3GU |
| R3‑191602 | Discussion on the bearer type selection hosted by SN | Huawei | imported from 3GU |
| R3‑191603 | Determination of bearer type by SN | Huawei | imported from 3GU |
| R3‑191604 | Introduce assistance information for determination of bearer type by SN | Huawei | imported from 3GU |
| R3‑191605 | Handling of the SN terminated bearer upon resume procedures | Huawei | imported from 3GU |
| R3‑191606 | Handling of the SN terminated bearer upon resume procedures | Huawei | imported from 3GU |
| R3‑191607 | Support of V2X QoS over Uu interface | Huawei, Qualcomm Incorporated | imported from 3GU |
| R3‑191608 | [DRAFT] Reply LS on QoS Support for eV2X over Uu interface | Huawei | imported from 3GU |
| R3‑191609 | CR TS 38.473 IAB BH RLC Channel Management | Ericsson | imported from 3GU |
| R3‑191610 | CR to 38.455 Support NR new positioning techniques | CATT | imported from 3GU |
| R3‑191611 | Access Control Information over F1 | Huawei | imported from 3GU |
| R3‑191612 | Discussion on Resources not available for the slice IE on E1 and F1 | Huawei | imported from 3GU |
| R3‑191613 | Resources not available for the slice | Huawei | imported from 3GU |
| R3‑191614 | Resources not available for the slice | Huawei | imported from 3GU |
| R3‑191615 | Slice(s) not supported on E1 and F1 | Huawei | imported from 3GU |
| R3‑191616 | Slice(s) not supported | Huawei | imported from 3GU |
| R3‑191617 | Slice(s) not supported | Huawei | imported from 3GU |
| R3‑191618 | Slicing information during handover | Huawei, Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑191619 | Rescue ASN.1 | Huawei | imported from 3GU |
| R3‑191620 | Addition of UAC assistance information | Huawei | imported from 3GU |
| R3‑191621 | Energy saving use case and measurements | Orange | imported from 3GU |
| R3‑191622 | Text proposal for Energy Saving use case | Orange | imported from 3GU |
| R3‑191623 | Discussion on correction over Iuant series 37 | Huawei | imported from 3GU |
| R3‑191624 | Correction for Iuant | Huawei | imported from 3GU |
| R3‑191625 | Correction for Iuant | Huawei | imported from 3GU |
| R3‑191626 | Correction for Iuant | Huawei | imported from 3GU |
| R3‑191627 | Discussion on WI phase NR positioning | Huawei | imported from 3GU |
| R3‑191628 | Discussion on UL positioning and the Transmission measurement function | Huawei | imported from 3GU |
| R3‑191629 | Discussion on DL positioning technique | Huawei | imported from 3GU |
| R3‑191630 | Discussion on DL and UL based positioning technique | Huawei | imported from 3GU |
| R3‑191631 | NTN Miscellaneous Correctio | Huawei | imported from 3GU |
| R3‑191632 | Clarification on NTN ISL | Huawei | imported from 3GU |
| R3‑191633 | O&M and NTN | Huawei | imported from 3GU |
| R3‑191634 | Clarification for ephemeris in NTN | Huawei | imported from 3GU |
| R3‑191635 | General aspects on NTN GW | Huawei | imported from 3GU |
| R3‑191636 | TP for 38.473 on BH RLC CH configuration | Samsung Electronics Co., Ltd | imported from 3GU |
| R3‑191637 | Analysis on RAN3 impact from PARLOS | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑191638 | [Draft]Reply LS on PARLOS RAN impacts | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑191639 | Solution for PDCP end user throughput measurements | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑191640 | [DRAFT] Reply LS on PDCP end user throughput measurements | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑191641 | L1 and L2 measurements in NG-RAN | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑191642 | Mobility optimization solution | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑191643 | RACH optimization solution | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑191644 | Load management for disaggregated gNB | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑191645 | PCI selection use case: handling of PCI confusion resolution | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑191646 | Optimization of RAN Notification Areas | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑191647 | Management of System Information Area in NR | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑191648 | Support for network sharing | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑191649 | Common X2 interface between eNB and en-gNB for network sharing | Nokia, Nokia Shanghai Bell, Huawei, KDDI, China Telecom, Bell, CATT, ZTE, Samsung, CMCC, LG Electronics | imported from 3GU |
| R3‑191650 | Common Xn interface for network sharing | Nokia, Nokia Shanghai Bell, Huawei, KDDI, China Telecom, Bell, CATT, ZTE, Samsung, CMCC, LG Electronics | imported from 3GU |
| R3‑191651 | Common F1 interface for network sharing | Nokia, Nokia Shanghai Bell, Huawei, KDDI, China Telecom, Bell, CATT, ZTE, Samsung, CMCC, LG Electronics | imported from 3GU |
| R3‑191652 | Options for inter-cluster signalling | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑191653 | Inter-cluster signalling for Remote Interference Management | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑191654 | Network-based coordination for TDD CLI management | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑191655 | Support for cross-link interference coordination | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑191656 | Discussion on the CSI-RS Configuration Transfer | China Telecommunications | imported from 3GU |
| R3‑191657 | Addition of Network Access Rate Reduction message | Ericsson | imported from 3GU |
| R3‑191658 | Addition of Network Access Rate Reduction message | Ericsson | imported from 3GU |
| R3‑191659 | RAN UE ID for F1 | Ericsson | imported from 3GU |
| R3‑191660 | RAN UE ID for E1 | Ericsson | imported from 3GU |
| R3‑191661 | E1 Setup Request for virtualized CU-UPs | Ericsson, Deutsche Telekom, Vodafone | imported from 3GU |
| R3‑191662 | NAS PDU in Initial Context Setup | Ericsson | imported from 3GU |
| R3‑191663 | Correction of MaxnoofBPLMNs for NR | Ericsson | imported from 3GU |
| R3‑191664 | Clarification of SRB ID in UE CONTEXT RELEASE COMMAND | Ericsson | imported from 3GU |
| R3‑191665 | TS 38.463 Tabular clean up for Bearer Context messages | Ericsson | imported from 3GU |
| R3‑191666 | Temporary Identifier usage at interworking | Ericsson | imported from 3GU |
| R3‑191667 | Temporary Identifier usage at interworking | Ericsson | imported from 3GU |
| R3‑191668 | Clarification of cardinality for the NG-RAN Architecture | Ericsson | imported from 3GU |
| R3‑191669 | gNB-CU-UP ID | Ericsson | imported from 3GU |
| R3‑191670 | Adding Trace Messages in F1AP | Ericsson | imported from 3GU |
| R3‑191671 | Supporting Trace activation/Deactivation in E1AP | Ericsson | imported from 3GU |
| R3‑191672 | Network Sharing Considerations for X2, F1, E1 and Xn interfaces | Vodafone Romania S.A. | imported from 3GU |
| R3‑191673 | Endiannes for the Payload Protocol Identifier in S1 | Ericsson | imported from 3GU |
| R3‑191674 | Endiannes for the Payload Protocol Identifier in X2 | Ericsson | imported from 3GU |
| R3‑191675 | Endiannes for the Payload Protocol Identifier in Xw | Ericsson | imported from 3GU |
| R3‑191676 | Endiannes for the Payload Protocol Identifier in NG | Ericsson | imported from 3GU |
| R3‑191677 | Endiannes for the Payload Protocol Identifier in Xn | Ericsson | imported from 3GU |
| R3‑191678 | Endiannes for the Payload Protocol Identifier in E1 | Ericsson | imported from 3GU |
| R3‑191679 | Discussion on GFBR Automatic Restoration | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑191680 | Endiannes for the Payload Protocol Identifier in F1 | Ericsson | imported from 3GU |
| R3‑191681 | Reply LS on Automatic Restoration of GFBR QoS | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑191682 | Correction of flow remapping before handover | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑191683 | MT UP EDT indication in S1-AP | Ericsson | imported from 3GU |
| R3‑191684 | Correction of flow remapping before handover | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑191685 | Correction of data forwarding | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑191686 | Correction of Emergency Calls | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑191687 | MT EDT initiation in Paging | Ericsson | imported from 3GU |
| R3‑191688 | Correction of Emergency Calls | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑191689 | Selection of UP solution for NB-IOT and MTC connected to 5GC | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑191690 | Reply LS on Completion of Study on Cellular IoT support and evolution for the 5G System | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑191691 | Data Notification | Ericsson | imported from 3GU |
| R3‑191692 | Support for Positioning in F1AP | Ericsson | imported from 3GU |
| R3‑191693 | Draft Reply LS on Completion of FS_RACS study | Qualcomm Incorporated | imported from 3GU |
| R3‑191694 | Discussion on Annex B solution for Key Issue 7: Automatic Restoration of GFBR QOS | Ericsson | imported from 3GU |
| R3‑191695 | [Draft] Reply LS on Automatic Restoration of GFBR QOS | Ericsson | imported from 3GU |
| R3‑191696 | On introducing an Additional RRM Policy Index to EPS | Ericsson, Vodafone | imported from 3GU |
| R3‑191697 | Introduction of Additional RRM Policy Index (ARPI) | Ericsson, Vodafone | imported from 3GU |
| R3‑191698 | Introduction of Additional RRM Policy Index (ARPI) | Ericsson, Vodafone | imported from 3GU |
| R3‑191699 | Introduction of Additional RRM Policy Index (ARPI) | Ericsson, Vodafone | imported from 3GU |
| R3‑191700 | Introduction of Additional RRM Policy Index (ARPI) | Ericsson, Vodafone | imported from 3GU |
| R3‑191701 | ERROR INDICATION Message in S1AP | Ericsson | imported from 3GU |
| R3‑191702 | ERROR INDICATION Message in S1AP | Ericsson | imported from 3GU |
| R3‑191703 | ERROR INDICATION Message in S1AP | Ericsson | imported from 3GU |
| R3‑191704 | LTE-M Devices | Ericsson | imported from 3GU |
| R3‑191705 | LTE-M Indication | Ericsson | imported from 3GU |
| R3‑191706 | BL-CE Indication | Ericsson | imported from 3GU |
| R3‑191707 | [Draft] LS on indication to distinguish category M1/M2 devices during RRC connection establishment | Ericsson | imported from 3GU |
| R3‑191708 | Resolving ambiguities with multiple SCTP associations | Ericsson | imported from 3GU |
| R3‑191709 | Multiple TNLA over F1 transport | Ericsson | imported from 3GU |
| R3‑191710 | Multiple SCTP associations over E1 | Ericsson | imported from 3GU |
| R3‑191711 | Multiple TNLA over E1 transport | Ericsson | imported from 3GU |
| R3‑191712 | Multiple SCTP associations over E1 | Ericsson | imported from 3GU |
| R3‑191713 | On a common interface solution for RAN sharing | Ericsson | imported from 3GU |
| R3‑191714 | On a PLMN specific interface solution for RAN sharing | Ericsson, Interdigital | imported from 3GU |
| R3‑191715 | RAN sharing with multiple Cell ID broadcast | Ericsson, Interdigital | imported from 3GU |
| R3‑191716 | RAN sharing with multiple Cell ID broadcast | Ericsson, Interdigital | imported from 3GU |
| R3‑191717 | RAN sharing with multiple Cell ID broadcast | Ericsson, Interdigital | imported from 3GU |
| R3‑191718 | Access class barring management over F1 | Ericsson | imported from 3GU |
| R3‑191719 | Addition of UAC assistance information | Ericsson | imported from 3GU |
| R3‑191720 | RAN UE ID | Ericsson | imported from 3GU |
| R3‑191721 | RAN UE ID for Xn | Ericsson | imported from 3GU |
| R3‑191722 | RAN UE ID for X2 | Ericsson | imported from 3GU |
| R3‑191723 | E1 Setup Request for virtualized CU-UPs | Ericsson, Deutsche Telekom, Vodafone | imported from 3GU |
| R3‑191724 | NAS PDU in Initial Context Setup | Ericsson | imported from 3GU |
| R3‑191725 | NAS PDU order | Ericsson | imported from 3GU |
| R3‑191726 | Correction on Error Indication procedure | Ericsson | imported from 3GU |
| R3‑191727 | Location Report Request | Ericsson | imported from 3GU |
| R3‑191728 | Location Report Request Type | Ericsson | imported from 3GU |
| R3‑191729 | Rapporteur’s corrections to version 15.3.0 | Ericsson | imported from 3GU |
| R3‑191730 | Allocation of F1-U DL TEIDs | Ericsson | imported from 3GU |
| R3‑191731 | About the possibility that gNB-CU indicates full configuration to the gNB-DU | Ericsson | imported from 3GU |
| R3‑191732 | Full configuration indication from gNB-CU to gNB-DU | Ericsson | imported from 3GU |
| R3‑191733 | About the case necessary UE capabilities not being supported | Ericsson | imported from 3GU |
| R3‑191734 | About the case necessary UE capabilities not being supported | Ericsson | imported from 3GU |
| R3‑191735 | Correction about gNB-CU System Information IE | Ericsson | imported from 3GU |
| R3‑191736 | Procedure description on optional IEs in CU to DU RRC information IE | Ericsson | imported from 3GU |
| R3‑191737 | Rapporteur’s editorial corrections for TS 38.463 | Ericsson | imported from 3GU |
| R3‑191738 | E1AP failure messages correction | Ericsson | imported from 3GU |
| R3‑191739 | New UL TNL Information clarification | Ericsson | imported from 3GU |
| R3‑191740 | New UL TNL Information clarification | Ericsson | imported from 3GU |
| R3‑191741 | New UL TNL Information clarification | Ericsson | imported from 3GU |
| R3‑191742 | Temporary Identifier usage at interworking | Ericsson | imported from 3GU |
| R3‑191743 | Clarification of cardinality for the NG-RAN Architecture | Ericsson | imported from 3GU |
| R3‑191744 | Regarding adding trace activation in F1AP and E1AP | Ericsson | imported from 3GU |
| R3‑191745 | Endianness for the Payload Protocol Identifier | Ericsson | imported from 3GU |
| R3‑191746 | WI work plan for Rel-16 LTE-MTC | Ericsson | imported from 3GU |
| R3‑191747 | Further discussion on enhancement: the Intra eNB CP Relocation for NB-IoT | Ericsson | imported from 3GU |
| R3‑191748 | MT early data transmission options | Ericsson | imported from 3GU |
| R3‑191749 | Discussion on potential MT early data transmission indication in Msg4 | Ericsson | imported from 3GU |
| R3‑191750 | Support of eDRX when connected to 5GC | Ericsson | imported from 3GU |
| R3‑191751 | Data notification for CIoT Ues | Ericsson | imported from 3GU |
| R3‑191752 | Up to Four RLC entities in the PDCP Duplication | Ericsson | imported from 3GU |
| R3‑191753 | Effective PDCP Duplication | Ericsson | imported from 3GU |
| R3‑191754 | PDCP Discarding | Ericsson | imported from 3GU |
| R3‑191755 | Solution #7 of Key Issue 1: Replication framework in 3GPP System | Ericsson | imported from 3GU |
| R3‑191756 | Solution #1 of Key Issue 1: Redundant user plane paths based on dual connectivity | Ericsson | imported from 3GU |
| R3‑191757 | [Draft] LS on Solution #1 of Key Issue 1: Redundant user plane paths based on dual connectivity | Ericsson | imported from 3GU |
| R3‑191758 | Solution #1 of Key Issue 1: Redundant user plane paths based on dual connectivity | Ericsson | imported from 3GU |
| R3‑191759 | Provisioning of UE’s TSC traffic pattern related information | Ericsson | imported from 3GU |
| R3‑191760 | Provisioning of UE’s TSC traffic pattern related information | Ericsson | imported from 3GU |
| R3‑191761 | Provisioning of UE’s TSC traffic pattern related information | Ericsson | imported from 3GU |
| R3‑191762 | Provisioning of UE’s TSC traffic pattern related information | Ericsson | imported from 3GU |
| R3‑191763 | Commonalities in solutions for Non-Public Network deployments | Ericsson | imported from 3GU |
| R3‑191764 | Draft LS on Non-Public Networks, NPN | Ericsson | imported from 3GU |
| R3‑191765 | On the Transmission Measurement Function in NG-RAN | Ericsson | imported from 3GU |
| R3‑191766 | How to Support Positioning in F1AP | Ericsson | imported from 3GU |
| R3‑191767 | Switching the Feeder Link Toward the Satellite | Ericsson | imported from 3GU |
| R3‑191768 | DC and NTN - Xn terminated on the ground | Ericsson | imported from 3GU |
| R3‑191769 | DC and NTN - Xn over ISL | Ericsson | imported from 3GU |
| R3‑191770 | Discussion on QoS Monitoring for URLLC | Ericsson | imported from 3GU |
| R3‑191771 | [Draft] Reply LS on 5G_URLLC | Ericsson | imported from 3GU |
| R3‑191772 | TP for TR 37.816 – Mapped 5QI over E1 | Ericsson | imported from 3GU |
| R3‑191773 | Discussion on L1/L2 measurements | Ericsson | imported from 3GU |
| R3‑191774 | [Draft] Reply LS on L1 and L2 measurements | Ericsson | imported from 3GU |
| R3‑191775 | TP to TR 37.816 on Mobility Optimization solution in NR | Ericsson | imported from 3GU |
| R3‑191776 | TP to TR 37.816 on Load Sharing and Load Balancing Solution for NR | Ericsson | imported from 3GU |
| R3‑191777 | TP to TR 37.816 on Coverage and Capacity Optimisation Solution for NR | Ericsson | imported from 3GU |
| R3‑191778 | Scope of Coverage and Capacity Optimisation for NR | Ericsson | imported from 3GU |
| R3‑191779 | Scope of Coverage and Capacity Optimisation Solution for NR | Ericsson | imported from 3GU |
| R3‑191780 | Discussion on MIMO and CCO | Ericsson | imported from 3GU |
| R3‑191781 | Discussion on UE Identification over E1 | Nokia, Nokia Shanghai Bell, Verizon Wireless, Samsung, KDDI, ATT | imported from 3GU |
| R3‑191782 | UE Identification over E1 | Nokia, Nokia Shanghai Bell, Verizon Wireless, Samsung, KDDI, ATT | imported from 3GU |
| R3‑191783 | Desired Buffer Size | Ericsson | imported from 3GU |
| R3‑191784 | Making DBS Useful for Dual Connectivity | Ericsson | imported from 3GU |
| R3‑191785 | CR TS 38.425 Making DBS Useful for Dual Connectivity | Ericsson | imported from 3GU |
| R3‑191786 | Discussion on UP solution for connection to 5GC | LG Electronics | imported from 3GU |
| R3‑191787 | RAN impact of dual connectivity based solution in higher-layer multi-connectivity | LG Electronics | imported from 3GU |
| R3‑191788 | Discussion on RAN Paging Failure over Xn interface | LG Electronics | imported from 3GU |
| R3‑191789 | CR on RAN Paging Failure over Xn interface | LG Electronics | imported from 3GU |
| R3‑191790 | Feeder link switch over principles | THALES | imported from 3GU |
| R3‑191791 | Correction for SN terminated DRB To Be Setup in SN Addition Response | Intel Corporation | imported from 3GU |
| R3‑191792 | Correction for data forwarding in MR-DC with 5GC operations involving SN change | Intel Corporation, CATT | imported from 3GU |
| R3‑191793 | Allow MN to retrieve forwarding proposal from the source SN | Intel Corporation, CATT | imported from 3GU |
| R3‑191794 | CR for TS 38.423 for Data Forwarding Proposal | CATT, Intel Corporation | imported from 3GU |
| R3‑191795 | X2AP and XnAP clean-up for the change of PDCP SN length and RLC mode over To Be Modified structure | Intel Corporation, Huawei, CATT | imported from 3GU |
| R3‑191796 | Tie up the change of PDCP SN length or RLC mode of a DRB over To Be Mofidified structure only when security key is updated | Intel Corporation, Huawei, CATT | imported from 3GU |
| R3‑191797 | Tie up the change of PDCP SN length or RLC mode of a DRB over To Be Mofidified structure only when security key is updated | Intel Corporation, Huawei, CATT | imported from 3GU |
| R3‑191798 | Configuration of Bearer Mapping for IAB nodes | Intel Corporation | imported from 3GU |
| R3‑191799 | IAB Flow Control for DL | Intel Corporation | imported from 3GU |
| R3‑191800 | IAB Flow Control for UL | Intel Corporation | imported from 3GU |
| R3‑191801 | IAB lossless delivery of UL data with hop-by-hop ARQ | Intel Corporation | imported from 3GU |
| R3‑191802 | CR TS 38.470 Remote Interference Management Message Transfer Support | Ericsson | imported from 3GU |
| R3‑191803 | [Draft] LS on OAM support for Remote Interference Management | Ericsson | imported from 3GU |
| R3‑191804 | RAN sharing with multiple Cell ID broadcast | Ericsson, Interdigital | imported from 3GU |
| R3‑191805 | RAN sharing with multiple Cell ID broadcast | Ericsson | imported from 3GU |
| R3‑191806 | RAN sharing with multiple Cell ID broadcast | Ericsson | imported from 3GU |
| R3‑191807 | UP solution for connecting LTE-M or NB-IoT to 5GC | Ericsson | imported from 3GU |
| R3‑191808 | Solution #1 of Key Issue 1: Redundant user plane paths based on dual connectivity | Ericsson | imported from 3GU |
| R3‑191809 | TP to TR 37.816 on Successful Handover Report for MRO in NR | Ericsson | imported from 3GU |
| R3‑191810 | Mobility robustness optimization in NR | Ericsson | imported from 3GU |
| R3‑191811 | RACH optimization in NR | Ericsson | imported from 3GU |
| R3‑191812 | Load sharing and load balancing optimization | Ericsson | imported from 3GU |
| R3‑191813 | Discussion on Energy Saving for RAN-centric DCU | Ericsson | imported from 3GU |
| R3‑191814 | On the challenges of TNL address discovery with the flexible gNB/en-gNB ID length | Ericsson | imported from 3GU |
| R3‑191815 | Draft LS on broadcasting gNB ID length in system information block | Ericsson | imported from 3GU |
| R3‑191816 | Status Quo and way forward for UE RRM policy handling | Ericsson | imported from 3GU |
| R3‑191817 | TR 37.816 v0.2.0 | CMCC | imported from 3GU |
| R3‑191818 | Network aspects of MDT for NR | CMCC | imported from 3GU |
| R3‑191819 | Text proposal for network aspects of MDT for NR | CMCC | imported from 3GU |
| R3‑191820 | Inter-set RIM backhaul signalling and OAM impact | CMCC | imported from 3GU |
| R3‑191821 | Consideration of RACH optimization for the NR | CMCC | imported from 3GU |
| R3‑191822 | Considerations on V2X use cases and measurements | CMCC | imported from 3GU |
| R3‑191823 | Discussion on Automatic Restoration of GFBR QOS in SA2 LS | CMCC | imported from 3GU |
| R3‑191824 | [DRAFT] Reply LS on Automatic Restoration of GFBR QOS for SA2 | CMCC | imported from 3GU |
| R3‑191825 | Signalling design of Accuracy Reference Time | CMCC | imported from 3GU |
| R3‑191826 | UE specific local RRM policy information storage and retrieval | CMCC | imported from 3GU |
| R3‑191827 | Load balancing optimization | CMCC | imported from 3GU |
| R3‑191828 | TP for load balancing optimization | CMCC | imported from 3GU |
| R3‑191829 | Energy saving in NR | CMCC | imported from 3GU |
| R3‑191830 | Interface support for PDCP duplication with more than 2 legs | CMCC | imported from 3GU |
| R3‑191831 | Use case of edge computing | CMCC, Vodafone, CATT, TIM, T-Mobile USA, China Unicom, Deutsche Telekom | imported from 3GU |
| R3‑191832 | Support of ongoing re-mapping on source side during SDAP mobility | Ericsson | imported from 3GU |
| R3‑191833 | Support of ongoing re-mapping on source side during SDAP mobility | Ericsson | imported from 3GU |
| R3‑191834 | IAB Node integration procedure | Huawei | imported from 3GU |
| R3‑191835 | (TP for NR_IAB BL CR for TS 38.401): Integration of IAB-node | Huawei | imported from 3GU |
| R3‑191836 | Adaptation layer configuration | Huawei | imported from 3GU |
| R3‑191837 | Backhaul RLC bearer management | Huawei | imported from 3GU |
| R3‑191838 | (TP for NR_IAB BL CR for TS 38.401):BH RLC bearer management | Huawei | imported from 3GU |
| R3‑191839 | Bearer mapping in Donor-DU and IAB node | Huawei | imported from 3GU |
| R3‑191840 | QoS management and configuration of IAB node | Huawei | imported from 3GU |
| R3‑191841 | IP address management of IAB node | Huawei | imported from 3GU |
| R3‑191842 | Support of flow control for IAB Network | Huawei | imported from 3GU |
| R3‑191843 | Remaining issues of the UP protocol architecture | Huawei | imported from 3GU |
| R3‑191844 | Support of multiple connectivity in IAB network | Huawei | imported from 3GU |
| R3‑191845 | RAN3 impact analysis of IAB usage in NSA network | Huawei | imported from 3GU |
| R3‑191846 | Congestion reporting and handling for IAB networks | Huawei | imported from 3GU |
| R3‑191847 | Resource coordination between multi-hop BH links | Huawei | imported from 3GU |
| R3‑191848 | Routing address design and configuration | Huawei | imported from 3GU |
| R3‑191849 | Routing table design and configuration | Huawei | imported from 3GU |
| R3‑191850 | Backhaul RLF Recovery | Huawei | imported from 3GU |
| R3‑191851 | Intra IAB donor CU topology adaptation | Huawei | imported from 3GU |
| R3‑191852 | (TP for NR_IAB BL CR for TS 38.401): Intra IAB donor-CU topology adaptation procedure | Huawei | imported from 3GU |
| R3‑191853 | Inter IAB donor CU topology adaptation | Huawei | imported from 3GU |
| R3‑191854 | IAB impact to CN | Huawei | imported from 3GU |
| R3‑191855 | Support of ongoing re-mapping on source side during SDAP mobility | Ericsson | imported from 3GU |
| R3‑191856 | Idle Mode UEs in Non-Terrestrial Networks (NTN) | Mitsubishi Electric RCE | imported from 3GU |
| R3‑191857 | Correction of AMF set related statements | Ericsson | imported from 3GU |
| R3‑191858 | Correction on DRB ID co-ordination between MN and SN | Ericsson | imported from 3GU |
| R3‑191859 | Introduction of EN-DC | Ericsson | imported from 3GU |
| R3‑191860 | Support of Direct Data forwarding for handover between 4G and 5G | Ericsson, NTT DoCoMo | imported from 3GU |
| R3‑191861 | Support of SDAP mobility when re-mapping at source side is not yet finalised | Ericsson | imported from 3GU |
| R3‑191862 | Support of ongoing re-mapping on source side during SDAP mobility | Ericsson | imported from 3GU |
| R3‑191863 | SN Status Transfer applicability for Re-establishment | Ericsson | imported from 3GU |
| R3‑191864 | Rapporteur’s corrections to version 15.5.0 | Ericsson | imported from 3GU |
| R3‑191865 | DRB ID co-ordination between MN and SN | Ericsson | imported from 3GU |
| R3‑191866 | Intersystem Data Forwarding – Current status of discussions and way forward | Ericsson | imported from 3GU |
| R3‑191867 | [DRAFT] LS on data forwarding for intra and inter-system HO | Ericsson | imported from 3GU |
| R3‑191868 | Introduction of direct and indirect data forwarding for inter-system HO between EPS and 5GS | Ericsson | imported from 3GU |
| R3‑191869 | Reporting RLM related issues upon handover and access to the target cell | Ericsson | imported from 3GU |
| R3‑191870 | Successful Handover Report for MRO | Ericsson | imported from 3GU |
| R3‑191871 | Reply LS on network slicing terminology | 3GPP RAN2, Huawei | imported from 3GU |
| R3‑191872 | LS on full data rate support for UP IP | 3GPP SA3, Qualcomm | imported from 3GU |
| R3‑191873 | SN Status Transfer applicability for Re-establishment | Ericsson | imported from 3GU |
| R3‑191874 | Rapporteur updates for TS 38.413 | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑191875 | Text Proposals for load balancing | Huawei | imported from 3GU |
| R3‑191876 | Text Proposals for PCI selection | Huawei | imported from 3GU |
| R3‑191877 | Text Proposals for RACH optimisation | Huawei | imported from 3GU |
| R3‑191878 | Text Proposals for Energy Saving | Huawei | imported from 3GU |
| R3‑191879 | Discussion on LTE V2X optimisation | Huawei | imported from 3GU |
| R3‑191880 | Text proposals on LTE V2X optimisation | Huawei | imported from 3GU |
| R3‑191881 | Discussion on user consent of MDT | Huawei | imported from 3GU |
| R3‑191882 | Text Proposals for L2 measurements | Huawei | imported from 3GU |
| R3‑191883 | Direct data forwarding for inter-system handover | Huawei | imported from 3GU |
| R3‑191884 | (TP for data_fw BL CR for TS 38.300): Direct data forwarding for inter-system handover | Huawei | imported from 3GU |
| R3‑191885 | Direct data forwarding for inter-system handover | Huawei | imported from 3GU |
| R3‑191886 | Correction of Core Network Type Restriction | Huawei,Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑191887 | Correction of Core Network Type Restriction | Huawei, Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑191888 | GUAMI update in case of AMF change | Huawei | imported from 3GU |
| R3‑191889 | GUAMI update in case of AMF change | Huawei | imported from 3GU |
| R3‑191890 | Enforcement of UP integrity protection | Huawei | imported from 3GU |
| R3‑191891 | Enforcement of UP integrity protection | Huawei | imported from 3GU |
| R3‑191892 | Transport Level Packet Marking | Huawei | imported from 3GU |
| R3‑191893 | [Draft] Reply LS on Transport Level Packet Marking | Huawei | imported from 3GU |
| R3‑191894 | Data forwarding and QoS flow remapping | Huawei | imported from 3GU |
| R3‑191895 | Data forwarding and QoS flow remapping | Huawei | imported from 3GU |
| R3‑191896 | Data forwarding and QoS flow remapping | Huawei | imported from 3GU |
| R3‑191897 | PDU session split for E1 | Huawei | imported from 3GU |
| R3‑191898 | Correction of Network Instance | Huawei, Nokia, Nokia Shanghai Bell, China Unicom, China Telecom, Orange | imported from 3GU |
| R3‑191899 | The GUAMI and GUMMEI usage for EPS/5GS interworking | Huawei | imported from 3GU |
| R3‑191900 | The GUAMI and GUMMEI usage for EPS/5GS interworking | Huawei | imported from 3GU |
| R3‑191901 | The GUAMI and GUMMEI usage for EPS/5GS interworking | Huawei | imported from 3GU |
| R3‑191902 | Correction of NAS PDU in initial context setup request | Huawei | imported from 3GU |
| R3‑191903 | Correction of NAS PDU in initial context setup request | Huawei | imported from 3GU |
| R3‑191904 | Resource efficient DL PDCP duplication | Huawei | imported from 3GU |
| R3‑191905 | PDCP duplication with more than 2 entities | Huawei | imported from 3GU |
| R3‑191906 | Dynamic control of UL duplication | Huawei | imported from 3GU |
| R3‑191907 | Higher layer duplication for solution 4 | Huawei | imported from 3GU |
| R3‑191908 | Higher layer duplication for solution 4 | Huawei | imported from 3GU |
| R3‑191909 | Higher layer duplication for solution 4 | Huawei | imported from 3GU |
| R3‑191910 | Higher layer duplication for solution 4 | Huawei | imported from 3GU |
| R3‑191911 | IIoT QoS support over NG | Huawei | imported from 3GU |
| R3‑191912 | Dynamic CN component of PDB | Huawei | imported from 3GU |
| R3‑191913 | Dynamic CN component of PDB | Huawei | imported from 3GU |
| R3‑191914 | Dynamic CN component of PDB | Huawei | imported from 3GU |
| R3‑191915 | Dynamic CN component of PDB | Huawei | imported from 3GU |
| R3‑191916 | IIoT QoS support between RAN nodes | Huawei | imported from 3GU |
| R3‑191917 | Reference timing delivery over F1 | Huawei | imported from 3GU |
| R3‑191918 | TSN synchronization for inter-gNB scenario | Huawei | imported from 3GU |
| R3‑191919 | UE Maximum IP Rate indication after inter-system handover | Huawei | imported from 3GU |
| R3‑191920 | UE Maximum IP Rate indication after inter-system handover | Huawei | imported from 3GU |
| R3‑191921 | UE Maximum IP Rate indication after inter-system handover | Huawei | imported from 3GU |
| R3‑191922 | Correction of PDU session resource release response | Huawei | imported from 3GU |
| R3‑191923 | Update of AMF NGAP UE ID | Huawei | imported from 3GU |
| R3‑191924 | IP Version of Transport Layer Address | Huawei | imported from 3GU |
| R3‑191925 | Correction on transport layer address | Huawei | imported from 3GU |
| R3‑191926 | Correction on transport layer address | Huawei | imported from 3GU |
| R3‑191927 | Correction on transport layer address | Huawei | imported from 3GU |
| R3‑191928 | Correction on transport layer address | Huawei | imported from 3GU |
| R3‑191929 | CR to 38.473 on clarification to RRC reconfigure complete indicator | Huawei, CATT | imported from 3GU |
| R3‑191930 | CR to 38.401 on clarification to RRC reconfiguration complete indicator | Huawei, CATT | imported from 3GU |
| R3‑191931 | Further discussion on PPID for DTLS over SCTP | Huawei | imported from 3GU |
| R3‑191932 | Further discussions on RAN sharing | Huawei | imported from 3GU |
| R3‑191933 | pCR to 36.300 on clarifications for RAN sharing | Huawei | imported from 3GU |
| R3‑191934 | CR to 38.401 on clarifications for RAN sharing | Huawei | imported from 3GU |
| R3‑191935 | Discussion on Delta RRC config support in gNB-CU | Huawei | imported from 3GU |
| R3‑191936 | CR to 38473 on Delta RRC config support in gNB-CU | Huawei | imported from 3GU |
| R3‑191937 | CR to 38.473 on the condition of gNB-DU providing C-RNTI | Huawei | imported from 3GU |
| R3‑191938 | CR to 38.473 on inactivity monitoring request | Huawei | imported from 3GU |
| R3‑191939 | Discussion on deconfiguring CA Based PDCP duplication | Huawei | imported from 3GU |
| R3‑191940 | CR to 38.473 on deconfiguring CA based PDCP duplication on F1 | Huawei | imported from 3GU |
| R3‑191941 | CR to 38.463 on deconfiguring PDCP duplication on E1 | Huawei | imported from 3GU |
| R3‑191942 | CR to 38.463 on TNLA Transport Layer Information and TNLA Usage on E1 | Huawei | imported from 3GU |
| R3‑191943 | Discussion on cell management during gNB-CU Configuration Update procedures | Huawei | imported from 3GU |
| R3‑191944 | CR to 38.473 on cell management during gNB-CU Configuration Update procedures | Huawei | imported from 3GU |
| R3‑191945 | CR to 38.401 on cell management during gNB-CU Configuration Update procedure | Huawei | imported from 3GU |
| R3‑191946 | UE Maximum Integrity Protected Data Rate IE on E1 | Huawei | imported from 3GU |
| R3‑191947 | CR to 38.463 on Maximum Integrity Protected Data Rate IE in Security Indication over E1 interface | Huawei | imported from 3GU |
| R3‑191948 | CR on the usage of gNB-CU-UP capacity for gNB-CU-CP | Huawei | imported from 3GU |
| R3‑191949 | Clarifications on RRC Suspend indication in Bearer Context Status Change | Huawei | imported from 3GU |
| R3‑191950 | CR on UL COUNT IE and DL COUNT IE | Huawei | imported from 3GU |
| R3‑191951 | Clarifications to DRB Status List IE | Huawei | imported from 3GU |
| R3‑191952 | Discussion on Removal of Multiple TNLA for E1 and F1 | Huawei | imported from 3GU |
| R3‑191953 | CR to 38.463 on removal of multiple TNLAs | Huawei | imported from 3GU |
| R3‑191954 | CR to 38.462 on Removal of Multiple TNLA(s) for E1 | Huawei | imported from 3GU |
| R3‑191955 | CR to 38.473 on Removal of Multiple TNLAs | Huawei | imported from 3GU |
| R3‑191956 | CR to 38.472 on Removal of Multiple TNLA (s) for F1 | Huawei | imported from 3GU |
| R3‑191957 | CR to 38.401 on Multiple TNLAs for E1 | Huawei | imported from 3GU |
| R3‑191958 | CR to 38.401 on Multiple TNLAs for F1 | Huawei | imported from 3GU |
| R3‑191959 | CR on 38.401 to RRC Inactive to RRC Connected state transition | Huawei | imported from 3GU |
| R3‑191960 | Discussion on security indication in the modification procedure over E1 interface | Huawei | imported from 3GU |
| R3‑191961 | CR on security Indication IE in Bearer Context Modification Request | Huawei | imported from 3GU |
| R3‑191962 | Clarification on Header Compression | Huawei | imported from 3GU |
| R3‑191963 | CR to 38473 on cause value | Huawei | imported from 3GU |
| R3‑191964 | CR to 38.463 on counter check procedure | Huawei | imported from 3GU |
| R3‑191965 | Discussion on the handling of System Information for W1 | Huawei, China Unicom | imported from 3GU |
| R3‑191966 | Discussion on the Resource Coordination procedure | Huawei, China Unicom | imported from 3GU |
| R3‑191967 | Discussion on the Status Indication procedure | Huawei, China Unicom | imported from 3GU |
| R3‑191968 | Discussion on mobility procedures in case of disaggregated ng-eNB architecture | Huawei, China Unicom | imported from 3GU |
| R3‑191969 | Discussion on the UE Inactivity Notification | Huawei, China Unicom | imported from 3GU |
| R3‑191970 | pCR to 37.470 on W1AP functions and procedures | Huawei, China Unicom | imported from 3GU |
| R3‑191971 | Discussion on the Notify procedure | Huawei, China Unicom | imported from 3GU |
| R3‑191972 | Discussion on DL-TDOA positioning | ZTE Corporation | imported from 3GU |
| R3‑191973 | Response to R3-191637 | Ericsson | imported from 3GU |
| R3‑191974 | Response to R3-191955 | Ericsson | imported from 3GU |
| R3‑191975 | Response to R3-191742 | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑191976 | Response to R3-191227, R3-181450, R3-191783, R3-191598 | NEC | imported from 3GU |
| R3‑191977 | Clarifying affected 5G architecture options by each CR | NTT DOCOMO, INC. | imported from 3GU |
| R3‑191978 | Supporting transport level packet marking provided by SMF | SAMSUNG | imported from 3GU |
| R3‑191979 | Update on UAC for TS38.473 | ZTE Corporation | imported from 3GU |
| R3‑191980 | Necessity on path switch request for inter MN HO without SN change | NTT DOCOMO, INC. | imported from 3GU |
| R3‑191981 | CR for clarification on path switch request for inter MN HO without SN change | NTT DOCOMO, INC. | imported from 3GU |
| R3‑191982 | CR36423 for Addition of MN (MeNB) cell ID to solve the PCI confusion in SN(SgNB) modification Request messag | ZTE, Samsung, NEC | imported from 3GU |
| R3‑191983 | Summary of offline discussion on PPID for DTLS over SCTP | Huawei | imported from 3GU |
| R3‑191984 | Introduction of Additional RRM Policy Index (ARPI) | Ericsson, Vodafone | imported from 3GU |
| R3‑191985 | Introduction of Additional RRM Policy Index (ARPI) | Ericsson, Vodafone | imported from 3GU |
| R3‑191986 | Introduction of Additional RRM Policy Index (ARPI) | Ericsson, Vodafone | imported from 3GU |
| R3‑191987 | Introduction of Additional RRM Policy Index (ARPI) | Ericsson, Vodafone | imported from 3GU |
| R3‑191988 | Reply LS on transport level packet marking | Huawei | imported from 3GU |
| R3‑191989 | [DRAFT] Reply LS on QoS Support for eV2X over Uu interface | Huawei | imported from 3GU |
| R3‑191990 | Clarification on desired buffer size | Huawei | imported from 3GU |
| R3‑191991 | Reply LS on Automatic Restoration of GFBR QoS | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑191992 | UE Identification over E1 | Nokia, Nokia Shanghai Bell, Verizon Wireless, Samsung, KDDI, ATT | imported from 3GU |
| R3‑191993 | E1 Setup Request for virtualized CU-UPs | Ericsson, Deutsche Telekom, Vodafone, BT, Orange | imported from 3GU |
| R3‑191994 | Rapporteur’s editorial corrections for TS 38.463 | Ericsson | imported from 3GU |
| R3‑191995 | Reply LS on PARLOS RAN impacts | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑191996 | Multiple TNLA over F1 transport | Ericsson | imported from 3GU |
| R3‑191997 | Summary of offline discussion on on Removal of Multiple TNLAs | Ericsson | imported from 3GU |
| R3‑191998 | Multiple SCTP associations over E1 | Ericsson | imported from 3GU |
| R3‑191999 | Multiple TNLA over E1 transport | Ericsson | imported from 3GU |
| R3‑192000 | CR to 38.473 on Removal of Multiple TNLAs | Huawei | imported from 3GU |
| R3‑192001 | CR to 38.472 on Removal of Multiple TNLA (s) for F1 | Huawei | imported from 3GU |
| R3‑192002 | CR to 38.463 on removal of multiple TNLAs | Huawei | imported from 3GU |
| R3‑192003 | CR to 38.462 on Removal of Multiple TNLA(s) for E1 | Huawei | imported from 3GU |
| R3‑192004 | Clarify the support for multiple TNLAs for F1-C | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑192005 | CR to 38.401 on Multiple TNLAs for E1 | Huawei | imported from 3GU |
| R3‑192006 | Clarify the support for multiple TNL Endpoints in the NG-RAN node | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑192007 | Addition and removal of multiple SCTP associations | Intel Corporation | imported from 3GU |
| R3‑192008 | Support for network sharing | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑192009 | Summary of Offline discussion on RAN Sharing with Multiple Cell ID Broadcast | InterDigital Communications | imported from 3GU |
| R3‑192010 | RAN sharing with multiple Cell ID broadcast | Ericsson, Interdigital | imported from 3GU |
| R3‑192011 | RAN sharing with multiple Cell ID broadcast | Ericsson, Interdigital | imported from 3GU |
| R3‑192012 | RAN sharing with multiple Cell ID broadcast | Ericsson, Interdigital | imported from 3GU |
| R3‑192013 | RAN sharing with multiple Cell ID broadcast | Ericsson | imported from 3GU |
| R3‑192014 | RAN sharing with multiple Cell ID broadcast | Ericsson | imported from 3GU |
| R3‑192015 | Common X2 interface between eNB and en-gNB for network sharing | Nokia, Nokia Shanghai Bell, Huawei, KDDI, China Telecom, Bell, CATT, ZTE, Samsung, CMCC, LG Electronics | imported from 3GU |
| R3‑192016 | Common Xn interface for network sharing | Nokia, Nokia Shanghai Bell, Huawei, KDDI, China Telecom, Bell, CATT, ZTE, Samsung, CMCC, LG Electronics | imported from 3GU |
| R3‑192017 | Common F1 interface for network sharing | Nokia, Nokia Shanghai Bell, Huawei, KDDI, China Telecom, Bell, CATT, ZTE, Samsung, CMCC, LG Electronics | imported from 3GU |
| R3‑192018 | Access Control Information over F1: Summary of offline discussion | Huawei | imported from 3GU |
| R3‑192019 | UE Identification and Trace Correlation over E1 - Summary of offline discussion | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑192020 | Various Clean-ups for TS37.340 | ZTE | imported from 3GU |
| R3‑192021 | Support of ongoing re-mapping on source side during SDAP mobility | Ericsson | imported from 3GU |
| R3‑192022 | Support of ongoing re-mapping on source side during SDAP mobility | Ericsson | imported from 3GU |
| R3‑192023 | Support of ongoing re-mapping on source side during SDAP mobility | Ericsson | imported from 3GU |
| R3‑192024 | Summary of offline discussion on Flow remapping before handover | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑192025 | XnAP Alignment of MN Triggered PDU Session Split | ZTE | imported from 3GU |
| R3‑192026 | Correction of Core Network Type restriction | Nokia, Nokia Shanghai Bell, Huawei | imported from 3GU |
| R3‑192027 | Correction of Core Network Type restriction | Nokia, Nokia Shanghai Bell, Huawei | imported from 3GU |
| R3‑192028 | Correction of Core Network Type Restriction | Huawei,Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑192029 | Correction of Core Network Type Restriction | Huawei, Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑192030 | Correction of handover 5g to 4g | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑192031 | NGAP Further Clarification of S-NSSAI Update for EPS to 5GS HO | ZTE | imported from 3GU |
| R3‑192032 | XnAP Further Clarification of S-NSSAI Update for EPS to 5GS HO | ZTE | imported from 3GU |
| R3‑192033 | CR to 38.473 on deconfiguring CA based PDCP duplication on F1 | Huawei | imported from 3GU |
| R3‑192034 | CR to 38.463 on deconfiguring PDCP duplication on E1 | Huawei | imported from 3GU |
| R3‑192035 | E1 Setup Request for virtualized CU-UPs – Summary of offline discussion | Ericsson | imported from 3GU |
| R3‑192036 | Clarification on desired buffer size | Huawei, Ericsson | imported from 3GU |
| R3‑192037 | Summary of offline discussion on NAS PDU order | Ericsson | imported from 3GU |
| R3‑192038 | CR for TS 38.423 for Data Forwarding Proposal | CATT, Intel Corporation | imported from 3GU |
| R3‑192039 | Correction of AMF set related statements | Ericsson | imported from 3GU |
| R3‑192040 | Correction on AMF connectivity | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑192041 | Rapporteur updates for TS 38.413 | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑192042 | Rapporteur’s corrections to version 15.3.0 | Ericsson | imported from 3GU |
| R3‑192043 | Rapporteur’s corrections to version 15.5.0 | Ericsson | imported from 3GU |
| R3‑192044 | Rapporteur’s editorial corrections for TS 38.463 | Ericsson | imported from 3GU |
| R3‑192045 | GUAMI update in case of AMF change | Huawei | imported from 3GU |
| R3‑192046 | Report email discussion 105#45 RAN2+3 IAB misc | Qualcomm Incorporated (Rapporteur) | imported from 3GU |
| R3‑192047 | RAN2/RAN3 offline IAB discussion | Qualcomm | imported from 3GU |
| R3‑192048 | Summary of offline discussion on GUAMI HANDLING | Ericsson | imported from 3GU |
| R3‑192049 | Summary of offline discussion on PDU Session Release | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑192050 | Correction of Emergency Calls | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑192051 | N2 mobility issue - alternative 2 | Intel Corporation | imported from 3GU |
| R3‑192052 | Correction of data forwarding | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑192053 | Slicing information during handover | Huawei, Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑192054 | Summary of offline discussion on MR-DC | Intel | imported from 3GU |
| R3‑192055 | CR TS 38.470 IAB General Aspects | Ericsson | imported from 3GU |
| R3‑192056 | CR TS 38.473 IAB General Aspects | Ericsson | imported from 3GU |
| R3‑192057 | Summary of offline discussion on IAB node indication | Ericsson | imported from 3GU |
| R3‑192058 | IAB OAM connectivity: Summary of offline discussion | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑192059 | XnAP Correction of PDU Session Resource Setup Complete Info – SN terminated | ZTE | imported from 3GU |
| R3‑192060 | XnAP Correction of PDU Session Resource Setup Response Info – MN terminated | ZTE | imported from 3GU |
| R3‑192061 | Parent node selection: Summary of offline discussion | CATT | imported from 3GU |
| R3‑192062 | (TP for NR-IAB BL CR for TS 38.401) Backhaul Channel Setup and Modification Procedure for IAB Networks | Ericsson | imported from 3GU |
| R3‑192063 | Summary of offline discussion on IAB Node Release Procedure | Ericsson | imported from 3GU |
| R3‑192064 | Removal of multiple TNLA(s) | Ericsson | imported from 3GU |
| R3‑192065 | LS to RAN2 on bearer limit with IPv6 flow label | Qualcomm | imported from 3GU |
| R3‑192066 | Correction for SN terminated DRB To Be Setup in SN Addition Response | Intel Corporation | imported from 3GU |
| R3‑192067 | Summary of offline on Default DRB coordination for MR-DC | Huawei | imported from 3GU |
| R3‑192068 | Correction to behaviour of SN for integrity protection with options 4 and 7 | Qualcomm Incorporated | imported from 3GU |
| R3‑192069 | Support of ciphering protection for MR-DC | Huawei | imported from 3GU |
| R3‑192070 | [DRAFT] Reply LS on Completion of FS_RACS study | Qualcomm Incorporated | imported from 3GU |
| R3‑192071 | RRC config indication behaviour | NEC, NTT DOCOMO, INC. | imported from 3GU |
| R3‑192072 | CR38423 for Addition of MN (MeNB) cell ID to solve the PCI confusion in SN(SgNB) modification Request message | ZTE, Samsung, NEC | imported from 3GU |
| R3‑192073 | Corrections for support of data forwarding for reestablishment UE | Huawei | imported from 3GU |
| R3‑192074 | Summary of offline discussion on Making DBS Useful for Dual Connectivity | Ericsson | imported from 3GU |
| R3‑192075 | Correction of PDU Session Release | Nokia, Nokia Shanghai Bell, Ericsson | imported from 3GU |
| R3‑192076 | LS on Handling of Direct Data Forwarding | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑192077 | Introduction of direct and indirect data forwarding for inter-system HO between EPS and 5GS | Ericsson | imported from 3GU |
| R3‑192078 | Support of Direct Data forwarding for handover between 4G and 5G | Ericsson, NTT DoCoMo | imported from 3GU |
| R3‑192079 | MTC&IoT Enh session report | Vice-chairman (ZTE) | imported from 3GU |
| R3‑192080 | CLI&RIM session report | Vice-chairman (ZTE) | imported from 3GU |
| R3‑192081 | NR IIoT session report | Vice-chairman (ZTE) | imported from 3GU |
| R3‑192082 | RAN-Centric DCU SI session report | Vice-chairman (Intel) | imported from 3GU |
| R3‑192083 | Reply LS on Completion of Study on Cellular IoT support and evolution for the 5G System | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑192084 | CR TS 38.473 Inter-gNB coordination for CLI management | Ericsson | imported from 3GU |
| R3‑192085 | UE Maximum IP Rate indication after inter-system handover | Huawei | imported from 3GU |
| R3‑192086 | UE Maximum IP Rate indication after inter-system handover | Huawei | imported from 3GU |
| R3‑192087 | LS to RAN2 on bearer limit with IPv6 flow label | Qualcomm | imported from 3GU |
| R3‑192088 | Correction to Feature Set and Band Combination Indeces | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑192089 | Summary of offline discussion on the Intended DL/UL configuration Definition | ZTE | imported from 3GU |
| R3‑192090 | CLI support on XnAP | LG Electronics, ZTE, Ericsson | imported from 3GU |
| R3‑192091 | CR TS 38.473 Inter-gNB coordination for CLI management | Ericsson, ZTE | imported from 3GU |
| R3‑192092 | Summary of offline discussion on RIM backhaul signalling | CMCC | imported from 3GU |
| R3‑192093 | LS on piggy-backing of NAS PDUs in NGAP messages | Nokia | imported from 3GU |
| R3‑192094 | Correction of RAN triggered PDU session split | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑192095 | Correction of flow remapping before handover | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑192096 | Tie up the change of PDCP SN length or RLC mode of a DRB over To Be Mofidified structure only when security key is updated | Intel Corporation, Huawei, CATT | imported from 3GU |
| R3‑192097 | Tie up the change of PDCP SN length or RLC mode of a DRB over To Be Mofidified structure only when security key is updated | Intel Corporation, Huawei, CATT | imported from 3GU |
| R3‑192098 | Summary of offline discussion on Correction of Network Instance | nn | imported from 3GU |
| R3‑192099 | Trace for E1 and F1 – Summary of offline discussion | ZTE | imported from 3GU |
| R3‑192100 | LS on CSI-RS configuration transfer over Xn | Huawei | imported from 3GU |
| R3‑192101 | Allow MN to retrieve forwarding proposal from the source SN | Intel Corporation, CATT | imported from 3GU |
| R3‑192102 | CR for TS 38.423 for Data Forwarding Proposal | CATT, Intel Corporation | imported from 3GU |
| R3‑192103 | TP on small corrections on scenarios | Nokia, Nokia Shanghai Bell, Thales | imported from 3GU |
| R3‑192104 | Way forward on the selective DL PDCP duplication for URLLC | Nokia | imported from 3GU |
| R3‑192105 | RAN UE ID for F1 | Ericsson | imported from 3GU |
| R3‑192106 | Signalling design of Accuracy Reference Time | CMCC | imported from 3GU |
| R3‑192107 | Summary of offline discussion on Option 1 | Ericsson | imported from 3GU |
| R3‑192108 | Summary of offline discussion on solution 4 | Huawei | imported from 3GU |
| R3‑192109 | Summary of offline discussion on Solution #7 | Ericsson | imported from 3GU |
| R3‑192110 | Clarification on NTN ISL | Huawei | imported from 3GU |
| R3‑192111 | General aspects on NTN GW | Huawei | imported from 3GU |
| R3‑192112 | NR-NTN Tracking Area Management | Fraunhofer IIS, Fraunhofer HHI | imported from 3GU |
| R3‑192113 | Idle Mode UEs in Non-Terrestrial Networks (NTN) | Mitsubishi Electric RCE | imported from 3GU |
| R3‑192114 | RAN paging failure handling in SN | Ericsson | imported from 3GU |
| R3‑192115 | Feeder link switch over principles | THALES | imported from 3GU |
| R3‑192116 | Analysis on mobilitry due to interface change: Summary of offline discussion | Nokia | imported from 3GU |
| R3‑192117 | NTN multi connectivity | THALES | imported from 3GU |
| R3‑192118 | DC and NTN - Xn over ISL | Ericsson | imported from 3GU |
| R3‑192119 | DC and NTN - Xn terminated on the ground | Ericsson | imported from 3GU |
| R3‑192120 | O&M and NTN | Huawei | imported from 3GU |
| R3‑192121 | Clarification for ephemeris in NTN | Huawei | imported from 3GU |
| R3‑192122 | Reply LS on L1 and L2 measurements | Huawei | imported from 3GU |
| R3‑192123 | [Draft] Reply LS on 5G_URLLC | Ericsson | imported from 3GU |
| R3‑192124 | Reply LS on PDCP end user throughput measurements | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑192125 | Discussion for MDT configuration and reporting | Samsung | imported from 3GU |
| R3‑192126 | Discussion on Mobility Robust Optimization in 5G system | CATT | imported from 3GU |
| R3‑192127 | Data forwarding and QoS flow remapping | Huawei | imported from 3GU |
| R3‑192128 | Data forwarding and QoS flow remapping | Huawei | imported from 3GU |
| R3‑192129 | Default DRB coordination in MR-DC over Xn | Huawei, OPPO | imported from 3GU |
| R3‑192130 | Load management for disaggregated gNB | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑192131 | Summary of offline discussion on MLB | CMCC | imported from 3GU |
| R3‑192132 | Summary of offline on R16 energy saving | ZTE | imported from 3GU |
| R3‑192133 | UE Identification over E1 | Nokia, Nokia Shanghai Bell, Verizon Wireless, Samsung, KDDI, ATT | imported from 3GU |
| R3‑192134 | RAN paging failure handling in SN in case of MR-DC | Huawei, NEC | imported from 3GU |
| R3‑192135 | Summary of offline discussion on RAN paging failure indication in MR-DC | Huawei | imported from 3GU |
| R3‑192136 | TP for Rel-16 energy saving | ZTE | imported from 3GU |
| R3‑192137 | Trace function Support over E1 Interface for TS38.460 | ZTE Corporation, China Unicom | imported from 3GU |
| R3‑192138 | Trace function Support over F1 Interface for TS38.470 | ZTE Corporation, China Unicom | imported from 3GU |
| R3‑192139 | [Draft] LS on Solution #1 of Key Issue 1: Redundant user plane paths based on dual connectivity | Ericsson | imported from 3GU |
| R3‑192140 | Introduction of Additional RRM Policy Index (ARPI) | Ericsson, Vodafone | imported from 3GU |
| R3‑192141 | Introduction of Additional RRM Policy Index (ARPI) | Ericsson, Vodafone | imported from 3GU |
| R3‑192142 | Introduction of Additional RRM Policy Index (ARPI) | Ericsson, Vodafone | imported from 3GU |
| R3‑192143 | Reply LS on QoS Support for eV2X over Uu interface | Huawei | imported from 3GU |
| R3‑192144 | CR to 38.473 on Removal of Multiple TNLAs | Huawei | imported from 3GU |
| R3‑192145 | Multiple SCTP associations over E1 | Ericsson | imported from 3GU |
| R3‑192146 | RAN sharing with multiple Cell ID broadcast | Ericsson, Interdigital | imported from 3GU |
| R3‑192147 | [draft] LS on support of default DRB configuration | Huawei | imported from 3GU |
| R3‑192148 | (TP for NR-IAB BL CR for TS 38.401) Backhaul Channel Setup and Modification Procedure for IAB Networks | Ericsson | imported from 3GU |
| R3‑192149 | Summary of offline discussion on IAB node indication | Ericsson | imported from 3GU |
| R3‑192150 | UE Identification over E1 | Nokia, Nokia Shanghai Bell, Verizon Wireless, Samsung, KDDI, ATT | imported from 3GU |
| R3‑192151 | CB: # 46bis_PDCP-SN_RLCmode – Summary of Offline Discussion | Intel | imported from 3GU |
| R3‑192152 | CR TS 38.470 IAB General Aspects | Ericsson | imported from 3GU |
| R3‑192153 | Correction of flow remapping before handover | Nokia, Nokia Shanghai Bell, Huawei | imported from 3GU |
| R3‑192154 | Data forwarding and QoS flow remapping | Huawei, Intel, Nokia, Nokia Shanghai Bell, Ericsson | imported from 3GU |
| R3‑192155 | Data forwarding and QoS flow remapping | Huawei, Intel, Nokia, Nokia Shanghai Bell, Ericsson | imported from 3GU |
| R3‑192156 | CR to 38.473 on deconfiguring CA based PDCP duplication on F1 | Huawei | imported from 3GU |
| R3‑192157 | CR to 38.463 on deconfiguring PDCP duplication on E1 | Huawei | imported from 3GU |
| R3‑192158 | LS on piggy-backing of NAS PDUs in NGAP messages | Nokia | imported from 3GU |
| R3‑192159 | GUAMI update in case of AMF change | Huawei | imported from 3GU |
| R3‑192160 | Summary of offline discussion on Option 1 | Ericsson | imported from 3GU |
| R3‑192161 | CR TS 38.470 IAB General Aspects | Ericsson | imported from 3GU |
| R3‑192162 | BL CR to 38.401: Support of IAB | Huawei | imported from 3GU |
| R3‑192163 | Adding Trace Messages in F1AP | Ericsson | imported from 3GU |
| R3‑192164 | Supporting Trace activation/Deactivation in E1AP | Ericsson | imported from 3GU |
| R3‑192165 | (TP for NR-IAB BL CR for TS 38.401) Backhaul Channel Setup and Modification Procedure for IAB Networks | Ericsson | imported from 3GU |
| R3‑192166 | LS on support of default DRB configuration | Huawei | imported from 3GU |
| R3‑192167 | LS on handling of Direct Data Forwarding | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑192168 | Analysis on mobilitry due to interface change | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑192169 | Analysis on mobilitry due to interface change | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑192170 | O&M and NTN | Huawei | imported from 3GU |
| R3‑192171 | DC and NTN - Xn over ISL | Ericsson | imported from 3GU |
| R3‑192172 | Introduction of direct and indirect data forwarding for inter-system HO between EPS and 5GS | Ericsson | imported from 3GU |
| R3‑192173 | Support of Direct Data forwarding for handover between 4G and 5G | Ericsson, NTT DoCoMo | imported from 3GU |
| R3‑192174 | [DRAFT] Reply LS on Completion of FS_RACS study | Qualcomm Incorporated | imported from 3GU |
| R3‑192175 | (TP for NR_IAB BL CR for TS 38.401): IAB Node Release Procedure | Ericsson | imported from 3GU |
| R3‑192176 | Reply LS on Completion of Study on Cellular IoT support and evolution for the 5G System | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑192177 | CR38423 for Addition of MN (MeNB) cell ID to solve the PCI confusion in SN(SgNB) modification Request message | ZTE, Samsung, NEC | imported from 3GU |
| R3‑192178 | Summary of offline discussion on Solution #7 | Ericsson | imported from 3GU |
| R3‑192179 | Reply LS on 5G_URLLC | Ericsson | imported from 3GU |
| R3‑192180 | Discussion for MDT configuration and reporting | Samsung | imported from 3GU |
| R3‑192181 | Discussion on Mobility Robust Optimization in 5G system | CATT | imported from 3GU |
| R3‑192182 | Addition and removal of multiple SCTP associations | Intel Corporation | imported from 3GU |
| R3‑192183 | Reply LS on Completion of FS_RACS study | Qualcomm Incorporated | imported from 3GU |
| R3‑192184 | Draft TR 37.470 v0.3.0 | China Unicom | imported from 3GU |
| R3‑192185 | Draft TR 37.816 v0.3.0 | China Mobile | imported from 3GU |
| R3‑192186 | Draft TR 38.821 v0.5.0 | Thales | imported from 3GU |
| R3‑192187 | BL CR to 38.401: Support of IAB | Huawei | imported from 3GU |
| R3‑192188 | Draft TR 37.816 v0.3.0 | China Mobile | imported from 3GU |
page generated from database: 2024-04-22 07:58:53