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-1909943 | Reply LS on channel quality report in connected mode for NB-IoT |
LS in LS is reply to R1-1907624 source LS: R2-1911587 LS To: RAN1, RAN4 |
RAN2, Huawei | NB_IOTenh3-Core | Rel-16 |
R1-98 AI: 5 |
treated | [WTS] [JSN] | |
| R1-1909944 | LS on UL-SL prioritization |
LS in source LS: R2-1911679 LS To: RAN1, RAN4 |
RAN2, OPPO | 5G_V2X_NRSL-Core | Rel-16 |
R1-98 AI: 5 |
treated | [WTS] [JSN] | |
| R1-1909945 | LS to on NR V2X cross-RAT configuration |
LS in source LS: R2-1911680 LS To: RAN4 |
RAN2, CATT | 5G_V2X_NRSL-Core | Rel-16 |
R1-98 AI: 5 |
noted | [WTS] [JSN] | |
| R1-1909946 | Reply LS on SFTD measurement |
LS in LS is reply to R4-1907319 source LS: R2-1911700 LS To: RAN4 |
RAN2, Huawei | NR_newRAT-Core | Rel-15 |
R1-98 AI: 5 |
noted | [WTS] [JSN] | |
| R1-1909947 | Reply LS on physical layer data rate of RAN-assisted codec adaptation |
LS in LS is reply to R1-1907911 source LS: R2-1911785 LS To: SA4, RAN1 |
RAN2, Huawei | LTE_VoLTE_ViLTE_enh-S4, E2E_DELAY | Rel-16 |
R1-98 AI: 5 |
treated | [WTS] [JSN] | |
| R1-1909948 | LS on O-RAN Alliance & 3GPP Coordination on O-RAN Alliance Outputs |
LS in source LS: ORAN_3GPP_Liaison_Statement LS To: SA, CT, RAN, SA1, SA2, SA3, SA5, SA6, RAN1, RAN2, RAN3 |
O-RAN Alliance, AT&T, CMCC |
R1-98 AI: 5 |
treated | [WTS] [JSN] | |||
| R1-1909949 | LS on second SMTC periodicity in idle mode |
LS in source LS: R2-1911840 LS To: RAN4 |
RAN2, Orange | TEI16 | Rel-16 |
R1-98 AI: 5 |
treated | [WTS] [JSN] | |
| R1-1909950 | LS on the feasibility of Received Interference Power measurement |
LS in source LS: R2-1911846 LS To: RAN1 LS reply in R1-1912062 |
RAN2, Huawei | NR_SON_MDT-Core | Rel-16 |
R1-98 AI: 5 |
treated | [WTS] [JSN] | |
| R1-1909951 | LS on single PDCCH-based multi-TRP operation |
LS in source LS: R2-1911848 LS To: RAN1 LS reply in R1-1910866 |
RAN2, Samsung | NR_eMIMO-Core | Rel-16 |
R1-98 AI: 5 |
treated | [WTS] [JSN] | |
| R1-1909952 | Reply LS on CSI-RS configuration transfer |
LS in LS is reply to R3-192100 source LS: R2-1911855 LS To: RAN3 |
RAN2, ZTE | TEI16 | Rel-16 |
R1-98 AI: 5 |
noted | [WTS] [JSN] | |
| R1-1909953 | LS on ambiguity of UE L1 FDD/TDD FR1/FR2 capabilities |
LS in source LS: R2-1911858 LS To: RAN1 |
RAN2, ZTE | NR_newRAT-Core | Rel-15 |
R1-98 AI: 5 |
treated | [WTS] [JSN] | |
| R1-1909954 | LS on additional PDCCH monitoring occasions for paging for NR-U |
LS in source LS: R2-1911861 LS To: RAN1 |
RAN2, ZTE | NR_unlic-Core | Rel-16 |
R1-98 AI: 5 |
treated | [WTS] [JSN] | |
| R1-1909955 | LS to RAN1 on RAN2 agreements related to 2-step RACH |
LS in source LS: R2-1911862 LS To: RAN1 |
RAN2, CATT | NR_2step_RACH-Core | Rel-16 |
R1-98 AI: 5 |
treated | [WTS] [JSN] | |
| R1-1909956 | Reply LS on LS on maximum value of MDBV |
LS in LS is reply to S2-1907955 source LS: R2-1911864 LS To: SA2. RAN1, CT3, CT4 |
RAN2, Qualcomm | 5GS_Ph1 | Rel-16 |
R1-98 AI: 5 |
treated | [WTS] [JSN] | |
| R1-1909957 | Reply LS on LS on maximum value of MDBV |
LS in LS is reply to S2-1907955 source LS: R3-194553 LS To: SA2, RAN1, RAN2, CT3, CT4 |
RAN3, Qualcomm | 5GS_Ph1 | Rel-16 |
R1-98 AI: 5 |
treated | [WTS] [JSN] | |
| R1-1909958 | Reply LS on measurement gap for SRS-RSRP or CLI-RSSI measurements |
LS in source LS: R4-1908777 LS To: RAN2 |
RAN4, LG Electronics | NR_CLI_RIM-Core | Rel-16 |
R1-98 AI: 5 |
noted | [WTS] [JSN] | |
| R1-1909959 | Reply LS on RAN1/4 feature lists |
LS in LS is reply to R2-1908476 source LS: R4-1909845 LS To: RAN2 |
RAN4, Intel Corporation | NR_newRAT-Core | Rel-15 |
R1-98 AI: 5 |
noted | [WTS] [JSN] | |
| R1-1909960 | Reply LS on simultaneous RX/TX for NR |
LS in LS is reply to R2-1902745 source LS: R4-1909992 LS To: RAN1, RAN2 |
RAN4, Ericsson | NR_Mob_enh-Core | Rel-16 |
R1-98 AI: 5 |
treated | [WTS] [JSN] | |
| R1-1909961 | Reply LS on maximum allowed SCell activation delay for Rel16 CA |
LS in LS is reply to R1-1905901 source LS: R4-1909995 LS To: RAN1 |
RAN4, Nokia | LTE_NR_DC_CA_enh-Core | Rel-16 |
R1-98 AI: 5 |
treated | [WTS] [JSN] | |
| R1-1909962 | Reply LS on OTA timing alignment for IAB |
LS in LS is reply to R1-1903810, R1-1905842 source LS: R4-1909999 LS To: RAN1 |
RAN4, Samsung | NR_IAB-Core | Rel-16 |
R1-98 AI: 5 |
treated | [WTS] [JSN] | |
| R1-1909963 | Reply to LS on DL channel quality report for configured carrier in RRC connected mode |
LS in LS is reply to R2-1908262 source LS: R4-1910110 LS To: RAN2 |
RAN4, Qualcomm Incorporated | NB_IOTenh3-Core | Rel-16 |
R1-98 AI: 5 |
noted | [WTS] [JSN] | |
| R1-1909964 | LS on signalling measurement thresholds for validating the TA for PUR |
LS in source LS: R4-1910176 LS To: RAN2 |
RAN4, Ericsson | LTE_eMTC5-Core, NB_IOTenh3-Core | Rel-16 |
R1-98 AI: 5 |
noted | [WTS] [JSN] | |
| R1-1909965 | LS reply on supported BW for initial BWP |
LS in LS is reply to R2-1908301 source LS: R4-1910522 LS To: RAN2, RAN1 |
RAN4, Nokia | NR_newRAT-Core | Rel-15 |
R1-98 AI: 5 |
treated | [WTS] [JSN] | |
| R1-1909966 | LS on sidelink BWP reconfiguration on ITS band |
LS in source LS: R4-1910542 LS To: RAN1 |
RAN4, MediaTek | 5G_V2X_NRSL-Core | Rel-16 |
R1-98 AI: 5 |
treated | [WTS] [JSN] | |
| R1-1909967 | LS on RSSI definition |
LS in source LS: R4-1910573 LS To: RAN1 |
RAN4, MediaTek | NR_unlic-Core | Rel-16 |
R1-98 AI: 5 |
treated | [WTS] [JSN] | |
| R1-1909968 | Reply LS on NR fast Scell activation |
LS in LS is reply to R2-1908483 source LS: R4-1910574 LS To: RAN1, RAN2 |
RAN4, Huawei | LTE_NR_DC_CA_enh-Core | Rel-16 |
R1-98 AI: 5 |
treated | [WTS] [JSN] | |
| R1-1909969 | LS on SS-RSRPB definition |
LS in source LS: R4-1910610 LS To: RAN1 |
RAN4, Huawei | FS_NR_MIMO_OTA_test | Rel-16 |
R1-98 AI: 5 |
treated | [WTS] [JSN] | |
| R1-1909970 | Reply LS to LS on O-RAN Alliance & 3GPP Coordination on O-RAN Alliance Outputs |
LS in LS is reply to ORAN_3GPP_Liaison_Statement source LS: SP-190947 LS To: O-RAN Alliance |
SA, Intel |
R1-98 AI: 5 |
noted | [WTS] [JSN] | |||
| R1-1909979 | Draft Reply LS on additional PDCCH monitoring occasions for paging for NR-U |
LS out LS is reply to R2-1911861 LS To: RAN2 revised to R1-1911596 |
ZTE, Sanechips | NR_unlic-Core | Rel-16 |
R1-98 AI: 5 |
revised | [WTS] [JSN] | |
| R1-1909980 | Considerations on additional PDCCH monitoring occasions for paging for NR-U | discussion | ZTE, Sanechips | Rel-16 |
R1-98 AI: 5 |
not treated | [WTS] [JSN] | ||
| R1-1910113 | Draft response LS on ambiguity of UE L1 FDD&TDD FR1&FR2 capabilities | discussion | ZTE | Rel-15 |
R1-98 AI: 5 |
not treated | [WTS] [JSN] | ||
| R1-1910194 | Draft reply LS on mapping restriction for LCP procedure |
LS out LS is reply to R2-1908300 LS To: RAN2 |
vivo | 5G_V2X_NRSL-Core | Rel-16 |
R1-98 AI: 5 |
not treated | [WTS] [JSN] | |
| R1-1910303 | Draft reply LS on single PDCCH-based multi-TRP operation |
LS out LS is reply to R2-1911848 LS To: RAN2 |
ZTE | NR_eMIMO-Core | Rel-16 |
R1-98 AI: 5 |
not treated | [WTS] [JSN] | |
| R1-1910304 | DRAFT Reply LS on NR V2X resource pool configuration and selection |
LS out LS is reply to R2-1908486 LS To: RAN2 |
vivo | 5G_V2X_NRSL-Core | Rel-16 |
R1-98 AI: 5 |
not treated | [WTS] [JSN] | |
| R1-1910305 | DRAFT Reply LS on UL-SL prioritization |
LS out LS is reply to R2-1911679 LS To: RAN2 |
vivo | 5G_V2X_NRSL-Core | Rel-16 |
R1-98 AI: 5 |
not treated | [WTS] [JSN] | |
| R1-1910306 | Draft reply LS for RAN2 LS on additional PDCCH monitoring occasions for paging for NR-U |
LS out LS is reply to R2-1911861 LS To: RAN2 |
vivo | NR_unlic-Core | Rel-16 |
R1-98 AI: 5 |
not treated | [WTS] [JSN] | |
| R1-1910307 | Discussions on RAN4 LS on RSSI definition | discussion | vivo |
R1-98 AI: 5 |
not treated | [WTS] [JSN] | |||
| R1-1910308 | Draft reply LS on single PDCCH-based multi-TRP operation |
LS out LS is reply to R2-1911848 LS To: RAN2 |
vivo | NR_eMIMO-Core | Rel-16 |
R1-98 AI: 5 |
not treated | [WTS] [JSN] | |
| R1-1910377 | Discussion on UL and SL prioritization for NR-V2X | discussion | OPPO |
R1-98 AI: 5 |
not treated | [WTS] [JSN] | |||
| R1-1910378 | Draft reply LS on UL-SL prioritization |
LS out LS is reply to R2-1911679 LS To: RAN2 revised to R1-1911719 |
OPPO | 5G_V2X_NRSL-Core | Rel-16 |
R1-98 AI: 5 |
revised | [WTS] [JSN] | |
| R1-1910390 | Draft Reply LS on HARQ feedback in response to MsgB |
LS out LS is reply to R2-1911862 LS To: RAN2 |
Huawei, HiSilicon | NR_2step_RACH-Core | Rel-16 |
R1-98 AI: 5 |
not treated | [WTS] [JSN] | |
| R1-1910391 | [DRAFT] Reply LS on UL-SL prioritization |
LS out LS is reply to R2-1911679 LS To: RAN2 |
Huawei | 5G_V2X_NRSL-Core | Rel-16 |
R1-98 AI: 5 |
not treated | [WTS] [JSN] | |
| R1-1910400 | Draft Reply LS on ambiguity of UE L1 FDD/TDD FR1/FR2 capabilities |
LS out LS is reply to R2-1911858 LS To: RAN2 |
Huawei, HiSilicon | NR_newRAT-Core | Rel-15 |
R1-98 AI: 5 |
not treated | [WTS] [JSN] | |
| R1-1910402 | Draft Reply LS on single PDCCH based multi-TRP operation |
LS out LS is reply to R2-1911848 LS To: RAN2 revised to R1-1911524 |
Huawei, HiSilicon | NR_eMIMO-Core | Rel-16 |
R1-98 AI: 5 |
revised | [WTS] [JSN] | |
| R1-1910403 | Draft Reply LS on additional PDCCH monitoring occasions for paging for NR-U |
LS out LS is reply to R2-1911861 LS To: RAN2 |
Huawei, HiSilicon | NR_unlic-Core | Rel-16 |
R1-98 AI: 5 |
not treated | [WTS] [JSN] | |
| R1-1910443 | [DRAFT] Reply LS to RAN 2 on single PDCCH-based multi-TRP operation |
LS out LS is reply to R2-1911848 LS To: RAN2 |
Samsung | NR_eMIMO-Core | Rel-16 |
R1-98 AI: 5 |
not treated | [WTS] [JSN] | |
| R1-1910444 | [DRAFT] Reply LS on UL-SL prioritization |
LS out LS is reply to R2-1911679 LS To: RAN2 |
Samsung | 5G_V2X_NRSL-Core | Rel-16 |
R1-98 AI: 5 |
not treated | [WTS] [JSN] | |
| R1-1910445 | [DRAFT] Reply LS on ambiguity of UE L1 FDD/TDD FR1/FR2 capabilities |
LS out LS is reply to R2-1911858 LS To: RAN2 |
Samsung | NR_newRAT-Core | Rel-15 |
R1-98 AI: 5 |
not treated | [WTS] [JSN] | |
| R1-1910552 | Discussion of LS on Propagation Delay Compensation for Reference Time Information Delivery | discussion | Ericsson |
R1-98 AI: 5 |
not treated | [WTS] [JSN] | |||
| R1-1910593 | Discussion on additional PDCCH monitoring occasions for paging for NR-U | discussion | Nokia, Nokia Shanghai Bell |
R1-98 AI: 5 |
not treated | [WTS] [JSN] | |||
| R1-1910618 | Discussion on RSSI Measurements for NR-U | discussion | Nokia, Nokia Shanghai Bell | Rel-16 |
R1-98 AI: 5 |
not treated | [WTS] [JSN] | ||
| R1-1910691 | [Draft] Reply to LS on RAN2 agreements related to 2-step RACH |
LS out LS is reply to R2-1911862 LS To: RAN2 |
Nokia, Nokia Shanghai Bell | NR_2step_RACH-Core | Rel-16 |
R1-98 AI: 5 |
not treated | [WTS] [JSN] | |
| R1-1910703 | DRAFT Reply LS on UL-SL prioritization |
LS out LS is reply to R2-1911679 LS To: RAN2, RAN4 |
Futurewei | 5G_V2X_NRSL-Core | Rel-16 |
R1-98 AI: 5 |
not treated | [WTS] [JSN] | |
| R1-1910705 | DRAFT LS on PSBCH content | other | Futurewei |
R1-98 AI: 5 |
not treated | [WTS] [JSN] | |||
| R1-1910866 | DRAFT LS response on single PDCCH-based multi-TRP operation |
LS out LS is reply to R2-1911848 LS To: RAN2 |
Ericsson | NR_eMIMO-Core | Rel-16 |
R1-98 AI: 5 |
not treated | [WTS] [JSN] | |
| R1-1910904 | Notification of July 2019 Coexistence Workshop Results |
LS in LS To: RAN1 |
IEEE 802.11 Working Group Chair | LTE_LAA, NR_unlic | Rel-16 |
R1-98 AI: 5 |
treated | [WTS] [JSN] | |
| R1-1911024 | Draft Reply LS on single PDCCH-based multi-TRP operation |
LS out LS is reply to R2-1911848 LS To: RAN2 |
Futurewei | NR_eMIMO-Core | Rel-16 |
R1-98 AI: 5 |
not treated | [WTS] [JSN] | |
| R1-1911025 | Draft Reply LS on ambiguity of UE L1 FDD/TDD FR1/FR2 capabilities |
LS out LS is reply to R2-1911858 LS To: RAN2 |
Futurewei | NR_newRAT-Core | Rel-15 |
R1-98 AI: 5 |
not treated | [WTS] [JSN] | |
| R1-1911041 | LS Response on LS on MsgA Content Size | discussion | Ericsson |
R1-98 AI: 5 |
not treated | [WTS] [JSN] | |||
| R1-1911087 | Discussion on ambiguity of UE L1 FDD-TDD FR1-FR2 capabilities | discussion | Qualcomm Incorporated | NR_newRAT-Core | Rel-15 |
R1-98 AI: 5 |
withdrawn | [WTS] [JSN] | |
| R1-1911193 | Draft Reply LS on single PDCCH-based multi-TRP operation |
LS out LS is reply to R2-1911848 LS To: RAN2 |
Nokia, Nokia Shanghai Bell | NR_eMIMO-Core | Rel-16 |
R1-98 AI: 5 |
not treated | [WTS] [JSN] | |
| R1-1911238 | [Draft] Reply LS on UL-SL prioritization |
LS out LS is reply to R2-1911679 LS To: RAN2 |
Ericsson | 5G_V2X_NRSL-Core | Rel-16 |
R1-98 AI: 5 |
withdrawn | [WTS] [JSN] | |
| R1-1911266 | Discussion on the feasibility of received interference power measurement in NR | other | Huawei, HiSilicon |
R1-98 AI: 5 |
noted | [WTS] [JSN] | |||
| R1-1911428 | LS Reply on maximum value of MDBV |
LS in LS is reply to S2-1907955 LS To: SA2 |
CT3, Nokia | 5GS_Ph1 | Rel-16 |
R1-98 AI: 5 |
noted | [WTS] [JSN] | |
| R1-1911500 | LS to RAN1 on WUS for short DRX cycle |
LS in source LS: R2-1914060 LS To: RAN1 |
RAN2, vivo | NR_UE_pow_sav-Core | Rel-16 |
R1-98 AI: 5 |
treated | [WTS] [JSN] | |
| R1-1911536 | LS on differentiating between MSG2 and MSGB |
LS in source LS: R2-1914191 LS To: RAN1 |
RAN2, ZTE | NR_2step_RACH-Core | Rel-16 |
R1-98 AI: 5 |
treated | [WTS] [JSN] | |
| R1-1911551 | Contention Window Update in Initiating Device Channel Access Mechanism of EN 301 893 |
LS in source LS: BRAN(19)103033r1 LS To: RAN1, IEEE 802.11 |
ETSI TC BRAN |
R1-98 AI: 5 |
treated | [WTS] [JSN] | |||
| R1-1911584 | LS on SFN LSB indication in msg2/msgB |
LS in source LS: R2-1914064 LS To: RAN1 |
RAN2, Qualcomm | NR_unlic-Core, NR_2step_RACH-Core | Rel-16 |
R1-98 AI: 5 |
treated | [WTS] [JSN] | |
| R1-1911585 | LS on PHR reporting for NR-U |
LS in source LS: R2-1914068 LS To: RAN1 |
RAN2, Lenovo | NR_unlic-Core | Rel-16 |
R1-98 AI: 5 |
treated | [WTS] [JSN] | |
| R1-1911596 | Draft Reply LS on additional PDCCH monitoring occasions for paging for NR-U |
LS out LS is reply to R2-1911861 LS To: RAN2 revision of R1-1909979 revised to R1-1911705 |
ZTE, Sanechips | NR_unlic-Core | Rel-16 |
R1-98 AI: 5 |
revised | [WTS] [JSN] | |
| R1-1911648 | [draft] Reply LS on RAN2 agreements related to 2-step RACH |
LS out LS is reply to R2-1911862 LS To: RAN2 revised to R1-1911739 |
Nokia | NR_2step_RACH-Core | Rel-16 |
R1-98 AI: 5 |
revised | [WTS] [JSN] | |
| R1-1911649 | [Draft] Reply to LS on differentiating between MSG2 and MSGB |
LS out LS is reply to R2-1914191 LS To: RAN2 revised to R1-1911656 |
Nokia | NR_2step_RACH-Core | Rel-16 |
R1-98 AI: 5 |
revised | [WTS] [JSN] | |
| R1-1911656 | Reply to LS on differentiating between MSG2 and MSGB |
LS out LS is reply to R2-1914191 LS To: RAN2 revision of R1-1911649 |
RAN1, Nokia | NR_2step_RACH-Core | Rel-16 |
R1-98 AI: 5 |
approved | [WTS] [JSN] | |
| R1-1911665 | [DRAFT] Response LS on the feasibility of Received Interference Power measurement |
LS out LS is reply to R2-1911846 LS To: RAN2 |
Huawei | NR_SON_MDT-Core | Rel-16 |
R1-98 AI: 5 |
noted | [WTS] [JSN] | |
| R1-1911671 | LCP restriction for Dynamic Grant |
LS in source LS: R2-1914214 LS To: RAN1 |
RAN2, Qualcomm | NR_IIOT-Core | Rel-16 |
R1-98 AI: 5 |
treated | [WTS] [JSN] | |
| R1-1911672 | LS on Handling Multiple Unicast Links with Peer UE |
LS in source LS: R2-1914150 LS To: RAN1 |
RAN2, InterDigital | 5G_V2X_NRSL-Core | Rel-16 |
R1-98 AI: 5 |
treated | [WTS] [JSN] | |
| R1-1911673 | LS on Layer 2 Identifiers for NR sidelink communication |
LS in source LS: R2-1914147 LS To: RAN1, SA2 |
RAN2, LG Electronics | 5G_V2X_NRSL-Core | Rel-16 |
R1-98 AI: 5 |
treated | [WTS] [JSN] | |
| R1-1911675 | Reply LS on mapping between LTE V2X PPPP and NR V2X priority |
LS in LS is reply to R1-1909876 source LS: S2-1909987 LS To: RAN1 |
SA2, Qualcomm | eV2XARC | Rel-16 |
R1-98 AI: 5 |
treated | [WTS] [JSN] | |
| R1-1911676 | Reply LS on Sidelink HARQ Feedback for Groupcast |
LS in LS is reply to R1-1909879 source LS: S2-1910771 LS To: RAN1, RAN2 |
SA2, LG Electronics | eV2XARC, 5G_V2X_NRSL-Core | Rel-16 |
R1-98 AI: 5 |
treated | [WTS] [JSN] | |
| R1-1911677 | LS on sync raster for NR V2X |
LS in source LS: R4-1913063 LS To: RAN1, RAN2 |
RAN4, vivo | 5G_V2X_NRSL-Core | Rel-16 |
R1-98 AI: 5 |
treated | [WTS] [JSN] | |
| R1-1911678 | Reply LS on simultaneous transmission of PSFCH |
LS in source LS: R4-1913061 LS To: RAN1 |
RAN4, Qualcomm Incorporated | 5G_V2X_NRSL-Core | Rel-16 |
R1-98 AI: 5 |
treated | [WTS] [JSN] | |
| R1-1911679 | Reply LS on AGC settling time and RB size of PSFCH |
LS in LS is reply to R1-1909922 source LS: R4-1912888 LS To: RAN1 |
RAN4, LG Electronics | 5G_V2X_NRSL-Core | Rel-16 |
R1-98 AI: 5 |
treated | [WTS] [JSN] | |
| R1-1911680 | LS on UL wideband operation for NR-U |
LS in LS is reply to R1-1905895 source LS: R4-1912866 LS To: RAN1 |
RAN4, Qualcomm Incorporated | NR_unlic-Core | Rel-16 |
R1-98 AI: 5 |
treated | [WTS] [JSN] | |
| R1-1911681 | LS Response on the feasibility of time synchronization accuracy requirements and related testing |
LS in LS is reply to R1-1909906 source LS: R4-1912743 LS To: RAN1, RAN2 |
RAN4, Nokia | NR_IIOT-Core | Rel-16 |
R1-98 AI: 5 |
treated | [WTS] [JSN] | |
| R1-1911705 | Reply LS on additional PDCCH monitoring occasions for paging for NR-U |
LS out LS is reply to R2-1911861 LS To: RAN2 revision of R1-1911596 |
RAN1, ZTE | NR_unlic-Core | Rel-16 |
R1-98 AI: 5 |
approved | [WTS] [JSN] | |
| R1-1911719 | Draft reply LS on UL-SL prioritization |
LS out LS is reply to R2-1911679 LS To: RAN2, RAN4 revision of R1-1910378 revised to R1-1911720 |
OPPO | 5G_V2X_NRSL-Core | Rel-16 |
R1-98 AI: 5 |
revised | [WTS] [JSN] | |
| R1-1911720 | Reply LS on UL-SL prioritization |
LS out LS is reply to R2-1911679 LS To: RAN2, RAN4 revision of R1-1911719 |
RAN1, OPPO | 5G_V2X_NRSL-Core | Rel-16 |
R1-98 AI: 5 |
approved | [WTS] [JSN] | |
| R1-1911739 | Reply LS on RAN2 agreements related to 2-step RACH |
LS out LS is reply to R2-1911862 LS To: RAN2 revision of R1-1911648 |
RAN1, Nokia | NR_2step_RACH-Core | Rel-16 |
R1-98 AI: 5 |
approved | [WTS] [JSN] |
88 documents (0.4167149066925 seconds)