[{"name":"C4-150457","title":"Pseudo-CR on Addressing Editor's Notes","source":"Cisco","contact":"Sridhar Bhaskaran","contact-id":58580,"tdoctype":"pCR","for":"Decision","abstract":"The following questions were raised during CT4#68 and it was discussed that these aspects need to be addressed. Hence some editor's notes were captured in v0.3.0 of TS 29.405. This contribution tries to address the questions raised and proposes a way forward to handle the editor's notes.\n1.\tDoes every request message on the Nq \/ Nq' interfaces require at least one response message?\n2.\tIs a status code required for a given eNodeB ID \/ ECGI an MME could not find any subscriber?\n3.\tIs an SGSN required to report a status code for IMSIs it could not find under it?\n4.\tIs an SGSN required to send a response if it cant find any of the IMSIs sent in the request message?\n\nWe try to analyze the questions raised above so that we arrive at some solutions \/ conclusions to address the editors notes.","secretary_remarks":"","agenda_item_sort_order":19,"ainumber":"6.2.1","ainame":"User Plane Connectivity [UPCON-DOTCON-CT]","tdoc_agenda_sort_order":0,"status":"revised","reservation_date":"2015-03-31 09:35:43","uploaded":"2015-04-02 06:17:03","revisionof":"","revisedto":"C4-150606","release":"Rel-13","crspec":29.405,"crspecversion":"0.3.0","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_68bis_Bratislava\/Docs\/C4-150457.zip","group":"C4","meeting":"C4-68","year":2015,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"C4-150462","title":"Clarification on active PDP context for GERAN","source":"Ericsson","contact":"Yong Yang","contact-id":42295,"tdoctype":"pCR","for":"Decision","abstract":"","secretary_remarks":"","agenda_item_sort_order":19,"ainumber":"6.2.1","ainame":"User Plane Connectivity [UPCON-DOTCON-CT]","tdoc_agenda_sort_order":0,"status":"rejected","reservation_date":"2015-03-31 10:00:44","uploaded":"2015-04-02 16:03:48","revisionof":"","revisedto":"","release":"Rel-13","crspec":29.405,"crspecversion":"0.5.0","workitem":[{"winame":"UPCON-DOTCON-CT"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_68bis_Bratislava\/Docs\/C4-150462.zip","group":"C4","meeting":"C4-68","year":2015,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"C4-150463","title":"Discussion on NqAP procedures and transactions","source":"Ericsson","contact":"Yong Yang","contact-id":42295,"tdoctype":"other","for":"Decision","abstract":"","secretary_remarks":"","agenda_item_sort_order":19,"ainumber":"6.2.1","ainame":"User Plane Connectivity [UPCON-DOTCON-CT]","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2015-03-31 10:03:36","uploaded":"2015-04-02 16:03:48","revisionof":"","revisedto":"","release":"Rel-13","crspec":29.405,"crspecversion":"0.5.0","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_68bis_Bratislava\/Docs\/C4-150463.zip","group":"C4","meeting":"C4-68","year":2015,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"C4-150555","title":"Removal of the Editor's Note concerning push mechanism","source":"ORANGE","contact":"Julien Bournelle","contact-id":41373,"tdoctype":"pCR","for":"Decision","abstract":"This pCR removes the Editor's Note concerning push mechanism.","secretary_remarks":"","agenda_item_sort_order":19,"ainumber":"6.2.1","ainame":"User Plane Connectivity [UPCON-DOTCON-CT]","tdoc_agenda_sort_order":0,"status":"revised","reservation_date":"2015-04-01 17:00:59","uploaded":"2015-04-07 10:20:03","revisionof":"","revisedto":"C4-150649","release":"Rel-13","crspec":29.405,"crspecversion":"0.3.0","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_68bis_Bratislava\/Docs\/C4-150555.zip","group":"C4","meeting":"C4-68","year":2015,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"C4-150606","title":"Pseudo-CR on Addressing Editor's Notes","source":"Cisco","contact":"Sridhar Bhaskaran","contact-id":58580,"tdoctype":"pCR","for":"Decision","abstract":"The following questions were raised during CT4#68 and it was discussed that these aspects need to be addressed. Hence some editor's notes were captured in v0.3.0 of TS 29.405. This contribution tries to address the questions raised and proposes a way forward to handle the editor's notes.\n1.\tDoes every request message on the Nq \/ Nq' interfaces require at least one response message?\n2.\tIs a status code required for a given eNodeB ID \/ ECGI an MME could not find any subscriber?\n3.\tIs an SGSN required to report a status code for IMSIs it could not find under it?\n4.\tIs an SGSN required to send a response if it cant find any of the IMSIs sent in the request message?\n\nWe try to analyze the questions raised above so that we arrive at some solutions \/ conclusions to address the editors notes.","secretary_remarks":"","agenda_item_sort_order":19,"ainumber":"6.2.1","ainame":"User Plane Connectivity [UPCON-DOTCON-CT]","tdoc_agenda_sort_order":0,"status":"revised","reservation_date":"2015-04-14 10:49:16","uploaded":"2015-04-16 12:22:54","revisionof":"C4-150457","revisedto":"C4-150695","release":"Rel-13","crspec":29.405,"crspecversion":"0.3.0","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_68bis_Bratislava\/Docs\/C4-150606.zip","group":"C4","meeting":"C4-68","year":2015,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"C4-150649","title":"Removal of the Editor's Note concerning push mechanism","source":"ORANGE","contact":"Julien Bournelle","contact-id":41373,"tdoctype":"pCR","for":"Decision","abstract":"This pCR removes the Editor's Note concerning push mechanism.","secretary_remarks":"","agenda_item_sort_order":19,"ainumber":"6.2.1","ainame":"User Plane Connectivity [UPCON-DOTCON-CT]","tdoc_agenda_sort_order":0,"status":"agreed","reservation_date":"2015-04-15 10:36:00","uploaded":"2015-04-16 08:04:28","revisionof":"C4-150555","revisedto":"","release":"Rel-13","crspec":29.405,"crspecversion":"0.3.0","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_68bis_Bratislava\/Docs\/C4-150649.zip","group":"C4","meeting":"C4-68","year":2015,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"C4-150680","title":"3GPP TS 29.405 v0.4.0","source":"Huawei","contact":"Xiaoyan Shi","contact-id":43518,"tdoctype":"draft TS","for":"Decision","abstract":"","secretary_remarks":"","agenda_item_sort_order":19,"ainumber":"6.2.1","ainame":"User Plane Connectivity [UPCON-DOTCON-CT]","tdoc_agenda_sort_order":0,"status":"agreed","reservation_date":"2015-04-16 10:02:15","uploaded":"2015-04-25 11:30:30","revisionof":"","revisedto":"","release":"Rel-13","crspec":29.405,"crspecversion":"0.4.0","workitem":[{"winame":"UPCON-DOTCON-CT"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_68bis_Bratislava\/Docs\/C4-150680.zip","group":"C4","meeting":"C4-68","year":2015,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"C4-150695","title":"Pseudo-CR on Addressing Editor's Notes","source":"Cisco","contact":"Sridhar Bhaskaran","contact-id":58580,"tdoctype":"pCR","for":"Decision","abstract":"The following questions were raised during CT4#68 and it was discussed that these aspects need to be addressed. Hence some editor's notes were captured in v0.3.0 of TS 29.405. This contribution tries to address the questions raised and proposes a way forward to handle the editor's notes.\n1.\tDoes every request message on the Nq \/ Nq' interfaces require at least one response message?\n2.\tIs a status code required for a given eNodeB ID \/ ECGI an MME could not find any subscriber?\n3.\tIs an SGSN required to report a status code for IMSIs it could not find under it?\n4.\tIs an SGSN required to send a response if it cant find any of the IMSIs sent in the request message?\n\nWe try to analyze the questions raised above so that we arrive at some solutions \/ conclusions to address the editors notes.","secretary_remarks":"","agenda_item_sort_order":19,"ainumber":"6.2.1","ainame":"User Plane Connectivity [UPCON-DOTCON-CT]","tdoc_agenda_sort_order":0,"status":"revised","reservation_date":"2015-04-16 14:25:23","uploaded":"2015-04-17 07:21:08","revisionof":"C4-150606","revisedto":"C4-150713","release":"Rel-13","crspec":29.405,"crspecversion":"0.3.0","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_68bis_Bratislava\/Docs\/C4-150695.zip","group":"C4","meeting":"C4-68","year":2015,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"C4-150713","title":"Pseudo-CR on Addressing Editor's Notes","source":"Cisco","contact":"Sridhar Bhaskaran","contact-id":58580,"tdoctype":"pCR","for":"Decision","abstract":"The following questions were raised during CT4#68 and it was discussed that these aspects need to be addressed. Hence some editor's notes were captured in v0.3.0 of TS 29.405. This contribution tries to address the questions raised and proposes a way forward to handle the editor's notes.\n1.\tDoes every request message on the Nq \/ Nq' interfaces require at least one response message?\n2.\tIs a status code required for a given eNodeB ID \/ ECGI an MME could not find any subscriber?\n3.\tIs an SGSN required to report a status code for IMSIs it could not find under it?\n4.\tIs an SGSN required to send a response if it cant find any of the IMSIs sent in the request message?\n\nWe try to analyze the questions raised above so that we arrive at some solutions \/ conclusions to address the editors notes.","secretary_remarks":"","agenda_item_sort_order":19,"ainumber":"6.2.1","ainame":"User Plane Connectivity [UPCON-DOTCON-CT]","tdoc_agenda_sort_order":0,"status":"agreed","reservation_date":"2015-04-20 22:25:21","uploaded":"2015-04-23 07:41:31","revisionof":"C4-150695","revisedto":"","release":"Rel-13","crspec":29.405,"crspecversion":"0.3.0","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_68bis_Bratislava\/Docs\/C4-150713.zip","group":"C4","meeting":"C4-68","year":2015,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]