[{"name":"CP-160532","title":"Reply LS on Multiple bearer capability handling","source":"CT1","contact":"Kimmo Kymalainen","contact-id":19464,"tdoctype":"LS in","for":"Information","abstract":"CT1 would like to thank RAN2 for their LS on Multiple bearer capability handling in (R2-163288\/C1-162557).\nCT1 has taken into account RAN2 agreement that a NB-IOT UE supporting CIoT user plane optimisation can optionally support up to 2 DRBs and has also conditionally agreed to signal this capability information over NAS as suggested by RAN2. Please see attached CR to TS 24.301. \nHowever the approval of this CR in CT plenary is dependent on SA2 updating their specifications accordingly.","secretary_remarks":"","agenda_item_sort_order":8,"ainumber":"4.1","ainame":"Incoming liaisons","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2016-09-12 07:47:45","uploaded":"2016-09-12 08:16:02","revisionof":"","revisedto":"","release":"Rel-13","crspec":"","crspecversion":"","workitem":[{"winame":"CIoT-CT"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"R2-163288\/C1-162557","lsto":"SA WG2, RAN WG2","Cc":"RAN WG3, TSG CT","lsoriginalls":"C1-163890","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/tsg_ct\/TSGC_73_New_Orleans\/Docs\/CP-160532.zip","group":"CP","meeting":"CP-73","year":2016,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"CP-160533","title":"LS on delay tolerant access via NB-IOT","source":"CT1","contact":"Kimmo Kymalainen","contact-id":19464,"tdoctype":"LS in","for":"Action","abstract":"CT1 would like to thank SA2 on their LS on Core Network overload control and delay tolerant access via NB-IOT from SA2. \nCT1 understands and agrees that the decision to re-introduce the delay tolerant establishment cause for NB-IoT is to be made by RAN2. Due to the constraints set by the meeting calendars of RAN2, SA2 and CT1, there would be no opportunity for CT1 to implement the RAN2 decision in the same plenary cycle, if this decision requires updating CT1 specifications. Consequently, CT1 decided to technically endorse the related CRs in C1-163847 (Rel-13) and C1-163848 (Rel-14), which re-introduce the delay tolerant establishment cause at the NAS layer. The fate of these CRs will be determined by the RAN2 decision on this matter.","secretary_remarks":"","agenda_item_sort_order":8,"ainumber":"4.1","ainame":"Incoming liaisons","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2016-09-12 07:51:38","uploaded":"2016-09-12 08:16:02","revisionof":"","revisedto":"","release":"Rel-14","crspec":"","crspecversion":"","workitem":[{"winame":"CIoT-CT"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"C1-163526\/S2-163061","lsto":"SA2, RAN2, CT","Cc":"","lsoriginalls":"C1-164010","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/tsg_ct\/TSGC_73_New_Orleans\/Docs\/CP-160533.zip","group":"CP","meeting":"CP-73","year":2016,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"CP-160534","title":"IoT DCE request to formalize the Service Layer Interface","source":"GSMA TSGIoTDCE","contact":"Kimmo Kymalainen","contact-id":19464,"tdoctype":"LS in","for":"Information","abstract":"IoT Device Connection Efficiency, Guidelines (TS.34) and Test Book (TS.35) have been released as version 3.0.\nThe group has been focusing on the definition of a common verticals service layer. The requirements for this service layer have been defined as part of the next version of TS 34 due for publication Q3 2016\nIn order to minimize fragmentation within the ecosystem, the IoT DCE group is asking existing industry standards groups who are working on similar aspects to define the interface between the IoT application and the IoT DCE service layer.\nThis interface is of particular importance for the certification of IoT modules implementing TS.34 requirements. \nThese requirements are embedded within the overall GSMA IoT Mobile Certification & Test programme.","secretary_remarks":"","agenda_item_sort_order":8,"ainumber":"4.1","ainame":"Incoming liaisons","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2016-09-12 07:55:02","uploaded":"2016-09-12 08:16:02","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"GSMA Connected Living (Mobile IoT Initiative CT)","Cc":"One M2M, 3GPP.CT1\/SA2, cc 3GPP RAN\/CT,","lsoriginalls":"IoTDCE_054 LS for the Service Layer Interface v3","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/tsg_ct\/TSGC_73_New_Orleans\/Docs\/CP-160534.zip","group":"CP","meeting":"CP-73","year":2016,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"CP-160535","title":"LIAISON STATEMENT TO GCS PROPONENTS AND TRANSPOSING ORGANIZATIONS ON THE PROVISION OF TRANSPOSITION REFERENCES AND CERTIFICATION C FOR DRAFT REVISION 13 OF  RECOMMENDATION ITU-R M.1457","source":"ITU-R Working Party 5D","contact":"Kimmo Kymalainen","contact-id":19464,"tdoctype":"LS in","for":"Information","abstract":"Working Party 5D thanks the relevant GCS Proponents for their successful work in regards to completion of the milestone identified by Item 8 of Table 1 for the draft Revision 13 update of Recommendation ITU-R M.1457 \u201cDetailed specifications of the terrestrial radio interfaces of International Mobile Telecommunications-2000 (IMT-2000)\u201d following the process in Document IMT-2000\/6 (Rev.1), \u201cSchedule for the Revision 13 Update of Recommendation ITU-R M.1457\u201d.\nWP 5D wishes to inform the GCS Proponents and the Transposing Organizations that during its 24th meeting (14-22 June 2016 in Geneva, Switzerland) the specific technology updates for the draft Revision 13 of Recommendation ITU R M.1457 (not including the full set of final detailed transposition references) were finalized and agreed.","secretary_remarks":"","agenda_item_sort_order":8,"ainumber":"4.1","ainame":"Incoming liaisons","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2016-09-12 07:58:38","uploaded":"2016-09-12 08:16:02","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"LS_EOs_5D_234_temp_96R1","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/tsg_ct\/TSGC_73_New_Orleans\/Docs\/CP-160535.zip","group":"CP","meeting":"CP-73","year":2016,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"CP-160536","title":"Invitation for submission of proposals for candidate radio interface technologies for the terrestrial components of the radio interface(s) for IMT-2020 and invitation to participate in their subsequent evaluation","source":"ITU-R Working Party 5D","contact":"Kimmo Kymalainen","contact-id":19464,"tdoctype":"LS in","for":"Information","abstract":"ITU-R has commenced the process of developing ITU-R Recommendations for the terrestrial components of the IMT-2020 radio interface(s). ITU-R WP 5D is responsible for the overall radio system aspects of the terrestrial component of International Mobile Telecommunications (IMT) systems, comprised of IMT-2000, IMT-Advanced and IMT-2020. \nThe invitation for submission of proposals for candidate radio interface technologies for the terrestrial components of IMT-2020 was issued with Circular Letter 5\/LCCE\/59 by ITU-R on 22 March, 2016. Addendum 1 to this Circular Letter was also developed by WP 5D during its 24th meeting in 14-22 June. The Circular Letter and its Addendum are enclosed.\nWP 5D kindly invites the interested organizations for submission of proposals for candidate radio interface technologies for the terrestrial components of the radio interface technologies for IMT 2020 and to participate in the subsequent evaluation.","secretary_remarks":"","agenda_item_sort_order":8,"ainumber":"4.1","ainame":"Incoming liaisons","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2016-09-12 08:02:43","uploaded":"2016-09-12 08:16:02","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"LS_EOs_5D_234_temp_159","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/tsg_ct\/TSGC_73_New_Orleans\/Docs\/CP-160536.zip","group":"CP","meeting":"CP-73","year":2016,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"CP-160537","title":"Response LS on delay tolerant access via NB-IOT","source":"RAN2","contact":"Kimmo Kymalainen","contact-id":19464,"tdoctype":"LS in","for":"Action","abstract":"RAN2 thanks CT1 and SA2 on their LS on Core Network overload control and delay tolerant access via NB-IOT. \nRAN2 has agreed to introduce RRC delayTolerantAccess establishment cause from Release 13 without any access barring changes. From access barring point of view, RRC considers delayTolerantAccess same as mo-Data and mo-Sigalling.","secretary_remarks":"","agenda_item_sort_order":8,"ainumber":"4.1","ainame":"Incoming liaisons","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2016-09-12 08:06:48","uploaded":"2016-09-12 08:16:02","revisionof":"","revisedto":"","release":"Rel-13","crspec":"","crspecversion":"","workitem":[{"winame":"NB_IOT-Core"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA2, CT, CT1","Cc":"RAN3","lsoriginalls":"R2-165824","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/tsg_ct\/TSGC_73_New_Orleans\/Docs\/CP-160537.zip","group":"CP","meeting":"CP-73","year":2016,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"CP-160538","title":"Reply LS on I-WLAN handling and specification withdrawal","source":"SA2","contact":"Kimmo Kymalainen","contact-id":19464,"tdoctype":"LS in","for":"Information","abstract":"SA WG2 thanks TSG SA for their LS informing SA WG2 on the process to discontinue I-WLAN specifications.\n\nSA WG2 approved the attached CRs to address the guidance from TSG SA.","secretary_remarks":"","agenda_item_sort_order":8,"ainumber":"4.1","ainame":"Incoming liaisons","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2016-09-12 08:10:39","uploaded":"2016-09-12 08:16:02","revisionof":"","revisedto":"","release":"Rel-13","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-164290\/SP-160508","lsto":"SA","Cc":"SA1, SA3, SA3-LI, SA5, CT1, CT3, CT4, CT6, CT","lsoriginalls":"S2-165026","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/tsg_ct\/TSGC_73_New_Orleans\/Docs\/CP-160538.zip","group":"CP","meeting":"CP-73","year":2016,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"CP-160539","title":"Reply LS on Multiple bearer capability handling","source":"SA2","contact":"Kimmo Kymalainen","contact-id":19464,"tdoctype":"LS in","for":"Information","abstract":"SA2 would like to thank CT1 for their LS on Multiple bearer capability handling (S2-164294\/C1-163890).\nSA2 supports the updates from CT1 wherein a NB-IoT UE can optionally support 2 DRBs and signal this capability information over NAS. SA2 has analysed the system behaviour and updated the stage-2 specifications accordingly. Please see attached CR to TS 23.401 that was agreed in SA2.","secretary_remarks":"","agenda_item_sort_order":8,"ainumber":"4.1","ainame":"Incoming liaisons","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2016-09-12 08:13:06","uploaded":"2016-09-12 08:16:02","revisionof":"","revisedto":"","release":"Rel-13","crspec":"","crspecversion":"","workitem":[{"winame":"CIoT"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-164294\/C1-163890","lsto":"CT1, CT4","Cc":"RAN2, RAN3, CT","lsoriginalls":"S2-165196","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/tsg_ct\/TSGC_73_New_Orleans\/Docs\/CP-160539.zip","group":"CP","meeting":"CP-73","year":2016,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"CP-160540","title":"LS on I-WLAN handling and specification withdrawal","source":"SA","contact":"Kimmo Kymalainen","contact-id":19464,"tdoctype":"LS in","for":"Action","abstract":"SA is working on a general process for feature withdrawal to be documented during SA#73. This may include aspect such as notifying of the discontinuation on the 3GPP website, informing OPs, in addition to defining an internal process to provide approval for discontinuation of an existing feature in the appropriate Work Item Description.","secretary_remarks":"","agenda_item_sort_order":8,"ainumber":"4.1","ainame":"Incoming liaisons","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2016-09-12 08:15:22","uploaded":"2016-09-12 08:16:02","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA1, SA2, SA3, SA3-LI, SA5, CT1, CT3, CT4, CT6, CT","Cc":"","lsoriginalls":"SP-160508","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/tsg_ct\/TSGC_73_New_Orleans\/Docs\/CP-160540.zip","group":"CP","meeting":"CP-73","year":2016,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]