[{"name":"S2-2200012","title":"LS on Slice list and priority information for cell reselection","source":"CT WG1","contact":"Mikael Wass","contact-id":42217,"tdoctype":"LS in","for":"Action","abstract":"CT WG1 thanks RAN WG2 for the LS on slice-based cell reselection and would like to respond to the questions asked as follows. 1. Can UE NAS provide to UE AS a list of slices (or slice group(s)), each with its corresponding priority for cell reselection evaluation in RRC_IDLE\/RRC_INACTIVE? Answer 1: CT WG1 assumes SA WG2 to agree a stage 2 solution on how a list of slices (or slice group(s)) with priorities is provided to UE NAS. Once such solution is agreed in SA WG2, CT WG1 can work on clarifying the related interaction between the NAS and AS layers. 2. Can the concept of Slice group and its signalling (Slice Group and its identifier) be supported using NAS signalling? Answer 2: CT WG1 sees no issues to introduce support in NAS to convey information on Slice groups from the network to the UE. A solution would depend on requirements outside CT WG1 area of responsibility to configure Slice group information in the network, but once stage 2 requirements are available, CT WG1 can proceed with stage 3 NAS details. Action: CT WG1 asks RAN WG2 and SA WG2 groups to take the information above into account for the further work on slice-based cell reselection.","secretary_remarks":"Revision of Postponed S2-2108280 from S2#148E. Response drafted in S2-2201030. CC#2: Moved back to Agenda item 8.28. CC#5: Final response in S2-2201859","agenda_item_sort_order":71,"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":17820,"status":"replied to","reservation_date":"2022-01-10 13:42:19","uploaded":"2022-01-10 13:44:26","revisionof":"S2-2108280","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2, SA WG2","Cc":"","lsoriginalls":"C1-216256","lsreply":"S2-2201859","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_149E_Electronic_2022-02\/Docs\/S2-2200012.zip","group":"S2","meeting":"S2-149-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2200017","title":"Reply LS on Slice list and priority information for cell reselection","source":"RAN WG2","contact":"Jiayao Tan","contact-id":90833,"tdoctype":"LS in","for":"Action","abstract":"RAN WG2 thanks SA WG2 for their reply LS on Slice list and priority information for cell reselection. RAN WG2 answers to the further questions asked by SA WG2 are below: 1. SA WG2 would like to understand from RAN WG2 perspective, whether it is possible that a network slice can be associated to none, one or more slice groups? RAN WG2 Answer: A slice can be associated to none or only one slice group. From RAN WG2 perspective, it is allowed to not associate a slice to any of the slice groups. 2. Does RAN WG2 intend to use the slice groups only for cell reselection or also for slice based RACH and if for both would RAN WG2 require different type of slice groups or is one type of slice group enough? RAN WG2 answer: RAN WG2 aims to use slice groups for both cell reselection and slice based RACH. This means slice to slice-group configuration is common to cell reselection and RACH. Configuration of whether to use slice-specific cell reselection or slice specific RACH is up to network configuration (i.e. some slice groups may use cell reselection but not RACH, some may use RACH but not cell reselection, some may use both). 3. What are the granularities of the slice groups for cell reselection, i.e. per TA or PLMN? RAN WG2 answer: RAN WG2 understanding is that the granularities of the slice groups are per TA but RAN WG2 details are FFS. 4. With regards to the logic of network slice priority for cell reselection; SA WG2 wonder if the UE NAS prioritization should consider network slice registration status (i.e. selecting among registered network slices from the Allowed NSSAI or also not yet registered network slices? RAN WG2 answer: RAN WG2 understands it is up to SA WG2\/CT WG1 whether to consider the slice registration status. From RAN WG2 perspective, both registered slices and not yet registered slices can be considered for the slice priority. Furthermore, RAN WG2 confirms the following understanding and expects SA WG2, RAN WG3 and CT WG1 to take into account for future work: - Mapping between slice and slice group should be consistent between serving cell and UE, in order to avoid misunderstanding of system information. Action: RAN WG2 kindly asks SA WG2, RAN WG3 and CT WG1 to take the above information into consideration.","secretary_remarks":"Revision of Postponed S2-2108996 from S2#148E. Response drafted in S2-2201030. CC#2: Moved back to Agenda item 8.28. CC#5: Final response in S2-2201859","agenda_item_sort_order":71,"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":17830,"status":"replied to","reservation_date":"2022-01-10 13:42:20","uploaded":"2022-01-10 13:44:26","revisionof":"S2-2108996","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG3, SA WG2","Cc":"CT WG1","lsoriginalls":"R2-2111310","lsreply":"S2-2201859","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_149E_Electronic_2022-02\/Docs\/S2-2200017.zip","group":"S2","meeting":"S2-149-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2200026","title":"LS from RAN WG3: LS on Clarification of SCG outside RA for slicing","source":"RAN WG3","contact":"Philippe Godin","contact-id":68843,"tdoctype":"LS in","for":"Action","abstract":"RAN WG3 is discussing a solution for resource optimisation for a slice 1 in a gNB cell called Multi Carrier Resource Sharing solution. This solution assumes that the gNB hosts another cell with different frequency and overlapping coverage where the same slice 1 is available. It consists of setting up DC using SCG resources on the 'other cell' for offloading the PDU sessions of slice 1 of some or all UEs. RAN WG3 is not sure if gNB can select such 'other cell' outside of the RA (registration area) of the concerned UE as SCG resource (i.e. the secondary cell group in Dual Connectivity.). Action: RAN WG3 kindly ask SA WG2 to provide feedback on the question above and if yes, how to address it.","secretary_remarks":"Revision of Postponed S2-2109012 from S2#148E. Responses drafted in S2-2200507, S2-2200523 and S2-2200846. Final response in S2-2201549","agenda_item_sort_order":71,"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":17710,"status":"replied to","reservation_date":"2022-01-10 13:42:21","uploaded":"2022-01-10 13:44:26","revisionof":"S2-2109012","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"","lsoriginalls":"R3-216237","lsreply":"S2-2201549","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_149E_Electronic_2022-02\/Docs\/S2-2200026.zip","group":"S2","meeting":"S2-149-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2200032","title":"LS from RAN WG2: LS on paging subgrouping and PEI","source":"RAN WG2","contact":"Yanhua Li","contact-id":76945,"tdoctype":"LS in","for":"Action","abstract":"RAN WG2 discussed UE paging subgrouping as part of the Rel-17 work on UE power saving enhancement (see RP-200938). On paging subgrouping, the following provides the detailed agreements for the 2 approaches (CN-assigned subgrouping and UE ID-based subgrouping): \u00de Assume that one subgroup indication refers to either CN-assigned subgroups or UE ID-based subgroup (no overlapping) \u00de Both UE ID-based and CN-assigned subgrouping can be supported simultaneously in a cell, it is allowed to just support one of them. \u00de The total number of CN-assigned subgroups that is used is not fixed and can be configured up to 8 (e.g. by OAM). No impact on signalling is assumed. \u00de RAN introduces a new parameter Nsg-UEID to indicate its support of UE ID-based subgrouping. \u00de RAN does not support any type of subgrouping if its configuration for subgrouping is either absent or nullified (e.g. subgroupsNumPerPO is either absent or set to zero). FFS for the signalling details. \u00de We assume separate indications for UE capability of CN-assigned subgrouping and UE ID-based subgrouping. \u00de UE's capability of supporting the UE ID-based subgrouping is reported to RAN by AS UE capability signalling while R2 assumes that UE's capability of supporting the CN-assigned subgrouping is reported to CN by NAS signalling. RAN WG2 also discussed the Paging Early Indication, and agreed to the following: \u00de RAN WG2 assumes that if PEI is detected, and the PEI indicates that the UE has to monitor the associated PO, then the UE monitors paging DCI in the associated PO, including scheduling information for paging PDSCH (if included) as in legacy. This assumption may be updated based on RAN WG1 agreements. \u00de As a baseline RAN WG2 has a preference to support PEI with both DRX and eDRX, but potential issues (e.g. PEI and PTW) are FFS. \u00de For UE ID-based subgroups the UE identity is UE_ID = 5G-S-TMSI mod X, where X is 8192 (1024*8). \u00de Introduce a UERadioPagingInfo IE in the UECapabilityInformation message in NR in Rel-17. \u00de If the UE was not able to monitor the PEI occasion corresponding to its PO, the UE shall monitor the PO. Actions: To SA WG2 and CT WG1: RAN WG2 respectfully asks SA WG2 and CT WG1 to take the above information into account for their future work, and provide further information on the following issue once concluded: - NAS signalling between AMF and UE to convey the related information to the UE, e.g., UE's capability reporting by NAS.","secretary_remarks":"Revision of Postponed S2-2109371 from S2#148E. Postponed","agenda_item_sort_order":71,"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":17950,"status":"postponed","reservation_date":"2022-01-10 13:42:22","uploaded":"2022-01-10 13:44:25","revisionof":"S2-2109371","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, CT WG1, RAN WG3, RAN WG1","Cc":"","lsoriginalls":"R2-2111415","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_149E_Electronic_2022-02\/Docs\/S2-2200032.zip","group":"S2","meeting":"S2-149-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2200042","title":"LS on access to multiple IMS networks via a 5GC network slice","source":"CT WG1","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Action","abstract":"CT WG1 has been performing study on enhanced IMS to 5GC integration. Within the study a scenario depicted in the figure below was discussed (the figure is copied from 3GPP TR 23.700-10). In the scenario, a 5GC network slice provides access to a different IMS network for each of two UEs. Figure 5.1-5: Two UEs connect to separate IMS network through one common 5GC network slice To be more specific, CT WG1 investigated how an SMF in the 5GC network slice can discover an appropriate P-CSCF (in the figure above, for UE#1 and UE#2, an SMF in 5GC Slice #1 should select a P-CSCF in IMS network#1 and IMS network#2, respectively). Two solutions were incorporated in 3GPP TR 23.700-10: - Solution 2 (see clause 6.2 of the TR) proposes that a UE provides IMS network domain information during the establishment of an IMS PDU session. It is assumed that IMS network#1 and IMS network#2 are associated with the same DNN. - Solution 4 (see clause 6.4 of the TR) proposes that if multiple IMS networks can be accessed by a 5GC network slice, an IMS DNN needs to include information identifying the corresponding IMS network similar to clause AB.1.2.3 of 3GPP TS 23.228. Action: CT WG1 kindly asks SA WG2 to provide feedback on the solutions above. If SA WG2 has other comments on the P-CSCF discovery in the scenario described above, please include them also.","secretary_remarks":"Response drafted in S2-2200129. Postponed","agenda_item_sort_order":71,"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":17620,"status":"postponed","reservation_date":"2022-01-10 14:20:56","uploaded":"2022-01-10 16:05:25","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"CT WG4","lsoriginalls":"C1-216839","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_149E_Electronic_2022-02\/Docs\/S2-2200042.zip","group":"S2","meeting":"S2-149-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2200058","title":"LS from CT WG4: LS on Deletion of ME support of SOR-CMCI indicator during Nudm_SDM_Get","source":"CT WG4","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Action","abstract":"CT WG4 is carrying out work to support SOR-CMCI in CT WG4 specifications. CT WG4 has noticed following in 3GPP TS 23.122 v17.4.0, Annex C.2: Step #2 & 3a state: 2) Upon receiving REGISTRATION REQUEST message, the VPLMN AMF executes the registration procedure as defined in clause 4.2.2.2.2 of 3GPP TS 23.502 [63]. As part of the registration procedure: \u2026 \u2026 then the VPLMN AMF invokes Nudm_SDM_Get service operation message to the HPLMN UDM to retrieve the steering of roaming information (see step 14b in clause 4.2.2.2.2 of 3GPP TS 23.502 [63]); \u2026 3a) If the user subscription information indicates to send the steering of roaming information due to initial registration in a VPLMN, then the HPLMN UDM shall provide the steering of roaming information to the UE when the UE performs initial registration in a VPLMN, otherwise the HPLMN UDM may provide the steering of roaming information to the UE, based on operator policy. If the UE is performing initial registration or emergency registration, the HPLMN UDM shall delete the stored 'ME support of SOR-CMCI' indicator, if any. \u2026 \u2026 Question 1: CT WG4 would like to highlight that Nudm_SDM_Get is a read-only operation on UDM, and should not cause changes to server state. Hence, CT WG4 would like to request CT WG1 to explore if the deletion of 'ME support of SOR-CMCI' indicator during initial\/emergency registrations can be performed via some alternate procedures (e.g. before\/after Nudm_SDM_Get) instead, or an alternative that does not require deletion of 'ME support of CMCI' indicator upon specific registration types by the UE. Question 2: CT WG4 has discussed the possibility of using any information provided in Nudm_UECM_Registration operation to be used for influencing the steering of roaming related information, however was not sure if Nudm_UECM_Registration operation always completes prior to Nudm_SDM_Get operation during UE's initial registration. Action: CT WG4 kindly asks SA WG2 to provide response on Question 2 above as to whether Nudm_UECM_Registration operation always completes prior to Nudm_SDM_Get operation during UE's initial registration.","secretary_remarks":"Responses drafted in S2-2201013 and S2-2201143. Final response in S2-2201553","agenda_item_sort_order":71,"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":18040,"status":"replied to","reservation_date":"2022-01-10 14:20:57","uploaded":"2022-01-10 16:05:25","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1, SA WG2","Cc":"","lsoriginalls":"C4-216607","lsreply":"S2-2201553","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_149E_Electronic_2022-02\/Docs\/S2-2200058.zip","group":"S2","meeting":"S2-149-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2200081","title":"LS from CT WG1: LS on Deletion of ME support of SOR-CMCI indicator during Nudm_SDM_Get","source":"CT WG1","contact":"Ban Al-Bakri","contact-id":64347,"tdoctype":"LS in","for":"Action","abstract":"CT WG1 thanks CT WG4 for the LS in C4-216607\/C1-220090 on Deletion of 'ME support of SOR-CMCI' indicator during Nudm_SDM_Get. CT WG1 provides the following answer to Q1: Question 1: CT WG4 would like to highlight that Nudm_SDM_Get is a read-only operation on UDM, and should not cause changes to server state. Hence, CT WG4 would like to request CT WG1 to explore if the deletion of 'ME support of SOR-CMCI' indicator during initial\/emergency registrations can be performed via some alternate procedures (e.g. before\/after Nudm_SDM_Get) instead, or an alternative that does not require deletion of 'ME support of CMCI' indicator upon specific registration types by the UE. CT WG1 answer to Q1: It should be possible for the AMF to provide the registration type to the UDM using Nudm_UECM_Registration service operation when a registration request is performed by the UE. As a consequence, the UDM updates the UDR using the Nudr_DM_Update service operation (see TS23.502). In the case of initial registration and emergency registration, the UDR shall delete the stored 'ME support of SOR-CMCI' indicator, if any. Therefore, it is required that the AMF provides the UDM with the registration type for every 'initial registration ' and 'emergency registration'. CT WG1 has agreed the CR in C1-220558 that implements this solution. CT WG1 notices that the current TS23.502 and TS 29.503 allow only to indicate 'initial registration' over the Nudm_UECM_Registration service operation, where there is a need to indicate 'emergency registration' as well. Therefore CT WG1 kindly asks SA WG2 and CT WG4 to update the spec to allow the 'emergency registration' to be provided over the Nudm_UECM_Registration service operation, and make it mandatory for the AMF to provide the UDM with the 'initial registration' and the 'emergency registration'. CT WG1 kindly asks SA WG2 and CT WG4 to confirm if the solution agreed in C1-220558 is acceptable. Action: - CT WG1 kindly asks SA WG2 and CT WG4 to confirm if the solution agreed in C1-220558 is acceptable. - CT WG1 kindly asks SA WG2 and CT WG4 to update the spec to allow the 'emergency registration' to be provided over the Nudm_UECM_Registration service operation, and make it mandatory for the AMF to provide the UDM with the 'initial registration' and the 'emergency registration'.","secretary_remarks":"Responses drafted in S2-2201013 and S2-2201143. Final response in S2-2201553","agenda_item_sort_order":71,"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":18010,"status":"replied to","reservation_date":"2022-01-10 14:20:57","uploaded":"2022-01-25 15:36:02","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG4, SA WG2","Cc":"","lsoriginalls":"C1-220559","lsreply":"S2-2201553","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_149E_Electronic_2022-02\/Docs\/S2-2200081.zip","group":"S2","meeting":"S2-149-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2200082","title":"LS from CT WG1: LS on progress of FS_eIMS5G2","source":"CT WG1","contact":"haitao Wei","contact-id":48249,"tdoctype":"LS in","for":"Action","abstract":"CT WG1, CT WG3 and CT WG4 are carrying out work of FS_eIMS5G2. From the perspective of CT WG1, we reached conclusions for key issue 1 of TR 23.700-10 as follows: - providing 'IMS home network domain name' in the traffic descriptor and Solution 4 will be the basis for work in the normative phase. Action: CT WG1 kindly asks SA WG2 to complete the normative work on solutions above.","secretary_remarks":"Postponed","agenda_item_sort_order":71,"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":17640,"status":"postponed","reservation_date":"2022-01-10 14:20:57","uploaded":"2022-01-25 15:36:02","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"CT WG4, CT WG3","lsoriginalls":"C1-220734","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_149E_Electronic_2022-02\/Docs\/S2-2200082.zip","group":"S2","meeting":"S2-149-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2200129","title":"[DRAFT] Reply LS on access to multiple IMS networks via a 5GC network slice","source":"China Mobile","contact":"Yi Jiang","contact-id":40863,"tdoctype":"LS out","for":"Approval","abstract":"Reply LS to CT WG1 LS on access to multiple IMS networks via a 5GC network slice","secretary_remarks":"Response to S2-2200042. Noted","agenda_item_sort_order":71,"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":17630,"status":"noted","reservation_date":"2022-01-25 04:39:50","uploaded":"2022-01-28 14:21:04","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"CT WG4","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_149E_Electronic_2022-02\/Docs\/S2-2200129.zip","group":"S2","meeting":"S2-149-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2200204","title":"LS from CT WG4: LS on progress of FS_eIMS5G2","source":"CT WG4","contact":"haitao Wei","contact-id":48249,"tdoctype":"LS in","for":"Action","abstract":"CT WG1, CT WG3 and CT WG4 are carrying out work of FS_eIMS5G2. From the perspective of CT WG4, we reached conclusions for key issue 1 of TR 23.700-12 as follows: - It is recommended to adopt solution#1 (Conveying UPF FQDN to IMS nodes) as basis for normat","secretary_remarks":"Response drafted in S2-2200324. Final response in S2-2201548","agenda_item_sort_order":71,"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":17650,"status":"replied to","reservation_date":"2022-01-25 15:00:46","uploaded":"2022-01-25 15:11:10","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"CT WG1, CT WG3","lsoriginalls":"C4-220445","lsreply":"S2-2201548","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_149E_Electronic_2022-02\/Docs\/S2-2200204.zip","group":"S2","meeting":"S2-149-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2200277","title":"Remove the EN on UPIP for EPS","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Delete the EN related to SA WG3 and change the EN on UE capability to a note.","secretary_remarks":"WI Code should be UPIP_SEC_LTE. r01 agreed. Revised to S2-2201550.","agenda_item_sort_order":71,"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":17910,"status":"revised","reservation_date":"2022-01-26 13:33:19","uploaded":"2022-01-28 12:22:22","revisionof":"","revisedto":"S2-2201550","release":"Rel-17","crspec":"23.401","crspecversion":"17.3.0","workitem":[{"winame":"UPIP_SEC_LTE"}],"crnumber":3680.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_149E_Electronic_2022-02\/Docs\/S2-2200277.zip","group":"S2","meeting":"S2-149-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2200278","title":"Correction on the MME handling for UPIP during interworking","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Correct the above description to focus on the EPS bearer.","secretary_remarks":"r03 agreed. Revised to S2-2201551.","agenda_item_sort_order":71,"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":17930,"status":"revised","reservation_date":"2022-01-26 13:33:20","uploaded":"2022-01-28 12:22:22","revisionof":"","revisedto":"S2-2201551","release":"Rel-17","crspec":"23.501","crspecversion":"17.3.0","workitem":[{"winame":"UPIP_SEC_LTE"}],"crnumber":3481.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_149E_Electronic_2022-02\/Docs\/S2-2200278.zip","group":"S2","meeting":"S2-149-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2200279","title":"Discussion on Slice Group and slice priority.","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"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":71,"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":17800,"status":"noted","reservation_date":"2022-01-26 13:33:21","uploaded":"2022-01-28 12:23:29","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_149E_Electronic_2022-02\/Docs\/S2-2200279.zip","group":"S2","meeting":"S2-149-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2200280","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 Slice Groups and slice priorities as requested.","secretary_remarks":"WI Code should be NR_slice-Core. CC#2: Moved back to Agenda item 8.28 for further discussion. CC#4: This CR was postponed","agenda_item_sort_order":71,"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":17890,"status":"postponed","reservation_date":"2022-01-26 13:33:21","uploaded":"2022-01-28 12:23:29","revisionof":"","revisedto":"","release":"Rel-17","crspec":"23.501","crspecversion":"17.3.0","workitem":[{"winame":"NR_slice-Core"}],"crnumber":3482.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_149E_Electronic_2022-02\/Docs\/S2-2200280.zip","group":"S2","meeting":"S2-149-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2200281","title":"Enabling Network Slice Acess stratum group","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Enabling the Slice Groups and slice priorities as requested.","secretary_remarks":"CC#2: Moved back to Agenda item 8.28 for further discussion. CC#4: This CR was postponed","agenda_item_sort_order":71,"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":17900,"status":"postponed","reservation_date":"2022-01-26 13:33:22","uploaded":"2022-01-28 12:23:29","revisionof":"","revisedto":"","release":"Rel-17","crspec":"23.502","crspecversion":"17.3.0","workitem":[{"winame":"NR_slice-Core"}],"crnumber":3334.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_149E_Electronic_2022-02\/Docs\/S2-2200281.zip","group":"S2","meeting":"S2-149-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2200321","title":"Conveying UPF FQDN to IMS nodes","source":"Nokia, Nokia Shanghai-Bell","contact":"Thomas Belling","contact-id":68266,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: As required for concluded solution 1 in the FS_eIMS5G2 study for key issue 1, the UDM DM service is extended with a UPF identity parameter.","secretary_remarks":"Noted","agenda_item_sort_order":71,"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":17690,"status":"noted","reservation_date":"2022-01-26 20:23:01","uploaded":"2022-01-28 21:19:21","revisionof":"","revisedto":"","release":"Rel-17","crspec":"23.502","crspecversion":"17.3.0","workitem":[{"winame":"TEI17"}],"crnumber":3342.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_149E_Electronic_2022-02\/Docs\/S2-2200321.zip","group":"S2","meeting":"S2-149-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2200323","title":"Routing of IMS traffic via localized IMS media plane functions","source":"Nokia, Nokia Shanghai-Bell","contact":"Thomas Belling","contact-id":68266,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The concluded solutions in the FS_eIMS5G2 study for key issue 1, Solutions #1 (Conveying UPF FQDN to IMS nodes) and solution #4 ('Conveying UPF service area to IMS nodes via PCF N5') are added.","secretary_remarks":"Noted","agenda_item_sort_order":71,"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":17700,"status":"noted","reservation_date":"2022-01-26 20:38:07","uploaded":"2022-01-28 21:19:21","revisionof":"","revisedto":"","release":"Rel-17","crspec":"23.228","crspecversion":"17.3.0","workitem":[{"winame":"TEI17"}],"crnumber":1256.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_149E_Electronic_2022-02\/Docs\/S2-2200323.zip","group":"S2","meeting":"S2-149-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2200324","title":"[DRAFT] Reply LS on progress of FS_eIMS5G2","source":"Nokia, Nokia Shanghai-Bell","contact":"Thomas Belling","contact-id":68266,"tdoctype":"LS out","for":"Approval","abstract":"SA WG2 informs CT WG4 that SA WG2 has agreed CRs to add Solutions #1 and #4, as requested by incoming LS S2-2200204 and concluded in the FS_eIMS5G2 study for key issue 1 (see TR 23.700-12)","secretary_remarks":"Response to S2-2200204. r02 agreed. Revised to S2-2201548.","agenda_item_sort_order":71,"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":17660,"status":"revised","reservation_date":"2022-01-26 20:48:19","uploaded":"2022-01-28 21:19:21","revisionof":"","revisedto":"S2-2201548","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"TEI17"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG4","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_149E_Electronic_2022-02\/Docs\/S2-2200324.zip","group":"S2","meeting":"S2-149-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2200338","title":"Number of CN paging subgroups","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Adding the description of configuring up to 8 CN subgroups Terminology alignment. Reference clause correction. Adding N2 procedure and reference.","secretary_remarks":"Approved","agenda_item_sort_order":71,"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":18090,"status":"agreed","reservation_date":"2022-01-26 21:22:32","uploaded":"2022-01-28 20:48:14","revisionof":"","revisedto":"","release":"Rel-17","crspec":"23.501","crspecversion":"17.3.0","workitem":[{"winame":"TEI17"},{"winame":" NR_UE_pow_sav_enh-Core"}],"crnumber":3491.0,"crrevision":"","crcategory":"F","tsg_crp":"SP-220066","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_149E_Electronic_2022-02\/Docs\/S2-2200338.zip","group":"S2","meeting":"S2-149-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2200339","title":"Clarification on rerouted Registration Request message","source":"Ericsson, Huawei, HiSilicon, NEC","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Adding clarificaiton on the re-routed Registration Request message between AMFs for rerouting possibilities.","secretary_remarks":"Revision of (Technically endorsed) S2-2108374 from S2#148E. r02 agreed. Revised to S2-2201477. CC#2: Moved to 8.28. r02 agreed","agenda_item_sort_order":71,"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":18110,"status":"revised","reservation_date":"2022-01-26 21:22:34","uploaded":"2022-01-28 20:48:14","revisionof":"S2-2108374","revisedto":"S2-2201477","release":"Rel-17","crspec":"23.502","crspecversion":"17.3.0","workitem":[{"winame":"TEI17"},{"winame":" 5GS_Ph1"}],"crnumber":3150.0,"crrevision":3.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_149E_Electronic_2022-02\/Docs\/S2-2200339.zip","group":"S2","meeting":"S2-149-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2200378","title":"Support slice group for cell re-selection","source":"Samsung","contact":"Dongeun Suh","contact-id":84836,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: -The AMF configures the RAN with the network slice group per TA. -The AMF may provide a UE, for S-NSSAIs, network slice group information -The AMF or NSSF takes the S-NSSAIs supported per TA in 5G-AN into account to determine NSAG(s) and its associated S-NSSAI(s).","secretary_remarks":"Merged intoS2-2200847 Postponed). Postponed","agenda_item_sort_order":71,"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":17770,"status":"postponed","reservation_date":"2022-01-27 11:54:24","uploaded":"2022-01-28 08:14:13","revisionof":"","revisedto":"","release":"Rel-17","crspec":"23.501","crspecversion":"17.3.0","workitem":[{"winame":"eNS_Ph2"}],"crnumber":3494.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_149E_Electronic_2022-02\/Docs\/S2-2200378.zip","group":"S2","meeting":"S2-149-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2200379","title":"Support slice group for cell re-selection","source":"Samsung","contact":"Dongeun Suh","contact-id":84836,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: -The AMF configures the RAN with the network slice group per TA. -The AMF may provide a UE, for S-NSSAIs, network slice group information -The AMF or NSSF takes the S-NSSAIs supported per TA in 5G-AN into account to determine NSAG(s) and its associated S-NSSAI(s).","secretary_remarks":"Merged into S2-2201297","agenda_item_sort_order":71,"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":17780,"status":"merged","reservation_date":"2022-01-27 12:01:46","uploaded":"2022-01-28 08:14:13","revisionof":"","revisedto":"","release":"Rel-17","crspec":"23.502","crspecversion":"17.3.0","workitem":[{"winame":"eNS_Ph2"}],"crnumber":3348.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_149E_Electronic_2022-02\/Docs\/S2-2200379.zip","group":"S2","meeting":"S2-149-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2200507","title":"[DRAFT] Reply LS on Clarification of SCG outside RA for slicing","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"LS out","for":"Approval","abstract":"Answering RAN WG3 question whether gNB can select a cell outside of RA","secretary_remarks":"Response to S2-2200026. r02 agreed. Revised to S2-2201549, merging S2-2200771 and S2-2200523","agenda_item_sort_order":71,"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":17720,"status":"revised","reservation_date":"2022-01-27 20:17:59","uploaded":"2022-01-28 20:55:44","revisionof":"","revisedto":"S2-2201549","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"NR_slice"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG3","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_149E_Electronic_2022-02\/Docs\/S2-2200507.zip","group":"S2","meeting":"S2-149-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2200508","title":"Enabling slice priority and slice groups for RRM purposes","source":"Ericsson, China Mobile","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Enabling the Slice Groups and slice priorities as requested.","secretary_remarks":"Revision of (Noted) S2-2108471 from S2#148E. CC#2: Moved back to Agenda item 8.28 for further discussion. CC#4: This CR was postponed","agenda_item_sort_order":71,"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":17860,"status":"postponed","reservation_date":"2022-01-27 20:17:59","uploaded":"2022-01-28 20:55:44","revisionof":"S2-2108471","revisedto":"","release":"Rel-17","crspec":"23.501","crspecversion":"17.3.0","workitem":[{"winame":"NR_slice-Core"}],"crnumber":3317.0,"crrevision":2.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_149E_Electronic_2022-02\/Docs\/S2-2200508.zip","group":"S2","meeting":"S2-149-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2200523","title":"[Draft] LS reply on Clarification of SCG outside RA for slicing","source":"QUALCOMM Europe Inc. - Italy","contact":"Stefano Faccin","contact-id":57487,"tdoctype":"LS out","for":"Approval","abstract":"To: RAN WG3","secretary_remarks":"Response to S2-2200026. Merged into S2-2201549","agenda_item_sort_order":71,"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":17740,"status":"merged","reservation_date":"2022-01-27 23:01:19","uploaded":"2022-01-28 21:06:01","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG3","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_149E_Electronic_2022-02\/Docs\/S2-2200523.zip","group":"S2","meeting":"S2-149-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2200719","title":"Support of slice priority and slice group information for cell (re)selection","source":"China Mobile, Ericsson","contact":"Dan Wang","contact-id":87155,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add description about AMF provide NSASGs for one or multiple S-NSSAIs in Configured NSSAI to UE NSASGs of Configured NSSAI update in UCU procedure","secretary_remarks":"Revision of (Noted) S2-2108798 from S2#148E. Merged into S2-2201372","agenda_item_sort_order":71,"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":17810,"status":"merged","reservation_date":"2022-01-28 09:07:03","uploaded":"2022-01-28 12:21:41","revisionof":"S2-2108798","revisedto":"","release":"Rel-17","crspec":"23.502","crspecversion":"17.3.0","workitem":[{"winame":"NR_slice-Core"}],"crnumber":3194.0,"crrevision":2.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_149E_Electronic_2022-02\/Docs\/S2-2200719.zip","group":"S2","meeting":"S2-149-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2200846","title":"[DRAFT] Reply LS on Clarification of SCG outside RA for slicing","source":"Nokia, Nokia Shanghai Bell","contact":"Alessio Casati","contact-id":82456,"tdoctype":"LS out","for":"Approval","abstract":"To: RAN WG3","secretary_remarks":"Response to S2-2200026. Merged into S2-2201335","agenda_item_sort_order":71,"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":17750,"status":"merged","reservation_date":"2022-01-28 11:25:13","uploaded":"2022-01-28 12:13:12","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG3","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_149E_Electronic_2022-02\/Docs\/S2-2200846.zip","group":"S2","meeting":"S2-149-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2200847","title":"Enabling configuration of Network Slice AS Groups","source":"Nokia, Nokia Shanghai Bell","contact":"Alessio Casati","contact-id":82456,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Configuration of NSAGs (Network Slices AS Groups)","secretary_remarks":"CC#2: Moved back to Agenda item 8.28 for further discussion. CC#4: This CR was postponed","agenda_item_sort_order":71,"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":17870,"status":"postponed","reservation_date":"2022-01-28 11:28:46","uploaded":"2022-01-28 12:13:12","revisionof":"","revisedto":"","release":"Rel-17","crspec":"23.501","crspecversion":"17.3.0","workitem":[{"winame":"eNS_Ph2"}],"crnumber":3539.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_149E_Electronic_2022-02\/Docs\/S2-2200847.zip","group":"S2","meeting":"S2-149-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2200906","title":"Providing IMS home network domain name information in URSP","source":"China Mobile","contact":"Yi Jiang","contact-id":40863,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: A new traffic descriptor 'IMS home network domain name' is defined.","secretary_remarks":"Postponed","agenda_item_sort_order":71,"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":17680,"status":"postponed","reservation_date":"2022-01-28 11:57:33","uploaded":"2022-01-28 14:21:04","revisionof":"","revisedto":"","release":"Rel-17","crspec":"23.503","crspecversion":"17.3.0","workitem":[{"winame":"eIMS5G_SBA"},{"winame":" FS_eIMS5G2"}],"crnumber":700.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_149E_Electronic_2022-02\/Docs\/S2-2200906.zip","group":"S2","meeting":"S2-149-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2200918","title":"Enabling configuration of Network Slice AS Groups","source":"Nokia, Nokia Shanghai Bell","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 (Noted) S2-2108866 from S2#148E. CC#2: Moved back to Agenda item 8.28 for further discussion. CC#4: This CR was postponed","agenda_item_sort_order":71,"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":17880,"status":"postponed","reservation_date":"2022-01-28 12:00:21","uploaded":"2022-01-28 12:13:12","revisionof":"S2-2108866","revisedto":"","release":"Rel-17","crspec":"23.502","crspecversion":"17.3.0","workitem":[{"winame":"eNS_Ph2"}],"crnumber":3300.0,"crrevision":1.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_149E_Electronic_2022-02\/Docs\/S2-2200918.zip","group":"S2","meeting":"S2-149-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2200998","title":"Registration type to the UDM for SoR","source":"NTT DOCOMO","contact":"Malla Reddy Sama","contact-id":48655,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Proposed that AMF shall provide the initial registration and emergency registration information to the UDM, so that the UDM updates the UDR.","secretary_remarks":"Source to WG incorrect!. r02 agreed. Revised to S2-2201554, merging S2-2200999","agenda_item_sort_order":71,"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":18070,"status":"revised","reservation_date":"2022-01-28 14:02:33","uploaded":"2022-01-28 16:12:03","revisionof":"","revisedto":"S2-2201554","release":"Rel-17","crspec":"23.502","crspecversion":"17.3.0","workitem":[{"winame":"TEI17"}],"crnumber":3402.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_149E_Electronic_2022-02\/Docs\/S2-2200998.zip","group":"S2","meeting":"S2-149-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2201013","title":"[DRAFT] LS Reply on Deletion of ME support of SOR-CMCI indicator during Nudm_SDM_Get","source":"NTT DOCOMO","contact":"Malla Reddy Sama","contact-id":48655,"tdoctype":"LS out","for":"Approval","abstract":"Incoming LS response to S2-2200081 and S2-2200058","secretary_remarks":"Response to S2-2200081 and S2-2200058. r01 agreed. Revised to S2-2201553, merging S2-2201249","agenda_item_sort_order":71,"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":18050,"status":"revised","reservation_date":"2022-01-28 14:13:54","uploaded":"2022-01-28 16:12:03","revisionof":"","revisedto":"S2-2201553","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"TEI17"},{"winame":" eCPSOR_CON"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1, CT WG4","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_149E_Electronic_2022-02\/Docs\/S2-2201013.zip","group":"S2","meeting":"S2-149-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2201030","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, RAN WG3. CC: CT WG1","secretary_remarks":"Response to S2-2200017 and S2-2200012. CC#2: Moved back to Agenda item 8.28 for further discussion. CC#4: postponed for further discussion for CC#5. CC#5: r17 agreed. Revised to S2-2201859.","agenda_item_sort_order":71,"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":17840,"status":"revised","reservation_date":"2022-01-28 14:17:45","uploaded":"2022-01-28 15:11:22","revisionof":"","revisedto":"S2-2201859","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"NR_slice-Core"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2, RAN WG3","Cc":"CT WG1","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_149E_Electronic_2022-02\/Docs\/S2-2201030.zip","group":"S2","meeting":"S2-149-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2201075","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":71,"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":17790,"status":"noted","reservation_date":"2022-01-28 14:28:40","uploaded":"2022-02-01 16:18:40","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_149E_Electronic_2022-02\/Docs\/S2-2201075.zip","group":"S2","meeting":"S2-149-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2201085","title":"Discussion paper related to draft reply LS in S2-2200846.","source":"Nokia, Nokia Shanghai-Bell","contact":"Alessio Casati","contact-id":82456,"tdoctype":"discussion","for":"Agreement","abstract":"This contribution is related to draft reply LS in S2-2200846.","secretary_remarks":"Noted","agenda_item_sort_order":71,"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":17760,"status":"noted","reservation_date":"2022-01-28 14:52:22","uploaded":"2022-01-28 14:55:37","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_149E_Electronic_2022-02\/Docs\/S2-2201085.zip","group":"S2","meeting":"S2-149-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2201138","title":"Nudm_UECM_Registration to delete the 'ME support of SOR-CMCI' indicator","source":"Samsung","contact":"Lalith Kumar","contact-id":80547,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Nudm_UECM_Registration is used to indicate the registration type in response to which UDM will delete 'ME support of SOR-CMCI' indicator","secretary_remarks":"Merged into S2-2201803","agenda_item_sort_order":71,"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":18030,"status":"merged","reservation_date":"2022-01-28 16:30:46","uploaded":"2022-01-28 16:44:27","revisionof":"","revisedto":"","release":"Rel-17","crspec":"23.502","crspecversion":"17.3.0","workitem":[{"winame":"TEI17"}],"crnumber":3415.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_149E_Electronic_2022-02\/Docs\/S2-2201138.zip","group":"S2","meeting":"S2-149-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2201143","title":"[DRAFT] Reply LS on Deletion of 'ME support of SOR-CMCI' indicator during Nudm_SDM_Get","source":"Samsung","contact":"Lalith Kumar","contact-id":80547,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG1, CT WG4","secretary_remarks":"Response to S2-2200081 and S2-2200058. Merged into S2-2201588","agenda_item_sort_order":71,"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":18020,"status":"merged","reservation_date":"2022-01-28 16:37:21","uploaded":"2022-01-28 16:44:27","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1, CT WG4","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_149E_Electronic_2022-02\/Docs\/S2-2201143.zip","group":"S2","meeting":"S2-149-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2201187","title":"UE assistance information in NAS needed to avoid PEI increasing power consumption of OTHER UEs","source":"VODAFONE","contact":"Chris Pudney","contact-id":1122,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Use NAS signalling to report MT event and MT VoNR probability, and mobility information to the AMF.","secretary_remarks":"Merged into S2-2201345","agenda_item_sort_order":71,"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":17960,"status":"merged","reservation_date":"2022-01-28 18:45:26","uploaded":"2022-01-28 18:53:57","revisionof":"","revisedto":"","release":"Rel-17","crspec":"23.501","crspecversion":"17.3.0","workitem":[{"winame":"NR_UE_pow_sav_enh-Core"}],"crnumber":3576.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_149E_Electronic_2022-02\/Docs\/S2-2201187.zip","group":"S2","meeting":"S2-149-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2201204","title":"Paging Early Indication: Removal of Editor's notes","source":"Qualcomm Incorporated","contact":"Miguel Griot","contact-id":84607,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Modify first editor's note with a note: If a gNB is using Paging subgrouping based on the UE's temporary ID, it is recommended that AMF paging strategies take into consideration that paging messages sent to that gNB for other UEs that support Paging Subgrouping based on the UE's temporary ID can increase, UE power consumption Remove second editor's note.","secretary_remarks":"CC#4: r07 + changes agreed. Revised to S2-2201846.","agenda_item_sort_order":71,"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":17970,"status":"revised","reservation_date":"2022-01-28 19:36:46","uploaded":"2022-01-28 20:17:56","revisionof":"","revisedto":"S2-2201846","release":"Rel-17","crspec":"23.501","crspecversion":"17.3.0","workitem":[{"winame":"NR_UE_pow_sav_enh"},{"winame":" TEI17"}],"crnumber":3578.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_149E_Electronic_2022-02\/Docs\/S2-2201204.zip","group":"S2","meeting":"S2-149-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2201208","title":"Paging Early Indication: Removal of Editor's note","source":"Qualcomm Incorporated","contact":"Miguel Griot","contact-id":84607,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Remove editor's note regarding UE providing paging probability in the context of PEI.","secretary_remarks":"r01 agreed. Revised to S2-2201552.","agenda_item_sort_order":71,"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":17990,"status":"revised","reservation_date":"2022-01-28 19:43:11","uploaded":"2022-01-28 20:17:56","revisionof":"","revisedto":"S2-2201552","release":"Rel-17","crspec":"23.502","crspecversion":"17.3.0","workitem":[{"winame":"TEI17"},{"winame":" NR_UE_pow_sav_enh"}],"crnumber":3417.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_149E_Electronic_2022-02\/Docs\/S2-2201208.zip","group":"S2","meeting":"S2-149-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2201477","title":"Clarification on rerouted Registration Request message","source":"Ericsson, Huawei, HiSilicon, NEC","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Adding clarificaiton on the re-routed Registration Request message between AMFs for rerouting possibilities.","secretary_remarks":"Revision of S2-2200339r02. CC#2: Moved to 8.28. Approved","agenda_item_sort_order":71,"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":18120,"status":"agreed","reservation_date":"2022-02-23 07:38:06","uploaded":"2022-03-01 08:41:21","revisionof":"S2-2200339","revisedto":"","release":"Rel-17","crspec":"23.502","crspecversion":"17.3.0","workitem":[{"winame":"5GS_Ph1"},{"winame":" TEI17"}],"crnumber":3150.0,"crrevision":4.0,"crcategory":"F","tsg_crp":"SP-220066","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_149E_Electronic_2022-02\/Docs\/S2-2201477.zip","group":"S2","meeting":"S2-149-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2201519","title":"LS from SA WG3: LS on full Registration Request upon AMF re-allocation","source":"SA WG3","contact":"Vlasios Tsiatsis","contact-id":76181,"tdoctype":"LS in","for":"Action","abstract":"SA WG3 thanks SA WG2 for the LS Response on full registration request message to be rerouted via RAN. SA WG3 would like to respond to SA WG2 that the TS 23.502 CR 3150 (originally provided by SA WG2 in S2-2107865\/S2-2108374) is acceptable to SA WG3 and SA WG3 has agreed to the attached TS 33.501 CR. In addition, SA WG3 has concluded the study of the security of AMF re-allocation with no agreement on the security handling of the AMF re-allocation via RAN case. Action: SA WG3 kindly asks SA WG2 to take this information into account and potentially make appropriate changes to the existing specifications.","secretary_remarks":"Postponed","agenda_item_sort_order":71,"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":18100,"status":"postponed","reservation_date":"2022-02-23 07:38:59","uploaded":"2022-03-01 08:41:21","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"","lsoriginalls":"S3-220453","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_149E_Electronic_2022-02\/Docs\/S2-2201519.zip","group":"S2","meeting":"S2-149-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2201548","title":"Reply LS on progress of FS_eIMS5G2","source":"SA WG2","contact":"Thomas Belling","contact-id":68266,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG3, CT WG4. CC: CT WG1, TSG CT, TSG SA","secretary_remarks":"Revision of S2-2200324r02. Approved","agenda_item_sort_order":71,"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":17670,"status":"approved","reservation_date":"2022-03-01 08:28:54","uploaded":"2022-03-01 08:41:13","revisionof":"S2-2200324","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"TEI17"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2200204","lsto":"CT WG3, CT WG4","Cc":"CT WG1, TSG CT, TSG SA","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_149E_Electronic_2022-02\/Docs\/S2-2201548.zip","group":"S2","meeting":"S2-149-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2201549","title":"Reply LS on Clarification of SCG outside RA for slicing","source":"SA WG2","contact":"Peter Hedman","contact-id":27550,"tdoctype":"LS out","for":"Approval","abstract":"To: RAN WG3","secretary_remarks":"Revision of S2-2200507r02, merging S2-2200771, merging S2-2200771 and S2-2200523. Approved","agenda_item_sort_order":71,"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":17730,"status":"approved","reservation_date":"2022-03-01 08:28:55","uploaded":"2022-03-01 08:41:13","revisionof":"S2-2200507","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"NR_slice"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2200026","lsto":"RAN WG3","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_149E_Electronic_2022-02\/Docs\/S2-2201549.zip","group":"S2","meeting":"S2-149-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2201550","title":"Remove the EN on UPIP for EPS","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Delete the EN related to SA WG3 and change the EN on UE capability to a note.","secretary_remarks":"Revision of S2-2200277r01. Approved","agenda_item_sort_order":71,"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":17920,"status":"agreed","reservation_date":"2022-03-01 08:28:55","uploaded":"2022-03-01 08:41:19","revisionof":"S2-2200277","revisedto":"","release":"Rel-17","crspec":"23.401","crspecversion":"17.3.0","workitem":[{"winame":"UPIP_SEC_LTE"}],"crnumber":3680.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-220068","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_149E_Electronic_2022-02\/Docs\/S2-2201550.zip","group":"S2","meeting":"S2-149-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2201551","title":"Correction on the MME handling for UPIP during interworking","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Correct the above description to focus on the EPS bearer.","secretary_remarks":"Revision of S2-2200278r03. Approved","agenda_item_sort_order":71,"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":17940,"status":"agreed","reservation_date":"2022-03-01 08:28:56","uploaded":"2022-03-01 08:41:19","revisionof":"S2-2200278","revisedto":"","release":"Rel-17","crspec":"23.501","crspecversion":"17.3.0","workitem":[{"winame":"UPIP_SEC_LTE"}],"crnumber":3481.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-220068","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_149E_Electronic_2022-02\/Docs\/S2-2201551.zip","group":"S2","meeting":"S2-149-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2201552","title":"Paging Early Indication: Removal of Editor's note","source":"Qualcomm Incorporated","contact":"Miguel Griot","contact-id":84607,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Remove editor's note regarding UE providing paging probability in the context of PEI.","secretary_remarks":"Revision of S2-2201208r01. Approved","agenda_item_sort_order":71,"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":18000,"status":"agreed","reservation_date":"2022-03-01 08:28:58","uploaded":"2022-03-01 08:41:19","revisionof":"S2-2201208","revisedto":"","release":"Rel-17","crspec":"23.502","crspecversion":"17.3.0","workitem":[{"winame":"NR_UE_pow_sav_enh"},{"winame":" TEI17"}],"crnumber":3417.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-220066","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_149E_Electronic_2022-02\/Docs\/S2-2201552.zip","group":"S2","meeting":"S2-149-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2201553","title":"LS Reply on Deletion of ME support of SOR-CMCI indicator during Nudm_SDM_Get","source":"SA WG2","contact":"Malla Reddy Sama","contact-id":48655,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG1, CT WG4. Attachments: TS 23.502 CR3402","secretary_remarks":"Revision of S2-2201013r01, merging S2-2201249. Approved","agenda_item_sort_order":71,"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":18060,"status":"approved","reservation_date":"2022-03-01 08:28:59","uploaded":"2022-03-01 08:41:13","revisionof":"S2-2201013","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"eCPSOR_CON"},{"winame":" TEI17"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2200081","lsto":"CT WG1, CT WG4","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_149E_Electronic_2022-02\/Docs\/S2-2201553.zip","group":"S2","meeting":"S2-149-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2201554","title":"Registration type to the UDM for SoR","source":"NTT DOCOMO, Ericsson, Samsung","contact":"Malla Reddy Sama","contact-id":48655,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Based on the existing 'Registration Type' provided by AMF and indicating initial registration and emergency registration information to the UDM, the UDM updates the UDR.","secretary_remarks":"Revision of S2-2200998r02, merging S2-2200999. Approved","agenda_item_sort_order":71,"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":18080,"status":"agreed","reservation_date":"2022-03-01 08:28:59","uploaded":"2022-03-01 08:41:19","revisionof":"S2-2200998","revisedto":"","release":"Rel-17","crspec":"23.502","crspecversion":"17.3.0","workitem":[{"winame":"TEI17"}],"crnumber":3402.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-220066","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_149E_Electronic_2022-02\/Docs\/S2-2201554.zip","group":"S2","meeting":"S2-149-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2201846","title":"Paging Early Indication: Removal of Editor's notes","source":"Qualcomm Incorporated","contact":"Miguel Griot","contact-id":84607,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Modify first editor's note to make it normative warning on the AMF implementation that if gNB is using paging grouping with Temporary UE ID, then paging sent to other UEs will increase the power consumption of also the other UEs. Remove second editor's note.","secretary_remarks":"Revision of S2-2201204r07 + changes. Approved","agenda_item_sort_order":71,"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":17980,"status":"agreed","reservation_date":"2022-03-01 08:32:08","uploaded":"2022-03-01 08:41:16","revisionof":"S2-2201204","revisedto":"","release":"Rel-17","crspec":"23.501","crspecversion":"17.3.0","workitem":[{"winame":"NR_UE_pow_sav_enh"},{"winame":" TEI17"}],"crnumber":3578.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-220066","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_149E_Electronic_2022-02\/Docs\/S2-2201846.zip","group":"S2","meeting":"S2-149-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2201859","title":"Reply LS on Slice list and priority information for cell reselection","source":"SA WG2","contact":"Jinguo Zhu","contact-id":32987,"tdoctype":"LS out","for":"Approval","abstract":"To: RAN WG2, RAN WG3, CT WG1. CC: TSG SA, TSG CT, TSG RAN","secretary_remarks":"Revision of S2-2201030r17. Approved","agenda_item_sort_order":71,"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":17850,"status":"approved","reservation_date":"2022-03-01 08:32:16","uploaded":"2022-03-01 08:41:16","revisionof":"S2-2201030","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"NR_slice-Core"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2200017","lsto":"RAN WG2, RAN WG3, CT WG1","Cc":"TSG SA, TSG CT, TSG RAN","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_149E_Electronic_2022-02\/Docs\/S2-2201859.zip","group":"S2","meeting":"S2-149-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]