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-2002604 | Open aspects on mode 2 operation | discussion | Intel Corporation | 5G_V2X_NRSL-Core | Rel-16 |
R2-ah-38104 AI: 6.4.2.2 |
not treated | [WTS] [JSN] | |
| R2-2002638 | Summary of [Post109e#20] V2X Remaining UE capability issues (OPPO) | report | OPPO | 5G_V2X_NRSL-Core | Rel-16 |
R2-ah-38104 AI: 6.4.2.2 |
noted | [WTS] [JSN] | |
| R2-2002639 | Summary of capability related Tdoc submitted to R2#109bis-E | report | OPPO |
R2-ah-38104 AI: 6.4.2.2 |
noted | [WTS] [JSN] | |||
| R2-2002661 | Further issues on the mismatch of UE capabilities in unicast sidelink | discussion | Nokia, Nokia Shanghai Bell | 5G_V2X_NRSL-Core | Rel-16 |
R2-ah-38104 AI: 6.4.2.2 |
not treated | [WTS] [JSN] | |
| R2-2002771 | Remaining Issues on NR V2X Resource Allocation for Zone Configuration | discussion | ITRI | 5G_V2X_NRSL-Core |
R2-ah-38104 AI: 6.4.2.2 |
not treated | [WTS] [JSN] | ||
| R2-2002808 | Discussion on Interoperability of V2X UEs camped in different cells |
discussion revised to R2-2005530 |
Apple | 5G_V2X_NRSL-Core |
R2-ah-38104 AI: 6.4.2.2 |
not treated | [WTS] [JSN] | ||
| R2-2002829 | Discussion on inter-RAT Cell Selection/Reselection | discussion | CATT | 5G_V2X_NRSL-Core | Rel-16 |
R2-ah-38104 AI: 6.4.2.2 |
not treated | [WTS] [JSN] | |
| R2-2002830 | Introduce a new IE in SIB1 to indicate the anchor frequency only | draftCR | CATT | 5G_V2X_NRSL-Core | Rel-16 |
R2-ah-38104 AI: 6.4.2.2 |
not treated | [WTS] [JSN] | |
| R2-2002859 | Left issues on UE capability for NR V2X | discussion | LG Electronics France | 5G_V2X_NRSL-Core | Rel-16 |
R2-ah-38104 AI: 6.4.2.2 |
not treated | [WTS] [JSN] | |
| R2-2003097 | Remaining issues of cell (re)selection for NR V2X | discussion | Lenovo, Motorola Mobility | Rel-16 |
R2-ah-38104 AI: 6.4.2.2 |
not treated | [WTS] [JSN] | ||
| R2-2003214 | UE capability left issue for NR V2X | discussion | Ericsson | 5G_V2X_NRSL-Core | Rel-16 |
R2-ah-38104 AI: 6.4.2.2 |
not treated | [WTS] [JSN] | |
| R2-2003366 | Remaining issue on RRC state transition for groupcast | discussion | ITRI | 5G_V2X_NRSL-Core |
R2-ah-38104 AI: 6.4.2.2 |
not treated | [WTS] [JSN] | ||
| R2-2003515 | Remaining issues on cell reselection for sidelink in TS 38.304 | discussion | Huawei, HiSilicon |
R2-ah-38104 AI: 6.4.2.2 |
not treated | [WTS] [JSN] | |||
| R2-2003516 | Draft CR to TS 38.304 on cell (re)selection for sidelink | draftCR | Huawei, HiSilicon | 5G_V2X_NRSL | Rel-16 |
R2-ah-38104 AI: 6.4.2.2 |
not treated | [WTS] [JSN] | |
| R2-2003603 | Clarification on cell reselection | draftCR | CATT | 5G_V2X_NRSL-Core | Rel-16 |
R2-ah-38104 AI: 6.4.2.2 |
not treated | [WTS] [JSN] | |
| R2-2003721 | Further discussion on cell reselection for V2X | discussion | Samsung Electronics Co., Ltd | 5G_V2X_NRSL-Core | Rel-16 |
R2-ah-38104 AI: 6.4.2.2 |
not treated | [WTS] [JSN] | |
| R2-2003756 | Correction on cell reselection for V2X | CR | Samsung Electronics Co., Ltd | 38.331 16.0.0 CR#1585 catF | 5G_V2X_NRSL-Core | Rel-16 |
R2-ah-38104 AI: 6.4.2.2 |
not treated | [WTS] [JSN] |
| R2-2003779 | Summary of NR V2X cell (re-)selection | discussion | ZTE Corporation | 5G_V2X_NRSL-Core | Rel-16 |
R2-ah-38104 AI: 6.4.2.2 |
noted | [WTS] [JSN] | |
| R2-2004081 | LS on UE capability |
LS out LS To: RAN1 LS reply in R1-2004601 revised to R2-2004087 |
OPPO | 5G_V2X_NRSL | Rel-16 |
R2-ah-38104 AI: 6.4.2.2 |
revised | [WTS] [JSN] | |
| R2-2004087 | LS on UE capability |
LS out LS To: RAN1 revision of R2-2004081 |
RAN2 | 5G_V2X_NRSL | Rel-16 |
R2-ah-38104 AI: 6.4.2.2 |
approved | [WTS] [JSN] |
20 documents (0.3597469329834 seconds)