[{"name":"C4-165007","title":"Reply LS on progress of the work on Diameter Load Control","source":"CT3","contact":"Tarek Abou-assali","contact-id":58502,"tdoctype":"LS in","for":"Action","abstract":"Postponed from CT4#74","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":"2016-09-26 21:56:08","uploaded":"2016-09-26 22:36:28","revisionof":"","revisedto":"C4-166008","release":"Rel-14","crspec":"","crspecversion":"","workitem":[{"winame":"FS_DLoCME"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT4","Cc":"SA5","lsoriginalls":"C3-161313","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_74bis_Guilin\/Docs\/C4-165007.zip","group":"C4","meeting":"C4-74","year":2016,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"C4-165008","title":"Reply LS to LS to CT3 for PDP type extension to non-IP PDN type","source":"CT3","contact":"Horst Brinkmann","contact-id":70091,"tdoctype":"LS in","for":"Information","abstract":"CT3 thanks SA5 for the \"LS to CT3 for PDP type extension to non-IP PDN type\". CT3 introduced the new type into 3GPP TS 29.061 as requested (see attachments C3-162181, C3-162182).","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":"2016-09-26 21:59:11","uploaded":"2016-09-26 22:36:28","revisionof":"","revisedto":"","release":"Rel-13","crspec":"","crspecversion":"","workitem":[{"winame":"CIoT-CT"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA5","Cc":"SA2, CT4","lsoriginalls":"C3-162183","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_74bis_Guilin\/Docs\/C4-165008.zip","group":"C4","meeting":"C4-74","year":2016,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"C4-165009","title":"Communication to 3GPP CT4on TC INT work","source":"ETSI TC INT","contact":"Giulio Maggiore","contact-id":2601,"tdoctype":"LS in","for":"Action","abstract":"This LS informs 3GPP CT4 of a number of recently published DIAMETER test specifications and requests feedback on these specifications with regard to their usage and\/or content.","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":"2016-09-26 22:03:49","uploaded":"2016-09-26 22:36:28","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT4","Cc":"","lsoriginalls":"INT(16)033032","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_74bis_Guilin\/Docs\/C4-165009.zip","group":"C4","meeting":"C4-74","year":2016,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"C4-165010","title":"LS on eDRX Paging Hyper-frame and PTW_Start Calculation","source":"RAN2","contact":"Wuri Hapsari","contact-id":33742,"tdoctype":"LS in","for":"Information","abstract":"RAN2 would like to inform the relevant WGs about the solution direction of changing the calculation formula of eDRX Paging Hyper-frame and PTW_Start Calculation.\nNote that RAN2 is performing a 2-weeks email checking to confirm the solution and to develop the actual RAN2 CR.","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":"2016-09-26 22:07:37","uploaded":"2016-09-26 22:36:28","revisionof":"","revisedto":"","release":"Rel-13","crspec":"","crspecversion":"","workitem":[{"winame":"LTE_extDRX-Core"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA2, RAN3, CT1","Cc":"SA3, CT4","lsoriginalls":"R2-165935","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_74bis_Guilin\/Docs\/C4-165010.zip","group":"C4","meeting":"C4-74","year":2016,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"C4-165011","title":"LS on Network-initiated release of NB-IFOM PDN connections","source":"SA2","contact":"Nicolas Drevon","contact-id":16459,"tdoctype":"LS in","for":"Action","abstract":"SA WG2 thanks CT WG4 for their LS informing SA WG2 about the new Release 13 mechanism whereby the network initiates the release of NB-IFOM PDN connections over both 3GPP and WLAN accesses, e.g. for SIPTO or P-CSCF restoration. \n\nSA WG2 kindly informs CT WG4 that they have agreed to attached CR to TS 23.161 in order to align stage 2 specifications to the stage 3 agreed mechanism.","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":"2016-09-26 22:10:49","uploaded":"2016-09-26 22:36:28","revisionof":"","revisedto":"","release":"Rel-13","crspec":"","crspecversion":"","workitem":[{"winame":"NBIFOM"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"C4-162255\/S2-163219","lsto":"CT1, CT4","Cc":"","lsoriginalls":"S2-165024","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_74bis_Guilin\/Docs\/C4-165011.zip","group":"C4","meeting":"C4-74","year":2016,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"C4-165012","title":"Reply LS on I-WLAN handling and specification withdrawal","source":"SA2","contact":"Haris Zisimopoulos","contact-id":57197,"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":7,"ainumber":"4","ainame":"Input liaison statements: allocation to agenda items as appropriate","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2016-09-26 22:13:21","uploaded":"2016-09-26 22:36:28","revisionof":"","revisedto":"","release":"Rel-13","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","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\/WG4_protocollars_ex-CN4\/TSGCT4_74bis_Guilin\/Docs\/C4-165012.zip","group":"C4","meeting":"C4-74","year":2016,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"C4-165013","title":"Reply LS on Multiple bearer capability handling","source":"SA2","contact":"Vivek Gupta","contact-id":36134,"tdoctype":"LS in","for":"Action","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":7,"ainumber":"4","ainame":"Input liaison statements: allocation to agenda items as appropriate","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2016-09-26 22:17:01","uploaded":"2016-09-26 22:36:28","revisionof":"","revisedto":"","release":"Rel-13","crspec":"","crspecversion":"","workitem":[{"winame":"CIoT-CT"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT1, CT4","Cc":"RAN2, RAN3, CT","lsoriginalls":"S2-165196","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_74bis_Guilin\/Docs\/C4-165013.zip","group":"C4","meeting":"C4-74","year":2016,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"C4-165014","title":"Reply to LS response on LS on confidentiality protection of an identity in a value of an XML attribute of an XML element of an XML document included in a SIP message.","source":"SA3","contact":"Peter Haigh","contact-id":70254,"tdoctype":"LS in","for":"Information","abstract":"SA3 thanks CT1 for its reply LS to on confidentiality protection of XML attributes. SA3 notes that the CT1's response suggests that CT1 is going to consider Option 2, as well as other security solutions. SA3 has not discussed or defined any security solution for Option 2 and recommended against this approach in its previous LS. SA3 contains 3GPP's subject matter experts on security and requests that any security solutions are brought to SA3 for discussion and approval prior to definition by CT1.","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":"2016-09-26 22:19:33","uploaded":"2016-09-26 22:36:28","revisionof":"","revisedto":"","release":"Rel-13","crspec":"","crspecversion":"","workitem":[{"winame":"MCPTT-CT"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"C1-162978 \/ S3-160906","lsto":"CT1","Cc":"SA6, CT4","lsoriginalls":"S3-161225","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_74bis_Guilin\/Docs\/C4-165014.zip","group":"C4","meeting":"C4-74","year":2016,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"C4-165015","title":"Reply LS on Introduction of simulcast and pause-resume usage into MMCMH","source":"SA4","contact":"Bo Burman","contact-id":16624,"tdoctype":"LS in","for":"Action","abstract":"SA4 thanks CT4 for their incoming reply LS (C4-164271) on \u201cIntroduction of simulcast and pause-resume usage into MMCMH\u201d and for their comments, and is happy to provide CT working groups with more information regarding Multi-stream Multiparty Conferencing Media Handling (Annexes S and T in 3GPP TS 26.114).\n\nThe reply LS from CT4 included a few questions, for which SA4 can provide the following answers.","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":"2016-09-26 22:24:48","uploaded":"2016-09-26 22:36:28","revisionof":"","revisedto":"","release":"Rel-14","crspec":"","crspecversion":"","workitem":[{"winame":"MMCMH_Enh-CT"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"C4-164271","lsto":"CT4, CT1, CT3","Cc":"","lsoriginalls":"S4-161030","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_74bis_Guilin\/Docs\/C4-165015.zip","group":"C4","meeting":"C4-74","year":2016,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"C4-165016","title":"LS on corrections of EVS specifications","source":"SA4","contact":"Stephane Ragot","contact-id":32055,"tdoctype":"LS in","for":"Action","abstract":"SA4 would like to inform CT3 and CT4 that corrections have been made to three EVS specifications (TS 26.445 Annex A, TS 26.454, TS 26.103).","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":"2016-09-26 22:28:06","uploaded":"2016-09-26 22:36:28","revisionof":"","revisedto":"","release":"Rel-12","crspec":"","crspecversion":"","workitem":[{"winame":"EVS_codec"},{"winame":"EVSoCS"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT3, CT4","Cc":"CT1","lsoriginalls":"S4-161085","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_74bis_Guilin\/Docs\/C4-165016.zip","group":"C4","meeting":"C4-74","year":2016,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"C4-165017","title":"Reply LS to LS reply from CT4 to SA5 on progress of the work on Diameter Base Protocol Update","source":"SA5","contact":"Maryse Gardella","contact-id":68914,"tdoctype":"LS in","for":"Action","abstract":"Based on the confirmation from CT4 regarding Diameter extensibility rules,SA5 acknowledges that existing text in the TR 29.819 already addresses SA5 concern and the need for a suitable solution aligned with these rules. \n\nTo this intent, SA5 has approved (during SA5#109), a study on forward compatibility for 3GPP Diameter charging applications. \n\nThe study, as approved from SA5#109 is attached. \n\nSA5 will share information with CT4 as the study progresses, and welcome input from CT4.","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":"2016-09-26 22:30:53","uploaded":"2016-09-26 22:36:28","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":[{"winame":"FS_DBPU"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT4","Cc":"CT3","lsoriginalls":"S5-165223","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_74bis_Guilin\/Docs\/C4-165017.zip","group":"C4","meeting":"C4-74","year":2016,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"C4-165018","title":"Reply LS to SA2 CT4 Response LSs on Control Plane CIoT Optimisation Indicator propagated to PGW for charging purpose","source":"SA5","contact":"Maryse Gardella","contact-id":68914,"tdoctype":"LS in","for":"Action","abstract":"SA5 thanks SA2 and CT4 for their response LSs on the Control Plane CIoT EPS Optimisation Indicator propagated to PGW for charging purpose.\n \nBased on SA2 confirmation on SGW capability to differentiate between data sent over S11-U and data sent over S1-U, SA5 will keep the already specified separate data volume recording by the SGW. \n\nSA5 understands that SA2 sees no strong need for the PGW to also be aware of which bearer (S11-U or S1-U) is used for the data transfer, since this is expected to be solely under VPLMN control (i.e. SGW level), therefore no mean has been specified to this intent.    \n\nConsequently, SA5 has re-evaluated the requirement for the PGW to record data volume differentiated between the bearers used by the SGW during data transfer, by considering inter-PLMN charging aspects. SA5 came to the same conclusion, i.e. since the bearer selection is fully under VPLMN control, this cannot be a criterion for inter-PLMN charging settlements.","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":"2016-09-26 22:34:29","uploaded":"2016-09-26 22:36:28","revisionof":"","revisedto":"","release":"Rel-13","crspec":"","crspecversion":"","workitem":[{"winame":"CIoT-CT"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S5-165046\/S2-163768, S5-165042\/C4-164288","lsto":"SA2, CT4","Cc":"","lsoriginalls":"S5-165280","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_74bis_Guilin\/Docs\/C4-165018.zip","group":"C4","meeting":"C4-74","year":2016,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"C4-165019","title":"LS to IETF for clarification on RFC 4006 for Diameter Base Protocol","source":"IETF DIME WG","contact":"Lionel Morand","contact-id":25150,"tdoctype":"LS in","for":"Information","abstract":"The IETF DIME WG thanks the 3GPP SA5 WG for their LS and query regarding the IETF RFC 4006 (https:\/\/datatracker.ietf.org\/liaison\/1470\/).\n\nThe IETF DIME WG has discussed both options raised in the LS from 3GPP SA5:\n\n1)\t Is IETF RFC 4006 planned to be updated in order to rely on IETF RFC 6733 as the new Diameter Base protocol?\n\n2)\tIf not, are there any recommendations from IETF on how to address the implicit reference to IETF RFC 3588 as Diameter Base Protocol for 3GPP SA5 Diameter Online charging through use of IETF RFC 4006?\n\nand the decision was made to update of the IETF RFC 4006 as per the option 1). \n\nThe aim of this update is to:\n-\talign the Diameter Credit-Control application specification with the IETF RFC 6733,\n-\tfix existing known issues in the current specification,\n-\tcomply with the recommendations given in the IETF RFC 7423 on the design of Diameter application. \n\nThe time line for the completion of the RFC 4006 update is set to November 2017.","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":"2016-09-27 19:18:13","uploaded":"2016-09-27 19:26:34","revisionof":"","revisedto":"","release":"Rel-14","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S5-162220","lsto":"SA5","Cc":"CT4, CT3","lsoriginalls":"IETF DIME WG LS","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_74bis_Guilin\/Docs\/C4-165019.zip","group":"C4","meeting":"C4-74","year":2016,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"C4-165020","title":"Reply LS on Cooperation on NGS FMC","source":"SA","contact":"Johannes Achter","contact-id":5595,"tdoctype":"LS in","for":"Information","abstract":"TSG SA endorses the informal conference call between SA2 and BBF as well as the expert workshop to scope the cooperation and identify the work areas. TSG SA chair in collaboration with BBF leadership will take the necessary steps to work on the procedures, agenda and list of participants to set up the close cooperation and workshop arrangements.\n\nFurthermore TSG SA wants to inform BBF, that TSG SA#73 updated the time schedule of the TR 23.799 'Study on Architecture for Next Generation System' to be approved in TSG SA#74 in Dec 2016.  \n\nNext steps agreed and endorsed by TSG SA#73:\n-\tOctober 2016: SA2-BBF conference call to identify potential areas of collaboration at the system architecture level for the discussion at the workshop\n-\tQ1 2017: 3GPP-BBF expert workshop \u2013 the objective of the workshop is to identify the next steps to improve the collaboration between 3GPP and BBF","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":"2016-09-27 19:22:28","uploaded":"2016-09-27 19:26:34","revisionof":"","revisedto":"","release":"Rel-14","crspec":"","crspecversion":"","workitem":[{"winame":"FS_NextGen"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA2","Cc":"SA1, SA3, SA5, CT, CT1, CT3, CT4","lsoriginalls":"SP-160743","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_74bis_Guilin\/Docs\/C4-165020.zip","group":"C4","meeting":"C4-74","year":2016,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"C4-165021","title":"Completion of SA3-LI Study TR 33.827 on S8HR","source":"SA","contact":"Alex Leadbeater","contact-id":71428,"tdoctype":"LS in","for":"Information","abstract":"At SA3-LI#62BIS, SA3-LI completed work on the S8HR LI feasibility study in TR33.827. At SA#73, SA have approved the TR for publication in R14. SA kindly asks GSMA, to review the TR (attached as v1.0.0 in SP-160606.zip), and consider how to address the issues within GSMA scope identified in the evaluation and conclusion sections.\n\nThe study broadly concludes that it is possible to meet LI requirements for S8HR in the VPLMN subject to normative implementation of solutions in TR33.827 in TS33.107 and TS33.108. However, the study concludes that GSMA will need to make specific provision for LI and separately Retained Data (RD), in roaming agreements relating to use of confidentiality disabling at the IMS level and enabling over S8.","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":"2016-09-27 19:26:00","uploaded":"2016-09-27 19:26:34","revisionof":"","revisedto":"","release":"Rel-14","crspec":"","crspecversion":"","workitem":[{"winame":"FS_LIV8"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"GSMA NG, GSMA WAS, GSMA PSMC","Cc":"SA3\/LI, SA2, CT, CT1, CT4","lsoriginalls":"SP-160744","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_74bis_Guilin\/Docs\/C4-165021.zip","group":"C4","meeting":"C4-74","year":2016,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"C4-165184","title":"LS to 3GPP CT4 Diameter Wait Timers","source":"GSMA PACKET#87","contact":"Kimmo Kymalainen","contact-id":19464,"tdoctype":"LS in","for":"Action","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":"2016-10-07 16:22:57","uploaded":"2016-10-07 16:26:10","revisionof":"","revisedto":"C4-166007","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT4","Cc":"","lsoriginalls":"88_107 Packet","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_74bis_Guilin\/Docs\/C4-165184.zip","group":"C4","meeting":"C4-74","year":2016,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"C4-165200","title":"LS on Flexible eNB-ID and Cell-ID in E-UTRAN","source":"RAN3","contact":"Zheng Zhou","contact-id":38699,"tdoctype":"LS in","for":"Action","abstract":"RAN3 is working on the WID of Flexible eNB-ID and Cell-ID in E-UTRAN to support number of eNB beyond 1.04 million in a PLMN and support more cells in an eNB, while keeping the length of the E-UTRAN CGI unchanged. RAN3 have decided to include two additional choices of eNB ID:\n-\tLong Macro eNB ID : 21 bits \n-\tShort Macro eNB ID: 18 bits \nRAN3 understands all the messages involving eNB ID will be impacted.","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":"2016-10-16 23:53:36","uploaded":"2016-10-17 00:07:56","revisionof":"","revisedto":"C4-166009","release":"Rel-14","crspec":"","crspecversion":"","workitem":[{"winame":"LTE_FNBID-Core"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT1, CT4, SA5, RAN6","Cc":"RAN2,SA2","lsoriginalls":"R3-162637","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_74bis_Guilin\/Docs\/C4-165200.zip","group":"C4","meeting":"C4-74","year":2016,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"C4-165204","title":"LS on Enhanced Coverage authorization impact on cell and PLMN selection procedures","source":"SA2","contact":"Miguel Griot","contact-id":43100,"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":"2016-10-17 02:30:48","uploaded":"2016-10-17 02:33:52","revisionof":"","revisedto":"","release":"Rel-14","crspec":"","crspecversion":"","workitem":[{"winame":"FS_CIoT_Ext"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN2, CT1","Cc":"","lsoriginalls":"S2-165214","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_74bis_Guilin\/Docs\/C4-165204.zip","group":"C4","meeting":"C4-74","year":2016,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]