[{"name":"C4-171067","title":"LS on progress of CT1 work on LTE light connection","source":"CT1","contact":"Lena Chaponniere","contact-id":38080,"tdoctype":"LS in","for":"Information","abstract":"","secretary_remarks":"","agenda_item_sort_order":7,"ainumber":"4","ainame":"Input liaison statements: allocation to agenda items as appropriate","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2017-02-01 07:27:04","uploaded":"2017-02-01 08:11:13","revisionof":"","revisedto":"","release":"Rel-14","crspec":"","crspecversion":"","workitem":[{"winame":"LTE_LIGHT_CON-CT"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN2, SA2","Cc":"RAN3, CT4","lsoriginalls":"C1-170531","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_76_Dubrovnik\/Docs\/C4-171067.zip","group":"C4","meeting":"C4-76","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"C4-171068","title":"LS on the PLMN ID for MBMS services for Receive Only Mode","source":"CT3","contact":"Amer Catovic","contact-id":39766,"tdoctype":"LS in","for":"Information","abstract":"As part of the Release 14 work, 3GPP is standardizing Mulitcast Broadcast Multimedia Services (MBMS) for Receive Only Mode devices. An example of such services is the broadcast TV service. Receive Only Mode device is a device that does not have subscription\/SIM card, cannot register with the 3GPP network and is only capable of receiving MBMS. These services for Receive Only Mode devices are therefore different from traditional 3GPP MBMS services in that they cannot be tied to subscription, are not subject to charging\/billing, and are anonymous. Therefore, the discovery of the availability of these services in a network cannot be based on the traditional methods, such as signalling with the network, or dynamic device provisioning. These services are not expected to be offered by all networks.","secretary_remarks":"","agenda_item_sort_order":7,"ainumber":"4","ainame":"Input liaison statements: allocation to agenda items as appropriate","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2017-02-01 07:30:20","uploaded":"2017-02-01 08:11:13","revisionof":"","revisedto":"","release":"Rel-14","crspec":"","crspecversion":"","workitem":[{"winame":"AE_enTV-CT"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"ITU-T TSB Director","Cc":"CT1, CT4, SA4, SA2, CT","lsoriginalls":"C3A170057","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_76_Dubrovnik\/Docs\/C4-171068.zip","group":"C4","meeting":"C4-76","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"C4-171071","title":"Response to LS on SA2 involvement for the light connection","source":"SA2","contact":"Hans Ronneke","contact-id":25844,"tdoctype":"LS in","for":"Discussion","abstract":"SA2 has initiated discussions on Light Connection during SA2#118bis; the attached document lists a preliminary set of identified potential system issues, responsible WGs, and, where applicable, potential solutions. Further work is required in SA2 to complete this activity. A number of companies proposed to initiate a work item to properly cater for this work in SA2 \u2013 further related discussions are expected during SA2#119. \nFurther SA2 would like to inform that Rel-14 stage 2 was officially closed in September 2016 (exceptions until December 2016). Irrespective whether or not a new work item is needed, it is SA plenary decision whether the work will be made into Rel-14 Stage 2 specifications or should be deferred to Rel-15.","secretary_remarks":"","agenda_item_sort_order":7,"ainumber":"4","ainame":"Input liaison statements: allocation to agenda items as appropriate","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2017-02-01 07:38:22","uploaded":"2017-02-01 08:11:13","revisionof":"","revisedto":"","release":"Rel-14","crspec":"","crspecversion":"","workitem":[{"winame":"LTE_LIGHT_CON-Core"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"C1-165447","lsto":"CT1, RAN2, RAN3, SA3-LI, CT4, SA","Cc":"CT, RAN","lsoriginalls":"S2-170695","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_76_Dubrovnik\/Docs\/C4-171071.zip","group":"C4","meeting":"C4-76","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"C4-171072","title":"LS on subscription-based restrictions on attach without PDN connection","source":"SA2","contact":"Haris Zisimopoulos","contact-id":56901,"tdoctype":"LS in","for":"Discussion","abstract":"The attached CR of CT1 was briefly discussed by SA2, and some potential drawbacks were raised by some companies:\n-\tUE can still initiate standalone PDN connection establishment procedure after the attach procedure which still creates SM signalling in the network\n-\tSubscription based restriction can be bypassed by the UE by not indicating support for attach without PDN connection capability\nAs the result of that, SA2#118bis agreed to postpone TS 23.401 CR3182 (and rel.14 mirror CR) to next meeting.","secretary_remarks":"","agenda_item_sort_order":7,"ainumber":"4","ainame":"Input liaison statements: allocation to agenda items as appropriate","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2017-02-01 07:40:53","uploaded":"2017-02-01 08:11:13","revisionof":"","revisedto":"","release":"Rel-13","crspec":"","crspecversion":"","workitem":[{"winame":"CIoT-CT"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-170013 \/ C1-165429","lsto":"CT1, CT4","Cc":"","lsoriginalls":"S2-170700","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_76_Dubrovnik\/Docs\/C4-171072.zip","group":"C4","meeting":"C4-76","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"C4-171073","title":"Reply LS on SA2 involvement for the light connection","source":"SA3-LI","contact":"Alex Leadbeater","contact-id":71428,"tdoctype":"LS in","for":"Information","abstract":"SA3-LI would like to thank SA2 for their LS in tdoc S2-170695. SA3-LI had an initial discussion to consider the potential implication for LI in terms of location information and would provide as feedback that location information to be reported for LI purposes shall have the same level of granularity known to the Core Network. \nIt is SA3-LI understanding that location information provided in the LI events in case of light connection will not differ from the one currently reported.\nFrom LI perspective, if in case of light connection the location information reported when LI events occur cannot be considered as updated, SA3-LI would recommend that location information is reported together with the time the location was obtained. \n\nSA3-LI will further study the potential LI implications for light connection and may provide additional feedback.","secretary_remarks":"","agenda_item_sort_order":7,"ainumber":"4","ainame":"Input liaison statements: allocation to agenda items as appropriate","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2017-02-01 07:43:46","uploaded":"2017-02-01 08:11:13","revisionof":"","revisedto":"","release":"Rel-14","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-170695","lsto":"SA2","Cc":"CT1, RAN2, RAN3, CT4, SA, RAN, CT","lsoriginalls":"s3i170035","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_76_Dubrovnik\/Docs\/C4-171073.zip","group":"C4","meeting":"C4-76","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"C4-171075","title":"LS on LI requirements reconfirmed, including 5G and CIoT","source":"SA3-LI","contact":"Koen Jaspers","contact-id":9291,"tdoctype":"LS in","for":"Information","abstract":"SA3LI would like to reconfirm that target identifiers in general are the network access identifier, equipment identifier or service level identifier (e.g. IMSI, IMEI or sip-uri). This also applies to roaming scenarios. This does not change for 5G and CIoT. This does not prevent CSPs from translating or mapping these long term identifiers to temporary or encrypted identifiers as long as the CSP can make the association back to the long term identifier for LI purposes.","secretary_remarks":"","agenda_item_sort_order":7,"ainumber":"4","ainame":"Input liaison statements: allocation to agenda items as appropriate","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2017-02-01 07:53:22","uploaded":"2017-02-01 08:11:13","revisionof":"","revisedto":"","release":"Rel-14","crspec":"","crspecversion":"","workitem":[{"winame":"LI14"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA1, SA2, SA3, RAN2","Cc":"TSG SA, CT1, CT3, CT4, RAN3","lsoriginalls":"S3i170054","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_76_Dubrovnik\/Docs\/C4-171075.zip","group":"C4","meeting":"C4-76","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"C4-171259","title":"LS on Reliable Data Service","source":"SA2","contact":"Michael Starsinic","contact-id":72107,"tdoctype":"LS in","for":"Action","abstract":"SA2 has agreed to specify a Reliable Data Delivery Service to be used for NIDD between the UE and SCEF (see attached CR to TS 23.682).\n\nSA2 would like to point out that overhead associated with the header size of the protocol should be kept to a minimum in consideration of the fact that the UE may be an NB-IoT UE and may be in enhanced coverage mode.","secretary_remarks":"","agenda_item_sort_order":7,"ainumber":"4","ainame":"Input liaison statements: allocation to agenda items as appropriate","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2017-02-13 07:14:04","uploaded":"2017-02-13 07:16:30","revisionof":"C4-170007","revisedto":"","release":"Rel-14","crspec":"","crspecversion":"","workitem":[{"winame":"CIoT_Ext-CT"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT1, CT3, CT4","Cc":"","lsoriginalls":"S2-167236","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_76_Dubrovnik\/Docs\/C4-171259.zip","group":"C4","meeting":"C4-76","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"C4-171260","title":"LS to 3GPP CT4 Diameter Wait Timers","source":"GSMA PACKET#87","contact":"Kimmo Kymalainen","contact-id":19464,"tdoctype":"LS in","for":"Action","abstract":"Postponed from CT4#75","secretary_remarks":"","agenda_item_sort_order":7,"ainumber":"4","ainame":"Input liaison statements: allocation to agenda items as appropriate","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2017-02-13 07:19:32","uploaded":"2017-02-13 07:22:03","revisionof":"C4-166007","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT4","Cc":"","lsoriginalls":"88_107 Packet","lsreply":"C4-171351, C4-171443","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_76_Dubrovnik\/Docs\/C4-171260.zip","group":"C4","meeting":"C4-76","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]