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 |
|---|---|---|---|---|---|---|---|---|---|
| RP-253061 | 6G Architecture and 5G-6G Migration | discussion | AT&T | FS_6G_RAN_Scen_Req |
RP-110 AI: 8.2.1.2 |
available | [WTS] [JSN] | ||
| RP-253079 | TP on Requirements for architecture and migration in 6G for TR 38.914 | discussion | Deutsche Telekom, Vodafone, Orange, Telecom Italia, Turkcell, Odido Spark NZ, BT, Bouygues Telecom, Telefonica, Telia Company, SK Telecom, KPN, Rakuten Mobile, CK Hutchison, Telenor, Boost Mobile Network, Jio Platforms |
RP-110 AI: 8.2.1.2 |
available | [WTS] [JSN] | |||
| RP-253087 | TP on Architecture/migration requirements for NTN | discussion | THALES, Sateliot, Iridium, Viasat, ST Engineering iDirect, Novamint, Airbus, Fraunhofer IIS, Fraunhofer HHI, Eutelsat, TNO, EchoStar, Gatehous Satcom, SES, ESA, Hispasat, Amazon | FS_6G_RAN_Scen_Req | Rel-20 |
RP-110 AI: 8.2.1.2 |
available | [WTS] [JSN] | |
| RP-253120 | Discussion on 6G RAN Architecture | discussion | CMCC | FS_6G_RAN_Scen_Req | Rel-20 |
RP-110 AI: 8.2.1.2 |
available | [WTS] [JSN] | |
| RP-253121 | Requirements for RAN data collection architecture | discussion | CMCC | FS_6G_RAN_Scen_Req | Rel-20 |
RP-110 AI: 8.2.1.2 |
available | [WTS] [JSN] | |
| RP-253122 | Views on architecture of 6G RAN for Sensing | discussion | CMCC | FS_6G_RAN_Scen_Req | Rel-20 |
RP-110 AI: 8.2.1.2 |
available | [WTS] [JSN] | |
| RP-253123 | Views on coexistence of 6G and 4G | discussion | CMCC | FS_6G_RAN_Scen_Req | Rel-20 |
RP-110 AI: 8.2.1.2 |
available | [WTS] [JSN] | |
| RP-253160 | Requirements for 6G RAN Architecture and migration | discussion | Samsung | FS_6G_RAN_Scen_Req | Rel-20 |
RP-110 AI: 8.2.1.2 |
available | [WTS] [JSN] | |
| RP-253178 | Discussion on requirements for 6G architecture and migration | discussion | Spreadtrum, UNISOC |
RP-110 AI: 8.2.1.2 |
available | [WTS] [JSN] | |||
| RP-253184 | Discussion on requirements for architecture and migration for 6G |
discussion revised to RP-253366 |
NTT DOCOMO, INC., Telstra, Tejas Networks, Boost Mobile, Verizon Wireless, Qualcomm Inc, FiberCop, KT Corp, Jio Platforms, T-Mobile USA, IIT-Hyderabad, WiSiG Networks, NEC, Fujitsu, AT&T, SONY, Deutsche Telekom, LG Electronics, CEWIT | Rel-20 |
RP-110 AI: 8.2.1.2 |
revised | [WTS] [JSN] | ||
| RP-253195 | Views on 6G Requirements for architecture and migration | discussion | ZTE Corporation | FS_6G_RAN_Scen_Req | Rel-20 |
RP-110 AI: 8.2.1.2 |
available | [WTS] [JSN] | |
| RP-253205 | NTN specific proposals related to updates to architecture and migration clause | discussion | ViaSat Satellite Holdings Ltd, Novamint, Airbus, Sateliot, Gatehouse Satcom, ESA, ST Engineering iDirect, EchoStar, Thales, Skylo, Terrestar |
RP-110 AI: 8.2.1.2 |
available | [WTS] [JSN] | |||
| RP-253238 | Requirements for architecture and migration | discussion | Xiaomi | FS_6G_RAN_Scen_Req | Rel-20 |
RP-110 AI: 8.2.1.2 |
available | [WTS] [JSN] | |
| RP-253239 | Discussion on requirement for data collection and observability | discussion | Xiaomi | FS_6G_RAN_Scen_Req | Rel-20 |
RP-110 AI: 8.2.1.2 |
available | [WTS] [JSN] | |
| RP-253267 | Discussion on architecture requirement | discussion | CATT | FS_6G_RAN_Scen_Req | Rel-20 |
RP-110 AI: 8.2.1.2 |
available | [WTS] [JSN] | |
| RP-253276 | Views on Data collection and transfer design | discussion | CATT, CBN, China Broadnet | FS_6G_RAN_Scen_Req | Rel-20 |
RP-110 AI: 8.2.1.2 |
available | [WTS] [JSN] | |
| RP-253308 | 6G RAN Architecture Requirements |
discussion revision of RP-252224 |
Ericsson | FS_6G_RAN_Scen_Req | Rel-20 |
RP-110 AI: 8.2.1.2 |
available | [WTS] [JSN] | |
| RP-253309 | Observability Requirements in 6G |
discussion revision of RP-252227 revised to RP-253524 |
Ericsson, Deutsche Telekom, NTT DOCOMO, SK Telecom, CHTTL, Nokia, T-Mobile USA, Verizon, China Unicom, AT&T, Telefonica, Telia Company, JIO Platforms, Qualcomm Incorporated, CATT | FS_6G_RAN_Scen_Req | Rel-20 |
RP-110 AI: 8.2.1.2 |
revised | [WTS] [JSN] | |
| RP-253327 | Proposed Requirements and SID update: Interworking between 6GR and 4G |
discussion revision of RP-252229 |
VODAFONE, NTT DOCOMO, SK Telecom, CHTTL |
RP-110 AI: 8.2.1.2 |
available | [WTS] [JSN] | |||
| RP-253366 | Discussion on requirements for architecture and migration for 6G |
discussion revision of RP-253184 |
NTT DOCOMO, INC., Telstra, Tejas Networks, Boost Mobile, Verizon Wireless, Qualcomm Inc, FiberCop, KT Corp, Jio Platforms, T-Mobile USA, IIT-Hyderabad, WiSiG Networks, NEC, Fujitsu, AT&T, SONY, Deutsche Telekom, LG Electronics, CEWIT, Mavenir, CMCC | Rel-20 |
RP-110 AI: 8.2.1.2 |
available | [WTS] [JSN] | ||
| RP-253412 | Requirements for Architecture and Migration | discussion | Reliance Jio | Rel-20 |
RP-110 AI: 8.2.1.2 |
available | [WTS] [JSN] | ||
| RP-253500 | Views on 6G RAN Architecture for Data Framework | discussion | PML |
RP-110 AI: 8.2.1.2 |
available | [WTS] [JSN] | |||
| RP-253524 | Observability Requirements in 6G |
discussion revision of RP-253309 |
Ericsson, Deutsche Telekom, NTT DOCOMO, SK Telecom, CHTTL, Nokia, T-Mobile USA, Verizon, China Unicom, AT&T, Telefonica, Telia Company, JIO Platforms, Qualcomm Incorporated, CATT, Lenovo | FS_6G_RAN_Scen_Req | Rel-20 |
RP-110 AI: 8.2.1.2 |
available | [WTS] [JSN] | |
| RP-253753 | pCR to TR 38.914 v0.2.0 with RAN #110 results for requirements for architecture and migration | pCR | NTT DOCOMO | 38.914 0.2.0 | FS_6G_RAN_Scen_Req | Rel-20 |
RP-110 AI: 8.2.1.2 |
reserved | [WTS] [JSN] |
24 documents (0.38084816932678 seconds)