{"text_format":"1","workbook":"xlsx","n_sheets":3,"sheets":["TDoc_List","CR_Packs_List","Parameters"],"not_rendered":{"charts":0,"images":0,"macros":1,"external_links":0,"defined_names":6,"comments":1,"pivot_tables":0},"unopened":[],"bounds":{"document_bytes":16777216,"sheet_cells":100000,"rows_first":2000,"rows_last":500,"rows_between":2000,"halvings":0,"cell_chars":16384,"cell_head_chars":4096},"cells_cut":0,"cells_raw":0,"read":"whole","date_system":"1900"}

{"sheet":"TDoc_List","index":0,"n_rows":75,"n_cols":32,"rows_kept":75,"cut":false,"hidden":false,"merged":[]}
["TDoc #","Title","Source","Contact","Contact ID","Type","Type supplement","For","Abstract","Secretary Remarks","Agenda item sort order","Agenda item #","Agenda item description","TDoc sort order within agenda item","TDoc Status","Reservation date","Uploaded","Is revision of","Revised to","Release","Spec #","Version","Related WIs","CR #","CR revision #","CR category","TSG CR Pack","Reply to","To","Cc","Original LS","Reply in"]
["S6-150101","SA6 Meeting 2 Agenda","Convenor","Andrew Howell",714,"agenda","","Decision","","","4","2","Approval of the agenda",0,"approved","2015-02-03T13:37:18.600","2015-02-03T15:44:59.547","","","","","","","","","","","","","","",""]
["S6-150102","SA6 Meeting 1 Report","MCC","Bernt Mattsson",14585,"report","","Decision","","","6","3.1","Approval of report from SA6#1",0,"approved","2015-02-03T13:41:45.503","2015-02-18T15:21:13.253","","","","","","","","","","","","","","",""]
["S6-150103","Update of MCPTT WID","BlackBerry UK Limited","Nick Russell",21192,"WID new","","Decision","This contribution proposes a minor update to the introductory text of the SA6 objectives that were agreed in SA6 #1 and adds a few more supporting companies.","","27","11.1","Agreement of New / Revised WIDS",0,"agreed","2015-02-09T11:12:02.870","2015-02-17T23:18:41.600","S6-150094","","Rel-13","","","","","","","","","","","",""]
["S6-150104","Proposal of way forward of MCPTT architecture","Huawei, Hisilicon, TD-tech","Yizhuang Wu",61155,"pCR","","Decision","this contribution give a proposal for way forward of MCPTT archtecure","","15","7","Mission Critical Push To Talk over LTE (MCPTT) architecture - Functional review",0,"noted","2015-02-16T08:26:08.133","2015-02-17T06:16:57.487","","","Rel-13","","","","","",null,"","","","","",""]
["S6-150105","MCPTT architecture for both carrier IMS and other type of SIP core","Huawei, Hisilicon, TD-tech","Yizhuang Wu",61155,"pCR","","Decision","this contribution propose a genrical architecture which include both IMS and Non-IMS based architecture to be as the basis for futher discussion","","17","8.1","General discussion items",0,"noted","2015-02-16T08:26:08.237","2015-02-17T06:16:57.520","","","Rel-13","","","","","",null,"","","","","",""]
["S6-150106","Group call setup for MCPTT user in on network use","Huawei, Hisilicon, TD-tech","Yizhuang Wu",61155,"pCR","","Decision","this contirbution gives an overview about the relationships among MCPTT user, MCPTT user’s Home MCPTT server and MCPTT user’s group home MCPTT server.And proposes a group call setup prosedure for MCPTT group user.","","21","8.5","Architecture considerations",0,"revised","2015-02-16T08:26:08.240","2015-02-17T06:16:57.540","","S6-150163","Rel-13","","","","","",null,"","","","","",""]
["S6-150107","SIP/IP Core Functions of MCPTT Application","Huawei,Hisilicon, TD-Tech","Yizhuang Wu",61155,"pCR","","Decision","This contribution discusses the MCPTT SIP core architecture and core functions, which the selection of MCPTT SIP/IP core architecture would be based on.","","21","8.5","Architecture considerations",0,"revised","2015-02-16T08:33:08.700","2015-02-17T06:34:20.873","","S6-150115, S6-150164","Rel-13","","","","","",null,"","","","","",""]
["S6-150108","Basic assumptions","BlackBerry UK Ltd.","Nick Russell",21192,"pCR","","Decision","In order to move discussions forward, some basic assumptions for the MCPTT architecture are proposed to be agreed, which it is believed can be agreed regardless of whether or not a SIP Core is IMS compliant.","","15","7","Mission Critical Push To Talk over LTE (MCPTT) architecture - Functional review",0,"revised","2015-02-16T16:44:39.333","2015-02-17T23:18:41.620","","S6-150153","Rel-13","23.779","0.5.1","MCPTT","","",null,"","","","","",""]
["S6-150109","Minor enhancements and corrections to Solution 2-1","BlackBerry UK Ltd.","Nick Russell",21192,"pCR","","Decision","Proposes some moving and repartitioning of some text, new text for the evaluation section, and corrects some minor editorials.","","21","8.5","Architecture considerations",0,"revised","2015-02-16T16:44:39.337","2015-02-17T23:18:41.643","","S6-150165","Rel-13","23.779","0.5.1","MCPTT","","",null,"","","","","",""]
["S6-150110","Addition of Registration procedure for Solution 2-1","BlackBerry UK Ltd.","Nick Russell",21192,"pCR","","Decision","This document proposes to add an information flow for the registration procedure for Solution 2-1 in TR 23.229 for the scenario where the PS-UDF selects an S-CSCF in the Public Safety domain.","","21","8.5","Architecture considerations",0,"noted","2015-02-16T16:44:39.343","2015-02-17T23:18:41.667","","S6-150216","Rel-13","23.779","0.5.1","MCPTT","","",null,"","","","","",""]
["S6-150111","LS on MCPTT core items selection","SA1","Mona Mustapha",35011,"LS in","","Decision","","","12","5.1","TSG CT, TSG RAN, TSG SA and PCG/OP",0,"noted","2015-02-17T15:25:02.633","2015-02-17T16:56:21.180","","","","","","","","","",""]
["S6-150112","LS reply on service continuity","SA1","Muthaiah Venkatachalam",39686,"LS in","","Decision","","","12","5.1","TSG CT, TSG RAN, TSG SA and PCG/OP",0,"noted","2015-02-17T15:26:07.550","2015-02-17T16:56:21.207","","","","","","","","","","",null,null,null,"S6-150100"]
["S6-150113","LS reply on support for ProSe one-to-one communication in Release 13","RAN2","Youn hyoung Heo",47007,"LS in","","Decision","","","12","5.1","TSG CT, TSG RAN, TSG SA and PCG/OP",0,"noted","2015-02-17T15:33:11.777","2015-02-17T16:56:21.230","","","","","","","","","","",null,null,null,"S6-150076"]
["S6-150114","SA6-ProSe-Status-Update","QUALCOMM UK Ltd","Alan Soloway",46784,"other","","Decision","","","29","12","AOB",0,"noted","2015-02-17T18:28:59.277","2015-02-17T23:51:41.960","","","Rel-13","","","","","","","","","","","",""]
["S6-150115","SIP/IP Core Functions of MCPTT Application","HUAWEI TECHNOLOGIES Co. Ltd.","Yanmei Yang",37039,"pCR","","Decision","","","21","8.5","Architecture considerations",0,"revised","2015-02-20T14:59:01.553","2015-02-20T15:11:52.350","S6-150107","","Rel-13","","","","","",null,"","","","","",""]
["S6-150116","Registration processing","Airbus Group SAS","Gérard Marque-Pucheu",51759,"pCR","","Decision","This contribution derives from the interoperability requirements between MCPTT systems the rules that shall be followed for the processing of MCPTT registration.","","15","7","Mission Critical Push To Talk over LTE (MCPTT) architecture - Functional review",0,"revised","2015-02-20T15:59:24.293","2015-02-23T09:29:42.970","","S6-150156","Rel-13","23.779","0.5.1","660054","","",null,"","","","","",""]
["S6-150117","Affiliation - nature and processing","Airbus Group SAS","Gérard Marque-Pucheu",51759,"pCR","","Decision","This contribution derives from the SA1 requirements, architecture requirements for the management of affiliation in MCPTT systems, including for the interoperability case","","23","8.7","Protocol considerations",0,"postponed","2015-02-20T16:02:57.173","2015-02-23T09:29:42.957","","S6-150177","Rel-13","23.779","0.5.1","660054","","",null,"","","","","",""]
["S6-150118","Registration call and roaming topics","Motorola Solutions UK Ltd.","David Chater-Lea",5018,"other","","Decision","","","15","7","Mission Critical Push To Talk over LTE (MCPTT) architecture - Functional review",0,"noted","2015-02-22T14:38:15.743","2015-02-22T14:48:34.627","","","Rel-13","","","","","","","","","","","",""]
["S6-150119","Functional diagram proposal","Motorola Solutions UK Ltd.","David Chater-Lea",5018,"pCR","","Decision","","","21","8.5","Architecture considerations",0,"noted","2015-02-22T14:41:03.537","2015-02-22T14:48:34.690","","","Rel-13","23.779","","","","",null,"","","","","",""]
["S6-150120","Proposal separate architecture solutions","Motorola Solutions UK Ltd.","David Chater-Lea",5018,"other","","Decision","","","21","8.5","Architecture considerations",0,"noted","2015-02-22T14:42:55.483","2015-02-22T14:48:34.703","","","Rel-13","23.779","","","","","","","","","","",""]
["S6-150121","Assumptions on Service Continuity based on SA1 LS (S6-150112)","LG Electronics Inc.","Hyunsook Kim",42013,"pCR","","Decision","This paper considers the working assumptions on service continuity, based on SA1 reply LS (S6-150112)","","24","9","Other MCPTT related issues (e.g. D2D)",0,"revised","2015-02-23T08:16:56.967","2015-02-23T09:27:27.797","","S6-150171","Rel-13","","","660054","","",null,"","","","","",""]
["S6-150122","Comments and Correction to 23.779","OTD","Selvam Rengasami",31626,"pCR","","Decision","","","17","8.1","General discussion items",0,"revised","2015-02-23T08:24:57.463","2015-02-23T15:04:11.390","","S6-150158","Rel-13","23.779","0.5.1","","","",null,"","","","","",""]
["S6-150123","Operator’s view for MCPTT architecture","SK Telecom","Jongmun Lee",60599,"other","","Decision","","","15","7","Mission Critical Push To Talk over LTE (MCPTT) architecture - Functional review",0,"noted","2015-02-23T08:40:49.733","2015-02-23T14:04:01.630","","","","","","","","","","","","","","",""]
["S6-150124","MCPTT terminology","Ericsson LM","Magnus Trank",60462,"other","","Decision","This contribution discusses MCPTT terminology related to MCPTT Group Call as defined in TS 22.179, and compares them with terms used in OMA PCPS","","17","8.1","General discussion items",0,"noted","2015-02-23T10:13:12.273","2015-02-23T15:29:38.210","","","Rel-13","","","","","","","","","","","",""]
["S6-150125","On media security for stateless DMO","Intel Mobile Communications","Saso Stojanovski",24932,"other","","Decision","Discusses the SA3 assumptions on media security and their applicability to stateless DMO. Proposes to liaise SA3.","","20","8.4","Security considerations",0,"noted","2015-02-23T10:30:21.063","2015-02-23T16:53:54.247","","","","","","","","","","","","","","",""]
["S6-150126","[DRAFT] LS on media security for stateless Direct Mode Operation","Intel Mobile Communications","Saso Stojanovski",24932,"LS out","","Decision","Request to SA3 to check applicability of media security in stateless DMO environment.","","20","8.4","Security considerations",0,"withdrawn","2015-02-23T10:34:40.287","2015-02-23T16:53:54.123","","","","","","","","","",""]
["S6-150127","Resolution of an Editor's note in clause 5.1.2 (Off-Network MCPTT Service using ProSe UE-UE Relay)","Intel Mobile Communications","Saso Stojanovski",24932,"pCR","","Decision","As in the title.","","21","8.5","Architecture considerations",0,"revised","2015-02-23T10:40:23.757","2015-02-23T16:53:54.157","","S6-150166","","","","","","",null,"","","","","",""]
["S6-150128","Resolution of an Editor's note in clause 5.3.1 (ALG Relay for MCPTT UE to Network Relay)","Intel Mobile Communications","Saso Stojanovski",24932,"pCR","","Decision","As in the title.","","21","8.5","Architecture considerations",0,"noted","2015-02-23T10:41:53.223","2015-02-23T16:53:54.187","","","","","","","","",null,"","","","","",""]
["S6-150129","Resolution of Editor's notes in clause 5.8.1 (SIP-based service continuity between NMO and NMO-R)","Intel Mobile Communications","Saso Stojanovski",24932,"pCR","","Decision","As in the title.","","21","8.5","Architecture considerations",0,"approved","2015-02-23T10:43:44.683","2015-02-23T16:53:54.200","","","","","","","","",null,"","","","","",""]
["S6-150130","Registration and User Authentication Procedure Section 5.2.1","Motorola Solutions UK Ltd.","Dominic Lazara",49677,"pCR","","Decision","This document addresses the Editor’s Note in section 5.2.1.2. It proposes to add an information flow for solution 2-1— registration and user authentication with the MCPTT Service.","","21","8.5","Architecture considerations",0,"noted","2015-02-23T10:47:15.597","2015-02-23T15:40:31.257","","S6-150170","Rel-13","23.779","0.5.1","660054","","",null,"","","","","",""]
["S6-150131","Registration and User Authentication Procedure Section 5.2.3","Motorola Solutions UK Ltd.","Dominic Lazara",49677,"pCR","","Decision","This document addresses the Editor’s Note in section 5.2.3.2. It proposes to add an information flow for solution 2-3— registration and user authentication with the MCPTT Service.","","21","8.5","Architecture considerations",0,"revised","2015-02-23T10:49:58.350","2015-02-23T15:20:25.330","","S6-150169","Rel-13","23.779","0.5.1","660054","","",null,"","","","","",""]
["S6-150132","Considerations of DMO Floor Control in a Shared Resource Environment","General Dynamics UK Limited","Jonathan Brawn",61107,"pCR","","Decision","Abstract: RAN provides resources to the ProSe communication service on a shared resource basis and does not support resource reservation for groups or individuals. Because of this, some elements of Candidate Solution 6-1-1  are erronous. Two wording changes are proposed and two subjects are suggested for further study.","","24","9","Other MCPTT related issues (e.g. D2D)",0,"approved","2015-02-23T11:01:05.533","2015-02-23T17:31:21.087","","","Rel-13","23.779","0.5.1","","","",null,"","","","","",""]
["S6-150133","Business relationship for mutual aid","Alcatel-Lucent, Alcatel-Lucent Shanghai Bell","Keith Drage",720,"pCR","","Decision","Subclause 4.2.3 of 3GPP TR 23.779 was added at the last meeting but had a number of open issues. This contribution provides text to address the business relationship needed for mutual aid.","","18","8.2","MCPTT deployment scenarios",0,"revised","2015-02-23T11:10:59.563","2015-02-23T12:20:53.593","","S6-150161","Rel-13","23.779","0.5.1","660054","","",null,"","","","","",""]
["S6-150134","Example of application of business relationships","Alcatel-Lucent, Alcatel-Lucent Shanghai Bell","Keith Drage",720,"pCR","","Decision","In order to better understand the impact of the defined business relationships, an example of their application is proposed.","","18","8.2","MCPTT deployment scenarios",0,"revised","2015-02-23T11:13:43.630","2015-02-23T12:20:53.500","","S6-150162","Rel-13","23.779","0.5.1","660054","","",null,"","","","","",""]
["S6-150135","Overview of functional model principles","Alcatel-Lucent, Alcatel-Lucent Shanghai Bell","Keith Drage",720,"pCR","","Decision","Within the functional model, this proposal introduces the concept of planes as a component of the functional model, and the principle of the services used by planes or provided to other planes. It introduces the concept that identity and security can be provided entirely within each plane.","","15","7","Mission Critical Push To Talk over LTE (MCPTT) architecture - Functional review",0,"revised","2015-02-23T11:56:45.943","2015-02-23T12:20:53.530","","S6-150154","Rel-13","23.779","0.5.1","660054","","",null,"","","","","",""]
["S6-150136","Description of individual planes","Alcatel-Lucent, Alcatel-Lucent Shanghai Bell","Keith Drage",720,"pCR","","Decision","A new subclause is proposed that provides a description of the involved planes introduced by a companion contribution.","","15","7","Mission Critical Push To Talk over LTE (MCPTT) architecture - Functional review",0,"revised","2015-02-23T12:04:45.487","2015-02-23T12:20:53.547","","S6-150155","Rel-13","23.779","0.5.1","660054","","",null,"","","","","",""]
["S6-150137","Functional model","Alcatel-Lucent, Alcatel-Lucent Shanghai Bell","Keith Drage",720,"pCR","","Decision","A single functional model is presented applicable to all solutions.","","15","7","Mission Critical Push To Talk over LTE (MCPTT) architecture - Functional review",0,"revised","2015-02-23T12:14:52.327","2015-02-23T12:20:53.563","","S6-150157","Rel-13","23.779","0.5.1","660054","","",null,"","","","","",""]
["S6-150138","Other option to support private calls for MCPTT on network","Samsung","Sangsoo Jeong",45429,"draft TS","","Decision","","","23","8.7","Protocol considerations",0,"withdrawn","2015-02-23T12:29:24.993",null,"","","Rel-13","23.779","0.5.0","","","","","","","","","",""]
["S6-150139","Reference points","Alcatel-Lucent, Alcatel-Lucent Shanghai Bell","Keith Drage",720,"pCR","","Decision","This contribution proposes a new subclause entitled reference points within the functional model description. Content is not currently provided.","","15","7","Mission Critical Push To Talk over LTE (MCPTT) architecture - Functional review",0,"approved","2015-02-23T12:31:58.107","2015-02-23T13:12:35.950","","","Rel-13","23.779","","660054","","",null,"","","","","",""]
["S6-150140","Structure of information flows","Alcatel-Lucent, Alcatel-Lucent Shanghai Bell","Keith Drage",720,"pCR","","Decision",": It is proposed that the information flows are structured as for the breakdown into planes proposed in a companion contribution.\nWhile there will not necessarily be flow content for all the subclauses, they should all be included for completeness. For example the bearer plane subclause will probably just consist of a reference to 3GPP TS 23.401.","","21","8.5","Architecture considerations",0,"noted","2015-02-23T12:49:36.643","2015-02-23T13:12:35.903","","","Rel-13","23.779","0.5.1","660054","","",null,"","","","","",""]
["S6-150141","Supporting floor control for MCPTT on network","Samsung","Sangsoo Jeong",45429,"pCR","","Decision","","","23","8.7","Protocol considerations",0,"postponed","2015-02-23T12:57:48.917","2015-02-23T16:49:05.850","","S6-150193","Rel-13","23.779","0.5.0","","","",null,"","","","","",""]
["S6-150142","Other option to support private calls for MCPTT on network","Samsung","Sangsoo Jeong",45429,"pCR","","Decision","","","23","8.7","Protocol considerations",0,"postponed","2015-02-23T13:00:58.753","2015-02-23T16:49:05.897","","","Rel-13","23.779","0.5.0","","","",null,"","","","","",""]
["S6-150143","Reducing call setup time by using unicast mode","Samsung, KT Corp., SK Telecom, ITL Inc.","Sangsoo Jeong",45429,"pCR","","Decision","","","23","8.7","Protocol considerations",0,"postponed","2015-02-23T13:03:43.037","2015-02-23T16:49:05.947","","","Rel-13","23.779","0.5.0","","","",null,"","","","","",""]
["S6-150144","Supporting private call for MCPTT on network","Samsung, KT Corp., SK Telecom, ITL Inc.","Sangsoo Jeong",45429,"pCR","","Decision","","","23","8.7","Protocol considerations",0,"postponed","2015-02-23T13:04:54.610","2015-02-23T16:49:05.977","","S6-150192","Rel-13","23.779","0.5.0","","","",null,"","","","","",""]
["S6-150145","Supporting Group Call initiation for MCPTT on network","Samsung","Basavaraj Pattan",61285,"pCR","","Decision","","","23","8.7","Protocol considerations",0,"withdrawn","2015-02-23T13:06:22.080","2015-02-23T15:53:10.680","","S6-150189","Rel-13","23.779","0.5.0","","","",null,"","","","","",""]
["S6-150146","Call Commencement Modes for MCPTT - On Network","Samsung","Basavaraj Pattan",61285,"pCR","","Decision","","","23","8.7","Protocol considerations",0,"postponed","2015-02-23T13:07:28.987","2015-02-23T15:53:55.470","","","Rel-13","23.779","0.5.0","","","",null,"","","","","",""]
["S6-150147","Group Management (Search) for MCPTT - On Network","Samsung","Basavaraj Pattan",61285,"pCR","","Decision","","","23","8.7","Protocol considerations",0,"postponed","2015-02-23T13:08:17.893","2015-02-23T15:53:55.500","","S6-150191","Rel-13","23.779","0.5.0","","","",null,"","","","","",""]
["S6-150148","Architecture Support for Multi-network users - On Network","Samsung","Basavaraj Pattan",61285,"pCR","","Decision","","","23","8.7","Protocol considerations",0,"postponed","2015-02-23T13:09:06.097","2015-02-23T15:53:55.530","","","Rel-13","23.779","0.5.0","","","",null,"","","","","",""]
["S6-150149","Minimizing Call set up time for MCPTT calls - On Network","Samsung","Basavaraj Pattan",61285,"pCR","","Decision","","","23","8.7","Protocol considerations",0,"postponed","2015-02-23T13:09:51.167","2015-02-23T15:53:55.437","","","Rel-13","23.779","0.5.0","","","",null,"","","","","",""]
["S6-150150","Evaluation of solution 1-2: Off-Network MCPTT Service using ProSe UE-UE Relay","Alcatel-Lucent, Alcatel-Lucent Shanghai Bell","Keith Drage",720,"pCR","","Decision","A solution evaluation is provided for solution 1-2, and it is concluded that solution 1-2 should not be proceeded with.","","21","8.5","Architecture considerations",0,"revised","2015-02-23T13:10:04.177","2015-02-23T13:12:35.933","","S6-150152","Rel-13","23.779","0.5.1","660054","","",null,"","","","","",""]
["S6-150151","Working assumption for MCPTT baseline architecture","Samsung, Ericsson, Qualcomm, KT Corp., SK Telecom, LG Electronics, ITL Inc., LG UPlus","Sangsoo Jeong",45429,"other","","Decision","","","15","7","Mission Critical Push To Talk over LTE (MCPTT) architecture - Functional review",0,"noted","2015-02-23T16:34:37.913","2015-02-23T16:49:06.007","","","Rel-13","23.779","0.5.0","","","","","","","","","",""]
["S6-150152","Evaluation of solution 1-2: Off-Network MCPTT Service using ProSe UE-UE Relay","Alcatel-Lucent, Alcatel-Lucent Shanghai Bell","Keith Drage",720,"pCR","","Decision","A solution evaluation is provided for solution 1-2, and it is concluded that solution 1-2 should not be proceeded with.","","21","8.5","Architecture considerations",0,"postponed","2015-02-24T14:23:36.423","2015-02-24T16:16:52.160","S6-150150","","Rel-13","23.779","0.5.1","660054","","",null,"","","","","",""]
["S6-150153","Basic assumptions","BlackBerry UK Limited","Nick Russell",21192,"pCR","","Decision","In order to move discussions forward, some basic assumptions for the MCPTT architecture are proposed to be agreed, which it is believed can be agreed regardless of whether or not a SIP Core is IMS compliant.","","15","7","Mission Critical Push To Talk over LTE (MCPTT) architecture - Functional review",0,"revised","2015-02-25T13:32:13.453","2015-02-27T13:55:52.997","S6-150108","S6-150173","Rel-13","23.779","0.5.1","MCPTT","","",null,"","","","","",""]
["S6-150154","Overview of functional model principles","Alcatel-Lucent, Alcatel-Lucent Shanghai Bell","Keith Drage",720,"pCR","","Decision","Within the functional model, this proposal introduces the concept of planes as a component of the functional model, and the principle of the services used by planes or provided to other planes. It introduces the concept that identity and security can be provided entirely within each plane.","","15","7","Mission Critical Push To Talk over LTE (MCPTT) architecture - Functional review",0,"approved","2015-02-25T17:00:05.607","2015-02-27T12:54:19.823","S6-150135","","Rel-13","23.779","0.5.1","660054","","",null,"","","","","",""]
["S6-150155","Description of individual planes","Alcatel-Lucent Telecom Ltd, Alcatel-Lucent Shanghai Bell","Keith Drage",720,"pCR","","Decision","A new subclause is proposed that provides a description of the involved planes introduced by a companion contribution.","","15","7","Mission Critical Push To Talk over LTE (MCPTT) architecture - Functional review",0,"approved","2015-02-25T17:02:41.437","2015-02-27T12:54:19.853","S6-150136","","Rel-13","23.779","0.5.1","660054","","",null,"","","","","",""]
["S6-150156","Registration processing","Airbus Group SAS","Gérard Marque-Pucheu",51759,"pCR","","Decision","This contribution derives from the interoperability requirements between MCPTT systems the rules that shall be followed for the processing of MCPTT registration.","","15","7","Mission Critical Push To Talk over LTE (MCPTT) architecture - Functional review",0,"revised","2015-02-25T17:04:22.680","2015-02-27T10:23:53.303","S6-150116","S6-150172","Rel-13","23.779","0.5.1","660054","","",null,"","","","","",""]
["S6-150157","Functional model","Alcatel-Lucent Telecom Ltd, Alcatel-Lucent Shanghai Bell","Keith Drage",720,"pCR","","Decision","A single functional model is presented applicable to all solutions.","","15","7","Mission Critical Push To Talk over LTE (MCPTT) architecture - Functional review",0,"approved","2015-02-25T17:06:17.153","2015-02-27T12:54:19.887","S6-150137","","Rel-13","23.779","0.5.1","660054","","",null,"","","","","",""]
["S6-150158","Editorial and Minor Corrections to 23.779","OTD","Selvam Rengasami",31626,"pCR","","Decision","","","17","8.1","General discussion items",0,"approved","2015-02-25T17:08:41.967","2015-02-26T15:17:01.977","S6-150122","","Rel-13","23.779","0.5.1","","","",null,"","","","","",""]
["S6-150159","SA4 MCPTT WID updates for information","MCC","Bernt Mattsson",14585,"WID new","","Decision","","","27","11.1","Agreement of New / Revised WIDS",0,"noted","2015-02-25T18:21:10.483","2015-02-25T18:45:29.003","","","","","","","","","","","","","","",""]
["S6-150160","Presentation on drafting rules","Alcatel-Lucent Telecom Ltd","Keith Drage",720,"other","","Decision","","","29","12","AOB",0,"noted","2015-02-25T18:27:25.897","2015-02-26T14:57:43.317","","","","","","","","","","","","","","",""]
["S6-150161","Business relationship for mutual aid","Alcatel-Lucent Telecom Ltd, Alcatel-Lucent Shanghai Bell","Keith Drage",720,"pCR","","Decision","Subclause 4.2.3 of 3GPP TR 23.779 was added at the last meeting but had a number of open issues. This contribution provides text to address the business relationship needed for mutual aid.","","18","8.2","MCPTT deployment scenarios",0,"approved","2015-02-26T10:17:27.127","2015-02-27T10:25:17.827","S6-150133","","Rel-13","23.779","0.5.1","660054","","",null,"","","","","",""]
["S6-150162","Example of application of business relationships","Alcatel-Lucent Telecom Ltd, Alcatel-Lucent Shanghai Bell","Keith Drage",720,"pCR","","Decision","In order to better understand the impact of the defined business relationships, an example of their application is proposed.","","18","8.2","MCPTT deployment scenarios",0,"approved","2015-02-26T10:18:25.393","2015-02-27T10:30:23.537","S6-150134","","Rel-13","23.779","0.5.1","660054","","",null,"","","","","",""]
["S6-150163","Group call setup for MCPTT user in on network use","HUAWEI TECHNOLOGIES Co. Ltd., Hisilicon, TD-tech","Yizhuang Wu",61155,"pCR","","Decision","this contirbution gives an overview about the relationships among MCPTT user, MCPTT user’s Home MCPTT server and MCPTT user’s group home MCPTT server.And proposes a group call setup prosedure for MCPTT group user.","","21","8.5","Architecture considerations",0,"noted","2015-02-26T10:45:23.403","2015-02-27T13:56:29.177","S6-150106","","Rel-13","","","","","",null,"","","","","",""]
["S6-150164","SIP/IP Core Functions of MCPTT Application","HUAWEI TECHNOLOGIES Co. Ltd. ,Hisilicon, TD-Tech","Yizhuang Wu",61155,"pCR","","Decision","This contribution discusses the MCPTT SIP core architecture and core functions, which the selection of MCPTT SIP/IP core architecture would be based on.","","21","8.5","Architecture considerations",0,"noted","2015-02-26T13:45:27.687","2015-02-27T13:56:29.207","S6-150107","","Rel-13","","","","","",null,"","","","","",""]
["S6-150165","Minor enhancements and corrections to Solution 2-1","BlackBerry UK Limited","Nick Russell",21192,"pCR","","Decision","Proposes some moving and repartitioning of some text, new text for the evaluation section, and corrects some minor editorials.","","21","8.5","Architecture considerations",0,"approved","2015-02-26T13:46:50.087","2015-02-26T14:58:08.823","S6-150109","","Rel-13","23.779","0.5.1","MCPTT","","",null,"","","","","",""]
["S6-150166","Resolution of an Editor's note in clause 5.1.2 (Off-Network MCPTT Service using ProSe UE-UE Relay)","Intel Mobile Communications","Saso Stojanovski",24932,"pCR","","Decision","As in the title.","","21","8.5","Architecture considerations",0,"postponed","2015-02-26T14:03:55.380","2015-02-27T12:55:22.037","S6-150127","","","","","","","",null,"","","","","",""]
["S6-150167","Comments on 23.779","OTD","Selvam Rengasami",31626,"pCR","","Decision","","","17","8.1","General discussion items",0,"revised","2015-02-26T14:37:09.107","2015-02-26T15:17:58.527","","S6-150174","Rel-13","23.779","0.5.1","","","",null,"","","","","",""]
["S6-150168","Functional diagram and text proposal for section 6 (from drafting session)","Motorola Solutions UK Ltd.","Dominic Lazara",49677,"pCR","","Decision","","","15","7","Mission Critical Push To Talk over LTE (MCPTT) architecture - Functional review",0,"approved","2015-02-26T15:54:26.783","2015-02-27T12:55:22.067","","","","","","","","",null,"","","","","",""]
["S6-150169","Registration and User Authentication Procedure Section 5.2.3","Motorola Solutions UK Ltd.","Dominic Lazara",49677,"pCR","","Decision","This document addresses the Editor’s Note in section 5.2.3.2. It proposes to add an information flow for solution 2-3— registration and user authentication with the MCPTT Service.","","21","8.5","Architecture considerations",0,"noted","2015-02-26T15:55:54.207","2015-02-27T13:56:29.267","S6-150131","","Rel-13","23.779","0.5.1","660054","","",null,"","","","","",""]
["S6-150170","Registration and User Authentication Procedure Section 5.2.1","Motorola Solutions UK Ltd.","Dominic Lazara",49677,"pCR","","Decision","This document addresses the Editor’s Note in section 5.2.1.2. It proposes to add an information flow for solution 2-1— registration and user authentication with the MCPTT Service.","","21","8.5","Architecture considerations",0,"withdrawn","2015-02-26T16:04:22.953",null,"S6-150130","","Rel-13","23.779","0.5.1","660054","","",null,"","","","","",""]
["S6-150171","Assumptions on Service Continuity based on SA1 LS (S6-150112)","LG Electronics Inc.","Hyunsook Kim",42013,"pCR","","Decision","This paper considers the working assumptions on service continuity, based on SA1 reply LS (S6-150112)","","24","9","Other MCPTT related issues (e.g. D2D)",0,"approved","2015-02-27T14:42:48.577","2015-02-27T15:49:19.697","S6-150121","","Rel-13","","","660054","","",null,"","","","","",""]
["S6-150172","Registration processing","Airbus Group SAS","Gérard Marque-Pucheu",51759,"pCR","","Decision","This contribution derives from the interoperability requirements between MCPTT systems the rules that shall be followed for the processing of MCPTT registration.","","15","7","Mission Critical Push To Talk over LTE (MCPTT) architecture - Functional review",0,"approved","2015-02-27T14:44:05.657","2015-02-27T15:49:19.727","S6-150156","","Rel-13","23.779","0.5.1","660054","","",null,"","","","","",""]
["S6-150173","Basic assumptions","BlackBerry UK Limited","Nick Russell",21192,"pCR","","Decision","In order to move discussions forward, some basic assumptions for the MCPTT architecture are proposed to be agreed, which it is believed can be agreed regardless of whether or not a SIP Core is IMS compliant.","","15","7","Mission Critical Push To Talk over LTE (MCPTT) architecture - Functional review",0,"noted","2015-02-27T14:46:05.370","2015-02-27T15:49:19.760","S6-150153","S6-150215","Rel-13","23.779","0.5.1","MCPTT","","",null,"","","","","",""]
["S6-150174","Comments on 23.779","OTD","Selvam Rengasami",31626,"pCR","","Decision","","","17","8.1","General discussion items",0,"approved","2015-02-27T14:47:23.480","2015-02-27T14:47:51.343","S6-150167","","Rel-13","23.779","0.5.1","","","",null,"","","","","",""]

