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 |
---|---|---|---|---|---|---|---|---|---|
R4-2218036 | FCC Part ยง25.202(f) discussion and implications on SEM, spurious emissions requirements and A-MPR for IoT NTN UE | discussion | Ligado Networks |
R4-105 AI: 9.5.5 |
noted | [WTS] [JSN] | |||
R4-2218376 | TS 36.102 v0.2.0 | draft TS | Mediatek India Technology Pvt. | LTE_NBIoT_eMTC_NTN_req-Core | Rel-18 |
R4-105 AI: 9.5.5 |
agreed | [WTS] [JSN] | |
R4-2218377 | TS 36.102 v0.3.0 | draft TS | Mediatek India Technology Pvt. | LTE_NBIoT_eMTC_NTN_req-Core | Rel-18 |
R4-105 AI: 9.5.5 |
agreed | [WTS] [JSN] | |
R4-2218421 | Discussion on UE RF requirements for IoT NTN | discussion | Mediatek India Technology Pvt. | LTE_NBIoT_eMTC_NTN_req-Core | Rel-18 |
R4-105 AI: 9.5.5 |
noted | [WTS] [JSN] | |
R4-2218767 | TP for IoT NTN RF requirement on ACS | other | Sony |
R4-105 AI: 9.5.5 |
approved | [WTS] [JSN] | |||
R4-2219039 | Discussion on UE spurious emission requirement for NB-iot/eMTC NTN | other | Xiaomi | LTE_NBIoT_eMTC_NTN_req-Core | Rel-18 |
R4-105 AI: 9.5.5 |
noted | [WTS] [JSN] | |
R4-2219040 | TP for TS 36.102 on spurious emission for NB-iot eMTC NTN | pCR | Xiaomi | 36.102 0.1.0 | LTE_NBIoT_eMTC_NTN_req-Core | Rel-18 |
R4-105 AI: 9.5.5 |
noted | [WTS] [JSN] |
R4-2219270 | Discussion on UE frequency error requirement for IoT NTN | other | Huawei, HiSilicon | LTE_NBIoT_eMTC_NTN_req-Core | Rel-18 |
R4-105 AI: 9.5.5 |
noted | [WTS] [JSN] | |
R4-2219370 | Further discussion on UE RF requirements for IoT over NTN | other | ZTE Corporation |
R4-105 AI: 9.5.5 |
noted | [WTS] [JSN] | |||
R4-2219371 | TP for TS 36.102: Clause 6.5.3 |
pCR revised to R4-2220802 |
ZTE Corporation | 36.102 0.1.0 | LTE_NBIoT_eMTC_NTN_req-Core | Rel-18 |
R4-105 AI: 9.5.5 |
revised | [WTS] [JSN] |
R4-2219475 | TP to TS 36.102 on MPR and A-MPR and discussion on emission requirements |
pCR revised to R4-2220803 |
Qualcomm Inc. | 36.102 0.2.0 | LTE_NBIoT_eMTC_NTN_req-Core | Rel-18 |
R4-105 AI: 9.5.5 |
revised | [WTS] [JSN] |
R4-2219788 | IoT UE RF remaining issues | discussion | Ericsson | LTE_NBIoT_eMTC_NTN_req-Core | Rel-18 |
R4-105 AI: 9.5.5 |
noted | [WTS] [JSN] | |
R4-2219789 | TP for UE RF requirement - Frequency error |
pCR revised to R4-2220804 |
Ericsson | 36.102 0.1.0 | LTE_NBIoT_eMTC_NTN_req-Core | Rel-18 |
R4-105 AI: 9.5.5 |
revised | [WTS] [JSN] |
R4-2219867 | TP on UE ACLR and SEM for IoT NTN |
pCR revised to R4-2220836 |
Huawei, HiSilicon | 36.102 0.1.0 | LTE_NBIoT_eMTC_NTN_req-Core | Rel-18 |
R4-105 AI: 9.5.5 |
revised | [WTS] [JSN] |
R4-2219878 | UE behaviour with mandatory frequency pre-compensation | other | Qualcomm Incorporated | LTE_NBIoT_eMTC_NTN_req-Core | Rel-18 |
R4-105 AI: 9.5.5 |
noted | [WTS] [JSN] | |
R4-2220023 | TP on TS36.102 Clause 2, 3 and 4 |
pCR revised to R4-2220828 |
MediaTek (Chengdu) Inc. | 36.102 0.2.0 | LTE_NBIoT_eMTC_NTN_req-Core | Rel-18 |
R4-105 AI: 9.5.5 |
revised | [WTS] [JSN] |
R4-2220028 | TP on suffix clause levels and other clarifications |
pCR revised to R4-2220805 |
MediaTek (Chengdu) Inc. | 36.102 0.2.0 | LTE_NBIoT_eMTC_NTN_req-Core | Rel-18 |
R4-105 AI: 9.5.5 |
revised | [WTS] [JSN] |
R4-2220046 | TP for 36.102 for NB frequency error |
pCR revised to R4-2220806 |
Qualcomm Incorporated | 36.102 0.1.0 | LTE_NBIoT_eMTC_NTN_req-Core | Rel-18 |
R4-105 AI: 9.5.5 |
revised | [WTS] [JSN] |
R4-2220802 | TP for TS 36.102: Clause 6.5.3 |
pCR revision of R4-2219371 revised to R4-2220835 |
ZTE Corporation | 36.102 0.1.0 | LTE_NBIoT_eMTC_NTN_req-Core | Rel-18 |
R4-105 AI: 9.5.5 |
revised | [WTS] [JSN] |
R4-2220803 | TP to TS 36.102 on MPR and A-MPR and discussion on emission requirements |
pCR revision of R4-2219475 |
Qualcomm Inc. | 36.102 0.2.0 | LTE_NBIoT_eMTC_NTN_req-Core | Rel-18 |
R4-105 AI: 9.5.5 |
approved | [WTS] [JSN] |
R4-2220804 | TP for UE RF requirement - Frequency error |
pCR revision of R4-2219789 |
Ericsson | 36.102 0.1.0 | LTE_NBIoT_eMTC_NTN_req-Core | Rel-18 |
R4-105 AI: 9.5.5 |
approved | [WTS] [JSN] |
R4-2220805 | TP on suffix clause levels and other clarifications |
pCR revision of R4-2220028 |
MediaTek (Chengdu) Inc. | 36.102 0.2.0 | LTE_NBIoT_eMTC_NTN_req-Core | Rel-18 |
R4-105 AI: 9.5.5 |
approved | [WTS] [JSN] |
R4-2220806 | TP for 36.102 for NB frequency error |
pCR revision of R4-2220046 |
Qualcomm Incorporated | 36.102 0.1.0 | LTE_NBIoT_eMTC_NTN_req-Core | Rel-18 |
R4-105 AI: 9.5.5 |
approved | [WTS] [JSN] |
R4-2220828 | TP on TS36.102 Clause 2, 3 and 4 |
pCR revision of R4-2220023 |
MediaTek (Chengdu) Inc. | 36.102 0.2.0 | LTE_NBIoT_eMTC_NTN_req-Core | Rel-18 |
R4-105 AI: 9.5.5 |
approved | [WTS] [JSN] |
R4-2220835 | TP for TS 36.102: Clause 6.5.3 |
pCR revision of R4-2220802 |
ZTE Corporation | 36.102 0.1.0 | LTE_NBIoT_eMTC_NTN_req-Core | Rel-18 |
R4-105 AI: 9.5.5 |
approved | [WTS] [JSN] |
R4-2220836 | TP on UE ACLR and SEM for IoT NTN |
pCR revision of R4-2219867 |
Huawei, HiSilicon | 36.102 0.1.0 | LTE_NBIoT_eMTC_NTN_req-Core | Rel-18 |
R4-105 AI: 9.5.5 |
approved | [WTS] [JSN] |
26 documents (0.32345199584961 seconds)