[{"name":"S2-2000028","title":"LS from BBF: Response to 3GPP S2-1910806 and S2-1912767 on Line ID","source":"BBF","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Action","abstract":"Dear colleagues, BBF also acknowledges the problem described in S2-1910806 and discussed in the follow up liaison S2-1912767. We believe we had already addressed the problem, but clearly did not successfully communicate this in our previous exchange (our ref: LIAISE-310). To illustrate our thinking, the actual problem goes further than ensuring uniqueness in a single operator domain; an operator may construct a network that includes wholesale of access facilities from 3PP operators. Therefore there are multiple uncoordinated administrations of Line ID to consider. As such we have specified the Line ID and Line ID source for the purposes of FMC as the following: {...} We believe the concatenation of Line ID source and Line ID is the functional equivalent of the Global Line Identifier (GLI) described in your liaison; designed to permit disambiguation of scenarios where there may be duplicate Line ID values within an operator network, or as a result of obtaining access facilities from third parties. We also assume that the AGF operator and the 5GC operator are one in the same, such that the GLI can be guaranteed to be unique within the context of the AGF\/5GC operator, and when combined with the operator's PLMN-ID can be guaranteed to be globally unique. Our current expectation is that we would not use an alternative to PLMN-ID to encode the owning operator, and do not have plans to establish a separate registry for that purpose. Therefore a 3GPP encoding that has the PLMN-ID, as well as the Line ID source\/Line ID (referred to as the GLI) is sufficient for our purposes. - In case the owning operator already has an assigned PLMN-ID, we expect they will use the assigned PLMN-ID with the Global Line Identifier (GLI). - In case the owning operator does NOT have a PLMN-ID (for example, a wireline-only operator), they can use a private PLMN-ID with an MCC of 999. We have not considered roaming for release 16, but if roaming eventually becomes in scope and a wireline-only operator intends to support roaming, they would be required to obtain a PLMN-ID. The current proposed encoding of SUCI with a GLI does not preclude this possible addition of roaming. As for the actual encoding, if only existing practice is considered, we require a variable length opaque object of up to 135 bytes to encode our 'disambiguated' Line ID; the equivalent of your proposed GLI. However as noted in our previous liaison, some of our member operators have suggested this may be inadequate in the future. Therefore we would suggest a variable length opaque object with the maximum length being the largest size that can be encoded in a SUPI net of any other fields. We will document encoding of the opaque value in WT-470. We did not go into this level of detail in our previous liaison, as we thought it would be source of confusion. We hope this clarifies our thinking. We are looking forward to continuing our fruitful collaboration. Sincerely, Lincoln Lavoie, Broadband Forum Technical Committee Chair","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":26,"ainumber":"7.2","ainame":"Wireless and Wireline Convergence for the 5G system architecture (5WWC)","tdoc_agenda_sort_order":13990,"status":"noted","reservation_date":"2019-12-18 15:23:44","uploaded":"2020-01-06 08:48:38","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, CT WG1","Cc":"","lsoriginalls":"LIAISE-353","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/TSG_SA\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2000028.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2000029","title":"LS from BBF: Request on work items for R17","source":"BBF","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Information","abstract":"Dear colleagues, Concerning the R17 items prioritization, it is of uttermost importance, from a commercial viewpoint, that operators would be able to offer per devices services for devices that do not use 3GPP procedures connected to the 5GC via a 5G-RG. In order to support this use case, some operators have expressed their preference to have a 5G-RG operating in a bridge mode, while there is an even stronger interest in having a 5G-RG operating in routed mode. In order to cover the most relevant use cases of interest to our providers BBF would request that 3GPP consider taking into its R17 work plan the FS_5WWC_Ph2 study items WT#1.3, WT#1.1 in addition to previously communicated interest in WT#0. We look forward to our continued cooperation and fruitful exchange. Sincerely, Lincoln Lavoie, Broadband Forum Technical Committee Chair","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":26,"ainumber":"7.2","ainame":"Wireless and Wireline Convergence for the 5G system architecture (5WWC)","tdoc_agenda_sort_order":13960,"status":"noted","reservation_date":"2019-12-18 15:23:44","uploaded":"2020-01-06 08:48:38","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG SA, SA WG2","Cc":"","lsoriginalls":"LIAISE-360","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/TSG_SA\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2000029.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2000030","title":"LS from BBF: General Status of Work","source":"BBF","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Information","abstract":"Dear colleagues, We wish to advise you of a number of aspects of both timing and content of our efforts to define 5G FMC, coordinated with 3GPP Release 16: 1) We have added an overall architecture document (WT-470 5G FMC Architecture) to our work plan to capture end-to-end aspects of the work. 2) We have recast our work plan to address Release 16 with two phases, which we have termed 16.1 and 16.2. These phases are: - 16.1: which is expected to be complete and into final ballot out of our Q1\/2020 meeting. It will include: - TR-124i6 Functional Requirements for Broadband Residential Gateway Devices, capturing the specification of 5G-RG requirements - TR-181i2 Amendment13 Device Data model for TR-069 - WT-456 AGF Functional Requirements - WT-470 5G FMC Architecture - 16.2: which is expected to be complete and into final ballot out of our Q3\/2020 meeting. It will include: - WT-457 FMIF Functional Requirements - WT-458 CUPS for FMC - Updates to the 16.1 document set to capture requirements to support ATSSS and devices using 3GPP procedures in the home With respect to technical subjects: 1) Previous study work identified a potential need for the Access Network Resource Control Function (ARCF), however, we have subsequently concluded this is not needed, and have decided to deprecate it. 2) The specification of 5FE in the IETF is expected to achieve RFC status in 2Q2020. 3) We have initiated discussion on the specification of the RG-LWAC as part of WT-456, for the phase 16.1. 4) We recommend that 3GPP specifies the following new IEs at the N2 interface: AGF-ID, GlobalAGF-ID, UserLocationInformationAGF 5) We are looking to complete protocol work for the support of NAS exchange across Y4. We would like 3GPP to confirm that the maximum length of a NAS message can exceed 1490 bytes, to assist us in finalizing the design. We kindly request that you take this information into account and please advise us with respect to items #4 and #5 above. We are looking forward to continuing our fruitful collaboration. Sincerely, Lincoln Lavoie, Broadband Forum Technical Committee Chair","secretary_remarks":"Response drafted in S2-2000610. Final response in S2-2001124","agenda_item_sort_order":26,"ainumber":"7.2","ainame":"Wireless and Wireline Convergence for the 5G system architecture (5WWC)","tdoc_agenda_sort_order":13970,"status":"replied to","reservation_date":"2019-12-18 15:23:44","uploaded":"2020-01-06 08:48:38","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG SA, SA WG2, CT WG1, RAN WG3","Cc":"","lsoriginalls":"LIAISE-363","lsreply":"S2-2001124","link":"http:\/\/www.3gpp.org\/ftp\/TSG_SA\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2000030.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2000233","title":"Support of Wireline access requires both N1 signalling and N2 signalling","source":"Nokia, Nokia Shanghai Bell","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Remove the wrong NOTE","secretary_remarks":"Revised in parallel session to S2-2001061.","agenda_item_sort_order":26,"ainumber":"7.2","ainame":"Wireless and Wireline Convergence for the 5G system architecture (5WWC)","tdoc_agenda_sort_order":14430,"status":"revised","reservation_date":"2020-01-03 15:45:44","uploaded":"2020-01-07 13:10:27","revisionof":"","revisedto":"S2-2001061","release":"Rel-16","crspec":"23.501","crspecversion":"16.3.0","workitem":[{"winame":"5WWC"}],"crnumber":2027.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2000233.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2000339","title":"Corrections to 5G-RG and FN-RG procedures","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify the text in clause 7.2.2.1 and 7.2.2.2 describing that the SMC proceudre is optional for 5G-RG and FN-RG respectively. Clarify the aplicability for step 2d for 5G-RG in 7.2.3.1, and remove the applicability of step 2d for FN-RG in clause 7.2.3.2.","secretary_remarks":"Revised in parallel session to S2-2001007.","agenda_item_sort_order":26,"ainumber":"7.2","ainame":"Wireless and Wireline Convergence for the 5G system architecture (5WWC)","tdoc_agenda_sort_order":14320,"status":"revised","reservation_date":"2020-01-06 01:09:31","uploaded":"2020-01-07 14:25:04","revisionof":"","revisedto":"S2-2001007","release":"Rel-16","crspec":"23.316","crspecversion":"16.2.0","workitem":[{"winame":"5WWC"}],"crnumber":63.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2000339.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2000340","title":"Resolving Editor's notes for Hybrid Access \/ ATSSS","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Remove editor's notes. Clarifications.","secretary_remarks":"Agreed in parallel session. Block approved","agenda_item_sort_order":26,"ainumber":"7.2","ainame":"Wireless and Wireline Convergence for the 5G system architecture (5WWC)","tdoc_agenda_sort_order":14250,"status":"agreed","reservation_date":"2020-01-06 01:09:33","uploaded":"2020-01-07 13:59:51","revisionof":"","revisedto":"","release":"Rel-16","crspec":"23.316","crspecversion":"16.2.0","workitem":[{"winame":"5WWC"}],"crnumber":64.0,"crrevision":"","crcategory":"F","tsg_crp":"SP-200068","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2000340.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2000431","title":"Remove a batch of ENs for WWC","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Remove a batch of ENs as above and corresponding clarifications are given.","secretary_remarks":"Revised in parallel session to S2-2001005.","agenda_item_sort_order":26,"ainumber":"7.2","ainame":"Wireless and Wireline Convergence for the 5G system architecture (5WWC)","tdoc_agenda_sort_order":14230,"status":"revised","reservation_date":"2020-01-06 14:57:22","uploaded":"2020-01-07 08:52:20","revisionof":"","revisedto":"S2-2001005","release":"Rel-16","crspec":"23.316","crspecversion":"16.2.0","workitem":[{"winame":"5WWC"}],"crnumber":65.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2000431.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2000433","title":"Location information for UE behind 5G-RG using trusted Non-3GPP based solution","source":"Huawei, Hisilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add the interactions between two AMFs to receive User Location information during UE registration procedure.","secretary_remarks":"Revision of unhandled S2-1911752 from S2#136. Noted in parallel session","agenda_item_sort_order":26,"ainumber":"7.2","ainame":"Wireless and Wireline Convergence for the 5G system architecture (5WWC)","tdoc_agenda_sort_order":14420,"status":"noted","reservation_date":"2020-01-06 14:57:23","uploaded":"2020-01-07 08:52:20","revisionof":"S2-1911752","revisedto":"","release":"Rel-16","crspec":"23.316","crspecversion":"16.2.0","workitem":[{"winame":"5WWC"}],"crnumber":62.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2000433.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2000444","title":"TS23.501 - Correction on User Location Information","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add the User Location Information for N5CW device, which includes TWAP identifier.","secretary_remarks":"Revised in parallel session to S2-2001008.","agenda_item_sort_order":26,"ainumber":"7.2","ainame":"Wireless and Wireline Convergence for the 5G system architecture (5WWC)","tdoc_agenda_sort_order":14350,"status":"revised","reservation_date":"2020-01-06 14:57:32","uploaded":"2020-01-07 08:52:20","revisionof":"","revisedto":"S2-2001008","release":"Rel-16","crspec":"23.501","crspecversion":"16.3.0","workitem":[{"winame":"5WWC"}],"crnumber":2047.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2000444.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2000469","title":"Configuration of URSP for FN RG","source":"Nokia, Nokia Shanghai Bell","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: A W-AGF needs to be able to determine the (DNN, S-NSSAI) parameters of the PDU Sessions it requests on behalf of a FN RG. The W-AGF requests such PDU Sessions upon data trigger (e.g. PPPoE , DHCP, \u2026) received over a data path identified by a VLAN; this is defined in BBF specifications. Thus the W-AGF needs to be configured to request different PDU Sessions for different VLAN terminated at different FN RG (the VLAN configuration may not be homogeneous for a W-AGF service area that may serve different Wireline access networks with different VLAN configurations). The corresponding W-AGF configuration about parameters of the PDU Sesssions to request corresponds to URSP that the W-AGF receives from the PCF (as the W-AGF acts as a 3GPP UE from 5GC perspective). Such URSP(s) map VLAN(s) on the V interface of the W-AGF (identifying the target service of the corresponding data flows : e.g. internet \/ IMS Voice \/ IPTV) towards PDU Session parameters: DNN, S-NSSAI, SSC mode, etc.. Such configuration (the VLAN values in the URSP) needs to be co-ordinated with the VLAN values actually used on the Wireline AN Connecting the FN RG, keeping in mind that the goal of the 5GC connectivity is to not require operator changes to this configuration. For FN RG, the 5GC offers a NEF API allowing for a FN RG (identified by its GLI) to associate a VLAN value at the V interface of the W-AGF (URSP \/ traffic descriptor) with proper URSP output parameters (URSP \/ Route selection components).","secretary_remarks":"Revised in parallel session to S2-2001006.","agenda_item_sort_order":26,"ainumber":"7.2","ainame":"Wireless and Wireline Convergence for the 5G system architecture (5WWC)","tdoc_agenda_sort_order":14260,"status":"revised","reservation_date":"2020-01-06 16:28:55","uploaded":"2020-01-07 13:10:27","revisionof":"","revisedto":"S2-2001006","release":"Rel-16","crspec":"23.316","crspecversion":"16.2.0","workitem":[{"winame":"5WWC"}],"crnumber":1829.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2000469.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2000520","title":"Clarify scope and interworking with 5GC","source":"BlackBerry UK Ltd.","contact":"John-Luc Bakker","contact-id":37326,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Take into acocunt WLANs connected to 5GC.","secretary_remarks":"Revised in parallel session to S2-2001062.","agenda_item_sort_order":26,"ainumber":"7.2","ainame":"Wireless and Wireline Convergence for the 5G system architecture (5WWC)","tdoc_agenda_sort_order":14460,"status":"revised","reservation_date":"2020-01-06 19:05:15","uploaded":"2020-01-07 13:48:23","revisionof":"","revisedto":"S2-2001062","release":"Rel-16","crspec":"23.402","crspecversion":"16.0.0","workitem":[{"winame":"5WWC"}],"crnumber":2995.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2000520.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2000610","title":"[DRAFT] Reply LS to BBF on general status of work","source":"Huawei, Hisilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"LS out","for":"Approval","abstract":"Reference alignment on 5WWC needs to be done based on BBF LS-363 of general states of work","secretary_remarks":"Response to S2-2000030. Revised in parallel session to S2-2001002.","agenda_item_sort_order":26,"ainumber":"7.2","ainame":"Wireless and Wireline Convergence for the 5G system architecture (5WWC)","tdoc_agenda_sort_order":14050,"status":"revised","reservation_date":"2020-01-07 04:54:25","uploaded":"2020-01-07 08:27:24","revisionof":"","revisedto":"S2-2001002","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"5WWC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"BBF","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2000610.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2000675","title":"Reference Alignment with BBF","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Reference of WT-470 is introduced firstly; Addition of reference WT-457 for FN-RG related description.","secretary_remarks":"Revised in parallel session to S2-2001004.","agenda_item_sort_order":26,"ainumber":"7.2","ainame":"Wireless and Wireline Convergence for the 5G system architecture (5WWC)","tdoc_agenda_sort_order":14210,"status":"revised","reservation_date":"2020-01-07 07:25:35","uploaded":"2020-01-07 08:27:24","revisionof":"","revisedto":"S2-2001004","release":"Rel-16","crspec":"23.316","crspecversion":"16.2.0","workitem":[{"winame":"5WWC"}],"crnumber":1831.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2000675.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2000676","title":"Support of location information for UE behind 5G-RG via W-5GAN using trusted Non-3GPP access","source":"Huawei, Hisilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"WITHDRAWN: Summary of change: Add Global Line ID as location information for UE if UE is behind 5G-BRG via W-5GBAN using trusted Non-3GPP access. Add Global Cable ID as location information for UE if UE is behind 5G-CRG via W-5GCAN using trusted Non-3GPP access.","secretary_remarks":"Revision of unhandled S2-1911753 from S2#136. Withdrawn","agenda_item_sort_order":26,"ainumber":"7.2","ainame":"Wireless and Wireline Convergence for the 5G system architecture (5WWC)","tdoc_agenda_sort_order":14410,"status":"withdrawn","reservation_date":"2020-01-07 07:25:36","uploaded":"2020-01-07 08:52:20","revisionof":"S2-1911753","revisedto":"","release":"Rel-16","crspec":"23.501","crspecversion":"16.3.0","workitem":[{"winame":"5WWC"}],"crnumber":1827.0,"crrevision":3.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2000676.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2000677","title":"TS23.316 - Correction on User Location Information","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: For all types of RG, GLI is used as ULI on wireline access. For all types of CRG, GCI together with HFC Node ID are used as ULI on Cable access.","secretary_remarks":"Revised in parallel session to S2-2001009.","agenda_item_sort_order":26,"ainumber":"7.2","ainame":"Wireless and Wireline Convergence for the 5G system architecture (5WWC)","tdoc_agenda_sort_order":14370,"status":"revised","reservation_date":"2020-01-07 07:25:37","uploaded":"2020-01-07 08:52:20","revisionof":"","revisedto":"S2-2001009","release":"Rel-16","crspec":"23.316","crspecversion":"16.2.0","workitem":[{"winame":"5WWC"}],"crnumber":1832.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2000677.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2000946","title":"LS from CableLabs: GCI and HFC_Identifier","source":"CableLabs","contact":"Jennifer Andreoli-Fang","contact-id":59177,"tdoctype":"LS in","for":"Information","abstract":"Dear Colleagues, CableLabs thanks SA WG2 for LS S2-1912767 regarding further clarifications on GLI\/GCI and Line ID\/ HFC_Identifier. This document provides responses to each of the questions SA WG2 has raised to CableLabs. 1. SA WG2 has removed the definition of the Line ID from 23.316 as this identifier should be defined by BBF. Likewise the GLI (and GCI) are expected to be defined by BBF (by CableLabs). This includes the definition and coding of the identifier of the Line ID source, of the HFC Node ID and of the HFC_Identifier. Action: SA WG2 kindly asks BBF, CableLabs and CT WG4 to take the above information into account. CableLabs response: CableLabs will take this into account and will update CableLabs released documentation to include the definitions of GCI, HFC Node ID and HFC_Identifier. 2. SA WG2 kindly asks to clarify whether the deployment scenario where the operator that is owning Wireline or Cable subscriptions cannot be identified by a PLMN ID is an actual scenario, for example when the 5G Core is deployed by a wireline or Cable only operator. Action: SA WG2 kindly asks BBF and CableLabs to answer to the Question in the bullet 2 above. CableLabs response: The deployment scenario where the operator that is owning Cable subscriptions and cannot be identified by as assigned and registered PLMN ID is an actual scenario in future deployments. For example, an operator owning cable subscriptions may deploy access technologies for the specific use of an enterprise or vertical customer. As convergence features increase, operators may increasingly select a 5G core to support a variety of non-3GPP access networks. In these cases, the operator of the 5G core may not be associated with an assigned PLMN ID. Operators that do not have a registered PLMN ID may select to use MCC = 999 per ITU recommendations in certain scenarios. 3. The overall format of SUPI \/ SUCI \/ ULI used to support RG connection to 5GC should be specified in TS 23.003 with references to BBF and CableLabs specifications where applicable (e.g. for the Line ID, Line ID source, HFC Node ID and HFC_Identifier). Action: SA WG2 kindly asks BBF and CableLabs to provide the requested definitions (as mentioned in the items 1 and 3) above in their specifications. CableLabs response: CableLabs will include the requested definitions, as mentioned in the items 1 and 3 above, in updated formally released documentation. The HFC_Identifier is an octet string and may contain a cable modem MAC address or an overall HFC account identifier, as defined by CableLabs in DOCSIS MULPI. The HFC_Identifier is unique within an operator's domain. The encoding of the HFC_Identifier for the purposes of 5WWC is the data type MacAddr48 which is presently used in 29.571. As noted in section 4.7.4 of 23.316, if the SUPI contains an HFC_Identifier, the SUPI also needs to contain an identifier of the operator administrating the HFC_Identifier value. An example with the HFC_Identifier with the operator ID is shown below: 00-00-5E-00-53-00@operator.com The HFC Node ID, which is used to build location information, is provisioned by the operator and encoded as a string of up to six characters in length. Sincerely Belal Hamzeh Chief Technology Officer CableLabs","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":26,"ainumber":"7.2","ainame":"Wireless and Wireline Convergence for the 5G system architecture (5WWC)","tdoc_agenda_sort_order":13980,"status":"noted","reservation_date":"2020-01-08 15:50:52","uploaded":"2020-01-08 15:52:16","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"CT WG4","lsoriginalls":"LS Jan 6, 2020","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2000946.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2001002","title":"[DRAFT] Reply LS to BBF on general status of work","source":"Huawei, Hisilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"LS out","for":"Approval","abstract":"Reference alignment on 5WWC needs to be done based on BBF LS-363 of general states of work","secretary_remarks":"Revision of S2-2000610. Revised in parallel session to S2-2001124.","agenda_item_sort_order":26,"ainumber":"7.2","ainame":"Wireless and Wireline Convergence for the 5G system architecture (5WWC)","tdoc_agenda_sort_order":14060,"status":"revised","reservation_date":"2020-01-14 20:12:22","uploaded":"2020-01-18 01:47:52","revisionof":"S2-2000610","revisedto":"S2-2001124","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"5WWC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"BBF","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2001002.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2001003","title":"[DRAFT} LS forwarding S2-2000028 to CT WG4","source":"SA WG2","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG4. Attachment: S2-2000028","secretary_remarks":"Created at meeting. Revised in parallel session to S2-2001118.","agenda_item_sort_order":26,"ainumber":"7.2","ainame":"Wireless and Wireline Convergence for the 5G system architecture (5WWC)","tdoc_agenda_sort_order":14000,"status":"revised","reservation_date":"2020-01-14 20:12:22","uploaded":"2020-01-18 01:47:52","revisionof":"","revisedto":"S2-2001118","release":"","crspec":"","crspecversion":"","workitem":[{"winame":"5WWC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG4","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2001003.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2001004","title":"Reference Alignment with BBF","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Reference of WT-470 is introduced firstly; Addition of reference WT-457 for FN-RG related description.","secretary_remarks":"Revision of S2-2000675. Agreed in parallel session. Block approved","agenda_item_sort_order":26,"ainumber":"7.2","ainame":"Wireless and Wireline Convergence for the 5G system architecture (5WWC)","tdoc_agenda_sort_order":14220,"status":"agreed","reservation_date":"2020-01-14 20:12:22","uploaded":"2020-01-18 01:47:52","revisionof":"S2-2000675","revisedto":"","release":"Rel-16","crspec":"23.316","crspecversion":"16.2.0","workitem":[{"winame":"5WWC"}],"crnumber":1831.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-200068","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2001004.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2001005","title":"Remove a batch of ENs for WWC","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Remove a batch of ENs as above and corresponding clarifications are given.","secretary_remarks":"Revision of S2-2000431. Agreed in parallel session. Block approved","agenda_item_sort_order":26,"ainumber":"7.2","ainame":"Wireless and Wireline Convergence for the 5G system architecture (5WWC)","tdoc_agenda_sort_order":14240,"status":"agreed","reservation_date":"2020-01-14 20:12:23","uploaded":"2020-01-18 01:47:52","revisionof":"S2-2000431","revisedto":"","release":"Rel-16","crspec":"23.316","crspecversion":"16.2.0","workitem":[{"winame":"5WWC"}],"crnumber":65.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-200068","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2001005.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2001006","title":"Configuration of URSP for FN RG","source":"Nokia, Nokia Shanghai Bell","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: A W-AGF needs to be able to determine the (DNN, S-NSSAI) parameters of the PDU Sessions it requests on behalf of a FN RG. The W-AGF requests such PDU Sessions upon data trigger (e.g. PPPoE , DHCP, \u2026) received over a data path identified by a VLAN; this is defined in BBF specifications. Thus the W-AGF needs to be configured to request different PDU Sessions for different VLAN terminated at different FN RG (the VLAN configuration may not be homogeneous for a W-AGF service area that may serve different Wireline access networks with different VLAN configurations). The corresponding W-AGF configuration about parameters of the PDU Sesssions to request corresponds to URSP that the W-AGF receives from the PCF (as the W-AGF acts as a 3GPP UE from 5GC perspective). Such URSP(s) map VLAN(s) on the V interface of the W-AGF (identifying the target service of the corresponding data flows : e.g. internet \/ IMS Voice \/ IPTV) towards PDU Session parameters: DNN, S-NSSAI, SSC mode, etc.. Such configuration (the VLAN values in the URSP) needs to be co-ordinated with the VLAN values actually used on the Wireline AN Connecting the FN RG, keeping in mind that the goal of the 5GC connectivity is to not require operator changes to this configuration. For FN RG, the 5GC offers a NEF API allowing for a FN RG (identified by its GLI) to associate a VLAN value at the V interface of the W-AGF (URSP \/ traffic descriptor) with proper URSP output parameters (URSP \/ Route selection components).","secretary_remarks":"Revision of S2-2000469. Corrupt document. Revised in parallel session to S2-2001120.","agenda_item_sort_order":26,"ainumber":"7.2","ainame":"Wireless and Wireline Convergence for the 5G system architecture (5WWC)","tdoc_agenda_sort_order":14270,"status":"revised","reservation_date":"2020-01-14 20:12:24","uploaded":"2020-01-18 01:47:52","revisionof":"S2-2000469","revisedto":"S2-2001120","release":"Rel-16","crspec":"23.316","crspecversion":"16.2.0","workitem":[{"winame":"5WWC"}],"crnumber":1829.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2001006.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2001007","title":"Corrections to 5G-RG and FN-RG procedures","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify the text in clause 7.2.2.1 and 7.2.2.2 describing that the SMC proceudre is optional for 5G-RG and FN-RG respectively. Clarify the aplicability for step 2d for 5G-RG in 7.2.3.1, and remove the applicability of step 2d for FN-RG in clause 7.2.3.2.","secretary_remarks":"Revision of S2-2000339. Revised in parallel session to S2-2001119.","agenda_item_sort_order":26,"ainumber":"7.2","ainame":"Wireless and Wireline Convergence for the 5G system architecture (5WWC)","tdoc_agenda_sort_order":14330,"status":"revised","reservation_date":"2020-01-14 20:12:25","uploaded":"2020-01-18 01:47:52","revisionof":"S2-2000339","revisedto":"S2-2001119","release":"Rel-16","crspec":"23.316","crspecversion":"16.2.0","workitem":[{"winame":"5WWC"}],"crnumber":63.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2001007.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2001008","title":"TS23.501 - Correction on User Location Information","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add the User Location Information for N5CW device, which includes TWAP identifier.","secretary_remarks":"Revision of S2-2000444. Agreed in parallel session. Block approved","agenda_item_sort_order":26,"ainumber":"7.2","ainame":"Wireless and Wireline Convergence for the 5G system architecture (5WWC)","tdoc_agenda_sort_order":14360,"status":"agreed","reservation_date":"2020-01-14 20:12:27","uploaded":"2020-01-18 01:47:52","revisionof":"S2-2000444","revisedto":"","release":"Rel-16","crspec":"23.501","crspecversion":"16.3.0","workitem":[{"winame":"5WWC"}],"crnumber":2047.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-200068","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2001008.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2001009","title":"TS23.316 - Correction on User Location Information","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: For all types of RG, GLI is used as ULI on wireline access. For all types of CRG, HFC Node ID are used as ULI on Cable access.","secretary_remarks":"Revision of S2-2000677. Revised in parallel session to S2-2001122.","agenda_item_sort_order":26,"ainumber":"7.2","ainame":"Wireless and Wireline Convergence for the 5G system architecture (5WWC)","tdoc_agenda_sort_order":14380,"status":"revised","reservation_date":"2020-01-14 20:12:28","uploaded":"2020-01-18 01:47:52","revisionof":"S2-2000677","revisedto":"S2-2001122","release":"Rel-16","crspec":"23.316","crspecversion":"16.2.0","workitem":[{"winame":"5WWC"}],"crnumber":1832.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2001009.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2001061","title":"Support of Wireline access requires both N1 signalling and N2 signalling","source":"Nokia, Nokia Shanghai Bell, Ericsson","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Remove the wrong NOTE","secretary_remarks":"Revision of S2-2000233. Revised in parallel session to S2-2001123.","agenda_item_sort_order":26,"ainumber":"7.2","ainame":"Wireless and Wireline Convergence for the 5G system architecture (5WWC)","tdoc_agenda_sort_order":14440,"status":"revised","reservation_date":"2020-01-14 20:13:24","uploaded":"2020-01-18 01:47:52","revisionof":"S2-2000233","revisedto":"S2-2001123","release":"Rel-16","crspec":"23.501","crspecversion":"16.3.0","workitem":[{"winame":"5WWC"}],"crnumber":2027.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2001061.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2001062","title":"Clarify scope and interworking with 5GC","source":"BlackBerry UK Ltd.","contact":"John-Luc Bakker","contact-id":37326,"tdoctype":"CR","for":"Approval","abstract":"WITHDRAWN: Summary of change: Take into acocunt WLANs connected to 5GC.","secretary_remarks":"Revision of S2-2000520. Withdrawn","agenda_item_sort_order":26,"ainumber":"7.2","ainame":"Wireless and Wireline Convergence for the 5G system architecture (5WWC)","tdoc_agenda_sort_order":14470,"status":"withdrawn","reservation_date":"2020-01-14 20:13:25","uploaded":null,"revisionof":"S2-2000520","revisedto":"","release":"Rel-16","crspec":"23.402","crspecversion":"16.0.0","workitem":[{"winame":"5WWC"}],"crnumber":2995.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2001117","title":"[DRAFT] LS on outcome of RAT type discussion","source":"SA WG2","contact":"Laurent Thiebaut","contact-id":72921,"tdoctype":"LS out","for":"Approval","abstract":"To: BBF, CableLabs","secretary_remarks":"Revision of S2-2001003. Revised in parallel session to S2-2001618.","agenda_item_sort_order":26,"ainumber":"7.2","ainame":"Wireless and Wireline Convergence for the 5G system architecture (5WWC)","tdoc_agenda_sort_order":14030,"status":"revised","reservation_date":"2020-01-18 01:18:59","uploaded":"2020-01-18 01:47:54","revisionof":"","revisedto":"S2-2001618","release":"","crspec":"","crspecversion":"","workitem":[{"winame":"5WWC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"BBF, CableLabs","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2001117.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2001118","title":"[DRAFT} LS forwarding S2-2000028 to CT WG4","source":"SA WG2","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG4. Attachment: S2-2000028","secretary_remarks":"Revision of S2-2001003. Revised in parallel session to S2-2001617.","agenda_item_sort_order":26,"ainumber":"7.2","ainame":"Wireless and Wireline Convergence for the 5G system architecture (5WWC)","tdoc_agenda_sort_order":14010,"status":"revised","reservation_date":"2020-01-18 01:18:59","uploaded":"2020-01-18 01:47:54","revisionof":"S2-2001003","revisedto":"S2-2001617","release":"","crspec":"","crspecversion":"","workitem":[{"winame":"5WWC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG4","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2001118.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2001119","title":"Corrections to 5G-RG and FN-RG procedures","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify the text in clause 7.2.2.1 and 7.2.2.2 describing that the SMC proceudre is optional for 5G-RG and FN-RG respectively. Clarify the aplicability for step 2d for 5G-RG in 7.2.3.1, and remove the applicability of step 2d for FN-RG in clause 7.2.3.2.","secretary_remarks":"Revision of S2-2001007. Agreed in parallel session. Block approved","agenda_item_sort_order":26,"ainumber":"7.2","ainame":"Wireless and Wireline Convergence for the 5G system architecture (5WWC)","tdoc_agenda_sort_order":14340,"status":"agreed","reservation_date":"2020-01-18 01:18:59","uploaded":"2020-01-18 01:47:54","revisionof":"S2-2001007","revisedto":"","release":"Rel-16","crspec":"23.316","crspecversion":"16.2.0","workitem":[{"winame":"5WWC"}],"crnumber":63.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"SP-200068","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2001119.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2001120","title":"Configuration of URSP for FN RG","source":"Nokia, Nokia Shanghai Bell","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: A W-AGF needs to be able to determine the (DNN, S-NSSAI) parameters of the PDU Sessions it requests on behalf of a FN RG. The W-AGF requests such PDU Sessions upon data trigger (e.g. PPPoE , DHCP, \u2026) received over a data path identified by a VLAN; this is defined in BBF specifications. Thus the W-AGF needs to be configured to request different PDU Sessions for different VLAN terminated at different FN RG (the VLAN configuration may not be homogeneous for a W-AGF service area that may serve different Wireline access networks with different VLAN configurations). The corresponding W-AGF configuration about parameters of the PDU Sesssions to request corresponds to URSP that the W-AGF receives from the PCF (as the W-AGF acts as a 3GPP UE from 5GC perspective). Such URSP(s) map VLAN(s) on the V interface of the W-AGF (identifying the target service of the corresponding data flows : e.g. internet \/ IMS Voice \/ IPTV) towards PDU Session parameters: DNN, S-NSSAI, SSC mode, etc.. Such configuration (the VLAN values in the URSP) needs to be co-ordinated with the VLAN values actually used on the Wireline AN Connecting the FN RG, keeping in mind that the goal of the 5GC connectivity is to not require operator changes to this configuration.","secretary_remarks":"Revision of S2-2001006. Revised in parallel session to S2-2001121.","agenda_item_sort_order":26,"ainumber":"7.2","ainame":"Wireless and Wireline Convergence for the 5G system architecture (5WWC)","tdoc_agenda_sort_order":14280,"status":"revised","reservation_date":"2020-01-18 01:19:00","uploaded":"2020-01-18 01:47:54","revisionof":"S2-2001006","revisedto":"S2-2001121","release":"Rel-16","crspec":"23.316","crspecversion":"16.2.0","workitem":[{"winame":"5WWC"}],"crnumber":1829.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2001120.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2001121","title":"Configuration of URSP for FN RG","source":"Nokia, Nokia Shanghai Bell","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: A W-AGF needs to be able to determine the (DNN, S-NSSAI) parameters of the PDU Sessions it requests on behalf of a FN RG. The W-AGF requests such PDU Sessions upon data trigger (e.g. PPPoE , DHCP, \u2026) received over a data path identified by a VLAN; this is defined in BBF specifications. Thus the W-AGF needs to be configured to request different PDU Sessions for different VLAN terminated at different FN RG (the VLAN configuration may not be homogeneous for a W-AGF service area that may serve different Wireline access networks with different VLAN configurations). The corresponding W-AGF configuration about parameters of the PDU Sesssions to request corresponds to URSP that the W-AGF receives from the PCF (as the W-AGF acts as a 3GPP UE from 5GC perspective). Such URSP(s) map VLAN(s) on the V interface of the W-AGF (identifying the target service of the corresponding data flows : e.g. internet \/ IMS Voice \/ IPTV) towards PDU Session parameters: DNN, S-NSSAI, SSC mode, etc.. Such configuration (the VLAN values in the URSP) needs to be co-ordinated with the VLAN values actually used on the Wireline AN Connecting the FN RG, keeping in mind that the goal of the 5GC connectivity is to not require operator changes to this configuration.","secretary_remarks":"Revision of S2-2001120. Revised in parallel session to S2-2001623.","agenda_item_sort_order":26,"ainumber":"7.2","ainame":"Wireless and Wireline Convergence for the 5G system architecture (5WWC)","tdoc_agenda_sort_order":14290,"status":"revised","reservation_date":"2020-01-18 01:19:01","uploaded":"2020-01-18 01:47:54","revisionof":"S2-2001120","revisedto":"S2-2001623","release":"Rel-16","crspec":"23.316","crspecversion":"16.2.0","workitem":[{"winame":"5WWC"}],"crnumber":1829.0,"crrevision":3.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2001121.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2001122","title":"TS23.316 - Correction on User Location Information","source":"Huawei, HiSilicon, Nokia, Nokia Shanghai Bell","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: For all types of RG, GLI is used as ULI on wireline access. For all types of CRG, HFC Node ID are used as ULI on Cable access.","secretary_remarks":"Revision of S2-2001009. Revised in parallel session to S2-2001619.","agenda_item_sort_order":26,"ainumber":"7.2","ainame":"Wireless and Wireline Convergence for the 5G system architecture (5WWC)","tdoc_agenda_sort_order":14390,"status":"revised","reservation_date":"2020-01-18 01:19:02","uploaded":"2020-01-18 01:47:54","revisionof":"S2-2001009","revisedto":"S2-2001619","release":"Rel-16","crspec":"23.316","crspecversion":"16.2.0","workitem":[{"winame":"5WWC"}],"crnumber":1832.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2001122.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2001123","title":"Support of Wireline access requires both N1 signalling and N2 signalling","source":"Nokia, Nokia Shanghai Bell, Ericsson","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Remove the wrong NOTE","secretary_remarks":"Revision of S2-2001061. Agreed in parallel session. Block approved","agenda_item_sort_order":26,"ainumber":"7.2","ainame":"Wireless and Wireline Convergence for the 5G system architecture (5WWC)","tdoc_agenda_sort_order":14450,"status":"agreed","reservation_date":"2020-01-18 01:19:03","uploaded":"2020-01-18 01:47:54","revisionof":"S2-2001061","revisedto":"","release":"Rel-16","crspec":"23.501","crspecversion":"16.3.0","workitem":[{"winame":"5WWC"}],"crnumber":2027.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"SP-200068","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2001123.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2001124","title":"LS on Reply to General Status of Work","source":"SA WG2","contact":"Marco Spini","contact-id":8356,"tdoctype":"LS out","for":"Approval","abstract":"To: BBF. Attachments: TS 23.316 CR1831, TS 23.501 CR2033.","secretary_remarks":"Revision of S2-2001002. Agreed in parallel session. Block approved","agenda_item_sort_order":26,"ainumber":"7.2","ainame":"Wireless and Wireline Convergence for the 5G system architecture (5WWC)","tdoc_agenda_sort_order":14070,"status":"approved","reservation_date":"2020-01-18 01:19:04","uploaded":"2020-01-18 01:47:54","revisionof":"S2-2001002","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"5WWC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2000030","lsto":"BBF","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2001124.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2001617","title":"Forwarding LS on definition of GLI","source":"SA WG2","contact":"Di Zhang","contact-id":60523,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG4, RAN WG3. CC: BBF. Attachments: S2-2000028","secretary_remarks":"Revision of S2-2001118. Agreed in parallel session. Block approved","agenda_item_sort_order":26,"ainumber":"7.2","ainame":"Wireless and Wireline Convergence for the 5G system architecture (5WWC)","tdoc_agenda_sort_order":14020,"status":"approved","reservation_date":"2020-01-18 01:20:26","uploaded":"2020-01-18 02:07:52","revisionof":"S2-2001118","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":[{"winame":"5WWC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG4, RAN WG3","Cc":"BBF","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2001617.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2001618","title":"LS on the on outcome of RAT type discussion","source":"SA WG2","contact":"Laurent Thiebaut","contact-id":72921,"tdoctype":"LS out","for":"Approval","abstract":"To: BFF, CableLabs. Attachments: 23.501 CR2033 (S2-2001149) + 23.316 CR1833 (S2-2001106)","secretary_remarks":"Revision of S2-2001117. Agreed in parallel session. Block approved","agenda_item_sort_order":26,"ainumber":"7.2","ainame":"Wireless and Wireline Convergence for the 5G system architecture (5WWC)","tdoc_agenda_sort_order":14040,"status":"approved","reservation_date":"2020-01-18 01:20:26","uploaded":"2020-01-18 02:07:52","revisionof":"S2-2001117","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":[{"winame":"5WWC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"BBF, CableLabs","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2001618.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2001619","title":"TS23.316 - Correction on User Location Information","source":"Huawei, HiSilicon, Nokia, Nokia Shanghai Bell","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: For all types of RG, GLI is used as ULI on wireline access. For all types of CRG, HFC Node ID are used as ULI on Cable access.","secretary_remarks":"Revision of S2-2001122. Agreed in parallel session. Block approved","agenda_item_sort_order":26,"ainumber":"7.2","ainame":"Wireless and Wireline Convergence for the 5G system architecture (5WWC)","tdoc_agenda_sort_order":14400,"status":"agreed","reservation_date":"2020-01-18 01:20:26","uploaded":"2020-01-18 02:07:52","revisionof":"S2-2001122","revisedto":"","release":"Rel-16","crspec":"23.316","crspecversion":"16.2.0","workitem":[{"winame":"5WWC"}],"crnumber":1832.0,"crrevision":3.0,"crcategory":"F","tsg_crp":"SP-200068","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2001619.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2001623","title":"Configuration of URSP for FN RG","source":"Nokia, Nokia Shanghai Bell","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: A W-AGF needs to be able to determine the (DNN, S-NSSAI) parameters of the PDU Sessions it requests on behalf of a FN RG. The W-AGF requests such PDU Sessions upon data trigger (e.g. PPPoE , DHCP, \u2026) received over a data path identified by a VLAN; this is defined in BBF specifications. Thus the W-AGF needs to be configured to request different PDU Sessions for different VLAN terminated at different FN RG (the VLAN configuration may not be homogeneous for a W-AGF service area that may serve different Wireline access networks with different VLAN configurations). The corresponding W-AGF configuration about parameters of the PDU Sesssions to request corresponds to URSP that the W-AGF receives from the PCF (as the W-AGF acts as a 3GPP UE from 5GC perspective). Such URSP(s) map VLAN(s) on the V interface of the W-AGF (identifying the target service of the corresponding data flows : e.g. internet \/ IMS Voice \/ IPTV) towards PDU Session parameters: DNN, S-NSSAI, SSC mode, etc.. Such configuration (the VLAN values in the URSP) needs to be co-ordinated with the VLAN values actually used on the Wireline AN Connecting the FN RG, keeping in mind that the goal of the 5GC connectivity is to not require operator changes to this configuration.","secretary_remarks":"Revision of S2-2001121. Revised to S2-2001624.","agenda_item_sort_order":26,"ainumber":"7.2","ainame":"Wireless and Wireline Convergence for the 5G system architecture (5WWC)","tdoc_agenda_sort_order":14170,"status":"revised","reservation_date":"2020-01-18 01:20:30","uploaded":"2020-01-18 02:07:52","revisionof":"S2-2001121","revisedto":"S2-2001624","release":"Rel-16","crspec":"23.316","crspecversion":"16.2.0","workitem":[{"winame":"5WWC"}],"crnumber":1829.0,"crrevision":4.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2001623.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2001624","title":"Configuration of URSP for FN RG","source":"Nokia, Nokia Shanghai Bell","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: A W-AGF needs to be able to determine the (DNN, S-NSSAI) parameters of the PDU Sessions it requests on behalf of a FN RG. The W-AGF requests such PDU Sessions upon data trigger (e.g. PPPoE , DHCP, \u2026) received over a data path identified by a VLAN; this is defined in BBF specifications. Thus the W-AGF needs to be configured to request different PDU Sessions for different VLAN terminated at different FN RG (the VLAN configuration may not be homogeneous for a W-AGF service area that may serve different Wireline access networks with different VLAN configurations). The corresponding W-AGF configuration about parameters of the PDU Sesssions to request corresponds to URSP that the W-AGF receives from the PCF (as the W-AGF acts as a 3GPP UE from 5GC perspective). Such URSP(s) map VLAN(s) on the V interface of the W-AGF (identifying the target service of the corresponding data flows : e.g. internet \/ IMS Voice \/ IPTV) towards PDU Session parameters: DNN, S-NSSAI, SSC mode, etc.. Such configuration (the VLAN values in the URSP) needs to be co-ordinated with the VLAN values actually used on the Wireline AN Connecting the FN RG, keeping in mind that the goal of the 5GC connectivity is to not require operator changes to this configuration.","secretary_remarks":"Revision of S2-2001623. Agreed in parallel session. Block approved","agenda_item_sort_order":26,"ainumber":"7.2","ainame":"Wireless and Wireline Convergence for the 5G system architecture (5WWC)","tdoc_agenda_sort_order":14310,"status":"agreed","reservation_date":"2020-01-18 01:20:31","uploaded":"2020-01-18 02:07:52","revisionof":"S2-2001623","revisedto":"","release":"Rel-16","crspec":"23.316","crspecversion":"16.2.0","workitem":[{"winame":"5WWC"}],"crnumber":1829.0,"crrevision":5.0,"crcategory":"F","tsg_crp":"SP-200068","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2001624.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]