Please enter the search related information in the fields below. Partial information works, e.g. "SP-21" in the "tdoc" field lists all TSG SA documents from 2021. Regular expressions mostly work in all fields (e.g. "2[34].501" in the "Spec" field lists all documents related to 23.501 and 24.501. Capitalization is disregarded, i.e. "3GPP" gives the same results as "3gpp".

Download results in JSON format

tdoc Title Type / Revs Source Spec / CR S/WID Release Meeting Status Links
R3-210076 Definitions for MRO scenarios for SN change failure discussion

revision of R3-205904

Nokia, Nokia Shanghai Bell NR_ENDC_SON_MDT_enh-Core Rel-17 R3-111-e

AI: 10.2.1.6

available [WTS] [JSN]
R3-210077 Definitions of SCG failure events for MRO for SN change draftCR

revision of R3-205905

Nokia, Nokia Shanghai Bell NR_ENDC_SON_MDT_enh-Core Rel-17 R3-111-e

AI: 10.2.1.6

available [WTS] [JSN]
R3-210110 Discussion on MRO for SN Change Failure discussion China Telecommunication Rel-17 R3-111-e

AI: 10.2.1.6

available [WTS] [JSN]
R3-210261 TP for SON BLCR for 38.423: Support of SN change failure other Samsung NR_ENDC_SON_MDT_enh Rel-17 R3-111-e

AI: 10.2.1.6

available [WTS] [JSN]
R3-210262 TP for SON BLCR for 37.340: Support of SN change failure other Samsung NR_ENDC_SON_MDT_enh Rel-17 R3-111-e

AI: 10.2.1.6

available [WTS] [JSN]
R3-210263 LS on information needed for MRO in SCG Failure Report LS out

LS To: RAN2

revised to R3-211209

Samsung NR_ENDC_SON_MDT_enh R3-111-e

AI: 10.2.1.6

revised [WTS] [JSN]
R3-210294 Consideration on support of SN change failure in case of MR-DC discussion CATT R3-111-e

AI: 10.2.1.6

available [WTS] [JSN]
R3-210295 (TP on SN Change failure for 38.423) Addition of SCG Failure Information transfer other CATT NR_ENDC_SON_MDT_enh Rel-17 R3-111-e

AI: 10.2.1.6

available [WTS] [JSN]
R3-210296 [Draft]LS to RAN2 on SN change failure LS out

LS To: RAN2

CATT R3-111-e

AI: 10.2.1.6

available [WTS] [JSN]
R3-210395 (TP for SON BLCR for 38.423) MRO for SN Change Failure other Huawei NR_ENDC_SON_MDT_enh R3-111-e

AI: 10.2.1.6

available [WTS] [JSN]
R3-210396 MRO for SN Change Failure draftCR Huawei NR_ENDC_SON_MDT_enh Rel-17 R3-111-e

AI: 10.2.1.6

available [WTS] [JSN]
R3-210397 (TP for SON BLCR for 38.300) MRO for SN Change Failure other Huawei NR_ENDC_SON_MDT_enh Rel-17 R3-111-e

AI: 10.2.1.6

available [WTS] [JSN]
R3-210565 Further consideration on MRO SN change failure discussion ZTE NR_ENDC_SON_MDT_enh Rel-17 R3-111-e

AI: 10.2.1.6

available [WTS] [JSN]
R3-210676 On the SCG Failure Information delivery for MRO use case discussion Ericsson NR_ENDC_SON_MDT_enh Rel-17 R3-111-e

AI: 10.2.1.6

available [WTS] [JSN]
R3-210677 (TP for SON BL CR for TS 37.340): Definition of SCG change failure types other Ericsson NR_ENDC_SON_MDT_enh Rel-17 R3-111-e

AI: 10.2.1.6

available [WTS] [JSN]
R3-210993 CB: # 1005_SONMDT_SNChangeFail - Summary of email discussion discussion

revised to R3-211168

Samsung - moderator R3-111-e

AI: 10.2.1.6

revised [WTS] [JSN]
R3-211168 CB: # 1005_SONMDT_SNChangeFail - Summary of email discussion discussion

revision of R3-210993

Samsung - moderator R3-111-e

AI: 10.2.1.6

noted [WTS] [JSN]
R3-211187 MRO for PScell Change Failure draftCR Samsung NR_ENDC_SON_MDT_enh-Core Rel-17 R3-111-e

AI: 10.2.1.6

withdrawn [WTS] [JSN]
R3-211189 MRO for PScell Change Failure draftCR

revised to R3-211333

Samsung, NR_ENDC_SON_MDT_enh-Core Rel-17 R3-111-e

AI: 10.2.1.6

revised [WTS] [JSN]
R3-211209 LS on information needed for MRO in SCG Failure Report LS out

LS To: RAN WG2

revision of R3-210263

revised to R3-211332

Samsung NR_ENDC_SON_MDT_enh Rel-17 R3-111-e

AI: 10.2.1.6

revised [WTS] [JSN]
R3-211332 LS on information needed for MRO in SCG Failure Report LS out

LS To: RAN WG2

revision of R3-211209

Samsung NR_ENDC_SON_MDT_enh Rel-17 R3-111-e

AI: 10.2.1.6

agreed [WTS] [JSN]
R3-211333 MRO for PScell Change Failure draftCR

revision of R3-211189

Samsung, Nokia, Nokia Shanghai Bell, Ericsson, Huawei NR_ENDC_SON_MDT_enh-Core Rel-17 R3-111-e

AI: 10.2.1.6

endorsed [WTS] [JSN]

22 documents (0.37506294250488 seconds)