[{"name":"C4-150918","title":"Reply LS on TR 26.924 Study on improved end-to-end QoS handling","source":"3GPP TSG CT WG1","contact":"Kimmo Kymalainen","contact-id":19464,"tdoctype":"LS in","for":"Decision","abstract":"CT1 thanks SA4 for the LS (S4-150163\/C1-150422) on TR 26.924 Study on improved end-to-end QoS handling.\n\nIn the LS, SA4 asked CT1 to review TR 26.924 v0.1.7 and provide feedback where needed.\n\nCT1 performed the review and has no comments.","secretary_remarks":"","agenda_item_sort_order":6,"ainumber":"4","ainame":"Input liaison statements: allocation to agenda items as appropriate","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2015-05-13 18:22:09","uploaded":"2015-05-13 18:53:17","revisionof":"","revisedto":"","release":"Rel-13","crspec":"","crspecversion":"","workitem":[{"winame":"QOSE2EMTSI-CT"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"C1-151042","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_69_Sanya\/Docs\/C4-150918.zip","group":"C4","meeting":"C4-69","year":2015,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"C4-150919","title":"Reply LS on CT Impacts of the ROI WI","source":"3GPP TSG CT WG1","contact":"Kimmo Kymalainen","contact-id":19464,"tdoctype":"LS in","for":"Decision","abstract":"CT1 has reviewed the SA4 WID and permanent document on the Release 13 work item on \u201cVideo Enhancements by Region-of-Interest Information Signaling\u201d (ROI). Based on the set of potential solutions described in the ROI permanent document, CT1 acknowledges the impact of this work to CT1 specifications. More specifically, the following specification would be impacted with the corresponding modifications also highlighted: \n\n\u2022\tTS 24.229: \no\tIndication of new SDP attribute for a=predefined_ROI lines for pre-defined ROI information signaling\no\tIndication of new RTP header extension URNs in the SDP for a=extmap lines for the \u2018Actual ROI\u2019 mode\n\nCT1 would also like to indicate that the appropriate IANA registration necessary for this ROI work need to be initiated by SA4.","secretary_remarks":"","agenda_item_sort_order":6,"ainumber":"4","ainame":"Input liaison statements: allocation to agenda items as appropriate","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2015-05-13 18:24:31","uploaded":"2015-05-13 18:53:17","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"C1-151598","lsreply":"C1-150952\/S4-150250","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_69_Sanya\/Docs\/C4-150919.zip","group":"C4","meeting":"C4-69","year":2015,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"C4-150920","title":"Liaison about ETSI ISG IP6 creation and interaction with other groups","source":"ETSI ISG IP6","contact":"Kimmo Kymalainen","contact-id":19464,"tdoctype":"LS in","for":"Decision","abstract":"ETSI has successfully held the first meeting of their newly created Industry Specification Group on IPv6 Integration on 22-23 April, 2015.\n\nThe ETSI \u201cIPv6 integration\u201d Industry Specification Group (IP6 ISG) is a working group to focus on IPv6-based best practices, deployment guidelines and success showcases identifying thereby what and where consensus and harmonization could be reached.\n\nWe invite all interested parties from your organization or others to join in. Participation in the ISG IP6 is subject to signature of an ISG IP6 Agreement you can find at https:\/\/portal.etsi.org\/tb.aspx?tbid=827&SubTB=827. Explanation about those agreements is also available from the same location.","secretary_remarks":"","agenda_item_sort_order":6,"ainumber":"4","ainame":"Input liaison statements: allocation to agenda items as appropriate","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2015-05-13 18:26:25","uploaded":"2015-05-13 18:53:17","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"IP6(15)001031","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_69_Sanya\/Docs\/C4-150920.zip","group":"C4","meeting":"C4-69","year":2015,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"C4-150921","title":"3GPP TSG CT4 Meeting #69\tC4-150xyz","source":"RAN2","contact":"Kimmo Kymalainen","contact-id":19464,"tdoctype":"LS in","for":"Decision","abstract":"RAN2 has discussed certain aspects related to EVS codec rates to be supported over UTRAN CS, in particular pertaining to radio capacity benefits and impacts. The following recommendations have been agreed:\n\n- It would be beneficial to define a default EVS mode set including EVS codec rates from 5.9VBR to 13.2 kbps, targeting similar spreading factors as current deployed codecs;\n\n- It would be beneficial to define a configuration with very low data rate in order to maximize CS voice radio capacity. In particular, it would be preferable to add an EVS configuration including the EVS 5.9 VBR mode only (allowing a high DL spreading factor, e.g. SF256). \n\nIt remains FFS whether and which AMR IO modes should be included as part of the above configurations, based on further analysis of error protection schemes and RAB subflows impacts.","secretary_remarks":"","agenda_item_sort_order":6,"ainumber":"4","ainame":"Input liaison statements: allocation to agenda items as appropriate","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2015-05-13 18:28:17","uploaded":"2015-05-13 18:53:17","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":[{"winame":"EVSoCS_UTRAN-Core"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"R2-151734","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_69_Sanya\/Docs\/C4-150921.zip","group":"C4","meeting":"C4-69","year":2015,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"C4-150922","title":"Reply LS on E-RAB(s) failed to modify in E-RAB Modification Confirm","source":"RAN3","contact":"Kimmo Kymalainen","contact-id":19464,"tdoctype":"LS in","for":"Decision","abstract":"RAN3 has taken the information provided by CT4 in C4-150686 into account and aligned stage 3 accordingly:\n-\tE-RAB(s) the EPC failed to modify but may be kept unmodified can be already indicated by the MME. The MeNB finally decides whether to keep or release those E-RAB(s).\n-\tE-RAB(s) for which corresponding bearer contexts have been deleted in the MME requires new information to be added to the E-RAB MODIFICATION CONFIRM message. Upon receiving this new information the MeNB releases the E-UTRA(N)resources for those E-RABs.","secretary_remarks":"","agenda_item_sort_order":6,"ainumber":"4","ainame":"Input liaison statements: allocation to agenda items as appropriate","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2015-05-13 18:30:39","uploaded":"2015-05-13 18:53:17","revisionof":"","revisedto":"","release":"Rel-12","crspec":"","crspecversion":"","workitem":[{"winame":"LTE_SC_enh_dualC-Core"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"R3-150896","lsreply":"S2-150547\/C4-150686","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_69_Sanya\/Docs\/C4-150922.zip","group":"C4","meeting":"C4-69","year":2015,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"C4-150924","title":"Reply to LS on VoLTE Roaming Architecture GSMA","source":"3GPP SA WG3-LI","contact":"Kimmo Kymalainen","contact-id":19464,"tdoctype":"LS in","for":"Decision","abstract":"GSMA NG requested 3GPP SA3-LI to review the S8HR candidate roaming architecture, consider the LI service impacts and indicate the scope of the work to address those impacts.\n\nThis Liaison Statement response describes the initial set of issues affecting the LI service currently specified by 3GPP when S8HR roaming is deployed.  It also lists the initial set of tasks that SA3-LI has identified to develop the support required for a 3GPP LI service to handle S8HR roaming scenarios.","secretary_remarks":"","agenda_item_sort_order":6,"ainumber":"4","ainame":"Input liaison statements: allocation to agenda items as appropriate","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2015-05-13 18:36:33","uploaded":"2015-05-13 18:53:17","revisionof":"","revisedto":"","release":"Rel-13","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"S3i150153","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_69_Sanya\/Docs\/C4-150924.zip","group":"C4","meeting":"C4-69","year":2015,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"C4-150925","title":"LS on CT Impacts of the ROI WI","source":"3GPP TSG SA WG4","contact":"Kimmo Kymalainen","contact-id":19464,"tdoctype":"LS in","for":"Decision","abstract":"SA4 would like to update the CT groups with regards to the latest progress of the Release 13 work item on \u201cVideo Enhancements by Region-of-Interest Information Signaling\u201d (ROI). In particular, during the SA4#83 meeting, a CR to TS 26.114 was agreed on the ROI feature and this CR is attached to this LS. Accordingly, the ROI solution for MTSI is composed of the following components:\n\u2022\tSupport for far end camera control (FECC) protocol based on ITU-T and IETF specifications \n\u2022\tSignalling of \u2018Arbitrary ROI\u2019 and \u2018Pre-defined ROI\u2019 requests with the associated SDP capability negotiation and RTCP feedback message format definitions \n\u2022\tReporting of \u2018Sent ROI\u2019 information based on RTP header extensions","secretary_remarks":"","agenda_item_sort_order":6,"ainumber":"4","ainame":"Input liaison statements: allocation to agenda items as appropriate","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2015-05-13 18:39:07","uploaded":"2015-05-13 18:53:17","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"S4 (15)0561","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_69_Sanya\/Docs\/C4-150925.zip","group":"C4","meeting":"C4-69","year":2015,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"C4-150942","title":"Draft Reply LS on CT Impacts of the ROI WI","source":"Intel","contact":"Ozgur Oyman","contact-id":44803,"tdoctype":"LS out","for":"Decision","abstract":"","secretary_remarks":"","agenda_item_sort_order":6,"ainumber":"4","ainame":"Input liaison statements: allocation to agenda items as appropriate","tdoc_agenda_sort_order":0,"status":"revised","reservation_date":"2015-05-18 21:05:15","uploaded":"2015-05-18 21:08:33","revisionof":"","revisedto":"C4-150953","release":"Rel-13","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_69_Sanya\/Docs\/C4-150942.zip","group":"C4","meeting":"C4-69","year":2015,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"C4-150953","title":"Draft Reply LS on CT Impacts of the ROI WI","source":"Intel","contact":"Vivek Gupta","contact-id":36134,"tdoctype":"LS out","for":"Decision","abstract":"","secretary_remarks":"","agenda_item_sort_order":6,"ainumber":"4","ainame":"Input liaison statements: allocation to agenda items as appropriate","tdoc_agenda_sort_order":0,"status":"revised","reservation_date":"2015-05-25 04:56:24","uploaded":"2015-06-02 06:40:03","revisionof":"C4-150942","revisedto":"C4-151056","release":"Rel-13","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_69_Sanya\/Docs\/C4-150953.zip","group":"C4","meeting":"C4-69","year":2015,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"C4-151056","title":"Reply LS on CT Impacts of the ROI WI","source":"Intel","contact":"Vivek Gupta","contact-id":36134,"tdoctype":"LS out","for":"Decision","abstract":"","secretary_remarks":"","agenda_item_sort_order":6,"ainumber":"4","ainame":"Input liaison statements: allocation to agenda items as appropriate","tdoc_agenda_sort_order":0,"status":"revised","reservation_date":"2015-05-28 08:27:08","uploaded":"2015-06-02 06:40:06","revisionof":"C4-150953","revisedto":"C4-151065","release":"Rel-13","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_69_Sanya\/Docs\/C4-151056.zip","group":"C4","meeting":"C4-69","year":2015,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"C4-151065","title":"Reply LS on CT Impacts of the ROI WI","source":"Intel","contact":"Vivek Gupta","contact-id":36134,"tdoctype":"LS out","for":"Decision","abstract":"","secretary_remarks":"","agenda_item_sort_order":6,"ainumber":"4","ainame":"Input liaison statements: allocation to agenda items as appropriate","tdoc_agenda_sort_order":0,"status":"approved","reservation_date":"2015-05-29 01:19:40","uploaded":"2015-06-02 06:40:06","revisionof":"C4-151056","revisedto":"","release":"Rel-13","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_69_Sanya\/Docs\/C4-151065.zip","group":"C4","meeting":"C4-69","year":2015,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]