[{"name":"S2-1902942","title":"LS from ETSI TC LI: Reporting All Cell IDs in 5G","source":"ETSI TC LI","contact":"Gerald McQuaid","contact-id":25351,"tdoctype":"LS in","for":"Action","abstract":"Lawful Interception standards have provided for the reporting of the location of a target of interception, if lawfully authorized, since 2G standards were developed. 3G systems and 4G systems continued to support this requirement and at a minimum were able to report the Cell Id of the respective 2G, or 3G, or 4G Cell to which the target (UE) was attached and utilizing for mobile services. With Dual\/Multi Connectivity the UE will be attached to two or more cells, but only the master cell ID is reported to the core network. This means that the secondary cell id(s) to which the UE is actually attached is not currently known to the core network. In case of multi-connectivity, the handover information (e.g., change of secondary cell ID) is also not transmitted to the core network. For LI purposes, the requirement is for the service provider to report the cell ID(s) to which the UE is actually attached, i.e., the secondary cell ID(s) as well as the master cell ID, for mobile services (e.g., internet access services, VoNR). This requirement is not currently fulfilled for Dual\/Multi Connectivity. ETSI TC LI is kindly requesting 3GPP to develop a mechanism to ensure that the all serving cells (including the secondary cell ID(s) and the master cell ID of the cell(s)) attached to by a UE are available to the core network.","secretary_remarks":"Postponed S2-1901419 from S2#131. Response in S2-1904819.","agenda_item_sort_order":21,"ainumber":"6.5.4","ainame":"Security related functions and flows","tdoc_agenda_sort_order":0,"status":"replied to","reservation_date":"2019-03-19 06:14:10","uploaded":"2019-03-29 07:20:30","revisionof":"S2-1901419","revisedto":"S2-1904850","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, CT WG1, CT WG 3, RAN WG3, SA WG3-LI","Cc":"","lsoriginalls":"LI(18)R45019r1","lsreply":"S2-1904819","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1902942.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1902948","title":"LS from SA WG3LI: Reporting All Cell IDs in 5G","source":"SA WG3LI","contact":"Koen Jaspers","contact-id":9291,"tdoctype":"LS in","for":"Action","abstract":"SA WG3LI thanks ETSI TC LI for their LS on 5G cell reporting (LI(18)R45019r1). SA WG3LI agrees to the analysis of TC LI that there is a requirement from law enforcement to have all the cell IDs used by a target in order to increase the probability of getting the most accurate target location reported by the network based on cell IDs. It is SA WG3LI's understanding that Secondary Node Change of 3GPP TS 37.340 does not currently report 5G secondary cells to a 4G or 5G core network. Although the scenario with 5G secondary cells in a 4G network with 4G master cells (EN-DC) is foreseen as a temporary situation, it is not clear how long this situation will remain. In order to meet LI requirements, SA WG3LI requires that secondary CGI is available for all dual\/multi-connectivity scenarios in real-time in the core network. Action: SA WG3LI asks the CT and SA WG2 groups, contingent on RAN WG3 and RAN groups decisions, to enhance their own specifications.","secretary_remarks":"Postponed S2-1901437 from S2#131. Response in S2-1904819.","agenda_item_sort_order":21,"ainumber":"6.5.4","ainame":"Security related functions and flows","tdoc_agenda_sort_order":0,"status":"replied to","reservation_date":"2019-03-19 06:14:10","uploaded":"2019-03-29 07:20:30","revisionof":"S2-1901437","revisedto":"S2-1904852","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"ETSI TC LI, TSG RAN, RAN WG3, SA WG2, TSG CT","Cc":"CT WG1, CT WG3","lsoriginalls":"S3i190043","lsreply":"S2-1904819","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1902948.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1902952","title":"LS from GSMA 5GJA: HTTP\/s SMS roaming interface evolution","source":"GSMA 5GJA","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Action","abstract":"Introduction: The GSMA 5G Joint Activity (5GJA) is responsible for all 5G related items and topics within the Networks Group (NG) domain. The GSMA 5GJA will work in cooperation with GSMA working groups, GSMA program, as well as external organizations. The scope of the GSMA 5GJA includes, but is not limited to, the following topics: \u00b7 - UNI for operator-provided communication services (i.e. Voice, Video, messaging) over 5G - Guidelines for technical aspects of deployment of 5G. - Guidelines for 5G roaming and interconnection. Background: GSMA NG welcomes the Release 15 specifications for the SEPP in 3GPP to protect the HTTP-based signalling via the N32 reference point between VPMN and HPMN when both PMNs are using the service-based 5G Core Network. Based on discussion in 5GJA#5 on 7 November 2018, GSMA 5GJA also see a need for SMS roaming interface to benefit from this security improvement. By also including the SMS roaming interface based on HTTP\/S to compliment the MAP and Diameter interfaces already proposed, it will be possible to provide integrity and confidentiality protection for the SMS user plane. Without HTTP\/S for SMS roaming interface and associated policy enforcement provided by SEPP, SMS would be excluded from the 5G design objective to secure all roaming interfaces. Action: to TSG SA and SA WG2: TSG SA and it associated working group of SA WG2 are kindly requested to include this requirement of the SMS roaming architecture to also use the HTTP\/s interface and SEPP security enforcement, and also when such specifications providing a solution will be made available.","secretary_remarks":"Postponed S2-1902182 from S2#131. Noted in parallel session","agenda_item_sort_order":21,"ainumber":"6.5.4","ainame":"Security related functions and flows","tdoc_agenda_sort_order":12820,"status":"noted","reservation_date":"2019-03-19 06:14:10","uploaded":"2019-03-29 07:20:31","revisionof":"S2-1902182","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG SA, SA WG2","Cc":"CT WG4","lsoriginalls":"5GJA5_120","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1902952.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1902986","title":"Correction to the provisioning of the UE Integrity Protection Data Rate capability","source":"Qualcomm Incorporated","contact":"Faccin Stefano","contact-id":79506,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Correct the text referring to the UE providing the UE Integrity Protection Data Rate capability as part of the 5GSM capability.","secretary_remarks":"Agreed in parallel session This was Block approved","agenda_item_sort_order":21,"ainumber":"6.5.4","ainame":"Security related functions and flows","tdoc_agenda_sort_order":12850,"status":"agreed","reservation_date":"2019-03-27 22:03:20","uploaded":"2019-04-02 00:27:54","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.5.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":1032.0,"crrevision":"","crcategory":"F","tsg_crp":"SP-190399","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1902986.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1902987","title":"Correction to the provisioning of the UE Integrity Protection Data Rate capability","source":"Qualcomm Incorporated","contact":"Faccin Stefano","contact-id":79506,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Correct the text referring to the UE providing the UE Integrity Protection Data Rate capability as part of the 5GSM capability.","secretary_remarks":"Revised in parallel session to S2-1904575.","agenda_item_sort_order":21,"ainumber":"6.5.4","ainame":"Security related functions and flows","tdoc_agenda_sort_order":12920,"status":"revised","reservation_date":"2019-03-27 22:05:18","uploaded":"2019-04-02 00:27:54","revisionof":"","revisedto":"S2-1904575","release":"Rel-15","crspec":23.502,"crspecversion":"15.5.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":1123.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1902987.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1903032","title":"LS from CT WG1: LS on reporting all Cell IDs in 5G","source":"CT WG1","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Information","abstract":"CT WG1 thanks SA WG3-LI for their LS on reporting all Cell IDs in 5G. In the LS, SA WG3-LI 'requires that secondary CGI is available for all dual\/multi-connectivity scenarios in real-time in the core network'. CT WG1's understanding is that this requirement does not require any UE functionality.","secretary_remarks":"Response in S2-1904819.","agenda_item_sort_order":21,"ainumber":"6.5.4","ainame":"Security related functions and flows","tdoc_agenda_sort_order":0,"status":"replied to","reservation_date":"2019-03-29 08:08:03","uploaded":"2019-03-29 10:31:47","revisionof":"","revisedto":"S2-1904858","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG3LI","Cc":"ETSI TC LI, TSG RAN, RAN WG3, SA WG2, TSG CT, CT WG3","lsoriginalls":"C1-191388","lsreply":"S2-1904819","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1903032.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1903060","title":"LS from RAN WG2: Reply LS on Enforcement of maximum supported data rate for integrity protection","source":"RAN WG2","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Action","abstract":"RAN WG2 thanks RAN WG3 and SA WG2 for the LS responses on LS on Enforcement of maximum supported data rate for integrity protection. RAN WG2 had previously discussed and agreed that UE behaviour on exceeding the maximum supported data rate for integrity protection will be left to UE implementation. RAN WG2 will not specify any UE behaviour for this case in Rel-15. RAN WG2 would also like to point out that normally the network should avoid the situation where the UE maximum supported data rate is exceeded but understand this may not be possible in all cases. Action: RAN WG2 kindly asks RAN WG3 and SA WG2 to take note of the RAN WG2 agreement.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":21,"ainumber":"6.5.4","ainame":"Security related functions and flows","tdoc_agenda_sort_order":12840,"status":"noted","reservation_date":"2019-03-29 08:08:04","uploaded":"2019-03-29 10:31:48","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG3, SA WG2","Cc":"SA WG3","lsoriginalls":"R2-1902700","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1903060.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1903071","title":"LS from RAN WG3: Response LS on reporting all cell IDs in 5G","source":"RAN WG3","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Information","abstract":"RAN WG3 would like to thank SA WG3-LI for the LS on Reporting All Cell IDs in 5G. RAN WG3 has discussed the matter and enabled a mechanism for Dual Connectivity with 5G, equal to the existing mechanism for LTE and 5G stand-alone: When needed, the Secondary Node reports the secondary serving cell (PSCell) information to the Master Node when the secondary serving cell is selected and then, when it changes; the Master Node reports it then back to the Core Network. There were doubts whether this solution causes excessive signaling in the RAN. A possible mitigation to this drawback is to add a flag from the Core Network to indicate whether PSCell shall be reported. This can be added as an enhancement to the current solution.","secretary_remarks":"Response drafted in S2-1904571. Final response in S2-1904819","agenda_item_sort_order":21,"ainumber":"6.5.4","ainame":"Security related functions and flows","tdoc_agenda_sort_order":12640,"status":"replied to","reservation_date":"2019-03-29 08:08:04","uploaded":"2019-03-29 10:31:48","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG3LI","Cc":"TSG SA, SA WG2, SA WG3, TSG RAN, TSG CT, CT WG1, CT WG3, ETSI TC LI","lsoriginalls":"R3-191111","lsreply":"S2-1904819","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1903071.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1903084","title":"LS from TSG SA: Reply LS on User Plane Security for 5GC Roaming","source":"TSG SA","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Information","abstract":"TSG SA would like to inform GSMA 5GJA that SA has reviewed the liaison statement from GSMA 5GJA on User Plane Security for 5GC Roaming in SP-190006 and would like to provide additional guidance to GSMA 5GJA on actions being taken by 3GPP to address the issues raised by GSMA 5GJA. Within release 15 timescales it has not been possible to add new functionality to N9 to address the issues raised by GSMA 5GJA. However, the following text has been added to TS 33.501 clause 13.3.2 to mitigate the security risk raised by GSMA 5GJA; - 'The present document does not provide a standardised solution for binding 5G SBA REST Service Operations between the PLMN V-SMF and H-SMF over N16 \/ N32 to GTP-U over N9 in roaming scenarios. To prevent injection or spoofing of UP traffic over N9, it is recommended to use a common firewall that can correlate HTTP\/2 methods and GTP-U in order to bind and filter out any malicious traffic on N9. Use of a common firewall may place other implementation restrictions (e.g. co-location of SMF, SEPP and UPF) in order to allow use of a common firewall.' Within the scope of release 16, SA WG3 have extended their study on SBA Security Enhancements for release 16 (FS_SBA-SEC) to include binding of SBA signalling sessions to N9 sessions and to develop the necessary N9 security function to achieve this. Once SA WG3 have concluded their study, it is expected that SA WG2 and SA WG3 will undertake any necessary normative work to fully address the issues raised by GSMA 5GJA within release 16 timescales. SA WG3 consider that this may require a function equivalent to the SEPP used on N32 to be standardised on N9.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":21,"ainumber":"6.5.4","ainame":"Security related functions and flows","tdoc_agenda_sort_order":12830,"status":"noted","reservation_date":"2019-03-29 08:08:04","uploaded":"2019-03-29 10:31:48","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"GSMA 5GJA","Cc":"SA WG3, SA WG2","lsoriginalls":"SP-190252","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1903084.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1903227","title":"Clarification on user plane integrity protection","source":"Intel","contact":"Saso Stojanovski","contact-id":24932,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: This CR clarifies that the UE Integrity Protection Data Rate is enforced only in downlink.","secretary_remarks":"Revision of S2-1902180 from S2#131. Revised in parallel session to S2-1904573.","agenda_item_sort_order":21,"ainumber":"6.5.4","ainame":"Security related functions and flows","tdoc_agenda_sort_order":12880,"status":"revised","reservation_date":"2019-04-01 07:58:26","uploaded":"2019-04-02 13:46:01","revisionof":"S2-1902180","revisedto":"S2-1904573","release":"Rel-15","crspec":23.501,"crspecversion":"15.5.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":1023.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1903227.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1903260","title":"Clarification on user plane integrity protection","source":"Intel","contact":"Saso Stojanovski","contact-id":24932,"tdoctype":"CR","for":"Approval","abstract":"Rel-16 mirror CR: Summary of change: This CR clarifies that the UE Integrity Protection Data Rate is enforced only in downlink.","secretary_remarks":"Revised in parallel session to S2-1904574.","agenda_item_sort_order":21,"ainumber":"6.5.4","ainame":"Security related functions and flows","tdoc_agenda_sort_order":12900,"status":"revised","reservation_date":"2019-04-01 09:54:29","uploaded":"2019-04-02 13:46:01","revisionof":"","revisedto":"S2-1904574","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.1","workitem":[{"winame":"5GS_Ph1"}],"crnumber":1090.0,"crrevision":"","crcategory":"A","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1903260.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1903405","title":"Correction to the provisioning of the UE Integrity Protection Data Rate capability","source":"Qualcomm Incorporated","contact":"Faccin Stefano","contact-id":79506,"tdoctype":"CR","for":"Approval","abstract":"Rel-16 mirror CR: Summary of change: Correct the text referring to the UE providing the UE Integrity Protection Data Rate capability as part of the 5GSM capability.","secretary_remarks":"Revised in parallel session to S2-1904572.","agenda_item_sort_order":21,"ainumber":"6.5.4","ainame":"Security related functions and flows","tdoc_agenda_sort_order":12860,"status":"revised","reservation_date":"2019-04-01 21:42:09","uploaded":"2019-04-02 00:27:54","revisionof":"","revisedto":"S2-1904572","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.2","workitem":[{"winame":"5GS_Ph1"},{"winame":"TEI16"}],"crnumber":1132.0,"crrevision":"","crcategory":"A","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1903405.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1903406","title":"Correction to the provisioning of the UE Integrity Protection Data Rate capability","source":"Qualcomm Incorporated","contact":"Faccin Stefano","contact-id":79506,"tdoctype":"CR","for":"Approval","abstract":"Rel-16 mirror CR: Summary of change: Correct the text referring to the UE providing the UE Integrity Protection Data Rate capability as part of the 5GSM capability.","secretary_remarks":"Revised in parallel session to S2-1904576.","agenda_item_sort_order":21,"ainumber":"6.5.4","ainame":"Security related functions and flows","tdoc_agenda_sort_order":12940,"status":"revised","reservation_date":"2019-04-01 21:44:34","uploaded":"2019-04-02 00:27:54","revisionof":"","revisedto":"S2-1904576","release":"Rel-16","crspec":23.502,"crspecversion":"16.0.2","workitem":[{"winame":"5GS_Ph1"},{"winame":"TEI16"}],"crnumber":1198.0,"crrevision":"","crcategory":"A","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1903406.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1903412","title":"Updating LCS procedures for location reporting for multiple cells","source":"OTD","contact":"Jeffrey Gray","contact-id":61557,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Adding requirement for secondary cell reporting when supported.","secretary_remarks":"Revised in parallel session to S2-1904567.","agenda_item_sort_order":21,"ainumber":"6.5.4","ainame":"Security related functions and flows","tdoc_agenda_sort_order":12680,"status":"revised","reservation_date":"2019-04-01 22:18:04","uploaded":"2019-04-02 05:25:29","revisionof":"","revisedto":"S2-1904567","release":"Rel-15","crspec":23.502,"crspecversion":"15.5.1","workitem":[{"winame":"5G_eLCS"}],"crnumber":1199.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1903412.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1903413","title":"Updating LCS procedures for location reporting for multiple cells","source":"OTD","contact":"Jeffrey Gray","contact-id":61557,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Adding requirement for secondary cell reporting when supported for Dual and Multi-Connectivity related NR.","secretary_remarks":"Revised in parallel session to S2-1904569.","agenda_item_sort_order":21,"ainumber":"6.5.4","ainame":"Security related functions and flows","tdoc_agenda_sort_order":12750,"status":"revised","reservation_date":"2019-04-01 22:36:08","uploaded":"2019-04-02 05:25:42","revisionof":"","revisedto":"S2-1904569","release":"Rel-15","crspec":23.401,"crspecversion":"15.7.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":3505.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1903413.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1903865","title":"Knowledge of Secondary Cell Group ID in Core Network - Discussion on LS from SA WG3 LI in S2-1902948 and RAN 3 Response LS in S2-1903071","source":"Vodafone","contact":"Chris Pudney","contact-id":1122,"tdoctype":"discussion","for":"Approval","abstract":"Discussion on LS from SA WG3 LI in S2-1902948 and RAN WG3 Response LS in S2-1903071","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":21,"ainumber":"6.5.4","ainame":"Security related functions and flows","tdoc_agenda_sort_order":12960,"status":"noted","reservation_date":"2019-04-02 14:29:01","uploaded":"2019-04-02 14:32:23","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1903865.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1904567","title":"Updating LCS procedures for location reporting for multiple cells","source":"OTD, Nokia, Nokia Shanghai Bell, Verizon UK Ltd, Telecom Italia","contact":"Jeffrey Gray","contact-id":61557,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Adding requirement for secondary cell reporting when supported. PSCell is added in the definitions and vocabulary via reference to the existing definition in TS 36.331.","secretary_remarks":"Revision of S2-1903412. Revised in parallel session to S2-1904700.","agenda_item_sort_order":21,"ainumber":"6.5.4","ainame":"Security related functions and flows","tdoc_agenda_sort_order":12690,"status":"revised","reservation_date":"2019-04-15 10:39:32","uploaded":"2019-04-15 11:18:01","revisionof":"S2-1903412","revisedto":"S2-1904700","release":"Rel-15","crspec":23.502,"crspecversion":"15.5.1","workitem":[{"winame":"TEI15"},{"winame":"LI15"}],"crnumber":1199.0,"crrevision":1.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1904567.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1904568","title":"Updating LCS procedures for location reporting for multiple cells","source":"OTD, Nokia, Nokia Shanghai Bell, Verizon UK Ltd, Telecom Italia","contact":"Jeffrey Gray","contact-id":61557,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Adding requirement for secondary cell reporting when supported. PSCell is added in the definitions and vocabulary via reference to the existing definition in TS 36.331.","secretary_remarks":"Revised in parallel session to S2-1904701.","agenda_item_sort_order":21,"ainumber":"6.5.4","ainame":"Security related functions and flows","tdoc_agenda_sort_order":12720,"status":"revised","reservation_date":"2019-04-15 10:39:32","uploaded":"2019-04-15 11:18:01","revisionof":"","revisedto":"S2-1904701","release":"Rel-16","crspec":23.502,"crspecversion":"16.0.2","workitem":[{"winame":"TEI15"},{"winame":"LI15"}],"crnumber":1307.0,"crrevision":"","crcategory":"A","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1904568.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1904569","title":"Updating LCS procedures for location reporting for multiple cells","source":"OTD, Nokia, Nokia Shanghai Bell, Verizon UK Ltd, Telecom Italia","contact":"Jeffrey Gray","contact-id":61557,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Adding requirement for secondary serving cell (PSCell) reporting when Dual connectivity with NR is supported. PSCell is added in the definitions and vocabulary via reference to the existing definition in TS 36.331.","secretary_remarks":"Revision of S2-1903413. Revised in parallel session to S2-1904698.","agenda_item_sort_order":21,"ainumber":"6.5.4","ainame":"Security related functions and flows","tdoc_agenda_sort_order":12760,"status":"revised","reservation_date":"2019-04-15 10:41:58","uploaded":"2019-04-15 11:18:01","revisionof":"S2-1903413","revisedto":"S2-1904698","release":"Rel-15","crspec":23.401,"crspecversion":"15.7.0","workitem":[{"winame":"TEI15"},{"winame":"LI15"}],"crnumber":3505.0,"crrevision":1.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1904569.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1904570","title":"Updating LCS procedures for location reporting for multiple cells","source":"OTD, Nokia, Nokia Shanghai Bell, Verizon UK Ltd, Telecom Italia","contact":"Jeffrey Gray","contact-id":61557,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Adding requirement for secondary serving cell (PSCell) reporting when Dual connectivity with NR is supported. PSCell is added in the definitions and vocabulary via reference to the existing definition in TS 36.331.","secretary_remarks":"Revised in parallel session to S2-1904699.","agenda_item_sort_order":21,"ainumber":"6.5.4","ainame":"Security related functions and flows","tdoc_agenda_sort_order":12790,"status":"revised","reservation_date":"2019-04-15 10:41:59","uploaded":"2019-04-15 11:18:01","revisionof":"","revisedto":"S2-1904699","release":"Rel-16","crspec":23.401,"crspecversion":"16.2.0","workitem":[{"winame":"TEI15"},{"winame":"LI15"}],"crnumber":3509.0,"crrevision":"","crcategory":"A","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1904570.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1904571","title":"[DRAFT] Response LS on reporting all cell IDs in 5G","source":"SA WG2","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS out","for":"Approval","abstract":"To: SA WG3-LI. CC: RAN WG3, TSG SA, SA WG3, SA WG5, RAN, CT, CT WG1, CT WG3, CT WG4, ETSI TC LI","secretary_remarks":"Created at meeting. Response to S2-1903071. Revised in parallel session to S2-1904702.","agenda_item_sort_order":21,"ainumber":"6.5.4","ainame":"Security related functions and flows","tdoc_agenda_sort_order":12650,"status":"revised","reservation_date":"2019-04-15 10:42:04","uploaded":"2019-04-15 11:18:01","revisionof":"","revisedto":"S2-1904702","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG3-LI","Cc":"RAN WG3, TSG SA, SA WG3, SA WG5, RAN, CT, CT WG1, CT WG3, CT WG4, ETSI TC LI","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1904571.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1904572","title":"Correction to the provisioning of the UE Integrity Protection Data Rate capability","source":"Qualcomm Incorporated","contact":"Faccin Stefano","contact-id":79506,"tdoctype":"CR","for":"Approval","abstract":"Rel-16 mirror CR: Summary of change: Correct the text referring to the UE providing the UE Integrity Protection Data Rate capability as part of the 5GSM capability.","secretary_remarks":"Revision of S2-1903405. Agreed in parallel session This was Block approved","agenda_item_sort_order":21,"ainumber":"6.5.4","ainame":"Security related functions and flows","tdoc_agenda_sort_order":12870,"status":"agreed","reservation_date":"2019-04-15 10:42:04","uploaded":"2019-04-15 11:18:01","revisionof":"S2-1903405","revisedto":"","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.2","workitem":[{"winame":"5GS_Ph1"}],"crnumber":1132.0,"crrevision":1.0,"crcategory":"A","tsg_crp":"SP-190399","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1904572.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1904573","title":"Clarification on user plane integrity protection","source":"Intel","contact":"Saso Stojanovski","contact-id":24932,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: This CR clarifies that the UE is not required to perform strict enforcement of the Integrity Protection Data Rate in uplink.","secretary_remarks":"Revision of S2-1903227. Postponed","agenda_item_sort_order":21,"ainumber":"6.5.4","ainame":"Security related functions and flows","tdoc_agenda_sort_order":12890,"status":"postponed","reservation_date":"2019-04-15 10:42:05","uploaded":"2019-04-15 11:18:01","revisionof":"S2-1903227","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.5.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":1023.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1904573.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1904574","title":"Clarification on user plane integrity protection","source":"Intel","contact":"Saso Stojanovski","contact-id":24932,"tdoctype":"CR","for":"Approval","abstract":"Rel-16 mirror CR: Summary of change: This CR clarifies that the UE is not required to perform strict enforcement of the Integrity Protection Data Rate in uplink.","secretary_remarks":"Revision of S2-1903260. Postponed","agenda_item_sort_order":21,"ainumber":"6.5.4","ainame":"Security related functions and flows","tdoc_agenda_sort_order":12910,"status":"postponed","reservation_date":"2019-04-15 10:42:07","uploaded":"2019-04-15 11:18:01","revisionof":"S2-1903260","revisedto":"","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.2","workitem":[{"winame":"5GS_Ph1"}],"crnumber":1090.0,"crrevision":1.0,"crcategory":"A","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1904574.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1904575","title":"Correction to the provisioning of the UE Integrity Protection Data Rate capability","source":"Qualcomm Incorporated, LG Electronics, Ericsson","contact":"Faccin Stefano","contact-id":79506,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Correct the text referring to the UE providing the UE Integrity Protection Data Rate capability as part of the 5GSM capability.","secretary_remarks":"Revision of S2-1902987. Agreed in parallel session This was Block approved","agenda_item_sort_order":21,"ainumber":"6.5.4","ainame":"Security related functions and flows","tdoc_agenda_sort_order":12930,"status":"agreed","reservation_date":"2019-04-15 10:42:08","uploaded":"2019-04-15 11:18:01","revisionof":"S2-1902987","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.5.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":1123.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-190400","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1904575.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1904576","title":"Correction to the provisioning of the UE Integrity Protection Data Rate capability","source":"Qualcomm Incorporated, LG Electronics, Ericsson","contact":"Faccin Stefano","contact-id":79506,"tdoctype":"CR","for":"Approval","abstract":"Rel-16 mirror CR: Summary of change: Correct the text referring to the UE providing the UE Integrity Protection Data Rate capability as part of the 5GSM capability.","secretary_remarks":"Revision of S2-1903406. Agreed in parallel session This was Block approved","agenda_item_sort_order":21,"ainumber":"6.5.4","ainame":"Security related functions and flows","tdoc_agenda_sort_order":12950,"status":"agreed","reservation_date":"2019-04-15 10:42:09","uploaded":"2019-04-15 11:18:01","revisionof":"S2-1903406","revisedto":"","release":"Rel-16","crspec":23.502,"crspecversion":"16.0.2","workitem":[{"winame":"5GS_Ph1"}],"crnumber":1198.0,"crrevision":1.0,"crcategory":"A","tsg_crp":"SP-190400","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1904576.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1904698","title":"Updating LCS procedures for location reporting for multiple cells","source":"OTD, Nokia, Nokia Shanghai Bell, Verizon UK Ltd, Telecom Italia","contact":"Jeffrey Gray","contact-id":61557,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Adding requirement for secondary serving cell (PSCell) reporting when Dual connectivity with NR is supported.","secretary_remarks":"Revision of S2-1904569. Revised to S2-1904815.","agenda_item_sort_order":21,"ainumber":"6.5.4","ainame":"Security related functions and flows","tdoc_agenda_sort_order":12770,"status":"revised","reservation_date":"2019-04-15 10:43:55","uploaded":"2019-04-15 11:18:02","revisionof":"S2-1904569","revisedto":"S2-1904815","release":"Rel-15","crspec":23.401,"crspecversion":"15.7.0","workitem":[{"winame":"TEI15"},{"winame":"LI15"}],"crnumber":3505.0,"crrevision":2.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1904698.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1904699","title":"Updating LCS procedures for location reporting for multiple cells","source":"OTD, Nokia, Nokia Shanghai Bell, Verizon UK Ltd, Telecom Italia","contact":"Jeffrey Gray","contact-id":61557,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Adding requirement for secondary serving cell (PSCell) reporting when Dual connectivity with NR is supported.","secretary_remarks":"Revision of S2-1904570. Revised to S2-1904816.","agenda_item_sort_order":21,"ainumber":"6.5.4","ainame":"Security related functions and flows","tdoc_agenda_sort_order":12800,"status":"revised","reservation_date":"2019-04-15 10:43:56","uploaded":"2019-04-15 11:18:02","revisionof":"S2-1904570","revisedto":"S2-1904816","release":"Rel-16","crspec":23.401,"crspecversion":"16.2.0","workitem":[{"winame":"TEI15"},{"winame":"LI15"}],"crnumber":3509.0,"crrevision":1.0,"crcategory":"A","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1904699.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1904700","title":"Updating LCS procedures for location reporting for multiple cells","source":"OTD, Nokia, Nokia Shanghai Bell, Verizon UK Ltd, Telecom Italia","contact":"Jeffrey Gray","contact-id":61557,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Adding requirement for secondary serving cell reporting when supported.","secretary_remarks":"Revision of S2-1904567. Revised to S2-1904817.","agenda_item_sort_order":21,"ainumber":"6.5.4","ainame":"Security related functions and flows","tdoc_agenda_sort_order":12700,"status":"revised","reservation_date":"2019-04-15 10:43:57","uploaded":"2019-04-15 11:18:02","revisionof":"S2-1904567","revisedto":"S2-1904817","release":"Rel-15","crspec":23.502,"crspecversion":"15.5.1","workitem":[{"winame":"TEI15"},{"winame":"LI15"}],"crnumber":1199.0,"crrevision":2.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1904700.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1904701","title":"Updating LCS procedures for location reporting for multiple cells","source":"OTD, Nokia, Nokia Shanghai Bell, Verizon UK Ltd, Telecom Italia","contact":"Jeffrey Gray","contact-id":61557,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Adding requirement for secondary serving cell reporting when supported.","secretary_remarks":"Revision of S2-1904568. Revised to S2-1904818.","agenda_item_sort_order":21,"ainumber":"6.5.4","ainame":"Security related functions and flows","tdoc_agenda_sort_order":12730,"status":"revised","reservation_date":"2019-04-15 10:43:58","uploaded":"2019-04-15 11:18:02","revisionof":"S2-1904568","revisedto":"S2-1904818","release":"Rel-16","crspec":23.502,"crspecversion":"16.0.2","workitem":[{"winame":"TEI15"},{"winame":"LI15"}],"crnumber":1307.0,"crrevision":1.0,"crcategory":"A","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1904701.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1904702","title":"[DRAFT] Response LS on reporting all cell IDs in 5G","source":"SA WG2","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS out","for":"Approval","abstract":"To: SA WG3-LI. CC: RAN WG3, TSG SA, SA WG3, SA WG5, RAN, CT, CT WG1, CT WG3, CT WG4, ETSI TC LI","secretary_remarks":"Revision of S2-1904571. Revised to S2-1904819.","agenda_item_sort_order":21,"ainumber":"6.5.4","ainame":"Security related functions and flows","tdoc_agenda_sort_order":12660,"status":"revised","reservation_date":"2019-04-15 10:43:59","uploaded":"2019-04-15 11:18:02","revisionof":"S2-1904571","revisedto":"S2-1904819","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG3-LI","Cc":"RAN WG3, TSG SA, SA WG3, SA WG5, RAN, CT, CT WG1, CT WG3, CT WG4, ETSI TC LI","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1904702.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1904815","title":"Updating LCS procedures for location reporting for multiple cells","source":"OTD, Nokia, Nokia Shanghai Bell, Verizon UK Ltd, Telecom Italia","contact":"Jeffrey Gray","contact-id":61557,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Adding requirement for secondary serving cell reporting when Dual connectivity with NR is supported.","secretary_remarks":"Revision of S2-1904698. For e-mail approval. e-mail revision 1 approved. Revised to S2-1904832.","agenda_item_sort_order":21,"ainumber":"6.5.4","ainame":"Security related functions and flows","tdoc_agenda_sort_order":12780,"status":"revised","reservation_date":"2019-04-15 10:49:34","uploaded":"2019-04-15 11:18:03","revisionof":"S2-1904698","revisedto":"S2-1904832","release":"Rel-15","crspec":23.401,"crspecversion":"15.7.0","workitem":[{"winame":"TEI15"},{"winame":"LI15"}],"crnumber":3505.0,"crrevision":3.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1904815.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1904816","title":"Updating LCS procedures for location reporting for multiple cells","source":"OTD, Nokia, Nokia Shanghai Bell, Verizon UK Ltd, Telecom Italia","contact":"Jeffrey Gray","contact-id":61557,"tdoctype":"CR","for":"Approval","abstract":"Rel-16 mirror CR: Summary of change: Adding requirement for secondary serving cell reporting when Dual connectivity with NR is supported.","secretary_remarks":"Revision of S2-1904699. For e-mail approval. e-mail revision 2 approved. Revised to S2-1904833.","agenda_item_sort_order":21,"ainumber":"6.5.4","ainame":"Security related functions and flows","tdoc_agenda_sort_order":12810,"status":"revised","reservation_date":"2019-04-15 10:49:35","uploaded":"2019-04-15 11:18:03","revisionof":"S2-1904699","revisedto":"S2-1904833","release":"Rel-16","crspec":23.401,"crspecversion":"16.2.0","workitem":[{"winame":"TEI15"},{"winame":"LI15"}],"crnumber":3509.0,"crrevision":2.0,"crcategory":"A","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1904816.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1904817","title":"Updating LCS procedures for location reporting for multiple cells","source":"OTD, Nokia, Nokia Shanghai Bell, Verizon UK Ltd, Telecom Italia","contact":"Jeffrey Gray","contact-id":61557,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Adding requirement for secondary serving cell reporting when supported.","secretary_remarks":"Revision of S2-1904700. For e-mail approval. e-mail revision 1 approved. Revised to S2-1904834.","agenda_item_sort_order":21,"ainumber":"6.5.4","ainame":"Security related functions and flows","tdoc_agenda_sort_order":12710,"status":"revised","reservation_date":"2019-04-15 10:49:36","uploaded":"2019-04-15 11:18:03","revisionof":"S2-1904700","revisedto":"S2-1904834","release":"Rel-15","crspec":23.502,"crspecversion":"15.5.1","workitem":[{"winame":"TEI15"},{"winame":"LI15"}],"crnumber":1199.0,"crrevision":3.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1904817.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1904818","title":"Updating LCS procedures for location reporting for multiple cells","source":"OTD, Nokia, Nokia Shanghai Bell, Verizon UK Ltd, Telecom Italia","contact":"Jeffrey Gray","contact-id":61557,"tdoctype":"CR","for":"Approval","abstract":"Rel-16 mirror CR: Summary of change: Adding requirement for secondary serving cell reporting when supported.","secretary_remarks":"Revision of S2-1904701. For e-mail approval. e-mail revision 2 approved. Revised to S2-1904835.","agenda_item_sort_order":21,"ainumber":"6.5.4","ainame":"Security related functions and flows","tdoc_agenda_sort_order":12740,"status":"revised","reservation_date":"2019-04-15 10:49:37","uploaded":"2019-04-15 11:18:03","revisionof":"S2-1904701","revisedto":"S2-1904835","release":"Rel-16","crspec":23.502,"crspecversion":"16.0.0","workitem":[{"winame":"TEI15"},{"winame":"LI15"}],"crnumber":1307.0,"crrevision":2.0,"crcategory":"A","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1904818.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1904819","title":"Response LS on reporting all cell IDs in 5G","source":"SA WG2","contact":"Haris Zisimopoulos","contact-id":57197,"tdoctype":"LS out","for":"Approval","abstract":"To: SA WG3-LI. CC: RAN WG3, TSG SA, SA WG3, SA WG5, RAN, CT, CT WG1, CT WG3, CT WG4, ETSI TC LI","secretary_remarks":"Revision of S2-1904702. Approved","agenda_item_sort_order":21,"ainumber":"6.5.4","ainame":"Security related functions and flows","tdoc_agenda_sort_order":12670,"status":"approved","reservation_date":"2019-04-15 10:49:38","uploaded":"2019-04-15 11:18:03","revisionof":"S2-1904702","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-1903071","lsto":"SA WG3-LI","Cc":"RAN WG3, TSG SA, SA WG3, SA WG5, RAN, CT, CT WG1, CT WG3, CT WG4, ETSI TC LI","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1904819.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1904832","title":"Updating LCS procedures for location reporting for multiple cells","source":"OTD, Nokia, Nokia Shanghai Bell, Verizon UK Ltd, Telecom Italia","contact":"Jeffrey Gray","contact-id":61557,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Adding requirement for secondary serving cell reporting when Dual connectivity with NR is supported.","secretary_remarks":"e-mail revision 1 of S2-1904815. This CR was agreed","agenda_item_sort_order":21,"ainumber":"6.5.4","ainame":"Security related functions and flows","tdoc_agenda_sort_order":12781,"status":"agreed","reservation_date":"2019-04-19 10:27:25","uploaded":"2019-04-19 10:29:50","revisionof":"S2-1904815","revisedto":"","release":"Rel-15","crspec":23.401,"crspecversion":"15.7.0","workitem":[{"winame":"EDCE5"},{"winame":"LI15"}],"crnumber":3505.0,"crrevision":4.0,"crcategory":"B","tsg_crp":"SP-190403","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1904832.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1904833","title":"Updating LCS procedures for location reporting for multiple cells","source":"OTD, Nokia, Nokia Shanghai Bell, Verizon UK Ltd, Telecom Italia","contact":"Jeffrey Gray","contact-id":61557,"tdoctype":"CR","for":"Approval","abstract":"Rel-16 mirror CR: Summary of change: Adding requirement for secondary serving cell reporting when Dual connectivity with NR is supported.","secretary_remarks":"e-mail revision 2 of S2-1904816. This CR was agreed","agenda_item_sort_order":21,"ainumber":"6.5.4","ainame":"Security related functions and flows","tdoc_agenda_sort_order":12811,"status":"agreed","reservation_date":"2019-04-19 10:27:27","uploaded":"2019-04-19 10:29:50","revisionof":"S2-1904816","revisedto":"","release":"Rel-16","crspec":23.401,"crspecversion":"16.2.0","workitem":[{"winame":"EDCE5"},{"winame":"LI15"}],"crnumber":3509.0,"crrevision":3.0,"crcategory":"A","tsg_crp":"SP-190403","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1904833.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1904834","title":"Updating LCS procedures for location reporting for multiple cells","source":"OTD, Nokia, Nokia Shanghai Bell, Verizon UK Ltd, Telecom Italia","contact":"Jeffrey Gray","contact-id":61557,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Adding requirement for secondary serving cell reporting when supported.","secretary_remarks":"e-mail revision 1 of S2-1904817. This CR was agreed","agenda_item_sort_order":21,"ainumber":"6.5.4","ainame":"Security related functions and flows","tdoc_agenda_sort_order":12711,"status":"agreed","reservation_date":"2019-04-19 10:27:28","uploaded":"2019-04-19 10:29:50","revisionof":"S2-1904817","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.5.1","workitem":[{"winame":"TEI15"},{"winame":"LI15"}],"crnumber":1199.0,"crrevision":4.0,"crcategory":"B","tsg_crp":"SP-190404","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1904834.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1904835","title":"Updating LCS procedures for location reporting for multiple cells","source":"OTD, Nokia, Nokia Shanghai Bell, Verizon UK Ltd, Telecom Italia","contact":"Jeffrey Gray","contact-id":61557,"tdoctype":"CR","for":"Approval","abstract":"Rel-16 mirror CR: Summary of change: Adding requirement for secondary serving cell reporting when supported.","secretary_remarks":"e-mail revision 2 of S2-1904818. This CR was agreed","agenda_item_sort_order":21,"ainumber":"6.5.4","ainame":"Security related functions and flows","tdoc_agenda_sort_order":12741,"status":"agreed","reservation_date":"2019-04-19 10:27:29","uploaded":"2019-04-19 10:29:50","revisionof":"S2-1904818","revisedto":"","release":"Rel-16","crspec":23.502,"crspecversion":"16.0.0","workitem":[{"winame":"TEI15"},{"winame":"LI15"}],"crnumber":1307.0,"crrevision":3.0,"crcategory":"A","tsg_crp":"SP-190404","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1904835.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]