{"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":734,"n_cols":31,"rows_kept":734,"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"]
["S2-150699","Draft Agenda for SA WG2#108","SA WG2 Chairman","Erik Guttman",18782,"agenda","","","The meeting agenda.","2","2","Approval of the agenda",10000,"Revised","2015-03-18T08:02:34.997","2015-04-03T09:11:30.603","","S2-151307","","","","","","","","","","","","",""]
["S2-150700","SA WG2 Chairman's Report on TSG SA#67","SA WG2 Chairman","Erik Guttman",18782,"report","","","A summary of actions and decisions at TSG SA#67 of relevance to SA WG2.","5","3","Meeting reports",10010,"Noted","2015-03-18T08:02:35.013","2015-04-07T06:37:35.733","","","","","","","","","","","","","","",""]
["S2-150701","SA WG2 Specification Adoption","SA WG2 Chairman","Erik Guttman",18782,"other","","","A proposal for action on assignment of Rapporteurs for active specifications in SA WG2. A summary of expected roles and responsibilities of these Rapporteurs of specifications in the maintenance phase.","49","7","Project Planning and Management",13810,"Available","2015-03-18T08:02:35.013","2015-04-07T06:37:35.767","","","","","","","","","","","","","","",""]
["S2-150702","Draft Report of SA WG2 meeting #107","SA WG2 Secretary","Maurice Pope",648,"report","","","Draft Report version 0.1.0rm of meeting #107 for approval","5","3","Meeting reports",10030,"Approved","2015-03-18T08:02:35.013","2015-04-06T13:45:04.097","","","","","","","","","","","","","","",""]
["S2-150703","TD Handling Report of SA WG2 meeting #107E","SA WG2 Secretary","Maurice Pope",648,"report","","","Automated report of TD handling at SA WG2#107E Electronic meeting","5","3","Meeting reports",10020,"Noted","2015-03-18T08:02:35.027","2015-03-20T15:14:02.243","","","","","","","","","","","","","","",""]
["S2-150704","LS from GSMA PSMC: LS on VoLTE Roaming Architecture","GSMA PSMC","Maurice Pope",648,"LS in","","","GSMA Product and Services Management Committee (PSMC), Network 2020 Programme and related Working Groups have been investigating a new VoLTE roaming architecture option, 'S8 Home Routed (S8HR)'. PSMC would like to inform 3GPP that PSMC endorsed S8HR as a candidate for VoLTE roaming, subject to issues (inclusive of Lawful Intercept, Emergency Call, SRVCC, and others) being resolved by 3GPP. PSMC would like to have initial feedback by PSMC#135 meeting in July 2014. Action: PSMC would like to kindly seek support from 3GPP to determine the solutions for issues identified in the GSMA (to be provided under a separate LS from GSMA NG), and inform us of the anticipated completion date.","8","4.2","LS (S2-150704) on VoLTE Roaming and Replies",10190,"Postponed","2015-03-18T08:02:35.027","2015-03-18T08:13:46.870","","S2-151434","","","","","","","","",null,null,null,"PSMC 131 Doc 201","S2-151121"]
["S2-150705","LS from GSMA RILTE: LS to 3GPP on IMS Emergency Session over WLAN","GSMA RILTE","Maurice Pope",648,"LS in","","","GSMA Networks Group (NG) RILTE has recently concluded the work on creating VoWiFi profile (IR.51). In conjunction with that work, Networks Group RILTE has discussed scenarios pertaining to IMS Emergency Session support over WLAN (EPC Integrated). The underlying assumption is that IMS Emergency sessions can be established over WLAN for deployments supporting VoWiFi. Due to lack of 3GPP specifications on this topic, RILTE would like to request 3GPP to review the following requirements identified and provide guidance: 1. Providing access to EPC over WLAN to support an emergency session 2. Support for determination of location during emergency call 3. Roaming scenarios and ePDG selection 4. Emergency handover between WLAN and 3GPP access 5. Support for unauthenticated emergency calls over WLAN 6. Support for UE undetected emergency calls over WLAN. Action: GSMA Networks Group RILTE kindly requests SA WG1 to confirm the above requriements and SA WG2 to provide guidance on how they are/will","41","6.17","Feasibility study on the Support of Emergency services over WLAN (FS_SEW)",13600,"Treated","2015-03-18T08:02:35.043","2015-03-18T08:13:46.933","","","","","","","","","","",null,null,null,"RILTE #43 Doc 121","S2-151431"]
["S2-150706","LS from CT WG1: Reply LS on provision of WLAN identifiers for RAN rule","CT WG1","Maurice Pope",648,"LS in","","","CT WG1 thanks for RAN WG2 LS pointing on the conflict between RAN WG2 and CT WG1 specification regarding WLAN identifiers provided for RAN rule from E-UTRAN to the UE. CT WG1 has discussed this issue but did not agree the related CRs to align with RAN WG2 agreement. Several companies had concern that according to IEEE 802.11-2012, the HESSID and SSID should be used together when both are available from the WLAN access point. Furthermore, in an LS to CT WG1 (please see attached), IEEE recommended using HESSID in conjunction with SSID. However, one company believes that frequent and serious misoperation was not identified. CT WG1 kindly asks RAN WG2 to clarify the rationale behind excluding the option of using HESSID and SSID together as recommended by IEEE.","17","5.3","Non-3GPP Access Maintenance",10790,"Noted","2015-03-18T08:02:35.043","2015-03-18T08:13:47.010","","","Rel-12","","","","","","","",null,null,null,"C1-150841"]
["S2-150707","LS from CT WG1: LS on Addition of proximity services group identifier","CT WG1","Maurice Pope",648,"LS in","","","CT WG1 discussed a contribution which proposes to add an identifier ('Service Group Identifier') to the PC5_DISCOVERY message to discriminate the group of proximity services to which the ProSe Application ID identified by the announced ProSe Application Code belongs. The goal is to allow a UE with limited resources (e.g. an MTC UE) monitoring for a Public Safety service to apply the discovery filter only when the contained Application Code is related to a Public Safety service; which would allow saving processing and energy resources for such UEs. It was commented that such extension would require the evolution of the stage 2. Action: CT WG1 kindly asks SA WG2 if the evolution discussed above requires modification to stage 2.","15","5.1","3GPP Packet Access Maintenance",10500,"Treated","2015-03-18T08:02:35.043","2015-03-18T08:13:47.057","","","Rel-12","","","","","","","",null,null,null,"C1-150879","S2-151326"]
["S2-150708","LS from CT WG1: Clarification regarding change of active time value and periodic TAU or RAU timer value for UE supporting PSM","CT WG1","Maurice Pope",648,"LS in","","","CT WG1 would like to clarify the following requirements mentioned in the clause 4.5.4 for TS 23.682. Requirement 1: If the UE wants to change the Active Time value, e.g. when not content with the value provided in the Attach or TAU/RAU Accept, the UE requests the value it wants in the TAU/RAU procedure. Requirement 2: If the UE wants to change the periodic TAU/RAU Timer value, e.g. when not content with the value provided in the Attach or TAU/RAU Accept, the UE requests the value it wants in the TAU/RAU procedure. Question 1: Does the above requirement allow the UE to initiate tracking area procedure or Routing area procedure immediately when the UE wants to change the Active time value or Periodic TAU/RAU timer even when PSM is activated? There have been concerns in CT WG1 from some companies that UEs can stick on repeatedly requesting an Active time value by TAU/RAU which is not provided by the network and this may end up in a signalling storm. Question 2: If the answer to question","15","5.1","3GPP Packet Access Maintenance",10430,"Treated","2015-03-18T08:02:35.060","2015-03-18T08:13:47.120","","","Rel-12","","","","","","","",null,null,null,"C1-150880","S2-151384"]
["S2-150709","LS from CT WG1: Reply LS on PLMN reselection for ProSe","CT WG1","Maurice Pope",648,"LS in","","","CT WG1 would like to inform SA WG2 that CT WG1 has discussed the options identified by SA WG2 to address the multi-carrier scenario across PLMNs, and intends to specify Option 2. Action: CT WG1 kindly asks SA WG2 to take the above information into account.","15","5.1","3GPP Packet Access Maintenance",10460,"Postponed","2015-03-18T08:02:35.077","2015-03-18T08:13:47.183","","S2-151435, S2-151444","Rel-12","","","","","","","",null,null,null,"C1-150886"]
["S2-150710","LS from CT WG3: LS Reply to LS related to Mobile VoIP IMS Roaming","CT WG3","Maurice Pope",648,"LS in","","","CT WG3 thanks SA WG3-LI for the LS. SA WG3-LI has requested CT WG3 to provide details to SA WG3 LI for assessments on the impacts on the ability to meet LI obligations when CT WG3 and GSMA NG begin to work to address the output of the network 2020 project task force. CT WG3 will only start to work on any new requirements resulting from the ongoing GMSA studies after stage 2 requirements have been agreed in 3GPP. While CT WG3 is responsible for documenting the IMS Network to Network Interface (II-NNI), the scope of our related specifications is at this moment not including S8 based roaming: - 3GPP TS 29.165 is limited to SIP aspects of the II-NNI, and only considers IMS based roaming. For S8 based roaming, SIP as used over the UNI (between the UE and the P-CSCF) would be applicable. This is not covered in TS 29.165 so far. - The scope the 3GPP TR 29.949 'Study on Technical aspects on Roaming End-to-end scenarios with VoLTE IMS and other networks' is limited to SIP aspects of the RAVEL","8","4.2","LS (S2-150704) on VoLTE Roaming and Replies",10230,"Noted","2015-03-18T08:02:35.077","2015-03-18T08:13:47.230","","","Rel-12","","","","","","","",null,null,null,"C3-150256"]
["S2-150711","LS from CT WG3: LS on Enable MB2 authorization","CT WG3","Maurice Pope",648,"LS in","","","CT WG3 have discussed the authorization of the GCS AS for making use of the supported procedures over the MB2-C interface, such as TMGI allocation/deallocation and MBMS bearer procedures. It is required that the BM-SC per supported procedure mentioned above determine whether the GCS AS is authorized to make use of this procedure or not. The mutual authentication between the GCS AS and BM-SC over MB2-C is defined in TS 33.246 Annex N. Once the involved nodes are authenticated it is assumed that a secure connection is established between these nodes. The nodes are also authorized in the security domains to communicate with respective node. 1. CT WG3 kindly ask SA WG3 if there is a need to provide an additional mechanism to authorize the application server over the MB2-C interface? 2. CT WG3 kindly ask SA WG3 if a new proposed AVP to convey the identity of the GCS AS for authorization purposes within MB2-C Diameter procedures towards the BM-SC can help to authorize the GCS AS in the BM-S","15","5.1","3GPP Packet Access Maintenance",10360,"Postponed","2015-03-18T08:02:35.077","2015-03-18T08:14:21.953","","S2-151436","Rel-12","","","","","","","",null,null,null,"C3-150424"]
["S2-150712","LS from CT WG3: LS on Flow ID supplied by GCS AS","CT WG3","Maurice Pope",648,"LS in","","","CT WG3 has discussed the stage 3 impacts of CR 55 against TS 23.468 agreed by SA WG2 in their recent meeting in San Francisco (S2-144533). In this CR, SA WG2 adds the option for the GCS AS to provide the Flow ID in the Activate MBMS Bearer Request. The reasoning of that CR argues that this is required to enable location dependent services. This issue has already been discussed in a joined session between SA WG2 and CT WG3 in Phoenix (see S2-141843, Question 5). At that time, CT WG3 argued that 'TS 23.246 states that Flow Ids are assigned by the BM-SC. Flow Ids seem to have no fixed configured meaning in the RAN but are rather dynamically allocated. They are used if the same service (as identified by TMGI) requires different content to be delivered to different service areas. It thus appears unclear what benefit the GCS AS would gain from providing Flow Ids. To the contrary, allowing two network entities to allocate identifiers from the same range bears the risk of conflicts and compli","15","5.1","3GPP Packet Access Maintenance",10610,"Postponed","2015-03-18T08:02:35.090","2015-03-18T08:14:22.017","","S2-151437","Rel-12","","","","","","","",null,null,null,"C3-150446","S2-151100"]
["S2-150713","LS from CT WG3: Reply LS on End-to-end QoS handling of MTSI","CT WG3","Maurice Pope",648,"LS in","","","CT WG3 would like to thank SA WG4 for obtaining an early opportunity to comment the requirements for End-to-end QoS handling of MTSI suggested in SA WG4´s LS. CT WG3 thanks SA WG4 for the LS on TR 26.924 Study on improved end-to-end QoS handling. CT WG3 already commented on clause 5 of that document and thanks SA WG4 for taking those comments into consideration. CT WG3 has now analysed some of the provided use cases from a stage 3 PCC perspective and would like to provide additional comments. Although no specific solutions are provided in the Technical Report yet, some suggestions are mentioned for some use cases. CT WG3 would like to comment on the identified PCC impacts for the following aspects: a) Bandwidth negotiation in a second Offer-Answer This second negotiation is considered relevant for those cases when multiple codecs or specific conditions for a codec are being negotiated. CT WG3 would like to comment that this solution would work according to current PCC procedures and n","7","4.1","Common issues and Incoming LSs",10060,"Noted","2015-03-18T08:02:35.090","2015-03-18T08:14:22.077","","","","","","","","","","",null,null,null,"C3-150450"]
["S2-150714","LS from TSG GERAN: LS on New WID on RAN aspects for improvements to CS/PS coordination in GERAN Shared Networks","TSG GERAN","Maurice Pope",648,"LS in","","","TSG GERAN would like to inform SA WG2 that we have approved the Rel-13 building block CSPS_Coord_GERAN and therefore it can now be included within the work item CSPS_Coord. Action: TSG GERAN kindly asks SA WG2 to take the above into account.","7","4.1","Common issues and Incoming LSs",10050,"Noted","2015-03-18T08:02:35.107","2015-03-18T08:14:22.140","","","","","","","","","","",null,null,null,"GP-150278"]
["S2-150715","LS from GERAN WG2: LS on extended DRX in idle mode","GERAN WG2","Maurice Pope",648,"LS in","","","GERAN WG2 is studying power savings for MTC devices within the scope of two ongoing study items, Power Savings for MTC devices (FS_uPOD) and the Cellular IoT study item (FS_IoT_LC) and has identified extended DRX in idle mode as a candidate solution. In this context the SGSN will need to send a paging request to the BSS which will then be relayed over the radio interface by the BSS according to the eDRX cycle being used by the target device. However, it is unclear how the SGSN knows when to send the page to the BSS since the paging occurrence of a device within the context of eDRX may occur tens of minutes into the future from the point where the BSS receives the paging request. Furthermore, it is unclear how to guarantee that a device will not miss a page while moving between cells of the same Routing Area since the occurrence of its nominal paging group occurs at different times in different cells when these cells are not synchronized. GERAN kindly requests feedback on this issue in","39","6.15","Feasibility study on Extended DRX cycle for Power Consumption Optimization (FS_eDRX)",0,"Postponed","2015-03-18T08:02:35.107","2015-03-18T08:14:22.187","","S2-151438","Rel-13","","","","","","","",null,null,null,"GP-150311"]
["S2-150716","LS from TSG GERAN: Reply LS on paging for MTC","TSG GERAN","Maurice Pope",648,"LS in","","","GERAN thanks SA WG2 for the LS on paging for MTC. GERAN has reviewed the LS and concluded that within the Cellular IoT study item (FS_IoT_LC), where multiple solutions are being studied, there is in general a need for similar system enhancements for paging message transmission to devices belonging to different coverage classes (i.e. requiring different coverage enhancements). GERAN has reviewed the questions and some answers are provided below: Q1: Is the eNB expected to determine the required amount of coverage enhancement techniques based only on static information (such as UE radio capability) or also dynamic information e.g. whether they are in good or bad coverage? Answer: The amount of coverage enhancement to use is expected to be based on dynamic information. A UE can potentially detect a change in its required coverage enhancement at any time in idle or packet transfer mode and will convey this information to the core network. Q2: Is there benefit to store the information abou","15","5.1","3GPP Packet Access Maintenance",10370,"Treated","2015-03-18T08:02:35.123","2015-03-18T08:14:22.250","","","Rel-13","","","","","","","",null,null,null,"GP-150312","S2-151383"]
["S2-150717","LS from TSG GERAN: Reply LS on MBMS for Message delivery to Group of devices","TSG GERAN","Maurice Pope",648,"LS in","","","TSG GERAN thanks SA WG2 for their LS (S2-150421/GP-150065) on MBMS for Message delivery to Group of devices. TSG GERAN wish to notify SA WG2 the following: - MBMS is supported in GERAN specifications from Release 6 - no test cases have been defined - no MS implementation is known to support GERAN MBMS Therefore, GERAN MBMS is not a viable option for Message delivery to a Group of devices. Action: TSG GERAN asks SA WG2 to take the above into account.","31","6.7","Group based Enhancements (GROUPE)",11930,"Noted","2015-03-18T08:02:35.123","2015-03-18T08:14:22.297","","","Rel-13","","","","","","","",null,null,null,"GP-150313"]
["S2-150718","LS from GERAN WG2: Reply LS on Security Framework for Cellular IoT","GERAN WG2","Maurice Pope",648,"LS in","","","GERAN WG2 thanks SA WG3 for their reply LS (S3-151198/GPC150096) on Security Framework for Cellular IoT. GERAN WG2 wish to clarify SA WG3's understanding: any CIoT system need not be a standalone network in the sense that a network implies core network plus radio access network. CIoT is a Radio Access Technology. GERAN WG2 has reviewed the questions and some answers are provided below. Q1: Whether roaming needs to be supported in Cellular IoT? If so, then is it expected that UEs will roam between countries where encryption is allowed and countries where encryption is not used? GERAN WG2 Answer: In our understanding yes is the answer for both questions. Q2: Should SA WG3 develop the security assuming that there will be some inter-RAT interactions in the future? GERAN WG2 Answer: No. Inter-RAT mobility is not supported. This includes both idle mode and connected mode mobility. Owing to the ultra-low device complexity target of the CIoT work, GERAN WG2 does not anticipate changing this v","7","4.1","Common issues and Incoming LSs",10130,"Noted","2015-03-18T08:02:35.137","2015-03-18T08:14:22.343","","","Rel-13","","","","","","","",null,null,null,"GPC150120"]
["S2-150719","LS from GERAN WG2: Response LS on work split for Study on Cellular IoT","GERAN WG2","Maurice Pope",648,"LS in","","","GERAN WG2 would like to thank SA WG3 for the work they have done so far on the Cellular Internet of Things topic in their living document in S3-151195. GERAN WG2 note SA WG3's request for guidance from SA plenary on the work split between SA and GERAN, and GERAN WG2 would like to provide the following information: a) In GPC150120, GERAN WG2 has responded to the questions in the LS in S3-151198(GPC150096). b) In the work under the FS_IoT_LC study item, GERAN is examining and comparing evolution of the GSM Radio Access Network and clean-slate radio access network concept(s). In all the approaches, the radio access networks are intended to connect to a 3GPP core network using either the Gb interface or the S1 interface; utilize the associated NAS protocols in TSs 24.008 or 24.301; and use USIM based security. Hence from GERAN WG2 perspective we do not foresee the need for any change to the existing work split between SA, CT, RAN and GERAN as a result of FS_IoT_LC. c) Existing GERAN devic","7","4.1","Common issues and Incoming LSs",10140,"Noted","2015-03-18T08:02:35.137","2015-03-18T08:14:22.420","","","Rel-13","","","","","","","",null,null,null,"GPC150122"]
["S2-150720","LS from RAN WG1: Reply LS on Paging for MTC","RAN WG1","Maurice Pope",648,"LS in","","","RAN WG1 thanks SA WG2 for the reply LS in S2-150697 on paging for MTC. RAN WG1 discussed the questions from SA WG2 and provided the following answers: Question 1: Is the eNB expected to determine the required amount of coverage enhancement techniques based only on static information (such as UE radio capability) or also dynamic information e.g. whether they are in good or bad coverage? Answer: In order to determine the required amount of the coverage enhancement techniques, both the UE radio capability and information about the UE's current coverage situation are required. The UE radio capability on whether it supports coverage enhancement techniques does not change. Note that a UE with coverage enhancement capability is not necessarily in extended coverage. The required amount of coverage enhancement can be practically stable for some users, but changing for some other users. RAN WG1 has not yet discussed granularity of coverage enhancements for paging transmissions. Question 2: Is t","15","5.1","3GPP Packet Access Maintenance",10380,"Treated","2015-03-18T08:02:35.153","2015-03-18T08:14:46.887","","","Rel-13","","","","","","","",null,null,null,"R1-190924","S2-151383"]
["S2-150721","LS from RAN WG1: Response LS on public safety discovery","RAN WG1","Maurice Pope",648,"LS in","","","RAN WG1 would like to thank SA WG2 for their LS R1-150695(S2-150691) on public safety discovery. RAN WG1 notes that RAN WG1 has not studied UE-Network relay which is within the scope of the approved Rel-13 WID. Accordingly, the analysis below is not applicable for UE-Network relay discovery. RAN WG1 will provide guidance regarding the RAN solution for UE-Network relay discovery at a future meeting. RAN WG1 would like to note the following technical aspects based on the Rel-12 design for comparison of using Rel-12 discovery or Rel-12 communication as transport channels for PS discovery. [...] Action: RAN WG1 would respectfully like to ask SA WG2 to take the above into consideration for designing public safety discovery.","34","6.10","Extended Proximity-based Services TR Phase (eProSe-Ext-SA2TR)",12320,"Noted","2015-03-18T08:02:35.153","2015-03-18T08:14:46.933","","","Rel-13","","","","","","","",null,null,null,"R1-150948"]
["S2-150722","LS from RAN WG2: Reply LS on provision of WLAN identifiers for RAN rule","RAN WG2","Maurice Pope",648,"LS in","","","RAN WG2 thanks for CT WG1 LS on CT WG1's understanding with regard to WLAN identifiers provided for RAN rule from (E-)UTRAN to the UE. RAN WG2 has discussed the issue again and agreed that for each entry in the list of WLAN identities for RAN rule, the network may signal SSID, BSSID, HESSID, or any combination of them. RAN WG2 believes that with this change, the RAN WG2 specification is consistent with the recommendation from CT WG1. RAN WG2 kindly asks CT WG1 to take the above agreement and the attachment into account.","17","5.3","Non-3GPP Access Maintenance",10780,"Noted","2015-03-18T08:02:35.170","2015-03-18T08:14:47.027","","","Rel-12","","","","","","","",null,null,null,"R2-150684"]
["S2-150723","LS from RAN WG2: Reply LS on eMPS-eMLPP in CSFB to GERAN","RAN WG2","Maurice Pope",648,"LS in","","","RAN WG2 thanks SA WG2 for the LS on eMPS-eMLPP in CSFB to GERAN (R2-150016/S2-144358) on the discrepancy between TS 23.272 and TS 36.331 related to the usage of CSFB high priority indicator received from the MME by the eNB. RAN WG2 discussed the case where the eNB may provide the UE with GERAN carrier as target carrier when performing a RRC Connection Release with redirection, but the UE might still connect to UTRAN autonomously e.g., when the UE does not have GERAN coverage at this time. However, RAN WG2 concluded this is a special case with small probability and decided not to update the RAN WG2 specification to allow inclusion of CSFB high priority indication for re-direction to GERAN. Action: RAN WG2 respectfully asks SA WG2 to take note of the RAN WG2 decision and consider an update SA WG2 specification if required.","18","5.4","IMS-Related Maintenance",10840,"Noted","2015-03-18T08:02:35.170","2015-03-18T08:14:47.090","","","Rel-11","","","","","","","",null,null,null,"R2-150691"]
["S2-150724","LS from RAN WG2: LS reply on PLMN reselection for ProSe","RAN WG2","Maurice Pope",648,"LS in","","","RAN WG2 would like to thank SA WG2 for the LS R2-150024/S2-150664 on PLMN selection for ProSe. RAN WG2 would also like to thank CT WG1 for the LS R2-150031/ C1-150886 on PLMN selection for ProSe. The Access Stratum ProSe protocol does not consider the PLMN so far. For any of the three options RAN WG2 consider the impact to AS protocols to be minor, if any. Therefore, RAN WG2 suggests SA WG2 and CT WG1 to select their preferred option and to inform RAN WG2 about the decision. Action: RAN WG2 respectfully asks SA WG2 and CT WG1 take the reply provided above into account.","15","5.1","3GPP Packet Access Maintenance",10470,"Postponed","2015-03-18T08:02:35.183","2015-03-18T08:14:47.137","","S2-151439","Rel-12","","","","","","","",null,null,null,"R2-150695"]
["S2-150725","LS from RAN WG2: LS on ProSe direct discovery announcements","RAN WG2","Maurice Pope",648,"LS in","","","RAN WG2 has discussed the issue whether UE can keep announcing the ProSe direct discovery message including the same ProSe Application Code (PAC). The current UE Access Stratum (AS) behaviours are such that once AS layer receives the discovery message from upper layer, depending on configuration it transmits the message up to 4 times in a discovery period. Then, it is RAN WG2 understanding that upper layer should take care of announcing discovery message multiple times while the concerned PAC is valid.","15","5.1","3GPP Packet Access Maintenance",10480,"Noted","2015-03-18T08:02:35.183","2015-03-18T08:14:47.200","","","Rel-12","","","","","","","",null,null,null,"R2-150696"]
["S2-150726","LS from RAN WG2: LS on SC-PTM transmission","RAN WG2","Maurice Pope",648,"LS in","","","At RAN WG2#89, RAN WG2 discussed the newly approved Study Item 'Support of Single-cell PTM transmission in LTE' (see RP-142205), which studies provisioning of multicast via PDSCH on a per cell basis, instead of providing multicast via PMCH over the whole MBSFN area. RAN WG2 assumes that SC-PTM reuses the MBMS system architecture and acts as a complementary bearer type of MBMS. RAN WG2 is targeting GCSE requirements (and MCPTT if available) for the SC-PTM transmission. RAN WG2 noticed that the SA WG2 Study Item 'Study on MBMS Enhancements' is considering 'improvements to allow establishment of MBMS bearers using target area information (e.g. a list of cell identifiers), as distinct from using an MBMS Service Area'. RAN WG2 would like to focus on radio interface enhancements, and would like RAN WG3 to support the study of the potential impacts on architecture and network interfaces for SC-PTM. In order for the SC-PTM transmission to work, RAN WG2 would like SA WG2 and RAN WG3 to provide","38","6.14","MBMS Enhancements (MBMS_enh)",13140,"Treated","2015-03-18T08:02:35.183","2015-03-18T08:14:47.247","","","Rel-13","","","","","","","",null,null,null,"R2-150709","S2-151102"]
["S2-150727","LS from RAN WG2: LS reply on support for ProSe one-to-one communication in Release 13","RAN WG2","Maurice Pope",648,"LS in","","","RAN WG2 thanks SA WG6 for their LS on support for ProSe one-to-one communication in Release 13. RAN WG2 discussed the topic and agreed the following reply to SA WG6's question: Question 1: Will a ProSe one-to-one communication service be supported in Release 13? RAN WG2 reply: RAN WG2 has not yet started Rel-13 work. Although the Rel-12 ProSe WI focus has been on ProSe one-to-many communication, addressing for ProSe one-to-one communication can be realized e.g. by using a Layer-2 ID addressing only a single target UE as the Destination Layer-2 ID. It is noted that Destination Layer-2 ID is 24 bits long, which is provided by upper layer. RAN WG2 respectfully suggests SA6 to continue to liaise with both RAN WG2 and SA WG2 for further details regarding possible Rel-13 enhancements that may be relevant for one-to-one communication.","26","6.2","Mission Critical Push-to-Talk over LTE (MCPTT)",11120,"Noted","2015-03-18T08:02:35.200","2015-03-18T08:14:47.310","","","Rel-13","","","","","","","",null,null,null,"R2-150710"]
["S2-150728","LS from RAN WG3: Response LS on Paging Optimization","RAN WG3","Maurice Pope",648,"LS in","","","RAN WG3 has discussed the LS referenced here-above to provide guidance on how to limit both MME and radio interface paging load. RAN WG3 acknowledges the issue and has started to discuss possible solutions to solve it, also taking into account enhancement for small cell deployment. RAN WG3 has not yet finalized and will inform SA WG2 when RAN WG3 has reached a conclusion. Action: RAN WG3 kindly ask SA WG2 to take note of the above.","7","4.1","Common issues and Incoming LSs",10110,"Noted","2015-03-18T08:02:35.200","2015-03-18T08:14:47.357","","","Rel-13","","","","","","","",null,null,null,"R3-150461"]
["S2-150729","LS from RAN WG3: Response LS on Support of a mix of IPv4 and IPv6 eNBs and Backhauls in eMBMS","RAN WG3","Maurice Pope",648,"LS in","","","RAN WG3 has discussed the LS referenced here-above. In order to allow flexibility in deployment scenarios, RAN WG3 has decided that when the MCE receives an Alternative TNL information IE from the MME, the MCE may send the content of that IE to the eNB and when the eNB receives two IP Multicast destination addresses of different version it selects the one to be used. The attached CRs are technically endorsed by RAN WG3. There was no consensus in RAN WG3 to agree the CRs and send them to RAN for approval due to the timeline consideration. RAN WG3 just starts release 13. Action: RAN WG3 kindly ask SA WG2 to take note of the above.","7","4.1","Common issues and Incoming LSs",10100,"Noted","2015-03-18T08:02:35.217","2015-03-18T08:14:47.403","","","Rel-13","","","","","","","",null,null,null,"R3-150489"]
["S2-150730","LS from RAN WG4: LS on impact of optional preconfigured parameters for D2D out of Network coverage mode","RAN WG4","Maurice Pope",648,"LS in","","","In reading the current release 12 text in TS 23.303 there is a clear statement in section 4.5.1.1.2.3.1 indicating the UE shall support setting Geographical Areas, and NOTE 5 of that section provides guidelines on how it should be used. The concern RAN WG4 has is section 4.5.1.1.2.3.2 states the optional provisioning of the Geographical Area parameters. The 3GPP standard needs to include mandatory mechanisms to ensure that the UE meets local regulatory requirements. The most critical of these is prevent the UE from operating illegally in areas and on frequencies where it is not authorized by the Operator/ local regulatory body. Also, the standard must ensure the appropriate out of band emissions are met everywhere that the UE is or could be operating. To meet these requirements, the UE needs to know its location and whether the network operator permits D2D operations. Due to the challenges outlined above RAN WG4 has decided that: When a ProSe UE is out-of-coverage and does not have kn","15","5.1","3GPP Packet Access Maintenance",10410,"Noted","2015-03-18T08:02:35.217","2015-03-18T08:15:11.463","","","Rel-12","","","","","","","",null,null,null,"R4-151170"]
["S2-150731","LS from TSG RAN: LS on Consequence of RAN WI prioritisation for UPCON work in SA2","TSG RAN","Maurice Pope",648,"LS in","","","The decision in SA WG2 on the normative phase for a part of the SA WG2 UPCON work, namely 'Flow priority-based traffic differentiation on the same QCI (FPI)', has been waiting for feedback on its feasibility from a TSG RAN point of view. As a result of the Rel-13 prioritization of Work Items and Study Items during the RAN#67 plenary meeting, TSG RAN would like to inform TSG SA and SA WG2 that RAN WG2 and RAN WG3 will not be able to study the feasibility of this solution before June 2015. Whether such a feasibility study can be done by RAN WG2 and RAN WG3 in future will depend on the outcome of WI/SI prioritization discussions during future TSG RAN plenary meetings. Action: TSG RAN asks SA WG2 to take the above information into account in its discussion on finalizing the 'Flow priority-based traffic differentiation on the same QCI (FPI)' solution.","23","6.1.2","Rel-13 PCC/QoS Maintenance",11090,"Noted","2015-03-18T08:02:35.230","2015-03-18T08:15:11.510","","","Rel-13","","","","","","","",null,null,null,"RP-150514"]
["S2-150732","LS from TSG RAN: LS on D2D off network operations","TSG RAN","Maurice Pope",648,"LS in","","","At RAN WG4#74 in Athens RAN WG4 had considerable discussion on ensuring that UE's meet local regulatory requirements. The most critical of these is prevent the UE from operating illegally in areas and on frequencies where it is not authorized by the Operator/ local regulatory body. Also, the standard must ensure the appropriate out of band emissions are met everywhere that the UE is or could be operating. To meet these requirements, the UE needs to know its location and whether the network operator permits D2D operations. Due to the challenges outlined above RAN decided that: When a ProSe UE is out-of-coverage and does not have knowledge of its geographical area the UE is not permitted to transmit. The method that a UE uses to determine its location is left to implementation. Additionally, there is no need to define pre-configured radio parameters that are not associated with any known Geographical Area. RAN requests CT WG1 to align the language in TS 24.334 with the RAN decision.","15","5.1","3GPP Packet Access Maintenance",10510,"Noted","2015-03-18T08:02:35.230","2015-03-18T08:15:11.570","","","Rel-12","","","","","","","",null,null,null,"RP-150516"]
["S2-150733","LS from SA WG1: Reply LS on eCall implementation in IMS","SA WG1","Maurice Pope",648,"LS in","","","SA WG1 would like to thank CT WG1 for their LS in which they raise the question about 'the status of the requirements for IMS based eCall service and for eCall service using IMS Centralized Services.' TS 22.101 defines the requirements for emergency calls, eCall as well as ICS. Clause 22 on ICS states the following: 'ICS shall not limit the ICS user's capability to make emergency calls.' Furthermore there are no requirements that would restrict eCall or emergency calls in that context. As such SA WG1 concludes that all requirements for eCall also apply for ICS. With regards to the status of the requirements for an IMS based eCall service SA WG1 would like to state that current specifications do not contain any requirements. Dependent on company contributions related work may be started within the Release 14 timeframe.","7","4.1","Common issues and Incoming LSs",10070,"Noted","2015-03-18T08:02:35.247","2015-03-18T08:15:11.633","","","Rel-13","","","","","","","",null,null,null,"S1-150001"]
["S2-150734","LS from SA WG1: Reply LS on end-to-end WebRTC-IMS security","SA WG1","Maurice Pope",648,"LS in","","","SA WG1 thanks SA WG3 for their LS on end to end WebRTC-IMS security. SA WG1 considers the liberal interpretation of the SA WG1 requirement (e2ae), as proposed by SA WG3 to be adequate to meet LI regulations when necessary. 2. A liberal interpretation of the SA 1 requirement means encryption at all paths and points between WebRTC clients. This can include hop-by-hop encryption as long as every hop has a sufficient form of encryption. This view can be deployed by an operator in such a fashion as to meet the TSG SA 3 LI requirements described above, but will effectively constitute an e2ae configuration. SA WG1 further considers that the language used in the requirements and supporting text allows the use of end to end (e2e) WebRTC security when LI regulations do not apply.","33","6.9","Enhancements to WEBRTC interoperability (eWebRTCi)",0,"Noted","2015-03-18T08:02:35.247","2015-03-18T08:15:11.697","","","Rel-13","","","","","","","",null,null,null,"S1-150212"]
["S2-150735","LS from SA WG1: LS reply on service continuity","SA WG1","Maurice Pope",648,"LS in","","","SA WG1 thanks SA WG6 for their LS on service continuity. SA WG1 discussed the topic of potentially related service continuity requirements for ProSe and MCPTT and the SA WG1 response is per below. 1. SA WG6 respectfully asks SA WG1 to clarify whether MCPTT service continuity is implied and/or desirable for the case where MCPTT UE switches between EPC path and ProSe Communication path (requirements R-7.14-001, R-7.14-002, R-7.14-003). SA WG1 reply: MCPTT is largely focused on group voice services and in this scenario, when a UE goes off network, the ProSe Communication would allow that UE to communicate with others within ProSe Communication range, however the other group members may not be in ProSe Communication range; hence service continuity may not be possible. 2. SA WG6 respectfully asks SA WG1 to clarify whether MCPTT service continuity is implied and/or desirable for the case where MCPTT UE, prior to automatically going off network, attempts to make use of a ProSe UE-to-Network","34","6.10","Extended Proximity-based Services TR Phase (eProSe-Ext-SA2TR)",12330,"Noted","2015-03-18T08:02:35.263","2015-03-18T08:15:11.760","","","Rel-13","","","","","","","",null,null,null,"S1-150296"]
["S2-150736","LS from SA WG1: LS on MCPTT core items selection","SA WG1","Maurice Pope",648,"LS in","","","At SA WG1#69, interested 3GPP individual members identified MCPTT modules they considered necessary in order to provide a viable deployable MCPTT service. The results of this exercise is provided in the attachment. Action: SA WG1 asks that SA WG2 and SA WG6 take this information into account in their work on MCPTT.","26","6.2","Mission Critical Push-to-Talk over LTE (MCPTT)",11150,"Noted","2015-03-18T08:02:35.277","2015-03-18T08:15:11.837","","","Rel-13","","","","","","","",null,null,null,"S1-150340"]
["S2-150737","LS from SA WG3: LS on end-to-end WebRTC-IMS security","SA WG3","Maurice Pope",648,"LS in","","","Based on SA WG3 LI evaluation of the SA WG1 requirement [3GPP TS 22.228] to allow for the end to end user traffic security between WebRTC clients using IMS services and capabilities, the SA WG3 seeks clarifications on the following: In discussion of the realization of the end to end traffic security requirement between WebRTC clients using IMS services and capabilities, two different interpretations were presented: 1. A strict interpretation is that this requirement means end-to-end encryption between WebRTC clients using IMS services and capabilities. If this is the correct view, then the possible solutions conflict with the two following Lawful Interception requirements: a. Non-detectability - in this scenario, a subject of LI's traffic security would be re-directed to an access edge (e2ae). This change in behaviour for LI does not meet the TSG SA 3 LI requirement that LI shall not be detectable or observable by the target. b. Reporting content in decrypted form - in this scenario,","33","6.9","Enhancements to WEBRTC interoperability (eWebRTCi)",0,"Noted","2015-03-18T08:02:35.277","2015-03-18T08:15:11.917","","","Rel-13","","","","","","","",null,null,null,"S3-151162"]
["S2-150738","LS from SA WG3: Reply LS on Security Framework for Cellular IoT","SA WG3","Maurice Pope",648,"LS in","","","SA WG3 thank GERAN WG2 for their LS (GP-140717/S3-151007) on Security Framework for Cellular IoT. SA WG3 has started to consider security for Cellular IoT (CIoT) and several questions have arisen during this work. GERAN WG2, SA WG1 and SA WG2 are requested to respond to the following questions (please note that not all groups are expected to respond to each question). SA WG3 asks GERAN WG2, SA WG1 and SA WG2: Q1: Whether roaming needs to be supported in Cellular IoT? If so, then is it expected that UEs will roam between countries where encryption is allowed and countries where encryption is not used? SA WG3 understands that CIoT is being developed as a standalone network but would like to know what to assume in the long run. Q2: Should SA WG3 develop the security assuming that there will be some inter-RAT interactions in the future? Q3: Is it expected that subscriptions used to access CIoT will be used to access other networks? Q4: Are there any requirements in CIoT to provide securit","7","4.1","Common issues and Incoming LSs",10170,"Treated","2015-03-18T08:02:35.293","2015-03-18T08:15:11.977","","","Rel-13","","","","","","","",null,null,null,"S3-151198","S2-151382"]
["S2-150739","LS from SA WG3: LS on work split for Study on Cellular IoT","SA WG3","Maurice Pope",648,"LS in","","","SA WG3 was asked by TSG GERAN to 'develop the security framework for Cellular IoT' and provide 'guidance on the architecture considerations', cf. GP-140717/S3-151007. SA WG3 has created a living document on security enhancements for Cellular Internet of Things (S3-151195). However, the discussions have revealed that SA WG3 would need to consider use cases and architecture. Corresponding questions were sent in an LS to GERAN WG2, SA WG1 and SA WG2, cf. S3-151198. SA WG3 would like to ask TSG SA plenary for guidance on what is the work split between SA and GERAN groups for the study on Cellular IoT.","7","4.1","Common issues and Incoming LSs",10150,"Noted","2015-03-18T08:02:35.293","2015-03-18T08:15:12.040","","","","","","","","","","",null,null,null,"S3-151201"]
["S2-150740","LS from SA WG4: LS on TR 26.924 Study on improved end-to-end QoS handling","SA WG4","Maurice Pope",648,"LS in","","","SA WG4 has progressed the study on improved end-to-end QoS handling and have updated draft TR 26.924. The latest version of TR 26.924 (v0.1.7) is attached. The version sent in the previous LS was v0.1.1. The updates compared to v0.1.1 are: - Updates based on feedback from previous reviews - Added Use case K for EVS codec - Added recommended requirements - Various editorial changes Both a clean version of the latest TR and a diff version (compared to v0.1.1) are attached. SA WG4 would request SA WG2, CT WG1, CT WG3 and CT WG4 to review the new version of the TR and provide feedback where needed. Action: SA WG2, CT WG1, CT WG3 and CT WG4 are requested to review the TR and provide feedback where needed.","7","4.1","Common issues and Incoming LSs",10080,"Treated","2015-03-18T08:02:35.310","2015-03-18T08:15:36.973","","","Rel-13","","","","","","","",null,null,null,"S4-150163","S2-151425"]
["S2-150741","LS from SA WG4: LS reply on codec support in IMS-WebRTC","SA WG4","Maurice Pope",648,"LS in","","","SA WG4 thanks CT WG1 for their LS on codec support in IMS-WebRTC. Since WebRTC IMS Clients in 3GPP UEs are used for real-time multimedia communication, and since transcoding has negative impacts on quality and consumes resources, SA WG4 recommendation is that WebRTC IMS clients in 3GPP UEs are required to comply with TS 26.114. Hence, for speech, WebRTC IMS clients in 3GPP UE - shall support AMR; - shall support AMR-WB if wideband speech is supported; - should support EVS and shall support EVS if super-wideband and fullband speech is supported. For video, WebRTC IMS client in 3GPP UE shall support H.264 CBP Level 1.2 and should support H.264 CBP Level 3.1 and HEVC (H.265). Since the reference to draft-ietf-rtcweb-overview excluding codec aspects is within 3GPP TS 24.371, SA WG4 suggests specification of these recommendations in an attached draft CR to TS 24.371.","18","5.4","IMS-Related Maintenance",10830,"Noted","2015-03-18T08:02:35.327","2015-03-18T08:15:37.020","","","Rel-12","","","","","","","",null,null,null,"S4-150224"]
["S2-150742","LS from SA WG6: LS on support for ProSe one-to-one communication in Release 13","SA WG6","Maurice Pope",648,"LS in","","","The current proposed solution for the MCPTT Private Call functionality in the draft TR 23.779 'Study on architectural enhancements to support Mission Critical Push to Talk over LTE (MCPTT)' states the intention of using the ProSe one-to-one communication service. However, the recently approved D2D Release 13 RAN WID (RP-142311) does not indicate support for one-to-one communication, either at the physical layer or at a higher layer. SA WG6 would like to ask RAN WG2 the following question: Question 1: Will a ProSe one-to-one communication service be supported in Release 13?","26","6.2","Mission Critical Push-to-Talk over LTE (MCPTT)",11130,"Noted","2015-03-18T08:02:35.327","2015-03-18T08:15:37.083","","","Rel-13","","","","","","","",null,null,null,"S6-150076"]
["S2-150743","LS from SA WG6: LS on service continuity","SA WG6","Maurice Pope",648,"LS in","","","SA WG6 has identified that selected MCPTT Stage 1 requirements in TS 22.179 may be related to ProSe service continuity Stage 1 requirements in TS 22.278. Please refer to a list of potentially related requirements in the Annex A of this liaison. Some companies in SA WG6 were of the opinion that these MCPTT Stage 1 requirements do not necessarily imply service continuity and/or had concerns about potential overlap between service continuity solutions defined as part of ProSe (in SA WG2) with 'upper layer' service continuity solutions defined as part of MCPTT. SA WG6 understands that SA WG2 has not yet made any agreements on ProSe-level service continuity solutions in TR 23.713. Question 1: SA WG6 respectfully asks SA WG1 to clarify whether MCPTT service continuity is implied and/or desirable for the case where MCPTT UE switches between EPC path and ProSe Communication path (requirements R-7.14-001, R-7.14-002, R-7.14-003). Question 2: SA WG6 respectfully asks SA WG1 to clarify whether M","26","6.2","Mission Critical Push-to-Talk over LTE (MCPTT)",11140,"Noted","2015-03-18T08:02:35.340","2015-03-18T08:15:37.147","","","Rel-13","","","","","","","",null,null,null,"S6-150100"]
["S2-150744","LS from TSG SA: LS on I-WLAN specification maintenance","TSG SA","Maurice Pope",648,"LS in","","","In the context of promoting 3GPP specifications to Rel-12, TSG SA discussed the maintenance of I-WLAN feature and the related specifications. The earlier decision from TSG SA #64 to discontinue the maintenance of the I-WLAN feature was documented in SP-140397 and was re-confirmed. Also the requirement to avoid conflicts between I-WLAN and other WLAN interworking methods introduced in later releases still holds. TSG SA has decided not to discontinue any of the I-WLAN related specifications that still exist in release 12. TSG SA did not yet decide whether the existing I-WLAN specifications should also be part of Rel-13. Any decision on inclusion of any I-WLAN specifications in Rel-13 should take place in TSG SA. However, for those I-WLAN specifications not being maintained it is important to capture in the scope the following points: - WLAN interworking specified in 3GPP TS 23.402 and specifications dependent on it supersede I-WLAN from release 12 - Maintaining of I-WLAN feature stops f","17","5.3","Non-3GPP Access Maintenance",10770,"Noted","2015-03-18T08:02:35.340","2015-03-18T08:15:37.207","","","Rel-12","","","","","","","",null,null,null,"SP-150158"]
["S2-150745","LS from TSG SA: Reply LS on work split for Study on Cellular IoT","TSG SA","Maurice Pope",648,"LS in","","","TSG SA thanks SA WG3 and GERAN WG2 for the LS on work split for Study on Cellular IoT. The TSG SA - TSG GERAN joint session concluded and subsequently TSG SA approved three activities to support Cellular IoT work within TSG SA: 1) Potential security enhancements for Gb 2) Potential security enhancements to support end-to-end security model, which is common for different radio technologies 3) Potential architecture enhancements to support Cellular IoT requirements, which is common for different radio technologies It is worth mentioning that the above activities do not prevent GERAN FS_IoT_LC Study continuing. The decision of normative architecture related matters pertaining to the 'clean slate' proposals may need to involve other TSGs. Action: TSG SA kindly requests SA WG2 and SA WG3 to take the above information into account and proceed with the above activities.","7","4.1","Common issues and Incoming LSs",10160,"Noted","2015-03-18T08:02:35.357","2015-03-18T08:15:37.303","","","Rel-13","","","","","","","",null,null,null,"SP-150170"]
["S2-150746","Tutorial for use of the 3G Ultimate TD allocation tools","SA WG2 Secretary","Maurice Pope",648,"other","","","This tutorial provides some information on the use of the 3GPP Portal for TD and CR number allocation, the upload of documents and consultation of Document lists for meeting using the 3G Ultimate (3GU) tools. These instructions are based on the on-line tutorial at: http://www.3gpp.org/ftp/webExtensions/3GU/3GU_instructions_for_delegates/ats00000.htm","6","4","General",10040,"Noted","2015-03-18T10:25:59.760","2015-03-19T13:56:24.903","","","","","","","","","","","","","","",""]
["S2-150747","Enhancements to Solution 2","Ericsson","Shabnam Sultana",21207,"pCR","","","This contribution includes further clarification and editorial changes to Solution 2","33","6.9","Enhancements to WEBRTC interoperability (eWebRTCi)",12100,"Revised","2015-03-23T13:58:28.077","2015-04-06T13:07:27.613","","S2-151153","Rel-13","23.706","","eWebRTCi","","","","","","","","",""]
["S2-150748","Evaluation Criteria For Solution 2","Ericsson","Shabnam Sultana",21207,"pCR","","","This contribution completes the evaluation criteria for Solution 2","33","6.9","Enhancements to WEBRTC interoperability (eWebRTCi)",12110,"Revised","2015-03-23T13:58:28.093","2015-04-06T13:07:27.643","","S2-151169","Rel-13","23.706","","eWebRTCi","","","","","","","","",""]
["S2-150749","High Level Solution 2 Description","Ericsson","Shabnam Sultana",21207,"pCR","","","This contribution completes the high level description of the Ericsson Solution 2","33","6.9","Enhancements to WEBRTC interoperability (eWebRTCi)",12120,"Available","2015-03-23T13:58:28.093","2015-04-06T13:07:27.690","","","Rel-13","23.706","","eWebRTCi","","","","","","","","",""]
["S2-150750","Mandatory use of Geographical Areas","Ericsson, Sprint, Qualcomm Incorporated, LG Electronics, U.S. Department of Commerce, Home Office","Shabnam Sultana",21207,"CR","","","Summary of change: Geographical Area made mandatory in the Radio parameters for when the UE is 'not served by E-UTRAN' provisioning for ProSe Direct Discovery and ProSe Direct Communication.","15","5.1","3GPP Packet Access Maintenance",10600,"Revised","2015-03-23T13:58:28.110","2015-04-06T13:07:27.720","","S2-151324","Rel-12","23.303","12.4.0","ProSe","0158","","F",null,"","","","",""]
["S2-150751","LS reply on End to End QoS handling","Ericsson","Shabnam Sultana",21207,"LS out","","","LS reply to LS from SA WG4 on improved end to end QoS handling","7","4.1","Common issues and Incoming LSs",10090,"Revised","2015-03-24T20:46:36.277","2015-04-07T13:16:42.297","","S2-151308","Rel-13","","","","","","","","S2-150740","SA WG4","CT WG3"]
["S2-150752","Monitoring via PCRF","Ericsson","Shabnam Sultana",21207,"CR","","","Summary of change: Reporting current user location and communication failure via PCRF as defined in 23.203.","30","6.6","Monitoring Enhancements (MONTE)",12870,"Revised","2015-03-24T20:46:36.290","2015-04-07T12:59:28.507","","S2-151215","Rel-13","23.682","13.1.0","MONTE","0093","","B",null,"","","","",""]
["S2-150753","Semantics of the Traffic Steering Policy","Ericsson, AT&T, Nokia Networks, Orange","Shabnam Sultana",21207,"pCR","","","Proposes a Traffic Steering Rule over St interface","37","6.13","Flexible Mobile Service Steering (FMSS)",0,"Revised","2015-03-24T20:46:36.383","2015-04-07T12:59:28.557","","S2-151166","Rel-13","23.718","","FMSS","","","","","","","","",""]
["S2-150754","Clarifications for QoS change of default bearer","Huawei, Hisilicon","Mirko Schramm",23396,"CR","","","Summary of change: It is proposed to clarify the requirements for the PCRF and the PCEF/BBERF related to the default bearer QoS change due to a PCRF provisioning of the Authorized Default EPS Bearer QoS parameter. In clause 6.1.1.4 (Bearer Binding) it is","16","5.2","QoS and PCC Maintenance",10940,"Revised","2015-03-27T14:20:02.123","2015-04-07T13:44:29.267","S2-150383","S2-151206","Rel-12","23.203","12.8.0","SAES, TEI12","0940","3","F",null,"","","","",""]
["S2-150755","Clarifications for QoS change of default bearer","Huawei, Hisilicon","Mirko Schramm",23396,"CR","","","Rel-13 mirror CR: Summary of change: It is proposed to clarify the requirements for the PCRF and the PCEF/BBERF related to the default bearer QoS change due to a PCRF provisioning of the Authorized Default EPS Bearer QoS parameter. In clause 6.1.1.4 (Bea","16","5.2","QoS and PCC Maintenance",10970,"Revised","2015-03-27T14:23:03.330","2015-04-07T13:44:29.297","S2-150384","S2-151207","Rel-13","23.203","13.3.0","SAES, TEI12","0941","3","A",null,"","","","",""]
["S2-150756","Priority of Default Bearer","Huawei, Hisilicon, Applied Communication Sciences, OEC","Mirko Schramm",23396,"CR","","","Summary of change: It is proposed to extend clause 6.1.1.3 (PCC rule authorization and QoS rule generation) with a general requirement for the PCRF to ensure that the ARP of the default bearer needs to be permanently aligned with the highest ARP used by","16","5.2","QoS and PCC Maintenance",11000,"Revised","2015-03-27T14:24:46.383","2015-04-07T13:44:29.347","S2-150385","S2-151268","Rel-12","23.203","12.8.0","eMPS, TEI12","0890","7","F",null,"","","","",""]
["S2-150757","Priority of Default Bearer","Huawei, Hisilicon, Applied Communication Sciences, OEC","Mirko Schramm",23396,"CR","","","Rel-13 mirror CR: Summary of change: It is proposed to extend clause 6.1.1.3 (PCC rule authorization and QoS rule generation) with a general requirement for the PCRF to ensure that the ARP of the default bearer needs to be permanently aligned with the hi","16","5.2","QoS and PCC Maintenance",11020,"Revised","2015-03-27T14:27:16.360","2015-04-07T13:44:29.377","S2-150386","S2-151269","Rel-13","23.203","13.3.0","eMPS, TEI12","0905","5","A",null,"","","","",""]
["S2-150758","Solution update for setting up an AS session with required QoS","Huawei, HiSilicon, Alcatel-Lucent, Intel","Mirko Schramm",23396,"pCR","","","This contribution completes the solution description.","29","6.5","Architecture Enhancements for Service Exposure (AESE)",11610,"Revised","2015-03-27T14:46:03.990","2015-04-07T13:45:20.433","","S2-151222","Rel-13","23.708","","AESE","","","","","","","","",""]
["S2-150759","Solution update for change of chargeable party","Huawei, HiSilicon","Mirko Schramm",23396,"pCR","","","This contribution completes the solution description.","29","6.5","Architecture Enhancements for Service Exposure (AESE)",11620,"Revised","2015-03-27T14:48:02.207","2015-04-07T13:45:20.467","","S2-151239","Rel-13","23.708","","AESE","","","","","","","","",""]
["S2-150760","Solution update for informing about UE’s connection properties","Huawei, HiSilicon","Mirko Schramm",23396,"pCR","","","This contribution updates the solution description and proposes a new alternative.","29","6.5","Architecture Enhancements for Service Exposure (AESE)",11630,"Revised","2015-03-27T14:50:05.350","2015-04-07T13:45:20.513","","S2-151240","Rel-13","23.708","","AESE","","","","","","","","",""]
["S2-150761","Solution update for background data transfer","Huawei, HiSilicon, NTT DOCOMO","Mirko Schramm",23396,"pCR","","","This contribution updates the solution description and proposes a new alternative.","29","6.5","Architecture Enhancements for Service Exposure (AESE)",11640,"Revised","2015-03-27T14:52:24.907","2015-04-07T13:45:20.543","","S2-151242","Rel-13","23.708","","AESE","","","","","","","","",""]
["S2-150762","IOPS network configuration/establishment","General Dynamics UK Ltd.","Philip Young",27298,"pCR","","","This contribution proposes text to resolve the Editor's Note relating to dynamic establishment of IOPS networks","40","6.16","Feasibility study on IOPS (FS_IOPS_St2)",13470,"Revised","2015-03-27T16:35:08.840","2015-03-30T14:51:48.017","","S2-151315","Rel-13","23.797","","FS_IOPS_St2","","","","","","","","",""]
["S2-150763","Clarification of applicable UE mobility procedures","General Dynamics UK Ltd.","Philip Young",27298,"pCR","","","This contribution proposes text to clarify the applicable UE mobility procedures in the full range of possible cell transition scenarios","40","6.16","Feasibility study on IOPS (FS_IOPS_St2)",13480,"Revised","2015-03-27T16:44:40.510","2015-03-30T14:51:48.050","","S2-151338","Rel-13","23.797","","FS_IOPS_St2","","","","","","","","",""]
["S2-150764","Support of public safety services over an IOPS network","General Dynamics UK Ltd.","Philip Young",27298,"pCR","","","This contribution proposes text to clarify the manner in which public safety services should be supported over an IOPS network and proposes an LS to SA WG3 and SA WG6","40","6.16","Feasibility study on IOPS (FS_IOPS_St2)",13490,"Revised","2015-03-27T16:46:29.957","2015-03-30T14:51:48.097","","S2-151339","Rel-13","23.797","","FS_IOPS_St2","","","","","","","","",""]
["S2-150765","[DRAFT] LS on support of public safety services over an IOPS network","General Dynamics UK Limited","Philip Young",27298,"LS out","","","LS to SA WG6 and SA WG3 informing them of SA WG2 decisions regarding the manner in which public safety services will be supported over IOPS networks","40","6.16","Feasibility study on IOPS (FS_IOPS_St2)",0,"Revised","2015-03-27T16:50:15.267","2015-03-30T14:51:47.987","","S2-151340","Rel-13","","","","","","","",null,"SA WG6, SA WG3","-"]
["S2-150766","NBIFOM operation Modes","Verizon, Oracle","Uri Baniel",40054,"pCR","","","Enable the operator (via the PCRF) to either accept or reject the request of the UE for NBIFOM operation mode of UE-Initiated mode.","28","6.4","IP Flow Mobility support for S2a and S2b interfaces (NBIFOM)",0,"Revised","2015-03-30T21:36:27.530","2015-03-30T21:49:34.900","","S2-151224","","23.861","","NBIFOM","","","","","","","","",""]
["S2-150767","APN and group specific NAS Level congestion control","NTT DOCOMO","SRISAKUL THAKOLSRI",42550,"CR","","","Summary of change: Adding criteria to detect NAS signalling congestion associated with the group of UEs belong to the same group ID and subscribed to particular APN.","31","6.7","Group based Enhancements (GROUPE)",13350,"Revised","2015-04-01T07:56:46.410","2015-04-07T07:55:10.443","","S2-151172","Rel-13","23.401","13.2.0","GROUPE","2843","","B",null,"","","","",""]
["S2-150768","APN and group specific NAS level congestion control","NTT DOCOMO","SRISAKUL THAKOLSRI",42550,"CR","","","Summary of change: Adding criteria to detect NAS signalling congestion associated with the group of MSs belong to the same group ID and subscribed to particular APN.","31","6.7","Group based Enhancements (GROUPE)",13380,"Revised","2015-04-01T08:08:39.313","2015-04-07T07:55:10.410","","S2-151173","Rel-13","23.060","13.2.0","GROUPE","1956","","B",null,"","","","",""]
["S2-150769","Issue for eDRX","Acer Incorporated, ITRI","Pei-jung Chen",59891,"pCR","","","This document proposes to add an issue to the TR for FS_eDRX","39","6.15","Feasibility study on Extended DRX cycle for Power Consumption Optimization (FS_eDRX)",13310,"Revised","2015-04-01T10:24:21.053","2015-04-07T09:30:31.147","","S2-151230","","23.770","","FS_eDRX","","","","","","","","",""]
["S2-150770","Discussion of Match report issue for User permission change","Acer Incorporated, ITRI","Pei-jung Chen",59891,"other","","","This paper proposes to discuss and address the match report issue during user permission change period.","34","6.10","Extended Proximity-based Services TR Phase (eProSe-Ext-SA2TR)",12340,"Noted","2015-04-01T10:29:12.667","2015-04-07T10:07:59.677","","","","","","","","","","","","","","",""]
["S2-150771","PCRF obligations at Default EPS Bearer QoS change","Ericsson","Shabnam Sultana",21207,"CR","","","Summary of change: The risk of accidental termination of the default bearer is mitigated by requiring the BBF to bind at least one PCC/QoS rule to the default bearer, provided there is at laest one PCC/QoS rule that can bind to the default bearer. For IP-CAN session modification with Default EPS Bearer QoS change, any method that ensures that there is least one PCC/QoS rule with a matching QoS is allowed. In particular PCRF can be configured to know that the PCEF is configured to take care of the change locally, so that no PCC rule operation from the PCRF is necessary.","16","5.2","QoS and PCC Maintenance",11040,"Merged","2015-04-01T12:38:57.907","2015-04-07T12:03:26.140","","","Rel-12","23.203","12.8.0","SAES, TEI12","0973","","F",null,"","","","",""]
["S2-150772","PCRF obligations at Default EPS Bearer QoS change","Ericsson","Shabnam Sultana",21207,"CR","","","Rel-12 mirror CR: Summary of change: The risk of accidental termination of the default bearer is mitigated by requiring the BBF to bind at least one PCC/QoS rule to the default bearer, provided there is at laest one PCC/QoS rule that can bind to the default bearer. For IP-CAN session modification with Default EPS Bearer QoS change, any method that ensures that there is least one PCC/QoS rule with a matching QoS is allowed. In particular PCRF can be configured to know that the PCEF is configured to take care of the change locally, so that no PCC rule operation from the PCRF is necessary.","16","5.2","QoS and PCC Maintenance",11050,"Noted","2015-04-01T12:38:57.967","2015-04-07T12:03:26.173","","","Rel-12","23.203","12.8.0","SAES, TEI12","0974","","A",null,"","","","",""]
["S2-150773","Updates to Annex on PC5 interface","Ericsson","Shabnam Sultana",21207,"pCR","","","Updates to Annex on PC5 to reflect correct explanation & RAN WG1 feedback","34","6.10","Extended Proximity-based Services TR Phase (eProSe-Ext-SA2TR)",12300,"Revised","2015-04-01T12:38:58.013","2015-04-06T13:34:53.263","","S2-151314","Rel-13","23.713","","eProSe-Ext-SA2TR","","","","","","","","",""]
["S2-150774","PLMN Selection","Ericsson","Shabnam Sultana",21207,"pCR","","","Propose a change of how PLMN selection is done by the Public Safety user","40","6.16","Feasibility study on IOPS (FS_IOPS_St2)",13510,"Revised","2015-04-01T12:38:58.030","2015-04-06T13:34:53.307","","S2-151316","Rel-13","23.797","","FS_IOPS_St2","","","","","","","","",""]
["S2-150775","IOPS PDN/APN handling","Ericsson","Shabnam Sultana",21207,"pCR","","","aligns APN/PDN handling with basic procedures for LTE","40","6.16","Feasibility study on IOPS (FS_IOPS_St2)",13520,"Noted","2015-04-01T12:38:58.030","2015-04-06T13:34:53.323","","","Rel-13","23.797","","FS_IOPS_St2","","","","","","","","",""]
["S2-150776","Restriction of UEs not allowed in IOPS PLMN","Ericsson","Shabnam Sultana",21207,"pCR","","","define how to bar unauthorised UEs for IOPS","40","6.16","Feasibility study on IOPS (FS_IOPS_St2)",13530,"Revised","2015-04-01T12:38:58.047","2015-04-06T13:34:53.370","","S2-151319","Rel-13","23.797","","FS_IOPS_St2","","","","","","","","",""]
["S2-150777","Discussion on High Latency communication","Ericsson","Shabnam Sultana",21207,"other","","","This paper discusses high latency communication","36","6.12","Optimizations to Support High Latency Communications (FS_HLCom)",12810,"Noted","2015-04-01T12:38:58.047","2015-04-07T13:01:34.820","","","Rel-13","","","","","","","","","","","",""]
["S2-150778","Conclusions for HL_Com","Ericsson, Qualcomm Incorporated","Shabnam Sultana",21207,"pCR","","","This P-CR adds conclusions for the FS_HLCOM study","36","6.12","Optimizations to Support High Latency Communications (FS_HLCom)",12820,"Revised","2015-04-01T12:38:58.060","2015-04-07T13:01:34.853","","S2-151176","Rel-13","23.709","","FS_HLcom","","","","","","","","",""]
["S2-150779","Clean-up on HL_Com TR","Ericsson","Shabnam Sultana",21207,"pCR","","","This P-CR updates solutions in the TR","36","6.12","Optimizations to Support High Latency Communications (FS_HLCom)",12830,"Revised","2015-04-01T12:38:58.060","2015-04-07T13:01:34.900","","S2-151155","Rel-13","23.709","","FS_HLcom","","","","","","","","",""]
["S2-150780","Way forward on DECOR","Ericsson","Shabnam Sultana",21207,"other","","","Updates compared to DECOR baseline CRs in SA WG2#107","27","6.3","Dedicated Core Networks (DECOR)",11170,"Available","2015-04-01T12:38:58.060","2015-04-07T15:20:16.577","","","Rel-13","","","","","","","","","","","",""]
["S2-150781","Introduce the Dedicated Core Network (DECOR) feature","Ericsson","Shabnam Sultana",21207,"CR","","","Summary of change: Introduce the DECOR feature based on conclusions of TR 23.707","27","6.3","Dedicated Core Networks (DECOR)",11690,"Merged","2015-04-01T12:38:58.077","2015-04-07T16:48:02.213","","","Rel-13","23.401","13.2.0","DECOR","2844","","B",null,"","","","",""]
["S2-150782","Introduce the Dedicated Core Network (DECOR) feature","Ericsson","Shabnam Sultana",21207,"CR","","","Summary of change: Introduce the decor feature based on conclusions of TR 23.707.","27","6.3","Dedicated Core Networks (DECOR)",11780,"Merged","2015-04-01T12:38:58.140","2015-04-07T16:48:02.293","","","Rel-13","23.060","13.2.0","DECOR","1957","","B",null,"","","","",""]
["S2-150783","Load rebalancing within Dedicated Core Network (DECOR)","Ericsson","Shabnam Sultana",21207,"CR","","","Summary of change: Introduce the decor feature based on conclusions of TR 23.707 Added an informative annex as an example of how to optimize selection of DECOR nodes","27","6.3","Dedicated Core Networks (DECOR)",11760,"Merged","2015-04-01T12:38:58.187","2015-04-07T15:20:16.610","","","Rel-13","23.236","12.0.0","DECOR","0052","","B",null,"","","","",""]
["S2-150784","Handling of UE-initiated and NW-initiated NBIFOM modes","Ericsson, Huawei, HiSilicon","Shabnam Sultana",21207,"pCR","","","Provides further details and resolutions to the UE-initiated and NW-initiated NBIFOM modes and procedures","28","6.4","IP Flow Mobility support for S2a and S2b interfaces (NBIFOM)",11410,"Revised","2015-04-01T12:38:58.247","2015-04-07T14:12:21.410","","S2-151225","Rel-13","23.861","","NBIFOM","","","","","","","","",""]
["S2-150785","Updates to solution with policy steering interface","Ericsson, AT&T, KDDI, Nokia Networks, Orange","Shabnam Sultana",21207,"pCR","","","Proposes updates and further details to the solution with St policy steering interface","37","6.13","Flexible Mobile Service Steering (FMSS)",0,"Revised","2015-04-01T12:38:58.263","2015-04-07T14:05:40.207","","S2-151147","Rel-13","23.718","","FMSS","","","","","","","","",""]
["S2-150786","Call flows for the solution with service steering policy interface","Ericsson","Shabnam Sultana",21207,"pCR","","","This contribution proposes call flows for the FMSS solution with service steering policy interface","37","6.13","Flexible Mobile Service Steering (FMSS)",12980,"Revised","2015-04-01T12:38:58.263","2015-04-07T13:50:23.490","","S2-151164","Rel-13","23.718","","FMSS","","","","","","","","",""]
["S2-150787","ProSe UE to network Relay & Service continuity solution","Ericsson","Shabnam Sultana",21207,"pCR","","","Provides full solution for Service continuity in ProSe","34","6.10","Extended Proximity-based Services TR Phase (eProSe-Ext-SA2TR)",12310,"Noted","2015-04-01T12:38:58.280","2015-04-06T15:16:41.127","","","Rel-13","23.713","","eProSe-Ext-SA2TR","","","","","","","","",""]
["S2-150788","Application reporting functionality for FMSS solution","Cisco, Allot Communications, Huawei, HiSilicon, Sprint, Comverse, Sandvine Incoporated, US cellular, Broadcom Corporation","Nirav Salot",56645,"pCR","","","This contribution proposes various alternatives to resolve the editor's note on the support of application reporting functionality for FMSS solution.","37","6.13","Flexible Mobile Service Steering (FMSS)",12990,"Revised","2015-04-02T05:47:42.683","2015-04-07T10:20:14.263","","S2-151146","Rel-13","23.718","","FMSS","","","","","","","","",""]
["S2-150789","Mandatory functionality over the Sd interface","Cisco, Allot Communications, Sprint, Comverse, Sandvine Incoporated, US cellular, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell","Nirav Salot",56645,"pCR","","","This paper provides various stage 2 and stage 3 references to highlight that only Application detection function is mandatorily defined over the Sd interface.","37","6.13","Flexible Mobile Service Steering (FMSS)",13000,"Revised","2015-04-02T05:47:42.683","2015-04-07T10:20:14.297","","S2-151150","Rel-13","23.718","","FMSS","","","","","","","","",""]
["S2-150790","Enforcement of traffic steering policy","Cisco, Allot Communications, Huawei, HiSilicon, Sprint, Comverse, Sandvine Incoporated, US cellular, Broadcom Corporation, Alcatel-Lucent and Alcatel-Lucent Shanghai Bell","Nirav Salot",56645,"pCR","","","This paper provides high level description of the enforcement of the traffic steering policy by solution 1.1 and solution 1.2.","37","6.13","Flexible Mobile Service Steering (FMSS)",13010,"Revised","2015-04-02T05:47:42.697","2015-04-07T10:20:14.233","","S2-151162","Rel-13","23.718","","FMSS","","","","","","","","",""]
["S2-150791","Procedures, interface details and evaluation details for Sd/Gx based solutions","Allot Communications, Cisco, Huawei, Hisilicon, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, SPRINT, Comverse, Sandvine Incorporated, US Cellular, Broadcom Corporation, Openet Telecom","Alla Goldner",42718,"pCR","","","This paper provides description of procedures; resolves Editor's Notes related to interface enhancements and introduces more description into evaluation sections.","37","6.13","Flexible Mobile Service Steering (FMSS)",13020,"Revised","2015-04-02T06:27:43.030","2015-04-07T11:05:55.987","","S2-151148","Rel-13","23.718","","FMSS-SA2TR","","","","","","","","",""]
["S2-150792","Steering Rule for Uplink/Downlink Traffic","Huawei, Hisilicon, Cisco, Allot Communications, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Sprint, Comverse, Openet Telecom","Shufeng Shi",56675,"pCR","","","Updates the definition of steering rules applied to Gx and Sd based solution for uplink and downlink traffic.","37","6.13","Flexible Mobile Service Steering (FMSS)",13030,"Revised","2015-04-02T07:18:12.663","2015-04-07T11:40:08.593","","S2-151179","Rel-13","23.718","","FMSS-SA2TR","","","","","","","","",""]
["S2-150793","Add Location report action into delete bearer procedure","Huawei, HiSilicon","Runze Zhou",60945,"CR","","","Summary of change: Add clarification that the location change reporting may be controlled by the PGW at the PDN GW initiated dedicated bearer deactivation procedure.","15","5.1","3GPP Packet Access Maintenance",10870,"Noted","2015-04-02T12:34:10.873","2015-04-03T06:54:45.197","","","Rel-12","23.401","12.8.0","SAES, TEI12","2845","","F",null,"","","","",""]
["S2-150794","Add Location report action into delete bearer procedure","Huawei, HiSilicon","Runze Zhou",60945,"CR","","","Rel-13 mirror CR: Summary of change: Add clarification that the location change reporting may be controlled by the PGW at the PDN GW initiated dedicated bearer deactivation procedure.","15","5.1","3GPP Packet Access Maintenance",10880,"Revised","2015-04-02T12:34:10.967","2015-04-03T06:54:45.243","","S2-151134","Rel-13","23.401","13.2.0","TEI12","2846","","A",null,"","","","",""]
["S2-150795","Infinite loop in rerouting to dedicated networks - discussion","NEC","Iskren Ianev",59515,"other","","","This paper looks at a rerouting scenario where the rerouting to dedicated networks procedure ends in infinite loop.","27","6.3","Dedicated Core Networks (DECOR)",11210,"Available","2015-04-02T12:57:34.957","2015-04-07T09:32:12.657","","","Rel-13","","","","","","","","","","","",""]
["S2-150796","Rerouting when dedicated network is not available","NEC","Iskren Ianev",59515,"CR","","","Summary of change: Proposes a DECOR rerouting flag to be introduced in the eNB to MME interface to indicate that the requested dedicated core network is not available.","27","6.3","Dedicated Core Networks (DECOR)",11730,"Noted","2015-04-02T13:03:28.907","2015-04-07T11:09:53.997","","","Rel-13","23.401","13.2.0","DECOR","2847","","F",null,"","","","",""]
["S2-150797","Correction to the NAS message rerouting","NEC","Iskren Ianev",59515,"CR","","","Summary of change: Before a decision to reroute, add an extra check at the rerouting (default) MME whether a dedicated network of the UE Usage Type is supported in the MME Pool (i.e. in the MME service area).","27","6.3","Dedicated Core Networks (DECOR)",11870,"Available","2015-04-02T13:08:53.133","2015-04-07T10:24:40.293","","","Rel-13","23.401","13.2.0","DECOR","2848","","F",null,"","","","",""]
["S2-150798","Correction to the NAS message rerouting","NEC","Iskren Ianev",59515,"CR","","","Summary of change: Before a decision to reroute, add an extra check at the rerouting (default) SGSN wheather a dedicated network of the UE Usage Type is supported in the SGSN Pool (i.e. in the SGSN service area).","27","6.3","Dedicated Core Networks (DECOR)",11880,"Available","2015-04-02T13:12:56.583","2015-04-07T10:25:37.233","","","Rel-13","23.060","13.2.0","DECOR","1958","","F",null,"","","","",""]
["S2-150799","Proposed assumption for ProSe Service Continuity","Qualcomm Incorporated, Ericsson, Huawei, U.S. Department of Commerce","Hong Cheng",25668,"pCR","","","This contribution proposes an assumption regarding the ProSe Service Continuity and clarifies its relationship with application layer service continuity solutions.","34","6.10","Extended Proximity-based Services TR Phase (eProSe-Ext-SA2TR)",12350,"Noted","2015-04-02T14:45:09.913","2015-04-07T01:58:29.060","","","Rel-13","23.713","","eProSe-Ext-SA2TR","","","","","","","","",""]
["S2-150800","Extended DRX in Idle mode","Ericsson","Shabnam Sultana",21207,"pCR","","","This document discusses system wide implications from the introduction of support for extended DRX for UE in Idle mode and provides a solution proposal.","39","6.15","Feasibility study on Extended DRX cycle for Power Consumption Optimization (FS_eDRX)",13320,"Revised","2015-04-02T15:19:59.143","2015-04-07T14:05:40.223","","S2-151231","Rel-13","23.770","","FS_eDRX","","","","","","","","",""]
["S2-150801","Correcting SM re-activation attempts at PLMN change when only one IP version is supported by the network","TeliaSonera, Ericsson","Shabnam Sultana",21207,"CR","","","Summary of change: This change request aligns the stage 2 text to the change to the re-activation condition in stage 3, and also aligns stage 2 text to subscription or GGSN/PDN GW restrictions in stage 3.","15","5.1","3GPP Packet Access Maintenance",10900,"Agreed","2015-04-02T15:19:59.143","2015-04-07T12:04:09.587","S2-150163","","Rel-12","23.060","12.8.0","TEI12","1950","1","F",null,"","","","",""]
["S2-150802","Correcting SM re-activation attempts at PLMN change when only one IP version is supported by the network","TeliaSonera, Ericsson","Shabnam Sultana",21207,"CR","","","Rel-13 mirror CR: Summary of change: This change request aligns the stage 2 text to the change to the re-activation condition in stage 3, and also aligns stage 2 text to subscription or GGSN/PDN GW restrictions in stage 3.","15","5.1","3GPP Packet Access Maintenance",10910,"Agreed","2015-04-02T15:19:59.317","2015-04-07T12:04:09.617","S2-150164","","Rel-13","23.060","13.2.0","TEI12","1951","1","A",null,"","","","",""]
["S2-150803","Correcting ESM re-activation attempts at PLMN change when only one IP version is supported by the network","TeliaSonera, Ericsson","Shabnam Sultana",21207,"CR","","","Summary of change: This change request aligns the stage 2 text to the stage 3 change to the re-activation condition.","15","5.1","3GPP Packet Access Maintenance",10920,"Agreed","2015-04-02T15:19:59.517","2015-04-07T12:04:09.633","S2-150165","","Rel-12","23.401","12.8.0","TEI12","2830","1","F",null,"","","","",""]
["S2-150804","Correcting ESM re-activation attempts at PLMN change when only one IP version is supported by the network","TeliaSonera, Ericsson","Shabnam Sultana",21207,"CR","","","Rel-13 mirror CR: Summary of change: This change request aligns the stage 2 text to the stage 3 change to the re-activation condition.","15","5.1","3GPP Packet Access Maintenance",10930,"Agreed","2015-04-02T15:19:59.720","2015-04-07T12:04:32.533","S2-150166","","Rel-13","23.401","13.2.0","TEI12","2831","1","A",null,"","","","",""]
["S2-150805","Configuration of extended DRX for connected mode","Ericsson","Shabnam Sultana",21207,"pCR","","","This paper addresses the issue of configuration of the relevant network nodes enabling usage of eDRX in Connected mode","39","6.15","Feasibility study on Extended DRX cycle for Power Consumption Optimization (FS_eDRX)",13330,"Revised","2015-04-02T15:19:59.923","2015-04-07T13:54:11.653","","S2-151258","Rel-13","23.770","","FS_eDRX","","","","","","","","",""]
["S2-150806","Solution for Handling of Mobile Terminated Data (Idle mode)","Ericsson","Shabnam Sultana",21207,"pCR","","","WITHDRAWN: Solution for Handling of Mobile Terminated Data (Idle mode)","55","99","Reserved and Withdrawn documents",13940,"Withdrawn","2015-04-02T15:19:59.923",null,"","","Rel-13","23.770","","FS_eDRX","","","","","","","","",""]
["S2-150807","GTP-C re-transmissions (Connected mode)","Ericsson","Shabnam Sultana",21207,"pCR","","","This document proposes a solution for GTP-C retransmissions when UE is in connected mode","39","6.15","Feasibility study on Extended DRX cycle for Power Consumption Optimization (FS_eDRX)",13340,"Approved","2015-04-02T15:19:59.923","2015-04-07T13:54:11.700","","","Rel-13","23.770","","FS_eDRX","","","","","","","","",""]
["S2-150808","GTP-C re-transmissions (Idle mode)","Ericsson","Shabnam Sultana",21207,"pCR","","","This document proposes a solution for GTP-C retransmissions (idle mode)","39","6.15","Feasibility study on Extended DRX cycle for Power Consumption Optimization (FS_eDRX)",13350,"Approved","2015-04-02T15:19:59.940","2015-04-07T13:54:11.733","S2-150255","","Rel-13","23.770","","FS_eDRX","","","","","","","","",""]
["S2-150809","Interaction between eDRX and PSM (Power Saving Mode)","Ericsson","Shabnam Sultana",21207,"pCR","","","This document proposes a solution for the issue number 7 for Idle Mode DRX 'Interaction between eDRX and PSM (Power Saving Mode)'","39","6.15","Feasibility study on Extended DRX cycle for Power Consumption Optimization (FS_eDRX)",13360,"Noted","2015-04-02T15:19:59.953","2015-04-07T13:54:11.780","","","Rel-13","23.770","","FS_eDRX","","","","","","","","",""]
["S2-150810","Identity used in NAS level congestion control","Ericsson","Shabnam Sultana",21207,"CR","","","Summary of change: The group identifier used in Group specific NAS level congestion control is changed to Congestion Control Group Identifer, and some various alignments of the text is done.","31","6.7","Group based Enhancements (GROUPE)",13330,"Noted","2015-04-02T15:19:59.953","2015-04-07T13:54:11.810","","","Rel-13","23.060","13.2.0","GROUPE","1959","","F",null,"","","","",""]
["S2-150811","Identity used in NAS level congestion control","Ericsson","Shabnam Sultana",21207,"CR","","","Summary of change: The group identifier used in Group specific NAS level congestion control is changed to Congestion Control Group Identifer, and some various alignments of the text is done. Rows added for HSS data and MME MM context.","31","6.7","Group based Enhancements (GROUPE)",13340,"Noted","2015-04-02T15:20:00.033","2015-04-07T13:54:11.857","","","Rel-13","23.401","13.2.0","GROUPE","2849","","F",null,"","","","",""]
["S2-150812","Group Priority","Ericsson","Shabnam Sultana",21207,"pCR","","","Provides soln for Group Priority","34","6.10","Extended Proximity-based Services TR Phase (eProSe-Ext-SA2TR)",12360,"Revised","2015-04-02T15:20:00.097","2015-04-07T13:54:11.903","","S2-151607","Rel-13","23.713","","eProSe-Ext-SA2TR","","","","","","","","",""]
["S2-150813","Predictable UE communication pattern","Ericsson","Shabnam Sultana",21207,"pCR","","","Proposes some changes and clarifications for solution 5.","29","6.5","Architecture Enhancements for Service Exposure (AESE)",11650,"Revised","2015-04-02T15:20:00.110","2015-04-07T14:05:40.257","","S2-151223","Rel-13","23.708","","AESE","","","","","","","","",""]
["S2-150814","Reflections on monitoring events from MME","Ericsson","Shabnam Sultana",21207,"pCR","","","WITHDRAWN: Reflections on monitoring events from MME","55","99","Reserved and Withdrawn documents",13880,"Withdrawn","2015-04-02T15:20:00.110",null,"","","Rel-13","23.682","","MONTE","","","","","","","","",""]
["S2-150815","Reference Version of FMSS TR 23.718","Ericsson","Tao Sun",54129,"pCR","","","Provide the latest Version 0.2.0 of TR 23.718 for FMSS","37","6.13","Flexible Mobile Service Steering (FMSS)",13040,"Noted","2015-04-02T15:24:45.700","2015-04-07T16:08:25.813","","","Rel-13","23.718","","FMSS","","","","","","","","",""]
["S2-150816","Clarification and Evaluation of Policy Based TCF Solution","China Mobile, Broadcom Corporation, CATR, KDDI","Tao Sun",54129,"pCR","","","This contribution clarifies the TCF solution, addresses the corresponding FFS and evaluates the solution.","37","6.13","Flexible Mobile Service Steering (FMSS)",13050,"Revised","2015-04-02T15:29:51.633","2015-04-07T16:08:25.750","","S2-151163","Rel-13","23.718","","FMSS","","","","","","","","",""]
["S2-150817","Cleanup of the Loss of an Access from a PDN Connection","Huawei, HiSilicon, China Telecom","Runze Zhou",60945,"pCR","","","This contribution cleans up the Editor's notes in the section of loss of an access from a PDN connection.","28","6.4","IP Flow Mobility support for S2a and S2b interfaces (NBIFOM)",11420,"Revised","2015-04-03T00:54:02.813","2015-04-07T12:29:54.703","","S2-151227","Rel-13","23.861","","NBIFOM","","","","","","","","",""]
["S2-150818","NBIFOM Indications in Call Flows","Huawei, HiSilicon, China Telecom","Runze Zhou",60945,"pCR","","","This contribution discusses NBIFOM indications in different call flows.","28","6.4","IP Flow Mobility support for S2a and S2b interfaces (NBIFOM)",11430,"Merged","2015-04-03T00:54:02.830","2015-04-07T12:29:54.750","","","Rel-13","23.861","","NBIFOM","","","","","","","","",""]
["S2-150819","Adding Architecture alternative for S2a","Huawei, HiSilicon","Runze Zhou",60945,"CR","","","Summary of change: Add architecture in 16.1.1 to cover the above scenario. Add a note in 4.2.3 that the above scenarios are possible but they are not shown for simplicity.","17","5.3","Non-3GPP Access Maintenance",11170,"Noted","2015-04-03T00:54:02.830","2015-04-07T12:29:54.783","","","Rel-12","23.402","12.8.0","TEI12, WLAN_NS","1357","","F",null,"","","","",""]
["S2-150820","Adding Architecture alternative for S2a","Huawei, HiSilicon","Runze Zhou",60945,"CR","","","Rel-13 mirror CR: Summary of change: Add architecture in 16.1.1 to cover the above scenario. Add a note in 4.2.3 that the above scenarios are possible but they are not shown for simplicity.","17","5.3","Non-3GPP Access Maintenance",11180,"Noted","2015-04-03T00:54:02.907","2015-04-07T12:29:54.860","","","Rel-13","23.402","13.1.0","TEI12, WLAN_NS","1358","","A",null,"","","","",""]
["S2-150821","Clarification of ePDG selection function","Huawei, HiSilicon","Runze Zhou",60945,"CR","","","Summary of change: 1) Clarify that the home operator may use the static ePDG selection function to make UE select the Home ePDG as the preferred option. 2) Enhance the dynamic mechanism to allow the UE to select the Home ePDG as the preferred option.","24","6.1.3","Rel-13 Non-3GPP Access Maintenance",11570,"Noted","2015-04-03T00:54:02.970","2015-04-07T12:29:54.893","","","Rel-13","23.402","13.1.0","TEI13","1359","","F",null,"","","","",""]
["S2-150822","Service Continuity for ProSe","Huawei","Runze Zhou",60945,"pCR","","","This contribution proposes a solution for service continuity in which case the UE losing connection reconnects to network via a UE-to-Network Relay and re-enters E-UTRAN coverage from UE-to-Network Relay.","34","6.10","Extended Proximity-based Services TR Phase (eProSe-Ext-SA2TR)",12370,"Noted","2015-04-03T01:31:44.667","2015-04-07T06:45:19.413","","","Rel-13","23.713","","eProSe-Ext-SA2TR","","","","","","","","",""]
["S2-150823","Solution for ProSe Group Priority","Huawei","Runze Zhou",60945,"pCR","","","This contribution proposes that Public Safety Application Server (e.g. MCPTT Server) is the best place to determine the group priority, thereafter signals that to the Prose Function to achieve network controlled group priority for 1-to-many communication.","34","6.10","Extended Proximity-based Services TR Phase (eProSe-Ext-SA2TR)",12380,"Revised","2015-04-03T01:31:44.667","2015-04-07T06:45:19.447","","S2-151728","Rel-13","23.713","","eProSe-Ext-SA2TR","","","","","","","","",""]
["S2-150824","Update of Group Info","Huawei","Runze Zhou",60945,"pCR","","","This contribution proposes to update the description of Group Info in the UE-to-Network Relay discovery procedure.","34","6.10","Extended Proximity-based Services TR Phase (eProSe-Ext-SA2TR)",12390,"Merged","2015-04-03T01:31:44.680","2015-04-07T06:45:19.477","","","Rel-13","23.713","","eProSe-Ext-SA2TR","","","","","","","","",""]
["S2-150825","ProSe Open Discovery Enhancement for Dynamic Metadata","Huawei, Hisilicon","Runze Zhou",60945,"pCR","","","WITHDRAWN: ProSe Open Discovery Enhancement for Dynamic Metadata","55","99","Reserved and Withdrawn documents",13900,"Withdrawn","2015-04-03T01:54:52.937",null,"","","Rel-13","23.713","","eProSe-Ext-SA2TR","","","","","","","","",""]
["S2-150826","eMBMS traffic relay enhancement","Huawei, HiSilicon","Runze Zhou",60945,"pCR","","","WITHDRAWN: eMBMS traffic relay enhancement","55","99","Reserved and Withdrawn documents",13910,"Withdrawn","2015-04-03T01:54:52.937",null,"","S2-151568","Rel-13","23.713","","eProSe-Ext-SA2TR","","","","","","","","",""]
["S2-150827","Solution 3 Clarification","China Mobile","Aihua Li",58162,"pCR","","","This contribution provides clarification to AESE Solution 3. One Editor's note is removed.","29","6.5","Architecture Enhancements for Service Exposure (AESE)",11660,"Merged","2015-04-03T01:55:39.457","2015-04-08T05:10:36.447","","","Rel-13","23.708","","AESE","","","","","","","","",""]
["S2-150828","ProSe Open Discovery Enhancement for Dynamic Metadata","Huawei, Hisilicon","Runze Zhou",60945,"pCR","","","This contribution proposes a solution to enable a UE to update the metadata dynamically. The solution is enhanced based on the existing Open Discovery solution.","34","6.10","Extended Proximity-based Services TR Phase (eProSe-Ext-SA2TR)",12400,"Revised","2015-04-03T02:03:03.250","2015-04-07T03:28:21.733","","S2-151331","Rel-13","23.713","","eProSe-Ext-SA2TR","","","","","","","","",""]
["S2-150829","eMBMS traffic relay enhancement","Huawei, Hisilicon","Runze Zhou",60945,"pCR","","","in the existing eMBMS traffic relay solution, when the Remote UE sends a TMGI Monitoring Request to the UE-to-Network Relay, actually the Remote UE cannot know whether the TMGI corresponding eMBMS traffic can be transferred by the UE-to-Network Relay. In this contribution, an enhancement step is proposed to make sure the remote UE can always find the right UE-to-Network Relay to transfer the interested eMBMS traffic for him.","34","6.10","Extended Proximity-based Services TR Phase (eProSe-Ext-SA2TR)",12410,"Noted","2015-04-03T02:03:03.267","2015-04-07T03:28:21.747","","","Rel-13","23.713","","eProSe-Ext-SA2TR","","","","","","","","",""]
["S2-150830","Discussion on Shortening SRVCC HO voice interruption","Huawei, HiSilicon, China Unicom, Intel","Runze Zhou",60945,"other","","","This discussion paper is to point out an issue that the voice interruption is too long during SRVCC HO procedure, and to analysis the reasons for this problem. Finally, this paper gives some possible solutions to deal with this issue.","18","5.4","IMS-Related Maintenance",10860,"Noted","2015-04-03T02:08:12.597","2015-04-07T06:46:39.303","","","Rel-12","","","","","","","","","","","",""]
["S2-150831","Clarification of CS user plane restoration during SRVCC HO","Huawei, HiSilicon, Intel, China Unicom","Runze Zhou",60945,"CR","","","Summary of change: Clarify in TS23.216 that CS user plane can be resumed once the MSC receives Handover Detection message.","18","5.4","IMS-Related Maintenance",11220,"Revised","2015-04-03T02:08:12.597","2015-04-07T03:31:08.980","","S2-151547","Rel-12","23.216","12.2.0","TEI12","0331","","F",null,"","","","",""]
["S2-150832","Security between Public Safety Ues and Isolated E-UTRAN","Huawei","Runze Zhou",60945,"other","","","This contribution is to discuss the security between Isolated E-UTRAN and Ues connecting to the Isolated E-UTRAN for the backhaul-less scenarios.","40","6.16","Feasibility study on IOPS (FS_IOPS_St2)",13540,"Withdrawn","2015-04-03T02:12:06.173","2015-04-07T12:05:52.407","","","Rel-13","","","","","","","","","","","",""]
["S2-150833","Notify UE conference event package after SRVCC","Huawei, Hisilicon","Maurice Pope",648,"CR","","","Summary of change: This CR proposes that MSC notifies UE the conference related events when it receives conference related events from IMS, via the state independent Notify message.","19","5.5","IMS Maintenance",11430,"Revised","2015-04-03T03:07:50.110","2015-04-07T09:15:02.930","","S2-151111","Rel-13","23.292","13.1.0","IMS_SCC, TEI13","0228","","F",null,"","","","",""]
["S2-150834","Discussion of the UE-initiated NBIFOM","CATT","Juan Zhang",38523,"pCR","","","This contribution discusses the solutions for UE-initiated NBIFOM over TWAN","28","6.4","IP Flow Mobility support for S2a and S2b interfaces (NBIFOM)",11440,"Available","2015-04-03T03:22:32.657","2015-04-07T01:26:58.923","","","Rel-13","23.861","","NBIFOM","","","","","","","","",""]
["S2-150835","Solution to the FFS related to SCM","CATT, ZTE, Broadcom Corporation","Juan Zhang",38523,"pCR","","","This contribution is proposed to solve the FFS related to SCM.","28","6.4","IP Flow Mobility support for S2a and S2b interfaces (NBIFOM)",11450,"Merged","2015-04-03T03:22:32.673","2015-04-07T01:26:58.940","","","Rel-13","23.861","","NBIFOM","","","","","","","","",""]
["S2-150836","ProSe Discovery UE ID update","CATT","Juan Zhang",38523,"pCR","","","This contribution is proposed to enhance the ProSe function triggered ProSe Direct Service revocation procedure to support ProSe Discovery UE ID update.","34","6.10","Extended Proximity-based Services TR Phase (eProSe-Ext-SA2TR)",12420,"Revised","2015-04-03T03:22:32.673","2015-04-07T06:44:12.850","","S2-151329","Rel-13","23.713","","eProSe-Ext-SA2TR","","","","","","","","",""]
["S2-150837","IP address preservation","CATT","Juan Zhang",38523,"pCR","","","It is proposed that IP Address preservation is not supported when the Remote UE moves out of the ProSe UE-Network Relay coverage.","34","6.10","Extended Proximity-based Services TR Phase (eProSe-Ext-SA2TR)",12430,"Noted","2015-04-03T03:22:32.673","2015-04-07T06:44:12.880","","","Rel-13","23.713","","eProSe-Ext-SA2TR","","","","","","","","",""]
["S2-150838","Update of UE attach afresh to the macro EPC procedure","CATT","Juan Zhang",38523,"pCR","","","WITHDRAWN: Update of UE attach afresh to the macro EPC procedure","55","99","Reserved and Withdrawn documents",13950,"Withdrawn","2015-04-03T03:22:32.687",null,"","","Rel-13","23.797","","FS_IOPS_St2","","","","","","","","",""]
["S2-150839","Update of UE attach afresh to the macro EPC procedure","CATT","Juan Zhang",38523,"pCR","","","This contribution is discuss the procedure of how does UE reattach to the macro EPC when the backhaul to the macro EPC is re-established.","40","6.16","Feasibility study on IOPS (FS_IOPS_St2)",13550,"Merged","2015-04-03T05:34:09.857","2015-04-07T06:44:12.803","","","Rel-13","23.797","","FS_IOPS_St2","","","","","","","","",""]
["S2-150840","Options for delivering network parameters to correct MME","CATT","Hucheng Wang",43301,"pCR","","","This contribution proposes that the SCEF caches the CP information for re-sending the CP information to new serving MME directly when serving MME is relocated.","29","6.5","Architecture Enhancements for Service Exposure (AESE)",11670,"Available","2015-04-03T05:48:17.517","2015-04-03T05:58:47.493","","","Rel-13","23.708","","AESE","","","","","","","","",""]
["S2-150841","Optimize EPS bearer management using communication patterns","CATT","Hucheng Wang",43301,"pCR","","","This contribution proposes that PCRF/PGW can use communication patterns to manage EPS bearer","29","6.5","Architecture Enhancements for Service Exposure (AESE)",11680,"Available","2015-04-03T05:51:38.597","2015-04-03T05:58:47.523","","","Rel-13","23.708","","AESE","","","","","","","","",""]
["S2-150842","Group message delivery function and procedure","Huawei, Hisilicon, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Samsung, KPN","Runze Zhou",60945,"CR","","","Summary of change: High level description for group messge delivery function and delivery procedures is specified.","31","6.7","Group based Enhancements (GROUPE)",13270,"Revised","2015-04-03T06:39:43.670","2015-04-07T12:05:52.517","","S2-151160","Rel-13","23.682","13.1.0","GROUPE","0094","","B",null,"","","","",""]
["S2-150843","Architecture update for GROUPE","Huawei, Hisilicon, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Intel","Runze Zhou",60945,"CR","","","Summary of change: Update the figure of 3GPP Architecture for Service Capability Exposure to include the BM-SC and MB2","31","6.7","Group based Enhancements (GROUPE)",13310,"Agreed","2015-04-03T06:39:43.747","2015-04-07T12:05:52.750","","","Rel-13","23.682","13.1.0","GROUPE","0095","","B",null,"","","","",""]
["S2-150844","Cover Sheet for TR 23.769 for Approval at TSG SA","GROUPE Rapporteurs (Huawei)","Runze Zhou",60945,"other","","","This contribution proposes a cover page for submitting TR 23.769 to SA plenary for Approval.","31","6.7","Group based Enhancements (GROUPE)",12000,"Revised","2015-04-03T06:39:43.810","2015-04-07T12:05:53.280","","S2-151159","Rel-13","","","","","","","","","","","",""]
["S2-150845","GTP-C retransmission in eDRX","Huawei","Runze Zhou",60945,"pCR","","","Add new solution for GTP-C retransmission","39","6.15","Feasibility study on Extended DRX cycle for Power Consumption Optimization (FS_eDRX)",13370,"Revised","2015-04-03T06:39:43.810","2015-04-07T12:05:53.483","S2-150395","S2-151233","Rel-13","23.770","","FS_eDRX","","","","","","","","",""]
["S2-150846","RAN FS_LTE_SC_PTM consideration within SA2 MBMS_enh scope","Huawei, Hisilicon","Runze Zhou",60945,"pCR","","","Discuss the RAN work and relationship with SA WG2","38","6.14","MBMS Enhancements (MBMS_enh)",13180,"Noted","2015-04-03T06:39:43.827","2015-04-07T12:05:53.733","","","Rel-13","23.741","","MBMS_enh","","","","","","","","",""]
["S2-150847","LS on SC-PTM transmission feedback","Huawei","Runze Zhou",60945,"LS out","","","LS back to RAN WG2 and RAN WG3","38","6.14","MBMS Enhancements (MBMS_enh)",0,"Revised","2015-04-03T06:39:43.827","2015-04-07T12:05:53.937","","S2-151096","Rel-13","","","","","","","","S2-150726","RAN WG2, RAN WG3"]
["S2-150848","Consideration of PCO vs. APCO for S2b NBIFOM parameters Transport (Open issue 5)","ZTE","Tricci So",44974,"pCR","","","Discusses the considerations for the usage of defining new IKEv2 IE, PCO, vs. extending the existing use of IKE Configuration Payload which is used together with APCO to transport the routing rule over S2b.","28","6.4","IP Flow Mobility support for S2a and S2b interfaces (NBIFOM)",11460,"Revised","2015-04-03T06:42:58.513","2015-04-05T06:38:13.193","","S2-151254","Rel-13","23.861","","NBIFOM","","","","","","","","",""]
["S2-150849","Clarification of Impacts when Gxx is not used for eHRPD Access","China Telecom, Huawei, HiSilicon","Runze Zhou",60945,"CR","","","Summary of change: Add clarification of system impacts when Gateway Control Session is not established for eHRPD access.","24","6.1.3","Rel-13 Non-3GPP Access Maintenance",11580,"Revised","2015-04-03T06:46:54.710","2015-04-07T12:29:54.937","","S2-151211","Rel-13","23.402","13.1.0","TEI13","1360","","F",null,"","","","",""]
["S2-150850","Conclusions for App ID Support","ZTE","Tricci So",44974,"pCR","","","This P-CR proposes the conclusion to defer the support of App ID by NBIFOM in Rel-13","28","6.4","IP Flow Mobility support for S2a and S2b interfaces (NBIFOM)",11470,"Revised","2015-04-03T06:51:56.063","2015-04-05T06:39:15.953","","S2-151255","Rel-13","23.861","","NBIFOM","","","","","","","","",""]
["S2-150851","Conclusion for keeping “Handover Indication” in the enhanced handover procedure when adding addition access to multi-access PDN connection","ZTE, Huawei(?), HiSilicon(?)","Tricci So",44974,"pCR","","","This P-CR demonstrates and concludes the combined use of NBIFOM capability indication with the existing 'Handover Indication' in the enhanced handover procedure to support adding new access to an existing PDN connection, and not to release the other existing access; while the existing regular handover procedures for the same UE can still be supported when NBIFOM is not requested.","28","6.4","IP Flow Mobility support for S2a and S2b interfaces (NBIFOM)",11480,"Merged","2015-04-03T07:15:59.097","2015-04-05T06:39:53.283","","","Rel-13","23.861","","NBIFOM","","","","","","","","",""]
["S2-150852","Miscellaneous NBIFOM Editor’s Notes Cleanup","ZTE","Tricci So",44974,"pCR","","","This P-CR is to clean-up the Editor's Notes on routing rules consideration to be integrated with the PCC rules which have been agreed and resolved.","28","6.4","IP Flow Mobility support for S2a and S2b interfaces (NBIFOM)",11490,"Approved","2015-04-03T07:21:07.107","2015-04-05T06:40:27.027","","","Rel-13","23.861","","NBIFOM","","","","","","","","",""]
["S2-150853","Conclusions for NBIFOM Open Issues 6 and 7","ZTE","Tricci So",44974,"pCR","","","This P-CR proposes the conclusions oftwo open issues about the support for Inter-MME/SGSN IP flow mobility and PMIP to be deferred from the NBIFOM Rel-13 study.","28","6.4","IP Flow Mobility support for S2a and S2b interfaces (NBIFOM)",11500,"Revised","2015-04-03T07:28:34.767","2015-04-05T06:41:00.487","","S2-151229","Rel-13","23.861","","NBIFOM","","","","","","","","",""]
["S2-150854","AS allowing non-international format Request-URI when RAVEL is used","China Mobile","Maurice Pope",648,"CR","","","Summary of change: It is proposed to add contexts to complete the specification.","8","4.2","LS (S2-150704) on VoLTE Roaming and Replies",10420,"Agreed","2015-04-03T07:54:10.500","2015-04-05T10:23:09.060","","","Rel-11","23.228","11.10.0","RAVEL","1108","","F",null,"","","","",""]
["S2-150855","Notify UE conference event package after SRVCC","Huawei, Hisilicon","Maurice Pope",648,"CR","","","Summary of change: This CR proposes that MSC notifies UE the conference related events when it receives conference related events from IMS, via the state independent Notify message.","19","5.5","IMS Maintenance",11450,"Revised","2015-04-03T08:02:44.613","2015-04-07T09:15:02.960","","S2-151112","Rel-13","23.237","12.8.0","IMS_SCC, TEI13","0481","","F",null,"","","","",""]
["S2-150856","AS allowing non-international format Request-URI when RAVEL is used","China Mobile","Maurice Pope",648,"CR","","","Rel-12 mirror CR: Summary of change: It is proposed to add contexts to complete the specification.","8","4.2","LS (S2-150704) on VoLTE Roaming and Replies",10450,"Agreed","2015-04-03T08:18:29.943","2015-04-05T10:23:09.107","","","Rel-12","23.228","12.8.0","RAVEL","1109","","A",null,"","","","",""]
["S2-150857","AS allowing non-international format Request-URI when RAVEL is used","China Mobile","Maurice Pope",648,"CR","","","Rel-13 mirror CR: Summary of change: It is proposed to add contexts to complete the specification.","8","4.2","LS (S2-150704) on VoLTE Roaming and Replies",10460,"Agreed","2015-04-03T08:21:12.993","2015-04-05T10:23:09.153","","","Rel-13","23.228","13.2.0","RAVEL","1110","","A",null,"","","","",""]
["S2-150858","TRF supporting geo-local service number normalization","China Mobile","Maurice Pope",648,"CR","","","Summary of change: Description of geo-local number normalization is added on TRF.","8","4.2","LS (S2-150704) on VoLTE Roaming and Replies",10470,"Revised","2015-04-03T08:23:51.333","2015-04-05T10:23:09.200","","S2-151123","Rel-11","23.228","11.10.0","RAVEL","1111","","F",null,"","","","",""]
["S2-150859","TRF supporting geo-local service number normalization","China Mobile","Maurice Pope",648,"CR","","","Rel-12 mirror CR: Summary of change: Description of geo-local number normalization is added on TRF.","8","4.2","LS (S2-150704) on VoLTE Roaming and Replies",10490,"Revised","2015-04-03T08:26:19.580","2015-04-05T10:23:09.247","","S2-151124","Rel-12","23.228","12.8.0","RAVEL","1112","","A",null,"","","","",""]
["S2-150860","TRF supporting geo-local service number normalization","China Mobile","Maurice Pope",648,"CR","","","Rel-13 mirror CR: Summary of change: Description of geo-local number normalization is added on TRF.","8","4.2","LS (S2-150704) on VoLTE Roaming and Replies",10510,"Revised","2015-04-03T08:28:35.737","2015-04-05T10:23:09.310","","S2-151125","Rel-13","23.228","13.2.0","RAVEL","1113","","A",null,"","","","",""]
["S2-150861","Resolving the Default access negotiation and determination","ZTE","Tricci So",44974,"pCR","","","This P-CR addresses the unresolved Editor's note on how default access is determined and indicated to both UE and the network.","28","6.4","IP Flow Mobility support for S2a and S2b interfaces (NBIFOM)",11510,"Available","2015-04-03T08:46:55.043","2015-04-07T06:02:18.137","","","Rel-13","23.861","","NBIFOM","","","","","","","","",""]
["S2-150862","Conclusion for NBIFOM study in Rel-13","ZTE","Tricci So",44974,"pCR","","","This P-CR presents the conclusions of the NBIFOM study in Rel-13.","28","6.4","IP Flow Mobility support for S2a and S2b interfaces (NBIFOM)",11520,"Revised","2015-04-03T08:53:31.017","2015-04-05T06:41:59.003","","S2-151256","Rel-13","23.861","","NBIFOM","","","","","","","","",""]
["S2-150863","Key issues: UE location","Huawei","Marco Spini",8356,"pCR","","","This contribution introduce the key issue related how the UE can detect and knows its location when connected to WLAN and on how the LRF function can detect UE location.","41","6.17","Feasibility study on the Support of Emergency services over WLAN (FS_SEW)",13610,"Merged","2015-04-03T11:25:51.160","2015-04-07T08:20:39.790","","","Rel-13","23.771","","FS_SEW","","","","","","","","",""]
["S2-150864","Solution: How  LRF retrieve location information for s2a","Huawei , Hisilicon","Marco Spini",8356,"pCR","","","This document describes the solution for supporting the retrieval of location information via LRF function for IMS ES when UE is attached to a Trusted WLAN.","41","6.17","Feasibility study on the Support of Emergency services over WLAN (FS_SEW)",13620,"Revised","2015-04-03T11:28:18.377","2015-04-07T08:20:39.727","","S2-151262","Rel-13","23.771","","FS_SEW","","","","","","","","",""]
["S2-150865","Solution: How  LRF retrieve location information for s2b","Huawei","Marco Spini",8356,"pCR","","","This document describes the solution for supporting the retrieval of location information via LRF function for IMS ES when UE is attached to a Untrusted WLAN","41","6.17","Feasibility study on the Support of Emergency services over WLAN (FS_SEW)",13630,"Noted","2015-04-03T11:30:02.290","2015-04-07T08:20:39.777","","","Rel-13","23.771","","FS_SEW","","","","","","","","",""]
["S2-150866","Solution: how UE knows its location and how can sent it","Huawei","Marco Spini",8356,"pCR","","","This contribution analysis and proposes a solution to define how the UE can detect its location when connected to WLAN and how and when the UE can sent its location to the network","41","6.17","Feasibility study on the Support of Emergency services over WLAN (FS_SEW)",13640,"Merged","2015-04-03T11:32:30.427","2015-04-07T08:20:39.807","","","Rel-13","23.771","","FS_SEW","","","","","","","","",""]
["S2-150867","Architectural Considerations","NTT DOCOMO, AT&T, Alcatel-Lucent, Intel","Syed Husain",14749,"pCR","","","This contribution proposes text for empty clause 4 in TR 23.708.","29","6.5","Architecture Enhancements for Service Exposure (AESE)",11690,"Revised","2015-04-03T13:28:01.930","2015-04-07T00:38:06.193","","S2-151238","Rel-13","23.708","","AESE","","","","","","","","",""]
["S2-150868","Clause 5 update","NTT DOCOMO","Syed Husain",14749,"pCR","","","This contribution proposes modifications to Clause 5 on Key Issues in TR 23.708.","29","6.5","Architecture Enhancements for Service Exposure (AESE)",11700,"Approved","2015-04-03T13:32:42.137","2015-04-07T00:35:23.003","","","Rel-13","23.708","","AESE","","","","","","","","",""]
["S2-150869","Reflections on monitoring events from MME","Ericsson","Shabnam Sultana",21207,"other","","","Proposes some changes for solution 3 on monitoring events from MME.","30","6.6","Monitoring Enhancements (MONTE)",11810,"Noted","2015-04-03T13:37:57.227","2015-04-07T14:05:40.270","","","Rel-13","","","","","","","","","","","",""]
["S2-150870","Solution 2 update","NTT DOCOMO","Syed Husain",14749,"pCR","","","This contribution proposes updates for data buffering solution 2 in TR 23.709.","36","6.12","Optimizations to Support High Latency Communications (FS_HLCom)",12840,"Merged","2015-04-03T13:39:10.097","2015-04-07T00:37:08.537","","","Rel-13","23.709","","FS_HLcom","","","","","","","","",""]
["S2-150871","AESE – Solution 5 Corrections and Evaluations","NEC","Andreas Kunz",35384,"pCR","","","This contribution provides corrections to and evaluation of Solution 5 in TR 23.708 (AESE).","29","6.5","Architecture Enhancements for Service Exposure (AESE)",11710,"Noted","2015-04-03T14:46:16.557","2015-04-07T14:24:56.733","","","Rel-13","23.708","","AESE","","","","","","","","",""]
["S2-150872","Update to PSM to support monitoring events","Huawei, HiSilicon, Intel","Frank Mademann",6821,"CR","","","Summary of change: Active and reachability timer handling will be decoupled. The support of the monitoring event of Reachability for Data is introduced.","30","6.6","Monitoring Enhancements (MONTE)",13010,"Revised","2015-04-03T15:01:19.050","2015-04-07T12:56:56.830","","S2-151219","Rel-13","23.682","13.1.0","MONTE","0096","","B",null,"","","","",""]
["S2-150873","Update to PSM to support monitoring events","Huawei, HiSilicon, Intel","Frank Mademann",6821,"CR","","","Summary of change: Active and reachability timer handling will be decoupled. The support of monitoring event Reachability for Data are introduced.","30","6.6","Monitoring Enhancements (MONTE)",13040,"Revised","2015-04-03T15:04:43.147","2015-04-07T12:56:56.877","","S2-151220","Rel-13","23.401","13.2.0","MONTE","2850","","B",null,"","","","",""]
["S2-150874","Update to PSM to support monitoring events","Huawei, HiSilicon, Intel","Frank Mademann",6821,"CR","","","Summary of change: Active and reachability timer handling will be decoupled. The support of monitoring event Reachability for Data is introduced.","30","6.6","Monitoring Enhancements (MONTE)",13070,"Revised","2015-04-03T15:07:15.167","2015-04-07T12:56:56.707","","S2-151221","Rel-13","23.060","13.2.0","MONTE","1960","","B",null,"","","","",""]
["S2-150875","Introduction of monitoring procedures","Huawei, HiSilicon, Intel, Alcatel-Lucent","Frank Mademann",6821,"CR","","","Summary of change: The procedures for supporting monitoring configuration via MME/SGSN and via HSS are introduced.","30","6.6","Monitoring Enhancements (MONTE)",12980,"Revised","2015-04-03T15:19:33.597","2015-04-07T12:56:56.750","","S2-151218","Rel-13","23.682","13.1.0","MONTE","0097","","B",null,"","","","",""]
["S2-150876","Introduction of monitoring event removal and recall procedures","Huawei, HiSilicon","Frank Mademann",6821,"CR","","","Summary of change: The procedures for remove and replace of monitoring event configurations are introduced and the charging aspects.","30","6.6","Monitoring Enhancements (MONTE)",13110,"Available","2015-04-03T15:24:40.917","2015-04-07T12:56:56.797","","","Rel-13","23.682","13.1.0","MONTE","0098","","B",null,"","","","",""]
["S2-150877","Architectural updates for Monitoring feature","Intel, Alcatel-Lucent, Huawei","Puneet Jain",36283,"CR","","","Summary of change: Updates to architecture for Monitoring feature by adding new reference point between SGSN/MME/HSS and SCEF.","30","6.6","Monitoring Enhancements (MONTE)",12780,"Revised","2015-04-03T22:19:37.183","2015-04-07T04:46:46.453","","S2-151212","Rel-13","23.682","13.1.0","MONTE","0099","","B",null,"","","","",""]
["S2-150878","Monitoring Feature Description","Intel, Huawei, Alcatel-Lucent","Puneet Jain",36283,"CR","","","Summary of change: High level description for monitoring function and monitoring via HSS, SGSN/MME and PCRF is specified.","30","6.6","Monitoring Enhancements (MONTE)",12830,"Revised","2015-04-03T22:27:34.183","2015-04-07T04:46:46.483","","S2-151214","Rel-13","23.682","13.1.0","MONTE","0100","","B",null,"","","","",""]
["S2-150879","Support for Monitoring Events","Intel","Puneet Jain",36283,"CR","","","Summary of change: High level description for monitoring function.","30","6.6","Monitoring Enhancements (MONTE)",12910,"Revised","2015-04-03T22:33:14.757","2015-04-07T04:46:46.513","","S2-151216","Rel-13","23.060","13.2.0","MONTE","1961","","B",null,"","","","",""]
["S2-150880","Support for Monitoring Events","Intel","Puneet Jain",36283,"CR","","","Summary of change: High level description for monitoring function.","30","6.6","Monitoring Enhancements (MONTE)",12940,"Revised","2015-04-03T22:38:38.363","2015-04-07T04:46:46.560","","S2-151217","Rel-13","23.401","13.2.0","MONTE","2851","","B",null,"","","","",""]
["S2-150881","Resolution of the open issue in Model B Discovery","Huawei, HiSilicon","Runze Zhou",60945,"pCR","","","In this contribution, it clarifies the concerns listed in S2-150121 and proposes to accept that network returns ProSe response code in Model B discovery.","34","6.10","Extended Proximity-based Services TR Phase (eProSe-Ext-SA2TR)",12440,"Noted","2015-04-05T09:58:49.427","2015-04-07T12:26:40.237","","","Rel-13","23.713","","eProSe-Ext-SA2TR","","","","","","","","",""]
["S2-150882","Conclusion Supplements on ProSe Restricted Discovery","Huawei, HiSilicon","Runze Zhou",60945,"pCR","","","In this contribution, it is proposed to add the solution of on demand announcement into conclusion part of ProSe restricted discovery.","34","6.10","Extended Proximity-based Services TR Phase (eProSe-Ext-SA2TR)",12450,"Revised","2015-04-05T09:58:49.440","2015-04-07T12:26:40.267","","S2-151328","Rel-13","23.713","","eProSe-Ext-SA2TR","","","","","","","","",""]
["S2-150883","Clarification on the Configurations in Service Authorization","Huawei, HiSilicon","Runze Zhou",60945,"pCR","","","In this contribution, we proposed some enhancement for service authorization procedures.","34","6.10","Extended Proximity-based Services TR Phase (eProSe-Ext-SA2TR)",12460,"Revised","2015-04-05T09:58:49.440","2015-04-07T12:26:40.297","","S2-151744","Rel-13","23.713","","eProSe-Ext-SA2TR","","","","","","","","",""]
["S2-150884","Clarification on geo-local number handling","China Mobile, NTT DOCOMO","Maurice Pope",648,"CR","","","Summary of change: Addition of a sentence to clarify that HPLMN and/or VPLMN support non-internation format, and the use of non-internationl format shall be decided by the HPLMN based on the roaming agreement.","8","4.2","LS (S2-150704) on VoLTE Roaming and Replies",10430,"Revised","2015-04-05T13:03:23.453","2015-04-07T06:08:36.807","","S2-151122","Rel-13","23.228","13.2.0","TEI13","1114","","C",null,"","","","",""]
["S2-150885","Reference update","China Mobile","Maurice Pope",648,"pCR","","","reference is updated to include missing specifications which are referenced in this specification.","33","6.9","Enhancements to WEBRTC interoperability (eWebRTCi)",12130,"Approved","2015-04-05T13:29:58.467","2015-04-05T13:33:11.377","","","Rel-13","23.706","","eWebRTCi","","","","","","","","",""]
["S2-150886","Obtaining ProSe Discovery info Public Safety discovery","Qualcomm Incorporated","Haris Zisimopoulos",41602,"pCR","","","This contribution proposes to reuse existing procedures defined for restricted and open discovery in order to obtain the 'Announcer/Monitorer Info and Discoverer/Discoveree Info' that are to be used for Public Safety group member discovery","34","6.10","Extended Proximity-based Services TR Phase (eProSe-Ext-SA2TR)",12470,"Noted","2015-04-05T19:34:50.170","2015-04-07T10:33:56.653","","","Rel-13","23.713","","eProSe-Ext-SA2TR","","","","","","","","",""]
["S2-150887","APN information in ProSe UE-NW Relay discovery","Qualcomm Incorporated","Haris Zisimopoulos",41602,"pCR","","","WITHDRAWN: APN information in ProSe UE-NW Relay discovery","55","99","Reserved and Withdrawn documents",13920,"Withdrawn","2015-04-05T19:34:50.187",null,"S2-150126","","Rel-13","23.713","","eProSe-Ext-SA2TR","","","","","","","","",""]
["S2-150888","Support for ProSe in multicarrier across PLMNs","Qualcomm Incorporated, Ericsson","Haris Zisimopoulos",41602,"CR","","","Summary of change: - Clarifies the multicarrier support across PLMNs - Adds the term 'connected to a cell' for procedures that apply connected mode - Adds reference in TS 36.304","15","5.1","3GPP Packet Access Maintenance",10640,"Revised","2015-04-05T19:34:50.203","2015-04-07T10:33:56.607","S2-150123","S2-151139","Rel-12","23.303","12.4.0","ProSe","0151","1","F",null,"","","","",""]
["S2-150889","Updating SRVCC operation possible in E-UTRAN","Qualcomm Incorporated, Huawei, HiSilicon","Haris Zisimopoulos",41602,"CR","","","Summary of change: In order to resolve this issue it is identified that the MME needs to be able to inform the eNB after the TAU to update the UE context to include the SRVCC operation possible.","18","5.4","IMS-Related Maintenance",11230,"Revised","2015-04-05T19:34:50.403","2015-04-07T10:33:56.573","","S2-151110","Rel-13","23.216","12.2.0","TEI13","0332","","F",null,"","","","",""]
["S2-150890","Codecs for WebRTC","Qualcomm Incorporated, Telecom Italia, BlackBerry UK Limited, Nokia Networks","Haris Zisimopoulos",41602,"CR","","","Summary of change: - Updates the reference to draft-ietf-rtcweb-overview-13 - Indicates that any any requirements relating to specific audio and video codecs are excluded - Text is modeified to accurately state 'A WebRTC IMS Client (WIC) is an application using the WebRTC extensions specified in WebRTC 1.0 [85] except for those extensions specifically exempted by 3GPP specifications (e.g. codecs)'","18","5.4","IMS-Related Maintenance",11260,"Revised","2015-04-05T19:34:50.467","2015-04-07T10:33:56.527","","S2-151106","Rel-12","23.228","12.8.0","IMS_WebRTC","1115","","F",null,"","","","",""]
["S2-150891","Codecs for WebRTC","Qualcomm Incorporated, Telecom Italia, BlackBerry UK Limited, Nokia Networks","Haris Zisimopoulos",41602,"CR","","","Rel-13 mirror CR: Summary of change: - Updates the reference to draft-ietf-rtcweb-overview-13 - Indicates that any any requirements relating to specific audio and video codecs are excluded - Text is modeified to accurately state 'A WebRTC IMS Client (WIC) is an application using the WebRTC extensions specified in WebRTC 1.0 [85] except for those extensions specifically exempted by 3GPP specifications (e.g. codecs)'","18","5.4","IMS-Related Maintenance",11280,"Revised","2015-04-05T19:34:50.530","2015-04-07T10:33:56.497","","S2-151107","Rel-13","23.228","13.2.0","IMS_WebRTC","1116","","A",null,"","","","",""]
["S2-150892","ProSe Group Priority","Qualcomm Incorporated","Haris Zisimopoulos",41602,"pCR","","","Discusses options for ProSe Group Priority and proposes text for TR 23.713.","34","6.10","Extended Proximity-based Services TR Phase (eProSe-Ext-SA2TR)",12480,"Available","2015-04-05T19:34:50.593","2015-04-07T10:33:56.857","","","Rel-13","23.713","","eProSe-Ext-SA2TR","","","","","","","","",""]
["S2-150893","ProSe QoS","Qualcomm Incorporated","Haris Zisimopoulos",41602,"pCR","","","Discusses options for ProSe QoS and proposes text for TR 23.713.","34","6.10","Extended Proximity-based Services TR Phase (eProSe-Ext-SA2TR)",12490,"Available","2015-04-05T19:34:50.607","2015-04-07T10:33:56.807","","","Rel-13","23.713","","eProSe-Ext-SA2TR","","","","","","","","",""]
["S2-150894","Update of SRVCC capability","Qualcomm Incorporated, Huawei, HiSilicon","Haris Zisimopoulos",41602,"other","","","Identifies a problem with UE disabling 'SRVCC capability' followed up with handover.","18","5.4","IMS-Related Maintenance",10910,"Noted","2015-04-05T19:34:50.623","2015-04-07T10:33:56.777","","","Rel-12","","","","","","","","","","","",""]
["S2-150895","Removal of long expired reference to draft-kaplan-enum-sip-routing","BlackBerry","Andrew Allen",21705,"CR","","","Summary of change: The reference to this draft is removed and the editor's note deleted.","19","5.5","IMS Maintenance",11470,"Agreed","2015-04-06T01:17:41.580","2015-04-06T01:50:06.453","","","Rel-10","23.228","10.8.0","TEI10","1117","","F",null,"","","","",""]
["S2-150896","Removal of long expired reference to draft-kaplan-enum-sip-routing","BlackBerry","Andrew Allen",21705,"CR","","","Rel-11 mirror CR: Summary of change: The reference to this draft is removed and the editor's note deleted.","19","5.5","IMS Maintenance",11480,"Agreed","2015-04-06T01:22:34.270","2015-04-06T01:50:06.547","","","Rel-11","23.228","11.10.0","TEI10","1118","","A",null,"","","","",""]
["S2-150897","Removal of long expired reference to draft-kaplan-enum-sip-routing","BlackBerry","Andrew Allen",21705,"CR","","","Rel-12 mirror CR: Summary of change: The reference to this draft is removed and the editor's note deleted.","19","5.5","IMS Maintenance",11490,"Agreed","2015-04-06T01:30:03.257","2015-04-06T01:50:06.577","","","Rel-12","23.228","12.8.0","TEI10","1119","","A",null,"","","","",""]
["S2-150898","Removal of long expired reference to draft-kaplan-enum-sip-routing","BlackBerry","Andrew Allen",21705,"CR","","","Rel-13 mirror CR: Summary of change: The reference to this draft is removed and the editor's note deleted.","19","5.5","IMS Maintenance",11500,"Agreed","2015-04-06T01:35:31.137","2015-04-06T01:50:06.627","","","Rel-13","23.228","13.2.0","TEI10","1120","","A",null,"","","","",""]
["S2-150899","Correction of WIC definition","BlackBerry UK Limited","Andrew Allen",21705,"CR","","","Summary of change: Text is modeified to accurately state 'A WebRTC IMS Client (WIC) is an application using the WebRTC extensions specified in WebRTC 1.0 [85] except for those extensions specifically exempted by 3GPP specifications (e.g. codecs)'","18","5.4","IMS-Related Maintenance",11310,"Withdrawn","2015-04-06T01:41:01.437","2015-04-06T01:50:06.487","","","Rel-12","23.228","12.8.0","IMS_WebRTC","1121","","F",null,"","","","",""]
["S2-150900","Correction of WIC definition","BlackBerry UK Limited","Andrew Allen",21705,"CR","","","Rel-13 mirror CR: Summary of change: Text is modeified to accurately state 'A WebRTC IMS Client (WIC) is an application using the WebRTC extensions specified in WebRTC 1.0 [85] except for those extensions specifically exempted by 3GPP specifications (e.g. codecs)'","18","5.4","IMS-Related Maintenance",11320,"Withdrawn","2015-04-06T01:43:54.737","2015-04-06T01:50:06.533","","","Rel-13","23.228","13.2.0","IMS_WebRTC","1122","","A",null,"","","","",""]
["S2-150901","Draft Reply LS on “Clarification regarding change of active time value and periodic TAU or RAU timer value for UE supporting PSM”","LG Electronics Inc.","Jinsook Ryu",39022,"LS out","","","LS reply to CT WG1 to clarify Power Saving Mode configuration.","15","5.1","3GPP Packet Access Maintenance",10440,"Noted","2015-04-06T04:21:32.713","2015-04-07T00:30:58.410","","","Rel-12","","","","","","","","S2-150708","CT WG1"]
["S2-150902","Solution Updates on Solution 3","LG Electronics","Jinsook Ryu",39022,"pCR","","","This paper address further enhancement on Reusing MONTE solution for practical usage of the UE reachability function.","36","6.12","Optimizations to Support High Latency Communications (FS_HLCom)",12850,"Revised","2015-04-06T04:30:59.573","2015-04-07T07:21:18.600","","S2-151178","Rel-13","23.709","","FS_HLcom","","","","","","","","",""]
["S2-150903","Solution Updates on Solution 5","LG Electronics","Jinsook Ryu",39022,"pCR","","","Correction on figure 5.5.1.1 to reflect right procedure and alternative way of informing Max_T value is described in the evaluation section.","36","6.12","Optimizations to Support High Latency Communications (FS_HLCom)",12860,"Available","2015-04-06T04:34:11.437","2015-04-07T07:23:54.943","","","Rel-13","23.709","","FS_HLcom","","","","","","","","",""]
["S2-150904","New issue for idle mode eDRX: Maximizing Idle Period in regard to period TAU","LG Electronics","Jinsook Ryu",39022,"pCR","","","This paper proposes to include a new issue on idle mode eDRX especially to maximize idle period for power saving in regard to periodic TAU procedure.","39","6.15","Feasibility study on Extended DRX cycle for Power Consumption Optimization (FS_eDRX)",13380,"Noted","2015-04-06T04:38:56.230","2015-04-07T06:49:56.597","","","Rel-13","23.770","","FS_eDRX","","","","","","","","",""]
["S2-150905","Procedures for solution in section 6.1.4","China Unicom, Intel","Changhong Shan",45586,"pCR","","","Update the solution 2.1 of semantics of traffic steering policy in clause 6.2","37","6.13","Flexible Mobile Service Steering (FMSS)",13060,"Available","2015-04-06T04:39:34.263","2015-04-07T04:31:27.997","","","Rel-13","23.718","","FMSS","","","","","","","","",""]
["S2-150906","Solution for idle mode eDRX: Adjustable execution of P-TAU for further power saving","LG Electronics","Jinsook Ryu",39022,"pCR","","","This paper proposes to include a new solution on idle mode eDRX which realizes maximizing Idle more period for further power saving.","39","6.15","Feasibility study on Extended DRX cycle for Power Consumption Optimization (FS_eDRX)",13390,"Noted","2015-04-06T04:42:54.753","2015-04-07T06:54:44.257","","","Rel-13","23.770","","FS_eDRX","","","","","","","","",""]
["S2-150907","Update the solution 2.1 of semantics of traffic steering policy in section 6.2","Intel, China Unicom","Changhong Shan",45586,"pCR","","","Update the solution 2.1 of semantics of traffic steering policy in clause 6.2","37","6.13","Flexible Mobile Service Steering (FMSS)",13070,"Noted","2015-04-06T04:44:51.860","2015-04-07T04:31:28.030","","","Rel-13","23.718","","FMSS","","","","","","","","",""]
["S2-150908","Further description on avoiding SRVCC trigger","Samsung","Curt Wong",42596,"pCR","","","The paper provides more details on some of the options to avoid false SRVCC trigger and suggests a way forward.","33","6.9","Enhancements to WEBRTC interoperability (eWebRTCi)",12140,"Noted","2015-04-06T08:29:07.577","2015-04-06T20:21:05.420","","","Rel-13","23.706","","eWebRTCi","","","","","","","","",""]
["S2-150909","Reply LS on addition of proximity services group identifier","QUALCOMM UK Ltd","Haris Zisimopoulos",41602,"LS out","","","To: CT WG1 CC: RAN WG2","15","5.1","3GPP Packet Access Maintenance",0,"Revised","2015-04-06T08:29:44.457","2015-04-07T10:33:56.747","","S2-151326","Rel-12","","","","","","","","S2-150707","CT WG1","RAN WG2"]
["S2-150910","Handling of PSM timer","HTC","Kundan Tiwari",44236,"CR","","","Summary of change: Specify that the MS will trigger RAU/TAU when it needs to change the T3324 timer and negotiate the MRT.","15","5.1","3GPP Packet Access Maintenance",10830,"Revised","2015-04-06T08:52:30.793","2015-04-07T04:11:47.730","","S2-151131","Rel-12","23.682","12.3.0","MTCe-UEPCOP","0101","","F",null,"","","","",""]
["S2-150911","Handling of PSM timer","HTC","Kundan Tiwari",44236,"CR","","","Rel-13 mirror CR: Summary of change: Specify that the MS will trigger RAU/TAU when it needs to change the T3324 timer and negotiate the MRT.","15","5.1","3GPP Packet Access Maintenance",10850,"Revised","2015-04-06T08:55:12.597","2015-04-07T04:11:47.777","","S2-151132","Rel-13","23.682","13.1.0","MTCe-UEPCOP","0102","","A",null,"","","","",""]
["S2-150912","Consideration on \"WLAN offloadability” indication provided via NAS","LG Electronics","Hyunsook Kim",42013,"pCR","","","This paper considers NBIFOM Suspend/Resume Procedures for co-existence between RAN rule and NBIFOM.","28","6.4","IP Flow Mobility support for S2a and S2b interfaces (NBIFOM)",11530,"Noted","2015-04-06T09:39:42.730","2015-04-07T07:05:29.920","","","Rel-13","23.861","","NBIFOM","","","","","","","","",""]
["S2-150913","NBIFOM Suspend/Resume Procedures","LG Electronics","Hyunsook Kim",42013,"pCR","","","This paper considers the co-existence with RAN rule solution in case of an access loss from a PDN connection.","28","6.4","IP Flow Mobility support for S2a and S2b interfaces (NBIFOM)",11540,"Noted","2015-04-06T09:42:19.603","2015-04-07T07:05:29.967","","","Rel-13","23.861","","NBIFOM","","","","","","","","",""]
["S2-150914","Co-existence with RAN rule solution in case of an access loss","LG Electronics","Hyunsook Kim",42013,"pCR","","","This paper considers the co-existence with RAN rule solution in case of an access loss from a PDN connection.","28","6.4","IP Flow Mobility support for S2a and S2b interfaces (NBIFOM)",11550,"Noted","2015-04-06T09:47:05.753","2015-04-07T07:05:30.013","","","Rel-13","23.861","","NBIFOM","","","","","","","","",""]
["S2-150915","Update of MME load balancing for Dedicated Core Networks","Huawei, HiSilicon","Frank Mademann",6821,"CR","","","Summary of change: All functions describing connection of multiple CN nodes to a RAN node are enhanced to clarify the case where those CN nodes belong to different CNs, i.e. where DCOR is deployed","27","6.3","Dedicated Core Networks (DECOR)",11750,"Revised","2015-04-06T13:55:09.923","2015-04-07T12:58:00.993","S2-150266","S2-151322","Rel-13","23.236","12.0.0","DECOR","0051","2","B",null,"","","","",""]
["S2-150916","Update of load balancing functionality for DECOR","Huawei, HiSilicon","Frank Mademann",6821,"CR","","","Summary of change: Load re-balancing fucntionality clarified to consider dedicated CN specifics and the procedure for re-balancing within dedidacted CNs is described.","27","6.3","Dedicated Core Networks (DECOR)",11830,"Available","2015-04-06T13:57:56.110","2015-04-07T12:58:00.930","S2-150267","","Rel-13","23.401","13.2.0","DECOR","2835","1","B",null,"","","","",""]
["S2-150917","Discussion on various aspects","Huawei, HiSilicon","Frank Mademann",6821,"other","","","This paper discusses various aspects related to DCOR and proposes resolutions.","27","6.3","Dedicated Core Networks (DECOR)",11270,"Available","2015-04-06T14:00:51.017","2015-04-07T12:58:00.960","","","Rel-13","","","","","","","","","","","",""]
["S2-150918","ProSe APN Configuration","Huawei, HiSilicon","Runze Zhou",60945,"other","","","In this contribution, the need for ProSe APN is analyzed and how to configure it to UE are proposed.","15","5.1","3GPP Packet Access Maintenance",10530,"Noted","2015-04-06T14:23:06.067","2015-04-07T12:26:40.343","","","Rel-12","","","","","","","","","","","",""]
["S2-150919","ProSe APN Configuration","Huawei, HiSilicon","Runze Zhou",60945,"CR","","","Summary of change: SA WG2 need to specify how network configues the ProSe APN to UE.","15","5.1","3GPP Packet Access Maintenance",10720,"Available","2015-04-06T14:23:06.080","2015-04-07T12:26:40.377","","","Rel-12","23.303","12.4.0","ProSe","0159","","B",null,"","","","",""]
["S2-150920","Solutions for the location related Key Issue","Alcatel-Lucent, Alcatel-Lucent Shanghai Bell","Nicolas Drevon",16459,"pCR","","","This P-CR provides some background on the existing location procedures during session establishment in Trusted WLAN, which can be used for emergency calls, and proposes two solutions for untrusted WLAN case for inclusion in the technical report.","41","6.17","Feasibility study on the Support of Emergency services over WLAN (FS_SEW)",13650,"Revised","2015-04-06T14:31:06.660","2015-04-07T11:36:56.433","","S2-151244","Rel-13","23.771","","","","","","","","","","",""]
["S2-150921","Discussion on whether DÉCOR applies to Gn-SGSN","Alcatel-Lucent, Alcatel-Lucent Shanghai Bell","Nicolas Drevon",16459,"other","","","This paper discusses whether DCOR should apply to Gn SGSN.","27","6.3","Dedicated Core Networks (DECOR)",11280,"Available","2015-04-06T14:33:49.430","2015-04-07T11:36:56.480","","","Rel-13","","","","","","","","","","","",""]
["S2-150922","New UE-initiated update procedures for Open Direct Discovery","Qualcomm Incorporated","Hong Cheng",25668,"pCR","","","This contribution proposes extending procedures over PC3 to enhance open discovery.","34","6.10","Extended Proximity-based Services TR Phase (eProSe-Ext-SA2TR)",12500,"Revised","2015-04-06T14:59:11.543","2015-04-07T02:02:25.727","","S2-151343","Rel-13","23.713","","eProSe-Ext-SA2TR","","","","","","","","",""]
["S2-150923","Conclusions for Model B discovery","Qualcomm Incorporated","Hong Cheng",25668,"pCR","","","This contribution proposes resolutions to several open issues, and the conclusions for the Model B discovery.","34","6.10","Extended Proximity-based Services TR Phase (eProSe-Ext-SA2TR)",12510,"Approved","2015-04-06T15:01:38.293","2015-04-07T02:05:49.910","","","Rel-13","23.713","","eProSe-Ext-SA2TR","","","","","","","","",""]
["S2-150924","Metadata upload for Open and Restricted Discovery","Qualcomm Incorporated","Hong Cheng",25668,"pCR","","","This contribution adds details on how to enable the ProSe Function to obtain the metadata that is currently specified to be returned (optionally) in the Match Report procedures. These are specified separately for Open Discovery and Restricted discovery.","34","6.10","Extended Proximity-based Services TR Phase (eProSe-Ext-SA2TR)",12520,"Revised","2015-04-06T15:04:01.847","2015-04-07T02:09:52.747","S2-150116","S2-151332","Rel-13","23.713","","eProSe-Ext-SA2TR","","","","","","","","",""]
["S2-150925","UE-to-Network Relay conclusions","Qualcomm Incorporated","Hong Cheng",25668,"pCR","","","This contribution reviewed several operational aspects for UE-to-Network Relay and their relevance to RAN enhancements. Proposals based on the discussions are suggested.","34","6.10","Extended Proximity-based Services TR Phase (eProSe-Ext-SA2TR)",12530,"Merged","2015-04-06T15:06:21.887","2015-04-07T02:11:59.037","","","Rel-13","23.713","","eProSe-Ext-SA2TR","","","","","","","","",""]
["S2-150926","Proximity estimation","Qualcomm Incorporated","Hong Cheng",25668,"pCR","","","Discusses solutions for proximity estimation.","34","6.10","Extended Proximity-based Services TR Phase (eProSe-Ext-SA2TR)",12540,"Revised","2015-04-06T15:08:25.467","2015-04-07T02:12:42.823","S2-150130","S2-151344","Rel-13","23.713","","eProSe-Ext-SA2TR","","","","","","","","",""]
["S2-150927","Introduce the Dedicated Core Network (DECOR) feature","NTT DOCOMO, Huawei","Irfan Ali",50390,"CR","","","Summary of change: Introduce the DECOR feature based on conclusions of TR 23.707","27","6.3","Dedicated Core Networks (DECOR)",11680,"Revised","2015-04-06T15:16:22.607","2015-04-07T13:25:23.133","S2-150651","S2-151321","Rel-13","23.401","13.2.0","DECOR","2837","3","B",null,"","","","",""]
["S2-150928","Introduce the Dedicated Core Network (DECOR) feature","NTT DOCOMO, Huawei","Irfan Ali",50390,"CR","","","Summary of change: Introduce the decor feature based on conclusions of TR 23.707.","27","6.3","Dedicated Core Networks (DECOR)",11790,"Revised","2015-04-06T15:16:22.763","2015-04-07T13:25:23.210","S2-150609","S2-151323","Rel-13","23.060","13.2.0","DECOR","1953","2","B",null,"","","","",""]
["S2-150929","Discussion on intra-DECOR offloading","NTT DOCOMO, Huawei","Irfan Ali",50390,"other","","","Determine which alternative would be adopted to resolve intra-dcor offloading.","27","6.3","Dedicated Core Networks (DECOR)",11310,"Available","2015-04-06T15:16:22.920","2015-04-07T13:25:23.257","","","Rel-13","","","","","","","","","","","",""]
["S2-150930","Intra-decor MME offloading","NTT DOCOMO","Irfan Ali",50390,"CR","","","Summary of change: Introduce the DECOR features on intra-decor offloading.","27","6.3","Dedicated Core Networks (DECOR)",11820,"Revised","2015-04-06T15:16:22.937","2015-04-07T13:25:23.287","","S2-151540","Rel-13","23.401","13.2.0","DECOR","2852","","B",null,"","","","",""]
["S2-150931","Introduce the Dedicated Core Network (DECOR) feature of intra-DECOR offloading","NTT DOCOMO","Irfan Ali",50390,"CR","","","WITHDRAWN: 23.060 CR1962: Introduce the Dedicated Core Network (DECOR) feature of intra-DECOR offloading","55","99","Reserved and Withdrawn documents",17220,"Withdrawn","2015-04-06T15:16:22.997",null,"","","Rel-13","23.060","13.2.0","DECOR","1962","","B",null,"","","","",""]
["S2-150932","WID update on DECOR","NTT DOCOMO","Irfan Ali",50390,"WID","","","Update the number of plenary meeting.","27","6.3","Dedicated Core Networks (DECOR)",11330,"Revised","2015-04-06T15:16:23.060","2015-04-07T13:25:23.337","","S2-151542","Rel-13","","","","","","","","","","","",""]
["S2-150933","[DRAFT]  Request  specification of Dedicated Core Network (DECOR) feature","NTT DOCOMO","Irfan Ali",50390,"LS out","","","Ask CT WG4 to initiate the specification of DCOR feature.","27","6.3","Dedicated Core Networks (DECOR)",0,"Available","2015-04-06T15:16:23.060","2015-04-07T13:25:23.367","","","Rel-13","","","","","","","",null,"CT WG4, RAN WG3"]
["S2-150934","[DRAFT] Request for specification of Dedicated Core Network (DECOR) feature","NTT DOCOMO","Irfan Ali",50390,"LS out","","","WITHDRAWN: [LS OUT] Request for specification of Dedicated Core Network (DECOR) feature","55","99","Reserved and Withdrawn documents",0,"Withdrawn","2015-04-06T15:16:23.077",null,"","","Rel-13","","","","","","","",null,"RAN WG3"]
["S2-150935","Adding ProSe related introductions and definitions","Qualcomm Incorporated","Hong Cheng",25668,"CR","","","Summary of change: Adding the introductions and definitions ProSe related entities and interfaces at appropriate places in the TS.","15","5.1","3GPP Packet Access Maintenance",10750,"Agreed","2015-04-06T15:16:46.087","2015-04-07T02:13:36.827","","","Rel-12","23.002","12.6.0","ProSe","0282","","B",null,"","","","",""]
["S2-150936","Introducing HSS-SCEF and MME/SGSN-SCEF Reference Points","Intel, Huawei, Alcatel-Lucent","Puneet Jain",36283,"CR","","","Summary of change: Adding the introductions and definitions ProSe related entities and interfaces at appropriate places in the TS.","30","6.6","Monitoring Enhancements (MONTE)",12800,"Revised","2015-04-06T15:29:31.270","2015-04-07T04:46:46.593","","S2-151213","Rel-13","23.002","13.1.0","MONTE","0283","","B",null,"","","","",""]
["S2-150937","Solution 4 - Corrections and Evaluation","Alcatel-Lucent, Intel","Mike Dolan",1692,"pCR","","","This contribution provides corrections and evaluation text to Solution 4 in TR 23.708 (AESE). Editor's notes are removed. The primary change is to remove the ability to change the chargeable party during a session, and rely instead on stopping the existing flow and restarting it with the desired chargeable party.","29","6.5","Architecture Enhancements for Service Exposure (AESE)",11720,"Noted","2015-04-06T15:50:28.770","2015-04-06T16:36:41.653","","","Rel-13","23.708","","","","","","","","","","",""]
["S2-150938","AESE – Solution 5 Corrections and Evaluations","Alcatel-Lucent","Mike Dolan",1692,"pCR","","","This contribution provides an evaluation of Solution 5 in TR 23.708 (AESE).","29","6.5","Architecture Enhancements for Service Exposure (AESE)",11730,"Noted","2015-04-06T15:53:45.660","2015-04-06T16:36:41.717","","","Rel-13","23.708","","","","","","","","","","",""]
["S2-150939","AESE – Solution 6 Evaluation","Alcatel-Lucent, Cisco Systems Inc","Mike Dolan",1692,"pCR","","","This contribution provides evaluation text for Solution 6 in TR 23.708 (AESE).","29","6.5","Architecture Enhancements for Service Exposure (AESE)",11740,"Revised","2015-04-06T15:55:46.093","2015-04-06T16:36:41.747","","S2-151241","Rel-13","23.708","","","","","","","","","","",""]
["S2-150940","AESE – Solution 8 Evaluation","Alcatel-Lucent","Mike Dolan",1692,"pCR","","","This contribution adds evaluation text to Solution 8 in TR 23.708 (AESE).","29","6.5","Architecture Enhancements for Service Exposure (AESE)",11750,"Withdrawn","2015-04-06T15:58:40.313","2015-04-06T16:36:41.777","","","Rel-13","23.708","","","","","","","","","","",""]
["S2-150941","AESE - Evaluation","Alcatel-Lucent","Mike Dolan",1692,"pCR","","","This contribution provides text for clause 7 in TR 23.708 (AESE).","29","6.5","Architecture Enhancements for Service Exposure (AESE)",11760,"Approved","2015-04-06T16:00:22.307","2015-04-06T16:36:41.810","","","Rel-13","23.708","","","","","","","","","","",""]
["S2-150942","AESE - Conclusions","Alcatel-Lucent, Intel","Mike Dolan",1692,"pCR","","","This contribution provides conclusions text for clause 8 in TR 23.708 (AESE).","29","6.5","Architecture Enhancements for Service Exposure (AESE)",11770,"Revised","2015-04-06T16:01:47.670","2015-04-06T16:36:41.840","","S2-151257","Rel-13","23.708","","","","","","","","","","",""]
["S2-150943","GROUPE Conclusions","Alcatel-Lucent","Mike Dolan",1692,"pCR","","","This contribution provides the remainder of the conclusions for TR 23.769 (GROUPE).","31","6.7","Group based Enhancements (GROUPE)",12010,"Merged","2015-04-06T16:03:31.613","2015-04-06T16:36:41.870","","","Rel-13","23.769","","GROUPE","","","","","","","","",""]
["S2-150944","Remove Editor’s Notes","Alcatel-Lucent","Mike Dolan",1692,"pCR","","","This contribution provides text to remove some editor's notes in TR 23.769 (GROUPE).","31","6.7","Group based Enhancements (GROUPE)",12020,"Revised","2015-04-06T16:05:04.620","2015-04-06T16:36:41.917","","S2-151157","Rel-13","23.769","","GROUPE","","","","","","","","",""]
["S2-150945","[DRAFT] LS on APIs for using MBMS","Alcatel-Lucent","Mike Dolan",1692,"LS out","","","SA WG2 wish to inform GSMA and OMA of work done during Release 13 on service exposure that allows an application to take advantage of access to the MBMS system.","31","6.7","Group based Enhancements (GROUPE)",0,"Noted","2015-04-06T16:07:11.573","2015-04-06T16:36:41.950","","","Rel-13","","","","","","","",null,"GSMA, OMA","oneM2M"]
["S2-150946","Solution A for Key Issue 1","Alcatel-Lucent, Nokia Networks","Mike Dolan",1692,"pCR","","","This contribution provides a solution to address the Key Issues for MBMS enhancements in Rel-13.","38","6.14","MBMS Enhancements (MBMS_enh)",13190,"Revised","2015-04-06T16:09:28.857","2015-04-06T16:36:41.967","","S2-151097","Rel-13","23.741","","","","","","","","","","",""]
["S2-150947","Solution 1 – Impacts and Evaluation","Alcatel-Lucent","Mike Dolan",1692,"pCR","","","This contribution provides text for the Solution 1 impacts and evaluation clauses in TR 23.709 (HLCom).","36","6.12","Optimizations to Support High Latency Communications (FS_HLCom)",12870,"Available","2015-04-06T16:11:39.850","2015-04-06T16:36:41.997","","","Rel-13","23.709","","","","","","","","","","",""]
["S2-150948","HLCom – Solution 4 – add SCEF, additional evaluation text","Alcatel-Lucent","Mike Dolan",1692,"pCR","","","This contribution provides additional evaluation text to Solution 4 in TR 23.709 (HLCom) to indicate that Solution 4 incorporates Solution 3 and elaborates on MME actions. It also updates the figures and flows to include the SCEF.","36","6.12","Optimizations to Support High Latency Communications (FS_HLCom)",12880,"Revised","2015-04-06T16:14:58.420","2015-04-06T16:36:42.027","","S2-151177","Rel-13","23.709","","","","","","","","","","",""]
["S2-150949","HLCom – Solution 6 impacts and evaluation","Alcatel-Lucent","Mike Dolan",1692,"pCR","","","This contribution provides additional impacts and evaluation text for Solution 6 in TR 23.709 (HLCom).","36","6.12","Optimizations to Support High Latency Communications (FS_HLCom)",12890,"Available","2015-04-06T16:16:37.480","2015-04-06T16:36:42.060","","","Rel-13","23.709","","","","","","","","","","",""]
["S2-150950","eDRX – Idle Mode Issue 2: Solution A","Alcatel-Lucent, Qualcomm Incorporated","Mike Dolan",1692,"pCR","","","This contribution provides text for Solution A to Idle Mode Issue 2 in TR 23.770 (eDRX).","39","6.15","Feasibility study on Extended DRX cycle for Power Consumption Optimization (FS_eDRX)",13400,"Revised","2015-04-06T16:18:35.557","2015-04-06T16:36:42.090","","S2-151232","Rel-13","23.770","","","","","","","","","","",""]
["S2-150951","MBMS Session Start procedure correction and editorial corrections","China Telecom","Lin Wu",61553,"CR","","","Summary of change: It modidies the flow 8.3.2 to change that the MBMS GW initiates IP Multicast distribution and/or unicast bearers in step 6. It adds abbreviation MCE and modifies document accordingly. Some editorial corrections.","22","6.1.1","Rel-13 3GPP Pkt Access Maintenance",11510,"Revised","2015-04-06T17:56:02.857","2015-04-06T17:59:14.490","","S2-151138","Rel-13","23.246","13.0.0","TEI13, MBMS_enh","0392","","F",null,"","","","",""]
["S2-150952","OMR handling of SDP offer-answer exchanges after media path has been selected","Nokia Networks, Ericsson","Martin Oettl",17230,"CR","","","Summary of change: In subsequent SDP offer-answer exchanges, OMR procedures shall not change the media path. Details of those procedures are left for stage 3 work.","18","5.4","IMS-Related Maintenance",11330,"Revised","2015-04-06T19:28:54.067","2015-04-06T19:52:20.257","","S2-151671","Rel-10","23.228","10.8.0","OMR","1123","","F",null,"","","","",""]
["S2-150953","OMR handling of SDP offer-answer exchanges after media path has been selected","Nokia Networks, Ericsson","Martin Oettl",17230,"CR","","","Rel-11 mirror CR: Summary of change: In subsequent SDP offer-answer exchanges, OMR procedures shall not change the media path. Details of those procedures are left for stage 3 work.","18","5.4","IMS-Related Maintenance",11340,"Revised","2015-04-06T19:28:54.143","2015-04-06T19:52:20.303","","S2-151676","Rel-11","23.228","11.10.0","OMR","1124","","A",null,"","","","",""]
["S2-150954","OMR handling of SDP offer-answer exchanges after media path has been selected","Nokia Networks, Ericsson","Martin Oettl",17230,"CR","","","Rel-12 mirror CR: Summary of change: In subsequent SDP offer-answer exchanges, OMR procedures shall not change the media path. Details of those procedures are left for stage 3 work.","18","5.4","IMS-Related Maintenance",11350,"Revised","2015-04-06T19:28:54.207","2015-04-06T19:52:20.320","","S2-151677","Rel-12","23.228","12.8.0","OMR","1125","","A",null,"","","","",""]
["S2-150955","OMR handling of SDP offer-answer exchanges after media path has been selected","Nokia Networks, Ericsson","Martin Oettl",17230,"CR","","","Rel-13 mirror CR: Summary of change: In subsequent SDP offer-answer exchanges, OMR procedures shall not change the media path. Details of those procedures are left for stage 3 work.","18","5.4","IMS-Related Maintenance",11360,"Revised","2015-04-06T19:28:54.253","2015-04-06T19:52:20.350","","S2-151679","Rel-13","23.228","13.2.0","OMR","1126","","A",null,"","","","",""]
["S2-150956","High Level Description Solution 3","Nokia Networks, Huawei","Martin Oettl",17230,"pCR","","","This paper adds text for the high level description of solution 3.","33","6.9","Enhancements to WEBRTC interoperability (eWebRTCi)",12150,"Available","2015-04-06T19:28:54.317","2015-04-07T12:24:03.190","","","Rel-13","23.706","","eWebRTCi","","","","","","","","",""]
["S2-150957","Support of Procedures requiring the IMSI","Nokia Networks","Martin Oettl",17230,"pCR","","","This paper resolves an EN asking whether any of the proposed solutions is able to support procedures which require knowledge of the IMSI (e.g. SRVCC, T-ADS).","33","6.9","Enhancements to WEBRTC interoperability (eWebRTCi)",12160,"Available","2015-04-06T19:28:54.333","2015-04-07T06:15:42.833","","","Rel-13","23.706","","eWebRTCi","","","","","","","","",""]
["S2-150958","Potential reduction of scope of the WID","Nokia Networks","Martin Oettl",17230,"other","","","The paper discusses how to limit the work on WebRTC Rel-13.","33","6.9","Enhancements to WEBRTC interoperability (eWebRTCi)",12170,"Noted","2015-04-06T19:28:54.333","2015-04-07T05:12:29.687","","","Rel-13","","","","","","","","","","","",""]
["S2-150959","Resiliency Aspects for Solution 3","Nokia Networks","Martin Oettl",17230,"pCR","","","This paper adds text regarding resiliency aspects of solution 3.","33","6.9","Enhancements to WEBRTC interoperability (eWebRTCi)",12180,"Approved","2015-04-06T19:28:54.333","2015-04-07T06:13:53.477","","","Rel-13","23.706","","eWebRTCi","","","","","","","","",""]
["S2-150960","Evaluation of Solution 3 +5","Nokia Networks, Huawei","Martin Oettl",17230,"pCR","","","This paper adds text allowing an evaluation of solution 3 +5.","33","6.9","Enhancements to WEBRTC interoperability (eWebRTCi)",12190,"Revised","2015-04-06T19:28:54.347","2015-04-07T14:22:02.013","","S2-151170","Rel-13","23.706","","eWebRTCi","","","","","","","","",""]
["S2-150961","Text for the Overall Evaluation Section","Nokia Networks","Martin Oettl",17230,"pCR","","","This paper adds text allowing an evaluation of solution 3 +5.","37","6.13","Flexible Mobile Service Steering (FMSS)",13080,"Noted","2015-04-06T19:28:54.347","2015-04-07T13:29:11.187","","","Rel-13","23.718","","FMSS","","","","","","","","",""]
["S2-150962","Skeletton and scope for TR 23.771 (FS_SEW)","Alcatel-Lucent, Alcatel-Lucent ShangHai Bell","Laurent Thiebaut",11066,"pCR","","","Skeleton and scope for TR 23.771 (FS_SEW)","41","6.17","Feasibility study on the Support of Emergency services over WLAN (FS_SEW)",13660,"Revised","2015-04-06T19:44:31.317","2015-04-06T21:08:31.237","","S2-151246","Rel-13","23.771","","FS_SEW","","","","","","","","",""]
["S2-150963","Evaluation Comparison of Solutions in Section 5","T-Mobile USA","Christopher Joul",31136,"pCR","","","This document includes evaluation comparison table for solution 1,2 and 3","33","6.9","Enhancements to WEBRTC interoperability (eWebRTCi)",12200,"Revised","2015-04-06T20:02:53.010","2015-04-06T20:25:05.927","","S2-151171","Rel-13","23.706","","","","","","","","","","",""]
["S2-150964","Key issues: UE Location Information","T-Mobile USA","Christopher Joul",31136,"pCR","","","Describe the key issues related to the Location of the UE.","41","6.17","Feasibility study on the Support of Emergency services over WLAN (FS_SEW)",13670,"Revised","2015-04-06T20:05:22.830","2015-04-06T20:25:05.957","","S2-151260","Rel-13","23.771","","","","","","","","","","",""]
["S2-150965","First list of Key issues: AAA server knowledge of emergency & Location","Alcatel-Lucent, Alcatel-Lucent ShangHai Bell, Qualcom Inc","Laurent Thiebaut",11066,"pCR","","","Proposes key issues to 23.771 about AAA server knowledge of emergency & about Location","41","6.17","Feasibility study on the Support of Emergency services over WLAN (FS_SEW)",13680,"Revised","2015-04-06T20:27:58.150","2015-04-07T14:12:40.007","","S2-151243","Rel-13","23.771","","FS_SEW","","","","","","","","",""]
["S2-150966","Key issue: QoS","Alcatel-Lucent, Alcatel-Lucent ShangHai Bell","Laurent Thiebaut",11066,"pCR","","","Proposes a key issue to 23.771 about QoS","41","6.17","Feasibility study on the Support of Emergency services over WLAN (FS_SEW)",13690,"Revised","2015-04-06T20:30:17.847","2015-04-07T14:12:40.037","","S2-151250","","23.771","","FS_SEW","","","","","","","","",""]
["S2-150967","A solution for ePDG selection","Alcatel-Lucent, Alcatel-Lucent ShangHai Bell","Laurent Thiebaut",11066,"pCR","","","A solution for ePDG selection","41","6.17","Feasibility study on the Support of Emergency services over WLAN (FS_SEW)",13700,"Revised","2015-04-06T20:41:49.067","2015-04-07T14:12:40.067","","S2-151263","","23.771","","FS_SEW","","","","","","","","",""]
["S2-150968","Update to the SID on Feasibility study on the Support of Emergency services over WLAN","Alcatel-Lucent, Alcatel-Lucent ShangHai Bell","Laurent Thiebaut",11066,"WID","","","Revised WID TR presented for approval at end of phase 2","50","7.1","New and Revised Work Items, Cover sheets for completed work items",13820,"Revised","2015-04-06T20:44:19.283","2015-04-06T21:04:29.080","","S2-151309","Rel-13","","","","","","","","","","","",""]
["S2-150969","Handling of UE-initiated and NW-initiated NBIFOM modes","Alcatel-Lucent, Alcatel-Lucent ShangHai Bell, Verizon, Broadcom Corporation","Laurent Thiebaut",11066,"pCR","","","work on two NBIFOM modes (UE-initiated NBIFOM mode and NW-initiated NBIFOM mode","28","6.4","IP Flow Mobility support for S2a and S2b interfaces (NBIFOM)",11560,"Noted","2015-04-06T20:47:37.230","2015-04-07T14:12:40.113","","","Rel-13","23.861","","NBIFOM","","","","","","","","",""]
["S2-150970","Clarification on Solution 1 in § 5.2: forking","Alcatel-Lucent, Alcatel-Lucent ShangHai Bell","Laurent Thiebaut",11066,"pCR","","","clarifies how forking is supported with Solution 1 in 5.2","33","6.9","Enhancements to WEBRTC interoperability (eWebRTCi)",12210,"Approved","2015-04-06T20:50:28.020","2015-04-07T14:12:40.147","","","","23.706","","eWebRTCi","","","","","","","","",""]
["S2-150971","Clarification on Solution 1 in § 5.2: routing of terminating sessions","Alcatel-Lucent, Alcatel-Lucent ShangHai Bell","Laurent Thiebaut",11066,"pCR","","","clarifies Solution 1 in 5.2 especially on the routing of terminating sessions","33","6.9","Enhancements to WEBRTC interoperability (eWebRTCi)",12220,"Approved","2015-04-06T20:52:02.337","2015-04-07T17:31:04.427","","","","23.706","","eWebRTCi","","","","","","","","",""]
["S2-150972","Clarification on Solution 1 in § 5.2: scalability and service resiliency","Alcatel-Lucent, Alcatel-Lucent ShangHai Bell","Laurent Thiebaut",11066,"pCR","","","Clarification on Solution 1 in 5.2: scalability and service resiliency","33","6.9","Enhancements to WEBRTC interoperability (eWebRTCi)",12230,"Revised","2015-04-06T20:54:00.880","2015-04-07T14:12:40.177","","S2-151152","","23.706","","eWebRTCi","","","","","","","","",""]
["S2-150973","Evaluation Criteria For Solution 5.2.1","Alcatel-Lucent, Alcatel-Lucent ShangHai Bell","Laurent Thiebaut",11066,"pCR","","","Evaluation Criteria For Solution 5.2.1","33","6.9","Enhancements to WEBRTC interoperability (eWebRTCi)",12240,"Revised","2015-04-06T20:55:55.743","2015-04-07T14:12:40.207","","S2-151168","","23.706","","eWebRTCi","","","","","","","","",""]
["S2-150974","Reduction of eWebRTCi scope","Alcatel-Lucent, Alcatel-Lucent ShangHai Bell","Laurent Thiebaut",11066,"pCR","","","Reduction of eWebRTCi scope","33","6.9","Enhancements to WEBRTC interoperability (eWebRTCi)",12250,"Revised","2015-04-06T20:58:18.407","2015-04-07T14:12:40.223","","S2-151151","","23.706","","eWebRTCi","","","","","","","","",""]
["S2-150975","Modifications to issues for extended DRX","Qualcomm Incorporated, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell","Miguel Griot",43100,"pCR","","","Proposes to include defer solutions for MME restart issue to CT WG4, indicate that the issue of MT data handling is handled in HLCom, and adds new issue for connected mode eDRX, how MME indicates support of eDRX and eDRX cycle value range for connected mode.","39","6.15","Feasibility study on Extended DRX cycle for Power Consumption Optimization (FS_eDRX)",13410,"Approved","2015-04-06T22:30:38.467","2015-04-07T06:07:09.977","","","Rel-13","23.770","","FS_eDRX","","","","","","","","",""]
["S2-150976","Extended I-DRX and PSM coexistence","Qualcomm Incorporated","Miguel Griot",43100,"pCR","","","Proposes that it is SGSN/MME decision whether to enable only one of extended I-DRX or PSM, or use both.","39","6.15","Feasibility study on Extended DRX cycle for Power Consumption Optimization (FS_eDRX)",13420,"Revised","2015-04-06T22:30:38.483","2015-04-07T06:07:10.023","","S2-151234","Rel-13","23.770","","FS_eDRX","","","","","","","","",""]
["S2-150977","RAN and CN  coordination for extended C-DRX (Issue 1)","Qualcomm Incorporated","Miguel Griot",43100,"pCR","","","Proposes signalling from CN to RAN to authorize use of extended C-DRX, and from RAN to CN to indicate extended C-DRX has been enabled/disabled.","39","6.15","Feasibility study on Extended DRX cycle for Power Consumption Optimization (FS_eDRX)",13430,"Noted","2015-04-06T22:30:38.483","2015-04-07T07:38:49.357","","","Rel-13","23.770","","FS_eDRX","","","","","","","","",""]
["S2-150978","Extended C-DRX: New connected mode substate in the core network to handle NAS retransmissions and MT SMS (Issues 2 and 3)","Qualcomm Incorporated","Miguel Griot",43100,"pCR","","","Proposes to add a new sub-state for connected mode in the core network called temporarily unavailable, when the RAN has indicated the extended C-DRX has been enabled. When the MME is in this state, it asks RAN to disable eC-DRX when MT SMS or NW initiated procedure arrives.","39","6.15","Feasibility study on Extended DRX cycle for Power Consumption Optimization (FS_eDRX)",13440,"Revised","2015-04-06T22:30:38.497","2015-04-07T07:38:49.373","","S2-151259","Rel-13","23.770","","FS_eDRX","","","","","","","","",""]
["S2-150979","GROUPE Conclusions","Qualcomm Incorporated","Miguel Griot",43100,"pCR","","","Provides modifications to the conclusions based on UE support of MBMS.","31","6.7","Group based Enhancements (GROUPE)",12040,"Revised","2015-04-06T22:30:38.497","2015-04-07T06:07:10.057","","S2-151156","Rel-13","23.769","","GROUPE","","","","","","","","",""]
["S2-150980","[DRAFT] LS  on RAN assumptions from SA2 for FS_eDRX","Qualcomm Incorporated","Miguel Griot",43100,"LS out","","","Provides information to GERAN/RAN WG2 on the assumptions on RAN behaviour for FS_eDRX and requests corroboration.","39","6.15","Feasibility study on Extended DRX cycle for Power Consumption Optimization (FS_eDRX)",0,"Revised","2015-04-06T22:30:38.497","2015-04-07T07:38:49.417","","S2-151288","Rel-13","","","","","","","",null,"TSG GERAN, RAN WG2"]
["S2-150981","[DRAFT]  Reply LS on Clarification regarding change of active time value and periodic TAU or RAU timer value for UE supporting PSM","Qualcomm Incorporated","Miguel Griot",43100,"LS out","","","Replies that UE can start RAU/TAU when change in condition in the UE triggers a need for a different active time/periodic RAU/TAU timer.","15","5.1","3GPP Packet Access Maintenance",10450,"Revised","2015-04-06T22:30:38.513","2015-04-07T06:07:10.087","","S2-151133","Rel-12","","","","","","","","S2-150708","CT WG1"]
["S2-150982","Consideration for the GCSE_LTE Architecture to include the ProSe UE-Network Relay","U.S. Department of Commerce","Randy Bloomfield",56665,"other","","","This contribution discusses the need for ProSe UE-Network Relay architecture solution(s) to be specified in TS 23.468 (Group Communication System Enablers for LTE (GCSE_LTE); Stage 2).","26","6.2","Mission Critical Push-to-Talk over LTE (MCPTT)",11160,"Available","2015-04-06T23:57:32.860","2015-04-07T00:22:03.437","","","Rel-13","","","","","","","","","","","",""]
["S2-150983","MCC CR Implementation correction: Group specific NAS Level congestion control","MCC","Maurice Pope",648,"CR","","","Summary of change: Adds Group ID-list entries into tables 5.7.1-1 and 5.7.2-1 to correct implementation of agreed CR 23.401 CR2822R4.","31","6.7","Group based Enhancements (GROUPE)",13320,"Agreed","2015-04-07T05:24:50.190","2015-04-07T05:46:07.317","","","Rel-13","23.401","13.2.0","GROUPE","2853","","C",null,"","","","",""]
["S2-150984","Removing alternatives from S2b call flows","Apple Inc.","Krisztian Kiss",57762,"pCR","","","This contribution proposes to close Editor's Notes 18 from the Open Issues list and align clause 7.5.4 (S2b flows) with clause 7.3.2 (S2a flows).","28","6.4","IP Flow Mobility support for S2a and S2b interfaces (NBIFOM)",11570,"Revised","2015-04-07T06:05:34.673","2015-04-07T07:23:38.767","","S2-151253","Rel-13","23.861","","NBIFOM-SA2TR","","","","","","","","",""]
["S2-150985","Discussion on _x00B_S8HR VoLTE Roaming","NTT DOCOMO INC.","Motohiro Abe",57779,"other","","","This discussion provides the overview of the GSMA LS on VoLTE Roaming and proposes the way forward.","8","4.2","LS (S2-150704) on VoLTE Roaming and Replies",10200,"Noted","2015-04-07T06:07:12.443","2015-04-07T08:25:26.257","","","","","","","","","","","","","","",""]
["S2-150986","[DRAFT] Reply LS on VoLTE Roaming Architecture","NTT DOCOMO INC.","Motohiro Abe",57779,"LS out","","","Draft LS back to GSMA on VoLTE Roaming Architecture","8","4.2","LS (S2-150704) on VoLTE Roaming and Replies",0,"Revised","2015-04-07T06:08:55.810","2015-04-07T08:25:26.303","","S2-151121","","","","","","","","","S2-150704","GSMA PSMC, NG, SA WG3, SA WG3-LI","GSMA WAS, IDS,  TSG SA, CT WG3"]
["S2-150987","Conclusions for indication of 3GPP access loss in SCM","LG Electronics","Hyunsook Kim",42013,"pCR","","","This P-CR proposes the conclusions for 3GPP access loss indication in Single-connection mode.","28","6.4","IP Flow Mobility support for S2a and S2b interfaces (NBIFOM)",11580,"Revised","2015-04-07T06:10:31.720","2015-04-07T07:05:30.043","","S2-151228","Rel-13","23.861","","NBIFOM","","","","","","","","",""]
["S2-150988","Proposed Solution for Key Issue 1 using Application-level Zones","Motorola Solutions","Val Oprescu",14981,"pCR","","","This contribution proposes a solution for Key issue 1 for Rel-13 using Application-level Zones (ALZ) in lieu of service areas, to request/modify service. An ALZ can be an entire MBSFN area or a single cell, thus it can be used for SC-PTM. The ECGIs are available for all other uses, including being mapped to the ALZs locally (i.e. without interaction with the MBMS system).","38","6.14","MBMS Enhancements (MBMS_enh)",13200,"Noted","2015-04-07T06:10:33.560","2015-04-07T06:24:44.530","","S2-151633","Rel-13","23.741","","","","","","","","","","",""]
["S2-150989","Discussion on unauthenticated IMS Emergency Call","NTT DOCOMO INC.","Motohiro Abe",57779,"other","","","This Discussion paper discusses the problems with the current standards regarding IMS emergency call (with no IMS registration)","8","4.2","LS (S2-150704) on VoLTE Roaming and Replies",10310,"Noted","2015-04-07T06:11:59.597","2015-04-07T08:25:26.333","","","Rel-9","","","","","","","","","","","",""]
["S2-150990","Update of the solution using IP multicast in the UE-to-NW Relay","Nokia Networks","György Wolfner",31366,"pCR","","","This paper updates the solution using IP Multicast in the UE-to-Network Relay in section 7.2.2.4 to make the description of the solution complete and clarifies the impacts of the solution on existing network elements and interfaces.","34","6.10","Extended Proximity-based Services TR Phase (eProSe-Ext-SA2TR)",12550,"Revised","2015-04-07T06:14:12.820","2015-04-07T13:34:40.830","","S2-151335","Rel-13","23.713","","","","","","","","","","",""]
["S2-150991","Enable ISR for PS-only UE","CATT","Ming Ai",40862,"CR","","","Summary of change: 1. It is proposed that in such case the SGSN should activate ISR if 'SMS in SGSN' is used. 2. In such case, it is further proposed that SGSN forward received MT short message to MME.","45","6.20.1","TEI13 Category B/C for 3GPP Packet Access",16520,"Revised","2015-04-07T06:14:42.697","2015-04-07T08:13:42.943","S2-150295","S2-151135","Rel-13","23.060","13.2.0","SIMTC, TEI13","1893","4","C",null,"","","","",""]
["S2-150992","Correction of IMS Emergency Call without IMS emergency registration","NTT DOCOMO","Motohiro Abe",57779,"CR","","","Summary of change: - When IMS emergency registration fails, then UE retries with IMS emergency call without IMS registratin","8","4.2","LS (S2-150704) on VoLTE Roaming and Replies",10370,"Available","2015-04-07T06:14:46.237","2015-04-07T08:25:26.363","","","Rel-9","23.167","9.14.0","IMS_EMER_GPRS_EPS","0277","","F",null,"","","","",""]
["S2-150993","Per-PLMN configuration in P-CSCF for Non UE Detectable Emergency Call Handling","NTT DOCOMO","Motohiro Abe",57779,"CR","","","Summary of change: Clarify that P-CSCF takes into account MCC of the PLMN where UE is currently located.","8","4.2","LS (S2-150704) on VoLTE Roaming and Replies",10380,"Available","2015-04-07T06:16:43.877","2015-04-07T08:25:26.397","","","Rel-13","23.167","12.1.0","TEI13","0278","","C",null,"","","","",""]
["S2-150994","Enable ISR for PS-only UE","CATT","Ming Ai",40862,"CR","","","Summary of change: 1. It is proposed that in such case the SGSN should activate ISR in Combined RAU procedure if 'SMS in SGSN' is used. 2. If 'SMS in MME' is used, the MME should activated ISR, as well. 3. If 'SMS in SGSN' is used for a UE, the SGSN does","45","6.20.1","TEI13 Category B/C for 3GPP Packet Access",16540,"Revised","2015-04-07T06:17:14.687","2015-04-07T08:13:42.927","S2-150296","S2-151136","Rel-13","23.272","12.5.0","SIMTC, TEI13","0939","4","C",null,"","","","",""]
["S2-150995","Support of Session Continuity with UE-Network Relays","Nokia Networks","György Wolfner",31366,"pCR","","","It is proposed to agree that in Rel-13 the use of Mobile IP is the solution if an application requires service continuity with IP address preservation when there is switch from EPC path to a path via a Relay UE.","34","6.10","Extended Proximity-based Services TR Phase (eProSe-Ext-SA2TR)",12560,"Noted","2015-04-07T06:17:34.920","2015-04-07T13:34:40.877","","","Rel-13","23.713","","","","","","","","","","",""]
["S2-150996","Removing alternatives from S2a call flows","Apple Inc., Huawei, Hisilicon","Krisztian Kiss",57762,"pCR","","","This contribution proposes to close Editor's Notes 8a, 9, 11a and 16a from the Open Issues list and align section 7.5.4 (S2b flows) with section 7.3.2 (S2a flows).","28","6.4","IP Flow Mobility support for S2a and S2b interfaces (NBIFOM)",11590,"Revised","2015-04-07T06:18:13.700","2015-04-07T07:23:38.830","","S2-151252","Rel-13","23.861","","NBIFOM-SA2TR","","","","","","","","",""]
["S2-150997","Supporting a roaming scenario where ATCF/ATGW in HPLMN","NTT DOCOMO","Motohiro Abe",57779,"CR","","","Summary of change: Clarify that ATCF/ATGW can be in HPLMN.","8","4.2","LS (S2-150704) on VoLTE Roaming and Replies",10390,"Available","2015-04-07T06:18:40.267","2015-04-07T08:25:26.443","","","Rel-13","23.237","12.8.0","TEI13","0482","","C",null,"","","","",""]
["S2-150998","Corrections in ProSe UE-NW Relay discovery","Nokia Networks, Qualcomm Incorporated","György Wolfner",31366,"pCR","","","This paper investigates the usefulness of providing the 'APN information' and the PLMN ID from the Relay during the ProSe UE-NW Relay discovery and proposes certain mechanisms to do that.","34","6.10","Extended Proximity-based Services TR Phase (eProSe-Ext-SA2TR)",12570,"Revised","2015-04-07T06:20:51.043","2015-04-07T13:34:40.907","","S2-151336","Rel-13","23.713","","","","","","","","","","",""]
["S2-150999","Clarification of the meaning of 'VPLMN Address Allowed' flag","NTT DOCOMO","Motohiro Abe",57779,"CR","","","Summary of change: Clarify that 'VPLMN Address Allowed' flag no other meaning but to indicate whether LBO is allowed on the APN associated with the flag.","8","4.2","LS (S2-150704) on VoLTE Roaming and Replies",10400,"Available","2015-04-07T06:21:25.520","2015-04-07T08:25:26.473","","","Rel-13","23.401","13.2.0","TEI13","2854","","F",null,"","","","",""]
["S2-151000","Netloc for IMS Registration","NTT DOCOMO","Motohiro Abe",57779,"CR","","","Summary of change: Adds netloc support for IMS registration","8","4.2","LS (S2-150704) on VoLTE Roaming and Replies",10410,"Available","2015-04-07T06:23:00.913","2015-04-07T08:25:26.507","","","Rel-13","23.228","13.2.0","TEI13","1127","","B",null,"","","","",""]
["S2-151001","Clarification regarding change of active time value and periodic TAU or RAU timer value for UE supporting PSM","HTC Corporation","Kundan Tiwari",44236,"LS out","","","To: CT WG1","55","99","Reserved and Withdrawn documents",0,"Withdrawn","2015-04-07T06:29:14.660","2015-04-07T06:35:35.597","","","Rel-12","","","","","","","",null,"CT WG1"]
["S2-151002","LS response on “Flow ID supplied by GCS AS”","Motorola Solutions Germany","Val Oprescu",14981,"LS out","","","Draft response to S2-150712 (C3-150446)","15","5.1","3GPP Packet Access Maintenance",0,"Noted","2015-04-07T06:31:17.933","2015-04-07T06:58:38.970","","","Rel-12","","","","","","","","S2-150712","CT WG3"]
["S2-151003","Problems and solutions for Co-existing of 'SMSoverSGs', 'SMSinSGSN', 'SMSinMME'","CATT","Ming Ai",40862,"other","","","This DP analyse problem of the co-existing of SMSoverSG, SMSinMME and SMSinSGSN, and propose some solutions.","45","6.20.1","TEI13 Category B/C for 3GPP Packet Access",13790,"Noted","2015-04-07T06:39:48.693","2015-04-07T08:13:42.880","S2-150294","","","","","","","","","","","","","",""]
["S2-151004","LS response for SC-PTM transmission","Motorola Solutions Germany","Val Oprescu",14981,"LS out","","","To: RAN WG2 CC: RAN WG3","38","6.14","MBMS Enhancements (MBMS_enh)",0,"Noted","2015-04-07T06:42:43.210","2015-04-07T06:58:39.017","","","Rel-13","","","","","","","","S2-150726","RAN WG2","RAN WG3"]
["S2-151005","Clarification on MBMS based solution","ZTE","Zhendong Li",38521,"pCR","","","This contribution proposes clarifications on the MBMS based solution, e.g. HSS behaviour and impacts.","31","6.7","Group based Enhancements (GROUPE)",12060,"Merged","2015-04-07T06:45:34.657","2015-04-07T08:45:07.200","","S2-151158","Rel-13","23.769","","GROUPE","","","","","","","","",""]
["S2-151006","Mapping Geographic Area to MBMS SAI and Cell IDs","ZTE","Zhendong Li",38521,"pCR","","","This contribution proposes a solution in which the BM-SC has the capability to map geographic area to MBMS SAI and/or Cell IDs, without impacts on MBMS infrastructure.","38","6.14","MBMS Enhancements (MBMS_enh)",13210,"Available","2015-04-07T06:45:34.670","2015-04-07T08:45:07.230","","","Rel-13","23.741","","MBMS_enh","","","","","","","","",""]
["S2-151007","Discussion on the how to avoid SRVCC","ZTE","Zhendong Li",38521,"pCR","","","This paper analyzes the solutions on how to avoid the SRVCC and proposes the suggestion","33","6.9","Enhancements to WEBRTC interoperability (eWebRTCi)",12260,"Revised","2015-04-07T06:45:34.687","2015-04-07T08:45:07.260","","S2-151184","Rel-13","23.706","","eWebRTCi","","","","","","","","",""]
["S2-151008","Clarification to the solution 4","ZTE","Zhendong Li",38521,"pCR","","","This paper makes clarification to the solution 4.","33","6.9","Enhancements to WEBRTC interoperability (eWebRTCi)",12270,"Revised","2015-04-07T06:45:34.703","2015-04-07T08:45:07.307","","S2-151167","Rel-13","23.706","","eWebRTCi","","","","","","","","",""]
["S2-151009","Way forward on the key issue - Architectural aspects for minimizing the need for bearer level protocol conversion","ZTE","Zhendong Li",38521,"pCR","","","This paper analyzes the solution on the key issue - 'Architectural aspects for minimizing the need for bearer level protocol conversion' and proposes the way forward.","33","6.9","Enhancements to WEBRTC interoperability (eWebRTCi)",12280,"Revised","2015-04-07T06:45:34.703","2015-04-07T08:45:07.323","","S2-151185","Rel-13","23.706","","eWebRTCi","","","","","","","","",""]
["S2-151010","Service Continuity via a ProSe UE-to-Network Relay","LG Electronics","Laeyoung Kim",40613,"pCR","","","This P-CR proposes a solution for Service Continuity via a ProSe UE-to-Network Relay.","34","6.10","Extended Proximity-based Services TR Phase (eProSe-Ext-SA2TR)",12580,"Noted","2015-04-07T07:00:10.090","2015-04-07T08:03:17.333","","","Rel-13","23.713","","eProSe-Ext-SA2","","","","","","","","",""]
["S2-151011","Radio resource usage for Stateless ProSe UE-to-UE Relay","LG Electronics","Laeyoung Kim",40613,"pCR","","","This P-CR discusses and proposes radio resource usage for stateless ProSe UE-to-UE Relay.","34","6.10","Extended Proximity-based Services TR Phase (eProSe-Ext-SA2TR)",12590,"Noted","2015-04-07T07:01:44.563","2015-04-07T08:03:17.380","","","Rel-13","23.713","","eProSe-Ext-SA2","","","","","","","","",""]
["S2-151012","Alternative proposal for monitoring event configuration procedure to cover removal/replace","LG Electronics","Laeyoung Kim",40613,"other","","","This discussion paper proposes a single procedure for new monitoring configuration as well as monitoring configuration removal/replace.","30","6.6","Monitoring Enhancements (MONTE)",11920,"Available","2015-04-07T07:05:03.557","2015-04-07T08:03:17.397","","","Rel-13","","","","","","","","","","","",""]
["S2-151013","Need for more reliable MBMS signalling for Public Safety","Motorola Solutions","Val Oprescu",14981,"pCR","","","Proposes Key Issue to be studied: make the signalling complete and reliable","38","6.14","MBMS Enhancements (MBMS_enh)",13220,"Noted","2015-04-07T07:12:50.807","2015-04-07T07:51:42.883","","","Rel-13","23.741","","MBMS_enh","","","","","","","","",""]
["S2-151014","A clarification for Gx based solution","China Unicom, China Telecom, Intel","Maurice Pope",648,"pCR","","","WITHDRAWN: A clarification for Gx based solution","55","99","Reserved and Withdrawn documents",13930,"Withdrawn","2015-04-08T13:41:11.917",null,"","","Rel-13","23.718","","FMSS","","","","","","","","",""]
["S2-151015","LS from GSMA RAG: LS on VoLTE Roaming Architecture (Reply to 'LS related to Mobile VoIP IMS Roaming' / S3i150073)","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. Action: GSMA NG would like to request SA WG2 to review the items listed above, with the exception of lawful interception, and provide an analysis of the efforts that are expected to be needed to fulfil such requirements especially in terms of expected timeframe. GSMA NG would also like to learn if there are other architecture impacts that are not covered in this liaison statement.","8","4.2","LS (S2-150704) on VoLTE Roaming and Replies",10220,"Postponed","2015-04-07T07:27:34.217","2015-04-07T07:47:33.283","","S2-151440","","","","","","","","",null,null,null,"RAG 14 Doc 003"]
["S2-151016","Authorisation update: Additional info in context of announcing UE","Samsung","Youngkyo Baek",46395,"pCR","","","This contribution discusses part of the additional complexity introduced by the authorisation update procedure, especially concerning additional information to be stored in the context of the announcing UE.","34","6.10","Extended Proximity-based Services TR Phase (eProSe-Ext-SA2TR)",12600,"Approved","2015-04-07T07:31:28.093","2015-04-07T08:43:59.260","","","Rel-13","23.713","","eProSe-Ext-SA2TR","","","","","","","","",""]
["S2-151017","Correction to Monitor request procedure with application controlled extension","Samsung","Youngkyo Baek",46395,"pCR","","","This contribution corrects an error in the monitor request procedure agreed at SA WG2#107.","34","6.10","Extended Proximity-based Services TR Phase (eProSe-Ext-SA2TR)",12610,"Revised","2015-04-07T07:33:08.793","2015-04-07T08:43:59.307","","S2-151330","Rel-13","23.713","","eProSe-Ext-SA2TR","","","","","","","","",""]
["S2-151018","Destination address for one-to-one communication","Samsung","Youngkyo Baek",46395,"pCR","","","In this contribution we look in more detail at the destination L2 address to be used for one-to-one communication in Rel13 eProSe-Ext.","34","6.10","Extended Proximity-based Services TR Phase (eProSe-Ext-SA2TR)",12620,"Available","2015-04-07T07:34:30.630","2015-04-07T08:43:59.387","","","","23.713","","eProSe-Ext-SA2TR","","","","","","","","",""]
["S2-151019","Inform monitoring UE of PLMNs to monitor","Samsung","Youngkyo Baek",46395,"pCR","","","This contribution introduces an enhancement for ProSe direct discovery mechanism, which the ProSe Function gives the monitoring UE a list of PLMN information to monitor.","34","6.10","Extended Proximity-based Services TR Phase (eProSe-Ext-SA2TR)",12630,"Noted","2015-04-07T07:35:40.190","2015-04-07T08:43:59.463","","","","23.713","","eProSe-Ext-SA2TR","","","","","","","","",""]
["S2-151020","Update of MBMS design requirements for Public Safety","Motorola Solutions","Val Oprescu",14981,"pCR","","","Update specs to remove functional limitations (e.g. MBR > GBR) that may affect public safety","38","6.14","MBMS Enhancements (MBMS_enh)",13230,"Revised","2015-04-07T07:36:21.217","2015-04-07T07:51:42.917","","S2-151635","Rel-13","23.741","","MBMS_enh","","","","","","","","",""]
["S2-151021","Use of Group Info/Connectivity Info in UE2NW Relay discovery","Samsung","Youngkyo Baek",46395,"pCR","","","This contribution proposes to solve an unclarity w.r.t. the usage of 'Group Info' and 'Connectivity info' in UE2NW relay discovery.","34","6.10","Extended Proximity-based Services TR Phase (eProSe-Ext-SA2TR)",12640,"Revised","2015-04-07T07:37:05.087","2015-04-07T08:43:59.557","","S2-151313","Rel-13","23.713","","eProSe-Ext-SA2TR","","","","","","","","",""]
["S2-151022","Proposal for evaluation categorization for Scenario A of FS_HLCom","Qualcomm Incorporated","Miguel Griot",43100,"pCR","","","Proposes a categorization of FS_HLCom solutions to Scenario A for evaluation and conclusions.","36","6.12","Optimizations to Support High Latency Communications (FS_HLCom)",12900,"Available","2015-04-07T07:40:56.060","2015-04-07T07:42:46.103","","","Rel-13","23.709","","FS_HLcom","","","","","","","","",""]
["S2-151023","Clarification of ProSe Layer 2 Group ID provisioning","Samsung","Youngkyo Baek",46395,"CR","","","Summary of change: the ProSe Layer 2 Group ID is clarified it can be a configurable parameter.","15","5.1","3GPP Packet Access Maintenance",10760,"Revised","2015-04-07T07:43:41.483","2015-04-07T08:43:59.590","","S2-151327","Rel-12","23.303","12.4.0","TEI12, ProSe","0160","","F",null,"","","","",""]
["S2-151024","Correction for consistency description","Samsung","Youngkyo Baek",46395,"pCR","","","the contribution is proposed to align description for consistency and clean up the ambiguity.","40","6.16","Feasibility study on IOPS (FS_IOPS_St2)",13560,"Revised","2015-04-07T07:45:55.673","2015-04-07T08:43:59.637","","S2-151334","Rel-13","23.797","","FS_IOPS_St2","","","","","","","","",""]
["S2-151025","Mobility management considering IOPS operation","Samsung","Youngkyo Baek",46395,"pCR","","","the contribution is proposed to clarify the UE mobility management considering IOPS operation.","40","6.16","Feasibility study on IOPS (FS_IOPS_St2)",13570,"Merged","2015-04-07T07:47:02.677","2015-04-07T08:43:59.667","","","Rel-13","23.797","","FS_IOPS_St2","","","","","","","","",""]
["S2-151026","way forward on some unsolved FFS issues","Samsung","Youngkyo Baek",46395,"pCR","","","This contribution is to solve some remaining FFS issues.","40","6.16","Feasibility study on IOPS (FS_IOPS_St2)",13580,"Revised","2015-04-07T07:49:35.433","2015-04-07T08:43:59.697","","S2-151317","Rel-13","23.797","","FS_IOPS_St2","","","","","","","","",""]
["S2-151027","ProSe Discovery UE ID Renewal","Huawei, HiSilicon","Runze Zhou",60945,"pCR","","","WITHDRAWN: ProSe Discovery UE ID Renewal","55","99","Reserved and Withdrawn documents",13890,"Withdrawn","2015-04-07T07:51:07.863",null,"","","Rel-13","23.713","","eProSe-Ext-SA2TR","","","","","","","","",""]
["S2-151028","Coarse proximity estimation","Deutsche Telekom","Michele Zarri",20505,"pCR","","","This contribution proposes to specify a method for the monitoring UE to obtain a coarse estimation of the proximity to the announcing UE. The announcing UE assists the monitoring UE by indicating the transmit power used.","34","6.10","Extended Proximity-based Services TR Phase (eProSe-Ext-SA2TR)",12650,"Revised","2015-04-07T08:02:47.710","2015-04-07T11:58:25.200","","S2-151345","Rel-13","23.713","","eProSe-Ext-SA2TR","","","","","","","","",""]
["S2-151029","Way forward on ProSe communications Priority","Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Intel","Alessio Casati",13542,"pCR","","","This contribution discusses the topic of how to handle priority of ProSe-related communications transmissions","34","6.10","Extended Proximity-based Services TR Phase (eProSe-Ext-SA2TR)",12660,"Available","2015-04-07T08:03:44.260","2015-04-07T09:33:35.773","","","Rel-13","23.713","","eProSe-Ext-SA2TR","","","","","","","","",""]
["S2-151030","Way forward on UE to UE relays","Alcatel-Lucent, Alcatel-Lucent Shanghai Bell","Alessio Casati",13542,"pCR","","","This contribution aims at resolving the outstanding issues on the topic of ProSe UE to UE relays and concluding on this topic for rel-13","34","6.10","Extended Proximity-based Services TR Phase (eProSe-Ext-SA2TR)",12670,"Noted","2015-04-07T08:13:20.057","2015-04-07T09:33:35.743","","","Rel-13","23.713","","eProSe-Ext-SA2TR","","","","","","","","",""]
["S2-151031","Closing Editor’s notes in Solution 8","Intel","Saso Stojanovski",24932,"pCR","","","Proposes a resolution to the Editor's notes in Solution 8","36","6.12","Optimizations to Support High Latency Communications (FS_HLCom)",12910,"Available","2015-04-07T08:16:08.177","2015-04-07T14:02:37.203","","","Rel-13","23.709","","","","","","","","","","",""]
["S2-151032","Resolve FFS for UE-to-Network Relay Discovery","HTC","Ellen C. Liao",54895,"pCR","","","This paper proposes to clarify the required parameters used for UE to Network relay discovery.","34","6.10","Extended Proximity-based Services TR Phase (eProSe-Ext-SA2TR)",12680,"Revised","2015-04-07T08:18:02.823","2015-04-07T10:02:54.833","","S2-151337","Rel-13","23.713","","eProSe-Ext-SA2TR","","","","","","","","",""]
["S2-151033","Resolve FFS for IP Multicast on Relay","HTC","Ellen C. Liao",54895,"pCR","","","This contribution proposes to resolve the FFS issue for associating the IP multicast address with the ProSe Layer 2 Group ID.","34","6.10","Extended Proximity-based Services TR Phase (eProSe-Ext-SA2TR)",12690,"Merged","2015-04-07T08:20:44.987","2015-04-07T10:02:54.867","","","Rel-13","23.713","","eProSe-Ext-SA2TR","","","","","","","","",""]
["S2-151034","Discovery and association to Local EPC","Alcatel-Lucent, Alcatel-Lucent Shanghai Bell","Alessio Casati",13542,"pCR","","","this contribution addresses the open issue of how to make sure Isolated E-UTRAN find a suitable Local EPC and can associate to it.","40","6.16","Feasibility study on IOPS (FS_IOPS_St2)",13590,"Noted","2015-04-07T08:21:07.293","2015-04-07T09:33:35.820","","","Rel-13","23.797","","FS_IOPS_St2","","","","","","","","",""]
["S2-151035","FS_HLCom conclusion","Intel","Saso Stojanovski",24932,"other","","","Proposes a conclusion to the FS_HLCom study","36","6.12","Optimizations to Support High Latency Communications (FS_HLCom)",12920,"Noted","2015-04-07T08:21:39.617","2015-04-07T14:02:37.237","","","Rel-13","","","","","","","","","","","",""]
["S2-151036","Solution to provide ECGI and SAI over GC1 interface","Nokia Networks","Rainer Liebhart",13470,"pCR","","","In current discussion assumption is that the UE can notify the GCS AS via GC1 interface about its serving cell (in form of ECGI). This contribution proposes that UE does not only send ECGI but also SAI via GC1. Thus, it provides a solution to address the problem how the GCS AS can be made aware of the ECGI to SAI mapping, avoiding manual configuration of this mapping. GCS AS can then send ECGIs and SAIs to BM-SC. This helps to specify an end to end to solution for Key Issue 1 - 'Establishment of MBMS bearers using a list of cell identities or other area information' in TR 23.741'.","38","6.14","MBMS Enhancements (MBMS_enh)",13240,"Available","2015-04-07T08:22:29.193","2015-04-07T09:23:54.110","","","Rel-13","23.741","","MBMS_enh","","","","","","","","",""]
["S2-151037","Proposals for Open ProSe Direct Discovery Enhancement","HTC","Ellen C. Liao",54895,"pCR","","","This contribution proposes to resolve the open issues that were not resolved in Rel-12 time frame.","34","6.10","Extended Proximity-based Services TR Phase (eProSe-Ext-SA2TR)",12700,"Available","2015-04-07T08:23:06.463","2015-04-07T10:02:54.897","","","Rel-13","23.713","","eProSe-Ext-SA2TR","","","","","","","","",""]
["S2-151038","FS_HLCom conclusion (pCR)","Intel","Saso Stojanovski",24932,"pCR","","","Proposes a conclusion to the FS_HLCom study (pCR).","36","6.12","Optimizations to Support High Latency Communications (FS_HLCom)",12930,"Available","2015-04-07T08:24:54.197","2015-04-07T14:02:37.250","","","Rel-13","23.709","","FS_HLcom","","","","","","","","",""]
["S2-151039","Support of NB_IFOM for S2a SCM","Qualcomm Incorporated","Haris Zisimopoulos",41602,"pCR","","","A proposal for NB_IFOM for S2a SCM is provided.","28","6.4","IP Flow Mobility support for S2a and S2b interfaces (NBIFOM)",11600,"Revised","2015-04-07T08:28:24.860","2015-04-07T08:34:41.163","","S2-151226","Rel-13","23.861","","NBIFOM","","","","","","","","",""]
["S2-151040","General Key Issues: Proposed Assumptions for phase 1","Qualcomm Incorporated, Alcatel Lucent, Alcatel Lucent Shanghai Bell","Haris Zisimopoulos",41602,"pCR","","","This contribution addresses some key issues and concludes that no specific work should be done in Rel. 13 in SEW phase 1 to address these areas.","41","6.17","Feasibility study on the Support of Emergency services over WLAN (FS_SEW)",13710,"Revised","2015-04-07T08:28:24.877","2015-04-07T08:34:41.197","","S2-151247","Rel-13","23.771","","FS_SEW","","","","","","","","",""]
["S2-151041","Key Issues on Connectivity Establishment","Qualcomm Incorporated","Haris Zisimopoulos",41602,"pCR","","","The contribution introduces an issue for connectivity establishment related to the ePDG selection.","41","6.17","Feasibility study on the Support of Emergency services over WLAN (FS_SEW)",13720,"Revised","2015-04-07T08:28:24.877","2015-04-07T08:34:41.227","","S2-151248","Rel-13","23.771","","FS_SEW","","","","","","","","",""]
["S2-151042","Solution for Key Issues on Location Information","Qualcomm Incorporated","Haris Zisimopoulos",41602,"pCR","","","The contribution introduces three solutions for the key issue on location information.","41","6.17","Feasibility study on the Support of Emergency services over WLAN (FS_SEW)",13730,"Noted","2015-04-07T08:28:24.893","2015-04-07T08:34:41.103","","","Rel-13","23.771","","FS_SEW","","","","","","","","",""]
["S2-151043","Key Issues on Location Information","Qualcomm Incorporated","Haris Zisimopoulos",41602,"pCR","","","The contribution introduces a key issue on location information.","41","6.17","Feasibility study on the Support of Emergency services over WLAN (FS_SEW)",13740,"Merged","2015-04-07T08:28:24.893","2015-04-07T08:34:41.117","","","Rel-13","23.771","","FS_SEW","","","","","","","","",""]
["S2-151044","SC-PTM Architecture","Qualcomm Incorporated","Haris Zisimopoulos",41602,"other","","","This paper analyses the architecture options of SC-PTM based group communication system.","38","6.14","MBMS Enhancements (MBMS_enh)",13250,"Noted","2015-04-07T08:28:24.907","2015-04-07T10:33:56.700","","","Rel-13","","","","","","","","","","","",""]
["S2-151045","Cover Sheet for TR 23.708 for Approval at TSG SA","AESE Rapporteurs (Intel)","Puneet Jain",36283,"TS or TR","","","Proposes a cover page for submitting TR 23.708 v1.2.0 to SA#68 plenary for Approval","29","6.5","Architecture Enhancements for Service Exposure (AESE)",11780,"Noted","2015-04-07T08:28:28.840","2015-04-07T14:07:48.470","","","Rel-13","23.708","1.2.0","","","","","","","","","",""]
["S2-151046","On MME control on number of DL packets to be stored in SGW","Alcatel-Lucent, Alcatel-Lucent Shanghai Bell","Alessio Casati",13542,"pCR","","","this paper addresses an open issue on whether the MME should provide an indication to the SGW on the depth of the buffer used for HLCOM DL packet storage, in addition to the duration of the expected buffering.","36","6.12","Optimizations to Support High Latency Communications (FS_HLCom)",12940,"Merged","2015-04-07T08:28:34.237","2015-04-07T12:11:41.067","S2-150352","","Rel-13","23.709","","FS_HLcom","","","","","","","","",""]
["S2-151047","MBMS bearer establishment with ECGI list","Nokia Networks, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell","Rainer Liebhart",13470,"CR","","","Summary of change: Introduce the capability to include a list of ECGIs in the MBMS session start and update procedures.","38","6.14","MBMS Enhancements (MBMS_enh)",15450,"Available","2015-04-07T08:28:44.393","2015-04-07T09:23:54.157","","","Rel-13","23.246","13.0.0","MBMS_enh","0393","","B",null,"","","","",""]
["S2-151048","Changes to content of Connectivity Info for UE-to-Network Relay Discovery","ITRI","Stephan Gleixner",44214,"pCR","","","This contribution proposes to add the PDN type to the content of the Connectivity Info used for ProSe UE-to-Network Relay Discovery in clause 6.1.2.","34","6.10","Extended Proximity-based Services TR Phase (eProSe-Ext-SA2TR)",12710,"Noted","2015-04-07T08:30:56.557","2015-04-07T10:39:10.417","S2-150314","","Rel-13","23.713","","eProSe-Ext-SA2TR","","","","","","","","",""]
["S2-151049","MBMS bearer establishment with ECGI list","Nokia Networks, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell","Rainer Liebhart",13470,"CR","","","Summary of change: Clauses 5.1.2.3.2 and 5.1.2.4 are modified to allow the GCS AS to include either a list of ECGIs or MBMS service areas in the MBMS activate/modify bearer procedures. The BM-SC is required to map ECGIs received in messages over the MB2-C interface to corresponding MBMS service areas based on configuration. BM-SC sends SAIs and ECGIs in the session start and update procedures.","38","6.14","MBMS Enhancements (MBMS_enh)",15460,"Available","2015-04-07T08:33:16.893","2015-04-07T09:23:54.203","","","Rel-13","23.468","13.0.0","MBMS_enh","0057","","B",null,"","","","",""]
["S2-151050","Enhanced proximity estimation with logged location information","NEC","Genadi Velev",40661,"pCR","","","A solution enhancement of proximity estimation is proposed to efficiently activate the proximity monitoring on EPC-level discovery.","34","6.10","Extended Proximity-based Services TR Phase (eProSe-Ext-SA2TR)",12720,"Noted","2015-04-07T08:35:45.747","2015-04-07T14:27:02.657","","","Rel-13","23.713","","eProSe-Ext-SA2TR","","","","","","","","",""]
["S2-151051","On ProSe UE ID and ProSe Layer-2 Group ID format (preventing future backwards compatibility issues)","Intel","Saso Stojanovski",24932,"other","","","Discusses options for the addressing format of ProSe UE ID and ProSe Layer-2 Group ID and proposes a Rel-12 clarification CR in order to prevent future backwards compatibility issues.","15","5.1","3GPP Packet Access Maintenance",10570,"Noted","2015-04-07T08:36:59.627","2015-04-07T14:02:36.923","","","Rel-12","","","","","","","","","","","",""]
["S2-151052","Solution to address interaction between eDRX and PSM","Nokia Networks","Rainer Liebhart",13470,"pCR","","","This contribution provides a solution to address the interaction between eDRX and PSM. Some devices require extensive power savings and will require e.g. only two MT transactions per day. For such devices, PSM mode may be suitable. At the same time, if the network and/or device determine that the number of MT transactions per day cross a certain threshold, the device should be able to deactivate PSM so that the device is more easily reachable (i.e. probability to reach the device is increased while still power saving is possible) for MT transactions. This addresses the issue #7 listed in TR 23.770.","39","6.15","Feasibility study on Extended DRX cycle for Power Consumption Optimization (FS_eDRX)",13460,"Noted","2015-04-07T08:37:13.170","2015-04-07T09:22:32.973","","","Rel-13","23.770","","FS_eDRX","","","","","","","","",""]
["S2-151053","Solution for FMSS: Signalling procedures for supporting traffic steering policy solicitation over St interface","KDDI, ZTE","Takeshi Usui",59388,"pCR","","","This contribution proposes procedures for for the (S)Gi-LAN to solicit traffic steering policy over St interface","37","6.13","Flexible Mobile Service Steering (FMSS)",13090,"Merged","2015-04-07T08:37:15.260","2015-04-07T08:58:51.860","","","Rel-13","23.718","","FMSS","","","","","","","","",""]
["S2-151054","DL data transmission from an AS to an out-of-network coverage PS terminal via UE-Network Relay","ITRI","Stephan Gleixner",44214,"pCR","","","This contribution adds the capability to enable an application server that has downlink data for an out-of-coverage PS terminal that has not yet established connection with the network via a UE-Network Relay, to trigger that PS terminal to establish a connection for One-to-One communication with a UE-Network Relay.","34","6.10","Extended Proximity-based Services TR Phase (eProSe-Ext-SA2TR)",12730,"Available","2015-04-07T08:39:19.073","2015-04-07T11:20:31.757","","","Rel-13","23.713","","eProSe-Ext-SA2TR","","","","","","","","",""]
["S2-151055","Component of Traffic Steering Policy over St interface","KDDI, ZTE","Takeshi Usui",59388,"pCR","","","This document proposes the definitions of component St based solution for uplink and downlink traffic. TS 23.718 defines the component of Traffic Steering Policy for Gx and Sd interface. St interface should have the same component with Gx and Sd interface.","37","6.13","Flexible Mobile Service Steering (FMSS)",13100,"Noted","2015-04-07T08:40:02.613","2015-04-07T08:58:15.437","","","Rel-13","23.718","","FMSS","","","","","","","","",""]
["S2-151056","Clarification on ProSe UE ID and ProSe Layer-2 Group ID","Intel","Saso Stojanovski",24932,"CR","","","Summary of change: It is clarified that the Least Significant Bit (LSB) in the ProSe UE ID is always set to '0', whereas the LSB in the ProSe Layer-2 Group ID is always set to '1'.","15","5.1","3GPP Packet Access Maintenance",10740,"Available","2015-04-07T08:40:08.430","2015-04-07T14:02:36.970","","","Rel-12","23.303","12.4.0","ProSe","0161","","F",null,"","","","",""]
["S2-151057","Remove FFS in Clause 7.4.4","ITRI","Stephan Gleixner",44214,"pCR","","","Remove FFS in Clause 7.4.4.","34","6.10","Extended Proximity-based Services TR Phase (eProSe-Ext-SA2TR)",12740,"Available","2015-04-07T08:41:02.500","2015-04-07T10:39:10.480","","","Rel-13","23.713","","eProSe-Ext-SA2TR","","","","","","","","",""]
["S2-151058","Stateful ProSe UE-to-UE Relay","Intel","Saso Stojanovski",24932,"pCR","","","Proposes input to clause 7.3. (Solution for ProSe UE-UE Relays (stateful relay selection)) that is currently almost empty","34","6.10","Extended Proximity-based Services TR Phase (eProSe-Ext-SA2TR)",12750,"Noted","2015-04-07T08:43:21.370","2015-04-07T14:02:37.017","","S2-151759","Rel-13","23.713","","eProSe-Ext-SA2TR","","","","","","","","",""]
["S2-151059","Layer-2 ID Uniqueness for One-to-One Direct Communication","ITRI","Stephan Gleixner",44214,"pCR","","","In the absence of global uniqueness of Layer-2 ID used for one-to-one ProSe direct communication, UE needs to detect and avoid any potential conflict of Layer-2 ID with UEs in its vicinity.","34","6.10","Extended Proximity-based Services TR Phase (eProSe-Ext-SA2TR)",12760,"Available","2015-04-07T08:44:40.290","2015-04-07T10:39:10.447","S2-150315","","Rel-13","23.713","","eProSe-Ext-SA2TR","","","","","","","","",""]
["S2-151060","Way forward on ProSe service continuity","Intel, Alcatel-Lucent, BlackBerry UK Ltd","Saso Stojanovski",24932,"pCR","","","Proposes a way forward for service continuity when UE moves between direct network connection and a network connection via a ProSe UE-to-NW relay","34","6.10","Extended Proximity-based Services TR Phase (eProSe-Ext-SA2TR)",12770,"Noted","2015-04-07T08:47:00.563","2015-04-07T14:02:37.047","","","Rel-13","23.713","","eProSe-Ext-SA2TR","","","","","","","","",""]
["S2-151061","Fixes to Public Safety Discovery procedures","Intel","Saso Stojanovski",24932,"pCR","","","Proposes fixes to the Public Safety Discovery procedures","34","6.10","Extended Proximity-based Services TR Phase (eProSe-Ext-SA2TR)",12780,"Revised","2015-04-07T08:50:01.820","2015-04-07T14:02:37.080","","S2-151312","Rel-13","23.713","","eProSe-Ext-SA2TR","","","","","","","","",""]
["S2-151062","Permission of location reporting","NEC","Genadi Velev",40661,"other","","","In this contribution, additional consideration about the permission of location reporting from the contracted user (i.e. user consent) is proposed.","15","5.1","3GPP Packet Access Maintenance",10590,"Noted","2015-04-07T08:54:01.547","2015-04-07T14:27:02.687","","","Rel-12","","","","","","","","","","","",""]
["S2-151063","User consent handling during UE Registration","NEC","Genadi Velev",40661,"CR","","","Summary of change: If the ProSe Function sends ProSe Subscriber Information Request to HSS for UE Registration, the HSS responds ProSe Subscriber Information Answer which contains User-Consent, if available.","15","5.1","3GPP Packet Access Maintenance",10800,"Available","2015-04-07T08:56:53.237","2015-04-07T14:27:02.733","","","Rel-12","23.303","12.4.0","ProSe","0162","","F",null,"","","","",""]
["S2-151064","Solution for GUTI Sync issue for DECOR","NTT DOCOMO INC.","Irfan Ali",50390,"other","","","Provides an overview of the solution to the problem of GUTI sync issue identified in SA WG2-107.","27","6.3","Dedicated Core Networks (DECOR)",11350,"Available","2015-04-07T08:59:42.343","2015-04-07T13:25:23.413","","","Rel-13","","","","","","","","","","","",""]
["S2-151065","UE Usage Type clarifications","NEC","Genadi Velev",40661,"CR","","","Summary of change: It is proposed that the HPLMN can decide whether to send or not the 'UE Usage Type' parameter if the value is 'operator specific'.","27","6.3","Dedicated Core Networks (DECOR)",11890,"Revised","2015-04-07T09:03:27.483","2015-04-07T14:27:02.547","","S2-151719","Rel-13","23.401","13.2.0","DECOR","2855","","F",null,"","","","",""]
["S2-151066","Solution principles for S2b","Intel","Saso Stojanovski",24932,"pCR","","","Proposes solution principles for S2b SEW (including Location information types, ePDG selection, IKEv2 changes)","41","6.17","Feasibility study on the Support of Emergency services over WLAN (FS_SEW)",13750,"Noted","2015-04-07T09:06:23.653","2015-04-07T14:02:37.110","","","Rel-13","23.771","","FS_SEW","","","","","","","","",""]
["S2-151067","UE Usage Type clarifications","NEC","Genadi Velev",40661,"CR","","","Summary of change: It is proposed that the HPLMN can decide whether to send or not the 'UE Usage Type' parameter if the value is 'operator specific'.","55","99","Reserved and Withdrawn documents",17320,"Withdrawn","2015-04-07T09:09:31.553",null,"","","Rel-13","23.060","13.2.0","DECOR","1963","","F",null,"","","","",""]
["S2-151068","Group based NAS Level congestion control for multiple APNs","NEC","Genadi Velev",40661,"CR","","","Summary of change: It is proposed that the MME may deactivate existing bearer contexts from other APNs (different from the one to which the UE sent NAS ESM request) with a SM back-off timer having the same value as in the ESM reject message.","31","6.7","Group based Enhancements (GROUPE)",13410,"Noted","2015-04-07T09:19:53.527","2015-04-07T14:27:02.577","","","Rel-13","23.401","13.2.0","GROUPE","2856","","F",null,"","","","",""]
["S2-151069","Group based NAS Level congestion control for multiple APNs","NEC","Genadi Velev",40661,"CR","","","Summary of change: It is proposed that the SGSN may deactivate existing bearer contexts from other APNs (different from the one to which the MS sent NAS SM request) with a SM back-off timer having the same value as in the SM reject message.","31","6.7","Group based Enhancements (GROUPE)",13420,"Noted","2015-04-07T09:23:28.103","2015-04-07T14:27:02.610","","","Rel-13","23.060","13.2.0","GROUPE","1964","","F",null,"","","","",""]
["S2-151070","Conclusions on ProSe UE-to-UE Relay","Intel","Saso Stojanovski",24932,"pCR","","","Proposes conclusions on UE-to-UE Relay (both stateful and stateless)","34","6.10","Extended Proximity-based Services TR Phase (eProSe-Ext-SA2TR)",12790,"Available","2015-04-07T09:31:09.007","2015-04-07T14:02:37.143","","","Rel-13","23.713","","eProSe-Ext-SA2TR","","","","","","","","",""]
["S2-151071","Conclusion for key issue 6","China Mobile","Aihua Li",58162,"pCR","","","This contribution provides conclusions text for key issue 6 - Informing the 3rd party about potential network issues.","29","6.5","Architecture Enhancements for Service Exposure (AESE)",11790,"Merged","2015-04-07T09:49:26.737","2015-04-08T05:10:36.417","","","","23.708","","AESE","","","","","","","","",""]
["S2-151072","Procedures of TCF Solution","China Mobile, CATR","Tao Sun",54129,"pCR","","","Describe the procedures and call flows for the TCF solution","37","6.13","Flexible Mobile Service Steering (FMSS)",13110,"Revised","2015-04-07T09:53:23.077","2015-04-07T16:08:25.703","","S2-151161","Rel-13","23.718","","FMSS","","","","","","","","",""]
["S2-151073","Resolution of Editor's note in clause 7.2.2.4","Intel","Saso Stojanovski",24932,"pCR","","","Proposes a resolution of the Editor's note in clause 7.2.2.4.","34","6.10","Extended Proximity-based Services TR Phase (eProSe-Ext-SA2TR)",12800,"Merged","2015-04-07T09:54:02.297","2015-04-07T14:02:37.173","","S2-151755","Rel-13","23.713","","eProSe-Ext-SA2TR","","","","","","","","",""]
["S2-151074","Paging priority and ARP Priority level: extension of CR2812r2 to CR2840r2","Rapporteur (Vodafone)","Chris Pudney",1122,"CR","","","Summary of change: Clarify that the ARP value used for paging priority setting is the ARP priority level.","45","6.20.1","TEI13 Category B/C for 3GPP Packet Access",16580,"Revised","2015-04-07T10:32:36.047","2015-04-07T10:40:55.997","","S2-151137","Rel-13","23.401","13.2.0","SAES, TEI12","2857","","F",null,"","","","",""]
["S2-151075","A clarification for Gx or Sd based solution","China Unicom, China Telecom, Intel","Maurice Pope",648,"pCR","","","This paper adds 'NOTE's to further clarify Traffic steering control and enforcement over Sd can be applied without any other PCC functionalities, if not needed.","37","6.13","Flexible Mobile Service Steering (FMSS)",13120,"Noted","2015-04-07T10:45:19.857","2015-04-07T10:58:10.390","","S2-151149","Rel-13","23.718","","FMSS","","","","","","","","",""]
["S2-151076","Discussion on the support of QoS in trusted and untrusted WLAN","Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Broadcom Corporation","Nicolas Drevon",16459,"other","","","This paper discusses alternatives for the support of QoS in Trusted and Untrusted WLAN for VoIMS in general and for emergency calls over WLAN in particular.","41","6.17","Feasibility study on the Support of Emergency services over WLAN (FS_SEW)",13760,"Available","2015-04-07T11:09:44.590","2015-04-07T11:36:56.510","","","Rel-13","","","","","","","","","","","",""]
["S2-151077","Draft Response to Reply LS on Security Framework for Cellular IoT","VODAFONE Group Plc","Chris Pudney",1122,"LS out","","","Draft response to SA WG3 LS in S2-150738 = S3-151198","7","4.1","Common issues and Incoming LSs",0,"Revised","2015-04-07T11:37:57.427","2015-04-07T12:39:54.027","","S2-151311","Rel-13","","","","","","","","S2-150738","SA WG3","GERAN WG2, TSG GERAN, SA WG1, TSG SA"]
["S2-151078","Cleanup for Solution: Use of MBMS for Group Message Delivery","Samsung","Sung Hwan Won",46717,"pCR","","","It is proposed to modify solution description of 'Use of MBMS for Group Message Delivery.'","31","6.7","Group based Enhancements (GROUPE)",12090,"Revised","2015-04-07T11:46:16.063","2015-04-07T16:24:54.997","","S2-151174","Rel-13","23.769","","GROUPE","","","","","","","","",""]
["S2-151079","NNSF and initial UE message population","Samsung","Sung Hwan Won",46717,"CR","","","Summary of change: The reroute NAS message request message includes additional parameters for NNSF and initial UE message population. In addition, several editorial modifications are made.","27","6.3","Dedicated Core Networks (DECOR)",11740,"Merged","2015-04-07T11:47:56.230","2015-04-07T16:24:54.950","","","Rel-13","23.401","13.2.0","DECOR","2858","","C",null,"","","","",""]
["S2-151080","Correction in the HSS-initiated CN reselection","Samsung","Sung Hwan Won",46717,"other","","","It is suggested that the S1 release cause should not trigger load balancing TAU in case the HSS triggers CN reselection.","27","6.3","Dedicated Core Networks (DECOR)",11380,"Available","2015-04-07T11:49:56.973","2015-04-07T16:24:54.933","","","Rel-13","","","","","","","","","","","",""]
["S2-151081","Correction in the HSS-initiated CN reselection","Samsung","Sung Hwan Won",46717,"CR","","","Summary of change: If the HSS triggers CN reselection due to subscription change and the CN reselection does not require P-GW relocation, the MME performs the S1 release with a cause different than 'load balancing TAU required,' i.e. new cause value 'Intra-RAT Redirection.'","27","6.3","Dedicated Core Networks (DECOR)",11900,"Available","2015-04-07T11:51:14.537","2015-04-07T16:24:54.903","","","Rel-13","23.401","13.2.0","DECOR","2859","","C",null,"","","","",""]
["S2-151082","Stage 2 cleanup regarding the WIC registration with a security token","Samsung","Sung Hwan Won",46717,"CR","","","Summary of change: 1. In addition to IMS identities, e.g. the validity period is derived from the security token. 2. Web authentication can be avoided in case of registration refreshment.","18","5.4","IMS-Related Maintenance",11370,"Revised","2015-04-07T11:54:12.047","2015-04-07T16:24:54.857","","S2-151108","Rel-12","23.228","12.8.0","TEI12, IMS_WebRTC","1128","","F",null,"","","","",""]
["S2-151083","MBMS Congestion Mitigation for Rel-13","Motorola Solutions","Val Oprescu",14981,"pCR","","","Proposes the addition of the Key Issue to study for MBMS congestion management in Rel-13","38","6.14","MBMS Enhancements (MBMS_enh)",13280,"Revised","2015-04-07T11:54:14.230","2015-04-07T15:42:36.807","","S2-151640","Rel-13","23.741","","MBMS_enh","","","","","","","","",""]
["S2-151084","Stage 2 cleanup regarding the WIC registration with a security token","Samsung","Sung Hwan Won",46717,"CR","","","Rel-13 mirror CR: Summary of change: 1. In addition to IMS identities, e.g. the validity period is derived from the security token. 2. Web authentication can be avoided in case of registration refreshment.","18","5.4","IMS-Related Maintenance",11400,"Revised","2015-04-07T11:55:28.063","2015-04-07T16:24:54.823","","S2-151109","Rel-13","23.228","13.2.0","TEI12, IMS_WebRTC","1129","","A",null,"","","","",""]
["S2-151085","MBMS broadcast area and cell identities","General Dynamics UK Ltd.","Philip Young",27298,"pCR","","","This contribution proposes information flows to specify an MBMS broadcast area as a list of ECGIs to be included in TR 23.741","38","6.14","MBMS Enhancements (MBMS_enh)",13290,"Revised","2015-04-07T12:16:47.623","2015-04-07T18:29:32.220","","S2-151098","Rel-13","23.741","","MBMS_enh","","","","","","","","",""]
["S2-151086","[DRAFT] Response LS on SC-PTM transmission","General Dynamics UK Limited","Philip Young",27298,"LS out","","","Draft LS Response to RAN WG2 on SC-PTM","38","6.14","MBMS Enhancements (MBMS_enh)",0,"Merged","2015-04-07T12:20:01.797","2015-04-07T18:29:32.187","","","Rel-13","","","","","","","","S2-150726","RAN WG2, RAN WG3"]
["S2-151087","Updating solutions 2 and 6","Huawei, HiSilicon","Frank Mademann",6821,"pCR","","","This paper updates solution 2 to capture the aspects from solution 6.","36","6.12","Optimizations to Support High Latency Communications (FS_HLCom)",12950,"Revised","2015-04-07T12:54:42.887","2015-04-07T13:17:32.780","","S2-151175","Rel-13","23.709","","HLcom","","","","","","","","",""]
["S2-151088","MS Info Change Reporting Action at change of Serving Node (MME <--> SGSN): Update of call Flows","Alcatel-Lucent, Alcatel-Lucent Shanghai Bell","Laurent Thiebaut",11066,"CR","","","Summary of change: Align the call flows (of mobility between MME and SGSN) with text in § 5.9.2.1 which mostly consist in 1) if the target SGSN/MME supports location information change reporting, the target SGSN/MME shall include the User Location Information in the Modify Bearer Request, regardless of whether ULI change reporting had been requested in the previous RAT by the PGW 2) If User Location Information change reporting is required and supported in the target RAT, the PGW shall request MS Info Change Reporting Action in the Modify Bearer Response","16","5.2","QoS and PCC Maintenance",11060,"Revised","2015-04-07T13:00:45.337","2015-04-07T15:56:33.797","","S2-151208","Rel-12","23.401","12.8.0","CNO_ULI","2860","","F",null,"","","","",""]
["S2-151089","MS Info Change Reporting Action at change of Serving Node (MME <--> SGSN): Update of call Flows","Alcatel-Lucent, Alcatel-Lucent Shanghai Bell","Laurent Thiebaut",11066,"CR","","","Rel-13 mirror CR: Summary of change: Align the call flows (of mobility between MME and SGSN) with text in § 5.9.2.1 which mostly consist in 1) if the target SGSN/MME supports location information change reporting, the target SGSN/MME shall include the User Location Information in the Modify Bearer Request, regardless of whether ULI change reporting had been requested in the previous RAT by the PGW 2) If User Location Information change reporting is required and supported in the target RAT, the PGW shall request MS Info Change Reporting Action in the Modify Bearer Response","16","5.2","QoS and PCC Maintenance",11100,"Revised","2015-04-07T13:04:19.993","2015-04-07T15:56:33.843","","S2-151209","Rel-13","23.401","13.2.0","CNO_ULI","2861","","A",null,"","","","",""]
["S2-151090","Avoiding SRVCC in case of webRTC calls","Alcatel-Lucent, Alcatel-Lucent ShangHai Bell","Laurent Thiebaut",11066,"pCR","","","How to avoid SRVCC in case of WebRTC calls","33","6.9","Enhancements to WEBRTC interoperability (eWebRTCi)",12290,"Available","2015-04-07T14:06:52.280","2015-04-07T14:14:22.497","","","","23.706","","eWebRTCi","","","","","","","","",""]
["S2-151091","Draft Response to Reply LS on paging for MTC","VODAFONE Group Plc","Chris Pudney",1122,"LS out","","","Draft Response to Reply LS on paging for MTC (GP-150312/S2-150716; R1-150924/S2-150720 )","7","4.1","Common issues and Incoming LSs",0,"Revised","2015-04-07T14:25:06.233","2015-04-07T14:27:51.127","","S2-151354","Rel-13","","","","","","","","S2-150716","RAN WG1, RAN WG2, RAN WG3, GERAN WG2","TSG GERAN"]
["S2-151092","Key Issue proposal: Routing of Session Start/Stop/Update Request messages to valid nodes","Samsung","Sung Hwan Won",46717,"pCR","","","A new key issue and a solution for the key issue are proposed.","38","6.14","MBMS Enhancements (MBMS_enh)",13300,"Revised","2015-04-07T16:19:11.030","2015-04-07T16:24:54.807","","S2-151099","Rel-13","23.741","","MBMS_enh","","","","","","","","",""]
["S2-151093","[DRAFT] Reply LS on paging for MTC","Samsung","Sung Hwan Won",46717,"LS out","","","SA WG2 would like to ask an additional question related to Q2 in S2-150697: Is the coverage situation information of an MTC UE with a certain radio capability stable during the idle mode?","15","5.1","3GPP Packet Access Maintenance",0,"Available","2015-04-07T16:22:03.380","2015-04-07T16:24:54.777","","","Rel-13","","","","","","","","S2-150716","RAN WG1, RAN WG2, RAN WG3, TSG GERAN"]
["S2-151094","Additional SA WG2 #110ah Meeting Proposal","SA WG2 Chairman","Erik Guttman",18782,"other","","","This proposal would add a meeting to Q3 2015 to complete exceptions expected at TSG SA#68.","52","7.3","Planning future meetings",13830,"Revised","2015-04-08T07:44:18.337","2015-04-08T08:03:18.033","","S2-151310","","","","","","","","","","","","",""]
["S2-151095","LS from GSMA RiLTE: LS on ePDG selection when UE is roaming","GSMA RiLTE","Maurice Pope",648,"LS in","","","Action: Networks Group RILTE kindly requests CT WG1 and SA WG2 to 1) Clarify, whether it can be achieved with the current ePDG selection procedures and an appropriate configuration, that the UE connects to ePDG in the home network as the preferred option. 2) Enhance the specifications appropriately to allow a deployment scenario where the UE connects to ePDG in home network when roaming as the preferred option.","41","6.17","Feasibility study on the Support of Emergency services over WLAN (FS_SEW)",0,"Treated","2015-04-09T16:27:06.903","2015-04-09T16:28:03.017","","","","","","","","","","",null,null,null,"RILTE 45 Doc_112","S2-151395"]
["S2-151096","[DRAFT] LS on SC-PTM transmission feedback","SA WG2","Wanqiang Zhang",41153,"LS out","","","LS back to RAN WG2 and RAN WG3","38","6.14","MBMS Enhancements (MBMS_enh)",15320,"Revised","2015-04-20T16:09:10.190","2015-04-20T16:04:39.027","S2-150847","S2-151102","Rel-13","","","","","","","","S2-150726","RAN WG2, RAN WG3"]
["S2-151097","Solution A for Key Issue 1","Alcatel-Lucent, Nokia Networks","Mike Dolan",1692,"pCR","","","This contribution provides a solution to address the Key Issues for MBMS enhancements in Rel-13.","38","6.14","MBMS Enhancements (MBMS_enh)",15370,"Revised","2015-04-20T16:09:10.237","2015-04-20T16:04:39.043","S2-150946","S2-151104","Rel-13","23.741","","","","","","","","","","",""]
["S2-151098","MBMS broadcast area and cell identities","General Dynamics UK Ltd.","Philip Young",27298,"pCR","","","This contribution proposes information flows to specify an MBMS broadcast area as a list of ECGIs to be included in TR 23.741","38","6.14","MBMS Enhancements (MBMS_enh)",15280,"Revised","2015-04-20T16:09:10.283","2015-04-20T16:04:39.183","S2-151085","S2-151101","Rel-13","23.741","","MBMS_enh","","","","","","","","",""]
["S2-151099","Key Issue proposal: Routing of Session Start/Stop/Update Request messages to valid nodes","Samsung","Sung Hwan Won",46717,"pCR","","","A new key issue and a solution for the key issue are proposed.","38","6.14","MBMS Enhancements (MBMS_enh)",15420,"Revised","2015-04-20T16:09:10.313","2015-04-20T16:04:40.087","S2-151092","S2-151103","Rel-13","23.741","","MBMS_enh","","","","","","","","",""]
["S2-151100","[DRAFT] LS on Flow ID supplied by GCS AS","SA WG2","Mike Dolan",1692,"LS out","","","-","38","6.14","MBMS Enhancements (MBMS_enh)",15520,"Noted","2015-04-20T16:09:10.360","2015-04-20T16:04:40.963","","","Rel-12","","","","","","","","S2-150712","CT WG3"]
["S2-151101","MBMS broadcast area and cell identities","General Dynamics UK Ltd.","Philip Young",27298,"pCR","","","This contribution proposes information flows to specify an MBMS broadcast area as a list of ECGIs to be included in TR 23.741","38","6.14","MBMS Enhancements (MBMS_enh)",15290,"Approved","2015-04-20T16:09:10.377","2015-04-20T16:04:40.977","S2-151098","","Rel-13","23.741","","MBMS_enh","","","","","","","","",""]
["S2-151102","LS on SC-PTM transmission feedback","SA WG2","Wanqiang Zhang",41153,"LS out","","","LS back to RAN WG2 and RAN WG3","38","6.14","MBMS Enhancements (MBMS_enh)",15330,"Approved","2015-04-20T16:09:10.407","2015-04-20T16:04:41.867","S2-151096","","Rel-13","","","","","","","","S2-150726","RAN WG2, RAN WG3"]
["S2-151103","Key Issue proposal: Routing of Session Start/Stop/Update Request messages to valid nodes","Samsung","Sung Hwan Won",46717,"pCR","","","A new key issue and a solution for the key issue are proposed.","38","6.14","MBMS Enhancements (MBMS_enh)",15430,"Merged","2015-04-20T16:09:10.437","2015-04-20T16:04:41.883","S2-151099","","Rel-13","23.741","","MBMS_enh","","","","","","","","",""]
["S2-151104","Solution A for Key Issue 1","Alcatel-Lucent, Nokia Networks","Mike Dolan",1692,"pCR","","","This contribution provides a solution to address the Key Issues for MBMS enhancements in Rel-13.","38","6.14","MBMS Enhancements (MBMS_enh)",15380,"Approved","2015-04-20T16:09:10.470","2015-04-20T16:04:42.740","S2-151097","","Rel-13","23.741","","","","","","","","","","",""]
["S2-151105","Reserved for Curt's parallel sessions","-","Maurice Pope",648,"other","","","-","55","99","Reserved and Withdrawn documents",17010,"Withdrawn","2015-04-20T16:09:10.500",null,"","","","","","","","","","","","","","",""]
["S2-151106","Codecs for WebRTC","Qualcomm Incorporated, Telecom Italia, BlackBerry UK Limited, Nokia Networks","Haris Zisimopoulos",41602,"CR","","","Summary of change: - Updates the reference to draft-ietf-rtcweb-overview-13 - Indicates that any any requirements relating to specific audio and video codecs are excluded - Text is modeified to accurately state 'A WebRTC IMS Client (WIC) is an application using the WebRTC extensions specified in WebRTC 1.0 [85] except for those extensions specifically exempted by 3GPP specifications (e.g. codecs)'","18","5.4","IMS-Related Maintenance",11270,"Agreed","2015-04-20T16:09:10.533","2015-04-20T16:04:42.990","S2-150890","","Rel-12","23.228","12.8.0","IMS_WebRTC","1115","1","F",null,"","","","",""]
["S2-151107","Codecs for WebRTC","Qualcomm Incorporated, Telecom Italia, BlackBerry UK Limited, Nokia Networks","Haris Zisimopoulos",41602,"CR","","","Rel-13 mirror CR: Summary of change: - Updates the reference to draft-ietf-rtcweb-overview-13 - Indicates that any any requirements relating to specific audio and video codecs are excluded - Text is modeified to accurately state 'A WebRTC IMS Client (WIC) is an application using the WebRTC extensions specified in WebRTC 1.0 [85] except for those extensions specifically exempted by 3GPP specifications (e.g. codecs)'","18","5.4","IMS-Related Maintenance",11290,"Agreed","2015-04-20T16:09:10.703","2015-04-20T16:04:43.973","S2-150891","","Rel-13","23.228","13.2.0","IMS_WebRTC","1116","1","A",null,"","","","",""]
["S2-151108","Stage 2 cleanup regarding the WIC registration with a security token","Samsung","Sung Hwan Won",46717,"CR","","","Summary of change: 1. In addition to IMS identities, e.g. the validity period is derived from the security token. 2. Web authentication can be avoided in case of registration refreshment.","18","5.4","IMS-Related Maintenance",11380,"Revised","2015-04-20T16:09:10.797","2015-04-20T16:04:44.923","S2-151082","S2-151388","Rel-12","23.228","12.8.0","TEI12, IMS_WebRTC","1128","1","F",null,"","","","",""]
["S2-151109","Stage 2 cleanup regarding the WIC registration with a security token","Samsung","Sung Hwan Won",46717,"CR","","","Rel-13 mirror CR: Summary of change: 1. In addition to IMS identities, e.g. the validity period is derived from the security token. 2. Web authentication can be avoided in case of registration refreshment.","18","5.4","IMS-Related Maintenance",11410,"Revised","2015-04-20T16:09:10.890","2015-04-20T16:04:46.657","S2-151084","S2-151389","Rel-13","23.228","13.2.0","TEI12, IMS_WebRTC","1129","1","A",null,"","","","",""]
["S2-151110","Updating SRVCC operation possible in E-UTRAN","Qualcomm Incorporated, Huawei, HiSilicon","Haris Zisimopoulos",41602,"CR","","","Summary of change: In order to resolve this issue it is identified that the MME needs to be able to inform the eNB after the TAU to update the UE context to include the SRVCC operation possible.","18","5.4","IMS-Related Maintenance",11240,"Revised","2015-04-20T16:09:10.970","2015-04-20T16:04:48.420","S2-150889","S2-151114","Rel-13","23.216","12.2.0","TEI13","0332","1","F",null,"","","","",""]
["S2-151111","Notify UE conference event package after SRVCC","Huawei, Hisilicon","Maurice Pope",648,"CR","","","Summary of change: This CR proposes that MSC notifies UE the conference related events when it receives conference related events from IMS, via the state independent Notify message.","19","5.5","IMS Maintenance",11440,"Agreed","2015-04-20T16:09:11.063","2015-04-20T16:04:49.403","S2-150833","","Rel-13","23.292","13.1.0","IMS_SCC, TEI13","0228","1","F",null,"","","","",""]
["S2-151112","Notify UE conference event package after SRVCC","Huawei, Hisilicon","Maurice Pope",648,"CR","","","Summary of change: This CR proposes that MSC notifies UE the conference related events when it receives conference related events from IMS, via the state independent Notify message.","19","5.5","IMS Maintenance",11460,"Agreed","2015-04-20T16:09:11.157","2015-04-20T16:04:51.163","S2-150855","","Rel-13","23.237","12.8.0","IMS_SCC, TEI13","0481","1","F",null,"","","","",""]
["S2-151113","Reserved for Gyuri's parallel sessions","-","Maurice Pope",648,"other","","","-","55","99","Reserved and Withdrawn documents",16860,"Withdrawn","2015-04-20T16:09:11.250",null,"","","","","","","","","","","","","","",""]
["S2-151114","Updating SRVCC operation possible in E-UTRAN","Qualcomm Incorporated, Huawei, HiSilicon, Samsung","Haris Zisimopoulos",41602,"CR","","","Summary of change: In order to resolve this issue it is identified that the MME needs to be able to inform the eNB after the TAU to update the UE context to include the SRVCC operation possible.","18","5.4","IMS-Related Maintenance",11250,"Agreed","2015-04-20T16:09:11.280","2015-04-20T16:04:52.833","S2-151110","","Rel-13","23.216","12.2.0","TEI13","0332","2","F",null,"","","","",""]
["S2-151115","Reserved for Gyuri's parallel sessions","-","Maurice Pope",648,"other","","","-","55","99","Reserved and Withdrawn documents",16870,"Withdrawn","2015-04-20T16:09:11.360",null,"","","","","","","","","","","","","","",""]
["S2-151116","Reserved for Gyuri's parallel sessions","-","Maurice Pope",648,"other","","","-","55","99","Reserved and Withdrawn documents",16880,"Withdrawn","2015-04-20T16:09:11.390",null,"","","","","","","","","","","","","","",""]
["S2-151117","Reserved for Gyuri's parallel sessions","-","Maurice Pope",648,"other","","","-","55","99","Reserved and Withdrawn documents",16890,"Withdrawn","2015-04-20T16:09:11.420",null,"","","","","","","","","","","","","","",""]
["S2-151118","Reserved for Gyuri's parallel sessions","-","Maurice Pope",648,"other","","","-","55","99","Reserved and Withdrawn documents",16900,"Withdrawn","2015-04-20T16:09:11.453",null,"","","","","","","","","","","","","","",""]
["S2-151119","Reserved for Gyuri's parallel sessions","-","Maurice Pope",648,"other","","","-","55","99","Reserved and Withdrawn documents",16910,"Withdrawn","2015-04-20T16:09:11.483",null,"","","","","","","","","","","","","","",""]
["S2-151120","Reserved for Gyuri's parallel sessions","-","Maurice Pope",648,"other","","","-","55","99","Reserved and Withdrawn documents",16920,"Withdrawn","2015-04-20T16:09:11.517",null,"","","","","","","","","","","","","","",""]
["S2-151121","[DRAFT] Reply LS on VoLTE Roaming Architecture","NTT DOCOMO INC.","Motohiro Abe",57779,"LS out","","","Draft LS back to GSMA on VoLTE Roaming Architecture","8","4.2","LS (S2-150704) on VoLTE Roaming and Replies",10350,"Withdrawn","2015-04-20T16:09:11.547",null,"S2-150986","","","","","","","","","","S2-150704","GSMA PSMC, NG, SA WG3, SA WG3-LI","GSMA WAS, IDS,  TSG SA, CT WG3"]
["S2-151122","Clarification on geo-local number handling","China Mobile, NTT DOCOMO","Maurice Pope",648,"CR","","","Summary of change: Addition of a sentence to clarify that HPLMN and/or VPLMN support non-internation format, and the use of non-internationl format shall be decided by the HPLMN based on the roaming agreement.","8","4.2","LS (S2-150704) on VoLTE Roaming and Replies",10440,"Withdrawn","2015-04-20T16:09:11.577",null,"S2-150884","","Rel-13","23.228","13.2.0","TEI13","1114","1","C",null,"","","","",""]
["S2-151123","TRF supporting geo-local service number normalization","China Mobile","Maurice Pope",648,"CR","","","Summary of change: Description of geo-local number normalization is added on TRF.","8","4.2","LS (S2-150704) on VoLTE Roaming and Replies",10480,"Noted","2015-04-20T16:09:11.687","2015-04-20T16:04:54.863","S2-150858","","Rel-11","23.228","11.10.0","RAVEL","1111","1","F",null,"","","","",""]
["S2-151124","TRF supporting geo-local service number normalization","China Mobile","Maurice Pope",648,"CR","","","Rel-12 mirror CR: Summary of change: Description of geo-local number normalization is added on TRF.","8","4.2","LS (S2-150704) on VoLTE Roaming and Replies",10500,"Noted","2015-04-20T16:09:11.780","2015-04-20T16:04:55.860","S2-150859","","Rel-12","23.228","12.8.0","RAVEL","1112","1","A",null,"","","","",""]
["S2-151125","TRF supporting geo-local service number normalization","China Mobile","Maurice Pope",648,"CR","","","Rel-13 mirror CR: Summary of change: Description of geo-local number normalization is added on TRF.","8","4.2","LS (S2-150704) on VoLTE Roaming and Replies",10520,"Noted","2015-04-20T16:09:11.873","2015-04-20T16:04:56.873","S2-150860","","Rel-13","23.228","13.2.0","RAVEL","1113","1","A",null,"","","","",""]
["S2-151126","Reserved for Krisztian's parallel sessions","-","Maurice Pope",648,"other","","","-","55","99","Reserved and Withdrawn documents",16660,"Withdrawn","2015-04-20T16:09:11.967",null,"","","","","","","","","","","","","","",""]
["S2-151127","Reserved for Krisztian's parallel sessions","-","Maurice Pope",648,"other","","","-","55","99","Reserved and Withdrawn documents",16670,"Withdrawn","2015-04-20T16:09:11.997",null,"","","","","","","","","","","","","","",""]
["S2-151128","Reserved for Krisztian's parallel sessions","-","Maurice Pope",648,"other","","","-","55","99","Reserved and Withdrawn documents",16680,"Withdrawn","2015-04-20T16:09:12.030",null,"","","","","","","","","","","","","","",""]
["S2-151129","Reserved for Krisztian's parallel sessions","-","Maurice Pope",648,"other","","","-","55","99","Reserved and Withdrawn documents",16690,"Withdrawn","2015-04-20T16:09:12.060",null,"","","","","","","","","","","","","","",""]
["S2-151130","Reserved for Krisztian's parallel sessions","-","Maurice Pope",648,"other","","","-","55","99","Reserved and Withdrawn documents",16700,"Withdrawn","2015-04-20T16:09:12.093",null,"","","","","","","","","","","","","","",""]
["S2-151131","Handling of PSM timer","HTC, Spreadtrum Communications, Qualcomm Incorporated, LG Electronics, Ericsson","Kundan Tiwari",44236,"CR","","","Summary of change: Specify that the MS will trigger RAU/TAU when it needs to change the T3324 timer and negotiate the MRT.","15","5.1","3GPP Packet Access Maintenance",10840,"Agreed","2015-04-20T16:09:12.123","2015-04-20T16:04:57.873","S2-150910","","Rel-12","23.682","12.3.0","MTCe-UEPCOP","0101","1","F",null,"","","","",""]
["S2-151132","Handling of PSM timer","HTC, Spreadtrum Communications, Qualcomm Incorporated, LG Electronics, Ericsson","Kundan Tiwari",44236,"CR","","","Rel-13 mirror CR: Summary of change: Specify that the MS will trigger RAU/TAU when it needs to change the T3324 timer and negotiate the MRT.","15","5.1","3GPP Packet Access Maintenance",10860,"Agreed","2015-04-20T16:09:12.217","2015-04-20T16:04:58.887","S2-150911","","Rel-13","23.682","13.1.0","MTCe-UEPCOP","0102","1","A",null,"","","","",""]
["S2-151133","[DRAFT] Reply LS on Clarification regarding change of active time value and periodic TAU or RAU timer value for UE supporting PSM","Qualcomm Incorporated","Miguel Griot",43100,"LS out","","","Replies that UE can start RAU/TAU when change in condition in the UE triggers a need for a different active time/periodic RAU/TAU timer.","15","5.1","3GPP Packet Access Maintenance",10560,"Revised","2015-04-20T16:09:12.327","2015-04-20T16:04:59.760","S2-150981","S2-151384","Rel-12","","","","","","","","S2-150708","CT WG1"]
["S2-151134","Add Location report action into delete bearer procedure","Huawei, HiSilicon","Runze Zhou",60945,"CR","","","Rel-13 mirror CR: Summary of change: Add clarification that the location change reporting may be controlled by the PGW at the PDN GW initiated dedicated bearer deactivation procedure.","15","5.1","3GPP Packet Access Maintenance",10890,"Noted","2015-04-20T16:09:12.357","2015-04-20T16:04:59.887","S2-150794","","Rel-13","23.401","13.2.0","TEI12","2846","1","A",null,"","","","",""]
["S2-151135","Enable ISR for PS-only UE","CATT","Ming Ai",40862,"CR","","","Summary of change: 1. It is proposed that in such case the SGSN should activate ISR if 'SMS in SGSN' is used. 2. In such case, it is further proposed that SGSN forward received MT short message to MME.","45","6.20.1","TEI13 Category B/C for 3GPP Packet Access",16530,"Agreed","2015-04-20T16:09:12.450","2015-04-20T16:05:00.883","S2-150991","","Rel-13","23.060","13.2.0","TEI13","1893","5","C",null,"","","","",""]
["S2-151136","Enable ISR for PS-only UE","CATT","Ming Ai",40862,"CR","","","Summary of change: 1. It is proposed that in such case the SGSN should activate ISR in Combined RAU procedure if 'SMS in SGSN' is used. 2. If 'SMS in MME' is used, the MME should activated ISR, as well. 3. If 'SMS in SGSN' is used for a UE, the SGSN does","45","6.20.1","TEI13 Category B/C for 3GPP Packet Access",16550,"Revised","2015-04-20T16:09:12.560","2015-04-20T16:05:02.663","S2-150994","S2-151145","Rel-13","23.272","12.5.0","TEI13","0939","5","C",null,"","","","",""]
["S2-151137","Paging priority and ARP Priority level: extension of CR2812r2 to CR2840r2","Vodafone","Chris Pudney",1122,"CR","","","Summary of change: Clarify that the ARP value used for paging priority setting is the ARP priority level.","45","6.20.1","TEI13 Category B/C for 3GPP Packet Access",16590,"Agreed","2015-04-20T16:09:12.653","2015-04-20T16:05:04.377","S2-151074","","Rel-13","23.401","13.2.0","SAES, TEI13","2857","1","F",null,"","","","",""]
["S2-151138","MBMS Session Start procedure correction and editorial corrections","China Telecom","Lin Wu",61553,"CR","","","Summary of change: It modidies the flow 8.3.2 to change that the MBMS GW initiates IP Multicast distribution and/or unicast bearers in step 6. It adds abbreviation MCE and modifies document accordingly. Some editorial corrections.","22","6.1.1","Rel-13 3GPP Pkt Access Maintenance",11520,"Agreed","2015-04-20T16:09:12.763","2015-04-20T16:05:06.157","S2-150951","","Rel-13","23.246","13.0.0","TEI13","0392","1","F",null,"","","","",""]
["S2-151139","Support for ProSe in multicarrier across PLMNs","Qualcomm Incorporated, Ericsson","Haris Zisimopoulos",41602,"CR","","","Summary of change: - Clarifies the multicarrier support across PLMNs - Adds the term 'connected to a cell' for procedures that apply connected mode - Adds reference in TS 36.304","15","5.1","3GPP Packet Access Maintenance",10650,"Revised","2015-04-20T16:09:12.857","2015-04-20T16:05:07.157","S2-150888","S2-151325","Rel-12","23.303","12.4.0","ProSe","0151","2","F",null,"","","","",""]
["S2-151140","Solution update for setting up an AS session with required QoS","Huawei, HiSilicon, Alcatel-Lucent, Intel, China Mobile","Mirko Schramm",23396,"pCR","","","This contribution completes the solution description.","29","6.5","Architecture Enhancements for Service Exposure (AESE)",12440,"Revised","2015-04-20T16:37:00.197","2015-04-20T16:32:27.100","S2-151236","S2-151405","Rel-13","23.708","","AESE","","","","","","","","",""]
["S2-151141","AESE - Solution 6 Evaluation","Alcatel-Lucent, Cisco Systems Inc","Mike Dolan",1692,"pCR","","","This contribution provides evaluation text for Solution 6 in TR 23.708 (AESE).","29","6.5","Architecture Enhancements for Service Exposure (AESE)",12620,"Approved","2015-04-20T16:37:00.257","2015-04-20T16:32:27.990","S2-151241","","Rel-13","23.708","","","","","","","","","","",""]
["S2-151142","Solution update for background data transfer","Huawei, HiSilicon, NTT DOCOMO","Mirko Schramm",23396,"pCR","","","This contribution updates the solution description and proposes a new alternative.","29","6.5","Architecture Enhancements for Service Exposure (AESE)",12650,"Revised","2015-04-20T16:37:00.303","2015-04-20T16:32:28.097","S2-151242","S2-151407","Rel-13","23.708","","AESE","","","","","","","","",""]
["S2-151143","Reserved for Puneet's parallel sessions","-","Maurice Pope",648,"other","","","-","55","99","Reserved and Withdrawn documents",17190,"Withdrawn","2015-04-20T16:09:12.980",null,"","","","","","","","","","","","","","",""]
["S2-151144","Reserved for Puneet's parallel sessions","-","Maurice Pope",648,"other","","","-","55","99","Reserved and Withdrawn documents",17200,"Withdrawn","2015-04-20T16:09:13.013",null,"","","","","","","","","","","","","","",""]
["S2-151145","Enable ISR for PS-only UE","CATT","Ming Ai",40862,"CR","","","Summary of change: 1. It is proposed that in such case the SGSN should activate ISR in Combined RAU procedure if 'SMS in SGSN' is used. 2. If 'SMS in MME' is used, the MME should activated ISR, as well. 3. If 'SMS in SGSN' is used for a UE, the SGSN does","45","6.20.1","TEI13 Category B/C for 3GPP Packet Access",16560,"Agreed","2015-04-20T16:09:13.060","2015-04-20T16:05:08.043","S2-151136","","Rel-13","23.272","12.5.0","TEI13","0939","6","C",null,"","","","",""]
["S2-151146","Application reporting functionality for FMSS solution","Cisco, Allot Communications, Huawei, HiSilicon, Sprint, Comverse, Sandvine Incoporated, US cellular, Broadcom Corporation","Nirav Salot",56645,"pCR","","","This contribution proposes various alternatives to resolve the editor's note on the support of application reporting functionality for FMSS solution.","37","6.13","Flexible Mobile Service Steering (FMSS)",14850,"Revised","2015-04-20T16:09:13.137","2015-04-20T16:05:09.743","S2-150788","S2-151180","Rel-13","23.718","","FMSS","","","","","","","","",""]
["S2-151147","Updates to solution with policy steering interface","Ericsson, AT&T, KDDI, Nokia Networks","Shabnam Sultana",21207,"pCR","","","Proposes updates and further details to the solution with St policy steering interface","37","6.13","Flexible Mobile Service Steering (FMSS)",14880,"Revised","2015-04-20T16:09:13.183","2015-04-20T16:05:10.757","S2-150785","S2-151204","Rel-13","23.718","","FMSS","","","","","","","","",""]
["S2-151148","Procedures, interface details and evaluation details for Sd/Gx based solutions","Allot Communications, Cisco, Huawei, Hisilicon, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, SPRINT, Comverse, Sandvine Incorporated, US Cellular, Broadcom Corporation, Openet Telecom","Alla Goldner",42718,"pCR","","","This paper provides description of procedures; resolves Editor's Notes related to interface enhancements and introduces more description into evaluation sections.","37","6.13","Flexible Mobile Service Steering (FMSS)",14910,"Revised","2015-04-20T16:09:13.247","2015-04-20T16:05:11.633","S2-150791","S2-151181","Rel-13","23.718","","FMSS-SA2TR","","","","","","","","",""]
["S2-151149","A clarification for Gx or Sd based solution","China Unicom, China Telecom, Intel","Maurice Pope",648,"pCR","","","This paper adds 'NOTE's to further clarify Traffic steering control and enforcement over Sd can be applied without any other PCC functionalities, if not needed.","37","6.13","Flexible Mobile Service Steering (FMSS)",14940,"Withdrawn","2015-04-20T16:09:13.310",null,"S2-151075","","Rel-13","23.718","","FMSS","","","","","","","","",""]
["S2-151150","Mandatory functionality over the Sd interface","Cisco, Allot Communications, Sprint, Comverse, Sandvine Incoporated, US cellular, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell","Nirav Salot",56645,"pCR","","","This paper provides various stage 2 and stage 3 references to highlight that only Application detection function is mandatorily defined over the Sd interface.","37","6.13","Flexible Mobile Service Steering (FMSS)",14960,"Revised","2015-04-20T16:09:13.357","2015-04-20T16:05:13.380","S2-150789","S2-151182","Rel-13","23.718","","FMSS","","","","","","","","",""]
["S2-151151","Reduction of eWebRTCi scope","Alcatel-Lucent, Alcatel-Lucent ShangHai Bell","Laurent Thiebaut",11066,"pCR","","","Reduction of eWebRTCi scope","33","6.9","Enhancements to WEBRTC interoperability (eWebRTCi)",13460,"Approved","2015-04-20T16:09:13.403","2015-04-20T16:05:14.267","S2-150974","","","23.706","","eWebRTCi","","","","","","","","",""]
["S2-151152","Clarification on Solution 1 in 5.2: scalability and service resiliency","Alcatel-Lucent, Alcatel-Lucent ShangHai Bell","Laurent Thiebaut",11066,"pCR","","","Clarification on Solution 1 in 5.2: scalability and service resiliency","33","6.9","Enhancements to WEBRTC interoperability (eWebRTCi)",13520,"Approved","2015-04-20T16:09:13.450","2015-04-20T16:05:15.143","S2-150972","","","23.706","","eWebRTCi","","","","","","","","",""]
["S2-151153","Enhancements to Solution 2","Ericsson","Shabnam Sultana",21207,"pCR","","","This contribution includes further clarification and editorial changes to Solution 2","33","6.9","Enhancements to WEBRTC interoperability (eWebRTCi)",13540,"Approved","2015-04-20T16:09:13.497","2015-04-20T16:05:16.047","S2-150747","","Rel-13","23.706","","eWebRTCi","","","","","","","","",""]
["S2-151154","Evaluation of \"ePSM\" proposal in FS_Hlcom","Qualcomm Incorporated, LGE","Miguel Griot",43100,"other","","","Slides on Evaluation of 'ePSM' proposal in FS_Hlcom","36","6.12","Optimizations to Support High Latency Communications (FS_HLCom)",14640,"Available","2015-04-20T16:09:13.543","2015-04-20T16:05:16.907","","","Rel-13","","","","","","","","","","","",""]
["S2-151155","Clean-up on HL_Com TR","Ericsson","Shabnam Sultana",21207,"pCR","","","This P-CR updates solutions in the TR","36","6.12","Optimizations to Support High Latency Communications (FS_HLCom)",14670,"Revised","2015-04-20T16:09:13.590","2015-04-20T16:05:16.920","S2-150779","S2-151188","Rel-13","23.709","","FS_HLcom","","","","","","","","",""]
["S2-151156","GROUPE Conclusions","Qualcomm Incorporated","Miguel Griot",43100,"pCR","","","Provides modifications to the conclusions based on UE support of MBMS.","31","6.7","Group based Enhancements (GROUPE)",13150,"Revised","2015-04-20T16:09:13.637","2015-04-20T16:05:17.873","S2-150979","S2-151191","Rel-13","23.769","","GROUPE","","","","","","","","",""]
["S2-151157","Remove Editor's Notes","Alcatel-Lucent","Mike Dolan",1692,"pCR","","","This contribution provides text to remove some editor's notes in TR 23.769 (GROUPE).","31","6.7","Group based Enhancements (GROUPE)",13180,"Approved","2015-04-20T16:09:13.683","2015-04-20T16:05:18.730","S2-150944","","Rel-13","23.769","","GROUPE","","","","","","","","",""]
["S2-151158","Clarification on MBMS based solution","ZTE","Zhendong Li",38521,"pCR","","","This contribution proposes clarifications on the MBMS based solution, e.g. HSS behaviour and impacts.","31","6.7","Group based Enhancements (GROUPE)",13200,"Withdrawn","2015-04-20T16:09:13.730",null,"S2-151005","","Rel-13","23.769","","GROUPE","","","","","","","","",""]
["S2-151159","Cover Sheet for TR 23.769 for Approval at TSG SA","GROUPE Rapporteurs (Huawei)","Runze Zhou",60945,"TS or TR","","","This contribution proposes a cover page for submitting TR 23.769 to SA plenary for Approval.","31","6.7","Group based Enhancements (GROUPE)",13250,"Revised","2015-04-20T16:09:13.777","2015-04-20T16:05:20.523","S2-150844","S2-151413","Rel-13","23.769","1.2.0","","","","","","","","","",""]
["S2-151160","Group message delivery function and procedure","Huawei, Hisilicon, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Samsung, KPN","Runze Zhou",60945,"CR","","","Summary of change: High level description for group messge delivery function and delivery procedures is specified.","31","6.7","Group based Enhancements (GROUPE)",13280,"Revised","2015-04-20T16:09:13.857","2015-04-20T16:05:20.757","S2-150842","S2-151192","Rel-13","23.682","13.1.0","GROUPE","0094","1","B",null,"","","","",""]
["S2-151161","Procedures of TCF Solution","China Mobile, CATR","Tao Sun",54129,"pCR","","","Describe the procedures and call flows for the TCF solution","37","6.13","Flexible Mobile Service Steering (FMSS)",15120,"Revised","2015-04-20T16:09:13.980","2015-04-20T16:05:21.773","S2-151072","S2-151165","Rel-13","23.718","","FMSS","","","","","","","","",""]
["S2-151162","Enforcement of traffic steering policy","Cisco, Allot Communications, Huawei, HiSilicon, Sprint, Comverse, Sandvine Incoporated, US cellular, Broadcom Corporation, Alcatel-Lucent and Alcatel-Lucent Shanghai Bell","Nirav Salot",56645,"pCR","","","This paper provides high level description of the enforcement of the traffic steering policy by solution 1.1 and solution 1.2.","37","6.13","Flexible Mobile Service Steering (FMSS)",14990,"Revised","2015-04-20T16:09:14.027","2015-04-20T16:05:22.693","S2-150790","S2-151183","Rel-13","23.718","","FMSS","","","","","","","","",""]
["S2-151163","Clarification and Evaluation of Policy Based TCF Solution","China Mobile, Broadcom Corporation, CATR, KDDI","Tao Sun",54129,"pCR","","","This contribution clarifies the TCF solution, addresses the corresponding FFS and evaluates the solution.","37","6.13","Flexible Mobile Service Steering (FMSS)",15030,"Revised","2015-04-20T16:09:14.073","2015-04-20T16:05:23.550","S2-150816","S2-151199","Rel-13","23.718","","FMSS","","","","","","","","",""]
["S2-151164","Call flows for the solution with service steering policy interface","Ericsson","Shabnam Sultana",21207,"pCR","","","This contribution proposes call flows for the FMSS solution with service steering policy interface","37","6.13","Flexible Mobile Service Steering (FMSS)",15080,"Revised","2015-04-20T16:09:14.120","2015-04-20T16:05:24.423","S2-150786","S2-151200","Rel-13","23.718","","FMSS","","","","","","","","",""]
["S2-151165","Procedures of TCF Solution","China Mobile, CATR","Tao Sun",54129,"pCR","","","Describe the procedures and call flows for the TCF solution","37","6.13","Flexible Mobile Service Steering (FMSS)",15130,"Revised","2015-04-20T16:09:14.167","2015-04-20T16:05:25.297","S2-151161","S2-151202","Rel-13","23.718","","FMSS","","","","","","","","",""]
["S2-151166","Semantics of the Traffic Steering Policy","Ericsson, AT&T, Nokia Networks","Shabnam Sultana",21207,"pCR","","","Proposes a Traffic Steering Rule over St interface","37","6.13","Flexible Mobile Service Steering (FMSS)",15160,"Revised","2015-04-20T16:09:14.197","2015-04-20T16:05:26.187","S2-150753","S2-151201","Rel-13","23.718","","FMSS","","","","","","","","",""]
["S2-151167","Clarification to the solution 4","ZTE","Zhendong Li",38521,"pCR","","","This paper makes clarification to the solution 4.","33","6.9","Enhancements to WEBRTC interoperability (eWebRTCi)",13570,"Approved","2015-04-20T16:09:14.260","2015-04-20T16:05:27.077","S2-151008","","Rel-13","23.706","","eWebRTCi","","","","","","","","",""]
["S2-151168","Evaluation Criteria For Solution 5.2.1","Alcatel-Lucent, Alcatel-Lucent ShangHai Bell","Laurent Thiebaut",11066,"pCR","","","Evaluation Criteria For Solution 5.2.1","33","6.9","Enhancements to WEBRTC interoperability (eWebRTCi)",13620,"Revised","2015-04-20T16:09:14.307","2015-04-20T16:05:27.967","S2-150973","S2-151195","","23.706","","eWebRTCi","","","","","","","","",""]
["S2-151169","Evaluation Criteria For Solution 2","Ericsson","Shabnam Sultana",21207,"pCR","","","This contribution completes the evaluation criteria for Solution 2","33","6.9","Enhancements to WEBRTC interoperability (eWebRTCi)",13650,"Revised","2015-04-20T16:09:14.353","2015-04-20T16:05:28.853","S2-150748","S2-151197","Rel-13","23.706","","eWebRTCi","","","","","","","","",""]
["S2-151170","Evaluation of Solution 3 +5","Nokia Networks, Huawei","Martin Oettl",17230,"pCR","","","This paper adds text allowing an evaluation of solution 3 +5.","33","6.9","Enhancements to WEBRTC interoperability (eWebRTCi)",13680,"Revised","2015-04-20T16:09:14.400","2015-04-20T16:05:29.777","S2-150960","S2-151198","Rel-13","23.706","","eWebRTCi","","","","","","","","",""]
["S2-151171","Evaluation Comparison of Solutions in Section 5","T-Mobile USA","Christopher Joul",31136,"pCR","","","This document includes evaluation comparison table for solution 1,2 and 3","33","6.9","Enhancements to WEBRTC interoperability (eWebRTCi)",13710,"Revised","2015-04-20T16:09:14.463","2015-04-20T16:05:30.710","S2-150963","S2-151196","Rel-13","23.706","","","","","","","","","","",""]
["S2-151172","APN and group specific NAS Level congestion control","NTT DOCOMO","SRISAKUL THAKOLSRI",42550,"CR","","","Summary of change: Adding criteria to detect NAS signalling congestion associated with the group of UEs belong to the same group ID and subscribed to particular APN.","31","6.7","Group based Enhancements (GROUPE)",13360,"Revised","2015-04-20T16:09:14.510","2015-04-20T16:05:30.930","S2-150767","S2-151193","Rel-13","23.401","13.2.0","GROUPE","2843","1","B",null,"","","","",""]
["S2-151173","APN and group specific NAS level congestion control","NTT DOCOMO","SRISAKUL THAKOLSRI",42550,"CR","","","Summary of change: Adding criteria to detect NAS signalling congestion associated with the group of MSs belong to the same group ID and subscribed to particular APN.","31","6.7","Group based Enhancements (GROUPE)",13390,"Revised","2015-04-20T16:09:14.637","2015-04-20T16:05:31.897","S2-150768","S2-151194","Rel-13","23.060","13.2.0","GROUPE","1956","1","B",null,"","","","",""]
["S2-151174","Cleanup for Solution: Use of MBMS for Group Message Delivery","Samsung","Sung Hwan Won",46717,"pCR","","","It is proposed to modify solution description of 'Use of MBMS for Group Message Delivery.'","31","6.7","Group based Enhancements (GROUPE)",13220,"Revised","2015-04-20T16:09:14.743","2015-04-20T16:05:32.770","S2-151078","S2-151415","Rel-13","23.769","","GROUPE","","","","","","","","",""]
["S2-151175","Updating solutions 2 and 6","Huawei, HiSilicon","Frank Mademann",6821,"pCR","","","This paper updates solution 2 to capture the aspects from solution 6.","36","6.12","Optimizations to Support High Latency Communications (FS_HLCom)",14720,"Revised","2015-04-20T16:09:14.790","2015-04-20T16:05:33.643","S2-151087","S2-151402","Rel-13","23.709","","HLcom","","","","","","","","",""]
["S2-151176","Conclusions for HL_Com","Ericsson, Qualcomm Incorporated","Shabnam Sultana",21207,"pCR","","","This P-CR adds conclusions for the FS_HLCOM study","36","6.12","Optimizations to Support High Latency Communications (FS_HLCom)",14590,"Revised","2015-04-20T16:09:14.853","2015-04-20T16:05:34.503","S2-150778","S2-151190","Rel-13","23.709","","FS_HLcom","","","","","","","","",""]
["S2-151177","HLCom - Solution 4 - add SCEF, additional evaluation text","Alcatel-Lucent","Mike Dolan",1692,"pCR","","","This contribution provides additional evaluation text to Solution 4 in TR 23.709 (HLCom) to indicate that Solution 4 incorporates Solution 3 and elaborates on MME actions. It also updates the figures and flows to include the SCEF.","36","6.12","Optimizations to Support High Latency Communications (FS_HLCom)",14770,"Revised","2015-04-20T16:09:14.900","2015-04-20T16:05:35.377","S2-150948","S2-151189","Rel-13","23.709","","","","","","","","","","",""]
["S2-151178","Solution Updates on Solution 3","LG Electronics","Jinsook Ryu",39022,"pCR","","","This paper address further enhancement on Reusing MONTE solution for practical usage of the UE reachability function.","36","6.12","Optimizations to Support High Latency Communications (FS_HLCom)",14750,"Approved","2015-04-20T16:09:14.947","2015-04-20T16:05:35.517","S2-150902","","Rel-13","23.709","","FS_HLcom","","","","","","","","",""]
["S2-151179","Steering Rule for Uplink/Downlink Traffic","Huawei, Hisilicon, Cisco, Allot Communications, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Sprint, Comverse, Openet Telecom","Shufeng Shi",56675,"pCR","","","Updates the definition of steering rules applied to Gx and Sd based solution for uplink and downlink traffic.","37","6.13","Flexible Mobile Service Steering (FMSS)",15210,"Revised","2015-04-20T16:09:14.993","2015-04-20T16:05:36.407","S2-150792","S2-151203","Rel-13","23.718","","FMSS-SA2TR","","","","","","","","",""]
["S2-151180","Application reporting functionality for FMSS solution","Cisco, Allot Communications, Huawei, HiSilicon, Sprint, Comverse, Sandvine Incoporated, US cellular, Broadcom Corporation","Nirav Salot",56645,"pCR","","","This contribution proposes various alternatives to resolve the editor's note on the support of application reporting functionality for FMSS solution.","37","6.13","Flexible Mobile Service Steering (FMSS)",14860,"Approved","2015-04-20T16:09:15.057","2015-04-20T16:05:37.277","S2-151146","","Rel-13","23.718","","FMSS","","","","","","","","",""]
["S2-151181","Procedures, interface details and evaluation details for Sd/Gx based solutions","Allot Communications, Cisco, Huawei, Hisilicon, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, SPRINT, Comverse, Sandvine Incorporated, US Cellular, Broadcom Corporation, Openet Telecom","Alla Goldner",42718,"pCR","","","This paper provides description of procedures; resolves Editor's Notes related to interface enhancements and introduces more description into evaluation sections.","37","6.13","Flexible Mobile Service Steering (FMSS)",14920,"Approved","2015-04-20T16:09:15.103","2015-04-20T16:05:38.153","S2-151148","","Rel-13","23.718","","FMSS-SA2TR","","","","","","","","",""]
["S2-151182","Mandatory functionality over the Sd interface","Cisco, Allot Communications, Sprint, Comverse, Sandvine Incoporated, US cellular, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell","Nirav Salot",56645,"pCR","","","This paper provides various stage 2 and stage 3 references to highlight that only Application detection function is mandatorily defined over the Sd interface.","37","6.13","Flexible Mobile Service Steering (FMSS)",14970,"Approved","2015-04-20T16:09:15.150","2015-04-20T16:05:39.027","S2-151150","","Rel-13","23.718","","FMSS","","","","","","","","",""]
["S2-151183","Enforcement of traffic steering policy","Cisco, Allot Communications, Huawei, HiSilicon, Sprint, Comverse, Sandvine Incoporated, US cellular, Broadcom Corporation, Alcatel-Lucent and Alcatel-Lucent Shanghai Bell, Openet Telecom","Nirav Salot",56645,"pCR","","","This paper provides high level description of the enforcement of the traffic steering policy by solution 1.1 and solution 1.2.","37","6.13","Flexible Mobile Service Steering (FMSS)",15000,"Revised","2015-04-20T16:09:15.197","2015-04-20T16:05:39.883","S2-151162","S2-151396","Rel-13","23.718","","FMSS","","","","","","","","",""]
["S2-151184","Discussion on the how to avoid SRVCC","ZTE","Zhendong Li",38521,"pCR","","","This paper analyzes the solutions on how to avoid the SRVCC and proposes the suggestion","33","6.9","Enhancements to WEBRTC interoperability (eWebRTCi)",13760,"Revised","2015-04-20T16:09:15.243","2015-04-20T16:05:40.757","S2-151007","S2-151385","Rel-13","23.706","","eWebRTCi","","","","","","","","",""]
["S2-151185","Way forward on the key issue - Architectural aspects for minimizing the need for bearer level protocol conversion","ZTE","Zhendong Li",38521,"pCR","","","This paper analyzes the solution on the key issue - 'Architectural aspects for minimizing the need for bearer level protocol conversion' and proposes the way forward.","33","6.9","Enhancements to WEBRTC interoperability (eWebRTCi)",13820,"Revised","2015-04-20T16:09:15.307","2015-04-20T16:05:41.663","S2-151009","S2-151386","Rel-13","23.706","","eWebRTCi","","","","","","","","",""]
["S2-151186","[DRAFT] Request confirmation on OMR-based solution for end-to-end transparent media in eWebRTCi","SA WG2","Zhendong Li",38521,"LS out","","","To: SA WG3-LI. Attachments: TR 23.706 v0.3.0","33","6.9","Enhancements to WEBRTC interoperability (eWebRTCi)",13840,"Revised","2015-04-20T16:09:15.353","2015-04-20T16:05:42.520","","S2-151387","Rel-13","","","","","","","",null,"SA3-LI","-"]
["S2-151187","Conclusions for key issue 1","Alcatel-Lucent, Alcatel-Lucent ShangHai Bell","Maurice Pope",648,"pCR","","","Provides Conclusions on KI 1","33","6.9","Enhancements to WEBRTC interoperability (eWebRTCi)",13730,"Approved","2015-04-20T16:09:15.400","2015-04-20T16:05:42.537","","","Rel-13","23.706","","eWebRTCi","","","","","","","","",""]
["S2-151188","Clean-up on HL_Com TR","Ericsson","Shabnam Sultana",21207,"pCR","","","This P-CR updates solutions in the TR","36","6.12","Optimizations to Support High Latency Communications (FS_HLCom)",14680,"Approved","2015-04-20T16:09:15.447","2015-04-20T16:05:43.410","S2-151155","","Rel-13","23.709","","FS_HLcom","","","","","","","","",""]
["S2-151189","HLCom - Solution 4 - add SCEF, additional evaluation text","Alcatel-Lucent","Mike Dolan",1692,"pCR","","","This contribution provides additional evaluation text to Solution 4 in TR 23.709 (HLCom) to indicate that Solution 4 incorporates Solution 3 and elaborates on MME actions. It also updates the figures and flows to include the SCEF.","36","6.12","Optimizations to Support High Latency Communications (FS_HLCom)",14780,"Revised","2015-04-20T16:09:15.493","2015-04-20T16:05:44.267","S2-151177","S2-151403","Rel-13","23.709","","","","","","","","","","",""]
["S2-151190","Conclusions for HL_Com","Ericsson, Qualcomm Incorporated","Shabnam Sultana",21207,"pCR","","","This P-CR adds conclusions for the FS_HLCOM study","36","6.12","Optimizations to Support High Latency Communications (FS_HLCom)",14600,"Revised","2015-04-20T16:09:15.557","2015-04-20T16:05:44.393","S2-151176","S2-151401","Rel-13","23.709","","FS_HLcom","","","","","","","","",""]
["S2-151191","GROUPE Conclusions","Qualcomm Incorporated","Miguel Griot",43100,"pCR","","","Provides modifications to the conclusions based on UE support of MBMS.","31","6.7","Group based Enhancements (GROUPE)",13160,"Approved","2015-04-20T16:09:15.603","2015-04-20T16:49:29.747","S2-151156","","Rel-13","23.769","","GROUPE","","","","","","","","",""]
["S2-151192","Group message delivery function and procedure","Huawei, Hisilicon, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Samsung, KPN","Runze Zhou",60945,"CR","","","Summary of change: High level description for group messge delivery function and delivery procedures is specified.","31","6.7","Group based Enhancements (GROUPE)",13290,"Revised","2015-04-20T16:09:15.650","2015-04-20T16:05:46.170","S2-151160","S2-151414","Rel-13","23.682","13.1.0","GROUPE","0094","2","B",null,"","","","",""]
["S2-151193","APN and group specific NAS Level congestion control","NTT DOCOMO","SRISAKUL THAKOLSRI",42550,"CR","","","Summary of change: Adding criteria to detect NAS signalling congestion associated with the group of UEs belong to the same group ID and subscribed to particular APN.","31","6.7","Group based Enhancements (GROUPE)",13370,"Agreed","2015-04-20T16:09:15.757","2015-04-20T16:05:47.027","S2-151172","","Rel-13","23.401","13.2.0","GROUPE","2843","2","B",null,"","","","",""]
["S2-151194","APN and group specific NAS level congestion control","NTT DOCOMO","SRISAKUL THAKOLSRI",42550,"CR","","","Summary of change: Adding criteria to detect NAS signalling congestion associated with the group of MSs belong to the same group ID and subscribed to particular APN.","31","6.7","Group based Enhancements (GROUPE)",13400,"Agreed","2015-04-20T16:09:15.867","2015-04-20T16:05:47.917","S2-151173","","Rel-13","23.060","13.2.0","GROUPE","1956","2","B",null,"","","","",""]
["S2-151195","Evaluation Criteria For Solution 5.2.1","Alcatel-Lucent, Alcatel-Lucent ShangHai Bell","Laurent Thiebaut",11066,"pCR","","","Evaluation Criteria For Solution 5.2.1","33","6.9","Enhancements to WEBRTC interoperability (eWebRTCi)",13630,"Noted","2015-04-20T16:09:15.960","2015-04-20T16:05:48.790","S2-151168","","","23.706","","eWebRTCi","","","","","","","","",""]
["S2-151196","Evaluation Comparison of Solutions in Section 5","T-Mobile USA","Christopher Joul",31136,"pCR","","","This document includes evaluation comparison table for solution 1,2 and 3","33","6.9","Enhancements to WEBRTC interoperability (eWebRTCi)",13720,"Approved","2015-04-20T16:09:16.007","2015-04-20T16:05:49.650","S2-151171","","Rel-13","23.706","","","","","","","","","","",""]
["S2-151197","Evaluation Criteria For Solution 2","Ericsson","Shabnam Sultana",21207,"pCR","","","This contribution completes the evaluation criteria for Solution 2","33","6.9","Enhancements to WEBRTC interoperability (eWebRTCi)",13660,"Noted","2015-04-20T16:09:16.053","2015-04-20T16:05:49.773","S2-151169","","Rel-13","23.706","","eWebRTCi","","","","","","","","",""]
["S2-151198","Evaluation of Solution 3 +5","Nokia Networks, Huawei","Martin Oettl",17230,"pCR","","","This paper adds text allowing an evaluation of solution 3 +5.","33","6.9","Enhancements to WEBRTC interoperability (eWebRTCi)",13690,"Noted","2015-04-20T16:09:16.117","2015-04-20T16:05:50.647","S2-151170","","Rel-13","23.706","","eWebRTCi","","","","","","","","",""]
["S2-151199","Clarification and Evaluation of Policy Based TCF Solution","China Mobile, Broadcom Corporation, CATR, KDDI","Tao Sun",54129,"pCR","","","This contribution clarifies the TCF solution, addresses the corresponding FFS and evaluates the solution.","37","6.13","Flexible Mobile Service Steering (FMSS)",15040,"Revised","2015-04-20T16:09:16.163","2015-04-20T16:05:51.490","S2-151163","S2-151397","Rel-13","23.718","","FMSS","","","","","","","","",""]
["S2-151200","Call flows for the solution with service steering policy interface","Ericsson","Shabnam Sultana",21207,"pCR","","","This contribution proposes call flows for the FMSS solution with service steering policy interface","37","6.13","Flexible Mobile Service Steering (FMSS)",15090,"Approved","2015-04-20T16:36:55.420","2015-04-20T16:31:10.037","S2-151164","","Rel-13","23.718","","FMSS","","","","","","","","",""]
["S2-151201","Semantics of the Traffic Steering Policy","Ericsson, AT&T, Nokia Networks","Shabnam Sultana",21207,"pCR","","","Proposes a Traffic Steering Rule over St interface","37","6.13","Flexible Mobile Service Steering (FMSS)",15170,"Revised","2015-04-20T16:36:55.453","2015-04-20T16:31:10.940","S2-151166","S2-151398","Rel-13","23.718","","FMSS","","","","","","","","",""]
["S2-151202","Procedures of TCF Solution","China Mobile, CATR","Tao Sun",54129,"pCR","","","Describe the procedures and call flows for the TCF solution","37","6.13","Flexible Mobile Service Steering (FMSS)",15140,"Approved","2015-04-20T16:36:55.467","2015-04-20T16:31:11.830","S2-151165","","Rel-13","23.718","","FMSS","","","","","","","","",""]
["S2-151203","Steering Rule for Uplink/Downlink Traffic","Huawei, Hisilicon, Cisco, Allot Communications, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Sprint, Comverse, Openet Telecom","Shufeng Shi",56675,"pCR","","","Updates the definition of steering rules applied to Gx and Sd based solution for uplink and downlink traffic.","37","6.13","Flexible Mobile Service Steering (FMSS)",15220,"Approved","2015-04-20T16:36:55.483","2015-04-20T16:31:12.733","S2-151179","","Rel-13","23.718","","FMSS-SA2TR","","","","","","","","",""]
["S2-151204","Updates to solution with policy steering interface","Ericsson, AT&T, KDDI, Nokia Networks","Shabnam Sultana",21207,"pCR","","","Proposes updates and further details to the solution with St policy steering interface","37","6.13","Flexible Mobile Service Steering (FMSS)",14890,"Approved","2015-04-20T16:36:55.500","2015-04-20T16:31:13.607","S2-151147","","Rel-13","23.718","","FMSS","","","","","","","","",""]
["S2-151205","Reserved for Ivano's parallel sessions","-","Maurice Pope",648,"other","","","-","55","99","Reserved and Withdrawn documents",16930,"Withdrawn","2015-04-20T16:36:55.517",null,"","","","","","","","","","","","","","",""]
["S2-151206","Clarifications for QoS change of default bearer","Huawei, Hisilicon","Mirko Schramm",23396,"CR","","","Summary of change: It is proposed to clarify the requirements for the PCRF and the PCEF/BBERF related to the default bearer QoS change due to a PCRF provisioning of the Authorized Default EPS Bearer QoS parameter. In clause 6.1.1.4 (Bearer Binding) it is","16","5.2","QoS and PCC Maintenance",10950,"Revised","2015-04-20T16:36:55.530","2015-04-20T16:31:14.607","S2-150754","S2-151266","Rel-12","23.203","12.8.0","SAES, TEI12","0940","4","F",null,"","","","",""]
["S2-151207","Clarifications for QoS change of default bearer","Huawei, Hisilicon","Mirko Schramm",23396,"CR","","","Rel-13 mirror CR: Summary of change: It is proposed to clarify the requirements for the PCRF and the PCEF/BBERF related to the default bearer QoS change due to a PCRF provisioning of the Authorized Default EPS Bearer QoS parameter. In clause 6.1.1.4 (Bea","16","5.2","QoS and PCC Maintenance",10980,"Revised","2015-04-20T16:36:55.640","2015-04-20T16:31:16.370","S2-150755","S2-151267","Rel-13","23.203","13.3.0","SAES, TEI12","0941","4","A",null,"","","","",""]
["S2-151208","MS Info Change Reporting Action at change of Serving Node (MME <--> SGSN): Update of call Flows","Alcatel-Lucent, Alcatel-Lucent Shanghai Bell","Laurent Thiebaut",11066,"CR","","","Summary of change: Align the call flows (of mobility between MME and SGSN) with text in § 5.9.2.1 which mostly consist in 1) if the target SGSN/MME supports location information change reporting, the target SGSN/MME shall include the User Location Information in the Modify Bearer Request, regardless of whether ULI change reporting had been requested in the previous RAT by the PGW 2) If User Location Information change reporting is required and supported in the target RAT, the PGW shall request MS Info Change Reporting Action in the Modify Bearer Response","16","5.2","QoS and PCC Maintenance",11070,"Revised","2015-04-20T16:36:55.733","2015-04-20T16:31:18.163","S2-151088","S2-151264","Rel-12","23.401","12.8.0","CNO_ULI","2860","1","F",null,"","","","",""]
["S2-151209","MS Info Change Reporting Action at change of Serving Node (MME <--> SGSN): Update of call Flows","Alcatel-Lucent, Alcatel-Lucent Shanghai Bell","Laurent Thiebaut",11066,"CR","","","Rel-13 mirror CR: Summary of change: Align the call flows (of mobility between MME and SGSN) with text in § 5.9.2.1 which mostly consist in 1) if the target SGSN/MME supports location information change reporting, the target SGSN/MME shall include the User Location Information in the Modify Bearer Request, regardless of whether ULI change reporting had been requested in the previous RAT by the PGW 2) If User Location Information change reporting is required and supported in the target RAT, the PGW shall request MS Info Change Reporting Action in the Modify Bearer Response","16","5.2","QoS and PCC Maintenance",11110,"Revised","2015-04-20T16:36:55.810","2015-04-20T16:31:19.130","S2-151089","S2-151265","Rel-13","23.401","13.2.0","CNO_ULI","2861","1","A",null,"","","","",""]
["S2-151210","[DRAFT] Reply to LS on ePDG selection when UE is roaming","SA WG2","Huan Li",43311,"LS out","","","Response to S2-151095.","24","6.1.3","Rel-13 Non-3GPP Access Maintenance",11550,"Revised","2015-04-20T16:36:55.890","2015-04-20T16:31:19.987","","S2-151395","","","","","","","","","S2-151095","GSMA RiLTE","CT WG1, SA WG1"]
["S2-151211","Clarification of Impacts when Gxx is not used for eHRPD Access","China Telecom, Huawei, HiSilicon","Runze Zhou",60945,"CR","","","Summary of change: Add clarification of system impacts when Gateway Control Session is not established for eHRPD access.","24","6.1.3","Rel-13 Non-3GPP Access Maintenance",11590,"Agreed","2015-04-20T16:36:55.907","2015-04-20T16:31:20.097","S2-150849","","Rel-13","23.402","13.1.0","TEI13","1360","1","F",null,"","","","",""]
["S2-151212","Architectural updates for Monitoring feature","Intel, Alcatel-Lucent, Huawei, Cisco","Puneet Jain",36283,"CR","","","Summary of change: Updates to architecture for Monitoring feature by adding new reference point between SGSN/MME/HSS and SCEF.","30","6.6","Monitoring Enhancements (MONTE)",12790,"Agreed","2015-04-20T16:36:55.983","2015-04-20T16:31:21.080","S2-150877","","Rel-13","23.682","13.1.0","MONTE","0099","1","B",null,"","","","",""]
["S2-151213","Introducing HSS-SCEF and MME/SGSN-SCEF Reference Points","Intel, Huawei, Alcatel-Lucent","Puneet Jain",36283,"CR","","","Summary of change: Adding the introductions and definitions ProSe related entities and interfaces at appropriate places in the TS.","30","6.6","Monitoring Enhancements (MONTE)",12810,"Revised","2015-04-20T16:36:56.077","2015-04-20T16:31:22.063","S2-150936","S2-151271","Rel-13","23.002","13.1.0","MONTE","0283","1","B",null,"","","","",""]
["S2-151214","Monitoring Feature Description","Intel, Huawei, Alcatel-Lucent","Puneet Jain",36283,"CR","","","Summary of change: High level description for monitoring function and monitoring via HSS, SGSN/MME and PCRF is specified.","30","6.6","Monitoring Enhancements (MONTE)",12840,"Revised","2015-04-20T16:36:56.153","2015-04-20T16:31:23.047","S2-150878","S2-151272","Rel-13","23.682","13.1.0","MONTE","0100","1","B",null,"","","","",""]
["S2-151215","Monitoring via PCRF","Ericsson","Shabnam Sultana",21207,"CR","","","Summary of change: Reporting current user location and communication failure via PCRF as defined in 23.203.","30","6.6","Monitoring Enhancements (MONTE)",12880,"Revised","2015-04-20T16:36:56.247","2015-04-20T16:31:24.027","S2-150752","S2-151273","Rel-13","23.682","13.1.0","MONTE","0093","1","B",null,"","","","",""]
["S2-151216","Support for Monitoring Events","Intel","Puneet Jain",36283,"CR","","","Summary of change: High level description for monitoring function.","30","6.6","Monitoring Enhancements (MONTE)",12920,"Revised","2015-04-20T16:36:56.327","2015-04-20T16:31:25.010","S2-150879","S2-151274","Rel-13","23.060","13.2.0","MONTE","1961","1","B",null,"","","","",""]
["S2-151217","Support for Monitoring Events","Intel","Puneet Jain",36283,"CR","","","Summary of change: High level description for monitoring function.","30","6.6","Monitoring Enhancements (MONTE)",12950,"Revised","2015-04-20T16:36:56.403","2015-04-20T16:31:25.963","S2-150880","S2-151275","Rel-13","23.401","13.2.0","MONTE","2851","1","B",null,"","","","",""]
["S2-151218","Introduction of monitoring procedures","Huawei, HiSilicon, Intel, Alcatel-Lucent","Frank Mademann",6821,"CR","","","Summary of change: The procedures for supporting monitoring configuration via MME/SGSN and via HSS are introduced.","30","6.6","Monitoring Enhancements (MONTE)",12990,"Revised","2015-04-20T16:36:56.483","2015-04-20T16:31:26.960","S2-150875","S2-151276","Rel-13","23.682","13.1.0","MONTE","0097","1","B",null,"","","","",""]
["S2-151219","Update to PSM to support monitoring events","Huawei, HiSilicon, Intel","Frank Mademann",6821,"CR","","","Summary of change: Active and reachability timer handling will be decoupled. The support of the monitoring event of Reachability for Data is introduced.","30","6.6","Monitoring Enhancements (MONTE)",13020,"Revised","2015-04-20T16:36:56.577","2015-04-20T16:31:27.943","S2-150872","S2-151410","Rel-13","23.682","13.1.0","MONTE","0096","1","B",null,"","","","",""]
["S2-151220","Update to PSM to support monitoring events","Huawei, HiSilicon, Intel","Frank Mademann",6821,"CR","","","Summary of change: Active and reachability timer handling will be decoupled. The support of monitoring event Reachability for Data are introduced.","30","6.6","Monitoring Enhancements (MONTE)",13050,"Revised","2015-04-20T16:36:56.670","2015-04-20T16:31:28.927","S2-150873","S2-151411","Rel-13","23.401","13.2.0","MONTE","2850","1","B",null,"","","","",""]
["S2-151221","Update to PSM to support monitoring events","Huawei, HiSilicon, Intel","Frank Mademann",6821,"CR","","","Summary of change: Active and reachability timer handling will be decoupled. The support of monitoring event Reachability for Data is introduced.","30","6.6","Monitoring Enhancements (MONTE)",13080,"Revised","2015-04-20T16:36:56.763","2015-04-20T16:31:29.927","S2-150874","S2-151412","Rel-13","23.060","13.2.0","MONTE","1960","1","B",null,"","","","",""]
["S2-151222","Solution update for setting up an AS session with required QoS","Huawei, HiSilicon, Alcatel-Lucent, Intel","Mirko Schramm",23396,"pCR","","","This contribution completes the solution description.","29","6.5","Architecture Enhancements for Service Exposure (AESE)",12420,"Revised","2015-04-20T16:36:56.840","2015-04-20T16:31:30.830","S2-150758","S2-151236","Rel-13","23.708","","AESE","","","","","","","","",""]
["S2-151223","Predictable UE communication pattern","Ericsson","Shabnam Sultana",21207,"pCR","","","Proposes some changes and clarifications for solution 5.","29","6.5","Architecture Enhancements for Service Exposure (AESE)",12520,"Revised","2015-04-20T16:36:56.873","2015-04-20T16:31:31.827","S2-150813","S2-151237","Rel-13","23.708","","AESE","","","","","","","","",""]
["S2-151224","NBIFOM operation Modes","Verizon, Oracle","Uri Baniel",40054,"pCR","","","Enable the operator (via the PCRF) to either accept or reject the request of the UE for NBIFOM operation mode of UE-Initiated mode.","28","6.4","IP Flow Mobility support for S2a and S2b interfaces (NBIFOM)",11980,"Noted","2015-04-20T16:36:56.903","2015-04-20T16:31:32.717","S2-150766","","","23.861","","NBIFOM","","","","","","","","",""]
["S2-151225","Handling of UE-initiated and NW-initiated NBIFOM modes","Ericsson, Huawei, HiSilicon","Shabnam Sultana",21207,"pCR","","","Provides further details and resolutions to the UE-initiated and NW-initiated NBIFOM modes and procedures","28","6.4","IP Flow Mobility support for S2a and S2b interfaces (NBIFOM)",12000,"Revised","2015-04-20T16:36:56.933","2015-04-20T16:31:33.623","S2-150784","S2-151251","Rel-13","23.861","","NBIFOM","","","","","","","","",""]
["S2-151226","Support of NB_IFOM for S2a SCM","Qualcomm Incorporated","Haris Zisimopoulos",41602,"pCR","","","A proposal for NB_IFOM for S2a SCM is provided.","28","6.4","IP Flow Mobility support for S2a and S2b interfaces (NBIFOM)",12080,"Revised","2015-04-20T16:36:56.967","2015-04-20T16:31:34.527","S2-151039","S2-151390","Rel-13","23.861","","NBIFOM","","","","","","","","",""]
["S2-151227","Cleanup of the Loss of an Access from a PDN Connection","Huawei, HiSilicon, China Telecom","Runze Zhou",60945,"pCR","","","This contribution cleans up the Editor's notes in the section of loss of an access from a PDN connection.","28","6.4","IP Flow Mobility support for S2a and S2b interfaces (NBIFOM)",12120,"Revised","2015-04-20T16:36:56.980","2015-04-20T16:31:35.400","S2-150817","S2-151277","Rel-13","23.861","","NBIFOM","","","","","","","","",""]
["S2-151228","Conclusions for indication of 3GPP access loss in SCM","LG Electronics","Hyunsook Kim",42013,"pCR","","","This P-CR proposes the conclusions for 3GPP access loss indication in Single-connection mode.","28","6.4","IP Flow Mobility support for S2a and S2b interfaces (NBIFOM)",12160,"Revised","2015-04-20T16:36:57.013","2015-04-20T16:31:36.307","S2-150987","S2-151278","Rel-13","23.861","","NBIFOM","","","","","","","","",""]
["S2-151229","Conclusions for NBIFOM Open Issues 6 and 7","ZTE","Tricci So",44974,"pCR","","","This P-CR proposes the conclusions oftwo open issues about the support for Inter-MME/SGSN IP flow mobility and PMIP to be deferred from the NBIFOM Rel-13 study.","28","6.4","IP Flow Mobility support for S2a and S2b interfaces (NBIFOM)",12270,"Revised","2015-04-20T16:36:57.043","2015-04-20T16:31:37.180","S2-150853","S2-151279","Rel-13","23.861","","NBIFOM","","","","","","","","",""]
["S2-151230","Issue for eDRX","Acer Incorporated, ITRI","Pei-jung Chen",59891,"pCR","","","This document proposes to add an issue to the TR for FS_eDRX","39","6.15","Feasibility study on Extended DRX cycle for Power Consumption Optimization (FS_eDRX)",15540,"Approved","2015-04-20T16:36:57.077","2015-04-20T16:31:38.067","S2-150769","","","23.770","","FS_eDRX","","","","","","","","",""]
["S2-151231","Extended DRX in Idle mode","Ericsson","Shabnam Sultana",21207,"pCR","","","This document discusses system wide implications from the introduction of support for extended DRX for UE in Idle mode and provides a solution proposal.","39","6.15","Feasibility study on Extended DRX cycle for Power Consumption Optimization (FS_eDRX)",15580,"Approved","2015-04-20T16:36:57.090","2015-04-20T16:31:38.927","S2-150800","","Rel-13","23.770","","FS_eDRX","","","","","","","","",""]
["S2-151232","eDRX - Idle Mode Issue 2: Solution A","Alcatel-Lucent, Qualcomm Incorporated","Mike Dolan",1692,"pCR","","","This contribution provides text for Solution A to Idle Mode Issue 2 in TR 23.770 (eDRX).","39","6.15","Feasibility study on Extended DRX cycle for Power Consumption Optimization (FS_eDRX)",15600,"Revised","2015-04-20T16:36:57.123","2015-04-20T16:31:39.817","S2-150950","S2-151284","Rel-13","23.770","","","","","","","","","","",""]
["S2-151233","GTP-C retransmission in eDRX","Huawei","Runze Zhou",60945,"pCR","","","Add new solution for GTP-C retransmission","39","6.15","Feasibility study on Extended DRX cycle for Power Consumption Optimization (FS_eDRX)",15640,"Approved","2015-04-20T16:36:57.153","2015-04-20T16:31:39.940","S2-150845","","Rel-13","23.770","","FS_eDRX","","","","","","","","",""]
["S2-151234","Extended I-DRX and PSM coexistence","Qualcomm Incorporated","Miguel Griot",43100,"pCR","","","Proposes that it is SGSN/MME decision whether to enable only one of extended I-DRX or PSM, or use both.","39","6.15","Feasibility study on Extended DRX cycle for Power Consumption Optimization (FS_eDRX)",15690,"Revised","2015-04-20T16:36:57.183","2015-04-20T16:31:40.813","S2-150976","S2-151285","Rel-13","23.770","","FS_eDRX","","","","","","","","",""]
["S2-151235","AESE drafting session report","AESE Rapporteurs (Intel)","Puneet Jain",36283,"other","","","Report of AESE drafting session","29","6.5","Architecture Enhancements for Service Exposure (AESE)",12770,"Noted","2015-04-20T16:36:57.217","2015-04-20T16:31:41.733","","","Rel-13","","","","","","","","","","","",""]
["S2-151236","Solution update for setting up an AS session with required QoS","Huawei, HiSilicon, Alcatel-Lucent, Intel","Mirko Schramm",23396,"pCR","","","This contribution completes the solution description.","29","6.5","Architecture Enhancements for Service Exposure (AESE)",12430,"Revised","2015-04-20T16:36:57.230","2015-04-20T16:31:41.750","S2-151222","S2-151140","Rel-13","23.708","","AESE","","","","","","","","",""]
["S2-151237","Predictable UE communication pattern","Ericsson","Shabnam Sultana",21207,"pCR","","","Proposes some changes and clarifications for solution 5.","29","6.5","Architecture Enhancements for Service Exposure (AESE)",12530,"Approved","2015-04-20T16:36:57.263","2015-04-20T16:31:42.703","S2-151223","","Rel-13","23.708","","AESE","","","","","","","","",""]
["S2-151238","Architectural Considerations","NTT DOCOMO, AT&T, Alcatel-Lucent, Intel","Syed Husain",14749,"pCR","","","This contribution proposes text for empty clause 4 in TR 23.708.","29","6.5","Architecture Enhancements for Service Exposure (AESE)",12400,"Approved","2015-04-20T16:36:57.277","2015-04-20T16:31:43.590","S2-150867","","Rel-13","23.708","","AESE","","","","","","","","",""]
["S2-151239","Solution update for change of chargeable party","Huawei, HiSilicon","Mirko Schramm",23396,"pCR","","","This contribution completes the solution description.","29","6.5","Architecture Enhancements for Service Exposure (AESE)",12480,"Revised","2015-04-20T16:36:57.310","2015-04-20T16:31:44.497","S2-150759","S2-151406","Rel-13","23.708","","AESE","","","","","","","","",""]
["S2-151240","Solution update for informing about UE's connection properties","Huawei, HiSilicon","Mirko Schramm",23396,"pCR","","","This contribution updates the solution description and proposes a new alternative.","29","6.5","Architecture Enhancements for Service Exposure (AESE)",12590,"Approved","2015-04-20T16:36:57.340","2015-04-20T16:31:45.387","S2-150760","","Rel-13","23.708","","AESE","","","","","","","","",""]
["S2-151241","AESE - Solution 6 Evaluation","Alcatel-Lucent, Cisco Systems Inc","Mike Dolan",1692,"pCR","","","This contribution provides evaluation text for Solution 6 in TR 23.708 (AESE).","29","6.5","Architecture Enhancements for Service Exposure (AESE)",12610,"Revised","2015-04-20T16:36:57.370","2015-04-20T16:31:46.290","S2-150939","S2-151141","Rel-13","23.708","","","","","","","","","","",""]
["S2-151242","Solution update for background data transfer","Huawei, HiSilicon, NTT DOCOMO","Mirko Schramm",23396,"pCR","","","This contribution updates the solution description and proposes a new alternative.","29","6.5","Architecture Enhancements for Service Exposure (AESE)",12640,"Revised","2015-04-20T16:36:57.403","2015-04-20T16:31:46.413","S2-150761","S2-151142","Rel-13","23.708","","AESE","","","","","","","","",""]
["S2-151243","First list of Key issues: AAA server knowledge of emergency & Location","Alcatel-Lucent, Alcatel-Lucent ShangHai Bell, Qualcom Inc","Laurent Thiebaut",11066,"pCR","","","Proposes key issues to 23.771 about AAA server knowledge of emergency & about Location","41","6.17","Feasibility study on the Support of Emergency services over WLAN (FS_SEW)",16260,"Revised","2015-04-20T16:36:57.433","2015-04-20T16:31:47.287","S2-150965","S2-151249","Rel-13","23.771","","FS_SEW","","","","","","","","",""]
["S2-151244","Solutions for the location related Key Issue","Alcatel-Lucent, Alcatel-Lucent Shanghai Bell","Nicolas Drevon",16459,"pCR","","","This P-CR provides some background on the existing location procedures during session establishment in Trusted WLAN, which can be used for emergency calls, and proposes two solutions for untrusted WLAN case for inclusion in the technical report.","41","6.17","Feasibility study on the Support of Emergency services over WLAN (FS_SEW)",16430,"Revised","2015-04-20T16:36:57.467","2015-04-20T16:31:48.163","S2-150920","S2-151261","Rel-13","23.771","","FS_SEW","","","","","","","","",""]
["S2-151245","[DRAFT] Reply to LS to 3GPP on IMS Emergency Session over WLAN","SA WG2","Hyunsook Kim",42013,"LS out","","","Response to S2-150705.","41","6.17","Feasibility study on the Support of Emergency services over WLAN (FS_SEW)",16150,"Revised","2015-04-20T16:36:57.497","2015-04-20T16:31:49.037","","S2-151418","","","","","","","","","S2-150705","GSMA Networks Group RILTE","TSG SA, SA WG1"]
["S2-151246","Skeleton and scope for TR 23.771 (FS_SEW)","Alcatel-Lucent, Alcatel-Lucent ShangHai Bell","Laurent Thiebaut",11066,"pCR","","","Skeleton and scope for TR 23.771 (FS_SEW)","41","6.17","Feasibility study on the Support of Emergency services over WLAN (FS_SEW)",16190,"Approved","2015-04-20T16:36:57.527","2015-04-20T16:31:49.050","S2-150962","","Rel-13","23.771","","FS_SEW","","","","","","","","",""]
["S2-151247","General Key Issues: Proposed Assumptions for phase 1","Qualcomm Incorporated, Alcatel Lucent, Alcatel Lucent Shanghai Bell","Haris Zisimopoulos",41602,"pCR","","","This contribution addresses some key issues and concludes that no specific work should be done in Rel. 13 in SEW phase 1 to address these areas.","41","6.17","Feasibility study on the Support of Emergency services over WLAN (FS_SEW)",16210,"Revised","2015-04-20T16:36:57.557","2015-04-20T16:31:49.923","S2-151040","S2-151280","Rel-13","23.771","","FS_SEW","","","","","","","","",""]
["S2-151248","Key Issues on Connectivity Establishment","Qualcomm Incorporated","Haris Zisimopoulos",41602,"pCR","","","The contribution introduces an issue for connectivity establishment related to the ePDG selection.","41","6.17","Feasibility study on the Support of Emergency services over WLAN (FS_SEW)",16240,"Approved","2015-04-20T16:36:57.590","2015-04-20T17:46:40.397","S2-151041","","Rel-13","23.771","","FS_SEW","","","","","","","","",""]
["S2-151249","First list of Key issues: AAA server knowledge of emergency & Location","Alcatel-Lucent, Alcatel-Lucent ShangHai Bell, Qualcom Inc","Laurent Thiebaut",11066,"pCR","","","Proposes key issues to 23.771 about AAA server knowledge of emergency & about Location","41","6.17","Feasibility study on the Support of Emergency services over WLAN (FS_SEW)",16270,"Revised","2015-04-20T16:36:57.620","2015-04-20T16:31:51.843","S2-151243","S2-151281","Rel-13","23.771","","FS_SEW","","","","","","","","",""]
["S2-151250","Key issue: QoS","Alcatel-Lucent, Alcatel-Lucent ShangHai Bell","Laurent Thiebaut",11066,"pCR","","","Proposes a key issue to 23.771 about QoS","41","6.17","Feasibility study on the Support of Emergency services over WLAN (FS_SEW)",16360,"Noted","2015-04-20T16:36:57.637","2015-04-20T16:31:52.687","S2-150966","","","23.771","","FS_SEW","","","","","","","","",""]
["S2-151251","Handling of UE-initiated and NW-initiated NBIFOM modes","Ericsson, Huawei, HiSilicon","Shabnam Sultana",21207,"pCR","","","Provides further details and resolutions to the UE-initiated and NW-initiated NBIFOM modes and procedures","28","6.4","IP Flow Mobility support for S2a and S2b interfaces (NBIFOM)",12010,"Approved","2015-04-20T16:36:57.667","2015-04-20T16:31:53.667","S2-151225","","Rel-13","23.861","","NBIFOM","","","","","","","","",""]
["S2-151252","Removing alternatives from S2a call flows","Apple Inc., Huawei, Hisilicon","Krisztian Kiss",57762,"pCR","","","This contribution proposes to close Editor's Notes 8a, 9, 11a and 16a from the Open Issues list and align section 7.5.4 (S2b flows) with section 7.3.2 (S2a flows).","28","6.4","IP Flow Mobility support for S2a and S2b interfaces (NBIFOM)",12320,"Revised","2015-04-20T16:36:57.713","2015-04-20T16:31:54.637","S2-150996","S2-151393","Rel-13","23.861","","NBIFOM-SA2TR","","","","","","","","",""]
["S2-151253","Removing alternatives from S2b call flows","Apple Inc.","Krisztian Kiss",57762,"pCR","","","This contribution proposes to close Editor's Notes 18 from the Open Issues list and align clause 7.5.4 (S2b flows) with clause 7.3.2 (S2a flows).","28","6.4","IP Flow Mobility support for S2a and S2b interfaces (NBIFOM)",12350,"Approved","2015-04-20T16:36:57.760","2015-04-20T16:31:55.617","S2-150984","","Rel-13","23.861","","NBIFOM-SA2TR","","","","","","","","",""]
["S2-151254","Consideration of PCO vs. APCO for S2b NBIFOM parameters Transport (Open issue 5)","ZTE","Tricci So",44974,"pCR","","","Discusses the considerations for the usage of defining new IKEv2 IE, PCO, vs. extending the existing use of IKE Configuration Payload which is used together with APCO to transport the routing rule over S2b.","28","6.4","IP Flow Mobility support for S2a and S2b interfaces (NBIFOM)",12220,"Approved","2015-04-20T16:36:57.807","2015-04-20T16:31:56.557","S2-150848","","Rel-13","23.861","","NBIFOM","","","","","","","","",""]
["S2-151255","Conclusions for App ID Support","ZTE","Tricci So",44974,"pCR","","","This P-CR proposes the conclusion to defer the support of App ID by NBIFOM in Rel-13","28","6.4","IP Flow Mobility support for S2a and S2b interfaces (NBIFOM)",12240,"Revised","2015-04-20T16:36:57.870","2015-04-20T16:31:57.507","S2-150850","S2-151270","Rel-13","23.861","","NBIFOM","","","","","","","","",""]
["S2-151256","Conclusion for NBIFOM study in Rel-13","ZTE","Tricci So",44974,"pCR","","","This P-CR presents the conclusions of the NBIFOM study in Rel-13.","28","6.4","IP Flow Mobility support for S2a and S2b interfaces (NBIFOM)",12370,"Revised","2015-04-20T16:36:57.917","2015-04-20T16:31:58.410","S2-150862","S2-151394","Rel-13","23.861","","NBIFOM","","","","","","","","",""]
["S2-151257","AESE - Conclusions","Alcatel-Lucent, Intel","Mike Dolan",1692,"pCR","","","This contribution provides conclusions text for clause 8 in TR 23.708 (AESE).","29","6.5","Architecture Enhancements for Service Exposure (AESE)",12700,"Revised","2015-04-20T16:36:57.947","2015-04-20T16:31:59.253","S2-150942","S2-151404","Rel-13","23.708","","","","","","","","","","",""]
["S2-151258","Configuration of extended DRX for connected mode","Ericsson","Shabnam Sultana",21207,"pCR","","","This paper addresses the issue of configuration of the relevant network nodes enabling usage of eDRX in Connected mode","39","6.15","Feasibility study on Extended DRX cycle for Power Consumption Optimization (FS_eDRX)",15730,"Revised","2015-04-20T16:36:57.980","2015-04-20T16:31:59.377","S2-150805","S2-151286","Rel-13","23.770","","FS_eDRX","","","","","","","","",""]
["S2-151259","Extended C-DRX: New connected mode substate in the core network to handle NAS retransmissions and MT SMS (Issues 2 and 3)","Qualcomm Incorporated","Miguel Griot",43100,"pCR","","","Proposes to add a new sub-state for connected mode in the core network called temporarily unavailable, when the RAN has indicated the extended C-DRX has been enabled. When the MME is in this state, it asks RAN to disable eC-DRX when MT SMS or NW initiated procedure arrives.","39","6.15","Feasibility study on Extended DRX cycle for Power Consumption Optimization (FS_eDRX)",15770,"Revised","2015-04-20T16:36:58.027","2015-04-20T16:32:00.253","S2-150978","S2-151287","Rel-13","23.770","","FS_eDRX","","","","","","","","",""]
["S2-151260","Key issues: UE Location Information","T-Mobile USA","Christopher Joul",31136,"pCR","","","Describe the key issues related to the Location of the UE.","41","6.17","Feasibility study on the Support of Emergency services over WLAN (FS_SEW)",16330,"Revised","2015-04-20T16:36:58.057","2015-04-20T16:32:01.110","S2-150964","S2-151282","Rel-13","23.771","","","","","","","","","","",""]
["S2-151261","Solutions for the location related Key Issue","Alcatel-Lucent, Alcatel-Lucent Shanghai Bell","Nicolas Drevon",16459,"pCR","","","This P-CR provides some background on the existing location procedures during session establishment in Trusted WLAN, which can be used for emergency calls, and proposes two solutions for untrusted WLAN case for inclusion in the technical report.","41","6.17","Feasibility study on the Support of Emergency services over WLAN (FS_SEW)",16440,"Revised","2015-04-20T16:36:58.090","2015-04-20T16:32:01.237","S2-151244","S2-151420","Rel-13","23.771","","FS_SEW","","","","","","","","",""]
["S2-151262","Solution: How LRF retrieve location information for s2a","Huawei , Hisilicon","Marco Spini",8356,"pCR","","","This document describes the solution for supporting the retrieval of location information via LRF function for IMS ES when UE is attached to a Trusted WLAN.","41","6.17","Feasibility study on the Support of Emergency services over WLAN (FS_SEW)",16400,"Revised","2015-04-20T16:36:58.120","2015-04-20T16:32:02.123","S2-150864","S2-151283","Rel-13","23.771","","FS_SEW","","","","","","","","",""]
["S2-151263","A solution for ePDG selection","Alcatel-Lucent, Alcatel-Lucent ShangHai Bell","Laurent Thiebaut",11066,"pCR","","","A solution for ePDG selection","41","6.17","Feasibility study on the Support of Emergency services over WLAN (FS_SEW)",16480,"Revised","2015-04-20T16:36:58.150","2015-04-20T16:32:02.997","S2-150967","S2-151421","","23.771","","FS_SEW","","","","","","","","",""]
["S2-151264","MS Info Change Reporting Action at change of Serving Node (MME <--> SGSN): Update of call Flows","Alcatel-Lucent, Alcatel-Lucent Shanghai Bell","Laurent Thiebaut",11066,"CR","","","Summary of change: Align the call flows (of mobility between MME and SGSN) with text in § 5.9.2.1 which mostly consist in 1) if the target SGSN/MME supports location information change reporting, the target SGSN/MME shall include the User Location Information in the Modify Bearer Request, regardless of whether ULI change reporting had been requested in the previous RAT by the PGW 2) If User Location Information change reporting is required and supported in the target RAT, the PGW shall request MS Info Change Reporting Action in the Modify Bearer Response","16","5.2","QoS and PCC Maintenance",11080,"Revised","2015-04-20T16:36:58.213","2015-04-20T16:32:03.870","S2-151208","S2-151416","Rel-12","23.401","12.8.0","CNO_ULI","2860","2","F",null,"","","","",""]
["S2-151265","MS Info Change Reporting Action at change of Serving Node (MME <--> SGSN): Update of call Flows","Alcatel-Lucent, Alcatel-Lucent Shanghai Bell","Laurent Thiebaut",11066,"CR","","","Rel-13 mirror CR: Summary of change: Align the call flows (of mobility between MME and SGSN) with text in § 5.9.2.1 which mostly consist in 1) if the target SGSN/MME supports location information change reporting, the target SGSN/MME shall include the User Location Information in the Modify Bearer Request, regardless of whether ULI change reporting had been requested in the previous RAT by the PGW 2) If User Location Information change reporting is required and supported in the target RAT, the PGW shall request MS Info Change Reporting Action in the Modify Bearer Response","16","5.2","QoS and PCC Maintenance",11120,"Revised","2015-04-20T16:36:58.323","2015-04-20T16:32:04.747","S2-151209","S2-151417","Rel-13","23.401","13.2.0","CNO_ULI","2861","2","A",null,"","","","",""]
["S2-151266","Clarifications for QoS change of default bearer","Huawei, Hisilicon, Ericsson, Alcatel-Lucent","Mirko Schramm",23396,"CR","","","Summary of change: It is proposed to clarify the requirements for the PCRF and the PCEF/BBERF related to the default bearer QoS change due to a PCRF provisioning of the Authorized Default EPS Bearer QoS parameter. In clause 6.1.1.4 (Bearer Binding) it is","16","5.2","QoS and PCC Maintenance",10960,"Agreed","2015-04-20T16:36:58.417","2015-04-20T16:32:05.650","S2-151206","","Rel-12","23.203","12.8.0","SAES, TEI12","0940","5","F",null,"","","","",""]
["S2-151267","Clarifications for QoS change of default bearer","Huawei, Hisilicon, Ericsson, Alcatel-Lucent","Mirko Schramm",23396,"CR","","","Rel-13 mirror CR: Summary of change: It is proposed to clarify the requirements for the PCRF and the PCEF/BBERF related to the default bearer QoS change due to a PCRF provisioning of the Authorized Default EPS Bearer QoS parameter. In clause 6.1.1.4 (Bea","16","5.2","QoS and PCC Maintenance",10990,"Agreed","2015-04-20T16:36:58.510","2015-04-20T16:32:07.287","S2-151207","","Rel-13","23.203","13.3.0","SAES, TEI12","0941","5","A",null,"","","","",""]
["S2-151268","Priority of Default Bearer","Huawei, Hisilicon, Applied Communication Sciences, OEC","Mirko Schramm",23396,"CR","","","Summary of change: It is proposed to extend clause 6.1.1.3 (PCC rule authorization and QoS rule generation) with a general requirement for the PCRF to ensure that the ARP of the default bearer needs to be permanently aligned with the highest ARP used by","16","5.2","QoS and PCC Maintenance",11010,"Agreed","2015-04-20T16:36:58.587","2015-04-20T16:32:09.037","S2-150756","","Rel-12","23.203","12.8.0","eMPS, TEI12","0890","8","F",null,"","","","",""]
["S2-151269","Priority of Default Bearer","Huawei, Hisilicon, Applied Communication Sciences, OEC","Mirko Schramm",23396,"CR","","","Rel-13 mirror CR: Summary of change: It is proposed to extend clause 6.1.1.3 (PCC rule authorization and QoS rule generation) with a general requirement for the PCRF to ensure that the ARP of the default bearer needs to be permanently aligned with the hi","16","5.2","QoS and PCC Maintenance",11030,"Agreed","2015-04-20T16:36:58.683","2015-04-20T16:32:10.767","S2-150757","","Rel-13","23.203","13.3.0","eMPS, TEI12","0905","6","A",null,"","","","",""]
["S2-151270","Conclusions for App ID Support","ZTE","Tricci So",44974,"pCR","","","This P-CR proposes the conclusion to defer the support of App ID by NBIFOM in Rel-13","28","6.4","IP Flow Mobility support for S2a and S2b interfaces (NBIFOM)",12250,"Approved","2015-04-20T16:36:58.790","2015-04-20T16:32:12.420","S2-151255","","Rel-13","23.861","","NBIFOM","","","","","","","","",""]
["S2-151271","Introducing HSS-SCEF and MME/SGSN-SCEF Reference Points","Intel, Huawei, Alcatel-Lucent, Cisco","Puneet Jain",36283,"CR","","","Summary of change: Add description of new reference points S6t (HSS - SCEF) and T6a/T6b (MME/SGSN - SCEF) that were introduced in TS 23.682 as part of monitoring event feature.","30","6.6","Monitoring Enhancements (MONTE)",12820,"Agreed","2015-04-20T16:36:58.837","2015-04-24T04:49:55.390","S2-151213","","Rel-13","23.002","13.1.0","MONTE","0283","2","B",null,"","","","",""]
["S2-151272","Monitoring Feature Description","Intel, Huawei, Alcatel-Lucent","Puneet Jain",36283,"CR","","","Summary of change: High level description for monitoring function and monitoring via HSS, SGSN/MME and PCRF is specified.","30","6.6","Monitoring Enhancements (MONTE)",12850,"Revised","2015-04-20T16:36:58.963","2015-04-20T16:32:14.197","S2-151214","S2-151408","Rel-13","23.682","13.1.0","MONTE","0100","2","B",null,"","","","",""]
["S2-151273","Monitoring via PCRF","Ericsson","Shabnam Sultana",21207,"CR","","","Summary of change: Reporting current user location and communication failure via PCRF as defined in 23.203.","30","6.6","Monitoring Enhancements (MONTE)",12890,"Revised","2015-04-20T16:36:59.040","2015-04-20T16:32:15.073","S2-151215","S2-151409","Rel-13","23.682","13.1.0","MONTE","0093","2","B",null,"","","","",""]
["S2-151274","Support for Monitoring Events","Intel","Puneet Jain",36283,"CR","","","Summary of change: High level description for monitoring function.","30","6.6","Monitoring Enhancements (MONTE)",12930,"Revised","2015-04-20T16:36:59.117","2015-04-20T16:32:15.960","S2-151216","S2-151483","Rel-13","23.060","13.2.0","MONTE","1961","2","B",null,"","","","",""]
["S2-151275","Support for Monitoring Events","Intel, Cisco","Puneet Jain",36283,"CR","","","Summary of change: High level description for monitoring function.","30","6.6","Monitoring Enhancements (MONTE)",12960,"Agreed","2015-04-20T16:36:59.213","2015-04-20T16:32:16.837","S2-151217","","Rel-13","23.401","13.2.0","MONTE","2851","2","B",null,"","","","",""]
["S2-151276","Introduction of monitoring procedures","Huawei, HiSilicon, Intel, Alcatel-Lucent","Frank Mademann",6821,"CR","","","Summary of change: The procedures for supporting monitoring configuration via MME/SGSN and via HSS are introduced.","30","6.6","Monitoring Enhancements (MONTE)",13000,"Revised","2015-04-20T16:36:59.307","2015-04-20T16:32:17.707","S2-151218","S2-151736","Rel-13","23.682","13.1.0","MONTE","0097","2","B",null,"","","","",""]
["S2-151277","Cleanup of the Loss of an Access from a PDN Connection","Huawei, HiSilicon, China Telecom","Runze Zhou",60945,"pCR","","","This contribution cleans up the Editor's notes in the section of loss of an access from a PDN connection.","28","6.4","IP Flow Mobility support for S2a and S2b interfaces (NBIFOM)",12130,"Revised","2015-04-20T16:36:59.383","2015-04-20T16:32:18.597","S2-151227","S2-151391","Rel-13","23.861","","NBIFOM","","","","","","","","",""]
["S2-151278","Conclusions for indication of 3GPP access loss in SCM","LG Electronics","Hyunsook Kim",42013,"pCR","","","This P-CR proposes the conclusions for 3GPP access loss indication in Single-connection mode.","28","6.4","IP Flow Mobility support for S2a and S2b interfaces (NBIFOM)",12170,"Approved","2015-04-20T16:36:59.417","2015-04-20T16:32:19.517","S2-151228","","Rel-13","23.861","","NBIFOM","","","","","","","","",""]
["S2-151279","Conclusions for NBIFOM Open Issues 6 and 7","ZTE","Tricci So",44974,"pCR","","","This P-CR proposes the conclusions oftwo open issues about the support for Inter-MME/SGSN IP flow mobility and PMIP to be deferred from the NBIFOM Rel-13 study.","28","6.4","IP Flow Mobility support for S2a and S2b interfaces (NBIFOM)",12280,"Revised","2015-04-20T16:36:59.447","2015-04-20T16:32:20.390","S2-151229","S2-151392","Rel-13","23.861","","NBIFOM","","","","","","","","",""]
["S2-151280","General Key Issues: Proposed Assumptions for phase 1","Qualcomm Incorporated, Alcatel Lucent, Alcatel Lucent Shanghai Bell","Haris Zisimopoulos",41602,"pCR","","","This contribution addresses some key issues and concludes that no specific work should be done in Rel. 13 in SEW phase 1 to address these areas.","41","6.17","Feasibility study on the Support of Emergency services over WLAN (FS_SEW)",16220,"Approved","2015-04-20T16:36:59.493","2015-04-20T16:32:21.280","S2-151247","","Rel-13","23.771","","FS_SEW","","","","","","","","",""]
["S2-151281","First list of Key issues: AAA server knowledge of emergency & Location","Alcatel-Lucent, Alcatel-Lucent ShangHai Bell, Qualcom Inc","Laurent Thiebaut",11066,"pCR","","","Proposes key issues to 23.771 about AAA server knowledge of emergency & about Location","41","6.17","Feasibility study on the Support of Emergency services over WLAN (FS_SEW)",16280,"Revised","2015-04-20T16:36:59.523","2015-04-20T16:32:22.200","S2-151249","S2-151419","Rel-13","23.771","","FS_SEW","","","","","","","","",""]
["S2-151282","Key issues: UE Location Information","T-Mobile USA","Christopher Joul",31136,"pCR","","","Describe the key issues related to the Location of the UE.","41","6.17","Feasibility study on the Support of Emergency services over WLAN (FS_SEW)",16340,"Approved","2015-04-20T16:36:59.557","2015-04-20T16:32:23.200","S2-151260","","Rel-13","23.771","","","","","","","","","","",""]
["S2-151283","Solution: How LRF retrieve location information for s2a","Huawei , Hisilicon","Marco Spini",8356,"pCR","","","This document describes the solution for supporting the retrieval of location information via LRF function for IMS ES when UE is attached to a Trusted WLAN.","41","6.17","Feasibility study on the Support of Emergency services over WLAN (FS_SEW)",16410,"Approved","2015-04-20T16:36:59.603","2015-04-20T16:32:23.340","S2-151262","","Rel-13","23.771","","FS_SEW","","","","","","","","",""]
["S2-151284","eDRX - Idle Mode Issue 2: Solution A","Alcatel-Lucent, Qualcomm Incorporated","Mike Dolan",1692,"pCR","","","This contribution provides text for Solution A to Idle Mode Issue 2 in TR 23.770 (eDRX).","39","6.15","Feasibility study on Extended DRX cycle for Power Consumption Optimization (FS_eDRX)",15610,"Revised","2015-04-20T16:36:59.633","2015-04-20T16:32:24.277","S2-151232","S2-151400","Rel-13","23.770","","","","","","","","","","",""]
["S2-151285","Extended I-DRX and PSM coexistence","Qualcomm Incorporated","Miguel Griot",43100,"pCR","","","Proposes that it is SGSN/MME decision whether to enable only one of extended I-DRX or PSM, or use both.","39","6.15","Feasibility study on Extended DRX cycle for Power Consumption Optimization (FS_eDRX)",15700,"Approved","2015-04-20T16:36:59.663","2015-04-20T16:32:24.400","S2-151234","","Rel-13","23.770","","FS_eDRX","","","","","","","","",""]
["S2-151286","Configuration of extended DRX for connected mode","Ericsson","Shabnam Sultana",21207,"pCR","","","This paper addresses the issue of configuration of the relevant network nodes enabling usage of eDRX in Connected mode","39","6.15","Feasibility study on Extended DRX cycle for Power Consumption Optimization (FS_eDRX)",15740,"Approved","2015-04-20T16:36:59.697","2015-04-20T16:32:25.260","S2-151258","","Rel-13","23.770","","FS_eDRX","","","","","","","","",""]
["S2-151287","Extended C-DRX: New connected mode substate in the core network to handle NAS retransmissions and MT SMS (Issues 2 and 3)","Qualcomm Incorporated","Miguel Griot",43100,"pCR","","","Proposes to add a new sub-state for connected mode in the core network called temporarily unavailable, when the RAN has indicated the extended C-DRX has been enabled. When the MME is in this state, it asks RAN to disable eC-DRX when MT SMS or NW initiated procedure arrives.","39","6.15","Feasibility study on Extended DRX cycle for Power Consumption Optimization (FS_eDRX)",15780,"Approved","2015-04-20T16:36:59.727","2015-04-20T16:32:26.147","S2-151259","","Rel-13","23.770","","FS_eDRX","","","","","","","","",""]
["S2-151288","[DRAFT] LS on RAN assumptions from SA WG2 for FS_eDRX","Qualcomm Incorporated","Miguel Griot",43100,"LS out","","","Provides information to GERAN/RAN WG2 on the assumptions on RAN behaviour for FS_eDRX and requests corroboration.","39","6.15","Feasibility study on Extended DRX cycle for Power Consumption Optimization (FS_eDRX)",15810,"Revised","2015-04-20T16:36:59.773","2015-04-20T16:32:27.067","S2-150980","S2-151430","Rel-13","","","","","","","",null,"TSG GERAN, RAN WG2"]
["S2-151289","Reserved for Frank's parallel sessions","-","Maurice Pope",648,"other","","","-","55","99","Reserved and Withdrawn documents",17020,"Withdrawn","2015-04-20T16:36:59.807",null,"","","","","","","","","","","","","","",""]
["S2-151290","Reserved for Frank's parallel sessions","-","Maurice Pope",648,"other","","","-","55","99","Reserved and Withdrawn documents",17030,"Withdrawn","2015-04-20T16:36:59.837",null,"","","","","","","","","","","","","","",""]
["S2-151291","Reserved for Frank's parallel sessions","-","Maurice Pope",648,"other","","","-","55","99","Reserved and Withdrawn documents",17040,"Withdrawn","2015-04-20T16:36:59.867",null,"","","","","","","","","","","","","","",""]
["S2-151292","Reserved for Frank's parallel sessions","-","Maurice Pope",648,"other","","","-","55","99","Reserved and Withdrawn documents",17050,"Withdrawn","2015-04-20T16:36:59.913",null,"","","","","","","","","","","","","","",""]
["S2-151293","Reserved for Frank's parallel sessions","-","Maurice Pope",648,"other","","","-","55","99","Reserved and Withdrawn documents",17060,"Withdrawn","2015-04-20T16:36:59.947",null,"","","","","","","","","","","","","","",""]
["S2-151294","Reserved for Frank's parallel sessions","-","Maurice Pope",648,"other","","","-","55","99","Reserved and Withdrawn documents",17070,"Withdrawn","2015-04-20T16:36:59.993",null,"","","","","","","","","","","","","","",""]
["S2-151295","Reserved for Frank's parallel sessions","-","Maurice Pope",648,"other","","","-","55","99","Reserved and Withdrawn documents",17080,"Withdrawn","2015-04-20T16:37:00.023",null,"","","","","","","","","","","","","","",""]
["S2-151296","Reserved for Frank's parallel sessions","-","Maurice Pope",648,"other","","","-","55","99","Reserved and Withdrawn documents",17090,"Withdrawn","2015-04-20T16:37:00.053",null,"","","","","","","","","","","","","","",""]
["S2-151297","Reserved for Frank's parallel sessions","-","Maurice Pope",648,"other","","","-","55","99","Reserved and Withdrawn documents",17100,"Withdrawn","2015-04-20T16:37:00.100",null,"","","","","","","","","","","","","","",""]
["S2-151298","Reserved for Frank's parallel sessions","-","Maurice Pope",648,"other","","","-","55","99","Reserved and Withdrawn documents",17110,"Withdrawn","2015-04-20T16:37:00.133",null,"","","","","","","","","","","","","","",""]
["S2-151299","Reserved for Frank's parallel sessions","-","Maurice Pope",648,"other","","","-","55","99","Reserved and Withdrawn documents",17120,"Withdrawn","2015-04-20T16:37:00.163",null,"","","","","","","","","","","","","","",""]
["S2-151300","Reserved for Frank's parallel sessions","-","Maurice Pope",648,"other","","","-","55","99","Reserved and Withdrawn documents",17130,"Withdrawn","2015-04-20T16:45:38.947",null,"","","","","","","","","","","","","","",""]
["S2-151301","Reserved for Frank's parallel sessions","-","Maurice Pope",648,"other","","","-","55","99","Reserved and Withdrawn documents",17140,"Withdrawn","2015-04-20T16:45:38.947",null,"","","","","","","","","","","","","","",""]
["S2-151302","Reserved for Frank's parallel sessions","-","Maurice Pope",648,"other","","","-","55","99","Reserved and Withdrawn documents",17150,"Withdrawn","2015-04-20T16:45:38.960",null,"","","","","","","","","","","","","","",""]
["S2-151303","Reserved for Frank's parallel sessions","-","Maurice Pope",648,"other","","","-","55","99","Reserved and Withdrawn documents",17160,"Withdrawn","2015-04-20T16:45:38.977",null,"","","","","","","","","","","","","","",""]
["S2-151304","Reserved for Frank's parallel sessions","-","Maurice Pope",648,"other","","","-","55","99","Reserved and Withdrawn documents",17170,"Withdrawn","2015-04-20T16:45:38.993",null,"","","","","","","","","","","","","","",""]
["S2-151305","Reserved for Frank's parallel sessions","-","Maurice Pope",648,"other","","","-","55","99","Reserved and Withdrawn documents",17180,"Withdrawn","2015-04-20T16:45:38.993",null,"","","","","","","","","","","","","","",""]
["S2-151306","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.","18","5.4","IMS-Related Maintenance",11200,"Noted","2015-04-20T16:45:39.007","2015-04-20T16:44:18.230","","","Rel-12","","","","","","","",null,null,null,"S4-150401"]
["S2-151307","Draft Agenda for SA WG2#108","SA WG2 Chairman","Erik Guttman",18782,"agenda","","","The meeting agenda.","2","2","Approval of the agenda",10010,"Approved","2015-04-20T16:45:39.023","2015-04-20T16:44:18.260","S2-150699","","","","","","","","","","","","","",""]
["S2-151308","[DRAFT] Reply LS on Study on improved end-to-end QoS handling","SA WG2","Shabnam Sultana",21207,"LS out","","","LS reply to LS from SA WG4 on improved end to end QoS handling","7","4.1","Common issues and Incoming LSs",10110,"Revised","2015-04-20T16:45:39.040","2015-04-20T16:44:18.277","S2-150751","S2-151425","Rel-13","","","","","","","","S2-150740","SA WG4","CT WG3"]
["S2-151309","Update to the SID on Feasibility study on the Support of Emergency services over WLAN","Alcatel-Lucent, Alcatel-Lucent ShangHai Bell","Laurent Thiebaut",11066,"WID","","","Revised WID TR presented for approval at end of phase 2","50","7.1","New and Revised Work Items, Cover sheets for completed work items",16620,"Revised","2015-04-20T16:45:39.070","2015-04-20T16:44:18.293","S2-150968","S2-151422","Rel-13","","","","","","","","","","","",""]
["S2-151310","Additional SA WG2 #110ah Meeting Proposal","SA WG2 Chairman","Erik Guttman",18782,"other","","","This proposal would add a meeting to Q3 2015 to complete exceptions expected at TSG SA#68.","52","7.3","Planning future meetings",16650,"Available","2015-04-20T16:45:39.087","2015-04-20T16:44:18.307","S2-151094","","","","","","","","","","","","","",""]
["S2-151311","Draft Response to Reply LS on Security Framework for Cellular IoT","SA WG2","Chris Pudney",1122,"LS out","","","Draft response to SA WG3 LS in S2-150738 = S3-151198","7","4.1","Common issues and Incoming LSs",10210,"Revised","2015-04-20T16:45:39.117","2015-04-20T16:44:18.323","S2-151077","S2-151382","Rel-13","","","","","","","","S2-150738","SA WG3","GERAN WG2, TSG GERAN, SA WG1, TSG SA"]
["S2-151312","Fixes to Public Safety Discovery procedures","Intel","Saso Stojanovski",24932,"pCR","","","Proposes fixes to the Public Safety Discovery procedures","21","6.1","Release 13 Maintenance",13890,"Revised","2015-04-20T16:45:39.133","2015-04-20T16:44:18.357","S2-151061","S2-151375","Rel-13","23.713","","eProSe-Ext-SA2TR","","","","","","","","",""]
["S2-151313","Use of Group Info/Connectivity Info in UE2NW Relay discovery","Samsung","Youngkyo Baek",46395,"pCR","","","This contribution proposes to solve an unclarity w.r.t. the usage of 'Group Info' and 'Connectivity info' in UE2NW relay discovery.","21","6.1","Release 13 Maintenance",13920,"Approved","2015-04-20T16:45:39.147","2015-04-20T16:44:19.383","S2-151021","","Rel-13","23.713","","eProSe-Ext-SA2TR","","","","","","","","",""]
["S2-151314","Updates to Annex on PC5 interface","Ericsson","Shabnam Sultana",21207,"pCR","","","Updates to Annex on PC5 to reflect correct explanation & RAN WG1 feedback","21","6.1","Release 13 Maintenance",13940,"Approved","2015-04-20T16:45:39.180","2015-04-20T16:44:20.353","S2-150773","","Rel-13","23.713","","eProSe-Ext-SA2TR","","","","","","","","",""]
["S2-151315","IOPS network configuration/establishment","General Dynamics UK Ltd.","Maurice Pope",648,"pCR","","","This contribution proposes text to resolve the Editor's Note relating to dynamic establishment of IOPS networks","40","6.16","Feasibility study on IOPS (FS_IOPS_St2)",15850,"Approved","2015-04-20T16:45:39.197","2015-04-20T16:44:21.240","S2-150762","","Rel-13","23.797","","FS_IOPS_St2","","","","","","","","",""]
["S2-151316","PLMN Selection","Ericsson","Shabnam Sultana",21207,"pCR","","","Propose a change of how PLMN selection is done by the Public Safety user","40","6.16","Feasibility study on IOPS (FS_IOPS_St2)",15880,"Approved","2015-04-20T16:45:39.227","2015-04-20T16:44:22.113","S2-150774","","Rel-13","23.797","","FS_IOPS_St2","","","","","","","","",""]
["S2-151317","way forward on some unsolved FFS issues","Samsung","Youngkyo Baek",46395,"pCR","","","This contribution is to solve some remaining FFS issues.","40","6.16","Feasibility study on IOPS (FS_IOPS_St2)",15910,"Revised","2015-04-20T16:45:39.240","2015-04-20T16:44:22.987","S2-151026","S2-151377","Rel-13","23.797","","FS_IOPS_St2","","","","","","","","",""]
["S2-151318","[DRAFT] LS on proposed method of restricting access to IOPS cells","SA WG2","Philip Young",27298,"LS out","","","To: SA WG1","40","6.16","Feasibility study on IOPS (FS_IOPS_St2)",15960,"Revised","2015-04-20T16:45:39.273","2015-04-20T16:44:23.957","","S2-151379","","","","","","","","",null,"SA WG1","-"]
["S2-151319","Restriction of UEs not allowed in IOPS PLMN","Ericsson","Shabnam Sultana",21207,"pCR","","","define how to bar unauthorised UEs for IOPS","40","6.16","Feasibility study on IOPS (FS_IOPS_St2)",15940,"Revised","2015-04-20T16:45:39.287","2015-04-20T16:44:23.970","S2-150776","S2-151378","Rel-13","23.797","","FS_IOPS_St2","","","","","","","","",""]
["S2-151320","Way Forward on service continuity","T-Mobile Austria","Michele Zarri",20505,"pCR","","","Capture in TR 23.713 that service cont. is not supported in ProSe/EPS layer in this release","26","6.2","Mission Critical Push-to-Talk over LTE (MCPTT)",11640,"Revised","2015-04-20T16:45:39.320","2015-04-20T16:44:24.890","","S2-151333","","23.713","","eProSe-Ext-SA2","","","","","","","","",""]
["S2-151321","Introduce the Dedicated Core Network (DECOR) feature","NTT DOCOMO, Huawei","Irfan Ali",50390,"CR","","","Summary of change: Introduce the DECOR feature based on conclusions of TR 23.707","27","6.3","Dedicated Core Networks (DECOR)",11700,"Revised","2015-04-20T16:45:39.337","2015-04-20T16:44:25.920","S2-150927","S2-151371","Rel-13","23.401","13.2.0","DECOR","2837","4","B",null,"","","","",""]
["S2-151322","Update of MME load balancing for Dedicated Core Networks","Huawei, HiSilicon, NTT DOCOMO","Frank Mademann",6821,"CR","","","Summary of change: All functions describing connection of multiple CN nodes to a RAN node are enhanced to clarify the case where those CN nodes belong to different CNs, i.e. where DCOR is deployed","27","6.3","Dedicated Core Networks (DECOR)",11770,"Agreed","2015-04-20T16:45:39.430","2015-04-20T16:44:26.857","S2-150915","","Rel-13","23.236","12.0.0","DECOR","0051","3","B",null,"","","","",""]
["S2-151323","Introduce the Dedicated Core Network (DECOR) feature","NTT DOCOMO, Huawei","Irfan Ali",50390,"CR","","","Summary of change: Introduce the decor feature based on conclusions of TR 23.707.","27","6.3","Dedicated Core Networks (DECOR)",11800,"Revised","2015-04-20T16:45:39.523","2015-04-20T16:44:27.823","S2-150928","S2-151372","Rel-13","23.060","13.2.0","DECOR","1953","3","B",null,"","","","",""]
["S2-151324","Mandatory use of Geographical Areas","Ericsson, Sprint, Qualcomm Incorporated, LG Electronics, U.S. Department of Commerce, Home Office, Alcatel-Lucent","Shabnam Sultana",21207,"CR","","","Summary of change: Geographical Area made mandatory in the Radio parameters for when the UE is 'not served by E-UTRAN' provisioning for ProSe Direct Discovery and ProSe Direct Communication.","15","5.1","3GPP Packet Access Maintenance",10610,"Agreed","2015-04-20T16:45:39.600","2015-04-20T16:44:28.807","S2-150750","","Rel-12","23.303","12.4.0","ProSe","0158","1","F",null,"","","","",""]
["S2-151325","Support for ProSe in multicarrier across PLMNs","Qualcomm Incorporated, Ericsson","Haris Zisimopoulos",41602,"CR","","","Summary of change: - Clarifies the multicarrier support across PLMNs - Adds the term 'connected to a cell' for procedures that apply connected mode - Adds reference in TS 36.304","15","5.1","3GPP Packet Access Maintenance",10660,"Agreed","2015-04-20T16:45:39.693","2015-04-20T16:44:29.773","S2-151139","","Rel-12","23.303","12.4.0","ProSe","0151","3","F",null,"","","","",""]
["S2-151326","Reply LS on addition of proximity services group identifier","SA WG2","Haris Zisimopoulos",41602,"LS out","","","To: CT WG1 CC: RAN WG2","15","5.1","3GPP Packet Access Maintenance",10700,"Approved","2015-04-20T16:45:39.773","2015-04-20T16:44:30.663","S2-150909","","Rel-12","","","","","","","","S2-150707","CT WG1","RAN WG2"]
["S2-151327","Clarification of ProSe Layer 2 Group ID provisioning","Samsung","Youngkyo Baek",46395,"CR","","","Summary of change: the ProSe Layer 2 Group ID is clarified it can be a configurable parameter.","15","5.1","3GPP Packet Access Maintenance",10770,"Revised","2015-04-20T16:45:39.803","2015-04-20T16:44:30.773","S2-151023","S2-151373","Rel-12","23.303","12.4.0","TEI12, ProSe","0160","1","F",null,"","","","",""]
["S2-151328","Conclusion Supplements on ProSe Restricted Discovery","Huawei, HiSilicon","Runze Zhou",60945,"pCR","","","In this contribution, it is proposed to add the solution of on demand announcement into conclusion part of ProSe restricted discovery.","21","6.1","Release 13 Maintenance",14100,"Approved","2015-04-20T16:45:39.880","2015-04-20T16:44:32.427","S2-150882","","Rel-13","23.713","","eProSe-Ext-SA2TR","","","","","","","","",""]
["S2-151329","ProSe Discovery UE ID update","CATT","Juan Zhang",38523,"pCR","","","This contribution is proposed to enhance the ProSe function triggered ProSe Direct Service revocation procedure to support ProSe Discovery UE ID update.","21","6.1","Release 13 Maintenance",14130,"Approved","2015-04-20T16:45:39.913","2015-04-20T16:44:33.317","S2-150836","","Rel-13","23.713","","eProSe-Ext-SA2TR","","","","","","","","",""]
["S2-151330","Correction to Monitor request procedure with application controlled extension","Samsung","Youngkyo Baek",46395,"pCR","","","This contribution corrects an error in the monitor request procedure agreed at SA WG2#107.","21","6.1","Release 13 Maintenance",14150,"Revised","2015-04-20T16:45:39.943","2015-04-20T16:44:34.220","S2-151017","S2-151374","Rel-13","23.713","","eProSe-Ext-SA2TR","","","","","","","","",""]
["S2-151331","ProSe Open Discovery Enhancement for Dynamic Metadata","Huawei, Hisilicon, Qualcomm Incorporated","Runze Zhou",60945,"pCR","","","This contribution proposes a solution to enable a UE to update the metadata dynamically. The solution is enhanced based on the existing Open Discovery solution.","21","6.1","Release 13 Maintenance",14330,"Approved","2015-04-20T16:45:39.960","2015-04-20T16:44:35.093","S2-150828","","Rel-13","23.713","","eProSe-Ext-SA2TR","","","","","","","","",""]
["S2-151332","Metadata upload for Restricted Discovery","Qualcomm Incorporated","Hong Cheng",25668,"pCR","","","This contribution adds details on how to enable the ProSe Function to obtain the metadata that is currently specified to be returned (optionally) in the Match Report procedures. These are specified separately for Open Discovery and Restricted discovery.","21","6.1","Release 13 Maintenance",14350,"Revised","2015-04-20T16:45:39.990","2015-04-20T16:44:35.983","S2-150924","S2-151342","Rel-13","23.713","","eProSe-Ext-SA2TR","","","","","","","","",""]
["S2-151333","Way Forward on service continuity","T-Mobile Austria","Michele Zarri",20505,"pCR","","","Capture in TR 23.713 that service cont. is not supported in ProSe/EPS layer in this release","26","6.2","Mission Critical Push-to-Talk over LTE (MCPTT)",11650,"Noted","2015-04-20T16:45:40.020","2015-04-20T16:44:36.840","S2-151320","","","23.713","","eProSe-Ext-SA2","","","","","","","","",""]
["S2-151334","Correction for consistency description","Samsung","Youngkyo Baek",46395,"pCR","","","the contribution is proposed to align description for consistency and clean up the ambiguity.","40","6.16","Feasibility study on IOPS (FS_IOPS_St2)",16110,"Revised","2015-04-20T16:45:40.053","2015-04-20T16:44:37.747","S2-151024","S2-151341","Rel-13","23.797","","FS_IOPS_St2","","","","","","","","",""]
["S2-151335","Update of the solution using IP multicast in the UE-to-NW Relay","Nokia Networks","György Wolfner",31366,"pCR","","","This paper updates the solution using IP Multicast in the UE-to-Network Relay in section 7.2.2.4 to make the description of the solution complete and clarifies the impacts of the solution on existing network elements and interfaces.","21","6.1","Release 13 Maintenance",14240,"Approved","2015-04-20T16:45:40.067","2015-04-20T16:44:38.620","S2-150990","","Rel-13","23.713","","","","","","","","","","",""]
["S2-151336","Corrections in ProSe UE-NW Relay discovery","Nokia Networks, Qualcomm Incorporated","György Wolfner",31366,"pCR","","","This paper investigates the usefulness of providing the 'APN information' and the PLMN ID from the Relay during the ProSe UE-NW Relay discovery and proposes certain mechanisms to do that.","21","6.1","Release 13 Maintenance",14260,"Revised","2015-04-20T16:45:40.100","2015-04-20T16:44:38.760","S2-150998","S2-151376","Rel-13","23.713","","","","","","","","","","",""]
["S2-151337","Resolve FFS for UE-to-Network Relay Discovery","HTC","Ellen C. Liao",54895,"pCR","","","This paper proposes to clarify the required parameters used for UE to Network relay discovery.","21","6.1","Release 13 Maintenance",14300,"Approved","2015-04-20T16:45:40.130","2015-04-20T16:44:38.887","S2-151032","","Rel-13","23.713","","eProSe-Ext-SA2TR","","","","","","","","",""]
["S2-151338","Clarification of applicable UE mobility procedures","General Dynamics UK Ltd.","Philip Young",27298,"pCR","","","This contribution proposes text to clarify the applicable UE mobility procedures in the full range of possible cell transition scenarios","40","6.16","Feasibility study on IOPS (FS_IOPS_St2)",16020,"Revised","2015-04-20T16:45:40.177","2015-04-20T16:44:39.790","S2-150763","S2-151380","Rel-13","23.797","","FS_IOPS_St2","","","","","","","","",""]
["S2-151339","Support of public safety services over an IOPS network","General Dynamics UK Ltd.","Philip Young",27298,"pCR","","","This contribution proposes text to clarify the manner in which public safety services should be supported over an IOPS network and proposes an LS to SA WG3 and SA WG6","40","6.16","Feasibility study on IOPS (FS_IOPS_St2)",16050,"Approved","2015-04-20T16:45:40.223","2015-04-20T16:44:40.663","S2-150764","","Rel-13","23.797","","FS_IOPS_St2","","","","","","","","",""]
["S2-151340","[DRAFT] LS on support of public safety services over an IOPS network","General Dynamics UK Limited","Philip Young",27298,"LS out","","","LS to SA WG6 and SA WG3 informing them of SA WG2 decisions regarding the manner in which public safety services will be supported over IOPS networks","40","6.16","Feasibility study on IOPS (FS_IOPS_St2)",16070,"Revised","2015-04-20T16:45:40.240","2015-04-20T16:44:41.553","S2-150765","S2-151381","Rel-13","","","","","","","",null,"SA WG6, SA WG3","-"]
["S2-151341","Correction for consistency description","Samsung","Youngkyo Baek",46395,"pCR","","","the contribution is proposed to align description for consistency and clean up the ambiguity.","40","6.16","Feasibility study on IOPS (FS_IOPS_St2)",16120,"Approved","2015-04-20T16:45:40.270","2015-04-20T16:44:41.567","S2-151334","","Rel-13","23.797","","FS_IOPS_St2","","","","","","","","",""]
["S2-151342","Metadata upload for Restricted Discovery","Qualcomm Incorporated","Hong Cheng",25668,"pCR","","","This contribution adds details on how to enable the ProSe Function to obtain the metadata that is currently specified to be returned (optionally) in the Match Report procedures. These are specified separately for Open Discovery and Restricted discovery.","21","6.1","Release 13 Maintenance",14360,"Approved","2015-04-20T16:45:40.303","2015-04-20T16:44:42.427","S2-151332","","Rel-13","23.713","","eProSe-Ext-SA2TR","","","","","","","","",""]
["S2-151343","New UE-initiated update procedures for Open Direct Discovery","Qualcomm Incorporated","Hong Cheng",25668,"pCR","","","This contribution proposes extending procedures over PC3 to enhance open discovery.","21","6.1","Release 13 Maintenance",14380,"Approved","2015-04-20T16:45:40.317","2015-04-20T16:44:43.317","S2-150922","","Rel-13","23.713","","eProSe-Ext-SA2TR","","","","","","","","",""]
["S2-151344","Proximity estimation","Qualcomm Incorporated","Hong Cheng",25668,"pCR","","","Discusses solutions for proximity estimation.","21","6.1","Release 13 Maintenance",14420,"Approved","2015-04-20T16:45:40.350","2015-04-20T16:44:44.237","S2-150926","","Rel-13","23.713","","eProSe-Ext-SA2TR","","","","","","","","",""]
["S2-151345","Coarse proximity estimation","Deutsche Telekom","Michele Zarri",20505,"pCR","","","This contribution proposes to specify a method for the monitoring UE to obtain a coarse estimation of the proximity to the announcing UE. The announcing UE assists the monitoring UE by indicating the transmit power used.","21","6.1","Release 13 Maintenance",14440,"Approved","2015-04-20T16:45:40.380","2015-04-20T16:44:45.127","S2-151028","","Rel-13","23.713","","eProSe-Ext-SA2TR","","","","","","","","",""]
["S2-151346","Reserved for Ivano's parallel sessions","-","Maurice Pope",648,"other","","","-","55","99","Reserved and Withdrawn documents",16940,"Withdrawn","2015-04-20T16:45:40.410",null,"","","","","","","","","","","","","","",""]
["S2-151347","Reserved for Ivano's parallel sessions","-","Maurice Pope",648,"other","","","-","55","99","Reserved and Withdrawn documents",16950,"Withdrawn","2015-04-20T16:45:40.443",null,"","","","","","","","","","","","","","",""]
["S2-151348","Reserved for Ivano's parallel sessions","-","Maurice Pope",648,"other","","","-","55","99","Reserved and Withdrawn documents",16960,"Withdrawn","2015-04-20T16:45:40.457",null,"","","","","","","","","","","","","","",""]
["S2-151349","Reserved for Ivano's parallel sessions","-","Maurice Pope",648,"other","","","-","55","99","Reserved and Withdrawn documents",16970,"Withdrawn","2015-04-20T16:45:40.490",null,"","","","","","","","","","","","","","",""]
["S2-151350","Reserved for Ivano's parallel sessions","-","Maurice Pope",648,"other","","","-","55","99","Reserved and Withdrawn documents",16980,"Withdrawn","2015-04-20T16:45:40.507",null,"","","","","","","","","","","","","","",""]
["S2-151351","Reserved for Ivano's parallel sessions","-","Maurice Pope",648,"other","","","-","55","99","Reserved and Withdrawn documents",16990,"Withdrawn","2015-04-20T16:45:40.537",null,"","","","","","","","","","","","","","",""]
["S2-151352","Reserved for Ivano's parallel sessions","-","Maurice Pope",648,"other","","","-","55","99","Reserved and Withdrawn documents",17000,"Withdrawn","2015-04-20T16:45:40.553",null,"","","","","","","","","","","","","","",""]
["S2-151353","[DRAFT] Status of UE-UE relays in SA WG2","SA WG2","Haris Zisimopoulos",41602,"LS out","","","To: SA WG6","21","6.1","Release 13 Maintenance",14490,"Noted","2015-04-20T16:45:40.583","2015-04-20T16:44:46.013","","","","","","","","","","",null,"-","-"]
["S2-151354","Draft Response to Reply LS on paging for MTC","VODAFONE Group Plc","Chris Pudney",1122,"LS out","","","Draft Response to Reply LS on paging for MTC (GP-150312/S2-150716; R1-150924/S2-150720 )","7","4.1","Common issues and Incoming LSs",10260,"Revised","2015-04-20T16:45:40.600","2015-04-20T16:44:46.047","S2-151091","S2-151370","Rel-13","","","","","","","","S2-150716","RAN WG1, RAN WG2, RAN WG3, GERAN WG2","TSG GERAN"]
["S2-151355","Reserved for Puneet's parallel sessions","-","Maurice Pope",648,"other","","","-","55","99","Reserved and Withdrawn documents",16710,"Withdrawn","2015-04-20T16:45:40.647",null,"","","","","","","","","","","","","","",""]
["S2-151356","Reserved for Puneet's parallel sessions","-","Maurice Pope",648,"other","","","-","55","99","Reserved and Withdrawn documents",16720,"Withdrawn","2015-04-20T16:45:40.660",null,"","","","","","","","","","","","","","",""]
["S2-151357","Reserved for Puneet's parallel sessions","-","Maurice Pope",648,"other","","","-","55","99","Reserved and Withdrawn documents",16730,"Withdrawn","2015-04-20T16:45:40.693",null,"","","","","","","","","","","","","","",""]
["S2-151358","Reserved for Puneet's parallel sessions","-","Maurice Pope",648,"other","","","-","55","99","Reserved and Withdrawn documents",16740,"Withdrawn","2015-04-20T16:45:40.707",null,"","","","","","","","","","","","","","",""]
["S2-151359","Reserved for Puneet's parallel sessions","-","Maurice Pope",648,"other","","","-","55","99","Reserved and Withdrawn documents",16750,"Withdrawn","2015-04-20T16:45:40.740",null,"","","","","","","","","","","","","","",""]
["S2-151360","Reserved for Puneet's parallel sessions","-","Maurice Pope",648,"other","","","-","55","99","Reserved and Withdrawn documents",16760,"Withdrawn","2015-04-20T16:45:40.770",null,"","","","","","","","","","","","","","",""]
["S2-151361","Reserved for Puneet's parallel sessions","-","Maurice Pope",648,"other","","","-","55","99","Reserved and Withdrawn documents",16770,"Withdrawn","2015-04-20T16:45:40.787",null,"","","","","","","","","","","","","","",""]
["S2-151362","Reserved for Puneet's parallel sessions","-","Maurice Pope",648,"other","","","-","55","99","Reserved and Withdrawn documents",16780,"Withdrawn","2015-04-20T16:45:40.817",null,"","","","","","","","","","","","","","",""]
["S2-151363","Reserved for Puneet's parallel sessions","-","Maurice Pope",648,"other","","","-","55","99","Reserved and Withdrawn documents",16790,"Withdrawn","2015-04-20T16:45:40.847",null,"","","","","","","","","","","","","","",""]
["S2-151364","Reserved for Puneet's parallel sessions","-","Maurice Pope",648,"other","","","-","55","99","Reserved and Withdrawn documents",16800,"Withdrawn","2015-04-20T16:45:40.880",null,"","","","","","","","","","","","","","",""]
["S2-151365","Reserved for Puneet's parallel sessions","-","Maurice Pope",648,"other","","","-","55","99","Reserved and Withdrawn documents",16810,"Withdrawn","2015-04-20T16:45:40.897",null,"","","","","","","","","","","","","","",""]
["S2-151366","Reserved for Puneet's parallel sessions","-","Maurice Pope",648,"other","","","-","55","99","Reserved and Withdrawn documents",16820,"Withdrawn","2015-04-20T16:45:40.927",null,"","","","","","","","","","","","","","",""]
["S2-151367","Reserved for Puneet's parallel sessions","-","Maurice Pope",648,"other","","","-","55","99","Reserved and Withdrawn documents",16830,"Withdrawn","2015-04-20T16:45:40.957",null,"","","","","","","","","","","","","","",""]
["S2-151368","Reserved for Puneet's parallel sessions","-","Maurice Pope",648,"other","","","-","55","99","Reserved and Withdrawn documents",16840,"Withdrawn","2015-04-20T16:45:40.990",null,"","","","","","","","","","","","","","",""]
["S2-151369","Reserved for Puneet's parallel sessions","-","Maurice Pope",648,"other","","","-","55","99","Reserved and Withdrawn documents",16850,"Withdrawn","2015-04-20T16:45:41.003",null,"","","","","","","","","","","","","","",""]
["S2-151370","Draft Response to Reply LS on paging for MTC","SA WG2","Chris Pudney",1122,"LS out","","","Draft Response to Reply LS on paging for MTC (GP-150312/S2-150716; R1-150924/S2-150720 )","7","4.1","Common issues and Incoming LSs",10270,"Revised","2015-04-20T16:45:41.037","2015-04-20T16:44:46.107","S2-151354","S2-151383","Rel-13","","","","","","","","S2-150716","RAN WG1, RAN WG2, RAN WG3, GERAN WG2","TSG GERAN"]
["S2-151371","Introduce the Dedicated Core Network (DECOR) feature","NTT DOCOMO, Huawei","Irfan Ali",50390,"CR","","","Summary of change: Introduce the DECOR feature based on conclusions of TR 23.707","27","6.3","Dedicated Core Networks (DECOR)",11710,"Revised","2015-04-20T16:45:41.067","2015-04-20T16:44:46.107","S2-151321","S2-151399","Rel-13","23.401","13.2.0","DECOR","2837","5","B",null,"","","","",""]
["S2-151372","Introduce the Dedicated Core Network (DECOR) feature","NTT DOCOMO, Huawei","Irfan Ali",50390,"CR","","","Summary of change: Introduce the decor feature based on conclusions of TR 23.707.","27","6.3","Dedicated Core Networks (DECOR)",11810,"Revised","2015-04-20T16:45:41.160","2015-04-20T16:44:46.967","S2-151323","S2-151743","Rel-13","23.060","13.2.0","DECOR","1953","4","B",null,"","","","",""]
["S2-151373","Clarification of ProSe Layer 2 Group ID provisioning","Samsung","Youngkyo Baek",46395,"CR","","","Summary of change: the ProSe Layer 2 Group ID is clarified it can be a configurable parameter.","15","5.1","3GPP Packet Access Maintenance",10780,"Agreed","2015-04-20T16:45:41.237","2015-04-20T16:44:47.840","S2-151327","","Rel-12","23.303","12.4.0","TEI12, ProSe","0160","2","F",null,"","","","",""]
["S2-151374","Correction to Monitor request procedure with application controlled extension","Samsung","Youngkyo Baek",46395,"pCR","","","This contribution corrects an error in the monitor request procedure agreed at SA WG2#107.","21","6.1","Release 13 Maintenance",14160,"Approved","2015-04-20T16:45:41.317","2015-04-20T16:44:49.460","S2-151330","","Rel-13","23.713","","eProSe-Ext-SA2TR","","","","","","","","",""]
["S2-151375","Fixes to Public Safety Discovery procedures","Intel","Saso Stojanovski",24932,"pCR","","","Proposes fixes to the Public Safety Discovery procedures","21","6.1","Release 13 Maintenance",13900,"Approved","2015-04-20T16:45:41.347","2015-04-20T16:44:50.320","S2-151312","","Rel-13","23.713","","eProSe-Ext-SA2TR","","","","","","","","",""]
["S2-151376","Corrections in ProSe UE-NW Relay discovery","Nokia Networks, Qualcomm Incorporated","György Wolfner",31366,"pCR","","","This paper investigates the usefulness of providing the 'APN information' and the PLMN ID from the Relay during the ProSe UE-NW Relay discovery and proposes certain mechanisms to do that.","21","6.1","Release 13 Maintenance",14270,"Approved","2015-04-20T16:45:41.380","2015-04-20T16:44:51.193","S2-151336","","Rel-13","23.713","","","","","","","","","","",""]
["S2-151377","way forward on some unsolved FFS issues","Samsung","Youngkyo Baek",46395,"pCR","","","This contribution is to solve some remaining FFS issues.","40","6.16","Feasibility study on IOPS (FS_IOPS_St2)",15920,"Approved","2015-04-20T16:45:41.410","2015-04-20T16:44:51.317","S2-151317","","Rel-13","23.797","","FS_IOPS_St2","","","","","","","","",""]
["S2-151378","Restriction of UEs not allowed in IOPS PLMN","Ericsson","Shabnam Sultana",21207,"pCR","","","define how to bar unauthorised UEs for IOPS","40","6.16","Feasibility study on IOPS (FS_IOPS_St2)",15950,"Approved","2015-04-20T16:45:41.440","2015-04-20T16:44:52.190","S2-151319","","Rel-13","23.797","","FS_IOPS_St2","","","","","","","","",""]
["S2-151379","[DRAFT] LS on proposed method of restricting access to IOPS cells","SA WG2","Philip Young",27298,"LS out","","","To: SA WG1","40","6.16","Feasibility study on IOPS (FS_IOPS_St2)",15970,"Revised","2015-04-20T16:45:41.473","2015-04-20T16:44:53.050","S2-151318","S2-151423","","","","","","","","",null,"SA WG1","-"]
["S2-151380","Clarification of applicable UE mobility procedures","General Dynamics UK Ltd.","Philip Young",27298,"pCR","","","This contribution proposes text to clarify the applicable UE mobility procedures in the full range of possible cell transition scenarios","40","6.16","Feasibility study on IOPS (FS_IOPS_St2)",16030,"Approved","2015-04-20T16:45:41.503","2015-04-20T16:44:53.067","S2-151338","","Rel-13","23.797","","FS_IOPS_St2","","","","","","","","",""]
["S2-151381","[DRAFT] LS on support of public safety services over an IOPS network","SA WG2","Philip Young",27298,"LS out","","","LS to SA WG6 and SA WG3 informing them of SA WG2 decisions regarding the manner in which public safety services will be supported over IOPS networks","40","6.16","Feasibility study on IOPS (FS_IOPS_St2)",16080,"Revised","2015-04-20T16:45:41.537","2015-04-20T16:44:53.923","S2-151340","S2-151424","Rel-13","","","","","","","",null,"SA WG6, SA WG3","-"]
["S2-151382","Response to Reply LS on Security Framework for Cellular IoT","SA WG2","Chris Pudney",1122,"LS out","","","Draft response to SA WG3 LS in S2-150738 = S3-151198","7","4.1","Common issues and Incoming LSs",10220,"Approved","2015-04-20T16:45:41.567","2015-04-20T16:44:53.940","S2-151311","","Rel-13","","","","","","","","S2-150738","SA WG3","GERAN WG2, TSG GERAN, TSG SA, SA WG1"]
["S2-151383","Response to Reply LS on paging for MTC","SA WG2","Chris Pudney",1122,"LS out","","","Draft Response to Reply LS on paging for MTC (GP-150312/S2-150716; R1-150924/S2-150720 )","7","4.1","Common issues and Incoming LSs",10280,"Approved","2015-04-20T16:45:41.613","2015-04-20T16:44:53.953","S2-151370","","Rel-13","","","","","","","","S2-150716","RAN WG3, RAN WG2, RAN WG1, GERAN WG2, GERAN WG1","TSG GERAN"]
["S2-151384","Reply LS on Clarification regarding change of active time value and periodic TAU or RAU timer value for UE supporting PSM","SA WG2","Miguel Griot",43100,"LS out","","","Replies that UE can start RAU/TAU when change in condition in the UE triggers a need for a different active time/periodic RAU/TAU timer.","15","5.1","3GPP Packet Access Maintenance",10570,"Approved","2015-04-20T16:45:41.643","2015-04-20T16:44:53.970","S2-151133","","Rel-12","","","","","","","","S2-150708","CT WG1"]
["S2-151385","Discussion on the how to avoid SRVCC","ZTE","Zhendong Li",38521,"pCR","","","This paper analyzes the solutions on how to avoid the SRVCC and proposes the suggestion","33","6.9","Enhancements to WEBRTC interoperability (eWebRTCi)",13770,"Revised","2015-04-20T16:45:41.690","2015-04-20T16:44:53.987","S2-151184","S2-151428","Rel-13","23.706","","eWebRTCi","","","","","","","","",""]
["S2-151386","Way forward on the key issue - Architectural aspects for minimizing the need for bearer level protocol conversion","ZTE","Zhendong Li",38521,"pCR","","","This paper analyzes the solution on the key issue - 'Architectural aspects for minimizing the need for bearer level protocol conversion' and proposes the way forward.","33","6.9","Enhancements to WEBRTC interoperability (eWebRTCi)",13830,"Approved","2015-04-20T16:45:41.737","2015-04-20T16:44:54.890","S2-151185","","Rel-13","23.706","","eWebRTCi","","","","","","","","",""]
["S2-151387","LS on OMR-based solution for end-to-end transparent media in eWebRTCi","SA WG2","Zhendong Li",38521,"LS out","","","To: SA WG3-LI. Attachments: link to TR 23.706","33","6.9","Enhancements to WEBRTC interoperability (eWebRTCi)",13850,"Approved","2015-04-20T16:45:41.847","2015-04-20T16:44:55.747","S2-151186","","Rel-13","","","","","","","",null,"SA WG3-LI","-"]
["S2-151388","Stage 2 cleanup regarding the WIC registration with a security token","Samsung","Sung Hwan Won",46717,"CR","","","Summary of change: 1. In addition to IMS identities, e.g. the validity period is derived from the security token. 2. Web authentication can be avoided in case of registration refreshment.","18","5.4","IMS-Related Maintenance",11390,"Agreed","2015-04-20T16:45:41.893","2015-04-20T16:44:55.873","S2-151108","","Rel-12","23.228","12.8.0","TEI12, IMS_WebRTC","1128","2","F",null,"","","","",""]
["S2-151389","Stage 2 cleanup regarding the WIC registration with a security token","Samsung","Sung Hwan Won",46717,"CR","","","Rel-13 mirror CR: Summary of change: 1. In addition to IMS identities, e.g. the validity period is derived from the security token. 2. Web authentication can be avoided in case of registration refreshment.","18","5.4","IMS-Related Maintenance",11420,"Agreed","2015-04-20T16:45:42.003","2015-04-20T16:44:57.590","S2-151109","","Rel-13","23.228","13.2.0","TEI12, IMS_WebRTC","1129","2","A",null,"","","","",""]
["S2-151390","Support of NB_IFOM for S2a SCM","Qualcomm Incorporated","Haris Zisimopoulos",41602,"pCR","","","A proposal for NB_IFOM for S2a SCM is provided.","28","6.4","IP Flow Mobility support for S2a and S2b interfaces (NBIFOM)",12090,"Approved","2015-04-20T16:45:42.113","2015-04-20T16:44:59.227","S2-151226","","Rel-13","23.861","","NBIFOM","","","","","","","","",""]
["S2-151391","Cleanup of the Loss of an Access from a PDN Connection","Huawei, HiSilicon, China Telecom","Runze Zhou",60945,"pCR","","","This contribution cleans up the Editor's notes in the section of loss of an access from a PDN connection.","28","6.4","IP Flow Mobility support for S2a and S2b interfaces (NBIFOM)",12140,"Approved","2015-04-20T16:45:42.160","2015-04-20T16:45:00.100","S2-151277","","Rel-13","23.861","","NBIFOM","","","","","","","","",""]
["S2-151392","Conclusions for NBIFOM Open Issues 6 and 7","ZTE","Tricci So",44974,"pCR","","","This P-CR proposes the conclusions oftwo open issues about the support for Inter-MME/SGSN IP flow mobility and PMIP to be deferred from the NBIFOM Rel-13 study.","28","6.4","IP Flow Mobility support for S2a and S2b interfaces (NBIFOM)",12290,"Approved","2015-04-20T16:45:42.190","2015-04-20T16:45:01.147","S2-151279","","Rel-13","23.861","","NBIFOM","","","","","","","","",""]
["S2-151393","Removing alternatives from S2a call flows","Apple Inc., Huawei, Hisilicon","Krisztian Kiss",57762,"pCR","","","This contribution proposes to close Editor's Notes 8a, 9, 11a and 16a from the Open Issues list and align section 7.5.4 (S2b flows) with section 7.3.2 (S2a flows).","28","6.4","IP Flow Mobility support for S2a and S2b interfaces (NBIFOM)",12330,"Approved","2015-04-20T16:45:42.237","2015-04-20T16:45:02.067","S2-151252","","Rel-13","23.861","","NBIFOM-SA2TR","","","","","","","","",""]
["S2-151394","Conclusion for NBIFOM study in Rel-13","ZTE","Tricci So",44974,"pCR","","","This P-CR presents the conclusions of the NBIFOM study in Rel-13.","28","6.4","IP Flow Mobility support for S2a and S2b interfaces (NBIFOM)",12380,"Approved","2015-04-20T16:45:42.283","2015-04-20T16:45:03.017","S2-151256","","Rel-13","23.861","","NBIFOM","","","","","","","","",""]
["S2-151395","Reply LS on ePDG selection","SA WG2","Huan Li",43311,"LS out","","","Response to S2-151095.","24","6.1.3","Rel-13 Non-3GPP Access Maintenance",11560,"Approved","2015-04-20T16:45:42.330","2015-04-20T16:45:04","S2-151210","","","","","","","","","","S2-151095","GSMA RiLTE","CT WG1, SA WG1"]
["S2-151396","Enforcement of traffic steering policy","Cisco, Allot Communications, Huawei, HiSilicon, Sprint, Comverse, Sandvine Incoporated, US cellular, Broadcom Corporation, Alcatel-Lucent and Alcatel-Lucent Shanghai Bell, Openet Telecom","Nirav Salot",56645,"pCR","","","This paper provides high level description of the enforcement of the traffic steering policy by solution 1.1 and solution 1.2.","37","6.13","Flexible Mobile Service Steering (FMSS)",15010,"Approved","2015-04-20T16:45:42.360","2015-04-20T16:45:04.017","S2-151183","","Rel-13","23.718","","FMSS","","","","","","","","",""]
["S2-151397","Clarification and Evaluation of Policy Based TCF Solution","China Mobile, Broadcom Corporation, CATR, KDDI","Tao Sun",54129,"pCR","","","This contribution clarifies the TCF solution, addresses the corresponding FFS and evaluates the solution.","37","6.13","Flexible Mobile Service Steering (FMSS)",15050,"Approved","2015-04-20T16:45:42.407","2015-04-20T16:45:04.983","S2-151199","","Rel-13","23.718","","FMSS","","","","","","","","",""]
["S2-151398","Semantics of the Traffic Steering Policy","Ericsson, AT&T, Nokia Networks","Shabnam Sultana",21207,"pCR","","","Proposes a Traffic Steering Rule over St interface","37","6.13","Flexible Mobile Service Steering (FMSS)",15180,"Approved","2015-04-20T16:45:42.457","2015-04-20T16:45:06.030","S2-151201","","Rel-13","23.718","","FMSS","","","","","","","","",""]
["S2-151399","Introduce the Dedicated Core Network (DECOR) feature","NTT DOCOMO, Huawei","Irfan Ali",50390,"CR","","","Summary of change: Introduce the DECOR feature based on conclusions of TR 23.707","27","6.3","Dedicated Core Networks (DECOR)",11720,"Revised","2015-04-20T16:45:42.503","2015-04-20T16:45:06.997","S2-151371","S2-151539, S2-151608","Rel-13","23.401","13.2.0","DECOR","2837","6","B",null,"","","","",""]
["S2-151400","eDRX - Idle Mode Issue 2: Solution A","Alcatel-Lucent, Qualcomm Incorporated","Mike Dolan",1692,"pCR","","","This contribution provides text for Solution A to Idle Mode Issue 2 in TR 23.770 (eDRX).","39","6.15","Feasibility study on Extended DRX cycle for Power Consumption Optimization (FS_eDRX)",15620,"Approved","2015-04-20T16:45:42.597","2015-04-20T16:45:07.993","S2-151284","","Rel-13","23.770","","","","","","","","","","",""]
["S2-151401","Conclusions for HL_Com","Ericsson, Qualcomm Incorporated","Shabnam Sultana",21207,"pCR","","","This P-CR adds conclusions for the FS_HLCOM study","36","6.12","Optimizations to Support High Latency Communications (FS_HLCom)",14610,"Revised","2015-04-20T16:45:42.643","2015-04-20T16:45:08.150","S2-151190","S2-151429","Rel-13","23.709","","FS_HLcom","","","","","","","","",""]
["S2-151402","Updating solutions 2 and 6","Huawei, HiSilicon","Frank Mademann",6821,"pCR","","","This paper updates solution 2 to capture the aspects from solution 6.","36","6.12","Optimizations to Support High Latency Communications (FS_HLCom)",14730,"Approved","2015-04-20T16:45:42.707","2015-04-20T16:45:09.087","S2-151175","","Rel-13","23.709","","HLcom","","","","","","","","",""]
["S2-151403","HLCom - Solution 4 - add SCEF, additional evaluation text","Alcatel-Lucent","Mike Dolan",1692,"pCR","","","This contribution provides additional evaluation text to Solution 4 in TR 23.709 (HLCom) to indicate that Solution 4 incorporates Solution 3 and elaborates on MME actions. It also updates the figures and flows to include the SCEF.","36","6.12","Optimizations to Support High Latency Communications (FS_HLCom)",14790,"Approved","2015-04-20T16:45:42.750","2015-04-20T16:45:09.990","S2-151189","","Rel-13","23.709","","","","","","","","","","",""]
["S2-151404","AESE - Conclusions","Alcatel-Lucent, Intel","Mike Dolan",1692,"pCR","","","This contribution provides conclusions text for clause 8 in TR 23.708 (AESE).","29","6.5","Architecture Enhancements for Service Exposure (AESE)",12710,"Revised","2015-04-20T16:45:42.797","2015-04-20T16:45:10.133","S2-151257","S2-151427","Rel-13","23.708","","","","","","","","","","",""]
["S2-151405","Solution update for setting up an AS session with required QoS","Huawei, HiSilicon, Alcatel-Lucent, Intel, China Mobile","Mirko Schramm",23396,"pCR","","","This contribution completes the solution description.","29","6.5","Architecture Enhancements for Service Exposure (AESE)",12450,"Approved","2015-04-20T16:45:42.847","2015-04-20T16:45:10.257","S2-151140","","Rel-13","23.708","","AESE","","","","","","","","",""]
["S2-151406","Solution update for change of chargeable party","Huawei, HiSilicon","Mirko Schramm",23396,"pCR","","","This contribution completes the solution description.","29","6.5","Architecture Enhancements for Service Exposure (AESE)",12490,"Approved","2015-04-20T16:45:42.893","2015-04-20T16:45:11.287","S2-151239","","Rel-13","23.708","","AESE","","","","","","","","",""]
["S2-151407","Solution update for background data transfer","Huawei, HiSilicon, NTT DOCOMO","Mirko Schramm",23396,"pCR","","","This contribution updates the solution description and proposes a new alternative.","29","6.5","Architecture Enhancements for Service Exposure (AESE)",12660,"Revised","2015-04-20T16:45:42.940","2015-04-20T16:45:12.627","S2-151142","S2-151426","Rel-13","23.708","","AESE","","","","","","","","",""]
["S2-151408","Monitoring Feature Description","Intel, Huawei, Alcatel-Lucent","Puneet Jain",36283,"CR","","","Summary of change: High level description for monitoring function and monitoring via HSS, SGSN/MME and PCRF is specified.","30","6.6","Monitoring Enhancements (MONTE)",12860,"Revised","2015-04-20T16:45:42.987","2015-04-21T05:32:28.453","S2-151272","S2-151510","Rel-13","23.682","13.1.0","MONTE","0100","3","B",null,"","","","",""]
["S2-151409","Monitoring via PCRF","Ericsson","Shabnam Sultana",21207,"CR","","","Summary of change: Reporting current user location and communication failure via PCRF as defined in 23.203.","30","6.6","Monitoring Enhancements (MONTE)",12900,"Revised","2015-04-20T16:45:43.097","2015-04-20T16:45:14.843","S2-151273","S2-151491, S2-151749","Rel-13","23.682","13.1.0","MONTE","0093","3","B",null,"","","","",""]
["S2-151410","Update to PSM to support monitoring events","Huawei, HiSilicon, Intel","Frank Mademann",6821,"CR","","","Summary of change: Active and reachability timer handling will be decoupled. The support of the monitoring event of Reachability for Data is introduced.","30","6.6","Monitoring Enhancements (MONTE)",13030,"Agreed","2015-04-20T16:45:43.203","2015-04-20T16:45:15.967","S2-151219","","Rel-13","23.682","13.1.0","MONTE","0096","2","B",null,"","","","",""]
["S2-151411","Update to PSM to support monitoring events","Huawei, HiSilicon, Intel","Frank Mademann",6821,"CR","","","Summary of change: Active and reachability timer handling will be decoupled. The support of monitoring event Reachability for Data are introduced.","30","6.6","Monitoring Enhancements (MONTE)",13060,"Agreed","2015-04-20T16:45:43.313","2015-04-20T16:45:17.043","S2-151220","","Rel-13","23.401","13.2.0","MONTE","2850","2","B",null,"","","","",""]
["S2-151412","Update to PSM to support monitoring events","Huawei, HiSilicon, Intel","Frank Mademann",6821,"CR","","","Summary of change: Active and reachability timer handling will be decoupled. The support of monitoring event Reachability for Data is introduced.","30","6.6","Monitoring Enhancements (MONTE)",13090,"Agreed","2015-04-20T16:45:43.423","2015-04-20T16:45:18.103","S2-151221","","Rel-13","23.060","13.2.0","MONTE","1960","2","B",null,"","","","",""]
["S2-151413","Cover Sheet for TR 23.769 for Approval at TSG SA","GROUPE Rapporteurs (Huawei)","Runze Zhou",60945,"TS or TR","","","This contribution proposes a cover page for submitting TR 23.769 to SA plenary for Approval.","31","6.7","Group based Enhancements (GROUPE)",13260,"Approved","2015-04-20T16:45:43.530","2015-04-20T16:45:19.023","S2-151159","","Rel-13","23.769","1.2.0","","","","","","","","","",""]
["S2-151414","Group message delivery function and procedure","Huawei, Hisilicon, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Samsung, KPN","Runze Zhou",60945,"CR","","","Summary of change: High level description for group messge delivery function and delivery procedures is specified.","31","6.7","Group based Enhancements (GROUPE)",13300,"Revised","2015-04-20T16:45:43.610","2015-04-20T16:45:19.257","S2-151192","S2-151753","Rel-13","23.682","13.1.0","GROUPE","0094","3","B",null,"","","","",""]
["S2-151415","Cleanup for Solution: Use of MBMS for Group Message Delivery","Samsung","Sung Hwan Won",46717,"pCR","","","It is proposed to modify solution description of 'Use of MBMS for Group Message Delivery.'","31","6.7","Group based Enhancements (GROUPE)",13230,"Approved","2015-04-20T16:45:43.703","2015-04-20T16:45:20.273","S2-151174","","Rel-13","23.769","","GROUPE","","","","","","","","",""]
["S2-151416","MS Info Change Reporting Action at change of Serving Node (MME <--> SGSN): Update of call Flows","Alcatel-Lucent, Alcatel-Lucent Shanghai Bell","Laurent Thiebaut",11066,"CR","","","Summary of change: Align the call flows (of mobility between MME and SGSN) with text in § 5.9.2.1 which mostly consist in 1) if the target SGSN/MME supports location information change reporting, the target SGSN/MME shall include the User Location Information in the Modify Bearer Request, regardless of whether ULI change reporting had been requested in the previous RAT by the PGW 2) If User Location Information change reporting is required and supported in the target RAT, the PGW shall request MS Info Change Reporting Action in the Modify Bearer Response","16","5.2","QoS and PCC Maintenance",11090,"Agreed","2015-04-20T16:45:43.750","2015-04-20T16:45:21.427","S2-151264","","Rel-12","23.401","12.8.0","CNO_ULI","2860","3","F",null,"","","","",""]
["S2-151417","MS Info Change Reporting Action at change of Serving Node (MME <--> SGSN): Update of call Flows","Alcatel-Lucent, Alcatel-Lucent Shanghai Bell","Laurent Thiebaut",11066,"CR","","","Rel-13 mirror CR: Summary of change: Align the call flows (of mobility between MME and SGSN) with text in § 5.9.2.1 which mostly consist in 1) if the target SGSN/MME supports location information change reporting, the target SGSN/MME shall include the User Location Information in the Modify Bearer Request, regardless of whether ULI change reporting had been requested in the previous RAT by the PGW 2) If User Location Information change reporting is required and supported in the target RAT, the PGW shall request MS Info Change Reporting Action in the Modify Bearer Response","16","5.2","QoS and PCC Maintenance",11130,"Agreed","2015-04-20T16:45:43.860","2015-04-20T16:45:22.440","S2-151265","","Rel-13","23.401","13.2.0","CNO_ULI","2861","3","A",null,"","","","",""]
["S2-151418","[DRAFT] Reply to LS to 3GPP on IMS Emergency Session over WLAN","SA WG2","Hyunsook Kim",42013,"LS out","","","Response to S2-150705.","41","6.17","Feasibility study on the Support of Emergency services over WLAN (FS_SEW)",16160,"Revised","2015-04-20T16:45:43.953","2015-04-20T16:45:23.500","S2-151245","S2-151431","","","","","","","","","S2-150705","GSMA Networks Group RILTE","TSG SA, SA WG1"]
["S2-151419","First list of Key issues: AAA server knowledge of emergency & Location","Alcatel-Lucent, Alcatel-Lucent ShangHai Bell, Qualcom Inc","Laurent Thiebaut",11066,"pCR","","","Proposes key issues to 23.771 about AAA server knowledge of emergency & about Location","41","6.17","Feasibility study on the Support of Emergency services over WLAN (FS_SEW)",16290,"Approved","2015-04-20T16:45:44","2015-04-20T16:45:23.517","S2-151281","","Rel-13","23.771","","FS_SEW","","","","","","","","",""]
["S2-151420","Solutions for the location related Key Issue","Alcatel-Lucent, Alcatel-Lucent Shanghai Bell","Nicolas Drevon",16459,"pCR","","","This P-CR provides some background on the existing location procedures during session establishment in Trusted WLAN, which can be used for emergency calls, and proposes two solutions for untrusted WLAN case for inclusion in the technical report.","41","6.17","Feasibility study on the Support of Emergency services over WLAN (FS_SEW)",16450,"Approved","2015-04-20T16:45:44.047","2015-04-20T16:45:24.577","S2-151261","","Rel-13","23.771","","FS_SEW","","","","","","","","",""]
["S2-151421","A solution for ePDG selection","Alcatel-Lucent, Alcatel-Lucent ShangHai Bell","Laurent Thiebaut",11066,"pCR","","","A solution for ePDG selection","41","6.17","Feasibility study on the Support of Emergency services over WLAN (FS_SEW)",16490,"Approved","2015-04-20T16:45:44.093","2015-04-20T16:45:25.450","S2-151263","","","23.771","","FS_SEW","","","","","","","","",""]
["S2-151422","Update to the SID on Feasibility study on the Support of Emergency services over WLAN","Alcatel-Lucent, Alcatel-Lucent ShangHai Bell","Laurent Thiebaut",11066,"WID","","","Revised WID TR presented for approval at end of phase 2","50","7.1","New and Revised Work Items, Cover sheets for completed work items",16630,"Approved","2015-04-20T16:45:44.157","2015-04-20T16:45:26.310","S2-151309","","Rel-13","","","","","","","","","","","",""]
["S2-151423","LS on proposed method of restricting access to IOPS cells","SA WG2","Philip Young",27298,"LS out","","","To: SA WG1, RAN WG2, CT WG1","40","6.16","Feasibility study on IOPS (FS_IOPS_St2)",15980,"Approved","2015-04-20T16:45:44.187","2015-04-20T16:45:26.323","S2-151379","","","","","","","","","",null,"SA WG1, RAN WG2, CT WG1","-"]
["S2-151424","LS on support of public safety services over an IOPS network","SA WG2","Philip Young",27298,"LS out","","","LS to SA WG6 and SA WG3 informing them of SA WG2 decisions regarding the manner in which public safety services will be supported over IOPS networks","40","6.16","Feasibility study on IOPS (FS_IOPS_St2)",16090,"Approved","2015-04-20T16:45:44.233","2015-04-20T16:45:26.323","S2-151381","","Rel-13","","","","","","","",null,"SA WG6, SA WG3","-"]
["S2-151425","Reply LS on Study on improved end-to-end QoS handling","SA WG2","Shabnam Sultana",21207,"LS out","","","LS reply to LS from SA WG4 on improved end to end QoS handling","7","4.1","Common issues and Incoming LSs",10120,"Approved","2015-04-20T16:45:44.280","2015-04-20T16:45:26.340","S2-151308","","Rel-13","","","","","","","","S2-150740","SA WG4","CT WG3, CT WG1, CT WG4"]
["S2-151426","Solution update for background data transfer","Huawei, HiSilicon, NTT DOCOMO","Mirko Schramm",23396,"pCR","","","This contribution updates the solution description and proposes a new alternative.","29","6.5","Architecture Enhancements for Service Exposure (AESE)",12670,"Approved","2015-04-20T16:45:44.327","2015-04-20T16:45:26.340","S2-151407","","Rel-13","23.708","","AESE","","","","","","","","",""]
["S2-151427","AESE - Conclusions","Alcatel-Lucent, Intel","Mike Dolan",1692,"pCR","","","This contribution provides conclusions text for clause 8 in TR 23.708 (AESE).","29","6.5","Architecture Enhancements for Service Exposure (AESE)",12720,"Approved","2015-04-20T16:45:44.357","2015-04-20T16:45:27.247","S2-151404","","Rel-13","23.708","","","","","","","","","","",""]
["S2-151428","Discussion on the how to avoid SRVCC","ZTE","Zhendong Li",38521,"pCR","","","This paper analyzes the solutions on how to avoid the SRVCC and proposes the suggestion","33","6.9","Enhancements to WEBRTC interoperability (eWebRTCi)",13780,"Approved","2015-04-20T16:45:44.407","2015-04-20T16:45:27.387","S2-151385","","Rel-13","23.706","","eWebRTCi","","","","","","","","",""]
["S2-151429","Conclusions for HL_Com","Ericsson, Qualcomm Incorporated","Shabnam Sultana",21207,"pCR","","","This P-CR adds conclusions for the FS_HLCOM study","36","6.12","Optimizations to Support High Latency Communications (FS_HLCom)",14620,"Approved","2015-04-20T16:45:44.453","2015-04-20T16:45:28.277","S2-151401","","Rel-13","23.709","","FS_HLcom","","","","","","","","",""]
["S2-151430","LS on RAN assumptions from SA WG2 for FS_eDRX","SA WG2","Miguel Griot",43100,"LS out","","","Provides information to GERAN/RAN WG2 on the assumptions on RAN behaviour for FS_eDRX and requests corroboration.","39","6.15","Feasibility study on Extended DRX cycle for Power Consumption Optimization (FS_eDRX)",15820,"Approved","2015-04-20T16:45:44.500","2015-04-20T16:45:29.163","S2-151288","","Rel-13","","","","","","","",null,"TSG GERAN, RAN WG2"]
["S2-151431","Reply LS on IMS Emergency Session over WLAN","SA WG2","Hyunsook Kim",42013,"LS out","","","Response to S2-150705.","41","6.17","Feasibility study on the Support of Emergency services over WLAN (FS_SEW)",16170,"Approved","2015-04-20T16:45:44.547","2015-04-20T16:45:29.180","S2-151418","","","","","","","","","","S2-150705","GSMA Networks Group RILTE","TSG SA, SA WG1"]

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

{"sheet":"Parameters","index":2,"n_rows":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"]