[{"name":"S2-2203629","title":"LS from TSG CT: LS on parameters preconfigured in the UE to receive MBS service","source":"TSG CT","contact":"Lena Chaponniere","contact-id":38080,"tdoctype":"LS in","for":"Action","abstract":"TSG CT has an approved WID on 5MBS to define necessary CT WGs stage 3 details of the feature based on approved stage 2 requirements. UE preconfiguration for receiving MBS service is one of them. TSG CT notes that the related requirement is in TS 23.247 subclause 7.3.1 stating that the UE can be preconfigured with needed configuration to receive MBS service and if this configuration exists, the UE does not need to interact with the network, quote: To receive the data of broadcast communication service, the UE is either preconfigured with needed configuration (e.g. USD as defined in TS 26.346 [13]) for the UE to receive MBS service, or provisioned with the configuration of broadcast session on application level (service announcement; the configuration may for instance be performed using SIP signalling, or methods described in TS 26.346 [13]). If the needed configuration is pre-configured, the UE does not need to interact with network. CT would like to ask SA WG2 the following questions to define the necessary stage 3 details: Question 1: Which parameters can be preconfigured in the UE to receive MBS service? Question 2: How are these parameters used by the UE?. Action: TSG CT kindly asks SA WG2 to answer the above questions.","secretary_remarks":"Revision of Postponed S2-2201963 from S2#150E. Responses drafted in S2-2204262, S2-2204330. Response in S2-2204721. CC#3: This was postponed.","agenda_item_sort_order":52,"ainumber":"8.9","ainame":"Architectural enhancements for 5G multicast-broadcast services (5MBS)","tdoc_agenda_sort_order":12160,"status":"postponed","reservation_date":"2022-04-21 14:48:20","uploaded":"2022-04-21 14:49:13","revisionof":"S2-2201963","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"CT WG1, CT WG4, SA WG4, RAN WG2, CT WG6","lsoriginalls":"CP-220398","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_151E_Electronic_2022-05\/Docs\/S2-2203629.zip","group":"S2","meeting":"S2-151-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2203631","title":"LS from CT WG1: LS on the impact of MSK update on MBS multicast session update procedure","source":"CT WG1","contact":"Mohamed Amin Nassar","contact-id":87799,"tdoctype":"LS in","for":"Action","abstract":"CT WG1 has observed the following issue that is related to MBS security requirements: The following requirements are specified in clause W.4.1.2 in TS 33.501, v17.4.2: The MSK may be updated based on the request from MB-SMF or AS (e.g., due to the change of authorization information) or based on the local policy (e.g., key lifetime expiration). When the MSK is updated, the MBSF shall send the new MSK to the MB-SMF and then the MB-SMF shall trigger the session update as specified in clause 7.2.6 in TS 23.247 [103]. The MSK and the corresponding key ID are delivered to the UEs that has joined the multicast session. The MBSF shall also send the new MSK to the MBSTF. The MBSTF may request a MSK to the MBSF when it does not have a valid MSK (e.g., due to the current MSK expiration). However, the 'Multicast session update procedure' defined in clause 7.2.6 in TS 23.247 v17.1.0 doesn't support the yellow highlighted requirement in the statement above. CT WG1 would like to draw the attention of SA WG2 to reflect the above highlighted requirement into stage-2 specification TS 23.247, for CT WG1 to be able to proceed with the protocol implementation for MBS security requirements. Action: CT WG1 kindly requests SA WG2 to reflect the above highlighted requirement into the stage-2 specification TS 23.247.","secretary_remarks":"Revision of Postponed S2-2202773 from S2#150E. Response drafted in S2-2203970. Final response in S2-2204741","agenda_item_sort_order":52,"ainumber":"8.9","ainame":"Architectural enhancements for 5G multicast-broadcast services (5MBS)","tdoc_agenda_sort_order":12300,"status":"replied to","reservation_date":"2022-04-21 14:48:20","uploaded":"2022-04-21 14:49:13","revisionof":"S2-2202773","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"SA WG3, CT WG4","lsoriginalls":"C1-221747","lsreply":"S2-2204741","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_151E_Electronic_2022-05\/Docs\/S2-2203631.zip","group":"S2","meeting":"S2-151-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2203635","title":"LS from RAN WG3: LS on further outstanding issues in TS 23.247","source":"RAN WG3","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Action","abstract":"RAN WG3 would like to provide further feedback on issues contained in the latest version of TS 23.247 concerning NG-RAN. {. . .} Action: RAN WG3 asks SA WG2 and RAN WG2 to take into account the provided feedback.","secretary_remarks":"Revision of Postponed S2-2202801 from S2#150E. Responses drafted in S2-2203928, S2-2204303. CC#3: This was postponed.","agenda_item_sort_order":52,"ainumber":"8.9","ainame":"Architectural enhancements for 5G multicast-broadcast services (5MBS)","tdoc_agenda_sort_order":12220,"status":"postponed","reservation_date":"2022-04-21 14:48:20","uploaded":"2022-04-21 14:49:13","revisionof":"S2-2202801","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, RAN WG2","Cc":"","lsoriginalls":"R3-222867","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_151E_Electronic_2022-05\/Docs\/S2-2203635.zip","group":"S2","meeting":"S2-151-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2203644","title":"LS from CT WG3: Reply LS on 5MBS User Services","source":"CT WG3","contact":"Tianmei Liang","contact-id":69846,"tdoctype":"LS in","for":"Information","abstract":"CT WG3 would like to thank SA WG4 for their LS on 5MBS User Services providing an updated progress status of the 5MBUSA work item. {. . .}","secretary_remarks":"Noted","agenda_item_sort_order":52,"ainumber":"8.9","ainame":"Architectural enhancements for 5G multicast-broadcast services (5MBS)","tdoc_agenda_sort_order":12540,"status":"noted","reservation_date":"2022-04-21 14:48:20","uploaded":"2022-04-22 05:13:38","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG4","Cc":"SA WG2, SA WG6, CT WG4","lsoriginalls":"C3-222478","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_151E_Electronic_2022-05\/Docs\/S2-2203644.zip","group":"S2","meeting":"S2-151-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2203646","title":"LS from CT WG3: Questions on PCC aspects related to 5MBS","source":"CT WG3","contact":"Abdessamad EL MOATAMID","contact-id":89270,"tdoctype":"LS in","for":"Action","abstract":"CT WG3 is currently still undertaking the stage 3 work on 5MBS (based on the agreed exception sheet in CP-220165) and has the following questions on the related stage 2 work defined in TS 23.247, in order to enable to finalize the stage 3 work in due time. Question 1: What information is provided by the AF to the NEF? In particular what do the 'service requirements' provided by the AF to the NEF consist of and what are the relationship and restrictions between them? Is it possible to receive several media components (per media type)? How should an application be identified (i.e. more details are needed on the Application Identifier, the AF Communication Service Identifier, the emergency indicator Application service provider defined today in TS 23.247). Question 2: Can SA WG2 elaborate on the content of MBS Session 'PCC rules', the supported Policy Control Request Triggers, other relevant policy information derived and provided by the PCF and possible information the NF service consumer can provide to the PCF? Question 3: Is an Npcf_MBSPolicyControl_Update service operation needed to convey MBS policy trigger information? If it is the case, can SA WG2 clarify where in the procedure this interaction applies depending on the related trigger? Question 4: Regarding the procedure defined in clause 7.1.1.3 of TS 23.247, CT WG3 would like to understand the need and motivation behind some interactions, i.e.: - For both alternatives, can SA WG2 indicate what information can be retrieved in step 15 and what is the difference with the information provided in step 18 (for alternative A) \/ step 24 (for alternative B)? Would it be possible to query the UDR only once? - For alternative B, step 20 in clause 7.1.1.3-1, can SA WG2 clarify what status is expected to be reported since the MBS session is not yet created?. Action: CT WG3 kindly asks SA WG2 to answer the above questions and update the SA WG2 specifications accordingly, where appropriate and if necessary.","secretary_remarks":"Responses drafted in S2-2203931, S2-2203968, S2-2204276, S2-2204552. Postponed","agenda_item_sort_order":52,"ainumber":"8.9","ainame":"Architectural enhancements for 5G multicast-broadcast services (5MBS)","tdoc_agenda_sort_order":12340,"status":"postponed","reservation_date":"2022-04-21 14:48:20","uploaded":"2022-04-22 05:13:38","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"CT WG4","lsoriginalls":"C3-222578","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_151E_Electronic_2022-05\/Docs\/S2-2203646.zip","group":"S2","meeting":"S2-151-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2203647","title":"LS on Clarifications on Nmbstf_MBSDistributionSession Service","source":"CT WG4","contact":"Varini Gupta","contact-id":83459,"tdoctype":"LS in","for":"Information","abstract":"CT WG4 has started work on SBI specification of the Nmbstf_MBSDistributionSession service and would like to request following clarifications from SA WG4: Background: Table 4.5.6-3 of TS 26.502 specifies that 'MBSF' is the assigner of the MBSTF tunnel endpoint address. On the other hand, Annex B.3.1 and B.3.2 specify that the 'MBSTF' provides the MBSTF tunnel endpoint address to the MBS Application Provider (AF\/AS). It is CT WG4's understanding that the MBSTF tunnel endpoint address is assigned by MBSTF, and hence may be present in the response sent by MBSTF upon receiving the Nmbstf_MBSDistributionSession_Create request from the MBSF. {. . .}","secretary_remarks":"Noted","agenda_item_sort_order":52,"ainumber":"8.9","ainame":"Architectural enhancements for 5G multicast-broadcast services (5MBS)","tdoc_agenda_sort_order":12450,"status":"noted","reservation_date":"2022-04-21 14:48:20","uploaded":"2022-04-22 05:13:38","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG4","Cc":"CT WG3, SA WG2","lsoriginalls":"C4-222300","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_151E_Electronic_2022-05\/Docs\/S2-2203647.zip","group":"S2","meeting":"S2-151-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2203652","title":"LS from SA WG5: LS on Traffic usage reporting on 5MBS service","source":"SA WG5","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Information","abstract":"SA WG5 thanks CT WG4 for their LS. There is currently no work item for 5MBS in SA WG5, and the TS 32.273 which is specifies 'Multimedia Broadcast and Multicast Service (MBMS) charging' covering LTE have not been updated to cover 5G. There is however work done on charging for network exposure in TS 32.254 'Exposure function northbound Application Program Interfaces (APIs) charging' which should cover any 5MBS requirements in regards to the interaction with NEF and 5G connectivity charging TS 32.255 'Charging management; 5G Data connectivity domain charging' which should cover collection of usage data for 5MBS. To support the 5MBS would require a study or work item in SA WG5 and could at earliest be included in rel-18, since rel-17 is closed for functional changes.","secretary_remarks":"Noted","agenda_item_sort_order":52,"ainumber":"8.9","ainame":"Architectural enhancements for 5G multicast-broadcast services (5MBS)","tdoc_agenda_sort_order":12510,"status":"noted","reservation_date":"2022-04-21 14:48:20","uploaded":"2022-04-22 05:13:38","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG4","Cc":"SA WG2","lsoriginalls":"S5-222812","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_151E_Electronic_2022-05\/Docs\/S2-2203652.zip","group":"S2","meeting":"S2-151-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2203659","title":"LS from SA WG4: LS on Security architecture for 5G multicast\/broadcast services","source":"SA WG4","contact":"Richard Bradbury","contact-id":82569,"tdoctype":"LS in","for":"Information","abstract":"SA WG4 provides a progress update on the 5MBUSA work item and has some questions regarding the security architecture for 5G multicast\/broadcast services.","secretary_remarks":"Noted","agenda_item_sort_order":52,"ainumber":"8.9","ainame":"Architectural enhancements for 5G multicast-broadcast services (5MBS)","tdoc_agenda_sort_order":12550,"status":"noted","reservation_date":"2022-04-21 14:48:20","uploaded":"2022-04-29 06:27:12","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG3","Cc":"SA WG2","lsoriginalls":"S4-220531","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_151E_Electronic_2022-05\/Docs\/S2-2203659.zip","group":"S2","meeting":"S2-151-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2203660","title":"LS from SA WG4: Response LS on maximum number of MBS sessions that can be associated to a PDU session","source":"SA WG4","contact":"Thorsten Lohmar","contact-id":59317,"tdoctype":"LS in","for":"Action","abstract":"SA WG4 thanks SA WG2 for their LS in S4-220456 (S2-2109171). SA WG4 has discussed it and reviewed also the feedback from RAN WG2 and SA WG6 on the subject. SA WG4 would like to indicate to SA WG2 and CT WG1, that SA WG4 has no specific use-cases, which require a high number of simultaneously joined MBS Sessions at the same time. However, the maximal number of four is potentially a bit limiting to be future proof for upcoming services and SA WG4 agrees with the SA WG6 response. SA WG4 kindly asks SA WG2 to take this into consideration to decide the maximum number of MBS sessions that can be associated to a PDU session. Action: SA WG4 kindly asks SA WG2 and CT WG1 to take the above information into account.","secretary_remarks":"Noted","agenda_item_sort_order":52,"ainumber":"8.9","ainame":"Architectural enhancements for 5G multicast-broadcast services (5MBS)","tdoc_agenda_sort_order":12530,"status":"noted","reservation_date":"2022-04-21 14:48:20","uploaded":"2022-04-29 06:27:12","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, CT WG1","Cc":"SA WG6, RAN WG2","lsoriginalls":"S4-220567","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_151E_Electronic_2022-05\/Docs\/S2-2203660.zip","group":"S2","meeting":"S2-151-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2203663","title":"LS from SA WG4: Response LS on Clarifications on Nmbstf_MBCDistributionSession service","source":"SA WG4","contact":"Richard Bradbury","contact-id":82569,"tdoctype":"LS in","for":"Action","abstract":"SA WG4 provides responses to clarification questions from CT WG4 concerning the Nmbstf_MBSDistributionSession service exposed by the MBSTF to the MBSF at reference on Nmb2, and advises CT WG4 of a forthcoming Change Request to TS 26.502. {. . .} Action: SA WG4 kindly asks SA WG2 to review SA WG4's feedback in section 1 above and confirm whether SA WG4's understanding is correct, in particular SA WG4's answer to question 2. Action: SA WG4 kindly asks SA WG2 to confirm that it is reasonable for the MBSTF to set a DS Code Point on the multicast IP packets it generates or forwards at Nmb9. Additionally, SA WG4 asks whether it is reasonable for this DS Code Point to be provisioned by the AF\/AS at Nmb10\/Nmb5 or whether the MBSF should determine the DS Code Point to use for traffic labelling in order to guarantee correct end-to-end multicast QoS operation between the AF\/AS and the UE.","secretary_remarks":"Responses drafted in S2-2203929, S2-2204261. Final response in S2-2204742","agenda_item_sort_order":52,"ainumber":"8.9","ainame":"Architectural enhancements for 5G multicast-broadcast services (5MBS)","tdoc_agenda_sort_order":12440,"status":"replied to","reservation_date":"2022-04-21 14:48:20","uploaded":"2022-05-03 12:59:53","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, CT WG4","Cc":"SA WG3","lsoriginalls":"S4-220575","lsreply":"S2-2204742","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_151E_Electronic_2022-05\/Docs\/S2-2203663.zip","group":"S2","meeting":"S2-151-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2203669","title":"LS from CT WG4: LS on Clarification on MBS Security Keys","source":"CT WG4","contact":"Varini Gupta","contact-id":83459,"tdoctype":"LS in","for":"Information","abstract":"CT WG4 is developing support of MBS Keys distribution via control place procedure as specified in Annex W of 3GPP TS 33.501, and would like to request following clarifications from SA WG3: {. . .}","secretary_remarks":"Postponed","agenda_item_sort_order":52,"ainumber":"8.9","ainame":"Architectural enhancements for 5G multicast-broadcast services (5MBS)","tdoc_agenda_sort_order":12290,"status":"postponed","reservation_date":"2022-04-21 14:48:21","uploaded":"2022-05-18 08:29:46","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG3","Cc":"CT WG1, CT WG3","lsoriginalls":"C4-223302","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_151E_Electronic_2022-05\/Docs\/S2-2203669.zip","group":"S2","meeting":"S2-151-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2203926","title":"Clarifications on traffic usage reporting and charging","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify the collection and reporting of MBS specific charging information are not specified in this release and remove the traffic usage reporting related text","secretary_remarks":"Approved","agenda_item_sort_order":52,"ainumber":"8.9","ainame":"Architectural enhancements for 5G multicast-broadcast services (5MBS)","tdoc_agenda_sort_order":12520,"status":"agreed","reservation_date":"2022-05-05 18:49:40","uploaded":"2022-05-06 22:27:40","revisionof":"","revisedto":"","release":"Rel-17","crspec":"23.247","crspecversion":"17.2.0","workitem":[{"winame":"5MBS"}],"crnumber":117.0,"crrevision":"","crcategory":"F","tsg_crp":"SP-220395","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_151E_Electronic_2022-05\/Docs\/S2-2203926.zip","group":"S2","meeting":"S2-151-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2203927","title":"Clarification of MBS data forwarding","source":"[Huawei, HiSilicon,] Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: In clause 7.2.3.2 and 7.2.3.3, the detail of how to perform the MBS data forwading, add a reference to clause 7.2.3.5. Also, remove the Editor s Note Details on data forwarding, if applicable, needs to wait for RAN WGs . Per the RAN WG3","secretary_remarks":"Revision of (Noted) S2-2202536. Noted","agenda_item_sort_order":52,"ainumber":"8.9","ainame":"Architectural enhancements for 5G multicast-broadcast services (5MBS)","tdoc_agenda_sort_order":12250,"status":"noted","reservation_date":"2022-05-05 18:49:41","uploaded":"2022-05-06 22:27:40","revisionof":"S2-2202536","revisedto":"","release":"Rel-17","crspec":"23.247","crspecversion":"17.2.0","workitem":[{"winame":"5MBS"}],"crnumber":90.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_151E_Electronic_2022-05\/Docs\/S2-2203927.zip","group":"S2","meeting":"S2-151-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2203928","title":"[DRAFT] Reply LS on further outstanding issues in TS 23.247","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"LS out","for":"Approval","abstract":"Reply LS to RAN WG3 on the feedback on outstanding issues. Response to S2-2203653","secretary_remarks":"Response to S2-2203653. Noted","agenda_item_sort_order":52,"ainumber":"8.9","ainame":"Architectural enhancements for 5G multicast-broadcast services (5MBS)","tdoc_agenda_sort_order":12230,"status":"noted","reservation_date":"2022-05-05 18:49:42","uploaded":"2022-05-06 22:27:40","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"5MBS"},{"winame":" NR_MBS-Core"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG3 RAN WG2","Cc":"CC: RAN WG20","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_151E_Electronic_2022-05\/Docs\/S2-2203928.zip","group":"S2","meeting":"S2-151-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2203929","title":"[DRAFT] Reply LS on Clarifications on Nmbstf_MBSDistributionSession service","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"LS out","for":"Approval","abstract":"Reply LS to SA WG4, CT WG4, CT WG3 on Clarifications on Nmbstf_MBSDistributionSession service. Response to S2-2203663","secretary_remarks":"Response to S2-2203663. r05 agreed. Revised to S2-2204742, merging S2-2204058","agenda_item_sort_order":52,"ainumber":"8.9","ainame":"Architectural enhancements for 5G multicast-broadcast services (5MBS)","tdoc_agenda_sort_order":12460,"status":"revised","reservation_date":"2022-05-05 18:49:42","uploaded":"2022-05-06 22:27:40","revisionof":"","revisedto":"S2-2204742","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"5MBS"},{"winame":" 5MBUSA"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG4, SA WG4, CT WG3 SA WG3","Cc":"CC: SA WG3","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_151E_Electronic_2022-05\/Docs\/S2-2203929.zip","group":"S2","meeting":"S2-151-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2203930","title":"Discussion on Questions on PCC aspects related to 5MBS.","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"discussion","for":"Agreement","abstract":"This paper discusses the questions on MBS PCC from CT WG3 and proposes a simplification.","secretary_remarks":"CC#1: Marked Not Handled. Noted","agenda_item_sort_order":52,"ainumber":"8.9","ainame":"Architectural enhancements for 5G multicast-broadcast services (5MBS)","tdoc_agenda_sort_order":12390,"status":"noted","reservation_date":"2022-05-05 18:49:42","uploaded":"2022-05-06 22:27:40","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"5MBS"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_151E_Electronic_2022-05\/Docs\/S2-2203930.zip","group":"S2","meeting":"S2-151-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2203931","title":"[DRAFT] Reply to LS on PCC aspects related to 5MBS","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"LS out","for":"Approval","abstract":"This LS reply answers the CT WG3 questions. Response to S2-2203646","secretary_remarks":"Response to S2-2203646 CC#1: Marked Not Handled. Postponed","agenda_item_sort_order":52,"ainumber":"8.9","ainame":"Architectural enhancements for 5G multicast-broadcast services (5MBS)","tdoc_agenda_sort_order":12350,"status":"postponed","reservation_date":"2022-05-05 18:49:42","uploaded":"2022-05-06 22:27:40","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"5MBS"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG3","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_151E_Electronic_2022-05\/Docs\/S2-2203931.zip","group":"S2","meeting":"S2-151-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2203932","title":"Update of PCC procedure for 5MBS","source":"[Huawei, HiSilicon,] Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Note that changes made in SA WG2#151E is yellow highlighted Replace service requirement with service information , or QoS related information and Flow Description Clause 5.3.2.1, remove The PCF can receive MBS information from AF, NEF o","secretary_remarks":"Revision of (Noted) S2-2202687. Original zip file corrupt CC#1: Marked Not Handled. Postponed","agenda_item_sort_order":52,"ainumber":"8.9","ainame":"Architectural enhancements for 5G multicast-broadcast services (5MBS)","tdoc_agenda_sort_order":12400,"status":"postponed","reservation_date":"2022-05-05 18:49:43","uploaded":"2022-05-06 22:27:40","revisionof":"S2-2202687","revisedto":"","release":"Rel-17","crspec":"23.247","crspecversion":"17.2.0","workitem":[{"winame":"5MBS"}],"crnumber":109.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_151E_Electronic_2022-05\/Docs\/S2-2203932.zip","group":"S2","meeting":"S2-151-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2203968","title":"[DRAFT] Reply LS on Questions on PCC aspects related to 5MBS","source":"Nokia, Nokia Shanghai Bell","contact":"Thomas Belling","contact-id":68266,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG3. CC: CT WG4. Attachments: Revision of S2-2203969. Response to S2-2203646","secretary_remarks":"Response to S2-2203646. Postponed","agenda_item_sort_order":52,"ainumber":"8.9","ainame":"Architectural enhancements for 5G multicast-broadcast services (5MBS)","tdoc_agenda_sort_order":12360,"status":"postponed","reservation_date":"2022-05-05 22:54:41","uploaded":"2022-05-06 22:47:34","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"5MBS"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG3 CT WG4","Cc":"CC: CT WG4","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_151E_Electronic_2022-05\/Docs\/S2-2203968.zip","group":"S2","meeting":"S2-151-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2203969","title":"Corrections related to PCC aspects related to 5MBS","source":"Nokia, Nokia Shanghai-Bell","contact":"Thomas Belling","contact-id":68266,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The parameters of the Nnef_MBSSession_Create service operation and the Npcf_MBSPolicyAuthorization_Create service operation are clarified: Service requirements provided by the AF to the NEF include the service description provided as pa","secretary_remarks":"Postponed","agenda_item_sort_order":52,"ainumber":"8.9","ainame":"Architectural enhancements for 5G multicast-broadcast services (5MBS)","tdoc_agenda_sort_order":12410,"status":"postponed","reservation_date":"2022-05-05 23:07:28","uploaded":"2022-05-06 22:47:34","revisionof":"","revisedto":"","release":"Rel-17","crspec":"23.247","crspecversion":"17.2.0","workitem":[{"winame":"5MBS"}],"crnumber":118.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_151E_Electronic_2022-05\/Docs\/S2-2203969.zip","group":"S2","meeting":"S2-151-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2203970","title":"[DRAFT] Reply LS on LS on the impact of MSK update on MBS multicast session update procedure","source":"Nokia","contact":"Thomas Belling","contact-id":68266,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG1, SA WG3, SA WG4. CC: CT WG4. Response to S2-2203631","secretary_remarks":"Revision of (Postponed) S2-2202984. Response to S2-2203631. r02 agreed. Revised to S2-2204741.","agenda_item_sort_order":52,"ainumber":"8.9","ainame":"Architectural enhancements for 5G multicast-broadcast services (5MBS)","tdoc_agenda_sort_order":12310,"status":"revised","reservation_date":"2022-05-05 23:23:35","uploaded":"2022-05-06 22:47:34","revisionof":"S2-2202984","revisedto":"S2-2204741","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1, SA WG3, SA WG4 CT WG4","Cc":"CC: CT WG4","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_151E_Electronic_2022-05\/Docs\/S2-2203970.zip","group":"S2","meeting":"S2-151-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2203971","title":"MSK update on MBS multicast session update procedure.","source":"Nokia, Nokia Shanghai-Bell","contact":"Thomas Belling","contact-id":68266,"tdoctype":"discussion","for":"Discussion","abstract":"This discussion paper provides some background for the draft LS in S2-2203970","secretary_remarks":"Sources missing from document. Noted","agenda_item_sort_order":52,"ainumber":"8.9","ainame":"Architectural enhancements for 5G multicast-broadcast services (5MBS)","tdoc_agenda_sort_order":12330,"status":"noted","reservation_date":"2022-05-05 23:31:02","uploaded":"2022-05-06 22:47:34","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_151E_Electronic_2022-05\/Docs\/S2-2203971.zip","group":"S2","meeting":"S2-151-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2204260","title":"Tunnel between MBSTF and MB-UPF","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarified that the user plane between MBSTF and MB-UPF is unicast tunnel.","secretary_remarks":"r04 agreed. Revised to S2-2204743.","agenda_item_sort_order":52,"ainumber":"8.9","ainame":"Architectural enhancements for 5G multicast-broadcast services (5MBS)","tdoc_agenda_sort_order":12490,"status":"revised","reservation_date":"2022-05-06 09:49:05","uploaded":"2022-05-06 13:03:25","revisionof":"","revisedto":"S2-2204743","release":"Rel-17","crspec":"23.247","crspecversion":"17.2.0","workitem":[{"winame":"5MBS"}],"crnumber":119.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_151E_Electronic_2022-05\/Docs\/S2-2204260.zip","group":"S2","meeting":"S2-151-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2204261","title":"[DRAFT] Reply LS to SA WG4 regarding MB-UPF and MBSTF distribution","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"LS out","for":"Approval","abstract":"Reply LS to SA WG4 regarding MB-UPF and MBSTF distribution. Response to S2-2203663","secretary_remarks":"Response to S2-2203663. Merged into S2-2204805","agenda_item_sort_order":52,"ainumber":"8.9","ainame":"Architectural enhancements for 5G multicast-broadcast services (5MBS)","tdoc_agenda_sort_order":12480,"status":"merged","reservation_date":"2022-05-06 09:49:07","uploaded":"2022-05-06 13:03:25","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"5MBS"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG4, CT WG4 SA WG3","Cc":"CC: SA WG3","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_151E_Electronic_2022-05\/Docs\/S2-2204261.zip","group":"S2","meeting":"S2-151-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2204262","title":"[DRAFT] Response to LS on UE pre-configuration","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"LS out","for":"Approval","abstract":"Reply LS on pre-configuration. Response to S2-2203629","secretary_remarks":"Revision of (Postponed) S2-2202357. Response to S2-2203629. r00 agreed. Revised to S2-2204721. CC#3: S2-2204262 was postponed.","agenda_item_sort_order":52,"ainumber":"8.9","ainame":"Architectural enhancements for 5G multicast-broadcast services (5MBS)","tdoc_agenda_sort_order":12170,"status":"postponed","reservation_date":"2022-05-06 09:49:07","uploaded":"2022-05-06 13:03:25","revisionof":"S2-2202357","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"5MBS"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT CT WG1, CT WG4, SA WG4, RAN WG2","Cc":"CC: CT WG1, CT WG4, SA WG4, RAN WG2","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_151E_Electronic_2022-05\/Docs\/S2-2204262.zip","group":"S2","meeting":"S2-151-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2204263","title":"Need for pre-configured USD and service announcement","source":"Huawei, HiSilicon [Qualcomm]","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarifies reference to preconfigured parameters Corrects reference to service announcement\/USD and methods it can be obtained inline with TS 26.502 and TS 26.517","secretary_remarks":"Revision of (Noted) S2-2202000. CC#3: This was postponed.","agenda_item_sort_order":52,"ainumber":"8.9","ainame":"Architectural enhancements for 5G multicast-broadcast services (5MBS)","tdoc_agenda_sort_order":12200,"status":"postponed","reservation_date":"2022-05-06 09:49:07","uploaded":"2022-05-06 13:03:25","revisionof":"S2-2202000","revisedto":"","release":"Rel-17","crspec":"23.247","crspecversion":"17.2.0","workitem":[{"winame":"5MBS"}],"crnumber":100.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_151E_Electronic_2022-05\/Docs\/S2-2204263.zip","group":"S2","meeting":"S2-151-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2204276","title":"[DRAFT] Response to LS on Questions on PCC aspects related to 5MBS","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"LS out","for":"Approval","abstract":"Answers the questions in the LS. Response to S2-2203646","secretary_remarks":"Response to S2-2203646. Postponed","agenda_item_sort_order":52,"ainumber":"8.9","ainame":"Architectural enhancements for 5G multicast-broadcast services (5MBS)","tdoc_agenda_sort_order":12370,"status":"postponed","reservation_date":"2022-05-06 10:00:25","uploaded":"2022-05-06 15:47:36","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"5MBS"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG3 CT WG4","Cc":"CC: CT WG4","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_151E_Electronic_2022-05\/Docs\/S2-2204276.zip","group":"S2","meeting":"S2-151-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2204303","title":"[DRAFT] Response LS on further outstanding issues in TS 23.247","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"LS out","for":"Approval","abstract":"Response LS on further outstanding issues in TS 23.247. Response to S2-2203635","secretary_remarks":"Response to S2-2203635. CC#3: Postponed","agenda_item_sort_order":52,"ainumber":"8.9","ainame":"Architectural enhancements for 5G multicast-broadcast services (5MBS)","tdoc_agenda_sort_order":12240,"status":"postponed","reservation_date":"2022-05-06 10:29:33","uploaded":"2022-05-06 15:25:39","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"5MBS"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG3, RAN WG2","Cc":"","lsoriginalls":"R3-222867","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_151E_Electronic_2022-05\/Docs\/S2-2204303.zip","group":"S2","meeting":"S2-151-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2204304","title":"Clarification of MBS data forwarding","source":"Huawei, HiSilicon, Nokia, Nokia Shanghai-Bell, CATT, OPPO VIVO, CBN","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: In clause 7.2.3.2 and 7.2.3.3, the detail of how to perform the MBS data forwading, add a reference to clause 7.2.3.5. Also, remove the Editor s Note Details on data forwarding, if applicable, needs to wait for RAN WGs . Per the RAN WG3","secretary_remarks":"Revision of (Noted) S2-2202536. r11 agreed. Revised to S2-2204740, merging S2-2204200","agenda_item_sort_order":52,"ainumber":"8.9","ainame":"Architectural enhancements for 5G multicast-broadcast services (5MBS)","tdoc_agenda_sort_order":12260,"status":"revised","reservation_date":"2022-05-06 10:29:33","uploaded":"2022-05-06 15:25:39","revisionof":"S2-2202536","revisedto":"S2-2204740","release":"Rel-17","crspec":"23.247","crspecversion":"17.2.0","workitem":[{"winame":"5MBS"}],"crnumber":90.0,"crrevision":3.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_151E_Electronic_2022-05\/Docs\/S2-2204304.zip","group":"S2","meeting":"S2-151-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2204314","title":"Update of PCC procedure for 5MBS","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The following updates and changes are proposed for the MBS session management procedures: The structure of the PCC procedures for 5MBS are changed so that the NEF MB-PCF interaction happens before the NEF MB-SMF interaction. The PCC pro","secretary_remarks":"Revision of (Noted) S2-2202687. Postponed","agenda_item_sort_order":52,"ainumber":"8.9","ainame":"Architectural enhancements for 5G multicast-broadcast services (5MBS)","tdoc_agenda_sort_order":12420,"status":"postponed","reservation_date":"2022-05-06 10:36:37","uploaded":"2022-05-06 15:47:36","revisionof":"S2-2202687","revisedto":"","release":"Rel-17","crspec":"23.247","crspecversion":"17.2.0","workitem":[{"winame":"5MBS"}],"crnumber":109.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_151E_Electronic_2022-05\/Docs\/S2-2204314.zip","group":"S2","meeting":"S2-151-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2204319","title":"Need for pre-configured USD and service announcement","source":"Qualcomm Incorporated, Orange, Ericsson, Deutsche Telekom, AT&T","contact":"Haris Zisimopoulos","contact-id":84603,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarifies reference to preconfigured parameters Corrects reference to service announcement\/USD and methods it can be obtained inline with TS 26.502 and TS 26.517","secretary_remarks":"Revision of (Noted) S2-2202000. CC#3: Postponed","agenda_item_sort_order":52,"ainumber":"8.9","ainame":"Architectural enhancements for 5G multicast-broadcast services (5MBS)","tdoc_agenda_sort_order":12210,"status":"postponed","reservation_date":"2022-05-06 10:53:25","uploaded":"2022-05-06 17:54:11","revisionof":"S2-2202000","revisedto":"","release":"Rel-17","crspec":"23.247","crspecversion":"17.2.0","workitem":[{"winame":"5MBS"}],"crnumber":100.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_151E_Electronic_2022-05\/Docs\/S2-2204319.zip","group":"S2","meeting":"S2-151-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2204330","title":"[DRAFT] Reply LS on parameters preconfigured in the UE to receive MBS service","source":"Qualcomm","contact":"Haris Zisimopoulos","contact-id":84603,"tdoctype":"LS out","for":"Approval","abstract":"Responds to S2-223629. Response to S2-2203629","secretary_remarks":"Response to S2-2203629. CC#3: This was postponed.","agenda_item_sort_order":52,"ainumber":"8.9","ainame":"Architectural enhancements for 5G multicast-broadcast services (5MBS)","tdoc_agenda_sort_order":12190,"status":"postponed","reservation_date":"2022-05-06 10:59:52","uploaded":"2022-05-06 17:54:11","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"5MBS"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT, CT WG1 CT WG4, SA WG4, RAN WG2, CT WG6","Cc":"CC: CT WG4, SA WG4, RAN WG2, CT WG6","lsoriginalls":"S2-223629","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_151E_Electronic_2022-05\/Docs\/S2-2204330.zip","group":"S2","meeting":"S2-151-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2204552","title":"[DRAFT] Reply LS On Questions on PCC aspects related to 5MBS","source":"ZTE","contact":"Zhendong Li","contact-id":38521,"tdoctype":"LS out","for":"Approval","abstract":"Proposes a Reply LS On Questions on PCC aspects related to 5MBS. Response to S2-2203646","secretary_remarks":"Response to S2-2203646. Postponed","agenda_item_sort_order":52,"ainumber":"8.9","ainame":"Architectural enhancements for 5G multicast-broadcast services (5MBS)","tdoc_agenda_sort_order":12380,"status":"postponed","reservation_date":"2022-05-06 15:25:01","uploaded":"2022-05-06 15:49:44","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"5MBS"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG3","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_151E_Electronic_2022-05\/Docs\/S2-2204552.zip","group":"S2","meeting":"S2-151-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2204553","title":"Clarification on the PCC part.","source":"ZTE","contact":"Zhendong Li","contact-id":38521,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify theis no restriction for PCF querying the UDR. Adding Npcf_MBSPolicyControl_Update service operation, which is missing. Clarify the application identifier in Npcf_MBSPolicyAuthorization_Create service operation.","secretary_remarks":"Postponed","agenda_item_sort_order":52,"ainumber":"8.9","ainame":"Architectural enhancements for 5G multicast-broadcast services (5MBS)","tdoc_agenda_sort_order":12430,"status":"postponed","reservation_date":"2022-05-06 15:25:01","uploaded":"2022-05-06 15:49:44","revisionof":"","revisedto":"","release":"Rel-17","crspec":"23.247","crspecversion":"17.2.0","workitem":[{"winame":"5MBS"}],"crnumber":121.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_151E_Electronic_2022-05\/Docs\/S2-2204553.zip","group":"S2","meeting":"S2-151-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2204554","title":"Clarification of MBS data forwarding","source":"[Huawei, HiSilicon, Nokia, Nokia Shanghai-Bell, ] ZTE","contact":"Zhendong Li","contact-id":38521,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: In clause 7.2.3.2 and 7.2.3.3, the detail of how to perform the MBS data forwading, add a reference to clause 7.2.3.5. Also, remove the Editor s Note Details on data forwarding, if applicable, needs to wait for RAN WGs . Per the RAN WG3","secretary_remarks":"Revision of (Noted) S2-2202536. Merged into S2-2205172","agenda_item_sort_order":52,"ainumber":"8.9","ainame":"Architectural enhancements for 5G multicast-broadcast services (5MBS)","tdoc_agenda_sort_order":12280,"status":"merged","reservation_date":"2022-05-06 15:25:02","uploaded":"2022-05-06 15:49:44","revisionof":"S2-2202536","revisedto":"","release":"Rel-17","crspec":"23.247","crspecversion":"17.2.0","workitem":[{"winame":"5MBS"}],"crnumber":90.0,"crrevision":4.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_151E_Electronic_2022-05\/Docs\/S2-2204554.zip","group":"S2","meeting":"S2-151-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2204721","title":"[DRAFT] Response to LS on UE pre-configuration","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"LS out","for":"Approval","abstract":"WITHDRAWN: Reply LS on pre-configuration. Response to S2-2203629","secretary_remarks":"Revision of S2-2204262r00. CC#3: This was withdrawn","agenda_item_sort_order":52,"ainumber":"8.9","ainame":"Architectural enhancements for 5G multicast-broadcast services (5MBS)","tdoc_agenda_sort_order":12180,"status":"withdrawn","reservation_date":"2022-05-23 07:09:35","uploaded":null,"revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"5MBS"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT CT WG1, CT WG4, SA WG4, RAN WG2","Cc":"CC: CT WG1, CT WG4, SA WG4, RAN WG2","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-151-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2204740","title":"Clarification of MBS data forwarding","source":"Huawei, HiSilicon, Nokia, Nokia Shanghai-Bell, CATT, OPPO VIVO, CBN, ZTE","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: In clause 7.2.3.2 and 7.2.3.3, the detail of how to perform the MBS data forwading, add a reference to clause 7.2.3.5. Also, remove the Editor s Note Details on data forwarding, if applicable, needs to wait for RAN WGs . Per the RAN WG3","secretary_remarks":"Revision of S2-2204304r11, merging S2-2204200. Approved","agenda_item_sort_order":52,"ainumber":"8.9","ainame":"Architectural enhancements for 5G multicast-broadcast services (5MBS)","tdoc_agenda_sort_order":12270,"status":"agreed","reservation_date":"2022-05-23 07:09:45","uploaded":"2022-05-24 08:11:20","revisionof":"S2-2204304","revisedto":"","release":"Rel-17","crspec":"23.247","crspecversion":"17.2.0","workitem":[{"winame":"5MBS"}],"crnumber":90.0,"crrevision":5.0,"crcategory":"F","tsg_crp":"SP-220395","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_151E_Electronic_2022-05\/Docs\/S2-2204740.zip","group":"S2","meeting":"S2-151-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2204741","title":"Reply LS on the impact of MSK update on MBS multicast session update procedure","source":"SA WG2","contact":"Thomas Belling","contact-id":68266,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG1, SA WG3, SA WG4. CC: CT WG4","secretary_remarks":"Revision of S2-2203970r02. Approved","agenda_item_sort_order":52,"ainumber":"8.9","ainame":"Architectural enhancements for 5G multicast-broadcast services (5MBS)","tdoc_agenda_sort_order":12320,"status":"approved","reservation_date":"2022-05-23 07:09:46","uploaded":"2022-05-24 08:11:20","revisionof":"S2-2203970","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"5MBS"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2203631","lsto":"CT WG1, SA WG3, SA WG4","Cc":"CT WG4","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_151E_Electronic_2022-05\/Docs\/S2-2204741.zip","group":"S2","meeting":"S2-151-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2204742","title":"Reply LS on Clarifications on Nmbstf_MBSDistributionSession service","source":"SA WG2","contact":"Robbie Ling","contact-id":37246,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG4, SA WG4, CT WG3. CC: SA WG3. Attachments: S2-2203663","secretary_remarks":"Revision of S2-2203929r05, merging S2-2204058. Approved","agenda_item_sort_order":52,"ainumber":"8.9","ainame":"Architectural enhancements for 5G multicast-broadcast services (5MBS)","tdoc_agenda_sort_order":12470,"status":"approved","reservation_date":"2022-05-23 07:09:46","uploaded":"2022-05-24 08:11:20","revisionof":"S2-2203929","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"5MBS"},{"winame":" 5MBUSA"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2203663","lsto":"CT WG4, SA WG4, CT WG3","Cc":"SA WG3","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_151E_Electronic_2022-05\/Docs\/S2-2204742.zip","group":"S2","meeting":"S2-151-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2204743","title":"Tunnel between MBSTF and MB-UPF","source":"Huawei, HiSilicon, Ericsson","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarified that the user plane between MBSTF and MB-UPF is unicast tunnel.","secretary_remarks":"Revision of S2-2204260r04. Approved","agenda_item_sort_order":52,"ainumber":"8.9","ainame":"Architectural enhancements for 5G multicast-broadcast services (5MBS)","tdoc_agenda_sort_order":12500,"status":"agreed","reservation_date":"2022-05-23 07:09:46","uploaded":"2022-05-24 08:11:20","revisionof":"S2-2204260","revisedto":"","release":"Rel-17","crspec":"23.247","crspecversion":"17.2.0","workitem":[{"winame":"5MBS"}],"crnumber":119.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-220395","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_151E_Electronic_2022-05\/Docs\/S2-2204743.zip","group":"S2","meeting":"S2-151-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]