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 |
|---|---|---|---|---|---|---|---|---|---|
| R1-2500034 | Coding aspects for Ambient IoT | discussion | Ericsson | Ambient_IoT_Solutions-Core | Rel-19 |
R1-120 AI: 9.4.2 |
not treated | [WTS] [JSN] | |
| R1-2500045 | Discussion on coding aspects for A-IoT physical channel | discussion | FUTUREWEI | Ambient_IoT_Solutions-Core | Rel-19 |
R1-120 AI: 9.4.2 |
not treated | [WTS] [JSN] | |
| R1-2500125 | Discussion on Ambient IoTcoding |
discussion revised to R1-2501373 |
ZTE Corporation, Sanechips | Ambient_IoT_Solutions-Core | Rel-19 |
R1-120 AI: 9.4.2 |
not treated | [WTS] [JSN] | |
| R1-2500154 | Physical channel design on channel coding | discussion | Huawei, HiSilicon | Ambient_IoT_Solutions-Core | Rel-19 |
R1-120 AI: 9.4.2 |
not treated | [WTS] [JSN] | |
| R1-2500170 | Discussion on line coding, FEC, CRC, repetition aspects for Ambient IoT | discussion | Spreadtrum, UNISOC | Ambient_IoT_Solutions-Core | Rel-19 |
R1-120 AI: 9.4.2 |
not treated | [WTS] [JSN] | |
| R1-2500225 | Ambient IoT channel coding and small frequency shift | discussion | CATT | Ambient_IoT_Solutions-Core | Rel-19 |
R1-120 AI: 9.4.2 |
not treated | [WTS] [JSN] | |
| R1-2500260 | Discussion on physical channels design about line coding, FEC, CRC, repetition aspects for Ambient IoT | discussion | China Telecom | Ambient_IoT_Solutions-Core | Rel-19 |
R1-120 AI: 9.4.2 |
not treated | [WTS] [JSN] | |
| R1-2500288 | Discussion on coding aspects of physical channel design | discussion | CMCC | Ambient_IoT_Solutions-Core | Rel-19 |
R1-120 AI: 9.4.2 |
not treated | [WTS] [JSN] | |
| R1-2500350 | Discussion on line coding, FEC, CRC and repetition for A-IoT | discussion | vivo | Ambient_IoT_Solutions-Core | Rel-19 |
R1-120 AI: 9.4.2 |
not treated | [WTS] [JSN] | |
| R1-2500395 | AIoT Physical channels design - line coding, FEC, CRC, repetition aspects | discussion | Nokia | Ambient_IoT_Solutions-Core | Rel-19 |
R1-120 AI: 9.4.2 |
not treated | [WTS] [JSN] | |
| R1-2500425 | Discussion on other aspects for Ambient IoT physical design | discussion | TCL | Ambient_IoT_Solutions-Core | Rel-19 |
R1-120 AI: 9.4.2 |
not treated | [WTS] [JSN] | |
| R1-2500451 | Discussion on physical channels design for A-IoT | discussion | OPPO | Ambient_IoT_Solutions-Core | Rel-19 |
R1-120 AI: 9.4.2 |
not treated | [WTS] [JSN] | |
| R1-2500487 | Discussion on Physical Channel Designs for A-IoT | discussion | Panasonic | Ambient_IoT_Solutions-Core | Rel-19 |
R1-120 AI: 9.4.2 |
not treated | [WTS] [JSN] | |
| R1-2500611 | Physical layer design – line coding, FEC, CRC, repetition aspects | discussion | NEC | Ambient_IoT_Solutions-Core | Rel-19 |
R1-120 AI: 9.4.2 |
not treated | [WTS] [JSN] | |
| R1-2500733 | Discussion on line coding, FEC, CRC and repetition aspects for Ambient IoT | discussion | Xiaomi | Ambient_IoT_Solutions-Core | Rel-19 |
R1-120 AI: 9.4.2 |
not treated | [WTS] [JSN] | |
| R1-2500779 | On coding aspects for Ambient IoT | discussion | Apple | Ambient_IoT_Solutions-Core | Rel-19 |
R1-120 AI: 9.4.2 |
not treated | [WTS] [JSN] | |
| R1-2500851 | Views on Physical channels design – line coding, FEC, CRC, repetition aspects | discussion | Samsung | Ambient_IoT_Solutions-Core | Rel-19 |
R1-120 AI: 9.4.2 |
not treated | [WTS] [JSN] | |
| R1-2500894 | Discussion on general aspects of physical layer design of A-IoT | discussion | IIT, Kharagpur | Ambient_IoT_Solutions-Core | Rel-19 |
R1-120 AI: 9.4.2 |
withdrawn | [WTS] [JSN] | |
| R1-2500937 | Discussion on coding aspects | discussion | Fujitsu | Ambient_IoT_Solutions-Core | Rel-19 |
R1-120 AI: 9.4.2 |
not treated | [WTS] [JSN] | |
| R1-2500950 | A-IoT PHY layer design - line coding, FEC, CRC and repetition aspects | discussion | LG Electronics | Ambient_IoT_Solutions-Core | Rel-19 |
R1-120 AI: 9.4.2 |
not treated | [WTS] [JSN] | |
| R1-2501017 | A-IoT - PHY line coding, FEC, CRC, repetition aspects | discussion | MediaTek Inc. | Ambient_IoT_Solutions-Core | Rel-19 |
R1-120 AI: 9.4.2 |
not treated | [WTS] [JSN] | |
| R1-2501072 | Discussion on the Ambient IoT physical layer design aspects for Line coding, FEC, CRC, Repetition | discussion | Lenovo | Ambient_IoT_Solutions-Core | Rel-19 |
R1-120 AI: 9.4.2 |
not treated | [WTS] [JSN] | |
| R1-2501093 | Discussion on coding aspects | discussion | Sharp | Ambient_IoT_Solutions-Core | Rel-19 |
R1-120 AI: 9.4.2 |
not treated | [WTS] [JSN] | |
| R1-2501109 | Discussion on Physical channels design for Ambient IoT-other aspects | discussion | HONOR | Ambient_IoT_Solutions-Core | Rel-19 |
R1-120 AI: 9.4.2 |
not treated | [WTS] [JSN] | |
| R1-2501118 | Coding aspects of physical channel design for Ambient IoT | discussion | InterDigital, Inc. | Ambient_IoT_Solutions-Core | Rel-19 |
R1-120 AI: 9.4.2 |
not treated | [WTS] [JSN] | |
| R1-2501124 | Discussion on A-IoT Physical channels design |
discussion revised to R1-2502752 |
ASUSTeK | Ambient_IoT_Solutions-Core | Rel-19 |
R1-120 AI: 9.4.2 |
not treated | [WTS] [JSN] | |
| R1-2501157 | Physical channels design – line coding, FEC, CRC, repetition aspects | discussion | Qualcomm Incorporated | Ambient_IoT_Solutions-Core | Rel-19 |
R1-120 AI: 9.4.2 |
not treated | [WTS] [JSN] | |
| R1-2501203 | Discussion on coding and CRC aspects of physical channel design for Ambient IoT | discussion | NTT DOCOMO, INC. | Ambient_IoT_Solutions-Core | Rel-19 |
R1-120 AI: 9.4.2 |
not treated | [WTS] [JSN] | |
| R1-2501269 | Coding aspects for Ambient IoT | discussion | ITL | Ambient_IoT_Solutions-Core | Rel-19 |
R1-120 AI: 9.4.2 |
not treated | [WTS] [JSN] | |
| R1-2501311 | Discussion on other aspects of Phy design for AIoT | discussion | IIT Kanpur | Ambient_IoT_Solutions-Core | Rel-19 |
R1-120 AI: 9.4.2 |
not treated | [WTS] [JSN] | |
| R1-2501373 | Discussion on Ambient IoT coding |
discussion revision of R1-2500125 |
ZTE Corporation, Sanechips | Ambient_IoT_Solutions-Core | Rel-19 |
R1-120 AI: 9.4.2 |
not treated | [WTS] [JSN] | |
| R1-2501435 | Summary #1 for coding aspects of physical channel design | discussion | Moderator (CMCC) | FS_Ambient_IoT_solutions | Rel-19 |
R1-120 AI: 9.4.2 |
noted | [WTS] [JSN] | |
| R1-2501436 | Summary #2 for coding aspects of physical channel design | discussion | Moderator (CMCC) | FS_Ambient_IoT_solutions | Rel-19 |
R1-120 AI: 9.4.2 |
noted | [WTS] [JSN] | |
| R1-2501437 | Summary #3 for coding aspects of physical channel design | discussion | Moderator (CMCC) | FS_Ambient_IoT_solutions | Rel-19 |
R1-120 AI: 9.4.2 |
noted | [WTS] [JSN] | |
| R1-2501591 | Summary #4 for coding aspects of physical channel design |
discussion revised to R1-2501592 |
Moderator (CMCC) | FS_Ambient_IoT_solutions | Rel-19 |
R1-120 AI: 9.4.2 |
revised | [WTS] [JSN] | |
| R1-2501592 | Summary #5 for coding aspects of physical channel design |
discussion revision of R1-2501591 |
Moderator (CMCC) | FS_Ambient_IoT_solutions | Rel-19 |
R1-120 AI: 9.4.2 |
noted | [WTS] [JSN] | |
| R1-2501634 | Summary #6 for coding aspects of physical channel design (eom) | discussion | Moderator (CMCC) | FS_Ambient_IoT_solutions | Rel-19 |
R1-120 AI: 9.4.2 |
noted | [WTS] [JSN] | |
| R1-2501707 | Discussion on coding aspects for A-IoT physical channel | discussion | FUTUREWEI | Ambient_IoT_Solutions-Core | Rel-19 |
R1-120-bis AI: 9.4.2 |
not treated | [WTS] [JSN] | |
| R1-2501720 | Coding aspects for Ambient IoT | discussion | Ericsson | Ambient_IoT_Solutions-Core | Rel-19 |
R1-120-bis AI: 9.4.2 |
not treated | [WTS] [JSN] | |
| R1-2501734 | Discussion on other aspects for Ambient IoT physical design | discussion | TCL | Ambient_IoT_Solutions-Core | Rel-19 |
R1-120-bis AI: 9.4.2 |
not treated | [WTS] [JSN] | |
| R1-2501761 | Discussion on Ambient IoTcoding | discussion | ZTE Corporation, Sanechips | Ambient_IoT_Solutions-Core | Rel-19 |
R1-120-bis AI: 9.4.2 |
not treated | [WTS] [JSN] | |
| R1-2501777 | AIoT Physical channels design - line coding, FEC, CRC, repetition aspects | discussion | Nokia | Ambient_IoT_Solutions-Core | Rel-19 |
R1-120-bis AI: 9.4.2 |
not treated | [WTS] [JSN] | |
| R1-2501807 | Discussion on line coding, FEC, CRC and repetition for A-IoT | discussion | vivo | Ambient_IoT_Solutions-Core | Rel-19 |
R1-120-bis AI: 9.4.2 |
not treated | [WTS] [JSN] | |
| R1-2501869 | Discussion on line coding, FEC, CRC, repetition aspects for Ambient IoT | discussion | Spreadtrum, UNISOC | Ambient_IoT_Solutions-Core | Rel-19 |
R1-120-bis AI: 9.4.2 |
not treated | [WTS] [JSN] | |
| R1-2501993 | Ambient IoT channel coding and small frequency shift | discussion | CATT | Ambient_IoT_Solutions-Core | Rel-19 |
R1-120-bis AI: 9.4.2 |
not treated | [WTS] [JSN] | |
| R1-2502023 | Discussion on physical channels design about line coding, FEC, CRC, repetition aspects for Ambient IoT | discussion | China Telecom | Ambient_IoT_Solutions-Core | Rel-19 |
R1-120-bis AI: 9.4.2 |
not treated | [WTS] [JSN] | |
| R1-2502069 | Physical layer design – line coding, FEC, CRC, repetition aspects | discussion | NEC | Ambient_IoT_Solutions-Core | Rel-19 |
R1-120-bis AI: 9.4.2 |
not treated | [WTS] [JSN] | |
| R1-2502124 | Discussion on coding aspects | discussion | Fujitsu | Ambient_IoT_Solutions-Core | Rel-19 |
R1-120-bis AI: 9.4.2 |
not treated | [WTS] [JSN] | |
| R1-2502161 | Discussion on coding aspects of physical channel design | discussion | CMCC | Ambient_IoT_Solutions-Core | Rel-19 |
R1-120-bis AI: 9.4.2 |
not treated | [WTS] [JSN] | |
| R1-2502204 | Discussion on Physical Channel Designs for A-IoT | discussion | Panasonic | Ambient_IoT_Solutions-Core | Rel-19 |
R1-120-bis AI: 9.4.2 |
not treated | [WTS] [JSN] | |
| R1-2502234 | Physical channel design on channel coding | discussion | Huawei, HiSilicon | Ambient_IoT_Solutions-Core | Rel-19 |
R1-120-bis AI: 9.4.2 |
not treated | [WTS] [JSN] | |
| R1-2502274 | Discussion on physical channels design for A-IoT | discussion | OPPO | Ambient_IoT_Solutions-Core | Rel-19 |
R1-120-bis AI: 9.4.2 |
not treated | [WTS] [JSN] | |
| R1-2502369 | Views on Physical channels design – line coding, FEC, CRC, repetition aspects | discussion | Samsung | Ambient_IoT_Solutions-Core | Rel-19 |
R1-120-bis AI: 9.4.2 |
not treated | [WTS] [JSN] | |
| R1-2502442 | Discussion on line coding, FEC, CRC and repetition aspects for Ambient IoT | discussion | Xiaomi | Ambient_IoT_Solutions-Core | Rel-19 |
R1-120-bis AI: 9.4.2 |
not treated | [WTS] [JSN] | |
| R1-2502475 | A-IoT PHY layer design - line coding, FEC, CRC and repetition aspects | discussion | LG Electronics | Ambient_IoT_Solutions-Core | Rel-19 |
R1-120-bis AI: 9.4.2 |
not treated | [WTS] [JSN] | |
| R1-2502583 | Discussion on coding aspects of physical channel design for Ambient IoT | discussion | InterDigital Finland Oy | Ambient_IoT_Solutions-Core | Rel-19 |
R1-120-bis AI: 9.4.2 |
not treated | [WTS] [JSN] | |
| R1-2502606 | On coding aspects for Ambient IoT | discussion | Apple | Ambient_IoT_Solutions-Core | Rel-19 |
R1-120-bis AI: 9.4.2 |
not treated | [WTS] [JSN] | |
| R1-2502672 | Discussion on coding aspects | discussion | Sharp | Ambient_IoT_Solutions-Core | Rel-19 |
R1-120-bis AI: 9.4.2 |
not treated | [WTS] [JSN] | |
| R1-2502691 | Discussion on Physical channels design for Ambient IoT-other aspects | discussion | HONOR | Ambient_IoT_Solutions-Core | Rel-19 |
R1-120-bis AI: 9.4.2 |
not treated | [WTS] [JSN] | |
| R1-2502705 | A-IoT - PHY line coding, FEC, CRC, repetition aspects | discussion | MediaTek Inc. | Ambient_IoT_Solutions-Core | Rel-19 |
R1-120-bis AI: 9.4.2 |
not treated | [WTS] [JSN] | |
| R1-2502752 | Discussion on A-IoT Physical channels design |
discussion revision of R1-2501124 revised to R1-2504474 |
ASUSTeK | Ambient_IoT_Solutions-Core | Rel-19 |
R1-120-bis AI: 9.4.2 |
not treated | [WTS] [JSN] | |
| R1-2502767 | Discussion on coding and CRC aspects of physical channel design for Ambient IoT | discussion | NTT DOCOMO, INC. | Ambient_IoT_Solutions-Core | Rel-19 |
R1-120-bis AI: 9.4.2 |
not treated | [WTS] [JSN] | |
| R1-2502840 | Physical channels design – line coding, FEC, CRC, repetition aspects | discussion | Qualcomm Incorporated | Ambient_IoT_Solutions-Core | Rel-19 |
R1-120-bis AI: 9.4.2 |
not treated | [WTS] [JSN] | |
| R1-2502906 | Discussion on the Ambient IoT physical layer design aspects for Line coding, FEC, CRC, Repetition | discussion | Lenovo | Ambient_IoT_Solutions-Core | Rel-19 |
R1-120-bis AI: 9.4.2 |
not treated | [WTS] [JSN] | |
| R1-2502930 | Coding aspects for Ambient IoT | discussion | ITL | Ambient_IoT_Solutions-Core | Rel-19 |
R1-120-bis AI: 9.4.2 |
not treated | [WTS] [JSN] | |
| R1-2502939 | Discussion on other aspects of Phy design for AIoT | discussion | IIT Kanpur | Ambient_IoT_Solutions-Core | Rel-19 |
R1-120-bis AI: 9.4.2 |
withdrawn | [WTS] [JSN] | |
| R1-2503020 | Summary #1 for coding aspects of physical channel design | discussion | Moderator (CMCC) | Ambient_IoT_Solutions-Core | Rel-19 |
R1-120-bis AI: 9.4.2 |
noted | [WTS] [JSN] | |
| R1-2503021 | Summary #2 for coding aspects of physical channel design | discussion | Moderator (CMCC) | Ambient_IoT_Solutions-Core | Rel-19 |
R1-120-bis AI: 9.4.2 |
noted | [WTS] [JSN] | |
| R1-2503022 | Summary #3 for coding aspects of physical channel design | discussion | Moderator (CMCC) | Ambient_IoT_Solutions-Core | Rel-19 |
R1-120-bis AI: 9.4.2 |
noted | [WTS] [JSN] | |
| R1-2503023 | Summary #4 for coding aspects of physical channel design | discussion | Moderator (CMCC) | Ambient_IoT_Solutions-Core | Rel-19 |
R1-120-bis AI: 9.4.2 |
noted | [WTS] [JSN] | |
| R1-2503106 | Summary #5 for coding aspects of physical channel design | discussion | Moderator (CMCC) | Ambient_IoT_Solutions-Core | Rel-19 |
R1-120-bis AI: 9.4.2 |
noted | [WTS] [JSN] | |
| R1-2503107 | Summary #6 for coding aspects of physical channel design | discussion | Moderator (CMCC) | Ambient_IoT_Solutions-Core | Rel-19 |
R1-120-bis AI: 9.4.2 |
noted | [WTS] [JSN] |
72 documents (0.37949299812317 seconds)