{"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":5,"comments":0,"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":201,"n_cols":31,"rows_kept":201,"cut":false,"hidden":false,"merged":[]}
["TDoc #","Title","Source","Contact","Contact ID","Type","Type supplement","For","Abstract","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"]
["SP-150172","LS from TSG RAN ITU-R Ad Hoc: Letter to ITU on Update submission for LTE-Advanced toward Rev. 2 of Rec. ITU-R M.2012","TSG CT","Maurice Pope",648,"LS in","","","Overall description: ITU-R Working Party 5D (WP 5D) is developing Revision 2 of the Recommendation M.2012 ('Detailed specifications of the terrestrial radio interfaces of International Mobile Telecommunications-Advanced (IMT-Advanced)').  According to the approved procedure, 3GPP is requested to submit a preliminary indication of the modifications foreseen to be submitted in ITU-R WP5D. The baseline for the material to be submitted to ITU-R will be the 3GPP specifications approved in Rel. 12. Since MCC provided a comprehensive description of the features included in Release 12, it is proposed to submit to ITU-R WP5D the document 'Rel-12_description_20131224', as indicated in Annex 1 of the document.  Actions: 3GPP ITU-R Ad Hoc asks TSG RAN to review the attached draft answer back to ITU-R and submit the approved version to SA. 3GPP ITU-R Ad Hoc asks TSG SA to review the document as approved by RAN and provide feedbacks to the PCG.","17","7.7","TSG RAN report and Questions for Advice",10190,"Approved","2015-06-09T16:55:55.790","2015-06-09T16:55:49.083","","SP-150173","","","","","","","","",null,null,null,"CP-150221"]
["SP-150173","LS from TSG RAN ITU-R Ad Hoc: Letter to ITU on Update submission for LTE-Advanced toward Rev. 2 of Rec. ITU-R M.2012","TSG SA","Maurice Pope",648,"LS out","","","Overall description: ITU-R Working Party 5D (WP 5D) is developing Revision 2 of the Recommendation M.2012 ('Detailed specifications of the terrestrial radio interfaces of International Mobile Telecommunications-Advanced (IMT-Advanced)').  According to the approved procedure, 3GPP is requested to submit a preliminary indication of the modifications foreseen to be submitted in ITU-R WP5D. The baseline for the material to be submitted to ITU-R will be the 3GPP specifications approved in Rel. 12. Since MCC provided a comprehensive description of the features included in Release 12, it is proposed to submit to ITU-R WP5D the document 'Rel-12_description_20131224', as indicated in Annex 1 of the document.  Actions: 3GPP ITU-R Ad Hoc asks TSG RAN to review the attached draft answer back to ITU-R and submit the approved version to SA. 3GPP ITU-R Ad Hoc asks TSG SA to review the document as approved by RAN and provide feedbacks to the PCG.","17","7.7","TSG RAN report and Questions for Advice",10200,"Approved","2015-06-09T16:55:55.820","2015-06-09T16:55:49.083","SP-150172","","","","","","","","","",null,"PCG"]
["SP-150174","Draft agenda for TSG SA meeting #68","TSG SA Chairman","Erik Guttman",18782,"agenda","","","Draft agenda for TSG SA meeting #68","2","2","Approval of Agenda",10000,"Approved","2015-06-09T16:55:55.820","2015-06-09T16:55:49.083","","","","","","","","","","","","","","",""]
["SP-150175","Draft Report of TSG SA meeting #67","TSG SA Secretary","Maurice Pope",648,"report","","","Draft Report of TSG SA meeting #67 containing revision marks of changes on the distributed draft.","5","4.1","Report from SA#67",10030,"Approved","2015-06-09T16:55:55.837","2015-06-11T05:37:05.537","","","","","","","","","","","","","","",""]
["SP-150176","LS from CT WG1: LS on Rel-13 MCPTT work","CT WG1","Maurice Pope",648,"LS in","","","CT WG1 would like to inform SA6 that, in light of the project plan proposal on Rel-13 MCPTT that was presented at CT#67 in CP-150184, CT WG1 has had some preliminary discussion about the stage 3 Rel-13 MCPTT work that is scheduled to start in CT WGs in August 2015. During the discussion, for On Network Operations, a majority of companies expressed their preference for an IMS-based architecture due to concerns about the feasibility of specifying the stage 3 for a non-IMS-based solution within only 3 CT WG1 WG meetings. Additionally an alternative deployment option could be worked on by CT WG1, but likely in a longer timeframe. For this it is essential to get informed about SA6 decision as soon as possible.  Moreover, in order to prepare for the start of the stage 3 work on Rel-13 MCPTT, CT WG1 would also appreciate some feedback from SA6 on the following points:  a. Per CT WG1's Terms of Reference, CT WG1 expects the application and extension of SIP, SDP and XCAP for MCPTT to","84","13.1","(MCPTT) - Mission Critical Push-to-Talk over LTE",10690,"Noted","2015-06-09T16:55:55.853","2015-06-09T16:55:49.097","","","Rel-13","","","MCPTT","","","","",null,null,null,"C1-151620"]
["SP-150177","LS from ETSI TC ITS: Reply LS on information regarding V2X study in 3GPP","ETSI TC ITS","Maurice Pope",648,"LS in","","","ETSI TC ITS thanks 3GPP SA for their LS on information regarding V2X study in 3GPP. ETSI TC ITS would like to inform 3GPP about the availability of the ITS standards Release 1 (see the Technical Report TR 101 607 enclosed). These specifications include the basic use cases and the requirements of the Cooperative-ITS system and is available on the ETSI portal free of charge. ETSI TC ITS encourages 3GPP to take these use cases and requirements into consideration and reuse them as their benefits have been proven to be feasible in large scale by research projects, tests and field trials. ETSI TC ITS would like to make 3GPP aware that the ETSI G5-air interface of the Cooperative-ITS solution is based on IEEE 802.11p. The overall ITS architecture allows for other access technologies, including a mixture of cellular and ETSI G5-air interface. This may be taken into consideration in the 3GPP study. ETSI TC ITS invites 3GPP SA WG1 to keep them informed of the progress of the study on L","186","15.2.31","(FS_V2XLTE) - Study on LTE support for V2X services",11630,"Noted","2015-06-09T16:55:55.853","2015-06-09T16:55:49.097","","","Rel-13","","","MCPTT","","","","",null,null,null,"ITS(15)000063r1"]
["SP-150178","LS from GSMA RAG: LS on VoLTE Roaming Architecture","GSMA RAG","Itsuma Tanaka",38539,"LS in","","","Introduction As announced in the previous communication from GSMA PSMC (PSMC 131 Doc 201, SP-150139) on a new VoLTE roaming architecture option called 'S8 Home Routed (S8HR)', Networks Group (NG) would like to provide more details on the areas that may require further technical investigation.","124","13.41","(LI13) - Lawful Interception in Rel-13",11220,"Noted","2015-06-09T16:55:55.867","2015-06-09T16:55:49.097","","","Rel-13","","","LI13","","","","",null,null,null,"RAG 14 Doc 013"]
["SP-150179","LS from SA WG1: Response to Reply LS on Security Framework for Cellular IoT","SA WG1","Chris Pudney",1122,"LS in","","","SA WG1 thanks SA WG3 for their LS in S3-151198. SA WG1 is aware of the reply from GERAN 2 to SA WG3 in GPC150120. SA WG1 is also aware of the SIDs agreed at SA#67 in Shanghai as attached to SA's outgoing LS in SP-150170, and, that the GERAN TR 45.820 has now reached the formal v1.0.0 'for information' status level of >60% completion level (see http://www.3gpp.org/DynaReport/45820.htm).   In addition to the questions raised by SA WG3 in the LS, SA WG1understand that SA WG3 would like SA WG1 to provide information about use cases for these ultra-low throughput, extended range and low complexity devices.","158","15.2.2","(FS_AE_CIoT) - Study on architecture enhancements of cellular systems for ultra low complexity and low throughput Internet of Things",11490,"Noted","2015-06-09T16:55:55.883","2015-06-09T16:55:49.113","","","Rel-13","","","FS_IoT_LC","","","","",null,null,null,"S1-151528"]
["SP-150180","LS from SA WG1: LS on V2X Study in 3GPP SA1","SA WG1","Maurice Pope",648,"LS in","","","SA WG1 would like to thank ETSI ITS for sending SA WG1 a Reply LS on information regarding V2X study in 3GPP (ITS(15)000063 rev1/S1-151448), inviting SA WG1 to keep ETSI ITS informed of the progress of the study on LTE support for V2X services. SA WG1 is happy to provide the following information: - SA WG1 is progressing Study on LTE support for V2X services (FS_V2XLTE); - SA WG1 recognises that there are important V2V, V2I, and V2P. SA WG1 has prioritised V2V services but is also addressing V2I and V2P; - SA WG1 is not proposing that 3GPP defines application layer message sets, but that 3GPP provides a transport system capable of supporting the various service layers (including ETSI ITS); - All 3GPP SA WG1 documents can be found at the 3GPP web site, including latest approved versions of TR 22.885.","186","15.2.31","(FS_V2XLTE) - Study on LTE support for V2X services",11650,"Withdrawn","2015-06-09T16:55:55.883","2015-06-09T16:55:49.113","","","Rel-14","","","FS_V2XLTE","","","","",null,null,null,"S1-151605"]
["SP-150181","LS from SA WG1: Reply LS on LTE based Vehicular Communication","SA WG1","Maurice Pope",648,"LS in","","","SA WG1 would like to thank RAN for sending SA WG1 an LS on LTE based Vehicular Communication (RP-142312/S1-151227/=S1-150039), which informed SA WG1 of a potential RAN study on LTE-based Vehicular Communication for Release 13.   SA WG1 had agreed on Study on LTE support for V2X services (FS_V2XLTE) for Release 14, which was approved in SA#67 (03/2015) with Target Completion in SA#70 (12/2015). SA WG1 recognises that there are important V2V, V2I and V2P use cases. SA WG1 has prioritised work on V2V services over V2I and V2P. SA WG1 recently agreed to several potential requirements for V2V which are captured together with some potential requirements on V2I and V2P in the attached draft TR.","186","15.2.31","(FS_V2XLTE) - Study on LTE support for V2X services",11640,"Noted","2015-06-09T16:55:55.900","2015-06-09T16:55:49.113","","","Rel-14","","","FS_V2XLTE","","","","",null,null,null,"S1-151629"]
["SP-150182","LS from SA WG2: Response to Reply LS on Security Framework for Cellular IoT","SA WG2","Chris Pudney",1122,"LS in","","","SA WG2 thanks SA WG3 for their LS in S3-151198. SA WG2 is aware of the reply from GERAN 2 to SA WG3 in GPC150120. SA WG2 is also aware of the SIDs agreed at SA#67 in Shanghai as attached to SA's outgoing LS in SP-150170, and, that the GERAN TR 45.820 has now reached the formal v1.0.0 'for information' status level of >60% completion level (see http://www.3gpp.org/DynaReport/45820.htm).","158","15.2.2","(FS_AE_CIoT) - Study on architecture enhancements of cellular systems for ultra low complexity and low throughput Internet of Things",11500,"Noted","2015-06-09T16:55:55.913","2015-06-09T16:55:49.113","","","Rel-13","","","FS_IoT_LC","","","","",null,null,null,"S2-151382"]
["SP-150183","LS from SA WG2: Reply LS on IMS Emergency Session over WLAN","SA WG2","Hyunsook Kim",42013,"LS in","","","SA WG2 would like to inform GSMA Networks Group RILTE that SA WG2 has started to work on the feasibility of supporting emergency services over WLAN.  The study will be split up into 2 phases.  If deemed appropriate, topics studied (and solutions agreed) in phase 1 can be selected to be moved to normative work (with an associated WID) before the phase 2 starts and the study concludes.  Topics to be studied in phase 1 are: - Providing access to EPC over WLAN in order to support an emergency session only in case of 'Valid' UEs as in the case 1 in clause 4.3.12.1 of TS 23.401: the support of emergency session is only studied for UEs which (a) have valid credentials to access EPC over WLAN and (b) are authorized to connect to EPC over WLAN in the location where they initiate an emergency session - Providing Location information (in particular for untrusted WLAN). Only existing location determination mechanisms are considered i.e. location determination mechanisms that should not r","176","15.2.20","(FS_SEW) - Study on the Support of Emergency services over WLAN",11580,"Noted","2015-06-09T16:55:55.913","2015-06-09T16:55:49.113","","","Rel-13","","","FS_SEW","","","","",null,null,null,"S2-151431"]
["SP-150184","LS from SA WG4: LS on codec support in IMS-WebRTC for WLAN and fixed access","SA WG4","Maurice Pope",648,"LS in","","","SA WG4 would like to thank CT WG1 for their CR on IMS-WebRTC following SA WG4 communication from SA WG4#82. [...] Assuming a WLAN connected to EPC (TS 24.229 Annex R), handover is defined between EPS (E-UTRAN+EPC) and WLAN connected to EPC, hence WLAN connected to EPC should be considered a 3GPP access and the GPRS/EPS codecs should apply to WLAN connected to EPC as well.  Also, codecs for fixed access are specified in clause 18 of TS 26.114 via reference to ETSI TS 181 005 (ETSI TS 181 005, v3.3.1: 'Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Service and Capability Requirements'.). Such reference to clause 18 can be used for recommended codecs of WebRTC IMS over fixed access. In particular, AMR, AMR-WB, EVS, G.711 and H.264 are recommended.","31","12.2","(IMS_WebRTC) - Web Real Time Communication (WebRTC) Access to IMS",10380,"Noted","2015-06-09T16:55:55.930","2015-06-09T16:55:49.113","","","Rel-12","","","IMS_WebRTC","","","","",null,null,null,"S4-150401"]
["SP-150185","LS from SA WG6: Reply to Document C1-151620:  LS on Rel-13 MCPTT work","SA WG6","Alan Soloway",46784,"LS in","","","SA WG6 would like to thank CT WG1 (CT WG1) for contacting SA WG6 for clarification related to Mission Critical Push to Talk (MCPTT).  Requested actions to SA WG6: 1. CT WG1 kindly asks SA WG6 to take into account the summary of the CT WG1 discussion above for their Rel-13 work on MCPTT. 2. CT WG1 kindly asks SA WG6 to provide feedback on items a, b and c above to help CT WG1 prepare for their Rel-13 work on MCPTT. In regards to requested action #1, SA WG6 thanks CT WG1 for the information and will take the summary of the CT WG1 discussion into account for the Rel-13 MCPTT work. In regards to requested action #2, please see the individual feedback below for items a, b and c. a. Per CT WG1's Terms of Reference, CT WG1 expects the application and extension of SIP, SDP and XCAP for MCPTT to be under the responsibility of CT WG1. CT WG1 would like to know if SA WG6 has already identified other additional MCPTT protocol aspects b. Which MCPTT architecture aspects will be under the","84","13.1","(MCPTT) - Mission Critical Push-to-Talk over LTE",10700,"Noted","2015-06-09T16:55:55.947","2015-06-09T16:55:49.127","","","Rel-13","","","MCPTT","","","","",null,null,null,"S6-150292"]
["SP-150186","LS from TTC: Liaison to 3GPP on TTC's white paper future mobile networking","TTC","Maurice Pope",648,"LS in","","","It is a great honor to inform you that TTC provides herewith our white paper on future mobile networking.  Since September 2014, TTC has studieSince September 2014, TTC has studied future mobile networking around 2020 and beyond in various aspects, incl. mobile core network, mobile back-haul, mobile front-haul, security, and network management. And the study has identified technical challenges, surveyed candidate solutions, and con sidered future directions. TTC has recently finalized the white paper, and it is attached to this liaison. The key messages are captured in section 8. TTC hopes our white paper is of use for further development development future mobile networking in 3GPP.","9","6","General Incoming Liaisons (Liaisons related to specific features will be covered under the feature related agenda item)",10100,"Noted","2015-06-09T16:55:55.947","2015-06-09T16:55:49.127","","","","","","","","","","",null,null,null,"TTC liaison on WP_20150409"]
["SP-150187","LS from NGMN:  Liaison on NGMN 5G White Paper","NGMN","Maurice Pope",648,"LS in","","","The intention of this liaison is to inform 3GPP about the NGMN 5G vision, requirements, guidelines and way forward outlined in the NGMN 5G White Paper. Please share the NGMN 5G White Paper with all your relevant working groups or projects and kindly ask them to consider this in their future work. Please make them aware of the future NGMN 5G related planning as outlined above. We would like to invite 3GPP to provide feedback on the NGMN 5G White Paper. In addition, we would like to inform 3GPP that it is our intention to keep 3GPP updated on our future NGMN 5G work-programme and the related requirements at major milestones.  We look forward to deeper and further collaboration with 3GPP on 5G related activities.","9","6","General Incoming Liaisons (Liaisons related to specific features will be covered under the feature related agenda item)",10070,"Noted","2015-06-09T16:55:55.960","2015-06-09T16:55:49.127","","","","","","","","","","",null,null,null,"NGMN_150323"]
["SP-150188","LS from APT Wireless Group: Liaison Statement to 3GPP regarding scope and status relevant to PPDR work items and study items","APT Wireless Group","Maurice Pope",648,"LS in","","","The APT AWG would like to thank 3GPP for their liaison statement no. SP-140886 received from TSG SA Meeting #66 (10-12 December 2014, Maui, USA) and would like to seek confirmation of the Table attached as Annex 1 with this LS, which has been developed based on the input from your LS.  The AWG therefore requests 3GPP to provide confirmation of the contents of the attached Annex 1.  APT respectfully requests response in time for the next meeting of the AWG, which is scheduled to be held in February 2016.","84","13.1","(MCPTT) - Mission Critical Push-to-Talk over LTE",10670,"Postponed","2015-06-09T16:55:55.977","2015-06-09T16:55:49.127","","","Rel-13","","","MCPTT","","","","",null,null,null,"AWG-18-OUT-06-R1-PPDR-LS-to-3GPP"]
["SP-150189","LS from GERAN WG1:  LS on LTE/UMTS coexistence studies for FS_IoT_LC","GERAN WG1","Chris Pudney",1122,"LS in","","","GERAN WG1 are making progress with their work on the 'Study Item on Cellular System Support for Ultra Low Complexity and Low Throughput Internet of Things' (FS_IoT_LC) and documenting it in TR 45.820.  Currently TR 45.820 contains a description of one evolved-GSM proposal and 2 'clean slate' (new) proposals. Two other 'clean slate' proposals, and one other evolved-GSM concept have been discussed in TSG GERAN but are not yet included within TR 45.820.  While the final outcome of the study item is, as yet, uncertain, the rapporteur intends it to lead to normative work within Release 13.  The FS_IoT_LC Study Item Description in GP-140421 contains the objective:  - Avoid negative impacts to legacy GSM/WCDMA/LTE system(s) deployed in the same frequency band and adhere to the regulatory requirements applying to the spectrum bands in which the system operates. GERAN WG1 understands that RAN WG4 has a very heavy workload and hence is unlikely to wish to review inter-RAT co-existence","158","15.2.2","(FS_AE_CIoT) - Study on architecture enhancements of cellular systems for ultra low complexity and low throughput Internet of Things",11510,"Noted","2015-06-09T16:55:55.977","2015-06-09T16:55:49.127","","","Rel-13","","","FS_IoT_LC","","","","",null,null,null,"GPC150305"]
["SP-150190","LS from ETSI ISG Chairman: Liaison about ETSI ISG IP6 creation and interaction with other groups","ETSI ISG Chairman","Maurice Pope",648,"LS in","","","Dear Madam, Dear Sir,  We are pleased to inform you that ETSI has successfully held the first meeting of their newly created Industry Specification Group on IPv6 Integration on 22-23 April, 2015.  The ETSI 'IPv6 integration' Industry Specification Group (IP6 ISG) is a working group to focus on IPv6-based best practices, deployment guidelines and success showcases identifying thereby what and where consensus and harmonization could be reached.  We invite all interested parties from your organization or others to join in. Participation in the ISG IP6 is subject to signature of an ISG IP6 Agreement you can find at https://portal.etsi.org/tb.aspx?tbid=827&SubTB=827. Explanation about those agreements is also available from the same location.  We have started work on the following items: -      IPv6 Deployment in the Enterprise -      IPv6 in Telecom /ISPs -      IPv6 in Safety & Emergency Sector -      IPv6 For Academia & Education -      IPv6 For Governments -      Generic migra","9","6","General Incoming Liaisons (Liaisons related to specific features will be covered under the feature related agenda item)",10080,"Noted","2015-06-09T16:55:55.993","2015-06-09T16:55:49.127","","","","","","","","","","",null,null,null,"IP6(15)001031"]
["SP-150191","LS from SA WG3LI: Reply LS on VoLTE Roaming Architecture","SA WG3LI","Maurice Pope",648,"LS in","","","SA WG3 LI would like to thank GSMA PSMC for their LS on VoLTE Roaming architecture.  SA WG3 LI identified that LI in VPLMN for inbound roamers is the issue, and that LI in HPLMN for outbound roamers is not an issue. SA WG3 LI also identified that LI in HPLMN on behalf of VPLMN across jurisdictions will not meet requirements.  SA WG3 LI understands that there are countries (e.g. Japan) in which the national regulations' LI requirement may be met possibly using LI capabilities not specified by 3GPP in case of S8HR without further work by 3GPP, and that there are countries (e.g. France) in which the national regulations lead to further work by 3GPP, based on current LI capabilities as defined in 3GPP specifications.   SA WG3 LI understands that there are national regulations that lead to the requirement that S8HR scenario can only be deployed when there is no confidentiality protection for all inbound roamers only at the point of interception in the VPLMN. For these cases there","124","13.41","(LI13) - Lawful Interception in Rel-13",11260,"Noted","2015-06-09T16:55:56.007","2015-06-09T16:55:49.143","","","Rel-13","","","LI13","","","","",null,null,null,"S3i150145","SP-150371"]
["SP-150192","LS from SA WG3LI: Reply to LS on VoLTE Roaming Architecture GSMA","SA WG3LI","Maurice Pope",648,"LS in","","","GSMA NG requested SA WG3-LI to review the S8HR candidate roaming architecture, consider the LI service impacts and indicate the scope of the work to address those impacts.  This Liaison Statement response describes the initial set of issues affecting the LI service currently specified by 3GPP when S8HR roaming is deployed. It also lists the initial set of tasks that SA WG3-LI has identified to develop the support required for a 3GPP LI service to handle S8HR roaming scenarios.","124","13.41","(LI13) - Lawful Interception in Rel-13",11250,"Noted","2015-06-09T16:55:56.023","2015-06-09T16:55:49.143","","","Rel-13","","","LI13","","","","",null,null,null,"S3i150153"]
["SP-150193","LS from GSMA RAG: LS on VoLTE Roaming Charging","GSMA RAG","Itsuma Tanaka",38539,"LS in","","","Introduction: GSMA Networks Group (NG) is currently assessing the scenario where operators would implement VoLTE Roaming according to the S8HR (Home Routing) architecture. In that context, questions on charging aspects have come up, and GSMA would like to address to 3GPP for further consideration.","124","13.41","(LI13) - Lawful Interception in Rel-13",11230,"Noted","2015-06-09T16:55:56.040","2015-06-09T16:55:49.143","","","Rel-13","","","LI13","","","","",null,null,null,"RAG 15 Doc 007"]
["SP-150194","LS from SA WG5: Reply LS on Extension of 3GPP Service-Information AVP","SA WG5","David Shrader",46800,"LS in","","","SA WG5 thanks oneM2M TP for their LS on Extension of 3GPP Service-Information AVP. We understand that oneM2M has chosen to reuse the 3GPP offline charging framework and has defined the M2M-Information AVP as a container for oneM2M-specific charging AVPs. SA WG5 supports this re-use and has accommodated other SDOs in this activity. SA WG5 has agreed to a change request to 3GPP TS 32.299 (attached) in which the oneM2M-defined M2M-Information AVP can be optionally included within the 3GPP Service-Information AVP.  An Editor's note has been inserted into the specification as a placeholder to indicate that the specific AVP code will be inserted upon completion of the oneM2M specification.","9","6","General Incoming Liaisons (Liaisons related to specific features will be covered under the feature related agenda item)",10090,"Noted","2015-06-09T16:55:56.040","2015-06-09T16:55:49.143","","","","","","","","","","",null,null,null,"S5-153289"]
["SP-150195","LS from SA WG2: LS on 3GPP Rel-13 MTC features for service capability exposure","SA WG2","Puneet Jain",36283,"LS in","","","The 3GPP System Architecture Working Group 2 (SA WG2) wishes to inform GSMA, OMA and oneM2M of the work done during Release 13 on Machine Type Communications (MTC) features that allows an application to take advantage of service capabilities provided by the 3GPP system. Please note that from an SA WG2 perspective these features are not limited to MTC devices/applications.  In Release 13, SA WG2 has progressed work on stage 2 architecture requirements on the following topics -  - AESE (Architecture Enhancements for Service capability Exposure): As part of this work SA WG2 defined the Service Capability Exposure Function (SCEF) that provides a means to expose the services and capabilities provided by 3GPP network interfaces. In addition, solutions for the following issue were defined - 1) Support for setting up an Application Server (AS) session with required QoS; 2) Support of changing the chargeable party at the session set-up or during the session; 3) Support of 3rd party in","9","6","General Incoming Liaisons (Liaisons related to specific features will be covered under the feature related agenda item)",10110,"Noted","2015-06-09T16:55:56.057","2015-06-09T16:55:49.143","","","","","","AESE, MONTE, GROUPE, HLcom","","","","",null,null,null,"S2-152032"]
["SP-150196","SA WG4 Status Report at TSG SA#68","SA WG4 Chairman","Maurice Pope",648,"report","","","Status Report of SA WG4 activities to TSG SA#68","14","7.4","SA WG4 Report and Questions for Advice",10160,"Noted","2015-06-09T16:55:56.070","2015-06-14T11:57:34.273","","","","","","","","","","","","","","",""]
["SP-150197","CRs to TS 26.346 on 'Enhancements to Multimedia: PSS, MMS, and MBMS Enhancements and Performance Improvements (EMM)' (Release 11 to Release 13)","SA WG4","Maurice Pope",648,"CR Pack","","","26.346 CR0455R1; 26.346 CR0456R1; 26.346 CR0457R1; 26.346 CR0465; 26.346 CR0466; 26.346 CR0472","28","11","Rel-11 CRs",10330,"Approved","2015-06-09T16:55:56.087","2015-06-09T16:55:49.160","","","","","","","","","","","","","","",""]
["SP-150198","CRs to TS 26.346 on 'Multiple TMGIs in SDP (TEI11)' (Release 11 to Release 13)","SA WG4","Maurice Pope",648,"CR Pack","","","26.346 CR0469R4; 26.346 CR0470R2; 26.346 CR0471R2","28","11","Rel-11 CRs",10340,"Approved","2015-06-09T16:55:56.087","2015-06-09T16:55:49.160","","","","","","","","","","","","","","",""]
["SP-150199","CRs to TS 26.114 on 'Codec for Enhanced Voice Services (EVS_codec)' (Release 12)","SA WG4","Maurice Pope",648,"CR Pack","","","26.114 CR0311; 26.114 CR0314R2","33","12.4","(EVS_codec) - Codec for Enhanced Voice Services",10410,"Approved","2015-06-09T16:55:56.103","2015-06-09T16:55:49.160","","","Rel-12","","","EVS_codec","","","","","","","","",""]
["SP-150200","CR to TS 26.442 on 'Codec for Enhanced Voice Services (EVS); ANSI C code (fixed-point) (EVS_codec)' (Release 12)","SA WG4","Maurice Pope",648,"CR Pack","","","26.442 CR0009","33","12.4","(EVS_codec) - Codec for Enhanced Voice Services",10420,"Approved","2015-06-09T16:55:56.117","2015-06-09T16:55:49.160","","","Rel-12","","","EVS_codec","","","","","","","","",""]
["SP-150201","CR to TS 26.443 on 'Codec for Enhanced Voice Services (EVS); ANSI C code (floating-point) (EVS_codec)' (Release 12)","SA WG4","Maurice Pope",648,"CR Pack","","","26.443 CR0005","33","12.4","(EVS_codec) - Codec for Enhanced Voice Services",10430,"Approved","2015-06-09T16:55:56.133","2015-06-09T16:55:49.160","","","Rel-12","","","EVS_codec","","","","","","","","",""]
["SP-150202","CR to TS 26.444 on ‘Update of test vectors for the EVS codec (EVS_codec)' (Release 12)","SA WG4","Maurice Pope",648,"CR Pack","","","26.444 CR0004","33","12.4","(EVS_codec) - Codec for Enhanced Voice Services",10440,"Approved","2015-06-09T16:55:56.147","2015-06-09T16:55:49.160","","","Rel-12","","","EVS_codec","","","","","","","","",""]
["SP-150203","CR to TS 26.445 on ‘Corrections to the Algorithmic Description (EVS_codec)' (Release 12)","SA WG4","Maurice Pope",648,"CR Pack","","","26.445 CR0004R1","33","12.4","(EVS_codec) - Codec for Enhanced Voice Services",10450,"Approved","2015-06-09T16:55:56.147","2015-06-09T16:55:49.177","","","Rel-12","","","EVS_codec","","","","","","","","",""]
["SP-150204","CR to TS 26.447 on 'Corrections to the description of the packet loss concealment algorithm (EVS_codec)' (Release 12)","SA WG4","Maurice Pope",648,"CR Pack","","","26.447 CR0003","33","12.4","(EVS_codec) - Codec for Enhanced Voice Services",10460,"Approved","2015-06-09T16:55:56.163","2015-06-09T16:55:49.177","","","Rel-12","","","EVS_codec","","","","","","","","",""]
["SP-150205","CR to TR 26.952 on 'Inclusion of verification results (EVS_codec)' (Release 12)","SA WG4","Maurice Pope",648,"CR Pack","","","26.952 CR0002R2","33","12.4","(EVS_codec) - Codec for Enhanced Voice Services",10470,"Approved","2015-06-09T16:55:56.180","2015-06-09T16:55:49.177","","","Rel-12","","","EVS_codec","","","","","","","","",""]
["SP-150206","TR 26.923 Study on Media Handling Aspects of IMS-based Telepresence (Release 13) v. 1.0.0","SA WG4","Maurice Pope",648,"TS or TR","","","Abstract of document: This Technical Report provides a study on the media handling aspects of IMS-based telepresence in 3GPP services. This includes the investigation of the following areas: - Media codecs (speech, video, real-time text) for IMS-based telepresence  - Media configuration including session setup and control procedures for IMS-based telepresence, and media provisioning aspects of capability negotiation based on SDP and CLUE protocols, etc. - Set-up and control of the individual media streams between clients including interactivity, such as adding and dropping of media components, as well as end-to-end QoS handling, etc. for IMS-based telepresence - Data transport including usage of RTP / RTCP protocols, RTP profiles, RTP payload formats, RTP mapping, media synchronization, etc. for IMS-based telepresence, e.g., in relation to negotiation and establishment of the CLUE data channel, and exchange of CLUE ADVERTISEMENT and CONFIGURE messages - Requirements and guide","95","13.12","(IMS_TELEP_S4) - Media Handling Aspects of IMS-based Telepresence",10880,"Noted","2015-06-09T16:55:56.197","2015-06-09T16:55:49.177","","","Rel-13","26.923","1.0.0","IMS_TELEP_S4","","","","","","","","",""]
["SP-150207","CR to TS 26.114 on 'Integrating H.265 (HEVC) into 3GPP MTSINP MO (HEVC)' (Release 12)","SA WG4","Maurice Pope",648,"CR Pack","","","26.114 CR0315","70","12.41","(HEVC) - High Efficiency Video Coding",10560,"Approved","2015-06-09T16:55:56.243","2015-06-09T16:55:49.300","","","Rel-12","","","HEVC","","","","","","","","",""]
["SP-150208","CRs to TS 26.346 and TR 26.849 on 'MBMS Improvements (MI, MI-EMO & MI-MooD)' (Release 12 & Release 13)","SA WG4","Maurice Pope",648,"CR Pack","","","26.346 CR0448; 26.346 CR0449; 26.346 CR0450; 26.346 CR0451; 26.346 CR0452; 26.346 CR0453; 26.849 CR0001R1","74","12.45","(MI) - MBMS Improvements",10570,"Approved","2015-06-09T16:55:56.257","2015-06-09T16:55:49.300","","","Rel-12","","","MI","","","","","","","","",""]
["SP-150209","CRs to TS 26.114, TS 26.131, TS 26.132, TS 26.346 on 'Technical Enhancements and Improvements (TEI12)' (Release 12 & Release 13)","SA WG4","Maurice Pope",648,"CR Pack","","","26.114 CR0317R2; 26.114 CR0319R1; 26.131 CR0065R3; 26.132 CR0083R2; 26.346 CR0444R4; 26.346 CR0458R1; 26.346 CR0459R1; 26.346 CR0460R3; 26.346 CR0461R3; 26.346 CR0476R2","81","12.52","(TEI12) - TEI Rel-12",10660,"Approved","2015-06-09T16:55:56.273","2015-06-09T16:55:49.300","","","Rel-12","","","TEI12","","","","","","","","",""]
["SP-150210","CR to TS 26.114 on 'Video Region-of-Interest Signalling (ROI)' (Release 13)","SA WG4","Maurice Pope",648,"CR Pack","","","26.114 CR0318R4","108","13.25","(ROI) - Video Enhancements by Region-of-Interest Information Signalling",11090,"Approved","2015-06-09T16:55:56.273","2015-06-09T16:55:49.300","","","Rel-13","","","ROI","","","","","","","","",""]
["SP-150211","Revised WID on eDASH update for mosaic services (eDASH)","SA WG4","Maurice Pope",648,"WID","","","Objective: The objective of the work item is to address relevant enhancements for DASH-based services in 3GPP services and networks. The work item addresses normative aspects and operational guidelines to address the relevant gaps identified in the conclusions of TR26.938. Specifically, the work item addresses the following objectives: - For Live Services (see clause 6.2 of TR26.938), TS26.247 supports all basic aspects to offer a live service. Additional tools may be considered to optimize efficiency and robustness. MPEG-DASH second edition defines certain tools for this purpose that may be considered to improve latency. In addition, the use of certain HTTP delivery modes may be considered. - For Content Protection (see clause 6.3 of TR26.938), TS 26.247 is agnostic to the DRM that is used. However, neither in TS 26.247 nor in 3GPP file format TS 26.244 there is explicit support for common encryption nor key rotation. Consider adding support for common encryption.","113","13.30","(eDASH) - Enhanced DASH",11100,"Approved","2015-06-09T16:55:56.290","2015-06-09T16:55:49.300","","","Rel-13","","","eDASH","","","","","","","","",""]
["SP-150212","CR to TS 26.244 on 'Adding Quality Metadata Carriage and orientation information in the 3GPP file format (eDASH)' (Release 13)","SA WG4","Maurice Pope",648,"CR Pack","","","26.244 CR0056R1","113","13.30","(eDASH) - Enhanced DASH",11110,"Approved","2015-06-09T16:55:56.303","2015-06-09T16:55:49.317","","","Rel-13","","","eDASH","","","","","","","","",""]
["SP-150213","New BB WID on Media and Quality Aspects of SRVCC Enhancements (SETA-S4)","SA WG4","Maurice Pope",648,"WID","","","Objective: The SA WG4 work is structured as follows: - Identify relevant scenarios, especially with Codec Mode Control from AMR-WB and EVS to AMR-WB in CS and EVS in CS; - Analyse Speech quality aspects and Media handling aspects, based on these scenarios; - Analyse Codec Mode Control before, during and after SRVCC; - Analyse the existing SDP Offer - Answer protocol between CS and IMS during SRVCC; - Clarify the existing Codec Compatibility aspects for SRVCC; - Propose enhancements for media and quality aspects of SRVCC with the aims:  a) to avoid transcoding cases as much as possible; b) to minimize the speech path interruption time during SRVCC; - Support SA WG2 work by SA WG4 expertise in speech quality and media handling; - Identify and update the relevant clauses in TS 26.114 (e.g. clause 12.3.4).","122","13.39","(SETA) - SRVCC Enhancements for Transcoding Avoidance",11130,"Revised","2015-06-09T16:55:56.320","2015-06-09T16:55:49.317","","SP-150361","Rel-13","","","SETA","","","","","","","","",""]
["SP-150214","CR to TS 26.346 on 'Signalling independent Units (TEI13)' (Release 13)","SA WG4","Maurice Pope",648,"CR Pack","","","26.346 CR0464R4","127","13.44","(TEI13) - TEI Rel-13",11430,"Postponed","2015-06-09T16:55:56.337","2015-06-09T16:55:49.317","","","Rel-13","","","TEI13","","","","","","","","",""]
["SP-150215","New WID on Development of super-wideband and fullband P.835 test framework, databases, and performance specification (DESUDAPS)","SA WG4","Maurice Pope",648,"WID","","","Objective: - Define appropriate noise types, levels, and background noise simulation methods for database development. - Develop a suitable P.835 subjective test plan framework, including reference signals and appropriate codec operating modes for training and validation of objective predictors. - Define minimum performance requirements for the objective predictor model handling FB and SWB. - Develop appropriate UE test methods and set SWB and FB performance objectives in the presence of background noise, considering ES 202 396-1 as a background noise simulation method for testing. It is expected that performance requirements will eventually be defined, when terminals supporting FB or SWB are commercially available to provide a quantitative basis for such requirements.","189","16","Proposed New WIDs (not part of an existing feature)",11820,"Approved","2015-06-09T16:55:56.350","2015-06-09T16:55:49.317","","","","","","","","","","","","","","",""]
["SP-150216","SA WG6 Status Report to TSG SA Plenary","SA WG6 Chairman","Andrew Howell",714,"report","","","Status Report of SA WG6 activities to TSG SA#68","16","7.6","SA WG6 Report and Questions for Advice",10180,"Noted","2015-06-09T16:55:56.367","2015-06-09T16:55:49.317","","","","","","","","","","","","","","",""]
["SP-150217","Update to the MCPTT WID","SA WG6","Maurice Pope",648,"WID","","","Changes Deliverable details, Rapporteur and supporting company list.","84","13.1","(MCPTT) - Mission Critical Push-to-Talk over LTE",10720,"Revised","2015-06-09T16:55:56.383","2015-06-11T05:37:05.773","","SP-150356","Rel-13","","","MCPTT","","","","","","","","",""]
["SP-150218","Presentation of TR 23.779 v1.0.0: Study on application architecture to support Mission Critical Push To Talk over LTE (MCPTT) services (Release 13)","SA WG6","Maurice Pope",648,"TS or TR","","","Abstract of the contribution: 3GPP TR 23.779 contains the results of the Stage 2 study and evaluation of possible 3GPP technical system solutions for the Mission Critical Push To Talk over LTE (MCPTT) application.  The TR contains a description of candidate solutions for different functions required for the support of MCPTT service. It also contains clauses that have been used by SA WG6 as a working area for text that will be included in stage 2 TS for MCPTT. Changes since last presentation to TSG SA: This is the first presentation to TSG SA. Conclusions were agreed on the overall architecture for on-network operations. Work on functional model, applicable to both on-network and off-network, has also started. This will be transferred to stage 2 TS and includes initial description of architecture models, identities, functional entities and reference points. Initial information flows were approved for on-network operations (affiliation, floor control, temporary groups formation","84","13.1","(MCPTT) - Mission Critical Push-to-Talk over LTE",10770,"Noted","2015-06-09T16:55:56.383","2015-06-11T05:37:05.773","","","Rel-13","23.779","1.0.0","MCPTT","","","","","","","","",""]
["SP-150219","TR 26.922 Video Telephony Robustness Improvements Extensions; Performance Evaluation (VTRI_EXT) (Release 13) v. 1.0.0","SA WG4","Maurice Pope",648,"TS or TR","","","Abstract of document: The present document reports the study on video telephony robustness improvements extensions in Multimedia Telephony Service for IMS and provides recommendation on their applicability for MTSI video telephony applications. These extensions target Error Robustness (ER) for higher bitrate MTSI video telephony as well as inter-working with WLAN use cases where error resiliency is more important. Retransmission, Forward Error Correction (FEC), and complementary Reference Picture Selection Indication (RPSI) Audio Video Profile Feedback (AVPF) mechanisms are discussed and evaluated. Test conditions and evaluation criteria are defined. The performance of the considered error resilience tools is evaluated under the defined testing conditions taking into account packet loss rate/pattern, end to end delay, bitrate overhead and video smoothness (dropped frames, rendering jitter). Based on the performance results, conclusions are made in terms of recommendations for","116","13.33","(VTRI_EXT) - Video Telephony Robustness Improvements Extensions",11120,"Noted","2015-06-09T16:55:56.430","2015-06-09T16:55:49.440","","","Rel-13","26.922","1.0.0","VTRI_EXT","","","","","","","","",""]
["SP-150220","TSG GERAN Status report to TSG SA#68","TSG GERAN Chairman","Maurice Pope",648,"report","","","Status Report of TSG GERAN activities to TSG SA#68","19","7.9","TSG GERAN report and Questions for Advice",10240,"Noted","2015-06-09T16:55:56.460","2015-06-09T16:55:49.567","","","","","","","","","","","","","","",""]
["SP-150221","SA WG2 Status Report to TSG SA Plenary","SA WG2 Chairman","Frank Mademann",6821,"report","","","Status Report of SA WG2 activities to TSG SA#68","12","7.2","SA WG2 Report and Questions for Advice",10130,"Noted","2015-06-09T16:55:56.477","2015-06-14T11:57:49.030","","","","","","","","","","","","","","",""]
["SP-150222","8 CRs to 23.228 on OMR and TEI10 (Rel-10, Rel-11, Rel-12, Rel-13)","SA WG2","Maurice Pope",648,"CR Pack","","","23.228 CR1123R2; 23.228 CR1124R2; 23.228 CR1125R2; 23.228 CR1126R2; 23.228 CR1117; 23.228 CR1118; 23.228 CR1119; 23.228 CR1120","27","10","Rel-10 CRs (Need to be very well justified!)",10280,"Approved","2015-06-09T16:55:56.493","2015-06-09T16:55:49.567","","","","","","","","","","","","","","",""]
["SP-150223","3 CRs to 23.228 on RAVEL (Rel-11, Rel-12, Rel-13)","SA WG2","Maurice Pope",648,"CR Pack","","","23.228 CR1108; 23.228 CR1109; 23.228 CR1110","28","11","Rel-11 CRs",10310,"Approved","2015-06-09T16:55:56.507","2015-06-09T16:55:49.567","","","","","","","","","","","","","","",""]
["SP-150224","2 CRs to 23.272 on TEI11, eMPS (Rel-11, Rel-12)","SA WG2","Maurice Pope",648,"CR Pack","","","23.272 CR0945; 23.272 CR0946","28","11","Rel-11 CRs",10320,"Approved","2015-06-09T16:55:56.523","2015-06-09T16:55:49.567","","","","","","","","","","","","","","",""]
["SP-150225","2 CRs to 23.228 on IMS_WebRTC (Rel-12, Rel-13)","SA WG2","Maurice Pope",648,"CR Pack","","","23.228 CR1115R1; 23.228 CR1116R1","31","12.2","(IMS_WebRTC) - Web Real Time Communication (WebRTC) Access to IMS",10400,"Approved","2015-06-09T16:55:56.537","2015-06-09T16:55:49.567","","","Rel-12","","","IMS_WebRTC","","","","","","","","",""]
["SP-150226","8 CRs to 23.002, 23.303 on ProSe (Rel-12)","SA WG2","Maurice Pope",648,"CR Pack","","","23.002 CR0282; 23.303 CR0151R3; 23.303 CR0158R1; 23.303 CR0163; 23.303 CR0170R2; 23.303 CR0173R2; 23.303 CR0160R2; 23.303 CR0165R1","43","12.14","(ProSe and FS_ProSe) - Proximity based Services",10480,"Approved","2015-06-09T16:55:56.553","2015-06-09T16:55:49.580","","","Rel-12","","","FS_ProSe, ProSe","","","","","","","","",""]
["SP-150227","4 CRs to 23.468 on GCSE_LTE (Rel-12, Rel-13)","SA WG2","Maurice Pope",648,"CR Pack","","","23.468 CR0058R1; 23.468 CR0059R1; 23.468 CR0063R2; 23.468 CR0064R1","44","12.15","(GCSE_LTE) - Group Communication System Enablers for LTE",10510,"Approved","2015-06-09T16:55:56.570","2015-06-09T16:55:49.580","","","Rel-12","","","GCSE_LTE","","","","","","","","",""]
["SP-150228","2 CRs to 23.682 on MTCe-UEPCOP (Rel-12, Rel-13)","SA WG2","Maurice Pope",648,"CR Pack","","","23.682 CR0101R1; 23.682 CR0102R1","51","12.22","(MTCe and FS_MTCe) - Machine-Type and other mobile data applications Communications Enhancements",10520,"Approved","2015-06-09T16:55:56.587","2015-06-09T16:55:49.580","","","Rel-12","","","FS_MTCe, MTCe","","","","","","","","",""]
["SP-150229","2 CRs to 23.401 on CNO_ULI (Rel-12, Rel-13)","SA WG2","Maurice Pope",648,"CR Pack","","","23.401 CR2860R3; 23.401 CR2861R3","54","12.25","(CNO_ULI) - User Location Information reporting improvements",10540,"Approved","2015-06-09T16:55:56.600","2015-06-09T16:55:49.580","","","Rel-12","","","CNO_ULI","","","","","","","","",""]
["SP-150230","14 CRs to 23.060, 23.203, 23.216, 23.228, 23.237, 23.401 on TEI12 (Rel-12, Rel-13)","SA WG2","Maurice Pope",648,"CR Pack","","","23.060 CR1950R1; 23.060 CR1951R1; 23.401 CR2830R1; 23.401 CR2831R1; 23.203 CR0890R8; 23.203 CR0905R6; 23.228 CR1128R2; 23.228 CR1129R2; 23.401 CR2875R1; 23.401 CR2876R1; 23.203 CR0940R5; 23.203 CR0941R5; 23.216 CR0331R2; 23.237 CR0483R1","81","12.52","(TEI12) - TEI Rel-12",10650,"Approved","2015-06-09T16:55:56.617","2015-06-09T16:55:49.580","","","Rel-12","","","TEI12","","","","","","","","",""]
["SP-150231","1 CR to 23.203 on UPCON (Rel-13)","SA WG2","Maurice Pope",648,"CR Pack","","","23.203 CR0978R2","94","13.11","(UPCON and FS_UPCON) - UserPlane Congestion Management",10870,"Approved","2015-06-09T16:55:56.633","2015-06-09T16:55:49.597","","","Rel-13","","","FS_UPCON, UPCON","","","","","","","","",""]
["SP-150232","2 CRs to 23.203, 23.228 on eWebRTCi (Rel-13)","SA WG2","Maurice Pope",648,"CR Pack","","","23.203 CR0976R3; 23.228 CR1134R2","97","13.14","(eWebRTCi) - Enhancements to WebRTC interoperability",10900,"Approved","2015-06-09T16:55:56.647","2015-06-09T16:55:49.597","","","Rel-13","","","eWebRTCi","","","","","","","","",""]
["SP-150233","6 CRs to 23.303 on eProSe-Ext-SA WG2 (Rel-13)","SA WG2","Maurice Pope",648,"CR Pack","","","23.303 CR0164R1; 23.303 CR0166R1; 23.303 CR0168R2; 23.303 CR0169R2; 23.303 CR0174R1; 23.303 CR0175R2","99","13.16","(ePROSE, PROSE_EXT) - Enhancements to Proximity-based Services",10940,"Approved","2015-06-09T16:55:56.663","2015-06-09T16:55:49.597","","","Rel-13","","","eProSe","","","","","","","","",""]
["SP-150234","5 CRs to 23.060, 23.236, 23.401 on DECOR (Rel-13)","SA WG2","Maurice Pope",648,"CR Pack","","","23.060 CR1953R7; 23.236 CR0051R3; 23.236 CR0053R2; 23.401 CR2837R11; 23.401 CR2864R3","101","13.18","(DÉCOR) - Dedicated Core Networks",10970,"Approved","2015-06-09T16:55:56.680","2015-06-09T16:55:49.597","","","Rel-13","","","DECOR","","","","","","","","",""]
["SP-150235","10 CRs to 23.002, 23.401, 23.682 on AESE (Rel-13)","SA WG2","Maurice Pope",648,"CR Pack","","","23.002 CR0284R2; 23.203 CR0975R2; 23.401 CR2872R2; 23.682 CR0109R1; 23.682 CR0113R3; 23.682 CR0114R2; 23.682 CR0116R2; 23.682 CR0117R1; 23.682 CR0118R3; 23.682 CR0119R4","103","13.20","(AESE) - Architecture Enhancements for Service Capability Exposure",11020,"Approved","2015-06-09T16:55:56.693","2015-06-09T16:55:49.597","","","Rel-13","","","AESE","","","","","","","","",""]
["SP-150236","14 CRs to 23.002, 23.060, 23.401, 23.682 on MONTE (Rel-13)","SA WG2","Maurice Pope",648,"CR Pack","","","23.002 CR0283R2; 23.060 CR1960R2; 23.060 CR1961R5; 23.060 CR1968R2; 23.401 CR2850R2; 23.401 CR2851R2; 23.401 CR2871R2; 23.682 CR0093R6; 23.682 CR0096R2; 23.682 CR0097R5; 23.682 CR0099R1; 23.682 CR0100R4; 23.682 CR0104R2; 23.682 CR0107R5","104","13.21","(MONTE) - Monitoring Enhancements",11040,"Partially approved","2015-06-09T16:55:56.710","2015-06-09T16:55:49.597","","","Rel-13","","","MONTE","","","","","","","","",""]
["SP-150237","9 CRs to 23.060, 23.401, 23.682 on GROUPE (Rel-13)","SA WG2","Maurice Pope",648,"CR Pack","","","23.060 CR1956R2; 23.060 CR1967R3; 23.060 CR1971R2; 23.401 CR2843R2; 23.401 CR2853; 23.401 CR2866R3; 23.401 CR2877R1; 23.682 CR0094R6; 23.682 CR0095","105","13.22","(GROUPE) - Group based Enhancements",11060,"Approved","2015-06-09T16:55:56.727","2015-06-09T16:55:49.613","","","Rel-13","","","GROUPE","","","","","","","","",""]
["SP-150238","5 CRs to 23.060, 23.401, 23.682 on HLcom (Rel-13)","SA WG2","Maurice Pope",648,"CR Pack","","","23.060 CR1965R3; 23.401 CR2862R3; 23.682 CR0106R3; 23.682 CR0108R2; 23.682 CR0115R4","189","16","Proposed New WIDs (not part of an existing feature)",11810,"Approved","2015-06-09T16:55:56.757","2015-06-09T16:55:49.613","","","","","","","","","","","","","","",""]
["SP-150239","11 CRs to various specifications on TEI13 (Rel-13)","SA WG2","Maurice Pope",648,"CR Pack","","","23.060 CR1893R5; 23.203 CR0977R1; 23.216 CR0332R2; 23.246 CR0392R1; 23.272 CR0939R6; 23.401 CR2865; 23.402 CR1360R1; 23.402 CR1366R2; 23.237 CR0481R1; 23.292 CR0228R1; 23.401 CR2857R1","127","13.44","(TEI13) - TEI Rel-13",11440,"Approved","2015-06-09T16:55:56.773","2015-06-09T16:55:49.613","","","Rel-13","","","TEI13","","","","","","","","",""]
["SP-150240","Presentation of TR 23.797 version 1.0.0: Study on architecture enhancements to support Isolated E-UTRAN Operation for Public Safety (Release 13)","SA WG2","Maurice Pope",648,"TS or TR","","","Abstract of document: The report TR 23.797 studies and evaluates architecture enhancements to support operation of an E-UTRAN formed by one or more eNBs which have been deployed without (i.e. Nomadic) or have lost backhaul communications to normal operator core network. Changes since last presentation to SA: This is the first time TR 23.797 has been presented for information. This study has been completed and a conclusion has been reached. The agreed solution requires further work from SA WG3 which is being carried out in their study item (FS_IOPS_Sec). The solution chosen by SA WG3 may possibly require alignment of the architecture enhancements recommended in this TR, including the appropriate AuC functions needed for security/authentication. An LS has been sent to SA WG1 asking whether Public Safety UEs can be allocated with AC 11 or 15 for the IOPS PLMN. If this approach, to preventing access by non Public Safety UEs, is not acceptable to SA WG1 the existing means of preve","85","13.2","(IOPS, FS_IOPS and FS_IOPS_St2) - Isolated E-UTRAN Operation for Public Safety (including FS phase)",10790,"Approved","2015-06-09T16:55:56.787","2015-06-14T11:58:01.557","","","Rel-13","23.797","1.0.0","FS_IOPS, IOPS, FS_IOPS_St2","","","","","","","","",""]
["SP-150241","Presentation of TR 23.718 version 1.0.0: Architecture Enhancement for Flexible Mobile Service Steering; (Release 13)","SA WG2","Maurice Pope",648,"TS or TR","","","Abstract of document: TR 23.718 is the technical report of Flexible Mobile Service Steering (FS_FMSS). The present document studies and evaluates architectural enhancements required for 3GPP systems to provide flexible mobile service steering policies as per the service requirements defined in TS 22.101, clause 30. Changes since last presentation: This is the first presentation.  Outstanding Issues: No normative work has been done yet and such work is expected during the exception time of R13. Contentious Issues: None","92","13.9","(FMSS and FS_FMSS) - Flexible Mobile Service Steering",10860,"Noted","2015-06-09T16:55:56.820","2015-06-14T11:58:03.897","","","Rel-13","23.718","1.0.0","FS_FMSS, FMSS","","","","","","","","",""]
["SP-150242","Presentation of TR 23.861 version 2.0.0: Network based IP flow mobility (Release 13)","SA WG2","Maurice Pope",648,"TS or TR","","","Abstract of document: Network-based IP Flow Mobility Support between 3GPP and Trusted/Untrusted WLAN accesses. Changes since last presentation to TSG Meeting #66: - Completed the study and resolved all the key issues to define the network-based IP flow mobility functions between 3GPP access and WLAN access based on trusted GTP-based S2a and untrusted S2b. The scope of the work is based on the use-cases, the service requirements and the conclusions as captured in TR 23.861. Outstanding Issues: None Contentious Issues: None","102","13.19","(NBIFOM) - IP Flow Mobility support for S2a and S2b Interfaces",11000,"Approved","2015-06-09T16:55:56.850","2015-06-14T11:58:05.457","","","Rel-13","23.861","2.0.0","NBIFOM","","","","","","","","",""]
["SP-150243","Presentation of TR 23.708 version 2.0.0: Architecture Enhancements for Service Capability Exposure (Release 13)","SA WG2","Maurice Pope",648,"TS or TR","","","Abstract of document: The TR 23.708 studies and evaluates architecture enhancements for a service capability exposure framework wherein 3GPP system provided service capabilities are exposed via one or more standardized APIs, e.g. the OMA-API(s). As part of this work it will be identified how the APIs and the 3GPP system functionality act together to expose 3GPP service capabilities. The definition of APIs is out of scope of this work item. The present document also defines the architectural enhancements for new service capabilities and services (based on the Stage 1 SEES normative requirements) that are exposed via the service capability exposure framework as per TS 22.101, clause 29.2 and TS 22.115, clause 5.1.3. Changes since last presentation to SA: This is second time TR 23.708 is presented to TSG SA.  Conclusions as stated in TR 23.708, clause 8 were agreed and are listed below:  - For key issue 1 - Service Capability Exposure Framework, it is recommended that the soluti","103","13.20","(AESE) - Architecture Enhancements for Service Capability Exposure",11010,"Approved","2015-06-09T16:55:56.897","2015-06-14T11:58:06.317","","","Rel-13","23.708","2.0.0","AESE","","","","","","","","",""]
["SP-150244","Presentation of TR 23.769 version 2.0.0: Group based Enhancements (Release 13)","SA WG2","Maurice Pope",648,"TS or TR","","","Abstract of document: The TR 23.769 studies and evaluates architectural enhancements for group based enhancements (GROUPE). System improvements for GROUPE include following key issues: - Key issue 1: Message delivery to a group of devices - Key issue 2: Selection of delivery mechanisms for messaging to a group - Key issue 3: Group based Policy Control - Key issue 4: Group-specific NAS Level Congestion Control - Key issue 5: Group based addressing and identifiers In Rel-13 the work is prioritized on key issue 1, key issue 4 and key issue 5. Key issue 5 is limited to only address the problem of key issue 1 and key issue 4. Focusing on the above prioritized key issues, the TR has concluded by selecting the solution for the basis of normative work. Changes since last presentation to SA: TR is 100% completed and any future developments will be reflected in the normative work. Conclusion as stated in TR 23.769 was agreed on the above prioritized key issues as below: - For the Key I","105","13.22","(GROUPE) - Group based Enhancements",11050,"Approved","2015-06-09T16:55:56.927","2015-06-14T11:58:07.173","","","Rel-13","23.769","2.0.0","GROUPE","","","","","","","","",""]
["SP-150245","Presentation of TR 23.709 version 2.0.0: Study on Optimizations to Support High Latency Communications; Stage 2 (Release 13)","SA WG2","Maurice Pope",648,"TS or TR","","","Abstract of document: The TR 23.709 studies and evaluates architecture enhancements to support applications that communicate with devices that are not reachable for a long period over the 3GPP IP connectivity and being able to support large number of such devices in the system without negatively affecting the system performance. Changes since last presentation to SA: The study has been completed. Outstanding Issues: None. Contentious Issues: None.","160","15.2.4","(FS_HLCom) - Study on Optimizations to Support High Latency Communications",11530,"Approved","2015-06-09T16:55:56.960","2015-06-14T11:58:08.047","","","Rel-13","23.709","2.0.0","FS_HLcom","","","","","","","","",""]
["SP-150246","Presentation of TR 23.771 version 1.0.0: Study on system impacts of IMS emergency sessions over WLAN (Release 13)","SA WG2","Maurice Pope",648,"TS or TR","","","Abstract of document: TR 23.771 studies the support of Emergency services over WLAN ('FS_SEW Study Item). This study is divided in 2 phases where the phase 1 considers simpler deployments cases such as: - support an emergency session only in case of 'Valid' UEs as in the case 1 in § 4.3.12.1 of 23.401: the support of emergency session is only studied for UEs which (a) have valid credentials to access EPC over WLAN and (b) are authorized to connect to EPC over WLAN in the location where they initiate an emergency session. - Only existing location determination mechanisms are considered in this phase. - No Roaming cases (user not in his / her home country). - No Support of session continuity of emergency sessions at inter-access mobility. Changes since last presentation: This is the first presentation. The study for phase 1 has been carried out and conclusions made. A spin-off WID ('SEW1') is also proposed for approval at SA #67 in order to work on the corresponding normative i","176","15.2.20","(FS_SEW) - Study on the Support of Emergency services over WLAN",11570,"Noted","2015-06-09T16:55:56.990","2015-06-14T11:58:08.890","","","Rel-13","23.771","1.0.0","FS_SEW","","","","","","","","",""]
["SP-150247","Presentation of TR 23.770 version 1.0.0: Study on System Impacts of Extended DRX Cycle for Power Consumption Optimization; (Release 13)","SA WG2","Maurice Pope",648,"TS or TR","","","Abstract of document: The TR 23.770 studies the core network and NAS impacts in UE of extending DRX cycle for both idle mode and connected mode, solutions in the core network to support it, and interactions between GERAN/RAN and Core Network. The main goal is to identify issues of extending DRX for idle mode and connected more and document potential solutions and conclude on which feasible solutions would be adopted in core network (pending work in RAN regarding extension of DRX cycle). No connected mode mobility enhancements for extended C-DRX are considered in this document, i.e., if a UE using extended C-DRX moves to a different cell, current connected mode mobility procedures apply. Changes since last presentation to TSG SA: This is the first time TR 23.770 is presented. A list of issues and solutions for each issue have been captured for both extended idle mode DRX and extended connected mode DRX. It was concluded to extend DRX cycle for idle mode beyond 10.24 seconds. T","157","15.2.1","(FS_eDRX) - Feasibility study on Extended DRX cycle for Power Consumption Optimization",11480,"Noted","2015-06-09T16:55:57.037","2015-06-14T11:58:09.717","","","Rel-13","23.770","1.0.0","FS_eDRX","","","","","","","","",""]
["SP-150248","Updated WID for Isolated E-UTRAN Operation for Public Safety","SA WG2","Maurice Pope",648,"WID","","","Objective: The SA WG2 objectives are as follows: 1. Document in an informative annex in the relevant specification (TS 23.401) the implementation and deployment guidelines for 'operation of public safety networks in the no backhaul (to Macro EPC) scenario' using a Local EPC approach as identified in the Stage 2 Feature Study (TR 23.797). No stage-3 work is expected from the SA WG2 part of the work item.","85","13.2","(IOPS, FS_IOPS and FS_IOPS_St2) - Isolated E-UTRAN Operation for Public Safety (including FS phase)",10800,"Revised","2015-06-09T16:55:57.070","2015-06-09T16:55:50.563","","SP-150358","Rel-13","","","FS_IOPS, IOPS, FS_IOPS_St2","","","","","","","","",""]
["SP-150249","Updated WID: Dedicated Core Networks (DECOR)","SA WG2","Maurice Pope",648,"WID","","","Objective: The objective of this work item is to enable the deployment of dedicated core networks where each dedicated core network is dedicated to UEs sharing the same characteristics. The specific dedicated core network that serves a UE is selected based on subscription information and operator configuration, without requiring the UEs to be modified. A dedicated core network consists of a set of MMEs, S4-SGSNs, SGWs and PGWs. The objective of the WID includes studying and creating solutions for the following: - Defining the subscription information and configuration used to determine the selection of the specific dedicated core network that shall serve the UE. - Enable the initial allocation of serving MMEs or SGSNs from the dedicated network selected for the UE and maintaining the UE's association with the selected dedicated network during MME/SGSN change. - Enable the allocation/reallocation of serving SGW and PGW from the dedicated network selected for serving the UE.  -","101","13.18","(DÉCOR) - Dedicated Core Networks",10960,"Approved","2015-06-09T16:55:57.083","2015-06-09T16:55:50.563","","","Rel-13","","","DECOR","","","","","","","","",""]
["SP-150250","Revised WID: IP Flow Mobility support for S2a and S2b Interfaces (NBIFOM)","SA WG2","Maurice Pope",648,"WID","","","Objective: The objective of this work item is to define the IFOM functionality for GTP-based S2a and S2b over WLAN based on the use-cases, the service requirements and the NBIFOM Rel-13 conclusions as captured in TR 23.861. It is assumed that - the UE supports dual radio for 3GPP and WLAN access simultaneously","102","13.19","(NBIFOM) - IP Flow Mobility support for S2a and S2b Interfaces",10990,"Approved","2015-06-09T16:55:57.117","2015-06-09T16:55:50.563","","","Rel-13","","","NBIFOM","","","","","","","","",""]
["SP-150251","Update to the SID on Feasibility study on the Support of Emergency services over WLAN (FS_SEW)","SA WG2","Maurice Pope",648,"WID","","","Objective: To study the mechanisms needed to support IMS Emergency sessions over WLAN (both in the Trusted -S2a - and in the untrusted -S2b- cases).  The study will be split up into 2 phases. If deemed appropriate, topics studied (and solutions agreed) in phase 1 can be selected to be moved to normative work (with an associated WID) before the phase 2 starts and the study concludes. The study will define working assumptions as to what requirements need to be addressed. Topics to be studied in phase 1 are: - Providing access to EPC over WLAN in order to support an emergency session only in case of 'Valid' UEs as in the case 1 in § 4.3.12.1 of 23.401: the support of emergency session is only studied for UEs which (a) have valid credentials to access EPC over WLAN and (b) are authorized to connect to EPC over WLAN in the location where they initiate an emergency session - Providing Location information (in particular for untrusted WLAN). Only existing location determination mech","176","15.2.20","(FS_SEW) - Study on the Support of Emergency services over WLAN",11560,"Approved","2015-06-09T16:55:57.130","2015-06-09T16:55:50.563","","","Rel-13","","","FS_SEW","","","","","","","","",""]
["SP-150252","New WID on Optimizations to Support High Latency Communications","SA WG2","Maurice Pope",648,"WID","","","Objective: The objective of this work item is to specify enhancements for applications that communicate with devices that are not reachable for a long period over the 3GPP IP connectivity and being able to support large number of such devices in the system without negatively affecting the system performance. In addressing the above, the following problem has been addressed in TR 23.709: - Downlink access for devices that are not reachable for a long period and the problems associated with such devices (e.g. packet discard when the UE sleeps, frequent retransmissions, load on the CN network, waste of radio resources and UE power when the network unnecessarily conveys retransmit packets, etc). This work may propose and evaluate enhancements to the 3GPP system documented in the TR 23.709 or make normative updates to the 3GPP system as concluded in the TR 23.709. Depending on conclusions, the study may also propose 3GPP enablers to be used by the service layer e.g. defined by oth","189","16","Proposed New WIDs (not part of an existing feature)",11780,"Approved","2015-06-09T16:55:57.147","2015-06-09T16:55:50.580","","","","","","","","","","","","","","",""]
["SP-150253","New WID on Support of Emergency services over WLAN - Phase 1","SA WG2","Maurice Pope",648,"WID","","","Objective: Objective of this feature is to specify a solution for the Support of Emergency calls over WLAN based on conclusions reached in TR 23.771 for the phase 1 of the FS_SEW study (Study on the Support of Emergency services over WLAN). This WID will consider the following simple deployment case: - support an emergency session only in case of 'Valid' UEs as in the case 1 in § 4.3.12.1 of 23.401: the support of emergency session is only addressed for UEs which (a) have valid credentials to access EPC over WLAN and (b) are authorized to connect to EPC over WLAN in the location where they initiate an emergency session.  - Only existing location determination mechanisms are considered in this phase. - No Roaming cases (user not in his / her home country). - No Support of session continuity of emergency sessions at inter-access mobility.  - No solutions that imply specification activities in other SDO(s) SA WG1 and GSMA will be notified on the subset of requirements within 22.","189","16","Proposed New WIDs (not part of an existing feature)",11790,"Approved","2015-06-09T16:55:57.177","2015-06-09T16:55:50.580","","","","","","","","","","","","","","",""]
["SP-150254","New Work Item on Extended DRX cycle for Power Consumption Optimization","SA WG2","Maurice Pope",648,"WID","","","Objective: Objective is to specify the solutions to the identified issues as captured in the conclusions of TR 23.770 to extend the DRX cycle in idle for GERAN, UTRAN and E-UTRAN. The specified solutions will reflect the agreements performed in GERAN/RAN groups, including the maximum length of the DRX cycle for idle mode.  Solutions are to be specified for the following identified issues for extending idle mode DRX cycle up to and beyond 10.24 seconds: - Support NAS-protocol extensions to enable extended DRX cycle. There needs to be coordination between UE and Core Network (SGSN/MME) for use of extended DRX. - Paging strategy in CN that fits the needs of the extended DRX cycle and normal DRX cycle. - Handling of MT SMS, e.g. avoiding retransmissions for long DRX cycles. - Impact in S/P-GW retransmissions when handling Network originated control plane procedure. - Interaction between eDRX and PSM (Power Saving Mode) in UE and MME/SGSN procedures.  - MT Location services suppor","189","16","Proposed New WIDs (not part of an existing feature)",11800,"Revised","2015-06-09T16:55:57.193","2015-06-09T16:55:50.580","","SP-150369","","","","","","","","","","","","",""]
["SP-150255","New Study on S8 Home Routing Architecture for VoLTE","SA WG2","Maurice Pope",648,"WID","","","Objective: This study aims to identify the specification changes needed to enable S8HR as a routing architecture for VoLTE.  The following key issues (non exhaustive-list) will be part of the SA WG2 scope of the study item: 1) Regulatory requirements  S8HR roaming architecture needs to meet all the current regulatory requirements applicable to voice roaming, specifically: - Authenticated/unauthenticated emergency calls shall be supported as in circuit switched voice today. - When a non UE detectable IMS Emergency call is carried, over the IMS APN, back to the HPLMN the P-CSCF (in the HPLMN) needs to be capable of deciding the subsequent action. 2) Voice call continuity - Study impacts on SRVCC for the S8HR roaming scenarios required by GSMA. 3) Coexistence of LBO and S8HR roaming architectures - An operator may need to support both LBO and S8HR roaming architecture options for VoLTE roaming with different operators, on the basis of bilateral agreement and depending on the cap","190","17","Proposed New Study Items (SIDs)",11840,"Approved","2015-06-09T16:55:57.210","2015-06-09T16:55:50.580","","","","","","","","","","","","","","",""]
["SP-150256","SA WG2 Exception Sheet for MCPTT","SA WG2","Maurice Pope",648,"other","","","Expected Completion Date: SA#69 (September 2015) Service(s) impacted: MCPTT Specification(s) affected: To Be Determined Task(s) within work which are not complete: The exception is to address any potential features/enhancements for which SA WG6 may identify requirements until SA WG2#110 or SA WG2#110ah, which can reasonably be finalized with about 2 TUs during SA WG2#110 and about 3 TUs during SA WG2#110ah. Consequences if not included in Release 13: MCPTT application cannot use EPS and IMS features/functionality other than available without any MCPTT exception.  Abstract of document: SA WG2 Exception sheet for the MCPTT feature. Contentious Issues: None","84","13.1","(MCPTT) - Mission Critical Push-to-Talk over LTE",10680,"Approved","2015-06-09T16:55:57.240","2015-06-09T16:55:50.580","","","Rel-13","","","MCPTT","","","","","","","","",""]
["SP-150257","Rel-13 Work Item Exception for IOPS","SA WG2","Maurice Pope",648,"other","","","Expected Completion Date: SA#69 (September 2015) Service(s) impacted: IOPS Service Specification(s) affected: TS 23.401 Task(s) within work which are not complete: Document in an informative annex in the relevant specification (TS 23.401) the implementation and deployment guidelines for 'operation of public safety networks in the no backhaul (to Macro EPC) scenario' using a Local EPC approach as identified in the Stage 2 Feature Study (TR 23.797).  No stage-3 work is expected from the SA WG2 part of the work item.  Resource Estimate: one small/medium CR to TS 23.401  Alignment of the Stage 2 specification (TS 23.401) may be required based on feedback from SA WG3 following the conclusions of their IOPS Security study (TR 33.897).  Consequences if not included in Release 13: A standardised approach to supporting Public Safety networks, in the event that the backhaul to the EPC is lost, will not be supported by 3GPP.  Abstract of document: Exception sheet for Rel-13 Stage 2 norm","85","13.2","(IOPS, FS_IOPS and FS_IOPS_St2) - Isolated E-UTRAN Operation for Public Safety (including FS phase)",10820,"Revised","2015-06-09T16:55:57.257","2015-06-09T16:55:50.580","","SP-150359","Rel-13","","","FS_IOPS, IOPS, FS_IOPS_St2","","","","","","","","",""]
["SP-150258","Rel-13 Work Item Exception for FMSS","SA WG2","Maurice Pope",648,"other","","","Expected Completion Date: September, 2015 Service(s) impacted: Service traffic steering in (S)Gi-LAN Specification(s) affected: TS 23.203 Policy and charging control architecture  Task(s) within work which are not complete: It is expected for 4 additional time unites to complete the following in Stage 2: traffic steering architecture, extension of PCEF and TDF to support traffic steering, a new functional entity Traffic Steering Support Function (TSSF), enhancement of Gx & Sd interface, a new reference point (St) from PCRF to Traffic Steering Support Function, procedures for traffic steering policy provision over St, semantics of steering policy Consequences if not included in Release 13: If this feature is not completed, there will be lack of capability in 3GPP to support flexible mobile service steering in (S)Gi-LAN.   Abstract of document: At SA WG2#109, conclusions for Flexible Mobile Service Steering (FMSS) have been reached to move to normative work in Rel-13 timeframe.","92","13.9","(FMSS and FS_FMSS) - Flexible Mobile Service Steering",10850,"Approved","2015-06-09T16:55:57.273","2015-06-09T16:55:50.597","","","Rel-13","","","FS_FMSS, FMSS","","","","","","","","",""]
["SP-150259","Rel-13 Work Item Exception for eWebRTCi","SA WG2","Maurice Pope",648,"other","","","Expected Completion Date: Initially planned as SA#68 (June 2015). Exception requested for SA#69 (September 2015). Service(s) impacted: Enhancements of WebRTC interworking with IMS. Specification(s) affected: 23.228 + 23.203 Task(s) within work which are not complete: Work on 'Minimize the need for bearer level protocol conversion when supporting WebRTC media capabilities between WebRTC IMS clients without the need to convert to/from IMS protocols' Consequences if not included in Release 13: The feature 'Minimize the need for bearer level protocol conversion when supporting WebRTC media capabilities between WebRTC IMS clients without the need to convert to/from IMS protocols' cannot be supported.  Abstract of document: Out of the features that have been studied by SA WG2, following lead to impacts to Rel13 normative specifications: - WebRTC support of IMS subscriptions corresponding to users managed by third parties: A 23.228 clarification CR is presented to SA#68 and complete","97","13.14","(eWebRTCi) - Enhancements to WebRTC interoperability",10890,"Approved","2015-06-09T16:55:57.287","2015-06-09T16:55:50.597","","","Rel-13","","","eWebRTCi","","","","","","","","",""]
["SP-150260","Rel-13 Work Item Exception for eProSe-Ext-SA2","SA WG2","Maurice Pope",648,"other","","","Expected Completion Date: September 2015 (SA#69) Service(s) impacted: Proximity-based services Specification(s) affected: TS 23.303, TS 23.002 Task(s) within work which are not complete: The preliminary study phase during which solutions have been studied and documented in TR 23.713 with a set of conclusions for some of the topics, and some open issues for others. It is expected that the time budget required will be 7 Time Units in the next plenary cycle.  SA WG2 will need to:  Complete the normative phase for concluded topics:  - Open discovery enhancements Complete study and (if needed) normative phase for:  - ProSe direct discovery for Public Safety use - ProSe UE-Network relay procedures - ProSe Direct One-to-one communication - ProSe Priority/QoS - Proximity estimation Additional items in the work item that are not in the list above and have not had their normative work completed already will not be pursued any further  Consequences if not included in Release 13: Critica","99","13.16","(ePROSE, PROSE_EXT) - Enhancements to Proximity-based Services",10930,"Approved","2015-06-09T16:55:57.317","2015-06-09T16:55:50.597","","","Rel-13","","","eProSe","","","","","","","","",""]
["SP-150261","Rel-13 Work Item Exception for NBIFOM","SA WG2","Maurice Pope",648,"other","","","Expected Completion Date: September, 2015 Service(s) impacted: None identified Specification(s) affected: TS 23.203, TS 23.xxx Task(s) within work which are not complete:  It is expected for 3 additional time units to complete the following set of CRs by next SA plenary cycle: - Complete the description of the GERAN/UTRAN related procedures - Finalize the co-existence of NBIFOM routing rules with ANDSF and RAN rules,  - Finalize the Loss of access handling  - Create the description of the PCC enhancements Consequences if not included in Release 13: If this feature is not completed, there will be lack of capability in 3GPP to allow offloading specific IP flow to WLAN access.  Abstract of document: The objective of this work item extension is to specify the IP flow mobility functionality for GTP-based S2a and S2b over WLAN based on the NBIFOM Rel-13 conclusions as captured in TR 23.861.  Contentious Issues: None identified.","102","13.19","(NBIFOM) - IP Flow Mobility support for S2a and S2b Interfaces",10980,"Approved","2015-06-09T16:55:57.333","2015-06-09T16:55:50.597","","","Rel-13","","","NBIFOM","","","","","","","","",""]
["SP-150262","Rel-13 Work Item Exception for HLcom","SA WG2","Maurice Pope",648,"other","","","Expected Completion Date: SA#69 September 2015 Service(s) impacted: High latency communication Specification(s) affected: TS 23.682, TS 23.401, TS 23.060 Task(s) within work which are not complete: Update the High latency feature in TS 23.401, TS 23.060 and TS 23.682 with one additional power saving function when the eDRX feature has been completed.  Consequences if not included in Release 13 The High latency feature will not be supported for UEs using the eDRX function.  Abstract of document: SA WG2 Exception sheet for the HLCOM feature.  Contentious Issues: None","189","16","Proposed New WIDs (not part of an existing feature)",11760,"Approved","2015-06-09T16:55:57.350","2015-06-09T16:55:50.610","","","","","","","","","","","","","","",""]
["SP-150263","Rel-13 Work Item Exception for eDRX","SA WG2","Maurice Pope",648,"other","","","Expected Completion Date: September 2015 (SA plenary #69) Service(s) impacted: Delay tolerant data services Specification(s) affected: 23.401 General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access 23.060 General Packet Radio Service (GPRS); Service description; Stage 2 23.682 Architecture enhancements to facilitate communications with packet data networks and applications 23.271 Support for MT Location services for UEs in extended DRX 23.272 Support for MT SMS for UE in extended DRX Task(s) within work which are not complete: - Negotiation of extended I-DRX between UE and network,  - Handling of paging strategy,  - Handling of mobile terminated SMS and location services,  - Handling of GTP-C retransmissions,  - Interaction between PSM and extended DRX. Consequences if not included in Release 13: Particularly for machine type communications (MTC), for applications requiring mobile terminated data with some delay","189","16","Proposed New WIDs (not part of an existing feature)",11740,"Approved","2015-06-09T16:55:57.367","2015-06-09T16:55:50.610","","SP-150352","","","","","","","","","","","","",""]
["SP-150264","Rel-13 Work Item Exception for SEW1","SA WG2","Maurice Pope",648,"other","","","Expected Completion Date: SA#69 (September 2015) Service(s) impacted: Emergency services over WLAN Specification(s) affected: 23.402 , 23.167, 23.271, 23.203, 23.228 Task(s) within work which are not complete: No work has been carried out yet on this WID that is presented for approval at SA plenary Refer to the section on Abstract of document for an assessment of the expected work. Consequences if not included in Release 13: Emergency services over WLAN not supported  Abstract of document: This is the normative WID (SEW1) spinned-off from the phase 1 of FS_SEW. FS_SEW phase 1 has concluded and is now over (FS_SEW will continue with a phase 2 that would run as part of Rel-14, once this SEW1 WID has been completed). FS_SEW phase 1 considers simpler deployments cases such as: - support an emergency session only in case of 'Valid' UEs as in the case 1 in § 4.3.12.1 of 23.401: the support of emergency session is only studied for UEs which (a) have valid credentials to access EPC o","189","16","Proposed New WIDs (not part of an existing feature)",11770,"Approved","2015-06-09T16:55:57.397","2015-06-09T16:55:50.610","","","","","","","","","","","","","","",""]
["SP-150265","LS from SA WG2: Reply LS on VoLTE Roaming Architecture","SA WG2","Motohiro Abe",57779,"LS in","","","SA WG2 would like to thank GSMA PSMC and GSMA RAG for their LS on VoLTE Roaming architecture.  SA WG2 would like to inform the above groups that SA WG2 has approved a new study item whose aim is to identify the architecture and functionality needed to enable S8HR as a roaming architecture for VoLTE. SA WG2 hopes to complete this study item by March 2016.","124","13.41","(LI13) - Lawful Interception in Rel-13",11240,"Noted","2015-06-09T16:55:57.413","2015-06-09T16:55:50.610","","","Rel-13","","","LI13","","","","",null,null,null,"S2-152117"]
["SP-150266","SA WG1 Report to TSG SA#68","SA WG1 Chairman","Toon Norp",8605,"report","","","Status Report of SA WG1 activities to TSG SA#68","11","7.1","SA WG1 Report and Questions for Advice",10120,"Noted","2015-06-09T16:55:57.427","2015-06-09T16:55:50.627","","","","","","","","","","","","","","",""]
["SP-150267","Stage 1 CRs on ACDC-ST1","SA WG1","Maurice Pope",648,"CR Pack","","","22.011 CR0214R2","90","13.7","(ACDC and FS_ACDC) - Application specific Congestion control for Data Communication (including FS phase)",10840,"Approved","2015-06-09T16:55:57.460","2015-06-09T16:55:50.627","","","Rel-13","","","FS_ACDC, ACDC","","","","","","","","",""]
["SP-150268","Stage 1 CRs on IMS_WebRTC","SA WG1","Maurice Pope",648,"CR Pack","","","22.228 CR0211R1; 22.228 CR0212R1","31","12.2","(IMS_WebRTC) - Web Real Time Communication (WebRTC) Access to IMS",10390,"Approved","2015-06-09T16:55:57.473","2015-06-09T16:55:50.627","","","Rel-12","","","IMS_WebRTC","","","","","","","","",""]
["SP-150269","Updated WID on MCPTT","SA WG1","Maurice Pope",648,"WID","","","Updates Rapporteur and adds to Justification: - Ministry of Public Safety and Security (MPSS) of , Korea has defined the functional requirements which include MCPTT components such as 'Compiling of Group Call', 'Listening Plural Talk Group' and 'Network Interoperability' for Korean Public Safety Broadband Network (PSBN). Telecommunications Technology Association has opened the work items on LTE for Public Safety.","84","13.1","(MCPTT) - Mission Critical Push-to-Talk over LTE",10780,"Merged","2015-06-09T16:55:57.507","2015-06-09T16:55:50.627","","","Rel-13","","","MCPTT","","","","","","","","",""]
["SP-150270","Stage 1 CRs on Multimedia Priority Service (MPS) Modifications (MPS_Mods)","SA WG1","Maurice Pope",648,"WID","","","22.153 CR0019R3; 22.153 CR0020R2; 22.153 CR0021R2; 22.011 CR0210R2; 22.011 CR0211R2; 22.011 CR0212R2; 22.011 CR0213R2","131","14.2","(MPS_Mods) Multimedia Priority Service Modifications",11450,"Approved","2015-06-09T16:55:57.553","2015-06-09T16:55:50.627","","","Rel-14","","","MPS_Mods","","","","","","","","",""]
["SP-150271","Stage 1 CRs on Enhancing Location Capabilities for Indoor and Outdoor Emergency Communications (ELIOT)","SA WG1","Maurice Pope",648,"CR Pack","","","22.071 CR0080R2; 22.071 CR0081R1","132","14.3","(ELIOT) Enhancing Location Capabilities for Indoor and Outdoor Emergency Communications",11460,"Approved","2015-06-09T16:55:57.567","2015-06-09T16:55:50.643","","","Rel-14","","","ELIOT","","","","","","","","",""]
["SP-150272","Stage 1 CRs on Enhancements to Domain Selection between VoLTE and CDMA CS (eDSVCC)","SA WG1","Maurice Pope",648,"CR Pack","","","22.101 CR0499R3","133","14.4","(eDSVCC) Enhancements to Domain Selection between VoLTE and CDMA CS",11470,"Approved","2015-06-09T16:55:57.600","2015-06-09T16:55:50.643","","","Rel-14","","","eDSVCC","","","","","","","","",""]
["SP-150273","New WID on Control of Applications when Third party Servers encounter difficulties (CATS)","SA WG1","Maurice Pope",648,"WID","","","Objective: The objective is to specify following service requirements to control traffic from UE to the affected application on a third party server or the third party server itself while not affecting other traffic. Also, following service requirements for the above functionality will be provided. ? Identification of the application or its associated traffic according to operator policy ? Granularity of control ? Co-existence with other access control mechanism(e.g. ACDC) ? Information(such as subscription profile of MNO or third party) used to control ? Charging and Security aspect ? Awareness of third party servers issues(e.g. receiving an indication or detecting and monitoring)","189","16","Proposed New WIDs (not part of an existing feature)",11660,"Approved","2015-06-09T16:55:57.617","2015-06-09T16:55:50.643","","","","","","","","","","","","","","",""]
["SP-150274","Stage 1 CRs on Control of Applications when Third party Servicers encounter difficulties (CATS)","SA WG1","Maurice Pope",648,"CR Pack","","","WITHDRAWN: Stage 1 CRs on Control of Applications when Third party Servicers encounter difficulties (CATS)","189","16","Proposed New WIDs (not part of an existing feature)",11830,"Withdrawn","2015-06-09T16:55:57.647",null,"","","","","","","","","","","","","","",""]
["SP-150275","New WID on Evolution to and Interworking with eCall in IMS (EIEI)","SA WG1","Maurice Pope",648,"WID","","","Objective: The objective of this work item is to specify requirements for an eCall based on IMS emergency calls to overcome current limitations of the service and to prepare for the long-term phase out of CS core and access networks. Furthermore requirements for connecting legacy (TS12 based) eCall IVSs to legacy PSAPs via IMS networks according to the ICS solution will be specified. Finally requirements for interworking of legacy IVSs with IMS emergency call based eCall supporting PSAPs and of IMS emergency call based eCall IVSs with legacy PSAPs will be defined.","189","16","Proposed New WIDs (not part of an existing feature)",11670,"Approved","2015-06-09T16:55:57.663","2015-06-09T16:55:50.643","","","","","","","","","","","","","","",""]
["SP-150276","Stage 1 CRs on Evolution to and Interworking with eCall in IMS (EIEI)","SA WG1","Maurice Pope",648,"CR Pack","","","22.101 CR0496R3; 22.101 CR0497R2; 22.101 CR0498R2","189","16","Proposed New WIDs (not part of an existing feature)",11680,"Approved","2015-06-09T16:55:57.693","2015-06-09T16:55:50.657","","","","","","","","","","","","","","",""]
["SP-150277","TR 22.802 v.2.0.0 on Study on Need for multiple APNs (FS_MAPN) for approval","SA WG1","Maurice Pope",648,"TS or TR","","","Abstract of document: The scope of this TR is: - to provide details about the use cases where there is a need of control of APNs; - to identify potential new requirements to fulfil the use cases; - to identify potential solutions to fulfil the use cases; The scope of the TR is focussed on Machine-To-Machine UEs but can take into account a more generic set of UEs. This study identifies what connectivity use-cases that are needed to be fulfilled, and studies if multiple APN or a multi-purpose APN per subscription (IMSI) combined with other 3GPP specified features can support those connectivity use-cases. The study also analyses the impacts in scenarios where the service provider decides to change the MNO. Changes since last presentation to TSG SA Meeting #66: -'APN Provisioning based on UE bootstrap from UICC' solution description for In-vehicle use case and for 'Provision of an International M2M Service for a Business Customer' use case -An enhanced ME and existing UICC based","181","15.2.25","(FS_MAPN) - Study on Need for multiple APNs",11600,"Approved","2015-06-09T16:55:57.707","2015-06-11T05:37:07.193","","","Rel-14","22.802","2.0.0","FS_MAPN","","","","","","","","",""]
["SP-150278","TR 22.899 v.2.0.0 on Enhancements to User Location Reporting Support (FS_eULRS)","SA WG1","Maurice Pope",648,"TS or TR","","","Abstract of document: TR 22.899 contains use cases for enhanced location reporting, when the LCS function is not deployed. It also identifies the potential requirements, which include: - When LCS system is not deployed, the 3GPP core network shall be able to obtain user's cell-level location at pre-configured time points. - When LCS system is not deployed, the 3GPP core network shall be able to determine which users with common characteristics are within defined cell or cells. - The 3GPP core network shall be able to define the Focus Area for certain service, offered to a subscriber. Subject to regional regulatory requirements, the 3GPP core network shall be notified when the user either in connected mode or the idle mode enters or leaves the Focus Area. The conclusion of the TR recommends that the requirements identified in the TR are taken as a basis for the development of normative work. Changes since last presentation to SA Meeting: Provide several editorial cleanup chang","182","15.2.27","(FS_eULRS) - Study on Enhancements to User Location Reporting Support",11610,"Approved","2015-06-09T16:55:57.757","2015-06-11T05:37:07.300","","","Rel-14","22.899","2.0.0","FS_eULRS","","","","","","","","",""]
["SP-150279","TR 22.818 v.2.0.0 on Control of Applications when Third party Servers encounter difficulties (FS_CATS)","SA WG1","Maurice Pope",648,"TS or TR","","","Abstract of document: This TR identifies potential requirements that will enable the 3GPP network to control traffic from UE to an application on a third party server or the third party server itself while not affecting other traffic when the 3GPP network becomes aware that the application on the third party server or the third party server itself has run into difficulties. This will make it possible to: - Reduce or avoid unproductive traffic in 3GPP network (i.e., traffic that the 3rd party server is not able to receive) by blocking it either in the UE or in the 3GPP network (primary objective) - Allow 3GPP network to help 3rd party servers to handle overload and recover from failures (secondary objective) Changes since last presentation to TSG SA Meeting #66:  Consolidation of potential requirements Conclusions and recommendations Considerations on Relationship between CATS and other existing Access Controls Considerations on Network Sharing Considerations on Security Use c","183","15.2.28","(FS_CATS) - Study on Control of Applications when Third party Servers encounter difficulties",11620,"Approved","2015-06-09T16:55:57.787","2015-06-11T05:37:07.427","","","Rel-14","22.818","2.0.0","FS_CATS","","","","","","","","",""]
["SP-150280","New WID on study on Enhancement to FMSS for Rel-14","SA WG1","Maurice Pope",648,"WID","","","Objective: The objective is to study use cases and propose potential requirements to enhance flexible mobile service steering developed in Rel-13. Some candidate scenarios are listed in the following:  1. Support third party owned (S)Gi-LAN service is used by the operator for user's IP traffic. 2. Support charging to the user traffic routed to 3rd party (S)Gi-LAN network.","189","16","Proposed New WIDs (not part of an existing feature)",11690,"Approved","2015-06-09T16:55:57.833","2015-06-09T16:55:51","","","","","","","","","","","","","","",""]
["SP-150281","Request for Exception for Enhancement of ePDG Selection Mechanisms","Rogers Communications, China Mobile, Intel, Qualcomm Inc., Alcatel-Lucent","Alexander Markman",35093,"other","","","Network Operators deploying S2b VoWiFi solutions identified an urgent need to enhance ePDG selection procedures to support the location based ePDG selection and accommodate various roaming use cases.","127","13.44","(TEI13) - TEI Rel-13",11380,"Noted","2015-06-09T16:55:57.850","2015-06-12T13:52:33.967","","","Rel-13","","","TEI13","","","","","","","","",""]
["SP-150282","Rel-13 Work Item Exception for TEI13 CRs for Enhancements of ePDG Selection Mechanisms","Rogers Communications, China Mobile, Intel, Qualcomm Inc., Alcatel-Lucent, Deutsche Telekom, Telecom Italia","Alexander Markman",35093,"other","","","Expected Completion Date: September, 2015 (SA#69) Service(s) impacted: Voice service over WiFi (S2b) Specification(s) affected: TS 23.402 Task(s) within work which are not complete: The consideration of the problems and the technical solutions for ePDG Selection mechanisms, including the Location Based ePDG Selection and other Enhancements. Consequences if not included in Release 13: Non optimal WiFi calling quality of experience with negative affect on VoLTE service quality perception will persist. Inability to accommodate practical deployment scenarios will persist. Abstract of document: This exception expresses the expectation that SA WG2 will consider solutions for ePDG selection needed to address problems raised by operators deploying S2b based VoWiFi, e.g. to enable reduction of the end-to-end speech path delay and to add flexibility to the selection mechanisms to accommodate different practical deployment/roaming scenarios and regulatory (LI) requirements. Motivation t","127","13.44","(TEI13) - TEI Rel-13",11390,"Revised","2015-06-09T16:55:57.863","2015-06-12T13:52:33.997","","SP-150351","Rel-13","","","TEI13","","","","","","","","",""]
["SP-150283","2 CRs to 23.401 on TEI12 (Rel-12, Rel-13)","SA WG2","Maurice Pope",648,"CR Pack","","","23.401 CR2868R1; 23.401 CR2869R1","81","12.52","(TEI12) - TEI Rel-12",10630,"Revised","2015-06-09T16:55:57.880","2015-06-09T16:55:51.017","","SP-150284","Rel-12","","","TEI12","","","","","","","","",""]
["SP-150284","2 updated CRs to 23.401: Clarification on Network Triggered Service Request (Rel-12, Rel-13)","LG Electronics, Alcatel-Lucent","Laeyoung Kim",40613,"CR Pack","","","Propose to update two CRs to TS 23.401 entitled Clarification on Network Triggered Service Request. 23.401 CR2868R2; 23.401 CR2869R2","81","12.52","(TEI12) - TEI Rel-12",10640,"Approved","2015-06-09T16:55:57.910","2015-06-14T11:58:32.383","SP-150283","","Rel-12","","","TEI12","","","","","","","","",""]
["SP-150285","WID on MBMS Enhancements Stage 2 for Rel-13","Nokia Networks, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, LG Electronics","Rainer Liebhart",13470,"WID","","","Rel-13 work item to do normative work on MBMS Enhancements","189","16","Proposed New WIDs (not part of an existing feature)",11700,"Noted","2015-06-09T16:55:57.927","2015-06-20T13:04:37.393","","","","","","","","","","","","","","",""]
["SP-150286","Rel-13 Work Item Exception for MBMS_enh_St2","Nokia Networks","Rainer Liebhart",13470,"other","","","Exception sheet for the MBMS_enh_St2 feature","189","16","Proposed New WIDs (not part of an existing feature)",11710,"Noted","2015-06-09T16:55:57.943","2015-06-20T13:04:37.393","","","","","","","","","","","","","","",""]
["SP-150287","Way forward for work on Rel-13 MBMS enhancements","Motorola Solutions","Val Oprescu",14981,"other","","","Moving forward with GCSE and MBMS enhancements for Rel-13, work should proceed under TEI13 (rather than MBMS_enh SID or WID), with cat B/C CRs (and potentially liaison statements to other groups) being the vehicle for incremental improvements to existing specifications.","189","16","Proposed New WIDs (not part of an existing feature)",11720,"Noted","2015-06-11T05:37:16.553","2015-06-20T13:04:37.393","","","","","","","","","","","","","","",""]
["SP-150288","Explicit identifications of application impacts in 3GPP templates","Motorola Solutions","Val Oprescu",14981,"other","","","Proposes that the Secretariat reviews and revises, as appropriate, the 3GPP templates, with the goal of adding, where necessary, an identifiable 'Application' category for relevant specs targeted outside traditional network operator's realm.","196","19.1","Improvements to working methods",11870,"Noted","2015-06-11T05:37:16.583","2015-06-20T13:04:37.407","","","","","","","","","","","","","","",""]
["SP-150289","SA WG3 Status Report","SA WG3 Chairman","Maurice Pope",648,"report","","","Status Report of SA WG3 activities to TSG SA#68","13","7.3","SA WG3 Report and Questions for Advice",10150,"Noted","2015-06-11T05:37:16.617","2015-06-14T11:58:33.163","","","","","","","","","","","","","","",""]
["SP-150290","Revised WID Lawful Interception Rel-13 (LI13)","SA WG3","Maurice Pope",648,"WID","","","Objective: The objective of this work item is to enhance the 3GPP LI service to accommodate Release 13 service enhancements and extensions. Enhancements to specifications TS 33.106, TS 33.107 and TS 33.108 will address LI Service Requirements, LI Architecture, LI functions and the HI2 (Intercepted Related Information) and the HI3 (Content) interfaces for delivery to the Law Enforcement Monitoring Facilities.","124","13.41","(LI13) - Lawful Interception in Rel-13",11280,"Approved","2015-06-11T05:37:16.630","2015-06-14T11:58:33.163","","","Rel-13","","","LI13","","","","","","","","",""]
["SP-150291","Revised WID Study on Security aspects of Integration of Single Sign-On (SSO) frameworks with 3GPP networks","SA WG3","Maurice Pope",648,"WID","","","Objective: The objective of this Study Item is to investigate the security aspects of the service requirements specified by SA WG1 in TS 22.101, clause 26, on the integration of SSO frameworks with 3GPP networks for various operator authentication configurations, and identify if the SA WG1 requirements give rise to further specification work in SA WG3. In particular, this study evaluates existing interworking solutions, cf. clause 2.1, between SSO frameworks and 3GPP authentication mechanisms against the SA WG1 requirements in TS 22.101 and develops new solutions as appropriate.","161","15.2.5","(FS_SSO_Int_Sec) - Study on Security aspects of Integration of Single Sign-On (SSO) frameworks with 3GPP networks",11540,"Revised","2015-06-11T05:37:16.647","2015-06-14T11:58:33.913","","SP-150368","Rel-12","","","FS_SSO_Int, SSO_Int","","","","","","","","",""]
["SP-150292","Revised WID Security Assurance Specification for 3GPP network products (SCAS)","SA WG3","Maurice Pope",648,"WID","","","The present contribution proposes updating the approved WID to implement the proposal in section S3-151141 'Discussion of way forward for SCAS' about including requirements that are expected to apply to more than one network product class in a 'SECAM Catalogue' TS.  It is further suggested to not include the threats description in any of these TSs and delete corresponding text from the objectives section of the present WID. The major specifications do not contain threats descriptions. E.g. threats for EPS / LTE are contained in TR 33.821. It is therefore suggested to leave threats and risks in TR 33.806. Furthermore, the names of the relevant GSMA groups have changed and are corrected here. Finally, the WID update adjusts the completion dates and deletes the name of the co-rapporteur that no longer attends SA WG3.","107","13.24","(SCAS) - Security Assurance Specification for 3GPP network products",11070,"Approved","2015-06-11T05:37:16.660","2015-06-14T11:58:35.397","","","Rel-13","","","SCAS","","","","","","","","",""]
["SP-150293","TR 33.895: Study on Security aspects of integration of Single Sign-On (SSO) frameworks with 3GPP operator-controlled resources and mechanisms","SA WG3","Maurice Pope",648,"TS or TR","","","Abstract of document: The TR contains a study on the security aspects of the service requirements specified by SA WG1 on the integration of SSO frameworks with 3GPP networks for various operator authentication configurations. The study covers the security requirements to enable the operator to become the preferred SSO Identity Provider. Changes since last presentation to <TSG> Meeting #<N>: This is the first presentation to TSG SA. Outstanding Issues: None. Contentious Issues: None.","161","15.2.5","(FS_SSO_Int_Sec) - Study on Security aspects of Integration of Single Sign-On (SSO) frameworks with 3GPP networks",11550,"Noted","2015-06-11T05:37:16.693","2015-06-14T11:58:36.143","","","Rel-12","33.895","1.0.0","FS_SSO_Int, SSO_Int","","","","","","","","",""]
["SP-150294","TR 33.872: Security enhancements to support webRTC interworking","SA WG3","Maurice Pope",648,"TS or TR","","","Abstract of document: The TR contains a study on security issues following the potential modifications of the IMS architecture and stage 2 procedures as required by the support of eWebRTCi (Enhancements to WEBRTC interoperability).  In particular, the present document focuses on: Feasibility of support for end to end WebRTC security, security aspects of WebRTC NAT traversal, and security aspects of third-party WebRTC access in the case where the 3rd party allocates IMS identities from a block.  Changes since last presentation: This is the first presentation to TSG SA. Outstanding Issues: Completion of the study on security aspects of WebRTC NAT traversal, especially TURN credential provisioning.  Completion of the study on third-party WebRTC access in the case where the 3rd party allocates IMS identities from a block where the associated subscription corresponds to a class of users supported by the WebRTC environment (e.g., enterprise associates) rather than a single end user","97","13.14","(eWebRTCi) - Enhancements to WebRTC interoperability",10910,"Noted","2015-06-11T05:37:16.723","2015-06-14T11:58:37.737","","","Rel-13","33.872","1.0.0","eWebRTCi","","","","","","","","",""]
["SP-150295","TR 33.916: Security Assurance Methodology for 3GPP network products","SA WG3","Maurice Pope",648,"TS or TR","","","Abstract of document: TR 33.916 defines the complete Security Assurance Methodology (SECAM) evaluation process (evaluation, relation to SECAM Accreditation Body, roles, etc.) as well as the components of SECAM that are intended to provide the expected security assurance. It will thus describe the general scheme providing an overview of the entire scheme and explaining how to create and apply the Security Assurance Specifications (SCASs). It will detail the different evaluation tasks (vendor network product development and network product lifecycle management process assessment, Security Compliance Testing, Basic Vulnerability Testing and Enhanced Vulnerability Analysis) and the different actors involved. The present document will help all involved parties to have a clear understanding of the overall process and the covered threats. The concrete security requirements will be part of the SCASs for each network product class and not part of this overall process document. Some of","107","13.24","(SCAS) - Security Assurance Specification for 3GPP network products",11080,"Noted","2015-06-11T05:37:16.770","2015-06-14T11:58:38.593","","","Rel-13","33.916","1.0.0","SCAS","","","","","","","","",""]
["SP-150296","Release 10 CRs on Lawful Interception (LI10)","SA WG3","Maurice Pope",648,"CR Pack","","","33.106 CR0137; 33.106 CR0138; 33.106 CR0139; 33.106 CR0140","27","10","Rel-10 CRs (Need to be very well justified!)",10290,"Approved","2015-06-11T05:37:16.817","2015-06-14T11:58:39.467","","","","","","","","","","","","","","",""]
["SP-150297","Release 12 CRs on Lawful Interception (LI12)","SA WG3","Maurice Pope",648,"CR Pack","","","33.107 CR0172; 33.107 CR0173; 33.108 CR0267; 33.108 CR0268; 33.108 CR0269; 33.108 CR0270; 33.108 CR0271; 33.108 CR0272; 33.108 CR0273","77","12.48","(LI12) - Lawful Interception in Rel-12",10580,"Approved","2015-06-11T05:37:16.833","2015-06-14T11:58:39.467","","","Rel-12","","","LI12","","","","","","","","",""]
["SP-150298","Release 13 CRs on Lawful Interception (LI13)","SA WG3","Maurice Pope",648,"CR Pack","","","33.106 CR0141; 33.106 CR0142","124","13.41","(LI13) - Lawful Interception in Rel-13",11290,"Approved","2015-06-11T05:37:16.850","2015-06-14T11:58:40.200","","","Rel-13","","","LI13","","","","","","","","",""]
["SP-150299","Release 13 CRs on enhancements of Proximity Based Services (eProSe)","SA WG3","Maurice Pope",648,"CR Pack","","","33.303 CR0066","99","13.16","(ePROSE, PROSE_EXT) - Enhancements to Proximity-based Services",10950,"Approved","2015-06-11T05:37:16.880","2015-06-14T11:58:40.933","","","Rel-13","","","eProSe","","","","","","","","",""]
["SP-150300","Release 12 CRs on Proximity based Services (ProSe)","SA WG3","Maurice Pope",648,"CR Pack","","","33.303 CR0057R1; 33.303 CR0058R1; 33.303 CR0060R1; 33.303 CR0062R1; 33.303 CR0063R1; 33.303 CR0064R1; 33.303 CR0065; 33.303 CR0067; 33.303 CR0068","43","12.14","(ProSe and FS_ProSe) - Proximity based Services",10490,"Approved","2015-06-11T05:37:16.897","2015-06-14T11:58:41.697","","","Rel-12","","","FS_ProSe, ProSe","","","","","","","","",""]
["SP-150301","Release 8 CRs on Generic Bootstrapping Architecture Push Function (GBAPush)","SA WG3","Maurice Pope",648,"CR Pack","","","33.223 CR0024; 33.223 CR0025; 33.223 CR0026; 33.223 CR0027; 33.223 CR0028","25","8.5","Rel-8 CRs (Need to be very well justified!)",10250,"Approved","2015-06-11T05:37:16.910","2015-06-14T11:58:43.180","","","","","","","","","","","","","","",""]
["SP-150302","Release 12 CRs on Specification of the TUAK Algorithm Set (STAS)","SA WG3","Maurice Pope",648,"CR Pack","","","35.936 CR0001R1","51","12.22","(MTCe and FS_MTCe) - Machine-Type and other mobile data applications Communications Enhancements",10530,"Approved","2015-06-11T05:37:16.943","2015-06-14T11:58:43.180","","","Rel-12","","","FS_MTCe, MTCe","","","","","","","","",""]
["SP-150303","2 CRs to 22.179 on MCPTT","HOME OFFICE","Richard Allen",57420,"CR Pack","","","22.179 CR0031; 22.179 CR0032. Telefonica submitted the document S1-151042 to SA WG1#70 meeting in Los Cabos Mexico in April. The Telefonica paper had 11 questions related to the MCPTT requirements, these questions were discussed with interested parties at SA WG1#70. It was that decided that there should be further discussion on a subset of these queries in a conference call prior to SA#68, so that CRs could be discussed and CRs input into the Malmo SA plenary to be agreed.  The result of the conference calls and various discussions on and off the SA WG1 reflector has led to 2 company CRs presented by the Home Office for approval at this meeting. Please see the documents in the CR pack: - Change 1 - CR#0031 Clarification on the update and use of codecs in MCPTT - Change 4 - CR#0032 Clarification on Broadcast Groups Off-Network Requirement R-7.5-002","84","13.1","(MCPTT) - Mission Critical Push-to-Talk over LTE",10740,"Revised","2015-06-11T05:37:16.957","2015-06-13T21:32:21.193","","SP-150354, SP-150355","Rel-13","","","MCPTT","","","","","","","","",""]
["SP-150304","SA WG5 Status Report","SA WG5 Chairman","Maurice Pope",648,"report","","","Status Report of SA WG5 activities to TSG SA#68","15","7.5","SA WG5 Report and Questions for Advice",10170,"Noted","2015-06-11T05:37:16.990","2015-06-20T13:04:50.247","","","","","","","","","","","","","","",""]
["SP-150305","Revised WID Energy Efficiency related Performance Measurements","SA WG5","Maurice Pope",648,"WID","","","Objective: For the use cases, requirements and/or global KPIs provided by ETSI TC EE related to energy efficiency, by cooperation with RAN WG2 and if needed with other 3GPP WGs, to  - identify whether or not the existing performance measurements and/or MDT data can be reused to support these needs;  - define the new performance measurements if needed; - introduce the relevant L2 performance measurements if any newly defined by RAN WG2 to SA WG5 specification; - reply to ETSI TC EE with the outcome of work listed above in a formal approach. Note: the works mentioned above shall be based only on formal requests (e.g. by LS) from ETSI TC EE.","123","13.40","(OAM13) - OAM&P Rel-13 (including all building blocks and work tasks)",11150,"Approved","2015-06-11T05:37:17.007","2015-06-14T11:58:45.440","","","Rel-13","","","OAM13","","","","","","","","",""]
["SP-150306","New WID Enhanced S2a Mobility Over Trusted WLAN access to EPC – Charging","SA WG5","Maurice Pope",648,"WID","","","Objective: Objective of this work item is to specify for the Trusted WLAN Access Gateway (TWAG) specified in TS 23.402: - Offline charging from TWAG for traffic routed to the PDN GW over S2a, also considering handover between TWAN and 3GPP access.  - Offline Charging for Rf, Ga and Bp, with TWAG supporting Rf only.","125","13.42","(CH13) - Charging Management Rel-13 (including all building blocks and work tasks)",11300,"Noted","2015-06-11T05:37:17.020","2015-06-14T11:58:46.177","","","Rel-12","","","FS_SaMOG, eSaMOG","","","","","","","","",""]
["SP-150307","New WID Announcements for IMS Online Charging (ANIMO)","SA WG5","Maurice Pope",648,"WID","","","Objective: The objective of this work item is to start the normative work on announcement notification mechanisms and information in Ro interface. Normative work will address the following aspects: 1- Announcements notification mechanism for pre, mid and post call phases 2- Common announcement information including: Life cycle notifications, usage notifications, call disconnection/rejection reasons, alerts etc.","125","13.42","(CH13) - Charging Management Rel-13 (including all building blocks and work tasks)",11320,"Approved","2015-06-11T05:37:17.050","2015-06-14T11:58:47.673","","","Rel-13","","","CH13","","","","","","","","",""]
["SP-150308","New WID Management of mobile networks that include virtualized network functions","SA WG5","Maurice Pope",648,"WID","","","Objective: The objective of this building block is to provide solutions for the management of mobile networks that include VNFs which can be part of EPC or IMS. The scope of this building block includes: 1. Concept, reference model and requirements for the management of mobile networks that include VNFs. 2. LCM for mobile networks that include VNFs. 3. CM for mobile networks that include VNFs. 4. FM for mobile networks that include VNFs. 5. PM for mobile networks that include VNFs. 6. Policy management for mobile networks that include VNFs.  7. Network Resource Model, alarms types and performance measurements for the management of mobile networks that include VNFs.  Item 1 will need to be addressed first as the other items have dependency on the progress of item 1.  SA WG5 work will be based on ETSI ISG NFV Group Specifications where applicable. SA WG5 will coordinate with ETSI ISG NFV as necessary. If SA WG5 identifies issues in ETSI ISG NFV Group Specifications, SA WG5 shou","123","13.40","(OAM13) - OAM&P Rel-13 (including all building blocks and work tasks)",11160,"Revised","2015-06-11T05:37:17.067","2015-06-14T11:58:48.407","","SP-150362","","","","","","","","","","","","",""]
["SP-150309","New WID Management concept, architecture and requirements for mobile networks that include virtualized network functions","SA WG5","Maurice Pope",648,"WID","","","Objective: The scope of this work task is to specify the management concepts, the NFV management requirements for operators and to provide the management architecture for mobile networks that include VNFs which can be part of EPC or IMS.  The objectives of the work task include: - Specify network management concept for mobile networks that include VNFs - Specify use cases and requirements for mobile networks that include VNFs - Specify management architecture and reference model for mobile networks that include VNFs SA WG5 work will be based on ETSI ISG NFV Group Specifications where applicable. SA WG5 will coordinate with ETSI ISG NFV as necessary. If SA WG5 identifies issues in ETSI ISG NFV Group Specifications, SA WG5 should indicate that to ETSI ISG NFV.","123","13.40","(OAM13) - OAM&P Rel-13 (including all building blocks and work tasks)",11170,"Revised","2015-06-11T05:37:17.083","2015-06-14T11:58:48.420","","SP-150363","","","","","","","","","","","","",""]
["SP-150310","New Study Item on Overload Control for Diameter Charging Applications","SA WG5","Maurice Pope",648,"WID","","","Objective: The objective of this study item is to study overload control mechanisms for Rf and Ro interfaces based on the conclusion of the Study Item FS_DOCME. For 3GPP Charging Diameter interfaces, the Diameter overload control mechanism will be based on the IETF Draft 'Diameter Overload Indication Conveyance' that defines the AVPs for the transport of overload information of Diameter application as well as the basic behaviour of the Diameter endpoints receiving this information. The latest IETF version: i.e. draft-ietf-dime-ovli-08 will be considered as the reference of this SI based on the fact that the IETF draft has evolved since the TR conclusion. Whenever IETF draft beyond 08 is available before study completion, it shall be considered as the new reference of the Study Item. As per TR 29.809, the following conclusions apply and will not be studied in this study item: - How a reporting node determines it is entering into an overload condition is implementation dependen","190","17","Proposed New Study Items (SIDs)",11850,"Approved","2015-06-11T05:37:17.097","2015-06-14T11:58:48.420","","","","","","","","","","","","","","",""]
["SP-150311","TR 32.849: Study on Charging aspects on Roaming End-to-end scenarios with VoLTE IMS and interconnecting networks.","SA WG5","Maurice Pope",648,"TS or TR","","","Abstract of document: The objective of this study item is to document missing elements and information with regard to the roaming architecture for Voice over IMS with Local Breakout.  This TR collects and evaluates end-to-end roaming scenarios under different aspects of charging. The main scenarios presented will include mobile originating calls with and without the use of the loopback mechanism and mobile terminating call scenarios. It analyses operator requirements in consideration of the roaming scenarios and the existing Charging specifications  The conclusions are presented in a further section with assumptions made and proposed further proceedings on these issues.  Within TR 29.949 'Study on technical aspects on roaming end-to-end scenarios with Voice over LTE (VoLTE) IP Multimedia Subsystem (IMS) and other networks' describes the scenarios seen from signalling aspect where TR 32.849 is based on. TR 32.849 study the charging aspects of the scenarios described in TR 29.4","179","15.2.23","(FS_REVOLTE_IMS_CH) - Charging aspects on Roaming End-to-end scenarios with VoLTE IMS and interconnecting networks",11590,"Approved","2015-06-11T05:37:17.130","2015-06-14T11:58:48.420","","","Rel-13","32.849","2.0.0","FS_REVOLTE_IMS_CH","","","","","","","","",""]
["SP-150312","TR 32.843: Study on Inter-PLMN PS domain online charging","SA WG5","Maurice Pope",648,"TS or TR","","","Abstract of document: The document intends to study in a first phase, based on high level scenarios for Flow Based Charging, relying on defined TS 23.203 [72] PCC roaming architectures with Gy crossing PLMNs, the following aspects: - Information availability in both PLMNs,  - Inter-PLMN connection mechanisms for Diameter messages - Impacts on Inter-operator charging  - Whether a 'proxy OCS' is needed The scenarios intended to be covered, are based on a set of GSMA defined services (e.g. Video over LTE, RCS services), services provided through generic AF in both roaming LBO and fixed-mobile convergence contexts (3GPP UE NSWO traffic). The document intends to identify Key issues (generic or identified within the scenarios), propose solutions and provide recommendation for these Key issues. The document intends also to derive a simplified Gy for IOT purpose. Changes since last presentation to SA Meeting#66:  Remaining outstanding issues were:  - For some key issues identified fr","125","13.42","(CH13) - Charging Management Rel-13 (including all building blocks and work tasks)",11330,"Noted","2015-06-11T05:37:17.177","2015-06-14T11:58:49.297","","","Rel-13","32.843","1.2.0","CH13","","","","","","","","",""]
["SP-150313","Rel-13 CRs on WLAN Management (WLAN-OAM)","SA WG5","Maurice Pope",648,"CR Pack","","","32.401 CR0031R2","123","13.40","(OAM13) - OAM&P Rel-13 (including all building blocks and work tasks)",11180,"Approved","2015-06-11T05:37:17.207","2015-06-14T11:58:50.153","","","Rel-13","","","OAM13","","","","","","","","",""]
["SP-150314","Rel-13 CRs on Energy Efficiency related Performance Measurements (OAM-PM_EE)","SA WG5","Maurice Pope",648,"CR Pack","","","32.425 CR0148R2; 32.425 CR0157R1","123","13.40","(OAM13) - OAM&P Rel-13 (including all building blocks and work tasks)",11190,"Approved","2015-06-11T05:37:17.240","2015-06-14T11:58:50.887","","","Rel-13","","","OAM13","","","","","","","","",""]
["SP-150315","Rel-13 CRs on Multi-Broadcast Single Frequency Network (MBSFN) Minimization of Drive Tests (MDT) enhancement (MBSFN_MDT)","SA WG5","Maurice Pope",648,"CR Pack","","","32.421 CR0074R1; 32.422 CR0078R2; 32.441 CR0019R2; 32.442 CR0238R2; 32.446 CR0060R1","123","13.40","(OAM13) - OAM&P Rel-13 (including all building blocks and work tasks)",11200,"Approved","2015-06-11T05:37:17.253","2015-06-14T11:58:51.637","","","Rel-13","","","OAM13","","","","","","","","",""]
["SP-150316","Rel-11 CRs on OAM Maintenance and small Enhancements  (OAM11)","SA WG5","Maurice Pope",648,"CR Pack","","","28.652 CR0010; 28.652 CR0011; 28.652 CR0012; 28.652 CR0013; 32.101 CR0056; 32.421 CR0073; 32.422 CR0271; 32.441 CR0018","28","11","Rel-11 CRs",10350,"Approved","2015-06-11T05:37:17.287","2015-06-14T11:58:52.400","","","","","","","","","","","","","","",""]
["SP-150317","Rel-12 CRs on OAM Maintenance and small Enhancements  (OAM12)","SA WG5","Maurice Pope",648,"CR Pack","","","32.300 CR0031R1","79","12.50","(OAM12) - OAM&P Rel-12 (including all building blocks and work tasks)",10620,"Approved","2015-06-11T05:37:17.300","2015-06-14T11:58:52.400","","","Rel-12","","","OAM12","","","","","","","","",""]
["SP-150318","Rel-13 CRs on ULI and release causes for charging enhancement for VoLTE (ULRELC-CH)","SA WG5","Maurice Pope",648,"CR Pack","","","32.251 CR0404R1; 32.298 CR0527R1; 32.299 CR0643R1","125","13.42","(CH13) - Charging Management Rel-13 (including all building blocks and work tasks)",11340,"Approved","2015-06-11T05:37:17.333","2015-06-14T11:58:53.147","","","Rel-13","","","CH13","","","","","","","","",""]
["SP-150319","Rel-11 CRs of Charging of System Improvements to Machine-Type Communications (SIMTC-CH)","SA WG5","Maurice Pope",648,"CR Pack","","","32.251 CR0397R1; 32.251 CR0398R1; 32.251 CR0399R1","28","11","Rel-11 CRs",10360,"Approved","2015-06-11T05:37:17.347","2015-06-14T11:58:53.897","","","","","","","","","","","","","","",""]
["SP-150320","Rel-13 CRs on Enhanced Network Management (NM) centralized Coverage and Capacity Optimization (SON-NM-CCO)","SA WG5","Maurice Pope",648,"CR Pack","","","28.628 CR0010R3","123","13.40","(OAM13) - OAM&P Rel-13 (including all building blocks and work tasks)",11210,"Approved","2015-06-11T05:37:17.363","2015-06-14T11:58:53.913","","","Rel-13","","","OAM13","","","","","","","","",""]
["SP-150321","Rel-8 CRs on Charging Management (CH8)","SA WG5","Maurice Pope",648,"CR Pack","","","32.299 CR0644; 32.299 CR0645; 32.299 CR0646; 32.299 CR0647; 32.299 CR0648; 32.299 CR0649","25","8.5","Rel-8 CRs (Need to be very well justified!)",10260,"Approved","2015-06-11T05:37:17.397","2015-06-14T11:58:54.660","","","","","","","","","","","","","","",""]
["SP-150322","Rel-9 CRs on Charging Management (CH9)","SA WG5","Maurice Pope",648,"CR Pack","","","32.260 CR0310","26","9","Rel-9 CRs (Need to be very well justified!)",10270,"Approved","2015-06-11T05:37:17.410","2015-06-14T11:58:54.660","","","","","","","","","","","","","","",""]
["SP-150323","Rel-10 CRs on Charging Management (CH10)","SA WG5","Maurice Pope",648,"CR Pack","","","32.299 CR0650R1; 32.299 CR0651R1; 32.299 CR0652R1; 32.299 CR0653R1","27","10","Rel-10 CRs (Need to be very well justified!)",10300,"Approved","2015-06-11T05:37:17.427","2015-06-14T11:58:54.660","","","","","","","","","","","","","","",""]
["SP-150324","Rel-11 CRs on Charging Management (CH11)","SA WG5","Maurice Pope",648,"CR Pack","","","WITHDRAWN: Rel-11 CRs on Charging Management (CH11)","28","11","Rel-11 CRs",10370,"Withdrawn","2015-06-11T05:37:17.457",null,"","","","","","","","","","","","","","",""]
["SP-150325","Rel-12 CRs on Charging Management (CH12)","SA WG5","Maurice Pope",648,"CR Pack","","","32.260 CR0308R1; 32.260 CR0309R1; 32.299 CR0639; 32.299 CR0640","78","12.49","(CH12) - Charging Management Rel-12 (including all building blocks and work tasks)",10590,"Approved","2015-06-11T05:37:17.473","2015-06-14T11:58:54.660","","","Rel-12","","","CH12","","","","","","","","",""]
["SP-150326","Rel-13 CRs on Charging Management (CH13)","SA WG5","Maurice Pope",648,"CR Pack","","","32.251 CR0405R1; 32.260 CR0312; 32.260 CR0316R1; 32.297 CR0021R1; 32.297 CR0022R1; 32.298 CR0528R1; 32.299 CR0632R1; 32.299 CR0655R1; 32.299 CR0656R1; 32.299 CR0657","125","13.42","(CH13) - Charging Management Rel-13 (including all building blocks and work tasks)",11350,"Approved","2015-06-11T05:37:17.487","2015-06-14T11:58:55.393","","","Rel-13","","","CH13","","","","","","","","",""]
["SP-150327","Rel-12 CRs on Short Message Service - Service Center Offline Charging (SMS-SC-CH)","SA WG5","Maurice Pope",648,"CR Pack","","","32.274 CR0031","78","12.49","(CH12) - Charging Management Rel-12 (including all building blocks and work tasks)",10600,"Approved","2015-06-11T05:37:17.520","2015-06-14T11:58:56.127","","","Rel-12","","","CH12","","","","","","","","",""]
["SP-150328","Rel-12 CRs on Charging using an Alternative Roaming Provider (Stage 2/3) (CHARP)","SA WG5","Maurice Pope",648,"CR Pack","","","32.299 CR0633R1; 32.299 CR0634R1","78","12.49","(CH12) - Charging Management Rel-12 (including all building blocks and work tasks)",10610,"Approved","2015-06-11T05:37:17.537","2015-06-14T11:58:56.877","","","Rel-12","","","CH12","","","","","","","","",""]
["SP-150329","Rel-13 CRs on Charging on enhancements for IMS Service Continuity (CHeISC)","SA WG5","Maurice Pope",648,"CR Pack","","","32.260 CR0307R1; 32.260 CR0311R1; 32.260 CR0313","125","13.42","(CH13) - Charging Management Rel-13 (including all building blocks and work tasks)",11360,"Approved","2015-06-11T05:37:17.567","2015-06-14T11:58:57.640","","","Rel-13","","","CH13","","","","","","","","",""]
["SP-150330","Rel-13 CRs on Announcements for IMS Online Charging (ANIMO)","SA WG5","Maurice Pope",648,"CR Pack","","","32.260 CR0317R1","125","13.42","(CH13) - Charging Management Rel-13 (including all building blocks and work tasks)",11370,"Approved","2015-06-11T05:37:17.597","2015-06-14T11:58:58.390","","","Rel-13","","","CH13","","","","","","","","",""]
["SP-150331","Rel-12 CRs on Application Based Charging (ABC)","SA WG5","Maurice Pope",648,"CR Pack","","","32.251 CR0400; 32.251 CR0401R1; 32.251 CR0402R1; 32.251 CR0403R1; 32.299 CR0641R1; 32.299 CR0642R1","60","12.31","(ABC and FS_ABC) - Application Based Charging",10550,"Approved","2015-06-11T05:37:17.613","2015-06-14T11:58:59.137","","","Rel-12","","","FS_ABC, ABC","","","","","","","","",""]
["SP-150332","Rel-12 CRs on Charging Aspects of Proximity-based Services (Prose-CH)","SA WG5","Maurice Pope",648,"CR Pack","","","32.277 CR0007R1; 32.277 CR0008R1; 32.277 CR0009; 32.298 CR0525R1; 32.298 CR0526; 32.299 CR0635; 32.299 CR0636; 32.299 CR0637R2; 32.299 CR0638R1","43","12.14","(ProSe and FS_ProSe) - Proximity based Services",10500,"Approved","2015-06-11T05:37:17.630","2015-06-14T11:59:00.650","","","Rel-12","","","FS_ProSe, ProSe","","","","","","","","",""]
["SP-150333","On CR 26.346-464: Signal Independent Units","Qualcomm Incorporated","Maurice Pope",648,"other","","","Qualcomm has identified issues with CR26.346-0464 which we believe need to be addressed by SA WG4. Therefore this document proposes that SA does not approve the CR, thereby handing it back to SA WG4 such that SA WG4 can address the identified issues as documented in section 2 of this paper.","127","13.44","(TEI13) - TEI Rel-13",11420,"Noted","2015-06-11T05:37:17.643","2015-06-20T13:05:07.563","","","Rel-13","26.346","","TEI13","","","","","","","","",""]
["SP-150334","Rel-13 Work Item Exception for Study on security enhancements to Web Real Time Communication (WebRTC) access to IP Multimedia Subsystem (IMS)","SA WG3","Maurice Pope",648,"other","","","Expected Completion Date: 09/2015 Service(s) impacted: WebRTC Specification(s) affected: TR 33.872, TS 33.203, Task(s) within work which are not complete: Completing study on security aspects of WebRTC NAT traversal, especially TURN credential provisioning, and specifying solution. Completing study on Security aspects third-party WebRTC access in the case where the 3rd party allocates IMS identities from a block (Wild-carded IMPU). Consequences if not included in Release 13: Security for NAT traversal will not be available. Security functionality of wild-carded IMPU will not be available.  Abstract of document: The TR contains a study on security issues following the potential modifications of the IMS architecture and stage 2 procedures as required by the support of eWebRTCi (Enhancements to WEBRTC interoperability).  In particular, the present document focuses on: Feasibility of support for end to end WebRTC security, security aspects of WebRTC NAT traversal, and security as","97","13.14","(eWebRTCi) - Enhancements to WebRTC interoperability",10920,"Approved","2015-06-11T05:37:17.677","2015-06-14T11:59:02.977","","","Rel-13","","","eWebRTCi","","","","","","","","",""]
["SP-150335","Appraisal and concerns on MCPTT standardisation","TCCA","Maurice Pope",648,"other","","","TCCA welcomes the efforts made in SA WG6 to find consensus on the way forward with MCPTT. Further TCCA wishes to underline that MCPTT as well as future WIDs MCDATA and MCVIDEO are critical topics - the life of PPDR operatives and other mission critical users will depend on their implementation thus even requirement details matter.   With this TCCA encourages SA WG6 - to invest time and effort to find consensus and avoid votes as much as possible - to aim at support for all requirements - to ensure the releases contain incremental functionality with forward compatibility with building blocks than can be used immediately on the field - to aim at scheduling colocated and coscheduled meetings between SA WG6 and CT working groups while stage 3 MCPTT work progresses","84","13.1","(MCPTT) - Mission Critical Push-to-Talk over LTE",10710,"Noted","2015-06-11T05:37:17.690","2015-06-14T11:59:03.740","","","Rel-13","","","MCPTT","","","","","","","","",""]
["SP-150336","Support team report","MCC Director","Maurice Pope",648,"report","","","Report of MCC activities to TSG SA#68","197","19.2","MCC Status Report",11880,"Revised","2015-06-11T05:37:17.723","2015-06-20T13:05:10.327","","SP-150345","","","","","","","","","","","","",""]
["SP-150337","Cellular Internet of Things: Potential impact on SA work area from 'clean slate' part of GERAN's study on 'Cellular System Support for Ultra Low Complexity and Low Throughput Internet of Things' when using an existing RAN-CN interface","Vodafone","Chris Pudney",1122,"other","","","Provides background and rationale to the GERAN study; identifies the likely need for a future SA WID for a new RAT that uses a largely-unmodified existing RAN-Core Network interface; and starts the process of identifying the impacted specifications","7","5","Items for early consideration (Please contact chairman in advance)",10040,"Noted","2015-06-14T11:59:35.643","2015-06-20T13:05:10.327","","","","","","","","","","","","","","",""]
["SP-150338","Structuring of AESE, MONTE, GROUPE, and HLcom related CRs to TS 23.682","Intel","Puneet Jain",36283,"other","","","This paper proposes to incorporate SA WG2 agreed CRs to TS 23.682 for AESE, MONTE, GROUPE, and HLcom topics in structured way in order to improve overall readability of the specification","12","7.2","SA WG2 Report and Questions for Advice",10140,"Approved","2015-06-14T11:59:35.690","2015-06-14T11:59:04.490","","","","23.682","","AESE, MONTE, GROUPE, HLcom","","","","","","","","",""]
["SP-150339","Architectural updates for Monitoring feature","Intel, Alcatel-Lucent, Huawei, Cisco","Nicolas Drevon",16459,"CR Pack","","","This paper provides the reasons why a revision 2 of CR 0099 to TS 23.682 (in SA WG2 pack SP-150236) is necessary. 23.682 CR0099R2","104","13.21","(MONTE) - Monitoring Enhancements",11030,"Approved","2015-06-14T11:59:35.720","2015-06-20T13:05:13.820","","","Rel-13","","","MONTE","","","","","","","","",""]
["SP-150340","TEI13 exception request for non-exclusionary work on Rel-13 MBMS enhancements","Motorola Solutions","Val Oprescu",14981,"other","","","Exception sheet for the MBMS_enh_St2 feature","189","16","Proposed New WIDs (not part of an existing feature)",11730,"Available","2015-06-14T11:59:35.753","2015-06-20T13:05:14.617","","","","","","","","","","","","","","",""]
["SP-150341","Status report of TSG CT#68","TSG CT Chairman","Maurice Pope",648,"report","","","TSG CT Status Report to TSG SA#68","18","7.8","TSG CT report and Questions for Advice",10210,"Noted","2015-06-20T13:06:01.010","2015-06-20T13:05:14.617","","","","","","","","","","","","","","",""]
["SP-150342","Draft meeting report of TSG CT#68","MCC","Maurice Pope",648,"report","","","Draft report of TSG CT meeting #68","18","7.8","TSG CT report and Questions for Advice",10220,"Noted","2015-06-20T13:06:01.057","2015-06-20T13:05:14.617","","","","","","","","","","","","","","",""]
["SP-150343","IETF Status report","TSG CT Chairman","Maurice Pope",648,"report","","","IETF dependencies Status report","18","7.8","TSG CT report and Questions for Advice",10230,"Noted","2015-06-20T13:06:01.087","2015-06-20T13:05:14.630","","","","","","","","","","","","","","",""]
["SP-150344","New WID Enhanced S2a Mobility Over Trusted WLAN access to EPC – Charging","Alcatel-Lucent, Alcatel-Lucent Shanghai Bell","Maryse Gardella",33757,"WID","","","Objective: Objective of this work item is to specify for the Trusted WLAN Access Gateway (TWAG) specified in TS 23.402: - Offline charging from TWAG for traffic routed to the PDN GW over S2a, also considering handover between TWAN and 3GPP access.  - Offline Charging for Rf, Ga and Bp, with TWAG supporting Rf only.","125","13.42","(CH13) - Charging Management Rel-13 (including all building blocks and work tasks)",11310,"Approved","2015-06-20T13:06:01.137","2015-06-20T13:05:14.630","","","","","","CH13","","","","","","","","",""]
["SP-150345","Support team report","MCC Director","Maurice Pope",648,"report","","","Report of MCC activities to TSG SA#68","197","19.2","MCC Status Report",11890,"Noted","2015-06-20T13:06:01.180","2015-06-20T13:05:15.427","SP-150336","","","","","","","","","","","","","",""]
["SP-150346","TSG SA#68 Time Plan","TSG SA Chairman","Erik Guttman",18782,"other","","","A time plan for Information to delegates of TSG SA#68.","2","2","Approval of Agenda",10010,"Noted","2015-06-20T13:06:01.227","2015-06-20T13:05:15.427","","SP-150347","","","","","","","","","","","","",""]
["SP-150347","TSG SA#68 Time Plan","TSG SA Chairman","Erik Guttman",18782,"other","","","A time plan for Information to delegates of TSG SA#68.","2","2","Approval of Agenda",10020,"Noted","2015-06-20T13:06:01.277","2015-06-20T13:05:15.443","SP-150346","","","","","","","","","","","","","",""]
["SP-150348","[DRAFT] LS to SA WG1 on cellular IoT work","TSG SA","Chris Pudney",1122,"LS out","","","To: SA WG1","7","5","Items for early consideration (Please contact chairman in advance)",10050,"Withdrawn","2015-06-20T13:06:01.323",null,"","","","","","","","","","",null,"SA WG1"]
["SP-150349","[DRAFT] LS on considerations for clean slate CIoT for Rel-13","TSG SA","Puneet Jain",36283,"LS out","","","To: SA WG2","7","5","Items for early consideration (Please contact chairman in advance)",10060,"Revised","2015-06-20T13:06:01.353","2015-06-20T13:05:15.443","","SP-150366","","","","","","","","",null,"SA WG2"]
["SP-150350","Reply to SA WG3-LI LS on VoLTE Roaming Architecture impact on LI service","TSG SA","Greg Schumacher",35113,"LS out","","","To: SA WG3-LI. CC: SA WG2","124","13.41","(LI13) - Lawful Interception in Rel-13",11270,"Revised","2015-06-20T13:06:01.400","2015-06-20T13:05:15.457","","SP-150367","","","","","","","","","SP-150191","SA WG3-LI","SA WG2"]
["SP-150351","TEI13 Work Item Exception for Enhancement of ePDG Selection Mechanisms","Rogers Communications, China Mobile, Intel, Qualcomm Inc., Alcatel-Lucent, Deutsche Telekom, Telecom Italia","Alexander Markman",35093,"other","","","Expected Completion Date: September, 2015 (SA#69) Service(s) impacted: Voice service over WiFi (S2b) Specification(s) affected: TS 23.402 Task(s) within work which are not complete: The consideration of the problems and the technical solutions for ePDG Selection mechanisms, including the Location Based ePDG Selection and other Enhancements. Consequences if not included in Release 13: Non optimal WiFi calling quality of experience with negative affect on VoLTE service quality perception will persist. Inability to accommodate practical deployment scenarios will persist. Abstract of document: This exception expresses the expectation that SA WG2 will consider solutions for ePDG selection needed to address problems raised by operators deploying S2b based VoWiFi, e.g. to enable reduction of the end-to-end speech path delay and to add flexibility to the selection mechanisms to accommodate different practical deployment/roaming scenarios and regulatory (LI) requirements. Motivation t","127","13.44","(TEI13) - TEI Rel-13",11400,"Revised","2015-06-20T13:06:01.447","2015-06-20T13:05:15.473","SP-150282","SP-150365","Rel-13","","","TEI13","","","","","","","","",""]
["SP-150352","Rel-13 Work Item Exception for eDRX","SA WG2","Maurice Pope",648,"other","","","Expected Completion Date: September 2015 (SA plenary #69) Service(s) impacted: Delay tolerant data services Specification(s) affected: 23.401 General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access 23.060 General Packet Radio Service (GPRS); Service description; Stage 2 23.682 Architecture enhancements to facilitate communications with packet data networks and applications 23.271 Support for MT Location services for UEs in extended DRX 23.272 Support for MT SMS for UE in extended DRX Task(s) within work which are not complete: - Negotiation of extended I-DRX between UE and network,  - Handling of paging strategy,  - Handling of mobile terminated SMS and location services,  - Handling of GTP-C retransmissions,  - Interaction between PSM and extended DRX. Consequences if not included in Release 13: Particularly for machine type communications (MTC), for applications requiring mobile terminated data with some delay","189","16","Proposed New WIDs (not part of an existing feature)",11750,"Withdrawn","2015-06-20T13:06:01.493",null,"SP-150263","","","","","","","","","","","","","",""]
["SP-150353","TEI13 Work Item Exception for Enhancement of ePDG Selection Mechanisms","Blackberry","Andrew Allen",21705,"other","","","Counter proposal to SP-150351.","127","13.44","(TEI13) - TEI Rel-13",11410,"Noted","2015-06-20T13:06:01.557","2015-06-20T13:05:16.267","","","Rel-13","","","TEI13","","","","","","","","",""]
["SP-150354","CR 'Change 1' to 22.179 on MCPTT","HOME OFFICE","Andrew Howell",714,"CR Pack","","","22.179 CR0031R1","84","13.1","(MCPTT) - Mission Critical Push-to-Talk over LTE",10750,"Approved","2015-06-20T13:06:01.587","2015-06-20T13:05:17.080","SP-150303","","Rel-13","","","MCPTT","","","","","","","","",""]
["SP-150355","CR 'Change 4' to 22.179 on MCPTT","HOME OFFICE","Andrew Howell",714,"CR Pack","","","22.179 CR0032R1","84","13.1","(MCPTT) - Mission Critical Push-to-Talk over LTE",10760,"Approved","2015-06-20T13:06:01.650","2015-06-20T13:05:17.843","SP-150303","","Rel-13","","","MCPTT","","","","","","","","",""]
["SP-150356","Update to the MCPTT WID","SA WG6","Maurice Pope",648,"WID","","","Changes Deliverable details, Rapporteur and supporting company list.","84","13.1","(MCPTT) - Mission Critical Push-to-Talk over LTE",10730,"Approved","2015-06-20T13:06:01.697","2015-06-20T13:05:18.733","SP-150217","","Rel-13","","","MCPTT","","","","","","","","",""]
["SP-150357","LS from TSG RAN: LS on architecture for Clean Slate CIOT","TSG RAN","Lorenzo Casaccia",25173,"LS in","","","As per recent PCG decision, TSG RAN expects to start a Work item on Clean Slate Cellular IOT in RAN #69.   As part of that, RAN would like to ensure that the E-UTRAN based architecture is suitable for Clean Slate Cellular IOT.   Consequently, RAN would like to kindly ask SA to deliver significant progress on FS_AE_CIoT by RAN #69, so that RAN can make a choice on the architecture in RAN #69. Action: RAN politely requests SA to ensure that SA 2 (and SA 3) have sufficient time to deliver significant progress by RAN #69. More specifically RAN politely asks SA to ask SA 2 to provide input by RAN #69 on the E-UTRAN architecture optimisation for clean slate CIoT within R13.","158","15.2.2","(FS_AE_CIoT) - Study on architecture enhancements of cellular systems for ultra low complexity and low throughput Internet of Things",11520,"Noted","2015-06-20T13:06:01.760","2015-06-20T13:05:19.497","","","Rel-13","","","FS_IoT_LC","","","","",null,null,null,"RP-151087","SP-150366"]
["SP-150358","Updated WID for Isolated E-UTRAN Operation for Public Safety","SA WG2","Maurice Pope",648,"WID","","","Objective: The SA WG2 objectives are as follows: 1. Document in an informative annex in the relevant specification (TS 23.401) the implementation and deployment guidelines for 'operation of public safety networks in the no backhaul (to Macro EPC) scenario' using a Local EPC approach as identified in the Stage 2 Feature Study (TR 23.797). No stage-3 work is expected from the SA WG2 part of the work item.","85","13.2","(IOPS, FS_IOPS and FS_IOPS_St2) - Isolated E-UTRAN Operation for Public Safety (including FS phase)",10810,"Approved","2015-06-20T13:06:01.807","2015-06-20T13:05:20.310","SP-150248","","Rel-13","","","FS_IOPS, IOPS, FS_IOPS_St2","","","","","","","","",""]
["SP-150359","Rel-13 Work Item Exception for IOPS","SA WG2","Maurice Pope",648,"other","","","Expected Completion Date: SA#69 (September 2015) Service(s) impacted: IOPS Service Specification(s) affected: TS 23.401 Task(s) within work which are not complete: Document in an informative annex in the relevant specification (TS 23.401) the implementation and deployment guidelines for 'operation of public safety networks in the no backhaul (to Macro EPC) scenario' using a Local EPC approach as identified in the Stage 2 Feature Study (TR 23.797).  No stage-3 work is expected from the SA WG2 part of the work item.  Resource Estimate: one small/medium CR to TS 23.401  Alignment of the Stage 2 specification (TS 23.401) may be required based on feedback from SA WG3 following the conclusions of their IOPS Security study (TR 33.897).  Consequences if not included in Release 13: A standardised approach to supporting Public Safety networks, in the event that the backhaul to the EPC is lost, will not be supported by 3GPP.  Abstract of document: Exception sheet for Rel-13 Stage 2 norm","85","13.2","(IOPS, FS_IOPS and FS_IOPS_St2) - Isolated E-UTRAN Operation for Public Safety (including FS phase)",10830,"Approved","2015-06-20T13:06:01.853","2015-06-20T13:05:22.680","SP-150257","","Rel-13","","","FS_IOPS, IOPS, FS_IOPS_St2","","","","","","","","",""]
["SP-150360","Work Plan review at TSG SA#68","MCC Work Plan Manager","Maurice Pope",648,"WI status report","","","Work Plan review at TSG SA#68","192","18.1","Review of the work plan",11860,"Noted","2015-06-20T13:06:01.917","2015-06-20T13:05:24.990","","","","","","","","","","","","","","",""]
["SP-150361","New BB WID on Media and Quality Aspects of SRVCC Enhancements (SETA-S4)","SA WG4","Maurice Pope",648,"WID","","","Objective: The SA WG4 work is structured as follows: - Identify relevant scenarios, especially with Codec Mode Control from AMR-WB and EVS to AMR-WB in CS and EVS in CS; - Analyse Speech quality aspects and Media handling aspects, based on these scenarios; - Analyse Codec Mode Control before, during and after SRVCC; - Analyse the existing SDP Offer - Answer protocol between CS and IMS during SRVCC; - Clarify the existing Codec Compatibility aspects for SRVCC; - Propose enhancements for media and quality aspects of SRVCC with the aims:  a) to avoid transcoding cases as much as possible; b) to minimize the speech path interruption time during SRVCC; - Support SA WG2 work by SA WG4 expertise in speech quality and media handling; - Identify and update the relevant clauses in TS 26.114 (e.g. clause 12.3.4).","122","13.39","(SETA) - SRVCC Enhancements for Transcoding Avoidance",11140,"Approved","2015-06-20T13:06:01.960","2015-06-20T13:05:25.007","SP-150213","","Rel-13","","","SETA","","","","","","","","",""]
["SP-150362","New WID Management of mobile networks that include virtualized network functions","SA WG5","Maurice Pope",648,"WID","","","Objective: The objective of this building block is to provide solutions for the management of mobile networks that include VNFs which can be part of EPC or IMS. The scope of this building block includes: 1. Concept, reference model and requirements for the management of mobile networks that include VNFs. 2. LCM for mobile networks that include VNFs. 3. CM for mobile networks that include VNFs. 4. FM for mobile networks that include VNFs. 5. PM for mobile networks that include VNFs. 6. Policy management for mobile networks that include VNFs.  7. Network Resource Model, alarms types and performance measurements for the management of mobile networks that include VNFs.  Item 1 will need to be addressed first as the other items have dependency on the progress of item 1.  SA WG5 work will be based on ETSI ISG NFV Group Specifications where applicable. SA WG5 will coordinate with ETSI ISG NFV as necessary. If SA WG5 identifies issues in ETSI ISG NFV Group Specifications, SA WG5 shou","123","13.40","(OAM13) - OAM&P Rel-13 (including all building blocks and work tasks)",11161,"Approved","2015-06-20T13:06:02.007","2015-06-20T13:05:25.817","SP-150308","","","","","","","","","","","","","",""]
["SP-150363","New WID Management concept, architecture and requirements for mobile networks that include virtualized network functions","SA WG5","Maurice Pope",648,"WID","","","Objective: The scope of this work task is to specify the management concepts, the NFV management requirements for operators and to provide the management architecture for mobile networks that include VNFs which can be part of EPC or IMS.  The objectives of the work task include: - Specify network management concept for mobile networks that include VNFs - Specify use cases and requirements for mobile networks that include VNFs - Specify management architecture and reference model for mobile networks that include VNFs SA WG5 work will be based on ETSI ISG NFV Group Specifications where applicable. SA WG5 will coordinate with ETSI ISG NFV as necessary. If SA WG5 identifies issues in ETSI ISG NFV Group Specifications, SA WG5 should indicate that to ETSI ISG NFV.","123","13.40","(OAM13) - OAM&P Rel-13 (including all building blocks and work tasks)",11171,"Approved","2015-06-20T13:06:02.070","2015-06-20T13:05:25.830","SP-150309","","","","","","","","","","","","","",""]
["SP-150364","Issues to report to TSG SA#68","TSG RAN Chairman","Maurice Pope",648,"other","","","Report on issues from TSG RAN#68","17","7.7","TSG RAN report and Questions for Advice",10500,"Noted","2015-06-20T13:06:02.117","2015-06-20T13:05:25.830","","","","","","","","","","","","","","",""]
["SP-150365","TEI13 Work Item Exception for Enhancement of ePDG Selection Mechanisms","Rogers Communications, China Mobile, Intel, Qualcomm Inc., Alcatel-Lucent, Deutsche Telekom, Telecom Italia","Alexander Markman",35093,"other","","","Expected Completion Date: September, 2015 (SA#69) Service(s) impacted: Voice service over WiFi (S2b) Specification(s) affected: TS 23.402 Task(s) within work which are not complete: The consideration of the problems and the technical solutions for ePDG Selection mechanisms, including the Location Based ePDG Selection and other Enhancements. Consequences if not included in Release 13: Non optimal WiFi calling quality of experience with negative affect on VoLTE service quality perception will persist. Inability to accommodate practical deployment scenarios will persist. Abstract of document: This exception expresses the expectation that SA WG2 will consider solutions for ePDG selection needed to address problems raised by operators deploying S2b based VoWiFi, e.g. to enable reduction of the end-to-end speech path delay and to add flexibility to the selection mechanisms to accommodate different practical deployment/roaming scenarios and regulatory (LI) requirements. Motivation t","127","13.44","(TEI13) - TEI Rel-13",11401,"Approved","2015-06-20T13:06:02.163","2015-06-20T13:05:25.847","SP-150351","","Rel-13","","","TEI13","","","","","","","","",""]
["SP-150366","LS on considerations for clean slate CIoT for Rel-13","TSG SA","Puneet Jain",36283,"LS out","","","To: SA WG2","7","5","Items for early consideration (Please contact chairman in advance)",10061,"Approved","2015-06-20T13:06:02.210","2015-06-20T13:05:26.597","SP-150349","","","","","","","","","","SP-150357","SA WG2"]
["SP-150367","Reply to SA WG3-LI LS on VoLTE Roaming Architecture impact on LI service","TSG SA","Greg Schumacher",35113,"LS out","","","To: SA WG3-LI. CC: SA WG2","124","13.41","(LI13) - Lawful Interception in Rel-13",11271,"Revised","2015-06-20T13:06:02.257","2015-06-20T13:05:26.610","SP-150350","SP-150370","","","","","","","","",null,"SA WG3-LI","SA WG2"]
["SP-150368","Revised WID Study on Security aspects of Integration of Single Sign-On (SSO) frameworks with 3GPP networks","SA WG3","Maurice Pope",648,"WID","","","Objective: The objective of this Study Item is to investigate the security aspects of the service requirements specified by SA WG1 in TS 22.101, clause 26, on the integration of SSO frameworks with 3GPP networks for various operator authentication configurations, and identify if the SA WG1 requirements give rise to further specification work in SA WG3. In particular, this study evaluates existing interworking solutions, cf. clause 2.1, between SSO frameworks and 3GPP authentication mechanisms against the SA WG1 requirements in TS 22.101 and develops new solutions as appropriate.","161","15.2.5","(FS_SSO_Int_Sec) - Study on Security aspects of Integration of Single Sign-On (SSO) frameworks with 3GPP networks",11541,"Approved","2015-06-20T13:06:02.307","2015-06-20T13:05:26.627","SP-150291","","Rel-12","","","FS_SSO_Int, SSO_Int","","","","","","","","",""]
["SP-150369","New Work Item on Extended DRX cycle for Power Consumption Optimization","SA WG2","Maurice Pope",648,"WID","","","Objective: Objective is to specify the solutions to the identified issues as captured in the conclusions of TR 23.770 to extend the DRX cycle in idle for GERAN, UTRAN and E-UTRAN. The specified solutions will reflect the agreements performed in GERAN/RAN groups, including the maximum length of the DRX cycle for idle mode.  Solutions are to be specified for the following identified issues for extending idle mode DRX cycle up to and beyond 10.24 seconds: - Support NAS-protocol extensions to enable extended DRX cycle. There needs to be coordination between UE and Core Network (SGSN/MME) for use of extended DRX. - Paging strategy in CN that fits the needs of the extended DRX cycle and normal DRX cycle. - Handling of MT SMS, e.g. avoiding retransmissions for long DRX cycles. - Impact in S/P-GW retransmissions when handling Network originated control plane procedure. - Interaction between eDRX and PSM (Power Saving Mode) in UE and MME/SGSN procedures.  - MT Location services suppor","189","16","Proposed New WIDs (not part of an existing feature)",11801,"Approved","2015-06-20T13:06:02.367","2015-06-20T13:05:28.187","SP-150254","","","","","","","","","","","","","",""]
["SP-150370","Reply to SA WG3-LI LS on VoLTE Roaming Architecture impact on LI service","TSG SA","Greg Schumacher",35113,"LS out","","","To: SA WG3-LI. CC: SA WG2","124","13.41","(LI13) - Lawful Interception in Rel-13",11272,"Revised","2015-06-20T13:06:02.430","2015-06-20T13:05:28.203","SP-150367","SP-150371","","","","","","","","",null,"SA WG3-LI","SA WG2, GSMA PSMC, GSMA WAS, GSMA IDS, GSMA NG"]
["SP-150371","Reply to SA WG3-LI LS on VoLTE Roaming Architecture impact on LI service","TSG SA","Greg Schumacher",35113,"LS out","","","To: SA WG3-LI. CC: SA WG2","124","13.41","(LI13) - Lawful Interception in Rel-13",11273,"Approved","2015-06-20T13:06:02.477","2015-06-20T13:05:28.217","SP-150370","","","","","","","","","","SP-150191","SA WG3-LI","SA WG2, GSMA PSMC, GSMA WAS, GSMA IDS, GSMA NG"]

