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-2107013 | Discussion on MBS interesting indication for delivery mode 2 | discussion | OPPO | NR_MBS-Core | Rel-17 |
R2-115-e AI: 8.1.3.1 |
not treated | [WTS] [JSN] | |
| R2-2107017 | Discussion on MBS service continuity for delivery mode 2 | discussion | OPPO | NR_MBS-Core | Rel-17 |
R2-115-e AI: 8.1.3.1 |
not treated | [WTS] [JSN] | |
| R2-2107035 | Open Issues on Service Continuity of Delivery Mode 2 | discussion | CATT, CBN | NR_MBS-Core | Rel-17 |
R2-115-e AI: 8.1.3.1 |
not treated | [WTS] [JSN] | |
| R2-2107050 | Broadcast Service Continuity | discussion | MediaTek Inc. | Rel-17 |
R2-115-e AI: 8.1.3.1 |
not treated | [WTS] [JSN] | ||
| R2-2107234 | On Broadcast Service Continuity | discussion | Samsung |
R2-115-e AI: 8.1.3.1 |
not treated | [WTS] [JSN] | |||
| R2-2107339 | Broadcast Service Continuity | discussion | ZTE, Sanechips | NR_MBS-Core | Rel-17 |
R2-115-e AI: 8.1.3.1 |
not treated | [WTS] [JSN] | |
| R2-2107364 | Discussion on issues of delivery mode2 | discussion | Spreadtrum Communications | Rel-17 |
R2-115-e AI: 8.1.3.1 |
not treated | [WTS] [JSN] | ||
| R2-2107387 | Discussion on Service Continuity Support for NR MBS | discussion | TCL Communication Ltd. | Rel-17 |
R2-115-e AI: 8.1.3.1 |
not treated | [WTS] [JSN] | ||
| R2-2107798 | Discussion on Broadcast Service Continuity | discussion | vivo | NR_MBS-Core | Rel-17 |
R2-115-e AI: 8.1.3.1 |
not treated | [WTS] [JSN] | |
| R2-2107875 | MBS service continuity | discussion | LG Electronics Inc. | Rel-17 |
R2-115-e AI: 8.1.3.1 |
not treated | [WTS] [JSN] | ||
| R2-2107981 | MCCH considerations | discussion | Nokia, Nokia Shanghai Bell | NR_MBS-Core | Rel-17 |
R2-115-e AI: 8.1.3.1 |
not treated | [WTS] [JSN] | |
| R2-2107999 | Details of control plane aspects for delivery mode 2 in NR MBS |
discussion revision of R2-2105511 revised to R2-2110206 |
Kyocera | Rel-17 |
R2-115-e AI: 8.1.3.1 |
not treated | [WTS] [JSN] | ||
| R2-2108034 | Service continuity for delivery mode 2 | discussion | CHENGDU TD TECH LTD. | Rel-17 |
R2-115-e AI: 8.1.3.1 |
not treated | [WTS] [JSN] | ||
| R2-2108081 | Open issues in Broadcast Service Continuity | discussion | Ericsson | NR_MBS-Core | Rel-17 |
R2-115-e AI: 8.1.3.1 |
not treated | [WTS] [JSN] | |
| R2-2108201 | Remaining issues of MBS Interest Indication | discussion | Huawei, HiSilicon | NR_MBS-Core | Rel-17 |
R2-115-e AI: 8.1.3.1 |
not treated | [WTS] [JSN] | |
| R2-2108522 | Discussion on Broadcast service continuity issues | discussion | CMCC | NR_MBS-Core | Rel-17 |
R2-115-e AI: 8.1.3.1 |
not treated | [WTS] [JSN] | |
| R2-2108677 | Service continuity for delivery mode 2 | discussion | Intel Corporation | NR_MBS-Core | Rel-17 |
R2-115-e AI: 8.1.3.1 |
not treated | [WTS] [JSN] | |
| R2-2108799 | Summary of [Post114-e][073][MBS] Service continuity for Delivery Mode 2 (Xiaomi) | discussion | Xiaomi Communications | NR_MBS-Core | Rel-17 |
R2-115-e AI: 8.1.3.1 |
noted | [WTS] [JSN] | |
| R2-2108914 | LS on the MBS broadcast service continuity and MBS session identification |
LS out LS To: RAN3, SA2, SA4 LS reply in R3-215276, R3-215570, R3-215977 |
RAN2 | NR_MBS-Core | Rel-17 |
R2-115-e AI: 8.1.3.1 |
approved | [WTS] [JSN] | |
| R2-2109041 | Report of [AT115-e][047][MBS] Service Continuity deliver mode 2 | discussion | Xiaomi Communications | Rel-17 |
R2-115-e AI: 8.1.3.1 |
noted | [WTS] [JSN] | ||
| R2-2109052 | Report of [AT115-e][047][MBS] Service Continuity deliver mode 2 | discussion | Xiaomi Communications |
R2-115-e AI: 8.1.3.1 |
noted | [WTS] [JSN] |
21 documents (0.34967803955078 seconds)