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-2403843 | Frame structure and timing aspects for Ambient IoT | discussion | Ericsson | FS_Ambient_IoT_solutions | Rel-19 |
R1-117 AI: 9.4.2.2 |
not treated | [WTS] [JSN] | |
R1-2403861 | Frame Structure and Timing Aspects for Ambient IoT | discussion | FUTUREWEI | FS_Ambient_IoT_solutions | Rel-19 |
R1-117 AI: 9.4.2.2 |
not treated | [WTS] [JSN] | |
R1-2403889 | Frame structure and timing aspects for Ambient IoT | discussion | Nokia | FS_Ambient_IoT_solutions | Rel-19 |
R1-117 AI: 9.4.2.2 |
not treated | [WTS] [JSN] | |
R1-2403955 | On frame structure and timing aspects of Ambient IoT | discussion | Huawei, HiSilicon | FS_Ambient_IoT_solutions | Rel-19 |
R1-117 AI: 9.4.2.2 |
not treated | [WTS] [JSN] | |
R1-2403966 | Discussions on frame structure and timing aspects for A-IoT | discussion | Intel Corporation | FS_Ambient_IoT_solutions | Rel-19 |
R1-117 AI: 9.4.2.2 |
not treated | [WTS] [JSN] | |
R1-2404029 | Discussion on frame structure and timing aspects for Ambient IoT | discussion | Spreadtrum Communications | FS_Ambient_IoT_solutions | Rel-19 |
R1-117 AI: 9.4.2.2 |
not treated | [WTS] [JSN] | |
R1-2404118 | Considerations for frame structure and timing aspects | discussion | Samsung | FS_Ambient_IoT_solutions | Rel-19 |
R1-117 AI: 9.4.2.2 |
not treated | [WTS] [JSN] | |
R1-2404180 | Discussion on Frame structure, random access, scheduling and timing aspects | discussion | vivo | FS_Ambient_IoT_solutions | Rel-19 |
R1-117 AI: 9.4.2.2 |
not treated | [WTS] [JSN] | |
R1-2404219 | Discussion on frame structure and physical layer procedures for Ambient IoT | discussion | Lenovo | FS_Ambient_IoT_solutions | Rel-19 |
R1-117 AI: 9.4.2.2 |
not treated | [WTS] [JSN] | |
R1-2404287 | Frame structure and timing aspects for Ambient IoT | discussion | Apple | FS_Ambient_IoT_solutions | Rel-19 |
R1-117 AI: 9.4.2.2 |
not treated | [WTS] [JSN] | |
R1-2404329 | Discussion on frame structure and timing aspects for Ambient IoT | discussion | TCL | FS_Ambient_IoT_solutions | Rel-19 |
R1-117 AI: 9.4.2.2 |
not treated | [WTS] [JSN] | |
R1-2404404 | Study of Frame structure and timing aspects for Ambient IoT | discussion | CATT | FS_Ambient_IoT_solutions | Rel-19 |
R1-117 AI: 9.4.2.2 |
not treated | [WTS] [JSN] | |
R1-2404430 | Discussion on frame structure and timing aspects for Ambient IoT | discussion | China Telecom | FS_Ambient_IoT_solutions | Rel-19 |
R1-117 AI: 9.4.2.2 |
not treated | [WTS] [JSN] | |
R1-2404459 | Discussion on frame structure and timing aspects for A-IoT | discussion | CMCC | FS_Ambient_IoT_solutions | Rel-19 |
R1-117 AI: 9.4.2.2 |
not treated | [WTS] [JSN] | |
R1-2404503 | Frame structure and timing aspects for Ambient IoT | discussion | Sony | FS_Ambient_IoT_solutions | Rel-19 |
R1-117 AI: 9.4.2.2 |
not treated | [WTS] [JSN] | |
R1-2404519 | Frame structure and timing aspects of Ambient IoT | discussion | InterDigital, Inc. | FS_Ambient_IoT_solutions | Rel-19 |
R1-117 AI: 9.4.2.2 |
not treated | [WTS] [JSN] | |
R1-2404557 | Discussion on frame structure and physical layer procedure for Ambient IoT | discussion | ZTE, Sanechips | FS_Ambient_IoT_solutions | Rel-19 |
R1-117 AI: 9.4.2.2 |
not treated | [WTS] [JSN] | |
R1-2404593 | Discussion on frame structure and timing aspects | discussion | Fujitsu | FS_Ambient_IoT_solutions | Rel-19 |
R1-117 AI: 9.4.2.2 |
not treated | [WTS] [JSN] | |
R1-2404596 | Discussion on A-IoT Frame Structure and Timing Aspects | discussion | Panasonic | FS_Ambient_IoT_solutions | Rel-19 |
R1-117 AI: 9.4.2.2 |
not treated | [WTS] [JSN] | |
R1-2404621 | Discussion on frame structure and timing aspects for Ambient IoT | discussion | Xiaomi | FS_Ambient_IoT_solutions | Rel-19 |
R1-117 AI: 9.4.2.2 |
not treated | [WTS] [JSN] | |
R1-2404675 | Discussion on frame structure and timing for ambient IoT | discussion | NEC | FS_Ambient_IoT_solutions | Rel-19 |
R1-117 AI: 9.4.2.2 |
not treated | [WTS] [JSN] | |
R1-2404734 | Discussion on frame structure and timing aspects for Ambient IoT | discussion | BUPT | FS_Ambient_IoT_solutions | Rel-19 |
R1-117 AI: 9.4.2.2 |
not treated | [WTS] [JSN] | |
R1-2404776 | Discussion on frame structure and timing aspects | discussion | ETRI | FS_Ambient_IoT_solutions | Rel-19 |
R1-117 AI: 9.4.2.2 |
not treated | [WTS] [JSN] | |
R1-2404798 | Some Considerations on Frame Structure and Timing Aspects for A-IoT | discussion | Continental Automotive | FS_Ambient_IoT_solutions | Rel-19 |
R1-117 AI: 9.4.2.2 |
not treated | [WTS] [JSN] | |
R1-2404803 | Discussion on Frame Structure and Timing Aspects for Ambient IoT | discussion | IIT, Kharagpur | FS_Ambient_IoT_solutions | Rel-19 |
R1-117 AI: 9.4.2.2 |
not treated | [WTS] [JSN] | |
R1-2404871 | Discussion on frame structure and timing aspects of A-IoT communication | discussion | OPPO | FS_Ambient_IoT_solutions | Rel-19 |
R1-117 AI: 9.4.2.2 |
not treated | [WTS] [JSN] | |
R1-2404891 | Frame structure and timing aspects for Ambient IoT | discussion | LG Electronics | FS_Ambient_IoT_solutions | Rel-19 |
R1-117 AI: 9.4.2.2 |
not treated | [WTS] [JSN] | |
R1-2404963 | Discussion on frame structure and timing aspects | discussion | Sharp | FS_Ambient_IoT_solutions | Rel-19 |
R1-117 AI: 9.4.2.2 |
not treated | [WTS] [JSN] | |
R1-2405045 | Study on frame structure and timing aspects for Ambient IoT | discussion | NTT DOCOMO, INC. | FS_Ambient_IoT_solutions | Rel-19 |
R1-117 AI: 9.4.2.2 |
not treated | [WTS] [JSN] | |
R1-2405079 | Frame structure and timing aspects | discussion | MediaTek Inc. | FS_Ambient_IoT_solutions | Rel-19 |
R1-117 AI: 9.4.2.2 |
not treated | [WTS] [JSN] | |
R1-2405158 | Frame structure and timing aspects | discussion | Qualcomm Incorporated | FS_Ambient_IoT_solutions | Rel-19 |
R1-117 AI: 9.4.2.2 |
not treated | [WTS] [JSN] | |
R1-2405181 | Discussion on Frame structure and timing aspects for A-IoT | discussion | Unicompay | FS_Ambient_IoT_solutions | Rel-19 |
R1-117 AI: 9.4.2.2 |
withdrawn | [WTS] [JSN] | |
R1-2405183 | Discussion on Frame structure and timing aspects for A-IoT | discussion | China Unicom | FS_Ambient_IoT_solutions | Rel-19 |
R1-117 AI: 9.4.2.2 |
not treated | [WTS] [JSN] | |
R1-2405208 | Discussion on frame structure and timing aspect | discussion | ASUSTeK | FS_Ambient_IoT_solutions | Rel-19 |
R1-117 AI: 9.4.2.2 |
not treated | [WTS] [JSN] | |
R1-2405217 | Discussion on frame structure and timing aspects for Ambient IoT | discussion | Comba | FS_Ambient_IoT_solutions | Rel-19 |
R1-117 AI: 9.4.2.2 |
not treated | [WTS] [JSN] | |
R1-2405243 | Discussion on Frame structure and timing aspects | discussion | CEWiT | FS_Ambient_IoT_solutions | Rel-19 |
R1-117 AI: 9.4.2.2 |
not treated | [WTS] [JSN] | |
R1-2405273 | Discussion on frame structure and timing aspects | discussion | FS_Ambient_IoT_solutions | Rel-19 |
R1-117 AI: 9.4.2.2 |
not treated | [WTS] [JSN] | ||
R1-2405299 | Frame structure and timing aspects for AIoT | discussion | IIT Kanpur, Indian Institute of Tech (M) | FS_Ambient_IoT_solutions | Rel-19 |
R1-117 AI: 9.4.2.2 |
withdrawn | [WTS] [JSN] | |
R1-2405379 | FL summary #1 on frame structure and timing aspects for Rel-19 Ambient IoT | discussion | Moderator (vivo) | FS_Ambient_IoT_solutions | Rel-19 |
R1-117 AI: 9.4.2.2 |
noted | [WTS] [JSN] | |
R1-2405380 | FL summary #2 on frame structure and timing aspects for Rel-19 Ambient IoT | discussion | Moderator (vivo) | FS_Ambient_IoT_solutions | Rel-19 |
R1-117 AI: 9.4.2.2 |
noted | [WTS] [JSN] | |
R1-2405381 | FL summary #3 on frame structure and timing aspects for Rel-19 Ambient IoT | discussion | Moderator (vivo) | FS_Ambient_IoT_solutions | Rel-19 |
R1-117 AI: 9.4.2.2 |
noted | [WTS] [JSN] |
41 documents (0.32851004600525 seconds)