{"sheet":"CR_Packs_List","index":1,"n_rows":105,"n_cols":11,"rows_kept":105,"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"]
["SP-150223","S2-150854","Agreed","Approved","23.228","1108","","F","Rel-11","11.10.0","AS allowing non-international format Request-URI when RAVEL is used"]
["SP-150223","S2-150856","Agreed","Approved","23.228","1109","","A","Rel-12","12.8.0","AS allowing non-international format Request-URI when RAVEL is used"]
["SP-150223","S2-150857","Agreed","Approved","23.228","1110","","A","Rel-13","13.2.0","AS allowing non-international format Request-URI when RAVEL is used"]
["SP-150224","S2-151488","Agreed","Approved","23.272","0945","","F","Rel-11","11.9.0","Correction of CSFB references for CS domain priority schemes"]
["SP-150224","S2-151489","Agreed","Approved","23.272","0946","","A","Rel-12","12.5.0","Correction of CSFB references for CS domain priority schemes"]
["SP-150225","S2-151106","Agreed","Approved","23.228","1115","1","F","Rel-12","12.8.0","Codecs for WebRTC"]
["SP-150225","S2-151107","Agreed","Approved","23.228","1116","1","A","Rel-13","13.2.0","Codecs for WebRTC"]
["SP-150226","S2-150935","Agreed","Approved","23.002","0282","","B","Rel-12","12.6.0","Adding ProSe related introductions and definitions"]
["SP-150226","S2-151324","Agreed","Approved","23.303","0158","1","F","Rel-12","12.4.0","Mandatory use of Geographical Areas"]
["SP-150226","S2-151325","Agreed","Approved","23.303","0151","3","F","Rel-12","12.4.0","Support for ProSe in multicarrier across PLMNs"]
["SP-150226","S2-151373","Agreed","Approved","23.303","0160","2","F","Rel-12","12.4.0","Clarification of ProSe Layer 2 Group ID provisioning"]
["SP-150226","S2-151492","Agreed","Approved","23.303","0163","","F","Rel-12","12.4.0","Clarify APN configuration for connectivity to ProSe Function"]
["SP-150226","S2-151896","Agreed","Approved","23.303","0165","1","F","Rel-12","12.4.0","UE context clarification"]
["SP-150226","S2-151989","Agreed","Approved","23.303","0173","2","F","Rel-12","12.4.0","Clarification on service authorisation procedure based on location"]
["SP-150226","S2-152065","Agreed","Approved","23.303","0170","2","F","Rel-12","12.4.0","Correction of UE identities used between ProSe Function for service authorization"]
["SP-150227","S2-151987","Agreed","Approved","23.468","0063","2","F","Rel-12","12.4.0","Correction of specification of Group Call suspension"]
["SP-150227","S2-151988","Agreed","Approved","23.468","0064","1","A","Rel-13","13.0.0","Correction of specification of Group Call suspension"]
["SP-150227","S2-152067","Agreed","Approved","23.468","0058","1","F","Rel-12","12.4.0","Correct FlowID per agreement with CT WG3"]
["SP-150227","S2-152068","Agreed","Approved","23.468","0059","1","A","Rel-13","13.0.0","Correct FlowID per agreement with CT WG3"]
["SP-150228","S2-151131","Agreed","Approved","23.682","0101","1","F","Rel-12","12.3.0","Handling of PSM timer"]
["SP-150228","S2-151132","Agreed","Approved","23.682","0102","1","A","Rel-13","13.1.0","Handling of PSM timer"]
["SP-150229","S2-151416","Agreed","Approved","23.401","2860","3","F","Rel-12","12.8.0","MS Info Change Reporting Action at change of Serving Node (MME <--> SGSN): Update of call Flows"]
["SP-150229","S2-151417","Agreed","Approved","23.401","2861","3","A","Rel-13","13.2.0","MS Info Change Reporting Action at change of Serving Node (MME <--> SGSN): Update of call Flows"]
["SP-150231","S2-151959","Agreed","Approved","23.203","0978","2","F","Rel-13","13.3.0","Alignment of RUCI reporting restrictions' basis for UPCON"]
["SP-150232","S2-152091","Agreed","Approved","23.203","0976","3","F","Rel-13","13.3.0","Configuring AF application identifier value in PCRF to avoid SRVCC"]
["SP-150232","S2-152126","Agreed","Approved","23.228","1134","3","B","Rel-13","13.2.0","Supporting Class of Users"]
["SP-150233","S2-151802","Agreed","Approved","23.303","0164","1","B","Rel-13","12.4.0","Restricted ProSe Direct Discovery Model B procedures"]
["SP-150233","S2-151803","Agreed","Approved","23.303","0166","1","B","Rel-13","12.4.0","Authorization information for ProSe Restricted Direct Discovery, Model A and B"]
["SP-150233","S2-151806","Agreed","Approved","23.303","0174","1","B","Rel-13","12.4.0","Adding ProSe Discovery UE ID in the service authorization"]
["SP-150233","S2-151816","Agreed","Approved","23.303","0169","2","B","Rel-13","12.4.0","Restricted ProSe Direct Discovery with Application-controlled extension"]
["SP-150233","S2-152001","Agreed","Approved","23.303","0168","2","B","Rel-13","12.4.0","Restricted ProSe Direct Discovery Model A procedures"]
["SP-150233","S2-152002","Agreed","Approved","23.303","0175","2","B","Rel-13","12.4.0","Restricted ProSe Direct Discovery Model A Using on demand Announcing"]
["SP-150234","S2-151322","Agreed","Approved","23.236","0051","3","B","Rel-13","12.0.0","Update of MME load balancing for Dedicated Core Networks"]
["SP-150234","S2-151818","Agreed","Approved","23.060","1953","7","B","Rel-13","13.2.0","Introduce the Dedicated Core Network (DECOR) feature"]
["SP-150234","S2-151820","Agreed","Approved","23.236","0053","2","B","Rel-13","12.0.0","Load re-balancing for SGSNs with Dedicated Core Networks"]
["SP-150234","S2-152107","Agreed","Approved","23.401","2837","11","B","Rel-13","13.2.0","Introduce the Dedicated Core Network (DECOR) feature"]
["SP-150234","S2-152108","Agreed","Approved","23.401","2864","3","B","Rel-13","13.2.0","Adding support for load re-balancing within DCN"]
["SP-150235","S2-151909","Agreed","Approved","23.682","0109","1","B","Rel-13","13.1.0","Architectural updates for AESE feature"]
["SP-150235","S2-151913","Agreed","Approved","23.682","0117","1","B","Rel-13","13.1.0","Setting up an AS session with required QoS"]
["SP-150235","S2-152028","Agreed","Approved","23.002","0284","2","B","Rel-13","13.1.0","Introducing SCEF and RCAF Reference Point"]
["SP-150235","S2-152030","Agreed","Approved","23.401","2872","2","B","Rel-13","13.2.0","HSS and MME updates for AESE 3GPP resource optimizations based on providing predictable communication patterns of a UE to the MME"]
["SP-150235","S2-152041","Agreed","Approved","23.682","0116","2","B","Rel-13","13.1.0","Detailed description for informing about potential network issues"]
["SP-150235","S2-152071","Agreed","Approved","23.682","0113","3","B","Rel-13","13.1.0","Implementing AESE Solution on providing predictable communication patterns of a UE to the MME"]
["SP-150235","S2-152072","Agreed","Approved","23.682","0114","2","B","Rel-13","13.1.0","Addition of resource management for background data transfer feature"]
["SP-150235","S2-152073","Agreed","Approved","23.203","0975","2","B","Rel-13","13.3.0","Resource management for background data transfer via Rx"]
["SP-150235","S2-152074","Agreed","Approved","23.682","0118","3","B","Rel-13","13.1.0","Change the chargeable party at the session set-up or during the session"]
["SP-150235","S2-152124","Agreed","Approved","23.682","0119","4","C","Rel-13","13.1.0","Clarification on the overall architecture related with SCEF"]
["SP-150236","S2-151212","Agreed","Revised","23.682","0099","1","B","Rel-13","13.1.0","Architectural updates for Monitoring feature"]
["SP-150236","S2-151271","Agreed","Approved","23.002","0283","2","B","Rel-13","13.1.0","Introducing HSS-SCEF and MME/SGSN-SCEF Reference Points"]
["SP-150236","S2-151275","Agreed","Approved","23.401","2851","2","B","Rel-13","13.2.0","Support for Monitoring Events"]
["SP-150236","S2-151410","Agreed","Approved","23.682","0096","2","B","Rel-13","13.1.0","Update to PSM to support monitoring events"]
["SP-150236","S2-151411","Agreed","Approved","23.401","2850","2","B","Rel-13","13.2.0","Update to PSM to support monitoring events"]
["SP-150236","S2-151412","Agreed","Approved","23.060","1960","2","B","Rel-13","13.2.0","Update to PSM to support monitoring events"]
["SP-150236","S2-151510","Agreed","Approved","23.682","0100","4","B","Rel-13","13.1.0","Monitoring Feature Description"]
["SP-150236","S2-152035","Agreed","Approved","23.060","1961","5","B","Rel-13","13.2.0","Support for Monitoring Events"]
["SP-150236","S2-152036","Agreed","Approved","23.682","0104","2","B","Rel-13","13.1.0","Introduction of Charging Principles for Monitoring Events feature"]
["SP-150236","S2-152037","Agreed","Approved","23.401","2871","2","B","Rel-13","13.2.0","Monitoring event configuration in the HSS and MME"]
["SP-150236","S2-152038","Agreed","Approved","23.060","1968","2","B","Rel-13","13.2.0","Monitoring event configuration in the HSS and SGSN"]
["SP-150236","S2-152077","Agreed","Approved","23.682","0097","5","B","Rel-13","13.1.0","Introduction of monitoring procedures"]
["SP-150236","S2-152078","Agreed","Approved","23.682","0093","6","B","Rel-13","13.1.0","Monitoring via PCRF"]
["SP-150236","S2-152125","Agreed","Approved","23.682","0107","5","B","Rel-13","13.1.0","Enhancing roaming architecture for Service Exposure"]
["SP-150237","S2-150843","Agreed","Approved","23.682","0095","","B","Rel-13","13.1.0","Architecture update for GROUPE"]
["SP-150237","S2-150983","Agreed","Approved","23.401","2853","","C","Rel-13","13.2.0","MCC CR Implementation correction: Group specific NAS Level congestion control"]
["SP-150237","S2-151193","Agreed","Approved","23.401","2843","2","B","Rel-13","13.2.0","APN and group specific NAS Level congestion control"]
["SP-150237","S2-151194","Agreed","Approved","23.060","1956","2","B","Rel-13","13.2.0","APN and group specific NAS level congestion control"]
["SP-150237","S2-151883","Agreed","Approved","23.401","2877","1","F","Rel-13","13.2.0","Clarification of Group specific NAS Level congestion control"]
["SP-150237","S2-152017","Agreed","Approved","23.060","1971","2","F","Rel-13","13.2.0","Clarification of Group specific NAS Level congestion control"]
["SP-150237","S2-152018","Agreed","Approved","23.682","0094","6","B","Rel-13","13.1.0","Group message delivery function and procedure"]
["SP-150237","S2-152079","Agreed","Approved","23.401","2866","3","F","Rel-13","13.2.0","Group specific NAS Level congestion control for multiple APNs"]
["SP-150237","S2-152080","Agreed","Approved","23.060","1967","3","F","Rel-13","13.2.0","Group specific NAS level congestion control for multiple APNs"]
["SP-150238","S2-152022","Agreed","Approved","23.682","0108","2","B","Rel-13","13.1.0","HLcom solution reusing Monitoring Event 'UE Reachability' realization"]
["SP-150238","S2-152096","Agreed","Approved","23.682","0106","3","B","Rel-13","13.1.0","Introducing functions for High latency communication"]
["SP-150238","S2-152097","Agreed","Approved","23.401","2862","3","B","Rel-13","13.2.0","Introducing functions for High latency communication"]
["SP-150238","S2-152098","Agreed","Approved","23.060","1965","3","B","Rel-13","13.2.0","Introducing functions for High latency communication"]
["SP-150238","S2-152115","Agreed","Approved","23.682","0115","4","B","Rel-13","13.1.0","HLcom soluton Using Monitoring Event 'Availability after DDN Failure'"]
["SP-150239","S2-151111","Agreed","Approved","23.292","0228","1","F","Rel-13","13.1.0","Notify UE conference event package after SRVCC"]
["SP-150239","S2-151112","Agreed","Approved","23.237","0481","1","F","Rel-13","12.8.0","Notify UE conference event package after SRVCC"]
["SP-150239","S2-151114","Agreed","Approved","23.216","0332","2","F","Rel-13","12.2.0","Updating SRVCC operation possible in E-UTRAN"]
["SP-150239","S2-151135","Agreed","Approved","23.060","1893","5","C","Rel-13","13.2.0","Enable ISR for PS-only UE"]
["SP-150239","S2-151137","Agreed","Approved","23.401","2857","1","F","Rel-13","13.2.0","Paging priority and ARP Priority level: extension of CR2812r2 to CR2840r2"]
["SP-150239","S2-151138","Agreed","Approved","23.246","0392","1","F","Rel-13","13.0.0","MBMS Session Start procedure correction and editorial corrections"]
["SP-150239","S2-151145","Agreed","Approved","23.272","0939","6","C","Rel-13","12.5.0","Enable ISR for PS-only UE"]
["SP-150239","S2-151211","Agreed","Approved","23.402","1360","1","F","Rel-13","13.1.0","Clarification of Impacts when Gxx is not used for eHRPD Access"]
["SP-150239","S2-151506","Agreed","Approved","23.401","2865","","F","Rel-13","13.2.0","User CSG Information in TAU/RAU with SGW change procedure"]
["SP-150239","S2-151827","Agreed","Approved","23.203","0977","1","F","Rel-13","13.3.0","Session/bearer release cause over S2b"]
["SP-150239","S2-152083","Agreed","Approved","23.402","1366","2","F","Rel-13","13.1.0","Session/bearer release cause over S2b"]
["SP-150283","S2-151889","Agreed","Revised","23.401","2868","1","F","Rel-12","12.8.0","Clarification on Network Triggered Service Request"]
["SP-150283","S2-151890","Agreed","Revised","23.401","2869","1","A","Rel-13","13.2.0","Clarification on Network Triggered Service Request"]
["SP-150299","S3-151369","Agreed","Approved","33.303","0066","","F","Rel-12","12.3.0","UE obtaining the current time UTC from the BSF"]
["SP-150300","S3-151373","Agreed","Approved","33.303","0067","","F","Rel-12","12.3.0","Clarification on PC3ch (charging interface) security"]
["SP-150300","S3-151375","Agreed","Approved","33.303","0068","","F","Rel-12","12.3.0","Correction of standalone BSF term"]
["SP-150300","S3-151385","Agreed","Approved","33.303","0065","","F","Rel-12","12.3.0","Clarifying MIC Calculation is based on parameters, not the discovery message itself"]
["SP-150300","S3-151468","Agreed","Approved","33.303","0057","1","F","Rel-12","12.3.0","CR_ProSe NAF Key Indication"]
["SP-150300","S3-151469","Agreed","Approved","33.303","0060","1","F","Rel-12","12.3.0","Annex F correction to show ProSe Key Management Function KMS and PC8"]
["SP-150300","S3-151470","Agreed","Approved","33.303","0062","1","F","Rel-12","12.3.0","Correction of the hash input parameters for proximity request"]
["SP-150300","S3-151471","Agreed","Approved","33.303","0064","1","F","Rel-12","12.3.0","CR on PGK expiration of TS 33.303"]
["SP-150300","S3-151472","Agreed","Approved","33.303","0058","1","F","Rel-12","12.3.0","CR_ProSe Clause 6 1 3 3 VPLMN clarification"]
["SP-150300","S3-151522","Agreed","Approved","33.303","0063","1","F","Rel-12","12.3.0","Corretion on PTK ID handing"]
["SP-150301","S3-151290","Agreed","Approved","33.223","0024","","A","Rel-12","12.0.0","CR to TS 33.223: change to AUTN length"]
["SP-150301","S3-151291","Agreed","Approved","33.223","0025","","A","Rel-11","11.0.0","Change to AUTN length"]
["SP-150301","S3-151292","Agreed","Approved","33.223","0026","","A","Rel-10","10.0.0","Change to AUTN length"]
["SP-150301","S3-151293","Agreed","Approved","33.223","0027","","A","Rel-9","9.1.0","Change to AUTN length"]
["SP-150301","S3-151294","Agreed","Approved","33.223","0028","","F","Rel-8","8.6.0","Change to AUTN length"]
["SP-150302","S3-151482","Agreed","Approved","35.936","0001","1","F","Rel-12","12.0.0","Correction of clause title and text referring to wrong subject"]

{"sheet":"Parameters","index":2,"n_rows":16,"n_cols":3,"rows_kept":16,"cut":false,"hidden":true,"merged":[]}
["Types of Tdocs","Possible statuses of Tdocs","Categories"]
[]
["agenda","Reserved","A"]
["LS in","Available","B"]
["LS out","Revised","C"]
["pCR","Approved","D"]
["CR","Agreed","E"]
["CR pack","Postponed","F"]
["WID","Noted"]
["WI status report","Rejected"]
["TS or TR","Withdrawn"]
["report","Treated"]
["other","Partially approved"]
[null,"Technically endorsed"]
[null,"Merged"]
[null,"Reissued"]