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-2008751 | Reply LS on RAN impact of FS_5MBS Study (RP-202086; contact: Huawei) |
LS in LS is reply to S2-2006044 source LS: RP-202086 LS To: SA, SA2 |
RAN | FS_5MBS, NR_MBS-Core | Rel-17 |
R2-112-e AI: 8.1.1 |
noted | [WTS] [JSN] | |
| R2-2008755 | LS on RAN impact of FS_5MBS Study (S2-2006044; contact: Huawei) |
LS in source LS: S2-2006044 LS To: SA, RAN, RAN2, RAN3 |
SA2 | FS_5MBS, NR_MBS-Core | Rel-17 |
R2-112-e AI: 8.1.1 |
noted | [WTS] [JSN] | |
| R2-2008768 | Reply LS on RAN impact of FS_5MBS Study (SP-200884; contact: Huawei) |
LS in LS is reply to S2-2006044 source LS: SP-200884 LS To: RAN, SA2 |
SA | FS_5MBS, NR_MBS-Core | Rel-17 |
R2-112-e AI: 8.1.1 |
noted | [WTS] [JSN] | |
| R2-2008791 | Discussion on Requirement and Architecture of MBS | discussion | CATT | NR_MBS-Core | Rel-17 |
R2-112-e AI: 8.1.1 |
available | [WTS] [JSN] | |
| R2-2008865 | Considerations on Protocol stack and network architecture | discussion | OPPO | NR_MBS-Core | Rel-17 |
R2-112-e AI: 8.1.1 |
available | [WTS] [JSN] | |
| R2-2008929 | Discussioin on the protocol stack for NR MBS | discussion | CHENGDU TD TECH LTD. |
R2-112-e AI: 8.1.1 |
available | [WTS] [JSN] | |||
| R2-2009036 | NR Multicast Vs Broadcast comparison and Radio Bearer Architecture aspects |
discussion revised to R2-2100318 |
Qualcomm Inc | NR_MBS-Core | Rel-17 |
R2-112-e AI: 8.1.1 |
available | [WTS] [JSN] | |
| R2-2009196 | MBS L2 Architecture, user plane and control plane | discussion | Intel Corporation | NR_MBS-Core | Rel-17 |
R2-112-e AI: 8.1.1 |
available | [WTS] [JSN] | |
| R2-2009303 | MBS Protocol Architecture and Logical Channel Aggregation | discussion | Futurewei | NR_MBS-Core | Rel-17 |
R2-112-e AI: 8.1.1 |
available | [WTS] [JSN] | |
| R2-2009334 | Updated NR MBS workplan | discussion | Huawei, CMCC, HiSilicon | NR_MBS-Core | Rel-17 |
R2-112-e AI: 8.1.1 |
noted | [WTS] [JSN] | |
| R2-2009335 | Discussion on SA2 LS on RAN impact of FS_5MBS Study | discussion | Huawei, HiSilicon | NR_MBS-Core | Rel-17 |
R2-112-e AI: 8.1.1 |
available | [WTS] [JSN] | |
| R2-2009336 | Draft reply LS to SA2 on RAN impact of FS_5MBS Study |
LS out LS is reply to S2-2006044 LS To: SA, SA2, RAN3 revised to R2-2011133 |
Huawei, HiSilicon | NR_MBS-Core | Rel-17 |
R2-112-e AI: 8.1.1 |
revised | [WTS] [JSN] | |
| R2-2009337 | Summary of Email discussion Post111-e-904 MBS L2 Architecture | discussion | Huawei, HiSilicon | NR_MBS-Core | Rel-17 |
R2-112-e AI: 8.1.1 |
noted | [WTS] [JSN] | |
| R2-2009343 | 38.300 running CR for NR MBS | draftCR | Huawei, HiSilicon | NR_MBS-Core | Rel-17 |
R2-112-e AI: 8.1.1 |
available | [WTS] [JSN] | |
| R2-2009668 | Framework for NR MBS Broadcast and Multicast services | discussion | Lenovo, Motorola Mobility | NR_MBS-Core | Rel-17 |
R2-112-e AI: 8.1.1 |
available | [WTS] [JSN] | |
| R2-2009740 | L2 architecture for NR MBS | discussion | ZTE, Sanechips | Rel-17 |
R2-112-e AI: 8.1.1 |
available | [WTS] [JSN] | ||
| R2-2009822 | draft_Reply LS on RAN impact of FS_5MBS Study |
LS out LS To: SA2, RAN3 |
ZTE, Sanechips | Rel-17 |
R2-112-e AI: 8.1.1 |
available | [WTS] [JSN] | ||
| R2-2009883 | Security for PTP and PTM switching | discussion | Sony | NR_MBS-Core | Rel-17 |
R2-112-e AI: 8.1.1 |
available | [WTS] [JSN] | |
| R2-2009954 | SA2 questions about RRC state transitions for multicast | discussion | Ericsson | NR_MBS-Core | Rel-17 |
R2-112-e AI: 8.1.1 |
available | [WTS] [JSN] | |
| R2-2010064 | On Stage-2 aspects and overview of NR MBS | discussion | Samsung |
R2-112-e AI: 8.1.1 |
available | [WTS] [JSN] | |||
| R2-2010214 | General considerations on NR MBS | discussion | vivo |
R2-112-e AI: 8.1.1 |
available | [WTS] [JSN] | |||
| R2-2010234 | Consideration of control plane aspects for NR MBS | discussion | Kyocera | Rel-17 |
R2-112-e AI: 8.1.1 |
available | [WTS] [JSN] | ||
| R2-2010411 | Discussion on user-plane channel structure for MBS | discussion | LG Electronics Inc. | NR_MBS-Core | Rel-17 |
R2-112-e AI: 8.1.1 |
available | [WTS] [JSN] | |
| R2-2011022 | Summary of [AT112-e][036][MBS] SA2 LS on MBS | discussion | Huawei, HiSilicon | NR_MBS-Core | Rel-17 |
R2-112-e AI: 8.1.1 |
noted | [WTS] [JSN] | |
| R2-2011133 | Draft reply LS to SA2 on RAN impact of FS_5MBS Study |
LS out LS is reply to S2-2006044 LS To: SA, SA2, RAN3 revision of R2-2009336 revised to R2-2011170 |
Huawei, HiSilicon | NR_MBS-Core | Rel-17 |
R2-112-e AI: 8.1.1 |
revised | [WTS] [JSN] | |
| R2-2011170 | [DRAFT] Reply LS on RAN impact of FS_5MBS Study |
LS out LS is reply to S2-2006044 LS To: SA, SA2, RAN3 revision of R2-2011133 revised to R2-2011271 |
Huawei, HiSilicon | FS_5MBS, NR_MBS-Core | Rel-17 |
R2-112-e AI: 8.1.1 |
revised | [WTS] [JSN] | |
| R2-2011271 | Reply LS on RAN impact of FS_5MBS Study |
LS out LS is reply to S2-2006044 LS To: SA, SA2, RAN3 revision of R2-2011170 |
RAN2 | FS_5MBS, NR_MBS-Core | Rel-17 |
R2-112-e AI: 8.1.1 |
approved | [WTS] [JSN] |
27 documents (0.32423782348633 seconds)