[{"name":"S2-2000021","title":"LS from CT WG1: Reply LS on assistance indication for WUS","source":"CT WG1","contact":"Lin Shu","contact-id":43310,"tdoctype":"LS in","for":"Action","abstract":"CT WG1 thanks SA WG2 for their LS 'Reply LS on assistance indication for WUS'. Based on SA WG2 technical endorsed CR, CT WG1 would like to inform SA WG2, RAN WG2 and RAN WG3 that it has agreed TS 24.301 CRs as attached to implement the WUS assistance in stage 3 and request any feedback. CT WG1 further identified following open issues which are not covered by current SA WG2 endorsement: Question #1: Once the MME has determined the WUS assistance information for the UE, is it mandatory for the MME to send it to the UE in every attach\/TAU accept message and to the eNB in every S1 paging? Description: Based on the last pragrapgh in new general section in SA WG2 adorsed CR, one can see the answer is yes while based on the text provided in procedure sections, the answer is no. Once the MME has determined the WUS Assistance Information for a UE, does it mean that the MME has accepted to use the WUS assistance for the UE and will hence provide the determined WUS assistance information to both the UE and the eNB consistently? Question #2: Can (and how does) the UE actively request to stop the use of WUS assistance? Description: CT WG1 has agreed to add a TAU trigger for the UE to request the use of WUS assistance. CT WG1 noted that it is optional for the UE to include the requested UE paging probability in the attach\/TAU request message and the MME can still determine the WUS Assistance Information for the WUS supporting UE. However, it is unclear whether the UE can request to stop the use of WUS assistance and if so, how should this be done? Question #3: Can the WUS assistance usage conditions be changed at the UE and then to trigger a TAU to re-negotiate the use of WUS assistance with the network? Question #4: Can the WUS assistance be negotiated during a combined attach and combined TAU procedure? Description: CT WG1 observed WUS assistance can be used for eMTC UEs which may need voice services via CSFB and then the combined attach and combined TAU procedure need to be initiated. Question #5: Can the WUS assistance be used for a UE attached for emergency bearer services or a UE that has a PDN connection for emergency bearer services?. Action: CT WG1 would like to ask recipient groups to take the above description into account and provide feedback, if any. Action: CT WG1 would like to ask SA WG2 to provide answers to the questions above.","secretary_remarks":"Postponed S2-1911952 from SA2#136. Responses drafted in S2-2000334 and S2-2000726. Final response in S2-2001732","agenda_item_sort_order":8,"ainumber":"5.1","ainame":"3GPP Packet Access Maintenance","tdoc_agenda_sort_order":10160,"status":"replied to","reservation_date":"2019-12-18 15:23:44","uploaded":"2020-01-06 08:48:38","revisionof":"S2-1911952","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, RAN WG2, RAN WG3","Cc":"","lsoriginalls":"C1-199008","lsreply":"S2-2001732","link":"http:\/\/www.3gpp.org\/ftp\/TSG_SA\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2000021.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2000043","title":"LS from RAN WG3: Reply LS on Secondary Node Sharing","source":"RAN WG3","contact":"Markus Sommer","contact-id":70191,"tdoctype":"LS in","for":"Information","abstract":"RAN WG3 would like to thank the NGMN Alliance for their LS. The secondary node sharing as described by NGMN in their LS is supported in specifications under RAN WG3's responsibility from Rel-15.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":8,"ainumber":"5.1","ainame":"3GPP Packet Access Maintenance","tdoc_agenda_sort_order":10220,"status":"noted","reservation_date":"2019-12-18 15:23:44","uploaded":"2020-01-06 08:48:38","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"NGMN Alliance","Cc":"TSG RAN, SA WG2","lsoriginalls":"R3-197742","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/TSG_SA\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2000043.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2000068","title":"LS from RAN WG2: Reply LS on assistance indication for WUS","source":"RAN WG2","contact":"Mungal Singh Dhanda","contact-id":38917,"tdoctype":"LS in","for":"Action","abstract":"RAN WG2 thanks SA WG2 for their reply LS on assistance indication for WUS and RAN WG2 has discussed the following issue highlighted by SA WG2: 'SA WG2 would like to ask RAN WG2 whether additional assistance information is required and\/or MME needs to NOT send WUS Assistance Information in S1 Paging message for highly mobile UEs that will be interpreted by RAN to not use WUS' RAN WG2 recognise the issue created by a mobile UE using WUS but RAN WG2 has not yet concluded on a solution. RAN WG2 re-discussed 'whether and how using WUS may affect MME paging strategies' in R15 and concluded that with some MME paging strategies, e.g. always paging a UE in the entire TA list, this may lead to increased power consumption for UEs using WUS. Therefore, RAN WG2 asks SA WG2 to take this into consideration from Release 15 so that benefit of WUS can be realised. Action: RAN WG2 respectfully asks SA WG2, CT WG1 and RAN WG3 to take the above into account.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":8,"ainumber":"5.1","ainame":"3GPP Packet Access Maintenance","tdoc_agenda_sort_order":10310,"status":"noted","reservation_date":"2019-12-18 15:23:45","uploaded":"2020-01-07 09:39:14","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, CT WG1, RAN WG3","Cc":"TSG SA","lsoriginalls":"R2-1916440","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2000068.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2000332","title":"WUS indication to MME","source":"Qualcomm Incorprorated","contact":"Haris Zisimopoulos","contact-id":84603,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Based on UEs indication for support of WUS in RRC, the eNB provides an indication in S1 release that UE supports WUS. MME can store and take that indication into account for paging strategy","secretary_remarks":"Revised in parallel session to S2-2001165.","agenda_item_sort_order":8,"ainumber":"5.1","ainame":"3GPP Packet Access Maintenance","tdoc_agenda_sort_order":10240,"status":"revised","reservation_date":"2020-01-05 19:27:01","uploaded":"2020-01-07 15:00:32","revisionof":"","revisedto":"S2-2001165","release":"Rel-15","crspec":"23.401","crspecversion":"15.10.0","workitem":[{"winame":"NB_IOTenh-Core"},{"winame":"CIoT_Ext"},{"winame":"LTE_eMTC4-Core"},{"winame":"NB_IOTenh2-Core"}],"crnumber":3575.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2000332.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2000333","title":"WUS indication to MME","source":"Qualcomm Incorprorated","contact":"Haris Zisimopoulos","contact-id":84603,"tdoctype":"CR","for":"Approval","abstract":"Rel-16 mirror CR: Summary of change: Based on UEs indication for support of WUS in RRC, the eNB provides an indication in S1 release that UE supports WUS. MME can store and take that indication into account for paging strategy It also clarifies the relationship with WUS Assistance Information in NAS","secretary_remarks":"Revised in parallel session to S2-2001166.","agenda_item_sort_order":8,"ainumber":"5.1","ainame":"3GPP Packet Access Maintenance","tdoc_agenda_sort_order":10270,"status":"revised","reservation_date":"2020-01-05 19:33:03","uploaded":"2020-01-07 15:00:31","revisionof":"","revisedto":"S2-2001166","release":"Rel-16","crspec":"23.401","crspecversion":"16.5.0","workitem":[{"winame":"NB_IOTenh-Core"},{"winame":"CIoT_Ext"},{"winame":"LTE_eMTC4-Core"},{"winame":"NB_IOTenh2-Core"}],"crnumber":3576.0,"crrevision":"","crcategory":"A","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2000333.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2000334","title":"[DRAFT] Reply LS on assistance indication for WUS","source":"Qualcomm Incorporated","contact":"Haris Zisimopoulos","contact-id":84603,"tdoctype":"LS out","for":"Approval","abstract":"Response LS to RAN WG2, CT WG1 and RAN WG3 about assistance indication for WUS","secretary_remarks":"Response to S2-2000021. Noted in parallel session","agenda_item_sort_order":8,"ainumber":"5.1","ainame":"3GPP Packet Access Maintenance","tdoc_agenda_sort_order":10170,"status":"noted","reservation_date":"2020-01-05 19:37:58","uploaded":"2020-01-07 15:00:31","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"LTE_eMTC5-Core"},{"winame":"NB_IOTenh3-Core"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2, CT WG1, RAN WG3","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2000334.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2000335","title":"WUS assistance clarifications","source":"Qualcomm Incorprorated","contact":"Haris Zisimopoulos","contact-id":84603,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: MME shall provide (i.e. is mandatory) WUS Assistance Information to the UE in every Attach Accept\/TAU Accept message, IF it has stored WUS Assistance Information parameter in the MM context Support for WUS Assistance Information is not signalled at emergency attach and when UE has emergency PDN connection active","secretary_remarks":"Revised in parallel session, merging S2-2000337, to S2-2001170.","agenda_item_sort_order":8,"ainumber":"5.1","ainame":"3GPP Packet Access Maintenance","tdoc_agenda_sort_order":10290,"status":"revised","reservation_date":"2020-01-05 19:47:08","uploaded":"2020-01-07 15:00:31","revisionof":"","revisedto":"S2-2001170","release":"Rel-16","crspec":"23.401","crspecversion":"16.5.0","workitem":[{"winame":"LTE_eMTC5-Core"},{"winame":"NB_IOTenh3-Core"}],"crnumber":3577.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2000335.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2000337","title":"EPC awareness of WUS","source":"NTT DOCOMO INC.","contact":"Kenichiro Aoyagi","contact-id":73277,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The MME is aware of WUS (both grouping and non grouping) applied or not by its configuration, and may be configured to take it into account for the paging strategy.","secretary_remarks":"Revision of postponed S2-1911132 from S2#136 Merged into S2-2001170","agenda_item_sort_order":8,"ainumber":"5.1","ainame":"3GPP Packet Access Maintenance","tdoc_agenda_sort_order":10310,"status":"merged","reservation_date":"2020-01-06 00:06:06","uploaded":"2020-01-07 07:01:09","revisionof":"S2-1911132","revisedto":"","release":"Rel-16","crspec":"23.401","crspecversion":"16.5.0","workitem":[{"winame":"TEI16"},{"winame":"LTE_eMTC5-Core"},{"winame":"NB_IOTenh3-Core"}],"crnumber":3559.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2000337.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2000726","title":"[DRAFT] Reply LS on assistance indication for WUS","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"LS out","for":"Approval","abstract":"Response LS to (C1-199008) on Reply LS on assistance indication for WUS from CT WG1","secretary_remarks":"Response to S2-2000021. Revised in parallel session to S2-2001169.","agenda_item_sort_order":8,"ainumber":"5.1","ainame":"3GPP Packet Access Maintenance","tdoc_agenda_sort_order":10180,"status":"revised","reservation_date":"2020-01-07 09:00:11","uploaded":"2020-01-07 13:14:02","revisionof":"","revisedto":"S2-2001169","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"NB_IOTenh3-Core"},{"winame":"LTE_eMTC5-Core"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"RAN WG2, RAN WG3","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2000726.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2000830","title":"LS from RAN WG2: Reply LS on extended NAS timers for CE in 5GS","source":"RAN WG2","contact":"Tuomas Tirronen","contact-id":73195,"tdoctype":"LS in","for":"Information","abstract":"RAN WG2 thanks CT WG1 for their LS on Extended NAS timers for Coverage Enhancement in 5GS. RAN WG2 would like to inform CT WG1 that there should be no differences in RAN delay for WB-N1 (eMTC) or NB-N1 (NB-IoT) using coverage enhancements in 5GS compared to EPS when the UE is either in RRC_IDLE or in RRC_CONNECTED or during state transitions between these states. RAN WG2 would like to additionally inform CT WG1 that RAN WG2 has agreed WB-N1 UEs (eMTC UEs) in RRC_INACTIVE support eDRX up to 10.24s cycles without PTW. WB-N1 also supports coverage enhancements while in RRC_INACTIVE which may affect paging delay and the transition to RRC_CONNECTED state after paging. The maximum delay for state transition is 10s after sending UL RRC message (timer T300 in RRC). This may increase RAN delay compared to the existing delay with RRC_INACTIVE in eLTE, e.g., for delivery of downlink NAS PDU. NB-N1 (NB-IoT) does not support RRC_INACTIVE when connected to 5GC.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":8,"ainumber":"5.1","ainame":"3GPP Packet Access Maintenance","tdoc_agenda_sort_order":10320,"status":"noted","reservation_date":"2020-01-07 11:51:03","uploaded":"2020-01-07 12:14:50","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"RAN WG3, SA WG2","lsoriginalls":"R2-1916623","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2000830.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2000858","title":"MME handling for secondary RAT data reporting.","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"discussion","for":"Agreement","abstract":"This discussion paper discussed the issue when secondary RAT data reporting from source eNB comes later than path switch request from the target eNB, how MME handles the situation.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":8,"ainumber":"5.1","ainame":"3GPP Packet Access Maintenance","tdoc_agenda_sort_order":10330,"status":"noted","reservation_date":"2020-01-07 12:49:31","uploaded":"2020-01-07 13:23:33","revisionof":"","revisedto":"","release":"Rel-16","crspec":"23.401","crspecversion":"","workitem":[{"winame":"TEI16"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2000858.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2000859","title":"Clarification of MME handling for secondary RAT data reporting","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify that in case of X2 handover, when MME received 'path switch request' from target eNB earlier than 'secondary RAT data reporting' from the source eNB, MME may set a timer, and does not release the source eNB context before the timer expires. When receiving the secondary RAT data reporting, but later than 'path switch request', MME stored the reported data locally and sends to SGW in the next S11 signalling message.","secretary_remarks":"Revised in parallel session to S2-2001171.","agenda_item_sort_order":8,"ainumber":"5.1","ainame":"3GPP Packet Access Maintenance","tdoc_agenda_sort_order":10350,"status":"revised","reservation_date":"2020-01-07 12:49:31","uploaded":"2020-01-07 13:23:33","revisionof":"","revisedto":"S2-2001171","release":"Rel-16","crspec":"23.401","crspecversion":"16.5.0","workitem":[{"winame":"TEI16"}],"crnumber":3581.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2000859.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2000928","title":"System support for Wake Up Signal","source":"Vodafone","contact":"Chris Pudney","contact-id":1122,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Description of WUS added along with system aspects added in new section Paging section updated","secretary_remarks":"Revised in parallel session to S2-2001167.","agenda_item_sort_order":8,"ainumber":"5.1","ainame":"3GPP Packet Access Maintenance","tdoc_agenda_sort_order":10400,"status":"revised","reservation_date":"2020-01-07 15:33:32","uploaded":"2020-01-07 15:43:54","revisionof":"","revisedto":"S2-2001167","release":"Rel-15","crspec":"23.401","crspecversion":"15.10.0","workitem":[{"winame":"NB_IOTenh-Core"},{"winame":"CIoT_Ext"}],"crnumber":3582.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2000928.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2001165","title":"WUS indication to MME","source":"Qualcomm Incorprorated","contact":"Haris Zisimopoulos","contact-id":84603,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Based on UEs indication for support of WUS in RRC, the eNB provides an indication in S1 release that UE supports WUS. MME can store and take that indication into account for paging strategy","secretary_remarks":"Revision of S2-2000332. Revised in parallel session to S2-2001346.","agenda_item_sort_order":8,"ainumber":"5.1","ainame":"3GPP Packet Access Maintenance","tdoc_agenda_sort_order":10250,"status":"revised","reservation_date":"2020-01-14 20:13:46","uploaded":"2020-01-18 01:47:53","revisionof":"S2-2000332","revisedto":"S2-2001346","release":"Rel-15","crspec":"23.401","crspecversion":"15.10.0","workitem":[{"winame":"NB_IOTenh-Core"},{"winame":"CIoT_Ext"},{"winame":"LTE_eMTC4-Core"},{"winame":"NB_IOTenh2-Core"}],"crnumber":3575.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2001165.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2001166","title":"WUS indication to MME","source":"Qualcomm Incorprorated","contact":"Haris Zisimopoulos","contact-id":84603,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Based on UEs indication for support of WUS in RRC, the eNB provides an indication in S1 release that UE supports WUS. MME can store and take that indication into account for paging strategy It also clarifies the relationship with WUS Assistance Information in NAS","secretary_remarks":"Revision of S2-2000333. Withdrawn","agenda_item_sort_order":8,"ainumber":"5.1","ainame":"3GPP Packet Access Maintenance","tdoc_agenda_sort_order":10280,"status":"withdrawn","reservation_date":"2020-01-14 20:13:47","uploaded":"2020-01-18 01:47:53","revisionof":"S2-2000333","revisedto":"","release":"Rel-16","crspec":"23.401","crspecversion":"16.5.0","workitem":[{"winame":"NB_IOTenh-Core"},{"winame":"CIoT_Ext"},{"winame":"LTE_eMTC4-Core"},{"winame":"NB_IOTenh2-Core"}],"crnumber":3576.0,"crrevision":1.0,"crcategory":"A","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2001166.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2001167","title":"System support for Wake Up Signal","source":"Vodafone","contact":"Chris Pudney","contact-id":1122,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Description of WUS added along with system aspects added in new section Paging section updated so that, (at least for WUS UE) whenever the MME has the last used Cell ID, the MME sends it to the eNB in the S1-AP Paging message. In the Paging message, the MME uses the 'Assistance Data for Paging' to convey the last used cell ID to the eNB. If the last used eNB did not send the 'Information on Recommended Cells and eNBs for Paging', but the last used eNB did send User Location Information in the S1 association release procedure, then the MME should use this ULI to create the 'Assistance Data for Paging' and place it in the Paging message. The E-UTRAN CGI received in S1-AP Initial UE Message and Path Switch Request messages must not be used by the MME as this cell information would become unreliable following intra eNB mobility, and, the S1-AP Resume procedure does not (yet) carry location information.","secretary_remarks":"Revision of S2-2000928. Revised in parallel session to S2-2001345.","agenda_item_sort_order":8,"ainumber":"5.1","ainame":"3GPP Packet Access Maintenance","tdoc_agenda_sort_order":10410,"status":"revised","reservation_date":"2020-01-14 20:13:49","uploaded":"2020-01-18 01:47:53","revisionof":"S2-2000928","revisedto":"S2-2001168, S2-2001345","release":"Rel-15","crspec":"23.401","crspecversion":"15.10.0","workitem":[{"winame":"NB_IOTenh-Core"},{"winame":"CIoT_Ext"}],"crnumber":3582.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2001167.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2001168","title":"System support for Wake Up Signal","source":"Vodafone","contact":"Chris Pudney","contact-id":1122,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Description of WUS added along with system aspects added in new section Paging section updated so that, (at least for WUS UE) whenever the MME has the last used Cell ID, the MME sends it to the eNB in the S1-AP Paging message. In the Paging message, the MME uses the 'Assistance Data for Paging' to convey the last used cell ID to the eNB. If the last used eNB did not send the 'Information on Recommended Cells and eNBs for Paging', but the last used eNB did send User Location Information in the S1 association release procedure, then the MME should use this ULI to create the 'Assistance Data for Paging' and place it in the Paging message. The E-UTRAN CGI received in S1-AP Initial UE Message and Path Switch Request messages must not be used by the MME as this cell information would become unreliable following intra eNB mobility, and, the S1-AP Resume procedure does not (yet) carry location information. The eNB is specified to use the last used Cell ID to only send the WUS in that cell. If the MME does not send the last used Cell ID, WUS is sent in all the cells.","secretary_remarks":"Created at meeting. Mirror to S2-2001167, but Cat F because it is not an editorial mirror CR to CR 3582. This was left for e-mail approval. e-mail revision 1 approved. Revised to S2-2001686.","agenda_item_sort_order":8,"ainumber":"5.1","ainame":"3GPP Packet Access Maintenance","tdoc_agenda_sort_order":10450,"status":"revised","reservation_date":"2020-01-14 20:13:50","uploaded":"2020-01-18 01:47:53","revisionof":"S2-2001167","revisedto":"S2-2001686","release":"Rel-16","crspec":"23.401","crspecversion":"16.5.0","workitem":[{"winame":"NB_IOTenh-Core"},{"winame":"CIoT_Ext"}],"crnumber":3583.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2001168.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2001169","title":"[DRAFT] Reply LS on assistance indication for WUS","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"LS out","for":"Approval","abstract":"Response LS to (C1-199008) on Reply LS on assistance indication for WUS from CT WG1","secretary_remarks":"Revision of S2-2000726. Revised in parallel session to S2-2001344.","agenda_item_sort_order":8,"ainumber":"5.1","ainame":"3GPP Packet Access Maintenance","tdoc_agenda_sort_order":10190,"status":"revised","reservation_date":"2020-01-14 20:13:54","uploaded":"2020-01-18 01:47:53","revisionof":"S2-2000726","revisedto":"S2-2001344","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"NB_IOTenh3-Core"},{"winame":"LTE_eMTC5-Core"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"RAN WG2, RAN WG3","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2001169.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2001170","title":"WUS assistance clarifications","source":"Qualcomm Incorprorated","contact":"Haris Zisimopoulos","contact-id":84603,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: MME shall provide (i.e. is mandatory) WUS Assistance Information to the UE in every Attach Accept\/TAU Accept message, IF it has stored WUS Assistance Information parameter in the MM context Support for WUS Assistance Information is not signalled at emergency attach and when UE has emergency PDN connection active","secretary_remarks":"Revision of S2-2000335, merging S2-2000337. Agreed in parallel session. Block approved","agenda_item_sort_order":8,"ainumber":"5.1","ainame":"3GPP Packet Access Maintenance","tdoc_agenda_sort_order":10300,"status":"agreed","reservation_date":"2020-01-14 20:13:54","uploaded":"2020-01-18 01:47:53","revisionof":"S2-2000335","revisedto":"","release":"Rel-16","crspec":"23.401","crspecversion":"16.5.0","workitem":[{"winame":"LTE_eMTC5-Core"},{"winame":"NB_IOTenh3-Core"},{"winame":"CIoT_Ext"}],"crnumber":3577.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-200061","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2001170.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2001171","title":"Clarification of MME handling for secondary RAT data reporting","source":"Huawei, HiSilicon, China Unicom","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify that in case of X2 handover, when MME received 'path switch request' from target eNB earlier than 'secondary RAT data reporting' from the source eNB, MME may set a timer, and does not release the source eNB context before the timer expires. When receiving the secondary RAT data reporting, but later than 'path switch request', MME stored the reported data locally and sends to SGW in the next S11 signalling message.","secretary_remarks":"Revision of S2-2000859. Confirm CR Revision - CR states -1! Revised in parallel session to S2-2001564.","agenda_item_sort_order":8,"ainumber":"5.1","ainame":"3GPP Packet Access Maintenance","tdoc_agenda_sort_order":10360,"status":"revised","reservation_date":"2020-01-14 20:13:55","uploaded":"2020-01-18 01:47:53","revisionof":"S2-2000859","revisedto":"S2-2001564","release":"Rel-16","crspec":"23.401","crspecversion":"16.5.0","workitem":[{"winame":"TEI16"}],"crnumber":3581.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2001171.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2001344","title":"[DRAFT] Reply LS on assistance indication for WUS","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"LS out","for":"Approval","abstract":"Response LS to (C1-199008) on Reply LS on assistance indication for WUS from CT WG1","secretary_remarks":"Revision of S2-2001169. Revised in parallel session to S2-2001578.","agenda_item_sort_order":8,"ainumber":"5.1","ainame":"3GPP Packet Access Maintenance","tdoc_agenda_sort_order":10200,"status":"revised","reservation_date":"2020-01-18 01:19:51","uploaded":"2020-01-18 01:57:52","revisionof":"S2-2001169","revisedto":"S2-2001578","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"NB_IOTenh3-Core"},{"winame":"LTE_eMTC5-Core"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"RAN WG2, RAN WG3","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2001344.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2001345","title":"System support for Wake Up Signal","source":"Vodafone","contact":"Chris Pudney","contact-id":1122,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Description of WUS added along with system aspects added in new section Paging section updated so that, (at least for WUS UE) whenever the MME has the last used Cell ID, the MME sends it to the eNB in the S1-AP Paging message. In the Paging message, the MME uses the 'Assistance Data for Paging' to convey the last used cell ID to the eNB. If the last used eNB did not send the 'Information on Recommended Cells and eNBs for Paging', but the last used eNB did send User Location Information in the S1 association release procedure, then the MME should use this ULI to create the 'Assistance Data for Paging' and place it in the Paging message. The E-UTRAN CGI received in S1-AP Initial UE Message and Path Switch Request messages must not be used by the MME as this cell information would become unreliable following intra eNB mobility, and, the S1-AP Resume procedure does not (yet) carry location information.","secretary_remarks":"Revision of S2-2001167. Revised in parallel session to S2-2001579.","agenda_item_sort_order":8,"ainumber":"5.1","ainame":"3GPP Packet Access Maintenance","tdoc_agenda_sort_order":10400,"status":"revised","reservation_date":"2020-01-18 01:19:51","uploaded":"2020-01-18 01:57:52","revisionof":"S2-2001167","revisedto":"S2-2001579","release":"Rel-15","crspec":"23.401","crspecversion":"15.10.0","workitem":[{"winame":"NB_IOTenh-Core"},{"winame":"CIoT_Ext"}],"crnumber":3582.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2001345.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2001346","title":"WUS indication to MME","source":"Qualcomm Incorprorated","contact":"Haris Zisimopoulos","contact-id":84603,"tdoctype":"CR","for":"Approval","abstract":"WITHDRAWN: Summary of change: Based on UEs indication for support of WUS in RRC, the eNB provides an indication in S1 release that UE supports WUS. MME can store and take that indication into account for paging strategy","secretary_remarks":"Revision of S2-2001165. Withdrawn","agenda_item_sort_order":8,"ainumber":"5.1","ainame":"3GPP Packet Access Maintenance","tdoc_agenda_sort_order":10250,"status":"withdrawn","reservation_date":"2020-01-18 01:19:52","uploaded":null,"revisionof":"S2-2001165","revisedto":"","release":"Rel-15","crspec":"23.401","crspecversion":"15.10.0","workitem":[{"winame":"NB_IOTenh-Core"},{"winame":"CIoT_Ext"},{"winame":"LTE_eMTC4-Core"},{"winame":"NB_IOTenh2-Core"}],"crnumber":3575.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2001564","title":"Clarification of MME handling for secondary RAT data reporting","source":"Huawei, HiSilicon, China Unicom","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify that in case of X2 handover, the MME is expected to handle the secondary RAT data reporting from the source eNB after Path Switch Request (MME maintains the source eNB context for a certain time)..","secretary_remarks":"Revision of S2-2001171. Revised in parallel session to S2-2001580.","agenda_item_sort_order":8,"ainumber":"5.1","ainame":"3GPP Packet Access Maintenance","tdoc_agenda_sort_order":10360,"status":"revised","reservation_date":"2020-01-18 01:20:00","uploaded":"2020-01-18 02:07:52","revisionof":"S2-2001171","revisedto":"S2-2001580","release":"Rel-16","crspec":"23.401","crspecversion":"16.5.0","workitem":[{"winame":"TEI16"}],"crnumber":3581.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2001564.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2001578","title":"Reply LS on assistance indication for WUS","source":"SA WG2","contact":"Steven Wenham","contact-id":48132,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG1, RAN WG2, RAN WG3. Attachments: TS 23.401 CR 3582 (S2-2001579).","secretary_remarks":"Revision of S2-2001344. Agreed in parallel session. Block approved. Revised to add updated attachment in S2-2001732.","agenda_item_sort_order":8,"ainumber":"5.1","ainame":"3GPP Packet Access Maintenance","tdoc_agenda_sort_order":10210,"status":"revised","reservation_date":"2020-01-18 01:20:12","uploaded":"2020-01-18 02:07:52","revisionof":"S2-2001344","revisedto":"S2-2001732","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"NB_IOTenh3-Core"},{"winame":"LTE_eMTC5-Core"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1, RAN WG2, RAN WG3","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2001578.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2001579","title":"System support for Wake Up Signal","source":"Vodafone","contact":"Chris Pudney","contact-id":1122,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Description of WUS added along with system aspects added in new section Paging section updated so that, (at least for WUS UE) whenever the MME has the last used Cell ID, the MME sends it to the eNB in the S1-AP Paging message. In the Paging message, the MME uses the 'Assistance Data for Paging' to convey the last used cell ID to the eNB. If the last used eNB did not send the 'Information on Recommended Cells and eNBs for Paging', but the last used eNB did send User Location Information in the S1 association release procedure, then the MME should use this ULI to create the 'Assistance Data for Paging' and place it in the Paging message. The E-UTRAN CGI received in S1-AP Initial UE Message and Path Switch Request messages must not be used by the MME as this cell information would become unreliable following intra eNB mobility, and, the S1-AP Resume procedure does not (yet) carry location information. The eNB is specified to use the last used Cell ID to only send the WUS in that cell. If the MME does not send the last used Cell ID, WUS is sent in all the cells.","secretary_remarks":"Revision of S2-2001345. This was left for e-mail approval. e-mail revision 10 approved. Revised to S2-2001691.","agenda_item_sort_order":8,"ainumber":"5.1","ainame":"3GPP Packet Access Maintenance","tdoc_agenda_sort_order":10420,"status":"revised","reservation_date":"2020-01-18 01:20:12","uploaded":"2020-01-18 02:07:52","revisionof":"S2-2001345","revisedto":"S2-2001691","release":"Rel-15","crspec":"23.401","crspecversion":"15.10.0","workitem":[{"winame":"NB_IOTenh-Core"},{"winame":"CIoT_Ext"}],"crnumber":3582.0,"crrevision":3.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2001579.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2001580","title":"Clarification of MME handling for secondary RAT data reporting","source":"Huawei, HiSilicon, China Unicom","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: In case of X2 handover, the MME is expected to handle a secondary RAT data reporting from the source eNB after Path Switch Request. MME shall store the secondary RAT usage data (e.g. by maintaining the source eNB context for a certain time) and forward it to the SGW in the next signalling message or by using the GW Secondary RAT usage data Reporting procedure. This applies to previous release as well.","secretary_remarks":"Revision of S2-2001564. This was left for e-mail approval. e-mail revision 1 approved. Revised to S2-2001692.","agenda_item_sort_order":8,"ainumber":"5.1","ainame":"3GPP Packet Access Maintenance","tdoc_agenda_sort_order":10370,"status":"revised","reservation_date":"2020-01-18 01:20:13","uploaded":"2020-01-18 02:07:52","revisionof":"S2-2001564","revisedto":"S2-2001692","release":"Rel-16","crspec":"23.401","crspecversion":"16.5.0","workitem":[{"winame":"TEI16"}],"crnumber":3581.0,"crrevision":3.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2001580.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2001686","title":"System support for Wake Up Signal","source":"Vodafone","contact":"Chris Pudney","contact-id":1122,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Description of WUS added along with system aspects added in new section Paging section updated so that, (at least for WUS UE) whenever the MME has the last used Cell ID, the MME sends it to the eNB in the S1-AP Paging message. In the Paging message, the MME uses the 'Assistance Data for Paging' to convey the last used cell ID to the eNB. If the last used eNB did not send the 'Information on Recommended Cells and eNBs for Paging', but the last used eNB did send User Location Information in the S1 association release procedure, then the MME should use this ULI to create the 'Assistance Data for Paging' and place it in the Paging message. The E-UTRAN CGI received in S1-AP Initial UE Message and Path Switch Request messages must not be used by the MME as this cell information would become unreliable following intra eNB mobility, and, the S1-AP Resume procedure does not (yet) carry location information. The eNB is specified to use the last used Cell ID to only send the WUS in that cell. If the MME does not send the last used Cell ID, WUS is sent in all the cells.","secretary_remarks":"e-mail revision 1 of S2-2001168. This CR was agreed. (Functional mirror to CR3582)","agenda_item_sort_order":8,"ainumber":"5.1","ainame":"3GPP Packet Access Maintenance","tdoc_agenda_sort_order":10460,"status":"agreed","reservation_date":"2020-01-27 09:23:46","uploaded":"2020-01-27 09:28:18","revisionof":"S2-2001168","revisedto":"","release":"Rel-16","crspec":"23.401","crspecversion":"16.5.0","workitem":[{"winame":"NB_IOTenh-Core"},{"winame":"CIoT_Ext"}],"crnumber":3583.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-200061","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2001686.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2001691","title":"System support for Wake Up Signal","source":"Vodafone","contact":"Chris Pudney","contact-id":1122,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Description of WUS added along with system aspects added in new section Paging section updated so that, (at least for WUS UE) whenever the MME has the last used Cell ID, the MME sends it to the eNB in the S1-AP Paging message. In the Paging message, the MME uses the 'Assistance Data for Paging' to convey the last used cell ID to the eNB. If the last used eNB did not send the 'Information on Recommended Cells and eNBs for Paging', but the last used eNB did send User Location Information in the S1 association release procedure, then the MME should use this ULI to create the 'Assistance Data for Paging' and place it in the Paging message. The E-UTRAN CGI received in S1-AP Initial UE Message and Path Switch Request messages must not be used by the MME as this cell information would become unreliable following intra eNB mobility, and, the S1-AP Resume procedure does not (yet) carry location information. The eNB is specified to use the last used Cell ID to only send the WUS in that cell. If the MME does not send the last used Cell ID, WUS is sent in all the cells.","secretary_remarks":"e-mail revision 10 of S2-2001579. This CR was agreed. Revised at S2#137E in S2-2002119 (agreed)","agenda_item_sort_order":8,"ainumber":"5.1","ainame":"3GPP Packet Access Maintenance","tdoc_agenda_sort_order":10440,"status":"revised","reservation_date":"2020-01-27 09:23:53","uploaded":"2020-01-27 09:28:18","revisionof":"S2-2001579","revisedto":"S2-2002119","release":"Rel-15","crspec":"23.401","crspecversion":"15.10.0","workitem":[{"winame":"NB_IOTenh-Core"},{"winame":"CIoT_Ext"}],"crnumber":3582.0,"crrevision":4.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2001691.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2001692","title":"Clarification of MME handling for secondary RAT data reporting","source":"Huawei, HiSilicon, China Unicom","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: In case of X2 handover, the MME is expected to handle a secondary RAT data reporting from the source eNB after Path Switch Request. MME shall store the secondary RAT usage data (e.g. by maintaining the source eNB context for a certain time) and forward it to the SGW in the next signalling message or by using the GW Secondary RAT usage data Reporting procedure. This applies to previous release as well.","secretary_remarks":"e-mail revision 1 of S2-2001580. This CR was agreed","agenda_item_sort_order":8,"ainumber":"5.1","ainame":"3GPP Packet Access Maintenance","tdoc_agenda_sort_order":10390,"status":"agreed","reservation_date":"2020-01-27 09:23:54","uploaded":"2020-01-27 09:28:18","revisionof":"S2-2001580","revisedto":"","release":"Rel-16","crspec":"23.401","crspecversion":"16.5.0","workitem":[{"winame":"TEI16"}],"crnumber":3581.0,"crrevision":4.0,"crcategory":"F","tsg_crp":"SP-200081","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2001692.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2001732","title":"Reply LS on assistance indication for WUS","source":"SA WG2","contact":"Steven Wenham","contact-id":48132,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG1, RAN WG2, RAN WG3. Attachments: TS 23.401 CR 3582 (S2-2001691).","secretary_remarks":"Revision of S2-2001578. Approved","agenda_item_sort_order":8,"ainumber":"5.1","ainame":"3GPP Packet Access Maintenance","tdoc_agenda_sort_order":10220,"status":"approved","reservation_date":"2020-01-27 11:01:03","uploaded":"2020-01-27 11:02:04","revisionof":"S2-2001578","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"LTE_eMTC5-Core"},{"winame":"NB_IOTenh3-Core"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2000021","lsto":"CT WG1, RAN WG2, RAN WG3","Cc":"","lsoriginalls":"","lsreply":"R3-200193","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136AH_Incheon\/Docs\/S2-2001732.zip","group":"S2","meeting":"S2-ah-35699","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]