[{"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}]