[{"name":"C1A160005","title":"LS on extension of search for higher priority PLMN cycle beyond 8 hours (R2-161945)","source":"RAN2","contact":"Frederic Firmin","contact-id":53384,"tdoctype":"LS in","for":"","abstract":"RAN2 have discussed the idle mode behaviour of NB-IoT terminals and possible implication on UE requirements defined in TS 36.304.\n\nDuring the discussion it was noted that the UE in idle mode is required to perform the search for higher priority PLMN as","secretary_remarks":"","agenda_item_sort_order":3,"ainumber":"3","ainame":"Input LS","tdoc_agenda_sort_order":50,"status":"replied to","reservation_date":"2016-04-18 14:41:36","uploaded":"2016-04-18 14:42:22","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"C1A160029, C1A160029, C1A160091","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG1_mm-cc-sm_ex-CN1\/adhocMeetings\/2016-04-25-adhoc_IoT\/Docs\/C1A160005.zip","group":"C1","meeting":"C1-ah-32099","year":2016,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"C1A160006","title":"Reply LS on NB-IoT work progress in RAN2 (S2-161331)","source":"SA2","contact":"Frederic Firmin","contact-id":53384,"tdoctype":"LS in","for":"","abstract":"SA2 thanks RAN2 and CT1 for their respective LSs S2-161099 and S2-161091. SA2 would like to take the opportunity to reply to both since there are related considerations.\n\nSA2 understanding is that the \u201cdelayTolerantAccess\u201d RRC establishment cause is cur","secretary_remarks":"","agenda_item_sort_order":3,"ainumber":"3","ainame":"Input LS","tdoc_agenda_sort_order":60,"status":"replied to","reservation_date":"2016-04-19 06:14:41","uploaded":"2016-04-19 06:17:49","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"C1A160068, C1A160068, C1A160126, C1A160130, C1A160131","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG1_mm-cc-sm_ex-CN1\/adhocMeetings\/2016-04-25-adhoc_IoT\/Docs\/C1A160006.zip","group":"C1","meeting":"C1-ah-32099","year":2016,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"C1A160007","title":"Response LS on Reply LS on questions on NB-IOT (R3-161032)","source":"RAN3","contact":"Frederic Firmin","contact-id":53384,"tdoctype":"LS in","for":"","abstract":"RAN3 has discussed at RAN3#91bis the liaison referenced above about assisting the MME in its NAS signalling message retransmission strategies by providing eNB information to the MME e.g. coverage level during every S1 connection establishment.\n\nRAN3 has","secretary_remarks":"","agenda_item_sort_order":3,"ainumber":"3","ainame":"Input LS","tdoc_agenda_sort_order":70,"status":"postponed","reservation_date":"2016-04-19 06:15:53","uploaded":"2016-04-19 06:17:49","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG1_mm-cc-sm_ex-CN1\/adhocMeetings\/2016-04-25-adhoc_IoT\/Docs\/C1A160007.zip","group":"C1","meeting":"C1-ah-32099","year":2016,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"C1A160008","title":"LS on NB-IoT Progress in RAN3 (R3-161034)","source":"RAN3","contact":"Frederic Firmin","contact-id":53384,"tdoctype":"LS in","for":"","abstract":"Information from RAN3-agreement","secretary_remarks":"","agenda_item_sort_order":3,"ainumber":"3","ainame":"Input LS","tdoc_agenda_sort_order":80,"status":"noted","reservation_date":"2016-04-19 06:17:16","uploaded":"2016-04-19 06:17:49","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG1_mm-cc-sm_ex-CN1\/adhocMeetings\/2016-04-25-adhoc_IoT\/Docs\/C1A160008.zip","group":"C1","meeting":"C1-ah-32099","year":2016,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"C1A160016","title":"LS on Active flag handling for Control Plane CIoT Optimization (S2-162061)","source":"SA2","contact":"Frederic Firmin","contact-id":53384,"tdoctype":"LS in","for":"","abstract":"SA2 discussed an issue on handling of TAU procedure when uplink data via control plane is pending:\n\nSA2 politely asks the following question:\nIs a UE allowed to send data via NAS before the completion of TAU procedure?","secretary_remarks":"","agenda_item_sort_order":3,"ainumber":"3","ainame":"Input LS","tdoc_agenda_sort_order":160,"status":"replied to","reservation_date":"2016-04-21 14:13:18","uploaded":"2016-04-21 14:15:47","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"C1A160062, C1A160043, C1A160062","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG1_mm-cc-sm_ex-CN1\/adhocMeetings\/2016-04-25-adhoc_IoT\/Docs\/C1A160016.zip","group":"C1","meeting":"C1-ah-32099","year":2016,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"C1A160017","title":"Reply LS on CIoT optimization for non-NB-IoT UEs (S2-162233)","source":"SA2","contact":"Frederic Firmin","contact-id":53384,"tdoctype":"LS in","for":"","abstract":"","secretary_remarks":"","agenda_item_sort_order":3,"ainumber":"3","ainame":"Input LS","tdoc_agenda_sort_order":170,"status":"replied to","reservation_date":"2016-04-21 14:15:15","uploaded":"2016-04-21 14:15:47","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"C1A160069, C1A160069, C1A160111","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG1_mm-cc-sm_ex-CN1\/adhocMeetings\/2016-04-25-adhoc_IoT\/Docs\/C1A160017.zip","group":"C1","meeting":"C1-ah-32099","year":2016,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"C1A160024","title":"Reply LS on per-UE configuration to allow exception reporting (R2-163047)","source":"RAN2","contact":"Frederic Firmin","contact-id":53384,"tdoctype":"LS in","for":"","abstract":"RAN2 would like to provide the following answers to the questions raised by SA2:\n\u201cQ1: SA2 would like to ask whether the UE setting of \u201cmo-ExceptionData\u201d is foreseen to be dependent on NAS configuration?\u201d\nRAN 2 Answer: How the UE is configured for mo-Exc","secretary_remarks":"","agenda_item_sort_order":3,"ainumber":"3","ainame":"Input LS","tdoc_agenda_sort_order":240,"status":"noted","reservation_date":"2016-04-22 06:39:01","uploaded":"2016-04-22 06:47:10","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG1_mm-cc-sm_ex-CN1\/adhocMeetings\/2016-04-25-adhoc_IoT\/Docs\/C1A160024.zip","group":"C1","meeting":"C1-ah-32099","year":2016,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"C1A160025","title":"Reply LS on per-UE configuration to allow exception reporting (R2-163048)","source":"RAN2","contact":"Frederic Firmin","contact-id":53384,"tdoctype":"LS in","for":"","abstract":"","secretary_remarks":"","agenda_item_sort_order":3,"ainumber":"3","ainame":"Input LS","tdoc_agenda_sort_order":250,"status":"noted","reservation_date":"2016-04-22 06:40:52","uploaded":"2016-04-22 06:47:10","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG1_mm-cc-sm_ex-CN1\/adhocMeetings\/2016-04-25-adhoc_IoT\/Docs\/C1A160025.zip","group":"C1","meeting":"C1-ah-32099","year":2016,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"C1A160026","title":"LS latest updates about access control for NB-IOT in RAN2 (R2-163122)","source":"RAN2","contact":"Frederic Firmin","contact-id":53384,"tdoctype":"LS in","for":"","abstract":"","secretary_remarks":"","agenda_item_sort_order":3,"ainumber":"3","ainame":"Input LS","tdoc_agenda_sort_order":260,"status":"replied to","reservation_date":"2016-04-22 06:42:14","uploaded":"2016-04-22 06:47:10","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"C1A160070, C1A160070, C1A160102","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG1_mm-cc-sm_ex-CN1\/adhocMeetings\/2016-04-25-adhoc_IoT\/Docs\/C1A160026.zip","group":"C1","meeting":"C1-ah-32099","year":2016,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"C1A160027","title":"LS on DRX, eDRX and PTW value ranges ( R2-163127)","source":"RAN2","contact":"Frederic Firmin","contact-id":53384,"tdoctype":"LS in","for":"","abstract":"RAN2 has discussed the DRX, eDRX and PTW value ranges and made the following agreements:\n\n?\tNB-IoT supports a Cell specific DRX cycle that is configurable and broadcasted, Range {1.28, 2.56, 5.12, 10.24} sec \n?\teDRX cycle, NB-IoT supports {20.48, 40.96","secretary_remarks":"","agenda_item_sort_order":3,"ainumber":"3","ainame":"Input LS","tdoc_agenda_sort_order":270,"status":"noted","reservation_date":"2016-04-22 06:43:54","uploaded":"2016-04-22 06:47:10","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG1_mm-cc-sm_ex-CN1\/adhocMeetings\/2016-04-25-adhoc_IoT\/Docs\/C1A160027.zip","group":"C1","meeting":"C1-ah-32099","year":2016,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"C1A160028","title":"CIoT agreements for non-NB-IoT and for the bearer suspended list  (R2-163149)","source":"RAN2","contact":"Frederic Firmin","contact-id":53384,"tdoctype":"LS in","for":"","abstract":"","secretary_remarks":"","agenda_item_sort_order":3,"ainumber":"3","ainame":"Input LS","tdoc_agenda_sort_order":280,"status":"replied to","reservation_date":"2016-04-22 06:46:24","uploaded":"2016-04-22 06:47:10","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"C1A160071, C1A160071","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG1_mm-cc-sm_ex-CN1\/adhocMeetings\/2016-04-25-adhoc_IoT\/Docs\/C1A160028.zip","group":"C1","meeting":"C1-ah-32099","year":2016,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"C1A160066","title":"LS on RRC and System Information Broadcast impacts in the Attach procedure (S2-162247)","source":"SA2","contact":"Frederic Firmin","contact-id":53384,"tdoctype":"LS in","for":"","abstract":"","secretary_remarks":"","agenda_item_sort_order":3,"ainumber":"3","ainame":"Input LS","tdoc_agenda_sort_order":6600,"status":"replied to","reservation_date":"2016-04-23 07:31:25","uploaded":"2016-04-23 07:32:21","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"C1A160086, C1A160086, C1A160093","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG1_mm-cc-sm_ex-CN1\/adhocMeetings\/2016-04-25-adhoc_IoT\/Docs\/C1A160066.zip","group":"C1","meeting":"C1-ah-32099","year":2016,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"C1A160074","title":"Maximum upper layer data packet size for NB-IoT","source":"RAN2","contact":"Frederic Firmin","contact-id":53384,"tdoctype":"LS in","for":"","abstract":"","secretary_remarks":"","agenda_item_sort_order":3,"ainumber":"3","ainame":"Input LS","tdoc_agenda_sort_order":7400,"status":"noted","reservation_date":"2016-04-28 08:41:13","uploaded":"2016-08-31 15:49:11","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG1_mm-cc-sm_ex-CN1\/adhocMeetings\/2016-04-25-adhoc_IoT\/Docs\/C1A160074.zip","group":"C1","meeting":"C1-ah-32099","year":2016,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]