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-1905974 | Segmentation awareness in UE and Network |
discussion revision of R2-1904884 |
vivo | FS_RACS_RAN | Rel-16 |
R2-106 AI: 11.5.3 |
not treated | [WTS] [JSN] | |
| R2-1906030 | RRC segmentation for transfer of UE capability | discussion | MediaTek Inc. | Rel-16 |
R2-106 AI: 11.5.3 |
not treated | [WTS] [JSN] | ||
| R2-1906264 | Segementation of UE capability information | discussion | ZTE Corporation, Sanechips | RACS-RAN-Core | Rel-16 |
R2-106 AI: 11.5.3 |
noted | [WTS] [JSN] | |
| R2-1906346 | Implementation aspects of UL Capability Segmentation |
discussion revision of R2-1904462 |
Intel Corporation | RACS-RAN-Core | Rel-16 |
R2-106 AI: 11.5.3 |
not treated | [WTS] [JSN] | |
| R2-1906452 | Consideration on Segmentation in RRC | discussion | CATT | RACS-RAN-Core | Rel-16 |
R2-106 AI: 11.5.3 |
not treated | [WTS] [JSN] | |
| R2-1907220 | Processing time for UE capability in case of RRC segmentation |
discussion revised to R2-1910727 |
Huawei Technologies Co. Ltd. | RACS-RAN-Core | Rel-16 |
R2-106 AI: 11.5.3 |
not treated | [WTS] [JSN] | |
| R2-1907325 | Segmentation in DL | discussion | Ericsson, Deutsche Telekom | RACS-RAN-Core | Rel-16 |
R2-106 AI: 11.5.3 |
not treated | [WTS] [JSN] | |
| R2-1907327 | Introduction of RRC Segmentation - Downlink (38.331) | draftCR | Ericsson | RACS-RAN-Core | Rel-16 |
R2-106 AI: 11.5.3 |
not treated | [WTS] [JSN] | |
| R2-1907328 | Introduction of RRC segmentation - Uplink (38.331) | draftCR | Ericsson | RACS-RAN-Core | Rel-16 |
R2-106 AI: 11.5.3 |
not treated | [WTS] [JSN] | |
| R2-1907329 | RRC segmentation and max UE capability information size | discussion | Ericsson | RACS-RAN-Core | Rel-16 |
R2-106 AI: 11.5.3 |
not treated | [WTS] [JSN] | |
| R2-1907330 | Introduction of RRC segmentation for RRC Resume and RRC reconfiguration (38.306) | draftCR | Ericsson | RACS-RAN-Core | Rel-16 |
R2-106 AI: 11.5.3 |
not treated | [WTS] [JSN] | |
| R2-1907569 | Remaining issues on UE capability segmentation |
discussion revision of R2-1904813 revised to R2-1911047 |
Huawei, HiSilicon | RACS-RAN-Core | Rel-16 |
R2-106 AI: 11.5.3 |
not treated | [WTS] [JSN] | |
| R2-1907570 | Signalling of supporting segmentation of UE capability |
discussion revision of R2-1904814 |
Huawei, HiSilicon | RACS-RAN-Core | Rel-16 |
R2-106 AI: 11.5.3 |
not treated | [WTS] [JSN] | |
| R2-1907571 | 36.331 Draft CR on RRC segmentation for UE capability information | draftCR | Huawei, HiSilicon | RACS-RAN-Core | Rel-16 |
R2-106 AI: 11.5.3 |
not treated | [WTS] [JSN] | |
| R2-1907572 | 38.331 Draft CR on RRC segmentation for UE capability information | draftCR | Huawei, HiSilicon | RACS-RAN-Core | Rel-16 |
R2-106 AI: 11.5.3 |
not treated | [WTS] [JSN] | |
| R2-1907721 | SRB Type for the segmented UECapabilityInformation |
discussion revised to R2-1911355 |
Samsung | RACS-RAN-Core | Rel-16 |
R2-106 AI: 11.5.3 |
not treated | [WTS] [JSN] |
16 documents (0.35868906974792 seconds)