[{"name":"S2-180004","title":"LS from SA WG6: Reply LS on QCI values for MC Video","source":"SA WG6","contact":"Cuili Ge","contact-id":64432,"tdoctype":"LS in","for":"Action","abstract":"SA WG6 wishes to thank SA WG2 for the LS (S2-174856, S6-171142) on QCI values for MC Video. SA WG6 has discussed the QCI value for MC Video service based on the questions from SA WG2. SA WG6 provides answers to the questions as below: Q1: SA WG2 is seeking SA WG6 guidance on whether the current set of standardized QCI assignments, as specified in Table 6.1.7 of TS 23.203, are sufficient for supporting MC Video service. A1: SA WG6 believes that a new QCI is needed for MC Video media plane. The control signalling for MC Video can use the existing QCI=69 defined for Mission Critical delay sensitive signalling (e.g., MCPTT signalling). Q2: If SA WG6 perceives the need for new QCI value(s) for MC Video, SA WG2 requests guidance in how the desired QoS characteristics are different from existing standardized QCI values (e.g., relative to the current QoS characteristics for QCI=2, Conversational Video). In the context of Question Q2, particular consideration should be given related to any prop","secretary_remarks":"Postponed S2-178224 from SA WG2#124. Noted in parallel session","agenda_item_sort_order":9,"ainumber":"5.2","ainame":"QoS and PCC Maintenance","tdoc_agenda_sort_order":10770,"status":"noted","reservation_date":"2017-12-19 09:32:43","uploaded":"2017-12-19 09:33:50","revisionof":"S2-178224","revisedto":"","release":"Rel-14","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"SA WG4, CT WG1","lsoriginalls":"S6-171485","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180004.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180005","title":"LS from SA WG4: Reply LS on QCI values for MC Video","source":"SA WG4","contact":"Kyunghun Jung","contact-id":38881,"tdoctype":"LS in","for":"Action","abstract":"SA WG4 thanks SA WG2 for the LS on QCI values for MC Video and answer the following question: Q4: SA WG2 is seeking SA WG4 guidance on whether the current set of standardized QCI assignments, as specified for QCI=2 (Conversational Video) in Table 6.1.7 of TS 23.203, offer sufficient resiliency for handling of MC Video packets (e.g., due to potential packet loss characteristics). The required error resiliency of MC Video may differ depending on its use cases, especially the latency aspects of the services. QCI=2 is often paired with QCI=1 for real-time conversational services such as MTSI. If MC Video is used for such applications, then use of QCI=2 will be appropriate. If MC Video is used for applications with more relaxed latency requirements than MTSI, such as remote surveillance, then higher quality and error resiliency may be achieved, by assigning a QCI that allows a larger latency than with QCI=2 and a comparable or lower packet error loss rate, as the additional delay may be exp","secretary_remarks":"Postponed S2-178225 from SA WG2#124. Noted in parallel session","agenda_item_sort_order":9,"ainumber":"5.2","ainame":"QoS and PCC Maintenance","tdoc_agenda_sort_order":10780,"status":"noted","reservation_date":"2017-12-19 09:32:43","uploaded":"2017-12-19 09:33:50","revisionof":"S2-178225","revisedto":"","release":"Rel-14","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"CT WG1, CT WG3, SA WG6","lsoriginalls":"S4-170969","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180005.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180484","title":"Clarification on PRA reporting in ECM-IDLE state","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify the behaviour of MME\/S4-SGSN upon receiving request for notification of change of UE presence in PRA when UE is in CM-IDLE state.","secretary_remarks":"Revised in parallel session to S2-181029.","agenda_item_sort_order":9,"ainumber":"5.2","ainame":"QoS and PCC Maintenance","tdoc_agenda_sort_order":10790,"status":"revised","reservation_date":"2018-01-16 01:49:05","uploaded":"2018-01-16 13:10:38","revisionof":"","revisedto":"S2-181029","release":"Rel-15","crspec":23.401,"crspecversion":"15.2.0","workitem":[{"winame":"TEI15"}],"crnumber":3381.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180484.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181029","title":"Clarification on PRA reporting in ECM-IDLE state","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify the behaviour of MME\/S4-SGSN upon receiving request for notification of change of UE presence in PRA when UE is in CM-IDLE state.","secretary_remarks":"Revision of S2-180484. For e-mail approval. Revision 1 approved. Revised to S2-181393.","agenda_item_sort_order":9,"ainumber":"5.2","ainame":"QoS and PCC Maintenance","tdoc_agenda_sort_order":10800,"status":"revised","reservation_date":"2018-01-25 18:14:41","uploaded":"2018-01-26 18:07:54","revisionof":"S2-180484","revisedto":"S2-181393","release":"Rel-15","crspec":23.401,"crspecversion":"15.2.0","workitem":[{"winame":"TEI15"}],"crnumber":3381.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181029.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181393","title":"Clarification on PRA reporting in ECM-IDLE state","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify the behaviour of MME\/S4-SGSN upon receiving request for notification of change of UE presence in PRA when UE is in CM-IDLE state.","secretary_remarks":"e-mail revision 1 of S2-181029. This CR was agreed","agenda_item_sort_order":9,"ainumber":"5.2","ainame":"QoS and PCC Maintenance","tdoc_agenda_sort_order":10810,"status":"agreed","reservation_date":"2018-02-02 10:04:21","uploaded":"2018-02-02 10:30:31","revisionof":"S2-181029","revisedto":"","release":"Rel-15","crspec":23.401,"crspecversion":"15.2.0","workitem":[{"winame":"TEI15"}],"crnumber":3381.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"SP-180113","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181393.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]