[{"name":"CP-180115","title":"LS on Reply on 5G Specification of N28 interface","source":"CT3","contact":"Kimmo Kymalainen","contact-id":19464,"tdoctype":"LS in","for":"Information","abstract":"CT3 asks SA2 to kindly clarify if SA2 still intends to provide a service definition for the N28 interface in the Rel-15 timeframe, or if SA2 expects CT3 to base the stage 3 work only on the available procedural stage 2 description and design a suitable service based interface as part of the stage 3 work.","secretary_remarks":"","agenda_item_sort_order":8,"ainumber":"4.1","ainame":"Incoming liaisons","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2018-03-12 08:38:39","uploaded":"2018-03-12 08:57:28","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":[{"winame":"5GS_Ph1-CT"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"C3-180022\/ S2-179226","lsto":"SA2","Cc":"SA5, CT","lsoriginalls":"C3-180174","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/TSG_CT\/TSGC_79_Chennai\/Docs\/CP-180115.zip","group":"CP","meeting":"CP-79","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"CP-180116","title":"LS on user plane protocol study","source":"CT4","contact":"Kimmo Kymalainen","contact-id":19464,"tdoctype":"LS in","for":"Information","abstract":"CT4 respectfully asks IETF DMM to provide any information that may be relevant to the above CT4 work by July 2018.","secretary_remarks":"","agenda_item_sort_order":8,"ainumber":"4.1","ainame":"Incoming liaisons","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2018-03-12 08:41:13","uploaded":"2018-03-12 08:57:28","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"FS_UPPS"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"IETF DMM","Cc":"CT","lsoriginalls":"C4-181380","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/TSG_CT\/TSGC_79_Chennai\/Docs\/CP-180116.zip","group":"CP","meeting":"CP-79","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"CP-180117","title":"LS on Invitation to update the information in the IMT2020 roadmap [to ITU study groups and external IMT-2020 liaison partners]","source":"The ITU-T Joint Coordination Activity for IMT2020","contact":"Kimmo Kymalainen","contact-id":19464,"tdoctype":"LS in","for":"Information","abstract":"The ITU-T Joint Coordination Activity for IMT2020 (JCA IMT2020) thanks all that have replied to previous requests for input on IMT-2020 related standardization work. The current version of the roadmap is available from the JCA-IMT2020 website.","secretary_remarks":"","agenda_item_sort_order":8,"ainumber":"4.1","ainame":"Incoming liaisons","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2018-03-12 08:43:33","uploaded":"2018-03-12 08:57:28","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"3GPP","Cc":"","lsoriginalls":"JCA-IMT2020-O-003  JCA-IMT2020","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/TSG_CT\/TSGC_79_Chennai\/Docs\/CP-180117.zip","group":"CP","meeting":"CP-79","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"CP-180118","title":"Architectural Proposal for the Handling of Network Operations Data with Specific Focus on Virtualized Networks","source":"NGMN Alliance Project \u2013 Network Management & Orchestration Working Group","contact":"Kimmo Kymalainen","contact-id":19464,"tdoctype":"LS in","for":"Discussion","abstract":"The purpose of this liaison paper is to draw vendors\u2019 attention to a new technical direction which operators are keen to explore and develop further. In particular, the paper proposes an architectural solution which outlines operators\u2019 desires to achieve improved access to network data in order to broaden analytics capabilities and overcome some of today\u2019s functional limitations. \n\nThe NGMN Network Management and Orchestration Working Group requests vendors and probe suppliers review the paper with a view to incorporating the proposed architecture and requirements into their future solutions.","secretary_remarks":"","agenda_item_sort_order":8,"ainumber":"4.1","ainame":"Incoming liaisons","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2018-03-12 08:46:08","uploaded":"2018-03-12 08:57:28","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"3GPP, ETSI, TM Forum","Cc":"","lsoriginalls":"NGMN_LS_Future_Network_Tracing","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/TSG_CT\/TSGC_79_Chennai\/Docs\/CP-180118.zip","group":"CP","meeting":"CP-79","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"CP-180119","title":"Reply LS on NR interworking with GSM and UMTS","source":"ETSI","contact":"Kimmo Kymalainen","contact-id":19464,"tdoctype":"LS in","for":"Information","abstract":"Agreement: \n?\tRAN4 confirms that legacy EPS\/E-UTRA interworking with GSM, UTRA FDD and UTRA TDD in EN-DC operation can be supported from RAN4 perspective in Rel-15. \n?\tRAN4 will accordingly develop requirements to support legacy EPS\/E-UTRA interworking with GSM, UTRA FDD and UTRA TDD in EN-DC operation. RAN4 has planned to complete all the necessary requirements to support EPS\/E-UTRA interworking with GSM, UTRA FDD and UTRA TDD in EN-DC in Rel-15.","secretary_remarks":"","agenda_item_sort_order":8,"ainumber":"4.1","ainame":"Incoming liaisons","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2018-03-12 08:48:08","uploaded":"2018-03-12 08:57:28","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":[{"winame":"NR_newRAT"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"RP-172823","lsto":"RAN","Cc":"SA WG1, SA WG2, RAN WG2, RAN WG3, RAN WG4, RAN WG5, RAN WG6, TSG SA, TSG CT","lsoriginalls":"R4-1802691","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/TSG_CT\/TSGC_79_Chennai\/Docs\/CP-180119.zip","group":"CP","meeting":"CP-79","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"CP-180120","title":"LS on interworking mechanisms between 5G System and legacy RATs","source":"RAN","contact":"Kimmo Kymalainen","contact-id":19464,"tdoctype":"LS in","for":"Information","abstract":"To avoid possible confusion between Working Groups, RAN plenary wishes to repeat its earlier decision that \nno interworking is expected in Rel-15 between the 5G System (5GS) and 2G (GSM)\/3G (UMTS).\n\nThis means:\n-\tNo NAS interworking mechanisms between 5GS and GSM\/UMTS\n-\tNo Access-Stratum interworking mechanisms between GSM\/UMTS and 5G NR.\n-\tFor E-UTRA deployments with 5GC (i.e. deployment Options 5 and 7), Access-Stratum interworking between GSM\/UMTS and E-UTRA continues to be possible without changes to GSM\/UMTS\/E-UTRAN specifications, enabling:\n-\tIdle mode cell reselection\n-\tConnected mode measurements to support redirection at RRC connection release, CS call release, TBF release once in idle mode\n-\tFor EN-DC (i.e. deployment Option 3), legacy EPS\/E-UTRA interworking with GSM\/UMTS shall be fully supported.\n\nNote that even without AS interworking mechanisms it is possible for a UE that is initially camped on an NR cell (respectively GERAN\/UTRA cell) to lose coverage.","secretary_remarks":"","agenda_item_sort_order":8,"ainumber":"4.1","ainame":"Incoming liaisons","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2018-03-12 08:50:11","uploaded":"2018-03-12 08:57:28","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG1, SA WG2, RAN WG2, RAN WG3, RAN WG4, RAN WG5, RAN WG6","Cc":"TSG SA, TSG CT","lsoriginalls":"RP-172823","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/TSG_CT\/TSGC_79_Chennai\/Docs\/CP-180120.zip","group":"CP","meeting":"CP-79","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"CP-180121","title":"LS on the number of data bearers","source":"RAN","contact":"Kimmo Kymalainen","contact-id":19464,"tdoctype":"LS in","for":"Discussion","abstract":"TSG RAN received several LS documents \u2013 from RAN WG2, CT WG1, CT WG4 and SA WG2 \u2013 regarding the feasibility of having extended number of data bearers for LTE. Following the preference from SA WG2, TSG RAN will initiate the normative work to support 15 data bearers in LTE with the target completion date of June 2018.","secretary_remarks":"","agenda_item_sort_order":8,"ainumber":"4.1","ainame":"Incoming liaisons","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2018-03-12 08:52:01","uploaded":"2018-03-12 08:57:28","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA, CT","Cc":"RAN WG2, RAN WG3, SA WG2, CT WG1, CT WG4","lsoriginalls":"RP-172836","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/TSG_CT\/TSGC_79_Chennai\/Docs\/CP-180121.zip","group":"CP","meeting":"CP-79","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"CP-180122","title":"LS on indicating service continuity usage of the additional IPv6 prefix in Router Advertisement","source":"SA2","contact":"Kimmo Kymalainen","contact-id":19464,"tdoctype":"LS in","for":"Information","abstract":"SA2 would like to kindly ask IETF DMM working group to keep SA2 updated of the work on the subject of including property meta-data in IPv6 ND address assignment procedures for potential use in the 5G System to indicate the mobility property of additional IPv6 prefixes assigned as part of the Multi-homed IPv6 PDU Session functionality.","secretary_remarks":"","agenda_item_sort_order":8,"ainumber":"4.1","ainame":"Incoming liaisons","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2018-03-12 08:54:08","uploaded":"2018-03-12 08:57:28","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-181481","lsto":"IETF Internet Area, IETF DMM","Cc":"IETF 6MAN, CT1, CT","lsoriginalls":"S2-182967","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/TSG_CT\/TSGC_79_Chennai\/Docs\/CP-180122.zip","group":"CP","meeting":"CP-79","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"CP-180123","title":"LS on SoR mechanism","source":"SA3","contact":"Kimmo Kymalainen","contact-id":19464,"tdoctype":"LS in","for":"Discussion","abstract":"SA3 considers that triggering the SoR during the initial registration is possible after the Authentication procedure is completed.\n \nBased on the above, SA3considers that the procedure described in C1-180462 is not acceptable. SA3 requests that this procedure to be re-considered.","secretary_remarks":"","agenda_item_sort_order":8,"ainumber":"4.1","ainame":"Incoming liaisons","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2018-03-12 08:56:52","uploaded":"2018-03-12 08:57:28","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":[{"winame":"5GS_Ph1-CT"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"C1-180761","lsto":"CT, CT1, SA3-LI","Cc":"CT6, SA2, CT3, SA1","lsoriginalls":"S3-180998","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/TSG_CT\/TSGC_79_Chennai\/Docs\/CP-180123.zip","group":"CP","meeting":"CP-79","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"CP-180146","title":"Statement on urgency of alignment of ETSI SSP with 3GPP release 15","source":"GSMA Technology Group","contact":"David Hutton","contact-id":33294,"tdoctype":"LS in","for":"Discussion","abstract":"GSMA recommends that both ETSI TC SCP and 3GPP to break any linkage between SSP and 3GPP release 15 to allow adequate time for ETSI TC SCP to complete their work.\nThe GSMA, with its operator members, will actively contribute in the development of these specifications in a timely manner.\nCurrently the industry and operators are progressively adopting the eSIM specifications developed by the GSMA. Even if the SSP seems to provide added value to the industry, the development of SSP can be postponed to R16 at the earliest.","secretary_remarks":"","agenda_item_sort_order":8,"ainumber":"4.1","ainame":"Incoming liaisons","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2018-03-19 02:32:04","uploaded":"2018-03-19 02:33:50","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"ETSI TC SCP, 3GPP SA, 3GPP CT, 3GPP SA3, 3GPP CT6","Cc":"","lsoriginalls":"TG Doc 07_022 LS","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/TSG_CT\/TSGC_79_Chennai\/Docs\/CP-180146.zip","group":"CP","meeting":"CP-79","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]