[{"name":"S2-2208108","title":"LS from SA WG4: Reply LS on 5MBS User Services","source":"SA WG4","contact":"Thorsten Lohmar","contact-id":59317,"tdoctype":"LS in","for":"Action","abstract":"SA WG4 thanks SA WG2 for the LS on 5MBS User Services. SA WG4 discussed the LS and would like to provide following feedback: {. . .} Action: SA WG4 respectfully asks SA WG2 to take the above information into account. Specifically, SA WG4 invites SA WG2 to provide feedback on the question on the distribution of Group Communication traffic via 5GC and EPC (see item 2).","secretary_remarks":"Revision of Postponed S2-2205450 from S2#152-e. Responses drafted in S2-2208329, S2-2208720. Final response in S2-2209281","agenda_item_sort_order":52,"ainumber":"8.9","ainame":"Architectural enhancements for 5G multicast-broadcast services (5MBS)","tdoc_agenda_sort_order":12030,"status":"replied to","reservation_date":"2022-09-21 05:20:40","uploaded":"2022-09-21 08:06:27","revisionof":"S2-2205450","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"SA WG6, CT WG3","lsoriginalls":"S4-220828","lsreply":"S2-2209281, S2-2209281","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_153E_Electronic_2022-10\/Docs\/S2-2208108.zip","group":"S2","meeting":"S2-153-e","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2208115","title":"LS on modifications to MBS User Services architecture","source":"SA WG4","contact":"Richard Bradbury","contact-id":82569,"tdoctype":"LS in","for":"Information","abstract":"SA WG4 is pleased to attach a Change Request to TS 26.502 agreed at the SA WG4#120-e meeting. The change provides updates to the static domain model for MBS User Services made in response to feedback from CT WG3 and CT WG4 delegates since publication of the V17.1.0 of the TS at the end of the previous meeting cycle. It also provides definitions of events to be exposed over the Nmbstf and Nmbsf services. SA WG4 would like to thank CT WG3 and CT WG4 for the feedback received and for the constructive discussions held over recent weeks between rapporteurs and delegates of the three Working Groups. SA WG4 feels that this approach has facilitated a timely conclusion of our respective work items on Multicast Broadcast Services in the restricted time available, and provides a good template for future co-operation.","secretary_remarks":"Revision of Postponed S2-2208096 from S2#152-e. Noted","agenda_item_sort_order":52,"ainumber":"8.9","ainame":"Architectural enhancements for 5G multicast-broadcast services (5MBS)","tdoc_agenda_sort_order":12100,"status":"noted","reservation_date":"2022-09-21 05:20:40","uploaded":"2022-09-21 08:06:27","revisionof":"S2-2208096","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG4, CT WG3","Cc":"SA WG2","lsoriginalls":"S4-221119","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_153E_Electronic_2022-10\/Docs\/S2-2208115.zip","group":"S2","meeting":"S2-153-e","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2208124","title":"LS from CT WG1: Reply LS on AS-NAS layer interactions for MBS","source":"CT WG1","contact":"Christian Herrero-Veron","contact-id":45210,"tdoctype":"LS in","for":"Information","abstract":"CT WG1 thanks RAN WG2 for their LS on AS-NAS layer interactions for MBS and CT WG1 would like to provide the following information: 1. CT WG1 makes distinction in their specifications between the NAS, i.e., control-plane signalling, and the upper layers, i.e., applications. The NAS is not aware of broadcast MBS sessions. 2. CT WG1 confirms that the TMGI is needed in the NAS. For Idle mode, the TMGI is needed as the NAS needs it to determine paging response. For RRC Inactive, it is CT WG1 s understanding that the RAN paging is the responsibility of the AS, and therefore there is no need from an NAS perspective to be informed of the TMSI in this case. However, the NAS needs an indication from the AS when the UE has transitioned to RRC connected mode. 3. CT WG1 confirms that indication of establishment of user plane resources is needed in the NAS for multicast MBS sessions. Upper layers (i.e., application layer) may use this indication towards the user. 4. CT WG1 confirms that indication of release of user plane resources is needed in the NAS for multicast MBS sessions. Upper layers (i.e., application layer) may use this indication towards the user. CT WG1 does not see the need of more indications than the above mentioned at this moment in time. Action: CT WG1 would like to request RAN WG2, SA WG2 to take the information provided in this LS 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":12310,"status":"noted","reservation_date":"2022-09-21 05:20:41","uploaded":"2022-09-22 05:01:53","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2","Cc":"","lsoriginalls":"C1-225249","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_153E_Electronic_2022-10\/Docs\/S2-2208124.zip","group":"S2","meeting":"S2-153-e","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2208131","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 the LS reply on 5MBS User Services, the joint SA WG4\/CT WG3\/CT WG4 rapporteurs and delegates discussions on the open issues effectively, also the immediate updates on the agreed TS 26.502 CR 0007r1 at the SA WG4#120-e meeting, so that CT WG3 could update our implementation at once. CT WG3 would like to update the CT WG3 related implementation status as below: CT WG3 Feedback 1 on Nnef_MBSUserService and Nnef_MBSUserDataIngestSession services: CT WG3 has implemented Nnef_MBSUserService and Nnef_MBSUserDataIngestSession services in TS 29.522 to expose the similar (or even identical) APIs as the MBSF services. The CR package attached reflects the implementations which is planned to be submitted for approval in CT#97-e plenary, which is estimated to be included in TS 29.522 v17.7.0 in September. CT WG3 Feedback 2 on Nmbsf_MBSUserService and Nmbsf_MBSUserDataIngestSession services: Upon the SA WG4 specificiations, joint SA WG3\/CT WG3\/CT WG4 discussions and related SA WG4 dCRs updates, CT WG3 has implemented Nmbsf_MBSUserService and Nmbsf_MBSUserDataIngestSession services in TS 29.580. The pCR package attached reflects the implementations which is planned to be submitted for approval in CT#97-e plenary, which is estimated to be included in TS 29.580 v17.0.0 in September. CT WG3 futher concerns: For the MBS User Service Announcement encoding, whether we should reuse this encoding defined by SA WG4 in TS 26.517, and the encoding alignment will be done between TS 26.517 and TS 26.502 ?","secretary_remarks":"Noted","agenda_item_sort_order":52,"ainumber":"8.9","ainame":"Architectural enhancements for 5G multicast-broadcast services (5MBS)","tdoc_agenda_sort_order":12110,"status":"noted","reservation_date":"2022-09-21 05:20:41","uploaded":"2022-09-22 05:01:53","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG4","Cc":"SA WG2, SA WG6","lsoriginalls":"C3-224655","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_153E_Electronic_2022-10\/Docs\/S2-2208131.zip","group":"S2","meeting":"S2-153-e","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2208136","title":"LS from CT WG4: LS on Multicast MBS session Deactivation and Reactivation","source":"CT WG4","contact":"Bruno Landais","contact-id":68755,"tdoctype":"LS in","for":"Action","abstract":"CT WG4 kindly ask SA WG2 to answer the following questions. Q1: During the MBS session deactivation procedure, does the MB-SMF instruct the MB-UPF to stop the forwarding of DL MBS data towards the N3mb DL F-TEIDs configured in the MB-UPF for the MBS session? Q2: If the answer to Q1 is yes, when the multicast traffic resumes (i.e. first packet arrives at MB-UPF), does the forwarding of MBS data towards the N3mb DL F-TEIDs resume only after the MB-SMF instructs the MB-UPF to forward the packets at step 15 of the MBS session activation call flow (Figure 7.2.5.2-1), i.e. after the MB-SMF activates the multicast MBS session towards the AMF(s) (and NG-RAN nodes) and receives a successful response from the AMF (and a first NG-RAN node)? Clause 6.7 (User plane management) of TS 23.247 specifies: - If the SMF wants to maintain the MBS data reception over N19mb but suspends the delivery of the data to the UE's PDU session, the Action of FAR set to 'drop' (e.g. when the UE is switching from 5GC Individual delivery to 5GC Shared delivery due to the UE moving from MBS non-supporting NG-RAN to MBS supporting NG-RAN). Otherwise the SMF remove the related PDR and FAR. Clause 7.2.2.2 (Multicast session leave requested by the UE) specifies: 4. [Conditional] If the UPF indicates the tunnel release (i.e. unicast transport was used), the SMF invokes Nmbsmf_MBSSession_ContextUpdate Request (Release, MBS Session ID, tunnel information) to release the tunnel between UPF and MB-UPF for this multicast MBS session. The MB-SMF determines whether the context update is for tunnel release or create based on whether the tunnel information exists in the multicast MBS Session Context stored in the MB-SMF or not. Clause 7.2.5.3 (MBS session deactivation procedure) specifies: 2. The MB-SMF send N4mb Session Modification Request (TMGI, Buffered Downlink Traffic detection) to the MB-UPF. See clause 4.4 of TS 23.502 [6] for more details. The Buffered Downlink Traffic detection is requested by MB-SMF for next time MBS session activation. If the MBS session is to be activated via the AF request directly, this indication is not needed. The MB-SMF also indicates the MB-UPF to remove the shared tunnel(s) that are used for Individual MBS traffic delivery over N19mb interface. Q3: Can SA WG2 confirm that during an MBS session deactivation procedure, the SMF need not and shall not request the UPF(s) to maintain the N19mb tunnels and that, after an N19m tunnel (of the MBS session) is removed in the UPF, the SMF shall not send a ContextUpdate request message towards the MB-SMF to report the removal of the N19mb tunnel in the UPF?. Action: CT WG4 kindly asks SA WG2 to answer the above questions and clarify stage 2 if necessary.","secretary_remarks":"Responses drafted in S2-2208201, S2-2208328, S2-2208897. Final response in S2-2209283","agenda_item_sort_order":52,"ainumber":"8.9","ainame":"Architectural enhancements for 5G multicast-broadcast services (5MBS)","tdoc_agenda_sort_order":12120,"status":"replied to","reservation_date":"2022-09-21 05:20:41","uploaded":"2022-09-22 05:01:53","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"RAN WG3","lsoriginalls":"C4-224417","lsreply":"S2-2209283, S2-2209283","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_153E_Electronic_2022-10\/Docs\/S2-2208136.zip","group":"S2","meeting":"S2-153-e","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2208141","title":"LS from RAN WG2: Reply LS on the MBS broadcast service continuity and MBS session identification","source":"RAN WG2","contact":"Umesh Phuyal","contact-id":71775,"tdoctype":"LS in","for":"Information","abstract":"RAN WG2 thanks SA WG4 for the LS on the MBS broadcast service continuity and MBS session identification. SA WG4 requested RAN WG2 to provide us details to augment TS26.517 to add these parameters . RAN WG2 would like to provide following feedback: 1. In NR, the frequency parameter is coded as combination of FreqBandIndicatorNR and ARFCN-ValueNR as defined in 3GPP TS 38.331 and TS 38.101. 2. RAN WG2 didn t agree on adding other parameters, such as SCS or BW, in USD for Rel-17. Please note, this does not preclude whether RAN WG2 might request to add something for Rel-18 or later Release.","secretary_remarks":"Noted","agenda_item_sort_order":52,"ainumber":"8.9","ainame":"Architectural enhancements for 5G multicast-broadcast services (5MBS)","tdoc_agenda_sort_order":12320,"status":"noted","reservation_date":"2022-09-21 05:20:41","uploaded":"2022-09-22 05:01:53","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG4","Cc":"RAN WG3","lsoriginalls":"R2-2208885","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_153E_Electronic_2022-10\/Docs\/S2-2208141.zip","group":"S2","meeting":"S2-153-e","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2208146","title":"LS from RAN WG3: Response LS on Support of Broadcast and Multicast MBS sessions with AMF Set","source":"RAN WG3","contact":"Alexander Vesely","contact-id":10078,"tdoctype":"LS in","for":"Information","abstract":"The LS contains three questions from CT WG4 regarding AMF failure without restart. - Question 1: CT WG4 would like RAN WG3 to confirm if CT WG4's assumptions [for Broadcast MBS Sessions] are correct. - Question 2: CT WG4 would like RAN WG3 to confirm if CT WG4's assumption [for Multicast MBS Sessions] is correct. - Question 3: CT WG4 would like to get feedback from RAN WG3 on whether such a local link failure scenario is a common failure scenario that should be addressed by new restoration procedures defined by CT WG4. General Response RAN WG3 asks CT WG4 to confirm that the respective functions are only used for restoration scenarios and represent exceptional cases, i.e. planned or unplanned AMF removal, while in normal operation, a multicast\/broadcast MBS Session Context is kept in the same AMF. Response to Question 1 RAN WG3 confirms that a gNB is able (under the assumptions above) to receive a NGAP Broadcast Session Modification Request message or an NGAP Broadcast Session Release Request message from another AMF in the same AMF set or a backup AMF. Response to Question 2 RAN WG3 confirms that a gNB is able (under the assumptions above) to receive a NGAP Multicast Session Activation\/Update\/Deactivation request message from another AMF in the same AMF set or from a backup AMF than the AMF(s) via which NGAP Distribution Setup procedure was triggered. Response to Question 3 RAN WG3 did not identify any need to be addressed by new restoration procedures defined by CT WG4.","secretary_remarks":"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-09-21 05:20:41","uploaded":"2022-09-22 05:01:53","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG4","Cc":"SA WG2","lsoriginalls":"R3-225165","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_153E_Electronic_2022-10\/Docs\/S2-2208146.zip","group":"S2","meeting":"S2-153-e","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2208148","title":"LS from RAN WG3: LS on shared NG-U Termination among gNBs","source":"RAN WG3","contact":"Philippe Godin","contact-id":68843,"tdoctype":"LS in","for":"Information","abstract":"RAN WG3 has designed in release 17 the option to reuse the shared N3 termination of an MBS session of a first gNB by other gNBs. For multicast MBS sessions using unicast transport over shared N3, this means that any other gNB will send the NGAP Distribution Setup Request to setup the shared N3 including a unicast transport address for which the delivery of multicast data from the MB-UPF already exists. RAN WG3 has identified the following solutions: - The MB-SMF has means to identify that the received unicast transport address already receives the multicast (e.g. it stores unicast transport addresses of the distribution tree) and can avoid asking the MB-UPF to add it redundantly (1). - The MB-SMF doesn t have the means above and redundantly triggers the MB-UPF to add the address. MB-UPF can identify that this address already receives the multicast delivery and can ignore it (2). - gNB can indicate to the MB-SMF in the NGAP Distribution Setup Request that the included unicast transport address already receives the multicast to avoid that the MB-SMF uselessly triggers the MB-UPF to add it. (3).","secretary_remarks":"Responses drafted in S2-2208722, S2-2208950. Final response in S2-2209285","agenda_item_sort_order":52,"ainumber":"8.9","ainame":"Architectural enhancements for 5G multicast-broadcast services (5MBS)","tdoc_agenda_sort_order":12200,"status":"replied to","reservation_date":"2022-09-21 05:20:42","uploaded":"2022-09-22 05:01:53","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG4","Cc":"SA WG2","lsoriginalls":"R3-225247","lsreply":"S2-2209285, S2-2209285","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_153E_Electronic_2022-10\/Docs\/S2-2208148.zip","group":"S2","meeting":"S2-153-e","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2208152","title":"LS from SA WG3: Reply LS on the impact of MSK update on MBS multicast session update procedure","source":"SA WG3","contact":"Longhua Guo","contact-id":80179,"tdoctype":"LS in","for":"Action","abstract":"SA WG3 thanks SA WG2 for the LS on the impact of MSK update on MBS multicast session update procedure. SA WG3 would like to provide the following feedback. Issue 1: SA WG3 specified: 'The multicast session security context consists of the MBS session ID, MBS keys and the corresponding key ID. The MBS keys include MBS Service Key (MSK) and MBS Traffic Key (MTK). MBS traffic is protected with the MTK. The MSK is used to protect the MTK when the MTK is delivered to the UE. In the multicast session join and session establishment procedure, the SMF interacts with the MB-SMF to obtain the multicast session security context. . The SMF shall provide the multicast session security context to the UE if received from the MB-SMF and the UE is authorized to use the required multicast service' It seems that both the MSK and MTK need to be provided from MBSF towards UE. So far the procedures give the imnpression that both MSK and MTK are communicated via the same control plane signalling messages from MBSF towards MB-SMF, SMF and then via PDU session related signalling towards the UE. Is it acceptable to send both the MSK and MTK in the same messages or at least using the same signalling channel? If different signalling channels are required, what would they be? Answer 1: It s recommended to send both the MSK and MTK in the same messages or at least using the same signalling channel to reduce the complexity. Issue 2: SA WG3 specified 'If security protection to be applied, then the MBSF shall create the multicast session security context by generating the MSK and its key ID for a MBS session. Afterwards, the MBSF distributes the MSK with MBS session ID and its key ID to the MB-SMF and MBSTF. The MBSF shall also distribute them to MB-SMF either upon request by the MB-SMF (i.e., pull) or when a new MSK is generated (i.e., push).' What would be the triggers for the MB-SMF to request an MSK? Answer 2: If the MSK is not available (e.g. the old MSK expired), it would be feasible for MB-SMF to request the MSK. Issue 3: SA WG3 specified: '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). The MTK may be updated based on the change of the authorization information or based on the local policy (e.g. key lifetime expiration). In such cases, the MBSF or MB-SMF may trigger the MTK update to the MBSTF' What kind of authorization information does this refer to? How does the MB-SMF obtain that changed authorization information? Answer 3: the authorization information refers to whether the UE is authorized to access the multicast service identified by the multicast session ID. MB-SMF subscribes the authorization information change event to UDM and acquire the information afterwards. Issue 4: The impacts on multicast session join and session establishment procedure and session update procedure are described in W.4 of TS 33.501. SA WG2 expects the impacts on MBS session creation can be described as well.SA WG2 suggest making clearer references to related messages in the MBS session management procedures in clause 7.1.1 of TS 23.247. SA WG2 would prefer reusing existing messages in those procedures. Answer 4: SA WG3 agrees with the suggestion. Issue 5: The MBSF will be aware whether an AF sets the status of the MBS session to active or inactive. When an MBS session is inactive no MBS data can be distributed. Should the MTKs be distributed in the user plane together with data of the MBS session via multicast, SA WG2 thus recommends deferring the MTK distribution until the session is active. To ensure UEs have updated MSK\/MTK to decrypt content when the MBS session is activated, SA WG2 recommends keeping MSK distribution when the session is inactive. Answer 5: SA WG3 agrees with the suggestion. SA WG3 will update the TS 33.501 accordingly and keep informed if more progress is made. Action: SA WG2, CT WG1, SA WG4 are kindly requested to ta","secretary_remarks":"Response drafted in S2-2208327. Final response in S2-2209287","agenda_item_sort_order":52,"ainumber":"8.9","ainame":"Architectural enhancements for 5G multicast-broadcast services (5MBS)","tdoc_agenda_sort_order":12280,"status":"replied to","reservation_date":"2022-09-21 05:20:42","uploaded":"2022-09-22 05:01:53","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, CT WG1","Cc":"CT WG4","lsoriginalls":"S3-222391","lsreply":"S2-2209287, S2-2209287, S2-2210860","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_153E_Electronic_2022-10\/Docs\/S2-2208152.zip","group":"S2","meeting":"S2-153-e","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2208170","title":"Alignment with SA WG4 work on MBS service announcements","source":"Nokia, Nokia Shanghai-Bell","contact":"Thomas Belling","contact-id":68266,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Remove reference to TS 26.346 and add references to TS 26.502 and TS 26.517. The Service Announcement may be encoded as defined in TS 26.517 or use application specific formats outside the scope of 3GPP. User Service Announcement information may be delivered to the UE via application specific means or as defined in TS 26.502.","secretary_remarks":"Revision of (postponed) S2-2207689 from S2-152E. CC#3: Postponed to CC#4. CC#4: No consensus. 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-09-21 16:09:59","uploaded":"2022-09-30 20:55:20","revisionof":"S2-2207689","revisedto":"","release":"Rel-17","crspec":"23.247","crspecversion":"17.4.0","workitem":[{"winame":"5MBS"}],"crnumber":133.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_153E_Electronic_2022-10\/Docs\/S2-2208170.zip","group":"S2","meeting":"S2-153-e","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2208200","title":"Handling of tunnel between UPF and MB_UPF for Multicast MBS session Deactivation and Reactivation","source":"Nokia, Nokia Shanghai-Bell","contact":"Thomas Belling","contact-id":68266,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 1. If session activation is to be detected by the MB-UPF, the MB-SMF can request the MB-UPF to perform Buffered Downlink Traffic detection and thus to stop forwarding data. If session activation is to be based on an AF request, the MB-SMF does not request the MB-UPF to perform Buffered Downlink Traffic detection and to stop forwarding data. 2. Step 15 in Figure 7.2.5.2-1 only applies if session activation is detected by the MB-UPF via Buffered Downlink Traffic detection. It is executed in parallel to the previous steps to avoid that the start of the transmission is unduly delayed until replies from all NG-RAN nodes and SMFs are received. 3. During the MBS session deactivation procedure, the MB-SMF keeps the tunnels for data forwarding towards UPFs established unless it is requested to release such tunnels by the SMFs.","secretary_remarks":"r07 agreed. Revised to S2-2209284, merging S2-2208331","agenda_item_sort_order":52,"ainumber":"8.9","ainame":"Architectural enhancements for 5G multicast-broadcast services (5MBS)","tdoc_agenda_sort_order":12170,"status":"revised","reservation_date":"2022-09-27 17:26:48","uploaded":"2022-09-30 20:55:20","revisionof":"","revisedto":"S2-2209284","release":"Rel-17","crspec":"23.247","crspecversion":"17.4.0","workitem":[{"winame":"5MBS"}],"crnumber":134.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_153E_Electronic_2022-10\/Docs\/S2-2208200.zip","group":"S2","meeting":"S2-153-e","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2208201","title":"[DRAFT] Reply LS on Multicast MBS session Deactivation and Reactivation","source":"Nokia, Nokia Shanghai-Bell","contact":"Thomas Belling","contact-id":68266,"tdoctype":"LS out","for":"Approval","abstract":"Summary of change: Answers questions raised in incoming LS S2-2208136 from CT WG4: Shared tunnel between UPF and MB-UPF may be kept while MBS session is deactivated to enable a quicker resumption of data transmission","secretary_remarks":"Response to S2-2208136. Merged into S2-2209283","agenda_item_sort_order":52,"ainumber":"8.9","ainame":"Architectural enhancements for 5G multicast-broadcast services (5MBS)","tdoc_agenda_sort_order":12130,"status":"merged","reservation_date":"2022-09-27 17:33:26","uploaded":"2022-09-30 20:55:20","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"5MBS"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG4","Cc":"RAN WG3","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_153E_Electronic_2022-10\/Docs\/S2-2208201.zip","group":"S2","meeting":"S2-153-e","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2208327","title":"[DRAFT] Reply LS on the impact of MSK update on MBS multicast session update procedure","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"LS out","for":"Approval","abstract":"Reply LS on the impact of MSK update on MBS multicast session update procedure","secretary_remarks":"Response to S2-2208152. r01 agreed. Revised to S2-2209287.","agenda_item_sort_order":52,"ainumber":"8.9","ainame":"Architectural enhancements for 5G multicast-broadcast services (5MBS)","tdoc_agenda_sort_order":12290,"status":"revised","reservation_date":"2022-09-29 09:53:39","uploaded":"2022-09-30 14:32:18","revisionof":"","revisedto":"S2-2209287","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"5MBS"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG3","Cc":"SA WG4, CT WG1, CT WG4","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_153E_Electronic_2022-10\/Docs\/S2-2208327.zip","group":"S2","meeting":"S2-153-e","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2208328","title":"[DRAFT] Reply LS on Multicast MBS session Deactivation and Reactivation","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"LS out","for":"Approval","abstract":"Reply LS on Multicast MBS session Deactivation and Reactivation","secretary_remarks":"Response to S2-2208136. Merged into S2-2209283","agenda_item_sort_order":52,"ainumber":"8.9","ainame":"Architectural enhancements for 5G multicast-broadcast services (5MBS)","tdoc_agenda_sort_order":12140,"status":"merged","reservation_date":"2022-09-29 09:53:51","uploaded":"2022-09-30 14:32:18","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"5MBS"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG4","Cc":"RAN WG3","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_153E_Electronic_2022-10\/Docs\/S2-2208328.zip","group":"S2","meeting":"S2-153-e","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2208329","title":"[DRAFT] Reply LS on 5MBS User Services","source":"Ericsson, ZTE, Qualcomm Incorporated, Nokia, Nokia Shanghai Bell","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"LS out","for":"Approval","abstract":"Reply LS on 5MBS User Services","secretary_remarks":"Response to S2-2208108. r02 agreed. Revised to S2-2209281, merging S2-2208720","agenda_item_sort_order":52,"ainumber":"8.9","ainame":"Architectural enhancements for 5G multicast-broadcast services (5MBS)","tdoc_agenda_sort_order":12040,"status":"revised","reservation_date":"2022-09-29 09:53:51","uploaded":"2022-09-30 14:32:18","revisionof":"","revisedto":"S2-2209281","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"5MBS"},{"winame":" 5MBUSA"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG4","Cc":"SA WG6, CT WG3, CT WG4","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_153E_Electronic_2022-10\/Docs\/S2-2208329.zip","group":"S2","meeting":"S2-153-e","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2208330","title":"Missing NID in output parameters to AF for SNPN","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: In clause 9, in TMGI allocation response and MBS session creation response, include NID as an optional output parameter.","secretary_remarks":"Approved","agenda_item_sort_order":52,"ainumber":"8.9","ainame":"Architectural enhancements for 5G multicast-broadcast services (5MBS)","tdoc_agenda_sort_order":12340,"status":"agreed","reservation_date":"2022-09-29 09:53:51","uploaded":"2022-09-30 14:32:18","revisionof":"","revisedto":"","release":"Rel-17","crspec":"23.247","crspecversion":"17.4.0","workitem":[{"winame":"5MBS"}],"crnumber":135.0,"crrevision":"","crcategory":"F","tsg_crp":"SP-221068","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_153E_Electronic_2022-10\/Docs\/S2-2208330.zip","group":"S2","meeting":"S2-153-e","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2208331","title":"Clarification on MBS session activation and deactivation","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: In clause 7.2.5.2, in step 14, clarify AMF sends response to MB-SMF after receiving the first successful NGAP activation response from NG-RAN. In clause 7.2.5.3, in step 2, clarify MB-SMF requests MB-UPF to remove N19mb tunnels and there are no needs for the SMF(s) to send ContextStatusUpdate to remove N19mb tunnel again. Regarding N3mb tunnel handling, which hasn t been specified clearly, there are two options: Option-1 (keep current solution): In MBS session deactivation, MB-SMF requests MB-UPF to keep the N3mb tunnels. In MBS session activation, there is no need for MB-SMF to provision the available N3mb tunnel back to MB-UPF. In this way, if NG-RAN establishes or releases shared delivery when the MBS session is inactive, the MB-SMF needs to interact with the MB-UPF. Option-2 (optimize current solution): In MBS session deactivation, MB-SMF requests MB-UPF to remove the N3mb tunnels as well. In MBS session activation, the MB-SMF provisions the available N3mb tunnels back to MB-UPF. In this way, an N4 interaction can be saved, if the shared delivery is established or released when the MBS session is inactive. Clarify that the handling of interaction between MB-SMF and MB-UPF is the same as the handling of interaction between SMF and UPF, which can be referred to clause 4.4 of TS 23.502.","secretary_remarks":"Merged into S2-2209284","agenda_item_sort_order":52,"ainumber":"8.9","ainame":"Architectural enhancements for 5G multicast-broadcast services (5MBS)","tdoc_agenda_sort_order":12190,"status":"merged","reservation_date":"2022-09-29 09:53:52","uploaded":"2022-09-30 14:32:18","revisionof":"","revisedto":"","release":"Rel-17","crspec":"23.247","crspecversion":"17.4.0","workitem":[{"winame":"5MBS"}],"crnumber":136.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_153E_Electronic_2022-10\/Docs\/S2-2208331.zip","group":"S2","meeting":"S2-153-e","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2208577","title":"Clean-up of PCC procedures for 5MBS","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: A part of the text in step 22 in clause 7.1.1.3 and step 8 in clause 7.1.1.3 is re-formatted so that it is independent from the respective step. The figures are updated by: removing the listed parameters from those service operations which use many and optional parameters adding double arrows in two places in clause 7.1.1.3 adding a dashed box around step 9 in the clause 7.1.1.7 with the text IF PCF receives MBS Service Information from the MB-SMF (the text in the corresponding dashed box in clause 7.1.1.3 is updated in the same way) changing dotted boxes to solid boxes in clause 7.1.1.3 The terminology for MBS Session ID is aligned in several places.","secretary_remarks":"r02 agreed. Revised to S2-2209288.","agenda_item_sort_order":52,"ainumber":"8.9","ainame":"Architectural enhancements for 5G multicast-broadcast services (5MBS)","tdoc_agenda_sort_order":12350,"status":"revised","reservation_date":"2022-09-30 07:46:09","uploaded":"2022-09-30 16:00:41","revisionof":"","revisedto":"S2-2209288","release":"Rel-17","crspec":"23.247","crspecversion":"17.4.0","workitem":[{"winame":"5MBS"}],"crnumber":137.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_153E_Electronic_2022-10\/Docs\/S2-2208577.zip","group":"S2","meeting":"S2-153-e","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2208718","title":"Discussion on MBS user service.","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"discussion","for":"Discussion","abstract":"The incoming LS from SA WG4 asks for clarification that whether MB2 interface provided by 5GC can be used to trigger the establishment of broadcast MBS session in 5GC. This document analyses the issue and proposes a way forward.","secretary_remarks":"Noted","agenda_item_sort_order":52,"ainumber":"8.9","ainame":"Architectural enhancements for 5G multicast-broadcast services (5MBS)","tdoc_agenda_sort_order":12090,"status":"noted","reservation_date":"2022-09-30 09:15:39","uploaded":"2022-09-30 11:13:31","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_153E_Electronic_2022-10\/Docs\/S2-2208718.zip","group":"S2","meeting":"S2-153-e","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2208719","title":"CR on MBS user service","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 1. Update the note in clause 5.2 to clarify the case for provding MB2 in 5GS. 2. Clarified in Annex C the use cases for invoking MB2 interface.","secretary_remarks":"Not Handled","agenda_item_sort_order":52,"ainumber":"8.9","ainame":"Architectural enhancements for 5G multicast-broadcast services (5MBS)","tdoc_agenda_sort_order":12420,"status":"not treated","reservation_date":"2022-09-30 09:15:39","uploaded":"2022-09-30 11:13:31","revisionof":"","revisedto":"","release":"Rel-17","crspec":"23.247","crspecversion":"17.4.0","workitem":[{"winame":"5MBS"}],"crnumber":138.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_153E_Electronic_2022-10\/Docs\/S2-2208719.zip","group":"S2","meeting":"S2-153-e","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2208720","title":"[DRAFT] Reply LS on MBS user service","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"LS out","for":"Approval","abstract":"LS paper regarding the MBS User service clarifies the use case is only for GCS\/AS that only supports MB2 and GC1.","secretary_remarks":"Response to S2-2208108. Merged into S2-2209281","agenda_item_sort_order":52,"ainumber":"8.9","ainame":"Architectural enhancements for 5G multicast-broadcast services (5MBS)","tdoc_agenda_sort_order":12080,"status":"merged","reservation_date":"2022-09-30 09:15:40","uploaded":"2022-09-30 11:13:31","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"5MBS"},{"winame":" 5MBUSA"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG4","Cc":"SA WG6, CT WG3, CT WG4","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_153E_Electronic_2022-10\/Docs\/S2-2208720.zip","group":"S2","meeting":"S2-153-e","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2208721","title":"Discussion on the issue of shared NG-U Termination among gNBs.","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"discussion","for":"Discussion","abstract":"An LS from RAN WG3 asking for the possible solutions for supporting the scenario for shared NG-U termination.","secretary_remarks":"Noted","agenda_item_sort_order":52,"ainumber":"8.9","ainame":"Architectural enhancements for 5G multicast-broadcast services (5MBS)","tdoc_agenda_sort_order":12240,"status":"noted","reservation_date":"2022-09-30 09:15:40","uploaded":"2022-09-30 11:13:31","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_153E_Electronic_2022-10\/Docs\/S2-2208721.zip","group":"S2","meeting":"S2-153-e","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2208722","title":"[DRAFT] Reply LS on Common CU-UP","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"LS out","for":"Approval","abstract":"The LS proposes to minimize the system impact , among the alternatives, alt#1 is preferred.","secretary_remarks":"Response to S2-2208148. Merged into S2-2209285","agenda_item_sort_order":52,"ainumber":"8.9","ainame":"Architectural enhancements for 5G multicast-broadcast services (5MBS)","tdoc_agenda_sort_order":12210,"status":"merged","reservation_date":"2022-09-30 09:15:40","uploaded":"2022-09-30 11:13:31","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"5MBS"},{"winame":" NR_MBS-Core"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG3","Cc":"CT WG4","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_153E_Electronic_2022-10\/Docs\/S2-2208722.zip","group":"S2","meeting":"S2-153-e","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2208723","title":"CR on MTK or MSK processing","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 1. Update Session join\/establish\/update\/creation procedures, to reflect the content of the LS from SA WG3. 2. Update the associating services to reflect the LS from SA WG3.","secretary_remarks":"r02 agreed. Revised to S2-2209289.","agenda_item_sort_order":52,"ainumber":"8.9","ainame":"Architectural enhancements for 5G multicast-broadcast services (5MBS)","tdoc_agenda_sort_order":12370,"status":"revised","reservation_date":"2022-09-30 09:15:40","uploaded":"2022-09-30 11:13:31","revisionof":"","revisedto":"S2-2209289","release":"Rel-17","crspec":"23.247","crspecversion":"17.4.0","workitem":[{"winame":"5MBS"}],"crnumber":139.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_153E_Electronic_2022-10\/Docs\/S2-2208723.zip","group":"S2","meeting":"S2-153-e","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2208840","title":"Alignment with stage-3 for USD and service announcement","source":"Qualcomm Incorporated","contact":"Haris Zisimopoulos","contact-id":84603,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Removes 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":"CC#3: Postponed to CC#4. CC#4: No consensus. Noted","agenda_item_sort_order":52,"ainumber":"8.9","ainame":"Architectural enhancements for 5G multicast-broadcast services (5MBS)","tdoc_agenda_sort_order":12400,"status":"noted","reservation_date":"2022-09-30 10:56:19","uploaded":"2022-09-30 17:41:32","revisionof":"","revisedto":"SP-221211","release":"Rel-17","crspec":"23.247","crspecversion":"17.4.0","workitem":[{"winame":"5MBS"}],"crnumber":140.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_153E_Electronic_2022-10\/Docs\/S2-2208840.zip","group":"S2","meeting":"S2-153-e","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2208897","title":"[DRAFT] Reply LS on Multicast MBS session Deactivation and Reactivation","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"LS out","for":"Approval","abstract":"LS response on LS on Multicast MBS session Deactivation and Reactivation","secretary_remarks":"Response to S2-2208136. r04 agreed. Revised to S2-2209283, merging S2-2208201 and S2-2208328","agenda_item_sort_order":52,"ainumber":"8.9","ainame":"Architectural enhancements for 5G multicast-broadcast services (5MBS)","tdoc_agenda_sort_order":12150,"status":"revised","reservation_date":"2022-09-30 12:00:37","uploaded":"2022-09-30 15:38:40","revisionof":"","revisedto":"S2-2209283","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"5MBS"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG4","Cc":"RAN WG3","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_153E_Electronic_2022-10\/Docs\/S2-2208897.zip","group":"S2","meeting":"S2-153-e","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2208948","title":"Discussion on the common UP issue raised by RAN WG3 for shared delivery establishment management.","source":"ZTE","contact":"Zhendong Li","contact-id":38521,"tdoctype":"discussion","for":"Discussion","abstract":"This paper discusses the common UP issue by RAN WG3 LS S2-2208148 for shared delivery management and gives the proposal","secretary_remarks":"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-09-30 12:54:34","uploaded":"2022-09-30 13:36:17","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_153E_Electronic_2022-10\/Docs\/S2-2208948.zip","group":"S2","meeting":"S2-153-e","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2208949","title":"Clarification on the shared delivery tunnel management for common gNB UP case","source":"ZTE","contact":"Zhendong Li","contact-id":38521,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: During the shared delivery tunnel establishmentt, the MB-SMF store the RAN id and DL GTP tunnel info. The MB-SMF check whether the tunnel has been established before it config the MB-UPF. During the shared delivery tunnel release, the MB-SMF remove the stored the RAN id and DL GTP tunnel info. The MB-SMF check whether the tunnel is still used by other shared delivery tunnel before it config the MB-UPF to stop.","secretary_remarks":"r10 agreed. Revised to S2-2209286.","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-09-30 12:54:34","uploaded":"2022-09-30 13:36:17","revisionof":"","revisedto":"S2-2209286","release":"Rel-17","crspec":"23.247","crspecversion":"17.4.0","workitem":[{"winame":"5MBS"}],"crnumber":141.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_153E_Electronic_2022-10\/Docs\/S2-2208949.zip","group":"S2","meeting":"S2-153-e","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2208950","title":"[DRAFT] Reply LS on shared NG-U Termination among gNBs","source":"ZTE","contact":"Zhendong Li","contact-id":38521,"tdoctype":"LS out","for":"Approval","abstract":"Proposes a Reply LS on shared NG-U Termination among gNBs","secretary_remarks":"Response to S2-2208148. r03 agreed. Revised to S2-2209285, merging S2-2208722","agenda_item_sort_order":52,"ainumber":"8.9","ainame":"Architectural enhancements for 5G multicast-broadcast services (5MBS)","tdoc_agenda_sort_order":12220,"status":"revised","reservation_date":"2022-09-30 12:54:37","uploaded":"2022-09-30 13:36:17","revisionof":"","revisedto":"S2-2209285","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"5MBS"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG3","Cc":"CT WG4","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_153E_Electronic_2022-10\/Docs\/S2-2208950.zip","group":"S2","meeting":"S2-153-e","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2208951","title":"Clarification on the traffic handling in MBSTF for interworking","source":"ZTE, Ericsson, Nokia, Nokia Shanghai-Bell, Qualcomm","contact":"Zhendong Li","contact-id":38521,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify that the MBSTF distributes the received data to the MB-UPF at reference point Nmb9 and the MBMS-GW at reference point SGi-mb","secretary_remarks":"Revision of (Postponed) S2-2206206 from S2#152E. CR Revision incorrect: -1! r04 agreed. Revised to S2-2209282.","agenda_item_sort_order":52,"ainumber":"8.9","ainame":"Architectural enhancements for 5G multicast-broadcast services (5MBS)","tdoc_agenda_sort_order":12060,"status":"revised","reservation_date":"2022-09-30 12:54:37","uploaded":"2022-09-30 13:36:17","revisionof":"S2-2206206","revisedto":"S2-2209282","release":"Rel-17","crspec":"23.247","crspecversion":"17.4.0","workitem":[{"winame":"5MBS"}],"crnumber":129.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_153E_Electronic_2022-10\/Docs\/S2-2208951.zip","group":"S2","meeting":"S2-153-e","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2209198","title":"Update on service announcement\/pre-configuration description","source":"Samsung","contact":"Youngkyo Baek","contact-id":46395,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Removes unclear preconfiguration description Service announcement description is updated as aligned with TS 26.502 Some editorial level changes.","secretary_remarks":"Merged into (Covered by) S2-2208840","agenda_item_sort_order":52,"ainumber":"8.9","ainame":"Architectural enhancements for 5G multicast-broadcast services (5MBS)","tdoc_agenda_sort_order":12410,"status":"merged","reservation_date":"2022-09-30 22:41:54","uploaded":"2022-09-30 22:57:25","revisionof":"","revisedto":"","release":"Rel-17","crspec":"23.247","crspecversion":"17.4.0","workitem":[{"winame":"5MBS"}],"crnumber":142.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_153E_Electronic_2022-10\/Docs\/S2-2209198.zip","group":"S2","meeting":"S2-153-e","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2209281","title":"Reply LS on 5MBS User Services","source":"SA WG2","contact":"Robbie Ling","contact-id":37246,"tdoctype":"LS out","for":"Approval","abstract":"To: SA WG4. CC: SA WG6, CT WG3, CT WG4. Attachments: TS 23.247 CR0129 (S2-2209282)","secretary_remarks":"Revision of S2-2208329r02, merging S2-2208720. Approved","agenda_item_sort_order":52,"ainumber":"8.9","ainame":"Architectural enhancements for 5G multicast-broadcast services (5MBS)","tdoc_agenda_sort_order":12050,"status":"approved","reservation_date":"2022-10-18 14:16:53","uploaded":"2022-10-18 14:31:16","revisionof":"S2-2208329","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"5MBS"},{"winame":" 5MBUSA"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2208108","lsto":"SA WG4","Cc":"SA WG6, CT WG3, CT WG4","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_153E_Electronic_2022-10\/Docs\/S2-2209281.zip","group":"S2","meeting":"S2-153-e","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2209282","title":"Clarification on the traffic handling in MBSTF for interworking","source":"ZTE, Ericsson, Nokia, Nokia Shanghai-Bell, Qualcomm","contact":"Zhendong Li","contact-id":38521,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify that the MBSTF distributes the received data to the MB-UPF at reference point Nmb9 and the MBMS-GW at reference point SGi-mb In NOTE 1, clarify xMB-C\/U and MB2-C\/U are legacy reference points.","secretary_remarks":"Revision of S2-2208951r04. Approved","agenda_item_sort_order":52,"ainumber":"8.9","ainame":"Architectural enhancements for 5G multicast-broadcast services (5MBS)","tdoc_agenda_sort_order":12070,"status":"agreed","reservation_date":"2022-10-18 14:16:54","uploaded":"2022-10-18 14:31:16","revisionof":"S2-2208951","revisedto":"","release":"Rel-17","crspec":"23.247","crspecversion":"17.4.0","workitem":[{"winame":"5MBS"}],"crnumber":129.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"SP-221068","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_153E_Electronic_2022-10\/Docs\/S2-2209282.zip","group":"S2","meeting":"S2-153-e","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2209283","title":"Reply LS on Multicast MBS session Deactivation and Reactivation","source":"SA WG2","contact":"Fenqin Zhu","contact-id":26772,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG4. CC: RAN WG3. Attachments: 23.247 CR0134 (S2-2209284)","secretary_remarks":"Revision of S2-2208897r04, merging S2-2208201 and S2-2208328. Approved","agenda_item_sort_order":52,"ainumber":"8.9","ainame":"Architectural enhancements for 5G multicast-broadcast services (5MBS)","tdoc_agenda_sort_order":12160,"status":"approved","reservation_date":"2022-10-18 14:16:56","uploaded":"2022-10-18 14:31:16","revisionof":"S2-2208897","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"5MBS"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2208136","lsto":"CT WG4","Cc":"RAN WG3","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_153E_Electronic_2022-10\/Docs\/S2-2209283.zip","group":"S2","meeting":"S2-153-e","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2209284","title":"Handling of tunnel between UPF and MB_UPF for Multicast MBS session Deactivation and Reactivation","source":"Nokia, Nokia Shanghai-Bell, Ericsson, Huawei","contact":"Thomas Belling","contact-id":68266,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 1. If session activation is to be detected by the MB-UPF, the MB-SMF can request the MB-UPF to perform Buffered Downlink Traffic detection and thus to stop forwarding data. If session activation is to be based on an AF request, the MB-SMF also configures the MB-UPF to stop forwarding and possibly to buffer MBS data. 2. It is up to implementation when to execute Step 15 in Figure 7.2.5.2-1 It can be executed after the first successful response in step 14 to avoid that the start of the transmission is unduly delayed until replies from all NG-RAN nodes and SMFs are received. Buffering at the MB-UPF can also be applied sufficiently long for the majority of RAN nodes to activate the MBS session to reduce packet loss. 3. During the MBS session deactivation procedure, the MB-SMF keeps the tunnels for data forwarding towards UPFs established, However, the SMFs may then request to release such tunnels any time later. 4. remove the incorrect reference","secretary_remarks":"Revision of S2-2208200r07, merging S2-2208331. Approved","agenda_item_sort_order":52,"ainumber":"8.9","ainame":"Architectural enhancements for 5G multicast-broadcast services (5MBS)","tdoc_agenda_sort_order":12180,"status":"agreed","reservation_date":"2022-10-18 14:16:56","uploaded":"2022-10-18 14:31:16","revisionof":"S2-2208200","revisedto":"","release":"Rel-17","crspec":"23.247","crspecversion":"17.4.0","workitem":[{"winame":"5MBS"}],"crnumber":134.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-221068","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_153E_Electronic_2022-10\/Docs\/S2-2209284.zip","group":"S2","meeting":"S2-153-e","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2209285","title":"Reply LS on shared NG-U Termination among gNBs","source":"SA WG2","contact":"Zhendong Li","contact-id":38521,"tdoctype":"LS out","for":"Approval","abstract":"To: RAN WG3, CT WG4. Attachments: 23.247 CR#0141 (S2-2209286)","secretary_remarks":"Revision of S2-2208950r03, merging S2-2208722. Approved","agenda_item_sort_order":52,"ainumber":"8.9","ainame":"Architectural enhancements for 5G multicast-broadcast services (5MBS)","tdoc_agenda_sort_order":12230,"status":"approved","reservation_date":"2022-10-18 14:16:57","uploaded":"2022-10-18 14:31:16","revisionof":"S2-2208950","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"5MBS"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2208148","lsto":"RAN WG3, CT WG4","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_153E_Electronic_2022-10\/Docs\/S2-2209285.zip","group":"S2","meeting":"S2-153-e","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2209286","title":"Clarification on the shared delivery tunnel management for common gNB UP case","source":"ZTE, Nokia, Nokia Shanghai-Bell, Ericsson, Huawei","contact":"Zhendong Li","contact-id":38521,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: During the shared delivery tunnel establishmentt, the MB-SMF store the RAN id and DL GTP tunnel info. The MB-SMF check whether the tunnel has been established before it config the MB-UPF. During the shared delivery tunnel release, the MB-SMF remove the stored the RAN id and DL GTP tunnel info. The MB-SMF check whether the tunnel is still used by other shared delivery tunnel before it config the MB-UPF to stop. Stage 3 allignment: NG RAN ID is sent from AMF to MB-SMF.","secretary_remarks":"Revision of S2-2208949r10. 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-10-18 14:16:58","uploaded":"2022-10-18 14:31:16","revisionof":"S2-2208949","revisedto":"","release":"Rel-17","crspec":"23.247","crspecversion":"17.4.0","workitem":[{"winame":"5MBS"}],"crnumber":141.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-221068","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_153E_Electronic_2022-10\/Docs\/S2-2209286.zip","group":"S2","meeting":"S2-153-e","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2209287","title":"Reply LS on the impact of MSK update on MBS multicast session update procedure","source":"SA WG2","contact":"Robbie Ling","contact-id":37246,"tdoctype":"LS out","for":"Approval","abstract":"To: SA WG3. CC: SA WG4, CT WG1, CT WG4","secretary_remarks":"Revision of S2-2208327r01. Approved","agenda_item_sort_order":52,"ainumber":"8.9","ainame":"Architectural enhancements for 5G multicast-broadcast services (5MBS)","tdoc_agenda_sort_order":12300,"status":"approved","reservation_date":"2022-10-18 14:17:00","uploaded":"2022-10-18 14:31:16","revisionof":"S2-2208327","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"5MBS"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2208152","lsto":"SA WG3","Cc":"SA WG4, CT WG1, CT WG4","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_153E_Electronic_2022-10\/Docs\/S2-2209287.zip","group":"S2","meeting":"S2-153-e","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2209288","title":"Clean-up of PCC procedures for 5MBS","source":"Huawei, HiSilicon, Ericsson, Nokia, Nokia Shanghai-Bell","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The optional input parameter 'indication that PCF has to be contacted' is removed from the Nmbsmf_MBSSession_Create service operation in clause 9.1.3.6. A part of the text in step 22 in clause 7.1.1.3 and step 8 in clause 7.1.1.3 is re-formatted so that it is independent from the respective step. The figures are updated by: removing the listed parameters from those service operations which use many and optional parameters adding double arrows in two places in clause 7.1.1.3 adding a dashed box around step 9 in the clause 7.1.1.7 with the text IF PCF receives MBS Service Information from the MB-SMF (the text in the corresponding dashed box in clause 7.1.1.3 is updated in the same way) changing dotted boxes to solid boxes in clause 7.1.1.3 The terminology for MBS Session ID is aligned in several places.","secretary_remarks":"Revision of S2-2208577r02. Approved","agenda_item_sort_order":52,"ainumber":"8.9","ainame":"Architectural enhancements for 5G multicast-broadcast services (5MBS)","tdoc_agenda_sort_order":12360,"status":"agreed","reservation_date":"2022-10-18 14:17:00","uploaded":"2022-10-18 14:31:16","revisionof":"S2-2208577","revisedto":"","release":"Rel-17","crspec":"23.247","crspecversion":"17.4.0","workitem":[{"winame":"5MBS"}],"crnumber":137.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-221068","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_153E_Electronic_2022-10\/Docs\/S2-2209288.zip","group":"S2","meeting":"S2-153-e","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2209289","title":"CR on MTK or MSK processing","source":"Huawei, HiSilicon, Nokia, Nokia Shanghai-Bell, Ericsson","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 1. Update Session join\/establish\/update\/creation procedures, to reflect the content of the LS from SA WG3. 2. Update the associating services to reflect the LS from SA WG3.","secretary_remarks":"Revision of S2-2208723r02. Approved. Revised at S2#154 in S2-2210846","agenda_item_sort_order":52,"ainumber":"8.9","ainame":"Architectural enhancements for 5G multicast-broadcast services (5MBS)","tdoc_agenda_sort_order":12380,"status":"revised","reservation_date":"2022-10-18 14:17:02","uploaded":"2022-10-18 14:31:16","revisionof":"S2-2208723","revisedto":"S2-2210846","release":"Rel-17","crspec":"23.247","crspecversion":"17.4.0","workitem":[{"winame":"5MBS"}],"crnumber":139.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_153E_Electronic_2022-10\/Docs\/S2-2209289.zip","group":"S2","meeting":"S2-153-e","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0}]