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-260065 (pCR to TR 38.760-3) Evaluation criteria for 6G RAN-CN IF solutions pCR Qualcomm Incorporated, T-mobile USA, Verizon, NTT Docomo, Boost Mobile Networks, JIO Platforms, Sony, FiberCop, Charter Communications, Telstra, Google 38.760-3 0.2.0 FS_6G_Radio Rel-20 R3-131

AI: 10.3.2.3

available [WTS] [JSN]
R3-260164 Evaluation criteria for RAN-CN control plane interface options pCR Huawei 38.760-3 0.2.0 FS_6G_Radio Rel-20 R3-131

AI: 10.3.2.3

available [WTS] [JSN]
R3-260189 (pCR to TR38.760-3) Evaluation Criteria for 6G RAN-CN Interface Options pCR NEC 38.760-3 0.2.0 FS_6G_Radio Rel-20 R3-131

AI: 10.3.2.3

available [WTS] [JSN]
R3-260244 Evaluation Criteria of RAN-CN Interface Options pCR CATT 38.760-3 0.2.0 FS_6G_Radio Rel-20 R3-131

AI: 10.3.2.3

available [WTS] [JSN]
R3-260341 Evaluation for RAN-CN interface options discussion China Telecom FS_6G_Radio Rel-20 R3-131

AI: 10.3.2.3

noted [WTS] [JSN]
R3-260355 Evaluation Criteria for RAN-CN Interface Options pCR Tejas Network Limited 38.760-3 0.2.0 FS_6G_Radio Rel-20 R3-131

AI: 10.3.2.3

available [WTS] [JSN]
R3-260407 Template for comparison of different protocol options for control plane in 6G between 6GR and CN discussion VODAFONE Group Plc FS_6G_Radio Rel-20 R3-131

AI: 10.3.2.3

available [WTS] [JSN]
R3-260440 Proposal on Evaluation Criteria for RAN-CN CP interface options discussion Deutsche Telekom, FiberCop FS_6G_Radio Rel-20 R3-131

AI: 10.3.2.3

noted [WTS] [JSN]
R3-260453 (pCR to 38.760) Evaluation Criteria for 6G RAN–CN CP Interface discussion Jio Platforms FS_6G_Radio Rel-20 R3-131

AI: 10.3.2.3

withdrawn [WTS] [JSN]
R3-260468 On how to achieve interim study results on "P2P vs SBI" discussion Ericsson, Vodafone, Jio Platforms FS_6G_Radio Rel-20 R3-131

AI: 10.3.2.3

available [WTS] [JSN]
R3-260487 Evaluation Criteria for comparing P2P versus SBI pCR Nokia, Ericsson 38.760-3 0.3.0 FS_6G_Radio Rel-20 R3-131

AI: 10.3.2.3

available [WTS] [JSN]
R3-260495 (pCR to 38.760) Evaluation Criteria for 6G RAN–CN CP Interface discussion Jio Platforms FS_6G_Radio Rel-20 R3-131

AI: 10.3.2.3

available [WTS] [JSN]
R3-260551 Discussion on evaluation criteria for 6G RAN-CN control plane interface pCR ZTE Corporation 38.760-3 0.2.0 FS_6G_Radio Rel-20 R3-131

AI: 10.3.2.3

available [WTS] [JSN]
R3-260588 Discussion on the evaluation criteria for RAN-CN interface design pCR

revised to R3-260772

Samsung 38.760-3 0.2.0 FS_6G_Radio Rel-20 R3-131

AI: 10.3.2.3

revised [WTS] [JSN]
R3-260611 Necessary considerations for 6G RAN-CN interface options discussion NTT DOCOMO INC.. FS_6G_Radio Rel-20 R3-131

AI: 10.3.2.3

available [WTS] [JSN]
R3-260636 Discussion on RAN-CN interface evaluation criteria discussion Rakuten Mobile, Inc FS_6G_Radio Rel-20 R3-131

AI: 10.3.2.3

available [WTS] [JSN]
R3-260771 Summary of Offline Discussion on CB # 18_6GRANCNeval discussion Samsung FS_6G_Radio Rel-20 R3-131

AI: 10.3.2.3

noted [WTS] [JSN]
R3-260772 Discussion on the evaluation criteria for RAN-CN interface design pCR

revision of R3-260588

revised to R3-260780

Samsung 38.760-3 0.2.0 FS_6G_Radio Rel-20 R3-131

AI: 10.3.2.3

revised [WTS] [JSN]
R3-260780 pCR for RAN-CN interface option evaluation criteria pCR

revision of R3-260772

Samsung, Pengcheng Laboratory, Huawei, China Unicom, Ericsson, Nokia, China Telecom, LG Electronics, CMCC, NEC, CATT, Verizon, Ofinno, Docomo, Google, Jio Platforms, ZTE, Lenovo, Rakuten,T-Mobile USA, Tejas Networks, AT&T, Qualcomm, FiberCop, Boost Mobile, Deutsche Telekom, InterDigital 38.760-3 0.2.0 FS_6G_Radio Rel-20 R3-131

AI: 10.3.2.3

agreed [WTS] [JSN]

19 documents (0.43793892860413 seconds)