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 |
---|---|---|---|---|---|---|---|---|---|
R3-230016 | Reply LS on resource efficiency for MBS reception in RAN sharing scenario |
LS in LS is reply to R2-2211168/R3-226084 source LS: R2-2213109 LS To: RAN3 |
RAN2, CATT | NR_MBS_enh | Rel-18 |
R3-119 AI: 15.2 |
noted | [WTS] [JSN] | |
R3-230026 | Reply LS on the scope of resource efficiency for MBS reception in RAN sharing scenario |
LS in LS is reply to RP-222678/S2-2210175 source LS: S2-2211171 LS To: RAN3 |
SA2, Nokia | FS_5MBS_Ph2, NR_MBS_enh-Core | Rel-18 |
R3-119 AI: 15.2 |
noted | [WTS] [JSN] | |
R3-230078 | Sharing processing for both unicast reception and broadcast reception | discussion | TD Tech, Chengdu TD Tech | Rel-18 |
R3-119 AI: 15.2 |
not treated | [WTS] [JSN] | ||
R3-230081 | Support of MBS in RAN sharing scenarios |
discussion revised to R3-231187 |
Qualcomm Incorporated | NR_MBS_enh-Core | Rel-18 |
R3-119 AI: 15.2 |
not treated | [WTS] [JSN] | |
R3-230098 | (TPs to TS 38.300, 38.410, 38.413, 38.473 BL CRs) MBS reception in RAN sharing scenario | other | Huawei, CBN, China Unicom | NR_MBS_enh-Core | Rel-18 |
R3-119 AI: 15.2 |
noted | [WTS] [JSN] | |
R3-230220 | (TP for TS 38.300) RAN Impacts of Rel-18 RAN Sharing Solutions |
other revised to R3-230941 |
Nokia, Nokia Shanghai Bell |
R3-119 AI: 15.2 |
revised | [WTS] [JSN] | |||
R3-230248 | (TP for 38.413/38.473)Discussion on efficient MBS reception in RAN sharing scenario | other | CATT,CBN |
R3-119 AI: 15.2 |
noted | [WTS] [JSN] | |||
R3-230281 | MBS RAN sharing NG-U tunnel establishment | discussion | NEC | NR_MBS_enh | Rel-18 |
R3-119 AI: 15.2 |
not treated | [WTS] [JSN] | |
R3-230361 | Support of resource efficiency for MBS reception in RAN sharing scenarios | discussion | Ericsson | NR_MBS_enh | Rel-18 |
R3-119 AI: 15.2 |
noted | [WTS] [JSN] | |
R3-230642 | Discussion on MBS RAN sharing | discussion | BEIJING SAMSUNG TELECOM R&D | NR_MBS_enh-Core |
R3-119 AI: 15.2 |
not treated | [WTS] [JSN] | ||
R3-230661 | Discussion on MBS reception in RAN sharing scenarios | discussion | CMCC | NR_MBS_enh | Rel-18 |
R3-119 AI: 15.2 |
not treated | [WTS] [JSN] | |
R3-230742 | TP to TS 38.413 with discussion on network sharing of MBS | other | ZTE | NR_MBS_enh | Rel-18 |
R3-119 AI: 15.2 |
noted | [WTS] [JSN] | |
R3-230929 | Summary of offline discussion (CB:#35_MBS1_Networksharing) | other | Nokia |
R3-119 AI: 15.2 |
noted | [WTS] [JSN] | |||
R3-230941 | (TP for TS 38.300) RAN Impacts of Rel-18 RAN Sharing Solutions |
other revision of R3-230220 revised to R3-231031 |
Nokia, Nokia Shanghai Bell |
R3-119 AI: 15.2 |
revised | [WTS] [JSN] | |||
R3-230989 | (TP for TS 38.401) RAN impacts of Rel-18 RAN Sharing Solution |
other revised to R3-231032 |
Ericsson, Nokia, Nokia Shanghai Bell |
R3-119 AI: 15.2 |
revised | [WTS] [JSN] | |||
R3-231031 | (TP for TS 38.300) RAN impacts of Rel-18 RAN Sharing Solution |
other revision of R3-230941 |
Nokia, Nokia Shanghai Bell, Ericsson, Huawei, Qualcomm Incorporated, ZTE, CATT |
R3-119 AI: 15.2 |
agreed | [WTS] [JSN] | |||
R3-231032 | (TP for TS 38.401) RAN impacts of Rel-18 RAN Sharing Solution |
other revision of R3-230989 |
Ericsson, Nokia, Nokia Shanghai Bell | NR_MBS_enh | Rel-18 |
R3-119 AI: 15.2 |
agreed | [WTS] [JSN] | |
R3-231187 | Support of MBS in RAN sharing scenarios |
discussion revision of R3-230081 |
Qualcomm Incorporated | NR_MBS_enh-Core | Rel-18 |
R3-119-bis-e AI: 15.2 |
noted | [WTS] [JSN] | |
R3-231197 | Sharing processing for both unicast reception and broadcast reception | discussion | TD Tech, Chengdu TD Tech | Rel-18 |
R3-119-bis-e AI: 15.2 |
noted | [WTS] [JSN] | ||
R3-231252 | Discussions and proposals concerning Rel-18 work on MBS reception in RAN sharing scenarios | discussion | Ericsson | NR_MBS_enh | Rel-18 |
R3-119-bis-e AI: 15.2 |
noted | [WTS] [JSN] | |
R3-231283 | (TP for TS 38.300) RAN Impacts of Rel-18 RAN Sharing Solutions | other | Nokia, Nokia Shanghai Bell |
R3-119-bis-e AI: 15.2 |
noted | [WTS] [JSN] | |||
R3-231336 | (TP for 38.473)Discussion on MBS RAN sharing | other | Samsung | NR_MBS_enh-Core | Rel-17 |
R3-119-bis-e AI: 15.2 |
noted | [WTS] [JSN] | |
R3-231350 | (TP for 38.413/38.473/38.401)Discussion on efficient MBS reception in RAN sharing scenario | other | CATT,CBN,China Telecom |
R3-119-bis-e AI: 15.2 |
noted | [WTS] [JSN] | |||
R3-231397 | (TPs to TS 38.401, 38.410, 38.413, 38.473 BL CRs) MBS reception in RAN sharing scenario | other | Huawei, CBN | NR_MBS_enh-Core | Rel-18 |
R3-119-bis-e AI: 15.2 |
noted | [WTS] [JSN] | |
R3-231445 | Remaining issue of supporting MBS reception in RAN Sharing | discussion | Lenovo |
R3-119-bis-e AI: 15.2 |
noted | [WTS] [JSN] | |||
R3-231503 | TP to TS 38.413 and 38.473 with discussion on network sharing of MBS | discussion | ZTE | NR_MBS_enh | Rel-18 |
R3-119-bis-e AI: 15.2 |
noted | [WTS] [JSN] | |
R3-231887 | CB: # MBS1_NetworkSharing- Summary of email discussion | discussion | Ericsson - moderator |
R3-119-bis-e AI: 15.2 |
noted | [WTS] [JSN] |
27 documents (0.29704403877258 seconds)