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-255266 | Remaing issues for IoT NTN | other | ZTE Corporation | IoT_NTN_Ph3-Core | Rel-19 |
R3-129 AI: 15.2 |
available | [WTS] [JSN] | |
| R3-255293 | Discussion on the support of S&F | discussion | Nokia, Nokia Shanghai Bell | IoT_NTN_Ph3-Core | Rel-19 |
R3-129 AI: 15.2 |
withdrawn | [WTS] [JSN] | |
| R3-255294 | (TP to BL CR for TS 36.300) Correction on S1 Removal | other | Nokia, Nokia Shanghai Bell, Huawei, Ericsson, LG Electronics, Samsung | IoT_NTN_Ph3-Core | Rel-19 |
R3-129 AI: 15.2 |
agreed | [WTS] [JSN] | |
| R3-255295 | (TP to BL CR for TS 36.413) Support of regenerative payload | other | Nokia, Nokia Shanghai Bell, ZTE Corporation, CATT, Qualcomm, CMCC, Samsung, China Telecom, LG Electronics, Xiaomi | IoT_NTN_Ph3-Core | Rel-19 |
R3-129 AI: 15.2 |
available | [WTS] [JSN] | |
| R3-255311 | (TP for TS 36.300) Support for Regenerative Payload for IoT NTN | other | Qualcomm Incorporated, Nokia, Nokia Shanghai Bell, ZTE, CATT, China Telecom, CMCC, LG Electronics, Xiaomi | IoT_NTN_Ph3-Core | Rel-19 |
R3-129 AI: 15.2 |
available | [WTS] [JSN] | |
| R3-255312 | Discussion on Support for IoT NTN for Regenerative Payload | discussion | Qualcomm Incorporated | IoT_NTN_Ph3-Core | Rel-19 |
R3-129 AI: 15.2 |
available | [WTS] [JSN] | |
| R3-255345 | Remaining issue on support of regenerative payload for IoT NTN | discussion | Samsung | IoT_NTN_Ph3-Core | Rel-19 |
R3-129 AI: 15.2 |
available | [WTS] [JSN] | |
| R3-255381 | Discussion on remaining issues for IoT NTN | discussion | China Telecom | IoT_NTN_Ph3-Core | Rel-19 |
R3-129 AI: 15.2 |
available | [WTS] [JSN] | |
| R3-255443 | (TP for TS 36.300) IoT-NTN Switchover (FLSO) & Store-and-Forward Principles | other | Jio Platforms | IoT_NTN_Ph3-Core | Rel-19 |
R3-129 AI: 15.2 |
available | [WTS] [JSN] | |
| R3-255507 | (TP for TS 36.413) S1 Removal completion | other | Huawei, LG Electronics, Nokia, Nokia Shanghai Bell, Ericsson, Thales, Jio Platforms, CATT, Qualcomm Incorporated, Deutsche Telekom,Samsung | IoT_NTN_Ph3-Core | Rel-19 |
R3-129 AI: 15.2 |
agreed | [WTS] [JSN] | |
| R3-255509 | (TP to BL CR for TS 36.300) Hard FLSO and MME management |
other revised to R3-255897 |
Huawei, Ericsson, Thales, Jio Platforms, Deutsche Telekom | IoT_NTN_Ph3-Core | Rel-19 |
R3-129 AI: 15.2 |
revised | [WTS] [JSN] | |
| R3-255511 | (TP to BL CR for TS 36.300) Removal of the Suspend/Resume part of TS 36.300 | other | Huawei | IoT_NTN_Ph3-Core | Rel-19 |
R3-129 AI: 15.2 |
withdrawn | [WTS] [JSN] | |
| R3-255512 | (TP for TS 36.300) Full eNB as Regenerative Payload - TNL aspetcs | other | Huawei, Jio Platforms | IoT_NTN_Ph3-Core | Rel-19 |
R3-129 AI: 15.2 |
available | [WTS] [JSN] | |
| R3-255513 | (TP for TS 36.300) Discussion on S&F mode transition | other | Huawei, Jio Platforms, Ericsson | IoT_NTN_Ph3-Core | Rel-19 |
R3-129 AI: 15.2 |
available | [WTS] [JSN] | |
| R3-255514 | (TP for TS 36.300) Provision of S&F Mode Indication of neighbour cell list | other | Huawei, Ericsson, Jio Platforms | IoT_NTN_Ph3-Core | Rel-19 |
R3-129 AI: 15.2 |
available | [WTS] [JSN] | |
| R3-255515 | Discussion on Reply LS to SA2 on support of Full eNB as Regenerative Payload | other | Huawei, Jio Platforms, Ericsson | IoT_NTN_Ph3-Core | Rel-19 |
R3-129 AI: 15.2 |
available | [WTS] [JSN] | |
| R3-255516 | [DRAFT] Reply LS on Support of Regenerative-based Satellite Access |
LS out LS is reply to R3-247016/ S2-2410918 source LS: S2-2410918 LS To: SA2 |
Huawei, Jio Platforms, Ericsson | NR_NTN_Ph3-Core, 5GSAT_Ph3_ARCH | Rel-19 |
R3-129 AI: 15.2 |
available | [WTS] [JSN] | |
| R3-255549 | Downlink Transmission Suspend/Resume – Stage 2 TP |
other revised to R3-255750 |
Ericsson, Thales, Huawei, Jio Platforms, Airbus, ESA, Sateliot, Deutsche Telekom | IoT_NTN_Ph3-Core | Rel-19 |
R3-129 AI: 15.2 |
revised | [WTS] [JSN] | |
| R3-255607 | (TP to BLCR for TS 36.300) Left issues in IoT NTN | other | CATT | IoT_NTN_Ph3-Core | Rel-19 |
R3-129 AI: 15.2 |
available | [WTS] [JSN] | |
| R3-255747 | Response to R3-255513 | discussion | Nokia, Nokia Shanghai Bell, ZTE Corporation, Qualcomm, CATT, China Telecom, CMCC, Samsung | IoT_NTN_Ph3-Core | Rel-19 |
R3-129 AI: 15.2 |
available | [WTS] [JSN] | |
| R3-255748 | Response to R3-255514 | response | ZTE Corporation, Nokia, Nokia Shanghai Bell, Qualcomm, CATT, China Telecom, CMCC, Samsung | IoT_NTN_Ph3-Core | Rel-19 |
R3-129 AI: 15.2 |
available | [WTS] [JSN] | |
| R3-255750 | Downlink Transmission Suspend/Resume – Stage 2 TP |
other revision of R3-255549 revised to R3-255892 |
Ericsson, Thales, Huawei, Jio Platforms, Airbus, ESA, Sateliot, Deutsche Telekom | IoT_NTN_Ph3-Core | Rel-19 |
R3-129 AI: 15.2 |
revised | [WTS] [JSN] | |
| R3-255874 | SoD for CB: # 27_IoTNTN | discussion | ZTE Coroporation | IoT_NTN_Ph3-Core | Rel-19 |
R3-129 AI: 15.2 |
noted | [WTS] [JSN] | |
| R3-255892 | Removal of Downlink Transmission Suspend/Resume – Stage 2 TP |
other revision of R3-255750 |
Ericsson, Thales, Huawei, Jio Platforms, Airbus, ESA, Sateliot, Deutsche Telekom | IoT_NTN_Ph3-Core | Rel-19 |
R3-129 AI: 15.2 |
agreed | [WTS] [JSN] | |
| R3-255897 | (TP to BL CR for TS 36.300) Hard FLSO and MME management |
other revision of R3-255509 revised to R3-255950 |
Huawei, Ericsson, Thales, Jio Platforms, Deutsche Telekom | IoT_NTN_Ph3-Core | Rel-19 |
R3-129 AI: 15.2 |
revised | [WTS] [JSN] | |
| R3-255950 | (TP to BL CR for TS 36.300) Hard FLSO and MME management |
other revision of R3-255897 |
Huawei, Ericsson, Thales, Jio Platforms, Deutsche Telekom, LG Electronics Inc., ZTE | IoT_NTN_Ph3-Core | Rel-19 |
R3-129 AI: 15.2 |
agreed | [WTS] [JSN] |
26 documents (0.34742188453674 seconds)