[{"name":"C3-194017","title":"HalForms data type","source":"China Mobile","contact":"Yue Song","contact-id":57977,"tdoctype":"other","for":"Discussion","abstract":"","secretary_remarks":"","agenda_item_sort_order":106,"ainumber":"18","ainame":"Joint Sessions","tdoc_agenda_sort_order":40170,"status":"noted","reservation_date":"2019-09-26 01:26:19","uploaded":"2019-09-27 09:43:01","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":[{"winame":"SBIProtoc16"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG3_interworking_ex-CN3\/TSGC3_106_Portoroz\/Docs\/C3-194017.zip","group":"C3","meeting":"C3-106","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"C3-194018","title":"3gppHalForms media type","source":"China Mobile","contact":"Yue Song","contact-id":57977,"tdoctype":"other","for":"Discussion","abstract":"","secretary_remarks":"","agenda_item_sort_order":106,"ainumber":"18","ainame":"Joint Sessions","tdoc_agenda_sort_order":40180,"status":"noted","reservation_date":"2019-09-26 01:26:19","uploaded":"2019-09-27 09:43:01","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":[{"winame":"SBIProtoc16"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG3_interworking_ex-CN3\/TSGC3_106_Portoroz\/Docs\/C3-194018.zip","group":"C3","meeting":"C3-106","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"C3-194019","title":"Discussion on response messages","source":"China Mobile","contact":"Yue Song","contact-id":57977,"tdoctype":"other","for":"Discussion","abstract":"","secretary_remarks":"","agenda_item_sort_order":106,"ainumber":"18","ainame":"Joint Sessions","tdoc_agenda_sort_order":40190,"status":"noted","reservation_date":"2019-09-26 01:26:19","uploaded":"2019-09-27 09:43:01","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":[{"winame":"SBIProtoc16"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG3_interworking_ex-CN3\/TSGC3_106_Portoroz\/Docs\/C3-194019.zip","group":"C3","meeting":"C3-106","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"C3-194020","title":"Binding information conveyance","source":"China Mobile","contact":"Yue Song","contact-id":57977,"tdoctype":"other","for":"Discussion","abstract":"","secretary_remarks":"","agenda_item_sort_order":106,"ainumber":"18","ainame":"Joint Sessions","tdoc_agenda_sort_order":40200,"status":"noted","reservation_date":"2019-09-26 01:26:19","uploaded":"2019-09-27 09:43:01","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":[{"winame":"5G_eSBA"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG3_interworking_ex-CN3\/TSGC3_106_Portoroz\/Docs\/C3-194020.zip","group":"C3","meeting":"C3-106","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"C3-194025","title":"Work plan for eNA","source":"Huawei","contact":"Yali Yan","contact-id":66362,"tdoctype":"discussion","for":"Discussion","abstract":"","secretary_remarks":"","agenda_item_sort_order":106,"ainumber":"18","ainame":"Joint Sessions","tdoc_agenda_sort_order":40250,"status":"noted","reservation_date":"2019-09-27 08:57:46","uploaded":"2019-09-30 10:20:44","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"eNA"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG3_interworking_ex-CN3\/TSGC3_106_Portoroz\/Docs\/C3-194025.zip","group":"C3","meeting":"C3-106","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"C3-194027","title":"Missed feature and resources from Application Data","source":"Huawei","contact":"Yali Yan","contact-id":66362,"tdoctype":"discussion","for":"Discussion","abstract":"","secretary_remarks":"","agenda_item_sort_order":106,"ainumber":"18","ainame":"Joint Sessions","tdoc_agenda_sort_order":40270,"status":"noted","reservation_date":"2019-09-27 08:57:46","uploaded":"2019-09-30 10:20:44","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"5G_URLLC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG3_interworking_ex-CN3\/TSGC3_106_Portoroz\/Docs\/C3-194027.zip","group":"C3","meeting":"C3-106","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"C3-194043","title":"Increasing the maximum MDBV value","source":"Qualcomm Incorporated \/ Lena","contact":"Lena Chaponniere","contact-id":38080,"tdoctype":"discussion","for":"Information","abstract":"","secretary_remarks":"","agenda_item_sort_order":106,"ainumber":"18","ainame":"Joint Sessions","tdoc_agenda_sort_order":40430,"status":"noted","reservation_date":"2019-09-28 16:37:06","uploaded":"2019-09-29 17:17:19","revisionof":"","revisedto":"","release":"Rel-16","crspec":29.571,"crspecversion":"","workitem":[{"winame":"5GS_Ph1-CT"},{"winame":"TEI16"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG3_interworking_ex-CN3\/TSGC3_106_Portoroz\/Docs\/C3-194043.zip","group":"C3","meeting":"C3-106","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"C3-194238","title":"Draft Reply LS on Nudr_DM evolution","source":"Ericsson \/ CT4","contact":"Nevenka Biondic","contact-id":41878,"tdoctype":"LS out","for":"Information","abstract":"C4-194211\nCT4 thanks SA2 for the LS on Nudr_DM evolution, and would like to provide input on the questions raised in the LS.\nQuestion 1: \"Would it be preferable from the perspective of extensibility, versioning, and backward compatibility to define separate services rather than new data sets for future extensions of the data stored in the UDR?\"\nAnswer:\nCT4 discussed the pros and cons of both alternatives, and it was acknowledged that having a single version for the overall Nudr_DM service has the drawback of requiring a version upgrade of the API even when a given UDR instance may only support a number of data sets, potentially not affected by a change in other data sets that triggered the version update.\nOn the other hand, even though from a technical perspective CT4 has not detected any major problem with defining new services for the Nudr SBI, it was mentioned that defining new services creates a big overhead in terms of standardization effort, even when a number of design patterns might be reused for the different APIs. So, defining a large number of services is clearly not desirable, either.\nA technical implication that could result from a potential definition of a large number of Nudr services is related to the fact that the \"service name\" (specific to each API\/service) must be included in the Oauth2 access token used to get access to a given service; therefore, an NF consumer that would need to access a large number of Nudr services needs to include all of them in the access token request towards NRF, and need to manage it accordingly as long as new services are added. It is CT4's view that this may be fine for a moderate number of services, but it gets harder to manage as the amount of new defined services grow.\nQuestion 2: \"If only a small subset of service operations of Nudr_DM is to be used for a data set, is it preferable to define a new service or reuse the existing Nudr_DM service?\"\nAnswer:\nThe number of operations to be used of an existing service does not favour or penalize the reuse of the service to have access to new data.\nQuestion 3: \"From the perspective of implementation and standardisation effort, are more synergies expected from a single service with multiple data sets, compared to separate data management services with their own service operations that would still follow common design patterns as defined in Table 5.2.12.1-1 in TS 23.502 and TS 29.504?\"\nAnswer: See answers to question 1 and 2.\nConclusion\nCT4 would suggest considering the definition of new Nudr services with a similar granularity than the existing data sets currently defined (i.e., Subscription Data, Policy Data, Application Data, Exposure Data).\nA good candidate for definition of an independent service would be the case of new data definition that is expected to be accessed by specific consumers, that may not access other Data Sets, since in this case, the data modification should not affect to other consumers unnecessarily.\nIn any case, as indicated earlier, CT4's main concern is related to the standardization effort it would require. Having a few services could be manageable but having a multitude of services would not be desirable.\n2. Actions: To SA2 group. T4 kindly asks SA2 to consider the feedback provided to the questions above, to progress the work of those Work Items requiring to evolve the data model of the UDR.","secretary_remarks":"","agenda_item_sort_order":106,"ainumber":"18","ainame":"Joint Sessions","tdoc_agenda_sort_order":42380,"status":"noted","reservation_date":"2019-09-30 13:58:29","uploaded":"2019-09-30 14:05:33","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"TEI16"},{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-1908635","lsto":"SA2","Cc":"CT3","lsoriginalls":"C4-194211","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG3_interworking_ex-CN3\/TSGC3_106_Portoroz\/Docs\/C3-194238.zip","group":"C3","meeting":"C3-106","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"C3-194239","title":"NF Discovery Factors Conveyance","source":"Deutsche Telekom","contact":"Yvette Koza","contact-id":31372,"tdoctype":"discussion","for":"Decision","abstract":"AI 16.6","secretary_remarks":"","agenda_item_sort_order":106,"ainumber":"18","ainame":"Joint Sessions","tdoc_agenda_sort_order":42390,"status":"noted","reservation_date":"2019-09-30 14:19:52","uploaded":"2019-09-30 14:26:31","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"5G_eSBA"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG3_interworking_ex-CN3\/TSGC3_106_Portoroz\/Docs\/C3-194239.zip","group":"C3","meeting":"C3-106","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"C3-194246","title":"Binding between NF Service Consumer and NF Service Producer","source":"Nokia, Nokia Shanghai Bell","contact":"Hao Jing","contact-id":83214,"tdoctype":"other","for":"Discussion","abstract":"","secretary_remarks":"","agenda_item_sort_order":106,"ainumber":"18","ainame":"Joint Sessions","tdoc_agenda_sort_order":42460,"status":"noted","reservation_date":"2019-10-01 14:18:07","uploaded":"2019-10-02 07:34:38","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG3_interworking_ex-CN3\/TSGC3_106_Portoroz\/Docs\/C3-194246.zip","group":"C3","meeting":"C3-106","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"C3-194247","title":"Usage of NF Binding as Discovery and Selection","source":"Oracle Corporation","contact":"Ingbert Sigovich","contact-id":28887,"tdoctype":"discussion","for":"Discussion","abstract":"will be discussed in the CT3-CT4 joint session.","secretary_remarks":"","agenda_item_sort_order":106,"ainumber":"18","ainame":"Joint Sessions","tdoc_agenda_sort_order":424700,"status":"noted","reservation_date":"2019-10-14 14:33:05","uploaded":"2019-10-14 14:37:59","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":[{"winame":"5G_eSBA"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG3_interworking_ex-CN3\/TSGC3_106_Portoroz\/Docs\/C3-194247.zip","group":"C3","meeting":"C3-106","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"C3-194248","title":"MAC Address as PEI format","source":"Ericsson","contact":"Ingbert Sigovich","contact-id":28887,"tdoctype":"draftCR","for":"Information","abstract":"CT4 LSCR on 29.571 out in C4-194231","secretary_remarks":"","agenda_item_sort_order":106,"ainumber":"18","ainame":"Joint Sessions","tdoc_agenda_sort_order":424800,"status":"noted","reservation_date":"2019-10-14 14:33:05","uploaded":"2019-10-14 14:37:59","revisionof":"","revisedto":"","release":"Rel-16","crspec":29.571,"crspecversion":"16.1.0","workitem":[{"winame":"5WWC"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG3_interworking_ex-CN3\/TSGC3_106_Portoroz\/Docs\/C3-194248.zip","group":"C3","meeting":"C3-106","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"C3-194330","title":"LS on maximum value of MDBV","source":"Nokia, Nokia shanghai Bell","contact":"Ingbert Sigovich","contact-id":28887,"tdoctype":"LS out","for":"Approval","abstract":"Response to:\tLS (S2-1907955) on maximum value of MDBV.\nRelease:\tRel-16\nWork Item:\t5GS_Ph1\nCT3 thanks SA2 for their LS (S2-1907955) on maximum value of MDBV. \nCT3 has found no issue with implementing an increase of the maximum allowed value of MDBV for signalled 5QI characteristics. \nCT3 will wait for a recommendation on the new desired range before an agreement on the stage 3 support in specification 3GPP TS 29.512.\nActions: To SA2 group: CT3 kindly asks SA2 group to take the above information into account and to inform CT3 about the SA2 recommendation.","secretary_remarks":"","agenda_item_sort_order":106,"ainumber":"18","ainame":"Joint Sessions","tdoc_agenda_sort_order":433000,"status":"approved","reservation_date":"2019-10-14 14:35:06","uploaded":"2019-10-14 14:38:00","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"C3-194221 \/ S2-1907955","lsto":"SA2","Cc":"RAN1, RAN2, RAN3, CT4, SA1","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG3_interworking_ex-CN3\/TSGC3_106_Portoroz\/Docs\/C3-194330.zip","group":"C3","meeting":"C3-106","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"C3-194424","title":"LS on separating the scenarios","source":"China Telecom","contact":"Ingbert Sigovich","contact-id":28887,"tdoctype":"LS out","for":"Approval","abstract":"Release:\tRel-16\nWork Item:\ten5GPccSer\nSome operators in CT3 have raised the issue that the IMS layer cannot identified  EPS Fallback scenario from other scenarios (e.g. IMS session is initiated directly via the EPS) when the IMS receives the IP-CAN type change notification via Rx interface or access type change notification via N5 interface from the PCF. Identification of these scenarios is important from the operator\u2019s point of view.\nActions: To SA2 group: CT3 kindly asks SA2 to study this requirement and specify the possible solution in that respect.","secretary_remarks":"","agenda_item_sort_order":106,"ainumber":"18","ainame":"Joint Sessions","tdoc_agenda_sort_order":442400,"status":"revised","reservation_date":"2019-10-14 14:36:50","uploaded":"2019-10-14 14:38:01","revisionof":"","revisedto":"C3-194438","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"en5GPccSer"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA2","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG3_interworking_ex-CN3\/TSGC3_106_Portoroz\/Docs\/C3-194424.zip","group":"C3","meeting":"C3-106","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"C3-194426","title":"LS on reporting level in charging data","source":"Cisco Systems","contact":"Ingbert Sigovich","contact-id":28887,"tdoctype":"LS out","for":"Approval","abstract":"","secretary_remarks":"","agenda_item_sort_order":106,"ainumber":"18","ainame":"Joint Sessions","tdoc_agenda_sort_order":442600,"status":"revised","reservation_date":"2019-10-14 14:36:52","uploaded":"2019-10-14 14:38:01","revisionof":"","revisedto":"C3-194431","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"en5GPccSer"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA2","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG3_interworking_ex-CN3\/TSGC3_106_Portoroz\/Docs\/C3-194426.zip","group":"C3","meeting":"C3-106","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"C3-194431","title":"LS on reporting level in charging data","source":"Cisco Systems","contact":"Ingbert Sigovich","contact-id":28887,"tdoctype":"LS out","for":"Approval","abstract":"","secretary_remarks":"","agenda_item_sort_order":106,"ainumber":"18","ainame":"Joint Sessions","tdoc_agenda_sort_order":442601,"status":"approved","reservation_date":"2019-10-14 14:36:57","uploaded":"2019-10-14 14:38:01","revisionof":"C3-194426","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"en5GPccSer"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA2","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG3_interworking_ex-CN3\/TSGC3_106_Portoroz\/Docs\/C3-194431.zip","group":"C3","meeting":"C3-106","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"C3-194438","title":"LS on separating the scenarios","source":"China Telecom","contact":"Ingbert Sigovich","contact-id":28887,"tdoctype":"LS out","for":"Approval","abstract":"","secretary_remarks":"","agenda_item_sort_order":106,"ainumber":"18","ainame":"Joint Sessions","tdoc_agenda_sort_order":442401,"status":"approved","reservation_date":"2019-10-14 14:37:04","uploaded":"2019-10-14 14:38:01","revisionof":"C3-194424","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"en5GPccSer"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA2","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG3_interworking_ex-CN3\/TSGC3_106_Portoroz\/Docs\/C3-194438.zip","group":"C3","meeting":"C3-106","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]