{"sheet":"CR_Packs_List","index":1,"n_rows":1,"n_cols":11,"rows_kept":1,"cut":false,"hidden":false,"merged":[]}
["CR Pack TDoc #","WG TDoc #","WG TDoc decision","CR Individual TSG decision","Spec #","CR #","CR revision #","CR category","Release","Version","CR title"]

{"sheet":"Parameters","index":2,"n_rows":24,"n_cols":4,"rows_kept":24,"cut":false,"hidden":true,"merged":[]}
["Types of Tdocs","Possible statuses of Tdocs","Categories"]
[]
["agenda","reserved","A","Decision"]
["Work Plan","available","B","Agreement"]
["LS in","revised","C","Approval"]
["LS out","agreed","D","Information"]
["pCR","conditionally agreed","E","Discussion"]
["draftCR","approved","F","Action"]
["CR","conditionally approved",null,"Endorsement"]
["CR pack","partially approved",null,"Presentation"]
["ToR","treated"]
["WID new","endorsed"]
["WID revised","replied to"]
["SID new","merged"]
["SID revised","not pursued"]
["WI status report","postponed"]
["WI exception request","noted"]
["TS or TR cover","not concluded"]
["draft TS","withdrawn"]
["draft TR","reissued"]
["report"]
["discussion"]
["response"]
["other"]