[{"name":"S5-187012","title":"Time Plan for OAM&P","source":"WG Vice Chair (Huawei)","contact":"Christian Toche","contact-id":23029,"tdoctype":"other","for":"","abstract":"","secretary_remarks":"","agenda_item_sort_order":15,"ainumber":"6.1","ainame":"OAM&P Plenary","tdoc_agenda_sort_order":70120,"status":"revised","reservation_date":"2018-10-23 13:08:26","uploaded":"2018-11-09 14:15:35","revisionof":"","revisedto":"S5-187338","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/TSG_SA\/WG5_TM\/TSGS5_122\/Docs\/S5-187012.zip","group":"S5","meeting":"S5-122","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S5-187013","title":"OAM Executive Report","source":"WG Vice Chair (Huawei)","contact":"Mirko Cano Soveri","contact-id":41957,"tdoctype":"report","for":"","abstract":"","secretary_remarks":"","agenda_item_sort_order":15,"ainumber":"6.1","ainame":"OAM&P Plenary","tdoc_agenda_sort_order":70130,"status":"revised","reservation_date":"2018-10-23 13:08:26","uploaded":"2018-11-16 23:03:28","revisionof":"","revisedto":"S5-187543","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/TSG_SA\/WG5_TM\/TSGS5_122\/Docs\/S5-187013.zip","group":"S5","meeting":"S5-122","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S5-187014","title":"OAM&P SWG action list","source":"WG Vice Chair (Huawei)","contact":"Christian Toche","contact-id":23029,"tdoctype":"other","for":"","abstract":"","secretary_remarks":"","agenda_item_sort_order":15,"ainumber":"6.1","ainame":"OAM&P Plenary","tdoc_agenda_sort_order":70140,"status":"revised","reservation_date":"2018-10-23 13:08:26","uploaded":"2018-11-02 18:44:48","revisionof":"","revisedto":"S5-187493","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/TSG_SA\/WG5_TM\/TSGS5_122\/Docs\/S5-187014.zip","group":"S5","meeting":"S5-122","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S5-187015","title":"Minutes of OAM&P SWG opening session","source":"WG Vice Chair (Huawei)","contact":"Mirko Cano Soveri","contact-id":41957,"tdoctype":"report","for":"","abstract":"","secretary_remarks":"","agenda_item_sort_order":15,"ainumber":"6.1","ainame":"OAM&P Plenary","tdoc_agenda_sort_order":70150,"status":"noted","reservation_date":"2018-10-23 13:08:26","uploaded":"2018-11-14 02:42:56","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/TSG_SA\/WG5_TM\/TSGS5_122\/Docs\/S5-187015.zip","group":"S5","meeting":"S5-122","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S5-187037","title":"Reply LS from RAN2 to SA5 on L2 measurements","source":"RAN2","contact":"Mirko Cano Soveri","contact-id":41957,"tdoctype":"LS in","for":"","abstract":"Answer 1 from RAN2: RAN2 is fine with approach. RAN2 would also like to inform SA5 that in Rel-16 there will be a SI to address L2 measurements and RAN2 may further modify what has been temprorarily agreed in Rel-15 or add new ones.\nRAN2: For both questions, assuming a Rel-16 WI is approved by RAN plenary RAN2 expects to have a new TS to capture all relevant parameters including adding new ones and modification of agreed ones from SA5 in Rel-15. However the progress depends on RAN2 discussions in Rel-16, e.g. RAN2 progresses on the RAN3 led SI RAN-centric Data Collection and Utilization for NR.","secretary_remarks":"","agenda_item_sort_order":15,"ainumber":"6.1","ainame":"OAM&P Plenary","tdoc_agenda_sort_order":70370,"status":"noted","reservation_date":"2018-10-26 14:47:52","uploaded":"2018-10-30 10:34:12","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":[{"winame":"NR_newRAT-Core"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA5","Cc":"RAN3","lsoriginalls":"R2-1816011","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/TSG_SA\/WG5_TM\/TSGS5_122\/Docs\/S5-187037.zip","group":"S5","meeting":"S5-122","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S5-187038","title":"Reply LS to SA5 on L2 measurements","source":"RAN3","contact":"Mirko Cano Soveri","contact-id":41957,"tdoctype":"LS in","for":"","abstract":"RAN3 thanks SA5 for the reply LS in S5-185560 and provides following answers to SA5\u2019s questions.  \n3GPP SA5 would like RAN3 to clarify:\n-\tWill RAN3 capture L2 measurements in any normative TS that SA5 can refer to? \n-\tHow to handle L2 measurements that needs to be defined by both RAN2 and RAN3? \nRAN3 Answer: The L2 measurement that may involve both RAN2 and RAN3 may be discussed and determined in the scope of the \u201cRAN-centric data collection and utilization\u201d SI. Eventually, the L2 measurements may be defined in a normative TS in RAN possibly in a corresponding work item phase of the \u201cRAN-centric data collection and utilization\u201d.\n3GPP SA5 would like RAN3 to clarify:\n-\tIs \u201cmapped 5QI\u201d in any RAN specifications? \n-\tDoes RAN3 have a plan for lifting the restrictions assumed by this term and address the case when the bearer contains multiple QoS Flows with different 5QIs that cannot be mapped onto a single mapped 5QI because these flows have essentially different QoS properties?\nRAN3 Answer: In RAN3 specification, there is no \u201cmapped 5QI\u201d definition. RAN3 has no intention to define it in RAN3 specifications. The intention of the term \u2018mapped 5QI\u2019 is to represent the 5QI applied to the DRB. An example can be found in the DRB QoS IE of DRB to Be Setup List in section 9.2.2.1 UE CONTEXT SETUP REQUEST message in TS 38.473. This is in-line with the definition in TS 28.552.\nAnd it is RAN3 understanding that for the QoS flows having different QoS properties the CU may map them on different DRBs.","secretary_remarks":"","agenda_item_sort_order":15,"ainumber":"6.1","ainame":"OAM&P Plenary","tdoc_agenda_sort_order":70380,"status":"noted","reservation_date":"2018-10-26 14:47:52","uploaded":"2018-10-30 10:34:12","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":[{"winame":"NR_newRAT-Core"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA5","Cc":"RAN3","lsoriginalls":"R3-186232","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/TSG_SA\/WG5_TM\/TSGS5_122\/Docs\/S5-187038.zip","group":"S5","meeting":"S5-122","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S5-187039","title":"LS from SA2 to SA5 on QoS Monitoring","source":"SA2","contact":"Mirko Cano Soveri","contact-id":41957,"tdoctype":"LS in","for":"","abstract":"SA2 would like to ask SA5 \n1. to provide feedback on the study of the QoS Monitoring for URLLC services in SA2. \n2. whether QoS monitoring for end-to-end packet delay per UE per QoS Flow can be deduced from the mechanisms defined already in SA5 or they are under the remit of ongoing SA5 work and whether (if needed) these mechanisms can be further extended based on new requirements from SA2 and SA1 (defined in TS 22.261).","secretary_remarks":"","agenda_item_sort_order":15,"ainumber":"6.1","ainame":"OAM&P Plenary","tdoc_agenda_sort_order":70391,"status":"replied to","reservation_date":"2018-10-26 14:47:52","uploaded":"2018-10-30 10:34:12","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"FS_5G_URLLC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA5, RAN2, RAN3","Cc":"","lsoriginalls":"S2-1811558","lsreply":"S5-187339, S5-187293, S5-187296, S5-187339","link":"http:\/\/www.3gpp.org\/ftp\/TSG_SA\/WG5_TM\/TSGS5_122\/Docs\/S5-187039.zip","group":"S5","meeting":"S5-122","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S5-187041","title":"Resubmitted LS from ITU-T to SA5 on cooperation on REST-based network management framework","source":"ITU-T Study Group 2","contact":"Mirko Cano Soveri","contact-id":41957,"tdoctype":"LS in","for":"","abstract":"This document contains the liaison ITU-T SG2 sends to 3GPP, informing them about the creation of two new work items on REST-based management framework, and invite co-operations on this topic. This document also expressed the opinions about URI format of the current 3GPP TS 32.158(V0.1.0).","secretary_remarks":"","agenda_item_sort_order":15,"ainumber":"6.1","ainame":"OAM&P Plenary","tdoc_agenda_sort_order":70430,"status":"replied to","reservation_date":"2018-10-26 14:47:52","uploaded":"2018-10-30 10:34:12","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA5","Cc":"","lsoriginalls":"SG2-LS62","lsreply":"S5-187340, S5-187340, S5-187557","link":"http:\/\/www.3gpp.org\/ftp\/TSG_SA\/WG5_TM\/TSGS5_122\/Docs\/S5-187041.zip","group":"S5","meeting":"S5-122","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S5-187042","title":"LS\/r from ITU-T to SA5 on Energy Efficiency (reply to 3GPP TSG SA5 - S5-182439)","source":"ITU-T Study Group 5","contact":"Mirko Cano Soveri","contact-id":41957,"tdoctype":"LS in","for":"","abstract":"This document contains a draft reply to 3GPP TSG SA5 - S5-182439 -E on Energy Efficiency","secretary_remarks":"","agenda_item_sort_order":15,"ainumber":"6.1","ainame":"OAM&P Plenary","tdoc_agenda_sort_order":72930,"status":"noted","reservation_date":"2018-10-26 14:47:52","uploaded":"2018-10-30 10:34:12","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA5","Cc":"","lsoriginalls":"SG5-LS76","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/TSG_SA\/WG5_TM\/TSGS5_122\/Docs\/S5-187042.zip","group":"S5","meeting":"S5-122","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S5-187043","title":"LS\/r from ITU-T ccSA5 on Energy Efficiency (reply to ETSI TC EE - EE(18)053033-E)","source":"ITU-T Study Group 5","contact":"Mirko Cano Soveri","contact-id":41957,"tdoctype":"LS in","for":"","abstract":"ITU-T Study Group 5 would like to thank ETSI TC EE for sending the liaison statement contained in ETSI TC EE - EE(18)053033-E and for inviting ITU-T Study Group 5 to a joint meeting to discuss Energy efficiency for 5G in 2019 in Europe (possibly at the scheduled 3GPP SA5 meeting in Sophia Antipolis).","secretary_remarks":"","agenda_item_sort_order":15,"ainumber":"6.1","ainame":"OAM&P Plenary","tdoc_agenda_sort_order":72940,"status":"postponed","reservation_date":"2018-10-26 14:47:52","uploaded":"2018-10-30 10:34:12","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"ETSI TC EE","Cc":"","lsoriginalls":"SG5-LS81","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/TSG_SA\/WG5_TM\/TSGS5_122\/Docs\/S5-187043.zip","group":"S5","meeting":"S5-122","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S5-187293","title":"LS reply on QoS monitoring","source":"SA5 (Intel China Ltd.)","contact":"Yizhi Yao","contact-id":66963,"tdoctype":"LS out","for":"Approval","abstract":"SA5 thanks SA2 for the LS on QoS monitoring. As SA2 observed, SA5 has defined the KPI on end to end latency, however the detailed mechanisms to collect the performance measurements to support this KPI are yet to be defined. So far, the SA5 defined mechanisms on performance measurements collection cannot support the monitoring of end-to-end packet delay per UE per QoS Flow. The mechanisms to collect end to end latency measurements are under an ongoing SA5 work item (WI title: Enhancement of performance assurance for 5G networks including network slicing), and SA5 has received contributions discussing the mechanisms, however there is no agreement reached up to now. \nSA5 would like to continue working on the mechanisms on end to end QoS monitoring, by operating with SA2, RAN2 and RAN3, to support the requirements from SA2 and SA1 (as defined in TS 22.261).","secretary_remarks":"","agenda_item_sort_order":15,"ainumber":"6.1","ainame":"OAM&P Plenary","tdoc_agenda_sort_order":70400,"status":"noted","reservation_date":"2018-11-08 16:03:51","uploaded":"2018-11-08 18:45:04","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":[{"winame":"NETSLICE-ADPM5G"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S5-187039","lsto":"SA2, RAN2, RAN3","Cc":"","lsoriginalls":"S2-1811558","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/TSG_SA\/WG5_TM\/TSGS5_122\/Docs\/S5-187293.zip","group":"S5","meeting":"S5-122","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S5-187294","title":"Outstanding questions from ETSI NFV ISG related to network slicing","source":"Ericsson, Nokia, Huawei, ZTE","contact":"Anatoly Andrianov","contact-id":68259,"tdoctype":"discussion","for":"Discussion","abstract":"Heads-up for the incoming LS on behalf of FEAT05 (Network Slicing) feature primes.","secretary_remarks":"","agenda_item_sort_order":15,"ainumber":"6.1","ainame":"OAM&P Plenary","tdoc_agenda_sort_order":72960,"status":"noted","reservation_date":"2018-11-08 18:03:48","uploaded":"2018-11-08 18:46:38","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/TSG_SA\/WG5_TM\/TSGS5_122\/Docs\/S5-187294.zip","group":"S5","meeting":"S5-122","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S5-187296","title":"Draft LS reply on QoS monitoring","source":"SA5 (Huawei Tech.(UK) Co., Ltd)","contact":"Lan Zou","contact-id":35534,"tdoctype":"LS out","for":"","abstract":"SA5 thanks SA2 for the LS in S5-187039\/S2-1811558. SA5 is currently working on the \u201cEnd-to-end latency of 5G network\u201d KPI and related measurements definition under the Rel-16 Workitem \u201cAssurance data and Performance Management for 5G networks and network slicing\u201c. SA5 has combined the \u201cEnd-to-end latency\u201d KPI definition in TS 28.554 in SA5#121. \nSA5 has discussed the two questions from SA2 and would like to provide the following answers:\nQ1: to provide feedback on the study of the QoS Monitoring for URLLC services in SA2.\nSA5 understands that \u201cRTT3 \u201c and \u201cOne way delay 3\u201d measurements described in SA2 QoS monitoring represent the UL or DL packet delay between UE and UPF N6 interface for per UE per QoS Flow corresponding to round trip and one way respectively. The KPI defined in SA5 represents the KPI statistics of the end to end packet delay between UE and UPF N6 interface from network point of view. SA5 does not address KPI for per UE per Qos Flow, while SA5 thinks the UL and DL packet delay described in TR 23.725 is related to \u201cEnd-to-end latency of 5G network\u201d KPI defined in subclause 6.3.1 of TS 28.554.\nQ2: whether QoS monitoring for end-to-end packet delay per UE per QoS Flow can be deduced from the mechanisms defined already in SA5 or they are under the remit of ongoing SA5 work and whether (if needed) these mechanisms can be further extended based on new requirements from SA2 and SA1 (defined in TS 22.261).\nSo far, there is no mechanism defined in SA5 to support the End-to-end latency of 5G network measurement for per UE per QoS Flow.  \nSA5 is currently working on the \u201cEnd-to-end latency of 5G network\u201d KPI and related measurements definition in Rel-16. SA5 may utilize the information from SA2, RAN2 and RAN3 to support the SA5 defined KPI \u201cEnd-to-end latency of 5G network\u201d and related measurements. SA5 is happy to cooperate with SA2, RAN2 and RAN3 and will update the progress on this topic.","secretary_remarks":"","agenda_item_sort_order":15,"ainumber":"6.1","ainame":"OAM&P Plenary","tdoc_agenda_sort_order":70410,"status":"noted","reservation_date":"2018-11-09 04:21:28","uploaded":"2018-11-09 05:21:44","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"FS_5G_URLLC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S5-187039","lsto":"SA2,RAN2,RAN3","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/TSG_SA\/WG5_TM\/TSGS5_122\/Docs\/S5-187296.zip","group":"S5","meeting":"S5-122","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S5-187303","title":"JSON Schema related IETF draft reference update","source":"Ericsson LM (WG chairman)","contact":"Thomas Tovinger","contact-id":3654,"tdoctype":"discussion","for":"Discussion","abstract":"Information from CT chair about updated IETF drafts referred to by SA5 specs for JSON schemas","secretary_remarks":"","agenda_item_sort_order":15,"ainumber":"6.1","ainame":"OAM&P Plenary","tdoc_agenda_sort_order":73030,"status":"noted","reservation_date":"2018-11-09 14:11:29","uploaded":"2018-11-09 15:29:14","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/TSG_SA\/WG5_TM\/TSGS5_122\/Docs\/S5-187303.zip","group":"S5","meeting":"S5-122","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S5-187338","title":"Time Plan for OAM&P","source":"WG Vice Chair (Huawei)","contact":"John M Meredith","contact-id":637,"tdoctype":"other","for":"","abstract":"","secretary_remarks":"","agenda_item_sort_order":15,"ainumber":"6.1","ainame":"OAM&P Plenary","tdoc_agenda_sort_order":70121,"status":"approved","reservation_date":"2018-11-17 00:47:57","uploaded":"2018-11-17 00:47:57","revisionof":"S5-187012","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/TSG_SA\/WG5_TM\/TSGS5_122\/Docs\/S5-187338.zip","group":"S5","meeting":"S5-122","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S5-187339","title":"Reply to: LS from SA2 to SA5 on QoS Monitoring","source":"SA5 (Huawei, Intel China)","contact":"John M Meredith","contact-id":637,"tdoctype":"LS out","for":"Approval","abstract":"","secretary_remarks":"","agenda_item_sort_order":15,"ainumber":"6.1","ainame":"OAM&P Plenary","tdoc_agenda_sort_order":70415,"status":"approved","reservation_date":"2018-11-16 17:00:39","uploaded":"2018-11-16 17:00:39","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":[{"winame":"FS_5G_URLLC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S5-187039","lsto":"SA2","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/TSG_SA\/WG5_TM\/TSGS5_122\/Docs\/S5-187339.zip","group":"S5","meeting":"S5-122","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S5-187340","title":"Reply to: Resubmitted LS from ITU-T to SA5 on cooperation on REST-based network management framework","source":"SA5 (Ericsson)","contact":"John M Meredith","contact-id":637,"tdoctype":"LS out","for":"Approval","abstract":"","secretary_remarks":"","agenda_item_sort_order":15,"ainumber":"6.1","ainame":"OAM&P Plenary","tdoc_agenda_sort_order":70431,"status":"revised","reservation_date":"2018-11-16 23:38:22","uploaded":"2018-11-16 23:38:22","revisionof":"","revisedto":"S5-187557","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S5-187041","lsto":"ITU-T Study Group 2","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/TSG_SA\/WG5_TM\/TSGS5_122\/Docs\/S5-187340.zip","group":"S5","meeting":"S5-122","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S5-187341","title":"Preparation of reply to ETSI NFV on network slicing","source":"Nokia, Huawei, Ericsson","contact":"John M Meredith","contact-id":637,"tdoctype":"other","for":"Discussion","abstract":"","secretary_remarks":"","agenda_item_sort_order":15,"ainumber":"6.1","ainame":"OAM&P Plenary","tdoc_agenda_sort_order":734100,"status":"endorsed","reservation_date":"2018-11-16 17:20:29","uploaded":"2018-11-16 17:20:29","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/TSG_SA\/WG5_TM\/TSGS5_122\/Docs\/S5-187341.zip","group":"S5","meeting":"S5-122","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S5-187488","title":"Clarifications topics for NFV NS in context of Network Slicing","source":"ETSI ISG NFV","contact":"John M Meredith","contact-id":637,"tdoctype":"LS in","for":"Action","abstract":"1) ETSI NFV kindly requests 3GPP SA5 to consider the questions above and to provide us a response at the earliest convenience, as well as to confirm or correct our understanding as appropriate.\n2) Please provide use cases that clarify how the priority and tenancy aspects are intended to be used for the NFV NSs in the context of Network Slicing. \n3) A joint session (e.g. webconf) between 3GPP SA5 experts and ETSI NFV ISG would be highly desirable to address and present the 3GPP SA5 answers to the ETSI NFV ISG, please provide us a few alternative dates of availability (ideally before the NFV#24 in December).","secretary_remarks":"","agenda_item_sort_order":15,"ainumber":"6.1","ainame":"OAM&P Plenary","tdoc_agenda_sort_order":748800,"status":"replied to","reservation_date":"2018-11-15 19:04:51","uploaded":"2018-11-15 19:04:51","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA5","Cc":"","lsoriginalls":"NFVIFA(18)000844r1","lsreply":"S5-187515, S5-187515, S5-187516, S5-187539, S5-187544","link":"http:\/\/www.3gpp.org\/ftp\/TSG_SA\/WG5_TM\/TSGS5_122\/Docs\/S5-187488.zip","group":"S5","meeting":"S5-122","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S5-187493","title":"OAM&P SWG action list","source":"WG Vice Chair (Huawei)","contact":"John M Meredith","contact-id":637,"tdoctype":"other","for":"","abstract":"","secretary_remarks":"","agenda_item_sort_order":15,"ainumber":"6.1","ainame":"OAM&P Plenary","tdoc_agenda_sort_order":70141,"status":"noted","reservation_date":"2018-11-16 17:00:40","uploaded":"2018-11-16 17:00:40","revisionof":"S5-187014","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/TSG_SA\/WG5_TM\/TSGS5_122\/Docs\/S5-187493.zip","group":"S5","meeting":"S5-122","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S5-187515","title":"Reply to: Clarifications topics for NFV NS in context of Network Slicing","source":"SA5 (Huawei)","contact":"John M Meredith","contact-id":637,"tdoctype":"LS out","for":"Approval","abstract":"","secretary_remarks":"","agenda_item_sort_order":15,"ainumber":"6.1","ainame":"OAM&P Plenary","tdoc_agenda_sort_order":748801,"status":"revised","reservation_date":"2018-11-16 17:09:01","uploaded":"2018-11-16 17:09:01","revisionof":"","revisedto":"S5-187516","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S5-187488","lsto":"ETSI ISG NFV","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/TSG_SA\/WG5_TM\/TSGS5_122\/Docs\/S5-187515.zip","group":"S5","meeting":"S5-122","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S5-187516","title":"Reply to: Clarifications topics for NFV NS in context of Network Slicing","source":"SA5 (Huawei)","contact":"John M Meredith","contact-id":637,"tdoctype":"LS out","for":"Approval","abstract":"","secretary_remarks":"","agenda_item_sort_order":15,"ainumber":"6.1","ainame":"OAM&P Plenary","tdoc_agenda_sort_order":748802,"status":"revised","reservation_date":"2018-11-16 18:08:53","uploaded":"2018-11-16 18:08:53","revisionof":"S5-187515","revisedto":"S5-187539","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S5-187488","lsto":"ETSI ISG NFV","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/TSG_SA\/WG5_TM\/TSGS5_122\/Docs\/S5-187516.zip","group":"S5","meeting":"S5-122","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S5-187539","title":"Reply to: Clarifications topics for NFV NS in context of Network Slicing","source":"SA5 (Huawei)","contact":"John M Meredith","contact-id":637,"tdoctype":"LS out","for":"Approval","abstract":"","secretary_remarks":"","agenda_item_sort_order":15,"ainumber":"6.1","ainame":"OAM&P Plenary","tdoc_agenda_sort_order":748803,"status":"revised","reservation_date":"2018-11-16 22:07:16","uploaded":"2018-11-16 22:07:16","revisionof":"S5-187516","revisedto":"S5-187544","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S5-187488","lsto":"ETSI ISG NFV","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/TSG_SA\/WG5_TM\/TSGS5_122\/Docs\/S5-187539.zip","group":"S5","meeting":"S5-122","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S5-187543","title":"OAM Executive Report","source":"WG Vice Chair (Huawei)","contact":"John M Meredith","contact-id":637,"tdoctype":"report","for":"","abstract":"","secretary_remarks":"","agenda_item_sort_order":15,"ainumber":"6.1","ainame":"OAM&P Plenary","tdoc_agenda_sort_order":70131,"status":"noted","reservation_date":"2018-11-17 00:46:14","uploaded":"2018-11-17 00:46:14","revisionof":"S5-187013","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/TSG_SA\/WG5_TM\/TSGS5_122\/Docs\/S5-187543.zip","group":"S5","meeting":"S5-122","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S5-187544","title":"Reply to: Clarifications topics for NFV NS in context of Network Slicing","source":"SA5 (Huawei)","contact":"John M Meredith","contact-id":637,"tdoctype":"LS out","for":"Approval","abstract":"","secretary_remarks":"","agenda_item_sort_order":15,"ainumber":"6.1","ainame":"OAM&P Plenary","tdoc_agenda_sort_order":748804,"status":"approved","reservation_date":"2018-11-17 00:46:14","uploaded":"2018-11-17 00:46:14","revisionof":"S5-187539","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S5-187488","lsto":"ETSI ISG NFV","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/TSG_SA\/WG5_TM\/TSGS5_122\/Docs\/S5-187544.zip","group":"S5","meeting":"S5-122","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S5-187557","title":"Reply to: Resubmitted LS from ITU-T to SA5 on cooperation on REST-based network management framework","source":"SA5 (Ericsson)","contact":"Mirko Cano Soveri","contact-id":41957,"tdoctype":"LS out","for":"Approval","abstract":"","secretary_remarks":"","agenda_item_sort_order":15,"ainumber":"6.1","ainame":"OAM&P Plenary","tdoc_agenda_sort_order":0,"status":"approved","reservation_date":"2018-11-28 14:52:02","uploaded":"2018-12-03 14:12:12","revisionof":"S5-187340","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S5-187041","lsto":"ITU-T Study Group 2","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/TSG_SA\/WG5_TM\/TSGS5_122\/Docs\/S5-187557.zip","group":"S5","meeting":"S5-122","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]