[{"name":"S2-2105241","title":"LS from RAN WG2: LS on introducing extended DRX for RedCap UEs","source":"RAN WG2","contact":"Tuomas Tirronen","contact-id":73195,"tdoctype":"LS in","for":"Action","abstract":"RAN WG2 has started work on the support of reduced capability (RedCap) NR devices, where the related study item has been concluded in TR 38.875, v17.0.0 and work has been started according to WID in RP-210918. The WID has the following objectives on introduction of extended DRX: - Specify support for the following Extended DRX enhancements for RedCap UEs [RAN WG2, RAN WG3, RAN WG4]: o Extended DRX for RRC Inactive and Idle with eDRX cycles up to 10.24 s, without using PTW and PH, and with common design (e.g. common set of eDRX values) between RRC Inactive and Idle o Extended DRX for RRC Inactive and Idle with eDRX cycles up to 10485.76 s; the details of mechanisms and feasibility regarding maximum length of the extended DRX cycles for RRC Inactive and Idle need to be checked by SA WG2, CT WG1 and\/or RAN WG4. o RAN WG2 to decide which Node(s) configure eDRX in RRC_Idle and RRC_Inactive. RAN WG2 has discussed support for extended DRX for RedCap UEs during RAN WG2#113bis-e and has reached the following agreements and would like to ask SA WG2 and CT WG1 for feedback, if any: - RAN decides and configures eDRX via RRC for RRC_INACTIVE (FFS on the need and details of coordination with the CN) - At least for eDRX cycle, the configurations of the eDRX for RRC_IDLE and RRC_INACTIVE can be different (FFS for PTW, e.g. length and starting point, when eDRX cycles are longer than 10.24s) - RAN WG2 assumes that CN provides necessary assistance information on eDRX config. for RRC_IDLE to RAN (e.g. reusing eDRX config. defined in 'CN Assistance Information for RRC INACTIVE IE' for E-UTRA\/5GC). - eDRX feature, including the related parameters (i.e. PH, PTW. H-SFN) and corresponding paging operation defined for E-UTRA\/5GC is used as baseline to enable eDRX >10.24sec for both RRC_IDLE and RRC_INACTIVE in NR\/5GC. RAN WG2 would like to ask whether it is feasible from SA WG2 and CT WG1 perspective to introduce extended DRX up to 10485.76 s in RRC_IDLE and RRC_INACTIVE and if feasible, to specify the necessary support. RAN WG2 would like SA WG2 and CT WG1 to take the above aspects into consideration in their work and further consult with RAN WG2 if needed. Action: 1) RAN WG2 respectfully requests SA WG2 and CT WG1 to evaluate whether it is feasible to specify extended DRX up to 10485.76 s for RRC_IDLE and RRC_INACTIVE and if found feasible, specify the necessary support. 2) RAN WG2 respectfully requests SA WG2 and CT WG1 to take above information into account and provide feedback, if any.","secretary_remarks":"Revision of postponed S2-2103769 from S2-145E. Responses drafted in S2-2105802 and S2-2106402. Final response in S2-2106978","agenda_item_sort_order":73,"ainumber":"8.26","ainame":"Rel-17 CAT B\/C alignment CR(s) due to the work led by other 3GPP Working Groups","tdoc_agenda_sort_order":25460,"status":"replied to","reservation_date":"2021-06-24 14:38:56","uploaded":"2021-06-25 10:42:11","revisionof":"S2-2103769","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, CT WG1","Cc":"RAN WG3","lsoriginalls":"R2-2104374","lsreply":"S2-2106978","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_146E_Electronic_2021-08\/Docs\/S2-2105241.zip","group":"S2","meeting":"S2-146-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2105252","title":"LS from CT WG1: Reply LS on introducing extended DRX for RedCap UEs","source":"CT WG1","contact":"Lena Chaponniere","contact-id":38080,"tdoctype":"LS in","for":"Information","abstract":"CT WG1 thanks RAN WG2 for their LS on introducing extended DRX for RedCap UEs. Extended DRX cycles of up to 10485.76 seconds in RRC_IDLE are already supported since Release 16 for NB-IoT connected to the 5GC. It is feasible to extend this support to RedCap UEs in RRC_IDLE in Release 17. CT WG1 could not reach consensus on feedback regarding the feasibility of extending extended DRX in RRC_INACTIVE up to 10485.76 seconds.","secretary_remarks":"Noted","agenda_item_sort_order":73,"ainumber":"8.26","ainame":"Rel-17 CAT B\/C alignment CR(s) due to the work led by other 3GPP Working Groups","tdoc_agenda_sort_order":25390,"status":"noted","reservation_date":"2021-06-24 14:38:56","uploaded":"2021-06-25 10:42:11","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2","Cc":"RAN WG3, SA WG2","lsoriginalls":"C1-213966","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_146E_Electronic_2021-08\/Docs\/S2-2105252.zip","group":"S2","meeting":"S2-146-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2105269","title":"LS from RAN WG2: LS on lower bound for eDRX cycle length","source":"RAN WG2","contact":"Tuomas Tirronen","contact-id":73195,"tdoctype":"LS in","for":"Action","abstract":"RAN WG2 would like to inform SA WG2 and CT WG1 that RAN WG2 has agreed 2.56 seconds as lower bound for eDRX cycle length for RRC_IDLE and RRC_INACTIVE for RedCap. RAN WG2 would like SA WG2 and CT WG1 to take the above agreement into consideration in their work and inform RAN WG2 if there is any concern. Action: RAN WG2 respectfully requests SA WG2 and CT WG1 to take the RAN WG2 agreement on lower bound for eDRX cycle length into account in their work and inform RAN WG2 if there is any concern.","secretary_remarks":"Response drafted in S2-2106413 (noted). Postponed","agenda_item_sort_order":73,"ainumber":"8.26","ainame":"Rel-17 CAT B\/C alignment CR(s) due to the work led by other 3GPP Working Groups","tdoc_agenda_sort_order":25370,"status":"postponed","reservation_date":"2021-06-24 14:38:57","uploaded":"2021-06-25 10:42:12","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, CT WG1","Cc":"RAN WG3","lsoriginalls":"R2-2106537","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_146E_Electronic_2021-08\/Docs\/S2-2105269.zip","group":"S2","meeting":"S2-146-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2105292","title":"LS from SA WG3: LS on Supporting UP Integrity Protection Policy Handling for Interworking from 5GS to EPS","source":"SA WG3","contact":"Wu Rong","contact-id":49499,"tdoctype":"LS in","for":"Action","abstract":"SA WG3 would like to inform SA WG2 that SA WG3 agreed to apply user plane integrity protection for EPC, it is agreed that 'The solution with local RAN policy configuration for UP IP, shall be enhanced with the option of a Core Network\/RAN solution for UP IP policy handling.'. SA WG3 is studying user plane integrity protection policy handling from 5GS to EPS, and found that there are restrictions for interworking: As described in clause 5.10.3 in TS 23.501, 'For PDU Sessions with UP integrity protection of UP Security Enforcement Information set to Required, the SMF shall not trigger the EPS bearer ID allocation procedure in TS 23.502 [3] clause 4.11.1.4.', and as described in clause 4.11.5.3 in TS 23.502, 'Step 4: If the EPS Interworking indication received from AMF indicates that the UE supports EPS interworking and the SMF determines, based on the EPS interworking support indication from the AMF and additional UE subscription data (e.g. whether UP integrity protection of UP Security Enforcement Information is not set to required, EPS interworking is allowed for this DNN and S-NSSAI), that the PDU Session supports EPS interworking, the PGW-C+SMF FQDN for S5\/S8 interface is included in the Nudm_UECM_Registration Request.', SA WG3 realized that the restriction may avoid a PDU session interworking from 5GS to EPS if user plane integrity protection policy is set as 'required'. SA WG3 would like to request SA WG2 to confirm it is acceptable to remove these restrictions if UP IP when connected to EPS is supported. Action: SA WG3 kindly asks SA WG2 to take the above information into account.","secretary_remarks":"Response drafted in S2-2105697. Final response in S2-2106974","agenda_item_sort_order":73,"ainumber":"8.26","ainame":"Rel-17 CAT B\/C alignment CR(s) due to the work led by other 3GPP Working Groups","tdoc_agenda_sort_order":25260,"status":"replied to","reservation_date":"2021-06-25 10:32:22","uploaded":"2021-06-25 10:42:13","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"CT WG4","lsoriginalls":"S3-212196","lsreply":"S2-2106974","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_146E_Electronic_2021-08\/Docs\/S2-2105292.zip","group":"S2","meeting":"S2-146-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2105392","title":"EPS User Plane Integrity Protection with minimal core network changes","source":"Vodafone","contact":"Chris Pudney","contact-id":1122,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: In 5.3.10.4.0, a brief description of the 'best effort' solution is added, along with pointers to 23.501\/2 for the 'full solution'. Text added to show that UPIP is supported, not just user plane ciphering. Associated errors are tidied up in 5.7.2 and 5.11.3.","secretary_remarks":"r14 agreed. Revised to S2-2106975","agenda_item_sort_order":73,"ainumber":"8.26","ainame":"Rel-17 CAT B\/C alignment CR(s) due to the work led by other 3GPP Working Groups","tdoc_agenda_sort_order":25320,"status":"revised","reservation_date":"2021-07-30 16:06:53","uploaded":"2021-07-30 16:13:44","revisionof":"","revisedto":"S2-2106975","release":"Rel-17","crspec":23.401,"crspecversion":"17.1.0","workitem":[{"winame":"UPIP_SEC_LTE"}],"crnumber":3645.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_146E_Electronic_2021-08\/Docs\/S2-2105392.zip","group":"S2","meeting":"S2-146-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2105393","title":"EPS User Plane Integrity Protection using SMF+PGW-C","source":"Vodafone (based on earlier draft from Huawei, HiSilicon)","contact":"Chris Pudney","contact-id":1122,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: New UE 5GSM capability added for EPS-UPIP. Description added to 5.10.3 PDU Session User Plane Security. To avoid the accidental handover of bearers with UPIP=required to a non-upgraded EPS, it is necessary that the AMF is upgraded, and, that the SMF knows that the AMF is upgraded.","secretary_remarks":"r06 agreed. Revised to S2-2106976, merging S2-2105698","agenda_item_sort_order":73,"ainumber":"8.26","ainame":"Rel-17 CAT B\/C alignment CR(s) due to the work led by other 3GPP Working Groups","tdoc_agenda_sort_order":25340,"status":"revised","reservation_date":"2021-07-30 16:38:57","uploaded":"2021-07-30 16:42:09","revisionof":"","revisedto":"S2-2106976","release":"Rel-17","crspec":23.501,"crspecversion":"17.1.1","workitem":[{"winame":"UPIP_SEC_LTE"}],"crnumber":3009.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_146E_Electronic_2021-08\/Docs\/S2-2105393.zip","group":"S2","meeting":"S2-146-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2105394","title":"EPS User Plane Integrity Protection using SMF+PGW-C","source":"Vodafone (based on earlier draft from Huawei, HiSilicon)","contact":"Chris Pudney","contact-id":1122,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: UPIP related PDN Connection establishment in EPS is described in 4.11.0a.5 Interworking flows in 4.11.1 are updated. Information added to 4.11.5.3","secretary_remarks":"Merge into S2-2106668","agenda_item_sort_order":73,"ainumber":"8.26","ainame":"Rel-17 CAT B\/C alignment CR(s) due to the work led by other 3GPP Working Groups","tdoc_agenda_sort_order":25360,"status":"merged","reservation_date":"2021-07-30 16:44:57","uploaded":"2021-07-30 17:03:36","revisionof":"","revisedto":"","release":"Rel-17","crspec":23.502,"crspecversion":"17.1.0","workitem":[{"winame":"UPIP_SEC_LTE"}],"crnumber":2898.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_146E_Electronic_2021-08\/Docs\/S2-2105394.zip","group":"S2","meeting":"S2-146-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2105697","title":"[DRAFT] LS reply on Supporting UP Integrity Protection Policy Handling for Interworking from 5GS to EPS","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"LS out","for":"Approval","abstract":"This LS confirms SA WG2 will support the conculsion on UPIP from SA WG3.","secretary_remarks":"Response to S2-2105292. Revised to S2-2106974.","agenda_item_sort_order":73,"ainumber":"8.26","ainame":"Rel-17 CAT B\/C alignment CR(s) due to the work led by other 3GPP Working Groups","tdoc_agenda_sort_order":25270,"status":"revised","reservation_date":"2021-08-09 13:49:02","uploaded":"2021-08-10 15:15:17","revisionof":"","revisedto":"S2-2106974","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"FS_UP_IP_Sec"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG3","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_146E_Electronic_2021-08\/Docs\/S2-2105697.zip","group":"S2","meeting":"S2-146-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2105698","title":"Update on Supporting UP Integrity Protection Policy Handling for Interworking from 5GS to EPS","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Based on the SA WG3's conclusion, add related UE capability on UPIP support in EPS. Besides, remove the restriction on the EBI allocation and transfer when the UE and MME support UPIP in EPS.","secretary_remarks":"Merged into S2-2106976","agenda_item_sort_order":73,"ainumber":"8.26","ainame":"Rel-17 CAT B\/C alignment CR(s) due to the work led by other 3GPP Working Groups","tdoc_agenda_sort_order":25290,"status":"merged","reservation_date":"2021-08-09 13:49:02","uploaded":"2021-08-10 15:15:17","revisionof":"","revisedto":"","release":"Rel-17","crspec":23.501,"crspecversion":"17.1.1","workitem":[{"winame":"TEI17"},{"winame":" 5GS_Ph1"}],"crnumber":3063.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_146E_Electronic_2021-08\/Docs\/S2-2105698.zip","group":"S2","meeting":"S2-146-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2105699","title":"Update on Supporting UP Integrity Protection Policy Handling for Interworking from 5GS to EPS","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Based on the SA WG3's conclusion, add related UE capability on UPIP support in EPS. Besides, remove the restriction on the EBI allocation and transfer when the UE and MME support UPIP in EPS. The SMF will only allocate EBIs when the UE support UPIP in EPS and transfer the bearer context when the MME also support it. Besides, the SMF also needs to know the AMF capability on UPIP support in EPS, otherwise, in roaming scenario, when neither MME nor AMF support UPIP in EPS, but the UE does support it. Then the Home SMF (which is in a different country to the VPLMN's AMF) would use a policy of UPIP to allocate the EBIs, which is not correct.","secretary_remarks":"CC#4: r07 + changes agreed. Revised, merging S2-2105394, to S2-2106668.","agenda_item_sort_order":73,"ainumber":"8.26","ainame":"Rel-17 CAT B\/C alignment CR(s) due to the work led by other 3GPP Working Groups","tdoc_agenda_sort_order":25300,"status":"revised","reservation_date":"2021-08-09 13:49:03","uploaded":"2021-08-10 15:15:17","revisionof":"","revisedto":"S2-2106668","release":"Rel-17","crspec":23.502,"crspecversion":"17.1.0","workitem":[{"winame":"TEI17"},{"winame":" 5GS_Ph1"}],"crnumber":2957.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_146E_Electronic_2021-08\/Docs\/S2-2105699.zip","group":"S2","meeting":"S2-146-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2105802","title":"[DRAFT] Reply LS on introducing extended DRX for RedCap UEs","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"LS out","for":"Approval","abstract":"Reply LS to RAN WG2 and other working group informing the SA WG2 view on eDRX value range support and agreements from SA WG2","secretary_remarks":"Response to S2-2105241. Noted","agenda_item_sort_order":73,"ainumber":"8.26","ainame":"Rel-17 CAT B\/C alignment CR(s) due to the work led by other 3GPP Working Groups","tdoc_agenda_sort_order":25470,"status":"noted","reservation_date":"2021-08-09 18:49:18","uploaded":"2021-08-10 21:59:03","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"NR_redcap-Core"},{"winame":" TEI17"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2, RAN WG3, CT WG1, CT WG4","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_146E_Electronic_2021-08\/Docs\/S2-2105802.zip","group":"S2","meeting":"S2-146-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2105803","title":"Discussion on long eDRX value system impact to support RedCap.","source":"Ericsson, MediaTek Inc, Deutsche Telekom","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"discussion","for":"Agreement","abstract":"This document discusses the long eDRX value system impact to support the REDCAP.","secretary_remarks":"Noted","agenda_item_sort_order":73,"ainumber":"8.26","ainame":"Rel-17 CAT B\/C alignment CR(s) due to the work led by other 3GPP Working Groups","tdoc_agenda_sort_order":25500,"status":"noted","reservation_date":"2021-08-09 18:49:18","uploaded":"2021-08-10 21:59:03","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"NR_redcap-Core"},{"winame":" TEI17"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_146E_Electronic_2021-08\/Docs\/S2-2105803.zip","group":"S2","meeting":"S2-146-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2105804","title":"Support for RedCap UE indication and eDRX","source":"Ericsson, MediaTek Inc, Deutsche Telekom","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Introducing the support for RedCap UE in NR with indication and eDRX.","secretary_remarks":"Revision of (Noted) S2-2103903 from S2-145E. Noted","agenda_item_sort_order":73,"ainumber":"8.26","ainame":"Rel-17 CAT B\/C alignment CR(s) due to the work led by other 3GPP Working Groups","tdoc_agenda_sort_order":25510,"status":"noted","reservation_date":"2021-08-09 18:49:18","uploaded":"2021-08-10 21:59:03","revisionof":"S2-2103903","revisedto":"","release":"Rel-17","crspec":23.501,"crspecversion":"17.1.1","workitem":[{"winame":"NR_redcap-Core"},{"winame":" TEI17"}],"crnumber":2869.0,"crrevision":1.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_146E_Electronic_2021-08\/Docs\/S2-2105804.zip","group":"S2","meeting":"S2-146-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2105805","title":"Support for RedCap UE indication and eDRX","source":"Ericsson, MediaTek Inc, Deutsche Telekom","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Introducing the MT signaling and data handling in Network triggered resume procedure for UE in RRC Inactive state with long eDRX. Introducing RRC Inactive state information provision from RAN to CN. Introducting the MT signaling and data handling in MT NIDD flow","secretary_remarks":"Noted","agenda_item_sort_order":73,"ainumber":"8.26","ainame":"Rel-17 CAT B\/C alignment CR(s) due to the work led by other 3GPP Working Groups","tdoc_agenda_sort_order":25520,"status":"noted","reservation_date":"2021-08-09 18:49:19","uploaded":"2021-08-10 21:59:03","revisionof":"","revisedto":"","release":"Rel-17","crspec":23.502,"crspecversion":"17.1.0","workitem":[{"winame":"NR_redcap-Core"},{"winame":" TEI17"}],"crnumber":2986.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_146E_Electronic_2021-08\/Docs\/S2-2105805.zip","group":"S2","meeting":"S2-146-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2105806","title":"Event subscription parameters With DNN and S-NSSAI","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Adding the option for AF to provide the DNN, S-NSSAI to NEF. Adding DNN, S-NSSAI as optional parameters in the NEF and SMF service operations.","secretary_remarks":"Approved","agenda_item_sort_order":73,"ainumber":"8.26","ainame":"Rel-17 CAT B\/C alignment CR(s) due to the work led by other 3GPP Working Groups","tdoc_agenda_sort_order":25530,"status":"agreed","reservation_date":"2021-08-09 18:49:20","uploaded":"2021-08-10 21:47:17","revisionof":"","revisedto":"","release":"Rel-17","crspec":23.502,"crspecversion":"17.1.0","workitem":[{"winame":"NBI17"},{"winame":" TEI17"}],"crnumber":2987.0,"crrevision":"","crcategory":"C","tsg_crp":"SP-210936","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_146E_Electronic_2021-08\/Docs\/S2-2105806.zip","group":"S2","meeting":"S2-146-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2106025","title":"Discussion on eDRX in RRC_Inactive for RedCap.","source":"Apple","contact":"Sudeep M Vamanan","contact-id":87305,"tdoctype":"discussion","for":"Discussion","abstract":"This document discusses the impact to support eDRX in RRC_Inactive for RedCap UEs in 5GC.","secretary_remarks":"Noted","agenda_item_sort_order":73,"ainumber":"8.26","ainame":"Rel-17 CAT B\/C alignment CR(s) due to the work led by other 3GPP Working Groups","tdoc_agenda_sort_order":25400,"status":"noted","reservation_date":"2021-08-10 08:43:55","uploaded":"2021-08-10 18:56:53","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_146E_Electronic_2021-08\/Docs\/S2-2106025.zip","group":"S2","meeting":"S2-146-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2106159","title":"EDRX enhancement for 10.24s cycle for RedCap","source":"China Mobile","contact":"Aihua Li","contact-id":58162,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add the architecture enhancements to support eDRX for RRC Inactive and Idle with eDRX cycles up to 10.24 s for RedCap UE.","secretary_remarks":"Merged into S2-2106977","agenda_item_sort_order":73,"ainumber":"8.26","ainame":"Rel-17 CAT B\/C alignment CR(s) due to the work led by other 3GPP Working Groups","tdoc_agenda_sort_order":25540,"status":"merged","reservation_date":"2021-08-10 10:31:53","uploaded":"2021-08-10 12:59:49","revisionof":"","revisedto":"","release":"Rel-17","crspec":23.501,"crspecversion":"17.1.1","workitem":[{"winame":"5GS_Ph1"},{"winame":" TEI17"}],"crnumber":3153.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_146E_Electronic_2021-08\/Docs\/S2-2106159.zip","group":"S2","meeting":"S2-146-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2106161","title":"Support RedCap UEs differentiation in 5GC","source":"China Mobile","contact":"Aihua Li","contact-id":58162,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add the architecture enhancements to support RedCap UEs differentiation in 5GC.","secretary_remarks":"r04 agreed. Revised to S2-2106979","agenda_item_sort_order":73,"ainumber":"8.26","ainame":"Rel-17 CAT B\/C alignment CR(s) due to the work led by other 3GPP Working Groups","tdoc_agenda_sort_order":25550,"status":"revised","reservation_date":"2021-08-10 10:37:00","uploaded":"2021-08-10 12:59:49","revisionof":"","revisedto":"S2-2106979","release":"Rel-17","crspec":23.501,"crspecversion":"17.1.1","workitem":[{"winame":"5GS_Ph1"},{"winame":" TEI17"}],"crnumber":3155.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_146E_Electronic_2021-08\/Docs\/S2-2106161.zip","group":"S2","meeting":"S2-146-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2106175","title":"Support Idle mode eDRX up to 10485.76 s for RedCap","source":"China Mobile","contact":"Aihua Li","contact-id":58162,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add the architecture enhancements to support eDRX for CM_IDLE with eDRX cycles up to 10485.76s for RedCap UE.","secretary_remarks":"Merged into S2-2106977","agenda_item_sort_order":73,"ainumber":"8.26","ainame":"Rel-17 CAT B\/C alignment CR(s) due to the work led by other 3GPP Working Groups","tdoc_agenda_sort_order":25570,"status":"merged","reservation_date":"2021-08-10 10:39:39","uploaded":"2021-08-10 12:59:49","revisionof":"","revisedto":"","release":"Rel-17","crspec":23.501,"crspecversion":"17.1.1","workitem":[{"winame":"5GS_Ph1"},{"winame":" TEI17"}],"crnumber":3163.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_146E_Electronic_2021-08\/Docs\/S2-2106175.zip","group":"S2","meeting":"S2-146-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2106273","title":"EPS Support for IoT NTN.","source":"MediaTek Inc., Deutsche Telekom AG, Eutelsat, Intelsat, Sateliot, THALES","contact":"Guillaume Sebire","contact-id":45073,"tdoctype":"discussion","for":"Decision","abstract":"This contribution discusses the support for IoT NTN in EPS in Rel-17 as alignment to RAN#92e-approved WI.","secretary_remarks":"Noted","agenda_item_sort_order":73,"ainumber":"8.26","ainame":"Rel-17 CAT B\/C alignment CR(s) due to the work led by other 3GPP Working Groups","tdoc_agenda_sort_order":25580,"status":"noted","reservation_date":"2021-08-10 12:49:46","uploaded":"2021-08-10 17:15:54","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"TEI17"},{"winame":" LTE_NBIOT_eMTC_NTN"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_146E_Electronic_2021-08\/Docs\/S2-2106273.zip","group":"S2","meeting":"S2-146-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2106275","title":"Introduction of Satellite support for Cellular IoT","source":"MediaTek Inc.","contact":"Guillaume Sebire","contact-id":45073,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Adding IoT NTN support in EPS [Note the CR is in its present form not complete e.g. procedural changes are missing]","secretary_remarks":"Postponed","agenda_item_sort_order":73,"ainumber":"8.26","ainame":"Rel-17 CAT B\/C alignment CR(s) due to the work led by other 3GPP Working Groups","tdoc_agenda_sort_order":25590,"status":"postponed","reservation_date":"2021-08-10 12:49:46","uploaded":"2021-08-10 17:15:54","revisionof":"","revisedto":"","release":"Rel-17","crspec":23.401,"crspecversion":"17.1.0","workitem":[{"winame":"TEI17"},{"winame":" LTE_NBIOT_eMTC_NTN"}],"crnumber":3653.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_146E_Electronic_2021-08\/Docs\/S2-2106275.zip","group":"S2","meeting":"S2-146-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2106276","title":"[DRAFT] LS on EPS support for IoT NTN in Rel-17","source":"MediaTek Inc.","contact":"Guillaume Sebire","contact-id":45073,"tdoctype":"LS out","for":"Approval","abstract":"LS to CT and RAN groups to indicate SA WG2 agreements wrt Rel-17 IoT NTN support in EPS","secretary_remarks":"r00 agreed. Revised to remove 'draft' in S2-2106834","agenda_item_sort_order":73,"ainumber":"8.26","ainame":"Rel-17 CAT B\/C alignment CR(s) due to the work led by other 3GPP Working Groups","tdoc_agenda_sort_order":25600,"status":"revised","reservation_date":"2021-08-10 12:49:47","uploaded":"2021-08-10 17:15:54","revisionof":"","revisedto":"S2-2106834","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"TEI17"},{"winame":" LTE_NBIOT_eMTC_NTN"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG RAN, RAN WG1, RAN WG2, RAN WG3, TSG CT, CT WG1, CT WG3, CT WG4, CT WG6","Cc":"TSG SA, SA WG1","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_146E_Electronic_2021-08\/Docs\/S2-2106276.zip","group":"S2","meeting":"S2-146-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2106394","title":"Extended DRX for NR (RedCap)","source":"Qualcomm Inc.","contact":"Miguel Griot","contact-id":84607,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Extend eDRX support to 5GS with NR: eDRX beyond 10.24s for CM idle. eDRX up to RRC inactive for CM-Connected with RRC inactive.","secretary_remarks":"r05 agreed. Revised to S2-2106977, merging S2-2106159 and S2-2106175","agenda_item_sort_order":73,"ainumber":"8.26","ainame":"Rel-17 CAT B\/C alignment CR(s) due to the work led by other 3GPP Working Groups","tdoc_agenda_sort_order":25410,"status":"revised","reservation_date":"2021-08-10 15:57:46","uploaded":"2021-08-10 18:51:21","revisionof":"","revisedto":"S2-2106977","release":"Rel-17","crspec":23.501,"crspecversion":"17.1.1","workitem":[{"winame":"TEI17"},{"winame":" NR_redcap-Core"}],"crnumber":3209.0,"crrevision":"","crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_146E_Electronic_2021-08\/Docs\/S2-2106394.zip","group":"S2","meeting":"S2-146-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2106396","title":"RRC inactive and eDRX longer than 10.24s.","source":"Qualcomm Inc","contact":"Miguel Griot","contact-id":84607,"tdoctype":"discussion","for":"Agreement","abstract":"This document proposes to support CM-IDLE with RRC inactive in case of eDRX>10.24s, but it is preferred to defer to Rel-18.","secretary_remarks":"Noted","agenda_item_sort_order":73,"ainumber":"8.26","ainame":"Rel-17 CAT B\/C alignment CR(s) due to the work led by other 3GPP Working Groups","tdoc_agenda_sort_order":25430,"status":"noted","reservation_date":"2021-08-10 16:02:44","uploaded":"2021-08-10 18:51:21","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"TEI17"},{"winame":" NR_redcap-Core"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_146E_Electronic_2021-08\/Docs\/S2-2106396.zip","group":"S2","meeting":"S2-146-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2106399","title":"RRC inactive with CM-IDLE for eDRX>10.24s","source":"Qualcomm Incorporated","contact":"Miguel Griot","contact-id":84607,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Introduce CM-IDLE with RRC inactive for eDRX>10.24s.","secretary_remarks":"Check WI Code spelling. Noted","agenda_item_sort_order":73,"ainumber":"8.26","ainame":"Rel-17 CAT B\/C alignment CR(s) due to the work led by other 3GPP Working Groups","tdoc_agenda_sort_order":25440,"status":"noted","reservation_date":"2021-08-10 16:21:34","uploaded":"2021-08-10 18:51:21","revisionof":"","revisedto":"","release":"Rel-17","crspec":23.501,"crspecversion":"17.1.1","workitem":[{"winame":"TEI17"},{"winame":" NR_redcap-Core"}],"crnumber":3212.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_146E_Electronic_2021-08\/Docs\/S2-2106399.zip","group":"S2","meeting":"S2-146-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2106400","title":"CM-IDLE with RRC inactive procedures","source":"Qualcomm Incorporated","contact":"Miguel Griot","contact-id":84607,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Modifications to: Suspend procedure Resume procedure NW initiated service request","secretary_remarks":"Noted","agenda_item_sort_order":73,"ainumber":"8.26","ainame":"Rel-17 CAT B\/C alignment CR(s) due to the work led by other 3GPP Working Groups","tdoc_agenda_sort_order":25450,"status":"noted","reservation_date":"2021-08-10 16:27:08","uploaded":"2021-08-10 18:51:21","revisionof":"","revisedto":"","release":"Rel-17","crspec":23.502,"crspecversion":"17.1.0","workitem":[{"winame":"TEI17"},{"winame":" NR_redcap-Core"}],"crnumber":3098.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_146E_Electronic_2021-08\/Docs\/S2-2106400.zip","group":"S2","meeting":"S2-146-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2106402","title":"[DRAFT] Reply LS on introducing extended DRX for RedCap UEs","source":"Qualcomm Technologies Int","contact":"Miguel Griot","contact-id":84607,"tdoctype":"LS out","for":"Approval","abstract":"Responds that SA WG2 agrees to extend current eDRX system architecture solution for CM-IDLE\/RRC idle, and also for RRC inactive up to 10.24s. eDRX>10.24s for RRC inactive is left to be studied in Rel-18.","secretary_remarks":"Response to S2-2105241. r01 agreed. Revised to S2-2106978","agenda_item_sort_order":73,"ainumber":"8.26","ainame":"Rel-17 CAT B\/C alignment CR(s) due to the work led by other 3GPP Working Groups","tdoc_agenda_sort_order":25480,"status":"revised","reservation_date":"2021-08-10 16:34:40","uploaded":"2021-08-10 18:51:21","revisionof":"","revisedto":"S2-2106978","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"TEI17"},{"winame":" NR_redcap-Core"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2, RAN WG3, CT WG1","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_146E_Electronic_2021-08\/Docs\/S2-2106402.zip","group":"S2","meeting":"S2-146-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2106413","title":"[DRAFT] Reply LS on lower bound for eDRX cycle length","source":"Qualcomm Technologies Int","contact":"Miguel Griot","contact-id":84607,"tdoctype":"LS out","for":"Approval","abstract":"Proposes that SA WG2 ask RAN WG2 to reconsider the eDRX based solution and adopt a more explicit negotiation approach in NAS to always use UE specific DRX whenever supported by NG-RAN node.","secretary_remarks":"Response to S2-2105269. Noted","agenda_item_sort_order":73,"ainumber":"8.26","ainame":"Rel-17 CAT B\/C alignment CR(s) due to the work led by other 3GPP Working Groups","tdoc_agenda_sort_order":25380,"status":"noted","reservation_date":"2021-08-10 16:59:47","uploaded":"2021-08-10 18:51:21","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"TEI17"},{"winame":" NR_redcap"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2, CT WG1","Cc":"RAN WG3","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_146E_Electronic_2021-08\/Docs\/S2-2106413.zip","group":"S2","meeting":"S2-146-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2106668","title":"Update on Supporting UP Integrity Protection Policy Handling for Interworking from 5GS to EPS","source":"Huawei, HiSilicon, Vodafone, Nokia, Nokia Shanghai Bell, Ericsson","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Based on the SA WG3's conclusion, add related UE capability on UPIP support in EPS. Besides, remove the restriction on the EBI allocation and transfer when the UE and MME support UPIP in EPS. The SMF will only allocate EBIs when the UE support UPIP in EPS and transfer the bearer context when the MME also support it. Besides, the SMF also needs to know the AMF capability on UPIP support in EPS, otherwise, in roaming scenario, when neither MME nor AMF support UPIP in EPS, but the UE does support it. Then the Home SMF (which is in a different country to the VPLMN's AMF) would use a policy of UPIP to allocate the EBIs, which is not correct. UPIP related PDN Connection establishment in EPS is described in 4.11.0a.5.","secretary_remarks":"Revision of S2-2105699r07 + changes, merging S2-2105394. Approved","agenda_item_sort_order":73,"ainumber":"8.26","ainame":"Rel-17 CAT B\/C alignment CR(s) due to the work led by other 3GPP Working Groups","tdoc_agenda_sort_order":25310,"status":"agreed","reservation_date":"2021-09-01 09:15:11","uploaded":"2021-09-01 14:31:25","revisionof":"S2-2105699","revisedto":"","release":"Rel-17","crspec":23.502,"crspecversion":"17.1.0","workitem":[{"winame":"5GS_Ph1"},{"winame":" TEI17"}],"crnumber":2957.0,"crrevision":1.0,"crcategory":"B","tsg_crp":"SP-210936","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_146E_Electronic_2021-08\/Docs\/S2-2106668.zip","group":"S2","meeting":"S2-146-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2106679","title":"LS on EPS support for IoT NTN in Rel-17","source":"SA WG2","contact":"Guillaume Sebire","contact-id":45073,"tdoctype":"LS out","for":"Approval","abstract":"To: TSG RAN. CC: TSG SA, TSG CT. Attachments: S2-2106794","secretary_remarks":"Revision of S2-2106834r01. Approved","agenda_item_sort_order":73,"ainumber":"8.26","ainame":"Rel-17 CAT B\/C alignment CR(s) due to the work led by other 3GPP Working Groups","tdoc_agenda_sort_order":25620,"status":"approved","reservation_date":"2021-09-01 09:15:24","uploaded":"2021-09-01 14:31:25","revisionof":"S2-2106834","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"LTE_NBIOT_eMTC_NTN"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG RAN","Cc":"TSG SA, TSG CT","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_146E_Electronic_2021-08\/Docs\/S2-2106679.zip","group":"S2","meeting":"S2-146-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2106834","title":"[DRAFT] LS on EPS support for IoT NTN in Rel-17","source":"MediaTek Inc.","contact":"Guillaume Sebire","contact-id":45073,"tdoctype":"LS out","for":"Approval","abstract":"To: TSG RAN. CC: TSG SA. Attachments: S2-2106794","secretary_remarks":"Revision of S2-2106276r00. CC#4: Left open for further discussion before CC#5. CC#5: r01 agreed. Revised to S2-2106679.","agenda_item_sort_order":73,"ainumber":"8.26","ainame":"Rel-17 CAT B\/C alignment CR(s) due to the work led by other 3GPP Working Groups","tdoc_agenda_sort_order":25610,"status":"revised","reservation_date":"2021-09-01 09:17:21","uploaded":"2021-09-01 14:31:28","revisionof":"S2-2106276","revisedto":"S2-2106679","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"TEI17"},{"winame":" LTE_NBIOT_eMTC_NTN"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG RAN","Cc":"TSG SA","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_146E_Electronic_2021-08\/Docs\/S2-2106834.zip","group":"S2","meeting":"S2-146-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2106974","title":"LS Reply on Supporting UP Integrity Protection Policy Handling for Interworking from 5GS to EPS","source":"SA WG2","contact":"Haiyang Sun","contact-id":79579,"tdoctype":"LS out","for":"Approval","abstract":"To: SA WG3. CC: TSG RAN, TSG CT, RAN WG2, RAN WG3, CT WG1, CT WG4. Attachments: TS 23.501 CR 3009, TS 23.502 CR 2957, 23.401 CR 3645","secretary_remarks":"Revision of S2-2105697r02. Approved","agenda_item_sort_order":73,"ainumber":"8.26","ainame":"Rel-17 CAT B\/C alignment CR(s) due to the work led by other 3GPP Working Groups","tdoc_agenda_sort_order":25280,"status":"approved","reservation_date":"2021-09-01 09:19:03","uploaded":"2021-09-01 14:31:29","revisionof":"S2-2105697","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"FS_UP_IP_Sec"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2105292","lsto":"SA WG3","Cc":"TSG RAN, TSG CT, RAN WG2, RAN WG3, CT WG1, CT WG4","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_146E_Electronic_2021-08\/Docs\/S2-2106974.zip","group":"S2","meeting":"S2-146-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2106975","title":"EPS User Plane Integrity Protection with minimal core network changes","source":"Vodafone, Nokia, Nokia Shanghai Bell, Ericsson","contact":"Chris Pudney","contact-id":1122,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: In 5.3.10.4.0, a brief description of the 'best effort' solution is added, along with pointers to 23.501\/2 for the 'full solution'. Text added to show that UPIP is supported, not just user plane ciphering. Associated errors are tidied up in 5.7.2 and 5.11.3.","secretary_remarks":"Revision of S2-2105392r14. Approved","agenda_item_sort_order":73,"ainumber":"8.26","ainame":"Rel-17 CAT B\/C alignment CR(s) due to the work led by other 3GPP Working Groups","tdoc_agenda_sort_order":25330,"status":"agreed","reservation_date":"2021-09-01 09:19:04","uploaded":"2021-09-01 14:31:29","revisionof":"S2-2105392","revisedto":"","release":"Rel-17","crspec":23.401,"crspecversion":"17.1.0","workitem":[{"winame":"UPIP_SEC_LTE"}],"crnumber":3645.0,"crrevision":1.0,"crcategory":"B","tsg_crp":"SP-210935","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_146E_Electronic_2021-08\/Docs\/S2-2106975.zip","group":"S2","meeting":"S2-146-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2106976","title":"EPS User Plane Integrity Protection using SMF+PGW-C","source":"Vodafone, Nokia, Nokia Shanghai Bell, Huawei, HiSilicon, Ericsson","contact":"Chris Pudney","contact-id":1122,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Description added to 5.10.3 PDU Session User Plane Security. To avoid the accidental handover of bearers with UPIP=required to a non-upgraded EPS, it is necessary that the AMF is upgraded, and, that the SMF knows that the AMF is upgraded.","secretary_remarks":"Revision of S2-2105393r06, merging S2-2105698. Approved","agenda_item_sort_order":73,"ainumber":"8.26","ainame":"Rel-17 CAT B\/C alignment CR(s) due to the work led by other 3GPP Working Groups","tdoc_agenda_sort_order":25350,"status":"agreed","reservation_date":"2021-09-01 09:19:06","uploaded":"2021-09-01 14:31:29","revisionof":"S2-2105393","revisedto":"","release":"Rel-17","crspec":23.501,"crspecversion":"17.1.1","workitem":[{"winame":"UPIP_SEC_LTE"}],"crnumber":3009.0,"crrevision":1.0,"crcategory":"B","tsg_crp":"SP-210935","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_146E_Electronic_2021-08\/Docs\/S2-2106976.zip","group":"S2","meeting":"S2-146-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2106977","title":"Extended DRX for NR (RedCap)","source":"Qualcomm Inc.","contact":"Miguel Griot","contact-id":84607,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Extend eDRX support to 5GS with NR: eDRX beyond 10.24s for CM idle. eDRX up to 10.24s in RRC inactive for CM-Connected with RRC inactive.","secretary_remarks":"Revision of S2-2106394r05, merging S2-2106159 and S2-2106175. Approved","agenda_item_sort_order":73,"ainumber":"8.26","ainame":"Rel-17 CAT B\/C alignment CR(s) due to the work led by other 3GPP Working Groups","tdoc_agenda_sort_order":25420,"status":"agreed","reservation_date":"2021-09-01 09:19:08","uploaded":"2021-09-01 14:31:29","revisionof":"S2-2106394","revisedto":"","release":"Rel-17","crspec":23.501,"crspecversion":"17.1.1","workitem":[{"winame":"NR_redcap-Core"}],"crnumber":3209.0,"crrevision":1.0,"crcategory":"C","tsg_crp":"SP-210933","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_146E_Electronic_2021-08\/Docs\/S2-2106977.zip","group":"S2","meeting":"S2-146-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2106978","title":"Reply LS on introducing extended DRX for RedCap UEs","source":"SA WG2","contact":"Miguel Griot","contact-id":84607,"tdoctype":"LS out","for":"Approval","abstract":"To: RAN WG2, RAN WG3, CT WG1. Attachments: S2-2106977 (TS 23.501 CR#3209)","secretary_remarks":"Revision of S2-2106402r01. Approved","agenda_item_sort_order":73,"ainumber":"8.26","ainame":"Rel-17 CAT B\/C alignment CR(s) due to the work led by other 3GPP Working Groups","tdoc_agenda_sort_order":25490,"status":"approved","reservation_date":"2021-09-01 09:19:10","uploaded":"2021-09-01 14:31:29","revisionof":"S2-2106402","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"TEI17"},{"winame":" NR_redcap-Core"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2105241","lsto":"RAN WG2, RAN WG3, CT WG1","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_146E_Electronic_2021-08\/Docs\/S2-2106978.zip","group":"S2","meeting":"S2-146-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2106979","title":"Support RedCap UEs differentiation in 5GC","source":"China Mobile, Ericsson, Nokia, Nokia Shanghai Bell","contact":"Aihua Li","contact-id":58162,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add the architecture enhancements to support RedCap UEs differentiation in 5GC.","secretary_remarks":"Revision of S2-2106161r04. Approved","agenda_item_sort_order":73,"ainumber":"8.26","ainame":"Rel-17 CAT B\/C alignment CR(s) due to the work led by other 3GPP Working Groups","tdoc_agenda_sort_order":25560,"status":"agreed","reservation_date":"2021-09-01 09:19:10","uploaded":"2021-09-01 14:31:29","revisionof":"S2-2106161","revisedto":"","release":"Rel-17","crspec":23.501,"crspecversion":"17.1.1","workitem":[{"winame":"NR_redcap"}],"crnumber":3155.0,"crrevision":1.0,"crcategory":"B","tsg_crp":"SP-210933","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_146E_Electronic_2021-08\/Docs\/S2-2106979.zip","group":"S2","meeting":"S2-146-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]