[{"name":"S2-2002623","title":"LS from SA WG3LI: LS on uniqueness of PEI in certain FN-RG configurations","source":"SA WG3LI","contact":"Jeffrey Gray","contact-id":61557,"tdoctype":"LS in","for":"Action","abstract":"SA WG3-LI would like to get some clarification on the following aspects of the uniqueness of PEI in certain FN-RG configurations. SA WG3-LI understands that in many implementations, networks enforce MAC locking such that an FN-RG has to be unique in a network. SA WG3-LI considers an FN-RG to be a UE from a regulatory perspective, per TS 23.316 clause 4.2.6 'UE is replaced by FN-RG', thus all requirements for a 3GPP UE apply to the FN-RG as specified in TS 33.126. SA WG3-LI kindly asks SA WG3 and SA WG2 to consider that when each UE has a globally unique PEI, the ability for the Lawful Interception aspects to operate normally can be standardized by SA WG3-LI. However, if the PEI is not globally unique, this will lead to problems for LI including the potential to deliver interception product for UEs not under warrant. For LI and security procedures in the overall 3GPP system to work as intended, the PEI is required to be trusted and globally unique. SA WG3-LI kindly asks that this be taken into consideration during continuing system design. Action: SA WG3-LI asks SA WG2 and SA WG3 to take the above into account when developing a solution.","secretary_remarks":"Postponed S2-2001794 from S2#137E. Postponed","agenda_item_sort_order":25,"ainumber":"7.2","ainame":"Wireless and Wireline Convergence for the 5G system architecture (5WWC)","tdoc_agenda_sort_order":12370,"status":"postponed","reservation_date":"2020-03-26 10:57:37","uploaded":"2020-03-27 13:44:13","revisionof":"S2-2001794","revisedto":"S2-2003521","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, SA WG3","Cc":"","lsoriginalls":"s3i200069","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_138e_Electronic\/Docs\/S2-2002623.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-2002626","title":"LS from CableLabs: Status and Evolution of 5WWC","source":"CableLabs","contact":"Bernie Mckibben","contact-id":13024,"tdoctype":"LS in","for":"Information","abstract":"Dear Colleagues, CableLabs is aware that the proposed 5WWC study item as described in SP-191200 was not accepted as part of the scope in 3GPP release 17. CableLabs works with many operators who view the following convergence features to be of high priority in addition to those already standardized in 3GPP R16: - How to improve the support of L2 Bridge 5G-RG scenario for providing connectivity to devices behind the RG. This is similar to BBF requirements expressed in LS BBF-291\/S2-1903875; - How to improve the support of QoS for UE connected behind an RG via Untrusted and Trusted Non-3GPP access. It is important that these convergence features and future converged core network evolution be included in 3GPP work planning. CableLabs requests SA plenary and SA WG2 take this information into account for future release planning. Sincerely Belal Hamzeh Chief Technology Officer CableLabs","secretary_remarks":"Postponed S2-2001798 from S2#137E. Noted","agenda_item_sort_order":25,"ainumber":"7.2","ainame":"Wireless and Wireline Convergence for the 5G system architecture (5WWC)","tdoc_agenda_sort_order":12380,"status":"noted","reservation_date":"2020-03-26 10:57:37","uploaded":"2020-03-27 13:44:13","revisionof":"S2-2001798","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG SA, SA WG2","Cc":"","lsoriginalls":"LS to SA2 5WWC status from CableLabs","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_138e_Electronic\/Docs\/S2-2002626.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-2002627","title":"LS from CableLabs: RAT Type for Wireline Access","source":"CableLabs","contact":"Bernie Mckibben","contact-id":13024,"tdoctype":"LS in","for":"Information","abstract":"Dear Colleagues, CableLabs thanks SA WG2 for LS S2-2001618 regarding the outcome of RAT type discussions in SA WG2. CableLabs has reviewed LS S2-2001618, and referenced 23.501 CR2033 (S2-2001685), and 23.316 CR1833 (S2-2001106). CableLabs would like to provide the following input on the RAT type for wireline access. Operators may select to have separate policies for traffic management, packet prioritization, service tiers and charging partially dependent upon the wireline technology employed in the access network. Therefore, it is important for the 5G core to distinguish between the HFC technology and other technologies used for the wireline access network. The 3GPP CRs suggest using the RG location information to determine the technology employed in the wireline access network. While this method provides a means to determine the wireline technology, this is an inferred association between location and wireline technology. An enhanced method would be a direct or explicit reporting of the technology type into the 5G core. CableLabs recognizes that the R16 timeline is quickly coming to a close. Therefore, further enhancements to the reporting of access network technology within the RAT type beyond what is already contained in the referenced CRs may be considered in a future release. CableLabs requests SA WG2 take this information into account. Sincerely Belal Hamzeh Chief Technology Officer CableLabs","secretary_remarks":"Postponed S2-2001799 from S2#137E. Noted","agenda_item_sort_order":25,"ainumber":"7.2","ainame":"Wireless and Wireline Convergence for the 5G system architecture (5WWC)","tdoc_agenda_sort_order":12390,"status":"noted","reservation_date":"2020-03-26 10:57:37","uploaded":"2020-03-27 13:44:13","revisionof":"S2-2001799","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"","lsoriginalls":"LS to SA2 RAT type from CableLabs","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_138e_Electronic\/Docs\/S2-2002627.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-2002632","title":"LS from BBF: Clarification on encryption requirements for AGF interfaces (N1, N2, N3) [WWC]","source":"BBF","contact":"Lincoln Lavoie","contact-id":39231,"tdoctype":"LS in","for":"Information","abstract":"Dear colleagues, We wish to clarify security requirements for AGF interfaces, as specified in WT-456 (AGF Functional Requirements), currently in straw ballot phase. W-AGF is expected to be in the same trusted boundaries as the AMF\/SMF (5G CN) of the service provider. In case of FN-RG (legacy RG which does not support N1, by contrast to 5G-RG, that supports N1), W-AGF emulates the N1 endpoint for the FN-RGs. 3GPP TS 33.501 currently implies that wireline access is a category of non-3GPP access. The result of which all the security requirements which apply to N3IWF would apply to W-AGF as well. This is not consistent with what is specified in WT-456, in the AGF Security section. WT-456 stipulates the following: 1. The SUPI generated from the wireline LINE-ID for a FN-RG is encoded into SUCI using null scheme. a. SUPI in case of FN-RG is not related to subscriber identity, it is based on information obtained from the wireline access network. 2. The AS\/NAS Messages generated by W-AGF on behalf of a FN-RG can use Null Integrity Protection Algorithm for Integrity Protection and can use Null Ciphering Algorithm a. It is Optional to Implement Integrity protection and ciphering for AS\/NAS Messages 3. For the N2 reference point security in case of W-AGF, a. It is Optional to Implement \/ Use is Operator's decision to apply IPSec\/DTLS. b. An external security gateway can be used to provide IPSec\/DTLS based encryption in case the Operator wants to secure the N2 endpoints. 4. For the N3 reference point security in case of W-AGF, a. It is Optional to Implement \/ Use is Operator's decision to apply IPSec. b. An external security gateway can be used to provide IPSec based encryption in case the Operator wants to secure the N3 endpoints. 5. In deployments of co-located W-AGF and UPF, the N3 reference point security is not applicable, as it is internal to the combined implementation. We suggest you consider updating TS 33.501 to be consistent with these requirements. Note: Wireline networks do not use encryption in today's deployments, and it has been deemed not necessary by operators, as detailed in our previous liaison BBF LIAISE-318. Forcing encryption for 5G Wireline Wireless Convergence could significantly increase the complexity of the infrastructure, driving network service providers to stay away from WWC and the benefits of extending the 5G core network to wireline access. Thanks, Lincoln Lavoie, Broadband Forum Technical Committee Chair","secretary_remarks":"Noted","agenda_item_sort_order":25,"ainumber":"7.2","ainame":"Wireless and Wireline Convergence for the 5G system architecture (5WWC)","tdoc_agenda_sort_order":12400,"status":"noted","reservation_date":"2020-03-26 10:57:37","uploaded":"2020-03-27 15:57:56","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG3, SA WG2, CT WG1, CT WG4, RAN WG3","Cc":"","lsoriginalls":"LIAISE-382-03","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_138e_Electronic\/Docs\/S2-2002632.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-2002633","title":"LS from CT WG1: Reply LS on general status of work","source":"CT WG1","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Information","abstract":"CT WG1 would like to thank Broadband Forum for the LS (LIAISE-363\/C1-200211) on General Status of Work. Broadband Forum's LS states: ----------------- 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. ----------------- CT WG1 confirms that the maximum length of a NAS message can exceed 1490 bytes. NOTE: E.g. SUCI contained in a NAS message can be longer than 3000 octets, according to TS 33.501.","secretary_remarks":"Noted","agenda_item_sort_order":25,"ainumber":"7.2","ainame":"Wireless and Wireline Convergence for the 5G system architecture (5WWC)","tdoc_agenda_sort_order":12410,"status":"noted","reservation_date":"2020-03-26 10:57:37","uploaded":"2020-03-27 15:57:56","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"Broadband Forum","Cc":"TSG SA, SA WG2, RAN WG3","lsoriginalls":"C1-200309","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_138e_Electronic\/Docs\/S2-2002633.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-2002651","title":"LS from CT WG4: Reply LS on Further clarifications on GLI\/GCI and Line ID\/ HFC_Identifier","source":"CT WG4","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Action","abstract":"CT WG4 thanks SA WG2 for their LS (S2-1912767) on clarifications on GLI\/GCI and Line ID\/ HFC_Identifier. CT WG4 has agreed 23.003 CRs defining: - the NAI format for a SUPI containing a GCI or GLI - the NAI format for a SUCI containing a GCI or GLI - the User Location for an RG accessing the 5GC via W-5GCAN or W-5GBAN. Action: CT WG4 kindly asks SA WG2, BBF and CableLabs groups to take the above information into account.","secretary_remarks":"Noted","agenda_item_sort_order":25,"ainumber":"7.2","ainame":"Wireless and Wireline Convergence for the 5G system architecture (5WWC)","tdoc_agenda_sort_order":12420,"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, BBF, CableLabs","Cc":"CT WG1, SA WG3, RAN WG3","lsoriginalls":"C4-201220","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_138e_Electronic\/Docs\/S2-2002651.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-2002686","title":"Removing explicit signaling of RG-TMBR","source":"Nokia, Nokia Shanghai Bell","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Remove references to RG-TMBR in 23.316","secretary_remarks":"e-meeting r02 agreed. Revised, merging S2-2003085, to S2-2003435.","agenda_item_sort_order":25,"ainumber":"7.2","ainame":"Wireless and Wireline Convergence for the 5G system architecture (5WWC)","tdoc_agenda_sort_order":12460,"status":"revised","reservation_date":"2020-04-06 09:55:17","uploaded":"2020-04-10 17:28:33","revisionof":"","revisedto":"S2-2003435","release":"Rel-16","crspec":23.316,"crspecversion":"16.3.0","workitem":[{"winame":"5WWC"}],"crnumber":2038.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-2002686.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-2002734","title":"Handover of a PDU Session procedure between 3GPP and trusted non-3GPP access","source":"China Telecom","contact":"Yingbin Niu","contact-id":86757,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add a new clause 4.9.x for 'Handover of a PDU Session procedure between 3GPP and trusted non-3GPP access'.","secretary_remarks":"e-meeting r01 agreed. Revised to S2-2003436.","agenda_item_sort_order":25,"ainumber":"7.2","ainame":"Wireless and Wireline Convergence for the 5G system architecture (5WWC)","tdoc_agenda_sort_order":12480,"status":"revised","reservation_date":"2020-04-08 06:25:29","uploaded":"2020-04-08 07:04:43","revisionof":"","revisedto":"S2-2003436","release":"Rel-16","crspec":23.502,"crspecversion":"16.4.0","workitem":[{"winame":"5WWC"}],"crnumber":2183.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-2002734.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-2002762","title":"Corrections of RG procedures","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: - Apply a consistent terminology for N2 message names in 23.316, aligning with NGAP - Include PLMN ID as part of AN-level parameters in Registration procedures - Correct AS- and NAS-level parameters in FN-RG Registration procedure.","secretary_remarks":"e-meeting r04 agreed. Revised to S2-2003437.","agenda_item_sort_order":25,"ainumber":"7.2","ainame":"Wireless and Wireline Convergence for the 5G system architecture (5WWC)","tdoc_agenda_sort_order":12500,"status":"revised","reservation_date":"2020-04-08 20:16:57","uploaded":"2020-04-10 19:30:54","revisionof":"","revisedto":"S2-2003437","release":"Rel-16","crspec":23.316,"crspecversion":"16.3.0","workitem":[{"winame":"5WWC"}],"crnumber":2039.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-2002762.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-2002999","title":"Correction on RAT types of wireline access","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Correct the title of 4.7.10 to RAT types dedicated for wireline access","secretary_remarks":"e-meeting r01 agreed. Revised to S2-2003438.","agenda_item_sort_order":25,"ainumber":"7.2","ainame":"Wireless and Wireline Convergence for the 5G system architecture (5WWC)","tdoc_agenda_sort_order":12520,"status":"revised","reservation_date":"2020-04-10 09:04:04","uploaded":"2020-04-10 11:29:19","revisionof":"","revisedto":"S2-2003438","release":"Rel-16","crspec":23.316,"crspecversion":"16.3.0","workitem":[{"winame":"5WWC"}],"crnumber":2040.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-2002999.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-2003000","title":"Correction on RAT type","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Make a correction on the definition of RAT type. Clarify the RAT type for different access network.","secretary_remarks":"e-meeting r01 agreed. Revised to S2-2003439.","agenda_item_sort_order":25,"ainumber":"7.2","ainame":"Wireless and Wireline Convergence for the 5G system architecture (5WWC)","tdoc_agenda_sort_order":12540,"status":"revised","reservation_date":"2020-04-10 09:04:05","uploaded":"2020-04-10 11:29:19","revisionof":"","revisedto":"S2-2003439","release":"Rel-16","crspec":23.501,"crspecversion":"16.4.0","workitem":[{"winame":"5WWC"}],"crnumber":2308.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-2003000.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-2003001","title":"Correction on identifiers of N3 terminations and conditions for N5CW devices","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The list of identifiers of N3 terminations sent from TNGF and TWIF should be a FQDN and\/or IP address(es). N5CW devices shall have registered to 5GC over 3GPP before they connect to Trusted WLAN access network. AMF shall send the SUPI of N5CW device derived in the registration procedure for 3GPP access to the AUSF.","secretary_remarks":"Noted","agenda_item_sort_order":25,"ainumber":"7.2","ainame":"Wireless and Wireline Convergence for the 5G system architecture (5WWC)","tdoc_agenda_sort_order":12560,"status":"noted","reservation_date":"2020-04-10 09:04:06","uploaded":"2020-04-10 11:29:19","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.502,"crspecversion":"16.4.0","workitem":[{"winame":"5WWC"}],"crnumber":2246.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-2003001.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-2003002","title":"Correction on wireline access and reference point between N5CW device and TWAP","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Change the name of reference point between the N5CW devices and TWAP to Yt'. The list of identifiers of N3 terminations should be a FQDN and\/or IP addess(es).","secretary_remarks":"Approved","agenda_item_sort_order":25,"ainumber":"7.2","ainame":"Wireless and Wireline Convergence for the 5G system architecture (5WWC)","tdoc_agenda_sort_order":12570,"status":"agreed","reservation_date":"2020-04-10 09:04:07","uploaded":"2020-04-10 11:29:19","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.501,"crspecversion":"16.4.0","workitem":[{"winame":"5WWC"}],"crnumber":2309.0,"crrevision":"","crcategory":"F","tsg_crp":"SP-200427","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_138e_Electronic\/Docs\/S2-2003002.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-2003003","title":"Correction on wireline access","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Delete the sentence of 'using the GCI of the CRG as defined in clause 4.7.9'. Change the word '5G-RG' to 'FN-RG'. The list of identifiers of W-AGF should be a FQDN and\/or IP address(es).","secretary_remarks":"e-meeting r01 agreed. Revised to S2-2003440.","agenda_item_sort_order":25,"ainumber":"7.2","ainame":"Wireless and Wireline Convergence for the 5G system architecture (5WWC)","tdoc_agenda_sort_order":12580,"status":"revised","reservation_date":"2020-04-10 09:04:08","uploaded":"2020-04-10 11:29:19","revisionof":"","revisedto":"S2-2003440","release":"Rel-16","crspec":23.316,"crspecversion":"16.3.0","workitem":[{"winame":"5WWC"}],"crnumber":2041.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-2003003.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-2003004","title":"Adding SUPI and SUCI for N5GC device support","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add a new clause to describe SUPI and SUCI for N5GC device. The SUPI for N5GC device shall contain a network-specific identifier and shall take the form of Network Access Identifier. Additionally, the SUCI for N5GC device shall have the form of username@realm.","secretary_remarks":"e-meeting r03 agreed. Revised to S2-2003441.","agenda_item_sort_order":25,"ainumber":"7.2","ainame":"Wireless and Wireline Convergence for the 5G system architecture (5WWC)","tdoc_agenda_sort_order":12600,"status":"revised","reservation_date":"2020-04-10 09:04:09","uploaded":"2020-04-10 11:29:19","revisionof":"","revisedto":"S2-2003441","release":"Rel-16","crspec":23.316,"crspecversion":"16.3.0","workitem":[{"winame":"5WWC"}],"crnumber":2042.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-2003004.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-2003085","title":"MBR values for wireline access","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify RG-TMBR and RG-LWAC usage for BBF access. Clarify that UE-AMBR is not applicable to wireline access.","secretary_remarks":"Merged into S2-2003435","agenda_item_sort_order":25,"ainumber":"7.2","ainame":"Wireless and Wireline Convergence for the 5G system architecture (5WWC)","tdoc_agenda_sort_order":12620,"status":"merged","reservation_date":"2020-04-10 11:43:41","uploaded":"2020-04-10 19:32:32","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.316,"crspecversion":"16.3.0","workitem":[{"winame":"5WWC"}],"crnumber":2043.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-2003085.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-2003119","title":"Correction of references causing wrong specification","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: See above","secretary_remarks":"e-meeting r02 agreed. Revised to S2-2003442.","agenda_item_sort_order":25,"ainumber":"7.2","ainame":"Wireless and Wireline Convergence for the 5G system architecture (5WWC)","tdoc_agenda_sort_order":12630,"status":"revised","reservation_date":"2020-04-10 13:27:46","uploaded":"2020-04-10 14:51:29","revisionof":"","revisedto":"S2-2003442","release":"Rel-16","crspec":23.316,"crspecversion":"16.3.0","workitem":[{"winame":"5WWC"}],"crnumber":2044.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-2003119.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-2003142","title":"Sending the IP address of TNGF to UE","source":"Motorola Mobility, Lenovo","contact":"Apostolis Salkintzis","contact-id":22112,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: It is specified that the TNGF sends the TNGF address to UE after it receives the TNGF key from the AMF in step 10a. At this point, the TNGF first sends the TNGF address to UE within an EAP-Request\/5G-Notification packet and then sends the EAP-Success packet after receiving an EAP-Response\/5G-Notification from the UE. Note: The EAP-Request\/5G-Notification is similar to the existing EAP-Request\/AKA-Notification specified in RFC 4187.","secretary_remarks":"Approved","agenda_item_sort_order":25,"ainumber":"7.2","ainame":"Wireless and Wireline Convergence for the 5G system architecture (5WWC)","tdoc_agenda_sort_order":12650,"status":"agreed","reservation_date":"2020-04-10 14:46:59","uploaded":"2020-04-10 15:34:41","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.502,"crspecversion":"16.4.0","workitem":[{"winame":"5WWC"}],"crnumber":2293.0,"crrevision":"","crcategory":"F","tsg_crp":"SP-200427","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_138e_Electronic\/Docs\/S2-2003142.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-2003157","title":"[DRAFT] Reply LS on LS on status of 5WWC work","source":"Nokia, Nokia Shanghai Bell","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"LS out","for":"Approval","abstract":"Reply LS on LS on status of 5WWC work","secretary_remarks":"Response to S2-2001797 (replied to at S2#137E). Response to S2-2003213. e-meeting r01 agreed. Revised to S2-2003434.","agenda_item_sort_order":25,"ainumber":"7.2","ainame":"Wireless and Wireline Convergence for the 5G system architecture (5WWC)","tdoc_agenda_sort_order":12440,"status":"revised","reservation_date":"2020-04-10 16:51:00","uploaded":"2020-04-10 17:28:33","revisionof":"","revisedto":"S2-2003434","release":"Rel-16","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_138e_Electronic\/Docs\/S2-2003157.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-2003213","title":"LS from BBF: LS on status of 5WWC work","source":"BBF","contact":"Lincoln Lavoie","contact-id":39231,"tdoctype":"LS in","for":"Action","abstract":"Dear colleagues, We have several items we would like to advise you of 1. We have evaluated the utility of RG-TMBR and have concluded that the BBF proposed encoding of RG-LWAC provides the same functionality as well as the possibility of encoding additional information more reflective of the wireline environment. We would recommend any protocol work to define and disseminate RG-TMBR be deprecated. 2. Our QOS model corresponds to the distribution of QOS functionality in the 5G System with the following changes: - We do not consider UE-AMBR to be applicable to wireline. The information in the RG-LWAC is sufficient to map PDU session traffic to the wireline resource model and as such is a direct replacement. Therefore if received by a W-AGF it would be ignored. 3. The encoding of RG-LWAC that we have adopted is variable length TLV encoded structure. An excerpted description is appended at the end of this liaison. We would appreciate being advised of the changes to the 5G System with respect to dissemination and protocol encoding of the RG-LWAC object. With respect to the questions in your liaison S2-2002331 Question to BBF: SA WG2 would kindly ask to BBF to confirm whether the W-AGF is able to determine the access technology to which the RG is connected to and whether this information may be used for determining and enforcing the QoS (as described above). We would advise that this information is far from ubiquitously exposed in broadband deployments. Given the several generations of DSLs and PON technology we would be expecting to support and that DSLs rate adapt according to distance we are not clear on how the access type provides useful information. For example, the DSLs under consideration range from a maximum B\/W of 12 Mbit\/s for G.992.3 to a Gbit\/s or more with G.9701. Common practice is to set the service rate comfortably under the maximum achievable rate. As far as setting policy and AMBR values, the provisioning of information to populate RG_LWAC (which is reflective of the service rate) would offer the best source of such information. Thanks, Lincoln Lavoie, Broadband Forum Technical Committee Chair","secretary_remarks":"Response drafted in S2-2003157. Final response in S2-2003434","agenda_item_sort_order":25,"ainumber":"7.2","ainame":"Wireless and Wireline Convergence for the 5G system architecture (5WWC)","tdoc_agenda_sort_order":12430,"status":"replied to","reservation_date":"2020-04-16 16:45:23","uploaded":"2020-04-16 16:45:48","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, CT WG1, CT WG4","Cc":"CableLabs","lsoriginalls":"LIAISE-390","lsreply":"S2-2003434","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_138e_Electronic\/Docs\/S2-2003213.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-2003434","title":"Reply LS on LS on status of 5WWC work","source":"SA WG2","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"LS out","for":"Approval","abstract":"To: BBF, CableLabs. Attachments: 23.316 CR2038 (S2-2003435)","secretary_remarks":"Revision of S2-2003157. Approved","agenda_item_sort_order":25,"ainumber":"7.2","ainame":"Wireless and Wireline Convergence for the 5G system architecture (5WWC)","tdoc_agenda_sort_order":12450,"status":"approved","reservation_date":"2020-04-27 09:10:27","uploaded":"2020-04-28 06:57:52","revisionof":"S2-2003157","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"5WWC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2003213","lsto":"BBF, CableLabs","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_138e_Electronic\/Docs\/S2-2003434.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-2003435","title":"Removing explicit signaling of RG-TMBR","source":"Nokia, Nokia Shanghai Bell, Ericsson","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Remove references to RG-TMBR in 23.316 Clarifying handling RG-LWAC in 5GC","secretary_remarks":"Revision of S2-2002686, merging S2-2003085. Approved","agenda_item_sort_order":25,"ainumber":"7.2","ainame":"Wireless and Wireline Convergence for the 5G system architecture (5WWC)","tdoc_agenda_sort_order":12470,"status":"agreed","reservation_date":"2020-04-27 09:10:27","uploaded":"2020-04-28 06:57:52","revisionof":"S2-2002686","revisedto":"","release":"Rel-16","crspec":23.316,"crspecversion":"16.3.0","workitem":[{"winame":"5WWC"}],"crnumber":2038.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-200427","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_138e_Electronic\/Docs\/S2-2003435.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-2003436","title":"Handover of a PDU Session procedure between 3GPP and trusted non-3GPP access","source":"China Telecom, Motorola Mobility, Lenovo, ZTE","contact":"Yingbin Niu","contact-id":86757,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add a new clause 4.9.3 for 'Handover of a PDU Session procedure between 3GPP and trusted non-3GPP access'.","secretary_remarks":"Revision of S2-2002734. Approved","agenda_item_sort_order":25,"ainumber":"7.2","ainame":"Wireless and Wireline Convergence for the 5G system architecture (5WWC)","tdoc_agenda_sort_order":12490,"status":"agreed","reservation_date":"2020-04-27 09:10:29","uploaded":"2020-04-28 06:57:52","revisionof":"S2-2002734","revisedto":"","release":"Rel-16","crspec":23.502,"crspecversion":"16.4.0","workitem":[{"winame":"5WWC"}],"crnumber":2183.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-200427","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_138e_Electronic\/Docs\/S2-2003436.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-2003437","title":"Corrections of RG procedures","source":"Ericsson, Nokia, Nokia Shanghai Bell","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: - Apply a consistent terminology for N2 message names in 23.316, aligning with NGAP - Correct AS- and NAS-level parameters in FN-RG Registration procedure - In order to support that 'The 5G RG and the network (AUSF) need to agree on the value of the Serving network Id to have a properly shared security context' While PLMN selection is not supported for wireline access, the 5G RG provides a PLMN ID in EAP-5G sent to the AGF. In this version of the specifications, this PLMN ID is the home domain of the SUCI NOTE: this information is transparently transferred from 5G RG to AUSF via the W-AGF and the AMF; it ensures the AUSF and the 5G RG consider the same information for Key derivations defined in 33.501 The W-AGF forwards this information over N2 to the AMF; The AMF forwards this information to the AUSF when asking for UE (5G RG) authentication","secretary_remarks":"Revision of S2-2002762. Approved","agenda_item_sort_order":25,"ainumber":"7.2","ainame":"Wireless and Wireline Convergence for the 5G system architecture (5WWC)","tdoc_agenda_sort_order":12510,"status":"agreed","reservation_date":"2020-04-27 09:10:30","uploaded":"2020-04-28 06:57:52","revisionof":"S2-2002762","revisedto":"","release":"Rel-16","crspec":23.316,"crspecversion":"16.3.0","workitem":[{"winame":"5WWC"}],"crnumber":2039.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-200427","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_138e_Electronic\/Docs\/S2-2003437.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-2003438","title":"Correction on RAT types of wireline access","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Correct the title of 4.7.10 to RAT types dedicated for wireline access","secretary_remarks":"Revision of S2-2002999. Approved","agenda_item_sort_order":25,"ainumber":"7.2","ainame":"Wireless and Wireline Convergence for the 5G system architecture (5WWC)","tdoc_agenda_sort_order":12530,"status":"agreed","reservation_date":"2020-04-27 09:10:31","uploaded":"2020-04-28 06:57:52","revisionof":"S2-2002999","revisedto":"","release":"Rel-16","crspec":23.316,"crspecversion":"16.3.0","workitem":[{"winame":"5WWC"}],"crnumber":2040.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-200427","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_138e_Electronic\/Docs\/S2-2003438.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-2003439","title":"Correction on RAT type","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Make a correction on the definition of RAT type. Clarify the RAT type for different access network.","secretary_remarks":"Revision of S2-2003000. Approved","agenda_item_sort_order":25,"ainumber":"7.2","ainame":"Wireless and Wireline Convergence for the 5G system architecture (5WWC)","tdoc_agenda_sort_order":12550,"status":"agreed","reservation_date":"2020-04-27 09:10:32","uploaded":"2020-04-28 06:57:52","revisionof":"S2-2003000","revisedto":"","release":"Rel-16","crspec":23.501,"crspecversion":"16.4.0","workitem":[{"winame":"5WWC"}],"crnumber":2308.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-200427","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_138e_Electronic\/Docs\/S2-2003439.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-2003440","title":"Correction on wireline access","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Delete the sentence of 'using the GCI of the CRG as defined in clause 4.7.9'. Change the word '5G-RG' to 'FN-RG'. The list of identifiers of W-AGF should be a FQDN and\/or IP address(es).","secretary_remarks":"Revision of S2-2003003. Approved","agenda_item_sort_order":25,"ainumber":"7.2","ainame":"Wireless and Wireline Convergence for the 5G system architecture (5WWC)","tdoc_agenda_sort_order":12590,"status":"agreed","reservation_date":"2020-04-27 09:10:33","uploaded":"2020-04-28 06:57:52","revisionof":"S2-2003003","revisedto":"","release":"Rel-16","crspec":23.316,"crspecversion":"16.3.0","workitem":[{"winame":"5WWC"}],"crnumber":2041.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-200427","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_138e_Electronic\/Docs\/S2-2003440.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-2003441","title":"Adding SUPI and SUCI for N5GC device support","source":"Huawei, HiSilicon, Nokia, Nokia Shanghai Bell","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add a new clause to describe SUPI and SUCI for N5GC device. The SUPI for N5GC device shall contain a network-specific identifier and shall take the form of Network Access Identifier. Additionally, the SUCI for N5GC device shall have the form of username@realm.","secretary_remarks":"Revision of S2-2003004. Approved","agenda_item_sort_order":25,"ainumber":"7.2","ainame":"Wireless and Wireline Convergence for the 5G system architecture (5WWC)","tdoc_agenda_sort_order":12610,"status":"agreed","reservation_date":"2020-04-27 09:10:35","uploaded":"2020-04-28 06:57:52","revisionof":"S2-2003004","revisedto":"","release":"Rel-16","crspec":23.316,"crspecversion":"16.3.0","workitem":[{"winame":"5WWC"}],"crnumber":2042.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-200427","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_138e_Electronic\/Docs\/S2-2003441.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-2003442","title":"Correction of references causing wrong specification","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: See above","secretary_remarks":"Revision of S2-2003119. Approved","agenda_item_sort_order":25,"ainumber":"7.2","ainame":"Wireless and Wireline Convergence for the 5G system architecture (5WWC)","tdoc_agenda_sort_order":12640,"status":"agreed","reservation_date":"2020-04-27 09:10:37","uploaded":"2020-04-28 06:57:52","revisionof":"S2-2003119","revisedto":"","release":"Rel-16","crspec":23.316,"crspecversion":"16.3.0","workitem":[{"winame":"5WWC"}],"crnumber":2044.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-200427","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_138e_Electronic\/Docs\/S2-2003442.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}]