[{"name":"S2-2201944","title":"LS from RAN WG2: Reply LS on LTE User Plane Integrity Protection","source":"RAN WG2","contact":"Chris Pudney","contact-id":1122,"tdoctype":"LS in","for":"Information","abstract":"RAN WG2 thanks SA WG3 for their LS in S3-214462\/R3-220128. RAN WG2 is taking this information into account (along with the CRs agreed in SA WG2, CT WG4 and CT WG1), but only to the extent that is described by the WID agreed by RAN plenary in RP-213669 which, in particular, restricts the scope to EN-DC capable UEs. In response to SA WG3's request '\u2026to inform SA WG3 on their final decision with respect to which algorithm code points are to be used', RAN WG2 would like to provide the following information: UPIP for the EPC connected architectures uses NR PDCP and is configured in following way: - (as is done for legacy LTE UE) an LTE algorithm code point is configured in field integrityProtectionAlgorithm in IE SecurityAlgorithmConfig in the TS 36.331 SecurityModeCommand message, and this is used to derive KUPint (and also to derive KUPEnc, as for legacy LTE UE). - The NR algorithm code point (corresponding to the LTE algorithm code point used in the SecurityModeCommand) indicated by the integrityProtAlgorithm included in the securityConfig in the TS 38.331 RadioBearerConfig is used to configure the UP IP algorithm applied by NR PDCP to perform integrity protection. - The integrityProtection indicated in pdcp-Config in the DRB-ToAddMod(list) in the TS 38.331 RadioBearerConfig is used to activate the UP IP for a DRB using the configured algorithm, which can be done only at DRB setup. Consequently, UP IP activation\/deactivation for a DRB can be changed only by DRB-release-and-add.","secretary_remarks":"Noted","agenda_item_sort_order":36,"ainumber":"8.28","ainame":"Rel-17 CAT B\/C alignment CR(s) due to the work led by other 3GPP Working Groups","tdoc_agenda_sort_order":14230,"status":"noted","reservation_date":"2022-03-25 17:03:58","uploaded":"2022-03-28 10:15:39","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG3","Cc":"SA WG2, RAN WG3","lsoriginalls":"R2-2203663","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_150E_Electronic_2022-04\/Docs\/S2-2201944.zip","group":"S2","meeting":"S2-150-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2201947","title":"LS from RAN WG2: Reply LS on Slice list and priority information for cell reselection","source":"RAN WG2","contact":"Zhe Fu","contact-id":78347,"tdoctype":"LS in","for":"Action","abstract":"RAN WG2 would like to thank SA WG2 for their reply LS on Slice list and priority information for cell reselection. RAN WG2 has re-discussed the mapping of slice to the slice groups based on the latest SA WG2 LS. RAN WG2 understands whether per TA or per PLMN granularity has no major RAN WG2 impacts. However, RAN WG2 assumes (based on majority views in RAN WG2) that the mapping of slice to the slice groups for cell reselection is per TA. RAN WG2 also assumes that the NAS layer in the UE is able to provide slice group priorities to AS layer in the UE. RAN WG2 considers the WI is completed from RAN WG2 specification perspective based on the above assumptions. RAN WG2 expects other WGs to finalize their relevant specifications and indicate if RAN WG2 assumptions are not valid before RAN WG2#118. RAN WG2 has achieved the following agreements. 1. A slice is not associated with multiple slice groups for the same purpose within a slice to slice group mapping 'granularity'. A slice can be associated at most with one slice group for RACH and with one slice group for reselection, within the same granularity. 2. Both for RACH and for cell reselection, the UE NAS needs to provide the slice information to the UE AS. The UE AS is aware of the slice group ID (s) based on such slice information provided by the UE NAS. Actions: RAN WG2 kindly asks SA WG2, CT WG1, RAN WG3, SA, RAN and CT to take the above information into consideration. RAN WG2 expects SA WG2, CT WG1 and RAN WG3 to finalize their relevant specifications and indicate if the RAN WG2 assumptions are not valid before RAN WG2#118.","secretary_remarks":"Response drafted in S2-2202658. Final response in S2-2203597","agenda_item_sort_order":36,"ainumber":"8.28","ainame":"Rel-17 CAT B\/C alignment CR(s) due to the work led by other 3GPP Working Groups","tdoc_agenda_sort_order":14240,"status":"replied to","reservation_date":"2022-03-25 17:03:58","uploaded":"2022-03-28 10:15:39","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, CT WG1, RAN WG3, TSG SA, TSG RAN, TSG CT","Cc":"","lsoriginalls":"R2-2203807","lsreply":"S2-2203597, S2-2203597","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_150E_Electronic_2022-04\/Docs\/S2-2201947.zip","group":"S2","meeting":"S2-150-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2201952","title":"LS from RAN WG2: LS out on PEI and UE Subgrouping","source":"RAN WG2","contact":"Fei Dong","contact-id":81560,"tdoctype":"LS in","for":"Information","abstract":"RAN WG2 has discussed about 'last used cell' issue for PEI capable UE, and the following agreements were made: - A PEI-capable UE stores its 'last used cell' information. FFS on how to capture this in the specifications. - Do not introduce an associated timer for the 'last used cell' information stored by UE. - The 'lastUsedCellOnly' indication is a cell-level configuration and there is no per-subgroup indication. - Introduce a one-bit indication of lastUsedCellOnly in PEI-Config. - RAN WG2 clarifies the meaning of 'last used cell only': When a cell broadcasts 'last used cell only', a UE monitors PEI only if its last connection was released by this cell. With above agreements, RAN WG2 also has triggered a further discussion on the mismatched understanding about the 'last used cell' between UE and NW. RAN WG2 understands that the UE assumes the 'last used cell' is a cell by which the last connection was released, but CN may not update the 'last used cell' to that cell if CN was not involved in such connection release. To solve this issue, one potential solution is to reuse LTE method, i.e. to introduce 'no last cell update' indication in RRCRelease message for NR PEI. RAN WG2 would like to ask: Question 1: Whether the mismatched understanding about the 'last used cell' between UE and NW still exists in NR, if so, whether the LTE method (i.e. to introduce 'no last cell update' indication in RRCRelease Message) can be reused? In addition, RAN WG2 also have discussed one problematic scenario where certain gNB(s) within a RNA does not support CN-assigned subgrouping but others do. In this scenario, assuming that the anchor gNB does not support CN assigned subgrouping, it may not forward any information (e.g. CN assigned subgroup ID) to other gNBs when initiating a RAN paging to a UE. It may result that the UE will try to receive the paging information according to the CN assigned subgroup ID, if any, after cell-reselection. But the current camped cell that supports CN assigned subgrouping will page UE by not using the CN assigned subgroup ID due to the lack of the CN assigned information about that UE from the anchor gNB. RAN WG2 would like to ask: Question 2: Whether this problematic scenario can be avoided or needs to be resolved through signaling?","secretary_remarks":"Response drafted in S2-2202900. Final response in S2-2203252","agenda_item_sort_order":36,"ainumber":"8.28","ainame":"Rel-17 CAT B\/C alignment CR(s) due to the work led by other 3GPP Working Groups","tdoc_agenda_sort_order":14200,"status":"replied to","reservation_date":"2022-03-25 17:03:59","uploaded":"2022-03-28 10:15:39","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG3","Cc":"SA WG2, CT WG1","lsoriginalls":"R2-2204240","lsreply":"S2-2203252, S2-2203252","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_150E_Electronic_2022-04\/Docs\/S2-2201952.zip","group":"S2","meeting":"S2-150-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2202052","title":"Enabling Network Slice Access Stratum groups","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Enabling the per PLMN level Slice Groups and slice priorities handling in UE as described above.","secretary_remarks":"Merged into S2-2203618","agenda_item_sort_order":36,"ainumber":"8.28","ainame":"Rel-17 CAT B\/C alignment CR(s) due to the work led by other 3GPP Working Groups","tdoc_agenda_sort_order":14280,"status":"merged","reservation_date":"2022-03-28 09:23:02","uploaded":"2022-03-29 14:51:13","revisionof":"","revisedto":"","release":"Rel-17","crspec":"23.501","crspecversion":"17.4.0","workitem":[{"winame":"NR_slice-Core"}],"crnumber":3586.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_150E_Electronic_2022-04\/Docs\/S2-2202052.zip","group":"S2","meeting":"S2-150-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2202053","title":"Enabling Network Slice Access Stratum groups","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Enabling the per PLMN level Slice Groups and slice priorities handling in UE as described above.","secretary_remarks":"Merged into S2-2203619","agenda_item_sort_order":36,"ainumber":"8.28","ainame":"Rel-17 CAT B\/C alignment CR(s) due to the work led by other 3GPP Working Groups","tdoc_agenda_sort_order":14290,"status":"merged","reservation_date":"2022-03-28 09:23:03","uploaded":"2022-03-29 14:51:13","revisionof":"","revisedto":"","release":"Rel-17","crspec":"23.502","crspecversion":"17.4.0","workitem":[{"winame":"NR_slice-Core"}],"crnumber":3422.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_150E_Electronic_2022-04\/Docs\/S2-2202053.zip","group":"S2","meeting":"S2-150-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2202176","title":"Updates to support 5G NSWO","source":"Nokia, Nokia Shanghai Bell","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The CR endorses the assumptions taken by SA WG3 on NSWO roaming and removes the corresponding Editor\u00b4s Note, adding a reference to 33.501 The CR removes the other EN (Editor\u00b4s Note: It is FFS whether the UE can first connect to a WLAN access network using 5GS credentials and without performing 5GS registration, and then later perform on this WLAN access network 5GS registration using the trusted non-3GPP access procedure.) When a UE first connects to a WLAN access network for NSWO (using 5GS credentials but without performing 5GS registration), the UE establishes a WLAN session not involving EAP-5G and 5G-NAS Registration related signaling; If the UE wants later to use the same AP for TNGF access, it cannot provide 5G-NAS information about EAP-5G without restarting the WLAN association from scratch","secretary_remarks":"Merged into S2-2203254","agenda_item_sort_order":36,"ainumber":"8.28","ainame":"Rel-17 CAT B\/C alignment CR(s) due to the work led by other 3GPP Working Groups","tdoc_agenda_sort_order":14300,"status":"merged","reservation_date":"2022-03-28 16:38:00","uploaded":"2022-03-29 19:09:54","revisionof":"","revisedto":"","release":"Rel-17","crspec":"23.501","crspecversion":"17.4.0","workitem":[{"winame":"NSWO_5G"}],"crnumber":3592.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_150E_Electronic_2022-04\/Docs\/S2-2202176.zip","group":"S2","meeting":"S2-150-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2202177","title":"Updates to support 5G NSWO","source":"Nokia, Nokia Shanghai Bell","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Different NAI realm formats are defined for the UE to be able to indicate to a WLAN access network whether the UE wishes Trusted Non 3GPP (TNGF) access to 5GC or wishes to connect to the WLAN access network using its 5GS credentials but without registration to 5GS (as defined in TS 23.501). These NAI formats are defined in TS 23.003.","secretary_remarks":"Noted","agenda_item_sort_order":36,"ainumber":"8.28","ainame":"Rel-17 CAT B\/C alignment CR(s) due to the work led by other 3GPP Working Groups","tdoc_agenda_sort_order":14310,"status":"noted","reservation_date":"2022-03-28 16:38:01","uploaded":"2022-03-29 19:09:54","revisionof":"","revisedto":"","release":"Rel-17","crspec":"23.502","crspecversion":"17.4.0","workitem":[{"winame":"NSWO_5G"}],"crnumber":3429.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_150E_Electronic_2022-04\/Docs\/S2-2202177.zip","group":"S2","meeting":"S2-150-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2202178","title":"[DRAFT] LS on 5G NSWO roaming aspects","source":"Nokia, Nokia Shanghai Bell","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"LS out","for":"Approval","abstract":"[draft] LS on 5G NSWO roaming aspects","secretary_remarks":"r02 agreed. Revised to S2-2203253","agenda_item_sort_order":36,"ainumber":"8.28","ainame":"Rel-17 CAT B\/C alignment CR(s) due to the work led by other 3GPP Working Groups","tdoc_agenda_sort_order":14310,"status":"revised","reservation_date":"2022-03-28 16:38:02","uploaded":"2022-03-29 19:09:54","revisionof":"","revisedto":"S2-2203253","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"NSWO_5G"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG3","Cc":"CT WG3, CT WG4, TSG CT","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_150E_Electronic_2022-04\/Docs\/S2-2202178.zip","group":"S2","meeting":"S2-150-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2202223","title":"Discussion on Slice list and priority information for cell reselection.","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"discussion","for":"Agreement","abstract":"This discussion paper aims at discussing the issues for slice based cell reselection, slice grouping, and the slice info required for cell reselection and proposes a way forward.","secretary_remarks":"Noted","agenda_item_sort_order":36,"ainumber":"8.28","ainame":"Rel-17 CAT B\/C alignment CR(s) due to the work led by other 3GPP Working Groups","tdoc_agenda_sort_order":14330,"status":"noted","reservation_date":"2022-03-28 17:35:55","uploaded":"2022-03-29 21:10:21","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":[{"winame":"NR_slice-Core"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_150E_Electronic_2022-04\/Docs\/S2-2202223.zip","group":"S2","meeting":"S2-150-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2202224","title":"Enabling slice priority and slice groups for RRM purposes","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Enabling the slice priorities as requested. Option 1: NG-RAN provides the network slice priorities to the UE Option 2: AMF provides the network slice priorities to the UE","secretary_remarks":"Revision of SP-220319. Revised to S2-2203620, merging S2-2202702 and S2-2202225","agenda_item_sort_order":36,"ainumber":"8.28","ainame":"Rel-17 CAT B\/C alignment CR(s) due to the work led by other 3GPP Working Groups","tdoc_agenda_sort_order":14350,"status":"revised","reservation_date":"2022-03-28 17:35:55","uploaded":"2022-03-29 21:10:21","revisionof":"","revisedto":"S2-2203620","release":"Rel-17","crspec":"23.501","crspecversion":"17.4.0","workitem":[{"winame":"NR_slice-Core"}],"crnumber":3317.0,"crrevision":5.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_150E_Electronic_2022-04\/Docs\/S2-2202224.zip","group":"S2","meeting":"S2-150-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2202225","title":"Enabling slice priority and slice groups for RRM purposes","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Enabling the slice priorities as requested. AMF may provide the network slice priorities to the UE as part of Service Accept.","secretary_remarks":"Merged into S2-2203620","agenda_item_sort_order":36,"ainumber":"8.28","ainame":"Rel-17 CAT B\/C alignment CR(s) due to the work led by other 3GPP Working Groups","tdoc_agenda_sort_order":14370,"status":"merged","reservation_date":"2022-03-28 17:35:57","uploaded":"2022-03-29 21:10:21","revisionof":"","revisedto":"","release":"Rel-17","crspec":"23.502","crspecversion":"17.4.0","workitem":[{"winame":"NR_slice-Core"}],"crnumber":3435.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_150E_Electronic_2022-04\/Docs\/S2-2202225.zip","group":"S2","meeting":"S2-150-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2202226","title":"Enabling Network Slice Access Stratum groups","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Enabling the Slice Groups and slice priorities as requested, with a per PLMN granularity while allowing a re-use at a geographical distance based on OAM.","secretary_remarks":"Revision of SP-220317. Merged into S2-2203618","agenda_item_sort_order":36,"ainumber":"8.28","ainame":"Rel-17 CAT B\/C alignment CR(s) due to the work led by other 3GPP Working Groups","tdoc_agenda_sort_order":14380,"status":"merged","reservation_date":"2022-03-28 17:35:58","uploaded":"2022-03-29 21:10:21","revisionof":"","revisedto":"","release":"Rel-17","crspec":"23.501","crspecversion":"17.4.0","workitem":[{"winame":"NR_slice-Core"}],"crnumber":3482.0,"crrevision":2.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_150E_Electronic_2022-04\/Docs\/S2-2202226.zip","group":"S2","meeting":"S2-150-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2202227","title":"Enabling Network Slice Acess stratum group","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Enabling the Slice Groups and slice priorities as requested, with a per PLMN granularity while allowing a re-use at a geographical distance based on OAM.","secretary_remarks":"Revision of SP-220318. Merged into S2-2203619","agenda_item_sort_order":36,"ainumber":"8.28","ainame":"Rel-17 CAT B\/C alignment CR(s) due to the work led by other 3GPP Working Groups","tdoc_agenda_sort_order":14390,"status":"merged","reservation_date":"2022-03-28 17:36:00","uploaded":"2022-03-29 21:10:21","revisionof":"","revisedto":"","release":"Rel-17","crspec":"23.502","crspecversion":"17.4.0","workitem":[{"winame":"NR_slice-Core"}],"crnumber":3334.0,"crrevision":2.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_150E_Electronic_2022-04\/Docs\/S2-2202227.zip","group":"S2","meeting":"S2-150-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2202228","title":"[DRAFT] LS on enabling support for Slice Groups and Slice priorities for RAN Slicing","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"LS out","for":"Approval","abstract":"Informing WGs of SA WG2 progress on enabling RAN slicing and asks a set of questions","secretary_remarks":"Merged into S2-2203597","agenda_item_sort_order":36,"ainumber":"8.28","ainame":"Rel-17 CAT B\/C alignment CR(s) due to the work led by other 3GPP Working Groups","tdoc_agenda_sort_order":14390,"status":"merged","reservation_date":"2022-03-28 17:36:00","uploaded":"2022-03-29 21:10:21","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"NR_slice-Core"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2, RAN WG3, CT WG1, CT WG4","Cc":"TSG SA, TSG RAN, TSG CT, SA WG5","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_150E_Electronic_2022-04\/Docs\/S2-2202228.zip","group":"S2","meeting":"S2-150-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2202655","title":"NSWO and N3GPP access support.","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"discussion","for":"Agreement","abstract":"This contribution proposes to address the support of roaming, the connection to WLAN access network for NSWOF and the subsequent access to WLAN as untrusted and trusted network.","secretary_remarks":"Noted","agenda_item_sort_order":36,"ainumber":"8.28","ainame":"Rel-17 CAT B\/C alignment CR(s) due to the work led by other 3GPP Working Groups","tdoc_agenda_sort_order":14400,"status":"noted","reservation_date":"2022-03-29 12:10:43","uploaded":"2022-03-29 12:54:06","revisionof":"","revisedto":"","release":"Rel-17","crspec":"23.501","crspecversion":"","workitem":[{"winame":"NSWO_5G"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_150E_Electronic_2022-04\/Docs\/S2-2202655.zip","group":"S2","meeting":"S2-150-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2202658","title":"[DRAFT] Reply LS on Slice list and priority information for cell reselection","source":"ZTE","contact":"Jinguo Zhu","contact-id":32987,"tdoctype":"LS out","for":"Approval","abstract":"To: RAN WG2. CC: RAN WG3","secretary_remarks":"Response to S2-2201947. r17 + changes agreed. Revised to S2-2203597, merging S2-2202228.","agenda_item_sort_order":36,"ainumber":"8.28","ainame":"Rel-17 CAT B\/C alignment CR(s) due to the work led by other 3GPP Working Groups","tdoc_agenda_sort_order":14250,"status":"revised","reservation_date":"2022-03-29 12:14:54","uploaded":"2022-03-29 14:07:37","revisionof":"","revisedto":"S2-2203597","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"NR_slice-Core"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2","Cc":"RAN WG3","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_150E_Electronic_2022-04\/Docs\/S2-2202658.zip","group":"S2","meeting":"S2-150-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2202659","title":"Enabling configuration of Network Slice AS Groups","source":"ZTE, China Mobile","contact":"Jinguo Zhu","contact-id":32987,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Configuration of NSAGs (Network Slices AS Groups) Revision 2 Add one Editor Note Add NSAG priority in NAS to the UE","secretary_remarks":"Revision of SP-220303. Merged into S2-2203618","agenda_item_sort_order":36,"ainumber":"8.28","ainame":"Rel-17 CAT B\/C alignment CR(s) due to the work led by other 3GPP Working Groups","tdoc_agenda_sort_order":14420,"status":"merged","reservation_date":"2022-03-29 12:14:54","uploaded":"2022-03-29 14:07:37","revisionof":"","revisedto":"","release":"Rel-17","crspec":"23.501","crspecversion":"17.4.0","workitem":[{"winame":"NR_slice-Core"},{"winame":" TEI17"}],"crnumber":3539.0,"crrevision":2.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_150E_Electronic_2022-04\/Docs\/S2-2202659.zip","group":"S2","meeting":"S2-150-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2202676","title":"Proposal on slice priority and slice group","source":"China Mobile","contact":"Dan Wang","contact-id":87155,"tdoctype":"discussion","for":"Discussion","abstract":"Proposal on slice priority and slice group","secretary_remarks":"Noted","agenda_item_sort_order":36,"ainumber":"8.28","ainame":"Rel-17 CAT B\/C alignment CR(s) due to the work led by other 3GPP Working Groups","tdoc_agenda_sort_order":14420,"status":"noted","reservation_date":"2022-03-29 12:18:06","uploaded":"2022-03-29 14:20:49","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_150E_Electronic_2022-04\/Docs\/S2-2202676.zip","group":"S2","meeting":"S2-150-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2202677","title":"23.501: NSWO and N3GPP access support","source":"Huawei","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The following changes are proposed 1) specify in clause 4.2.15 and in 4.30.2.0 that 5G NSWO is not applicable to SNPN. 2) addition of roaming architceture in clause 4.2.15 in both point to point reference model and SBI model 3) addition in clause 5.3.2.4 that 5G NSWO authentication does not change the registration state of UE. 5) addition of new clause specifying the NSWOF NF. 4) addition of NSWOF in AUSF selection procedure in clause 5.3.2.4","secretary_remarks":"r05 agreed. Revised to S2-2203254, merging S2-2202176","agenda_item_sort_order":36,"ainumber":"8.28","ainame":"Rel-17 CAT B\/C alignment CR(s) due to the work led by other 3GPP Working Groups","tdoc_agenda_sort_order":14440,"status":"revised","reservation_date":"2022-03-29 12:18:46","uploaded":"2022-03-29 12:54:06","revisionof":"","revisedto":"S2-2203254","release":"Rel-17","crspec":"23.501","crspecversion":"17.4.0","workitem":[{"winame":"NSWO_5G"}],"crnumber":3617.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_150E_Electronic_2022-04\/Docs\/S2-2202677.zip","group":"S2","meeting":"S2-150-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2202702","title":"Enabling slice priority and slice groups for RRM purposes","source":"Nokia, Nokia Shanghai Bell, CMCC, NEC, Verizon UK ltd.,ZTE, InterDigital, Xiaomi, LGE, Samsung","contact":"Alessio Casati","contact-id":82456,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Enabling the UE to apply slice prioritization and trigger cell reselection based on local info","secretary_remarks":"Revision of S2-2200508. Merged into S2-2203620","agenda_item_sort_order":36,"ainumber":"8.28","ainame":"Rel-17 CAT B\/C alignment CR(s) due to the work led by other 3GPP Working Groups","tdoc_agenda_sort_order":14460,"status":"merged","reservation_date":"2022-03-29 13:29:14","uploaded":"2022-03-29 14:07:32","revisionof":"S2-2200508","revisedto":"","release":"Rel-17","crspec":"23.501","crspecversion":"17.4.0","workitem":[{"winame":"NR_slice-Core"},{"winame":" TEI17"}],"crnumber":3317.0,"crrevision":6.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_150E_Electronic_2022-04\/Docs\/S2-2202702.zip","group":"S2","meeting":"S2-150-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2202706","title":"Enabling configuration of Network Slice AS Groups","source":"Nokia, Nokia Shanghai Bell, CMCC, NEC, Verizon UK ltd, ZTE, InterDigital, Xiaomi, LGE, Samsung","contact":"Alessio Casati","contact-id":82456,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Configuration of NSAGs (Network Slices AS Groups)","secretary_remarks":"Revision of S2-2200847. Revised to S2-2203618, merging S2-2202052, S2-2202226 and S2-2202659","agenda_item_sort_order":36,"ainumber":"8.28","ainame":"Rel-17 CAT B\/C alignment CR(s) due to the work led by other 3GPP Working Groups","tdoc_agenda_sort_order":14470,"status":"revised","reservation_date":"2022-03-29 13:42:35","uploaded":"2022-03-29 14:07:32","revisionof":"S2-2200847","revisedto":"S2-2203618","release":"Rel-17","crspec":"23.501","crspecversion":"17.4.0","workitem":[{"winame":"NR_slice-Core"},{"winame":" TEI17"}],"crnumber":3539.0,"crrevision":3.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_150E_Electronic_2022-04\/Docs\/S2-2202706.zip","group":"S2","meeting":"S2-150-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2202711","title":"Enabling configuration of Network Slice AS Groups","source":"Nokia, Nokia Shanghai Bell, CMCC, NEC, Verizon UK ltd.,ZTE, InterDigital, Xiaomi, LGE, Samsung","contact":"Alessio Casati","contact-id":82456,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Configuration of NSAGs (Network Slices AS Groups)","secretary_remarks":"Revision of S2-2200918. Revised to S2-2203619, merging S2-2202053 and S2-2202227","agenda_item_sort_order":36,"ainumber":"8.28","ainame":"Rel-17 CAT B\/C alignment CR(s) due to the work led by other 3GPP Working Groups","tdoc_agenda_sort_order":14490,"status":"revised","reservation_date":"2022-03-29 13:45:33","uploaded":"2022-03-29 14:07:32","revisionof":"S2-2200918","revisedto":"S2-2203619","release":"Rel-17","crspec":"23.502","crspecversion":"17.4.0","workitem":[{"winame":"NR_slice-Core"},{"winame":" TEI17"}],"crnumber":3300.0,"crrevision":3.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_150E_Electronic_2022-04\/Docs\/S2-2202711.zip","group":"S2","meeting":"S2-150-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2202725","title":"Discussion on Slice list and priority information for cell reselection.","source":"Nokia, Nokia Shanghai Bell, InterDigital, NEC","contact":"Alessio Casati","contact-id":82456,"tdoctype":"discussion","for":"Discussion","abstract":"This discussion paper aims at discussing the issues for slice-based cell reselection, slice grouping, and the slice info required for cell reselection and proposes a way forward.","secretary_remarks":"Noted","agenda_item_sort_order":36,"ainumber":"8.28","ainame":"Rel-17 CAT B\/C alignment CR(s) due to the work led by other 3GPP Working Groups","tdoc_agenda_sort_order":14500,"status":"noted","reservation_date":"2022-03-29 14:02:25","uploaded":"2022-03-29 14:07:32","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"NR_slice-Core"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_150E_Electronic_2022-04\/Docs\/S2-2202725.zip","group":"S2","meeting":"S2-150-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2202739","title":"AMF relocation in connected state","source":"NEC","contact":"Kundan Tiwari","contact-id":76330,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Specify that when the serving AMF receives Registration Request message while in CM-CONNECTED state and the allowed NSSAI is served by another AMF, then AMF performs AMF relocation procedure either via NG-RAN or directly forwarding the NAS message to the target AMF.","secretary_remarks":"Revision of S2-2201165. r02 + changes agreed. Revised to S2-2203598 (New CR number 3465 allocated as this one was already TSG SA approved).","agenda_item_sort_order":36,"ainumber":"8.28","ainame":"Rel-17 CAT B\/C alignment CR(s) due to the work led by other 3GPP Working Groups","tdoc_agenda_sort_order":14520,"status":"revised","reservation_date":"2022-03-29 14:27:00","uploaded":"2022-03-29 17:10:12","revisionof":"S2-2201165","revisedto":"S2-2203598","release":"Rel-17","crspec":"23.502","crspecversion":"17.4.0","workitem":[{"winame":"eNS_Ph2"}],"crnumber":3102.0,"crrevision":3.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_150E_Electronic_2022-04\/Docs\/S2-2202739.zip","group":"S2","meeting":"S2-150-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2202786","title":"LS from RAN WG3: Reply LS on User Plane Integrity Protection for eUTRA connected to EPC","source":"RAN WG3","contact":"Luis Lopes","contact-id":84588,"tdoctype":"LS in","for":"Information","abstract":"RAN WG3 thanks SA WG3 for the further LS reply and understands that SA WG3 would like to ensure that all of MME, eNB, AMF and NG-RAN nodes copy on the complete UE security capabilities, so the information on all RAN interfaces is equivalent to that captured at NAS level. RAN WG3 has agreed to make the necessary changes from release 17, at both stage 2 (TS 36.300, TS 38.300 and TS 37.340) and stage 3 levels (TS 36.413, TS 36.423, TS 38.413 and TS 38.423), covering all relevant protocols and scenarios. RAN WG3 would also like to inform that the agreed S1AP CR includes support for the new requirement agreed by SA WG3 in S3-214452 to enable the MME to return its locally stored UE EPS security capabilities to the target eNB in the response to the Path Switch Request message.","secretary_remarks":"Noted","agenda_item_sort_order":36,"ainumber":"8.28","ainame":"Rel-17 CAT B\/C alignment CR(s) due to the work led by other 3GPP Working Groups","tdoc_agenda_sort_order":14530,"status":"noted","reservation_date":"2022-03-29 15:34:29","uploaded":"2022-03-29 17:47:55","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG3","Cc":"RAN WG2, CT WG1, CT WG4, SA WG2","lsoriginalls":"R3-222610","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_150E_Electronic_2022-04\/Docs\/S2-2202786.zip","group":"S2","meeting":"S2-150-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2202791","title":"LS on 5G NSWO roaming aspects","source":"SA WG3","contact":"Noamen Ben Henda","contact-id":92684,"tdoctype":"LS in","for":"Action","abstract":"SA WG3 has conditionally agreed on the attached CR to support roaming in 5G NSWO following a request from SA WG2. SA WG3's agreement is based on the premise and the common understanding that the architectural options included in the CR do not have stage 3 impact, other than descriptive changes and references. Therefore SA WG3 kindly requests CT WG3 and CT WG4 confirmation on this and in the same time solicits any feedback from SA WG2 on the agreed CR. Action: SA WG3 kindly request SA WG2's feedback, if any, on the attached CR.","secretary_remarks":"Postponed","agenda_item_sort_order":36,"ainumber":"8.28","ainame":"Rel-17 CAT B\/C alignment CR(s) due to the work led by other 3GPP Working Groups","tdoc_agenda_sort_order":14540,"status":"postponed","reservation_date":"2022-03-29 15:34:29","uploaded":"2022-03-29 17:47:55","revisionof":"","revisedto":"S2-2203632","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, CT WG4, CT WG3","Cc":"TSG CT","lsoriginalls":"S3-220446","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_150E_Electronic_2022-04\/Docs\/S2-2202791.zip","group":"S2","meeting":"S2-150-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2202792","title":"LS from SA WG3: Reply LS on LTE User Plane Integrity Protection","source":"SA WG3","contact":"Monica Wifvesson","contact-id":13327,"tdoctype":"LS in","for":"Action","abstract":"SA WG3 thanks RAN WG3 for their LS reply on LTE User Plane Integrity Protection in S3-220039\/R3-221473. SA WG3 has the following answers to the comments and questions mentioned in the LS. RAN WG3 thanks SA WG3 for their LS in S3-214462\/R3-220128. RAN WG3 is taking this information into account (along with the CRs agreed in SA WG2, CT WG4 and CT WG1), but only to the extent that is described by the WID agreed by RAN plenary in RP-213669 which, in particular, restricts the scope to EN-DC capable UEs. [SA WG3 answer]: SA WG3 acknowledge the information that RAN plenary has restricted the scope to EN-DC capable UEs. 1) (for SA WG3) In case of handover from a UPIP supporting eNB to a UPIP non-supporting eNB, would it be acceptable to SA WG3 if occasionally some packets over bearers with UPIP policy set to 'required' are sent without integrity protection before the CN triggers the release of the bearer? [SA WG3 answer]: SA WG3 prefers to avoid it since this violates the expected security policy. 2) (for SA WG3 and SA WG2) RAN WG3 has noted the functionality difference between EPS and 5GS, e.g., when UPIP policy is 'preferred', the NG-RAN node is required to notify if the UPIP is performed or not. [SA WG3 answer]: In both EPS\/LTE and 5GS, SA WG3 currently does not have any security requirement for the RAN (eNB) to notify Core Network when UP IP policy is set to 'Preferred'. SA WG3 only requires that the DRBs for which the UP IP policy set to 'Required' is not handed over to target RAN nodes that cannot fulfil this requirement. About the following comment in the LS: With regard to the reduced scope of the RAN WID, RAN 3 would like to inform SA WG3 that they do not plan to provide specification changes to support UPIP when using LTE-LTE Dual Connectivity. [SA WG3 answer]: SA WG3 acknowledge the information that RAN WG3 does not plan to provide specification changes to support UP IP when using LTE-LTE Dual Connectivity in Rel-17 and SA WG3 will update SA WG3 specification in TS 33.401 accordingly.","secretary_remarks":"Noted","agenda_item_sort_order":36,"ainumber":"8.28","ainame":"Rel-17 CAT B\/C alignment CR(s) due to the work led by other 3GPP Working Groups","tdoc_agenda_sort_order":14550,"status":"noted","reservation_date":"2022-03-29 15:34:29","uploaded":"2022-03-29 17:47:55","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, RAN WG3","Cc":"RAN WG2, CT WG1, CT WG4","lsoriginalls":"S3-220464","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_150E_Electronic_2022-04\/Docs\/S2-2202792.zip","group":"S2","meeting":"S2-150-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2202900","title":"[DRAFT] LS out on PEI and UE Subgrouping","source":"Qualcomm Europe Inc. Sweden","contact":"Miguel Griot","contact-id":84607,"tdoctype":"LS out","for":"Approval","abstract":"Provides feedback to RAN WG2, RAN WG3 that SA WG2 made no agreement to restrict applicability of PEIPS to last cell.","secretary_remarks":"Response to S2-2201952. r04 agreed. Revised to S2-2203252","agenda_item_sort_order":36,"ainumber":"8.28","ainame":"Rel-17 CAT B\/C alignment CR(s) due to the work led by other 3GPP Working Groups","tdoc_agenda_sort_order":14210,"status":"revised","reservation_date":"2022-03-29 17:25:41","uploaded":"2022-03-29 18:42:07","revisionof":"","revisedto":"S2-2203252","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"TEI17"},{"winame":" NR_UE_pow_sav_enh-Core"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG3, RAN WG2","Cc":"CT WG1","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_150E_Electronic_2022-04\/Docs\/S2-2202900.zip","group":"S2","meeting":"S2-150-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2203252","title":"[DRAFT] LS out on PEI and UE Subgrouping","source":"Qualcomm Europe Inc. Sweden","contact":"Miguel Griot","contact-id":84607,"tdoctype":"LS out","for":"Approval","abstract":"Provides feedback to RAN WG2, RAN WG3 that SA WG2 made no agreement to restrict applicability of PEIPS to last cell.","secretary_remarks":"Revision of S2-2202900r04. Approved","agenda_item_sort_order":36,"ainumber":"8.28","ainame":"Rel-17 CAT B\/C alignment CR(s) due to the work led by other 3GPP Working Groups","tdoc_agenda_sort_order":14220,"status":"approved","reservation_date":"2022-04-13 09:53:18","uploaded":"2022-04-13 15:41:13","revisionof":"S2-2202900","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"TEI17"},{"winame":" NR_UE_pow_sav_enh-Core"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2201952","lsto":"RAN WG3, RAN WG2","Cc":"CT WG1","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_150E_Electronic_2022-04\/Docs\/S2-2203252.zip","group":"S2","meeting":"S2-150-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2203253","title":"[DRAFT] LS on 5G NSWO roaming aspects","source":"Nokia, Nokia Shanghai Bell","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"LS out","for":"Approval","abstract":"[draft] LS on 5G NSWO roaming aspects","secretary_remarks":"Revision of S2-2202178r02. Approved","agenda_item_sort_order":36,"ainumber":"8.28","ainame":"Rel-17 CAT B\/C alignment CR(s) due to the work led by other 3GPP Working Groups","tdoc_agenda_sort_order":14320,"status":"approved","reservation_date":"2022-04-13 09:53:18","uploaded":"2022-04-13 15:41:13","revisionof":"S2-2202178","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"NSWO_5G"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG3","Cc":"CT WG3, CT WG4, TSG CT","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_150E_Electronic_2022-04\/Docs\/S2-2203253.zip","group":"S2","meeting":"S2-150-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2203254","title":"23.501: NSWO and N3GPP access support","source":"Huawei, Nokia, Nokia Shanghai Bell","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The following changes are proposed 1) specify in clause 4.2.15 and in 4.30.2.0 that 5G NSWO is not applicable to SNPN. 2) addition of roaming architceture in clause 4.2.15 in both point to point reference model and SBI model 3) addition","secretary_remarks":"Revision of S2-2202677r05, merging S2-2202176. Approved","agenda_item_sort_order":36,"ainumber":"8.28","ainame":"Rel-17 CAT B\/C alignment CR(s) due to the work led by other 3GPP Working Groups","tdoc_agenda_sort_order":14450,"status":"agreed","reservation_date":"2022-04-13 09:53:18","uploaded":"2022-04-14 09:01:22","revisionof":"S2-2202677","revisedto":"S2-2204095, S2-2204437","release":"Rel-17","crspec":"23.501","crspecversion":"17.4.0","workitem":[{"winame":"NSWO_5G"}],"crnumber":3617.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_150E_Electronic_2022-04\/Docs\/S2-2203254.zip","group":"S2","meeting":"S2-150-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2203597","title":"[DRAFT] Reply LS on Slice list and priority information for cell reselection","source":"ZTE","contact":"Jinguo Zhu","contact-id":32987,"tdoctype":"LS out","for":"Approval","abstract":"To: RAN WG2. CC: RAN WG3","secretary_remarks":"Revision of S2-2202658r17 + changes, merging S2-2202228. Approved","agenda_item_sort_order":36,"ainumber":"8.28","ainame":"Rel-17 CAT B\/C alignment CR(s) due to the work led by other 3GPP Working Groups","tdoc_agenda_sort_order":14260,"status":"approved","reservation_date":"2022-04-13 09:55:41","uploaded":"2022-04-13 15:41:16","revisionof":"S2-2202658","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"NR_slice-Core"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2201947","lsto":"RAN WG2","Cc":"RAN WG3","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_150E_Electronic_2022-04\/Docs\/S2-2203597.zip","group":"S2","meeting":"S2-150-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2203598","title":"AMF relocation in connected state","source":"NEC, Nokia; Nokia Shanghai Bell., Ericsson","contact":"Kundan Tiwari","contact-id":76330,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: removal of editor's note","secretary_remarks":"Revision of S2-2202739r02 + changes. Approved","agenda_item_sort_order":36,"ainumber":"8.28","ainame":"Rel-17 CAT B\/C alignment CR(s) due to the work led by other 3GPP Working Groups","tdoc_agenda_sort_order":14530,"status":"agreed","reservation_date":"2022-04-13 09:55:41","uploaded":"2022-04-14 09:01:26","revisionof":"S2-2202739","revisedto":"","release":"Rel-17","crspec":"23.502","crspecversion":"17.4.0","workitem":[{"winame":"5GS_Ph1"},{"winame":" TEI17"}],"crnumber":3465.0,"crrevision":"","crcategory":"F","tsg_crp":"SP-220410","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_150E_Electronic_2022-04\/Docs\/S2-2203598.zip","group":"S2","meeting":"S2-150-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2203618","title":"Enabling configuration of Network Slice AS Groups","source":"Nokia, Nokia Shanghai Bell, CMCC, NEC, Verizon UK ltd, ZTE, InterDigital, Xiaomi, LGE, Samsung, AT&T, Oppo, Huawei","contact":"Alessio Casati","contact-id":82456,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Configuration of NSAGs (Network Slices AS Groups)","secretary_remarks":"Revision of S2-2202706, merging S2-2202052, S2-2202226 and S2-2202659. This CR was agreed","agenda_item_sort_order":36,"ainumber":"8.28","ainame":"Rel-17 CAT B\/C alignment CR(s) due to the work led by other 3GPP Working Groups","tdoc_agenda_sort_order":14480,"status":"agreed","reservation_date":"2022-04-13 09:55:45","uploaded":"2022-04-14 09:01:26","revisionof":"S2-2202706","revisedto":"S2-2203921, SP-220452","release":"Rel-17","crspec":"23.501","crspecversion":"17.4.0","workitem":[{"winame":"NR_slice-Core"},{"winame":" TEI17"}],"crnumber":3539.0,"crrevision":4.0,"crcategory":"B","tsg_crp":"SP-220412","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_150E_Electronic_2022-04\/Docs\/S2-2203618.zip","group":"S2","meeting":"S2-150-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2203619","title":"Enabling configuration of Network Slice AS Groups","source":"Nokia, Nokia Shanghai Bell, CMCC, NEC, Verizon UK ltd.,ZTE, InterDigital, Xiaomi, LGE, Samsung, AT&T, Oppo, Huawei","contact":"Alessio Casati","contact-id":82456,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Configuration of NSAGs (Network Slices AS Groups)","secretary_remarks":"Revision of S2-2202711, merging S2-2202053 and S2-2202227. This CR was agreed","agenda_item_sort_order":36,"ainumber":"8.28","ainame":"Rel-17 CAT B\/C alignment CR(s) due to the work led by other 3GPP Working Groups","tdoc_agenda_sort_order":14500,"status":"agreed","reservation_date":"2022-04-13 09:55:46","uploaded":"2022-04-14 09:01:26","revisionof":"S2-2202711","revisedto":"S2-2203922, SP-220453, SP-220456","release":"Rel-17","crspec":"23.502","crspecversion":"17.4.0","workitem":[{"winame":"NR_slice-Core"},{"winame":" TEI17"}],"crnumber":3300.0,"crrevision":4.0,"crcategory":"B","tsg_crp":"SP-220412","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_150E_Electronic_2022-04\/Docs\/S2-2203619.zip","group":"S2","meeting":"S2-150-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2203620","title":"Enabling slice priority and slice groups for RRM purposes","source":"Ericsson, ZTE, AT&T, China Mobile, OPPO","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Enabling the slice priorities as requested. AMF provides the network slice priorities to the UE","secretary_remarks":"Revision of S2-2202224, merging S2-2202702 and S2-2202225. This CR was agreed","agenda_item_sort_order":36,"ainumber":"8.28","ainame":"Rel-17 CAT B\/C alignment CR(s) due to the work led by other 3GPP Working Groups","tdoc_agenda_sort_order":14360,"status":"agreed","reservation_date":"2022-04-13 09:55:48","uploaded":"2022-04-14 09:01:26","revisionof":"S2-2202224","revisedto":"S2-2203923, S2-2204152, SP-220454","release":"Rel-17","crspec":"23.501","crspecversion":"17.4.0","workitem":[{"winame":"NR_slice-Core"}],"crnumber":3317.0,"crrevision":7.0,"crcategory":"B","tsg_crp":"SP-220412","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_150E_Electronic_2022-04\/Docs\/S2-2203620.zip","group":"S2","meeting":"S2-150-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]