[{"name":"S2-2103764","title":"LS from CT WG3: Reply LS on the support of L2TP with CUPS","source":"CT WG3","contact":"Tianmei Liang","contact-id":69846,"tdoctype":"LS in","for":"Action","abstract":"CT WG3 would like to thank CT WG4 for the LS on the support of L2TP with CUPS (C4-211624). Below are the extracted questions in the LS where Q2 are for CT WG3 to address: Q2: CT WG4 kindly requests CT WG3 to check and provide comments if any, e.g. for AVPs to be specified in 29.561\/29.061 for L2TP tunneling. CT WG3 has discussed the questions and provides the following answers based on the current status of the specifications. For the RADIUS attributes for L2TP tunnelling supporting, IETF RFC 2868: 'RADIUS Attributes for Tunnel Protocol Support' can be referred. For the Diameter AVPs for L2TP tunnelling supporting, clause 4.5 in IETF RFC 7155: 'Diameter Network Access Server Application' can be referred. While not every attributes\/AVPs need to be specified in TS 29.061 and TS 29.561. CT WG3 prefer to specify the Tunnel-Type, Tunnel-Medium-Type, Tunnel-Server-Endpoint and Tunnel-Preference attributes\/AVPs in TS 29.061 and TS 29.561. For Tunnel-Password and security protection, CT WG3 prefer to wait SA WG3 evaluation on security related requirement. Action: CT WG3 kindly requests SA WG2 to take the above information into account.","secretary_remarks":"Noted","agenda_item_sort_order":17,"ainumber":"6.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":10600,"status":"noted","reservation_date":"2021-05-03 05:55:58","uploaded":"2021-05-03 06:24:45","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, CT WG4","Cc":"SA WG3, CT WG1","lsoriginalls":"C3-212569","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_145E_Electronic_2021-05\/Docs\/S2-2103764.zip","group":"S2","meeting":"S2-145-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2103766","title":"LS from CT WG4: LS on UPF support for multiple network slices","source":"CT WG4","contact":"Zhijun Li","contact-id":39295,"tdoctype":"LS in","for":"Action","abstract":"CT WG4 is discussing support by UPF of multiple network slices, as part of WI BEPoP (BEst Practice of PFCP). Per existing 3GPP TS 23.501 and 3GPP TS 29.244, the UP resources (e.g. UE IP addresses, GTP-U F-TEIDs, CPU, memory, bandwidth, etc.) are managed \/ allocated in the UPF per Network Instance (i.e. when establishing a PFCP session, the SMF indicates the Network Instance ID associated to the PDU session). The Network Instance can correspond to a transport network with distinct transport characteristics, e.g. transport network slice, support of UE IP Address allocation (with certain UE IP Address range), IP routes and routing protocol (OSPF, BGP) to receive DL packet over SGi\/N6, different routing engine or L2\/L3 technology (e.g. IPsec, UDP\/IP tunnel, MPLS, L2TP ) to separate the traffic (e.g. to support different network slices). For a given PDU session, the Network Instance used for the corresponding PFCP session is determined by the SMF based on many factors, e.g. DNN\/APN, S-NSSAI, 5G-VN, roaming status, location, subscribed UE IP Address Pool IDs, DNAI(s) for certain applications. In order to support various business scenarios where one UPF is shared by several customers while each customer may be allocated with one network slice, operators expect that one UPF shall be able to support multiple network slices, and thus UPF shall be able to manage UP resources at per network slice granularity. To support the possibility for a UPF to reserve and assign resources to PFCP sessions per network slice, CT WG4 has discussed the following two solutions: - Solution 1: This is the existing solution described above, where the SMF maps the S-NSSAI and other factors to a Network Instance ID and the UPF just uses the Network Instance for UP resource management, as described in TR 29.820 clause 6.3. This solution requires the SMF to map one S-NSSAI to specific Network Instance(s). If one UPF supports multiple network slices, it requires that each network slice has a mapped Network Instance. There is the opinion from some operators that such a solution requires a careful and more complex planning of the Network Instance and the slices, thus it reduces its flexibility. - Solution 2: The UPF uses the S-NSSAI in addition to the Network Instance ID to manage the UP resources, as described in TR 29.820 clause 6.9 (solution#9) and C4-212114 (Postponed). In existing TS 29.244, the S-NSSAI can already be provided by the SMF to the UPF (in a standalone S-NSSAI IE), but this has been intended for performance measurements (SA WG5 PM requirements). This solution requires the UPF to perform UP resource management (e.g. UP resource separation, UP resource allocation, UP resource usage report, etc.) using the S-NSSAI together with Network Instance, which is not yet supported by TS 29.244. This solution requires some configuration\/logic in the UP function to manage UP resources using the S-NSSAI together with the Network Instance information, and the CP function may then possibly select the Network Instance without considering the S-NSSAI of the PDU session, but it doesn't require the operator to configure a separate Network Instance for each network slice (e.g. when multiple 5GS slices would be mapped to the same transport slice), and managing UP resources at slice granularity looks natural when network slice is used. Some operators believe it provides flexibility to fulfil the requirement of various business scenarios and different implementations. During the discussion, some companies believe that selecting the right Network Instance to provision PDRs\/FARs for a PFCP session (i.e. a PDU session or a PDN connection) shall be part of the Control Plane Node (e.g. SMF\/PGW-C) functionality, and the SMF\/PGW-C is the network function which has full information related to a PDU session\/PDN connection. Requiring the UP function to use S-NSSAI together with Network Instance to manage the UP resources in the UPF may have architecture impacts (e.g. network slice","secretary_remarks":"Responses drafted in S2-2103873 and S2-2104157. Postponed. Revised at S2-146E to S2-2105240","agenda_item_sort_order":17,"ainumber":"6.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":10620,"status":"postponed","reservation_date":"2021-05-03 05:55:59","uploaded":"2021-05-03 06:24:45","revisionof":"","revisedto":"S2-2105240","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, SA WG5","Cc":"","lsoriginalls":"C4-212560","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_145E_Electronic_2021-05\/Docs\/S2-2103766.zip","group":"S2","meeting":"S2-145-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2103872","title":"Analysis of CT WG4's options to support multiple slices in UPF .","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"discussion","for":"Agreement","abstract":"This contribution discusses the CT WG4 LS on UPF support for multiple slices and proposes a way forward.","secretary_remarks":"Noted","agenda_item_sort_order":17,"ainumber":"6.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":10650,"status":"noted","reservation_date":"2021-05-07 16:41:45","uploaded":"2021-05-10 21:15:46","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":[{"winame":"BEPoP"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_145E_Electronic_2021-05\/Docs\/S2-2103872.zip","group":"S2","meeting":"S2-145-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2103873","title":"[DRAFT] Reply LS on UPF support for multiple network slices","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"LS out","for":"Approval","abstract":"This is a proposed reply to CT'4 LS on multiple slices in UPF","secretary_remarks":"Response to S2-2103766. Postponed","agenda_item_sort_order":17,"ainumber":"6.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":10630,"status":"postponed","reservation_date":"2021-05-07 16:41:45","uploaded":"2021-05-10 21:15:46","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"BEPoP"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG4, SA WG5","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_145E_Electronic_2021-05\/Docs\/S2-2103873.zip","group":"S2","meeting":"S2-145-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2104157","title":"[DRAFT] Reply LS on UPF support for multiple network slices","source":"China Telecommunications","contact":"Jiayifan Liu","contact-id":74811,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG4. CC: SA WG5","secretary_remarks":"Response to S2-2103766. Postponed","agenda_item_sort_order":17,"ainumber":"6.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":10640,"status":"postponed","reservation_date":"2021-05-10 08:21:33","uploaded":"2021-05-10 14:13:28","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"BEPoP"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG4","Cc":"SA WG5","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_145E_Electronic_2021-05\/Docs\/S2-2104157.zip","group":"S2","meeting":"S2-145-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2104707","title":"L2TP information provision","source":"China Telecom","contact":"Heng Nie","contact-id":40431,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add support for providing L2TP information in DN-AAA","secretary_remarks":"r04 agreed. Revised to S2-2104798.","agenda_item_sort_order":17,"ainumber":"6.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":10630,"status":"revised","reservation_date":"2021-05-10 17:34:41","uploaded":"2021-05-10 17:40:14","revisionof":"","revisedto":"S2-2104798","release":"Rel-17","crspec":23.501,"crspecversion":"17.0.0","workitem":[{"winame":"TEI17"},{"winame":" BEPoP"}],"crnumber":2973.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_145E_Electronic_2021-05\/Docs\/S2-2104707.zip","group":"S2","meeting":"S2-145-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2104798","title":"L2TP information provision","source":"China Telecom, Ericsson, Nokia, Nokia Shanghai Bell, Deutsche Telekom","contact":"Heng Nie","contact-id":40431,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add support for providing L2TP information in DN-AAA","secretary_remarks":"Revision of S2-2104707r04. Approved","agenda_item_sort_order":17,"ainumber":"6.3","ainame":"Session management and continuity functions and flows","tdoc_agenda_sort_order":10640,"status":"agreed","reservation_date":"2021-05-25 06:16:14","uploaded":"2021-06-01 06:21:33","revisionof":"S2-2104707","revisedto":"","release":"Rel-17","crspec":23.501,"crspecversion":"17.0.0","workitem":[{"winame":"BEPoP"},{"winame":" TEI17"}],"crnumber":2973.0,"crrevision":1.0,"crcategory":"B","tsg_crp":"SP-210346","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_145E_Electronic_2021-05\/Docs\/S2-2104798.zip","group":"S2","meeting":"S2-145-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]