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-2409365 | Frame structure and timing aspects for Ambient IoT | discussion | Nokia | FS_Ambient_IoT_solutions | Rel-19 |
R1-119 AI: 9.4.2.2 |
not treated | [WTS] [JSN] | |
| R1-2409389 | Frame structure and timing aspects for Ambient IoT | discussion | Ericsson | FS_Ambient_IoT_solutions | Rel-19 |
R1-119 AI: 9.4.2.2 |
not treated | [WTS] [JSN] | |
| R1-2409419 | On frame structure and timing aspects of Ambient IoT | discussion | Huawei, HiSilicon, CBN, China Broadnet | FS_Ambient_IoT_solutions | Rel-19 |
R1-119 AI: 9.4.2.2 |
not treated | [WTS] [JSN] | |
| R1-2409485 | Discussion on frame structure and physical layer procedures for Ambient IoT | discussion | Lenovo | FS_Ambient_IoT_solutions | Rel-19 |
R1-119 AI: 9.4.2.2 |
not treated | [WTS] [JSN] | |
| R1-2409514 | Discussion on frame structure and timing aspects for A-IoT | discussion | CMCC | FS_Ambient_IoT_solutions | Rel-19 |
R1-119 AI: 9.4.2.2 |
not treated | [WTS] [JSN] | |
| R1-2409553 | Discussion on frame structure and physical layer procedure for Ambient IoT | discussion | ZTE Corporation, Sanechips | FS_Ambient_IoT_solutions | Rel-19 |
R1-119 AI: 9.4.2.2 |
not treated | [WTS] [JSN] | |
| R1-2409599 | Considerations for frame structure and timing aspects | discussion | Samsung | FS_Ambient_IoT_solutions | Rel-19 |
R1-119 AI: 9.4.2.2 |
not treated | [WTS] [JSN] | |
| R1-2409638 | Discussion on frame structure and timing aspects for Ambient IoT | discussion | Spreadtrum, UNISOC | FS_Ambient_IoT_solutions | Rel-19 |
R1-119 AI: 9.4.2.2 |
not treated | [WTS] [JSN] | |
| R1-2409683 | Discussion on Frame structure, random access, scheduling and timing aspects for Ambient IoT | discussion | vivo | FS_Ambient_IoT_solutions | Rel-19 |
R1-119 AI: 9.4.2.2 |
not treated | [WTS] [JSN] | |
| R1-2409733 | Discussion on frame structure and timing aspects | discussion | InterDigital, Inc. | FS_Ambient_IoT_solutions | Rel-19 |
R1-119 AI: 9.4.2.2 |
not treated | [WTS] [JSN] | |
| R1-2409759 | Resource allocation and frame structure of A-IoT | discussion | Tejas Networks Limited | FS_Ambient_IoT_solutions | Rel-19 |
R1-119 AI: 9.4.2.2 |
not treated | [WTS] [JSN] | |
| R1-2409802 | On remaining frame structure and timing aspects for AIoT | discussion | Apple | FS_Ambient_IoT_solutions | Rel-19 |
R1-119 AI: 9.4.2.2 |
not treated | [WTS] [JSN] | |
| R1-2409865 | Discussion on frame structure and timing for ambient IoT | discussion | NEC | FS_Ambient_IoT_solutions | Rel-19 |
R1-119 AI: 9.4.2.2 |
not treated | [WTS] [JSN] | |
| R1-2409898 | Discussion on frame structure and timing aspects for Ambient IoT | discussion | Xiaomi | FS_Ambient_IoT_solutions | Rel-19 |
R1-119 AI: 9.4.2.2 |
not treated | [WTS] [JSN] | |
| R1-2409943 | Study of Frame structure and timing aspects for Ambient IoT | discussion | CATT | FS_Ambient_IoT_solutions | Rel-19 |
R1-119 AI: 9.4.2.2 |
not treated | [WTS] [JSN] | |
| R1-2410002 | Discussion on frame structure and timing aspects for Ambient IoT |
discussion revised to R1-2410647 |
China Telecom | FS_Ambient_IoT_solutions | Rel-19 |
R1-119 AI: 9.4.2.2 |
revised | [WTS] [JSN] | |
| R1-2410027 | Frame Structure and Timing Aspects for Ambient IoT | discussion | FUTUREWEI | FS_Ambient_IoT_solutions | Rel-19 |
R1-119 AI: 9.4.2.2 |
not treated | [WTS] [JSN] | |
| R1-2410060 | Discussion on frame structure and timing aspects | discussion | Fujitsu | FS_Ambient_IoT_solutions | Rel-19 |
R1-119 AI: 9.4.2.2 |
not treated | [WTS] [JSN] | |
| R1-2410063 | Discussion on A-IoT Frame Structure and Timing Aspects | discussion | Panasonic | FS_Ambient_IoT_solutions | Rel-19 |
R1-119 AI: 9.4.2.2 |
not treated | [WTS] [JSN] | |
| R1-2410093 | Discussion on frame structure and timing aspects of A-IoT communication | discussion | OPPO | FS_Ambient_IoT_solutions | Rel-19 |
R1-119 AI: 9.4.2.2 |
not treated | [WTS] [JSN] | |
| R1-2410166 | Discussion on frame structure and timing aspects | discussion | FS_Ambient_IoT_solutions | Rel-19 |
R1-119 AI: 9.4.2.2 |
not treated | [WTS] [JSN] | ||
| R1-2410179 | Discussion on frame structure and timing aspects for Ambient IoT | discussion | HONOR | FS_Ambient_IoT_solutions | Rel-19 |
R1-119 AI: 9.4.2.2 |
not treated | [WTS] [JSN] | |
| R1-2410226 | Frame structure and timing aspects of Ambient IoT | discussion | Sony | FS_Ambient_IoT_solutions | Rel-19 |
R1-119 AI: 9.4.2.2 |
not treated | [WTS] [JSN] | |
| R1-2410268 | Discussion on frame structure and timing aspects | discussion | ETRI | FS_Ambient_IoT_solutions | Rel-19 |
R1-119 AI: 9.4.2.2 |
not treated | [WTS] [JSN] | |
| R1-2410288 | Frame structure and timing aspects for Ambient IoT | discussion | LG Electronics | FS_Ambient_IoT_solutions | Rel-19 |
R1-119 AI: 9.4.2.2 |
not treated | [WTS] [JSN] | |
| R1-2410356 | Discussion on frame structure and timing aspects for Ambient IoT | discussion | TCL | FS_Ambient_IoT_solutions | Rel-19 |
R1-119 AI: 9.4.2.2 |
not treated | [WTS] [JSN] | |
| R1-2410391 | Study on frame structure and timing aspects for Ambient IoT | discussion | NTT DOCOMO, INC. | FS_Ambient_IoT_solutions | Rel-19 |
R1-119 AI: 9.4.2.2 |
not treated | [WTS] [JSN] | |
| R1-2410409 | Discussion on frame structure and timing aspect |
discussion revision of R1-2408763 |
ASUSTeK | FS_Ambient_IoT_solutions | Rel-19 |
R1-119 AI: 9.4.2.2 |
not treated | [WTS] [JSN] | |
| R1-2410417 | Discussion on frame structure and timing aspects | discussion | Sharp | FS_Ambient_IoT_solutions | Rel-19 |
R1-119 AI: 9.4.2.2 |
not treated | [WTS] [JSN] | |
| R1-2410480 | Frame structure and timing aspects | discussion | Qualcomm Incorporated | FS_Ambient_IoT_solutions | Rel-19 |
R1-119 AI: 9.4.2.2 |
not treated | [WTS] [JSN] | |
| R1-2410516 | Frame structure and timing aspects | discussion | MediaTek Inc. | FS_Ambient_IoT_solutions | Rel-19 |
R1-119 AI: 9.4.2.2 |
not treated | [WTS] [JSN] | |
| R1-2410560 | Discussion on frame structure and timing aspects for Ambient IoT | discussion | WILUS Inc. | FS_Ambient_IoT_solutions | Rel-19 |
R1-119 AI: 9.4.2.2 |
not treated | [WTS] [JSN] | |
| R1-2410578 | Discussion on Frame structure and timing aspects | discussion | CEWiT | FS_Ambient_IoT_solutions | Rel-19 |
R1-119 AI: 9.4.2.2 |
not treated | [WTS] [JSN] | |
| R1-2410592 | Frame structure and timing aspects of AIoT | discussion | IIT Kanpur, Indian Institute of Tech (M) | FS_Ambient_IoT_solutions | Rel-19 |
R1-119 AI: 9.4.2.2 |
not treated | [WTS] [JSN] | |
| R1-2410643 | FL summary #1 on frame structure and timing aspects for Rel-19 Ambient IoT | discussion | Moderator (vivo) | FS_Ambient_IoT_solutions | Rel-19 |
R1-119 AI: 9.4.2.2 |
noted | [WTS] [JSN] | |
| R1-2410644 | FL summary #2 on frame structure and timing aspects for Rel-19 Ambient IoT | discussion | Moderator (vivo) | FS_Ambient_IoT_solutions | Rel-19 |
R1-119 AI: 9.4.2.2 |
noted | [WTS] [JSN] | |
| R1-2410645 | FL summary #3 on frame structure and timing aspects for Rel-19 Ambient IoT | discussion | Moderator (vivo) | FS_Ambient_IoT_solutions | Rel-19 |
R1-119 AI: 9.4.2.2 |
noted | [WTS] [JSN] | |
| R1-2410647 | Discussion on frame structure and timing aspects for Ambient IoT |
discussion revision of R1-2410002 |
China Telecom | FS_Ambient_IoT_solutions | Rel-19 |
R1-119 AI: 9.4.2.2 |
not treated | [WTS] [JSN] | |
| R1-2410653 | TP updates on section 6.2 Device (un)availability for TR 38.769 | discussion | Moderator (vivo) | FS_Ambient_IoT_solutions | Rel-19 |
R1-119 AI: 9.4.2.2 |
noted | [WTS] [JSN] | |
| R1-2410866 | Final FL summary on frame structure and timing aspects for Rel-19 Ambient IoT | discussion | Moderator (vivo) | FS_Ambient_IoT_solutions | Rel-19 |
R1-119 AI: 9.4.2.2 |
noted | [WTS] [JSN] |
40 documents (0.35968399047852 seconds)