[{"name":"S6-220129","title":"Correction on Message Segment Recovery","source":"Huawei, Hisilicon","contact":"Han Wang","contact-id":92678,"tdoctype":"CR","for":"Approval","abstract":"Firstly, Point-to-Point message should support MSGin5G Message Segment Recovery flow ;\nSecondly, the description should be corrected in clause 8.5.6 and align with the figure steps (figure 8.5.6-1).","secretary_remarks":"","agenda_item_sort_order":24,"ainumber":"7.1","ainame":"5GMARCH - Application Architecture for MSGin5G Service","tdoc_agenda_sort_order":0,"status":"revised","reservation_date":"2022-02-08 10:43:04","uploaded":"2022-02-08 11:23:20","revisionof":"","revisedto":"S6-220362","release":"Rel-17","crspec":"23.554","crspecversion":"17.1.0","workitem":[{"winame":"5GMARCH"}],"crnumber":21.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG6_MissionCritical\/TSGS6_047-e\/Docs\/S6-220129.zip","group":"S6","meeting":"S6-47-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S6-220130","title":"Correction on Point-to-Point Message Segmentation and Reassembly","source":"Huawei, Hisilicon","contact":"Han Wang","contact-id":92678,"tdoctype":"CR","for":"Approval","abstract":"Proposal for including a recovery step in MSGin5G message segmentation and reassembly procedure.","secretary_remarks":"","agenda_item_sort_order":24,"ainumber":"7.1","ainame":"5GMARCH - Application Architecture for MSGin5G Service","tdoc_agenda_sort_order":0,"status":"revised","reservation_date":"2022-02-08 10:45:15","uploaded":"2022-02-08 11:23:20","revisionof":"","revisedto":"S6-220363","release":"Rel-17","crspec":"23.554","crspecversion":"17.1.0","workitem":[{"winame":"5GMARCH"}],"crnumber":22.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG6_MissionCritical\/TSGS6_047-e\/Docs\/S6-220130.zip","group":"S6","meeting":"S6-47-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S6-220131","title":"Correction on Usage of Network Capabilities","source":"Huawei, Hisilicon","contact":"Han Wang","contact-id":92678,"tdoctype":"CR","for":"Approval","abstract":"Proposal adding references for T8\/N33 where they first appear.","secretary_remarks":"","agenda_item_sort_order":24,"ainumber":"7.1","ainame":"5GMARCH - Application Architecture for MSGin5G Service","tdoc_agenda_sort_order":0,"status":"revised","reservation_date":"2022-02-08 10:46:49","uploaded":"2022-02-08 11:23:20","revisionof":"","revisedto":"S6-220435","release":"Rel-17","crspec":"23.554","crspecversion":"17.1.0","workitem":[{"winame":"5GMARCH"}],"crnumber":23.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG6_MissionCritical\/TSGS6_047-e\/Docs\/S6-220131.zip","group":"S6","meeting":"S6-47-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S6-220132","title":"Editoral corrections","source":"Huawei, Hisilicon","contact":"Han Wang","contact-id":92678,"tdoctype":"CR","for":"Approval","abstract":"Proposal to correct a number of editorial errors.","secretary_remarks":"","agenda_item_sort_order":24,"ainumber":"7.1","ainame":"5GMARCH - Application Architecture for MSGin5G Service","tdoc_agenda_sort_order":0,"status":"revised","reservation_date":"2022-02-08 10:48:43","uploaded":"2022-02-08 11:23:20","revisionof":"","revisedto":"S6-220436","release":"Rel-17","crspec":"23.554","crspecversion":"17.1.0","workitem":[{"winame":"5GMARCH"}],"crnumber":24.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG6_MissionCritical\/TSGS6_047-e\/Docs\/S6-220132.zip","group":"S6","meeting":"S6-47-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S6-220135","title":"Correction the last step of Segmentation and Reassembly","source":"Huawei, Hisilicon","contact":"Han Wang","contact-id":92678,"tdoctype":"CR","for":"Approval","abstract":"Proposal to delete notification of receiving failed message to Application Clientas superfluous.","secretary_remarks":"","agenda_item_sort_order":24,"ainumber":"7.1","ainame":"5GMARCH - Application Architecture for MSGin5G Service","tdoc_agenda_sort_order":0,"status":"postponed","reservation_date":"2022-02-08 11:15:31","uploaded":"2022-02-08 11:23:20","revisionof":"","revisedto":"","release":"Rel-17","crspec":"23.554","crspecversion":"17.1.0","workitem":[{"winame":"5GMARCH"}],"crnumber":25.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG6_MissionCritical\/TSGS6_047-e\/Docs\/S6-220135.zip","group":"S6","meeting":"S6-47-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S6-220174","title":"Clarification on clause 5.3.3  functional entity of MSGin5G Client","source":"China Mobile Com. Corporation","contact":"Yue Liu","contact-id":80533,"tdoctype":"CR","for":"Agreement","abstract":"The present CR proposes clarification on functional entity of MSGin5G Client in the constrained device scenario.","secretary_remarks":"","agenda_item_sort_order":24,"ainumber":"7.1","ainame":"5GMARCH - Application Architecture for MSGin5G Service","tdoc_agenda_sort_order":0,"status":"revised","reservation_date":"2022-02-08 16:12:04","uploaded":"2022-02-08 16:26:25","revisionof":"","revisedto":"S6-220318","release":"Rel-17","crspec":"23.554","crspecversion":"17.1.0","workitem":[{"winame":"5GMARCH"}],"crnumber":26.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG6_MissionCritical\/TSGS6_047-e\/Docs\/S6-220174.zip","group":"S6","meeting":"S6-47-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S6-220175","title":"correction on clause 8.8 Other MSGin5G messaging related procedures","source":"China Mobile Com. Corporation","contact":"Yue Liu","contact-id":80533,"tdoctype":"CR","for":"Agreement","abstract":"Two different procedures for Messaging Topic unsubscription are specified. The present CR proposes clarification on how to choose the procedure.","secretary_remarks":"","agenda_item_sort_order":24,"ainumber":"7.1","ainame":"5GMARCH - Application Architecture for MSGin5G Service","tdoc_agenda_sort_order":0,"status":"revised","reservation_date":"2022-02-08 16:18:47","uploaded":"2022-02-08 16:26:25","revisionof":"","revisedto":"S6-220319","release":"Rel-17","crspec":"23.554","crspecversion":"17.1.0","workitem":[{"winame":"5GMARCH"}],"crnumber":27.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG6_MissionCritical\/TSGS6_047-e\/Docs\/S6-220175.zip","group":"S6","meeting":"S6-47-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S6-220177","title":"Clarification and correction on clause 8.11 Constrained devices","source":"China Mobile Com. Corporation","contact":"Yue Liu","contact-id":80533,"tdoctype":"CR","for":"Agreement","abstract":"The text of 8.11 is not very clair since two architectural choices for constrained device is mentioned in clause 5, but only the procedure in MSGin5G-5 reference point is mentioned in clause 8.11.\nThe present CR proposes clarification and correction to the clause 8.11.","secretary_remarks":"","agenda_item_sort_order":24,"ainumber":"7.1","ainame":"5GMARCH - Application Architecture for MSGin5G Service","tdoc_agenda_sort_order":0,"status":"revised","reservation_date":"2022-02-08 16:23:02","uploaded":"2022-02-08 16:26:25","revisionof":"","revisedto":"S6-220320","release":"Rel-17","crspec":"23.554","crspecversion":"17.1.0","workitem":[{"winame":"5GMARCH"}],"crnumber":28.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG6_MissionCritical\/TSGS6_047-e\/Docs\/S6-220177.zip","group":"S6","meeting":"S6-47-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S6-220187","title":"Definitions of Gateway UE and Relay UE","source":"Samsung","contact":"Basavaraj (Basu) Pattan","contact-id":61285,"tdoctype":"CR","for":"Agreement","abstract":"The CR proposes adding definitions of Gateway MSGin5G UE and Relay MSGin5G UE.","secretary_remarks":"","agenda_item_sort_order":24,"ainumber":"7.1","ainame":"5GMARCH - Application Architecture for MSGin5G Service","tdoc_agenda_sort_order":0,"status":"revised","reservation_date":"2022-02-08 18:33:25","uploaded":"2022-02-08 19:11:44","revisionof":"","revisedto":"S6-220368","release":"Rel-17","crspec":"23.554","crspecversion":"17.1.0","workitem":[{"winame":"5GMARCH"}],"crnumber":29.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG6_MissionCritical\/TSGS6_047-e\/Docs\/S6-220187.zip","group":"S6","meeting":"S6-47-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S6-220318","title":"Clarification on clause 5.3.3  functional entity of MSGin5G Client","source":"China Mobile Com. Corporation","contact":"Yue Liu","contact-id":80533,"tdoctype":"CR","for":"Agreement","abstract":"The present CR proposes clarification on functional entity of MSGin5G Client in the constrained device scenario.","secretary_remarks":"","agenda_item_sort_order":24,"ainumber":"7.1","ainame":"5GMARCH - Application Architecture for MSGin5G Service","tdoc_agenda_sort_order":0,"status":"revised","reservation_date":"2022-02-19 14:10:40","uploaded":"2022-02-21 04:44:29","revisionof":"S6-220174","revisedto":"S6-220437","release":"Rel-17","crspec":"23.554","crspecversion":"17.1.0","workitem":[{"winame":"5GMARCH"}],"crnumber":26.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG6_MissionCritical\/TSGS6_047-e\/Docs\/S6-220318.zip","group":"S6","meeting":"S6-47-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S6-220319","title":"correction on clause 8.8 Other MSGin5G messaging related procedures","source":"China Mobile Com. Corporation","contact":"Yue Liu","contact-id":80533,"tdoctype":"CR","for":"Agreement","abstract":"Two different procedures for Messaging Topic unsubscription are specified. The present CR proposes clarification on how to choose the procedure.","secretary_remarks":"","agenda_item_sort_order":24,"ainumber":"7.1","ainame":"5GMARCH - Application Architecture for MSGin5G Service","tdoc_agenda_sort_order":0,"status":"revised","reservation_date":"2022-02-19 14:12:46","uploaded":"2022-02-21 04:44:29","revisionof":"S6-220175","revisedto":"S6-220438","release":"Rel-17","crspec":"23.554","crspecversion":"17.1.0","workitem":[{"winame":"5GMARCH"}],"crnumber":27.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG6_MissionCritical\/TSGS6_047-e\/Docs\/S6-220319.zip","group":"S6","meeting":"S6-47-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S6-220320","title":"Clarification and correction on clause 8.11 Constrained devices","source":"China Mobile Com. Corporation","contact":"Yue Liu","contact-id":80533,"tdoctype":"CR","for":"Agreement","abstract":"The text of 8.11 is not very clair since two architectural choices for constrained device is mentioned in clause 5, but only the procedure in MSGin5G-5 reference point is mentioned in clause 8.11.\nThe present CR proposes clarification and correction to the clause 8.11.","secretary_remarks":"","agenda_item_sort_order":24,"ainumber":"7.1","ainame":"5GMARCH - Application Architecture for MSGin5G Service","tdoc_agenda_sort_order":0,"status":"revised","reservation_date":"2022-02-19 14:14:24","uploaded":"2022-02-21 04:44:29","revisionof":"S6-220177","revisedto":"S6-220439","release":"Rel-17","crspec":"23.554","crspecversion":"17.1.0","workitem":[{"winame":"5GMARCH"}],"crnumber":28.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG6_MissionCritical\/TSGS6_047-e\/Docs\/S6-220320.zip","group":"S6","meeting":"S6-47-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S6-220362","title":"Correction on Message Segment Recovery","source":"Huawei, Hisilicon","contact":"Han Wang","contact-id":92678,"tdoctype":"CR","for":"Approval","abstract":"Firstly, Point-to-Point message should support MSGin5G Message Segment Recovery flow ;\nSecondly, the description should be corrected in clause 8.5.6 and align with the figure steps (figure 8.5.6-1).","secretary_remarks":"","agenda_item_sort_order":24,"ainumber":"7.1","ainame":"5GMARCH - Application Architecture for MSGin5G Service","tdoc_agenda_sort_order":0,"status":"revised","reservation_date":"2022-02-20 11:34:38","uploaded":"2022-02-20 11:56:45","revisionof":"S6-220129","revisedto":"S6-220433","release":"Rel-17","crspec":"23.554","crspecversion":"17.1.0","workitem":[{"winame":"5GMARCH"}],"crnumber":21.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG6_MissionCritical\/TSGS6_047-e\/Docs\/S6-220362.zip","group":"S6","meeting":"S6-47-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S6-220363","title":"Correction on Point-to-Point Message Segmentation and Reassembly","source":"Huawei, Hisilicon","contact":"Han Wang","contact-id":92678,"tdoctype":"CR","for":"Approval","abstract":"Proposal for including a recovery step in MSGin5G message segmentation and reassembly procedure.","secretary_remarks":"","agenda_item_sort_order":24,"ainumber":"7.1","ainame":"5GMARCH - Application Architecture for MSGin5G Service","tdoc_agenda_sort_order":0,"status":"revised","reservation_date":"2022-02-20 11:47:46","uploaded":"2022-02-20 11:56:45","revisionof":"S6-220130","revisedto":"S6-220434","release":"Rel-17","crspec":"23.554","crspecversion":"17.1.0","workitem":[{"winame":"5GMARCH"}],"crnumber":22.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG6_MissionCritical\/TSGS6_047-e\/Docs\/S6-220363.zip","group":"S6","meeting":"S6-47-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S6-220368","title":"5GMARCH_Definitions of gateway UE and relay UE","source":"Samsung","contact":"Basavaraj (Basu) Pattan","contact-id":61285,"tdoctype":"CR","for":"Agreement","abstract":"","secretary_remarks":"","agenda_item_sort_order":24,"ainumber":"7.1","ainame":"5GMARCH - Application Architecture for MSGin5G Service","tdoc_agenda_sort_order":0,"status":"agreed","reservation_date":"2022-02-20 12:06:09","uploaded":"2022-02-20 12:18:25","revisionof":"S6-220187","revisedto":"","release":"Rel-17","crspec":"23.554","crspecversion":"17.1.0","workitem":[{"winame":"5GMARCH"}],"crnumber":29.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-220105","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG6_MissionCritical\/TSGS6_047-e\/Docs\/S6-220368.zip","group":"S6","meeting":"S6-47-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S6-220433","title":"Correction on Message Segment Recovery","source":"Huawei, Hisilicon","contact":"Han Wang","contact-id":92678,"tdoctype":"CR","for":"Approval","abstract":"","secretary_remarks":"","agenda_item_sort_order":24,"ainumber":"7.1","ainame":"5GMARCH - Application Architecture for MSGin5G Service","tdoc_agenda_sort_order":1292,"status":"agreed","reservation_date":"2022-02-23 00:49:50","uploaded":"2022-02-23 00:51:36","revisionof":"S6-220362","revisedto":"","release":"Rel-17","crspec":"23.554","crspecversion":"17.1.0","workitem":[{"winame":"5GMARCH"}],"crnumber":21.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"SP-220105","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG6_MissionCritical\/TSGS6_047-e\/Docs\/S6-220433.zip","group":"S6","meeting":"S6-47-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S6-220434","title":"Correction on Point-to-Point Message Segmentation and Reassembly","source":"Huawei, Hisilicon","contact":"Han Wang","contact-id":92678,"tdoctype":"CR","for":"Approval","abstract":"","secretary_remarks":"","agenda_item_sort_order":24,"ainumber":"7.1","ainame":"5GMARCH - Application Architecture for MSGin5G Service","tdoc_agenda_sort_order":1302,"status":"agreed","reservation_date":"2022-02-23 00:49:50","uploaded":"2022-02-23 00:51:36","revisionof":"S6-220363","revisedto":"","release":"Rel-17","crspec":"23.554","crspecversion":"17.1.0","workitem":[{"winame":"5GMARCH"}],"crnumber":22.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"SP-220105","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG6_MissionCritical\/TSGS6_047-e\/Docs\/S6-220434.zip","group":"S6","meeting":"S6-47-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S6-220435","title":"Correction on Usage of Network Capabilities","source":"Huawei, Hisilicon","contact":"Han Wang","contact-id":92678,"tdoctype":"CR","for":"Approval","abstract":"","secretary_remarks":"","agenda_item_sort_order":24,"ainumber":"7.1","ainame":"5GMARCH - Application Architecture for MSGin5G Service","tdoc_agenda_sort_order":1311,"status":"agreed","reservation_date":"2022-02-23 00:49:51","uploaded":"2022-02-23 00:51:36","revisionof":"S6-220131","revisedto":"","release":"Rel-17","crspec":"23.554","crspecversion":"17.1.0","workitem":[{"winame":"5GMARCH"}],"crnumber":23.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-220105","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG6_MissionCritical\/TSGS6_047-e\/Docs\/S6-220435.zip","group":"S6","meeting":"S6-47-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S6-220436","title":"Editoral corrections","source":"Huawei, Hisilicon","contact":"Han Wang","contact-id":92678,"tdoctype":"CR","for":"Approval","abstract":"","secretary_remarks":"","agenda_item_sort_order":24,"ainumber":"7.1","ainame":"5GMARCH - Application Architecture for MSGin5G Service","tdoc_agenda_sort_order":1321,"status":"agreed","reservation_date":"2022-02-23 00:49:52","uploaded":"2022-02-23 00:51:36","revisionof":"S6-220132","revisedto":"","release":"Rel-17","crspec":"23.554","crspecversion":"17.1.0","workitem":[{"winame":"5GMARCH"}],"crnumber":24.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-220105","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG6_MissionCritical\/TSGS6_047-e\/Docs\/S6-220436.zip","group":"S6","meeting":"S6-47-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S6-220437","title":"Clarification on clause 5.3.3  functional entity of MSGin5G Client","source":"China Mobile Com. Corporation","contact":"Yue Liu","contact-id":80533,"tdoctype":"CR","for":"Agreement","abstract":"","secretary_remarks":"","agenda_item_sort_order":24,"ainumber":"7.1","ainame":"5GMARCH - Application Architecture for MSGin5G Service","tdoc_agenda_sort_order":1742,"status":"agreed","reservation_date":"2022-02-23 00:49:53","uploaded":"2022-02-23 00:51:36","revisionof":"S6-220318","revisedto":"","release":"Rel-17","crspec":"23.554","crspecversion":"17.1.0","workitem":[{"winame":"5GMARCH"}],"crnumber":26.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"SP-220105","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG6_MissionCritical\/TSGS6_047-e\/Docs\/S6-220437.zip","group":"S6","meeting":"S6-47-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S6-220438","title":"correction on clause 8.8 Other MSGin5G messaging related procedures","source":"China Mobile Com. Corporation","contact":"Yue Liu","contact-id":80533,"tdoctype":"CR","for":"Agreement","abstract":"","secretary_remarks":"","agenda_item_sort_order":24,"ainumber":"7.1","ainame":"5GMARCH - Application Architecture for MSGin5G Service","tdoc_agenda_sort_order":1752,"status":"agreed","reservation_date":"2022-02-23 00:49:55","uploaded":"2022-02-23 00:51:36","revisionof":"S6-220319","revisedto":"","release":"Rel-17","crspec":"23.554","crspecversion":"17.1.0","workitem":[{"winame":"5GMARCH"}],"crnumber":27.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"SP-220105","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG6_MissionCritical\/TSGS6_047-e\/Docs\/S6-220438.zip","group":"S6","meeting":"S6-47-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S6-220439","title":"Clarification and correction on clause 8.11 Constrained devices","source":"China Mobile Com. Corporation","contact":"Yue Liu","contact-id":80533,"tdoctype":"CR","for":"Agreement","abstract":"","secretary_remarks":"","agenda_item_sort_order":24,"ainumber":"7.1","ainame":"5GMARCH - Application Architecture for MSGin5G Service","tdoc_agenda_sort_order":1772,"status":"agreed","reservation_date":"2022-02-23 00:49:56","uploaded":"2022-02-23 00:51:36","revisionof":"S6-220320","revisedto":"","release":"Rel-17","crspec":"23.554","crspecversion":"17.1.0","workitem":[{"winame":"5GMARCH"}],"crnumber":28.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"SP-220105","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG6_MissionCritical\/TSGS6_047-e\/Docs\/S6-220439.zip","group":"S6","meeting":"S6-47-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]