[{"name":"CP-171147","title":"LS from the NGMN P1 Service-Based Architecture Project to 3GPP","source":"NGMN Alliance Project P1 \u201cService-Based Architecture in 5G\u201d","contact":"Dan Wang","contact-id":63556,"tdoctype":"LS in","for":"Information","abstract":"NGMN operators expect that SA2 will develop the SBA approach for the 5G system in Release 15 and continue to enhance the SBA approach beyond Release 15.\nFurthermore NGMN operators kindly request CT3\/CT4 to work on the appropriate protocol design for the Service-Based Interfaces in Release 15.","secretary_remarks":"","agenda_item_sort_order":8,"ainumber":"4.1","ainame":"Incoming liaisons","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2017-05-28 17:20:05","uploaded":"2017-05-28 17:47:02","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"3GPP TSG SA WG2, 3GPP TSG CT WG3, 3GPP TSG CT WG4","Cc":"3GPP TSG SA, 3GPP TSG CT","lsoriginalls":"170428 Liaison Statement","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/TSG_CT\/TSGC_76_West_Palm_Beach\/Docs\/CP-171147.zip","group":"CP","meeting":"CP-76","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"CP-171148","title":"LIAISON REQUESTING SUPPORT FOR DEFINING NEXT GENERATION PROTOCOLS","source":"FSCOM","contact":"Kimmo Kymalainen","contact-id":19464,"tdoctype":"LS in","for":"Discussion","abstract":"We have particular interest in the evolution of protocols to support the architecture of 5G as defined in 23.501 and would be willing to support the development of protocols for 5G that have been identified such as the \u20185G Encapsulation Protocol\u2019 mentioned in 23.501 or similar, to support the definition of 5G infrastructure. \n\nAs such, we would like to ask what steps you have in plan or could initiate in order to meet these requirements, either internally or by working together with other SDOs.","secretary_remarks":"","agenda_item_sort_order":8,"ainumber":"4.1","ainame":"Incoming liaisons","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2017-05-28 17:24:18","uploaded":"2017-05-28 17:47:02","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN, CT, IETF","Cc":"SA","lsoriginalls":"NGP(17)000038r2","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/TSG_CT\/TSGC_76_West_Palm_Beach\/Docs\/CP-171148.zip","group":"CP","meeting":"CP-76","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"CP-171149","title":"Reply LS on N2 and N3 reference points for 5G system","source":"RAN3","contact":"Luis Lopes","contact-id":47178,"tdoctype":"LS in","for":"Information","abstract":"RAN3 has analysed the implications for the design of the NG interface (associated with the above mentioned reference points), and has agreed on the following principles:\n\n-\tNG Interface is designed targeting gNB as the RAN endpoint\n-\tOther possible nodes are assumed to support \u201cNG terminating functionality\u201d \n-\tAMF is assumed to be access aware via e.g. TAI \n-\tMessages may include access-specific optional IEs as needed (whether these are simply added in a flat manner, or whether optional access-specific IE groups are defined is FFS).\n\nIn agreeing this approach, RAN3 assumes that SA2 will as far as possible attempt to maximise the procedure commonality in stage 2, while simultaneously minimizing the number of access-specific elements that are visible in the interface signalling.","secretary_remarks":"","agenda_item_sort_order":8,"ainumber":"4.1","ainame":"Incoming liaisons","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2017-05-28 17:26:32","uploaded":"2017-05-28 17:47:02","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-171611, R3-170940","lsto":"SA2","Cc":"TSG SA, TSG RAN, TSG CT, RAN WG3, CT WG4, CT WG1, SA WG3, RAN WG2","lsoriginalls":"R3-171401","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/TSG_CT\/TSGC_76_West_Palm_Beach\/Docs\/CP-171149.zip","group":"CP","meeting":"CP-76","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"CP-171150","title":"Reply LS on GSMA Mobile IoT response to \u201cNorthbound SCEF API standardisation requested by oneM2M\u201d","source":"SA2","contact":"Maulik Vaidya","contact-id":68224,"tdoctype":"LS in","for":"Information","abstract":"SA2 understands that, through the LS, GSMA requested for SA2 to identify which representative set of functions would fall under the purview of SA WG2. To that extent, SA2 has the following feedback to provide","secretary_remarks":"","agenda_item_sort_order":8,"ainumber":"4.1","ainame":"Incoming liaisons","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2017-05-28 17:30:30","uploaded":"2017-05-28 17:47:02","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":[{"winame":"750009"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-171634","lsto":"GSMA","Cc":"3GPP CT WG1, 3GPP CT WG3, 3GPP SA WG6, 3GPP SA, 3GPP CT, oneM2M TP","lsoriginalls":"S2-172737","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/TSG_CT\/TSGC_76_West_Palm_Beach\/Docs\/CP-171150.zip","group":"CP","meeting":"CP-76","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"CP-171151","title":"Reply LS to oneM2M LS on \u201cReply LS to 3GPP on Northbound SCEF API standardisation\u201d","source":"SA2","contact":"Maulik Vaidya","contact-id":68224,"tdoctype":"LS in","for":"Information","abstract":"SA2 understands that TR-0024 is a living document. SA2 assumes that the requirements, identified in Section 8.*.3.3 of v2_0_3 of TR-0024, for the four API use-cases indicated in the LS (Section 8.5, 8.7, 8.8, and 8.9) are considered stable. SA2 would appreciate if oneM2M can confirm this assumption?\nSA2 also requests to be informed of when the other API requirements, for which oneM2M requires SA2\u2019s feedback, are considered stable. \nPlease note that the current plan of record for SA2 is to complete the Stage 2 work for NAPS by September 2017. Furthermore, it is to note that analysis of the said requirements (from TR-0024) by SA2 is expected to follow normal 3GPP procedures. \nSA2 would also like to thank oneM2M for extending oneM2M\u2019s expertise to be made available for presenting\/discussing TR-0024. Should SA2 feel a need, at a future time, for the same then SA2 would be eager to solicit oneM2M\u2019s input.","secretary_remarks":"","agenda_item_sort_order":8,"ainumber":"4.1","ainame":"Incoming liaisons","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2017-05-28 17:32:51","uploaded":"2017-05-28 17:47:02","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":[{"winame":"750009"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-171648","lsto":"oneM2M TP","Cc":"3GPP CT WG3, 3GPP SA, 3GPP CT, 3GPP SA WG1, GSMA, OMA ARC","lsoriginalls":"S2-172742","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/TSG_CT\/TSGC_76_West_Palm_Beach\/Docs\/CP-171151.zip","group":"CP","meeting":"CP-76","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"CP-171152","title":"EPC QoS aspects for TSG RAN\u2019s lower latency features","source":"SA2","contact":"Chris Pudney","contact-id":1122,"tdoctype":"LS in","for":"Information","abstract":"SA2 politely request co-ordinated guidance from TSG RAN and TSG SA as to which lower latency features are to be considered in the intermediate Release 15 (March 2018 ASN.1) and which are to be considered for the full Release 15 for EPC.","secretary_remarks":"","agenda_item_sort_order":8,"ainumber":"4.1","ainame":"Incoming liaisons","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2017-05-28 17:36:26","uploaded":"2017-05-28 17:47:03","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":[{"winame":"LTE_sTTIandPT"},{"winame":"EDCE5"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN, SA","Cc":"SA 1, CT","lsoriginalls":"S2-173686","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/TSG_CT\/TSGC_76_West_Palm_Beach\/Docs\/CP-171152.zip","group":"CP","meeting":"CP-76","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"CP-171153","title":"LS (S4h160679 and C3A170068) on external interface for TV services from SA4 and CT3","source":"SA3","contact":"Noamen Ben Henda","contact-id":63310,"tdoctype":"LS in","for":"Information","abstract":"SA4 and CT3 suggest in their LSs and xMB related TSs 33.246 and 29.611 the use of OAuth to authorize the content provider to the BM-SC. However, it is not clear if the use of OAuth is needed in case there is already a mutually authenticated (D)TLS connection. A more granular authorization might be needed for example for authorizing separate users within a content provider domain to perform different actions over xMB. SA3 assumes that authorization on (D)TLS connection level would be sufficient for SA4 and CT3 purposes.\nSA3 would also like to note that the use of the above authorization mechanism cannot be used for identifying and removing any individual content streams that are submitted by the content provider that may be reported as being in violation of the rights of the copyright owners. Any such violations should be dealt with separately (e.g.,  by removing the offending content from the BM-SC).","secretary_remarks":"","agenda_item_sort_order":8,"ainumber":"4.1","ainame":"Incoming liaisons","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2017-05-28 17:38:50","uploaded":"2017-05-28 17:47:03","revisionof":"","revisedto":"","release":"Rel-14","crspec":"","crspecversion":"","workitem":[{"winame":"AE_enTV"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S4h160679 and C3A170068","lsto":"SA4, CT3","Cc":"SA2, SA, CT","lsoriginalls":"S3-171450","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/TSG_CT\/TSGC_76_West_Palm_Beach\/Docs\/CP-171153.zip","group":"CP","meeting":"CP-76","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"CP-171154","title":"LS on Common API Framework for 3GPP Northbound APIs","source":"SA6","contact":"Suresh Chitturi","contact-id":61003,"tdoctype":"LS in","for":"Information","abstract":"At TSG SA#75 (March 8-10, 2017), 3GPP TSG SA has approved a new study on Common API Framework for 3GPP Northbound APIs (FS_CAPIF). The approved study item is available in SP-170279 (also attached for your reference), and is expected to be completed by SA#77 (Sep 2017). The study has been assigned to SA6 Working Group that directly reports to 3GPP TSG SA.\n\nThe objective of the study is to identify architecture requirements and corresponding architecture solutions for a common API framework within 3GPP, and to provide recommendations for the normative work.","secretary_remarks":"","agenda_item_sort_order":8,"ainumber":"4.1","ainame":"Incoming liaisons","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2017-05-28 17:41:14","uploaded":"2017-05-28 17:47:03","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":[{"winame":"FS_CAPIF"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"oneM2M, GSMA, OMA ARC, ETSI MEC","Cc":"3GPP TSG SA, 3GPP TSG CT","lsoriginalls":"S6-170475","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/TSG_CT\/TSGC_76_West_Palm_Beach\/Docs\/CP-171154.zip","group":"CP","meeting":"CP-76","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"CP-171155","title":"Reply LS to 3GPP on Northbound SCEF API standardisation","source":"oneM2M TP","contact":"Kimmo Kymalainen","contact-id":19464,"tdoctype":"LS in","for":"Information","abstract":"oneM2M TP respectfully requests 3GPP SA:\n? To incorporate the information above into their planning and provide SA2 and CT3 with guidelines as they see fit.\n\noneM2M TP respectfully requests 3GPP SA2:\n? to refer to the specific sections of the oneM2M TR-0024 for our detailed requirements\n? to provide clarifications on the issues listed in 8.*.3 sections of oneM2M TR-0024\n? to investigate fulfilling the above requirements\n? to indicate if 3GPP SA2 would like a oneM2M representative to present\/discuss oneM2M TR-0024 at a convenient occasion, e.g. SA2 meeting in Busan, conference call.","secretary_remarks":"","agenda_item_sort_order":8,"ainumber":"4.1","ainame":"Incoming liaisons","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2017-05-28 17:43:46","uploaded":"2017-05-28 17:47:03","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"TP-2017-0016","lsto":"3GPP SA, 3GPP SA2","Cc":"3GPP SA1, 3GPP CT, 3GPP CT3, GSMA, OMA ARC","lsoriginalls":"TP-2017-0005R04","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/TSG_CT\/TSGC_76_West_Palm_Beach\/Docs\/CP-171155.zip","group":"CP","meeting":"CP-76","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"CP-171156","title":"Reply LS to SA2 LS on \u201cNorthbound SCEF API standardisation\u201d","source":"oneM2M TP","contact":"Kimmo Kymalainen","contact-id":19464,"tdoctype":"LS in","for":"Information","abstract":"oneM2M TP thanks SA2 for their LS on \u201cNorthbound SCEF API standardisation\u201d in S2-172742.\nSA2 is asking whether the requirements identified in Section 8.*.3 of v2_0_3 of oneM2M TR-0024, for the four API use-cases indicated in the LS (Section 8.5, 8.7, 8.8, and 8.9) are considered stable.\nWe confirm that the content of all clauses 8.*.3.3 (Key Issues and Requirements) of TR-0024 are stable and we recommend using v.2.1.1 (or later) of the document. oneM2M work in progress will be focused on the oneM2M-specific solutions not affecting the interface to the 3GPP network.","secretary_remarks":"","agenda_item_sort_order":8,"ainumber":"4.1","ainame":"Incoming liaisons","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2017-05-28 17:45:10","uploaded":"2017-05-28 17:47:03","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"SA2-172742","lsto":"3GPP SA2","Cc":"3GPP SA, 3GPP SA1, 3GPP CT, 3GPP CT3, GSMA MIoT, GSMA NG IoTTF, OMAARC","lsoriginalls":"TP-2017-0098R02","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/TSG_CT\/TSGC_76_West_Palm_Beach\/Docs\/CP-171156.zip","group":"CP","meeting":"CP-76","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"CP-171174","title":"Liaison statement on Network Slicing initiative in GSMA","source":"GSMA Future Networks Programme - Network Slicing Taskforce","contact":"Kimmo Kymalainen","contact-id":19464,"tdoctype":"LS in","for":"Discussion","abstract":"Based on such insights, GSMA intends to create a limited set of reference network slice types, that are globally available, with each serving specific business needs and reusable across as many vertical industries as possible. By capturing the characteristics of the basic set of slice types in a GSMA permanent reference document (PRD), such network slice types can be documented through well-defined roaming agreement templates and therefore made available globally. The PRD may also provide guidelines on how certain vertical industries\u2019 requirements could be met by the device, potentially through concurrent use of a set of slice types. \nThe definition of network slice types is intended to build upon and complement the specification of network slicing currently ongoing in 3GPP.","secretary_remarks":"","agenda_item_sort_order":8,"ainumber":"4.1","ainame":"Incoming liaisons","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2017-06-02 19:42:09","uploaded":"2017-06-02 19:45:40","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"3GPP TSG SA, 3GPP TSG CT, 5G-PPP, TM-Forum, 5GAA, NGMN, ARIB, ATIS, CCSA, ETSI ISG NFV, TTA, TTC, TSDSI, Broadband Forum","Cc":"3GPP TSG SA1, 3GPP TSG SA2, 3GPP TSG SA5","lsoriginalls":"NEST_03_006","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/TSG_CT\/TSGC_76_West_Palm_Beach\/Docs\/CP-171174.zip","group":"CP","meeting":"CP-76","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]