[{"name":"CP-170190","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":8,"ainumber":"4.1","ainame":"Incoming liaisons","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2017-02-26 22:41:18","uploaded":"2017-02-26 23:40:15","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\/TSG_CT\/TSGC_75_Dubrovnik\/Docs\/CP-170190.zip","group":"CP","meeting":"CP-75","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"CP-170191","title":"GSMA Mobile IoT response to \u201cNorthbound SCEF API standardisation requested by oneM2M\u201d","source":"GSMA Mobile IoT","contact":"Barbara Pareglio","contact-id":63010,"tdoctype":"LS in","for":"Discussion","abstract":"GSMA politely requests that 3GPP considers the availability of APIs covering the functions described above for Mobile IoT devices, in particular the example functions for exposure by the SCEF \u2013 to be considered for oneM2M Release 3.\nFeedback is kindly requested before 31 March 2017.","secretary_remarks":"","agenda_item_sort_order":8,"ainumber":"4.1","ainame":"Incoming liaisons","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2017-02-26 22:44:31","uploaded":"2017-02-26 23:40:15","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"3GPP SA, 3GPP SA1, 3GPP SA2, 3GPP CT, 3GPP CT3","Cc":"","lsoriginalls":"NBIOTDM 009_001","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/TSG_CT\/TSGC_75_Dubrovnik\/Docs\/CP-170191.zip","group":"CP","meeting":"CP-75","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"CP-170192","title":"LS on eV2X Normative Requirements Completion","source":"SA1","contact":"Ki-dong Lee","contact-id":58978,"tdoctype":"LS in","for":"Information","abstract":"Following the approval of FS_eV2X Study at SA#74 (Dec.\u201916), SA WG1 has agreed on eV2X WID (S1-171417) and completed the Normative Work at SA1#77 (Feb.\u201917). The normative requirements have been specified in S1-171204 (TS 22.abcv0.2.0), which has been sent to TSG SA for approval (Mar.\u201917), to enhance 3GPP support for V2X scenarios in the 3GPP systems (i.e., EPS, 5G system). It includes transport layer support for both safety and non-safety V2X scenarios: \n\u2022\tSafety-related V2X scenarios: e.g. automated driving, vehicle platooning \n\u2022\tNon-safety-related V2X scenarios: e.g., mobile high data rate entertainment, mobile hotspot\/office\/home, dynamic digital map update","secretary_remarks":"","agenda_item_sort_order":8,"ainumber":"4.1","ainame":"Incoming liaisons","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2017-02-26 22:46:42","uploaded":"2017-02-26 23:40:15","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":[{"winame":"FS_eV2X"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG RAN","Cc":"TSG SA, TSG CT","lsoriginalls":"S1-171461","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/TSG_CT\/TSGC_75_Dubrovnik\/Docs\/CP-170192.zip","group":"CP","meeting":"CP-75","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"CP-170193","title":"LS on standardization of Northbound SCEF API","source":"SA2","contact":"Maulik Vaidya","contact-id":68224,"tdoctype":"LS in","for":"Information","abstract":"SA WG2 would like to inform TSG SA that SA WG2 has agreed to a WID (WID on Northbound APIs for SCEF \u2013 SCS\/AS Interworking) which is submitted for TSG SA approval. SA WG2 is taking on the task of defining architectural description (including message flows, and parameters) of the northbound API(s) between the SCEF and the SCS \/AS for exposing the services and capabilities provided by 3GPP network interfaces.\nPending approval of the WID, SA WG2 recommends TSG SA to notify external organizations (oneM2M, OMA-ARC, GSMA etc) which have expressed interest in SCEF Northbound API standardization.","secretary_remarks":"","agenda_item_sort_order":8,"ainumber":"4.1","ainame":"Incoming liaisons","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2017-02-26 22:49:19","uploaded":"2017-02-26 23:40:15","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"3GPP TSG SA","Cc":"3GPP CT, 3GPP CT WG3, 3GPP SA WG3, 3GPP SA WG5, 3GPP SA WG1","lsoriginalls":"S2-170647","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/TSG_CT\/TSGC_75_Dubrovnik\/Docs\/CP-170193.zip","group":"CP","meeting":"CP-75","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"CP-170194","title":"Response to LS on SA2 involvement for the light connection","source":"SA2","contact":"Hans Ronneke","contact-id":25844,"tdoctype":"LS in","for":"Information","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":8,"ainumber":"4.1","ainame":"Incoming liaisons","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2017-02-26 22:51:12","uploaded":"2017-02-26 23:40:15","revisionof":"","revisedto":"","release":"Rel-14","crspec":"","crspecversion":"","workitem":[{"winame":"LTE_LIGHT_CON-Core"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT1, RAN2, RAN3, SA3-LI, CT4, SA","Cc":"RAN, CT","lsoriginalls":"S2-170695","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/TSG_CT\/TSGC_75_Dubrovnik\/Docs\/CP-170194.zip","group":"CP","meeting":"CP-75","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"CP-170195","title":"LS out on PWS support in 5G System","source":"SA2","contact":"Takeshi Usui","contact-id":59388,"tdoctype":"LS in","for":"Information","abstract":"SA2 has started the normative work for 5G System (5GS) in Release 15. SA2 discussed how 5GS supports Public Warning System (PWS) in Release 15. As far as E-UTRAN part of 5G RAN is concerned, SA2 assumes that it shall have the same functionality as E-UTRAN for PWS. SA2 expects that PWS in TS 23.041 will be enhanced under the responsibility of CT1 WG in order that 5GS supports PWS.","secretary_remarks":"","agenda_item_sort_order":8,"ainumber":"4.1","ainame":"Incoming liaisons","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2017-02-26 22:53:49","uploaded":"2017-02-26 23:40:15","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT1","Cc":"TSG CT, TSG RAN and TSG SA","lsoriginalls":"S2-171310","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/TSG_CT\/TSGC_75_Dubrovnik\/Docs\/CP-170195.zip","group":"CP","meeting":"CP-75","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"CP-170196","title":"LS on subscription-based restrictions on attach without PDN connection","source":"SA2","contact":"Hannu Hietalahti","contact-id":69922,"tdoctype":"LS in","for":"Information","abstract":"SA2 has further discussed the issue after sending the previous SA2 LS in S2-170700 related to subscription-based restrictions for UEs capable of attach without PDN connection. SA2 would like to provide the following comments. \nSA2 believes that there is a misalignment between the 3GPP TS 29.272 requirement in CT4 to reject the attach in EMM layer and 24.301 requirement in CT1 to accept the attach but not the PDN connectivity request when the network enforces the PDN connection restriction. \nSA2 would kindly request CT1 and CT4 to fix this misalignment between 29.272 and 24.301 so that SA2 specification TS 23.401 can be aligned accordingly. \nSA2 would also like to ask whether the PDN connection restriction flag is intended to affect also exception reporting and other high priority connection, such as emergency?","secretary_remarks":"","agenda_item_sort_order":8,"ainumber":"4.1","ainame":"Incoming liaisons","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2017-02-26 22:56:01","uploaded":"2017-02-26 23:40:15","revisionof":"","revisedto":"","release":"Rel-13","crspec":"","crspecversion":"","workitem":[{"winame":"CIoT-CT"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT1, CT4","Cc":"TSG CT","lsoriginalls":"S2-171408","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/TSG_CT\/TSGC_75_Dubrovnik\/Docs\/CP-170196.zip","group":"CP","meeting":"CP-75","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"CP-170197","title":"LS on N2 and N3 reference points for 5G system","source":"SA2","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"LS in","for":"Information","abstract":"SA2 would like to inform TSG RAN, TSG SA, RAN WG3, CT WG1, CT WG4 that SA2 is defining an access agnostic architecture wherein the 5G Core interfaces the 5G-AN with  common interface (N2\/N3). In other words, SA2 assumes that N2 and N3 defined between 5G-RAN and the 5G Core are also used to connect standalone non-3GPP Access  Networks to 5G core network control-plane functions and user-plane functions respectively. \n\nSA2 is currently defining common procedures for 5G-RAN and non 3GPP Access Network, and therefore assumes that \n-\ta single control plane protocol is defined for N2. \n-\ta single user plane protocol  is  used for 5G-RAN and non 3GPP Access Network as well as over N9.\n-\tThe single protocols mentioned above may have access dependent features\n\nSA2 understands the current terms of reference for RAN WG3 are focused on providing the specifications for protocols on the 5G-RAN - 5G Core Network interfaces.","secretary_remarks":"","agenda_item_sort_order":8,"ainumber":"4.1","ainame":"Incoming liaisons","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2017-02-26 22:58:43","uploaded":"2017-02-26 23:40:15","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG RAN, TSG SA","Cc":"TSG CT, RAN WG3, CT WG4, CT WG1, SA WG3, RAN WG2","lsoriginalls":"S2-171611","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/TSG_CT\/TSGC_75_Dubrovnik\/Docs\/CP-170197.zip","group":"CP","meeting":"CP-75","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"CP-170198","title":"Reply LS on external interface for TV services","source":"SA3","contact":"Anand Palanigounder","contact-id":26706,"tdoctype":"LS in","for":"Information","abstract":"SA3 discussed the security for the xMB interface and agreed that TLS is a suitable protocol for securing the interface. SA3 also recommends that SA4 and CT3 reference TS 33.310 for TLS related specification aspects (e.g., TLS version to support\/use, TLS\/certificate profiles) instead of specifying them in their TS.\n\nRegarding xMB related security aspects (including authentication and authorization), SA3 plans to perform a security analysis and specify suitable security mechanisms in an appropriate TS under SA3 responsibility (e.g., a new Annex in TS 33.246) by the next SA3 meeting.","secretary_remarks":"","agenda_item_sort_order":8,"ainumber":"4.1","ainame":"Incoming liaisons","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2017-02-26 23:26:55","uploaded":"2017-02-26 23:40:15","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":[{"winame":"AE_enTV-MI_MTV"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA4, CT3","Cc":"SA2, SA, CT","lsoriginalls":"S3-170356","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/TSG_CT\/TSGC_75_Dubrovnik\/Docs\/CP-170198.zip","group":"CP","meeting":"CP-75","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"CP-170199","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":8,"ainumber":"4.1","ainame":"Incoming liaisons","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2017-02-26 23:29:06","uploaded":"2017-02-26 23:40:15","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\/TSG_CT\/TSGC_75_Dubrovnik\/Docs\/CP-170199.zip","group":"CP","meeting":"CP-75","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"CP-170200","title":"Reply LS on xMB Interface for TV Services","source":"SA4","contact":"Imed Bouazizi","contact-id":37548,"tdoctype":"LS in","for":"Information","abstract":"SA4 kindly asks CT3 to take the responses and the agreed CR into account for the specification of the stage 3 of the xMB interface.","secretary_remarks":"","agenda_item_sort_order":8,"ainumber":"4.1","ainame":"Incoming liaisons","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2017-02-26 23:31:48","uploaded":"2017-02-26 23:40:15","revisionof":"","revisedto":"","release":"Rel-14","crspec":"","crspecversion":"","workitem":[{"winame":"AE_enTV-CT"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S4-170172","lsto":"SA4","Cc":"SA2, SA3, SA, CT","lsoriginalls":"S4-170240","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/TSG_CT\/TSGC_75_Dubrovnik\/Docs\/CP-170200.zip","group":"CP","meeting":"CP-75","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"CP-170201","title":"LS on the completion of ITU-T Focus Group on IMT-2020 and start of normative work in ITU-T Study Group 13","source":"ITU-T Focus Group IMT-2020","contact":"Peter Ashwood-Smith","contact-id":47832,"tdoctype":"LS in","for":"Discussion","abstract":"We would like to inform you that from its establishment under ITU-T Study Group 13 (SG13) on 1 May 2015 until its final meeting in Geneva, 5-9 December 2016, the ITU-T Focus Group on IMT 2020 (FG IMT-2020) has identified 85 non-radio standards gaps for IMT-2020 (so-called 5G), and developed a set of draft Recommendations and Technical Reports addressing several gaps identified in various technical areas and non-radio aspects of 5G: \n\u2013\tnetwork architecture with fixed-mobile convergence, \n\u2013\tnetwork softwarization, \n\u2013\tend-to-end quality of service, \n\u2013\tend-to-end network management, \n\u2013\tfronthaul\/backhaul, \n\u2013\tinformation centric networking (ICN). \nThe group also held a workshop and demo day during its last meeting to showcase networking innovations that support the diverse range of envisioned 5G use cases, use cases which span from automated driving to industrial robotics and tele-surgery.","secretary_remarks":"","agenda_item_sort_order":8,"ainumber":"4.1","ainame":"Incoming liaisons","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2017-02-26 23:33:58","uploaded":"2017-02-26 23:40:15","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"ITU-R WP5D, IEEE 802.1\/802.3, IEEE SA, 3GPP, ETSI ISG NFV, ARIB, ATIS, CCSA, TTA, TTC, OIF, ONF, IETF\/IRTF, NGMN Alliance, GSMA","Cc":"","lsoriginalls":"IMT \u2013 LS 004 \u2013 E","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/TSG_CT\/TSGC_75_Dubrovnik\/Docs\/CP-170201.zip","group":"CP","meeting":"CP-75","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"CP-170202","title":"We would like to inform you that from its establishment under ITU-T Study Group 13 (SG13) on 1 May 2015 until its final meeting in Geneva, 5-9 December 2016, the ITU-T Focus Group on IMT 2020 (FG IMT-2020) has identified 85 non-radio standards gaps for IMT-2020 (so-called 5G), and developed a set of draft Recommendations and Technical Reports addressing several gaps identified in various technical areas and non-radio aspects of 5G:","source":"ITU-T Study Group 12","contact":"Kimmo Kymalainen","contact-id":19464,"tdoctype":"LS in","for":"Discussion","abstract":"ITU-T Study Group 12 wishes to inform 3GPP that we have endorsed a new work item E.RQST - Voice and Data QoS KPI thresholds on mobile networks on frameworks that stakeholders and ICT regulators in particular can use as benchmarking when monitoring and enforcing network and services performance on mobile networks.\nIn order to have updated references on this important issues, SG12 would like to kindly ask 3GPP to inform us about any related work you have done so far on this matters and provide us appropriate references. The new work item base text is available in attachment to this document and contains numerical thresholds.","secretary_remarks":"","agenda_item_sort_order":8,"ainumber":"4.1","ainame":"Incoming liaisons","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2017-02-26 23:37:01","uploaded":"2017-02-26 23:40:15","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"3GPP","Cc":"ETSI TC STQ MOBILE","lsoriginalls":"COM 12 \u2013 LS 11 \u2013 E","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/TSG_CT\/TSGC_75_Dubrovnik\/Docs\/CP-170202.zip","group":"CP","meeting":"CP-75","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"CP-170203","title":"Northbound SCEF API standardisation requested by oneM2M","source":"SA","contact":"Rouzbeh Farhoumand","contact-id":38768,"tdoctype":"LS in","for":"Information","abstract":"3GPP recognizes the urgent market need for oneM2M to have these APIs delivered in their Release 3. To that end, 3GPP agrees with the request from oneM2M to take responsibility for standardising the northbound APIs from SCEF. The 3GPP work needs to take into consideration any relevant feedback from OMA who as reported to the SA Plenary has a gap analysis underway on required NetAPIs based on GSMA\u2019s LS regarding support for MIoT use cases.  \n  \n\n3GPP SA agrees for SA2 to be responsible for the stage 2 updates required for the SCEF functionalities and information flows, and CT3 to be responsible for the stage 3 work of specifying the APIs. Other 3GPP Working Groups may be involved as usual if need be.\n\nTo ensure that the 3GPP work on SCEF northbound API fulfils the oneM2M needs, 3GPP SA kindly requests oneM2M to provide their coherent API requirements, so that 3GPP can deliver the work accordingly.","secretary_remarks":"","agenda_item_sort_order":8,"ainumber":"4.1","ainame":"Incoming liaisons","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2017-02-26 23:39:17","uploaded":"2017-02-26 23:40:15","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"oneM2M, OMA-ARC","Cc":"GPP SA2, 3GPP SA1, 3GPP CT, 3GPP CT3, GSMA","lsoriginalls":"SP-160952","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/TSG_CT\/TSGC_75_Dubrovnik\/Docs\/CP-170203.zip","group":"CP","meeting":"CP-75","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"CP-170216","title":"LS on interworking and migration for 5GS and EPS (including Option 3)","source":"SA2","contact":"Irfan Ali","contact-id":57013,"tdoctype":"LS in","for":"Information","abstract":"SA WG2 would like to inform TSG SA and TSG RAN that in the context of the 5GS_Ph1 WID, SA WG2 has captured solution for migration from LTE\/EPC deployment including option 3 to 5GC based deployment options e.g. options 2, 4, 5 and 7, in TS 23.501 clause 5.17.1. This is to report progress since the last LS that SA2 had sent in S2-166288.\n\nOn the topic of interworking between 5GS and EPS, SA2 has started to capture solutions in TS 23.501 and TS 23.502. The interworking architecture diagram is captured in TS 23.501 clause 4.3. At the moment SA2 is not aware of any contentious issue that could adversely impact the timely completing of this feature. SA2 will interact directly with relevant RAN working groups on specific issues as we progress the work.","secretary_remarks":"","agenda_item_sort_order":8,"ainumber":"4.1","ainame":"Incoming liaisons","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2017-02-27 16:28:06","uploaded":"2017-02-27 16:29:57","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG SA, TSG RAN","Cc":"RAN WG2, RAN WG3, TSG CT","lsoriginalls":"S2-171591","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/TSG_CT\/TSGC_75_Dubrovnik\/Docs\/CP-170216.zip","group":"CP","meeting":"CP-75","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"CP-170218","title":"NGMN Recommendations regarding the Transparency of SEP Disclosures","source":"NGMN Alliance Project P3 \u2013 IPR Forum","contact":"Stefan Engel-Flechsig","contact-id":54958,"tdoctype":"LS in","for":"Discussion","abstract":"In February 2015 the NGMN Alliance published its 5G White Paper providing consolidat-ed 5G operator requirements (https:\/\/www.ngmn.org\/5g-white-paper.html). With reference to IPR, NGMN is developing recommendations and an implementation strategy support-ing a more transparent and predictable IPR eco-system for 5G Standards Essential Pa-tents (SEP) across industries that will support sustainable implementation of 5G technol-ogies and ensure that innovation is stimulated and innovators appropriately rewarded.","secretary_remarks":"","agenda_item_sort_order":8,"ainumber":"4.1","ainame":"Incoming liaisons","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2017-02-28 19:04:25","uploaded":"2017-02-28 19:21:33","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"3GPP, ATIS, ITU, ISO, IEC, ETSI, CEN\/CENELEC, IEEE, BBF, TMF, MEF","Cc":"","lsoriginalls":"170127 Liaison NGMN IPR Forum","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/TSG_CT\/TSGC_75_Dubrovnik\/Docs\/CP-170218.zip","group":"CP","meeting":"CP-75","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"CP-170219","title":"FURTHER INFORMATION ON THE INVITATION FOR SUBMISSION OF PROPOSALS FOR CANDIDATE RADIO INTERFACE TECHNOLOGIES FOR THE TERRESTRIAL COMPONENTS OF THE RADIO INTERFACE(S) FOR IMT-2020 AND INVITATION TO PARTICIPATE IN THEIR SUBSEQUENT EVALUATION","source":"ITU-R Working Party 5D","contact":"Sergio Buonomo","contact-id":56608,"tdoctype":"LS in","for":"Information","abstract":"ITU-R has commenced the process of developing ITU-R Recommendations for the terrestrial components of the IMT-2020 radio interface(s). The invitation for submission of proposals for candidate radio interface technologies for the terrestrial components of IMT-2020 was issued with Circular Letter 5\/LCCE\/59 by ITU-R on 22 March 2016. On 4 July 2016, Addendum 1 to this Circular Letter was issued to announce the availability of further relevant information including the availability of Document IMT-2020\/2 - Submission and evaluation process and consensus building for IMT-2020.","secretary_remarks":"","agenda_item_sort_order":8,"ainumber":"4.1","ainame":"Incoming liaisons","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2017-02-28 19:10:17","uploaded":"2017-02-28 19:21:33","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"3GPP, 3GPP2, ARIB, ATIS, CCSA, ETSI, IEEE, ITRI, TIA, TSDSI, TTA, TTC, WiMAX Forum, EBU, WWRF, 4G Americas, CDG, GSMA, UMTS Forum, Wi-Fi Alliance, Wireless Innovation Forum, XGP Forum, EU METIS Project, NGMN, 5G Innovation Centre, 5GMF, IMT 2020 Promotion Group, APT Wireless Group, 5G Infrastructure Public Private Partnership, NYU Wireless, 5GAA","Cc":"","lsoriginalls":"LS_EOs_5D_530Att3.5","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/TSG_CT\/TSGC_75_Dubrovnik\/Docs\/CP-170219.zip","group":"CP","meeting":"CP-75","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"CP-170220","title":"THE SCHEDULE FOR UPDATING RECOMMENDATION ITU-R M.1457","source":"ITU-R Working Party 5D","contact":"Sergio Buonomo","contact-id":56608,"tdoctype":"LS in","for":"Information","abstract":"ITU-R Working Party 5D (WP 5D) thanks the relevant External Organizations for their successful work in regards to the course of action to be taken towards the completion of Revision 13 of Recommendation ITU-R M.1457 \u2013 \u201cDetailed specifications of the terrestrial radio interfaces of International Mobile Telecommunications-2000 (IMT-2000)\u201d which was sent to Study Group 5 and will be available as a published ITU-R Recommendation.\nWP 5D wishes to inform the relevant External Organizations that it is commencing the cycle for the development of the Revision 14 update of Recommendation ITU-R M.1457 and provides its detailed schedule.","secretary_remarks":"","agenda_item_sort_order":8,"ainumber":"4.1","ainame":"Incoming liaisons","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2017-02-28 19:14:01","uploaded":"2017-02-28 19:21:33","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"3GPP, 3GPP2, ARIB, ATIS, CCSA, ETSI, IEEE, ITRI, TIA, TSDSI, TTA, TTC, WiMAX Forum, EBU, WWRF, 4G Americas, CDG, GSMA, UMTS Forum, Wi-Fi Alliance, Wireless Innovation Forum, XGP Forum, EU METIS Project, NGMN, 5G Innovation Centre, 5GMF, IMT 2020 Promotion Group, APT Wireless Group, 5G Infrastructure Public Private Partnership, NYU Wireless, 5GAA","Cc":"","lsoriginalls":"LS_EOs_5D_530Att5.5","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/TSG_CT\/TSGC_75_Dubrovnik\/Docs\/CP-170220.zip","group":"CP","meeting":"CP-75","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"CP-170221","title":"ITU-R WORKING PARTY 5D WORKSHOP ON IMT-2020","source":"ITU-R Working Party 5D","contact":"Sergio Buonomo","contact-id":56608,"tdoctype":"LS in","for":"Information","abstract":"WP 5D intends to have ITU-R Working Party 5D (WP 5D) workshop on the 4th October 2017 (the second day of the 28th meeting of WP 5D), with presentations from possible proponents and registered independent evaluation groups, and by the WP 5D experts explaining the IMT-2020 process, requirements, and evaluation. The draft programme of the workshop can also be found on the WP 5D website (under \u201cRelated activities\u201d).\nWP 5D kindly invites possible proponents and registered independent evaluation groups to consider the above information to plan for the workshop in the 28th meeting of WP 5D. Evaluation groups interested in presenting at the IMT-2020 workshop are encouraged to register sufficiently before the 28th meeting of WP 5D. The evaluation group registration form is available on the \u201cWeb page for the IMT-2020 submission and evaluation process\u201d.","secretary_remarks":"","agenda_item_sort_order":8,"ainumber":"4.1","ainame":"Incoming liaisons","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2017-02-28 19:17:23","uploaded":"2017-02-28 19:21:33","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"3GPP, 3GPP2, ARIB, ATIS, CCSA, ETSI, IEEE, ITRI, TIA, TSDSI, TTA, TTC, WiMAX Forum, EBU, WWRF, 4G Americas, CDG, GSMA, UMTS Forum, Wi-Fi Alliance, Wireless Innovation Forum, XGP Forum, EU METIS Project, NGMN, 5G Innovation Centre, 5GMF, IMT 2020 Promotion Group, APT Wireless Group, 5G Infrastructure Public Private Partnership, NYU Wireless, 5GAA","Cc":"","lsoriginalls":"LS_EOs_5D_530Att5.14","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/TSG_CT\/TSGC_75_Dubrovnik\/Docs\/CP-170221.zip","group":"CP","meeting":"CP-75","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]