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-1911856 | Resource multiplexing between backhaul and access in IAB | other | Huawei, HiSilicon |
R1-99 AI: 7.2.3.1 |
not treated | [WTS] [JSN] | |||
| R1-1912019 | Discussion on resource multiplexing among backhaul and access links | discussion | vivo | Rel-16 |
R1-99 AI: 7.2.3.1 |
not treated | [WTS] [JSN] | ||
| R1-1912133 | Remaining issues on IAN resource configuration and multiplexing | discussion | Ericsson |
R1-99 AI: 7.2.3.1 |
not treated | [WTS] [JSN] | |||
| R1-1912202 | Mechanisms for resource multiplexing among backhaul and access links | discussion | Intel Corporation | Rel-16 |
R1-99 AI: 7.2.3.1 |
not treated | [WTS] [JSN] | ||
| R1-1912265 | Discussions on resource multiplexing among backhaul and access links | discussion | LG Electronics |
R1-99 AI: 7.2.3.1 |
not treated | [WTS] [JSN] | |||
| R1-1912296 | Resource multiplexing between backhaul and access links | discussion | ZTE, Sanechips |
R1-99 AI: 7.2.3.1 |
not treated | [WTS] [JSN] | |||
| R1-1912321 | Remaining issues on resource partitioning for IAB network | discussion | Lenovo, Motorola Mobility |
R1-99 AI: 7.2.3.1 |
not treated | [WTS] [JSN] | |||
| R1-1912455 | Resource Multiplexing between Backhaul and Access Links | discussion | Samsung |
R1-99 AI: 7.2.3.1 |
not treated | [WTS] [JSN] | |||
| R1-1912533 | Discussion on resource multiplexing among backhaul and access links |
discussion revision of R1-1910162 |
CMCC |
R1-99 AI: 7.2.3.1 |
not treated | [WTS] [JSN] | |||
| R1-1912716 | Mechanisms for resource multiplexing among backhaul and access links | discussion | Nokia, Nokia Shanghai Bell | Rel-16 |
R1-99 AI: 7.2.3.1 |
not treated | [WTS] [JSN] | ||
| R1-1912838 | Mechanisms for supporting access and backhaul link multiplexing | discussion | AT&T |
R1-99 AI: 7.2.3.1 |
not treated | [WTS] [JSN] | |||
| R1-1912879 | Mechanisms for resource multiplexing among backhaul and access links | discussion | NTT DOCOMO, INC. | Rel-16 |
R1-99 AI: 7.2.3.1 |
not treated | [WTS] [JSN] | ||
| R1-1912943 | Remaining issues on IAB resource management | discussion | Qualcomm Incorporated | NR_IAB-Core | Rel-16 |
R1-99 AI: 7.2.3.1 |
not treated | [WTS] [JSN] | |
| R1-1913094 | Discussions on resource multiplexing among backhaul and access links | discussion | CEWiT |
R1-99 AI: 7.2.3.1 |
not treated | [WTS] [JSN] | |||
| R1-1913321 | Summary #1 of 7.2.3.1 – Mechanisms for resource multiplexing among backhaul and access links |
discussion revised to R1-1913408 |
AT&T | NR_IAB-Core | Rel-16 |
R1-99 AI: 7.2.3.1 |
noted | [WTS] [JSN] | |
| R1-1913408 | Summary #2 of 7.2.3.1 – Mechanisms for resource multiplexing among backhaul and access links |
discussion revision of R1-1913321 revised to R1-1913438 |
AT&T | NR_IAB-Core | Rel-16 |
R1-99 AI: 7.2.3.1 |
revised | [WTS] [JSN] | |
| R1-1913438 | Summary #2 of 7.2.3.1 – Mechanisms for resource multiplexing among backhaul and access links |
discussion revision of R1-1913408 revised to R1-1913503 |
AT&T | NR_IAB-Core | Rel-16 |
R1-99 AI: 7.2.3.1 |
revised | [WTS] [JSN] | |
| R1-1913503 | Summary #3 of 7.2.3.1 – Mechanisms for resource multiplexing among backhaul and access links |
discussion revision of R1-1913438 |
AT&T | NR_IAB-Core | Rel-16 |
R1-99 AI: 7.2.3.1 |
noted | [WTS] [JSN] |
18 documents (0.34536695480347 seconds)