[{"name":"C3-195173","title":"Reply LS to LS on maximum value of MDBV","source":"CT4","contact":"Hao Jing","contact-id":83214,"tdoctype":"LS in","for":"Discussion","abstract":"CT4 kindly asks SA2 group to take the above information into account and to provide a recommendation on the maximum allowed value of MDBV.","secretary_remarks":"","agenda_item_sort_order":15,"ainumber":"6","ainame":"Received Liaison Statements","tdoc_agenda_sort_order":51730,"status":"noted","reservation_date":"2019-11-04 10:47:05","uploaded":"2019-11-04 11:08:37","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA2","Cc":"RAN1, RAN2, RAN3, CT3, SA1","lsoriginalls":"S2-1907955","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG3_interworking_ex-CN3\/TSGC3_107_Reno\/Docs\/C3-195173.zip","group":"C3","meeting":"C3-107","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"C3-195174","title":"LS on NID structure and length","source":"CT4","contact":"Hao Jing","contact-id":83214,"tdoctype":"LS in","for":"Discussion","abstract":"CT4 would like to ask RAN2, RAN3, CT1 and CT3 to take this information into account and provide feedback, if necessary.","secretary_remarks":"","agenda_item_sort_order":15,"ainumber":"6","ainame":"Received Liaison Statements","tdoc_agenda_sort_order":51750,"status":"noted","reservation_date":"2019-11-04 10:47:05","uploaded":"2019-11-04 11:08:37","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"Vertical_LAN"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN2, RAN3, CT1, CT3","Cc":"SA2","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG3_interworking_ex-CN3\/TSGC3_107_Reno\/Docs\/C3-195174.zip","group":"C3","meeting":"C3-107","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"C3-195175","title":"LS on Support of Network Address Translation in the User Plane function","source":"CT4","contact":"Hao Jing","contact-id":83214,"tdoctype":"LS in","for":"Discussion","abstract":"CT4 kindly requests SA2 to answer whether specific requirements are expected for the control of NAT in the user plane function over N4\/Sxb and, if so, to consider specifying the relevant stage 2 requirements.","secretary_remarks":"","agenda_item_sort_order":15,"ainumber":"6","ainame":"Received Liaison Statements","tdoc_agenda_sort_order":51770,"status":"noted","reservation_date":"2019-11-04 10:47:05","uploaded":"2019-11-04 11:08:37","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA2","Cc":"CT3","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG3_interworking_ex-CN3\/TSGC3_107_Reno\/Docs\/C3-195175.zip","group":"C3","meeting":"C3-107","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"C3-195176","title":"LS on Enhanced coverage restriction","source":"CT4","contact":"Hao Jing","contact-id":83214,"tdoctype":"LS in","for":"Discussion","abstract":"CT4 kindly asks SA2 to take note of the above decision and let CT4 know if SA2 sees any issue with this approach.","secretary_remarks":"","agenda_item_sort_order":15,"ainumber":"6","ainame":"Received Liaison Statements","tdoc_agenda_sort_order":51780,"status":"noted","reservation_date":"2019-11-04 10:47:05","uploaded":"2019-11-04 11:08:37","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"5G_CIoT"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA2","Cc":"CT3","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG3_interworking_ex-CN3\/TSGC3_107_Reno\/Docs\/C3-195176.zip","group":"C3","meeting":"C3-107","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"C3-195177","title":"Reply LS on Nudr_DM evolution","source":"CT4","contact":"Hao Jing","contact-id":83214,"tdoctype":"LS in","for":"Discussion","abstract":"CT4 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":15,"ainumber":"6","ainame":"Received Liaison Statements","tdoc_agenda_sort_order":51790,"status":"noted","reservation_date":"2019-11-04 10:47:05","uploaded":"2019-11-04 11:08:38","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"TEI16"},{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA2","Cc":"CT3","lsoriginalls":"S2-1908635","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG3_interworking_ex-CN3\/TSGC3_107_Reno\/Docs\/C3-195177.zip","group":"C3","meeting":"C3-107","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"C3-195178","title":"Reply LS on \"SMF Event Exposure enhancement for service experience\"","source":"SA2","contact":"Hao Jing","contact-id":83214,"tdoctype":"LS in","for":"Discussion","abstract":"SA2 thanks CT3 for the \"LS on SMF Event Exposure enhancement for service experience\".\n1.\tIf the NWDAF subscribes to the SMF to collect information related to the QoS flow level Network Data event by invoking Nsmf_EventExposure service, what information is needed by the NWDAF and how the SMF determine the event is detected or not?\n[SA2 Answer]: How the SMF determine the event is detected is defined in Clause 5.2.8.3, TS 23.502.\n2.\tWhen requesting the QoS flow level Network Data from the SMF, whether the above highlighted information are all mandatory?\n[SA2 Answer]: As defined in clause 6.2.1, Clause 6.4.4 and Clause 6.4.5, TS 23.288, the data which NWDAF may collect is listed for each analytics in input data clause and is decided by the NWDAF, and therefore all the QoS flow level Network Data from the SMF are optional. \nSA2 has agreed the attached CRs to reflect the above changes.","secretary_remarks":"","agenda_item_sort_order":15,"ainumber":"6","ainame":"Received Liaison Statements","tdoc_agenda_sort_order":51800,"status":"postponed","reservation_date":"2019-11-04 10:47:05","uploaded":"2019-11-04 11:08:37","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"eNA"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT3","Cc":"","lsoriginalls":"C3-193429 \/ S2-1908665","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG3_interworking_ex-CN3\/TSGC3_107_Reno\/Docs\/C3-195178.zip","group":"C3","meeting":"C3-107","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"C3-195179","title":"Reply LS on N6 routing information in AF acknowledgement","source":"SA2","contact":"Hao Jing","contact-id":83214,"tdoctype":"LS in","for":"Discussion","abstract":"SA2 would like to thank CT3 for LS in S2-1908667\/C3-193643 and would like to provide the following feedback on the questions.\n\n[Q1] CT3 understands that if the SMF receives the AF acknowledgement indicates successful but not include N6 traffic routing information for the target DNAI, it means the N6 traffic routing information remains the same. Whether CT3\u2019s understanding aligns with stage 2?\n[SA2 Answer] \nAccording to clause 5.6.7.2 of 3GPP TS 23.501, N6 traffic routing information is provided per DNAI by AF:\n-\tInformation about the N6 traffic routing requirements that is provided per DNAI: for each DNAI, the N6 traffic routing requirements may contain a routing profile ID and\/or N6 traffic routing information.\nThe AF acknowledgement is one of the methods for the N6 traffic routing information provisioning. The AF can provide such information via PCF or NEF for future PDU sessions as well.  \nThe AF requests are sent to the PCF via N5 (in the case of requests targeting specific on-going PDU Sessions of individual UE(s), for an AF allowed to interact directly with the 5GC NFs) or via the NEF. The AF requests that target existing or future PDU Sessions of multiple UE(s) or of any UE are sent via the NEF and may target multiple PCF(s), as described in clause 6.3.7.2.\nIn the case that \u201cthe AF acknowledgement indicates successful but not include N6 traffic routing information for the target DNAI\u201d, the SMF can use the N6 traffic routing information for the target DNAI if it was provided via PCF or NEF as mentioned above. This process is described in clause 4.3.6.2 of TS 23.502.\n\n[Q2] If yes, then in the case as follows:\nif the AF does not provide the N6 routing information but just subscribe the event of UP path change notification in the previous traffic influence message via NEF and PCF, when the event is detected by the SMF, the SMF will notify the AF directly or via NEF of the UP path change event. If the AF includes the N6 traffic routing information in the acknowledgement to the SMF, then the SMF will access to the indicated N6 data network. \nAfter that, for instance, if the PDU session is re-established and the SMF is changed, the new SMF is not aware of the N6 traffic routing information, because it is unclear how the new SMF retrieve such information from the old SMF. \nin this case, the AF acknowledgement does not include the N6 traffic routing information, how the new SMF access to the desired AF?\n[SA2 Answer]\nThe subscription and notification of UP path change event are performed per PDU Session: \nThe AF may request to be subscribed to notifications about UP path management events, i.e. a UP path change occurs for the PDU Session.\nThe SMF (i.e. anchor SMF) serving a PDU session does not change during lifetime of the PDU session. When a new PDU Session is established, e.g. during PDU session re-establishment, the AF can subscribes to UP path change event during the PDU session establishment. As described in clause 4.3.6.2 of TS 23.502, the new SMF serving the new PDU session can retrieve N6 traffic routing information from PCF during the procedure.","secretary_remarks":"","agenda_item_sort_order":15,"ainumber":"6","ainame":"Received Liaison Statements","tdoc_agenda_sort_order":51810,"status":"postponed","reservation_date":"2019-11-04 10:47:05","uploaded":"2019-11-04 11:08:37","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"5G_URLLC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT3","Cc":"","lsoriginalls":"S2-1908667\/C3-193643","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG3_interworking_ex-CN3\/TSGC3_107_Reno\/Docs\/C3-195179.zip","group":"C3","meeting":"C3-107","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"C3-195180","title":"Reply LS on Nsmf_EventExposure and Nnef_EventExposure service handling of the \"Downlink data delivery status\" and \"Availability after DDN Failure\" events.","source":"SA2","contact":"Hao Jing","contact-id":83214,"tdoctype":"LS in","for":"Discussion","abstract":"SA2 asks CT3 to take the answers provided by SA2 and that related attached agreed CRs into account in the stage 3 work.","secretary_remarks":"","agenda_item_sort_order":15,"ainumber":"6","ainame":"Received Liaison Statements","tdoc_agenda_sort_order":51820,"status":"postponed","reservation_date":"2019-11-04 10:47:05","uploaded":"2019-11-04 11:08:37","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"5G_CIoT"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT3","Cc":"CT4","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG3_interworking_ex-CN3\/TSGC3_107_Reno\/Docs\/C3-195180.zip","group":"C3","meeting":"C3-107","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"C3-195181","title":"Reply LS on LS on maximum value of MDBV","source":"SA2","contact":"Hao Jing","contact-id":83214,"tdoctype":"LS in","for":"Discussion","abstract":"SA2 asks CT3 to take the answers provided by SA2 and that related attached agreed CRs into account in the stage 3 work.","secretary_remarks":"","agenda_item_sort_order":15,"ainumber":"6","ainame":"Received Liaison Statements","tdoc_agenda_sort_order":51740,"status":"noted","reservation_date":"2019-11-04 10:47:05","uploaded":"2019-11-04 11:08:37","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN3, CT4, CT3","Cc":"RAN1, RAN2, SA1","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG3_interworking_ex-CN3\/TSGC3_107_Reno\/Docs\/C3-195181.zip","group":"C3","meeting":"C3-107","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"C3-195182","title":"Reply LS on AUSF role in slice specific authentication","source":"SA2","contact":"Hao Jing","contact-id":83214,"tdoctype":"LS in","for":"Discussion","abstract":"SA2 kindly ask SA3 to:\n-\tConfirm whether the AUSF role as specified by SA2 is acceptable from a security architecture perspective.\n-\tcommunicate to SA2 any comments on the attached CR.","secretary_remarks":"","agenda_item_sort_order":15,"ainumber":"6","ainame":"Received Liaison Statements","tdoc_agenda_sort_order":51830,"status":"noted","reservation_date":"2019-11-04 10:47:05","uploaded":"2019-11-04 11:08:37","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"eNA"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA3","Cc":"CT3","lsoriginalls":"S3 193126\/S2-1908714","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG3_interworking_ex-CN3\/TSGC3_107_Reno\/Docs\/C3-195182.zip","group":"C3","meeting":"C3-107","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"C3-195183","title":"LS on QoS mapping procedure","source":"SA4","contact":"Hao Jing","contact-id":83214,"tdoctype":"LS in","for":"Discussion","abstract":"SA4 asks CT3 to consider if it would be appropriate and sufficient for the AF to use the SDP media level \u201ca=label:flus\u201d as input for a media level AF-Application-Identifier or a separate identifier, amended by information from the new 3gpp-qos-hint attribute to properly derive FLUS-specific 5QI\/QCI values for those media components in an MTSI session. SA4 also kindly asks CT3 to be informed about any identified shortcomings with this SDP approach to set FLUS-specific QoS for media components in MTSI.","secretary_remarks":"","agenda_item_sort_order":15,"ainumber":"6","ainame":"Received Liaison Statements","tdoc_agenda_sort_order":51950,"status":"postponed","reservation_date":"2019-11-04 10:47:05","uploaded":"2019-11-04 11:08:37","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"E_FLUS"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT3","Cc":"CT1","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG3_interworking_ex-CN3\/TSGC3_107_Reno\/Docs\/C3-195183.zip","group":"C3","meeting":"C3-107","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"C3-195195","title":"Reply LS on NID structure and length","source":"SA2","contact":"Hao Jing","contact-id":83214,"tdoctype":"LS in","for":"Discussion","abstract":"SA2 thanks CT4 for the LS on \" NID structure and length\".\nRegarding the length of the NID and that it is to be broadcasted, SA2 have captured the following two assumptions in TS 23.501:\n\"NOTE 1:\tIt is assumed that an NG-RAN node supports broadcasting a total of twelve NIDs. Further details are defined in TS 38.331 [28].\nNOTE 1:\tIt is assumed that an NG-RAN node supports broadcasting a total of twelve CAG Identifiers. Further details are defined in TS 38.331 [28].\"\nRegarding the supported assignment models, SA2 has agreed the attached CR.","secretary_remarks":"","agenda_item_sort_order":15,"ainumber":"6","ainame":"Received Liaison Statements","tdoc_agenda_sort_order":51760,"status":"noted","reservation_date":"2019-11-04 12:45:40","uploaded":"2019-11-04 12:48:22","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"Vertical_LAN"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN2, RAN3, CT1, CT4","Cc":"CT3","lsoriginalls":"S2-1909959 \/ C4-194332","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG3_interworking_ex-CN3\/TSGC3_107_Reno\/Docs\/C3-195195.zip","group":"C3","meeting":"C3-107","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"C3-195393","title":"Reply LS (S6-192023) on clarifications regarding SEAL services","source":"SA6","contact":"Mathieu Mangion","contact-id":27904,"tdoctype":"LS in","for":"Action","abstract":"SA6 thanks CT3 for their LS on clarifications regarding SEAL services API. SA6 would like to confirm that SEAL stage 2 specification has now been updated with the following:\n\n1.\t\"verb-xxx\" naming convention of all API names and corresponding changes to API Operations\n2.\tGrouping of group management service APIs into one service API due to similar functionality. Further Query_Group_Info and Obtain_Group_Configuration service operations are combined as the resource is same for both these operations.\n3.\tOperation semantics for some service APIs related to event subscription to follow the convention used in subclause 5.2 of TS 23.502.","secretary_remarks":"","agenda_item_sort_order":15,"ainumber":"6","ainame":"Received Liaison Statements","tdoc_agenda_sort_order":539300,"status":"revised","reservation_date":"2019-11-18 13:33:23","uploaded":"2019-11-18 13:37:54","revisionof":"","revisedto":"C3-195397","release":"","crspec":"","crspecversion":"","workitem":[{"winame":"SEAL"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT3","Cc":"CT1","lsoriginalls":"S6-192318","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG3_interworking_ex-CN3\/TSGC3_107_Reno\/Docs\/C3-195393.zip","group":"C3","meeting":"C3-107","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"C3-195397","title":"Reply LS (S6-192023) on clarifications regarding SEAL services","source":"SA6","contact":"Mathieu Mangion","contact-id":27904,"tdoctype":"LS in","for":"Action","abstract":"","secretary_remarks":"","agenda_item_sort_order":15,"ainumber":"6","ainame":"Received Liaison Statements","tdoc_agenda_sort_order":539301,"status":"noted","reservation_date":"2019-11-18 13:33:26","uploaded":"2019-11-18 13:37:54","revisionof":"C3-195393","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":[{"winame":"SEAL"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT3","Cc":"CT1","lsoriginalls":"S6-192318","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG3_interworking_ex-CN3\/TSGC3_107_Reno\/Docs\/C3-195397.zip","group":"C3","meeting":"C3-107","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]