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 |
|---|---|---|---|---|---|---|---|---|---|
| S2-2205395 | LS from RAN WG3: LS on further outstanding issues in TS 23.247 |
LS in source LS: R3-222867 LS To: SA WG2, RAN WG2 LS reply in S2-2207389 revision of S2-2203635 |
RAN WG3 | Rel-17 |
S2-152-e AI: 8.9 |
replied to | [WTS] [JSN] | ||
| S2-2205398 | LS from CT WG3: Questions on PCC aspects related to 5MBS |
LS in source LS: C3-222578 LS To: SA WG2 LS reply in S2-2207407 revision of S2-2203646 |
CT WG3 | Rel-17 |
S2-152-e AI: 8.9 |
replied to | [WTS] [JSN] | ||
| S2-2205403 | LS from CT WG4: LS on Clarification on MBS Security Keys |
LS in source LS: C4-223302 LS To: SA WG3 revision of S2-2203669 |
CT WG4 | Rel-17 |
S2-152-e AI: 8.9 |
noted | [WTS] [JSN] | ||
| S2-2205415 | LS from CT WG4: LS on Support of Broadcast and Multicast MBS sessions with AMF Set |
LS in source LS: C4-223303 LS To: RAN WG3 |
CT WG4 | Rel-17 |
S2-152-e AI: 8.9 |
noted | [WTS] [JSN] | ||
| S2-2205426 | LS from RAN WG2: LS on AS-NAS layer interactions for MBS |
LS in source LS: R2-2206609 LS To: CT WG1 LS reply in S2-2207409 |
RAN WG2 | Rel-17 |
S2-152-e AI: 8.9 |
replied to | [WTS] [JSN] | ||
| S2-2205445 | LS from SA WG6: LS on N5 clarification for MBS usage |
LS in source LS: S6-221440 LS To: SA WG2 LS reply in S2-2207406 |
SA WG6 | Rel-18 |
S2-152-e AI: 8.9 |
replied to | [WTS] [JSN] | ||
| S2-2205449 | LS from SA WG4: Reply LS on the MBS broadcast service continuity and MBS session identification |
LS in source LS: S4-220827 LS To: RAN WG2 |
SA WG4 | Rel-17 |
S2-152-e AI: 8.9 |
noted | [WTS] [JSN] | ||
| S2-2205450 | LS from SA WG4: Reply LS on 5MBS User Services |
LS in source LS: S4-220828 LS To: SA WG2 revised to S2-2208108 |
SA WG4 | Rel-17 |
S2-152-e AI: 8.9 |
postponed | [WTS] [JSN] | ||
| S2-2205456 | LS from SA WG3: Reply LS on Clarification on MBS Security Keys |
LS in source LS: S3-221665 LS To: CT WG4 |
SA WG3 | Rel-17 |
S2-152-e AI: 8.9 |
noted | [WTS] [JSN] | ||
| S2-2205463 | LS from SA WG4: Reply LS on 5MBS User Services |
LS in source LS: S4-220829 LS To: CT WG3, CT WG4 |
SA WG4 | Rel-17 |
S2-152-e AI: 8.9 |
noted | [WTS] [JSN] | ||
| S2-2205466 | LS from SA WG3: Reply LS on Security architecture for 5G multicast/broadcast services |
LS in source LS: S3-221158 LS To: SA WG4 LS reply in S2-2207390 |
SA WG3 | Rel-17 |
S2-152-e AI: 8.9 |
replied to | [WTS] [JSN] | ||
| S2-2205469 | LS from SA WG3: Reply LS on Clarification on MBS Security Keys |
LS in source LS: S3-221262 LS To: CT WG4 |
SA WG3 | Rel-17 |
S2-152-e AI: 8.9 |
noted | [WTS] [JSN] | ||
| S2-2205603 | MBS Session Status and broadcast MBS Session | CR | Ericsson | 23.247 17.3.0 CR#122 catF | 5MBS | Rel-17 |
S2-152-e AI: 8.9 |
agreed | [WTS] [JSN] |
| S2-2205604 | [DRAFT] Reply LS on AS-NAS layer interactions for MBS |
LS out LS To: RAN WG2, CT WG1 |
Ericsson | 5MBS, NR_MBS-Core | Rel-17 |
S2-152-e AI: 8.9 |
merged | [WTS] [JSN] | |
| S2-2205605 | [DRAFT] Reply LS on 5MBS User Services |
LS out LS To: SA WG4 |
Ericsson | 5MBS, 5MBUSA | Rel-17 |
S2-152-e AI: 8.9 |
postponed | [WTS] [JSN] | |
| S2-2205606 | Clarification on interworking at reference point of MB2 | CR | Ericsson | 23.247 17.3.0 CR#123 catF | 5MBS | Rel-17 |
S2-152-e AI: 8.9 |
postponed | [WTS] [JSN] |
| S2-2205686 | Clarification on local multicast | CR | LG Electronics | 23.247 17.3.0 CR#124 catF | 5MBS | Rel-17 |
S2-152-e AI: 8.9 |
agreed | [WTS] [JSN] |
| S2-2205757 | Need for pre-configured USD and service announcement |
CR revision of S2-2204319 |
Qualcomm Incorporated, Ericsson, Deutsche Telekom, AT&T, Orange | 23.247 17.3.0 CR#1003 catF | 5MBS | Rel-17 |
S2-152-e AI: 8.9 |
noted | [WTS] [JSN] |
| S2-2205758 | [DRAFT] Reply LS on parameters preconfigured in the UE to receive MBS service |
LS out LS To: TSG CT, CT WG1 |
Qualcomm | 5MBS | Rel-17 |
S2-152-e AI: 8.9 |
noted | [WTS] [JSN] | |
| S2-2205759 | [DRAFT] Reply LS on Security architecture for 5G multicast/broadcast services |
LS out LS To: SA WG3 revised to S2-2207390 |
Qualcomm | 5MBS | Rel-17 |
S2-152-e AI: 8.9 |
revised | [WTS] [JSN] | |
| S2-2205834 | Discussion on Questions on PCC aspects related to 5MBS | discussion | Ericsson | 5MBS | Rel-17 |
S2-152-e AI: 8.9 |
noted | [WTS] [JSN] | |
| S2-2205835 | [DRAFT] Reply to LS on PCC aspects related to 5MBS |
LS out LS To: CT WG3 |
Ericsson | 5MBS | Rel-17 |
S2-152-e AI: 8.9 |
merged | [WTS] [JSN] | |
| S2-2205836 | Update of PCC procedure for 5MBS | CR | Ericsson | 23.247 17.3.0 CR#125 catF | 5MBS | Rel-17 |
S2-152-e AI: 8.9 |
merged | [WTS] [JSN] |
| S2-2205837 | Correction to MB-SMF update in NRF |
CR revised to S2-2207411 |
Ericsson | 23.247 17.3.0 CR#126 catF | 5MBS | Rel-17 |
S2-152-e AI: 8.9 |
revised | [WTS] [JSN] |
| S2-2205896 | Corrections related to PCC aspects related to 5MBS |
CR revision of S2-2203969 |
Nokia, Nokia Shanghai-Bell | 23.247 17.3.0 CR#1181 catF | 5MBS | Rel-17 |
S2-152-e AI: 8.9 |
merged | [WTS] [JSN] |
| S2-2205897 | [DRAFT] Reply LS on Questions on PCC aspects related to 5MBS |
LS out LS To: CT WG3, CT WG4 revision of S2-2203968 |
Nokia, Nokia Shanghai Bell | 5MBS | Rel-17 |
S2-152-e AI: 8.9 |
merged | [WTS] [JSN] | |
| S2-2205950 | [DRAFT] Reply LS on N5 clarification for MBS usage |
LS out LS To: SA WG6 revised to S2-2207406 |
Nokia, Nokia Shanghai Bell | 5MBS | Rel-17 |
S2-152-e AI: 8.9 |
revised | [WTS] [JSN] | |
| S2-2206049 | Update of PCC procedure for 5MBS |
CR revision of S2-2204314 revised to S2-2207408 |
Huawei, HiSilicon | 23.247 17.3.0 CR#1093 catF | 5MBS | Rel-17 |
S2-152-e AI: 8.9 |
revised | [WTS] [JSN] |
| S2-2206050 | [DRAFT] Response to LS on Questions on PCC aspects related to 5MBS |
LS out LS To: CT WG3 revision of S2-2204276 revised to S2-2207407 |
Huawei, HiSilicon | 5MBS | Rel-17 |
S2-152-e AI: 8.9 |
revised | [WTS] [JSN] | |
| S2-2206076 | Corrections and improvement of TS 23.247 |
CR revised to S2-2207410 |
Huawei, HiSilicon | 23.247 17.3.0 CR#127 catF | 5MBS | Rel-17 |
S2-152-e AI: 8.9 |
revised | [WTS] [JSN] |
| S2-2206077 | [DRAFT] LS response to RAN WG2 regarding AS-NAS layer interactions |
LS out LS To: RAN WG2 revised to S2-2207409 |
Huawei, HiSilicon | 5MBS, NR_MBS-Core | Rel-17 |
S2-152-e AI: 8.9 |
revised | [WTS] [JSN] | |
| S2-2206078 | [DRAFT] Reply LS on N5 clarification for MBS usage |
LS out LS To: SA WG6 |
Huawei, HiSilicon | 5MBS, MCOver5MBS | Rel-18 |
S2-152-e AI: 8.9 |
merged | [WTS] [JSN] | |
| S2-2206089 | Pre-configured USD and service announcement | CR | Huawei, HiSilicon, ZTE, CATT, CBN | 23.247 17.3.0 CR#128 catF | 5MBS | Rel-17 |
S2-152-e AI: 8.9 |
noted | [WTS] [JSN] |
| S2-2206205 | [DRAFT] Reply LS on 5MBS User Services |
LS out LS To: SA WG4 |
ZTE | 5MBS | Rel-17 |
S2-152-e AI: 8.9 |
postponed | [WTS] [JSN] | |
| S2-2206206 | Clarification on the traffic handling in MBSTF for interworking |
CR revised to S2-2208951 |
ZTE | 23.247 17.3.0 CR#129 catF | 5MBS | Rel-17 |
S2-152-e AI: 8.9 |
postponed | [WTS] [JSN] |
| S2-2206207 | Clarificaiton on the mobility in RRC inactive |
CR revised to S2-2207412 |
ZTE | 23.247 17.3.0 CR#130 catF | 5MBS | Rel-17 |
S2-152-e AI: 8.9 |
revised | [WTS] [JSN] |
| S2-2206208 | Clarification on the MBS Broadcast | CR | ZTE | 23.247 17.3.0 CR#131 catF | 5MBS | Rel-17 |
S2-152-e AI: 8.9 |
merged | [WTS] [JSN] |
| S2-2206209 | Removing the EN on the HO |
CR revised to S2-2207413 |
ZTE | 23.247 17.3.0 CR#132 catF | 5MBS | Rel-17 |
S2-152-e AI: 8.9 |
revised | [WTS] [JSN] |
| S2-2206525 | [DRAFT] Response LS on further outstanding issues in TS 23.247 |
LS out LS To: RAN WG3, RAN WG2 revised to S2-2207389 |
Huawei, HiSilicon | 5MBS | Rel-17 |
S2-152-e AI: 8.9 |
revised | [WTS] [JSN] | |
| S2-2207389 | Response LS on further outstanding issues in TS 23.247 |
LS out LS is reply to S2-2205395 LS To: RAN WG3, RAN WG2 revision of S2-2206525 |
SA WG2 | 5MBS | Rel-17 |
S2-152-e AI: 8.9 |
approved | [WTS] [JSN] | |
| S2-2207390 | Reply LS on Security architecture for 5G multicast/broadcast services |
LS out LS is reply to S2-2205466 LS To: SA WG3 revision of S2-2205759 |
SA WG2 | 5MBS | Rel-17 |
S2-152-e AI: 8.9 |
approved | [WTS] [JSN] | |
| S2-2207406 | LS on N5 clarification for MBS usage |
LS out LS is reply to S2-2205445 LS To: SA WG6 revision of S2-2205950 |
SA WG2 | 5MBS | Rel-17 |
S2-152-e AI: 8.9 |
approved | [WTS] [JSN] | |
| S2-2207407 | Response to LS on Questions on PCC aspects related to 5MBS |
LS out LS is reply to S2-2205398 LS To: CT WG3 revision of S2-2206050 |
SA WG2 | 5MBS | Rel-17 |
S2-152-e AI: 8.9 |
approved | [WTS] [JSN] | |
| S2-2207408 | Update of PCC procedure for 5MBS |
CR revision of S2-2206049 |
Huawei, HiSilicon, Nokia, Nokia Shanghai-Bell, Ericsson, ZTE | 23.247 17.3.0 CR#1094 catF | 5MBS | Rel-17 |
S2-152-e AI: 8.9 |
agreed | [WTS] [JSN] |
| S2-2207409 | LS on AS-NAS layer interactions for MBS |
LS out LS is reply to S2-2205426 LS To: RAN WG2, CT WG1 revision of S2-2206077 |
SA WG2 | 5MBS, NR_MBS-Core | Rel-17 |
S2-152-e AI: 8.9 |
approved | [WTS] [JSN] | |
| S2-2207410 | Correction and editorial improvement |
CR revision of S2-2206076 |
Huawei, HiSilicon, Nokia, Nokia Shanghai-Bell, Ericsson, ZTE | 23.247 17.3.0 CR#1271 catF | 5MBS | Rel-17 |
S2-152-e AI: 8.9 |
agreed | [WTS] [JSN] |
| S2-2207411 | Correction to MB-SMF update in NRF |
CR revision of S2-2205837 |
Ericsson | 23.247 17.3.0 CR#1261 catF | 5MBS | Rel-17 |
S2-152-e AI: 8.9 |
agreed | [WTS] [JSN] |
| S2-2207412 | Clarification on the mobility in RRC inactive |
CR revision of S2-2206207 |
ZTE, Ericsson | 23.247 17.3.0 CR#1301 catF | 5MBS | Rel-17 |
S2-152-e AI: 8.9 |
agreed | [WTS] [JSN] |
| S2-2207413 | Removing the EN on the HO |
CR revision of S2-2206209 |
ZTE, Ericsson | 23.247 17.3.0 CR#1321 catF | 5MBS | Rel-17 |
S2-152-e AI: 8.9 |
agreed | [WTS] [JSN] |
49 documents (0.37760305404663 seconds)