[{"name":"S2-1910852","title":"LS from CT WG1: LS on sending CAG ID during resume procedure","source":"CT WG1","contact":"Kundan Tiwari","contact-id":66053,"tdoctype":"LS in","for":"Action","abstract":"CT WG1 would like to know whether NAS needs to provide CAG ID to AS during resume procedure when the UE is RRC-INACTIVE mode. Action: CT WG1 asks SA WG2 to kindly provide the answer to the above question.","secretary_remarks":"Postponed S2-1908661 from S2#135. Response drafted in S2-1911002. Final response in S2-1912731","agenda_item_sort_order":34,"ainumber":"7.7.3","ainame":"5GS Enhanced support of Vertical and LAN Services - Type a\/b aspects","tdoc_agenda_sort_order":19440,"status":"replied to","reservation_date":"2019-10-30 08:52:09","uploaded":"2019-11-04 09:40:46","revisionof":"S2-1908661","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"RAN WG2","lsoriginalls":"C1-195157","lsreply":"S2-1912731","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1910852.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1910853","title":"LS from CT WG1: LS on the applicability of the notification procedure in SNPNs","source":"CT WG1","contact":"Lena Chaponniere","contact-id":38080,"tdoctype":"LS in","for":"Action","abstract":"Some companies in CT WG1 think that the notification procedure is not applicable in SNPNs, while other companies think that it is needed in the following scenario: - The UE is registered in SNPN#1; and - The UE is also registered in PLMN#1 and accessing the services of SNPN#1 via PLMN#1. CT WG1 would like to ask SA WG2 the following question: Question 1: Is the scenario described above supported in Rel-16? Question 2: If the answer to Question 1 is Yes, when would the notification procedure be used in the scenario described above? Additionally, CT WG1 noted that TS 23.501 only contains requirements about access to SNPN via NG-RAN, but there is no text in TS 23.501 explicitly precluding the use of non-3GPP access to access an SNPN. Therefore, CT WG1 would also like to ask SA WG2 the following question: Question 3: Is non-3GPP access to an SNPN supported in Rel-16?. Action: CT WG1 asks SA WG2 to answer Question 1, Question 2 and Question 3 above.","secretary_remarks":"Postponed S2-1908662 from S2#135. Responses drafted in S2-1911094, S2-1911528 and S2-1911848. Final response in S2-1912601","agenda_item_sort_order":34,"ainumber":"7.7.3","ainame":"5GS Enhanced support of Vertical and LAN Services - Type a\/b aspects","tdoc_agenda_sort_order":19210,"status":"replied to","reservation_date":"2019-10-30 08:52:10","uploaded":"2019-11-04 09:40:46","revisionof":"S2-1908662","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"","lsoriginalls":"C1-195159","lsreply":"S2-1912601","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1910853.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1910859","title":"LS from RAN WG2: Reply LS on RAN sharing and Emergency services with NPN","source":"RAN WG2","contact":"Li Chai","contact-id":40955,"tdoctype":"LS in","for":"Action","abstract":"RAN WG2 thank SA WG2 for LS RAN sharing and Emergency services with NPN (S2-1906814). Accordingly, RAN WG2 had discussed the relevant issues and would like to provide the following feedback to the actions. ACTION 1: SA WG2 respectfully seeks feedback from RAN WG2 whether they see any issue to support scenarios E1 and RS1 for Rel-16 UEs. Regarding Action: 1: RAN WG2 concluded in the agreements below. Agreements: 1. There is no issue identified to support E1 for Rel-16 UEs. 2. There is no issue identified to support RS1 for Rel-16 UEs ACTION 2: SA WG2 respectfully asks RAN WG2 whether they have any preference with respect to supporting scenarios E2, RS2 and RS3 from the point of view of any additional protocol functionality in the access stratum to support these scenarios. Regarding Action: 2: RAN WG2 concluded in the agreements below. Agreements: 3. (Regarding question E2) Rel-16 UEs not supporting the CAG feature can camp on a CAG cell as an acceptable cell to obtain limited service 4. RS2 and RS3 can be supported from RAN WG2 point of view. Action: RAN WG2 respectfully asks SA WG2 to take above feedback into consideration.","secretary_remarks":"Postponed S2-1908685 from S2#135. This LS was postponed.","agenda_item_sort_order":34,"ainumber":"7.7.3","ainame":"5GS Enhanced support of Vertical and LAN Services - Type a\/b aspects","tdoc_agenda_sort_order":19430,"status":"postponed","reservation_date":"2019-10-30 08:52:11","uploaded":"2019-11-04 09:40:46","revisionof":"S2-1908685","revisedto":"S2-2000004","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"RAN WG3, CT WG1","lsoriginalls":"R2-1911827","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1910859.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1910860","title":"LS from RAN WG3: Reply LS on RAN sharing and Emergency services with Non-Public Networks","source":"RAN WG3","contact":"Luis Lopes","contact-id":47178,"tdoctype":"LS in","for":"Action","abstract":"RAN WG3 would like to thank SA WG2 for the LS on RAN sharing and Emergency services with Non-Public Networks. RAN WG3 would like to note that the feedback provided in this reply is preliminary and may require further validation. Regarding the emergency scenarios: UE's camping behaviour is in RAN WG2's scope. RAN WG3 does not foresee any impacts from scenarios E1 and E2 in e.g. mobility or network access control. Regarding the RAN sharing scenarios: RAN WG3 has started discussions on RAN sharing and expects that it should be possible to support all cases, but details need further work. During the discussion on network sharing, it was noted that this is closely connected to the SIB structure in RAN WG2. One possible approach is that a logical cell (i.e. defined by a cell identity) would be associated with a single access mode (i.e. a logical cell would either be part of a public or a private network, and in the latter case, support PNI-NPN, or SNPN). In this case, a physical cell may host several logical cells, and therefore may support different network types (and therefore sharing of the physical resource). This approach could facilitate scenarios RS1-3, and therefore RAN WG3 thinks that it should not be precluded but has not reached consensus on whether it is essential to fulfil all the sharing scenarios. In summary, for the actions requested: Action: SA WG2 respectfully seeks feedback from RAN WG2 and RAN WG3 whether they see any issue to support scenarios E1 and RS1 for Rel-16 UEs. Response: RAN WG3 has not found any specific issue for either of these scenarios. Action: SA WG2 respectfully seeks feedback from RAN WG2 and RAN WG3 whether they have any preference with respect to supporting scenarios E2, RS2 and RS3 from the point of view of any additional protocol functionality in the access stratum to support these scenarios. Response: As noted above, the question on emergency scenarios may be considered outside RAN WG3 scope. Regarding RAN sharing, RAN WG3's view is that they should all be feasible from RAN WG3 point of view. RAN WG3 will continue to work on the architecture and impacts of RAN sharing in NPN. Action: RAN WG3 kindly requests SA WG2 and RAN WG2 to take the above information into account, and to provide updates as needed.","secretary_remarks":"Postponed S2-1908695 from S2#135. This LS was postponed.","agenda_item_sort_order":34,"ainumber":"7.7.3","ainame":"5GS Enhanced support of Vertical and LAN Services - Type a\/b aspects","tdoc_agenda_sort_order":19420,"status":"postponed","reservation_date":"2019-10-30 08:52:11","uploaded":"2019-11-04 09:40:46","revisionof":"S2-1908695","revisedto":"S2-2000005","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, RAN WG2","Cc":"SA WG1","lsoriginalls":"R3-194785","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1910860.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1910866","title":"LS from SA WG3: LS on Sending CAG ID in NAS layer","source":"SA WG3","contact":"Adrian Escott","contact-id":24089,"tdoctype":"LS in","for":"Action","abstract":"SA WG3 are discussing CAG ID privacy and as part of that discussion are looking at ways of protecting the transfer of CAG ID between the UE and network. One proposal under discussion in SA WG3 is to not have the CAG ID sent in AS signalling but include it in NAS signalling instead. This means that the CAG ID can be protected by existing NAS signalling security mechanisms for example. SA WG3 realise that this requires a change to the current stage 2 flows and request feedback from SA WG2, RAN WG2 and RAN WG3 on this proposed change. Such feedback will help SA WG3 to progress its work on CAG ID privacy. SA WG3 would like to make it clear that no solution for CAG ID privacy has been agreed by SA WG3. Action: SA WG3 asks SA WG2, RAN WG2 and RAN WG3 groups to provide feedback on sending CAG ID in the NAS layer rather than the AS layer","secretary_remarks":"Postponed S2-1908715 from S2#135. Responses drafted in S2-1911004 and S2-1911893 (withdrawn). This LS was postponed.","agenda_item_sort_order":34,"ainumber":"7.7.3","ainame":"5GS Enhanced support of Vertical and LAN Services - Type a\/b aspects","tdoc_agenda_sort_order":19210,"status":"postponed","reservation_date":"2019-10-30 08:52:11","uploaded":"2019-11-04 09:40:45","revisionof":"S2-1908715","revisedto":"S2-2000008","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, RAN WG2, RAN WG3","Cc":"CT WG1","lsoriginalls":"S3-193142","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1910866.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1910869","title":"LS from TSG CT: LS on SUCI computation from an NSI","source":"TSG CT","contact":"Lena Chaponniere","contact-id":38080,"tdoctype":"LS in","for":"Action","abstract":"TSG CT has discussed the computation of a SUCI from a SUPI consisting of an NSI (Network Specific Identifier) by the USIM, triggered by a CT WG6 CR in C6-190279 submitted to TSG CT#85, and no consensus could be reached on whether: 1) There is any need for both an IMSI (in EFIMSI) and an NSI (in EFNSI) provisioned on the same USIM application; or 2) Maintaining the long held paradigm in 3GPP to have only one subscription identifier (either IMSI, or NSI) associated with a USIM application, to use separate USIM applications when both IMSI and NSI are needed. TSG CT determined that guidance from stage 1 and stage 2 groups was needed to make progress, and would therefore like to ask the following questions: Question 1 (to SA WG2): Are there use cases in which there needs to be both an IMSI and an NSI provisioned on the same USIM application, and if so in which release? Question 2 (to SA WG1): Is there any stage 1 requirement to support having 2 subscriber identities (IMSI and NSI) on the same USIM application, and if so in which release? Question 3 (to SA WG3): Are there any security concerns with having 2 subscriber identities (IMSI and NSI) on the same USIM application?. Action: CT asks SA WG2 to answer Question 1 above.","secretary_remarks":"Postponed S2-1908757 from S2#135. Response drafted in S2-1911006. Final response in S2-1912417","agenda_item_sort_order":34,"ainumber":"7.7.3","ainame":"5GS Enhanced support of Vertical and LAN Services - Type a\/b aspects","tdoc_agenda_sort_order":19510,"status":"replied to","reservation_date":"2019-10-30 08:52:12","uploaded":"2019-11-04 09:40:45","revisionof":"S2-1908757","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, SA WG1, SA WG3, CT WG1, CT WG6","Cc":"CT WG4, TSG SA","lsoriginalls":"CP-192262","lsreply":"S2-1912417","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1910869.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1910951","title":"[DRAFT] Reply LS on applicability of the notification procedure in SNPNs","source":"Nokia, Nokia Shanghai Bell","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"LS out","for":"Approval","abstract":"Reply LS on applicability of the notification procedure in SNPNs","secretary_remarks":"Revision of S2-1910618 from S2#135. Response to S2-1910853. Revised in parallel session, merging S2-1911094 and S2-1911848, to S2-1912381.","agenda_item_sort_order":34,"ainumber":"7.7.3","ainame":"5GS Enhanced support of Vertical and LAN Services - Type a\/b aspects","tdoc_agenda_sort_order":19110,"status":"revised","reservation_date":"2019-11-04 02:53:01","uploaded":"2019-11-08 20:14:35","revisionof":"S2-1910618","revisedto":"S2-1912381","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"Vertical_LAN"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1910951.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1910953","title":"UDM - AUSF Discovery & Selection in an SNPN","source":"Nokia, Nokia Shanghai Bell","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add that NID is needed along with PLMN ID for UDM, AUSF discovery & selection. Also clarify realm part of the NAI within the SUPI identifies the Home network.","secretary_remarks":"Revision of S2-1909721 from S2#135","agenda_item_sort_order":34,"ainumber":"7.7.3","ainame":"5GS Enhanced support of Vertical and LAN Services - Type a\/b aspects","tdoc_agenda_sort_order":19680,"status":"available","reservation_date":"2019-11-04 02:53:03","uploaded":"2019-11-08 20:14:35","revisionof":"S2-1909721","revisedto":"S2-2000663","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"Vertical_LAN"}],"crnumber":1882.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1910953.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1910954","title":"Handover between SNPNs","source":"Nokia, Nokia Shanghai Bell","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: It is proposed to clarify Service continuity reusing the same principles as for access to SNPN services via PLMN or access to PLMN services via SNPN. Also, clarify there is no Xn nor NG Handover between SNPNs via RAN nodes","secretary_remarks":"Revision of S2-1909722 from S2#135","agenda_item_sort_order":34,"ainumber":"7.7.3","ainame":"5GS Enhanced support of Vertical and LAN Services - Type a\/b aspects","tdoc_agenda_sort_order":19730,"status":"available","reservation_date":"2019-11-04 02:53:04","uploaded":"2019-11-08 20:14:35","revisionof":"S2-1909722","revisedto":"","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"Vertical_LAN"}],"crnumber":1883.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1910954.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1910966","title":"UE identifier for SNPN","source":"Nokia, Nokia Shanghai Bell, Deutsche Telekom, Charter, Orange, Vodafone, NTT DOCOMO,China Mobile","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add support for IMSI as SUPI also for UE(s) camping in SNPN, correct wrong reference (28.2.2 does not exist). Considerations: Why is NID needed along with IMSI in the SUPI? If the SNPN uses PLMN ID (MCC 999, MNC ???), then the IMSI with just the PLMN ID will not be unique. Thus the SUPI should also include NID to ensure that the IMSI is unique. In a non-roaming scenario, selected NID could be determined by AMF from NGAP initial UE message however this wouldn't work for SNPN-SNPN roaming scenario and\/or neutral host scenario (if it were to be supported in the future). In case of roaming or neutral host network scenario, home network NID is needed in order to locate the UDM\/UDR\/AUSF. Thus to be forward compatible, also Rel-16 UE(s) should provide the NID along with IMSI in the SUPI. Format in which the IMSI and NID should be encoded? NAI or not? If it is present in NAI, should IMSI be present as part of User name and PLMN ID + NID be present as part of realm? Option 1: UE\/USIM provides the IMSI, ME constructs the NAI using IMSI + NID. Option 2: In the first step, agree that IMSI is a valid identifier for accessing SNPN, also agree that the UE provides NID along with IMSI, simply refer to TS 23.003 for encoding. Way forward proposed: First agree that IMSI is a valid identifier of SUPI for accessing SNPN. Also agree that the UE should provide NID in order to uniquely identify the SNPN. This can be sent along with SUPI by the UE. Storage in USIM or not is not in scope of SA WG2, leave that to CT WG1, CT WG6 (SA WG3) discussion. Also, refer to TS 23.003 for encoding.","secretary_remarks":"Revision of S2-1909720 from S2#135. Revised in parallel session to S2-1912418.","agenda_item_sort_order":34,"ainumber":"7.7.3","ainame":"5GS Enhanced support of Vertical and LAN Services - Type a\/b aspects","tdoc_agenda_sort_order":19510,"status":"revised","reservation_date":"2019-11-04 04:46:16","uploaded":"2019-11-08 20:14:35","revisionof":"S2-1909720","revisedto":"S2-1912418","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"Vertical_LAN"}],"crnumber":1881.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1910966.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1910998","title":"IMSI-based SUPI for SNPNs","source":"Qualcomm Incorporated, Ericsson","contact":"Sebastian Speicher","contact-id":72922,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify in clause 5.9.2 that network-specific identifiers also apply to SNPNs. Clarify in clause 5.30.2.3: - If the UE uses credentials stored in the USIM to access the SNPN and the UE is not configured with a subscriber identifier in the form of a SUPI containing a network-specific identifier for the SNPN then the UE shall construct a network-specific identifier for the SNPN based on the IMSI and the SNPN identity (see TS 23.122 [17] clause 4.9.3.0). - Correct clause number in the reference to TS 23.003.","secretary_remarks":"Revision of S2-1909578 from S2#135. Revised in parallel session to S2-1912419.","agenda_item_sort_order":34,"ainumber":"7.7.3","ainame":"5GS Enhanced support of Vertical and LAN Services - Type a\/b aspects","tdoc_agenda_sort_order":19540,"status":"revised","reservation_date":"2019-11-05 12:30:06","uploaded":"2019-11-08 17:46:40","revisionof":"S2-1909578","revisedto":"S2-1912419","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"Vertical_LAN"}],"crnumber":1850.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1910998.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1910999","title":"Clarifying CAG handling during RRC resume procedure","source":"Qualcomm Incorporated, Ericsson","contact":"Sebastian Speicher","contact-id":72922,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify that - when the UE initiates RRC resume procedure for RRC Inactive to RRC Connected state transition in a CAG cell, NG-RAN shall reject the UE's request if none of the CAG Identifiers supported by the CAG cell are part of the UE's Allowed CAG list according to the Mobility Restrictions received from the AMF. - When the UE initiates RRC resume procedure for RRC Inactive to RRC Connected state transition in a non-CAG cell, NG-RAN shall reject the UE's resume request if the UE is only allowed to access CAG cells according to the Mobility Restrictions received from the AMF.","secretary_remarks":"Revision of S2-1910446 from S2#135. Revised in parallel session to S2-1912386.","agenda_item_sort_order":34,"ainumber":"7.7.3","ainame":"5GS Enhanced support of Vertical and LAN Services - Type a\/b aspects","tdoc_agenda_sort_order":19330,"status":"revised","reservation_date":"2019-11-05 12:37:42","uploaded":"2019-11-08 17:46:40","revisionof":"S2-1910446","revisedto":"S2-1912386","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"Vertical_LAN"}],"crnumber":1752.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1910999.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911000","title":"Handling of Allowed CAG list during registration","source":"Qualcomm Incorporated, Ericsson","contact":"Sebastian Speicher","contact-id":72922,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify that ' Mobility Restrictions signaled to the UE may include Service Area Restrictions and CAG information (as defined in TS 23.501 [2] clause 5.3.4.1.1)'","secretary_remarks":"Revision of S2-1909083 from S2#135","agenda_item_sort_order":34,"ainumber":"7.7.3","ainame":"5GS Enhanced support of Vertical and LAN Services - Type a\/b aspects","tdoc_agenda_sort_order":19840,"status":"available","reservation_date":"2019-11-05 12:39:57","uploaded":"2019-11-08 17:46:40","revisionof":"S2-1909083","revisedto":"S2-2000085","release":"Rel-16","crspec":"23.502","crspecversion":"16.2.0","workitem":[{"winame":"Vertical_LAN"}],"crnumber":1491.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911000.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911001","title":"Support of PLMN managed NIDs","source":"Qualcomm Incorporated, Ericsson, Nokia, Nokia Shanghai Bell, Samsung","contact":"Sebastian Speicher","contact-id":72922,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify that SNPN identity of PLMN ID and NID can be unique by assigning NIDs in relation to a PLMN ID as a new assignment mode. Introduce term 'coordinated assignment', rename locally managed to self-assignment to harmonize terminology.","secretary_remarks":"Revision of S2-1910783 from S2#135. Agreed in parallel session. Block approved","agenda_item_sort_order":34,"ainumber":"7.7.3","ainame":"5GS Enhanced support of Vertical and LAN Services - Type a\/b aspects","tdoc_agenda_sort_order":19620,"status":"agreed","reservation_date":"2019-11-05 12:46:00","uploaded":"2019-11-08 17:46:40","revisionof":"S2-1910783","revisedto":"","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"Vertical_LAN"}],"crnumber":1797.0,"crrevision":3.0,"crcategory":"F","tsg_crp":"SP-191092","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911001.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911002","title":"[DRAFT] Reply LS on sending CAG ID during resume procedure","source":"Qualcomm","contact":"Sebastian Speicher","contact-id":72922,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG1. CC: RAN WG2. Attachments: TS 23.501 CR#1752","secretary_remarks":"Revision of S2-1910447 from S2#135. Response to S2-1910852. Revised in parallel session to S2-1912387.","agenda_item_sort_order":34,"ainumber":"7.7.3","ainame":"5GS Enhanced support of Vertical and LAN Services - Type a\/b aspects","tdoc_agenda_sort_order":19350,"status":"revised","reservation_date":"2019-11-05 12:49:55","uploaded":"2019-11-08 17:46:40","revisionof":"S2-1910447","revisedto":"S2-1912387","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"Vertical_LAN"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"RAN WG2","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911002.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911003","title":"Adding Information about serving network to Nsmf_PDUSession service","source":"Nokia, Nokia Shanghai-Bell","contact":"Thomas Belling","contact-id":68266,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: To align with stage 3, the serving network (PLMN ID and when available NID) is added as mandatory input parameter to the Nsmf_PDUSession_CreateSMContext and Nsmf_PDUSession_Create service operations.","secretary_remarks":"Revision of S2-1909141 from S2#135","agenda_item_sort_order":34,"ainumber":"7.7.3","ainame":"5GS Enhanced support of Vertical and LAN Services - Type a\/b aspects","tdoc_agenda_sort_order":19690,"status":"available","reservation_date":"2019-11-05 13:00:02","uploaded":"2019-11-08 16:14:36","revisionof":"S2-1909141","revisedto":"S2-2000227","release":"Rel-16","crspec":"23.502","crspecversion":"16.2.0","workitem":[{"winame":"5GS_Ph1"},{"winame":"Vertical_LAN"}],"crnumber":1763.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911003.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911004","title":"[DRAFT] Reply LS on Sending CAG ID in NAS layer","source":"Qualcomm","contact":"Sebastian Speicher","contact-id":72922,"tdoctype":"LS out","for":"Approval","abstract":"To: SA WG3, RAN WG2, RAN WG3, CT WG1","secretary_remarks":"Revision of S2-1910445 from S2#135. Response to S2-1910866. Revised in parallel session, merging S2-1911893, to S2-1912384.","agenda_item_sort_order":34,"ainumber":"7.7.3","ainame":"5GS Enhanced support of Vertical and LAN Services - Type a\/b aspects","tdoc_agenda_sort_order":19220,"status":"revised","reservation_date":"2019-11-05 13:02:31","uploaded":"2019-11-08 17:46:40","revisionof":"S2-1910445","revisedto":"S2-1912384","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"Vertical_LAN"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG3, RAN WG2, RAN WG3, CT WG1","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911004.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911005","title":"Adding Information about serving network to Nudm and Nudr services","source":"Nokia, Nokia Shanghai-Bell","contact":"Thomas Belling","contact-id":68266,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: To align with stage 3, the serving network (PLMN ID) is added as data sub key for various subscription data in UDM and UDR, and the serving network is added as input parameter to the Nudm_UECM_Registration service operation. The NID as also added in all those places as optional additional parameter.","secretary_remarks":"Revision of S2-1909348 from S2#135. Confirm Spec version!","agenda_item_sort_order":34,"ainumber":"7.7.3","ainame":"5GS Enhanced support of Vertical and LAN Services - Type a\/b aspects","tdoc_agenda_sort_order":19700,"status":"available","reservation_date":"2019-11-05 13:03:52","uploaded":"2019-11-08 16:14:36","revisionof":"S2-1909348","revisedto":"S2-2000228","release":"Rel-16","crspec":"23.502","crspecversion":"16.2.0","workitem":[{"winame":"5GS_Ph1"},{"winame":"Vertical_LAN"}],"crnumber":1792.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911005.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911006","title":"[DRAFT] Reply LS on SUCI computation from an NSI","source":"Qualcomm","contact":"Sebastian Speicher","contact-id":72922,"tdoctype":"LS out","for":"Approval","abstract":"To: TSG CT, SA WG1, SA WG3, CT WG1, CT WG6. CC: CT WG4, TSG SA.","secretary_remarks":"Revision of S2-1910448 from S2#135. Response to S2-1910869. Revised in parallel session to S2-1912417.","agenda_item_sort_order":34,"ainumber":"7.7.3","ainame":"5GS Enhanced support of Vertical and LAN Services - Type a\/b aspects","tdoc_agenda_sort_order":19400,"status":"revised","reservation_date":"2019-11-05 13:18:16","uploaded":"2019-11-08 17:46:40","revisionof":"S2-1910448","revisedto":"S2-1912417","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"Vertical_LAN"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG CT, SA WG1, SA WG3, CT WG1, CT WG6","Cc":"CT WG4, TSG SA","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911006.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911027","title":"Alignments and corrections to Non-Public Network functionality","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Added abbreviation for Public network integrated NPN. Avoided 'will be specified' statements. Clarified that UAC information provided to the UE as described in 24.501. Clarified that the UE is required to have subscription for PLMN when accessing Public network integrated NPN. Clarified that an SNPN does not support multiple PLMN ID and NIDs. Rev 2: Clarified '(or combinations of PLMN ID and NID' to be AMF supporting multiple NIDs but used for different UEs i.e. not for equivalent SNPNs, e.g. to support different OT domain zones. Clarified SNPN Clarified NPN isolation in Annex D","secretary_remarks":"Revision of S2-1909369 from S2#135","agenda_item_sort_order":34,"ainumber":"7.7.3","ainame":"5GS Enhanced support of Vertical and LAN Services - Type a\/b aspects","tdoc_agenda_sort_order":19810,"status":"available","reservation_date":"2019-11-06 00:06:08","uploaded":"2019-11-08 21:51:28","revisionof":"S2-1909369","revisedto":"S2-2000180","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"Vertical_LAN"}],"crnumber":1482.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911027.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911028","title":"Support of NG-RAN sharing options for NPN","source":"Ericsson, Qualcomm Incorporated, NICT","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Support for following NG-RAN sharing options are added - RAN sharing between a PNI-NPN (with CAG) and an SNPN - RAN sharing between a PLMN and a PNI-NPN with CAG And existing NG-RAN sharing option for sharing between a PLMN and an SNPN is clarified. - Clarify that CAG Identifiers may be in Broadcast system information","secretary_remarks":"Revision of S2-1909370 from S2#135. Revised in parallel session to S2-1912379.","agenda_item_sort_order":34,"ainumber":"7.7.3","ainame":"5GS Enhanced support of Vertical and LAN Services - Type a\/b aspects","tdoc_agenda_sort_order":19470,"status":"revised","reservation_date":"2019-11-06 00:06:09","uploaded":"2019-11-08 21:51:28","revisionof":"S2-1909370","revisedto":"S2-1912379","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"Vertical_LAN"}],"crnumber":1798.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911028.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911029","title":"Support of CAG ID privacy","source":"Ericsson, Qualcomm Incorporated","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Removing the requirement for the UE to send the CAG ID in AS\/RRC, and instead the NG-RAN provides the list of CAG IDs of the CAG cell associated to the selected PLMN to the AMF to enable AMF authorization of the UE.","secretary_remarks":"Revision of S2-1910443 from S2#135. Noted in parallel session","agenda_item_sort_order":34,"ainumber":"7.7.3","ainame":"5GS Enhanced support of Vertical and LAN Services - Type a\/b aspects","tdoc_agenda_sort_order":19260,"status":"noted","reservation_date":"2019-11-06 00:06:11","uploaded":"2019-11-08 21:51:28","revisionof":"S2-1910443","revisedto":"S2-2000182","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"Vertical_LAN"}],"crnumber":1799.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911029.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911030","title":"Support of CAG ID privacy","source":"Ericsson, Qualcomm Incorporated","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Removing the requirement for the UE to send the CAG ID in AS\/RRC, and instead the NG-RAN provides the list of CAG IDs of the CAG cell associated to the selected PLMN to the AMF to enable AMF authorization of the UE.","secretary_remarks":"Revision of S2-1910444 from S2#135. Noted in parallel session","agenda_item_sort_order":34,"ainumber":"7.7.3","ainame":"5GS Enhanced support of Vertical and LAN Services - Type a\/b aspects","tdoc_agenda_sort_order":19270,"status":"noted","reservation_date":"2019-11-06 00:06:13","uploaded":"2019-11-08 21:51:28","revisionof":"S2-1910444","revisedto":"S2-2000183","release":"Rel-16","crspec":"23.502","crspecversion":"16.2.0","workitem":[{"winame":"Vertical_LAN"}],"crnumber":1796.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911030.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911031","title":"NID parameter for SNPN N3IWF deployments","source":"Ericsson, Qualcomm Incorporated","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Adding NID as parameter in registration and service request via untrusted N3GPP.","secretary_remarks":"Revision of S2-1909376 from S2#135","agenda_item_sort_order":34,"ainumber":"7.7.3","ainame":"5GS Enhanced support of Vertical and LAN Services - Type a\/b aspects","tdoc_agenda_sort_order":19740,"status":"available","reservation_date":"2019-11-06 00:06:15","uploaded":"2019-11-08 21:51:28","revisionof":"S2-1909376","revisedto":"S2-2000186","release":"Rel-16","crspec":"23.502","crspecversion":"16.2.0","workitem":[{"winame":"Vertical_LAN"}],"crnumber":1797.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911031.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911032","title":"Procedures for handover between SNPN and PLMN","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Informative procedures in a new annex is proposed. The procedures are already supported using the existing procedures in 23.502 but there is a benefit on showing more explicitly how these mobility procedures can be used for the applicable mobility scenarios.","secretary_remarks":"Revision of S2-1909377 from S2#135","agenda_item_sort_order":34,"ainumber":"7.7.3","ainame":"5GS Enhanced support of Vertical and LAN Services - Type a\/b aspects","tdoc_agenda_sort_order":19720,"status":"available","reservation_date":"2019-11-06 00:06:16","uploaded":"2019-11-08 21:51:28","revisionof":"S2-1909377","revisedto":"S2-2000185","release":"Rel-16","crspec":"23.502","crspecversion":"16.2.0","workitem":[{"winame":"Vertical_LAN"}],"crnumber":1798.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911032.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911076","title":"Missing description of using SNPN allocated 5G-GUTI","source":"OPPO","contact":"Yang Xu","contact-id":74478,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: If UE successfully registered to the SNPN and acquired a 5G-GUTI, the UE shall use this GUTI only when registering in this SNPN.","secretary_remarks":"","agenda_item_sort_order":34,"ainumber":"7.7.3","ainame":"5GS Enhanced support of Vertical and LAN Services - Type a\/b aspects","tdoc_agenda_sort_order":19790,"status":"available","reservation_date":"2019-11-06 10:20:57","uploaded":"2019-11-08 10:44:36","revisionof":"","revisedto":"","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"Vertical_LAN"}],"crnumber":1927.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911076.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911085","title":"PLMN+CAG information - minimum, maximum storage and survival of power cycle","source":"OPPO, MediaTek Inc.","contact":"ChenHo CHIN","contact-id":80545,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: the combinations of PLMN + CAG information is to be kept even at power off. A NOTE is added to mention the minimum and\/or maximum number of such PLMN + CAG combinations are left to Stage 3.","secretary_remarks":"Revision of S2-1909215 from S2#135","agenda_item_sort_order":34,"ainumber":"7.7.3","ainame":"5GS Enhanced support of Vertical and LAN Services - Type a\/b aspects","tdoc_agenda_sort_order":19850,"status":"available","reservation_date":"2019-11-06 13:42:25","uploaded":"2019-11-08 11:04:46","revisionof":"S2-1909215","revisedto":"","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"Vertical_LAN"}],"crnumber":1520.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911085.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911094","title":"[DRAFT] Reply LS on the applicability of the notification procedure in SNPNs","source":"Qualcomm Incorporated","contact":"Sebastian Speicher","contact-id":72922,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG1.","secretary_remarks":"Revision of S2-1909080 from S2#135. Response to S2-1910853. Merged into S2-1912381","agenda_item_sort_order":34,"ainumber":"7.7.3","ainame":"5GS Enhanced support of Vertical and LAN Services - Type a\/b aspects","tdoc_agenda_sort_order":19140,"status":"merged","reservation_date":"2019-11-06 15:11:17","uploaded":"2019-11-08 17:46:40","revisionof":"S2-1909080","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"Vertical_LAN"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911094.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911131","title":"Protocol stack and other correction for accessing to PLMN services via non-public networks and vice versa","source":"Vivo","contact":"xiaowan ke","contact-id":74585,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: - Fix the typo. - A DNN for accessing to the PLMN (SNPN) is configured to the UE. - The UE can also request QoS for the signaling IPsec SA with the 5QI used for signaling. - Modify CP and UP protocol stacks for N3IWF to be applicable for both N3GPP and accessing to PLMN services via NPN and vice versa.","secretary_remarks":"Revision of S2-1909088 from S2#135","agenda_item_sort_order":34,"ainumber":"7.7.3","ainame":"5GS Enhanced support of Vertical and LAN Services - Type a\/b aspects","tdoc_agenda_sort_order":19760,"status":"available","reservation_date":"2019-11-07 03:33:45","uploaded":"2019-11-08 18:55:10","revisionof":"S2-1909088","revisedto":"","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"Vertical_LAN"}],"crnumber":1293.0,"crrevision":3.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911131.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911152","title":"Support of emergency services for Rel-16 UE not supporting CAG in CAG cells","source":"China Telecom","contact":"Song Zhao","contact-id":71667,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add the support of emergency services for Rel-16 UE not supporting CAG in CAG cells.","secretary_remarks":"Revision of S2-1909646 from S2#135","agenda_item_sort_order":34,"ainumber":"7.7.3","ainame":"5GS Enhanced support of Vertical and LAN Services - Type a\/b aspects","tdoc_agenda_sort_order":19940,"status":"available","reservation_date":"2019-11-07 08:20:37","uploaded":"2019-11-08 12:40:27","revisionof":"S2-1909646","revisedto":"","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"Vertical_LAN"}],"crnumber":1831.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911152.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911251","title":"Correction of N3IWF selection for accessing an SNPN via a PLMN","source":"Motorola Mobility, Lenovo","contact":"Apostolis Salkintzis","contact-id":22112,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: A new clause is added that specifies how the UE selects an N3IWF when the UE wants to access an SNPN via a PLMN, by considering also the regulatory requirements of the country wherein the UE is located.","secretary_remarks":"","agenda_item_sort_order":34,"ainumber":"7.7.3","ainame":"5GS Enhanced support of Vertical and LAN Services - Type a\/b aspects","tdoc_agenda_sort_order":19780,"status":"available","reservation_date":"2019-11-07 15:35:27","uploaded":"2019-11-08 18:14:19","revisionof":"","revisedto":"S2-2000425","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"5GS_Ph1"},{"winame":"Vertical_LAN"}],"crnumber":1938.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911251.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911339","title":"Clarification for QoS between SNPN and PLMN","source":"Huawei, Hisilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify that existing 'usage report procedure' and 'network request PDU Session Modification Procedure' can be used for network-initiated QoS to meet the requirement of QoS differentiation in SNPN\/PLMN.","secretary_remarks":"Revision of S2-1909469 from S2#135","agenda_item_sort_order":34,"ainumber":"7.7.3","ainame":"5GS Enhanced support of Vertical and LAN Services - Type a\/b aspects","tdoc_agenda_sort_order":19750,"status":"available","reservation_date":"2019-11-07 18:32:47","uploaded":"2019-11-08 19:58:08","revisionof":"S2-1909469","revisedto":"S2-2000429","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"Vertical_LAN"}],"crnumber":1826.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911339.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911363","title":"[DRAFT] LS on RAN sharing for NPNs","source":"Qualcomm Incorporated","contact":"Sebastian Speicher","contact-id":72922,"tdoctype":"LS out","for":"Approval","abstract":"To: RAN WG2, RAN WG3. Attachments: TS 23.501 CR#1798.","secretary_remarks":"Revision of S2-1909294 from S2#135. Revised in parallel session to S2-1912380.","agenda_item_sort_order":34,"ainumber":"7.7.3","ainame":"5GS Enhanced support of Vertical and LAN Services - Type a\/b aspects","tdoc_agenda_sort_order":19440,"status":"revised","reservation_date":"2019-11-07 22:55:01","uploaded":"2019-11-08 17:46:40","revisionof":"S2-1909294","revisedto":"S2-1912380","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"Vertical_LAN"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2, RAN WG3","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911363.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911448","title":"CR on camping a CAG cell in limited service state","source":"Tencent","contact":"Yixue Lei","contact-id":78221,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Correct the statement that UE is allowed to camp on an acceptable CAG cell regardless whether it supports CAG or not.","secretary_remarks":"Revision of S2-1909662 from S2#135","agenda_item_sort_order":34,"ainumber":"7.7.3","ainame":"5GS Enhanced support of Vertical and LAN Services - Type a\/b aspects","tdoc_agenda_sort_order":19950,"status":"available","reservation_date":"2019-11-08 05:44:51","uploaded":"2019-11-08 11:59:05","revisionof":"S2-1909662","revisedto":"S2-2000612","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"Vertical_LAN"}],"crnumber":1867.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911448.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911501","title":"Definition of non-public network","source":"Samsung","contact":"Youngkyo Baek","contact-id":46395,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 1) SNPN is defined as NPN exclusively managed from a PLMN. 2) PNI NPN is defined a subset of a PLMN in order not to mix up with SNPN's definition.","secretary_remarks":"","agenda_item_sort_order":34,"ainumber":"7.7.3","ainame":"5GS Enhanced support of Vertical and LAN Services - Type a\/b aspects","tdoc_agenda_sort_order":19800,"status":"available","reservation_date":"2019-11-08 08:40:19","uploaded":"2019-11-08 08:49:42","revisionof":"","revisedto":"","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"Vertical_LAN"}],"crnumber":1960.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911501.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911527","title":"Discussion on CT WG1 LS in C1-195159 - Applicability of the notification procedure in SNPNs .","source":"MediaTek Inc.","contact":"Guillaume Sebire","contact-id":45073,"tdoctype":"discussion","for":"Decision","abstract":"This contribution is an update of a previous presentation in S2-1909706 [1].","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":34,"ainumber":"7.7.3","ainame":"5GS Enhanced support of Vertical and LAN Services - Type a\/b aspects","tdoc_agenda_sort_order":19100,"status":"noted","reservation_date":"2019-11-08 09:16:10","uploaded":"2019-11-08 11:48:46","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911527.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911555","title":"Clarification on rejecting UE registration","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: there is no valid SNPN subscription for the UE, then the AMF shall reject the UE registration in the SNPN","secretary_remarks":"Revision of S2-1908859 from S2#135","agenda_item_sort_order":34,"ainumber":"7.7.3","ainame":"5GS Enhanced support of Vertical and LAN Services - Type a\/b aspects","tdoc_agenda_sort_order":19860,"status":"available","reservation_date":"2019-11-08 09:16:59","uploaded":"2019-11-08 16:32:10","revisionof":"S2-1908859","revisedto":"","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"Vertical_LAN"}],"crnumber":1709.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911555.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911577","title":"Annex D Clarification","source":"Samsung","contact":"Sang-Jun Moon","contact-id":30993,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: N6 between DN and N3IWF is deleted, and Nwu is corrected into NWu.","secretary_remarks":"","agenda_item_sort_order":34,"ainumber":"7.7.3","ainame":"5GS Enhanced support of Vertical and LAN Services - Type a\/b aspects","tdoc_agenda_sort_order":19770,"status":"available","reservation_date":"2019-11-08 10:10:12","uploaded":"2019-11-08 12:49:06","revisionof":"","revisedto":"S2-2000811","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"Vertical_LAN"}],"crnumber":1964.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911577.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911581","title":"Clarification of handover procedure between PLMN and SNPN","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarification of service continuity between PLMN and SNPN is added.","secretary_remarks":"","agenda_item_sort_order":34,"ainumber":"7.7.3","ainame":"5GS Enhanced support of Vertical and LAN Services - Type a\/b aspects","tdoc_agenda_sort_order":19710,"status":"available","reservation_date":"2019-11-08 10:17:56","uploaded":"2019-11-08 18:47:33","revisionof":"","revisedto":"","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"Vertical_LAN"}],"crnumber":1967.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911581.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911582","title":"Clarification of CAG ID selection during handover procedure","source":"Huawei, HiSilicon, China Mobile","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add clarification that Source NG-RAN and target NG-RAN does not need to select CAG ID to be used in the target NG-RAN node. Source NG-RAN does not need to send the current used CAG ID to the AMF or the target NG-RAN.","secretary_remarks":"","agenda_item_sort_order":34,"ainumber":"7.7.3","ainame":"5GS Enhanced support of Vertical and LAN Services - Type a\/b aspects","tdoc_agenda_sort_order":19870,"status":"available","reservation_date":"2019-11-08 10:17:57","uploaded":"2019-11-08 18:47:33","revisionof":"","revisedto":"","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"Vertical_LAN"}],"crnumber":1968.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911582.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911583","title":"CAG-only indication and empty Allowed CAG list","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 1. Clarify that AMF will not send NAS rejection or configuration update message to sych the configuration in the UE if a CAG-only indication and an empty list is configured in the network. 2. All the service area will be set as Non-Allowed Area for mobility restriction if a CAG-only indication and empty allowed CAG list is configured in the network. AMF will be able to accept the NAS request and update new configuration.","secretary_remarks":"","agenda_item_sort_order":34,"ainumber":"7.7.3","ainame":"5GS Enhanced support of Vertical and LAN Services - Type a\/b aspects","tdoc_agenda_sort_order":19880,"status":"available","reservation_date":"2019-11-08 10:17:58","uploaded":"2019-11-08 18:47:33","revisionof":"","revisedto":"","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"Vertical_LAN"}],"crnumber":1969.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911583.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911584","title":"Clarification of N2 based handover considering CAG IDs supported by the target NG-RAN node","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: During N2 based handover procedure, the target cell needs to determine whether the handover can be performed based on CAG IDs.","secretary_remarks":"","agenda_item_sort_order":34,"ainumber":"7.7.3","ainame":"5GS Enhanced support of Vertical and LAN Services - Type a\/b aspects","tdoc_agenda_sort_order":19890,"status":"available","reservation_date":"2019-11-08 10:18:00","uploaded":"2019-11-08 18:47:33","revisionof":"","revisedto":"","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"Vertical_LAN"}],"crnumber":1970.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911584.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911748","title":"Clarification on paging related to CAG","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: When PNI-NPN needs to page a UE that is only allowed to access 5GS via CAG cells, it should avoid sending the paging messge to the NG-RAN node(s) that do not suport any CAG ID in UE's allowed CAG list. When PNI-NPN needs to page a UE that can access 5GS via non-CAG cells, it should avoid sending Paging messge to the NG-RAN node(s) that do not suport non-CAG cell and any CAG ID in UE's allowed CAG list.","secretary_remarks":"","agenda_item_sort_order":34,"ainumber":"7.7.3","ainame":"5GS Enhanced support of Vertical and LAN Services - Type a\/b aspects","tdoc_agenda_sort_order":19900,"status":"available","reservation_date":"2019-11-08 14:07:47","uploaded":"2019-11-08 16:32:10","revisionof":"","revisedto":"","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"Vertical_LAN"}],"crnumber":1987.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911748.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911749","title":"Clarification on paging related to CAG","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: When PNI-NPN needs to page a UE that is only allowed to access 5GS via CAG cells, it should avoid sending the paging messge to the NG-RAN node(s) that do not suport any CAG ID in UE's allowed CAG list. When PNI-NPN needs to page a UE that can access 5GS via non-CAG cells, it should avoid sending Paging messge to the NG-RAN node(s) that do not suport non-CAG cell and any CAG ID in UE's allowed CAG list.","secretary_remarks":"","agenda_item_sort_order":34,"ainumber":"7.7.3","ainame":"5GS Enhanced support of Vertical and LAN Services - Type a\/b aspects","tdoc_agenda_sort_order":19910,"status":"available","reservation_date":"2019-11-08 14:07:49","uploaded":"2019-11-08 16:32:10","revisionof":"","revisedto":"","release":"Rel-16","crspec":"23.502","crspecversion":"16.2.0","workitem":[{"winame":"Vertical_LAN"}],"crnumber":1939.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911749.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911754","title":"Discussion on CAG access control.","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"discussion","for":"Endorsement","abstract":"This discussion paper aims at explaining the CAG ID, and its usage, and proposes to keep it as it is.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":34,"ainumber":"7.7.3","ainame":"5GS Enhanced support of Vertical and LAN Services - Type a\/b aspects","tdoc_agenda_sort_order":19710,"status":"noted","reservation_date":"2019-11-08 14:07:58","uploaded":"2019-11-08 16:32:10","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"Vertical_LAN"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911754.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911764","title":"Support for Untrusted Non-3GPP access for SNPN","source":"Intel","contact":"Saso Stojanovski","contact-id":24932,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clause 4.12.1: clarified that the procedures for Untrusted non-3GPP access can also be used by UE that accesses SNPN service via a PLMN. Clause 4.12.2.2: clarified that 'Access Type' is set to 'non-3GPP access'.","secretary_remarks":"Revised in parallel session to S2-1912382.","agenda_item_sort_order":34,"ainumber":"7.7.3","ainame":"5GS Enhanced support of Vertical and LAN Services - Type a\/b aspects","tdoc_agenda_sort_order":19160,"status":"revised","reservation_date":"2019-11-08 14:35:20","uploaded":"2019-11-08 18:09:09","revisionof":"","revisedto":"S2-1912382","release":"Rel-16","crspec":"23.502","crspecversion":"16.2.0","workitem":[{"winame":"Vertical_LAN"}],"crnumber":1940.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911764.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911767","title":"Support for Untrusted Non-3GPP access for SNPN","source":"Intel","contact":"Saso Stojanovski","contact-id":24932,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clause 5.30.2.8: clarified that 'Access Type' is set to 'non-3GPP access'. Clause 5.30.2.8a (new): new clause on access to SNPN services via non-3GPP access.","secretary_remarks":"Revised in parallel session to S2-1912383.","agenda_item_sort_order":34,"ainumber":"7.7.3","ainame":"5GS Enhanced support of Vertical and LAN Services - Type a\/b aspects","tdoc_agenda_sort_order":19190,"status":"revised","reservation_date":"2019-11-08 14:42:49","uploaded":"2019-11-08 18:09:09","revisionof":"","revisedto":"S2-1912383","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"Vertical_LAN"}],"crnumber":1989.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911767.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911781","title":"CAG-only indication and empty Allowed CAG list","source":"InterDigtial, Inc.","contact":"Guanzhou Wang","contact-id":72777,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 1, Clarify that a UE may ignore the CAG-only configuration if the Allowed CAG list is empty; 2, In NAS reject message, the network also provides the latest Allowed CAG list and the UE updates its Allowed CAG list with the received list;","secretary_remarks":"","agenda_item_sort_order":34,"ainumber":"7.7.3","ainame":"5GS Enhanced support of Vertical and LAN Services - Type a\/b aspects","tdoc_agenda_sort_order":19920,"status":"available","reservation_date":"2019-11-08 15:05:12","uploaded":"2019-11-08 21:36:25","revisionof":"","revisedto":"","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"Vertical_LAN"}],"crnumber":1991.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911781.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911787","title":"Emergency calls for UEs not supporting CAG","source":"Qualcomm Incorporated, Ericsson","contact":"Haris Zisimopoulos","contact-id":84603,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarifies that emergency calls in limited service state from CAG can be supported by rel.16 UEs in limited service state not supporting CAG","secretary_remarks":"Revision of S2-1909896 from S2#135. Confirm Specification Number!","agenda_item_sort_order":34,"ainumber":"7.7.3","ainame":"5GS Enhanced support of Vertical and LAN Services - Type a\/b aspects","tdoc_agenda_sort_order":19960,"status":"available","reservation_date":"2019-11-08 15:21:04","uploaded":"2019-11-08 18:40:57","revisionof":"S2-1909896","revisedto":"S2-2000501","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"Vertical_LAN"}],"crnumber":1914.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911787.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911848","title":"[DRAFT] Reply LS on applicability of the notification procedure in SNPNs","source":"Intel","contact":"Saso Stojanovski","contact-id":24932,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG1","secretary_remarks":"Response to S2-1910853. Merged into S2-1912381","agenda_item_sort_order":34,"ainumber":"7.7.3","ainame":"5GS Enhanced support of Vertical and LAN Services - Type a\/b aspects","tdoc_agenda_sort_order":19150,"status":"merged","reservation_date":"2019-11-08 16:41:31","uploaded":"2019-11-08 18:09:09","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911848.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911887","title":"PNI-NPN - Reusing NSSAI for AMF selection when NPN isolation is needed","source":"Nokia, Nokia Shanghai Bell","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: It is proposed to clarify: If NPN isolation is required, it is assumed that the operator configures dedicated NSSAI for the given NPN and also configures the NSSAI Inclusion Mode parameter such that NG-RAN receives NSSAI from the UE and it can use the NSSAI for AMF selection.","secretary_remarks":"Confirm CR Revision!. Revised in parallel session to S2-1912385.","agenda_item_sort_order":34,"ainumber":"7.7.3","ainame":"5GS Enhanced support of Vertical and LAN Services - Type a\/b aspects","tdoc_agenda_sort_order":19280,"status":"revised","reservation_date":"2019-11-08 18:19:09","uploaded":"2019-11-08 20:14:35","revisionof":"","revisedto":"S2-1912385","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"Vertical_LAN"}],"crnumber":1997.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911887.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911893","title":"[DRAFT] Reply LS on sending CAG ID in NAS layer","source":"Samsung","contact":"Lalith Kumar","contact-id":80547,"tdoctype":"LS out","for":"Approval","abstract":"To: SA WG3. CC: RAN WG2, RAN WG3, CT WG1","secretary_remarks":"Response to S2-1910866. Merged into S2-1912384","agenda_item_sort_order":34,"ainumber":"7.7.3","ainame":"5GS Enhanced support of Vertical and LAN Services - Type a\/b aspects","tdoc_agenda_sort_order":19240,"status":"merged","reservation_date":"2019-11-08 18:59:31","uploaded":"2019-11-08 20:02:54","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"Vertical_LAN"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG3","Cc":"RAN WG2, RAN WG3, CT WG1","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911893.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911894","title":"CAG Capability indication","source":"Samsung","contact":"Lalith Kumar","contact-id":80547,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Align with CT WG1 specification to provide CAG supported indication..","secretary_remarks":"","agenda_item_sort_order":34,"ainumber":"7.7.3","ainame":"5GS Enhanced support of Vertical and LAN Services - Type a\/b aspects","tdoc_agenda_sort_order":19930,"status":"available","reservation_date":"2019-11-08 19:05:55","uploaded":"2019-11-08 20:02:54","revisionof":"","revisedto":"","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"Vertical_LAN"}],"crnumber":1999.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911894.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911946","title":"LS from CT WG6: LS on user identity when 5G-AKA or EAP AKA\u2019 is used for SNPN","source":"CT WG6","contact":"Kundan Tiwari","contact-id":66053,"tdoctype":"LS in","for":"Action","abstract":"Overall Description: 1- According to TS 33.501, a SUPI in the form of an NSI can be used as the user identity for 5G-AKA or EAP-AKA' algorithms. 2- Assuming that NSI could be used with 5G-AKA or EAP-AKA' and according to the requirement from SA WG3 in TS 33.501, the UE shall use the credentials (including SUPI) stored in the USIM when 5G-AKA or EAP-AKA' authentication method is chosen by the network (PLMN or SNPN). In this scenario if NSI is stored in the USIM as the SUPI then the UE shall use the NSI stored in this USIM as the user identity. Action: CT WG6 kindly requests CT WG1 and SA WG2 to take the above and the response of SA WG3 into account.","secretary_remarks":"Postponed in parallel session","agenda_item_sort_order":34,"ainumber":"7.7.3","ainame":"5GS Enhanced support of Vertical and LAN Services - Type a\/b aspects","tdoc_agenda_sort_order":19490,"status":"postponed","reservation_date":"2019-11-16 05:26:30","uploaded":"2019-11-16 05:26:53","revisionof":"","revisedto":"S2-2000017","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, CT WG1, SA WG3","Cc":"","lsoriginalls":"C6-190468","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911946.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911955","title":"LS from CT WG1: LS on Manual CAG Selection","source":"CT WG1","contact":"Vishnu Preman","contact-id":67508,"tdoctype":"LS in","for":"Information","abstract":"With respect to the manual CAG selection, the following service requirement question was raised within CT WG1 and SA WG1 is requested to provide feedback on the following: {Questions, assumptions and agreements}","secretary_remarks":"This LS was postponed.","agenda_item_sort_order":34,"ainumber":"7.7.3","ainame":"5GS Enhanced support of Vertical and LAN Services - Type a\/b aspects","tdoc_agenda_sort_order":19700,"status":"postponed","reservation_date":"2019-11-16 06:41:55","uploaded":"2019-11-16 06:42:42","revisionof":"","revisedto":"S2-2000023","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG1, TSG CT","Cc":"SA WG2","lsoriginalls":"C1-199047","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911955.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1912379","title":"Support of NG-RAN sharing options for NPN","source":"Ericsson, Qualcomm Incorporated, NICT, Deutsche Telekom","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Support for following NG-RAN sharing options are added - RAN sharing between a PNI-NPN (with CAG) and an SNPN - RAN sharing between a PLMN and a PNI-NPN with CAG And existing NG-RAN sharing option for sharing between a PLMN and an SNPN is clarified. - Clarify that CAG Identifiers may be in Broadcast system information Rev2: - Aligned Cell ID to Cell Identity","secretary_remarks":"Revision of S2-1911028. Agreed in parallel session. Block approved","agenda_item_sort_order":34,"ainumber":"7.7.3","ainame":"5GS Enhanced support of Vertical and LAN Services - Type a\/b aspects","tdoc_agenda_sort_order":19600,"status":"agreed","reservation_date":"2019-11-19 22:37:09","uploaded":"2019-11-25 16:07:54","revisionof":"S2-1911028","revisedto":"","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"Vertical_LAN"}],"crnumber":1798.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"SP-191092","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1912379.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1912380","title":"[DRAFT] LS on RAN sharing for NPNs","source":"Qualcomm Incorporated","contact":"Sebastian Speicher","contact-id":72922,"tdoctype":"LS out","for":"Approval","abstract":"To: RAN WG2, RAN WG3. Attachments: TS 23.501 CR#1798.","secretary_remarks":"Revision of S2-1911363. Revised in parallel session to S2-1912602.","agenda_item_sort_order":34,"ainumber":"7.7.3","ainame":"5GS Enhanced support of Vertical and LAN Services - Type a\/b aspects","tdoc_agenda_sort_order":19450,"status":"revised","reservation_date":"2019-11-19 22:37:10","uploaded":"2019-11-25 16:07:54","revisionof":"S2-1911363","revisedto":"S2-1912602","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"Vertical_LAN"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2, RAN WG3","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1912380.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1912381","title":"[DRAFT] Reply LS on applicability of the notification procedure in SNPNs","source":"Nokia, Nokia Shanghai Bell","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"LS out","for":"Approval","abstract":"Reply LS on applicability of the notification procedure in SNPNs","secretary_remarks":"Revision of S2-1910951, merging S2-1911094 and S2-1911848. Revised in parallel session to S2-1912601.","agenda_item_sort_order":34,"ainumber":"7.7.3","ainame":"5GS Enhanced support of Vertical and LAN Services - Type a\/b aspects","tdoc_agenda_sort_order":19120,"status":"revised","reservation_date":"2019-11-19 22:37:10","uploaded":"2019-11-25 16:07:54","revisionof":"S2-1910951","revisedto":"S2-1912601","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"Vertical_LAN"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1912381.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1912382","title":"Support for Untrusted Non-3GPP access for SNPN","source":"Intel","contact":"Saso Stojanovski","contact-id":24932,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clause 4.12.1: clarified that the procedures for Untrusted non-3GPP access can also be used by UE that accesses SNPN service via a PLMN. Clause 4.12.2.2: clarified that 'Access Type' is set to 'Non-3GPP access' even when the UE accesses to SNPN services via PLMN over 3GPP access.","secretary_remarks":"Revision of S2-1911764. Revised in parallel session to S2-1912598.","agenda_item_sort_order":34,"ainumber":"7.7.3","ainame":"5GS Enhanced support of Vertical and LAN Services - Type a\/b aspects","tdoc_agenda_sort_order":19170,"status":"revised","reservation_date":"2019-11-19 22:37:11","uploaded":"2019-11-25 16:07:54","revisionof":"S2-1911764","revisedto":"S2-1912598","release":"Rel-16","crspec":"23.502","crspecversion":"16.2.0","workitem":[{"winame":"Vertical_LAN"}],"crnumber":1940.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1912382.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1912383","title":"Support for Untrusted Non-3GPP access for SNPN","source":"Intel","contact":"Saso Stojanovski","contact-id":24932,"tdoctype":"CR","for":"Approval","abstract":"WITHDRAWN: Summary of change: Clause 5.30.2.8: clarified that 'Access Type' is set to 'non-3GPP access'. Clause 5.30.2.8a (new): new clause on access to SNPN services via non-3GPP access.","secretary_remarks":"Revision of S2-1911767. WITHDRAWN","agenda_item_sort_order":34,"ainumber":"7.7.3","ainame":"5GS Enhanced support of Vertical and LAN Services - Type a\/b aspects","tdoc_agenda_sort_order":19200,"status":"withdrawn","reservation_date":"2019-11-19 22:37:12","uploaded":null,"revisionof":"S2-1911767","revisedto":"","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"Vertical_LAN"}],"crnumber":1989.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1912384","title":"[DRAFT] Reply LS on Sending CAG ID in NAS layer","source":"Qualcomm","contact":"Sebastian Speicher","contact-id":72922,"tdoctype":"LS out","for":"Approval","abstract":"WITHDRAWN: To: SA WG3, RAN WG2, RAN WG3, CT WG1","secretary_remarks":"Revision of S2-1911004, merging S2-1911893. WITHDRAWN","agenda_item_sort_order":34,"ainumber":"7.7.3","ainame":"5GS Enhanced support of Vertical and LAN Services - Type a\/b aspects","tdoc_agenda_sort_order":19230,"status":"withdrawn","reservation_date":"2019-11-19 22:37:13","uploaded":null,"revisionof":"S2-1911004","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"Vertical_LAN"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG3, RAN WG2, RAN WG3, CT WG1","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1912385","title":"PNI-NPN - Reusing NSSAI for AMF selection when NPN isolation is needed","source":"Nokia, Nokia Shanghai Bell","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: It is proposed to clarify: If NPN isolation is required, it is assumed that the operator configures dedicated NSSAI for the given NPN and also configures the NSSAI Inclusion Mode parameter such that NG-RAN receives NSSAI from the UE and it can use the NSSAI for AMF selection.","secretary_remarks":"Revision of S2-1911887. Revised in parallel session to S2-1912599.","agenda_item_sort_order":34,"ainumber":"7.7.3","ainame":"5GS Enhanced support of Vertical and LAN Services - Type a\/b aspects","tdoc_agenda_sort_order":19290,"status":"revised","reservation_date":"2019-11-19 22:37:13","uploaded":"2019-11-25 16:07:54","revisionof":"S2-1911887","revisedto":"S2-1912599","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"Vertical_LAN"}],"crnumber":1997.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1912385.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1912386","title":"Clarifying CAG handling during RRC resume procedure","source":"Qualcomm Incorporated, Ericsson","contact":"Sebastian Speicher","contact-id":72922,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify that - when the UE initiates RRC resume procedure for RRC Inactive to RRC Connected state transition in a CAG cell, NG-RAN shall reject the UE's request if none of the CAG Identifiers supported by the CAG cell are part of the UE's Allowed CAG list according to the Mobility Restrictions received from the AMF. - When the UE initiates RRC resume procedure for RRC Inactive to RRC Connected state transition in a non-CAG cell, NG-RAN shall reject the UE's resume request if the UE is only allowed to access CAG cells according to the Mobility Restrictions received from the AMF.","secretary_remarks":"Revision of S2-1910999. Agreed in parallel session. Block approved","agenda_item_sort_order":34,"ainumber":"7.7.3","ainame":"5GS Enhanced support of Vertical and LAN Services - Type a\/b aspects","tdoc_agenda_sort_order":19460,"status":"agreed","reservation_date":"2019-11-19 22:37:14","uploaded":"2019-11-25 16:07:54","revisionof":"S2-1910999","revisedto":"","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"Vertical_LAN"}],"crnumber":1752.0,"crrevision":3.0,"crcategory":"F","tsg_crp":"SP-191092","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1912386.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1912387","title":"[DRAFT] Reply LS on sending CAG ID during resume procedure","source":"Qualcomm","contact":"Sebastian Speicher","contact-id":72922,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG1. CC: RAN WG2. Attachments: TS 23.501 CR#1752","secretary_remarks":"Revision of S2-1911002. Revised in parallel session to S2-1912603.","agenda_item_sort_order":34,"ainumber":"7.7.3","ainame":"5GS Enhanced support of Vertical and LAN Services - Type a\/b aspects","tdoc_agenda_sort_order":19360,"status":"revised","reservation_date":"2019-11-19 22:37:15","uploaded":"2019-11-25 16:07:54","revisionof":"S2-1911002","revisedto":"S2-1912603","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"Vertical_LAN"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"RAN WG2","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1912387.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1912410","title":"Vertical-LAN type a\/b Drafting Session report.","source":"Nokia","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"other","for":"Information","abstract":"Vertical-LAN type a\/b Drafting Session report.","secretary_remarks":"Created at meeting. Revised in parallel session to S2-1912416.","agenda_item_sort_order":34,"ainumber":"7.7.3","ainame":"5GS Enhanced support of Vertical and LAN Services - Type a\/b aspects","tdoc_agenda_sort_order":19070,"status":"revised","reservation_date":"2019-11-20 19:44:17","uploaded":"2019-11-25 16:07:54","revisionof":"","revisedto":"S2-1912416","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1912410.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1912416","title":"Vertical-LAN type a\/b Drafting Session report.","source":"Nokia","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"other","for":"Information","abstract":"Vertical-LAN type a\/b Drafting Session report.","secretary_remarks":"Revision of S2-1912410. Noted in parallel session","agenda_item_sort_order":34,"ainumber":"7.7.3","ainame":"5GS Enhanced support of Vertical and LAN Services - Type a\/b aspects","tdoc_agenda_sort_order":19080,"status":"noted","reservation_date":"2019-11-20 19:44:22","uploaded":"2019-11-25 16:07:54","revisionof":"S2-1912410","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1912416.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1912417","title":"Reply LS on SUCI computation from an NSI","source":"SA WG2","contact":"Sebastian Speicher","contact-id":72922,"tdoctype":"LS out","for":"Approval","abstract":"To: TSG CT, SA WG1, SA WG3, CT WG1, CT WG6. CC: CT WG4, TSG SA.","secretary_remarks":"Revision of S2-1911006. Agreed in parallel session. Block approved","agenda_item_sort_order":34,"ainumber":"7.7.3","ainame":"5GS Enhanced support of Vertical and LAN Services - Type a\/b aspects","tdoc_agenda_sort_order":19410,"status":"approved","reservation_date":"2019-11-20 19:44:22","uploaded":"2019-11-25 16:07:54","revisionof":"S2-1911006","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"Vertical_LAN"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-1910869","lsto":"TSG CT, SA WG1, SA WG3, CT WG1, CT WG6","Cc":"CT WG4, TSG SA","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1912417.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1912418","title":"UE identifier for SNPN","source":"Nokia, Nokia Shanghai Bell, Deutsche Telekom, Charter, Orange, Vodafone, NTT DOCOMO,China Mobile","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add support for IMSI as SUPI also for UE(s) camping in SNPN, correct wrong reference (28.2.2 does not exist). Considerations: Why is NID needed along with IMSI in the SUPI? If the SNPN uses PLMN ID (MCC 999, MNC ???), then the IMSI with just the PLMN ID will not be unique. Thus the SUPI should also include NID to ensure that the IMSI is unique. In a non-roaming scenario, selected NID could be determined by AMF from NGAP initial UE message however this wouldn't work for SNPN-SNPN roaming scenario and\/or neutral host scenario (if it were to be supported in the future). In case of roaming or neutral host network scenario, home network NID is needed in order to locate the UDM\/UDR\/AUSF. Thus to be forward compatible, also Rel-16 UE(s) should provide the NID along with IMSI in the SUPI. Format in which the IMSI and NID should be encoded? NAI or not? If it is present in NAI, should IMSI be present as part of User name and PLMN ID + NID be present as part of realm? Option 1: UE\/USIM provides the IMSI, ME constructs the NAI using IMSI + NID. Option 2: In the first step, agree that IMSI is a valid identifier for accessing SNPN, also agree that the UE provides NID along with IMSI, simply refer to TS 23.003 for encoding. Way forward proposed: First agree that IMSI is a valid identifier of SUPI for accessing SNPN. Since there is no roaming scenario supported in Rel-16, AMF can rely on the selected NID provided by the RAN over NGAP in order to locate the UDM. Storage in USIM or not is not in scope of SA WG2, leave that to CT WG1, CT WG6 (SA WG3) discussion. Also, refer to TS 23.003 for encoding.","secretary_remarks":"Revision of S2-1910966. Revised in parallel session to S2-1912600.","agenda_item_sort_order":34,"ainumber":"7.7.3","ainame":"5GS Enhanced support of Vertical and LAN Services - Type a\/b aspects","tdoc_agenda_sort_order":19520,"status":"revised","reservation_date":"2019-11-20 19:44:22","uploaded":"2019-11-25 16:07:54","revisionof":"S2-1910966","revisedto":"S2-1912600","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"Vertical_LAN"}],"crnumber":1881.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1912418.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1912419","title":"IMSI-based SUPI for SNPNs","source":"Qualcomm Incorporated, Ericsson","contact":"Sebastian Speicher","contact-id":72922,"tdoctype":"CR","for":"Approval","abstract":"WITHDRAWN: Summary of change: Clarify in clause 5.9.2 that network-specific identifiers also apply to SNPNs. Clarify in clause 5.30.2.3: - If the UE uses credentials stored in the USIM to access the SNPN and the UE is not configured with a subscriber identifier in the form of a SUPI containing a network-specific identifier for the SNPN then the UE shall construct a network-specific identifier for the SNPN based on the IMSI and the SNPN identity (see TS 23.122 [17] clause 4.9.3.0). - Correct clause number in the reference to TS 23.003.","secretary_remarks":"Revision of S2-1910998. WITHDRAWN","agenda_item_sort_order":34,"ainumber":"7.7.3","ainame":"5GS Enhanced support of Vertical and LAN Services - Type a\/b aspects","tdoc_agenda_sort_order":19550,"status":"withdrawn","reservation_date":"2019-11-20 19:44:23","uploaded":null,"revisionof":"S2-1910998","revisedto":"","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"Vertical_LAN"}],"crnumber":1850.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1912431","title":"LS from RAN WG3: Reply LS on Sending CAG ID in NAS layer","source":"RAN WG3","contact":"Alexander Vesely","contact-id":10078,"tdoctype":"LS in","for":"Action","abstract":"RAN WG3 thanks SA WG3 for the LS on Sending CAG ID in NAS Layer. RAN WG3 has discussed the SA WG3 proposal to protect the transfer of the selected CAG ID between the UE and the network and concluded that it is feasible from RAN WG3 point of view to perform initial access control without the UE providing any selected CAG ID to the network. Further access control during mobility will be performed by NG-RAN based on PNI-NPN specific information provided in the mobility restriction list. Action: RAN WG3 asks SA WG3, SA WG2 and RAN WG2 to take RAN WG3's finding into account and provide information about a final decision.","secretary_remarks":"Postponed","agenda_item_sort_order":34,"ainumber":"7.7.3","ainame":"5GS Enhanced support of Vertical and LAN Services - Type a\/b aspects","tdoc_agenda_sort_order":19250,"status":"postponed","reservation_date":"2019-11-20 19:44:36","uploaded":"2019-11-25 16:07:54","revisionof":"","revisedto":"S2-2000027","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG3, SA WG2, RAN WG2","Cc":"CT WG1","lsoriginalls":"R3-197591","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1912431.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1912598","title":"Support for Untrusted Non-3GPP access for SNPN","source":"Intel","contact":"Saso Stojanovski","contact-id":24932,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clause 4.12.1: clarified that the procedures for Untrusted non-3GPP access can also be used by UE that accesses SNPN service via a PLMN over 3GPP access. Clause 4.12.2.2: clarified that 'Access Type' is set to 'Non-3GPP access' even when the UE accesses to SNPN services via PLMN over 3GPP access.","secretary_remarks":"Revision of S2-1912382. Agreed in parallel session. Block approved","agenda_item_sort_order":34,"ainumber":"7.7.3","ainame":"5GS Enhanced support of Vertical and LAN Services - Type a\/b aspects","tdoc_agenda_sort_order":19300,"status":"agreed","reservation_date":"2019-11-25 15:21:17","uploaded":"2019-11-25 16:07:54","revisionof":"S2-1912382","revisedto":"","release":"Rel-16","crspec":"23.502","crspecversion":"16.2.0","workitem":[{"winame":"Vertical_LAN"}],"crnumber":1940.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"SP-191092","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1912598.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1912599","title":"PNI-NPN - Reusing NSSAI for AMF selection when NPN isolation is needed","source":"Nokia, Nokia Shanghai Bell, Ericsson","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: It is proposed to clarify: If NPN isolation is required, it is assumed that the operator configures dedicated NSSAI for the given NPN and also configures the NSSAI Inclusion Mode parameter such that NG-RAN receives NSSAI from the UE and it can use the NSSAI for AMF selection.","secretary_remarks":"Revision of S2-1912385. Revised in parallel session to S2-1912730.","agenda_item_sort_order":34,"ainumber":"7.7.3","ainame":"5GS Enhanced support of Vertical and LAN Services - Type a\/b aspects","tdoc_agenda_sort_order":19300,"status":"revised","reservation_date":"2019-11-25 15:21:18","uploaded":"2019-11-25 16:07:54","revisionof":"S2-1912385","revisedto":"S2-1912730","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"Vertical_LAN"}],"crnumber":1997.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1912599.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1912600","title":"UE identifier for SNPN","source":"Nokia, Nokia Shanghai Bell, Deutsche Telekom, Charter, Orange, Vodafone, NTT DOCOMO,China Mobile, Qualcomm, Ericsson","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add support for IMSI as SUPI also for UE(s) camping in SNPN, correct wrong reference (28.2.2 does not exist).","secretary_remarks":"Revision of S2-1912418. Agreed in parallel session. Block approved","agenda_item_sort_order":34,"ainumber":"7.7.3","ainame":"5GS Enhanced support of Vertical and LAN Services - Type a\/b aspects","tdoc_agenda_sort_order":19650,"status":"agreed","reservation_date":"2019-11-25 15:21:19","uploaded":"2019-11-25 16:07:54","revisionof":"S2-1912418","revisedto":"","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"Vertical_LAN"}],"crnumber":1881.0,"crrevision":3.0,"crcategory":"F","tsg_crp":"SP-191092","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1912600.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1912601","title":"Reply LS on applicability of the notification procedure in SNPNs","source":"SA WG2","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG1.","secretary_remarks":"Revision of S2-1912381. Agreed in parallel session. Block approved","agenda_item_sort_order":34,"ainumber":"7.7.3","ainame":"5GS Enhanced support of Vertical and LAN Services - Type a\/b aspects","tdoc_agenda_sort_order":19130,"status":"approved","reservation_date":"2019-11-25 15:21:20","uploaded":"2019-11-25 16:07:54","revisionof":"S2-1912381","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"Vertical_LAN"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-1910853","lsto":"CT WG1","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1912601.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1912602","title":"LS on RAN sharing for NPNs","source":"SA WG2","contact":"Sebastian Speicher","contact-id":72922,"tdoctype":"LS out","for":"Approval","abstract":"To: RAN WG2, RAN WG3. Attachments: S2-1912379 (TS 23.501 CR#1798).","secretary_remarks":"Revision of S2-1912380. Agreed in parallel session. Block approved","agenda_item_sort_order":34,"ainumber":"7.7.3","ainame":"5GS Enhanced support of Vertical and LAN Services - Type a\/b aspects","tdoc_agenda_sort_order":19460,"status":"approved","reservation_date":"2019-11-25 15:21:21","uploaded":"2019-11-25 16:07:54","revisionof":"S2-1912380","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"Vertical_LAN"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2, RAN WG3","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1912602.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1912603","title":"[DRAFT] Reply LS on sending CAG ID during resume procedure","source":"Qualcomm","contact":"Sebastian Speicher","contact-id":72922,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG1. CC: RAN WG2. Attachments: TS 23.501 CR#1752","secretary_remarks":"Revision of S2-1912387. Revised in parallel session to S2-1912731.","agenda_item_sort_order":34,"ainumber":"7.7.3","ainame":"5GS Enhanced support of Vertical and LAN Services - Type a\/b aspects","tdoc_agenda_sort_order":19370,"status":"revised","reservation_date":"2019-11-25 15:21:21","uploaded":"2019-11-25 16:07:54","revisionof":"S2-1912387","revisedto":"S2-1912731","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"Vertical_LAN"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"RAN WG2","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1912603.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1912730","title":"PNI-NPN - Reusing NSSAI for AMF selection when NPN isolation is needed","source":"Nokia, Nokia Shanghai Bell, Ericsson","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: It is proposed to clarify: If NPN isolation is required, it is assumed that the operator configures dedicated NSSAI for the given NPN and also configures the NSSAI Inclusion Mode parameter such that NG-RAN receives NSSAI from the UE and it can use the NSSAI for AMF selection.","secretary_remarks":"Revision of S2-1912599. Agreed in parallel session. Block approved","agenda_item_sort_order":34,"ainumber":"7.7.3","ainame":"5GS Enhanced support of Vertical and LAN Services - Type a\/b aspects","tdoc_agenda_sort_order":19430,"status":"agreed","reservation_date":"2019-11-25 15:22:36","uploaded":"2019-11-25 16:07:57","revisionof":"S2-1912599","revisedto":"","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"Vertical_LAN"}],"crnumber":1997.0,"crrevision":3.0,"crcategory":"F","tsg_crp":"SP-191092","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1912730.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1912731","title":"Reply LS on sending CAG ID during resume procedure","source":"SA WG2","contact":"Sebastian Speicher","contact-id":72922,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG1. CC: RAN WG2. Attachments: S2-1912386 (TS 23.501 CR#1752).","secretary_remarks":"Revision of S2-1912603. Agreed in parallel session. Block approved","agenda_item_sort_order":34,"ainumber":"7.7.3","ainame":"5GS Enhanced support of Vertical and LAN Services - Type a\/b aspects","tdoc_agenda_sort_order":19380,"status":"approved","reservation_date":"2019-11-25 15:22:37","uploaded":"2019-11-25 16:07:57","revisionof":"S2-1912603","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"Vertical_LAN"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-1910852","lsto":"CT WG1","Cc":"RAN WG2","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1912731.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]