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-260069 | TP on NTN new services | pCR | THALES | 38.914 0.3.0 | FS_6G_RAN_Scen_Req | Rel-20 |
RP-111 AI: 8.2.1.4 |
withdrawn | [WTS] [JSN] |
| RP-260086 | Scenarios and Requirements for 6G NTN | discussion | CMCC | FS_6G_RAN_Scen_Req | Rel-20 |
RP-111 AI: 8.2.1.4 |
noted | [WTS] [JSN] | |
| RP-260087 | Requirements of AI for 6G RAN | discussion | CMCC | FS_6G_RAN_Scen_Req | Rel-20 |
RP-111 AI: 8.2.1.4 |
noted | [WTS] [JSN] | |
| RP-260088 | Requirements of 6G RAN for AI | discussion | CMCC | FS_6G_RAN_Scen_Req | Rel-20 |
RP-111 AI: 8.2.1.4 |
noted | [WTS] [JSN] | |
| RP-260089 | Consideration on 6G service-based RAN | discussion | CMCC | FS_6G_RAN_Scen_Req | Rel-20 |
RP-111 AI: 8.2.1.4 |
noted | [WTS] [JSN] | |
| RP-260090 | Requirements for Network Digital Twin in 6G RAN | discussion | CMCC | FS_6G_RAN_Scen_Req | Rel-20 |
RP-111 AI: 8.2.1.4 |
noted | [WTS] [JSN] | |
| RP-260091 | Discussion on sensing requirements | discussion | CMCC | FS_6G_RAN_Scen_Req | Rel-20 |
RP-111 AI: 8.2.1.4 |
noted | [WTS] [JSN] | |
| RP-260092 | Support of Positioning Services for 6G | discussion | NextNav | FS_6G_RAN_Scen_Req | Rel-20 |
RP-111 AI: 8.2.1.4 |
withdrawn | [WTS] [JSN] | |
| RP-260196 | NTN preferred/priority mode for 6G | discussion | KT Corp., Thales, Iridium, Viasat | FS_6G_RAN_Scen_Req | Rel-20 |
RP-111 AI: 8.2.1.4 |
noted | [WTS] [JSN] | |
| RP-260215 | Consideration on support of Massive Communication IoT | discussion | Huawei, HiSilicon, VODAFONE | FS_6G_RAN_Scen_Req | Rel-20 |
RP-111 AI: 8.2.1.4 |
noted | [WTS] [JSN] | |
| RP-260216 | Consideration on supporting immersive communication services | discussion | Huawei, HiSilicon, China Telecom | FS_6G_RAN_Scen_Req | Rel-20 |
RP-111 AI: 8.2.1.4 |
noted | [WTS] [JSN] | |
| RP-260217 | Consideration on supporting ISAC services | discussion | Huawei, HiSilicon, CAICT, China Telcom, China Unicom, KT Corp., LG Uplus,SK Telecom, Telecom Italia | FS_6G_RAN_Scen_Req | Rel-20 |
RP-111 AI: 8.2.1.4 |
noted | [WTS] [JSN] | |
| RP-260234 | Requirements for NTN | discussion | Qualcomm Incorporated | FS_6G_RAN_Scen_Req | Rel-20 |
RP-111 AI: 8.2.1.4 |
noted | [WTS] [JSN] | |
| RP-260235 | Requirements of new and existing services | discussion | Qualcomm Incorporated | FS_6G_RAN_Scen_Req | Rel-20 |
RP-111 AI: 8.2.1.4 |
noted | [WTS] [JSN] | |
| RP-260240 | Requirements on Positioning and Sensing | discussion | Qualcomm Technologies Ireland | FS_6G_RAN_Scen_Req | Rel-20 |
RP-111 AI: 8.2.1.4 |
noted | [WTS] [JSN] | |
| RP-260243 | on requirements of new and existing services for 6G | discussion | Apple | FS_6G_RAN_Scen_Req | Rel-20 |
RP-111 AI: 8.2.1.4 |
noted | [WTS] [JSN] | |
| RP-260244 | Requirements for massive communication in 6G | discussion | CMCC | FS_6G_RAN_Scen_Req | Rel-20 |
RP-111 AI: 8.2.1.4 |
noted | [WTS] [JSN] | |
| RP-260246 | Considerations on Immersive Communication scenarios | discussion | China Telecom | FS_6G_RAN_Scen_Req | Rel-20 |
RP-111 AI: 8.2.1.4 |
noted | [WTS] [JSN] | |
| RP-260260 | Requirements of Integrated Sensing And Communication (ISAC) | discussion | Xiaomi | FS_6G_RAN_Scen_Req | Rel-20 |
RP-111 AI: 8.2.1.4 |
noted | [WTS] [JSN] | |
| RP-260262 | Considerations on scenarios and service requirements of 6G NTN | discussion | China Telecommunications Corp. | FS_6G_RAN_Scen_Req | Rel-20 |
RP-111 AI: 8.2.1.4 |
noted | [WTS] [JSN] | |
| RP-260266 | On support of tethered device services in 6G | discussion | Xiaomi, Meta, Apple, BYD, Verizon, MediaTek Inc, Hyundai Motor Company, Toyota ITC | FS_6G_RAN_Scen_Req | Rel-20 |
RP-111 AI: 8.2.1.4 |
noted | [WTS] [JSN] | |
| RP-260279 | 3GPP specific requirements on NTN |
discussion revision of RP-253091 |
Ericsson, CHTTL, CMCC, ESA, FirstNet, KT Corp., Nokia, T-Mobile USA, Telstra, SK Telecom, AT&T, Jio Platforms | FS_6G_RAN_Scen_Req | Rel-20 |
RP-111 AI: 8.2.1.4 |
noted | [WTS] [JSN] | |
| RP-260280 | Requirements on support for positioning | discussion | Ericsson, Nokia | FS_6G_RAN_Scen_Req | Rel-20 |
RP-111 AI: 8.2.1.4 |
noted | [WTS] [JSN] | |
| RP-260281 | 6G Positioning Architecture |
discussion revision of RP-253525 |
Ericsson | FS_6G_RAN_Scen_Req | Rel-20 |
RP-111 AI: 8.2.1.4 |
noted | [WTS] [JSN] | |
| RP-260287 | Requirements for supporting time-critical communications in 6G | discussion | Ericsson, AT&T, CMCC, FirstNet, T-Mobile USA, Telstra, Verizon | FS_6G_RAN_Scen_Req | Rel-20 |
RP-111 AI: 8.2.1.4 |
noted | [WTS] [JSN] | |
| RP-260294 | Adding Multihop Relays to Sidelink |
discussion revised to RP-260472 |
DHS Science & Technology, DISA, Lockheed Martin, VIAVI Solutions, Erillisverkot, FirstNet, DeepSig Inc | FS_6G_RAN_Scen_Req | Rel-20 |
RP-111 AI: 8.2.1.4 |
revised | [WTS] [JSN] | |
| RP-260305 | Sensing Requirements | discussion | MediaTek Inc. | FS_6G_RAN_Scen_Req | Rel-20 |
RP-111 AI: 8.2.1.4 |
noted | [WTS] [JSN] | |
| RP-260310 | 6G ISAC use case on infrastructure collapse monitoring | discussion | VIAVI Solutions, ZTE Corporation | FS_6G_RAN_Scen_Req | Rel-20 |
RP-111 AI: 8.2.1.4 |
noted | [WTS] [JSN] | |
| RP-260312 | On support of sensing in 6G | discussion | T-Mobile USA, Ericsson, Nokia, Verizon | FS_6G_RAN_Scen_Req | Rel-20 |
RP-111 AI: 8.2.1.4 |
noted | [WTS] [JSN] | |
| RP-260313 | Requirements for support of FWA in 6G |
discussion revised to RP-260591 |
T-Mobile USA, Ericsson, MediaTek Inc., Nokia, Verizon | FS_6G_RAN_Scen_Req | Rel-20 |
RP-111 AI: 8.2.1.4 |
revised | [WTS] [JSN] | |
| RP-260319 | 6G Positioning Requirements | discussion | T-Mobile USA, Ericsson | FS_6G_RAN_Scen_Req | Rel-20 |
RP-111 AI: 8.2.1.4 |
noted | [WTS] [JSN] | |
| RP-260321 | AI/ML Traffic Requirements | discussion | T-Mobile USA, Nokia | FS_6G_RAN_Scen_Req | Rel-20 |
RP-111 AI: 8.2.1.4 |
noted | [WTS] [JSN] | |
| RP-260327 | Considerations on 6G NTN’s functionalities and services | discussion | Xiaomi | FS_6G_RAN_Scen_Req | Rel-20 |
RP-111 AI: 8.2.1.4 |
noted | [WTS] [JSN] | |
| RP-260330 | Text proposal on ISAC to remove “human” requirements | discussion | Huawei, HiSilicon | FS_6G_RAN_Scen_Req | Rel-20 |
RP-111 AI: 8.2.1.4 |
noted | [WTS] [JSN] | |
| RP-260333 | Requirements for 6GR services | discussion | ZTE Corporation | FS_6G_RAN_Scen_Req | Rel-20 |
RP-111 AI: 8.2.1.4 |
noted | [WTS] [JSN] | |
| RP-260334 | Views on 6G ISAC use cases and requirements | discussion | ZTE Corporation, Turk Telekom, Verizon, China Telecom, China Unicom, Telecom Italia, CAICT, ETRI, Queens University Belfast, Pengcheng Laboratory, Shanghai Jiao Tong University, Sanechips, CATT, VIAVI | FS_6G_RAN_Scen_Req | Rel-20 |
RP-111 AI: 8.2.1.4 |
noted | [WTS] [JSN] | |
| RP-260335 | Views on 6G positioning service | discussion | ZTE Corporation, China Telecom, China Unicom, Sanechips | FS_6G_RAN_Scen_Req | Rel-20 |
RP-111 AI: 8.2.1.4 |
noted | [WTS] [JSN] | |
| RP-260338 | Consideration on 6G AIML New Use Case - Agentic AI | discussion | ZTE Corporation, Sanchips, Jio Platforms, NEC, CAICT, China Unicom, Tejas Network, Pengcheng Laboratory, TCL, FiberCop, Seoul National University, Verizon | FS_6G_RAN_Scen_Req | Rel-20 |
RP-111 AI: 8.2.1.4 |
noted | [WTS] [JSN] | |
| RP-260346 | Requirements for 6G IoT | discussion | Spreadtrum, UNISOC | FS_6G_RAN_Scen_Req | Rel-20 |
RP-111 AI: 8.2.1.4 |
noted | [WTS] [JSN] | |
| RP-260352 | Views on supporting new and existing services for 6G | discussion | NTT DOCOMO, INC. | FS_6G_RAN_Scen_Req | Rel-20 |
RP-111 AI: 8.2.1.4 |
noted | [WTS] [JSN] | |
| RP-260356 | TP on requirements of existing service for 6G positioning | discussion | CATT | FS_6G_RAN_Scen_Req | Rel-20 |
RP-111 AI: 8.2.1.4 |
noted | [WTS] [JSN] | |
| RP-260363 | Views on service requirements of 6G NTN | discussion | CATT | FS_6G_RAN_Scen_Req | Rel-20 |
RP-111 AI: 8.2.1.4 |
noted | [WTS] [JSN] | |
| RP-260364 | Consistent User Experience for Immersive Communication | discussion | CATT | FS_6G_RAN_Scen_Req | Rel-20 |
RP-111 AI: 8.2.1.4 |
noted | [WTS] [JSN] | |
| RP-260370 | Discussion on 6G requirements for ISAC | discussion | vivo | FS_6G_RAN_Scen_Req | Rel-20 |
RP-111 AI: 8.2.1.4 |
noted | [WTS] [JSN] | |
| RP-260377 | Views on 6G requirements for supporting RAN computing for AI services | discussion | CHTTL | FS_6G_RAN_Scen_Req | Rel-20 |
RP-111 AI: 8.2.1.4 |
noted | [WTS] [JSN] | |
| RP-260380 | Positioning service requirement in 6GR | discussion | CEWiT, Tejas Networks, IITM, IITK | FS_6G_RAN_Scen_Req | Rel-20 |
RP-111 AI: 8.2.1.4 |
noted | [WTS] [JSN] | |
| RP-260384 | New sensing scenarios and requirements in 6G | discussion | OPPO | FS_6G_RAN_Scen_Req | Rel-20 |
RP-111 AI: 8.2.1.4 |
noted | [WTS] [JSN] | |
| RP-260387 | Views on 6G requirements for supporting AI services | discussion | SK Telecom | FS_6G_RAN_Scen_Req | Rel-20 |
RP-111 AI: 8.2.1.4 |
noted | [WTS] [JSN] | |
| RP-260388 | Views on 6G requirements for supporting sensing | discussion | SK Telecom | FS_6G_RAN_Scen_Req | Rel-20 |
RP-111 AI: 8.2.1.4 |
noted | [WTS] [JSN] | |
| RP-260391 | 6G NTN Requirements | discussion | Samsung | FS_6G_RAN_Scen_Req | Rel-20 |
RP-111 AI: 8.2.1.4 |
noted | [WTS] [JSN] | |
| RP-260392 | Requirements for 6G Positioning in Day 1 | discussion | LG Electronics Deutschland | FS_6G_RAN_Scen_Req | Rel-20 |
RP-111 AI: 8.2.1.4 |
noted | [WTS] [JSN] | |
| RP-260395 | Requirements of supporting AI services | discussion | Xiaomi | FS_6G_RAN_Scen_Req | Rel-20 |
RP-111 AI: 8.2.1.4 |
noted | [WTS] [JSN] | |
| RP-260402 | Views on 6G NTN services | discussion | ZTE Corporation, Sanechips | FS_6G_RAN_Scen_Req | Rel-20 |
RP-111 AI: 8.2.1.4 |
noted | [WTS] [JSN] | |
| RP-260417 | Further considerations on 6G massive IoT requirements | discussion | Sony, AT&T, Semtech, Nordic Semiconductor ASA | FS_6G_RAN_Scen_Req | Rel-20 |
RP-111 AI: 8.2.1.4 |
noted | [WTS] [JSN] | |
| RP-260418 | Requirements for Sensing in TR 38.914 | pCR | ROBERT BOSCH GmbH | 38.914 0.3.0 | FS_6G_RAN_Scen_Req | Rel-20 |
RP-111 AI: 8.2.1.4 |
withdrawn | [WTS] [JSN] |
| RP-260420 | Positioning, Navigation and Timing (PNT) with 6GR NTN | pCR | Airbus, Thales, ESA, Aalyria, TNO, Novamint, Gatehouse Satcom, BMW, Eutelsat, SES, Hispasat, Robert Bosch GmbH, AST Space Mobile, Iridium, Amazon Web Services, Toyota, Sateliot, Terrestar, Fraunhofer IIS, Fraunhofer HHI, ETRI, JSAT | 38.914 0.3.0 | FS_6G_RAN_Scen_Req | Rel-20 |
RP-111 AI: 8.2.1.4 |
not pursued | [WTS] [JSN] |
| RP-260469 | Views on requirements of new and existing services for 6G NTN | discussion | CSCN, China Unicom, CATT, Xiaomi | FS_6G_RAN_Scen_Req | Rel-20 |
RP-111 AI: 8.2.1.4 |
noted | [WTS] [JSN] | |
| RP-260471 | Service requirements (IoT) | discussion | MediaTek Inc. | FS_6G_RAN_Scen_Req | Rel-20 |
RP-111 AI: 8.2.1.4 |
noted | [WTS] [JSN] | |
| RP-260472 | Adding Multi-hop Relays to Sidelink |
discussion revision of RP-260294 |
DHS Science & Technology, DISA, Lockheed Martin, VIAVI Solutions, Erillisverkot, FirstNet, DeepSig Inc, NIST | FS_6G_RAN_Scen_Req | Rel-20 |
RP-111 AI: 8.2.1.4 |
noted | [WTS] [JSN] | |
| RP-260475 | Massive Communication (IoT) requirements | discussion | Ericsson, AT&T, CMCC, Itron, Nokia, Nordic Semiconductor, NTT DOCOMO, Semtech, Sony, Verizon, Vodafone | FS_6G_RAN_Scen_Req | Rel-20 |
RP-111 AI: 8.2.1.4 |
noted | [WTS] [JSN] | |
| RP-260477 | TP for TR 38.914 for Geographical Zone Sensing in new 6G Services | discussion | Jio Platforms | FS_6G_RAN_Scen_Req | Rel-20 |
RP-111 AI: 8.2.1.4 |
noted | [WTS] [JSN] | |
| RP-260478 | Requirements for Sensing in TR 38.914 | pCR | ROBERT BOSCH GmbH | 38.914 0.3.0 | FS_6G_RAN_Scen_Req | Rel-20 |
RP-111 AI: 8.2.1.4 |
not pursued | [WTS] [JSN] |
| RP-260479 | Additional 6G Service Requirements for Vehicular Use Cases | discussion | ROBERT BOSCH GmbH, Volkswagen AG, BMW AG, AUMOVIO, Toyota ITC, Fraunhofer IIS | FS_6G_RAN_Scen_Req | Rel-20 |
RP-111 AI: 8.2.1.4 |
noted | [WTS] [JSN] | |
| RP-260484 | On ISAC Scenarios and Requirements | discussion | Lenovo | FS_6G_RAN_Scen_Req | Rel-20 |
RP-111 AI: 8.2.1.4 |
noted | [WTS] [JSN] | |
| RP-260486 | Additional requirements for new and existing services | discussion | AT&T | FS_6G_RAN_Scen_Req | Rel-20 |
RP-111 AI: 8.2.1.4 |
noted | [WTS] [JSN] | |
| RP-260493 | NTN operator views on 6G NTN in the first release of 6G | discussion | ViaSat Satellite Holdings Ltd, Terrestar, AST SpaceMobile, Inmarsat, Ligado Networks, Omnispace, Thuraya | FS_6G_RAN_Scen_Req | Rel-20 |
RP-111 AI: 8.2.1.4 |
noted | [WTS] [JSN] | |
| RP-260497 | TP for TR 38.914 for addition of Environmental Sensing for detection of extreme weather events in new 6G Services | discussion | Telstra, T-Mobile USA, Deutsche Telekom, Telenor, Turkcell, KDDI, Boost Mobile Network, Jio Platforms, Rakuten Mobile, Telecom Italia, Telefonica, Telus | FS_6G_RAN_Scen_Req | Rel-20 |
RP-111 AI: 8.2.1.4 |
noted | [WTS] [JSN] | |
| RP-260590 | Requirements for Voice Call Services | discussion | Jio Platforms | FS_6G_RAN_Scen_Req | Rel-20 |
RP-111 AI: 8.2.1.4 |
noted | [WTS] [JSN] | |
| RP-260591 | Requirements for support of FWA in 6G |
discussion revision of RP-260313 |
T-Mobile USA, Ericsson, MediaTek Inc., Nokia, Verizon | FS_6G_RAN_Scen_Req | Rel-20 |
RP-111 AI: 8.2.1.4 |
noted | [WTS] [JSN] | |
| RP-260612 | Protecting critical sovereign national and economic security with 6G | discussion | NextNav | FS_6G_RAN_Scen_Req | Rel-20 |
RP-111 AI: 8.2.1.4 |
noted | [WTS] [JSN] | |
| RP-260683 | Views on positioning in 6G Radio study item | discussion | CATT | FS_6G_Radio | Rel-20 |
RP-111 AI: 8.2.1.4 |
noted | [WTS] [JSN] | |
| RP-260701 | Requirements for 6GR Sensing | discussion | IIT Kanpur, IIT Madras, CEWIT, Tejas Networks | FS_6G_RAN_Scen_Req | Rel-20 |
RP-111 AI: 8.2.1.4 |
noted | [WTS] [JSN] | |
| RP-260722 | Moderator's summary for 6G requirements of new and existing services |
report revised to RP-260787 |
CMCC | FS_6G_RAN_Scen_Req | Rel-20 |
RP-111 AI: 8.2.1.4 |
revised | [WTS] [JSN] | |
| RP-260731 | Moderator's pCR to TS 38.914 on 6G requirements of new and existing services |
pCR revised to RP-260824 |
CMCC | 38.914 0.3.0 | FS_6G_RAN_Scen_Req | Rel-20 |
RP-111 AI: 8.2.1.4 |
revised | [WTS] [JSN] |
| RP-260787 | Moderator's summary for 6G requirements of new and existing services |
report revision of RP-260722 revised to RP-260819 |
CMCC | FS_6G_RAN_Scen_Req | Rel-20 |
RP-111 AI: 8.2.1.4 |
revised | [WTS] [JSN] | |
| RP-260819 | Moderator's summary for 6G requirements of new and existing services |
report revision of RP-260787 |
CMCC | FS_6G_RAN_Scen_Req | Rel-20 |
RP-111 AI: 8.2.1.4 |
noted | [WTS] [JSN] | |
| RP-260824 | Moderator's pCR to TS 38.914 on 6G requirements of new and existing services |
pCR revision of RP-260731 |
CMCC | 38.914 0.3.0 | FS_6G_RAN_Scen_Req | Rel-20 |
RP-111 AI: 8.2.1.4 |
approved | [WTS] [JSN] |
77 documents (0.36730599403381 seconds)