[{"name":"S2-2002662","title":"LS from SA WG3: reply-LS on UP gateway function on the N9 interface","source":"SA WG3","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Action","abstract":"SA WG3 thanks SA WG2 for their reply LS on UP gateway function on the N9 interface. In this LS, SA WG2 asks the following question to SA WG3: Question from SA WG2: [I]t is unclear to SA WG2 what information a UPF that supports the IPUPS functionality needs from SMF to achieve this 'GTP-u packet filtering'. To the above question, SA WG3 would like to provide the following answer: Answer from SA WG3: A UPF that supports the IPUPS functionality needs to receive the following information from the SMF: 1. PDU session establishment: Request to allocate destination IP address and TEID of a GTP-U tunnel for the PDU Session. 2. PDU session release: Information that the GTP-U tunnel is to be released. 3. During PDU Session lifetime: Request to allocate or release destination IP address and TEID in case the destination IP address and TEID for some reason need to change. SA WG3 foresees that only information that is currently sent on N4 from SMF to UPF will need to be sent from SMF to UPF with IPUPS functionality. That means, in release 16, the sent information between SMF and UPF with IPUPS functionality will be a subset of current N4. However, additions in future releases are not precluded. Action: SA WG3 asks SA WG2 group to take the above answer into account.","secretary_remarks":"Noted","agenda_item_sort_order":15,"ainumber":"6.4","ainame":"Security related functions and flows","tdoc_agenda_sort_order":11040,"status":"noted","reservation_date":"2020-03-26 10:57:38","uploaded":"2020-03-27 15:57:56","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"CT WG4, TSG SA","lsoriginalls":"S3-200482","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_138e_Electronic\/Docs\/S2-2002662.zip","group":"S2","meeting":"S2-ah-35701","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2002965","title":"Support of IPUPS Functionality","source":"Nokia, Nokia Shanghai Bell","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: \u00a7 5.8.2.11.6: add an IPUPS indication in FAR: The Action may also indicate that specific IPUPS related traffic flitering is to be enforced \u00a7 6.3.3.3: 'Remote PLMN(s) that the IPUPS allows to interface' is added","secretary_remarks":"Postponed","agenda_item_sort_order":15,"ainumber":"6.4","ainame":"Security related functions and flows","tdoc_agenda_sort_order":11050,"status":"postponed","reservation_date":"2020-04-10 08:15:59","uploaded":"2020-04-10 13:05:17","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.501,"crspecversion":"16.4.0","workitem":[{"winame":"5GS_Ph1"},{"winame":"TEI16"}],"crnumber":2298.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_138e_Electronic\/Docs\/S2-2002965.zip","group":"S2","meeting":"S2-ah-35701","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2003115","title":"Update on IPUPS functionality","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Update the description in clasue 5.8.2.14, to align with SA WG3 conclusion.","secretary_remarks":"e-meeting r03 agreed. Revised to S2-2003296.","agenda_item_sort_order":15,"ainumber":"6.4","ainame":"Security related functions and flows","tdoc_agenda_sort_order":11060,"status":"revised","reservation_date":"2020-04-10 13:27:43","uploaded":"2020-04-10 18:16:01","revisionof":"","revisedto":"S2-2003296","release":"Rel-16","crspec":23.501,"crspecversion":"16.4.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":2347.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_138e_Electronic\/Docs\/S2-2003115.zip","group":"S2","meeting":"S2-ah-35701","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2003296","title":"Update on IPUPS functionality","source":"Huawei, HiSilicon, Deutsche Telekom","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Update the description in clasue 5.8.2.14, to align with SA WG3 conclusion.","secretary_remarks":"Revision of S2-2003115. Approved","agenda_item_sort_order":15,"ainumber":"6.4","ainame":"Security related functions and flows","tdoc_agenda_sort_order":11070,"status":"agreed","reservation_date":"2020-04-27 09:08:40","uploaded":"2020-04-28 06:57:52","revisionof":"S2-2003115","revisedto":"","release":"Rel-16","crspec":23.501,"crspecversion":"16.4.0","workitem":[{"winame":"5GS_Ph1"},{"winame":"TEI16"}],"crnumber":2347.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-200551","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_138e_Electronic\/Docs\/S2-2003296.zip","group":"S2","meeting":"S2-ah-35701","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]