{"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":101,"n_cols":32,"rows_kept":101,"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"]
["S3i150248","Agenda","BT Group Plc","Alex Leadbeater",23753,"agenda","","","","","1","3","Approval of Agenda",0,"approved","2015-09-25T14:09:57.100","2015-10-05T18:41:19.070","","","","","","","","","","","","","","",""]
["S3i150249","Report from last meeting","BT Group Plc","Alex Leadbeater",23753,"report","","","","","2","4","Last meeting report SA3 LI#58",0,"approved","2015-09-25T14:11:12.230","2015-10-01T00:01:29.867","","","","","","","","","","","","","","",""]
["S3i150250","LI features and events with HLR for CS domain","Ministère Economie Indu. Numer","Pierre Courbon",52806,"CR","","","It is proposed to add new events and features related to HLR specially on interworking or any activities related to the target from CS access network or hybrid network with CS domain. Optional events and related information are included :\n•\tServing network\n•\tSubscriber record change \n•\tCancel Location\n•\tRegister Location\n•\tLocation information Request","","8","8.2","Release 12 & 13\t33.107 v12.11.0",0,"revised","2015-09-28T07:15:37.207","2015-09-30T07:24:37.317","","S3i150296","Rel-13","33.107","13.0.0","LI13","0182","","B",null,"","","","",""]
["S3i150251","Editorial modification of a comment in the ASN.1 field on “x 3GPP Asserted Identity”","Ministère Economie Indu. Numer","Pierre Courbon",52806,"CR","","","A wrong comment in one ASN.1 field related to XCAP may induce questions in the implementation of this standard.\nChange to “X 3GPP Asserted Identity” instead of “X 3GPP Intended Identity in Annexes B3 and B 9.","","10","9.2","Release 12 & 13  33.108 v12.9.0",0,"revised","2015-09-28T09:32:47.307","2015-09-28T09:39:36.307","","S3i150252","Rel-12","33.108","12.10.0","LI12","0279","","D",null,"","","","",""]
["S3i150252","Editorial modification of a comment in the ASN.1 field on “x 3GPP Asserted Identity”","Ministère Economie Indu. Numer","Pierre Courbon",52806,"CR","","","A wrong comment in one ASN.1 field related to XCAP may induce questions in the implementation of this standard.\nChange to “X 3GPP Asserted Identity” instead of “X 3GPP Intended Identity in Annexes B3 and B 9.","","10","9.2","Release 12 & 13  33.108 v12.9.0",0,"revised","2015-09-28T10:17:05.047","2015-09-28T10:22:59.073","S3i150251","S3i150309","Rel-12","33.108","12.10.0","LI12","0279","1","F",null,"","","","",""]
["S3i150253","Editorial corrections and clarifications","AQSACOM S.A.S.","Jean-Francois Zell",21411,"CR","","","Editorial corrections and clarifications related to:\n- §5.2.3 Delivery of IRI\n- §10.5.0 Introduction\n- §10.5.1.1 REPORT record information\n- Annex B.9 Intercept related information (HI2 SAE/EPS and IMS)","","10","9.2","Release 12 & 13  33.108 v12.9.0",0,"revised","2015-09-28T17:29:28.767","2015-09-29T13:22:47.533","","S3i150327","Rel-13","33.108","12.10.0","","0280","","F",null,"","","","",""]
["S3i150254","Reporting of UE local IP address and port","Ericsson LM, Orange","Maurizio Iovieno",23687,"CR","","","UE local IP address and port are added to the relevant events","","8","8.2","Release 12 & 13\t33.107 v12.11.0",0,"agreed","2015-09-29T07:42:53.323","2015-09-29T07:52:35.763","","","Rel-13","33.107","13.0.0","LI13","0183","","B","SP-150724","","","","",""]
["S3i150255","Reporting of UE local IP address and port","Ericsson LM, Orange","Maurizio Iovieno",23687,"CR","","","UE local IP address and port are added to the relevant IRI record","","10","9.2","Release 12 & 13  33.108 v12.9.0",0,"revised","2015-09-29T07:47:15.963","2015-09-29T07:53:17.667","","S3i150322","Rel-13","33.108","12.10.0","","0281","","B",null,"","","","",""]
["S3i150256","New LI events related to HSS in IMS, non 3GPP access network, 3GPP H(e)NBs, GBA and IMS-based VoIP.","Ministère Economie Indu. Numer","Pierre Courbon",52806,"CR","","","Some events and IRI related to HSS are proposed specially during interworking or any activities related to the target using an IMS network or non 3GPP access network or 3GPP H(e)NBs, GBA and IMS-based VoIP.\n\nOptional events and related information are included :\n•\tSubscriber record change \n•\tCancel location\n•\tRegistration termination\n•\tLocation information Request","","8","8.2","Release 12 & 13\t33.107 v12.11.0",0,"revised","2015-09-29T13:23:05.147","2015-09-29T13:26:59.707","","S3i150295","Rel-13","33.107","13.0.0","LI13","0184","","B",null,"","","","",""]
["S3i150257","CR to 33.106 to support LCS","Rogers Communications","Edward O'Leary",24518,"CR","","","Cr provides additional and clarifying  requirements when LCS is used","","6","7.2","Release 13\t33.106 v13.0.0",0,"revised","2015-09-29T19:25:04.040","2015-09-29T19:30:57.620","","S3i150258","Rel-13","33.106","13.1.0","","0147","","B",null,"","","","",""]
["S3i150258","CR to 33.106 to support LCS","Rogers Communications","Edward O'Leary",24518,"CR","","","Cr provides additional and clarifying  requirements when LCS is used , revised to include definition of Lawful Access Location Services","","6","7.2","Release 13\t33.106 v13.0.0",0,"revised","2015-09-29T19:47:52.767","2015-09-29T19:53:01.293","S3i150257","S3i150307","Rel-13","33.106","13.1.0","","0147","1","B",null,"","","","",""]
["S3i150259","ASN.1 Errors on B 3 and M2 annexes of TS 33.108","Ministère Economie Indu. Numer / THALES Communications & Security","Pierre Courbon",52806,"CR","","","Some ASN.1 definitions of Annex B3 and M2 of TS 33.108 cannot let a compiler to work. They cause a serious and frequent mis-operation. That's the main reason to propose Cat F corrections in frozen version 12.","","10","9.2","Release 12 & 13  33.108 v12.9.0",0,"revised","2015-09-30T07:40:06.167","2015-09-30T10:32:01.210","","S3i150260, S3i150280","Rel-12","33.108","12.10.0","LI12","0282","","F",null,"","","","",""]
["S3i150260","ASN.1 Errors on B 9 and M2 annexes of TS 33.108","Ministère Economie Indu. Numer / THALES Communications & Security","Pierre Courbon",52806,"CR","","","Some ASN.1 definitions of Annex B9 and M2 of TS 33.108 cannot let a compiler to work. They cause a serious and frequent mis-operation. That's the main reason to propose Cat F corrections in frozen version 12.","","10","9.2","Release 12 & 13  33.108 v12.9.0",0,"revised","2015-09-30T10:34:33.090","2015-09-30T10:42:37.360","S3i150259","","Rel-12","33.108","12.10.0","LI12","0282","1","F",null,"","","","",""]
["S3i150261","Discussion on LI for ProSe Remote UE via UE-NW Relay","Huawei Tech.(UK) Co., Ltd","Marcus Wong",40409,"discussion","","","This contribution explores possible LI option for ProSe remmte UE when it access the network via a ProSe UE-to-network Relay","","8","8.2","Release 12 & 13\t33.107 v12.11.0",0,"noted","2015-09-30T13:18:13.713","2015-09-30T18:48:54.230","","","Rel-13","","","","","","","","","","","",""]
["S3i150262","Reply LS to ETSI TC-LI on VoLTE Roaming Architecture","GSMA PACKET","Mirko Cano Soveri",41957,"LS in","","","","","4","6","Generic Incoming liaisons",0,"noted","2015-09-30T14:34:43.137","2015-09-30T14:44:40.987","","","","","","","","","",""]
["S3i150263","LTE FAQ Doc (TCLI output)","VODAFONE Group Plc","Gerald McQuaid",25351,"discussion","","","Output of LTE FAQ from TCLI","","11","10","Continued Discussion and New Business",0,"noted","2015-09-30T14:39:19.410","2015-10-01T14:12:20.263","","","","","","","","","","","","","","",""]
["S3i150264","LS on Security consideration on VoLTE S8HR","S3-151979","Mirko Cano Soveri",41957,"LS in","","","","","4","6","Generic Incoming liaisons",0,"noted","2015-09-30T14:40:50.107","2015-09-30T14:44:41.157","","","","","","","","","",""]
["S3i150265","Correlation Number parameter required for LTE","OTD","Selvam Rengasami",31626,"CR","","","The Correlation Number parameter is identified as being Conditional in LTE events reported to LE.  However, if this parameter is not reported, LE may not be able to correlate related LTE event messages.  Thus, this CR proposes changing the inclusion condition of this parameter to mandatory.","","10","9.2","Release 12 & 13  33.108 v12.9.0",0,"revised","2015-09-30T15:19:56.503","2015-09-30T16:25:41.057","","S3i150312","Rel-13","33.108","12.10.0","","0283","","C",null,"","","","",""]
["S3i150266","New LI events related to HLR for CS/Paquet domain Stage 3","Ministère Economie Indu. Numer","Pierre Courbon",52806,"CR","","","Some events and IRI related to HLR/HSS are proposed specially during roaming, interworking or any activities related to the target using CS /Paquet domains.\nOptional events and related information are included :\n•\tSubscriber record change \n•\tCancel location or Register Terminaison \n•\tRegister Location \n•\tLocation information Request","","10","9.2","Release 12 & 13  33.108 v12.9.0",0,"revised","2015-09-30T17:51:25.230","2015-09-30T17:54:52.960","","S3i150274","Rel-13","33.108","12.10.0","LI13","0284","","B",null,"","","","",""]
["S3i150267","Liaison Report: PTSC LAES","Nokia Networks","Nagaraja Rao",41611,"report","","","Brief report from the PTSC LAES","","3","5","Reports of other bodies which are relevant to SA3-LI",0,"noted","2015-09-30T20:43:29.780","2015-09-30T20:45:43.267","","","","","","","","","","","","","","",""]
["S3i150268","Correction to have consistant event name Packet Data Header Information","Nokia Networks","Nagaraja Rao",41611,"CR","","","The names “Packet Header Information Reporting” and “Packet Data Header Information” are used for the same event type.  The TS 33.108 uses the later. Besides, the event includes two types:   Packet Data Header Report and Packet Data Summary Report, which are referenced without the “Report” in TS 33.108.     \n\nAll references to Packet Header Information Reporting is changed to Packet Data Header Information with reporting added in a general sense rather than as a part of name.","","8","8.2","Release 12 & 13\t33.107 v12.11.0",0,"revised","2015-10-01T00:08:41.907","2015-10-01T00:13:38.290","","S3i150270","Rel-13","33.107","13.0.0","LI13","0185","","F",null,"","","","",""]
["S3i150269","Aligning Per-Packet and Summary Reporting ASN.1","OTD","Selvam Rengasami",31626,"CR","","","The ASN.1 for the per-packet reporting and summary reporting for Packet Header Information Reporting are not aligned.  The source and destination IP address and Protocol fields for the per-packet reporting should be required as they are for the summary reports.  This will also bring consistency with the Stage 2 requirements in 33.108.  Thus, this CR proposes changing the inclusion condition of this parameter to mandatory.","","10","9.2","Release 12 & 13  33.108 v12.9.0",0,"revised","2015-10-01T01:07:08.817","2015-10-01T01:12:00.253","","S3i150318","Rel-13","33.108","12.10.0","","0285","","F",null,"","","","",""]
["S3i150270","Correction to have consistant event name Packet Data Header Information","Nokia Networks","Nagaraja Rao",41611,"CR","","","The names “Packet Header Information Reporting” and “Packet Data Header Information” are used for the same event type.  The TS 33.108 uses the later. Besides, the event includes two types:   Packet Data Header Report and Packet Data Summary Report, which are referenced without the “Report” in TS 33.108.     \n\nAll references to Packet Header Information Reporting is changed to Packet Data Header Information with reporting added in a general sense rather than as a part of name.     \n\nThis revision includes the clause numbers in the cover sheet.","","8","8.2","Release 12 & 13\t33.107 v12.11.0",0,"revised","2015-10-01T01:15:47.480","2015-10-01T22:29:23.637","S3i150268","S3i150305","Rel-13","33.107","13.0.0","LI13","0185","1","F",null,"","","","",""]
["S3i150271","Correction to have consistant event name Packet Data Header Information (stage 3)","Nokia Networks","Nagaraja Rao",41611,"CR","","","Even though the name  “Packet Data Header Information” is used, at times, the event is named Packet Header Information Reporting. Also, the Packet Data Header Report and Packet Data Summary Report defined in TS 33.107 do not have the “Report” in some places.       \n\nAll references to Packet Header Information Reporting is changed to Packet Data Header Information with reporting added in a general sense rather than as a part of name.    “Report” is added to Packet Data Header and Packet Data Summary.","","10","9.2","Release 12 & 13  33.108 v12.9.0",0,"revised","2015-10-01T01:23:39.143","2015-10-01T22:29:43.400","","S3i150321","Rel-13","33.108","12.10.0","LI13","0286","","F",null,"","","","",""]
["S3i150272","Stage 3 definition for CC Unavailable Indication","Nokia Networks","Nagaraja Rao",41611,"CR","","","The stage 2 defintion (TS 33.107) specifies that in certain situations when the content is not available for an IMS-based VoIP call, the interception shall continue with IRI-only and shall send an indication to the LEMF that the content is not available. This document introduces the concept at a stage 3 level.        \n\nA new indication is added to the IMS events in order to have an ability for the IMS ICE to send an indication that in certain situations, the CC is not available.","","10","9.2","Release 12 & 13  33.108 v12.9.0",0,"revised","2015-10-01T01:27:16.403","2015-10-01T22:30:31.887","","S3i150320","Rel-13","33.108","12.10.0","LI13","0287","","B",null,"","","","",""]
["S3i150273","Call flow to illustrate the CC Unavailable case","Nokia Networks","Nagaraja Rao",41611,"CR","","","The stage 2 defintion (TS 33.107) specifies that in certain situations when the content is not available for an IMS-based VoIP call, the interception shall continue with IRI-only and shall send an indication to the LEMF that the content is not available. This document provides an informative call flow to illustrate that.","","8","8.2","Release 12 & 13\t33.107 v12.11.0",0,"revised","2015-10-01T01:30:08.830","2015-10-01T22:30:52.897","","S3i150306","Rel-13","33.107","13.0.0","LI13","0186","","C",null,"","","","",""]
["S3i150274","New LI events related to HLR for CS/Paquet domain Stage 3","Ministère Economie Indu. Numer","Pierre Courbon",52806,"CR","","","Some events and IRI related to HLR/HSS are proposed specially during roaming, interworking or any activities related to the target using CS /Paquet domains.\nOptional events and related information are included :\n•\tSubscriber record change \n•\tCancel location or Register Terminaison \n•\tRegister Location \n•\tLocation information Request","","10","9.2","Release 12 & 13  33.108 v12.9.0",0,"revised","2015-10-01T07:39:17.803","2015-10-01T16:35:35.007","S3i150266","S3i150281","Rel-13","33.108","12.10.0","LI13","0284","1","B",null,"","","","",""]
["S3i150275","Summary report ETSI TC-LI","PIDS","Koen Jaspers",9291,"other","","","Summary report ETSI TC-LI","","3","5","Reports of other bodies which are relevant to SA3-LI",0,"noted","2015-10-01T09:08:05.027","2015-10-04T08:47:55.497","","","","","","","","","","","","","","",""]
["S3i150276","Location Service","Rogers Communications","Edward O'Leary",24518,"discussion","","","Discussion paper on Location Services and the use of LCS,  resubmitted S3i150182 to further discuss LCS","","6","7.2","Release 13\t33.106 v13.0.0",0,"noted","2015-10-01T13:32:26.460","2015-10-05T14:11:24.813","S3i150182","","Rel-13","","","","","","","","","","","",""]
["S3i150277","Coding for Octet String Contents related to aPN","OTD","Selvam Rengasami",31626,"CR","","","In Annex B.9 of TS 33.108, in the parameter “GPRS-parameters”, there is a parameter called aPN which is of type OCTET STRING.  However, there is no coding defined for the contents of the OCTET STRING.  Decoding such a parameter is extremely difficult without knowing the coding of the contents.\nThus, this CR proposes adding comments identifying the coding to be used within this parameter.","","10","9.2","Release 12 & 13  33.108 v12.9.0",0,"revised","2015-10-01T21:19:03.177","2015-10-01T21:21:09.333","","S3i150319","Rel-13","33.108","12.10.0","","0288","","F",null,"","","","",""]
["S3i150278","Insertion of cal flow that was accidentally deleted","Nokia Networks","Nagaraja Rao",41611,"CR","","","","","8","8.2","Release 12 & 13\t33.107 v12.11.0",0,"revised","2015-10-01T22:25:54.473","2015-10-01T22:32:02.897","","S3i150294","Rel-13","33.107","13.0.0","LI13","0187","","D",null,"","","","",""]
["S3i150279","Discussion Paper: Overview of interception with RAVEL and S8HR","Nokia Networks","Nagaraja Rao",41611,"discussion","","","This discussion papers provides four diagrams showing examples of illustrating the LI implications in reference to the RAVEL and S8HR based approaches as roaming architecture for VoLTE. The purpose of this discussion paper is to have the same understanding on the two approaches from an LI perspective.","","11","10","Continued Discussion and New Business",0,"noted","2015-10-02T01:47:07.247","2015-10-02T01:49:14.977","","","","","","","","","","","","","","",""]
["S3i150280","ASN.1 Errors on B 3 and M2 annexes of TS 33.108","Ministère Economie Indu. Numer / THALES Communications & Security","Pierre Courbon",52806,"CR","","","Some ASN.1 definitions of Annex B3 and M2 of TS 33.108 cannot let a compiler to work. They cause a serious and frequent mis-operation. That's the main reason to propose Cat F corrections in frozen version 12.","","10","9.2","Release 12 & 13  33.108 v12.9.0",0,"revised","2015-10-02T17:48:38.887","2015-10-02T17:59:41.987","S3i150259","S3i150323","Rel-12","33.108","12.10.0","LI12","0282","2","F",null,"","","","",""]
["S3i150281","New LI events related to HLR for CS/Paquet domain Stage 3","Ministère Economie Indu. Numer","Pierre Courbon",52806,"CR","","","Some events and IRI related to HLR/HSS are proposed specially during roaming, interworking or any activities related to the target using CS /Paquet domains.\nOptional events and related information are included :\n•\tSubscriber record change \n•\tCancel location or Register Terminaison \n•\tRegister Location \n•\tLocation information Request","","10","9.2","Release 12 & 13  33.108 v12.9.0",0,"revised","2015-10-02T18:05:25.013","2015-10-02T18:13:02.607","S3i150274","S3i150326","Rel-13","33.108","12.10.0","LI13","0284","2","B",null,"","","","",""]
["S3i150282","WTSC LI summary report","AT&T GNS Belgium SPRL","Peter Musgrove",28558,"other","","","This document provides a brief summary report of the recent activities in ATIS WTSC LI.","","3","5","Reports of other bodies which are relevant to SA3-LI",0,"noted","2015-10-02T23:46:52.407","2015-10-02T23:56:55.843","","","","","","","","","","","","","","",""]
["S3i150283","S8HR P-CR proposing text for 4.1 assumptions","SPRINT Corporation, NTT Docomo","Greg Schumacher",35113,"pCR","","","","","11","10","Continued Discussion and New Business",0,"approved","2015-10-03T07:32:04.550","2015-10-03T07:47:31.730","","","Rel-13","","","","","",null,"","","","","",""]
["S3i150284","S8HR P-CR proposing text for 4.2 Architecture requirements","SPRINT Corporation, NTT Docomo","Greg Schumacher",35113,"pCR","","","","","11","10","Continued Discussion and New Business",0,"noted","2015-10-03T07:37:44.097","2015-10-03T07:47:31.917","","","Rel-13","","","","","",null,"","","","","",""]
["S3i150285","S8HR P-CR proposing text for 4.2 Architecture","SPRINT Corporation, NTT Docomo","Greg Schumacher",35113,"pCR","","","","","11","10","Continued Discussion and New Business",0,"revised","2015-10-03T07:42:39.747","2015-10-03T07:47:31.513","","S3i150341","Rel-13","","","","","",null,"","","","","",""]
["S3i150286","P-CR proposing editorials LIV-8 study","NTT DOCOMO INC.","Alf Zugenmaier",52494,"pCR","","","Add references to scope, add reference to SA2 study, refer to SA2 study for definitions and abbreviations defined there.","","11","10","Continued Discussion and New Business",0,"approved","2015-10-03T10:12:38.003","2015-10-03T13:37:49.283","","","Rel-14","","","","","",null,"","","","","",""]
["S3i150287","P-CR on LIV-8 study  for GTP selection criteria","NTT DOCOMO INC.","Alf Zugenmaier",52494,"pCR","","","Proposes a description and a solution for the key issue number #3.","","11","10","Continued Discussion and New Business",0,"revised","2015-10-03T13:06:38.277","2015-10-03T13:37:49.470","","S3i150347","Rel-14","","","","","",null,"","","","","",""]
["S3i150288","P-CR on implicit registrations for LIV-8 study","NTT DOCOMO INC.","Alf Zugenmaier",52494,"pCR","","","Proposes a description and a solution for implicit registrations by LMISF extracting the implicitly registered identities form the registration OK messages.","","11","10","Continued Discussion and New Business",0,"approved","2015-10-03T13:21:19.687","2015-10-03T13:37:49.673","","","Rel-14","","","","","",null,"","","","","",""]
["S3i150289","P-CR on intra-access handover for LIV-8 study","NTT DOCOMO INC.","Alf Zugenmaier",52494,"pCR","","","Proposes architectural requirements for intra-access handovers.","","11","10","Continued Discussion and New Business",0,"revised","2015-10-03T13:34:46.217","2015-10-03T13:37:49.923","","S3i150346","Rel-14","","","","","",null,"","","","","",""]
["S3i150290","Delivery of Messaging Services to LE separate from other services","OTD","Selvam Rengasami",31626,"CR","","","National requirements may require that Messaging Services be delivered separate from other services.  This CR provides modifications to 33.108 to meet this requirement.","","10","9.2","Release 12 & 13  33.108 v12.9.0",0,"noted","2015-10-05T04:30:24.740","2015-10-05T04:32:59.897","","","Rel-13","33.108","12.10.0","","0289","","B",null,"","","","",""]
["S3i150291","LTE Location Information: Cell Based IRI Reporting (MME)","TELEFONICA S.A.","Martin Kissel",46160,"CR","","","Cell based location information is updated available in MME on NAS Service Request, X2-based Handover and S1-based Handover and therefor should be made available in REPORT records.","","8","8.2","Release 12 & 13\t33.107 v12.11.0",0,"withdrawn","2015-10-05T20:06:04.823","2015-10-05T20:24:33.790","","","Rel-13","33.107","13.0.0","LI13","0188","","B",null,"","","","",""]
["S3i150292","LTE Location Information: Cell Based IRI Reporting (MME) 33.108","TELEFONICA S.A.","Martin Kissel",46160,"CR","","","Cell based location information is updated available in MME on UE triggered Service Request, X2-based handover and S1-based handover and therefor should be made available in REPORT records.","","10","9.2","Release 12 & 13  33.108 v12.9.0",0,"revised","2015-10-05T20:37:18.340","2015-10-05T20:40:20.580","","S3i150293","Rel-13","33.108","12.10.0","LI13","0290","","B",null,"","","","",""]
["S3i150293","LTE Location Information: Cell Based IRI Reporting (MME) 33.108","TELEFONICA S.A.","Martin Kissel",46160,"CR","","","Cell based location information is updated available in MME on UE triggered Service Request, X2-based handover and S1-based handover and therefor should be made available in REPORT records.","","10","9.2","Release 12 & 13  33.108 v12.9.0",0,"withdrawn","2015-10-05T21:13:45.213","2015-10-05T21:15:26.533","S3i150292","","Rel-13","33.108","12.10.0","LI13","0290","1","B",null,"","","","",""]
["S3i150294","Insertion of call flow that was accidentally deleted","Nokia Networks","Nagaraja Rao",41611,"CR","","","The call flow in Figure F.8 was accidentally deleted by the MCC in the latest version of 3GPP TS 33.107. This CR re-introduces that call flow.      In addition this CR clarifies the Note in Annex E.11.       \n\nAdds the call flow back.  Change to the Note in E.11 is  corrected.","","8","8.2","Release 12 & 13\t33.107 v12.11.0",0,"agreed","2015-10-05T23:02:50.977","2015-10-05T23:06:12.263","S3i150278","","Rel-13","33.107","13.0.0","LI13","0187","1","F","SP-150724","","","","",""]
["S3i150295","New LI events related to HSS in IMS, non 3GPP access network, 3GPP H(e)NBs, GBA and IMS-based VoIP.","Ministère Economie Indu. Numer","Pierre Courbon",52806,"CR","","","Some events and IRI related to HSS are proposed specially during interworking or any activities related to the target using an IMS network or non 3GPP access network or 3GPP H(e)NBs, GBA and IMS-based VoIP.\n\nOptional events and related information are included :\n•\tSubscriber record change \n•\tCancel location\n•\tRegistration termination\n•\tLocation information Request","","8","8.2","Release 12 & 13\t33.107 v12.11.0",0,"revised","2015-10-06T03:44:54.650",null,"S3i150256","S3i150325","Rel-13","33.107","13.0.0","LI13","0184","1","B",null,"","","","",""]
["S3i150296","LI features and events with HLR for CS domain","Ministère Economie Indu. Numer","Pierre Courbon",52806,"CR","","","It is proposed to add new events and features related to HLR specially on interworking or any activities related to the target from CS access network or hybrid network with CS domain. Optional events and related information are included :\n•\tServing network\n•\tSubscriber record change \n•\tCancel Location\n•\tRegister Location\n•\tLocation information Request","","8","8.2","Release 12 & 13\t33.107 v12.11.0",0,"agreed","2015-10-06T03:49:24.247","2015-10-06T22:16:48.610","S3i150250","","Rel-13","33.107","13.0.0","LI13","0182","1","B","SP-150724","","","","",""]
["S3i150297","LTE Location Information: Cell Based IRI Reporting (MME) 33.107 R10","TELEFONICA S.A.","Martin Kissel",46160,"CR","","","","","7","8.1","Release 11\t33.107 v11.5.0",0,"revised","2015-10-06T06:45:56.047","2015-10-06T13:16:46.317","","S3i150310","Rel-10","33.107","10.4.0","LI10","0189","","F",null,"","","","",""]
["S3i150298","LTE Location Information: Cell Based IRI Reporting (MME) 33.107 R11","TELEFONICA S.A.","Martin Kissel",46160,"CR","","","","","7","8.1","Release 11\t33.107 v11.5.0",0,"revised","2015-10-06T06:50:46.987","2015-10-06T13:16:46.487","","S3i150311","Rel-11","33.107","11.5.0","","0190","","A",null,"","","","",""]
["S3i150299","LTE Location Information: Cell Based IRI Reporting (MME) 33.107 R12","TELEFONICA S.A.","Martin Kissel",46160,"CR","","","","","8","8.2","Release 12 & 13\t33.107 v12.11.0",0,"revised","2015-10-06T06:53:19.567","2015-10-06T13:16:46.660","","S3i150313","Rel-12","33.107","12.12.0","","0191","","A",null,"","","","",""]
["S3i150300","LTE Location Information: Cell Based IRI Reporting (MME) 33.107 R13","TELEFONICA S.A.","Martin Kissel",46160,"CR","","","","","8","8.2","Release 12 & 13\t33.107 v12.11.0",0,"revised","2015-10-06T06:55:27.597","2015-10-06T13:16:46.847","","S3i150314","Rel-13","33.107","13.0.0","","0192","","A",null,"","","","",""]
["S3i150301","LTE Location Information: Cell Based IRI Reporting (MME) 33.108 R10","TELEFONICA S.A.","Martin Kissel",46160,"CR","","","","","9","9.1","Release 11   33.108 v11.6.0 and Earlier",0,"revised","2015-10-06T07:32:11.987","2015-10-06T13:16:47.033","","S3i150315","Rel-10","33.108","10.6.0","LI10","0291","","F",null,"","","","",""]
["S3i150302","LTE Location Information: Cell Based IRI Reporting (MME) 33.108 R11","TELEFONICA S.A.","Martin Kissel",46160,"CR","","","","","9","9.1","Release 11   33.108 v11.6.0 and Earlier",0,"revised","2015-10-06T07:34:07.973","2015-10-06T13:16:47.207","","S3i150316","Rel-11","33.108","11.6.0","","0292","","A",null,"","","","",""]
["S3i150303","LTE Location Information: Cell Based IRI Reporting (MME) 33.108 R12","TELEFONICA S.A.","Martin Kissel",46160,"CR","","","","","10","9.2","Release 12 & 13  33.108 v12.9.0",0,"revised","2015-10-06T07:35:08.500","2015-10-06T13:16:47.377","","S3i150317","Rel-12","33.108","12.10.0","","0293","","A",null,"","","","",""]
["S3i150304","Reply LS to Incoming liaison “GSMA LS on ePDG selection” S3i150210","Ministère Economie Indu. Numer","Pierre Courbon",52806,"LS out","","","3GPP SA3-LI would like to thank GSMA NG RILTE for the LS to 3GPP SA3-LI on ePDG Selection, about questions introduced by IR.51 and 3GPP TS 23.402 (section 7.2.1 for ePDG discovery). \nThe NG RILTE’s understanding is that according to TS 24.302, in roaming scenarios in which the UE knows the identity of the VPLMN, the UE first attempts to derive the FQDN for ePDG address from the visited PLMN ID and to connect with ePDG in visited network, and only attempts to connect with the ePDG of the HPLMN as the option of last resort.\nNG RILTE highlighted that in certain VoWiFi deployment scenarios the preference of the home operator might be that the UE should connect to the ePDG in home network also when roaming. Possible such scenarios include, for instance, when visited networks have not deployed VoWiFi yet, there is no S2b layer roaming agreement with visited networks, or not enough interoperability testing.","","16","13","Outgoing Liaisons",0,"revised","2015-10-06T11:35:39.127","2015-10-06T21:42:22.443","","S3i150340","Rel-13","","","","","","","","S3i150210","GSMA NG RILTE, 3GPP SA2, 3GPP CT1","ETSI TC LI"]
["S3i150305","Correction to have consistant event name Packet Data Header Information","Nokia Networks","Nagaraja Rao",41611,"CR","","","The names “Packet Header Information Reporting” and “Packet Data Header Information” are used for the same event type.  The TS 33.108 uses the later. Besides, the event includes two types:   Packet Data Header Report and Packet Data Summary Report, which are referenced without the “Report” in TS 33.108.     \n\nAll references to Packet Header Information Reporting is changed to Packet Data Header Information with reporting added in a general sense rather than as a part of name.     \n\nThis revision includes the clause numbers in the cover sheet.","","8","8.2","Release 12 & 13\t33.107 v12.11.0",0,"revised","2015-10-06T14:29:17.113","2015-10-06T14:39:13.857","S3i150270","S3i150308","Rel-13","33.107","13.0.0","LI13","0185","2","F",null,"","","","",""]
["S3i150306","Call flow to illustrate the CC Unavailable case","Nokia Networks","Nagaraja Rao",41611,"CR","","","The stage 2 defintion (TS 33.107) specifies that in certain situations when the content is not available for an IMS-based VoIP call, the interception shall continue with IRI-only and shall send an indication to the LEMF that the content is not available. This document provides an informative call flow to illustrate that.","","8","8.2","Release 12 & 13\t33.107 v12.11.0",0,"agreed","2015-10-06T14:30:52.757","2015-10-06T14:39:28.940","S3i150273","","Rel-13","33.107","13.0.0","LI13","0186","1","B","SP-150724","","","","",""]
["S3i150307","CR to 33.106 to support LCS","Rogers Communications","Edward O'Leary",24518,"CR","","","Cr provides additional and clarifying  requirements when LCS is used , revised to include definition of\n Lawful Access Location Services, revised as per meeting discussion","","6","7.2","Release 13\t33.106 v13.0.0",0,"revised","2015-10-06T14:38:43.687","2015-10-07T11:13:50.267","S3i150258","S3i150331","Rel-13","33.106","13.1.0","","0147","2","B",null,"","","","",""]
["S3i150308","Correction to have consistant event name Packet Data Header Information","Nokia Networks","Nagaraja Rao",41611,"CR","","","The names “Packet Header Information Reporting” and “Packet Data Header Information” are used for the same event type.  The TS 33.108 uses the later. Besides, the event includes two types:   Packet Data Header Report and Packet Data Summary Report, which are referenced without the “Report” in TS 33.108.     \n\nAll references to Packet Header Information Reporting is changed to Packet Data Header Information with reporting added in a general sense rather than as a part of name.     \n\nThis revision includes the clause numbers in the cover sheet.","","8","8.2","Release 12 & 13\t33.107 v12.11.0",0,"agreed","2015-10-06T14:48:42.127","2015-10-06T14:50:33.543","S3i150305","","Rel-13","33.107","13.0.0","LI13","0185","3","F","SP-150724","","","","",""]
["S3i150309","Modification related to ASN.1 field on “x 3GPP Asserted Identity”","Ministère Economie Indu. Numer","Pierre Courbon",52806,"CR","","","One ASN.1 field related to XCAP is incorrectly defined, therefore cannot be implemented.\nChange to “X 3GPP Asserted Identity” instead of “X 3GPP Intended Identity in Annexes B.3 and B.9.","","10","9.2","Release 12 & 13  33.108 v12.9.0",0,"agreed","2015-10-06T15:37:08.360","2015-10-06T15:48:19.263","S3i150252","","Rel-12","33.108","12.10.0","LI12","0279","2","F","SP-150723","","","","",""]
["S3i150310","LTE Location Information: Cell Based IRI Reporting (MME) 33.107 R10","TELEFONICA S.A.","Martin Kissel",46160,"CR","","","","","7","8.1","Release 11\t33.107 v11.5.0",0,"agreed","2015-10-06T16:25:22.250","2015-10-06T19:20:00.920","S3i150297","","Rel-10","33.107","10.4.0","LI10","0189","1","F","SP-150728","","","","",""]
["S3i150311","LTE Location Information: Cell Based IRI Reporting (MME) 33.107 R11","TELEFONICA S.A.","Martin Kissel",46160,"CR","","","","","7","8.1","Release 11\t33.107 v11.5.0",0,"agreed","2015-10-06T16:29:44.030","2015-10-06T19:20:01.093","S3i150298","","Rel-11","33.107","11.5.0","LI10","0190","1","A","SP-150728","","","","",""]
["S3i150312","Correlation Number parameter required for LTE","OTD","Selvam Rengasami",31626,"CR","","","The Correlation Number parameter is identified as being Conditional in LTE events reported to LE.  However, if this parameter is not reported, LE may not be able to correlate related LTE event messages.  Thus, this CR proposes changing the inclusion condition of this parameter to mandatory.","","10","9.2","Release 12 & 13  33.108 v12.9.0",0,"agreed","2015-10-06T16:30:41.097","2015-10-06T16:36:08.427","S3i150265","","Rel-12","33.108","12.10.0","LI12","0283","1","F","SP-150723","","","","",""]
["S3i150313","LTE Location Information: Cell Based IRI Reporting (MME) 33.107 R12","TELEFONICA S.A.","Martin Kissel",46160,"CR","","","","","8","8.2","Release 12 & 13\t33.107 v12.11.0",0,"agreed","2015-10-06T16:31:02.607","2015-10-06T19:20:01.280","S3i150299","","Rel-12","33.107","12.12.0","LI10","0191","1","A","SP-150728","","","","",""]
["S3i150314","LTE Location Information: Cell Based IRI Reporting (MME) 33.107 R13","TELEFONICA S.A.","Martin Kissel",46160,"CR","","","","","8","8.2","Release 12 & 13\t33.107 v12.11.0",0,"agreed","2015-10-06T16:32:04.027","2015-10-06T19:20:01.467","S3i150300","","Rel-13","33.107","13.0.0","LI10","0192","1","A","SP-150728","","","","",""]
["S3i150315","LTE Location Information: Cell Based IRI Reporting (MME) 33.108 R10","TELEFONICA S.A.","Martin Kissel",46160,"CR","","","","","9","9.1","Release 11   33.108 v11.6.0 and Earlier",0,"agreed","2015-10-06T16:33:19.917","2015-10-06T19:20:01.670","S3i150301","","Rel-10","33.108","10.6.0","LI10","0291","1","F","SP-150728","","","","",""]
["S3i150316","LTE Location Information: Cell Based IRI Reporting (MME) 33.108 R11","TELEFONICA S.A.","Martin Kissel",46160,"CR","","","","","9","9.1","Release 11   33.108 v11.6.0 and Earlier",0,"agreed","2015-10-06T16:34:35.890","2015-10-06T19:20:01.857","S3i150302","","Rel-11","33.108","11.6.0","LI10","0292","1","A","SP-150728","","","","",""]
["S3i150317","LTE Location Information: Cell Based IRI Reporting (MME) 33.108 R12","TELEFONICA S.A.","Martin Kissel",46160,"CR","","","","","10","9.2","Release 12 & 13  33.108 v12.9.0",0,"agreed","2015-10-06T16:35:39.070","2015-10-06T19:20:02.060","S3i150303","","Rel-12","33.108","12.10.0","LI10","0293","1","A","SP-150728","","","","",""]
["S3i150318","Aligning Per-Packet and Summary Reporting ASN.1","OTD","Selvam Rengasami",31626,"CR","","","The ASN.1 for the per-packet reporting and summary reporting for Packet Header Information Reporting are not aligned.  The source and destination IP address and Protocol fields for the per-packet reporting should be required as they are for the summary reports.  This will also bring consistency with the Stage 2 requirements.  Thus, this CR proposes changing the inclusion condition of this parameter to mandatory.","","10","9.2","Release 12 & 13  33.108 v12.9.0",0,"agreed","2015-10-06T17:24:49.167","2015-10-06T17:28:08.517","S3i150269","","Rel-12","33.108","12.10.0","LI12","0285","1","F","SP-150723","","","","",""]
["S3i150319","Coding for Octet String Contents related to aPN","OTD","Selvam Rengasami",31626,"CR","","","In Annex B.9 of TS 33.108, in the parameter “GPRS-parameters”, there is a parameter called aPN which is of type OCTET STRING.  However, there is no coding defined for the contents of the OCTET STRING.  Decoding such a parameter is extremely difficult without knowing the coding of the contents.\nThus, this CR proposes adding comments identifying the coding to be used within this parameter.","","10","9.2","Release 12 & 13  33.108 v12.9.0",0,"revised","2015-10-06T17:45:26.643","2015-10-06T17:47:14.360","S3i150277","S3i150324","Rel-12","33.108","12.10.0","","0288","1","F",null,"","","","",""]
["S3i150320","Stage 3 definition for CC Unavailable Indication","Nokia Networks","Nagaraja Rao",41611,"CR","","","The stage 2 defintion (TS 33.107) specifies that in certain situations when the content is not available for an IMS-based VoIP call, the interception shall continue with IRI-only and shall send an indication to the LEMF that the content is not available. This document introduces the concept at a stage 3 level.        \n\nA new indication is added to the IMS events in order to have an ability for the IMS ICE to send an indication that in certain situations, the CC is not available.","","10","9.2","Release 12 & 13  33.108 v12.9.0",0,"revised","2015-10-06T18:42:38.153","2015-10-06T19:20:20.670","S3i150272","S3i150337","Rel-13","33.108","12.10.0","LI13","0287","1","B",null,"","","","",""]
["S3i150321","Correction to have consistant event name Packet Data Header Information (stage 3)","Nokia Networks","Nagaraja Rao",41611,"CR","","","Even though the name  “Packet Data Header Information” is used, at times, the event is named Packet Header Information Reporting. Also, the Packet Data Header Report and Packet Data Summary Report defined in TS 33.107 do not have the “Report” in some places.       \n\nAll references to Packet Header Information Reporting is changed to Packet Data Header Information with reporting added in a general sense rather than as a part of name.    “Report” is added to Packet Data Header and Packet Data Summary.","","10","9.2","Release 12 & 13  33.108 v12.9.0",0,"agreed","2015-10-06T18:43:58.447","2015-10-06T19:20:36.363","S3i150271","","Rel-13","33.108","12.10.0","LI13","0286","1","F","SP-150724","","","","",""]
["S3i150322","Reporting of UE local IP address and port","Ericsson LM, Orange","Maurizio Iovieno",23687,"CR","","","UE local IP address and port are added to the relevant IRI record","","10","9.2","Release 12 & 13  33.108 v12.9.0",0,"revised","2015-10-06T21:16:45.527","2015-10-06T23:52:50.790","S3i150255","S3i150330","Rel-13","33.108","12.10.0","","0281","1","F",null,"","","","",""]
["S3i150323","ASN.1 Errors on B 3 and M2 annexes of TS 33.108","Ministère Economie Indu. Numer / THALES Communications & Security","Pierre Courbon",52806,"CR","","","Some ASN.1 definitions of Annex B3 and M2 of TS 33.108 cannot let a compiler to work. They cause a serious and frequent mis-operation. That's the main reason to propose Cat F corrections in frozen version 12.","","10","9.2","Release 12 & 13  33.108 v12.9.0",0,"revised","2015-10-06T21:21:13.033","2015-10-06T21:24:11.200","S3i150280","S3i150328","Rel-12","33.108","12.10.0","LI12","0282","3","F",null,"","","","",""]
["S3i150324","Coding for Octet String Contents related to aPN","OTD","Selvam Rengasami",31626,"CR","","","In Annex B.9 of TS 33.108, in the parameter “GPRS-parameters”, there is a parameter called aPN which is of type OCTET STRING.  However, there is no coding defined for the contents of the OCTET STRING.  Decoding such a parameter is extremely difficult without knowing the coding of the contents.\nThus, this CR proposes adding comments identifying the coding to be used within this parameter.","","10","9.2","Release 12 & 13  33.108 v12.9.0",0,"agreed","2015-10-06T21:25:22.677","2015-10-06T21:27:00.800","S3i150319","","Rel-12","33.108","12.10.0","LI12","0288","2","F","SP-150723","","","","",""]
["S3i150325","New LI events related to HSS in IMS, non 3GPP access network, 3GPP H(e)NBs, GBA and IMS-based VoIP.","Ministère Economie Indu. Numer","Pierre Courbon",52806,"CR","","","Some events and IRI related to HSS are proposed specially during interworking or any activities related to the target using an IMS network or non 3GPP access network or 3GPP H(e)NBs, GBA and IMS-based VoIP.\n\nOptional events and related information are included :\n•\tSubscriber record change \n•\tCancel location\n•\tRegistration termination\n•\tLocation information Request","","8","8.2","Release 12 & 13\t33.107 v12.11.0",0,"revised","2015-10-06T21:27:20.863","2015-10-06T21:33:33.840","S3i150295","S3i150332","Rel-13","33.107","13.0.0","LI13","0184","2","B",null,"","","","",""]
["S3i150326","New LI events related to HLR for CS/PS domain Stage 3","Ministère Economie Indu. Numer","Pierre Courbon",52806,"CR","","","Some events and IRI related to HLR/HSS are proposed specially during roaming, interworking or any activities related to the target using CS /Paquet domains.\nOptional events and related information are included :\n•\tSubscriber record change \n•\tCancel location or Register Terminaison \n•\tRegister Location \n•\tLocation information Request","","10","9.2","Release 12 & 13  33.108 v12.9.0",0,"revised","2015-10-06T21:35:13.487","2015-10-06T21:38:38.583","S3i150281","S3i150329","Rel-13","33.108","12.10.0","LI13","0284","3","B",null,"","","","",""]
["S3i150327","Fixing ASN.1 field","AQSACOM S.A.S.","Jean-Francois Zell",21411,"CR","","","Correction of pDNAddressAllocation into pDNType","","10","9.2","Release 12 & 13  33.108 v12.9.0",0,"revised","2015-10-06T22:28:02.227","2015-10-06T22:39:35.877","S3i150253","S3i150335, S3i150336","Rel-13","33.108","12.10.0","","0280","1","F",null,"","","","",""]
["S3i150328","ASN.1 Errors on B.3 and M.2 annexes of TS 33.108","Ministère Economie Indu. Numer / THALES Communications & Security","Pierre Courbon",52806,"CR","","","Some ASN.1 definitions of Annexes B.3 and M.2 of TS 33.108 cannot let a compiler to work. They cause a serious and frequent mis-operation. That's the main reason to propose Cat F corrections in frozen version 12.","","10","9.2","Release 12 & 13  33.108 v12.9.0",0,"agreed","2015-10-06T23:08:59.040","2015-10-06T23:12:44.693","S3i150323","","Rel-12","33.108","12.10.0","LI12","0282","4","F","SP-150723","","","","",""]
["S3i150329","New LI events related to HLR for CS/PS domain Stage 3","Ministère Economie Indu. Numer","Pierre Courbon",52806,"CR","","","Some events and IRI related to HLR/HSS are proposed specially during roaming, interworking or any activities related to the target using CS /Paquet domains.\nOptional events and related information are included :\n•\tSubscriber record change \n•\tCancel location or Register Terminaison \n•\tRegister Location \n•\tLocation information Request","","10","9.2","Release 12 & 13  33.108 v12.9.0",0,"revised","2015-10-06T23:14:40.803","2015-10-06T23:17:45.070","S3i150326","S3i150333","Rel-13","33.108","12.10.0","LI13","0284","4","B",null,"","","","",""]
["S3i150330","Reporting of UE local IP address and UDP port number","Ericsson LM, Orange","Maurizio Iovieno",23687,"CR","","","","","10","9.2","Release 12 & 13  33.108 v12.9.0",0,"agreed","2015-10-06T23:57:11.137","2015-10-07T00:00:09.523","S3i150322","","Rel-13","33.108","12.10.0","LI13","0281","2","F","SP-150724","","","","",""]
["S3i150331","CR to 33.106 to support LCS","Rogers Communications","Edward O'Leary",24518,"CR","","","Cr provides additional and clarifying  requirements when LCS is used , revised to include definition of\n Lawful Access Location Services, revised as per meeting discussion","","6","7.2","Release 13\t33.106 v13.0.0",0,"revised","2015-10-07T14:17:40.333","2015-10-07T14:22:50.863","S3i150307","S3i150334","Rel-13","33.106","13.1.0","","0147","3","B",null,"","","","",""]
["S3i150332","New LI events related to HSS in IMS, non 3GPP access network, 3GPP H(e)NBs, GBA and IMS-based VoIP.","Ministère Economie Indu. Numer","Pierre Courbon",52806,"CR","","","Some events and IRI related to HSS are proposed specially during interworking or any activities related to the target using an IMS network or non 3GPP access network or 3GPP H(e)NBs, GBA and IMS-based VoIP.\n\nOptional events and related information are included :\n•\tSubscriber record change \n•\tCancel location\n•\tRegistration termination\n•\tLocation information Request","","8","8.2","Release 12 & 13\t33.107 v12.11.0",0,"revised","2015-10-07T14:57:43.327","2015-10-07T15:02:01.800","S3i150325","S3i150338","Rel-13","33.107","13.0.0","LI13","0184","3","B",null,"","","","",""]
["S3i150333","New LI events related to HLR for CS/PS domain Stage 3","Ministère Economie Indu. Numer","Pierre Courbon",52806,"CR","","","Some events and IRI related to HLR/HSS are proposed specially during roaming, interworking or any activities related to the target using CS /Paquet domains.\nOptional events and related information are included :\n•\tSubscriber record change \n•\tCancel location or Register Terminaison \n•\tRegister Location \n•\tLocation information Request","","10","9.2","Release 12 & 13  33.108 v12.9.0",0,"agreed","2015-10-07T15:04:04.463","2015-10-07T15:08:15.200","S3i150329","","Rel-13","33.108","12.10.0","LI13","0284","5","B","SP-150724","","","","",""]
["S3i150334","CR to 33.106 to support LCS","Rogers Communications","Edward O'Leary",24518,"CR","","","Cr provides additional and clarifying  requirements when LCS is used , revised to include definition of\n Lawful Access Location Services, revised as per meeting discussion","","6","7.2","Release 13\t33.106 v13.0.0",0,"revised","2015-10-07T15:55:21.113","2015-10-07T16:40:44.107","S3i150331","S3i150339","Rel-13","33.106","13.1.0","","0147","4","B",null,"","","","",""]
["S3i150335","Fixing ASN.1 field","AQSACOM S.A.S.","Pierre Courbon",52806,"CR","","","Correction of pDNAddressAllocation into pDNType","","10","9.2","Release 12 & 13  33.108 v12.9.0",0,"withdrawn","2015-10-07T17:01:32.553",null,"S3i150327","","Rel-13","33.108","12.10.0","","0280","2","F",null,"","","","",""]
["S3i150336","Fixing ASN.1 field","AQSACOM S.A.S.","Jean-Francois Zell",21411,"CR","","","Correction of pDNAddressAllocation into pDNType","","10","9.2","Release 12 & 13  33.108 v12.9.0",0,"agreed","2015-10-07T17:04:15.227","2015-10-07T17:36:36.403","S3i150327","","Rel-13","33.108","12.10.0","LI12","0280","3","F","SP-150723","","","","",""]
["S3i150337","Stage 3 definition for CC Unavailable Indication","Nokia Networks","Nagaraja Rao",41611,"CR","","","The stage 2 defintion (TS 33.107) specifies that in certain situations when the content is not available for an IMS-based VoIP call, the interception shall continue with IRI-only and shall send an indication to the LEMF that the content is not available. This document introduces the concept at a stage 3 level.        \n\nA new indication is added to the IMS events in order to have an ability for the IMS ICE to send an indication that in certain situations, the CC is not available.","","10","9.2","Release 12 & 13  33.108 v12.9.0",0,"agreed","2015-10-07T17:11:32.743","2015-10-07T17:14:40.753","S3i150320","","Rel-13","33.108","12.10.0","LI13","0287","2","B","SP-150724","","","","",""]
["S3i150338","New LI events related to HSS in IMS, non 3GPP access network","Ministère Economie Indu. Numer","Pierre Courbon",52806,"CR","","","Some events and IRI related to HSS are proposed specially during interworking or any activities related to the target using an IMS network or non 3GPP access network.\n\nOptional events and related information are included :\n•\tSubscriber record change \n•\tCancel location\n•\tRegistration termination\n•\tLocation information Request","","8","8.2","Release 12 & 13\t33.107 v12.11.0",0,"revised","2015-10-07T18:51:58.797","2015-10-07T18:56:15.477","S3i150332","S3i150342","Rel-13","33.107","13.0.0","LI13","0184","4","B",null,"","","","",""]
["S3i150339","CR to 33.106 to support LCS","Rogers Communications","Edward O'Leary",24518,"CR","","","Cr provides additional and clarifying  requirements when LCS is used , revised to include definition of\n Lawful Access Location Services, revised as per meeting discussion , Final including Note update","","6","7.2","Release 13\t33.106 v13.0.0",0,"agreed","2015-10-07T19:00:23.173","2015-10-07T19:02:57.223","S3i150334","SP-150736","Rel-13","33.106","13.1.0","LI13","0147","5","B",null,"","","","",""]
["S3i150340","Reply LS to Incoming liaison “GSMA LS on ePDG selection” S3i150210","Ministère Economie Indu. Numer","Pierre Courbon",52806,"LS out","","","3GPP SA3-LI would like to thank GSMA NG RILTE for the LS to 3GPP SA3-LI on ePDG Selection, about questions introduced by IR.51 and 3GPP TS 23.402 (section 7.2.1 for ePDG discovery). \nThe NG RILTE’s understanding is that according to TS 24.302, in roaming scenarios in which the UE knows the identity of the VPLMN, the UE first attempts to derive the FQDN for ePDG address from the visited PLMN ID and to connect with ePDG in visited network, and only attempts to connect with the ePDG of the HPLMN as the option of last resort.\nNG RILTE highlighted that in certain VoWiFi deployment scenarios the preference of the home operator might be that the UE should connect to the ePDG in home network also when roaming. Possible such scenarios include, for instance, when visited networks have not deployed VoWiFi yet, there is no S2b layer roaming agreement with visited networks, or not enough interoperability testing.","","16","13","Outgoing Liaisons",0,"revised","2015-10-07T19:01:11.360","2015-10-07T19:06:32.377","S3i150304","S3i150344","Rel-13","","","","","","","","S3i150210","GSMA NG RILTE, 3GPP SA2, 3GPP CT1","ETSI TC LI"]
["S3i150341","S8HR P-CR proposing text for 4.2 Architecture","SPRINT Corporation, NTT Docomo","Greg Schumacher",35113,"pCR","","","","","11","10","Continued Discussion and New Business",0,"revised","2015-10-07T20:48:45.663","2015-10-07T20:52:48.773","S3i150285","S3i150343","Rel-13","","","","","",null,"","","","","",""]
["S3i150342","New LI events related to HSS in IMS, non 3GPP access network","Ministère Economie Indu. Numer","Pierre Courbon",52806,"CR","","","Some events and IRI related to HSS are proposed specially during interworking or any activities related to the target using an IMS network or non 3GPP access network.\n\nOptional events and related information are included :\n•\tSubscriber record change \n•\tCancel location\n•\tRegistration termination\n•\tLocation information Request","","8","8.2","Release 12 & 13\t33.107 v12.11.0",0,"agreed","2015-10-07T21:12:43.350","2015-10-07T21:52:54.363","S3i150338","","Rel-13","33.107","13.0.0","LI13","0184","5","B","SP-150724","","","","",""]
["S3i150343","S8HR P-CR proposing text for 4.2 Architecture","SPRINT Corporation, NTT Docomo","Greg Schumacher",35113,"pCR","","","","","11","10","Continued Discussion and New Business",0,"approved","2015-10-07T21:24:01.387","2015-10-07T21:54:00.630","S3i150341","","Rel-13","","","","","",null,"","","","","",""]
["S3i150344","Reply LS to Incoming liaison “GSMA LS on ePDG selection” S3i150210","Ministère Economie Indu. Numer","Pierre Courbon",52806,"LS out","","","3GPP SA3-LI would like to thank GSMA NG RILTE for the LS to 3GPP SA3-LI on ePDG Selection, about questions introduced by IR.51 and 3GPP TS 23.402 (section 7.2.1 for ePDG discovery). \nThe NG RILTE’s understanding is that according to TS 24.302, in roaming scenarios in which the UE knows the identity of the VPLMN, the UE first attempts to derive the FQDN for ePDG address from the visited PLMN ID and to connect with ePDG in visited network, and only attempts to connect with the ePDG of the HPLMN as the option of last resort.\nNG RILTE highlighted that in certain VoWiFi deployment scenarios the preference of the home operator might be that the UE should connect to the ePDG in home network also when roaming. Possible such scenarios include, for instance, when visited networks have not deployed VoWiFi yet, there is no S2b layer roaming agreement with visited networks, or not enough interoperability testing.","","16","13","Outgoing Liaisons",0,"not concluded","2015-10-07T21:48:03.877",null,"S3i150340","","Rel-13","","","","","","",""]
["S3i150345","LIV8 S8HR TR latest version","SPRINT Corporation","Greg Schumacher",35113,"draft TR","","","Version of TR incorporating P-CRs agreed in the Austin 3GPP SA 3 LI meeting #59. Proposed for further P-CR contributions at 3GPP SA 3 LI #60.","","11","10","Continued Discussion and New Business",0,"agreed","2015-10-07T22:26:56.233","2015-10-22T21:22:03.907","","","Rel-13","","","","","","","","","","","",""]
["S3i150346","P-CR on intra-access handover for LIV-8 study","NTT DOCOMO INC.","Alf Zugenmaier",52494,"pCR","","","Proposes architectural requirements for intra-access handovers.","","11","10","Continued Discussion and New Business",0,"approved","2015-10-07T22:48:21.977","2015-10-07T23:08:18.833","S3i150289","","Rel-14","","","","","",null,"","","","","",""]
["S3i150347","P-CR on LIV-8 study  for GTP selection criteria","NTT DOCOMO INC.","Alf Zugenmaier",52494,"pCR","","","Proposes a description and a solution for the key issue number #3.","","11","10","Continued Discussion and New Business",0,"approved","2015-10-07T22:50:05.483","2015-10-07T23:08:19.020","S3i150287","","Rel-14","","","","","",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"]