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 |
---|---|---|---|---|---|---|---|---|---|
R2-2209451 | Discussion on PDU prioritization | discussion | Qualcomm Incorporated | FS_NR_XR_enh | Rel-18 |
R2-119-bis-e AI: 8.5.2.2 |
available | [WTS] [JSN] | |
R2-2209468 | Prioritization of XR traffic | discussion | CATT | FS_NR_XR_enh | Rel-18 |
R2-119-bis-e AI: 8.5.2.2 |
available | [WTS] [JSN] | |
R2-2209486 | Discussion on PDU prioritization for XR awareness |
discussion revised to R2-2211492 |
vivo | FS_NR_XR_enh | Rel-18 |
R2-119-bis-e AI: 8.5.2.2 |
available | [WTS] [JSN] | |
R2-2209556 | LCP Impacts for XR | discussion | Nokia, Nokia Shanghai Bell | FS_NR_XR_enh | Rel-18 |
R2-119-bis-e AI: 8.5.2.2 |
available | [WTS] [JSN] | |
R2-2209632 | Handling and in-sequence delivery of XR packets with different priorities | discussion | Intel Corporation | FS_NR_XR_enh | Rel-18 |
R2-119-bis-e AI: 8.5.2.2 |
available | [WTS] [JSN] | |
R2-2209646 | PDU-set prioritization for XR | discussion | ZTE Corporation, Sanechips |
R2-119-bis-e AI: 8.5.2.2 |
available | [WTS] [JSN] | |||
R2-2209687 | Discussion on PDU prioritization | discussion | InterDigital, Inc. | FS_NR_XR_enh | Rel-18 |
R2-119-bis-e AI: 8.5.2.2 |
available | [WTS] [JSN] | |
R2-2209778 | Enhancements for Traffic Prioritization in XR | discussion | Apple | FS_NR_XR_enh | Rel-18 |
R2-119-bis-e AI: 8.5.2.2 |
available | [WTS] [JSN] | |
R2-2209889 | Discussion on PDU prioritization | discussion | Lenovo | FS_NR_XR_enh | Rel-18 |
R2-119-bis-e AI: 8.5.2.2 |
available | [WTS] [JSN] | |
R2-2209990 | Some LCP enhancements based on the traffic awareness | discussion | Spreadtrum Communications | Rel-18 |
R2-119-bis-e AI: 8.5.2.2 |
available | [WTS] [JSN] | ||
R2-2210013 | Discussion on LCP impact |
discussion revised to R2-2212205 |
Samsung | FS_NR_XR_enh | Rel-18 |
R2-119-bis-e AI: 8.5.2.2 |
available | [WTS] [JSN] | |
R2-2210022 | Discussion on PDU prioritization | discussion | OPPO | FS_NR_XR_enh | Rel-18 |
R2-119-bis-e AI: 8.5.2.2 |
available | [WTS] [JSN] | |
R2-2210046 | Discussion on the LCP enhancements for XR | discussion | ITRI | FS_NR_XR_enh |
R2-119-bis-e AI: 8.5.2.2 |
available | [WTS] [JSN] | ||
R2-2210202 | Discussion about XR-awareness impacts on LCP | discussion | Huawei, HiSilicon | FS_NR_XR_enh | Rel-18 |
R2-119-bis-e AI: 8.5.2.2 |
available | [WTS] [JSN] | |
R2-2210361 | Discussion on PDU prioritization | discussion | Google Inc. |
R2-119-bis-e AI: 8.5.2.2 |
available | [WTS] [JSN] | |||
R2-2210507 | Impact on PDU Prioritization by XR Awareness | discussion | CMCC | FS_NR_XR_enh | Rel-18 |
R2-119-bis-e AI: 8.5.2.2 |
available | [WTS] [JSN] | |
R2-2210536 | Discussion on traffic prioritization of XR traffic | discussion | Beijing Xiaomi Mobile Software |
R2-119-bis-e AI: 8.5.2.2 |
available | [WTS] [JSN] | |||
R2-2210560 | Discussion on the prioritization for XR | discussion | LG Electronics Inc. | FS_NR_XR_enh |
R2-119-bis-e AI: 8.5.2.2 |
available | [WTS] [JSN] | ||
R2-2210620 | Discussion on PDU prioritization for XR-awareness | discussion | III | FS_NR_XR_enh |
R2-119-bis-e AI: 8.5.2.2 |
available | [WTS] [JSN] | ||
R2-2210649 | On PDU prioritisation | discussion | MediaTek Inc. | FS_NR_XR_enh | Rel-18 |
R2-119-bis-e AI: 8.5.2.2 |
noted | [WTS] [JSN] | |
R2-2210688 | Discussion on PDU Prioritization | discussion | Ericsson | FS_NR_XR_enh | Rel-18 |
R2-119-bis-e AI: 8.5.2.2 |
available | [WTS] [JSN] |
21 documents (0.32948303222656 seconds)