[{"name":"C4-174105","title":"Reply LS on UE capabilities for MBMS","source":"SA2","contact":"Kimmo Kymalainen","contact-id":19464,"tdoctype":"LS in","for":"Information","abstract":"SA2 discussed the issue raised and approved CRs to TS 23.246 and TS 23.682 as attached. With these CRs,  the UE Category for MBMS and target coverage level information that are required to receive the service may be conveyed from SCS\/AS\/SCEF to BM-SC. The BMSC may be configured to take into account the UE Category for MBMS and coverage level information to derive operator defined QCI. The operator defined QCI is then sent using MBMS Session Start Procedure towards EUTRAN allowing E-UTRAN to use the appropriate radio configuration for the service indicated by TMGI.","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-08-05 15:36:13","uploaded":"2017-08-05 15:50:47","revisionof":"","revisedto":"","release":"Rel-14","crspec":"","crspecversion":"","workitem":[{"winame":"LTE_feMTC"},{"winame":"NB_IOTenh"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN1, RAN2, RAN3","Cc":"CT3, CT4","lsoriginalls":"S2-175071","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_79_Krakow\/Docs\/C4-174105.zip","group":"C4","meeting":"C4-79","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"C4-174108","title":"LS on new BEST Service","source":"SA3","contact":"Kimmo Kymalainen","contact-id":19464,"tdoctype":"LS in","for":"Discussion","abstract":"During the work, SA3 has defined a number of new interfaces, namely the BEST User Plane and BEST Control Plane interfaces and has defined an efficient, secure stage-3 protocol.\nSA2 and CT4 are asked to review the interfaces between the HSE and the HSS, the HSE and the EMKS, and the EMKS and HSS and advise SA3 of the way that they would like to implement this so that SA3 can update this specification accordingly.  In the TS, the S6a interface is currently indicated as it allows authorised access to Authentication quintets. SA3 would like to know whether CT4 will define a new interface for this usage based on S6a\nSA2 are also asked to review the interface requirements between the HSE and the EAS.\nSA3 has attached the draft TS to this LS.","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":"2017-08-05 15:44:43","uploaded":"2017-08-05 15:50:47","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":[{"winame":"BEST_MTC_Sec"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT1, CT4, SA3-LI, SA2","Cc":"ETSI TC LI","lsoriginalls":"S3-170956","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_79_Krakow\/Docs\/C4-174108.zip","group":"C4","meeting":"C4-79","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"C4-174109","title":"LS on a new requirement on \u201cUnpredictable GTP TEID\u201d.","source":"SA3","contact":"Kimmo Kymalainen","contact-id":19464,"tdoctype":"LS in","for":"Discussion","abstract":"SA3 would like to inform CT4 that a new requirement on GTP TEID assignment has been agreed for inclusion in the (Rel15) draft TS33.250:\nThe GTP TEID shall be unpredictable","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":"2017-08-05 15:46:50","uploaded":"2017-08-05 15:50:47","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":[{"winame":"SCAS_PGW"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT4","Cc":"","lsoriginalls":"S3-171536","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_79_Krakow\/Docs\/C4-174109.zip","group":"C4","meeting":"C4-79","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"C4-174110","title":"Reply LS on LI Requirements for CIoT services including BEST services","source":"SA3","contact":"Kimmo Kymalainen","contact-id":19464,"tdoctype":"LS in","for":"Information","abstract":"A3 thanks SA3-LI for their LS on IMSI availability in the VPLMN.\n\nSA3 provides the following feedback to the questions from SA3-LI.","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-08-05 15:49:49","uploaded":"2017-08-05 15:50:47","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S3i170163","lsto":"SA3-LI","Cc":"CT1, CT4, SA2, ETSI TC LI","lsoriginalls":"S3-171537","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_79_Krakow\/Docs\/C4-174110.zip","group":"C4","meeting":"C4-79","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"C4-174123","title":"LS on Evolution of IMSI format and E.212 Recommendation","source":"ITU-T Study Group 2","contact":"Kimmo Kymalainen","contact-id":19464,"tdoctype":"LS in","for":"Discussion","abstract":"This liaison is seeking information regarding the potential impact if changes are made to the IMSI as specified in Recommendation E.212. Those changes if any would be driven by new use cases and the need for more capacity in the identification plan. In addition, the need for changes (e.g. IoT\/MTC\/M2M type communications) may result from requirements relative to 5G networks or other new use cases relative to IMSIs.","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-08-07 19:08:36","uploaded":"2017-08-07 19:09:59","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":[{"winame":"TEI15"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"3GPP, GSMA, WBA","Cc":"ITU-T SG20, SG13 & SG3","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_79_Krakow\/Docs\/C4-174123.zip","group":"C4","meeting":"C4-79","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"C4-174198","title":"LS on 3GPP and ITU-T SG2 work on MTC\/M2M\/IoT identifiers","source":"ITU-T Study Group 2","contact":"Kimmo Kymalainen","contact-id":19464,"tdoctype":"LS in","for":"Discussion","abstract":"ITU-T Study Group 2 Question 1\/2 (SG2 Q.1\/2) is currently studying certain aspects of naming, addressing, and identification issues related to machine-to-machine communications (M2M, also referred to as MTC) and for the Internet of Things (IoT).\nIn particular, SG2 Q.1\/2 is considering what, if any, changes should be made for the assignment criteria for non-geographic E.164 numbers (Recommendation E.164.1) and E.212 identifiers (Recommendation E.212). At this stage, it is envisaged that the code 878, at present allocated to Universal Personal Telecommunications (UPT) services could be repurposed as a code for M2M\/IoT (without prejudice to the use of 882 and 883 codes for M2M\/IoT).","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-08-16 10:17:51","uploaded":"2017-08-16 11:32:00","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":[{"winame":"TEI15"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"3GPP","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_79_Krakow\/Docs\/C4-174198.zip","group":"C4","meeting":"C4-79","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"C4-174199","title":"Reply LS on LI Requirements for CIoT services including BEST services","source":"S3LI","contact":"Kimmo Kymalainen","contact-id":19464,"tdoctype":"LS in","for":"Information","abstract":"SA3 seems to suggest that LI requirements can be met by denying a service. This does not fulfil LI requirements and is disproportionate.\n\nAlthough restricting or blocking services that are only used for criminal or terrorist activities might be possible, the blocking of a service for all (roaming) users that might be incidentally used by a criminal or terrorist is not appropriately fulfilling LI requirements. The goal of LI is to get access to unencrypted metadata and content, and not to prevent the information being exchanged. Also from a general economic point of view the blocking of a service that might be beneficial for commercial parties is not acceptable.\n\nFor the BEST service the challenge appears to be that the VPLMN and the HPLMN may not have access to the unencrypted information for LI. In addition, the VPLMN shall be able to perform LI without LI-specific assistance from the HPLMN.","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-08-16 11:26:23","uploaded":"2017-08-16 11:32:00","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S3-171537","lsto":"SA3","Cc":"CT1, CT4, SA2, ETSI TC LI","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_79_Krakow\/Docs\/C4-174199.zip","group":"C4","meeting":"C4-79","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"C4-174201","title":"LS to 3GPP CT4 on 5G signalling protocol requirements","source":"GSMA NG Signal","contact":"Kimmo Kymalainen","contact-id":19464,"tdoctype":"LS in","for":"Discussion","abstract":"This LS intends to provide 3GPP CT4 inputs to their choice regarding target 5G signaling protocol.","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-08-18 13:27:30","uploaded":"2017-08-18 13:28:50","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"3GPP CT4","Cc":"Future Networks","lsoriginalls":"Signal 97_104","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_79_Krakow\/Docs\/C4-174201.zip","group":"C4","meeting":"C4-79","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"C4-174214","title":"LS on service-based architecture","source":"SA3","contact":"Kimmo Kymalainen","contact-id":19464,"tdoctype":"LS in","for":"Information","abstract":"SA3 has discussed the service based architecture defined by SA2 in TS 23.501 and decided to study the security of the interconnection network between core network entities with regard to this architecture. SA3 understands that there are discussions on replacing the use of DIAMETER and GTP between core network entities by other protocols. If this happened there would also be impact on the security mechanisms applied so far by SA3. SA3 would therefore appreciate information about any changes of protocols and procedures used between core network entities at SA2\u2019s earliest convenience.","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-08-21 16:11:43","uploaded":"2017-08-22 12:07:51","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA2","Cc":"SA, CT1, CT4","lsoriginalls":"S3-172097","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_79_Krakow\/Docs\/C4-174214.zip","group":"C4","meeting":"C4-79","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"C4-174278","title":"LS on supporting non-3GPP access in NGAP","source":"RAN3","contact":"Kimmo Kymalainen","contact-id":19464,"tdoctype":"LS in","for":"Information","abstract":"RAN3 is specifying the NGAP for 5G 3GPP Access. NGAP specification work follows principle guidelines from SA2, confirmed by SA and RAN, i.e. maximising the chances that the RAN 3 specifications can be reused for other Access Networks. \n\nSA2 is requested to inform RAN3 whenever access dependencies are identified during stage 2 work, which may affect RAN3 specification(s). Based on further LS from SA2, RAN3 will work on supporting non-3GPP access in NGAP.","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-08-23 15:34:44","uploaded":"2017-08-24 08:01:22","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":[{"winame":"NR_newRAT-Core"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA2","Cc":"CT4","lsoriginalls":"R3-173394","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_79_Krakow\/Docs\/C4-174278.zip","group":"C4","meeting":"C4-79","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]