[{"name":"S2-1811620","title":"LS from RAN WG2: Reply LS on Dynamic PLR Allocation in eVoLP","source":"RAN WG2","contact":"Masato Kitazoe","contact-id":29801,"tdoctype":"LS in","for":"Information","abstract":"RAN WG2 would like to thank SA WG4 for their LS on Dynamic PLR Allocation in eVoLP, and SA WG2 for their LS on FS_eVoLP. RAN WG2 would like to provide the following feedback. 1. For recommendation 3) Signalling to eNB RRC signalling is capable of carrying UL PLR and DL PLR from the UE to the eNB. The signalling could be as dynamic as every few hundred ms or larger, depending on the signalling load the air interface can accommodate. However, the frequency of RRC signalling is a concern from RAN WG2 point of view. 2. For recommendation 4) Adapting thresholds for SRVCC handovers at RAN node based on UE signal SA WG4 indicated that 'This framework enables further optimizations of the SRVCC thresholds for DL and UL after setting of the DL PLR and UL PLR thresholds at the eNB based on the SA WG2-defined signalling from the PCRF.' RAN WG2 therefore understand that the intention is to provide the information more frequently to the eNB for better SRVCC threshold adaption. One of the concerns is then how quickly the eNB can perform the adaptation and how to avoid unnecessary signalling from the UE. As already described above, RAN WG2's main concern is about the RRC signalling overhead. Also some companies in RAN WG2 expressed concerns on the complexity of the mechanism. RAN WG2 does not intend to analyse the benefits of the mechanism discussed by SA WG4 and therefore this LS does not imply RAN WG2 consensus on whether to introduce the mechanism in the future.","secretary_remarks":"Postponed S2-1811226 from S2#129. Noted in parallel session","agenda_item_sort_order":11,"ainumber":"5.4","ainame":"IMS and IMS-Related Maintenance","tdoc_agenda_sort_order":10090,"status":"noted","reservation_date":"2018-10-31 19:40:32","uploaded":"2018-11-21 06:04:14","revisionof":"S2-1811226","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG4","Cc":"SA WG2","lsoriginalls":"R2-1816041","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_129BIS_West_Palm_Beach\/Docs\/S2-1811620.zip","group":"S2","meeting":"S2-129","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1811737","title":"Missing Data Off requirement for non-IP PDN connection","source":"Ericsson, Telecom Italia, Intel, Deutsche Telekom","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add the missing aspect of data off handling for non-IP PDN connection.","secretary_remarks":"Revision of S2-1810913 from S2-129. Agreed in parallel session. This was Block approved","agenda_item_sort_order":11,"ainumber":"5.4","ainame":"IMS and IMS-Related Maintenance","tdoc_agenda_sort_order":10100,"status":"agreed","reservation_date":"2018-11-17 14:43:04","uploaded":"2018-11-20 13:43:50","revisionof":"S2-1810913","revisedto":"","release":"Rel-14","crspec":23.221,"crspecversion":"14.1.0","workitem":[{"winame":"PS_Data_Off"}],"crnumber":180.0,"crrevision":1.0,"crcategory":"C","tsg_crp":"SP-181080","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_129BIS_West_Palm_Beach\/Docs\/S2-1811737.zip","group":"S2","meeting":"S2-129","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1812051","title":"Reporting PS Data Off status change when SM back off timer is running","source":"Intel, Ericsson, LG Electronics, Telecom Italia, Deutsche Telekom","contact":"Changhong Shan","contact-id":45586,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The SMF shall not reject PDU Session Modification Request for reporting of Data Off activation even if congestion control applies. In clause 5.2.4, when back off timer is described, provide a reference to the clauses for congestion control.","secretary_remarks":"Agreed in parallel session. This was Block approved","agenda_item_sort_order":11,"ainumber":"5.4","ainame":"IMS and IMS-Related Maintenance","tdoc_agenda_sort_order":10110,"status":"agreed","reservation_date":"2018-11-20 00:40:37","uploaded":"2018-11-20 06:04:55","revisionof":"S2-1810986","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.3.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":628.0,"crrevision":3.0,"crcategory":"F","tsg_crp":"SP-181089","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_129BIS_West_Palm_Beach\/Docs\/S2-1812051.zip","group":"S2","meeting":"S2-129","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]