[{"name":"C4-173006","title":"LS on new BEST Service","source":"SA3","contact":"Kimmo Kymalainen","contact-id":19464,"tdoctype":"LS in","for":"Discussion","abstract":"Postponed from CT4#77\n\nSA3 kindly asks CT4 to define new interfaces in order to facilitate communication between the HSE and HSS, EMKS and HSS, and HSE and EMKS.","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-04-07 19:16:50","uploaded":"2017-05-03 06:27:27","revisionof":"C4-172159","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","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_78_Zhangiajie\/Docs\/C4-173006.zip","group":"C4","meeting":"C4-78","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"C4-173080","title":"Reply LS on subscription-based restrictions on attach without PDN connection","source":"CT1","contact":"Jennifer Liu","contact-id":43418,"tdoctype":"LS in","for":"Information","abstract":"CT1 thanks SA2 for their LSes in S2-171408 and S2-170700 on subscription-based restrictions on attach without PDN connection.","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-05-02 08:36:30","uploaded":"2017-05-02 08:58:34","revisionof":"","revisedto":"","release":"Rel-13","crspec":"","crspecversion":"","workitem":[{"winame":"CIoT-CT"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"C1-171304\/S2-171408","lsto":"SA2","Cc":"CT4","lsoriginalls":"C1-171942","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_78_Zhangiajie\/Docs\/C4-173080.zip","group":"C4","meeting":"C4-78","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"C4-173081","title":"LS reply to SA2 on maximum data rate","source":"RAN1","contact":"Tao Chen","contact-id":56050,"tdoctype":"LS in","for":"Information","abstract":"RAN1 would like to thank SA2 for its liaison statement on data rates and latency with NR, E-UTRA, EPS and 5GS in S2-172398\/R1-1706186.\n\nFrom a physical layer design perspective, NR targets 20Gbps for downlink and 10Gbps for uplink per UE according to the requirements in TR38.913 in Rel-15.\nRAN1 did not discuss potential differences between Options 3 (March 2018 \/ Rel-15) and 5G System as such, and leaves this discussion point to RAN2.\n\nRAN1 notes the question to SA1 on latency and would like to inform SA2 that there is ongoing work within TSG RAN on latency improvements for E-UTRAN under WID RP-170113 (Work Item on shortened TTI and processing time for LTE), and for NR under WID RP-170855 (Work Item on New Radio Access Technology).","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-05-02 08:42:46","uploaded":"2017-05-02 08:58:34","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":[{"winame":"5GS_Ph1-CT"},{"winame":"EDCE5"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-172398\/R1-1706186","lsto":"SA2, RAN2","Cc":"RAN3, SA1, CT4, CT1","lsoriginalls":"R1-1706857","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_78_Zhangiajie\/Docs\/C4-173081.zip","group":"C4","meeting":"C4-78","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"C4-173082","title":"Response LS Applying Extended NAS timers based on UE's operation in CE Mode B","source":"RAN3","contact":"Sasha Sirotkin","contact-id":41562,"tdoctype":"LS in","for":"Information","abstract":"With regards to the question to RAN3 on \u201cIt is SA2 understanding that CE levels are provided in the S1-AP Initial UE message and not at each S1-AP UL NAS Transport message. Does RAN3 see any issue with providing CE level with each S1-AP UL NAS Transport message?\u201d \nRAN3 has included a Coverage Level IE in the INITIAL UE MESSAGE at RAN3#95 to address a use case of positioning for CP CioT feature. This IE provides a binary value whether UE is operating in enhanced coverage or not. \nRAN3 see no technical issue in providing CE information in the UL NAS transport message. However RAN3 would like to point that UE CE mode is likely to change more frequently than occasions to send NAS UL messages and therefore even with this enhancement MME is likely to not have up to date information on the current UE CE levels.","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-05-02 08:45:36","uploaded":"2017-05-02 08:58:34","revisionof":"","revisedto":"","release":"Rel-14","crspec":"","crspecversion":"","workitem":[{"winame":"CIoT-CT"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA2","Cc":"CT1, CT4, RAN2","lsoriginalls":"R3-171379","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_78_Zhangiajie\/Docs\/C4-173082.zip","group":"C4","meeting":"C4-78","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"C4-173083","title":"LS on defining a GTP container for the Xw interface","source":"RAN3","contact":"Krzysztof Kordybach","contact-id":68359,"tdoctype":"LS in","for":"Discussion","abstract":"RAN3 would like to inform that in Rel.13 a new interworking solution was defined, LTE-WLAN Aggregation (LWA), based on Dual Connectivity. This solution introduced a new logical node, Wireless Termination (WT) and an interface to connect it to the eNB (Xw). This interface also provides user plane service, similarly to X2. Therefore, similar information like that transferred in the RAN Container in the GTP extension header over X2 is needed to be exchanged over Xw, too (the information to be transferred over Xw is not identical with the one needed on X2). \n\nRAN3 decided it would be better to define a new container for Xw instead of reusing the X2 RAN Container. The content of the Xw container, which is to be used for LWA, would be defined in TS 36.465.","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-05-02 08:47:54","uploaded":"2017-05-02 08:58:34","revisionof":"","revisedto":"","release":"Rel-13","crspec":"","crspecversion":"","workitem":[{"winame":"TEI13"},{"winame":"LTE_WLAN_radio-Core"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT4","Cc":"","lsoriginalls":"R3-171381","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_78_Zhangiajie\/Docs\/C4-173083.zip","group":"C4","meeting":"C4-78","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"C4-173084","title":"Reply LS on N2 and N3 reference points for 5G system","source":"QUALCOMM UK Ltd","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":7,"ainumber":"4","ainame":"Input liaison statements: allocation to agenda items as appropriate","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2017-05-02 08:50:08","uploaded":"2017-05-02 08:58:34","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-171611, R3-170940","lsto":"SA2","Cc":"SA, RAN, CT, RAN3, CT1, CT4, SA3, RAN2","lsoriginalls":"R3-171401","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_78_Zhangiajie\/Docs\/C4-173084.zip","group":"C4","meeting":"C4-78","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"C4-173085","title":"Reply LS on Pre-defined PCC\/ADC rules over Sx","source":"SA2","contact":"Runze Zhou","contact-id":60945,"tdoctype":"LS in","for":"Discussion","abstract":"SA2 thanks CT4 for the LS on pre-defined PCC\/ADC rules over Sx. SA2 has discussed the questions listed in the LS and provided the following answers.","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-05-02 08:52:57","uploaded":"2017-05-02 08:58:34","revisionof":"","revisedto":"","release":"Rel-14","crspec":"","crspecversion":"","workitem":[{"winame":"CUPS-CT"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-171762\/C4-171462","lsto":"CT4","Cc":"","lsoriginalls":"S2-172859","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_78_Zhangiajie\/Docs\/C4-173085.zip","group":"C4","meeting":"C4-78","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"C4-173086","title":"Reply LS on Clarification on Rel-14 MMCMH_Enh features","source":"SA4","contact":"Bo Burman","contact-id":16624,"tdoctype":"LS in","for":"Discussion","abstract":"SA4 can confirm that the CT4 assumption is correct and has decided to make that clarification in TS 26.114. The agreed CR is attached for information.","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-05-02 08:56:06","uploaded":"2017-05-02 08:58:34","revisionof":"","revisedto":"","release":"Rel-14","crspec":"","crspecversion":"","workitem":[{"winame":"MMCMH_Enh-CT"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"C4-172170)","lsto":"CT4","Cc":"","lsoriginalls":"S4-170501","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_78_Zhangiajie\/Docs\/C4-173086.zip","group":"C4","meeting":"C4-78","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"C4-173204","title":"Reply LS on Data rates and Latency with NR, E-UTRA, EPS and 5GS","source":"SA1","contact":"Alice Li","contact-id":62675,"tdoctype":"LS in","for":"Information","abstract":"","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-05-15 02:16:48","uploaded":"2017-05-19 04:17:52","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S1-172177\/S2-172398","lsto":"SA2","Cc":"RAN1, RAN2, RAN3, CT1, CT4","lsoriginalls":"S1-172409","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_78_Zhangiajie\/Docs\/C4-173204.zip","group":"C4","meeting":"C4-78","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"C4-173214","title":"LS on LI requirements for CIOT services including BEST services","source":"SA3-LI","contact":"Koen Jaspers","contact-id":9291,"tdoctype":"LS in","for":"Information","abstract":"Although, LI primarily focusses on intercepting the communication of a person, LI also applies to devices or infrastructure, again, in targeted fashion. Therefore, CIoT\/IoT is not excluded from LI obligations, and CIoT\/IoT LI functionality is required by national regulation.","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-05-15 03:58:43","uploaded":"2017-05-19 04:17:52","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA3","Cc":"CT1, CT4, SA3-LI, SA2, ETSI TC LI","lsoriginalls":"S3i170163","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_78_Zhangiajie\/Docs\/C4-173214.zip","group":"C4","meeting":"C4-78","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]