[{"name":"C4-175182","title":"Reply LS on request to update maximum data rate values in EPS","source":"CT1","contact":"Lena Chaponniere","contact-id":38080,"tdoctype":"LS in","for":"Information","abstract":"CT1 thanks SA2 for their LS requesting to update maximum data rate values in EPS.\nCT1 would like to inform SA2 that CT1 has agreed CRs in attached C1-173784 and C1-173785 to define new IEs enabling the network to convey maximum bit rates of up to 16 zetta (10^21) bit\/s to the UE.","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-10-12 07:39:29","uploaded":"2017-10-12 08:22:45","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":[{"winame":"5GS_Ph1-CT"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-173684","lsto":"3GPP TSG SA WG2","Cc":"3GPP TSG RAN WG3, 3GPP TSG CT WG4, 3GPP TSG CT WG3, 3GPP TSG SA WG5, 3GPP TSG SA WG1, 3GPP TSG RAN WG2","lsoriginalls":"C1-173572","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_80_Kochi\/Docs\/C4-175182.zip","group":"C4","meeting":"C4-80","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"C4-175183","title":"LS on (de-)registration procedure for SMS over NAS","source":"CT1","contact":"Sung Hwan Won","contact-id":70307,"tdoctype":"LS in","for":"Information","abstract":"CT1\u2019s understanding is that the registration procedure for SMS over NAS captured in subclause 4.13.3.1 of 3GPP TS 23.502 allows two alternatives for sending registration accept message as shown in steps 3a and 3b. CT1 has a concern on the alternative stated via step 3a because the failure in SMSF selection and\/or SMS activation towards the SMSF after sending the registration accept message would make abnormal behavior handling in the 5GMM sublayer complex.\nIn addition, CT1 considers that it is not necessary to mandate the deletion of the SMSF address from the UE context after notifying the SMSF that the UE is deregistered from the SMS over NAS service. To CT1\u2019s knowledge, as the allocation of an SMSF can be static for the UE, if the UE context is valid, it makes more sense to keep the SMSF address in the UE context and just deactivate the SMS over NAS service towards the SMSF, marking the UE as unable to use SMS over NAS in the UE context.","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-10-12 07:41:45","uploaded":"2017-10-12 08:22:45","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":[{"winame":"5GS_Ph1-CT"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA2","Cc":"CT4","lsoriginalls":"C1-173573","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_80_Kochi\/Docs\/C4-175183.zip","group":"C4","meeting":"C4-80","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"C4-175185","title":"LS on applicability of service based interface for legacy core network elements","source":"CT1","contact":"Jennifer Liu","contact-id":43418,"tdoctype":"LS in","for":"Information","abstract":"CT1 would like to get clarification from SA2 on the following:\n\n?\tDoes service based architecture apply to legacy core network elements, such as CBC in Public Warning System?  \n\n?\tCan point to point interface be used between 5G core network functions and legacy core network elements?\n\n?\tIf point to point interface can be used, is there a requirement to support both interfaces?","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-10-12 07:46:09","uploaded":"2017-10-12 08:22:45","revisionof":"","revisedto":"","release":"Rel-14","crspec":"","crspecversion":"","workitem":[{"winame":"5GS_Ph1-CT"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA2","Cc":"CT3, CT4, SA1, SA3","lsoriginalls":"C1-173753","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_80_Kochi\/Docs\/C4-175185.zip","group":"C4","meeting":"C4-80","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"C4-175189","title":"LS on Evolution of IMSI format and E.212 Recommendation","source":"CT","contact":"Lionel Morand","contact-id":25150,"tdoctype":"LS in","for":"Information","abstract":"3GPP SA is kindly asked to consider the proposed treatment of the LS received from ITU-T Study Group 2 on Evolution of IMSI format and E.212 Recommendation and to respond to 3GPP CT and CT4. Specifically, it would be appreciated if SA were to identify required working groups to involve in this activity.","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-10-12 07:54:42","uploaded":"2017-10-12 08:22:45","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":[{"winame":"TEI15"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"3GPP SA","Cc":"3GPP CT4, 3GPP CT1, 3GPP CT3, 3GPP SA5","lsoriginalls":"CP-172153","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_80_Kochi\/Docs\/C4-175189.zip","group":"C4","meeting":"C4-80","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"C4-175197","title":"TSG Announcing TS.37 V3.0","source":"GSMA TSG Requirements for Multi-SIM devices group","contact":"Kimmo Kymalainen","contact-id":19464,"tdoctype":"LS in","for":"Discussion","abstract":"TSG would like to request that TS.37 is used by all Mobile Network Operators (MNO) when \/ if they are specifying devices with multiple SIM.\nIf there are any requirements detailed in TS.37 that do not meet the needs of MNOs, then these should be communicated back to TSG. \nIf there are any requirements in TS.37 which are unclear to manufacturers, then these should be communicated back to TSG\nSimilarly, if omissions are identified, these should also be communicated to TSG.","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-10-12 08:21:51","uploaded":"2017-10-12 08:22:45","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":[{"winame":"TEI15"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"GCF SG, PTCRB, BABT, TAF, MSAI, 3GPP CT4, 3GPP CT6","Cc":"","lsoriginalls":"TSGRMS09_03","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_80_Kochi\/Docs\/C4-175197.zip","group":"C4","meeting":"C4-80","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"C4-175219","title":"LS on details of network identifiers","source":"RAN2","contact":"Malik Wahaj Arshad","contact-id":72857,"tdoctype":"LS in","for":"Information","abstract":"Questions to CT4:\nTo further progress details of RRC signalling, RAN2 respectfully ask CT4 the following question: \n1.\tRAN2 would request CT4 to provide the length of 5G-S-TMSI along with its constituent identifiers including AMF Set ID, AMF Pointer and 5G-TMSI. RAN2 would also request CT4 to provide the length of AMF Region ID.","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-10-22 09:53:00","uploaded":"2017-10-22 10:02:39","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":[{"winame":"LTE_5GCN_connect"},{"winame":"NR_newRAT-Core"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG4, SA WG2","Cc":"","lsoriginalls":"R2-1712068","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_80_Kochi\/Docs\/C4-175219.zip","group":"C4","meeting":"C4-80","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"C4-175220","title":"Reply LS on Charging for WLAN-based ProSe Direct Discovery","source":"SA5","contact":"Yizhi Yao","contact-id":66963,"tdoctype":"LS in","for":"Information","abstract":"SA5 thanks SA2 for their LS (S2-172506) on Stage 2 completion on introduction of WLAN as alternative technology for ProSe Direct Discovery.\n\nSA5 would like to inform SA2 that SA5 has agreed to start a work item to address the charging aspects of WLAN-based ProSe Direct Discovery, the WID (S5-175313) is as attached.","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-10-22 10:00:22","uploaded":"2017-10-22 10:02:39","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":[{"winame":"ProSe_WLAN_DD"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-172506","lsto":"SA2","Cc":"CT1, Ct4","lsoriginalls":"S5-175299","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_80_Kochi\/Docs\/C4-175220.zip","group":"C4","meeting":"C4-80","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]