[{"name":"C4-183245","title":"Reply LS on Differentiation of LTE-M (eMTC) traffic from other LTE data traffic","source":"Nokia, Nokia Shanghai Bell","contact":"Bruno Landais","contact-id":68755,"tdoctype":"LS out","for":"Approval","abstract":"","secretary_remarks":"","agenda_item_sort_order":7,"ainumber":"4","ainame":"Input liaison statements: allocation to agenda items as appropriate","tdoc_agenda_sort_order":32630,"status":"revised","reservation_date":"2018-04-05 09:44:20","uploaded":"2018-04-06 15:49:26","revisionof":"","revisedto":"C4-183278","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-182411","lsto":"SA2","Cc":"RAN3, CT3, SA5","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_84_KunMing\/Docs\/C4-183245.zip","group":"C4","meeting":"C4-84","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"C4-183258","title":"LS on TAI and forbidden TAI list for 5GS","source":"CT1","contact":"Robert Zaus","contact-id":10799,"tdoctype":"LS in","for":"Information","abstract":"The work on the NAS protocol (TS 24.501) has progressed to a point where CT1 would like to define the format of certain NAS parameters, e.g. the tracking area identity (TAI) and the TAI list for 5GS. As the TAI is also used by other protocols (RRC, NGAP),","secretary_remarks":"","agenda_item_sort_order":7,"ainumber":"4","ainame":"Input liaison statements: allocation to agenda items as appropriate","tdoc_agenda_sort_order":32661,"status":"noted","reservation_date":"2018-04-07 04:59:21","uploaded":"2018-04-07 05:44:05","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":[{"winame":"5GS_Ph1-CT"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA2, RAN2, RAN3","Cc":"CT4","lsoriginalls":"C1-181790","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_84_KunMing\/Docs\/C4-183258.zip","group":"C4","meeting":"C4-84","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"C4-183259","title":"LS on paging with IMSI\/SUCI in 5GS","source":"CT1","contact":"Lin Shu","contact-id":43310,"tdoctype":"LS in","for":"Information","abstract":"CT1 has discussed whether paging with IMSI or SUCI needs to be supported in 5GS. Paging with IMSI is an abnormal procedure used for error recovery in the network, which was supported in 2G, 3G and EPC.\nCT1 noted the privacy requirement on using IMSI was","secretary_remarks":"","agenda_item_sort_order":7,"ainumber":"4","ainame":"Input liaison statements: allocation to agenda items as appropriate","tdoc_agenda_sort_order":32670,"status":"noted","reservation_date":"2018-04-07 05:03:11","uploaded":"2018-04-07 05:44:05","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":[{"winame":"5GS_Ph1-CT"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA2","Cc":"SA3, CT4","lsoriginalls":"C1-181791","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_84_KunMing\/Docs\/C4-183259.zip","group":"C4","meeting":"C4-84","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"C4-183263","title":"LS on Handling of end marker packets","source":"RAN3","contact":"Philippe Godin","contact-id":68843,"tdoctype":"LS in","for":"Discussion","abstract":"RAN3 kindly ask SA2 and CT4 to feedback whether GTP-U end markers are to be sent over NG-U per QoS Flow or per PDU session.","secretary_remarks":"","agenda_item_sort_order":7,"ainumber":"4","ainame":"Input liaison statements: allocation to agenda items as appropriate","tdoc_agenda_sort_order":32450,"status":"postponed","reservation_date":"2018-04-07 05:18:55","uploaded":"2018-04-07 05:44:05","revisionof":"","revisedto":"C4-184059","release":"Rel-15","crspec":"","crspecversion":"","workitem":[{"winame":"NR_newRAT-Core"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA2, CT4","Cc":"","lsoriginalls":"R3-181575","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_84_KunMing\/Docs\/C4-183263.zip","group":"C4","meeting":"C4-84","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"C4-183265","title":"LS on Differentiation of LTE-M (eMTC) traffic from other LTE data traffic","source":"SA2","contact":"Alessio Casati","contact-id":68028,"tdoctype":"LS in","for":"Discussion","abstract":"3GPP TSG SA WG2 endorsed the attached TS 23.401 CR on Differentiation of LTE-M (eMTC) traffic from other LTE data traffic based on the assumption that addition of a new RAT-Type is feasible. SA2 has taken the approach of identifying the UEs traffic as LTE","secretary_remarks":"","agenda_item_sort_order":7,"ainumber":"4","ainame":"Input liaison statements: allocation to agenda items as appropriate","tdoc_agenda_sort_order":32580,"status":"noted","reservation_date":"2018-04-07 05:26:05","uploaded":"2018-04-07 05:44:05","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN3, CT3, CT4, SA5","Cc":"RAN2","lsoriginalls":"S2-182411","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_84_KunMing\/Docs\/C4-183265.zip","group":"C4","meeting":"C4-84","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"C4-183266","title":"LS on encrypting broadcasted positioning data and LS on provisioning of positioning assistance data via LPPa for broadcast","source":"SA2","contact":"Haris Zisimopoulos","contact-id":57197,"tdoctype":"LS in","for":"Discussion","abstract":"Based on the feedback received SA2 technically endorsed the attached CR to TS 23.271 implementing \"option 1 \u2013 i.e. the option where ciphering key data are transferred from an E-SMLC to MMEs (e.g. using a new LCS-AP message) and then included as a new IE i","secretary_remarks":"","agenda_item_sort_order":7,"ainumber":"4","ainame":"Input liaison statements: allocation to agenda items as appropriate","tdoc_agenda_sort_order":32660,"status":"noted","reservation_date":"2018-04-07 05:29:22","uploaded":"2018-04-07 05:44:05","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":[{"winame":"LCS_LTE_acc_enh-Core"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"C1-180643, C4-182150","lsto":"RAN2, RAN3, CT4, CT1","Cc":"SA3","lsoriginalls":"S2-182415","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_84_KunMing\/Docs\/C4-183266.zip","group":"C4","meeting":"C4-84","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"C4-183267","title":"LS on 5G-S-TMSI code space","source":"SA2","contact":"Peter Hedman","contact-id":27550,"tdoctype":"LS in","for":"Information","abstract":"SA2 is considering solutions to achieve appropriate support for number of network slices and connection density with 40 bits 5G-S-TMSI. Based on the discussions, SA2 has observed that this results in some complexities for EPS interworking. Thus it was que","secretary_remarks":"","agenda_item_sort_order":7,"ainumber":"4","ainame":"Input liaison statements: allocation to agenda items as appropriate","tdoc_agenda_sort_order":32750,"status":"noted","reservation_date":"2018-04-07 05:33:29","uploaded":"2018-04-07 05:44:05","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":[{"winame":"5GS_Ph1-CT"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN2, RAN3","Cc":"CT1, CT4","lsoriginalls":"S2-182964","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_84_KunMing\/Docs\/C4-183267.zip","group":"C4","meeting":"C4-84","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"C4-183275","title":"LS on 5G Trace","source":"SA5","contact":"Anatoly Andrianov","contact-id":68259,"tdoctype":"LS in","for":"Discussion","abstract":"SA5 is currently defining the support for Trace in Rel-15 for 5G including NG-RAN and 5GC. Attached are the agreed CRs to TSs 32.421 and 32.422 addressing use cases, requirements, activation\/deactivation mechanisms, control and configuration parameters. T","secretary_remarks":"","agenda_item_sort_order":7,"ainumber":"4","ainame":"Input liaison statements: allocation to agenda items as appropriate","tdoc_agenda_sort_order":32760,"status":"postponed","reservation_date":"2018-04-13 11:31:10","uploaded":"2018-04-13 11:33:17","revisionof":"","revisedto":"C4-184060","release":"Rel-15","crspec":"","crspecversion":"","workitem":[{"winame":"NETSLICE-5GTRACE"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA2, RAN3, CT4","Cc":"","lsoriginalls":"S5-182566","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_84_KunMing\/Docs\/C4-183275.zip","group":"C4","meeting":"C4-84","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"C4-183276","title":"LS on FS_eVoLP","source":"SA4","contact":"Nikolai Leung","contact-id":38562,"tdoctype":"LS in","for":"Discussion","abstract":"As part of the Rel-15 study item on \u201cEnhanced VoLTE Performance\u201d (FS_eVoLP), SA4 has investigated the media handling support and potential enhancements for the codec-aware SRVCC optimizations, toward supplementing the SA2-defined normative eVoLP features","secretary_remarks":"","agenda_item_sort_order":7,"ainumber":"4","ainame":"Input liaison statements: allocation to agenda items as appropriate","tdoc_agenda_sort_order":32770,"status":"postponed","reservation_date":"2018-04-15 14:13:12","uploaded":"2018-04-15 14:23:02","revisionof":"","revisedto":"C4-184061","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"3GPP TSG RAN WG2, 3GPP TSG SA WG2, 3GPP TSG CT WG1, 3GPP CT WG3, 3GPP CT WG4","Cc":"","lsoriginalls":"S4-180631","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_84_KunMing\/Docs\/C4-183276.zip","group":"C4","meeting":"C4-84","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"C4-183277","title":"LS Reply to SA2 on Differentiation of LTE-M (eMTC) traffic from other LTE data traffic","source":"SA5","contact":"Maryse Gardella","contact-id":68914,"tdoctype":"LS in","for":"Information","abstract":"In SA5 charging specifications for EPC (TS 32.251), the RAT type is already specified as an information which can be used for traffic volume differentiation.\nSimilarly as for NB-IoT, addition of a new RAT type value will allow to categorize the UEs traff","secretary_remarks":"","agenda_item_sort_order":7,"ainumber":"4","ainame":"Input liaison statements: allocation to agenda items as appropriate","tdoc_agenda_sort_order":32590,"status":"noted","reservation_date":"2018-04-15 14:18:51","uploaded":"2018-04-15 14:23:02","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA2","Cc":"RAN3, CT3, CT4, RAN2","lsoriginalls":"S5-1822334","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_84_KunMing\/Docs\/C4-183277.zip","group":"C4","meeting":"C4-84","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"C4-183278","title":"Reply LS on Differentiation of LTE-M (eMTC) traffic from other LTE data traffic","source":"CT4","contact":"John M Meredith","contact-id":637,"tdoctype":"LS out","for":"Approval","abstract":"","secretary_remarks":"","agenda_item_sort_order":7,"ainumber":"4","ainame":"Input liaison statements: allocation to agenda items as appropriate","tdoc_agenda_sort_order":32650,"status":"approved","reservation_date":"2018-04-19 11:12:41","uploaded":"2018-04-19 23:47:54","revisionof":"C4-183245","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-182411","lsto":"SA2","Cc":"RAN3, CT3, SA5","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_84_KunMing\/Docs\/C4-183278.zip","group":"C4","meeting":"C4-84","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"C4-183349","title":"Reply LS on 5G-S-TMSI","source":"RAN2","contact":"John M Meredith","contact-id":637,"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":334900,"status":"noted","reservation_date":"2018-04-19 11:16:55","uploaded":"2018-04-19 23:47:54","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":[{"winame":"NR_newRAT-Core"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT1, SA2","Cc":"RAN3, CT4","lsoriginalls":"R2-1806394","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_84_KunMing\/Docs\/C4-183349.zip","group":"C4","meeting":"C4-84","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"C4-183350","title":"Reply LS on Extending TAC for NR and NG-RAN","source":"RAN2","contact":"John M Meredith","contact-id":637,"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":335000,"status":"noted","reservation_date":"2018-04-19 11:16:55","uploaded":"2018-04-19 23:47:54","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":[{"winame":"5GS_Ph1-CT"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"C1-181790, R3-180634","lsto":"RAN3, CT1","Cc":"SA2, CT4","lsoriginalls":"R2-1806395","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_84_KunMing\/Docs\/C4-183350.zip","group":"C4","meeting":"C4-84","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"C4-183353","title":"Reply LS on SoR mechanism","source":"CT1","contact":"John M Meredith","contact-id":637,"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":335300,"status":"noted","reservation_date":"2018-04-19 11:16:55","uploaded":"2018-04-19 23:47:54","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":[{"winame":"5GS_Ph1-CT"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA3","Cc":"CT6, SA2, CT3, SA1, SA3-LI, CT4","lsoriginalls":"C4-182490","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_84_KunMing\/Docs\/C4-183353.zip","group":"C4","meeting":"C4-84","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"C4-183428","title":"Response to LS on encrypting broadcasted positioning data and LS on provisioning of positioning assistance data via LPPa for broadcast","source":"RAN2","contact":"Kimmo Kymalainen","contact-id":19464,"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":342800,"status":"noted","reservation_date":"2018-04-19 11:26:22","uploaded":"2018-04-19 23:47:54","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":[{"winame":"LCS_LTE_acc_enh-Core"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA2","Cc":"RAN3, CT1, CT4, SA3","lsoriginalls":"R2-1806307","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_84_KunMing\/Docs\/C4-183428.zip","group":"C4","meeting":"C4-84","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"C4-183429","title":"Reply LS on SoR mechanism","source":"SA3","contact":"Kimmo Kymalainen","contact-id":19464,"tdoctype":"LS in","for":"Discussion","abstract":"","secretary_remarks":"","agenda_item_sort_order":7,"ainumber":"4","ainame":"Input liaison statements: allocation to agenda items as appropriate","tdoc_agenda_sort_order":342900,"status":"noted","reservation_date":"2018-04-19 11:26:22","uploaded":"2018-04-19 23:47:54","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":[{"winame":"5GS_Ph1-SEC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"C1-182490","lsto":"CT1","Cc":"CT6, SA2, CT3, SA1, SA3-LI, CT4","lsoriginalls":"S3-181501","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_84_KunMing\/Docs\/C4-183429.zip","group":"C4","meeting":"C4-84","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"C4-183489","title":"Reply LS on 5G-S-TMSI","source":"SA2","contact":"Kimmo Kymalainen","contact-id":19464,"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":"postponed","reservation_date":"2018-04-20 02:20:11","uploaded":"2018-04-20 02:27:55","revisionof":"","revisedto":"C4-184062","release":"Rel-15","crspec":"","crspecversion":"","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"R2-1806394","lsto":"RAN2","Cc":"CT1, RAN3, CT4","lsoriginalls":"S2-184501","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_84_KunMing\/Docs\/C4-183489.zip","group":"C4","meeting":"C4-84","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]