[{"name":"C4-225254","title":"PCF selection","source":"Huawei","contact":"Caixia Qi","contact-id":56676,"tdoctype":"CR","for":"Agreement","abstract":"As defined in clause 5.2.7.2.2 of 3GPP TS 23.502:\n\n-\tIf the consumer is PCF or SMF, it includes the MA PDU Session capability to indicate if the NF instance supports MA PDU session or not.\n-\tIf the consumer is PCF, it includes the DNN replacement capability to indicate if the NF instance supports DNN replacement or not.\n\nThe MA PDU Session capability and DNN replacement capability have not been supported by the PCF in Nnrf_NFManagement_NFRegister service operation. The MA PDU Session capability is not supported by the SMF.","secretary_remarks":"","agenda_item_sort_order":87,"ainumber":"8.1.1","ainame":"Service based Interface protocol improvements [SBIProtoc16]","tdoc_agenda_sort_order":52540,"status":"postponed","reservation_date":"2022-11-03 11:52:55","uploaded":"2022-11-04 10:39:51","revisionof":"","revisedto":"","release":"Rel-16","crspec":29.51,"crspecversion":"16.12.0","workitem":[{"winame":"SBIProtoc16"}],"crnumber":776.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_113_Toulouse\/Docs\/C4-225254.zip","group":"C4","meeting":"C4-113","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"C4-225255","title":"PCF selection","source":"Huawei","contact":"Caixia Qi","contact-id":56676,"tdoctype":"CR","for":"Agreement","abstract":"","secretary_remarks":"","agenda_item_sort_order":87,"ainumber":"8.1.1","ainame":"Service based Interface protocol improvements [SBIProtoc16]","tdoc_agenda_sort_order":52550,"status":"postponed","reservation_date":"2022-11-03 11:52:56","uploaded":"2022-11-04 10:39:51","revisionof":"","revisedto":"","release":"Rel-17","crspec":29.51,"crspecversion":"17.7.0","workitem":[{"winame":"SBIProtoc16"}],"crnumber":777.0,"crrevision":"","crcategory":"A","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_113_Toulouse\/Docs\/C4-225255.zip","group":"C4","meeting":"C4-113","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"C4-225256","title":"PCF selection","source":"Huawei","contact":"Caixia Qi","contact-id":56676,"tdoctype":"CR","for":"Agreement","abstract":"","secretary_remarks":"","agenda_item_sort_order":87,"ainumber":"8.1.1","ainame":"Service based Interface protocol improvements [SBIProtoc16]","tdoc_agenda_sort_order":52560,"status":"postponed","reservation_date":"2022-11-03 11:52:57","uploaded":"2022-11-04 10:39:51","revisionof":"","revisedto":"","release":"Rel-18","crspec":29.51,"crspecversion":"18.0.0","workitem":[{"winame":"SBIProtoc16"}],"crnumber":778.0,"crrevision":"","crcategory":"A","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_113_Toulouse\/Docs\/C4-225256.zip","group":"C4","meeting":"C4-113","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"C4-225257","title":"Invalid API version in URI in indirect communication","source":"Huawei","contact":"Caixia Qi","contact-id":56676,"tdoctype":"CR","for":"Agreement","abstract":"","secretary_remarks":"","agenda_item_sort_order":87,"ainumber":"8.1.1","ainame":"Service based Interface protocol improvements [SBIProtoc16]","tdoc_agenda_sort_order":52570,"status":"merged","reservation_date":"2022-11-03 11:52:58","uploaded":"2022-11-04 10:39:51","revisionof":"","revisedto":"","release":"Rel-16","crspec":29.571,"crspecversion":"16.13.0","workitem":[{"winame":"SBIProtoc16"}],"crnumber":387.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_113_Toulouse\/Docs\/C4-225257.zip","group":"C4","meeting":"C4-113","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"C4-225258","title":"Invalid API version in URI in indirect communication","source":"Huawei","contact":"Caixia Qi","contact-id":56676,"tdoctype":"CR","for":"Agreement","abstract":"","secretary_remarks":"","agenda_item_sort_order":87,"ainumber":"8.1.1","ainame":"Service based Interface protocol improvements [SBIProtoc16]","tdoc_agenda_sort_order":52580,"status":"merged","reservation_date":"2022-11-03 11:52:59","uploaded":"2022-11-04 10:39:51","revisionof":"","revisedto":"","release":"Rel-17","crspec":29.571,"crspecversion":"17.7.0","workitem":[{"winame":"SBIProtoc16"}],"crnumber":388.0,"crrevision":"","crcategory":"A","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_113_Toulouse\/Docs\/C4-225258.zip","group":"C4","meeting":"C4-113","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"C4-225367","title":"Clarification on error handling at SEPP","source":"NTT DOCOMO INC.","contact":"Hiroshi Ishikawa","contact-id":91542,"tdoctype":"CR","for":"Agreement","abstract":"When using PRINS, HTTP Proxy in the IPX can return an error on behalf of HTTP server (i.e. target NFs) based on its application logic.\n\nIn such case, the originating SEPP needs to be able to return the message towards HTTP client (i.e. originating NFs) with the HTTP status codes and application error generated by the HTTP Proxy in the IPX.\n\nThe current spec is not clear in terms of whether:\n-\tGeneric HTTP status codes as defined in Table 5.2.7.1-1 are applicable\n-\tSEPP is expected to transparently forward the HTTP status code and application error that HTTP Proxy generates","secretary_remarks":"","agenda_item_sort_order":87,"ainumber":"8.1.1","ainame":"Service based Interface protocol improvements [SBIProtoc16]","tdoc_agenda_sort_order":53670,"status":"revised","reservation_date":"2022-11-08 08:42:03","uploaded":"2022-11-08 08:53:42","revisionof":"","revisedto":"C4-225407","release":"Rel-16","crspec":29.5,"crspecversion":"16.12.0","workitem":[{"winame":"SBIProtoc16"}],"crnumber":365.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_113_Toulouse\/Docs\/C4-225367.zip","group":"C4","meeting":"C4-113","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"C4-225368","title":"Clarification on error handling at SEPP","source":"NTT DOCOMO INC.","contact":"Hiroshi Ishikawa","contact-id":91542,"tdoctype":"CR","for":"Agreement","abstract":"","secretary_remarks":"","agenda_item_sort_order":87,"ainumber":"8.1.1","ainame":"Service based Interface protocol improvements [SBIProtoc16]","tdoc_agenda_sort_order":53680,"status":"not pursued","reservation_date":"2022-11-08 08:42:05","uploaded":"2022-11-08 08:53:42","revisionof":"","revisedto":"","release":"Rel-17","crspec":29.5,"crspecversion":"17.8.0","workitem":[{"winame":"SBIProtoc16"}],"crnumber":366.0,"crrevision":"","crcategory":"A","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_113_Toulouse\/Docs\/C4-225368.zip","group":"C4","meeting":"C4-113","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0}]