[{"name":"S2-1910867","title":"LS from SA WG4: LS on Group Message Delivery","source":"SA WG4","contact":"Peter Sanders","contact-id":33850,"tdoctype":"LS in","for":"Action","abstract":"SA WG4 thanks SA WG2 for the LS on 'Group Message Delivery' in which SA WG2 assumes that SA WG4 will specify the group identifier over xMB if not already specified. SA WG4 would like to inform SA WG2 that the Session Resource ID (as provided in Create Session response, Clause 5.4.2 in TS 26.348) identifies a session uniquely and that therefore a session can be mapped to a specific group. Note, that an MBMS broadcast bearer cannot address specific UEs in a group, it can only broadcast in a Service Area and the UEs, which are inside that Service Area, can receive the content. The Session Resource ID represents an MBMS streaming or download session, which targets a certain MBMS Service Area via a TMGI and an MBMS Service Area description. MBMS UEs, which have received the service announcement information including the TMGI for this MBMS streaming or download session, can activate the reception for that session and receive the content. Action: SA WG4 asks SA WG2 group to take the above information into consideration.","secretary_remarks":"Postponed S2-1908719 from S2#135. 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":"2019-10-30 08:52:12","uploaded":"2019-11-04 09:40:45","revisionof":"S2-1908719","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"CT WG3","lsoriginalls":"S4-191002","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1910867.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1910893","title":"LS from RAN WG2: Reply LS on FR2 Pmax","source":"RAN WG2","contact":"Brian Martin","contact-id":72959,"tdoctype":"LS in","for":"Information","abstract":"RAN WG2 thanks RAN WG4 on their LS which has resulted in the following agreements in RAN WG2: - R2 assumes that for FR2, Rel-15 UE ignores broadcasted Pmax if any - R2 assumes that for FR2, Rel-15 UE set Pcompensation = 0 The attached CRs have been agreed in principle to address this.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":8,"ainumber":"5.1","ainame":"3GPP Packet Access Maintenance","tdoc_agenda_sort_order":10180,"status":"noted","reservation_date":"2019-10-30 09:03:47","uploaded":"2019-11-04 09:40:45","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG4","Cc":"","lsoriginalls":"R2-1914222","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1910893.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911024","title":"Corrections to LCS Assistance Data Broadcast procedure","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Modify the procedure in 23.271 sec 9.3a.4 to make it bidirectional. The pattern from the bidirectional procedure in 9.3a.3 'Obtaining Non-UE Associated Network Assistance Data' is reused to avoid stage 3 impact.","secretary_remarks":"Agreed in parallel session. Block approved","agenda_item_sort_order":8,"ainumber":"5.1","ainame":"3GPP Packet Access Maintenance","tdoc_agenda_sort_order":10200,"status":"agreed","reservation_date":"2019-11-05 21:40:48","uploaded":"2019-11-08 04:33:34","revisionof":"","revisedto":"","release":"Rel-15","crspec":"23.271","crspecversion":"15.1.0","workitem":[{"winame":"TEI15"}],"crnumber":435.0,"crrevision":"","crcategory":"F","tsg_crp":"SP-191067","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911024.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911132","title":"EPC awareness of WUS","source":"NTT DOCOMO INC.","contact":"Kenichiro Aoyagi","contact-id":73277,"tdoctype":"CR","for":"","abstract":"Summary of change: The MME is aware of WUS (both grouping and non grouping) applied or not, and may be configured to take it into account","secretary_remarks":"Postponed in parallel session","agenda_item_sort_order":8,"ainumber":"5.1","ainame":"3GPP Packet Access Maintenance","tdoc_agenda_sort_order":10200,"status":"postponed","reservation_date":"2019-11-07 04:44:37","uploaded":"2019-11-08 05:16:39","revisionof":"","revisedto":"S2-2000337","release":"Rel-16","crspec":"23.401","crspecversion":"16.4.0","workitem":[{"winame":"TEI16"},{"winame":"LTE_eMTC5-Core"},{"winame":"NB_IOTenh3-Core"}],"crnumber":3559.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911132.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911506","title":"UE reachability monitoring correction","source":"Nokia, Nokia Shanghai Bell, Ericsson","contact":"Hannu Hietalahti","contact-id":69922,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Immediate reporting of UE reachability during PSM with Active Time is allowed and the Monitoring Event Report parameters is included in the call flows consistently.","secretary_remarks":"Agreed in parallel session. Block approved","agenda_item_sort_order":8,"ainumber":"5.1","ainame":"3GPP Packet Access Maintenance","tdoc_agenda_sort_order":10220,"status":"agreed","reservation_date":"2019-11-08 08:45:36","uploaded":"2019-11-08 12:01:28","revisionof":"","revisedto":"","release":"Rel-16","crspec":"23.682","crspecversion":"16.4.0","workitem":[{"winame":"TEI16"},{"winame":"CIoT"}],"crnumber":464.0,"crrevision":"","crcategory":"F","tsg_crp":"SP-191089","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911506.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911755","title":"Assistance indication for WUS grouping","source":"Huawei, HiSilicon, Sony","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The wake up signal (WUS) Assistance Information is added to support wake up signal paging.","secretary_remarks":"Revision of S2-1910191 from S2#135. Agreed in parallel session. Block approved","agenda_item_sort_order":8,"ainumber":"5.1","ainame":"3GPP Packet Access Maintenance","tdoc_agenda_sort_order":10230,"status":"agreed","reservation_date":"2019-11-08 14:07:58","uploaded":"2019-11-08 16:01:47","revisionof":"S2-1910191","revisedto":"","release":"Rel-16","crspec":"23.401","crspecversion":"16.4.0","workitem":[{"winame":"NB_IOTenh3-Core"},{"winame":"LTE_eMTC5-Core"},{"winame":"TEI16"}],"crnumber":3538.0,"crrevision":5.0,"crcategory":"F","tsg_crp":"SP-191089","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911755.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911763","title":"Alignment with SA WG4 for using Resource ID in xMB","source":"Qualcomm Incorporated","contact":"Haris Zisimopoulos","contact-id":84603,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Aligns with the answer with xMB specification TS 26.346 to use Session Resource ID Fixes references (no rel.15 version of TS 26.348). xMB procedures in rel.15 are documented in TS 26.346","secretary_remarks":"Agreed in parallel session. Block approved","agenda_item_sort_order":8,"ainumber":"5.1","ainame":"3GPP Packet Access Maintenance","tdoc_agenda_sort_order":10240,"status":"agreed","reservation_date":"2019-11-08 14:35:07","uploaded":"2019-11-08 18:40:56","revisionof":"","revisedto":"","release":"Rel-15","crspec":"23.682","crspecversion":"15.9.0","workitem":[{"winame":"NAPS"},{"winame":"TEI15"}],"crnumber":465.0,"crrevision":"","crcategory":"F","tsg_crp":"SP-191067","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911763.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911766","title":"Alignment with SA WG4 for using Resource ID in xMB","source":"Qualcomm Incorporated","contact":"Haris Zisimopoulos","contact-id":84603,"tdoctype":"CR","for":"Approval","abstract":"Rel-16 mirror CR: Summary of change: Aligns with the answer with xMB specification TS 26.348 to use Session Resource ID","secretary_remarks":"Agreed in parallel session. Block approved","agenda_item_sort_order":8,"ainumber":"5.1","ainame":"3GPP Packet Access Maintenance","tdoc_agenda_sort_order":10250,"status":"agreed","reservation_date":"2019-11-08 14:38:27","uploaded":"2019-11-08 18:40:56","revisionof":"","revisedto":"","release":"Rel-16","crspec":"23.682","crspecversion":"16.4.0","workitem":[{"winame":"TEI15"},{"winame":"NAPS"}],"crnumber":466.0,"crrevision":"","crcategory":"A","tsg_crp":"SP-191067","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911766.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911855","title":"System support for NB-IoT Paging across Multiple Carriers and WB-EUTRAN <-> NB-IoT mobility","source":"Vodafone","contact":"Chris Pudney","contact-id":1122,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: it is clarified that some RAN features now make the MME handling of UE Radio Capability for Paging mandatory, and, the MME stores seperate information for NB-IoT and WB-E-UTRAN the MME deletes this information at Attach (and first TAU).","secretary_remarks":"Revised in parallel session to S2-1912258.","agenda_item_sort_order":8,"ainumber":"5.1","ainame":"3GPP Packet Access Maintenance","tdoc_agenda_sort_order":10250,"status":"revised","reservation_date":"2019-11-08 16:51:19","uploaded":"2019-11-08 17:03:50","revisionof":"","revisedto":"S2-1912258","release":"Rel-14","crspec":"23.401","crspecversion":"14.10.0","workitem":[{"winame":"NB_IOTenh-Core"},{"winame":"CIoT_Ext"}],"crnumber":3565.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911855.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911875","title":"System support for NB-IoT Paging across Multiple Carriers and\/or WUS with WB-EUTRAN <-> NB-IoT mobility","source":"Vodafone","contact":"Chris Pudney","contact-id":1122,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: it is clarified that some RAN features now make the MME handling of UE Radio Capability for Paging mandatory, and, the MME stores seperate information for NB-IoT and WB-E-UTRAN the MME deletes this information at Attach (and first TAU).","secretary_remarks":"Revised in parallel session to S2-1912260.","agenda_item_sort_order":8,"ainumber":"5.1","ainame":"3GPP Packet Access Maintenance","tdoc_agenda_sort_order":10290,"status":"revised","reservation_date":"2019-11-08 17:19:09","uploaded":"2019-11-08 17:33:46","revisionof":"","revisedto":"S2-1912260","release":"Rel-15","crspec":"23.401","crspecversion":"15.9.0","workitem":[{"winame":"NB_IOTenh-Core"},{"winame":"CIoT_Ext"},{"winame":"LTE_eMTC4-Core"},{"winame":"NB_IOTenh2-Core"}],"crnumber":3567.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911875.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911931","title":"System support for NB-IoT Paging across Multiple Carriers and\/or WUS with WB-EUTRAN <-> NB-IoT mobility","source":"Vodafone","contact":"Chris Pudney","contact-id":1122,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: it is clarified that some RAN features now make the MME handling of UE Radio Capability for Paging mandatory, and, the MME stores seperate information for NB-IoT and WB-E-UTRAN the MME deletes this information at Attach (and first TAU).","secretary_remarks":"LATE DOC: Rx 20\/11. Revised in parallel session to S2-1912298.","agenda_item_sort_order":8,"ainumber":"5.1","ainame":"3GPP Packet Access Maintenance","tdoc_agenda_sort_order":10320,"status":"revised","reservation_date":"2019-11-08 23:42:32","uploaded":"2019-11-25 15:57:54","revisionof":"","revisedto":"S2-1912298","release":"Rel-16","crspec":"23.401","crspecversion":"16.4.0","workitem":[{"winame":"NB_IOTenh"},{"winame":"CIoT_Ext"},{"winame":"LTE_eMTC4-Core"},{"winame":"NB_IOTenh2-Core"}],"crnumber":3571.0,"crrevision":"","crcategory":"A","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911931.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911952","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":"This LS was postponed.","agenda_item_sort_order":8,"ainumber":"5.1","ainame":"3GPP Packet Access Maintenance","tdoc_agenda_sort_order":10340,"status":"postponed","reservation_date":"2019-11-16 06:41:55","uploaded":"2019-11-16 06:42:42","revisionof":"","revisedto":"S2-2000021","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, RAN WG2, RAN WG3","Cc":"","lsoriginalls":"C1-199008","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911952.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1912258","title":"System support for NB-IoT Paging across Multiple Carriers and WB-EUTRAN <-> NB-IoT mobility","source":"Vodafone","contact":"Chris Pudney","contact-id":1122,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: it is clarified that some RAN features now make the MME handling of UE Radio Capability for Paging mandatory, and, the MME stores seperate information for NB-IoT and WB-E-UTRAN the MME deletes this information at Attach (and first TAU).","secretary_remarks":"Revision of S2-1911855. Revised in parallel session to S2-1912296.","agenda_item_sort_order":8,"ainumber":"5.1","ainame":"3GPP Packet Access Maintenance","tdoc_agenda_sort_order":10270,"status":"revised","reservation_date":"2019-11-21 16:37:36","uploaded":"2019-11-25 15:57:55","revisionof":"S2-1911855","revisedto":"S2-1912296","release":"Rel-14","crspec":"23.401","crspecversion":"14.10.0","workitem":[{"winame":"NB_IOTenh-Core"},{"winame":"CIoT_Ext"}],"crnumber":3565.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1912258.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1912259","title":"Deletion of 'UE Radio Capability for Paging Information' at Detach\/Attach","source":"Vodafone","contact":"Chris Pudney","contact-id":1122,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: it is clarified that the MME deletes this information at Attach (and first TAU in the RAT).","secretary_remarks":"Rel-13 base CR created at meeting. Agreed in parallel session. Block approved","agenda_item_sort_order":8,"ainumber":"5.1","ainame":"3GPP Packet Access Maintenance","tdoc_agenda_sort_order":10270,"status":"agreed","reservation_date":"2019-11-21 16:37:37","uploaded":"2019-11-25 15:57:55","revisionof":"","revisedto":"","release":"Rel-13","crspec":"23.401","crspecversion":"13.13.0","workitem":[{"winame":"CIoT"}],"crnumber":3573.0,"crrevision":"","crcategory":"F","tsg_crp":"SP-191065","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1912259.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1912260","title":"System support for NB-IoT Paging across Multiple Carriers and\/or WUS with WB-EUTRAN <-> NB-IoT mobility","source":"Vodafone","contact":"Chris Pudney","contact-id":1122,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: it is clarified that some RAN features now make the MME handling of UE Radio Capability for Paging mandatory, and, the MME stores seperate information for NB-IoT and WB-E-UTRAN the MME deletes this information at Attach (and first TAU).","secretary_remarks":"Revision of S2-1911875. Revised in parallel session to S2-1912297.","agenda_item_sort_order":8,"ainumber":"5.1","ainame":"3GPP Packet Access Maintenance","tdoc_agenda_sort_order":10300,"status":"revised","reservation_date":"2019-11-21 16:37:42","uploaded":"2019-11-25 15:57:55","revisionof":"S2-1911875","revisedto":"S2-1912297","release":"Rel-15","crspec":"23.401","crspecversion":"15.9.0","workitem":[{"winame":"NB_IOTenh-Core"},{"winame":"CIoT_Ext"},{"winame":"LTE_eMTC4-Core"},{"winame":"NB_IOTenh2-Core"}],"crnumber":3567.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1912260.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1912296","title":"System support for NB-IoT Paging across Multiple Carriers and WB-EUTRAN <-> NB-IoT mobility","source":"Vodafone","contact":"Chris Pudney","contact-id":1122,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: it is clarified that some RAN features now make the MME handling of UE Radio Capability for Paging mandatory, and, the MME stores seperate information for NB-IoT and WB-E-UTRAN the MME deletes this information at Attach (and first TAU).","secretary_remarks":"Revision of S2-1912258. Agreed in parallel session.. Block approved","agenda_item_sort_order":8,"ainumber":"5.1","ainame":"3GPP Packet Access Maintenance","tdoc_agenda_sort_order":10290,"status":"agreed","reservation_date":"2019-11-25 15:19:11","uploaded":"2019-11-25 16:07:54","revisionof":"S2-1912258","revisedto":"","release":"Rel-14","crspec":"23.401","crspecversion":"14.10.0","workitem":[{"winame":"NB_IOTenh-Core"},{"winame":"CIoT_Ext"}],"crnumber":3565.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"SP-191065","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1912296.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1912297","title":"System support for NB-IoT Paging across Multiple Carriers and\/or WUS with WB-EUTRAN <-> NB-IoT mobility","source":"Vodafone","contact":"Chris Pudney","contact-id":1122,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: it is clarified that some RAN features now make the MME handling of UE Radio Capability for Paging mandatory, and, the MME stores seperate information for NB-IoT and WB-E-UTRAN the MME deletes this information at Attach (and first TAU).","secretary_remarks":"Revision of S2-1912260. Agreed in parallel session. Block approved","agenda_item_sort_order":8,"ainumber":"5.1","ainame":"3GPP Packet Access Maintenance","tdoc_agenda_sort_order":10320,"status":"agreed","reservation_date":"2019-11-25 15:19:12","uploaded":"2019-11-25 16:07:54","revisionof":"S2-1912260","revisedto":"","release":"Rel-15","crspec":"23.401","crspecversion":"15.9.0","workitem":[{"winame":"NB_IOTenh-Core"},{"winame":"CIoT_Ext"},{"winame":"LTE_eMTC4-Core"},{"winame":"NB_IOTenh2-Core"}],"crnumber":3567.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"SP-191065","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1912297.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1912298","title":"System support for NB-IoT Paging across Multiple Carriers and\/or WUS with WB-EUTRAN <-> NB-IoT mobility","source":"Vodafone","contact":"Chris Pudney","contact-id":1122,"tdoctype":"CR","for":"Approval","abstract":"Rel-16 mirror CR: Summary of change: it is clarified that some RAN features now make the MME handling of UE Radio Capability for Paging mandatory, and, the MME stores seperate information for NB-IoT and WB-E-UTRAN the MME deletes this information at Attach (and first TAU).","secretary_remarks":"Revision of S2-1911931. Agreed in parallel session. Block approved","agenda_item_sort_order":8,"ainumber":"5.1","ainame":"3GPP Packet Access Maintenance","tdoc_agenda_sort_order":10340,"status":"agreed","reservation_date":"2019-11-25 15:19:13","uploaded":"2019-11-25 16:07:54","revisionof":"S2-1911931","revisedto":"","release":"Rel-16","crspec":"23.401","crspecversion":"16.4.0","workitem":[{"winame":"NB_IOTenh"},{"winame":"CIoT_Ext"},{"winame":"LTE_eMTC4-Core"},{"winame":"NB_IOTenh2-Core"}],"crnumber":3571.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-191065","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1912298.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]