{"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":550,"n_cols":32,"rows_kept":550,"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"]
["C4-161000","Agenda","CT4 Chairman","Kimmo Kymalainen",19464,"agenda","","Information","","","4","2","Allocation of documents to agenda items",10000,"noted","2015-12-24T10:47:33.663","2016-02-01T13:44:39.497","","","","","","","","","","","","","","",""]
["C4-161001","Detailed agenda & time plan for CT4#72: status at document deadline","CT4 Chairman","Nigel. H Berry",68268,"agenda","","Information","","","4","2","Allocation of documents to agenda items",10010,"noted","2015-12-24T10:49:13.830","2016-02-09T13:23:04.070","","","","","","","","","","","","","","",""]
["C4-161002","Detailed agenda & time plan for CT4#71: status on eve of meeting","CT4 Chairman","Nigel. H Berry",68268,"agenda","","Information","","","4","2","Allocation of documents to agenda items",10020,"noted","2015-12-24T10:50:02.750","2016-02-12T15:56:40.640","","","","","","","","","","","","","","",""]
["C4-161003","Proposed allocation of documents to agenda items for CT4#71: status at document deadline","CT4 Chairman","Nigel. H Berry",68268,"agenda","","Information","","","4","2","Allocation of documents to agenda items",10030,"noted","2015-12-24T10:50:58.427","2016-02-09T13:23:04.117","","","","","","","","","","","","","","",""]
["C4-161004","Proposed allocation of documents to agenda items for CT4#68bis: status on eve of meeting","Alcatel-Lucent Telecom Ltd","Nigel. H Berry",68268,"agenda","","Approval","","","4","2","Allocation of documents to agenda items",10040,"noted","2015-12-24T10:51:39.457","2016-02-12T15:56:40.733","","","","","","","","","","","","","","",""]
["C4-161005","CT4 previous meeting report for approval","MCC","Kimmo Kymalainen",19464,"report","","Approval","","","5","3","Meeting Reports",10050,"approved","2015-12-24T10:52:23.243","2016-02-12T13:30:12.243","","","","","","","","","","","","","","",""]
["C4-161006","CT/SA #70 Status report","Chairman","Kimmo Kymalainen",19464,"report","","Information","","","5","3","Meeting Reports",10060,"noted","2015-12-24T10:53:07.547","2016-02-01T13:43:07.830","","","","","","","","","","","","","","",""]
["C4-161007","Release of WebRTC Data Channels","Alcatel-Lucent","Albrecht Schwarz",68771,"CR","","Approval","Description of WebRTC data channel release.","","18","7.1.8","H.248 Aspects of WebRTC Data Channel on IMS Access Gateway",10070,"revised","2016-01-11T14:10:01.510","2016-02-01T14:29:02.913","","C4-161273","Rel-13","23.334","13.4.0","WebRTCH248DC","0104","","B",null,"","","","",""]
["C4-161008","WebRTC Data Channels","Alcatel-Lucent","Albrecht Schwarz",68771,"CR","","Approval","Completion of WebRTC data channel release.","","18","7.1.8","H.248 Aspects of WebRTC Data Channel on IMS Access Gateway",12730,"revised","2016-01-11T14:20:26.540","2016-02-01T14:29:02.960","","C4-161274","Rel-13","29.334","13.3.0","WebRTCH248DC","0105","","B",null,"","","","",""]
["C4-161009","WebRTC gateway configuration for end-to-end WebRTC calls (stage 2)","Alcatel-Lucent","Albrecht Schwarz",68771,"CR","","Approval","Explicit requirements and procedures related the WebRTC gateway configuation for end-to-end IMS-WebRTC calls are proposed.","","44","7.2.12","Enhancements to WEBRTC interoperability stage 3 (CT1)  [eWebRTCi_CT]",10090,"withdrawn","2016-01-11T14:42:39.230","2016-02-01T14:29:02.990","","","Rel-13","23.334","13.4.0","eWebRTCi-CT","0105","","B",null,"","","","",""]
["C4-161010","WebRTC gateway configuration for end-to-end WebRTC calls (stage 3)","Alcatel-Lucent","Albrecht Schwarz",68771,"CR","","Approval","Explicit information related the WebRTC gateway configuation for end-to-end IMS-WebRTC calls is proposed.","","44","7.2.12","Enhancements to WEBRTC interoperability stage 3 (CT1)  [eWebRTCi_CT]",10100,"revised","2016-01-11T14:44:43.250","2016-02-01T14:29:03.023","","C4-161369","Rel-13","29.334","13.3.0","eWebRTCi-CT","0106","","B",null,"","","","",""]
["C4-161011","TrGW configuration for end-to-end WebRTC calls (stage 3)","Alcatel-Lucent","Albrecht Schwarz",68771,"CR","","Approval","Explicit information related the TrGW configuation for end-to-end IMS-WebRTC calls is proposed.","","44","7.2.12","Enhancements to WEBRTC interoperability stage 3 (CT1)  [eWebRTCi_CT]",10110,"revised","2016-01-11T14:47:08.223","2016-02-01T14:29:03.070","","C4-161370","Rel-13","29.238","13.0.0","eWebRTCi-CT","0062","","B",null,"","","","",""]
["C4-161012","H.248 WebRTC gateway bearer plane interworking for end-to-end WebRTC traffic","Alcatel-Lucent","Albrecht Schwarz",68771,"discussion","","Information","Update of DISC C4-151930 due to offline discussions since the last CT4#71 meeting.","","44","7.2.12","Enhancements to WEBRTC interoperability stage 3 (CT1)  [eWebRTCi_CT]",10010,"noted","2016-01-11T15:05:46.133","2016-02-01T14:29:03.117","","","Rel-13","29.334","","eWebRTCi-CT","","","","","","","","",""]
["C4-161013","QoS end-to-end MTSI extensions: possible impact on H.248 packet gateways","Alcatel-Lucent","Albrecht Schwarz",68771,"discussion","","Discussion","CT3 did already update the PCC \"Diameter gateway\" for support of QoSE2EMTSI at the last meeting, but the implementation of QoSE2EMTSI related extensions is still open for CT4 H.248 gateway types.\nQoSE2EMTSI leads essentially to an extended traffic descri","","35","7.2.3","CT aspects of QoS End to End MTSI extensions (CT3) [QOSE2EMTSI-CT]",10010,"noted","2016-01-13T07:51:56.603","2016-02-01T14:29:03.163","","","Rel-14","","","QOSE2EMTSI-CT","","","","","","","","",""]
["C4-161014","IMS-WebRTC Rel-14: potential enhancements for IMS-WebRTC gateways","Alcatel-Lucent","Albrecht Schwarz",68771,"discussion","","Discussion","The document attempts a wrap-up of the achieved IMS-WebRTC solution with focus on WebRTC services only which require an IMS-WebRTC gateway in the IP bearer path. The supported IMS-WebRTC capabilities with 3GPP Rel-13 represents still a subset in compariso","","85","8.2.5","IMS Web RTC [IMS_WebRTC]",10140,"noted","2016-01-13T08:10:33.003","2016-02-01T14:29:03.193","","","Rel-14","29.334","","IMS_WebRTC-CT4","","","","","","","","",""]
["C4-161015","Alternate IP Connectivity: upgrade options for ALTC support by H.248 gateways","Alcatel-Lucent","Albrecht Schwarz",68771,"discussion","","Information","Support for ALTC was introduced in the IMS Access Gateway with 3GPP Rel-12 in 2014-11. The selected, rudimentary stage 3 approach was considered to be a transient solution as long as H.248 extensions are not available for a more enhanced protocol solution","","76","8.1.16","Support of ALT-C attribute [ALTC]",10150,"noted","2016-01-13T08:14:40.600","2016-02-01T14:29:03.240","","","Rel-14","29.238","","ALTC","","","","","","","","",""]
["C4-161016","Clarification of EVS codec support by 3GPP H.248 Media Gateways","Alcatel-Lucent","Albrecht Schwarz",68771,"discussion","","Discussion","Support for EVS transcoding by 3GPP H.248 gateway equipment seems to be required only for a small number of calls (if at all for some gateway types), but apparently not for the very majority of end-to-end calls with EVS audio.\nAll 3GPP H.248 profiles are","","79","8.1.19","CT impacts of Codec for Enhanced Voices Services [EVS_codec-CT]",10160,"noted","2016-01-19T12:45:05.947","2016-02-01T14:29:03.270","","","Rel-13","23.334","","EVS_codec-CT","","","","","","","","",""]
["C4-161017","LS on NBIFOM procedure in SCM and RAN rules handling parameter","3GPP TSG CT WG1","Kimmo Kymalainen",19464,"LS in","","Discussion","According to the description in subclause 6.2.3.1 of TS 23.161, default access can be transported between the UE and the network via EAP procedures when adding addition of trusted WLAN using SCM. This implies that 3GPP AAA server should be able to convey","","38","7.2.6","IP Flow Mobility support for S2a and S2b Interfaces on stage 3 (CT1) [NBIFOM]",10170,"noted","2016-01-26T08:18:44.007","2016-01-26T09:57:27.460","","","Rel-13","","","NBIFOM-CT","","","","",null,"3GPP TSG SA WG2","3GPP TSG CT WG3, 3GPP TSG CT WG4","C1-154645"]
["C4-161018","Reply LS on Disconnection of NBIFOM PDN Connection with the Cause \"Reactivation Requested\"","3GPP TSG CT WG1","Kimmo Kymalainen",19464,"LS in","","Discussion","CT1 thanks CT4 for their LS on Disconnection of NBIFOM PDN Connection with the Cause \"Reactivation Requested\" (C4-151846/C1-154056)\nCT1 reviewed the possible behaviours of a UE supporting NBIFOM if it receives a request to release a PDN connection with t","","38","7.2.6","IP Flow Mobility support for S2a and S2b Interfaces on stage 3 (CT1) [NBIFOM]",10180,"noted","2016-01-26T08:22:19.253","2016-01-26T09:57:27.490","","","","","","PCSCF_RES_WLAN","","","","",null,"3GPP TSG CT WG4",null,"C1-154884"]
["C4-161019","Reply LS on Mapping table between GTPv2 S2a and WLCPDiameter","3GPP TSG CT WG1","Kimmo Kymalainen",19464,"LS in","","Discussion","CT1 has reviewed the CT4 CRs, and decided to introduce the reject causes \"user authentication failed\" and \"PDN connection does not exist\" to CT1's TS 24.244 WLCP (MCM, from TWAN to the UE) and TS 24.302 for EAP message (SCM, from 3GPP AAA Server to the UE","","95","8.3.1","GTP and PMIP [TEI12]",10000,"noted","2016-01-26T08:26:35.747","2016-01-26T09:57:27.523","","","Rel-13","","","","","","","",null,"3GPP TSG CT WG4",null,"C1-160598"]
["C4-161020","LS on issues related to MT SMS over SGs delivery in eDRX","3GPP TSG CT WG1","Kimmo Kymalainen",19464,"LS in","","","CT1 has observed some issues for the mobile terminated SMS in eDRX procedure described in TS 23.272 subclause 8.2.4a (the procedure shown in Figure 8.2.4a-1). The more critical issues are described below:\na.\tEvery MT SMS delivery for UEs in eDRX will cau","","42","7.2.10","Extended DRX cycle for power consumption optimization (CT1) [eDRX]",10200,"noted","2016-01-26T08:33:56.850","2016-01-26T09:57:27.570","","","Rel-13","","","eDRX-CT","","","","",null,"3GPP SA2","3GPP CT4","C1-160782"]
["C4-161021","LS on MCPTT Group data and affiliation","3GPP TSG CT WG1","Kimmo Kymalainen",19464,"LS in","","Discussion","","","43","7.2.11","Mission Critical Push To Talk over LTE protocol aspects (CT1) [MCPTT-CT]",10210,"noted","2016-01-26T08:36:58.230","2016-01-26T09:57:27.600","","","Rel-13","","","MCPTT-CT","","","","",null,"SA6","CT4","C1-160783"]
["C4-161022","LS on questions on CIoT","3GPP TSG CT WG1","Kimmo Kymalainen",19464,"LS in","","Discussion","CT1 have started work on CIoT and would like to ask the following questions:\n(1)\tTo SA2: Have CT1 to provide support for UEs which can have the UE-SCEF connection running in parallel with PDN connection such as Internet, IMS etc.\nFurther information: A","","46","7.2.14","CIoT-CT (CT1)  [CIoT-CT]",10000,"noted","2016-01-26T08:40:23.743","2016-01-26T09:57:27.630","","","Rel-13","","","CIoT-CT","","","","",null,"3GPP SA WG2, 3GGP RAN WG2, 3GPP RAN WG1","3GPP CT WG4","C1-160784"]
["C4-161023","Reply LS on OCS address for Gy and Gyn inter-PLMN","3GPP TSG CT WG3","Kimmo Kymalainen",19464,"LS in","","Discussion","CT3 would like to inform SA5 that the functionality is agreed for the Gx and the Sd procedures by TS 29.212 CR  1397 attached to this LS.","","6","4","Input liaison statements: allocation to agenda items as appropriate",10230,"noted","2016-01-26T08:45:51.997","2016-01-26T09:57:27.663","","","","","","TEI13, iPLMN-PS-OCH","","","","",null,"SA5","CT4, SA2","C3-155314"]
["C4-161024","LS on the decision of NBIFOM mode","3GPP TSG CT WG3","Kimmo Kymalainen",19464,"LS in","","Discussion","CT3 is working on the definition of NBIFOM mode on Gx interface and has some questions about the following definition in TS 23.161: \n\n5.4.4\tMode Selection\nWhen an NBIFOM-capable UE supports ANDSF and has an ISRP rule valid in the registered PLMN then:","","38","7.2.6","IP Flow Mobility support for S2a and S2b Interfaces on stage 3 (CT1) [NBIFOM]",10240,"noted","2016-01-26T08:49:00.473","2016-01-26T09:57:26.803","","","Rel-13","","","NBIFOM-CT","","","","",null,"SA2","CT1, CT4","C3-155320"]
["C4-161025","LS on Request for Diameter Command Code and Application ID for new St Interface","3GPP TSG CT WG3","Kimmo Kymalainen",19464,"LS in","","Discussion","St application ID was requested (by MCC) and IANA has registered the following Application ID: 16777349\t 3GPP S","","6","4","Input liaison statements: allocation to agenda items as appropriate",10250,"noted","2016-01-26T08:52:26.267","2016-01-26T09:57:26.837","","","Rel-13","","","FMSS-CT","","","","",null,"CT4",null,"C3-155351"]
["C4-161026","Reply LS on the Setting of Delay Tolerant Connection Indication","3GPP TSG CT WG3","Kimmo Kymalainen",19464,"LS in","","Discussion","CT4 has informed CT3 that CT4 had agreed to the following:\nThe DTCI is set by the PGW/GGSN according to the local policies in the PGW/GGSN e.g. on per APN basis.\nCT3 has discussed this and has come to the conclusion that there is no impact to PCC interfac","","42","7.2.10","Extended DRX cycle for power consumption optimization (CT1) [eDRX]",10260,"noted","2016-01-26T08:56:23.650","2016-01-26T09:57:26.867","","","Rel-13","","","eDRX-CT","","","","",null,"CT4","SA2","C3-155359"]
["C4-161027","Reply LS on Multi-stream Multiparty Conferencing Media Handling","3GPP TSG CT WG3","Kimmo Kymalainen",19464,"LS in","","Discussion","CT3 thanks SA4 for their LS providing the draft CR (S4-151542 CR 26.114-0355 rev 2) on \"Introduction of Multistream Multiparty Conference Media Handling (Release 13)\" for review.\n\nSA4 asked CT3 to review that CR and assess the related impacts on CT3´s spe","","6","4","Input liaison statements: allocation to agenda items as appropriate",10270,"noted","2016-01-26T08:58:23.130","2016-01-26T09:57:26.897","","","Rel-13","","","MMCMH","","","","",null,"SA4","CT1, CT4, CT","C3-155367"]
["C4-161028","NG PACKET LS to Standardization groups on PMIP removal","GSMA PACKET #83","Kimmo Kymalainen",19464,"LS in","","Discussion","GSMA Networks Group would like to inform all standardization groups working on LTE and EPS Roaming that decision has been taken to not support any more PMIP protocol over S8 interface for current and future International Roaming services, as only the GTP","","6","4","Input liaison statements: allocation to agenda items as appropriate",10280,"noted","2016-01-26T09:01:13.857","2016-01-26T09:57:26.947","","","","","","","","","","",null,"3GPP SA2, 3GPP CT4",null,"PACKET#83 Doc 107"]
["C4-161029","LS on extension to field length of PDCP Sequence Number","3GPP TSG RAN WG2","Kimmo Kymalainen",19464,"LS in","","Discussion","RAN2 would like to inform RAN3, CT4 and SA3 that RAN2 has taken as a baseline to extend the field length of PDCP SN [TS 36.323] for AM DRB for both UL and DL to 23 bits in Rel-13, in addition to the previous maximum value of 15 bits (which is per DRB conf","","58","7.3.11","18 bits PDCP PDU Number",10290,"noted","2016-01-26T09:03:32.820","2016-01-26T09:57:26.977","","","Rel-13","","","LTE_CA_enh_b5C-Core","","","","",null,"TSG-RAN WG3, TSG-CT WG4","TSG-SA WG3","R2-153873"]
["C4-161030","LS on extension to field length of PDCP Sequence Number","3GPP TSG RAN WG2","Kimmo Kymalainen",19464,"LS in","","Discussion","RAN2 would like to inform RAN3 and CT4 that RAN2 has made a decision to extend the field length of PDCP SN [TS 36.323] for AM DRB for both UL and DL to 18 bits in Rel-13, in addition to the previous maximum value of 15 bits (which is per DRB configurable)","","58","7.3.11","18 bits PDCP PDU Number",10300,"replied to","2016-01-26T09:07:49.687","2016-01-26T09:57:27.007","","","Rel-13","","","LTE_CA_enh_b5C-Core","","","","",null,"TSG-RAN WG3, TSG-CT WG4","TSG-SA WG3","R2-156977","C4-161337"]
["C4-161031","Reply LS on 3GPP Work on Explicit Congestion Notification for Lower Layer Protocols","3GPP TSG RAN WG2","Kimmo Kymalainen",19464,"LS in","","Discussion","RAN2 could be affected by the work on ECN for lower layer protocols. Among RAN2 specifications, ECN is used in section 11. 6 of TS 36.300 for codec rate control.\n\nAt this moment, RAN2 has no particular comments on draft-ietf-tsvwg-ecn-encap-guidelines-04.","","6","4","Input liaison statements: allocation to agenda items as appropriate",10310,"noted","2016-01-26T09:10:22.940","2016-01-26T09:57:27.037","","","Rel-10","","","ECSRA_LAA","","","","",null,"SA","CT, RAN, SA2, SA4, CT1, CT3, CT4","R2-157038"]
["C4-161032","Response LS on Conclusions from TR 23.712 on Warning Status Reporting","3GPP TSG RAN WG3","Kimmo Kymalainen",19464,"LS in","","Discussion","RAN3 thanks CT1 for their LS on Conclusions from TR 23.712 on Warning Status Reporting. \n\nRAN3 has agreed at RAN3#90 the attached CRs to TS 36.300 and TS 36.413 which introduce the new PWS Failure Indication procedure for ongoing PWS operation.","","36","7.2.4","Warning Status Report in EPS (CT1) [WSR_EPS]",10320,"noted","2016-01-26T09:14:18","2016-01-26T09:57:27.070","","","Rel-13","","","WSR_EPS","","","","",null,"CT1, CT4",null,"R3-152901"]
["C4-161033","LS on S1 signalling solutions for non-NB-IoT UEs","3GPP TSG RAN","Kimmo Kymalainen",19464,"LS in","","Discussion","RAN discussed applicability of S1 signalling enhancements for non-NB-IoT UEs, i.e., Solution 2 and Solution 18 as discussed in SA2.  RAN made following agreements how to proceed with this:\n\n•\tSignalling design for solution 2 and solution 18 for NB-IoT U","","46","7.2.14","CIoT-CT (CT1)  [CIoT-CT]",12000,"noted","2016-01-26T09:17:34.310","2016-01-26T09:57:27.100","","","Rel-13","","","NB_IOT-Core","","","","",null,"SA2, SA3, SA, CT1, CT3, CT4, RAN2, RAN3","RAN1","RP-152296"]
["C4-161034","Reply LS on clarification on requirements for AESE","3GPP TSG SA WG2","Kimmo Kymalainen",19464,"LS in","","Discussion","I) Overwriting of CP parameter set(s)\nIn TS 23.682 sub-clause 5.10.2 the NOTE2 talks about overwriting of CP sets. The NOTE2 mentions the same SCS/AS or another SCS/AS, but not what happens if it is the same or different SCEFs. CT4's understanding is:\n\n\tA","","40","7.2.8","CT aspects of Architecture Enhancements for Service Capability (CT3) [AESE-CT]",10340,"noted","2016-01-26T09:19:39.170","2016-01-26T09:57:27.133","","","Rel-13","","","AESE-CT","","","","",null,"3GPP TSG CT4",null,"S2-154234"]
["C4-161035","Reply LS on clarification on requirements for MONTE","3GPP TSG SA WG2","Kimmo Kymalainen",19464,"LS in","","Discussion","Question 1: If reporting is stopped due to roaming into an MME/SGSN which does not support the active monitoring event, should the HSS Inform the SCEF about the stop of Monitoring and continuation when the UE roams back into an MME/SGSN which supports the","","19","7.1.9","Monitoring Enhancements CT aspects [MONTE-CT]",10000,"replied to","2016-01-26T09:26:59.727","2016-01-26T09:57:27.180","","","Rel-13","","","MONTE-CT","","","","",null,"3GPP TSG CT4",null,"S2-154383","C4-161537"]
["C4-161036","LS on Network asserted WLAN Location Information for PDN connection establishment over S2b","3GPP TSG SA WG2","Kimmo Kymalainen",19464,"LS in","","Discussion","SA2 thanks CT4 for their LS on Network asserted WLAN Location Information for PDN connection establishment over S2b.\nSA2 have discussed the issue and, as proposed by CT4, concluded that it is valuable that, when available, User Location Information is tr","","41","7.2.9","Support of Emergency services over WLAN Ã¢â‚¬â€œ phase 1 (CT1) [SEW1-CT]",10360,"noted","2016-01-26T09:32:05.220","2016-01-26T09:57:27.210","","","Rel-13","","","SEW1-CT","","","","",null,"3GPP TSG CT4","3GPP TSG CT3","S2-154406"]
["C4-161037","LS on Mobile Equipment Identity Signalling over WLAN","3GPP TSG SA WG2","Kimmo Kymalainen",19464,"LS in","","Discussion","SA2 thanks CT4 for their LS on “Mobile Equipment Identity Signalling over WLAN”.\nBased on this LS, SA2 has agreed to the attached CR(s).\n\nIMEI checking (e.g. disallow WLAN access for stolen equipment) will be specified as part of the EWE WID that is al","","6","4","Input liaison statements: allocation to agenda items as appropriate",10370,"noted","2016-01-26T09:34:44.043","2016-01-26T09:57:27.257","","","Rel-13","","","MEI_WLAN","","","","",null,"CT4","CT1, SA3, SA3-LI, SA5","S2-154415"]
["C4-161038","LS on Retrieval of UE Usage Type from HSS","3GPP TSG SA WG2","Kimmo Kymalainen",19464,"LS in","","Discussion","SA2 thanks CT4 for their LS on retrieval of UE Usage Type from HSS. SA2 has evaluated and agreed to the proposal from CT4. \n\nTherefore, SA2 has agreed to the attached CR to TS 23.401. SA2 informs CT4 that there is no need for a CR to TS 23.060 because D","","28","7.1.18","Dedicated Core Networks [DECOR-CT]",10380,"noted","2016-01-26T09:37:42.570","2016-01-26T09:57:27.287","","","Rel-13","","","DECOR-CT","","","","",null,"CT4",null,"S2-154447"]
["C4-161039","Reply LS on proposed extension to GUSS to include AS address","3GPP TSG SA WG2","Kimmo Kymalainen",19464,"LS in","","Discussion","[Question#1 from CT1]\nWhen an AP receives an HTTP request from a user, and there are several AS instances providing the service requested in the received HTTP request, does stage-2 include any requirements on per-user configuration for AP's routing of th","","6","4","Input liaison statements: allocation to agenda items as appropriate",10390,"noted","2016-01-26T09:41:04.963","2016-01-26T09:57:27.320","","","Rel-13","","","","","","","",null,"3GPP TSG CT WG1","3GPP TSG CT WG4, TSG SA WG3","S2-1544450"]
["C4-161040","LS on Packet switched conversational multimedia applications TS 26.235 and TS 26.236","3GPP TSG SA WG4","Kimmo Kymalainen",19464,"LS in","","Discussion","3GPP TS 26.235 Packet switched conversational multimedia applications; Default codecs and 3GPP TS 26.236 Packet switched conversational multimedia applications; Transport protocols are both under SA4 responsibility. Those 2 TSs haven’t been updated since","","56","7.3.9","H.248 Interfaces",10449,"noted","2016-01-26T09:43:16.673","2016-01-26T09:57:27.350","","","Rel-13","","","IMS-CODEC","","","","",null,"3GPP TSG CT WG3, 3GPP TSG CT WG4, 3GPP TSG RAN WG5, 3GPP TSG RAN WG2","3GPP TSG SA","S4-151562"]
["C4-161041","Reply LS on 3GPP Work on Explicit Congestion Notification for Lower Layer Protocols","3GPP TSG SA","Kimmo Kymalainen",19464,"LS in","","Discussion","IETF tsvwg requested information from 3GPP.\n1) to tell the IETF tsvwg which 3GPP working groups could be affected by this work.\nThe working groups that could be affected by ongoing work on ECN include SA2, SA4, RAN2, CT1, CT3,  and CT4.\n2) To inform th","","6","4","Input liaison statements: allocation to agenda items as appropriate",10410,"noted","2016-01-26T09:46:28.800","2016-01-26T09:57:27.380","","","Rel-10","","","ECSRA_LAA","","","","",null,"IETF tsvwg","CT, RAN, SA2, SA4, RAN2, RAN3, CT1, CT3, CT4","SP-150829"]
["C4-161042","Reply LS on questions on CIoT","3GPP TSG RAN WG2 NB-IOT Ad-hoc","Kimmo Kymalainen",19464,"LS in","","Discussion","RAN2 thanks CT1 for the LS and would like to provide feedback on Q16:\n(16)\tTo: RAN2: Is (or will be) NB-IoT designed to guarantee in-sequence-delivery of packets?\nRAN2: Yes, NB-IoT design guarantees in-sequence-delivery of packets as for LTE.\nIn additi","","46","7.2.14","CIoT-CT (CT1)  [CIoT-CT]",13000,"noted","2016-01-26T09:50:39.537","2016-01-26T09:57:27.427","","","Rel-13","","","CIoT-CT","","","","",null,"3GPP CT WG1","3GPP SA WG2, RAN WG1, CT WG4","R2-160536"]
["C4-161043","Multi-stream Multiparty Conferencing Media Handling","Ericsson","Nevenka Biondic",41878,"discussion","","Discussion","The purpose of this discussion paper is to present an initial analysis of the updates required in CT WGs specifications to enable Multi-stream Multiparty Conferencing Media Handling (MMCMH), and to propose a way forward on the introduction of Multi-stream","","7","5","Work item management",10430,"noted","2016-01-26T12:50:23.380","2016-02-01T10:22:12.893","","","Rel-14","","","","","","","","","","","",""]
["C4-161044","CT aspects of MTSI Extension on Multi-stream Multiparty Conferencing Media Handling","Ericsson","Nevenka Biondic",41878,"WID new","","Agreement","The objective of this work item is to add an optional support for the MTSI extension on Multi-stream Multiparty Conferencing Media Handling to the specifications under CT WGs responsibility.","","7","5","Work item management",10440,"revised","2016-01-26T12:50:23.380","2016-02-01T10:22:12.927","","C4-161301","Rel-14","","","","","","","","","","","",""]
["C4-161045","Removal of references to TS 26.235","Ericsson","Nevenka Biondic",41878,"CR","","","TS 23.333 contains references to TS 26.235 that need to be removed. TS 26.235 is no longer maintained and considered superseded by TS 26.114.","","56","7.3.9","H.248 Interfaces",10450,"revised","2016-01-26T12:50:23.397","2016-02-01T10:22:12.973","","C4-161371","Rel-13","23.333","13.0.0","TEI13","0090","","F",null,"","","","",""]
["C4-161046","Removal of references to TS 26.235","Ericsson","Nevenka Biondic",41878,"CR","","","TS 29.333 contains references to TS 26.235 that need to be removed. TS 26.235 is no longer maintained and considered superseded by TS 26.114.","","56","7.3.9","H.248 Interfaces",10460,"agreed","2016-01-26T12:50:23.473","2016-02-01T10:22:13.003","","","Rel-13","29.333","13.0.0","TEI13","0083","","F","CP-160048","","","","",""]
["C4-161047","Removal of references to TS 26.236","Ericsson","Nevenka Biondic",41878,"CR","","","TS 29.232 contains references to TS 26.236 that need to be removed. TS 26.236 is no longer maintained and considered superseded by TS 26.114.","","56","7.3.9","H.248 Interfaces",10470,"revised","2016-01-26T12:50:23.567","2016-02-01T10:22:13.050","","C4-161372","Rel-13","29.232","13.0.0","TEI13","0658","","F",null,"","","","",""]
["C4-161048","Removal of references to TS 26.236","Ericsson","Nevenka Biondic",41878,"CR","","","TS 29.332 contains references to TS 26.236 that need to be removed. TS 26.236 is no longer maintained and considered superseded by TS 26.114.","","56","7.3.9","H.248 Interfaces",10480,"agreed","2016-01-26T12:50:23.647","2016-02-01T10:22:13.080","","","Rel-13","29.332","13.0.0","TEI13","0197","","F","CP-160048","","","","",""]
["C4-161049","Support of enhanced bandwidth negotiation mechanism for MTSI sessions","Ericsson","Nevenka Biondic",41878,"CR","","","Specification of stage 2 Iq procedures to support the enhanced bandwidth negotiation mechanism.","","35","7.2.3","CT aspects of QoS End to End MTSI extensions (CT3) [QOSE2EMTSI-CT]",10490,"revised","2016-01-26T12:50:23.707","2016-02-01T10:22:13.127","","C4-161330","Rel-13","23.334","13.4.0","QOSE2EMTSI-CT","0106","","B",null,"","","","",""]
["C4-161050","Support of enhanced bandwidth negotiation mechanism for MTSI sessions","Ericsson","Nevenka Biondic",41878,"CR","","","Update of Iq H.248 profile (stage 3) to support the related enhanced bandwidth indication for MTSI sessions.","","35","7.2.3","CT aspects of QoS End to End MTSI extensions (CT3) [QOSE2EMTSI-CT]",10500,"revised","2016-01-26T12:50:23.787","2016-02-01T10:22:13.160","","C4-161331","Rel-13","29.334","13.3.0","QOSE2EMTSI-CT","0107","","B",null,"","","","",""]
["C4-161051","Support of enhanced bandwidth negotiation mechanism for MTSI sessions","Ericsson","Nevenka Biondic",41878,"CR","","","Specification of stage 2 Mp procedures to support the enhanced bandwidth negotiation mechanism.","","35","7.2.3","CT aspects of QoS End to End MTSI extensions (CT3) [QOSE2EMTSI-CT]",10510,"revised","2016-01-26T12:50:23.863","2016-02-01T10:22:13.207","","C4-161332","Rel-13","23.333","13.0.0","QOSE2EMTSI-CT","0091","","B",null,"","","","",""]
["C4-161052","Support of enhanced bandwidth negotiation mechanism for MTSI sessions","Ericsson","Nevenka Biondic",41878,"CR","","","Update of Mp H.248 profile (stage 3) to support the related enhanced bandwidth indication for MTSI sessions.","","35","7.2.3","CT aspects of QoS End to End MTSI extensions (CT3) [QOSE2EMTSI-CT]",10520,"revised","2016-01-26T12:50:23.940","2016-02-01T10:22:13.237","","C4-161333","Rel-13","29.333","13.0.0","QOSE2EMTSI-CT","0084","","B",null,"","","","",""]
["C4-161053","Support of enhanced bandwidth negotiation mechanism for MTSI sessions","Ericsson","Nevenka Biondic",41878,"CR","","","Update of Ix H.248 profile (stage 3) to support the related enhanced bandwidth indication for MTSI sessions.","","35","7.2.3","CT aspects of QoS End to End MTSI extensions (CT3) [QOSE2EMTSI-CT]",10530,"revised","2016-01-26T12:50:24.020","2016-02-01T10:22:13.267","","C4-161334","Rel-13","29.238","13.0.0","QOSE2EMTSI-CT","0063","","B",null,"","","","",""]
["C4-161054","Support of enhanced bandwidth negotiation mechanism for MTSI sessions","Ericsson","Nevenka Biondic",41878,"CR","","","Update of Mn H.248 profile (stage 3) to support the related enhanced bandwidth indication for MTSI sessions.","","35","7.2.3","CT aspects of QoS End to End MTSI extensions (CT3) [QOSE2EMTSI-CT]",10540,"revised","2016-01-26T12:50:24.097","2016-02-01T10:22:12.847","","C4-161335","Rel-13","29.332","13.0.0","QOSE2EMTSI-CT","0198","","B",null,"","","","",""]
["C4-161055","SCC AS Restoration","China Mobile","Yue Song",57977,"WID new","","","The objectives of the work item for SCC AS restoration are as follows: \n-\tAdd the preferred SCC AS restoration procedure to TS23.380.\n-\tAdd some description on transparent data which will includes some SCC AS restoration related information.","","7","5","Work item management",10550,"revised","2016-01-27T10:18:35.283","2016-01-29T08:55:14.617","","C4-161302","","","","","","","","","","","","",""]
["C4-161056","eProSe-Ext-CT impacts","Qualcomm Incorporated","Lena Chaponniere",38080,"discussion","","Information","The purpose of this contribution is to provide an analysis of the work left to complete in each CT WG to develop the stage 3 for the stage 2 solutions agreed under the SA2 eProSe-Ext work item, and to record the associated planned timeline","","39","7.2.7","CT aspects of enhancements to Proximity-based Services extensions (CT1) [eProSe-Ext-CT]",10560,"noted","2016-01-28T00:56:31.273","2016-01-29T23:06:22.547","","","Rel-13","","","eProSe-Ext-CT","","","","","","","","",""]
["C4-161057","Addition of ProSe Application Code Prefix and ProSe Application Code Suffix formats","Qualcomm Incorporated","Lena Chaponniere",38080,"CR","","Agreement","The formats of the ProSe Application Code Prefix and of the ProSe Application Code Suffix were added in subclause 24.","","39","7.2.7","CT aspects of enhancements to Proximity-based Services extensions (CT1) [eProSe-Ext-CT]",10570,"revised","2016-01-28T00:58:46.120","2016-01-29T23:06:22.687","","C4-161374","Rel-13","23.003","13.4.0","eProSe-Ext-CT","0434","","B",null,"","","","",""]
["C4-161058","Resolution of Editor’s notes on EVS over UMTS CS","Qualcomm Incorporated","Lena Chaponniere",38080,"CR","","Agreement","Subclauses 5.6.2, 5.6.3 and 5.6.4 were updated based on the EVS allowed configurations and the encoding of the EVS Single Codec IE defined by SA4 in TS 26.103. The corresponding Editor’s notes were removed.","","17","7.1.7","CT aspects of EVS in 3G Circuit-Switched Networks [EVSoCS-CT]",10580,"revised","2016-01-28T01:01:40.183","2016-01-29T23:05:43.077","","C4-161327","Rel-13","23.153","13.0.0","EVSoCS-CT","0131","","B",null,"","","","",""]
["C4-161059","Resolution of Editor’s note on EVS over UMTS CS","Qualcomm Incorporated","Lena Chaponniere",38080,"CR","","Agreement","An example of encoding of an EVS codec was added to subclause 11, based on the EVS Single Codec IE added by SA4 in TS 26.103. The corresponding Editor’s note was removed.","","17","7.1.7","CT aspects of EVS in 3G Circuit-Switched Networks [EVSoCS-CT]",10590,"agreed","2016-01-28T01:04:24.373","2016-01-29T23:05:43.123","","","Rel-13","29.232","13.0.0","EVSoCS-CT","0659","","B","CP-160027","","","","",""]
["C4-161060","Pseudo-CR on Removing Editor's Note on IWK-SCEF Authorization and Configuration Failure at IWK-SCEF","Cisco Systems Inc","Sridhar Bhaskaran",58580,"pCR","","Approval","It is proposed to remove the editor's note in sub-clause 5.3.2 and to address the editor's note in sub-clause 5.4.3 specify that the MME/SGSN shall send a Notify Request to the HSS to inform the configuration status at the IWK-SCEF as specified in 3GPP TS","","19","7.1.9","Monitoring Enhancements CT aspects [MONTE-CT]",10000,"revised","2016-01-28T05:21:39.053","2016-01-31T14:05:51.153","","C4-161345","Rel-13","","1.0.0","","","",null,"","","","","",""]
["C4-161061","Notifying the status of MONTE event configuration at the IWK-SCEF to the HSS","Cisco Systems Inc","Sridhar Bhaskaran",58580,"CR","","Approval","It is proposed to use Notify Request for informing the monitoring event configuration status at the IWK-SCEF to the HSS by the MME/SGSN. Correspondingly the Notify Request is updated to carry the Monitoring-Event-Config-Status AVP.","","19","7.1.9","Monitoring Enhancements CT aspects [MONTE-CT]",10610,"revised","2016-01-28T05:29:01.170","2016-01-31T14:05:51.200","","C4-161346","Rel-13","29.272","13.4.0","MONTE-CT","0618","","B",null,"","","","",""]
["C4-161062","Requested Retransmission Time in MT-Forward-SM response","Nokia Networks, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell","Ulrich Wiehe",6963,"CR","","Agreement","Remove the new parameter requestedRetransmisionTime from the positive response (MT-ForwardSM-Res) and add it to the negative response (AbsentSubscriberSM-Param).","","42","7.2.10","Extended DRX cycle for power consumption optimization (CT1) [eDRX]",13000,"agreed","2016-01-28T09:39:55.167","2016-02-01T10:09:38.407","","","Rel-13","29.002","13.2.0","eDRX-CT","1200","","F","CP-160030","","","","",""]
["C4-161063","Application ID for St","Nokia Networks, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell","Ulrich Wiehe",6963,"CR","","Agreement","Add the St application Id as allocated by IANA.","","49","7.3.2","Diameter 29.230 CRs [TEI13]",10630,"agreed","2016-01-28T09:47:21.823","2016-02-01T10:09:38.437","","","Rel-13","29.230","13.3.0","FMSS-CT","0503","","F","CP-160041","","","","",""]
["C4-161064","AVP code range reservation for 32.299","Nokia Networks, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell","Ulrich Wiehe",6963,"CR","","Agreement","Allocate the AVP code range 3900-3999 to TS 32.299 as originally agreed in CR 0459r1 (and actually already used in 32.299 v13.3.0).\nShift range for TS 29.128 to 4300-4399 (AVP code values are not yet assigned in TS 29.128 v1.0.0).","","49","7.3.2","Diameter 29.230 CRs [TEI13]",10640,"revised","2016-01-28T09:55:27.477","2016-02-01T10:09:38.233","","C4-161241","Rel-13","29.230","13.3.0","TEI13","0504","","F",null,"","","","",""]
["C4-161065","Complete the EXTERNAL_SOURCE_IP4_NAT_INFO attribute information according to IANA registration","ZTE/Joy","Xingyue Zhou",42680,"CR","","Agreement","Specify the H(e)NB shall include a zero-length EXTERNAL_SOURCE_IP4_NAT_INFO attribute to request the SeGW to return the H(e)NB local IP address information.\nFill the information of the EXTERNAL_SOURCE_IP4_NAT_INFO attribute according to IANA registration","","112","9.8","BBF Interworking Building Block I [BBAI_BBI-CT]",10650,"revised","2016-01-28T11:26:21.950","2016-02-02T01:51:59.807","","C4-161449","Rel-11","29.139","11.1.0","BBAI_BBI-CT","0002","","F",null,"","","","",""]
["C4-161066","Complete the EXTERNAL_SOURCE_IP4_NAT_INFO attribute information according to IANA registration","ZTE/Joy","Xingyue Zhou",42680,"CR","","Agreement","Specify the H(e)NB shall include a zero-length EXTERNAL_SOURCE_IP4_NAT_INFO attribute to request the SeGW to return the H(e)NB local IP address information.\nFill the information of the EXTERNAL_SOURCE_IP4_NAT_INFO attribute according to IANA registration","","112","9.8","BBF Interworking Building Block I [BBAI_BBI-CT]",10660,"revised","2016-01-28T11:26:22.077","2016-02-02T01:51:59.853","","C4-161450","Rel-12","29.139","12.0.0","BBAI_BBI-CT","0003","","A",null,"","","","",""]
["C4-161067","Complete the EXTERNAL_SOURCE_IP4_NAT_INFO attribute information according to IANA registration","ZTE/Joy","Xingyue Zhou",42680,"CR","","Agreement","Specify the H(e)NB shall include a zero-length EXTERNAL_SOURCE_IP4_NAT_INFO attribute to request the SeGW to return the H(e)NB local IP address information.\nFill the information of the EXTERNAL_SOURCE_IP4_NAT_INFO attribute according to IANA registration","","112","9.8","BBF Interworking Building Block I [BBAI_BBI-CT]",10670,"revised","2016-01-28T11:26:22.170","2016-02-02T01:51:59.900","","C4-161451","Rel-13","29.139","13.0.0","BBAI_BBI-CT","0004","","A",null,"","","","",""]
["C4-161068","An Issue on HSS failure recover procedure","NEC EUROPE LTD","Toshiyuki Tamura",17921,"discussion","","Decision","The document describes a problematic scenario on an HSS failure recovery procedure by comparing with normal procedure.\n\nAs shown in solution comparison table in section 3, NEC believes that solution 1 is more feasible than others. Especially as captured","","51","7.3.4","Restoration Procedures [TEI13]",10680,"noted","2016-01-28T19:37:36.920","2016-01-29T13:26:37.673","","","Rel-13","","","TEI13","","","","","","","","",""]
["C4-161069","Fix the issue on HSS restart procedure","NEC EUROPE LTD","Toshiyuki Tamura",17921,"CR","","Decision","This CR proposed to fix the issue on the HSS restart procedure in case UE moves to other MME/SGSN due to mobility event right after the MME/SGSN receives the Reset message from the HSS.","","51","7.3.4","Restoration Procedures [TEI13]",10690,"not pursued","2016-01-28T19:41:59.327","2016-01-29T13:26:37.720","C4-151951","","Rel-13","29.274","13.4.0","TEI13","1654","1","F",null,"","","","",""]
["C4-161070","Fix the issue on HSS restart procedure","NEC EUROPE LTD","Toshiyuki Tamura",17921,"CR","","Approval","This CR proposed to fix the issue on the HSS restart procedure in case UE moves to other MME/SGSN due to mobility event right after the MME/SGSN receives the Reset message from the HSS.","","51","7.3.4","Restoration Procedures [TEI13]",10700,"revised","2016-01-28T19:46:13.120","2016-01-29T13:26:37.627","","C4-161360","Rel-13","29.272","13.4.0","TEI13","0619","","F",null,"","","","",""]
["C4-161071","User Plane Integrity Protection Indicator","Nokia Networks, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell","Ulrich Wiehe",6963,"CR","","Agreement","Define the User Plane Integrity Protection Indicator as permanent data conditionally stored in HSS/HLR and SGSN","","57","7.3.10","EGPRS Access Security Enhancements in relation to Cellular IoT",10710,"revised","2016-01-29T07:55:30.413","2016-02-01T10:09:38.267","","C4-161316","Rel-13","23.008","13.3.0","EASE_EC_GSM","0476","","F",null,"","","","",""]
["C4-161072","User Plane Integrity Protection Indicator","Nokia Networks, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell","Ulrich Wiehe",6963,"CR","","Agreement","Add User Plane Integrity Protection Indicator to Insert- and Delete Subscriber Data operations.","","57","7.3.10","EGPRS Access Security Enhancements in relation to Cellular IoT",10720,"revised","2016-01-29T08:01:00.837","2016-02-01T10:09:38.297","","C4-161317","Rel-13","29.002","13.2.0","EASE_EC_GSM","1201","","F",null,"","","","",""]
["C4-161073","User Plane Integrity Protection Indicator","Nokia Networks, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell","Ulrich Wiehe",6963,"CR","","Agreement","Allocate bits to the Subscription-Data-Flags and DSR-Flags AVPs for user plane integrity protection.","","57","7.3.10","EGPRS Access Security Enhancements in relation to Cellular IoT",10730,"revised","2016-01-29T08:04:44.147","2016-02-01T10:09:38.327","","C4-161318","Rel-13","29.272","13.4.0","EASE_EC_GSM","0620","","F",null,"","","","",""]
["C4-161074","Implicit Identities for PSI","Nokia Networks, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell","Ulrich Wiehe",6963,"CR","","Agreement","Add “as received” in the misleading sentence.","","54","7.3.7","IMS [TEI13]",10740,"merged","2016-01-29T09:54:43.827","2016-02-01T10:09:38.357","","","Rel-13","29.328","13.3.0","TEI13","0542","","F",null,"","","","",""]
["C4-161075","Discussion on status of MONTE work","Huawei","Peter Schmitt",13753,"discussion","","Discussion","Status and open issuess on MONTE","","19","7.1.9","Monitoring Enhancements CT aspects [MONTE-CT]",10750,"revised","2016-01-29T12:42:56.407","2016-02-01T12:31:29.263","","C4-161203","Rel-13","","","MONTE-CT","","","","","","","","",""]
["C4-161076","Pseudo-CR on cleanup of 29.128","Huawei","Peter Schmitt",13753,"pCR","","Decision","Before sending a TS for approval  clause 3 needs to be reduced to the changed clauses.\n Some AVP got AVP codes which need to be introduced.","","19","7.1.9","Monitoring Enhancements CT aspects [MONTE-CT]",10760,"revised","2016-01-29T12:42:56.420","2016-02-01T12:31:29.310","","C4-161288","Rel-13","29.128","1.0.0","MONTE-CT","","",null,"","","","","",""]
["C4-161077","AVAILABILITY_AFTER_DDN_FAILURE reporting","Huawei","Peter Schmitt",13753,"CR","","Decision","It is clarified that the reporting of availability after DDN failure the Monitoring-Type AVP shall be set to AVAILABILITY_AFTER_DDN_FAILURE in the Monitoring-Event-Report AVP.\nA reference to RFC3588 is corrected.","","19","7.1.9","Monitoring Enhancements CT aspects [MONTE-CT]",10770,"revised","2016-01-29T12:42:56.420","2016-02-01T12:31:29.340","","C4-161348","Rel-13","29.336","13.2.0","MONTE-CT","0037","","B",null,"","","","",""]
["C4-161078","Reporting of overload by the SCEF","Huawei","Peter Schmitt",13753,"CR","","Decision","Add ovedrload  control AVPs in RIA command.","","19","7.1.9","Monitoring Enhancements CT aspects [MONTE-CT]",10780,"withdrawn","2016-01-29T12:42:56.593","2016-02-01T12:31:29.370","","","Rel-13","29.336","13.2.0","MONTE-CT","0038","","B",null,"","","","",""]
["C4-161079","Clarification on usage of P and T needs","Huawei","Peter Schmitt",13753,"CR","","Decision","Remove  Editor's Note","","19","7.1.9","Monitoring Enhancements CT aspects [MONTE-CT]",10790,"revised","2016-01-29T12:42:56.670","2016-02-01T12:31:29.417","","C4-161350","Rel-13","23.008","13.3.0","MONTE-CT","0477","","B",null,"","","","",""]
["C4-161080","Pseudo-CR on  overload","Huawei","Peter Schmitt",13753,"pCR","","Decision","At the last meeting  the annex describing overload reporting by SCEF was agreed but the messages were not updated. The  AVPs to report overload are added to Reporting-Information-Answer command.","","19","7.1.9","Monitoring Enhancements CT aspects [MONTE-CT]",10800,"revised","2016-01-29T12:42:56.763","2016-02-01T12:31:29.450","","C4-161352","Rel-13","29.128","1.0.0","MONTE-CT","","",null,"","","","","",""]
["C4-161081","HSS restart MONTE impacts","Huawei","Peter Schmitt",13753,"CR","","Decision","The requirement is added that an HSS shall send a reset command to an SCEF after its restart.","","19","7.1.9","Monitoring Enhancements CT aspects [MONTE-CT]",10810,"revised","2016-01-29T12:42:56.780","2016-02-01T12:31:29.497","","C4-161354","Rel-13","23.007","13.3.0","MONTE-CT","0329","","B",null,"","","","",""]
["C4-161082","Restart of SCEF","Huawei","Peter Schmitt",13753,"CR","","Decision","A procedure description is added how to traet the sceanrio of SCEF restart.","","19","7.1.9","Monitoring Enhancements CT aspects [MONTE-CT]",10820,"revised","2016-01-29T12:42:56.857","2016-02-01T12:31:29.527","","C4-161358","Rel-13","23.007","13.3.0","MONTE-CT","0330","","B",null,"","","","",""]
["C4-161083","SCEF and HSS Restart","Huawei","Peter Schmitt",13753,"CR","","Decision","Introduce Reset procedure and the command pair reset requestand reset answer \n\nIntroduce new error cause DIAMETER_ERROR_SCEF_RERENCE_ID_DOES_NOT_EXIST for SCEF restart.","","19","7.1.9","Monitoring Enhancements CT aspects [MONTE-CT]",10830,"revised","2016-01-29T12:42:56.950","2016-02-01T12:31:29.557","","C4-161454","Rel-13","29.336","13.2.0","MONTE-CT","0039","","B",null,"","","","",""]
["C4-161084","Reporting of the start and stop of the reporting of monitoring events","Huawei, Cisco Systems Inc","Peter Schmitt",13753,"CR","","Decision","","","19","7.1.9","Monitoring Enhancements CT aspects [MONTE-CT]",10840,"revised","2016-01-29T12:42:57.047","2016-02-01T12:31:29.590","","C4-161359","Rel-13","29.336","13.2.0","MONTE-CT","0040","","B",null,"","","","",""]
["C4-161085","Correction of  AVP code and new AVP assignment","Huawei","Peter Schmitt",13753,"CR","","Decision","","","19","7.1.9","Monitoring Enhancements CT aspects [MONTE-CT]",10850,"revised","2016-01-29T12:42:57.107","2016-02-01T12:31:29.620","","C4-161286","Rel-13","29.230","13.3.0","MONTE-CT","0505","","B",null,"","","","",""]
["C4-161086","Reporting of  Monitoring update result","Huawei","Peter Schmitt",13753,"CR","","Decision","Added missing part from CR0029 (which was agreed but mistaken as CR0032 in CT4#70) approved at CT#70.\nEnhance ProSe Direct Discovery Authorization to support reporting of the outcome of Monitoring update in local PLMN to the HPLMN.\nA new discovery type","","39","7.2.7","CT aspects of enhancements to Proximity-based Services extensions (CT1) [eProSe-Ext-CT]",10860,"revised","2016-01-29T12:42:57.200","2016-02-01T16:03:59.717","","C4-161243","Rel-13","29.345","13.0.0","eProSe-Ext-CT","0036","","B",null,"","","","",""]
["C4-161087","Corrections on TS numbers","Huawei","Peter Schmitt",13753,"CR","","Decision","29.343 [35] is changed to 29.217 [35];\n29.254 [38] is changeded to 29.154 [38].","","49","7.3.2","Diameter 29.230 CRs [TEI13]",10870,"revised","2016-01-29T12:42:57.280","2016-02-01T12:31:29.653","","C4-161444","Rel-13","29.230","13.3.0","TEI13","0506","","F",null,"","","","",""]
["C4-161088","Introduction of AAA-1 interface","Huawei","Peter Schmitt",13753,"CR","","Decision","","","43","7.2.11","Mission Critical Push To Talk over LTE protocol aspects (CT1) [MCPTT-CT]",10880,"revised","2016-01-29T13:47:26.663","2016-02-01T12:31:29.683","C4-160021","C4-161244","Rel-13","29.228","13.0.0","MCPTT-CT","0661","2","B",null,"","","","",""]
["C4-161089","Data returned in IMSPublicIdentity correction, new EnhancedPublicIdentifiers class","Ericsson","Maria-Cruz Bartolome",44824,"CR","","","Description of what data IMSPublicIdentity shall include depends on Requested Identity Set information element value. Description included now into the Requested Identity Set information element is moved to the IMSPublicIdentity, where the wrong descripti","","54","7.3.7","IMS [TEI13]",10890,"revised","2016-01-29T18:30:50.337","2016-02-01T14:44:53.930","","C4-161263","Rel-13","29.328","13.3.0","TEI13","0543","","F",null,"","","","",""]
["C4-161090","De-registration of emergency registration correction","Ericsson","Maria-Cruz Bartolome",44824,"CR","","","“entities” is replaced by “identities”","","54","7.3.7","IMS [TEI13]",10900,"agreed","2016-01-29T18:55:26.913","2016-02-01T14:45:43.757","","","Rel-13","29.228","13.0.0","TEI13","0662","","F","CP-160046","","","","",""]
["C4-161091","Local Time Zone for CS retrieval","Ericsson","Maria-Cruz Bartolome",44824,"CR","","","Local Time Zone is included as part of the information that may be returned in the Sh-Pull Response when Location Information for CS is requested.\n\nClarification in the description of the Local Time Zone information for EPS and TWAN, to describe that it","","54","7.3.7","IMS [TEI13]",10910,"revised","2016-01-29T18:58:45.233","2016-02-01T14:45:43.723","","C4-161387","Rel-13","29.328","13.3.0","TEI13","0544","","F",null,"","","","",""]
["C4-161092","Remove the default access AVP","Huawei","Youyang Yu",46021,"CR","","","Delete the default access AVP defined in Diameter messages.","","38","7.2.6","IP Flow Mobility support for S2a and S2b Interfaces on stage 3 (CT1) [NBIFOM]",10920,"agreed","2016-01-30T09:36:54.127","2016-02-01T07:22:54.860","","","Rel-13","29.273","13.2.0","NBIFOM-CT","0446","","F","CP-160035","","","","",""]
["C4-161093","Remove the default access AVP","Huawei","Youyang Yu",46021,"CR","","","Remove the default access AVP from 3GPP specific AVP table 7.1.","","38","7.2.6","IP Flow Mobility support for S2a and S2b Interfaces on stage 3 (CT1) [NBIFOM]",10930,"agreed","2016-01-30T09:36:54.220","2016-02-01T07:22:54.907","","","Rel-13","29.230","13.3.0","NBIFOM-CT","0507","","F","CP-160035","","","","",""]
["C4-161094","Update the reference for NBIFOM container","Huawei","Youyang Yu",46021,"CR","","","1)\tAdd NBIFOM stage 3 reference TS 24.161.\n2)Change the reference from TS 23.161 to TS 24.161.","","38","7.2.6","IP Flow Mobility support for S2a and S2b Interfaces on stage 3 (CT1) [NBIFOM]",10940,"agreed","2016-01-30T09:36:54.297","2016-02-01T07:22:54.937","","","Rel-13","29.274","13.4.0","NBIFOM-CT","1682","","F","CP-160035","","","","",""]
["C4-161095","Specific AVP codes for NBIFOM","Huawei","Youyang Yu",46021,"CR","","","Add 3GPP specific AVP codes defined in TS 29.212.","","38","7.2.6","IP Flow Mobility support for S2a and S2b Interfaces on stage 3 (CT1) [NBIFOM]",10950,"agreed","2016-01-30T09:36:54.377","2016-02-01T07:22:54.970","","","Rel-13","29.230","13.3.0","NBIFOM-CT","0508","","F","CP-160035","","","","",""]
["C4-161096","Add cause values to TWAN mapping table","Huawei","Youyang Yu",46021,"CR","","","Delete not applicable lines.\nChange some FFS to NA.","","95","8.3.1","GTP and PMIP [TEI12]",10960,"revised","2016-01-30T09:36:54.453","2016-02-01T07:22:55.017","","C4-161356","Rel-12","29.274","12.11.0","TEI12","1683","","F",null,"","","","",""]
["C4-161097","Add cause values to TWAN mapping table","Huawei","Youyang Yu",46021,"CR","","","Change FFS to the corresponding cause values.","","95","8.3.1","GTP and PMIP [TEI12]",10970,"revised","2016-01-30T09:36:54.533","2016-02-01T07:22:55.047","","C4-161357","Rel-13","29.274","13.4.0","TEI12","1684","","F",null,"","","","",""]
["C4-161098","Extension on TWAN-S2a-Failure-Cause","Huawei","Youyang Yu",46021,"CR","","","Add “user authentication failed” and “PDN connection does not exist” to TWAN-S2a-Failure-Cause.","","50","7.3.3","EPS AAA interfaces [TEI13]",10980,"agreed","2016-01-30T09:36:54.640","2016-02-01T07:22:55.077","","","Rel-13","29.273","13.2.0","TEI13","0447","","F","CP-160042","","","","",""]
["C4-161099","Authorize the UE requested APN","Huawei","Youyang Yu",46021,"CR","","","1)\tClarify that the APN included in APN configuration data shall be explicitly subscribed APNs, or wildcard APN.\n2)\tClarify the ePDG shall utilize the downloaded APN configuration data to authorize the UE requested APN if received.","","50","7.3.3","EPS AAA interfaces [TEI13]",10990,"revised","2016-01-30T09:36:54.737","2016-02-01T07:22:55.110","","C4-161312","Rel-13","29.273","13.2.0","TEI13","0448","","F",null,"","","","",""]
["C4-161100","SCS Identity Format","Hewlett-Packard Enterprise","Anders Askerup",26315,"discussion","","Discussion","CT4 should decide the solution among 2 described solutions \nHewlett Packard Enterprise has a preference for the solution b) and has submitted a CR to TS 29.336. Hewlett Packard Enterprise is suggesting that th SCS identity is defined in the international","","119","9.13.2","Reach ability Aspects of SIMTC [SIMTC-Reach]",11000,"noted","2016-01-30T18:20:48.277","2016-01-31T19:16:14.767","","","Rel-11","","","","","","","","","","","",""]
["C4-161101","SCS identity format","Hewlett-Packard Enterprise","Anders Askerup",26315,"CR","","Agreement","","","119","9.13.2","Reach ability Aspects of SIMTC [SIMTC-Reach]",11010,"noted","2016-01-30T18:39:46.973","2016-01-31T19:16:14.813","","C4-164127","Rel-11","29.336","11.2.0","SIMTC-Reach","0041","","F",null,"","","","",""]
["C4-161102","SCS identity format","Hewlett-Packard Enterprise","Anders Askerup",26315,"CR","","Agreement","","","119","9.13.2","Reach ability Aspects of SIMTC [SIMTC-Reach]",11020,"postponed","2016-01-30T18:45:08.597","2016-01-31T19:16:14.843","","C4-164129","Rel-12","29.336","12.5.0","SIMTC-Reach","0042","","A",null,"","","","",""]
["C4-161103","SCS identity format","Hewlett-Packard Enterprise","Anders Askerup",26315,"CR","","Agreement","","","119","9.13.2","Reach ability Aspects of SIMTC [SIMTC-Reach]",11030,"postponed","2016-01-30T18:49:05.357","2016-01-31T19:16:14.877","","C4-164130","Rel-13","29.336","13.2.0","SIMTC-Reach","0043","","A",null,"","","","",""]
["C4-161104","Encoding of  IP-SM-GW Number","Hewlett-Packard Enterprise","Anders Askerup",26315,"CR","","Agreement","","","162","10.18","IMS [TEI8, TEI9]",11040,"revised","2016-01-30T22:00:26.290","2016-02-01T15:46:37.563","","C4-161386","Rel-8","29.328","8.18.0","TEI8","0545","","F",null,"","","","",""]
["C4-161105","Encoding of  IP-SM-GW Number","Hewlett-Packard Enterprise","Anders Askerup",26315,"CR","","Agreement","","","162","10.18","IMS [TEI8, TEI9]",11050,"withdrawn","2016-01-30T22:04:32.973","2016-02-01T15:46:37.597","","","Rel-9","29.328","9.16.0","TEI8","0546","","A",null,"","","","",""]
["C4-161106","Encoding of  IP-SM-GW Number","Hewlett-Packard Enterprise","Anders Askerup",26315,"CR","","Agreement","","","162","10.18","IMS [TEI8, TEI9]",11060,"withdrawn","2016-01-30T22:09:42.397",null,"","","Rel-9","29.328","9.16.0","TEI8","0547","","A",null,"","","","",""]
["C4-161107","Encoding of  IP-SM-GW Number","Hewlett-Packard Enterprise","Anders Askerup",26315,"CR","","Agreement","","","162","10.18","IMS [TEI8, TEI9]",11070,"withdrawn","2016-01-30T22:14:06.363","2016-02-01T15:46:37.643","","","Rel-10","29.328","10.14.0","TEI8","0548","","A",null,"","","","",""]
["C4-161108","Encoding of  IP-SM-GW Number","Hewlett-Packard Enterprise","Anders Askerup",26315,"CR","","Agreement","","","162","10.18","IMS [TEI8, TEI9]",11080,"withdrawn","2016-01-30T22:17:10.113","2016-02-01T15:46:37.673","","","Rel-11","29.328","11.15.0","TEI8","0549","","A",null,"","","","",""]
["C4-161109","Encoding of  IP-SM-GW Number","Hewlett-Packard Enterprise","Anders Askerup",26315,"CR","","Agreement","","","162","10.18","IMS [TEI8, TEI9]",11090,"revised","2016-01-30T22:21:32.627","2016-02-01T15:46:37.720","","C4-161389","Rel-12","29.328","12.10.0","TEI8","0550","","A",null,"","","","",""]
["C4-161110","Encoding of  IP-SM-GW Number","Hewlett-Packard Enterprise","Anders Askerup",26315,"CR","","Agreement","","","162","10.18","IMS [TEI8, TEI9]",11100,"revised","2016-01-30T22:36:43.630","2016-02-01T15:46:37.750","","C4-161390","Rel-13","29.328","13.3.0","TEI8","0551","","A",null,"","","","",""]
["C4-161111","IP-SW-GW number format","Hewlett-Packard Enterprise","Anders Askerup",26315,"CR","","Agreement","","","162","10.18","IMS [TEI8, TEI9]",11110,"withdrawn","2016-01-30T22:54:28.403","2016-02-01T15:46:37.797","","","Rel-8","23.008","8.13.0","TEI8","0478","","F",null,"","","","",""]
["C4-161112","IP-SW-GW number format","Hewlett-Packard Enterprise","Anders Askerup",26315,"CR","","Agreement","","","162","10.18","IMS [TEI8, TEI9]",11120,"withdrawn","2016-01-30T22:56:15.870","2016-02-01T15:46:37.830","","","Rel-9","23.008","9.7.0","TEI8","0479","","A",null,"","","","",""]
["C4-161113","IP-SW-GW number format","Hewlett-Packard Enterprise","Anders Askerup",26315,"CR","","Agreement","","","162","10.18","IMS [TEI8, TEI9]",11130,"withdrawn","2016-01-30T23:03:45.287","2016-02-01T15:46:37.860","","","Rel-10","23.008","10.7.0","TEI8","0480","","A",null,"","","","",""]
["C4-161114","IP-SW-GW number format","Hewlett-Packard Enterprise","Anders Askerup",26315,"CR","","Agreement","","","162","10.18","IMS [TEI8, TEI9]",11140,"withdrawn","2016-01-30T23:07:37.307","2016-02-01T15:46:37.907","","","Rel-11","23.008","11.12.0","TEI8","0481","","A",null,"","","","",""]
["C4-161115","IP-SW-GW number format","Hewlett-Packard Enterprise","Anders Askerup",26315,"CR","","Agreement","","","162","10.18","IMS [TEI8, TEI9]",11150,"revised","2016-01-30T23:10:37.297","2016-02-01T15:46:37.953","","C4-161391","Rel-12","23.008","12.9.0","TEI8","0482","","A",null,"","","","",""]
["C4-161116","IP-SW-GW number format","Hewlett-Packard Enterprise","Anders Askerup",26315,"CR","","Agreement","","","162","10.18","IMS [TEI8, TEI9]",11160,"revised","2016-01-30T23:16:35.830","2016-02-01T15:46:37.987","","C4-161392","Rel-13","23.008","13.3.0","TEI8","0483","","A",null,"","","","",""]
["C4-161117","Inter-PLMN discovery transmission support","Qualcomm Incorporated","Zhibin Wu",49530,"CR","","Agreement","1.\t Designation of the announcing PLMN was changed from “VPLMN” to “VPLMN or a PLMN other than the HPLMN/VPLMN” to account for the fact that the UE can announce in a PLMN that is not its registered PLMN\n2. Editorial changes were made in subclause 5.3.3 t","","39","7.2.7","CT aspects of enhancements to Proximity-based Services extensions (CT1) [eProSe-Ext-CT]",11170,"revised","2016-01-31T01:26:02.423","2016-01-31T23:12:26.637","","C4-161375","Rel-13","29.345","13.0.0","eProSe-Ext-CT","0037","","F",null,"","","","",""]
["C4-161118","Adding security related parameters for restricted ProSe direct discovery authorization","Qualcomm Incorporated","Zhibin Wu",49530,"CR","","Agreement","1.\tAdded DUCK, DUIK and DUSK to the abbreviations list. \n2.\tUpdated the procedure description for discovery authorization to include the sending and receiving of security materials in both the HPLMN ProSe Function and the peer ProSe Function(s).\n2. Adde","","39","7.2.7","CT aspects of enhancements to Proximity-based Services extensions (CT1) [eProSe-Ext-CT]",11180,"revised","2016-01-31T01:30:50.710","2016-01-31T23:12:26.590","","C4-161376","Rel-13","29.345","13.0.0","eProSe-Ext-CT","0038","","F",null,"","","","",""]
["C4-161119","Support open discovery with application-controlled extension","Qualcomm Incorporated","Zhibin Wu",49530,"CR","","Agreement","1.\tUpdated the discovery authorization procedure to indicate that the prefix/suffix may be included for announce authorization request.\n2.\tUpdated the existing AVPs and defined a new AVP to enable the supporting parameters to be used in the Diameter comm","","39","7.2.7","CT aspects of enhancements to Proximity-based Services extensions (CT1) [eProSe-Ext-CT]",11190,"revised","2016-01-31T01:37:50.080","2016-01-31T23:12:26.543","","C4-161377","Rel-13","29.345","13.0.0","eProSe-Ext-CT","0039","","F",null,"","","","",""]
["C4-161120","Discovery update for open and restricted ProSe direct discovery","Qualcomm Incorporated","Zhibin Wu",49530,"CR","","Agreement","The procedure description for discovery authorization were updated to cover the discovery update procedures.","","39","7.2.7","CT aspects of enhancements to Proximity-based Services extensions (CT1) [eProSe-Ext-CT]",11200,"agreed","2016-01-31T01:47:43.860","2016-01-31T23:12:26.387","","","Rel-13","29.345","13.0.0","eProSe-Ext-CT","0040","","F","CP-160036","","","","",""]
["C4-161121","Octet number in MM context IE","Huawei","Xiaoyan Shi",57110,"CR","","Agreement","Correct the octet number of \"Length of Voice Domain Preference and UE's Usage Setting\" by using a new value \"w\"","","48","7.3.1","GTP and PMIP [TEI13]",11210,"agreed","2016-01-31T13:18:32.893","2016-01-31T13:27:09.840","","","Rel-13","29.274","13.4.0","TEI13","1685","","F","CP-160038","","","","",""]
["C4-161122","Protocol Type in Create Session Request","Huawei","Xiaoyan Shi",57110,"CR","","Agreement","Change the flag name from \"S5/S8 Protocol Type\" to \"Protocol Type\" and clarify that the flag is set to 1 when chosen PMIP.","","48","7.3.1","GTP and PMIP [TEI13]",11220,"revised","2016-01-31T13:18:33","2016-01-31T13:27:09.887","","C4-161349","Rel-13","29.274","13.4.0","TEI13","1686","","F",null,"","","","",""]
["C4-161123","Correct the partial failure handling on SGW","Huawei","Xiaoyan Shi",57110,"CR","","Agreement","1.\tAdd a restriction on that the SGW only send/forward the FQ-CSID if the MME supports partial failure handling during PDN connection establishment;\n2.\tAdd a note to define the SGW behaviours during the RAU/HO to S4-SGSN procedure.","","51","7.3.4","Restoration Procedures [TEI13]",11230,"revised","2016-01-31T13:18:33.080","2016-01-31T13:27:09.920","","C4-161361","Rel-13","23.007","13.3.0","TEI13","0331","","F",null,"","","","",""]
["C4-161124","Encoding of  SC Address","Hewlett-Packard Enterprise","Anders Askerup",26315,"CR","","Agreement","","","162","10.18","IMS [TEI8, TEI9]",11240,"revised","2016-01-31T17:26:55.117","2016-02-01T15:36:56.267","","C4-161394","Rel-10","29.328","10.14.0","TEI10","0552","","F",null,"","","","",""]
["C4-161125","Encoding of  SC Address","Hewlett-Packard Enterprise","Anders Askerup",26315,"CR","","Agreement","","","162","10.18","IMS [TEI8, TEI9]",11250,"revised","2016-01-31T17:29:30.337","2016-02-01T15:36:56.297","","C4-161396","Rel-11","29.328","11.15.0","TEI10","0553","","A",null,"","","","",""]
["C4-161126","Encoding of  SC Address","Hewlett-Packard Enterprise","Anders Askerup",26315,"CR","","Agreement","","","162","10.18","IMS [TEI8, TEI9]",11260,"revised","2016-01-31T17:32:36.857","2016-02-01T15:36:56.343","","C4-161397","Rel-12","29.328","12.10.0","TEI10","0554","","A",null,"","","","",""]
["C4-161127","Encoding of  SC Address","Hewlett-Packard Enterprise","Anders Askerup",26315,"CR","","Agreement","","","162","10.18","IMS [TEI8, TEI9]",11270,"revised","2016-01-31T17:40:41.097","2016-02-01T15:36:56.373","","C4-161398","Rel-13","29.328","13.3.0","TEI10","0555","","A",null,"","","","",""]
["C4-161128","Configure Monitoring Event to Multiple Serving Nodes","ZTE","Zhijun Li",39295,"CR","","Approval","If a UE is registered to both SGSN and MME, the HSS needs to send Monitoring Event to each serving nodes.","","19","7.1.9","Monitoring Enhancements CT aspects [MONTE-CT]",11280,"revised","2016-02-01T02:31:53.757","2016-02-01T09:28:18.007","","C4-161419","Rel-13","29.272","13.4.0","MONTE-CT","0621","","B",null,"","","","",""]
["C4-161129","Inform the HSS of remaining number of reports","ZTE","Zhijun Li",39295,"CR","","Approval","To limit the maximum number of reports, the SGSN/MME needs to count the reports and send the remaining number of reports to the HSS when sending PUR / CLA message.","","19","7.1.9","Monitoring Enhancements CT aspects [MONTE-CT]",11290,"withdrawn","2016-02-01T02:31:53.850","2016-02-01T09:28:18.037","","","Rel-13","29.272","13.4.0","MONTE-CT","0622","","B",null,"","","","",""]
["C4-161130","Count and Stop Monitoring Event Reports at SCEF","ZTE","Zhijun Li",39295,"CR","","Approval","To limit the maximum number of Monitoring event reports, the SCEF shall count the received reports and stop the Monitoring events reporting when the received reports reach the maximum number.","","19","7.1.9","Monitoring Enhancements CT aspects [MONTE-CT]",11300,"revised","2016-02-01T02:31:53.943","2016-02-01T09:28:18.083","","C4-161423","Rel-13","29.336","13.2.0","MONTE-CT","0044","","B",null,"","","","",""]
["C4-161131","Allow SMS for NB-IoT UE without Combined Attach","ZTE","Zhijun Li",39295,"CR","","Approval","To provide SMS service to NB-IoT UE, the MME shall allow the EPS Attach request from NB-IoT UE with the SMS request indication, and register to the HSS for SMS.","","46","7.2.14","CIoT-CT (CT1)  [CIoT-CT]",32000,"revised","2016-02-01T02:31:54.020","2016-02-04T09:44:47.440","","C4-161323","Rel-13","29.272","13.4.0","CIoT-CT","0623","","B",null,"","","","",""]
["C4-161132","Clarification on Reporting Cell ID for NB-IoT","ZTE","Zhijun Li",39295,"CR","","Approval","It is clarified that the current ECGI IE is also used to carry the Cell ID of NB-IoT RAT.","","46","7.2.14","CIoT-CT (CT1)  [CIoT-CT]",32500,"not pursued","2016-02-01T02:31:54.113","2016-02-04T09:44:47.473","","","Rel-13","29.272","13.4.0","CIoT-CT","0624","","B",null,"","","","",""]
["C4-161133","P-CSCF_RESELECTION_SUPPORT Private Status Type","ZTE/Joy","Xingyue Zhou",42680,"CR","","Agreement","Revise the description of the P-CSCF_RESELECTION_SUPPORT in the Create Session Request.","","13","7.1.3","P-CSCF restoration enhancements with WLAN [PCSCF_RES_WLAN]",11330,"agreed","2016-02-01T02:46:06.787","2016-02-03T10:03:30.203","","","Rel-13","29.274","13.4.0","PCSCF_RES_WLAN","1687","","F","CP-160025","","","","",""]
["C4-161134","Incorrect use of the term \"full hexadecimal representation\" to mean binary encoding","Oracle Corporation","Tarek Abou-assali",58502,"CR","","Approval","The use of the \"Full hexadecimal representation\" in certain IEs to mean \"binary encoding\" is misleading and can result in erroneous implementations.","","48","7.3.1","GTP and PMIP [TEI13]",10001,"revised","2016-02-01T03:47:00.797","2016-02-01T04:28:18.730","","C4-161342","Rel-13","29.274","13.4.0","TEI13","1688","","F",null,"","","","",""]
["C4-161135","Incorrect use of the term \"full hexadecimal representation\" to mean binary encoding","Oracle Corporation","Tarek Abou-assali",58502,"CR","","Approval","The use of the \"Full hexadecimal representation\" term in certain IEs to mean \"binary encoding\" is misleading and can result in erroneous implementations.","","48","7.3.1","GTP and PMIP [TEI13]",10010,"revised","2016-02-01T04:15:02.933","2016-02-01T04:28:18.687","","C4-161343","Rel-13","29.060","13.3.0","TEI13","1032","","F",null,"","","","",""]
["C4-161136","Adjacent PLMNs","Ericsson","Jesus De Gregorio",40423,"CR","","","Introduce the Adjacent-PLMNs AVP in the ABNF of the ULR command.","","53","7.3.6","Diameter based Interfaces [TEI13]",11360,"agreed","2016-02-01T08:07:06.593","2016-02-01T15:14:50.447","","","Rel-13","29.272","13.4.0","TEI13","0625","","F","CP-160045","","","","",""]
["C4-161137","Invocation of Alert procedure by HSS after ULR","Ericsson","Jesus De Gregorio",40423,"CR","","","Specify that the HSS shall send Alert to SMS-IWMSC upon receipt of ULR, when the appropriate conditions apply with regard to the UE.","","53","7.3.6","Diameter based Interfaces [TEI13]",11370,"revised","2016-02-01T08:10:49.187","2016-02-01T15:14:50.477","","C4-161447","Rel-13","29.272","13.4.0","TEI13","0626","","F",null,"","","","",""]
["C4-161138","Handover to Non-3GPP Access Not Allowed","Ericsson","Jesus De Gregorio",40423,"CR","","","Clarify the description of the “HO-To-Non-3GPP-Access not allowed” bit to indicate that it is a consequence of the user not being allowed to get service via non-3GPP access.","","52","7.3.5","Addressing and Subscriber Data Handling [TEI13]",11380,"revised","2016-02-01T08:14:07.697","2016-02-01T15:14:50.507","","C4-161309","Rel-13","23.008","13.3.0","TEI13","0484","","F",null,"","","","",""]
["C4-161139","Implementation Error in CR#29","Ericsson, Nextnav, MCC","Jesus De Gregorio",40423,"CR","","","- Revert the change of “GNSS Positioning Method and Usage” to its original form, in table 7.4.13-1.\n- Add the missing row defining maxAddPosSet in table 7.4.13-2.","","31","7.1.21","Indoor Positioning Enhancements for UTRA and E-UTRA [UTRA_LTE_iPos_enh-CT]",11390,"agreed","2016-02-01T08:17:53.850","2016-02-01T15:14:50.540","","","Rel-13","29.171","13.1.0","UTRA_LTE_iPos_enh-CT","0034","","F","CP-160024","","","","",""]
["C4-161140","Change of type of Monitoring-Duration AVP to represent an absolute time","Ericsson","Jesus De Gregorio",40423,"CR","","","Change the definition and AVP type of Monitoring-Duration AVP, from Unsigned32 to Time data type.","","19","7.1.9","Monitoring Enhancements CT aspects [MONTE-CT]",11400,"revised","2016-02-01T08:20:51.610","2016-02-01T15:14:50.570","","C4-161428","Rel-13","29.336","13.2.0","MONTE-CT","0045","","F",null,"","","","",""]
["C4-161141","Change of type of Monitoring-Duration AVP to represent an absolute time","Ericsson","Jesus De Gregorio",40423,"CR","","","Change the definition and AVP type of Monitoring-Duration AVP, from Unsigned32 to Time data type.","","19","7.1.9","Monitoring Enhancements CT aspects [MONTE-CT]",12407,"agreed","2016-02-01T08:23:03.693","2016-02-01T15:14:50.600","","","Rel-13","29.230","13.3.0","MONTE-CT","0509","","F","CP-160029","","","","",""]
["C4-161142","AVPs for the Rx Diameter application","Ericsson","Jesus De Gregorio",40423,"CR","","","- Allocate AVP codes defined in 29.214 in the reserved range for that TS.\n- Allocate a new transient error code in the reserved range for that TS.","","49","7.3.2","Diameter 29.230 CRs [TEI13]",11420,"agreed","2016-02-01T08:26:17.460","2016-02-01T15:14:50.647","","","Rel-13","29.230","13.3.0","TEI13","0510","","B","CP-160041","","","","",""]
["C4-161143","CT4 impacts for CIoT","Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Nokia Networks","Bruno Landais",68755,"discussion","","Discussion","List of stage 2 CRs and CT4 impacts.","","46","7.2.14","CIoT-CT (CT1)  [CIoT-CT]",15001,"noted","2016-02-01T08:26:47.460","2016-02-05T16:48:30.873","","","","","","","","","","","","","","",""]
["C4-161144","GTP-U tunneling over S11","Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Nokia Networks","Bruno Landais",68755,"discussion","","Decision","MO/MT data transport in control plane (SGi based) requires tunneling of user plane data between the MME and SGW over the S11 interface. This contribution discusses possible options for setting up the S11-U tunnel between the MME and SGW, as well as Error","","46","7.2.14","CIoT-CT (CT1)  [CIoT-CT]",37000,"noted","2016-02-01T08:26:47.460","2016-02-05T16:48:30.920","","","","","","","","","","","","","","",""]
["C4-161145","S11-U tunneling for MO/MT data transport in control plane (SGi based) - with new S11-U F-TEIDs","Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Nokia Networks","Bruno Landais",68755,"CR","","Approval","Adds support for establishment of GTP-U tunnel over S11, including:\n-\t new MME S11-U F-TEID and S11-U SGW F-TEIDs \n-\t a new S11-U Tunnel Flag (S11TF) to tell the SGW whether to establish an S1-U or S11-U tunnel\n-\t the option for the MME to establish th","","46","7.2.14","CIoT-CT (CT1)  [CIoT-CT]",38000,"revised","2016-02-01T08:26:47.460","2016-02-05T16:48:30.967","","C4-161378","Rel-13","29.274","13.4.0","CIoT-CT","1689","","B",null,"","","","",""]
["C4-161146","RAT-Type extension for NB-IoT","Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Nokia Networks","Bruno Landais",68755,"CR","","Approval","A new RAT-Type value is defined for NB-IoT.\nThe existing RAT-Type value for E-UTRAN denotes a WB-E-UTRAN access.","","46","7.2.14","CIoT-CT (CT1)  [CIoT-CT]",48000,"revised","2016-02-01T08:26:47.553","2016-02-05T16:48:31.043","","C4-161399","Rel-13","29.274","13.4.0","CIoT-CT","1690","","B",null,"","","","",""]
["C4-161147","S11-U tunneling for MO/MT data transport in control plane (SGi based)","Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Nokia Networks","Bruno Landais",68755,"CR","","Approval","Adds support of GTP-U tunneling over S11.","","46","7.2.14","CIoT-CT (CT1)  [CIoT-CT]",40000,"revised","2016-02-01T08:26:47.630","2016-02-05T16:48:31.077","","C4-161379","Rel-13","29.281","13.0.0","CIoT-CT","0074","","B",null,"","","","",""]
["C4-161148","End Marker handling by MME","Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Nokia Networks","Bruno Landais",68755,"CR","","Approval","The MME shall discard End Marker packets received from the SGW.","","46","7.2.14","CIoT-CT (CT1)  [CIoT-CT]",41000,"revised","2016-02-01T08:26:47.723","2016-02-05T16:48:31.123","","C4-161381","Rel-13","29.281","13.0.0","CIoT-CT","0075","","B",null,"","","","",""]
["C4-161149","S11-U Error Indication handling","Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Nokia Networks","Bruno Landais",68755,"CR","","Approval","Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Nokia Networks","","46","7.2.14","CIoT-CT (CT1)  [CIoT-CT]",42000,"revised","2016-02-01T08:26:47.803","2016-02-05T16:48:31.187","","C4-161383, C4-161384","Rel-13","23.007","13.3.0","CIoT-CT","0332","","B",null,"","","","",""]
["C4-161150","S11-U Path Failure handling","Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Nokia Networks","Bruno Landais",68755,"CR","","Approval","The SGW should detect and handle S11-U path failures as specified in subclause 20.3.1. When deleting the bearer context associated with the path in failure, the SGW should only delete the S11-U bearer context.","","46","7.2.14","CIoT-CT (CT1)  [CIoT-CT]",43000,"not pursued","2016-02-01T08:26:47.863","2016-02-05T16:48:31.247","","","Rel-13","23.007","13.3.0","CIoT-CT","0333","","B",null,"","","","",""]
["C4-161151","New Alert procedure from MME/SGSN to SMS-GMSC for MT SMS to UE using eDRX","Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Nokia Networks, Ericsson, Verizon, AT&T, Vodafone","Bruno Landais",68755,"discussion","","Decision","CT4 has specified enhancements for efficient support of MT SMS in the PS domain to UEs using extended idle mode DRX (eDRX). See [1] to [7] (approved at CT#70) and the Annex of this document. \n\nIt was reported that one of these enhancements (SM retransmi","","42","7.2.10","Extended DRX cycle for power consumption optimization (CT1) [eDRX]",11510,"noted","2016-02-01T08:26:47.943","2016-02-01T15:33:54.293","","","","","","","","","","","","","","",""]
["C4-161152","Alert procedure from MME/SGSN to SMS-GMSC for MT SMS to UE using eDRX","Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Nokia Networks, Ericsson, Verizon, AT&T, Vodafone","Bruno Landais",68755,"CR","","Approval","The MME and SGSN alert the SMS-GMSC when the UE originates NAS signalling or moves to another serving node prior to time they requested the SMS-GMSC to retransmit the SM.\n\nThe existing ALR/ALA commands (S6c Application ID) are used over the SGd and Gdd","","42","7.2.10","Extended DRX cycle for power consumption optimization (CT1) [eDRX]",11520,"agreed","2016-02-01T08:26:47.957","2016-02-01T15:33:54.323","","","Rel-13","29.338","13.0.0","eDRX-CT","0019","","B","CP-160030","","","","",""]
["C4-161153","Alert procedure from MME/SGSN to SMS-GMSC for MT SMS to UE using eDRX","Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Nokia Networks, Ericsson, Verizon, AT&T, Vodafone","Bruno Landais",68755,"CR","","Approval","AVP codes are defined for two new AVPs: \n-\tSMS-GMSC-Address\n-\tSMS-GMSC-Alert-Event","","42","7.2.10","Extended DRX cycle for power consumption optimization (CT1) [eDRX]",11530,"agreed","2016-02-01T08:26:48.037","2016-02-01T15:33:54.370","","","Rel-13","29.230","13.3.0","eDRX-CT","0511","","B","CP-160030","","","","",""]
["C4-161154","Alert procedure from MME/SGSN to SMS-GMSC for MT SMS to UE using eDRX","Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Nokia Networks, Ericsson, Verizon, AT&T, Vodafone","Bruno Landais",68755,"CR","","Approval","The MME (via an IWF) and the SGSN alerts the SMS-GMSC when the UE originates NAS signalling or moves to another serving node prior to time they requested the SMS-GMSC to retransmit the SM.","","42","7.2.10","Extended DRX cycle for power consumption optimization (CT1) [eDRX]",11540,"revised","2016-02-01T08:26:48.147","2016-02-01T15:33:54.417","","C4-161271","Rel-13","29.002","13.2.0","eDRX-CT","1202","","B",null,"","","","",""]
["C4-161155","Alert procedure from MME/SGSN to SMS-GMSC for MT SMS to UE using eDRX","Alcatel-Lucent, Alcatel-Lucent Shanghai Bell","Bruno Landais",68755,"CR","","Approval","The Diameter / MAP interworking requirements for the above changes are specified.","","42","7.2.10","Extended DRX cycle for power consumption optimization (CT1) [eDRX]",11550,"agreed","2016-02-01T08:26:48.240","2016-02-05T16:48:31.293","","","Rel-13","29.305","13.1.0","eDRX-CT","0062","","B","CP-160030","","","","",""]
["C4-161156","Correction of CR Implementation on Emergency PDN connection over untrusted WLAN","MCC, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Nokia Networks","Bruno Landais",68755,"CR","","Approval","The CR adds the text from CR 29.273 #0429 which has not been implemented, which requires the 3GPP AAA Server to reject an S6b Authorization request if the requested APN does not pertain to the subscribed APN and the Emergency-Indication AVP is not receive","","41","7.2.9","Support of Emergency services over WLAN Ã¢â‚¬â€œ phase 1 (CT1) [SEW1-CT]",11560,"agreed","2016-02-01T08:26:48.347","2016-02-01T15:33:54.447","","","Rel-13","29.273","13.2.0","SEW1-CT, TEI13","0449","","F","CP-160037","","","","",""]
["C4-161157","ePDG retrieval of WLAN Location Information","Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Nokia Networks","Bruno Landais",68755,"CR","","Approval","The ePDG may initiate an SWm Authorization Request to retrieve the most up to date WLAN Location Information stored at the 3GPP AAA Server and to signal a change of the UE Local IP address to the 3GPP AAA Server.\n\nThe SWm Authorization Answer is expande","","41","7.2.9","Support of Emergency services over WLAN Ã¢â‚¬â€œ phase 1 (CT1) [SEW1-CT]",11570,"revised","2016-02-01T08:26:48.443","2016-02-01T15:33:54.497","","C4-161341","Rel-13","29.273","13.2.0","SEW1-CT, TEI13","0450","","F",null,"","","","",""]
["C4-161158","ePDG retrieval of WLAN Location Information","Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Nokia Networks","Bruno Landais",68755,"CR","","Approval","A new AVP code is defined.","","41","7.2.9","Support of Emergency services over WLAN Ã¢â‚¬â€œ phase 1 (CT1) [SEW1-CT]",11580,"agreed","2016-02-01T08:26:48.550","2016-02-01T15:33:54.527","","","Rel-13","29.230","13.3.0","SEW1-CT, TEI13","0512","","F","CP-160037","","","","",""]
["C4-161159","Use case for inclusion of the RAN/NAS Cause in Delete Bearer Response","Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Nokia Networks","Bruno Landais",68755,"CR","","Approval","A table note is added with a reference to the corresponding use case defined in stage 2.","","48","7.3.1","GTP and PMIP [TEI13]",11590,"agreed","2016-02-01T08:26:48.660","2016-02-01T15:33:54.573","","","Rel-13","29.274","13.4.0","TEI13, SAES","1691","","F","CP-160038","","","","",""]
["C4-161160","GTP-C Load Control - Mix of NAPTR records with \"s\" and \"a\" flags","Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Nokia Networks","Bruno Landais",68755,"CR","","Approval","When using GTP-C load control, the DNS should not be provisioned with a mix of NAPTR records with an \"s\" flag and with an \"a\" flag for a given FQDN.","","48","7.3.1","GTP and PMIP [TEI13]",11600,"revised","2016-02-01T08:26:48.737","2016-02-01T15:33:54.603","","C4-161351","Rel-13","29.303","13.2.0","TEI13, GOCMe","0084","","F",null,"","","","",""]
["C4-161161","Time Zone in MAP-Any-Time-Interrogation","Ericsson","Jesus De Gregorio",40423,"CR","","","Extend the ATI procedure to allow the retrieval of time zone and DST information of the UE.","","55","7.3.8","MAP [TEI13]",11610,"agreed","2016-02-01T08:29:03.957","2016-02-01T15:14:50.680","","","Rel-13","29.002","13.2.0","TEI13","1203","","B","CP-160047","","","","",""]
["C4-161162","Configuration for NIDD procedure over  S6t","Huawei","Peter Schmitt",13753,"CR","","Decision","","","46","7.2.14","CIoT-CT (CT1)  [CIoT-CT]",33000,"revised","2016-02-01T08:30:17.590",null,"","C4-161193","Rel-13","29.336","13.2.0","CIoT-CT","0046","","B",null,"","","","",""]
["C4-161163","Configuration for NIDD procedureover  S6a","Huawei","Peter Schmitt",13753,"CR","","Decision","","","46","7.2.14","CIoT-CT (CT1)  [CIoT-CT]",59000,"withdrawn","2016-02-01T08:30:17.683",null,"","","Rel-13","29.272","13.4.0","CIoT-CT","0627","","B",null,"","","","",""]
["C4-161164","Pseudo-CR on NIDD configuration over T6a","Huawei","Peter Schmitt",13753,"pCR","","Decision","","","46","7.2.14","CIoT-CT (CT1)  [CIoT-CT]",60000,"withdrawn","2016-02-01T08:30:17.777",null,"","","Rel-13","29.128","1.0.0","CIoT-CT","","",null,"","","","","",""]
["C4-161165","Definition of  AVP configuration of NIDD","Huawei","Peter Schmitt",13753,"CR","","Decision","Add AVP definition needed for Authorisation of NIDD.","","46","7.2.14","CIoT-CT (CT1)  [CIoT-CT]",36000,"revised","2016-02-01T08:30:17.777","2016-02-01T16:23:15.590","","C4-161325","Rel-13","29.230","13.3.0","CIoT-CT","0513","","B",null,"","","","",""]
["C4-161166","Storage of data for configuration of NIDD","Huawei","Peter Schmitt",13753,"CR","","Decision","","","46","7.2.14","CIoT-CT (CT1)  [CIoT-CT]",61000,"withdrawn","2016-02-01T08:30:17.870",null,"","","Rel-13","23.008","13.3.0","CIoT-CT","0485","","B",null,"","","","",""]
["C4-161167","PDN Connection Charging ID","Ericsson, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell","Yong Yang",42295,"CR","","","A new PDN connection charging ID IE is included in the Create Session Response message and Modify Bearer Response message.","","38","7.2.6","IP Flow Mobility support for S2a and S2b Interfaces on stage 3 (CT1) [NBIFOM]",11670,"agreed","2016-02-01T09:24:41.587","2016-02-01T16:08:42.837","","","Rel-13","29.274","13.4.0","NBIFOM-CT","1692","","F","CP-160035","","","","",""]
["C4-161168","Transferring AAA identifier from the ePDG to the PGW","Ericsson","Yong Yang",42295,"CR","","","A new IE AAA server Identifer is included in the Create Session Request message","","48","7.3.1","GTP and PMIP [TEI13]",11680,"revised","2016-02-01T09:28:58.987","2016-02-01T16:08:42.887","","C4-161276","Rel-13","29.274","13.4.0","TEI13","1693","","F",null,"","","","",""]
["C4-161169","Clarification on the use of UE Usage Type","Ericsson, NTT DOCOMO","Yong Yang",42295,"CR","","","Clarify the Usage Type used during DNS procedure is mapped from the UE Usage Type in the subscription, based on the serving network operator configured policies.","","28","7.1.18","Dedicated Core Networks [DECOR-CT]",11690,"revised","2016-02-01T09:33:25.293","2016-02-01T16:08:42.917","","C4-161364","Rel-13","29.303","13.2.0","DECOR-CT","0085","","B",null,"","","","",""]
["C4-161170","Cleanup of the editor's notes for reporting remote UE","Ericsson","Yong Yang",42295,"CR","","","Remove the editor's notes, and define the encoding of Remote UE ID, and refer to TS 24.301 for the encoding of Remote UE IP Info.","","39","7.2.7","CT aspects of enhancements to Proximity-based Services extensions (CT1) [eProSe-Ext-CT]",11700,"revised","2016-02-01T09:40:07.300","2016-02-01T16:08:42.963","","C4-161385","Rel-13","29.274","13.4.0","eProSe-Ext-CT","1694","","B",null,"","","","",""]
["C4-161171","Comprehension requirement for PDCP PDU Number","Ericsson","Yong Yang",42295,"CR","","","Add an exception that the SGW, when receives a G-PDU with a extension header PDCP PDU number, i.e. a G-PDU containing a Next Extension Hearer Field set to the value \"1100 0000\", the SGW shall consider this extension header as 'comprehension not required'.","","48","7.3.1","GTP and PMIP [TEI13]",11710,"revised","2016-02-01T09:42:37.140","2016-02-01T16:08:42.993","","C4-161355","Rel-13","29.281","13.0.0","TEI13","0076","","F",null,"","","","",""]
["C4-161172","Delay Tolerant Connection Indication","Ericsson, MCC","Yong Yang",42295,"CR","","","The DTCI definition is updated and the editorial note is removed.","","42","7.2.10","Extended DRX cycle for power consumption optimization (CT1) [eDRX]",11720,"revised","2016-02-01T09:45:48.317","2016-02-01T16:08:43.040","","C4-161338","Rel-13","29.060","13.3.0","eDRX-CT","1033","","B",null,"","","","",""]
["C4-161173","Triggering MT SM retransmission by the SMS GMSC to a UE in eDRX during inter MME/SGSN mobility procedure for GTPv1","Ericsson, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Vodafone","Yong Yang",42295,"CR","","","A new indication – Pending MT Short Message Indication (PMTSMI) is introduced in the SGSN Context Response and Forward Relocation Request message; and MME/SGSN MAP or Diameter Address for MT-SMS are included in Context Acknowledge and Forward Relocation R","","42","7.2.10","Extended DRX cycle for power consumption optimization (CT1) [eDRX]",11730,"revised","2016-02-01T09:49:13.750","2016-02-01T16:08:43.073","","C4-161339","Rel-13","29.060","13.3.0","eDRX-CT","1034","","B",null,"","","","",""]
["C4-161174","Triggering MT SM retransmission by the SMS GMSC to a UE in eDRX during inter MME/SGSN mobility procedure","Ericsson, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Vodafone","Yong Yang",42295,"CR","","","A new indication – Pending MT Short Message Indication (PMTSMI) is introduced in the Context Response and Forward Relocation Request message; and MME/SGSN MAP or Diameter Address for MT-SMS are included in Context Acknowledge and Forward Relocation Respon","","42","7.2.10","Extended DRX cycle for power consumption optimization (CT1) [eDRX]",11740,"revised","2016-02-01T09:52:31.167","2016-02-01T16:08:43.103","","C4-161340","Rel-13","29.274","13.4.0","eDRX-CT","1695","","B",null,"","","","",""]
["C4-161175","Subscription data for combined MME/SGSN","Nokia Networks, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell","Ulrich Wiehe",6963,"CR","","Agreement","Indicate for ULA and IDR that all subscripion data are downloaded to combined MME/SGSNs","","53","7.3.6","Diameter based Interfaces [TEI13]",11750,"revised","2016-02-01T10:21:05.597","2016-02-01T14:40:06.237","","C4-161493","Rel-13","29.272","13.4.0","TEI13","0628","","F",null,"","","","",""]
["C4-161176","DNS procedures for Decor","DOCOMO Communications Lab.","Mohammad Zahidul Islam",62745,"CR","","Agreement","In CT4#71 meeting, CR-0082 regarding DNS procedure for Decor was agreed in which the followings were FFS. \n1. the procedure for retrieval of SGSN Group ID\n2. Simple LTE example for a PLMN deploying Dedicated Core Network\n3.DNS procedures 3GPP clarificatio","","28","7.1.18","Dedicated Core Networks [DECOR-CT]",11760,"revised","2016-02-01T10:36:23.010","2016-02-01T11:43:36.003","","C4-161363","Rel-13","29.303","13.2.0","DECOR-CT","0086","","B",null,"","","","",""]
["C4-161177","AVP codes for 32.299","Nokia Networks, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell","Ulrich Wiehe",6963,"CR","","Agreement","AVP codes in the range of 3900 – 3999 are added as requested by SA5.","","49","7.3.2","Diameter 29.230 CRs [TEI13]",11770,"revised","2016-02-01T10:40:30.753","2016-02-01T12:55:23.487","","C4-161277","Rel-13","29.230","13.3.0","TEI13","0514","","F",null,"","","","",""]
["C4-161178","AVP code range reservation for 32.299","Nokia Networks, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell","Ulrich Wiehe",6963,"CR","","Agreement","To allocate a range of AVP codes for TS 32.299.\n\nAllocate the range of 4400 – 4499 for TS 32.299 as requested by SA5.","","101","8.3.7","Diameter 29.230 CRs [TEI12]",11780,"revised","2016-02-01T10:43:43.553","2016-02-01T12:55:23.517","","C4-161442","Rel-14","29.230","13.3.0","TEI14","0515","","F",null,"","","","",""]
["C4-161179","P-CSCF restoration not prioritized for WLAN","Nokia Networks","Jan Kåll",69918,"CR","","","It is clarified that the \"same principles\" for basic P-CSCF restoration over WLAN means that the UE is disconnected and then the UE re-establishes the IMS PDN connection via another P-CSCF.\n\nThe ambigous text that P-CSCF restoration over WLAN might not","","13","7.1.3","P-CSCF restoration enhancements with WLAN [PCSCF_RES_WLAN]",11790,"revised","2016-02-01T10:44:31.507","2016-02-05T15:38:06.123","","C4-161400","Rel-13","23.380","13.1.0","PCSCF_RES_WLAN","0083","","F",null,"","","","",""]
["C4-161180","Result-Codes for P-CSCF Restoration","Nokia Networks, Alcatel-Lucent, Alcatel-Lucent Bell","Jan Kåll",69918,"CR","","","A bullet is added to the description for 3GPP access about P-CSCF restoration in WLAN.\n\nTwo requirements are added:\nThe HSS shall not report an error to S-CSCF, if the P-CSCF restoration was triggered over 3GPP access or WLAN.\n\nThe HSS shall report D","","13","7.1.3","P-CSCF restoration enhancements with WLAN [PCSCF_RES_WLAN]",11800,"revised","2016-02-01T10:44:31.600","2016-02-05T15:38:06.060","","C4-161402","Rel-13","23.380","13.1.0","PCSCF_RES_WLAN","0084","","F",null,"","","","",""]
["C4-161181","Prolonging PDCP PDU numbers to 18 bits","Nokia Networks, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell","Jan Kåll",69918,"discussion","","","RAN2 informs CT4 in their LS in C4-161030 (R2-156977) that RAN2 has made a decision to extend the field length of PDCP Sequence Number (specified in TS 36.323) for both UL and DL to 18 bits in Rel-13, in addition to the previous maximum value of 15 bits.","","58","7.3.11","18 bits PDCP PDU Number",11810,"noted","2016-02-01T10:44:31.693","2016-02-01T16:40:09.413","","","","","","","","","","","","","","",""]
["C4-161182","18 bits PDCP PDU Number","Nokia Networks, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell","Jan Kåll",69918,"CR","","","A new type of extension header \"Long PDCP PDU Number\" is added and the content of the new extension header is specified.","","58","7.3.11","18 bits PDCP PDU Number",11820,"revised","2016-02-01T10:44:31.710","2016-02-01T16:40:09.367","","C4-161336","Rel-13","29.281","13.0.0","TEI13, LTE_CA_enh_b5C-Core","0077","","F",null,"","","","",""]
["C4-161183","Introduction of SGSN Group ID for Decor","DOCOMO Communications Lab.","Mohammad Zahidul Islam",62745,"CR","","Agreement","SGSN Group ID has been introduecd to support DNS procedure for Decor in 3GPP TS 23.401 which required to be specified in 3GPP TS 23.003. \nSummary of change:\tAddition of SGSN Group ID in SGSN FQDN","","28","7.1.18","Dedicated Core Networks [DECOR-CT]",11830,"withdrawn","2016-02-01T10:44:36.157","2016-02-01T11:43:35.957","","","Rel-13","23.003","13.4.0","DECOR-CT","0435","","B",null,"","","","",""]
["C4-161184","Transfer AAA information to avoid SWx redirection","ORANGE","Julien Bournelle",41373,"CR","","Approval","During Non-3GPP network attachment (both in Trusted and Untrusted Environment), the PGW contacts the 3GPP AAA server. As the PGW does not know which 3GPP AAA server has been used by the TWAN/ePDG, if it contacts a wrong one, the HSS has to use the redirec","","50","7.3.3","EPS AAA interfaces [TEI13]",11840,"withdrawn","2016-02-01T10:51:50.207",null,"","","Rel-13","29.273","13.2.0","TEI13","0451","","F",null,"","","","",""]
["C4-161185","WebRTC media plane optimization procedure","Nokia Networks","Thomas Belling",68266,"CR","","Agreement","Media Plane Optimization procedures for WebRTC are specified. The eIMS-AGW is configured with transport \"UDP\", as all higher protocol layers need to be passed without modification.","","44","7.2.12","Enhancements to WEBRTC interoperability stage 3 (CT1)  [eWebRTCi_CT]",11850,"revised","2016-02-01T10:55:06.407","2016-02-01T11:03:10.300","","C4-161272","Rel-13","23.334","13.4.0","eWebRTCi-CT","0107","","B",null,"","","","",""]
["C4-161186","Provide AAA information to the PGW","ORANGE","Julien Bournelle",41373,"CR","","Approval","In case of Non-3GPP attachment to the EPC, the PGW has to contact the 3GPP AAA server via S6b interface. If the PGW does not contact the 3GPP AAA server used by the ePDG/TWAN, the HSS will be contacted to provide the correct AAA. This may result in a HSS","","48","7.3.1","GTP and PMIP [TEI13]",11679,"merged","2016-02-01T11:48:24.317","2016-02-01T16:42:26.800","","","Rel-13","29.274","13.4.0","TEI13","1696","","F",null,"","","","",""]
["C4-161187","Transfer AAA information to avoid HSS overload","ORANGE","Julien Bournelle",41373,"discussion","","Decision","The goal of this paper is to discuss within CT4 the best way to proceed in order to avoid HSS overload during non-3GPP attachment to EPC. Indeed, if nothing is done, the PGW does not know the 3GPP AAA it has to contact which may result in the HSS having t","","50","7.3.3","EPS AAA interfaces [TEI13]",11870,"withdrawn","2016-02-01T13:17:45.343","2016-02-01T16:38:28.997","","","Rel-13","","","","","","","","","","","",""]
["C4-161188","Corrections to EVS AMR-WB IO mode-change-capability MIME parameter handling","Nokia Networks","Thomas Belling",68266,"CR","","Agreement","The handling of the EVS AMR-WB IO mode-change-capability MIME parameter  is aligned with recent changes agreed by SA4.","","79","8.1.19","CT impacts of Codec for Enhanced Voices Services [EVS_codec-CT]",11880,"revised","2016-02-01T13:56:48.150","2016-02-01T15:03:35.500","","C4-161416","Rel-12","23.334","12.9.0","EVS_codec-CT","0108","","F",null,"","","","",""]
["C4-161189","Corrections to EVS AMR-WB IO mode-change-capability MIME parameter handling","Nokia Networks","Thomas Belling",68266,"CR","","Agreement","Mirror CR","","79","8.1.19","CT impacts of Codec for Enhanced Voices Services [EVS_codec-CT]",11890,"revised","2016-02-01T14:01:00.230","2016-02-01T15:03:35.577","","C4-161417","Rel-13","23.334","13.4.0","EVS_codec-CT","0109","","A",null,"","","","",""]
["C4-161190","Indication of P-CSCF restoration extension support over IKEv2","Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Nokia Networks","Jean-Jacques Trottin",68942,"CR","","Agreement","UE capabilty for P-CSCF restoration for untrusted WLAN is conveyed in a notify payload of the IKEV2 message.","","13","7.1.3","P-CSCF restoration enhancements with WLAN [PCSCF_RES_WLAN]",11900,"agreed","2016-02-01T14:09:36.243","2016-02-01T16:46:20.860","","","Rel-13","23.380","13.1.0","PCSCF_RES_WLAN","0085","","F","CP-160025","","","","",""]
["C4-161191","Diameter message priority over S6m, S6n,  S6t","Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Nokia Networks, ACS, OEC","Jean-Jacques Trottin",68942,"CR","","Agreement","-  A new Annex for Diameter message priority over S6m, S6n, S6t is added and refers to the current IETF draft-ietf-dime-drmp-02.\n- Addition of the DRMP AVP in commands used over S6m, S6n, S6t interfaces, in the reused AVPs.","","30","7.1.20","Diameter Message Priority [DiaPri]",11910,"revised","2016-02-01T14:15:12.233","2016-02-01T16:46:20.893","","C4-161406","Rel-13","29.336","13.2.0","DiaPri","0047","","B",null,"","","","",""]
["C4-161192","Diameter message priority over S6c, SGd, GddDiameter message priority over S6c, SGd, Gdd","Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Nokia Networks, ACS, OEC","Jean-Jacques Trottin",68942,"CR","","Agreement","- A new Annex for Diameter message priority over S6c, SGd, Gdd interfaces is added and refers to the current IETF draft-ietf-dime-drmp-02.\n- Addition of the DRMP AVP in commands used over the S6c, SGd, Gdd interfaces, in the reused AVPs.","","30","7.1.20","Diameter Message Priority [DiaPri]",11920,"revised","2016-02-01T14:21:03.980","2016-02-01T16:46:20.940","","C4-161407","Rel-13","29.338","13.0.0","DiaPri","0020","","B",null,"","","","",""]
["C4-161193","Authorisation for NIDD procedure over  S6t","Huawei","Peter Schmitt",13753,"CR","","Decision","","","46","7.2.14","CIoT-CT (CT1)  [CIoT-CT]",33001,"revised","2016-02-01T14:23:23.927","2016-02-01T16:30:06.243","C4-161162","C4-161242","Rel-13","29.336","13.2.0","CIoT-CT","0046","1","B",null,"","","","",""]
["C4-161194","Diameter message priority over T4","Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Nokia Networks, ACS, OEC","Jean-Jacques Trottin",68942,"CR","","Agreement","- A new Annex for Diameter message priority over T4 is added and refers to the current IETF draft-ietf-dime-drmp-02.\n- Addition of the DRMP AVP in commands used over the T4 interface, in the reused AVPs.","","30","7.1.20","Diameter Message Priority [DiaPri]",11940,"revised","2016-02-01T14:24:33.893","2016-02-01T16:46:20.970","","C4-161408, C4-161409","Rel-13","29.337","13.0.0","DiaPri","0026","","B",null,"","","","",""]
["C4-161195","Diameter message priority over S7a/d, S13, S13’","Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Nokia Networks, ACS, OEC","Jean-Jacques Trottin",68942,"CR","","Agreement","- Update of the Annex E for Diameter message priority over S7a/d, S13, S13’.\n- Addition of the DRMP AVP in commands used over S7a/d, S13, S13’ interfaces. Update of the description of the DRMP AVP\n- Editorial in the title of Annex E","","30","7.1.20","Diameter Message Priority [DiaPri]",11950,"revised","2016-02-01T14:29:06.860","2016-02-01T16:46:21","","C4-161411","Rel-13","29.272","13.4.0","DiaPri","0629","","B",null,"","","","",""]
["C4-161196","Diameter message priority over PC4a","Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Nokia Networks, ACS, OEC","Jean-Jacques Trottin",68942,"CR","","Agreement","- A new Annex for Diameter message priority over the PC4a interface is added and refers to the current IETF draft-ietf-dime-drmp-02.\n- Addition of the DRMP AVP in commands used over the PC4a interface, in the reused AVPs.","","30","7.1.20","Diameter Message Priority [DiaPri]",11952,"revised","2016-02-01T14:33:07.287","2016-02-01T16:46:21.033","","C4-161412","Rel-13","29.344","13.0.0","DiaPri","0018","","B",null,"","","","",""]
["C4-161197","Diameter message priority over PC6/PC7","Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Nokia Networks, ACS, OEC","Jean-Jacques Trottin",68942,"CR","","Agreement","- A new Annex for Diameter message priority over the PC6/PC7 interfaces is added and refers to the current IETF draft-ietf-dime-drmp-02.\n- Addition of the DRMP AVP in commands used over the PC6/PC7 interfaces, in the reused AVPs.","","30","7.1.20","Diameter Message Priority [DiaPri]",11970,"revised","2016-02-01T14:36:06.277","2016-02-01T16:46:21.097","","C4-161413","Rel-13","29.345","13.0.0","DiaPri","0041","","B",null,"","","","",""]
["C4-161198","Corrections to EVS AMR-WB IO mode-change-capability MIME parameter handling","Nokia Networks","Thomas Belling",68266,"CR","","Agreement","The handling of the EVS AMR-WB IO mode-change-capability MIME parameter  is aligned with recent changes agreed by SA4.","","79","8.1.19","CT impacts of Codec for Enhanced Voices Services [EVS_codec-CT]",11980,"revised","2016-02-01T14:36:09.523","2016-02-01T15:03:35.627","","C4-161418","Rel-12","23.333","12.7.0","EVS_codec-CT","0092","","F",null,"","","","",""]
["C4-161199","Diameter message priority over T6a, T6ai, T6b, T6bi, T7","Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Nokia Networks, ACS, OEC","Jean-Jacques Trottin",68942,"pCR","","Agreement","This PCR specifies the Diameter message priority mechanism over the T6a, T6ai, T6b, T6bi, T7 interfaces","","30","7.1.20","Diameter Message Priority [DiaPri]",11990,"revised","2016-02-01T14:39:45.660","2016-02-01T16:46:21.063","","C4-161414","Rel-13","29.128","","DiaPri","","",null,"","","","","",""]
["C4-161200","Corrections to EVS AMR-WB IO mode-change-capability MIME parameter handling","Nokia Networks","Thomas Belling",68266,"CR","","","The handling of the EVS AMR-WB IO mode-change-capability MIME parameter  is aligned with recent changes agreed by SA4.","","79","8.1.19","CT impacts of Codec for Enhanced Voices Services [EVS_codec-CT]",12000,"revised","2016-02-01T14:45:02.370","2016-02-01T15:03:35.470","","C4-161420","Rel-13","23.333","13.0.0","EVS_codec-CT","0093","","A",null,"","","","",""]
["C4-161201","Adding eNB change reporting in Location Change Reporting","China Mobile Com. Corporation, ZTE, Allot Communications, China Unicom","Zhenning Huang",60086,"CR","","","This CR implements a new eNodeB granularity in Location Change Reporting Procedure, and this CR is applicable to macro eNodeB.\nThe MME supply the eNodeB ID reusing the ECGI IE and the 20 leftmost bits contained the ID of the eNodeB.","","8","6","Rel-14",12010,"postponed","2016-02-01T14:51:34.097","2016-02-01T15:15:48.460","C4-152135","C4-163133","Rel-14","29.274","13.4.0","TEI14","1681","1","B",null,"","","","",""]
["C4-161202","MCPTT data model","Ericsson","Maria-Cruz Bartolome",44824,"CR","","","Scope is clarified indicating that UDR data model is out of the scope of 3GPP only for legacy application FE data.\nNew abreviations are considered.\nObsolete Editor’s notes are removed.\nNew clause is added for UDR data model with a new subclause for MCP","","43","7.2.11","Mission Critical Push To Talk over LTE protocol aspects (CT1) [MCPTT-CT]",12020,"revised","2016-02-01T15:42:45.140","2016-02-05T11:58:55.140","","C4-161293","Rel-13","29.335","13.0.0","TEI13","0018","","B",null,"","","","",""]
["C4-161203","Discussion on status of MONTE work","Huawei","Peter Schmitt",13753,"discussion","","Discussion","Status and open issuess on MONTE","","19","7.1.9","Monitoring Enhancements CT aspects [MONTE-CT]",10755,"revised","2016-02-01T16:05:55.700","2016-02-01T16:23:15.637","C4-161075","C4-161285","Rel-13","","","MONTE-CT","","","","","","","","",""]
["C4-161204","Result-Codes for P-CSCF Restoration","Nokia Networks, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell","Jan Kåll",69918,"CR","","","If the 3GPP AAA Server did not send the P-CSCF Restoration Indication to the PGW, it still sends the Result Code DIAMETER_SUCCESS to the HSS, unless some of the other Result-Code values listed in Table 8.1.2.3.3/1 applies.\nThe 3GPP AAA Server and the PGW","","13","7.1.3","P-CSCF restoration enhancements with WLAN [PCSCF_RES_WLAN]",12040,"revised","2016-02-01T16:23:11.817","2016-02-01T16:40:09.333","","C4-161405","Rel-13","29.273","13.2.0","ePCSCF_WLAN","0452","","F",null,"","","","",""]
["C4-161205","New study item on PCRF failure and restoration enhancement","China Mobile Com. Corporation","Zhenning Huang",60086,"SID new","","","study an optional enhanced PCRF restoration procedure to support the scenario that the AF (e.g. P-CSCF) contacts with the PCRF before the PCEF/BBERF contacts with the PCRF after the PCRF failure (e.g. IMS initialing call).","","7","5","Work item management",12050,"postponed","2016-02-01T17:28:17.360","2016-02-01T17:40:26.700","","","Rel-14","","","","","","","","","","","",""]
["C4-161206","Transfer of non IP PDN to peer MME during mobility","Cisco Systems Inc","Sridhar Bhaskaran",58580,"CR","","Approval","GTPv2 changes for transfer of non IP PDN across S10 during UE mobility is addressed","","46","7.2.14","CIoT-CT (CT1)  [CIoT-CT]",50000,"revised","2016-02-02T05:34:59.340","2016-02-05T04:38:52.563","","C4-161401","Rel-13","29.274","13.4.0","CIoT-CT","1697","","B",null,"","","","",""]
["C4-161207","Discussion on non IP data transfer over T6a","Cisco Systems Inc","Sridhar Bhaskaran",58580,"discussion","","Decision","This discussion paper is to discuss the pros and cons of using EBI + UE identifier for the session lookup at MME vs using a stateful Diameter interface with session ID.","","46","7.2.14","CIoT-CT (CT1)  [CIoT-CT]",17000,"revised","2016-02-02T06:24:11.543","2016-02-05T04:38:52.500","","C4-161290","Rel-13","","","","","","","","","","","",""]
["C4-161208","Addition of NB-IoT radio access type to the Access-Restriction-Data feature","Vodafone GmbH, Vodafone, Deutsche Telekom, Huawei","Peter A. Wild",15130,"CR","","","“NB-IoT Not Allowed” as a new RAT is added to the Access-Restriction-Data","","46","7.2.14","CIoT-CT (CT1)  [CIoT-CT]",30000,"revised","2016-02-02T08:19:20.693","2016-02-05T08:50:09.520","","C4-161321","Rel-13","23.008","13.3.0","CIoT-CT","0486","","B",null,"","","","",""]
["C4-161209","Addition of NB-IoT radio access type to the Access-Restriction-Data feature","Vodafone GmbH, Deutsche Telekom, Huawei","Peter A. Wild",15130,"CR","","Approval","Description for the restriction of NB-IoT is added to the restriction of subsribers access","","46","7.2.14","CIoT-CT (CT1)  [CIoT-CT]",62000,"withdrawn","2016-02-02T08:21:07.973","2016-02-05T08:50:09.613","","","Rel-13","23.221","13.0.0","CIoT-CT","0167","","B",null,"","","","",""]
["C4-161210","Addition of NB-IoT radio access type to the Access-Restriction-Data feature","Vodafone GmbH, Deutsche Telekom, Huawei","Peter A. Wild",15130,"CR","","Approval","“NB-IoT Not Allowed” as a new RAT is added to the ASN.1 description of Access-Restriction-Data","","46","7.2.14","CIoT-CT (CT1)  [CIoT-CT]",29000,"revised","2016-02-02T08:22:48.467","2016-02-05T08:50:09.707","","C4-161320","Rel-13","29.002","13.2.0","CIoT-CT","1204","","B",null,"","","","",""]
["C4-161211","Addition of NB-IoT radio access type to the Access-Restriction-Data feature","Vodafone GmbH, Deutsche Telekom, Huawei","Peter A. Wild",15130,"CR","","Approval","“NB-IoT Not Allowed” as a new RAT is added to the Access-Restriction-Data table","","46","7.2.14","CIoT-CT (CT1)  [CIoT-CT]",28000,"revised","2016-02-02T08:24:23.317","2016-02-05T08:50:09.800","","C4-161319","Rel-13","29.272","13.4.0","CIoT-CT","0630","","B",null,"","","","",""]
["C4-161212","Addition of NB-IoT radio access type to the Access-Restriction-Data feature","Vodafone GmbH, Deutsche Telekom, Huawei","Peter A. Wild",15130,"CR","","Approval","“NB-IoT Not Allowed” as a new RAT is added to the MM context","","46","7.2.14","CIoT-CT (CT1)  [CIoT-CT]",31000,"revised","2016-02-02T08:25:30.457","2016-02-05T08:50:09.893","","C4-161322","Rel-13","29.274","13.4.0","CIoT-CT","1698","","B",null,"","","","",""]
["C4-161213","No Delete Session Request for non-existing PDN connection","Nokia Networks, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell","Jan Kåll",69918,"CR","","Agreement","The requirement is added that the MME shall not send the Delete Session Request message to the SGW on the S11 interface when the UE does not have any activated PDN connection.","","46","7.2.14","CIoT-CT (CT1)  [CIoT-CT]",53000,"revised","2016-02-02T11:13:52.187","2016-02-05T15:38:06.200","","C4-161432","Rel-13","29.274","13.4.0","CIoT-CT","1699","","B",null,"","","","",""]
["C4-161214","No Create Session Request for Attach without PDN connection","Nokia Networks, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell","Jan Kåll",69918,"CR","","Agreement","The requirement is added that the MME shall not send the Create Session Request message to the SGW on the S11 interface when the ESM message container was not included in the Attach Request received by the MME, or for PDN type \"non-IP\" when Control plane","","46","7.2.14","CIoT-CT (CT1)  [CIoT-CT]",54000,"revised","2016-02-02T11:19:14.013","2016-02-05T15:38:06.167","","C4-161434","Rel-13","29.274","13.4.0","CIoT-CT","1700","","B",null,"","","","",""]
["C4-161215","No PCI in DDN for non-IP PDN connections","Huawei","Xiaoyan Shi",57110,"CR","","Agreement","Add a restriction that the PCI is only used when the downlink packet is IPv4 or IPv6 type. \nAdd a note to clarify that the PCI shall not be carried for a Non-IP PDN connection.","","46","7.2.14","CIoT-CT (CT1)  [CIoT-CT]",55000,"revised","2016-02-02T13:40:10.347","2016-02-05T00:45:09.267","","C4-161435","Rel-13","29.274","13.4.0","CIoT-CT","1701","","B",null,"","","","",""]
["C4-161216","Behaviours upon receipt of unknown NIDD","Huawei","Xiaoyan Shi",57110,"CR","","Agreement","Add the MME behaviours on the MO/MT NIDD procedure failure\nAdd the SCEF behaviours on the MO/MT NIDD procedure failure.","","46","7.2.14","CIoT-CT (CT1)  [CIoT-CT]",56000,"revised","2016-02-02T13:40:10.423","2016-02-05T00:45:09.297","","C4-161436","Rel-13","23.007","13.3.0","CIoT-CT","0334","","B",null,"","","","",""]
["C4-161217","Dedicated Bearer NOT allowed for Non-IP PDN connections","Huawei","Xiaoyan Shi",57110,"CR","","Agreement","Add a new reject cause value\t\"Dedicated Bearer not allowed for the Non-IP PDN connections\" for the Create Bearer Response.","","46","7.2.14","CIoT-CT (CT1)  [CIoT-CT]",57000,"not pursued","2016-02-02T13:40:10.517","2016-02-05T00:45:09.343","","","Rel-13","29.274","13.4.0","CIoT-CT","1702","","B",null,"","","","",""]
["C4-161218","Enhance restoration procedure to be compatible with PDN connection to the SCEF","Huawei","Xiaoyan Shi",57110,"CR","","Agreement","Specify that the MME only detach the UE when there is not PDN connection to the SCEF of the UE.","","46","7.2.14","CIoT-CT (CT1)  [CIoT-CT]",58000,"revised","2016-02-02T13:40:10.580","2016-02-05T00:45:09.390","","C4-161437","Rel-13","23.007","13.3.0","CIoT-CT","0335","","B",null,"","","","",""]
["C4-161219","TAC Allocation as detailed in 3GPP TS 23.003","GSMA TSG","Kimmo Kymalainen",19464,"LS in","","Discussion","The GSMA has been providing training to manufacturers, regulatory authorities and other stakeholders all over the world about the TAC/IMEI usage, requirements and how to obtain them. IT has become apparent that new manufacturers and other interested parti","","6","4","Input liaison statements: allocation to agenda items as appropriate",12190,"replied to","2016-02-02T15:20:30.397","2016-02-02T16:13:34.907","","","","","","","","","","",null,"3GPP CT4 & ETSI",null,"TSG22_033","C4-161299"]
["C4-161220","Reply LS to CT4 LS on progress of the work on Diameter Base Protocol Update","3GPP TSG SA WG5","Kimmo Kymalainen",19464,"LS in","","Discussion","SA5 thanks CT4 for their LS on progress of the work on Diameter Base Protocol Update (S5-161193/C4-152375) provided with the version of TR 29.819 feasibility Study on the Diameter Base Protocol Update, as basis for their CT4#72 next February meeting.","","29","7.1.19","Feasibility Study on the Diameter Base Protocol Update [FS_DBPU]",12200,"noted","2016-02-02T15:23:41.677","2016-02-02T16:13:34.940","","","Rel-14","","","FS_DBPU","","","","",null,"3GPP TSG CT4","3GPP TSG CT3, 3GPP TSG SA3","S5-161308","C4-161541"]
["C4-161221","LS on Charging Id assignment for NBIFOM","3GPP TSG SA WG5","Kimmo Kymalainen",19464,"LS in","","Discussion","SA5 has studied the procedures in TS 23.161 for Network-based IP flow mobility and WLAN offload. Detailed analysis has resulted in some required changes to the current procedures for assignment of charging identifiers in the 3GPP system resulting from NBI","","38","7.2.6","IP Flow Mobility support for S2a and S2b Interfaces on stage 3 (CT1) [NBIFOM]",10241,"replied to","2016-02-02T15:27:24.507","2016-02-02T16:13:34.970","","","Rel-13","","","NBIFOM-CH","","","","",null,"SA2","CT3, CT4","S5-161252","C4-161466"]
["C4-161222","LS on Addition of AVP code definitions","3GPP TSG SA WG5","Kimmo Kymalainen",19464,"LS in","","Discussion","SA5 would like to inform CT4 about a number of AVPs defined for Rel-13 charging features in TS 32.299, for incorporation into TS 29.230.\nSA5 kindly asks CT4 to take into account the AVP  definitions above, and update their specification accordingly.\nSA5","","49","7.3.2","Diameter 29.230 CRs [TEI13]",12220,"replied to","2016-02-02T15:31:53.650","2016-02-02T16:13:35","","","Rel-13","","","CH13, CHeISC, ANIMO, eSaMOG-CH, MONTE-CH","","","","",null,"CT4",null,"S5-161246","C4-161443"]
["C4-161223","LS on EVS over CS","3GPP TSG SA WG4","Kimmo Kymalainen",19464,"LS in","","Discussion","SA4 would like to inform RAN1, RAN2, CT1, CT3 and CT4 that SA4 has agreed on the following new specifications and CR for Release 13:\n•\tS4-160298 CR TS 26.103, Introduction of EVS in the speech codec list for UMTS (Release 13)\n•\tS4-160200 TS 26.453 v.1.0","","17","7.1.7","CT aspects of EVS in 3G Circuit-Switched Networks [EVSoCS-CT]",10000,"noted","2016-02-02T15:34:46.577","2016-02-02T16:13:35.063","","","Rel-13","","","EVSoCS","","","","",null,null,null,"S4-160310"]
["C4-161224","Reply LS on Multi-stream Multiparty Conferencing Media Handling","3GPP TSG SA WG4","Kimmo Kymalainen",19464,"LS in","","Discussion","SA4 acknowledge that the procedure defined in the CR to 26.114 for the handling of too large SDPs is unsuitable. SA4 have studied this further and concluded that this issue is already handled by other 3GPP specifications, e.g. TS 24.229. SA4 have therefor","","6","4","Input liaison statements: allocation to agenda items as appropriate",12240,"noted","2016-02-02T15:38:27.597","2016-02-02T16:13:35.097","","","Rel-13","","","MMCMH","","","","",null,"CT3, CT1","CT4, CT","S4-160281"]
["C4-161225","LS on Completion of QOSE2EMTSI work item","3GPP TSG SA WG4","Kimmo Kymalainen",19464,"LS in","","Discussion","SA4 would like to inform CT1, CT3 and CT4 that the QOSE2EMTSI work item for Release 13 has now been completed.\n\nDuring the discussions in SA4 it was identified that the updates to the SDP definition may impact the PCC rules defined by CT3, see attached","","35","7.2.3","CT aspects of QoS End to End MTSI extensions (CT3) [QOSE2EMTSI-CT]",10000,"noted","2016-02-02T15:41:51.267","2016-02-02T16:13:35.143","","","Rel-13","","","QOSE2EMTSI-CT","","","","",null,"CT3","CT1, CT4","S4-160180"]
["C4-161226","Reply LS to CT4 on RTCP Handling for FECC","3GPP TSG SA WG4","Kimmo Kymalainen",19464,"LS in","","Discussion","SA4 has reviewed CT4’s questions with regards to RTCP handling for the Far End Camera Control (FECC) protocol and would like to provide the following clarification. SA4 believes that for FECC RTCP for the H.224/H.281 IP flow is not necessary; this is neit","","25","7.1.15","CT Aspects of Video Enhancements by Region-of-Interest Information Signalling [ROI-CT]",12260,"noted","2016-02-02T15:44:23.880","2016-02-02T16:13:35.173","","","","","","","","","","",null,"3GPP TSG CT WG4",null,"S4 (16)0173"]
["C4-161227","LS on guidance by SA2 on CIOT","3GPP TSG SA WG2","Kimmo Kymalainen",19464,"LS in","","Discussion","In relationship to a document received during SA2#113 (S2-160484) describing a list of questions by CT4 originated during the 1st CT4 Telco on CIoT that was held on Monday 18th January, SA2 would like to provide the following guidance\n1.\tIs there a need/","","46","7.2.14","CIoT-CT (CT1)  [CIoT-CT]",14000,"noted","2016-02-02T15:48:19.283","2016-02-02T16:13:35.203","","","Rel-13","","","CIoT-CT","","","","",null,"CT4",null,"S2-160910"]
["C4-161228","Response to LS on questions on CIoT","3GPP TSG SA WG2","Kimmo Kymalainen",19464,"LS in","","Discussion","SA2 thanks CT1 for starting the work on CIoT and raising these questions. \nFollowing the last TSG RAN decision to make both “solution 2” and “solution 18” applicable to all E-UTRAN devices, SA2 have made a similar decision that, in general, all the other","","46","7.2.14","CIoT-CT (CT1)  [CIoT-CT]",15000,"noted","2016-02-02T15:56:58.980","2016-02-02T16:13:34.707","","","Rel-13","","","CIoT-CT","","","","",null,"CT1, RAN2, RAN3","CT4, RAN1, SA3","S2-160906"]
["C4-161229","Reply LS on NBIFOM procedure in SCM and RAN rules handling parameter","3GPP TSG SA WG2","Kimmo Kymalainen",19464,"LS in","","Discussion","3GPP SA2 would like to thank CT1 for their LS (C1-154645/S2-160025) related to NBIFOM. Regarding the following questions asked by CT1:\n\nQ1: Based above, if the 3GPP AAA server does not support NBIFOM, how do the UE and the network achieve to determine t","","38","7.2.6","IP Flow Mobility support for S2a and S2b Interfaces on stage 3 (CT1) [NBIFOM]",10242,"noted","2016-02-02T16:01:20.200","2016-02-02T16:13:34.767","","","Rel-13","","","NBIFOM-CT","","","","",null,"3GPP TSG CT WG1","3GPP TSG CT WG3, 3GPP TSG CT WG4","S2-160889"]
["C4-161230","LS on the Revocation of Discovery Filters","3GPP TSG SA WG2","Kimmo Kymalainen",19464,"LS in","","Discussion","SA2 wants to clarify that the Revocation of Discovery Filters procedure in section 5.3.6A.2.2 has been defined to revoke the authorization to use certain discovery filters as soon as possible after the user has changed the discovery permissions. Answers t","","84","8.2.4","Proximity Services [ProSe-CT]",12300,"noted","2016-02-02T16:07:34.130","2016-02-02T16:13:34.830","","","Rel-13","","","ProSe-CT","","","","",null,"3GPP TSG CT4","3GPP TSG CT1","S2-160883"]
["C4-161231","LS on issues related to MT SMS over SGs delivery in eDRX","3GPP TSG SA WG2","Kimmo Kymalainen",19464,"LS in","","Discussion","SA2 thanks CT1 for your LS on issues related to MT SMS over SGs delivery in eDRX (C1-160782/S2-160206).\n\nSA2 have discussed these issues and finds the issues in the LS and would like to provide the following feedback:  \n\na.\tEvery MT SMS delivery for U","","42","7.2.10","Extended DRX cycle for power consumption optimization (CT1) [eDRX]",10265,"noted","2016-02-02T16:10:18.397","2016-02-02T16:13:34.860","","","Rel-13","","","eDRX-CT","","","","",null,"CT1","CT4","S2-160540"]
["C4-161232","New PDN-Type for Celular IoT","Ericsson","Jesus De Gregorio",40423,"CR","","","- Define the new PDN type = non-IP.\n- Include the NIDD mechanism selection (SGi vs SCEF).\n- Include the SCEF-ID.\n- Define the new default APN for APNs with PDN type = non-IP.","","46","7.2.14","CIoT-CT (CT1)  [CIoT-CT]",24000,"revised","2016-02-03T09:50:43.877","2016-02-05T16:49:31.867","","C4-161308","Rel-13","29.272","13.4.0","CIoT-CT","0631","","B",null,"","","","",""]
["C4-161233","MO Non-IP Data procedures over T6a","Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Nokia Networks","Jean-Jacques Trottin",68942,"pCR","","Agreement","This PCR specifies the Diameter MO Data procedures related to CIoT over the T6a, T6ai and T7 interfaces.","","46","7.2.14","CIoT-CT (CT1)  [CIoT-CT]",20000,"revised","2016-02-03T16:00:26.683","2016-02-05T16:54:03.230","","C4-161303","Rel-13","29.128","1.0.0","CIoT-CT","","",null,"","","","","",""]
["C4-161234","MT Non-IP Data procedures over T6a","Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Nokia Networks","Jean-Jacques Trottin",68942,"pCR","","Agreement","This PCR specifies the Diameter MT Data procedures related to CIoT over the T6a, T6ai and T7 interfaces.","","46","7.2.14","CIoT-CT (CT1)  [CIoT-CT]",21000,"revised","2016-02-03T16:03:13.383","2016-02-05T16:54:03.260","","C4-161304","Rel-13","29.128","1.0.0","CIoT-CT","","",null,"","","","","",""]
["C4-161235","Connection management  procedures over T6a","Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Nokia Networks","Jean-Jacques Trottin",68942,"pCR","","Agreement","This PCR specifies the Connection Management procedure related to CIoT over the T6a, T6ai and T7 interfaces","","46","7.2.14","CIoT-CT (CT1)  [CIoT-CT]",22000,"revised","2016-02-03T16:06:40.783","2016-02-05T16:54:03.307","","C4-161306","Rel-13","29.128","1.0.0","CIoT-CT","","",null,"","","","","",""]
["C4-161236","Protocol for Non IP-Data over T6a","Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Nokia Networks","Jean-Jacques Trottin",68942,"pCR","","Agreement","This PCR specifies the Diameter protocol used to support the Non-IP Data procedures and related to the CIoT-CT work item over the T6a, T6ai and T7 interfaces.","","46","7.2.14","CIoT-CT (CT1)  [CIoT-CT]",23000,"revised","2016-02-03T16:11:29.587","2016-02-05T16:54:03.337","","C4-161307","Rel-13","29.128","1.0.0","CIoT-CT","","",null,"","","","","",""]
["C4-161237","Sh* application for MCPTT-2 and CSC-13 interfaces","Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Nokia Networks","Jean-Jacques Trottin",68942,"discussion","","Decision","","","43","7.2.11","Mission Critical Push To Talk over LTE protocol aspects (CT1) [MCPTT-CT]",12370,"withdrawn","2016-02-03T16:22:16.683","2016-02-05T16:48:29.063","","","Rel-13","","","MCPTT-CT","","","","","","","","",""]
["C4-161238","Skeleton for Sh* application for MCPTT-2 and CSC-13 interfaces","Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Nokia Networks","Jean-Jacques Trottin",68942,"discussion","","Decision","","","43","7.2.11","Mission Critical Push To Talk over LTE protocol aspects (CT1) [MCPTT-CT]",12380,"revised","2016-02-03T16:31:06.520","2016-02-09T15:39:29.183","","C4-161479","Rel-13","","","MCPTT-CT","","","","","","","","",""]
["C4-161239","Storage for CIoT control plane optimization related information at MME","Cisco Systems Inc","Sridhar Bhaskaran",58580,"CR","","Approval","Add a place holder for storing CIoT control plane optimization related information at the MME with an Editor's Note to address the exact details after CT1 finalizes the information used between the MME and the UE.","","46","7.2.14","CIoT-CT (CT1)  [CIoT-CT]",63000,"revised","2016-02-04T07:31:49.513","2016-02-05T04:38:52.437","","C4-161403","Rel-13","23.008","13.3.0","CIoT-CT","0487","","B",null,"","","","",""]
["C4-161240","Data model for new Application FEs’ data clarification","Ericsson","Maria-Cruz Bartolome",44824,"CR","","","Scope is clarified.","","43","7.2.11","Mission Critical Push To Talk over LTE protocol aspects (CT1) [MCPTT-CT]",12400,"revised","2016-02-04T09:47:04.267","2016-02-05T11:58:55.220","","C4-161433","Rel-13","23.335","13.0.0","MCPTT-CT","0015","","B",null,"","","","",""]
["C4-161241","AVP code range reservation for 32.299","Nokia Networks, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell","Ulrich Wiehe",6963,"CR","","Agreement","","","49","7.3.2","Diameter 29.230 CRs [TEI13]",10641,"merged","2016-02-04T11:47:28.457","2016-02-04T11:50:01.570","C4-161064","","Rel-13","29.230","13.3.0","TEI13","0504","1","F",null,"","","","",""]
["C4-161242","Authorisation for NIDD procedure over  S6t","Huawei, Vodafone","Peter Schmitt",13753,"CR","","Decision","Enhancement for NIDD Authorisation in CIR and CIA","","46","7.2.14","CIoT-CT (CT1)  [CIoT-CT]",34000,"revised","2016-02-04T13:01:31.367","2016-02-05T15:37:57.447","C4-161193","C4-161324","Rel-13","29.336","13.2.0","CIoT-CT","0046","2","B",null,"","","","",""]
["C4-161243","Monitoring update and Reporting of update result","Huawei, Orange, Telecom Italia","Peter Schmitt",13753,"CR","","Decision","","","39","7.2.7","CT aspects of enhancements to Proximity-based Services extensions (CT1) [eProSe-Ext-CT]",10861,"revised","2016-02-04T13:03:34.137","2016-02-05T15:37:57.480","C4-161086","C4-161287","Rel-13","29.345","13.0.0","eProSe-Ext-CT","0036","1","B",null,"","","","",""]
["C4-161244","Introduction of AAA-1 interface","Huawei","Peter Schmitt",13753,"CR","","Decision","","","43","7.2.11","Mission Critical Push To Talk over LTE protocol aspects (CT1) [MCPTT-CT]",10881,"revised","2016-02-04T13:05:27.220","2016-02-05T15:37:57.527","C4-161088","C4-161362","Rel-13","29.228","13.0.0","MCPTT-CT","0661","3","B",null,"","","","",""]
["C4-161245","AVP Codes for 29.12","Nokia Networks, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell","Ulrich Wiehe",6963,"CR","","Agreement","Add AVP code for the Credit-Management-Status AVP to table 7.1.","","101","8.3.7","Diameter 29.230 CRs [TEI12]",12450,"revised","2016-02-04T13:09:01.953","2016-02-04T13:16:18.267","","C4-161440","Rel-12","29.230","12.11.0","TEI12","0516","","F",null,"","","","",""]
["C4-161246","Monitoring update and Reporting of update result","Huawei","Peter Schmitt",13753,"CR","","Decision","","","39","7.2.7","CT aspects of enhancements to Proximity-based Services extensions (CT1) [eProSe-Ext-CT]",10864,"revised","2016-02-04T13:11:11.667","2016-02-05T15:37:57.557","","C4-161380","Rel-13","29.230","13.3.0","eProSe-Ext-CT","0517","","B",null,"","","","",""]
["C4-161247","Codes for 29.212","Nokia Networks, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell","Ulrich Wiehe",6963,"CR","","Agreement","Add AVP codes to table 7.1.\nAdd Experimental Result Code to table 8.1.4","","49","7.3.2","Diameter 29.230 CRs [TEI13]",12470,"revised","2016-02-04T13:12:26.077","2016-02-04T13:16:18.313","","C4-161445","Rel-13","29.230","13.3.0","TEI13","0518","","F",null,"","","","",""]
["C4-161248","Allocation of new Diameter Application ID and commands code for PC2 protocol","Huawei","Peter Schmitt",13753,"CR","","Decision","Add new  application ID for PC2 reference point and add new command pair for  TS 29.343.","","39","7.2.7","CT aspects of enhancements to Proximity-based Services extensions (CT1) [eProSe-Ext-CT]",12480,"revised","2016-02-04T13:17:11.557","2016-02-05T15:37:57.603","","C4-161382","Rel-13","29.230","13.3.0","eProSe-Ext-CT","0519","","B",null,"","","","",""]
["C4-161249","S11-U tunneling for MO/MT data transport in control plane (SGi based) – reusing S1-U F-TEIDs","Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Nokia Networks","Bruno Landais",68755,"CR","","Approval","Adds support for establishment of GTP-U tunnel over S11, reusing existing S1-U F-TEIDs","","46","7.2.14","CIoT-CT (CT1)  [CIoT-CT]",39000,"withdrawn","2016-02-04T16:12:55.417","2016-02-05T16:48:31.327","","","Rel-13","29.274","13.4.0","CIoT-CT","1703","","B",null,"","","","",""]
["C4-161250","Revised WID on Controlling IMS Media Plane with SDP Capability Negotiation","Huawei","Weiwei(Tommy) YANG",55591,"WID revised","","Agreement","The SDP capability negotiation, as defined in IETF RFC 5939, enables SDP to provide limited support for indicating capabilities and their associated potential configurations, and negotiate the use of those potential configurations as actual configurations","","7","5","Work item management",12500,"withdrawn","2016-02-04T16:14:57.567","2016-02-04T16:16:08.937","CP-150238","","Rel-13","","","","","","","","","","","",""]
["C4-161251","Iq stage 3 to support SDP Capability Negotiation","Huawei","Weiwei(Tommy) YANG",55591,"CR","","","Stage 3 Iq procedures to support SDP Capability Negotiation","","22","7.1.12","SDP Capability Negotiation for IMS Media Plane [SDPCN_IMS]",12510,"revised","2016-02-04T16:19:27.477","2016-02-06T19:01:46.717","","C4-161421","Rel-13","29.334","13.3.0","SDPCN_IMS","0108","","B",null,"","","","",""]
["C4-161252","Ix stage 3 to support SDP Capability Negotiation","Huawei","Weiwei(Tommy) YANG",55591,"CR","","Agreement","Iq stage 3 to support SDP Capability Negotiation","","22","7.1.12","SDP Capability Negotiation for IMS Media Plane [SDPCN_IMS]",12520,"revised","2016-02-04T16:21:51.820","2016-02-06T19:01:46.843","","C4-161422","Rel-13","29.238","13.0.0","SDPCN_IMS","0064","","B",null,"","","","",""]
["C4-161253","Mp stage 3 to support SDP Capability Negotiation","Huawei","Weiwei(Tommy) YANG",55591,"CR","","","Mp stage 3 to support SDP Capability Negotiation","","22","7.1.12","SDP Capability Negotiation for IMS Media Plane [SDPCN_IMS]",12530,"revised","2016-02-04T16:23:18.057","2016-02-06T19:01:47.093","","C4-161424","Rel-13","29.333","13.0.0","SDPCN_IMS","0085","","B",null,"","","","",""]
["C4-161254","Mn stage 3 to support SDP Capability Negotiation","Huawei","Weiwei(Tommy) YANG",55591,"CR","","","Mn stage 3 to support SDP Capability Negotiation","","22","7.1.12","SDP Capability Negotiation for IMS Media Plane [SDPCN_IMS]",12540,"revised","2016-02-04T16:24:55.837","2016-02-06T19:01:47.187","","C4-161426","Rel-13","29.332","13.0.0","SDPCN_IMS","0199","","B",null,"","","","",""]
["C4-161255","Mc stage 3 to support SDP Capability Negotiation","Huawei","Weiwei(Tommy) YANG",55591,"CR","","Agreement","Mc stage 3 to support SDP Capability Negotiation","","22","7.1.12","SDP Capability Negotiation for IMS Media Plane [SDPCN_IMS]",12550,"revised","2016-02-04T16:26:20.700","2016-02-06T19:01:47.293","","C4-161429","Rel-13","29.232","13.0.0","SDPCN_IMS","0660","","B",null,"","","","",""]
["C4-161256","Discussion on the possible solution for GW selection","Ericsson","Yong Yang",42295,"discussion","","","It is propose to standardize the alternative 2 and document the alternative 1. The accompany CRs are provided in C4-161257 and C4-161258.","","46","7.2.14","CIoT-CT (CT1)  [CIoT-CT]",44000,"revised","2016-02-04T19:55:32.100","2016-02-05T11:25:05.047","","C4-161292","","","","","","","","","","","","",""]
["C4-161257","Impacts on the DNS procedures for CIoT with introduction of NB-IoT and Non-IP","Ericsson","Yong Yang",42295,"CR","","","DNS NAPTR record and procedures for selecting a PGW/SGW are updated accordingly.\n\nIn addition, a clarification using DECOR mechanism to achieve the same is also added.","","46","7.2.14","CIoT-CT (CT1)  [CIoT-CT]",46000,"revised","2016-02-04T19:59:39.310","2016-02-05T11:24:02.710","","C4-161291","Rel-13","29.303","13.2.0","CIoT-CT","0087","","B",null,"","","","",""]
["C4-161258","DNS service for NB-IoT and Non-IP","Ericsson","Yong Yang",42295,"CR","","","Introduce new application protocols NBIoT and NonIP for the SGW and the MME, and a new application protocol NBIoT for the PGW.","","46","7.2.14","CIoT-CT (CT1)  [CIoT-CT]",47500,"withdrawn","2016-02-04T20:03:00.863","2016-02-05T11:24:02.743","","","Rel-13","23.003","13.4.0","CIoT-CT","0436","","B",null,"","","","",""]
["C4-161259","Protocol change for Connection Suspend and Resume Procedure","Ericsson","Yong Yang",42295,"CR","","","Connection Suspend and Resume procedure are added for the relevant GTPv2 messages.","","46","7.2.14","CIoT-CT (CT1)  [CIoT-CT]",51000,"revised","2016-02-04T20:15:38.907","2016-02-05T11:24:02.790","","C4-161415","Rel-13","29.274","13.4.0","CIoT-CT","1704","","B",null,"","","","",""]
["C4-161260","Connection Resume procedure used during restoration","Ericsson","Yong Yang",42295,"CR","","","Connection Resume procedure may be used by the MME for those UEs has suspended its PDN connection preeviously during MME initiated SGW relocation procedure.","","46","7.2.14","CIoT-CT (CT1)  [CIoT-CT]",52000,"revised","2016-02-04T20:18:20.163","2016-02-05T11:24:02.820","","C4-161410","Rel-13","23.007","13.3.0","CIoT-CT","0336","","B",null,"","","","",""]
["C4-161261","Protocol change for introducing new non-IP PDN type","Ericsson","Yong Yang",42295,"CR","","","New PDN type Non-IP is introduced and impacted GTPv2 messages are updated accordingly.","","46","7.2.14","CIoT-CT (CT1)  [CIoT-CT]",49000,"revised","2016-02-04T20:20:31.953","2016-02-05T11:24:02.663","","C4-161404","Rel-13","29.274","13.4.0","CIoT-CT","1705","","B",null,"","","","",""]
["C4-161262","ePDG selection with DNS-based Discovery of Regulatory Requirements","Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Nokia Networks","Bruno Landais",68755,"CR","","Approval","A new Visited Country FQDN is specified, to be used as input to the above DNS query.\n\nA new subdomain is defined to support the above DNS query. The domain of the input FQDN does not correspond to an individual operator as the corresponding DNS record i","","52","7.3.5","Addressing and Subscriber Data Handling [TEI13]",12620,"revised","2016-02-05T08:47:20.447","2016-02-05T16:48:31.373","","C4-161310","Rel-13","23.003","13.4.0","TEI13","0437","","B",null,"","","","",""]
["C4-161263","Data returned in IMSPublicIdentity correction, new EnhancedPublicIdentifiers class","Ericsson","Maria-Cruz Bartolome",44824,"CR","","","","","54","7.3.7","IMS [TEI13]",10891,"revised","2016-02-05T09:09:55.347","2016-02-05T11:58:55.313","C4-161089","C4-161344","Rel-13","29.328","13.3.0","TEI13","0543","1","F",null,"","","","",""]
["C4-161264","New PDN-Type for Cellular IoT","Ericsson","Jesus De Gregorio",40423,"CR","","","- Define the new PDN type = non-IP.\n- Include the NIDD mechanism selection (SGi vs SCEF).\n- Include the SCEF-ID.\n- Define the new default APN for APNs with PDN type = non-IP.","","46","7.2.14","CIoT-CT (CT1)  [CIoT-CT]",25000,"revised","2016-02-05T09:16:13.877","2016-02-05T16:49:31.760","","C4-161313","Rel-13","29.002","13.2.0","CIoT-CT","1205","","B",null,"","","","",""]
["C4-161265","New PDN-Type for Celullar IoT","Ericsson","Jesus De Gregorio",40423,"CR","","","Define the subscription data elements related to APNs whose PDN type is Non-IP.","","46","7.2.14","CIoT-CT (CT1)  [CIoT-CT]",26000,"revised","2016-02-05T09:19:31.437","2016-02-05T16:49:31.807","","C4-161314","Rel-13","29.230","13.3.0","CIoT-CT","0520","","B",null,"","","","",""]
["C4-161266","New PDN-Type for Celular IoT","Ericsson","Jesus De Gregorio",40423,"CR","","","Define the subscription data elements related to APNs whose PDN type is Non-IP.","","46","7.2.14","CIoT-CT (CT1)  [CIoT-CT]",27000,"revised","2016-02-05T09:26:08.127","2016-02-05T16:49:31.837","","C4-161315","Rel-13","23.008","13.3.0","CIoT-CT","0488","","B",null,"","","","",""]
["C4-161267","Reply LS on CT4 assumptions on AAA-1, MCPTT-2 and CSC-13 reference points","3GPP TSG CT WG1","Kimmo Kymalainen",19464,"LS in","","Discussion","CT1 thanks CT4 for their liaison statement.\nThe LS lists a number of assumptions and some open questions.\nWith regard to the questions, CT1 believes that these questions should be answered by SA6 as they do not pertain to protocol-related aspects.\nWith","","43","7.2.11","Mission Critical Push To Talk over LTE protocol aspects (CT1) [MCPTT-CT]",12670,"noted","2016-02-05T13:14:38.657","2016-02-05T13:26:12.137","","","Rel-13","","","MCPTT-CT","","","","",null,"CT4","SA3, SA6","C1ah-160094"]
["C4-161268","LS Response on User Databases interfaces for MCPTT","3GPP TSG SA WG6","Kimmo Kymalainen",19464,"LS in","","Discussion","SA6 thanks CT4 for sending the LS on User Databases interfaces for MCPTT, focusing on interfaces AAA-1 and MCPTT-2. SA6 discussed the questions contained in the LS and reached conclusion that some answers were already provided during conference calls or w","","43","7.2.11","Mission Critical Push To Talk over LTE protocol aspects (CT1) [MCPTT-CT]",12680,"noted","2016-02-05T13:40:44.640","2016-02-05T13:42:15.617","","","Rel-13","","","MCPTT-CT","","","",""]
["C4-161269","LS Response on CT4 assumptions on AAA-1, MCPTT-2 and CSC-13 reference points","3GPP TSG SA WG6","Kimmo Kymalainen",19464,"LS in","","Discussion","SA6 would like to thank CT4 for their LS on CT4 assumptions on AAA-1, MCPTT-2 and CSC-13 reference points. The LS provided a set of working assumptions.\nSA6 kindly asks CT4 to take the above answers into account when defining stage 3 for AAA-1, MCPTT-2 a","","43","7.2.11","Mission Critical Push To Talk over LTE protocol aspects (CT1) [MCPTT-CT]",12690,"noted","2016-02-05T13:43:23.633","2016-02-05T14:00:18.203","","","Rel-13","","","MCPTT-CT","","","",""]
["C4-161270","new Diameter application for MCPTT-2 and CSC-13 reference points","ORANGE","Lionel Morand",25150,"pCR","","Approval","It is proposed to propose to agree on the principle to define a new Diameter application for use over MCPTT-2 and CSC-13 reference points and approve the proposed specification.","","43","7.2.11","Mission Critical Push To Talk over LTE protocol aspects (CT1) [MCPTT-CT]",12700,"revised","2016-02-05T16:52:27.617","2016-02-05T16:55:01.247","","C4-161298","Rel-13","","","MCPTT-CT","","",null,"","","","","",""]
["C4-161271","Alert procedure from MME/SGSN to SMS-GMSC for MT SMS to UE using eDRX","Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Nokia Networks, Ericsson, Verizon, AT&T, Vodafone","Bruno Landais",68755,"CR","","Approval","","","42","7.2.10","Extended DRX cycle for power consumption optimization (CT1) [eDRX]",11542,"agreed","2016-02-05T16:56:40.507","2016-02-05T17:02:28.493","C4-161154","","Rel-13","29.002","13.2.0","eDRX-CT","1202","1","B","CP-160030","","","","",""]
["C4-161272","WebRTC media plane optimization procedure","Nokia Networks, Alcatel-Lucent","Thomas Belling",68266,"CR","","Agreement","Media Plane Optimization procedures for WebRTC are specified. The eIMS-AGW is configured with transport \"UDP\", as all higher protocol layers need to be passed without modification.","","44","7.2.12","Enhancements to WEBRTC interoperability stage 3 (CT1)  [eWebRTCi_CT]",11851,"revised","2016-02-05T22:14:38.093","2016-02-05T22:20:05.067","C4-161185","C4-161368","Rel-13","23.334","13.4.0","eWebRTCi-CT","0107","1","B",null,"","","","",""]
["C4-161273","Release of WebRTC Data Channels","Alcatel-Lucent, Nokia Networks","Albrecht Schwarz",68771,"CR","","Approval","","","18","7.1.8","H.248 Aspects of WebRTC Data Channel on IMS Access Gateway",10080,"revised","2016-02-08T10:43:32.890","2016-02-08T14:12:35.337","C4-161007","C4-161328","Rel-13","23.334","13.4.0","WebRTCH248DC","0104","1","B",null,"","","","",""]
["C4-161274","WebRTC Data Channels","Alcatel-Lucent, Nokia Networks","Albrecht Schwarz",68771,"CR","","Approval","","","18","7.1.8","H.248 Aspects of WebRTC Data Channel on IMS Access Gateway",12740,"revised","2016-02-08T10:44:30.767","2016-02-08T14:12:35.260","C4-161008","C4-161329","Rel-13","29.334","13.3.0","WebRTCH248DC","0105","1","B",null,"","","","",""]
["C4-161275","CT4 aspect of the Workplan","CT4 Chairman","Nigel. H Berry",68268,"Work Plan","","Approval","","","168","11","Update of the Work Plan",12750,"revised","2016-02-08T17:01:36.957","2016-02-10T08:17:12.520","","C4-161547","Rel-13","","","","","","","","","","","",""]
["C4-161276","Transferring AAA identifier to the PGW","Ericsson, Orange","Yong Yang",42295,"CR","","","","","48","7.3.1","GTP and PMIP [TEI13]",11682,"revised","2016-02-09T09:07:23.310","2016-02-09T10:24:04.050","C4-161168","C4-161353","Rel-13","29.274","13.4.0","TEI13","1693","1","F",null,"","","","",""]
["C4-161277","AVP codes for 32.299","Nokia Networks, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell","Ulrich Wiehe",6963,"CR","","Agreement","","","49","7.3.2","Diameter 29.230 CRs [TEI13]",11771,"revised","2016-02-09T10:55:11.590","2016-02-09T11:00:47.397","C4-161177","C4-161441","Rel-13","29.230","13.3.0","TEI13","0514","1","F",null,"","","","",""]
["C4-161278","Editorial clean-up","ORANGE","Lionel Morand",25150,"pCR","","Approval","The paper is intended for a global editorial clean-up of the TR 29.819.","","29","7.1.19","Feasibility Study on the Diameter Base Protocol Update [FS_DBPU]",12780,"approved","2016-02-09T16:23:46.080","2016-02-09T16:48:52.873","","","Rel-13","29.819","1.0.0","FS_DBPU","","",null,"","","","","",""]
["C4-161279","Changes in the Command's CCF specifications","ORANGE","Lionel Morand",25150,"pCR","","Approval","This paper analyzes the impacts on the changes in some Diameter base protocol command's CCF specifications done in IETF RFC 6733.","","29","7.1.19","Feasibility Study on the Diameter Base Protocol Update [FS_DBPU]",12790,"revised","2016-02-09T16:30:13.957","2016-02-09T16:48:52.733","","C4-161452","Rel-13","29.819","1.0.0","FS_DBPU","","",null,"","","","","",""]
["C4-161280","Proposed Conclusions","ORANGE","Lionel Morand",25150,"pCR","","Approval","This paper proposes a conclusion for the TR 29.819.","","29","7.1.19","Feasibility Study on the Diameter Base Protocol Update [FS_DBPU]",12800,"postponed","2016-02-09T16:37:32.937","2016-02-09T16:48:52.767","","","Rel-13","29.819","1.0.0","FS_DBPU","","",null,"","","","","",""]
["C4-161281","Proposed recommendations","ORANGE","Lionel Morand",25150,"pCR","","Approval","This paper proposes to provide some generic recommendations regarding the support of the new version of the Diameter base protocol specification i.e. IETF RFC 6733.","","29","7.1.19","Feasibility Study on the Diameter Base Protocol Update [FS_DBPU]",12810,"postponed","2016-02-09T16:42:18.930","2016-02-09T16:48:52.797","","","Rel-13","29.819","1.0.0","FS_DBPU","","",null,"","","","","",""]
["C4-161282","Proposed text for the introduction of clause 5","ORANGE","Lionel Morand",25150,"pCR","","Approval","The paper proposes a text for the missing introduction in clause 5 to complete the TR 29.819.","","29","7.1.19","Feasibility Study on the Diameter Base Protocol Update [FS_DBPU]",12820,"revised","2016-02-09T16:45:43.600","2016-02-09T16:48:52.843","","C4-161448","Rel-13","29.819","1.0.0","FS_DBPU","","",null,"","","","","",""]
["C4-161283","3GPP Work on ECN for Lower Layer Protocols: possible impact on H.248 gateways","Alcatel-Lucent","Albrecht Schwarz",68771,"discussion","","Information","There is a pending question how the additional support of “ECN for lower layers” (ECNfLL) (draft-ietf-tsvwg-ecn-encap-guidelines) would affect existing ECN support nodes (C4-161041). Purpose of this document is provide a brief summary of our understanding","","151","10.7","Enabling Coder Selection and Rate Adaptation for UTRAN and -UTRAN for Load Adaptive Applications [ECSRA_LAA-CN]",12830,"noted","2016-02-10T11:19:40.297","2016-02-10T14:15:28.543","","","","","","ECSRA_LAA-CN","","","","","","","","",""]
["C4-161284","Protocol selection for T6a/b to support NIDD procedures","Ericsson","Yong Yang",42295,"discussion","","Decision","CT4 has decided to use Diameter protocol for T6a/b interface to support the procedures introduced by MONTE work item. However, with introduction of the CIoT Optimisation for support of Non-IP data delivery via SCEF to MME, some new procedures e.g. T6a Con","","46","7.2.14","CIoT-CT (CT1)  [CIoT-CT]",16000,"noted","2016-02-10T14:01:28.283","2016-02-10T14:03:17.127","","","","","","","","","","","","","","",""]
["C4-161285","Discussion on status of MONTE work","Huawei","Peter Schmitt",13753,"discussion","","Discussion","","","19","7.1.9","Monitoring Enhancements CT aspects [MONTE-CT]",10757,"noted","2016-02-10T14:53:26.657","2016-02-11T07:49:59.913","C4-161203","","Rel-13","","","MONTE-CT","","","","","","","","",""]
["C4-161286","New AVP assignment for MONTE","Huawei","Peter Schmitt",13753,"CR","","Decision","","","19","7.1.9","Monitoring Enhancements CT aspects [MONTE-CT]",10851,"revised","2016-02-10T14:56:33.093","2016-02-11T07:49:59.943","C4-161085","C4-161425","Rel-13","29.230","13.3.0","MONTE-CT","0505","1","B",null,"","","","",""]
["C4-161287","Monitoring update and Reporting of update result","Huawei, Orange, Telecom Italia","Peter Schmitt",13753,"CR","","Decision","","","39","7.2.7","CT aspects of enhancements to Proximity-based Services extensions (CT1) [eProSe-Ext-CT]",10862,"revised","2016-02-10T14:58:30.577","2016-02-11T07:49:59.990","C4-161243","C4-161373","Rel-13","29.345","13.0.0","eProSe-Ext-CT","0036","2","B",null,"","","","",""]
["C4-161288","Pseudo-CR on cleanup of 29.128","Huawei","Peter Schmitt",13753,"pCR","","Decision","","","19","7.1.9","Monitoring Enhancements CT aspects [MONTE-CT]",10765,"revised","2016-02-10T14:59:52.117","2016-02-11T07:50:00.037","C4-161076","C4-161347","Rel-13","29.128","1.0.0","MONTE-CT","","",null,"","","","","",""]
["C4-161289","Clarifications on Editor's notes on MONTE","Huawei","Peter Schmitt",13753,"CR","","Decision","Monitoring-type for NUMBER_OF_UE_PER_LOCATION_CONFIGURATION is defined.\nEditor's notes are removed.\nA recomendation is added on what an HSS should repoort if it gets different results of an configuration request from two nodes (UE registered in MME and","","19","7.1.9","Monitoring Enhancements CT aspects [MONTE-CT]",12890,"revised","2016-02-10T15:02:23.513","2016-02-11T07:50:00.083","","C4-161430","Rel-13","29.336","13.2.0","MONTE-CT","0048","","B",null,"","","","",""]
["C4-161290","Discussion on non IP data transfer over T6a","Cisco Systems Inc","Sridhar Bhaskaran",58580,"discussion","","Decision","","","46","7.2.14","CIoT-CT (CT1)  [CIoT-CT]",18000,"noted","2016-02-11T06:30:16.937","2016-02-11T06:33:51.093","C4-161207","","Rel-13","","","","","","","","","","","",""]
["C4-161291","Impacts on the DNS procedures for CIoT","Ericsson","Yong Yang",42295,"CR","","","The node performing selection function may use DNS procedures enhanced to support DCN to select a suitable SGW/PGW.","","46","7.2.14","CIoT-CT (CT1)  [CIoT-CT]",47000,"revised","2016-02-11T12:38:59.297","2016-02-11T12:59:04.687","C4-161257","C4-161395","Rel-13","29.303","13.2.0","CIoT-CT","0087","1","B",null,"","","","",""]
["C4-161292","Discussion on the possible solution for GW selection","Ericsson","Yong Yang",42295,"discussion","","","With introduction of CIoT related features/optimizations, there are some requirements agreed in SA2 to enhance the current PGW, SGW and MME selection function.  This paper discusses the possible solutions to address those requirements. As the selection of","","46","7.2.14","CIoT-CT (CT1)  [CIoT-CT]",45000,"noted","2016-02-11T12:45:55.440","2016-02-11T12:59:04.733","C4-161256","","","","","","","","","","","","","",""]
["C4-161293","MCPTT data model","Ericsson","Maria-Cruz Bartolome",44824,"CR","","","","","43","7.2.11","Mission Critical Push To Talk over LTE protocol aspects (CT1) [MCPTT-CT]",12021,"revised","2016-02-11T20:25:18.173","2016-02-11T20:26:41.287","C4-161202","C4-161366","Rel-13","29.335","13.0.0","TEI13","0018","1","B",null,"","","","",""]
["C4-161294","Subsciption for allowed services","Huawei","Peter Schmitt",13753,"CR","","Decision","A new paramenter is addded which contains the details of allowed AESE services for a subscriber","","19","7.1.9","Monitoring Enhancements CT aspects [MONTE-CT]",12940,"revised","2016-02-12T09:03:06.513","2016-02-12T09:06:19.423","","C4-161431","Rel-13","23.008","13.3.0","MONTE-CT","0489","","B",null,"","","","",""]
["C4-161295","Length Correction for tVPLMNID and tTimeZone","Nokia Networks","Ulrich Wiehe",6963,"CR","","Agreement","Modify the length definition as originally intended","","54","7.3.7","IMS [TEI13]",12950,"revised","2016-02-12T12:36:49.630","2016-02-12T13:04:13.797","","C4-161388","Rel-13","29.328","13.3.0","TEI11","0556","","F",null,"","","","",""]
["C4-161296","LS Response on MCPTT Group data and affiliation","3GPP TSG SA WG6","Kimmo Kymalainen",19464,"LS in","","Discussion","SA6 would like to thank CT1 for their LS C1-160783 / S6-160007 on on MCPTT Group data and affiliation. \n\nRegarding  the following:\n\nFrom 3GPP TS 23.179 v13.0.0, it indicates that affiliation status is a part of the MCPTT group information stored in th","","43","7.2.11","Mission Critical Push To Talk over LTE protocol aspects (CT1) [MCPTT-CT]",12960,"noted","2016-02-12T13:38:09.747","2016-02-12T13:41:29.083","","","Rel-13","","","MCPTT-CT","","","","",null,"3GPP TSG CT WG1","3GPP TSG CT WG4","S6-160148"]
["C4-161297","Future meeting calendar for information","MCC","Kimmo Kymalainen",19464,"other","","Information","","","170","13","Future meetings",12970,"noted","2016-02-12T14:22:04.710","2016-02-12T14:26:14.247","","","Rel-14","","","","","","","","","","","",""]
["C4-161298","new Diameter application for MCPTT-2 and CSC-13 reference points","ORANGE, HP","Lionel Morand",25150,"pCR","","Approval","Make a reference to the TS 24.384 that defines the content of the MCPTT use profile document.","","43","7.2.11","Mission Critical Push To Talk over LTE protocol aspects (CT1) [MCPTT-CT]",12705,"revised","2016-02-13T10:22:40.257","2016-02-13T10:58:27.660","C4-161270","C4-161439","Rel-13","","","MCPTT-CT","","",null,"","","","","",""]
["C4-161299","Reply to: TAC Allocation as detailed in 3GPP TS 23.003","current meeting","John M Meredith",637,"LS out","","Approval","CT4 thanks GSMA TSG for their LS on TAC Allocation and CT4 likes to inform GSMA that it took GSMAs suggestion into account and updated TS23.003 to clarify the TAC allocation process. In addition the link towards the GSMA TS.06 was added to the reference s","","6","4","Input liaison statements: allocation to agenda items as appropriate",12191,"revised","2016-02-15T01:06:52.520","2016-03-01T15:03:23.073","","C4-161506","","","","","","","","","C4-161219","GSMA TSG"]
["C4-161300","Clarification of TAC allocation","Vodafone","John M Meredith",637,"CR","","Agreement","To the informative reference section the GSMA TS.06 is added. In section 6.3 it is clarifyed that GSMA is allocating the TAC values.","","6","4","Input liaison statements: allocation to agenda items as appropriate",130000,"revised","2016-02-15T01:10:50.153","2016-03-01T15:03:23.090","","C4-161505","Rel-13","23.003","13.4.0","TEI13","0438","","B",null,"","","","",""]
["C4-161301","CT aspects of MTSI Extension on Multi-stream Multiparty Conferencing Media Handling","Ericsson","John M Meredith",637,"WID new","","Agreement","","","7","5","Work item management",10441,"agreed","2016-02-15T01:39:25.737","2016-02-18T23:34:00.330","C4-161044","","Rel-14","","","","","","","","","","","",""]
["C4-161302","SCC AS Restoration","China Mobile","John M Meredith",637,"WID new","","","","","7","5","Work item management",10551,"agreed","2016-02-15T02:22:16.117","2016-02-18T05:03:18.727","C4-161055","","Rel-14","","","","","","","","","","","",""]
["C4-161303","MO Non-IP Data procedures over T6a","Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Nokia Networks","John M Meredith",637,"pCR","","Agreement","","","46","7.2.14","CIoT-CT (CT1)  [CIoT-CT]",20001,"revised","2016-02-15T05:23:58.333","2016-02-18T07:38:57.950","C4-161233","C4-161483","Rel-13","29.128","1.0.0","CIoT-CT","","",null,"","","","","",""]
["C4-161304","MT Non-IP Data procedures over T6a","Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Nokia Networks","John M Meredith",637,"pCR","","Agreement","","","46","7.2.14","CIoT-CT (CT1)  [CIoT-CT]",21001,"revised","2016-02-15T05:37:59.307","2016-02-18T07:38:57.983","C4-161234","C4-161484","Rel-13","29.128","1.0.0","CIoT-CT","","",null,"","","","","",""]
["C4-161305","Questions on non-IP data delivery procedures","CT4","John M Meredith",637,"LS out","","Discussion","CR  23.682 #0160 (S2-160832), agreed at SA2#113, specifies that the User Identity used in the T6a connection establishment and in the MO/MT NIDD procedures may include the user 's IMSI, MSISDN or External ID(s).\n\nCf subclause 5.x.1.2 (T6a Connection Est","","46","7.2.14","CIoT-CT (CT1)  [CIoT-CT]",21003,"revised","2016-02-15T05:49:56.090","2016-02-18T05:26:48.613","","C4-161485","","","","","","","","",null,"S2","S3"]
["C4-161306","Connection management  procedures over T6a","Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Nokia Networks","John M Meredith",637,"pCR","","Agreement","","","46","7.2.14","CIoT-CT (CT1)  [CIoT-CT]",22001,"revised","2016-02-15T05:56:08.803","2016-02-18T07:38:58.027","C4-161235","C4-161487","Rel-13","29.128","1.0.0","CIoT-CT","","",null,"","","","","",""]
["C4-161307","Protocol for Non IP-Data over T6a","Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Nokia Networks","John M Meredith",637,"pCR","","Agreement","","","46","7.2.14","CIoT-CT (CT1)  [CIoT-CT]",23001,"revised","2016-02-15T06:06:32.333","2016-02-18T07:38:58.060","C4-161236","C4-161488","Rel-13","29.128","1.0.0","CIoT-CT","","",null,"","","","","",""]
["C4-161308","New PDN-Type for Celular IoT","Ericsson","John M Meredith",637,"CR","","","","","46","7.2.14","CIoT-CT (CT1)  [CIoT-CT]",24001,"revised","2016-02-15T06:37:19.547","2016-02-18T08:52:22.020","C4-161232","C4-161490","Rel-13","29.272","13.4.0","CIoT-CT","0631","1","B",null,"","","","",""]
["C4-161309","Handover to Non-3GPP Access Not Allowed","Ericsson, Orange","John M Meredith",637,"CR","","","","","52","7.3.5","Addressing and Subscriber Data Handling [TEI13]",11381,"agreed","2016-02-15T07:25:09.320","2016-02-18T08:52:22.067","C4-161138","","Rel-13","23.008","13.3.0","TEI13","0484","1","F","CP-160044","","","","",""]
["C4-161310","ePDG selection with DNS-based Discovery of Regulatory Requirements","Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Nokia Networks","John M Meredith",637,"CR","","Approval","","","52","7.3.5","Addressing and Subscriber Data Handling [TEI13]",12621,"agreed","2016-02-15T07:39:00.657","2016-02-18T05:26:48.643","C4-161262","","Rel-13","23.003","13.4.0","TEI13","0437","1","B","CP-160044","","","","",""]
["C4-161311","LS on New subdomain name for ePDG selection with DNS-based discovery of regulatory requirements","CT4","John M Meredith",637,"LS out","","Approval","An updated ePDG selection procedure has been specified in CR 23.402 #2933 to enable a roaming UE to determine whether the country it is located in mandates or does not mandate the selection of an ePDG in this country, for regulatory requirements (Lawful I","","52","7.3.5","Addressing and Subscriber Data Handling [TEI13]",131100,"revised","2016-02-15T07:40:53.503","2016-02-18T05:26:48.677","","C4-161504","","","","","","","","",null,"GSMA IREG","CT, CT1"]
["C4-161312","Authorize the UE requested APN","Huawei","John M Meredith",637,"CR","","","","","50","7.3.3","EPS AAA interfaces [TEI13]",10991,"agreed","2016-02-15T08:02:17.843","2016-02-19T02:20:15.877","C4-161099","","Rel-13","29.273","13.2.0","TEI13","0448","1","F","CP-160042","","","","",""]
["C4-161313","New PDN-Type for Cellular IoT","Ericsson","John M Meredith",637,"CR","","","","","46","7.2.14","CIoT-CT (CT1)  [CIoT-CT]",25001,"revised","2016-02-15T08:13:47.687","2016-02-19T00:11:16.350","C4-161264","C4-161527","Rel-13","29.002","13.2.0","CIoT-CT","1205","1","B",null,"","","","",""]
["C4-161314","New PDN-Type for Celullar IoT","Ericsson","John M Meredith",637,"CR","","","Allocate code points and data types for the new AVPs.","","46","7.2.14","CIoT-CT (CT1)  [CIoT-CT]",26001,"revised","2016-02-15T08:37:48.760","2016-02-19T00:11:16.397","C4-161265","C4-161528","Rel-13","29.230","13.3.0","CIoT-CT","0520","1","B",null,"","","","",""]
["C4-161315","New PDN-Type for Celular IoT","Ericsson","John M Meredith",637,"CR","","","","","46","7.2.14","CIoT-CT (CT1)  [CIoT-CT]",27001,"revised","2016-02-15T08:45:45.977","2016-02-19T00:11:16.430","C4-161266","C4-161529","Rel-13","23.008","13.3.0","CIoT-CT","0488","1","B",null,"","","","",""]
["C4-161316","User Plane Integrity Protection Indicator","Nokia Networks, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell","John M Meredith",637,"CR","","Agreement","Change of Category.","","57","7.3.10","EGPRS Access Security Enhancements in relation to Cellular IoT",10711,"agreed","2016-02-15T09:09:38.140","2016-02-17T08:19:59.557","C4-161071","","Rel-13","23.008","13.3.0","EASE_EC_GSM","0476","1","B","CP-160039","","","","",""]
["C4-161317","User Plane Integrity Protection Indicator","Nokia Networks, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell","John M Meredith",637,"CR","","Agreement","Change of Category","","57","7.3.10","EGPRS Access Security Enhancements in relation to Cellular IoT",10721,"agreed","2016-02-15T09:14:54.070","2016-02-17T08:19:59.587","C4-161072","","Rel-13","29.002","13.2.0","EASE_EC_GSM","1201","1","B","CP-160039","","","","",""]
["C4-161318","User Plane Integrity Protection Indicator","Nokia Networks, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell","John M Meredith",637,"CR","","Agreement","Change of Category","","57","7.3.10","EGPRS Access Security Enhancements in relation to Cellular IoT",10731,"agreed","2016-02-15T09:19:40.327","2016-02-17T08:19:59.650","C4-161073","","Rel-13","29.272","13.4.0","EASE_EC_GSM","0620","1","B","CP-160039","","","","",""]
["C4-161319","Addition of NB-IoT radio access type to the Access-Restriction-Data feature","Vodafone GmbH, Deutsche Telekom, Huawei","John M Meredith",637,"CR","","Approval","","","46","7.2.14","CIoT-CT (CT1)  [CIoT-CT]",28001,"revised","2016-02-15T09:25:43.103","2016-02-18T05:03:18.757","C4-161211","C4-161491","Rel-13","29.272","13.4.0","CIoT-CT","0630","1","B",null,"","","","",""]
["C4-161320","Addition of NB-IoT radio access type to the Access-Restriction-Data feature","Vodafone GmbH, Deutsche Telekom, Huawei","John M Meredith",637,"CR","","Approval","","","46","7.2.14","CIoT-CT (CT1)  [CIoT-CT]",29001,"revised","2016-02-15T09:34:47.587","2016-02-18T05:03:18.787","C4-161210","C4-161492","Rel-13","29.002","13.2.0","CIoT-CT","1204","1","B",null,"","","","",""]
["C4-161321","Addition of NB-IoT radio access type to the Access-Restriction-Data feature","Vodafone GmbH, Vodafone, Deutsche Telekom, Huawei","John M Meredith",637,"CR","","","","","46","7.2.14","CIoT-CT (CT1)  [CIoT-CT]",30001,"agreed","2016-02-15T09:36:26.567","2016-02-18T05:03:18.817","C4-161208","","Rel-13","23.008","13.3.0","CIoT-CT","0486","1","B","CP-160033","","","","",""]
["C4-161322","Addition of NB-IoT radio access type to the Access-Restriction-Data feature","Vodafone GmbH, Deutsche Telekom, Huawei","John M Meredith",637,"CR","","Approval","","","46","7.2.14","CIoT-CT (CT1)  [CIoT-CT]",31001,"agreed","2016-02-15T09:39:42.533","2016-02-18T05:03:18.850","C4-161212","","Rel-13","29.274","13.4.0","CIoT-CT","1698","1","B","CP-160033","","","","",""]
["C4-161323","Allow SMS for NB-IoT UE without Combined Attach","ZTE","John M Meredith",637,"CR","","Approval","","","46","7.2.14","CIoT-CT (CT1)  [CIoT-CT]",32001,"agreed","2016-02-15T09:56:31.410","2016-02-18T05:03:18.880","C4-161131","","Rel-13","29.272","13.4.0","CIoT-CT","0623","1","B","CP-160033","","","","",""]
["C4-161324","Authorisation for NIDD procedure over  S6t","Huawei, Vodafone","John M Meredith",637,"CR","","Decision","","","46","7.2.14","CIoT-CT (CT1)  [CIoT-CT]",34001,"revised","2016-02-15T10:14:51.267","2016-02-18T08:52:21.943","C4-161242","C4-161530","Rel-13","29.336","13.2.0","CIoT-CT","0046","3","B",null,"","","","",""]
["C4-161325","Definition of  AVP configuration of NIDD","Huawei","John M Meredith",637,"CR","","Decision","","","46","7.2.14","CIoT-CT (CT1)  [CIoT-CT]",36001,"revised","2016-02-15T10:24:38.057","2016-02-18T08:52:21.973","C4-161165","C4-161326","Rel-13","29.230","13.3.0","CIoT-CT","0513","1","B",null,"","","","",""]
["C4-161326","Definition of  AVP configuration of NIDD","Huawei","John M Meredith",637,"CR","","Decision","","","46","7.2.14","CIoT-CT (CT1)  [CIoT-CT]",36002,"agreed","2016-02-15T10:24:50.597","2016-03-01T15:03:23.090","C4-161325","","Rel-13","29.230","13.3.0","CIoT-CT","0513","2","B","CP-160033","","","","",""]
["C4-161327","Resolution of Editor’s notes on EVS over UMTS CS","Qualcomm Incorporated","John M Meredith",637,"CR","","Agreement","","","17","7.1.7","CT aspects of EVS in 3G Circuit-Switched Networks [EVSoCS-CT]",10581,"agreed","2016-02-15T23:09:20.807","2016-02-18T03:15:10.117","C4-161058","","Rel-13","23.153","13.0.0","EVSoCS-CT","0131","1","B","CP-160027","","","","",""]
["C4-161328","Release of WebRTC Data Channels","Alcatel-Lucent, Nokia Networks","John M Meredith",637,"CR","","Approval","","","18","7.1.8","H.248 Aspects of WebRTC Data Channel on IMS Access Gateway",10081,"agreed","2016-02-15T23:19:41.387","2016-02-18T05:26:48.550","C4-161273","","Rel-13","23.334","13.4.0","WebRTCH248DC","0104","2","B","CP-160028","","","","",""]
["C4-161329","WebRTC Data Channels","Alcatel-Lucent, Nokia Networks","John M Meredith",637,"CR","","Approval","","","18","7.1.8","H.248 Aspects of WebRTC Data Channel on IMS Access Gateway",12741,"agreed","2016-02-15T23:26:45.743","2016-02-18T05:26:48.580","C4-161274","","Rel-13","29.334","13.3.0","WebRTCH248DC","0105","2","B","CP-160028","","","","",""]
["C4-161330","Support of enhanced bandwidth negotiation mechanism for MTSI sessions","Ericsson","John M Meredith",637,"CR","","","","","35","7.2.3","CT aspects of QoS End to End MTSI extensions (CT3) [QOSE2EMTSI-CT]",10491,"revised","2016-02-15T23:57:22.880","2016-02-18T09:51:30.267","C4-161049","C4-161496","Rel-13","23.334","13.4.0","QOSE2EMTSI-CT","0106","1","B",null,"","","","",""]
["C4-161331","Support of enhanced bandwidth negotiation mechanism for MTSI sessions","Ericsson","John M Meredith",637,"CR","","","","","35","7.2.3","CT aspects of QoS End to End MTSI extensions (CT3) [QOSE2EMTSI-CT]",10501,"agreed","2016-02-15T23:58:11.190","2016-02-19T02:20:15.923","C4-161050","","Rel-13","29.334","13.3.0","QOSE2EMTSI-CT","0107","1","B","CP-160034","","","","",""]
["C4-161332","Support of enhanced bandwidth negotiation mechanism for MTSI sessions","Ericsson","John M Meredith",637,"CR","","","","","35","7.2.3","CT aspects of QoS End to End MTSI extensions (CT3) [QOSE2EMTSI-CT]",10511,"agreed","2016-02-15T23:59:19.677","2016-02-19T02:20:16.003","C4-161051","","Rel-13","23.333","13.0.0","QOSE2EMTSI-CT","0091","1","B","CP-160034","","","","",""]
["C4-161333","Support of enhanced bandwidth negotiation mechanism for MTSI sessions","Ericsson","John M Meredith",637,"CR","","","","","35","7.2.3","CT aspects of QoS End to End MTSI extensions (CT3) [QOSE2EMTSI-CT]",10521,"agreed","2016-02-16T00:00:26.007","2016-02-19T02:20:16.097","C4-161052","","Rel-13","29.333","13.0.0","QOSE2EMTSI-CT","0084","1","B","CP-160034","","","","",""]
["C4-161334","Support of enhanced bandwidth negotiation mechanism for MTSI sessions","Ericsson","John M Meredith",637,"CR","","","","","35","7.2.3","CT aspects of QoS End to End MTSI extensions (CT3) [QOSE2EMTSI-CT]",10531,"agreed","2016-02-16T00:01:13.960","2016-02-19T02:20:16.143","C4-161053","","Rel-13","29.238","13.0.0","QOSE2EMTSI-CT","0063","1","B","CP-160034","","","","",""]
["C4-161335","Support of enhanced bandwidth negotiation mechanism for MTSI sessions","Ericsson","John M Meredith",637,"CR","","","","","35","7.2.3","CT aspects of QoS End to End MTSI extensions (CT3) [QOSE2EMTSI-CT]",10541,"agreed","2016-02-16T00:01:59.963","2016-02-19T02:20:16.220","C4-161054","","Rel-13","29.332","13.0.0","QOSE2EMTSI-CT","0198","1","B","CP-160034","","","","",""]
["C4-161336","18 bits PDCP PDU Number","Nokia Networks, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell","John M Meredith",637,"CR","","","","","58","7.3.11","18 bits PDCP PDU Number",11821,"revised","2016-02-16T00:36:32.147","2016-02-18T05:23:36.953","C4-161182","C4-161498","Rel-13","29.281","13.0.0","TEI13, LTE_CA_enh_b5C-Core","0077","1","F",null,"","","","",""]
["C4-161337","Reply to: LS on extension to field length of PDCP Sequence Number","current meeting","John M Meredith",637,"LS out","","Approval","CT4 kindly request RAN2 and RAN3 to provide feedback on the attached 29.281 CR and to answer the questions posed, taking into account the limitation of using the Support Extension Header Notification.","","58","7.3.11","18 bits PDCP PDU Number",10301,"revised","2016-02-16T00:43:13.250","2016-02-18T05:23:36.983","","C4-161463","Rel-13","","","LTE_CA_enh_b5C-Core","","","","","C4-161030","3GPP TSG RAN WG2",null,"R2-156977"]
["C4-161338","Delay Tolerant Connection Indication","Ericsson, MCC","John M Meredith",637,"CR","","","","","42","7.2.10","Extended DRX cycle for power consumption optimization (CT1) [eDRX]",11721,"agreed","2016-02-16T01:18:17.660","2016-02-18T05:02:20.867","C4-161172","","Rel-13","29.060","13.3.0","eDRX-CT","1033","1","B","CP-160030","","","","",""]
["C4-161339","Triggering MT SM retransmission by the SMS GMSC to a UE in eDRX during inter MME/SGSN mobility procedure for GTPv1","Ericsson, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Vodafone, Verizon, Nokia Networks","John M Meredith",637,"CR","","","","","42","7.2.10","Extended DRX cycle for power consumption optimization (CT1) [eDRX]",11731,"agreed","2016-02-16T01:31:13.053","2016-02-18T05:02:20.897","C4-161173","","Rel-13","29.060","13.3.0","eDRX-CT","1034","1","B","CP-160030","","","","",""]
["C4-161340","Triggering MT SM retransmission by the SMS GMSC to a UE in eDRX during inter MME/SGSN mobility procedure","Ericsson, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Vodafone, Verizon, Nokia Networks","John M Meredith",637,"CR","","","","","42","7.2.10","Extended DRX cycle for power consumption optimization (CT1) [eDRX]",11741,"agreed","2016-02-16T01:36:48.827","2016-02-18T05:02:20.943","C4-161174","","Rel-13","29.274","13.4.0","eDRX-CT","1695","1","B","CP-160030","","","","",""]
["C4-161341","ePDG retrieval of WLAN Location Information","Alcatel-Lucent","Bruno Landais",68755,"CR","","Approval","","","41","7.2.9","Support of Emergency services over WLAN Ã¢â‚¬â€œ phase 1 (CT1) [SEW1-CT]",11571,"agreed","2016-02-16T02:07:08.103","2016-02-18T05:25:46.510","C4-161157","","Rel-13","29.273","13.2.0","TEI13, SEW1-CT","0450","1","F","CP-160037","","","","",""]
["C4-161342","Incorrect use of the term \"full hexadecimal representation\" to mean binary encoding","Oracle Corporation","John M Meredith",637,"CR","","Approval","","","48","7.3.1","GTP and PMIP [TEI13]",10002,"agreed","2016-02-16T02:08:22.840","2016-02-18T05:03:18.477","C4-161134","","Rel-13","29.274","13.4.0","TEI13","1688","1","F","CP-160038","","","","",""]
["C4-161343","Incorrect use of the term \"full hexadecimal representation\" to mean binary encoding","Oracle Corporation","John M Meredith",637,"CR","","Approval","","","48","7.3.1","GTP and PMIP [TEI13]",10011,"agreed","2016-02-16T02:10:21.870","2016-03-01T15:03:23.090","C4-161135","","Rel-13","29.060","13.3.0","TEI13","1032","1","F","CP-160038","","","","",""]
["C4-161344","Data returned in IMSPublicIdentity correction, new EnhancedPublicIdentifiers class","Ericsson, Nokia Networks, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Hewlett Packard Enterprise","Maria-Cruz Bartolome",44824,"CR","","","","","54","7.3.7","IMS [TEI13]",10892,"agreed","2016-02-16T02:10:30.247","2016-02-18T05:52:14.963","C4-161263","","Rel-13","29.328","13.3.0","TEI13","0543","2","F","CP-160046","","","","",""]
["C4-161345","Pseudo-CR on Removing Editor's Note on IWK-SCEF Authorization and Configuration Failure at IWK-SCEF","Cisco Systems Inc","Sridhar Bhaskaran",58580,"pCR","","Approval","It is proposed to remove the editor's note in sub-clause 5.3.2 and to address the editor's note in sub-clause 5.4.3 specify that the MME/SGSN shall send a Notify Request to the HSS to inform the configuration status at the IWK-SCEF as specified in 3GPP TS","","19","7.1.9","Monitoring Enhancements CT aspects [MONTE-CT]",10001,"revised","2016-02-16T02:13:33.780","2016-02-18T05:25:46.743","C4-161060","C4-161462","Rel-13","","1.0.0","","","",null,"","","","","",""]
["C4-161346","Notifying the status of MONTE event configuration at the IWK-SCEF to the HSS","Cisco Systems Inc","Sridhar Bhaskaran",58580,"CR","","Approval","","","19","7.1.9","Monitoring Enhancements CT aspects [MONTE-CT]",10611,"revised","2016-02-16T02:15:04.697","2016-02-18T05:25:46.773","C4-161061","C4-161465","Rel-13","29.272","13.4.0","MONTE-CT","0618","1","B",null,"","","","",""]
["C4-161347","Pseudo-CR on cleanup of 29.128","Huawei","Peter Schmitt",13753,"pCR","","Decision","","","19","7.1.9","Monitoring Enhancements CT aspects [MONTE-CT]",10766,"revised","2016-02-16T02:16:20.120","2016-02-18T05:02:21.223","C4-161288","C4-161467","Rel-13","29.128","1.0.0","MONTE-CT","","",null,"","","","","",""]
["C4-161348","AVAILABILITY_AFTER_DDN_FAILURE reporting","Huawei","Peter Schmitt",13753,"CR","","Decision","","","19","7.1.9","Monitoring Enhancements CT aspects [MONTE-CT]",10771,"revised","2016-02-16T02:17:31.367","2016-03-01T15:03:23.090","C4-161077","C4-161468","Rel-13","29.336","13.2.0","MONTE-CT","0037","1","B",null,"","","","",""]
["C4-161349","Protocol Type in Create Session Request","Huawei","John M Meredith",637,"CR","","Agreement","","","48","7.3.1","GTP and PMIP [TEI13]",11221,"agreed","2016-02-16T02:28:16.780","2016-02-18T05:05:30.887","C4-161122","","Rel-13","29.274","13.4.0","TEI13","1686","1","F","CP-160038","","","","",""]
["C4-161350","Clarification on usage of P and T needs","Huawei Tech.(UK) Co., Ltd","Peter Schmitt",13753,"CR","","Decision","","","19","7.1.9","Monitoring Enhancements CT aspects [MONTE-CT]",10791,"agreed","2016-02-16T02:35:47.850","2016-02-19T00:11:16.477","C4-161079","","Rel-13","23.008","13.3.0","MONTE-CT","0477","1","B","CP-160029","","","","",""]
["C4-161351","GTP-C Load Control - Mix of NAPTR records with \"s\" and \"a\" flags","Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Nokia Networks","John M Meredith",637,"CR","","Approval","","","48","7.3.1","GTP and PMIP [TEI13]",11601,"agreed","2016-02-16T02:37:37.377","2016-02-18T05:25:46.540","C4-161160","","Rel-13","29.303","13.2.0","GOCMe, TEI13","0084","1","F","CP-160038","","","","",""]
["C4-161352","Pseudo-CR on  overload","Huawei Tech.(UK) Co., Ltd","Peter Schmitt",13753,"pCR","","Decision","At the last meeting  the annex describing overload reporting by SCEF was agreed but the messages were not updated. The  AVPs to report overload are added to Reporting-Information-Answer command.","","19","7.1.9","Monitoring Enhancements CT aspects [MONTE-CT]",10801,"approved","2016-02-16T02:47:13.607","2016-03-01T15:03:23.107","C4-161080","","Rel-13","29.128","1.0.0","MONTE-CT","","",null,"","","","","",""]
["C4-161353","Transferring AAA identifier to the PGW","Ericsson, Orange, Telia Sonera","John M Meredith",637,"CR","","","","","48","7.3.1","GTP and PMIP [TEI13]",11682,"revised","2016-02-16T02:57:24.827","2016-02-18T05:02:20.973","C4-161276","C4-161459","Rel-13","29.274","13.4.0","TEI13","1693","2","F",null,"","","","",""]
["C4-161354","HSS restart MONTE impacts","Huawei Tech.(UK) Co., Ltd","Peter Schmitt",13753,"CR","","Decision","","","19","7.1.9","Monitoring Enhancements CT aspects [MONTE-CT]",10811,"revised","2016-02-16T03:00:40.077","2016-03-01T15:03:23.107","C4-161081","C4-161470","Rel-13","23.007","13.3.0","MONTE-CT","0329","1","B",null,"","","","",""]
["C4-161355","Comprehension requirement for PDCP PDU Number","Ericsson","John M Meredith",637,"CR","","","","","48","7.3.1","GTP and PMIP [TEI13]",11711,"revised","2016-02-16T03:02:40.523","2016-02-18T05:02:21.007","C4-161171","C4-161461","Rel-13","29.281","13.0.0","TEI13","0076","1","F",null,"","","","",""]
["C4-161356","Add cause values to TWAN mapping table","Huawei","John M Meredith",637,"CR","","","","","95","8.3.1","GTP and PMIP [TEI12]",10961,"revised","2016-02-16T03:21:51.450","2016-02-18T05:25:46.447","C4-161096","C4-161464","Rel-12","29.274","12.11.0","TEI12","1683","1","F",null,"","","","",""]
["C4-161357","Add cause values to TWAN mapping table","Huawei","John M Meredith",637,"CR","","","","","95","8.3.1","GTP and PMIP [TEI12]",10971,"agreed","2016-02-16T03:25:28.790","2016-02-18T05:25:46.477","C4-161097","","Rel-13","29.274","13.4.0","TEI13","1684","1","F","CP-160016","","","","",""]
["C4-161358","Restart of SCEF","Huawei Tech.(UK) Co., Ltd","Peter Schmitt",13753,"CR","","Decision","A procedure description is added how to traet the sceanrio of SCEF restart.","","19","7.1.9","Monitoring Enhancements CT aspects [MONTE-CT]",10821,"revised","2016-02-16T03:28:17.143","2016-03-01T15:03:23.107","C4-161082","C4-161472","Rel-13","23.007","13.3.0","MONTE-CT","0330","1","B",null,"","","","",""]
["C4-161359","Reporting of the start and stop of the reporting of monitoring events","Huawei Tech.(UK) Co., Ltd","Peter Schmitt",13753,"CR","","Decision","A new AVP is added to RIR commad  to indicate that the event is suspended, resumed or should be canceled.","","19","7.1.9","Monitoring Enhancements CT aspects [MONTE-CT]",10841,"revised","2016-02-16T03:51:47.467","2016-03-01T15:03:23.107","C4-161084","C4-161508","Rel-13","29.336","13.2.0","MONTE-CT","0040","1","B",null,"","","","",""]
["C4-161360","Fix the issue on HSS restart procedure","NEC EUROPE LTD","John M Meredith",637,"CR","","Approval","","","51","7.3.4","Restoration Procedures [TEI13]",10701,"agreed","2016-02-16T05:28:48.663","2016-02-18T05:02:20.833","C4-161070","","Rel-13","29.272","13.4.0","TEI13","0619","1","F","CP-160043","","","","",""]
["C4-161361","Correct the partial failure handling on SGW","Huawei","John M Meredith",637,"CR","","Agreement","","","51","7.3.4","Restoration Procedures [TEI13]",11231,"agreed","2016-02-16T05:37:15.303","2016-02-18T07:38:58.107","C4-161123","","Rel-13","23.007","13.3.0","TEI13","0331","1","F","CP-160043","","","","",""]
["C4-161362","Introduction of AAA-1 interface","Huawei","Peter Schmitt",13753,"CR","","Decision","","","43","7.2.11","Mission Critical Push To Talk over LTE protocol aspects (CT1) [MCPTT-CT]",10882,"revised","2016-02-16T05:53:57.017","2016-03-01T15:03:23.107","C4-161244","C4-161502","Rel-13","29.228","13.0.0","MCPTT-CT","0661","4","B",null,"","","","",""]
["C4-161363","DNS procedures for Decor","DOCOMO Communications Lab.","John M Meredith",637,"CR","","Agreement","","","28","7.1.18","Dedicated Core Networks [DECOR-CT]",11761,"revised","2016-02-16T06:05:19.140","2016-02-17T08:19:59.713","C4-161176","C4-161365","Rel-13","29.303","13.2.0","DECOR-CT","0086","1","B",null,"","","","",""]
["C4-161364","Clarification on the use of UE Usage Type","Ericsson, NTT DOCOMO","John M Meredith",637,"CR","","","","","28","7.1.18","Dedicated Core Networks [DECOR-CT]",11691,"agreed","2016-02-16T07:09:14.047","2016-02-18T05:02:21.037","C4-161169","","Rel-13","29.303","13.2.0","DECOR-CT","0085","1","B","CP-160022","","","","",""]
["C4-161365","DNS procedures for Decor","DOCOMO Communications Lab.","John M Meredith",637,"CR","","Agreement","","","28","7.1.18","Dedicated Core Networks [DECOR-CT]",11762,"revised","2016-02-16T07:24:56.437","2016-02-18T08:54:07.850","C4-161363","C4-161482","Rel-13","29.303","13.2.0","DECOR-CT","0086","2","B",null,"","","","",""]
["C4-161366","MCPTT data model","Ericsson","Maria-Cruz Bartolome",44824,"CR","","","","","43","7.2.11","Mission Critical Push To Talk over LTE protocol aspects (CT1) [MCPTT-CT]",12022,"withdrawn","2016-02-16T07:44:09.800",null,"C4-161293","","Rel-13","29.335","13.0.0","TEI13","0018","2","B",null,"","","","",""]
["C4-161367","PDN Connection Charging ID for NBIFOM","CT4","John M Meredith",637,"LS out","","Decision","","","38","7.2.6","IP Flow Mobility support for S2a and S2b Interfaces on stage 3 (CT1) [NBIFOM]",136600,"revised","2016-02-16T08:09:22.740","2016-02-18T05:02:21.067","","C4-161466","Rel-13","","","","","","","","C4-161221","SA5"]
["C4-161368","WebRTC media plane optimization procedure","Nokia Networks, Alcatel-Lucent","John M Meredith",637,"CR","","Agreement","","","44","7.2.12","Enhancements to WEBRTC interoperability stage 3 (CT1)  [eWebRTCi_CT]",11852,"agreed","2016-02-16T23:06:25.220","2016-02-18T05:25:46.243","C4-161272","","Rel-13","23.334","13.4.0","eWebRTCi-CT","0107","2","B","CP-160032","","","","",""]
["C4-161369","WebRTC gateway configuration for end-to-end WebRTC calls (stage 3)","Alcatel-Lucent","John M Meredith",637,"CR","","Approval","","","44","7.2.12","Enhancements to WEBRTC interoperability stage 3 (CT1)  [eWebRTCi_CT]",10101,"agreed","2016-02-16T23:21:15.210","2016-02-18T05:25:46.290","C4-161010","","Rel-13","29.334","13.3.0","eWebRTCi-CT","0106","1","B","CP-160032","","","","",""]
["C4-161370","TrGW configuration for end-to-end WebRTC calls (stage 3)","Alcatel-Lucent","John M Meredith",637,"CR","","Approval","","","44","7.2.12","Enhancements to WEBRTC interoperability stage 3 (CT1)  [eWebRTCi_CT]",10111,"agreed","2016-02-16T23:26:21.967","2016-02-18T05:25:46.323","C4-161011","","Rel-13","29.238","13.0.0","eWebRTCi-CT","0062","1","B","CP-160032","","","","",""]
["C4-161371","Removal of references to TS 26.235","Ericsson","John M Meredith",637,"CR","","","","","56","7.3.9","H.248 Interfaces",10451,"agreed","2016-02-16T23:38:45.833","2016-02-17T08:19:59.743","C4-161045","","Rel-13","23.333","13.0.0","TEI13","0090","1","F","CP-160048","","","","",""]
["C4-161372","Removal of references to TS 26.236","Ericsson","John M Meredith",637,"CR","","","","","56","7.3.9","H.248 Interfaces",10471,"agreed","2016-02-16T23:48:18.287","2016-02-17T08:19:59.777","C4-161047","","Rel-13","29.232","13.0.0","TEI13","0658","1","F","CP-160048","","","","",""]
["C4-161373","Monitoring update and Reporting of update result","Huawei, Orange, Telecom Italia","Peter Schmitt",13753,"CR","","Decision","","","39","7.2.7","CT aspects of enhancements to Proximity-based Services extensions (CT1) [eProSe-Ext-CT]",10863,"agreed","2016-02-17T00:29:06.690","2016-02-19T00:11:16.523","C4-161287","","Rel-13","29.345","13.0.0","eProSe-Ext-CT","0036","3","B","CP-160036","","","","",""]
["C4-161374","Addition of ProSe Application Code Prefix and ProSe Application Code Suffix formats","QUALCOMM Incorporated","Zhibin Wu",49530,"CR","","Agreement","","","39","7.2.7","CT aspects of enhancements to Proximity-based Services extensions (CT1) [eProSe-Ext-CT]",10571,"agreed","2016-02-17T00:42:45.920","2016-02-18T09:51:30.047","C4-161057","","Rel-13","23.003","13.4.0","eProSe-Ext-CT","0434","1","B","CP-160036","","","","",""]
["C4-161375","Inter-PLMN discovery transmission support","Qualcomm Incorporated","Zhibin Wu",49530,"CR","","Agreement","","","39","7.2.7","CT aspects of enhancements to Proximity-based Services extensions (CT1) [eProSe-Ext-CT]",11171,"agreed","2016-02-17T00:50:23.747","2016-02-18T09:51:30.093","C4-161117","","Rel-13","29.345","13.0.0","eProSe-Ext-CT","0037","1","F","CP-160036","","","","",""]
["C4-161376","Adding security related parameters for restricted ProSe direct discovery authorization","Qualcomm Incorporated","Zhibin Wu",49530,"CR","","Agreement","","","39","7.2.7","CT aspects of enhancements to Proximity-based Services extensions (CT1) [eProSe-Ext-CT]",11181,"agreed","2016-02-17T01:00:56.727","2016-02-18T09:51:30.140","C4-161118","","Rel-13","29.345","13.0.0","eProSe-Ext-CT","0038","1","F","CP-160036","","","","",""]
["C4-161377","Support open discovery with application-controlled extension","Qualcomm Incorporated","Zhibin Wu",49530,"CR","","Agreement","","","39","7.2.7","CT aspects of enhancements to Proximity-based Services extensions (CT1) [eProSe-Ext-CT]",11191,"agreed","2016-02-17T01:08:23.040","2016-02-18T09:51:30.170","C4-161119","","Rel-13","29.345","13.0.0","eProSe-Ext-CT","0039","1","F","CP-160036","","","","",""]
["C4-161378","S11-U tunneling for MO/MT data transport in control plane (SGi based) - with new S11-U F-TEIDs","Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Nokia Networks, Verizon, AT&T, Orange, China Mobile","John M Meredith",637,"CR","","Approval","","","46","7.2.14","CIoT-CT (CT1)  [CIoT-CT]",38001,"revised","2016-02-17T01:13:41.950","2016-02-18T05:25:46.573","C4-161145","C4-161469","Rel-13","29.274","13.4.0","CIoT-CT","1689","1","B",null,"","","","",""]
["C4-161379","S11-U tunneling for MO/MT data transport in control plane (SGi based)","Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Nokia Networks","John M Meredith",637,"CR","","Approval","","","46","7.2.14","CIoT-CT (CT1)  [CIoT-CT]",40001,"agreed","2016-02-17T01:17:39.863","2016-02-18T05:25:46.603","C4-161147","","Rel-13","29.281","13.0.0","CIoT-CT","0074","1","B","CP-160033","","","","",""]
["C4-161380","Monitoring update and Reporting of update result","Huawei","Peter Schmitt",13753,"CR","","Decision","","","39","7.2.7","CT aspects of enhancements to Proximity-based Services extensions (CT1) [eProSe-Ext-CT]",10865,"agreed","2016-02-17T01:25:44.083","2016-02-19T00:11:16.570","C4-161246","","Rel-13","29.230","13.3.0","eProSe-Ext-CT","0517","1","B","CP-160036","","","","",""]
["C4-161381","End Marker handling by MME","Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Nokia Networks","John M Meredith",637,"CR","","Approval","","","46","7.2.14","CIoT-CT (CT1)  [CIoT-CT]",41001,"agreed","2016-02-17T01:28:43.593","2016-02-18T05:25:46.650","C4-161148","","Rel-13","29.281","13.0.0","CIoT-CT","0075","1","B","CP-160033","","","","",""]
["C4-161382","Allocation of new Diameter Application ID and commands code for PC2 protocol","Huawei","Peter Schmitt",13753,"CR","","Decision","","","39","7.2.7","CT aspects of enhancements to Proximity-based Services extensions (CT1) [eProSe-Ext-CT]",12481,"revised","2016-02-17T01:38:50.787","2016-03-01T15:03:23.120","C4-161248","C4-161536","Rel-13","29.230","13.3.0","eProSe-Ext-CT","0519","1","B",null,"","","","",""]
["C4-161383","S11-U Error Indication handling","Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Nokia Networks","John M Meredith",637,"CR","","Approval","","","46","7.2.14","CIoT-CT (CT1)  [CIoT-CT]",42001,"agreed","2016-02-17T02:13:35.307","2016-02-18T05:25:46.680","C4-161149","","Rel-13","23.007","13.3.0","CIoT-CT","0332","1","B","CP-160033","","","","",""]
["C4-161384","S11-U Error Indication handling","Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Nokia Networks","John M Meredith",637,"CR","","Approval","","","46","7.2.14","CIoT-CT (CT1)  [CIoT-CT]",42002,"withdrawn","2016-02-17T02:13:46.040",null,"C4-161149","","Rel-13","23.007","13.3.0","CIoT-CT","0332","2","B",null,"","","","",""]
["C4-161385","Cleanup of the editor's notes for reporting remote UE","Ericsson","Yong Yang",42295,"CR","","","","","39","7.2.7","CT aspects of enhancements to Proximity-based Services extensions (CT1) [eProSe-Ext-CT]",11701,"revised","2016-02-17T02:23:06.030","2016-02-18T05:02:21.100","C4-161170","C4-161507","Rel-13","29.274","13.4.0","eProSe-Ext-CT","1694","1","B",null,"","","","",""]
["C4-161386","Encoding of  IP-SM-GW Number","Hewlett-Packard Enterprise","Anders Askerup",26315,"CR","","Agreement","","","162","10.18","IMS [TEI8, TEI9]",11041,"not pursued","2016-02-17T02:25:45.243","2016-02-17T08:19:59.823","C4-161104","","Rel-8","29.328","8.18.0","TEI8","0545","1","F",null,"","","","",""]
["C4-161387","Local Time Zone for CS retrieval","Ericsson","Maria-Cruz Bartolome",44824,"CR","","","","","54","7.3.7","IMS [TEI13]",10911,"agreed","2016-02-17T02:35:33.313","2016-02-18T03:15:10.150","C4-161091","","Rel-13","29.328","13.3.0","TEI13","0544","1","F","CP-160046","","","","",""]
["C4-161388","Length Correction for tVPLMNID and tTimeZone","Nokia Solutions & Networks (S)","Ulrich Wiehe",6963,"CR","","Agreement","","","54","7.3.7","IMS [TEI13]",13880,"agreed","2016-02-17T02:49:02.990","2016-02-17T08:19:59.867","C4-161295","","Rel-13","29.328","13.3.0","TEI11","0556","1","F","CP-160046","","","","",""]
["C4-161389","Encoding of  IP-SM-GW Number","Hewlett-Packard Enterprise","Anders Askerup",26315,"CR","","Agreement","","","162","10.18","IMS [TEI8, TEI9]",0,"agreed","2016-02-17T03:04:48.657","2016-02-17T08:19:59.900","C4-161109","","Rel-12","29.328","12.10.0","TEI12","0550","1","F","CP-160013","","","","",""]
["C4-161390","Encoding of  IP-SM-GW Number","Hewlett-Packard Enterprise","Anders Askerup",26315,"CR","","Agreement","","","162","10.18","IMS [TEI8, TEI9]",0,"agreed","2016-02-17T03:07:04.407","2016-02-17T08:19:59.947","C4-161110","","Rel-13","29.328","13.3.0","TEI12","0551","1","A","CP-160013","","","","",""]
["C4-161391","IP-SW-GW number format","Hewlett-Packard Enterprise","Anders Askerup",26315,"CR","","Agreement","","","162","10.18","IMS [TEI8, TEI9]",0,"agreed","2016-02-17T03:12:58.570","2016-02-17T08:19:59.977","C4-161115","","Rel-12","23.008","12.9.0","TEI12","0482","1","F","CP-160013","","","","",""]
["C4-161392","IP-SW-GW number format","Hewlett-Packard Enterprise","Anders Askerup",26315,"CR","","Agreement","","","162","10.18","IMS [TEI8, TEI9]",0,"agreed","2016-02-17T03:14:19.767","2016-02-17T08:20:00.023","C4-161116","","Rel-13","23.008","13.3.0","TEI12","0483","1","A","CP-160013","","","","",""]
["C4-161393","Impacts on the DNS procedures for CIoT with introduction of NB-IoT and Non-IP","Ericsson LM","Yong Yang",42295,"LS out","","Decision","CT4 discussed the possible solutions to select a suitable SGW/PGW which supports the relevant CIoT features, based on the requirements specified in CR 2948 of TS 23.401 and the LS on guidance by SA2 on CIOT (S2-160910).\n\nAccording to the stage 2 require","","46","7.2.14","CIoT-CT (CT1)  [CIoT-CT]",45005,"revised","2016-02-17T03:17:52.927","2016-02-18T05:02:21.130","","C4-161471","Rel-13","","","NB_IOT, CIoT-CT","","","","",null,"SA2"]
["C4-161394","Encoding of  SC Address","Hewlett-Packard Enterprise","Anders Askerup",26315,"CR","","Agreement","","","162","10.18","IMS [TEI8, TEI9]",11241,"agreed","2016-02-17T03:25:35.040","2016-02-19T00:11:16.633","C4-161124","","Rel-10","29.328","10.14.0","TEI10","0552","1","F","CP-160014","","","","",""]
["C4-161395","Impacts on the DNS procedures for CIoT","Ericsson","John M Meredith",637,"CR","","","","","46","7.2.14","CIoT-CT (CT1)  [CIoT-CT]",47001,"revised","2016-02-17T03:26:55.053","2016-02-18T05:02:21.160","C4-161291","C4-161473","Rel-13","29.303","13.2.0","CIoT-CT","0087","2","B",null,"","","","",""]
["C4-161396","Encoding of  SC Address","Hewlett-Packard Enterprise","Anders Askerup",26315,"CR","","Agreement","","","162","10.18","IMS [TEI8, TEI9]",11251,"agreed","2016-02-17T03:27:10.513","2016-03-01T15:03:23.120","C4-161125","","Rel-11","29.328","11.15.0","TEI10","0553","1","A","CP-160014","","","","",""]
["C4-161397","Encoding of  SC Address","Hewlett-Packard Enterprise","Anders Askerup",26315,"CR","","Agreement","","","162","10.18","IMS [TEI8, TEI9]",11261,"agreed","2016-02-17T03:28:28.700","2016-02-19T00:11:16.680","C4-161126","","Rel-12","29.328","12.10.0","TEI10","0554","1","A","CP-160014","","","","",""]
["C4-161398","Encoding of  SC Address","Hewlett-Packard Enterprise","Anders Askerup",26315,"CR","","Agreement","","","162","10.18","IMS [TEI8, TEI9]",11271,"agreed","2016-02-17T03:29:31.067","2016-02-19T00:11:16.710","C4-161127","","Rel-13","29.328","13.3.0","TEI10","0555","1","A","CP-160014","","","","",""]
["C4-161399","RAT-Type extension for NB-IoT","Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Nokia Networks","John M Meredith",637,"CR","","Approval","","","46","7.2.14","CIoT-CT (CT1)  [CIoT-CT]",48001,"agreed","2016-02-17T03:38:43.803","2016-02-18T05:25:46.697","C4-161146","","Rel-13","29.274","13.4.0","CIoT-CT","1690","1","B","CP-160033","","","","",""]
["C4-161400","P-CSCF restoration not prioritized for WLAN","Nokia Networks, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell","Jan Kåll",69918,"CR","","","","","13","7.1.3","P-CSCF restoration enhancements with WLAN [PCSCF_RES_WLAN]",11791,"agreed","2016-02-17T05:20:23.257","2016-02-18T23:39:13.623","C4-161179","","Rel-13","23.380","13.1.0","PCSCF_RES_WLAN","0083","1","F","CP-160025","","","","",""]
["C4-161401","Transfer of non IP PDN to peer MME during mobility","Cisco Systems Inc","John M Meredith",637,"CR","","Approval","","","46","7.2.14","CIoT-CT (CT1)  [CIoT-CT]",50001,"revised","2016-02-17T05:23:53.823","2016-02-18T05:25:46.383","C4-161206","C4-161480","Rel-13","29.274","13.4.0","CIoT-CT","1697","1","B",null,"","","","",""]
["C4-161402","Result-Codes for P-CSCF Restoration","Nokia Networks, Alcatel-Lucent, Alcatel-Lucent Bell","Jan Kåll",69918,"CR","","","","","13","7.1.3","P-CSCF restoration enhancements with WLAN [PCSCF_RES_WLAN]",11801,"agreed","2016-02-17T05:42:59.697","2016-02-18T23:39:13.593","C4-161180","","Rel-13","23.380","13.1.0","PCSCF_RES_WLAN","0084","1","F","CP-160025","","","","",""]
["C4-161403","Storage for CIoT control plane optimization related information at MME","Cisco Systems Inc","John M Meredith",637,"CR","","Approval","","","46","7.2.14","CIoT-CT (CT1)  [CIoT-CT]",63001,"agreed","2016-02-17T05:48:14.737","2016-02-18T05:25:46.417","C4-161239","","Rel-13","23.008","13.3.0","CIoT-CT","0487","1","B","CP-160033","","","","",""]
["C4-161404","Protocol change for introducing new non-IP PDN type","Ericsson","John M Meredith",637,"CR","","","","","46","7.2.14","CIoT-CT (CT1)  [CIoT-CT]",49001,"revised","2016-02-17T06:01:23.203","2016-02-18T06:17:42.187","C4-161261","C4-161476","Rel-13","29.274","13.4.0","CIoT-CT","1705","1","B",null,"","","","",""]
["C4-161405","Result-Codes for P-CSCF Restoration","Nokia Networks, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell","Jan Kåll",69918,"CR","","","","","13","7.1.3","P-CSCF restoration enhancements with WLAN [PCSCF_RES_WLAN]",12041,"agreed","2016-02-17T06:02:50.173","2016-02-18T23:37:48.200","C4-161204","CP-160153","Rel-13","29.273","13.2.0","ePCSCF_WLAN","0452","1","F","CP-160026","","","","",""]
["C4-161406","Diameter message priority over S6m, S6n,  S6t","Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Nokia Networks, ACS, OEC","Jean-Jacques Trottin",68942,"CR","","Agreement","","","30","7.1.20","Diameter Message Priority [DiaPri]",11911,"agreed","2016-02-17T06:15:59.870","2016-02-19T00:11:16.757","C4-161191","","Rel-13","29.336","13.2.0","DiaPri","0047","1","B","CP-160023","","","","",""]
["C4-161407","Diameter message priority over S6c, SGd, GddDiameter message priority over S6c, SGd, Gdd","Alcatel-Lucent","Jean-Jacques Trottin",68942,"CR","","Agreement","","","30","7.1.20","Diameter Message Priority [DiaPri]",11921,"agreed","2016-02-17T06:19:36.337","2016-02-19T00:11:16.803","C4-161192","","Rel-13","29.338","13.0.0","DiaPri","0020","1","B","CP-160023","","","","",""]
["C4-161408","Diameter message priority over T4","Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Nokia Networks, ACS, OEC","Jean-Jacques Trottin",68942,"CR","","Agreement","","","30","7.1.20","Diameter Message Priority [DiaPri]",11940,"revised","2016-02-17T06:21:07.437",null,"C4-161194","","Rel-13","29.337","13.0.0","DiaPri","0026","1","B",null,"","","","",""]
["C4-161409","Diameter message priority over T4","Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Nokia Networks, ACS, OEC","Jean-Jacques Trottin",68942,"CR","","Agreement","","","30","7.1.20","Diameter Message Priority [DiaPri]",11942,"agreed","2016-02-17T06:22:24.080","2016-02-19T00:11:16.850","C4-161194","","Rel-13","29.337","13.0.0","DiaPri","0026","2","B","CP-160023","","","","",""]
["C4-161410","Connection Resume procedure used during restoration","Ericsson","John M Meredith",637,"CR","","","","","46","7.2.14","CIoT-CT (CT1)  [CIoT-CT]",52001,"revised","2016-02-17T06:26:36.860","2016-02-18T05:02:20.710","C4-161260","C4-161477","Rel-13","23.007","13.3.0","CIoT-CT","0336","1","B",null,"","","","",""]
["C4-161411","Diameter message priority over S7a/d, S13, S13’","Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Nokia Networks, ACS, OEC","Jean-Jacques Trottin",68942,"CR","","Agreement","","","30","7.1.20","Diameter Message Priority [DiaPri]",11951,"agreed","2016-02-17T06:33:15.813","2016-03-01T15:03:23.120","C4-161195","","Rel-13","29.272","13.4.0","DiaPri","0629","1","B","CP-160023","","","","",""]
["C4-161412","Diameter message priority over PC4a","Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Nokia Networks, ACS, OEC","Jean-Jacques Trottin",68942,"CR","","Agreement","","","30","7.1.20","Diameter Message Priority [DiaPri]",11953,"agreed","2016-02-17T06:35:28.147","2016-02-19T00:11:16.883","C4-161196","","Rel-13","29.344","13.0.0","DiaPri","0018","1","B","CP-160023","","","","",""]
["C4-161413","Diameter message priority over PC6/PC7","Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Nokia Networks, ACS, OEC","Jean-Jacques Trottin",68942,"CR","","Agreement","","","30","7.1.20","Diameter Message Priority [DiaPri]",11971,"agreed","2016-02-17T06:37:51.307","2016-02-19T00:11:16.927","C4-161197","","Rel-13","29.345","13.0.0","DiaPri","0041","1","B","CP-160023","","","","",""]
["C4-161414","Diameter message priority over T6a, T6ai, T6b, T6bi, T7","Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Nokia Networks, ACS, OEC","Jean-Jacques Trottin",68942,"pCR","","Agreement","This PCR specifies the Diameter message priority mechanism over the T6a, T6ai, T6b, T6bi, T7 interfaces","","30","7.1.20","Diameter Message Priority [DiaPri]",11991,"approved","2016-02-17T06:40:37.260","2016-02-19T00:11:16.960","C4-161199","","Rel-13","29.128","","DiaPri","","",null,"","","","","",""]
["C4-161415","Protocol change for Connection Suspend and Resume Procedure","Ericsson","John M Meredith",637,"CR","","","","","46","7.2.14","CIoT-CT (CT1)  [CIoT-CT]",51001,"agreed","2016-02-17T06:21:08.203","2016-02-19T02:20:16.297","C4-161259","","Rel-13","29.274","13.4.0","CIoT-CT","1704","1","B","CP-160033","","","","",""]
["C4-161416","Corrections to EVS AMR-WB IO mode-change-capability MIME parameter handling","Nokia Networks, Alcatel Lucent","John M Meredith",637,"CR","","Agreement","","","79","8.1.19","CT impacts of Codec for Enhanced Voices Services [EVS_codec-CT]",11881,"agreed","2016-02-17T07:15:43.887","2016-02-18T03:13:26.877","C4-161188","","Rel-12","23.334","12.9.0","EVS_codec-CT","0108","1","F","CP-160015","","","","",""]
["C4-161417","Corrections to EVS AMR-WB IO mode-change-capability MIME parameter handling","Nokia Networks","John M Meredith",637,"CR","","Agreement","","","79","8.1.19","CT impacts of Codec for Enhanced Voices Services [EVS_codec-CT]",11891,"agreed","2016-02-17T07:18:29.760","2016-02-18T03:13:26.910","C4-161189","","Rel-13","23.334","13.4.0","EVS_codec-CT","0109","1","A","CP-160015","","","","",""]
["C4-161418","Corrections to EVS AMR-WB IO mode-change-capability MIME parameter handling","Nokia Networks, Alcatel Lucent","John M Meredith",637,"CR","","Agreement","","","79","8.1.19","CT impacts of Codec for Enhanced Voices Services [EVS_codec-CT]",11981,"agreed","2016-02-17T07:20:21.720","2016-02-18T03:13:26.957","C4-161198","","Rel-12","23.333","12.7.0","EVS_codec-CT","0092","1","F","CP-160015","","","","",""]
["C4-161419","Configure Monitoring Event to Multiple Serving Nodes","ZTE","Zhijun Li",39295,"CR","","Approval","","","19","7.1.9","Monitoring Enhancements CT aspects [MONTE-CT]",11281,"revised","2016-02-17T07:21:06.303","2016-02-18T05:03:18.647","C4-161128","C4-161510","Rel-13","29.272","13.4.0","MONTE-CT","0621","1","B",null,"","","","",""]
["C4-161420","Corrections to EVS AMR-WB IO mode-change-capability MIME parameter handling","Nokia Networks, Alcatel Lucent","John M Meredith",637,"CR","","","","","79","8.1.19","CT impacts of Codec for Enhanced Voices Services [EVS_codec-CT]",12001,"agreed","2016-02-17T07:21:40.217","2016-02-18T03:13:27.003","C4-161200","","Rel-13","23.333","13.0.0","EVS_codec-CT","0093","1","A","CP-160015","","","","",""]
["C4-161421","Iq stage 3 to support SDP Capability Negotiation","Huawei","John M Meredith",637,"CR","","","","","22","7.1.12","SDP Capability Negotiation for IMS Media Plane [SDPCN_IMS]",12511,"revised","2016-02-17T07:31:36.103","2016-02-18T08:52:21.617","C4-161251","C4-161494","Rel-13","29.334","13.3.0","SDPCN_IMS","0108","1","B",null,"","","","",""]
["C4-161422","Ix stage 3 to support SDP Capability Negotiation","Huawei","John M Meredith",637,"CR","","Agreement","","","22","7.1.12","SDP Capability Negotiation for IMS Media Plane [SDPCN_IMS]",12521,"agreed","2016-02-17T07:36:04.640","2016-02-18T08:52:21.663","C4-161252","","Rel-13","29.238","13.0.0","SDPCN_IMS","0064","1","B","CP-160021","","","","",""]
["C4-161423","Count and Stop Monitoring Event Reports at SCEF","ZTE","Zhijun Li",39295,"CR","","Approval","To limit the maximum number of Monitoring event reports, the SCEF shall count the received reports and stop the Monitoring events reporting when the received reports reach the maximum number.","","19","7.1.9","Monitoring Enhancements CT aspects [MONTE-CT]",11301,"agreed","2016-02-17T07:37:10.517","2016-02-18T05:03:18.677","C4-161130","","Rel-13","29.336","13.2.0","MONTE-CT","0044","1","B","CP-160029","","","","",""]
["C4-161424","Mp stage 3 to support SDP Capability Negotiation","Huawei","John M Meredith",637,"CR","","","","","22","7.1.12","SDP Capability Negotiation for IMS Media Plane [SDPCN_IMS]",12531,"revised","2016-02-17T07:38:11.950","2016-02-18T08:52:21.707","C4-161253","C4-161495","Rel-13","29.333","13.0.0","SDPCN_IMS","0085","1","B",null,"","","","",""]
["C4-161425","New AVP assignment for MONTE","Huawei","Peter Schmitt",13753,"CR","","Decision","","","19","7.1.9","Monitoring Enhancements CT aspects [MONTE-CT]",10852,"revised","2016-02-17T07:41:29.697","2016-03-01T15:03:23.137","C4-161286","C4-161509","Rel-13","29.230","13.3.0","MONTE-CT","0505","2","B",null,"","","","",""]
["C4-161426","Mn stage 3 to support SDP Capability Negotiation","Huawei","John M Meredith",637,"CR","","","","","22","7.1.12","SDP Capability Negotiation for IMS Media Plane [SDPCN_IMS]",12541,"agreed","2016-02-17T07:44:19.483","2016-02-18T08:52:21.757","C4-161254","C4-161427","Rel-13","29.332","13.0.0","SDPCN_IMS","0199","1","B","CP-160021","","","","",""]
["C4-161427","Mn stage 3 to support SDP Capability Negotiation","Huawei","John M Meredith",637,"CR","","","Mn stage 3 to support SDP Capability Negotiation","","22","7.1.12","SDP Capability Negotiation for IMS Media Plane [SDPCN_IMS]",12542,"withdrawn","2016-02-17T07:44:29.843",null,"C4-161426","","Rel-13","29.332","13.0.0","SDPCN_IMS","0199","2","B",null,"","","","",""]
["C4-161428","Change of type of Monitoring-Duration AVP to represent an absolute time","Ericsson","Jesus De Gregorio",40423,"CR","","","Change the definition and AVP type of Monitoring-Duration AVP, from Unsigned32 to Time data type.","","19","7.1.9","Monitoring Enhancements CT aspects [MONTE-CT]",11401,"agreed","2016-02-17T07:45:39.263","2016-03-01T15:03:23.137","C4-161140","","Rel-13","29.336","13.2.0","MONTE-CT","0045","1","F","CP-160029","","","","",""]
["C4-161429","Mc stage 3 to support SDP Capability Negotiation","Huawei","John M Meredith",637,"CR","","Agreement","","","22","7.1.12","SDP Capability Negotiation for IMS Media Plane [SDPCN_IMS]",12551,"agreed","2016-02-17T07:45:47.747","2016-02-18T08:52:21.803","C4-161255","","Rel-13","29.232","13.0.0","SDPCN_IMS","0660","1","B","CP-160021","","","","",""]
["C4-161430","Definition of Monitoring-Type and clarifications on UE in MME and SGSN for MONTE","Huawei","Peter Schmitt",13753,"CR","","Decision","","","19","7.1.9","Monitoring Enhancements CT aspects [MONTE-CT]",12891,"revised","2016-02-17T08:22:02.797","2016-02-18T05:03:18.507","C4-161289","C4-161497","Rel-13","29.336","13.2.0","MONTE-CT","0048","1","B",null,"","","","",""]
["C4-161431","Subsciption for allowed services","Huawei","Peter Schmitt",13753,"CR","","Decision","","","19","7.1.9","Monitoring Enhancements CT aspects [MONTE-CT]",12941,"revised","2016-02-17T08:37:27.370","2016-02-18T05:03:18.553","C4-161294","C4-161501","Rel-13","23.008","13.3.0","MONTE-CT","0489","1","B",null,"","","","",""]
["C4-161432","No Delete Session Request for non-existing PDN connection","Nokia Networks, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell","John M Meredith",637,"CR","","Agreement","","","46","7.2.14","CIoT-CT (CT1)  [CIoT-CT]",53001,"agreed","2016-02-17T09:04:27.793","2016-02-18T06:17:42.047","C4-161213","","Rel-13","29.274","13.4.0","CIoT-CT","1699","1","B","CP-160033","","","","",""]
["C4-161433","Data model for new Application FEs’ data clarification","Ericsson","Maria-Cruz Bartolome",44824,"CR","","","","","43","7.2.11","Mission Critical Push To Talk over LTE protocol aspects (CT1) [MCPTT-CT]",12401,"revised","2016-02-17T09:06:55.417",null,"C4-161240","C4-161457","Rel-13","23.335","13.0.0","MCPTT-CT","0015","1","B",null,"","","","",""]
["C4-161434","No Create Session Request for Attach without PDN connection","Nokia Networks, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell","John M Meredith",637,"CR","","Agreement","","","46","7.2.14","CIoT-CT (CT1)  [CIoT-CT]",54001,"agreed","2016-02-17T09:07:44.383","2016-02-18T05:25:46.353","C4-161214","","Rel-13","29.274","13.4.0","CIoT-CT","1700","1","B","CP-160033","","","","",""]
["C4-161435","No Paging and Serving Information in a DDN for a non-IP PDN connections","Huawei","John M Meredith",637,"CR","","Agreement","","","46","7.2.14","CIoT-CT (CT1)  [CIoT-CT]",55001,"revised","2016-02-17T09:14:47.517","2016-02-18T05:52:14.870","C4-161215","C4-161478","Rel-13","29.274","13.4.0","CIoT-CT","1701","1","B",null,"","","","",""]
["C4-161436","Behaviours upon receipt of unknown NIDD","Huawei","John M Meredith",637,"CR","","Agreement","","","46","7.2.14","CIoT-CT (CT1)  [CIoT-CT]",56001,"revised","2016-02-17T09:42:13.040","2016-02-18T06:17:42.107","C4-161216","C4-161533","Rel-13","23.007","13.3.0","CIoT-CT","0334","1","B",null,"","","","",""]
["C4-161437","Enhance restoration procedure to be compatible with PDN connection to the SCEF","Huawei","John M Meredith",637,"CR","","Agreement","","","46","7.2.14","CIoT-CT (CT1)  [CIoT-CT]",58001,"revised","2016-02-17T10:09:16.773","2016-02-18T06:17:42.140","C4-161218","C4-161438","Rel-13","23.007","13.3.0","CIoT-CT","0335","1","B",null,"","","","",""]
["C4-161438","Enhance restoration procedure to be compatible with PDN connection to the SCEF","Huawei","John M Meredith",637,"CR","","Agreement","","","46","7.2.14","CIoT-CT (CT1)  [CIoT-CT]",58002,"revised","2016-02-17T10:09:26.380","2016-02-18T23:37:47.793","C4-161437","C4-161481","Rel-13","23.007","13.3.0","CIoT-CT","0335","2","B",null,"","","","",""]
["C4-161439","new Diameter application for MCPTT-2 and CSC-13 reference points","ORANGE, HPE, Motorola","Lionel Morand",25150,"pCR","","Approval","Make a reference to the TS 24.384 that defines the content of the MCPTT use profile document.","","43","7.2.11","Mission Critical Push To Talk over LTE protocol aspects (CT1) [MCPTT-CT]",12706,"revised","2016-02-17T11:05:08.237","2016-02-18T07:38:58.170","C4-161298","C4-161515","Rel-13","","","MCPTT-CT","","",null,"","","","","",""]
["C4-161440","AVP Codes for 29.12","Nokia Networks, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell","Ulrich Wiehe",6963,"CR","","Agreement","","","101","8.3.7","Diameter 29.230 CRs [TEI12]",12706,"agreed","2016-02-17T23:12:45.240","2016-02-18T23:37:47.823","C4-161245","","Rel-12","29.230","12.11.0","TEI12","0516","1","F","CP-160017","","","","",""]
["C4-161441","AVP codes for 32.299","Nokia Networks, Alcatel-Lucent, MCC, Alcatel-Lucent Shanghai Bell","Ulrich Wiehe",6963,"CR","","Agreement","","","49","7.3.2","Diameter 29.230 CRs [TEI13]",11772,"agreed","2016-02-17T23:28:19.533","2016-02-18T23:37:47.870","C4-161277","","Rel-13","29.230","13.3.0","TEI13","0514","2","F","CP-160041","","","","",""]
["C4-161442","AVP code range reservation for 32.299","Nokia Networks, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell","Ulrich Wiehe",6963,"CR","","Agreement","To allocate a range of AVP codes for TS 32.299.\n\nAllocate the range of 4400 – 4499 for TS 32.299 as requested by SA5.","","101","8.3.7","Diameter 29.230 CRs [TEI12]",11781,"agreed","2016-02-17T23:38:30.143","2016-02-18T23:37:47.917","C4-161178","","Rel-14","29.230","13.3.0","TEI14","0515","1","F","CP-160018","","","","",""]
["C4-161443","Addition of AVP code definitions","CT4","Ulrich Wiehe",6963,"LS out","","Information","CT4 thanks SA5 for their LS on Addition of AVP code definitions.\nAs requested by SA5, CT4 have allocated a new range of AVP codes to TS 32.299 for Rel-14. \nThe new range is from 1400 to 1499. See also the agreed Rel-14 CR to 29.230 in C4-161442.","","49","7.3.2","Diameter 29.230 CRs [TEI13]",14430,"approved","2016-02-17T23:46:33.867","2016-02-18T23:37:47.950","","","Rel-14","","","","","","","","C4-161222","SA5"]
["C4-161444","Corrections on TS numbers","Huawei","Peter Schmitt",13753,"CR","","Decision","","","49","7.3.2","Diameter 29.230 CRs [TEI13]",10871,"agreed","2016-02-17T23:51:02.467","2016-02-18T05:03:18.583","C4-161087","","Rel-13","29.230","13.3.0","TEI13","0506","1","F","CP-160041","","","","",""]
["C4-161445","Codes for 29.212","Nokia Networks, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell","Ulrich Wiehe",6963,"CR","","Agreement","","","49","7.3.2","Diameter 29.230 CRs [TEI13]",12471,"agreed","2016-02-18T00:03:00.670","2016-02-18T23:37:48.010","C4-161247","","Rel-13","29.230","13.3.0","TEI13","0518","1","F","CP-160041","","","","",""]
["C4-161446","Update Conclusion on Changes and Clarifications of the rules for Diameter Extensibility","Alcatel-Lucent, Alcatel-Lucent Shanghai Bell","Jean-Jacques Trottin",68942,"pCR","","Agreement","The IETF RFC 6733 [3] statement on rules for extension of Diameter commands, has  impacts on 3GPP Diameter offline Charging Application Rf design, regarding the ACR/ACA extended with 3GPP specific AVPs..","","29","7.1.19","Feasibility Study on the Diameter Base Protocol Update [FS_DBPU]",14460,"revised","2016-02-18T00:07:08.927","2016-02-18T03:13:27.050","","C4-161453","Rel-13","29.819","1.0.0","FS_DBPU","","",null,"","","","","",""]
["C4-161447","Invocation of Alert procedure by HSS after ULR","Ericsson","Jesus De Gregorio",40423,"CR","","","","","53","7.3.6","Diameter based Interfaces [TEI13]",11371,"agreed","2016-02-18T00:21:57.853","2016-02-19T00:11:17.007","C4-161137","","Rel-13","29.272","13.4.0","TEI13","0626","1","F","CP-160045","","","","",""]
["C4-161448","Proposed text for the introduction of clause 5","ORANGE","Lionel Morand",25150,"pCR","","Approval","The paper proposes a text for the missing introduction in clause 5 to complete the TR 29.819.","","29","7.1.19","Feasibility Study on the Diameter Base Protocol Update [FS_DBPU]",12821,"approved","2016-02-18T01:32:23.320","2016-03-01T15:03:23.137","C4-161282","","Rel-13","29.819","1.0.0","FS_DBPU","","",null,"","","","","",""]
["C4-161449","Complete the EXTERNAL_SOURCE_IP4_NAT_INFO attribute information according to IANA registration","ZTE","Xiaoyun Zhou",38525,"CR","","Agreement","","","112","9.8","BBF Interworking Building Block I [BBAI_BBI-CT]",10651,"agreed","2016-02-18T02:25:41.300","2016-02-18T05:02:20.740","C4-161065","","Rel-11","29.139","11.1.0","BBAI_BBI-CT","0002","1","F","CP-160019","","","","",""]
["C4-161450","Complete the EXTERNAL_SOURCE_IP4_NAT_INFO attribute information according to IANA registration","ZTE","Xiaoyun Zhou",38525,"CR","","Agreement","","","112","9.8","BBF Interworking Building Block I [BBAI_BBI-CT]",10661,"agreed","2016-02-18T02:29:31.277","2016-02-18T05:02:20.770","C4-161066","","Rel-12","29.139","12.0.0","BBAI_BBI-CT","0003","1","A","CP-160019","","","","",""]
["C4-161451","Complete the EXTERNAL_SOURCE_IP4_NAT_INFO attribute information according to IANA registration","ZTE","Xiaoyun Zhou",38525,"CR","","Agreement","","","112","9.8","BBF Interworking Building Block I [BBAI_BBI-CT]",10672,"agreed","2016-02-18T02:30:49.850","2016-02-18T05:02:20.803","C4-161067","","Rel-13","29.139","13.0.0","BBAI_BBI-CT","0004","1","A","CP-160019","","","","",""]
["C4-161452","Changes in the Command's CCF specifications","ORANGE","Lionel Morand",25150,"pCR","","Approval","","","29","7.1.19","Feasibility Study on the Diameter Base Protocol Update [FS_DBPU]",12791,"approved","2016-02-18T03:11:48.257","2016-02-19T02:57:07.100","C4-161279","","Rel-13","29.819","1.0.0","FS_DBPU","","",null,"","","","","",""]
["C4-161453","Update Conclusion on Changes and Clarifications of the rules for Diameter Extensibility","Alcatel-Lucent, Alcatel-Lucent Shanghai Bell","Jean-Jacques Trottin",68942,"pCR","","Agreement","","","29","7.1.19","Feasibility Study on the Diameter Base Protocol Update [FS_DBPU]",14461,"approved","2016-02-18T03:51:25.650","2016-03-01T15:03:23.153","C4-161446","","Rel-13","29.819","1.0.0","FS_DBPU","","",null,"","","","","",""]
["C4-161454","SCEF  Restart","Huawei","Peter Schmitt",13753,"CR","","Decision","","","19","7.1.9","Monitoring Enhancements CT aspects [MONTE-CT]",10831,"revised","2016-02-18T03:52:28.890","2016-02-18T05:03:18.617","C4-161083","C4-161474","Rel-13","29.336","13.2.0","MONTE-CT","0039","1","B",null,"","","","",""]
["C4-161455","Pseudo-CR on SCEF restart","Huawei","Peter Schmitt",13753,"pCR","","Decision","","","19","7.1.9","Monitoring Enhancements CT aspects [MONTE-CT]",12403,"revised","2016-02-18T03:56:30.017","2016-02-18T05:02:21.193","","C4-161475","","29.128","","MONTE-CT","","",null,"","","","","",""]
["C4-161456","Reply LS to CT4 LS on progress of the work on Diameter Base Protocol Update","ORANGE","Lionel Morand",25150,"LS out","","Decision","CT4 thanks SA5 for the reply LS (S5-161308) on progress of the work on Diameter Base Protocol Update and the attached contributions that have been used as basis for company contributions agreed to be incorporated in the Technical Report.\n\nOne of these c","","29","7.1.19","Feasibility Study on the Diameter Base Protocol Update [FS_DBPU]",14560,"revised","2016-02-18T04:00:18.400","2016-03-01T15:03:23.153","","C4-161541","Rel-13","29.819","1.0.0","FS_DBPU","","","","","C4-161220","SA5"]
["C4-161457","MCPTT Application FEs","Ericsson, Nokia Networks, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell","Maria-Cruz Bartolome",44824,"CR","","","","","43","7.2.11","Mission Critical Push To Talk over LTE protocol aspects (CT1) [MCPTT-CT]",12402,"revised","2016-02-18T04:45:34.267","2016-02-18T05:52:14.917","C4-161433","C4-161489","Rel-13","23.335","13.0.0","MCPTT-CT","0015","2","B",null,"","","","",""]
["C4-161458","CT aspects for Non-IP for Cellular Internet of Things for 2G/3G-GPRS","Orange, Ericsson","John M Meredith",637,"other","","Endorsement","","","7","5","Work item management",145200,"revised","2016-02-18T04:49:19.810","2016-02-18T10:32:44.567","","C4-161503","Rel-13","","","","","","","","","","","",""]
["C4-161459","Transferring AAA identifier to the PGW","Ericsson, Orange, Telia Sonera","John M Meredith",637,"CR","","","","","48","7.3.1","GTP and PMIP [TEI13]",11683,"agreed","2016-02-18T05:15:26.960","2016-02-19T02:20:16.360","C4-161353","","Rel-13","29.274","13.4.0","TEI13","1693","3","F","CP-160038","","","","",""]
["C4-161460","Reply LS on clarification on requirements for MONTE","Huawei","Peter Schmitt",13753,"LS out","","","CT4 thanks SA2 for their LS on clarification on requirements for MONTE in S2-154383\n\nCT4 has continued the work onMONTE and reached the following conclusions on the remaining open issues:\nA) On how to keep the HSS up to date on remaining number of Repo","","19","7.1.9","Monitoring Enhancements CT aspects [MONTE-CT]",14600,"revised","2016-02-18T05:17:33.663","2016-02-19T02:20:16.437","","C4-161537","Rel-13","","","MONTE-CT","","","","","C4-161035","SA2"]
["C4-161461","Comprehension requirement for PDCP PDU Number","Ericsson","John M Meredith",637,"CR","","","","","48","7.3.1","GTP and PMIP [TEI13]",11712,"agreed","2016-02-18T05:19:58.303","2016-02-19T02:20:16.487","C4-161355","","Rel-13","29.281","13.0.0","TEI13","0076","2","F","CP-160038","","","","",""]
["C4-161462","Pseudo-CR on Removing Editor's Note on IWK-SCEF Authorization and Configuration Failure at IWK-SCEF","Cisco Systems Inc","Sridhar Bhaskaran",58580,"pCR","","Approval","","","19","7.1.9","Monitoring Enhancements CT aspects [MONTE-CT]",10002,"approved","2016-02-18T05:26:07.087","2016-03-01T15:03:23.153","C4-161345","","Rel-13","","1.0.0","","","",null,"","","","","",""]
["C4-161463","Reply to: LS on extension to field length of PDCP Sequence Number","current meeting","John M Meredith",637,"LS out","","Approval","","","58","7.3.11","18 bits PDCP PDU Number",10302,"revised","2016-02-18T05:27:47.113","2016-02-18T08:52:21.897","C4-161337","C4-161500","Rel-13","","","LTE_CA_enh_b5C-Core","","","","","C4-161030","3GPP TSG RAN WG2",null,"R2-156977"]
["C4-161464","Add cause values to TWAN mapping table","Huawei","John M Meredith",637,"CR","","","","","95","8.3.1","GTP and PMIP [TEI12]",10962,"agreed","2016-02-18T05:32:40.077","2016-02-18T05:52:14.840","C4-161356","","Rel-12","29.274","12.11.0","TEI12","1683","2","F","CP-160016","","","","",""]
["C4-161465","Notifying the status of MONTE event configuration at the IWK-SCEF to the HSS","Cisco Systems Inc","Sridhar Bhaskaran",58580,"CR","","Approval","","","19","7.1.9","Monitoring Enhancements CT aspects [MONTE-CT]",10612,"agreed","2016-02-18T05:37:10.237","2016-03-01T15:03:23.153","C4-161346","","Rel-13","29.272","13.4.0","MONTE-CT","0618","2","B","CP-160029","","","","",""]
["C4-161466","PDN Connection Charging ID for NBIFOM","CT4","John M Meredith",637,"LS out","","Decision","CT4 would like to thank SA5 for their LS (S5-161252) on the Charging Id assignment for NBIFOM. Based on the agreed SA2 TS 23.161 CR 0012, CT4 has also agreed to introduce PDN Connection Charging ID in the GTPv2 protocol as attached.\nCT4 kindly request SA","","38","7.2.6","IP Flow Mobility support for S2a and S2b Interfaces on stage 3 (CT1) [NBIFOM]",136601,"approved","2016-02-18T05:38:37.753","2016-02-19T02:20:16.517","C4-161367","","Rel-13","","","","","","","","C4-161221","SA5"]
["C4-161467","Pseudo-CR on cleanup of 29.128","Huawei","Peter Schmitt",13753,"pCR","","Decision","","","19","7.1.9","Monitoring Enhancements CT aspects [MONTE-CT]",10768,"approved","2016-02-18T05:40:59.040","2016-02-19T00:11:15.697","C4-161347","","Rel-13","29.128","1.0.0","MONTE-CT","","",null,"","","","","",""]
["C4-161468","AVAILABILITY_AFTER_DDN_FAILURE reporting","Huawei","Peter Schmitt",13753,"CR","","Decision","","","19","7.1.9","Monitoring Enhancements CT aspects [MONTE-CT]",10772,"agreed","2016-02-18T05:43:13.417","2016-02-19T00:11:15.743","C4-161348","","Rel-13","29.336","13.2.0","MONTE-CT","0037","2","B","CP-160029","","","","",""]
["C4-161469","S11-U tunneling for MO/MT data transport in control plane (SGi based) - with new S11-U F-TEIDs","Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Nokia Networks, Verizon, AT&T, Orange, China Mobile","John M Meredith",637,"CR","","Approval","","","46","7.2.14","CIoT-CT (CT1)  [CIoT-CT]",38002,"revised","2016-02-18T05:47:03.283","2016-02-18T23:34:00.237","C4-161378","C4-161531","Rel-13","29.274","13.4.0","CIoT-CT","1689","2","B",null,"","","","",""]
["C4-161470","HSS restart MONTE impacts","Huawei","Peter Schmitt",13753,"CR","","Decision","","","19","7.1.9","Monitoring Enhancements CT aspects [MONTE-CT]",10811,"agreed","2016-02-18T05:56:35.990","2016-02-19T02:20:16.547","C4-161354","","Rel-13","23.007","13.3.0","MONTE-CT","0329","2","B","CP-160029","","","","",""]
["C4-161471","Impacts on the DNS procedures for CIoT with introduction of NB-IoT and Non-IP","Ericsson LM","John M Meredith",637,"LS out","","Decision","","","46","7.2.14","CIoT-CT (CT1)  [CIoT-CT]",45006,"revised","2016-02-18T06:00:52.263","2016-02-19T00:11:15.837","C4-161393","C4-161519","Rel-13","","","NB_IOT, CIoT-CT","","","","",null,"SA2"]
["C4-161472","Restart of SCEF","Huawei","Peter Schmitt",13753,"CR","","Decision","","","19","7.1.9","Monitoring Enhancements CT aspects [MONTE-CT]",10822,"agreed","2016-02-18T06:03:51.990","2016-02-19T00:11:15.900","C4-161358","","Rel-13","23.007","13.3.0","MONTE-CT","0330","2","B","CP-160029","","","","",""]
["C4-161473","Impacts on the DNS procedures for CIoT","Ericsson","John M Meredith",637,"CR","","","","","46","7.2.14","CIoT-CT (CT1)  [CIoT-CT]",47002,"agreed","2016-02-18T06:08:14.600","2016-02-19T02:20:16.627","C4-161395","","Rel-13","29.303","13.2.0","CIoT-CT","0087","3","B","CP-160033","","","","",""]
["C4-161474","SCEF  Restart","Huawei","Peter Schmitt",13753,"CR","","Decision","","","19","7.1.9","Monitoring Enhancements CT aspects [MONTE-CT]",10832,"agreed","2016-02-18T06:09:51.087","2016-02-19T00:11:15.947","C4-161454","","Rel-13","29.336","13.2.0","MONTE-CT","0039","2","B","CP-160029","","","","",""]
["C4-161475","Pseudo-CR on SCEF restart","Huawei","Peter Schmitt",13753,"pCR","","Decision","","","19","7.1.9","Monitoring Enhancements CT aspects [MONTE-CT]",12404,"agreed","2016-02-18T06:24:52.587","2016-02-19T00:11:16.007","C4-161455","","Rel-13","29.128","13.2.0","MONTE-CT","","",null,"","","","","",""]
["C4-161476","Protocol change for introducing new non-IP PDN type","Ericsson","John M Meredith",637,"CR","","","","","46","7.2.14","CIoT-CT (CT1)  [CIoT-CT]",49002,"agreed","2016-02-18T06:24:55.800","2016-02-19T02:20:16.687","C4-161404","","Rel-13","29.274","13.4.0","CIoT-CT","1705","2","B","CP-160033","","","","",""]
["C4-161477","Connection Resume procedure used during restoration","Ericsson","John M Meredith",637,"CR","","","","","46","7.2.14","CIoT-CT (CT1)  [CIoT-CT]",52002,"agreed","2016-02-18T06:28:43.513","2016-02-18T08:54:50.937","C4-161410","","Rel-13","23.007","13.3.0","CIoT-CT","0336","2","B","CP-160033","","","","",""]
["C4-161478","No Paging and Serving Information in a DDN for a non-IP PDN connections","Huawei","John M Meredith",637,"CR","","Agreement","","","46","7.2.14","CIoT-CT (CT1)  [CIoT-CT]",55002,"agreed","2016-02-18T06:34:01.360","2016-02-18T07:38:58.137","C4-161435","","Rel-13","29.274","13.4.0","CIoT-CT","1701","2","B","CP-160033","","","","",""]
["C4-161479","Skeleton for Sh* application for MCPTT-2 and CSC-13 interfaces","Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Nokia Networks, Orange, Motorola","Jean-Jacques Trottin",68942,"discussion","","Decision","","","43","7.2.11","Mission Critical Push To Talk over LTE protocol aspects (CT1) [MCPTT-CT]",12381,"noted","2016-02-18T07:18:03.500","2016-02-19T00:11:16.040","C4-161238","C4-161514","Rel-13","","","MCPTT-CT","","","","","","","","",""]
["C4-161480","Transfer of non IP PDN to peer MME during mobility","Cisco Systems Inc","John M Meredith",637,"CR","","Approval","","","46","7.2.14","CIoT-CT (CT1)  [CIoT-CT]",50002,"revised","2016-02-18T07:35:43.623","2016-03-01T15:03:23.167","C4-161401","C4-161525","Rel-13","29.274","13.4.0","CIoT-CT","1697","2","B",null,"","","","",""]
["C4-161481","Enhance restoration procedure to be compatible with PDN connection to the SCEF","Huawei","John M Meredith",637,"CR","","Agreement","","","46","7.2.14","CIoT-CT (CT1)  [CIoT-CT]",58003,"agreed","2016-02-18T07:46:35.403","2016-03-01T15:03:23.167","C4-161438","","Rel-13","23.007","13.3.0","CIoT-CT","0335","3","B","CP-160033","","","","",""]
["C4-161482","DNS procedures for Decor","NTT DOCOMO","John M Meredith",637,"CR","","Agreement","","","28","7.1.18","Dedicated Core Networks [DECOR-CT]",11763,"revised","2016-02-18T08:07:58.963","2016-02-18T10:32:44.533","C4-161365","C4-161513","Rel-13","29.303","13.2.0","DECOR-CT","0086","3","B",null,"","","","",""]
["C4-161483","MO Non-IP Data procedures over T6a","Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Nokia Networks, Cisco Systems Inc","John M Meredith",637,"pCR","","Agreement","Adds new supporting company.","","46","7.2.14","CIoT-CT (CT1)  [CIoT-CT]",20002,"agreed","2016-02-18T08:17:26.783","2016-02-18T23:37:48.057","C4-161303","","Rel-13","29.128","1.0.0","CIoT-CT","","",null,"","","","","",""]
["C4-161484","MT Non-IP Data procedures over T6a","Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Nokia Networks, Cisco Systems Inc","John M Meredith",637,"pCR","","Agreement","Adds new supporting company.","","46","7.2.14","CIoT-CT (CT1)  [CIoT-CT]",21002,"agreed","2016-02-18T08:22:07.783","2016-02-18T23:37:48.090","C4-161304","","Rel-13","29.128","1.0.0","CIoT-CT","","",null,"","","","","",""]
["C4-161485","Questions on non-IP data delivery procedures","CT4","John M Meredith",637,"LS out","","Discussion","","","46","7.2.14","CIoT-CT (CT1)  [CIoT-CT]",21004,"revised","2016-02-18T08:24:04.173","2016-02-18T23:34:00.283","C4-161305","C4-161535","","","","","","","","",null,"SA2","SA3"]
["C4-161486","Iq stage 2 for SDP Media Capabilities Negotiation","Huawei","Weiwei(Tommy) YANG",55591,"CR","","Agreement","To update the support for SDP media capabilities negotiation in stage 2 procedures.","","22","7.1.12","SDP Capability Negotiation for IMS Media Plane [SDPCN_IMS]",14860,"withdrawn","2016-02-18T08:35:21.787","2016-02-18T08:52:21.833","","","Rel-13","23.334","13.4.0","SDPCN_IMS","0110","","F",null,"","","","",""]
["C4-161487","Connection management  procedures over T6a","Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Nokia Networks, Cisco Systems Inc","John M Meredith",637,"pCR","","Agreement","","","46","7.2.14","CIoT-CT (CT1)  [CIoT-CT]",22002,"revised","2016-02-18T08:36:53.453","2016-03-01T15:03:23.167","C4-161306","C4-161518","Rel-13","29.128","1.0.0","CIoT-CT","","",null,"","","","","",""]
["C4-161488","Protocol for Non IP-Data over T6a","Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Nokia Networks, Cisco Systems Inc","John M Meredith",637,"pCR","","Agreement","","","46","7.2.14","CIoT-CT (CT1)  [CIoT-CT]",23002,"revised","2016-02-18T08:46:38.557","2016-02-18T23:37:48.137","C4-161307","C4-161534","Rel-13","29.128","1.0.0","CIoT-CT","","",null,"","","","","",""]
["C4-161489","MCPTT Application FEs","Ericsson, Nokia Networks, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell","Maria-Cruz Bartolome",44824,"CR","","","","","43","7.2.11","Mission Critical Push To Talk over LTE protocol aspects (CT1) [MCPTT-CT]",12403,"agreed","2016-02-18T09:03:19.777","2016-02-18T09:29:32.137","C4-161457","","Rel-13","23.335","13.0.0","MCPTT-CT","0015","3","B","CP-160031","","","","",""]
["C4-161490","New PDN-Type for Cellular IoT","Ericsson","John M Meredith",637,"CR","","","","","46","7.2.14","CIoT-CT (CT1)  [CIoT-CT]",24002,"revised","2016-02-18T09:10:19.163","2016-02-19T00:11:16.087","C4-161308","C4-161526","Rel-13","29.272","13.4.0","CIoT-CT","0631","2","B",null,"","","","",""]
["C4-161491","Addition of NB-IoT radio access type to the Access-Restriction-Data feature","Vodafone GmbH, Deutsche Telekom, Huawei","John M Meredith",637,"CR","","Approval","","","46","7.2.14","CIoT-CT (CT1)  [CIoT-CT]",28002,"agreed","2016-02-18T09:17:33.933","2016-02-19T02:57:07.193","C4-161319","","Rel-13","29.272","13.4.0","CIoT-CT","0630","2","B","CP-160033","","","","",""]
["C4-161492","Addition of NB-IoT radio access type to the Access-Restriction-Data feature","Vodafone GmbH, Deutsche Telekom, Huawei","John M Meredith",637,"CR","","Approval","","","46","7.2.14","CIoT-CT (CT1)  [CIoT-CT]",29002,"agreed","2016-02-18T09:20:46.467","2016-02-19T02:57:07.273","C4-161320","","Rel-13","29.002","13.2.0","CIoT-CT","1204","2","B","CP-160033","","","","",""]
["C4-161493","Subscription data for combined MME/SGSN","Nokia Networks, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell","Ulrich Wiehe",6963,"CR","","Agreement","","","53","7.3.6","Diameter based Interfaces [TEI13]",11751,"postponed","2016-02-18T09:39:59.923","2016-02-18T23:37:48.167","C4-161175","C4-162059","Rel-13","29.272","13.4.0","TEI13","0628","1","F",null,"","","","",""]
["C4-161494","Iq stage 3 to support SDP Capability Negotiation","Huawei","John M Meredith",637,"CR","","","","","22","7.1.12","SDP Capability Negotiation for IMS Media Plane [SDPCN_IMS]",12512,"agreed","2016-02-18T09:41:11.790","2016-02-18T09:51:30.217","C4-161421","","Rel-13","29.334","13.3.0","SDPCN_IMS","0108","2","B","CP-160021","","","","",""]
["C4-161495","Mp stage 3 to support SDP Capability Negotiation","Huawei","John M Meredith",637,"CR","","","","","22","7.1.12","SDP Capability Negotiation for IMS Media Plane [SDPCN_IMS]",12532,"agreed","2016-02-18T09:46:46.330","2016-02-18T10:33:41.443","C4-161424","","Rel-13","29.333","13.0.0","SDPCN_IMS","0085","2","B","CP-160021","","","","",""]
["C4-161496","Support of enhanced bandwidth negotiation mechanism for MTSI sessions","Ericsson","John M Meredith",637,"CR","","","","","35","7.2.3","CT aspects of QoS End to End MTSI extensions (CT3) [QOSE2EMTSI-CT]",10492,"agreed","2016-02-18T09:59:20.960","2016-03-01T15:03:23.167","C4-161330","","Rel-13","23.334","13.4.0","QOSE2EMTSI-CT","0106","2","B","CP-160034","","","","",""]
["C4-161497","Definition of Monitoring-Type and clarifications on UE in MME and SGSN for MONTE","Huawei","Peter Schmitt",13753,"CR","","Decision","","","19","7.1.9","Monitoring Enhancements CT aspects [MONTE-CT]",12892,"revised","2016-02-18T10:10:28.417","2016-02-19T00:11:16.133","C4-161430","C4-161511","Rel-13","29.336","13.2.0","MONTE-CT","0048","2","B",null,"","","","",""]
["C4-161498","18 bits PDCP PDU Number","Nokia Networks, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell","John M Meredith",637,"CR","","","","","58","7.3.11","18 bits PDCP PDU Number",11822,"agreed","2016-02-18T10:14:09.327","2016-03-01T15:03:23.167","C4-161336","C4-161499","Rel-13","29.281","13.0.0","TEI13, LTE_CA_enh_b5C-Core","0077","2","F","CP-160040","","","","",""]
["C4-161499","18 bits PDCP PDU Number","Nokia Networks, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell","John M Meredith",637,"CR","","","","","58","7.3.11","18 bits PDCP PDU Number",14990,"withdrawn","2016-02-18T10:14:19.843",null,"C4-161498","","Rel-13","29.281","13.0.0","TEI13, LTE_CA_enh_b5C-Core","0077","3","F",null,"","","","",""]
["C4-161500","Reply to: LS on extension to field length of PDCP Sequence Number","CT4","John M Meredith",637,"LS out","","Approval","Change of attachment tdoc number.","","58","7.3.11","18 bits PDCP PDU Number",10303,"approved","2016-02-18T10:15:15.533","2016-03-01T15:03:23.183","C4-161463","","Rel-13","","","LTE_CA_enh_b5C-Core","","","","","C4-161030","RAN2, RAN3",null,"R2-156977"]
["C4-161501","Subsciption for allowed services","Huawei","Peter Schmitt",13753,"CR","","Decision","","","19","7.1.9","Monitoring Enhancements CT aspects [MONTE-CT]",12942,"agreed","2016-02-18T10:15:59.213","2016-02-19T00:11:16.243","C4-161431","","Rel-13","23.008","13.3.0","MONTE-CT","0489","2","B","CP-160029","","","","",""]
["C4-161502","Introduction of AAA-1 interface","Huawei","Peter Schmitt",13753,"CR","","Decision","","","43","7.2.11","Mission Critical Push To Talk over LTE protocol aspects (CT1) [MCPTT-CT]",10883,"revised","2016-02-18T10:19:16.053","2016-02-19T00:11:16.303","C4-161362","C4-161517","Rel-13","29.228","13.0.0","MCPTT-CT","0661","5","B",null,"","","","",""]
["C4-161503","CT aspects for Non-IP for Cellular Internet of Things for 2G/3G-GPRS","Orange, Ericsson","John M Meredith",637,"other","","Endorsement","","","7","5","Work item management",145201,"endorsed","2016-02-18T23:44:25.170","2016-02-19T02:20:15.613","C4-161458","C4-163132","Rel-13","","","","","","","","","","","",""]
["C4-161504","LS on New subdomain name for ePDG selection with DNS-based discovery of regulatory requirements","CT4","John M Meredith",637,"LS out","","Approval","","","52","7.3.5","Addressing and Subscriber Data Handling [TEI13]",131101,"approved","2016-02-18T23:52:50.777","2016-03-01T15:03:23.577","C4-161311","","","","","","","","","",null,"GSMA IREG","CT, CT1"]
["C4-161505","Clarification of TAC allocation","Vodafone","John M Meredith",637,"CR","","Agreement","","","6","4","Input liaison statements: allocation to agenda items as appropriate",130001,"agreed","2016-02-18T23:57:48.347","2016-03-01T15:03:23.577","C4-161300","","Rel-13","23.003","13.4.0","TEI13","0438","1","B","CP-160020","","","","",""]
["C4-161506","Reply to: TAC Allocation as detailed in 3GPP TS 23.003","current meeting","John M Meredith",637,"LS out","","Approval","Adds the attachment.","","6","4","Input liaison statements: allocation to agenda items as appropriate",12192,"approved","2016-02-19T00:01:40.623","2016-02-19T02:57:06.990","C4-161299","","","","","","","","","","C4-161219","GSMA TSG"]
["C4-161507","Cleanup of the editor's notes for reporting remote UE","Ericsson","John M Meredith",637,"CR","","","","","39","7.2.7","CT aspects of enhancements to Proximity-based Services extensions (CT1) [eProSe-Ext-CT]",11702,"agreed","2016-02-19T00:04:14.343","2016-03-01T15:03:23.590","C4-161385","","Rel-13","29.274","13.4.0","eProSe-Ext-CT","1694","2","B","CP-160036","","","","",""]
["C4-161508","Reporting of the start and stop of the reporting of monitoring events","Huawei Tech.(UK) Co., Ltd","John M Meredith",637,"CR","","Decision","","","19","7.1.9","Monitoring Enhancements CT aspects [MONTE-CT]",10842,"agreed","2016-02-19T00:11:25.727","2016-03-01T15:03:23.590","C4-161359","","Rel-13","29.336","13.2.0","MONTE-CT","0040","2","B","CP-160029","","","","",""]
["C4-161509","New AVP assignment for MONTE","Huawei","John M Meredith",637,"CR","","Decision","","","19","7.1.9","Monitoring Enhancements CT aspects [MONTE-CT]",10853,"agreed","2016-02-19T00:15:27.337","2016-03-01T15:03:23.590","C4-161425","","Rel-13","29.230","13.3.0","MONTE-CT","0505","3","B","CP-160029","","","","",""]
["C4-161510","Configure Monitoring Event to Multiple Serving Nodes","ZTE","John M Meredith",637,"CR","","Approval","","","19","7.1.9","Monitoring Enhancements CT aspects [MONTE-CT]",11282,"revised","2016-02-19T00:28:28.763","2016-02-19T03:13:17.727","C4-161419","C4-161540","Rel-13","29.272","13.4.0","MONTE-CT","0621","2","B",null,"","","","",""]
["C4-161511","Definition of Monitoring-Type and clarifications on UE in MME and SGSN for MONTE","Huawei","John M Meredith",637,"CR","","Decision","","","19","7.1.9","Monitoring Enhancements CT aspects [MONTE-CT]",12893,"agreed","2016-02-19T00:36:25.947","2016-02-19T02:20:15.767","C4-161497","CP-160129","Rel-13","29.336","13.2.0","MONTE-CT","0048","3","B","CP-160029","","","","",""]
["C4-161512","draft 29.128","rapporteur","John M Meredith",637,"draft TS","","Agreement","","","19","7.1.9","Monitoring Enhancements CT aspects [MONTE-CT]",12943,"not concluded","2016-02-22T17:22:36.753","2016-02-29T07:58:55.083","","","Rel-13","29.128","1.1.0","","","","","","","","","",""]
["C4-161513","DNS procedures for Decor","NTT DOCOMO, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell","John M Meredith",637,"CR","","Agreement","","","28","7.1.18","Dedicated Core Networks [DECOR-CT]",11764,"agreed","2016-02-22T17:22:37.177","2016-03-01T15:03:23.590","C4-161482","","Rel-13","29.303","13.2.0","DECOR-CT","0086","4","B","CP-160022","","","","",""]
["C4-161514","Skeleton for Sh* application for MCPTT-2 and CSC-13 interfaces","Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Nokia Networks, Orange, Motorola","John M Meredith",637,"pCR","","Decision","","","43","7.2.11","Mission Critical Push To Talk over LTE protocol aspects (CT1) [MCPTT-CT]",12382,"revised","2016-02-22T17:22:37.427","2016-03-01T15:03:23.607","C4-161479","C4-161538","Rel-13","","","MCPTT-CT","","",null,"","","","","",""]
["C4-161515","new Diameter application for MCPTT-2 and CSC-13 reference points","ORANGE, HPE, Motorola","John M Meredith",637,"draft TS","","Approval","","","43","7.2.11","Mission Critical Push To Talk over LTE protocol aspects (CT1) [MCPTT-CT]",12707,"revised","2016-02-22T17:22:37.613","2016-02-22T17:30:19.807","C4-161439","C4-161516","Rel-13","29.283","0.0.0","MCPTT-CT","","","","","","","","",""]
["C4-161516","new Diameter application for MCPTT-2 and CSC-13 reference points","ORANGE, HPE, Motorola","John M Meredith",637,"draft TS","","Approval","","","43","7.2.11","Mission Critical Push To Talk over LTE protocol aspects (CT1) [MCPTT-CT]",12708,"available","2016-02-22T17:22:37.940","2016-02-29T07:58:55.990","C4-161515","","Rel-13","29.283","0.1.0","MCPTT-CT","","","","","","","","",""]
["C4-161517","Introduction of AAA-1 interface","Huawei, Ericsson","John M Meredith",637,"CR","","Decision","AAA-1 interface is introduced.","","43","7.2.11","Mission Critical Push To Talk over LTE protocol aspects (CT1) [MCPTT-CT]",10884,"agreed","2016-02-22T17:22:38.220","2016-03-01T15:03:23.607","C4-161502","","Rel-13","29.228","13.0.0","MCPTT-CT","0661","6","B","CP-160031","","","","",""]
["C4-161518","Connection management  procedures over T6a","Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Nokia Networks, Cisco Systems Inc","John M Meredith",637,"pCR","","Agreement","","","46","7.2.14","CIoT-CT (CT1)  [CIoT-CT]",22003,"revised","2016-02-22T17:22:38.453","2016-03-01T15:03:23.607","C4-161487","C4-161544","Rel-13","29.128","1.0.0","CIoT-CT","","",null,"","","","","",""]
["C4-161519","Impacts on the DNS procedures for CIoT with introduction of NB-IoT and Non-IP","Ericsson LM","John M Meredith",637,"LS out","","Decision","","","46","7.2.14","CIoT-CT (CT1)  [CIoT-CT]",45007,"approved","2016-02-22T17:22:38.610","2016-03-01T15:03:23.607","C4-161471","","Rel-13","","","NB_IOT, CIoT-CT","","","","",null,"SA2"]
["C4-161520","LS on New AVPs and Experimental Result Code in TS 29.214","CT3","John M Meredith",637,"LS in","","Action","CT3 asks CT4 to kindly update TS 29.230 with the new AVPs and experimental result codes defined in TS 29.214 for Rel-13.","","49","7.3.2","Diameter 29.230 CRs [TEI13]",152000,"noted","2016-02-22T17:22:38.767","2016-03-01T15:03:23.607","","","","","","","","","","",null,null,null,"C3-160131"]
["C4-161521","LS on Allocation of new Diameter Application ID and commands code for PC2 protocol","CT3","John M Meredith",637,"LS in","","Action","CT3 kindly asks CT4 and their MCC support to request a new Diameter application ID and command codes for the PC2 Diameter application documented in TS29.343.\nCT3 also asks CT4 to kindly update TS 29.230 with the Diameter Codes provided in the present LS.","","39","7.2.7","CT aspects of enhancements to Proximity-based Services extensions (CT1) [eProSe-Ext-CT]",13829,"noted","2016-02-22T17:22:38.890","2016-03-01T15:03:23.623","","","","","","","","","","",null,null,null,"C3-160214"]
["C4-161522","LS on Request for Diameter Command Code for new St Interface","CT3","John M Meredith",637,"LS in","","Action","CT3 asks CT4 and their MCC to kindly request a new Diameter Commend code for the Diameter St application from IANA.","","6","4","Input liaison statements: allocation to agenda items as appropriate",152600,"postponed","2016-02-22T17:22:39.030","2016-03-01T15:03:23.623","","","","","","","","","","",null,null,null,"C3-160165"]
["C4-161523","LS on new AVPs in TS 29.212","CT3","John M Meredith",637,"LS in","","Action","CT4 to kindly update TS 29.230 with the Diameter Codes provided in the present LS.","","6","4","Input liaison statements: allocation to agenda items as appropriate",152600,"noted","2016-02-22T17:22:39.187","2016-03-01T15:03:23.623","","","","","","","","","","",null,null,null,"C3-160371"]
["C4-161524","LS on EVS over CS (S4-160310/ C3-160189)","CT3","John M Meredith",637,"LS in","","Action","CT3 would like to thank SA4 for their LS on EVS over CS.\nIn the LS, SA4 provided (among other specifications) TS 26.454 v.1.0.0 \"Codec for Enhanced Voice Services (EVS); Interface to Iu, Uu, Nb and Mb\" that is being submitted for approval to SA plenary f","","6","4","Input liaison statements: allocation to agenda items as appropriate",152600,"postponed","2016-02-22T17:22:39.343","2016-03-01T15:03:23.623","","","","","","","","","","",null,null,null,"C3-160393"]
["C4-161525","Transfer of non IP PDN to peer MME during mobility","Cisco Systems Inc","John M Meredith",637,"CR","","Approval","","","46","7.2.14","CIoT-CT (CT1)  [CIoT-CT]",50003,"revised","2016-02-22T17:22:39.483","2016-03-01T15:03:23.637","C4-161480","C4-161532","Rel-13","29.274","13.4.0","CIoT-CT","1697","3","B",null,"","","","",""]
["C4-161526","New PDN-Type for Cellular IoT","Ericsson","John M Meredith",637,"CR","","","","","46","7.2.14","CIoT-CT (CT1)  [CIoT-CT]",24003,"agreed","2016-02-22T17:22:39.703","2016-03-01T15:03:23.637","C4-161490","","Rel-13","29.272","13.4.0","CIoT-CT","0631","3","B","CP-160033","","","","",""]
["C4-161527","New PDN-Type for Cellular IoT","Ericsson","John M Meredith",637,"CR","","","","","46","7.2.14","CIoT-CT (CT1)  [CIoT-CT]",25002,"agreed","2016-02-22T17:22:39.967","2016-03-01T15:03:23.637","C4-161313","","Rel-13","29.002","13.2.0","CIoT-CT","1205","2","B","CP-160033","","","","",""]
["C4-161528","New PDN-Type for Celullar IoT","Ericsson","John M Meredith",637,"CR","","","","","46","7.2.14","CIoT-CT (CT1)  [CIoT-CT]",26002,"agreed","2016-02-22T17:22:40.233","2016-03-01T15:03:23.637","C4-161314","","Rel-13","29.230","13.3.0","CIoT-CT","0520","2","B","CP-160033","","","","",""]
["C4-161529","New PDN-Type for Celular IoT","Ericsson","John M Meredith",637,"CR","","","","","46","7.2.14","CIoT-CT (CT1)  [CIoT-CT]",27002,"agreed","2016-02-22T17:22:40.483","2016-03-01T15:03:23.653","C4-161315","","Rel-13","23.008","13.3.0","CIoT-CT","0488","2","B","CP-160033","","","","",""]
["C4-161530","Authorisation for NIDD procedure over  S6t","Huawei, Vodafone","John M Meredith",637,"CR","","Decision","","","46","7.2.14","CIoT-CT (CT1)  [CIoT-CT]",34002,"agreed","2016-02-22T17:22:40.717","2016-03-01T15:03:23.653","C4-161324","","Rel-13","29.336","13.2.0","CIoT-CT","0046","4","B","CP-160033","","","","",""]
["C4-161531","S11-U tunneling for MO/MT data transport in control plane (SGi based) - with new S11-U F-TEIDs","Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Nokia Networks, Verizon, AT&T, Orange, China Mobile, Deutsche Telekom, Huawei.","John M Meredith",637,"CR","","Approval","","","46","7.2.14","CIoT-CT (CT1)  [CIoT-CT]",38003,"agreed","2016-02-22T17:22:40.937","2016-03-01T15:03:23.653","C4-161469","","Rel-13","29.274","13.4.0","CIoT-CT","1689","3","B","CP-160033","","","","",""]
["C4-161532","Transfer of non IP PDN to peer MME during mobility","Cisco Systems Inc","John M Meredith",637,"CR","","Approval","","","46","7.2.14","CIoT-CT (CT1)  [CIoT-CT]",50004,"revised","2016-02-22T17:22:41.217","2016-03-01T15:03:23.653","C4-161525","C4-161539","Rel-13","29.274","13.4.0","CIoT-CT","1697","4","B",null,"","","","",""]
["C4-161533","Behaviours upon receipt of unknown NIDD","Huawei","John M Meredith",637,"CR","","Agreement","","","46","7.2.14","CIoT-CT (CT1)  [CIoT-CT]",56002,"revised","2016-02-22T17:22:41.403","2016-03-01T15:03:23.653","C4-161436","C4-161546","Rel-13","23.007","13.3.0","CIoT-CT","0334","2","B",null,"","","","",""]
["C4-161534","Protocol for Non IP-Data over T6a","Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Nokia Networks, Cisco Systems Inc","John M Meredith",637,"pCR","","Agreement","","","46","7.2.14","CIoT-CT (CT1)  [CIoT-CT]",23003,"approved","2016-02-22T17:22:41.653","2016-03-01T15:03:23.670","C4-161488","","Rel-13","29.128","1.0.0","CIoT-CT","","",null,"","","","","",""]
["C4-161535","Questions on non-IP data delivery procedures","CT4","John M Meredith",637,"LS out","","Discussion","","","46","7.2.14","CIoT-CT (CT1)  [CIoT-CT]",21005,"approved","2016-02-22T17:22:41.807","2016-03-01T15:03:23.670","C4-161485","","","","","","","","","",null,"SA2","SA3"]
["C4-161536","Allocation of new Diameter Application ID and commands code for PC2 protocol","Huawei","John M Meredith",637,"CR","","Decision","","","39","7.2.7","CT aspects of enhancements to Proximity-based Services extensions (CT1) [eProSe-Ext-CT]",13821,"revised","2016-02-22T17:22:41.963","2016-03-01T15:03:23.670","C4-161382","C4-161543","Rel-13","29.230","13.3.0","eProSe-Ext-CT","0519","2","B",null,"","","","",""]
["C4-161537","Reply LS on clarification on requirements for MONTE","Huawei","John M Meredith",637,"LS out","","","","","19","7.1.9","Monitoring Enhancements CT aspects [MONTE-CT]",14601,"approved","2016-02-22T17:22:42.213","2016-03-01T15:03:23.670","C4-161460","","Rel-13","","","MONTE-CT","","","","","C4-161035","SA2"]
["C4-161538","Skeleton for Sh* application for MCPTT-2 and CSC-13 interfaces","Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Nokia Networks, Orange, Motorola","John M Meredith",637,"pCR","","Decision","","","43","7.2.11","Mission Critical Push To Talk over LTE protocol aspects (CT1) [MCPTT-CT]",12383,"withdrawn","2016-02-22T17:22:42.370","2016-03-01T15:03:23.687","C4-161514","","Rel-13","","","MCPTT-CT","","",null,"","","","","",""]
["C4-161539","Transfer of non IP PDN to peer MME during mobility","Cisco Systems Inc","John M Meredith",637,"CR","","Approval","","","46","7.2.14","CIoT-CT (CT1)  [CIoT-CT]",50005,"revised","2016-02-22T17:22:42.510","2016-03-01T15:03:23.687","C4-161532","C4-161545","Rel-13","29.274","13.4.0","CIoT-CT","1697","5","B",null,"","","","",""]
["C4-161540","Configure Monitoring Event to Multiple Serving Nodes","ZTE","John M Meredith",637,"CR","","Approval","","","19","7.1.9","Monitoring Enhancements CT aspects [MONTE-CT]",11283,"agreed","2016-02-22T17:22:42.730","2016-03-01T15:03:23.687","C4-161510","","Rel-13","29.272","13.4.0","MONTE-CT","0621","3","B","CP-160029","","","","",""]
["C4-161541","Reply LS to CT4 LS on progress of the work on Diameter Base Protocol Update","ORANGE","John M Meredith",637,"LS out","","Decision","","","29","7.1.19","Feasibility Study on the Diameter Base Protocol Update [FS_DBPU]",14561,"agreed","2016-02-22T17:22:42.963","2016-03-01T15:03:23.687","C4-161456","","Rel-13","29.819","1.0.0","FS_DBPU","","","","","C4-161220","SA5","CT3, SA"]
["C4-161542","draft TR 29.819","Lionel Monrad","John M Meredith",637,"other","","Information","","","29","7.1.19","Feasibility Study on the Diameter Base Protocol Update [FS_DBPU]",14462,"not concluded","2016-02-22T17:22:43.120","2016-03-02T10:25:47.183","","","","29.819","1.1.0","","","","","","","","","",""]
["C4-161543","Allocation of new Diameter Application ID and commands code for PC2 protocol","Huawei","John M Meredith",637,"CR","","Decision","","","39","7.2.7","CT aspects of enhancements to Proximity-based Services extensions (CT1) [eProSe-Ext-CT]",13822,"agreed","2016-02-22T17:22:43.260","2016-03-01T15:03:23.700","C4-161536","","Rel-13","29.230","13.3.0","eProSe-Ext-CT","0519","3","B","CP-160036","","","","",""]
["C4-161544","Connection management  procedures over T6a","Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Nokia Networks, Cisco Systems Inc","John M Meredith",637,"pCR","","Agreement","","","46","7.2.14","CIoT-CT (CT1)  [CIoT-CT]",22004,"approved","2016-02-22T17:22:43.463","2016-03-01T15:03:23.700","C4-161518","","Rel-13","29.128","1.0.0","CIoT-CT","","",null,"","","","","",""]
["C4-161545","Transfer of non IP PDN to peer MME during mobility","Cisco Systems Inc","John M Meredith",637,"CR","","Approval","","","46","7.2.14","CIoT-CT (CT1)  [CIoT-CT]",50006,"agreed","2016-02-22T17:22:43.633","2016-03-01T15:03:23.700","C4-161539","","Rel-13","29.274","13.4.0","CIoT-CT","1697","6","B","CP-160033","","","","",""]
["C4-161546","Behaviours upon receipt of unknown NIDD","Huawei","John M Meredith",637,"CR","","Agreement","","","46","7.2.14","CIoT-CT (CT1)  [CIoT-CT]",56003,"agreed","2016-02-22T17:22:43.853","2016-03-01T15:03:23.700","C4-161533","","Rel-13","23.007","13.3.0","CIoT-CT","0334","3","B","CP-160033","","","","",""]
["C4-161547","CT4 aspect of the Workplan","CT4 Chairman","John M Meredith",637,"Work Plan","","Approval","","","168","11","Update of the Work Plan",12751,"approved","2016-02-22T17:22:44.053","2016-03-01T15:03:23.717","C4-161275","","Rel-13","","","","","","","","","","","",""]
["C4-161548","List of output documents","Chairman","John M Meredith",637,"other","","Information","","","171","14","Check of approved output documents",154800,"available","2016-02-22T17:22:44.210","2016-02-23T09:43:11.423","","","","","","","","","","","","","","",""]

{"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"]