3GPP TDocs (written contributions) at meeting
Meeting: S2-96 - 2013-04-08 to 2013-04-12, San Diego
meeting id: S2-96 (click id for more info on this meeting)Click on the Tdoc to open its file.
| TDoc | Title | Source | Remarks |
|---|---|---|---|
| S2‑130730 | Draft Agenda for SA WG2#96 | SA WG2 Chairman | Revised in S2-131252 |
| S2‑130731 | Draft Report of SA WG2 meeting #95 | SA WG2 Secretary | Approved |
| S2‑130732 | LS from CT WG3: Reply LS on Questions regarding BBAI procedures | CT WG3 (C3-121735) | Response in S2-131550 |
| S2‑130733 | LS from BBF: Diameter Routing Agent (DRA) enhancements to enable same PCRF selection for BBF fixed device and 3GPP WLAN UE NSWO Gxd IP CAN sessions | BBF (bbf2012.1501.02) | Response in S2-131551 |
| S2‑130734 | LS from CT WG1: LS on clarification of the packet filter precedence value | CT WG1 (C1-124975) | Postponed to meeting #97 |
| S2‑130735 | LS from CT WG1: LS on user experience impact on voice centric devices when PS back-off timer is received | CT WG1 (C1-124999) | Noted (handled in JM) |
| S2‑130736 | LS from SA WG1: LS on network charging for CSFB | SA WG1 (S1-124513) | Postponed to meeting #97 |
| S2‑130737 | LS from SA WG3: Reply LS of GP-121431 on Optimization of Security Parameters for CS to PS SRVCC from GERAN to E-UTRAN/HSPA | SA WG3 (S3-130209) | Noted |
| S2‑130738 | LS from CT WG1: Reply LS on providing access network information for charging | CT WG1 (C1-130802) | Noted |
| S2‑130739 | LS from RAN WG2: Reply LS on Inter RAT Reject with redirection between E-UTRAN and UTRAN | RAN WG2 (R2-130878) | Noted |
| S2‑130740 | LS from RAN WG3: LS on encoding issue on MS Classmark | RAN WG3 (R3-130415) | Response in S2-131253 |
| S2‑130741 | LS from CT WG1: LS on UE's inconsistent behaviour when PS Back-off timer is running | CT WG1 (C1-130841) | Response in S2-131283 |
| S2‑130742 | LS from CT WG1: Reply LS on size of E-UTRA Radio Capabilities | CT WG1 (C1-130842) | Noted |
| S2‑130743 | LS from CT WG1: LS on S1 connection release when rejecting the UE | CT WG1 (C1-130917) | Postponed to meeting #97 |
| S2‑130744 | LS from CT WG3: Reply LS on providing access network information for charging | CT WG3 (C3-130327) | Noted |
| S2‑130745 | LS from CT WG4: LS on Enforcement of Roaming Restriction during I-RAT TAU/RAU procedures | CT WG4 (C4-130417) | Response in S2-131526 |
| S2‑130746 | LS from CT WG4: Response LS on E-UTRA Radio Capabilities | CT WG4 (C4-130418) | Noted |
| S2‑130747 | LS from TSG CT: Shifting of WI IMS Emergency PSAP Callback stage 3 to Rel-12 | TSG CT (CP-130172) | Noted |
| S2‑130748 | LS from TSG CT: Shifting of missing parts of NETLOC stage 3 to Rel-12 | TSG CT (CP-130174) | Noted |
| S2‑130749 | LS from GERAN WG2: Reply LS on providing information on transcoding functions in 3GPP standards | GERAN WG2 (GP-130222) | Noted |
| S2‑130750 | LS from GERAN WG2: Reply LS on requesting input on MTCe solutions | GERAN WG2 (GP-130249) | Noted |
| S2‑130751 | LS from GERAN WG2: Provisioning of E-UTRA Radio Capabilities in GERAN | GERAN WG2 (GP-130258) | Noted |
| S2‑130752 | LS from RAN WG2: Response LS on Size of E-UTRA Radio Capabilities | RAN WG2 (R2-130868) | Noted |
| S2‑130753 | LS from RAN WG3: LS Response on CS AMR type change during relocation | RAN WG3 (R3-130397) | Noted |
| S2‑130754 | LS from RAN WG3: Clarification of the setting of E-UTRAN Service Handover IE on CS bearer | RAN WG3 (R3-130399) | Response in S2-131520 |
| S2‑130755 | LS from TSG RAN: Reply LS on MPLS in Mobile backhaul study in BBF | TSG RAN (RP-130409) | Revised in S2-130773 |
| S2‑130756 | Enforcement of Roaming Restriction during I-RAT TAU/RAU procedures | Cisco | Noted |
| S2‑130757 | 23.401 CR2513: Rejection of Context Request when roaming restrictions are known | Cisco | Revised in parallel session in S2-131265 |
| S2‑130758 | Rejection of Context Request when roaming restrictions are known | Cisco | - |
| S2‑130759 | Rejection of Context Request when roaming restrictions are known | Cisco | - |
| S2‑130760 | Rejection of Context Request when roaming restrictions are known | Cisco | - |
| S2‑130761 | Targeted Service Request | Cisco | Noted |
| S2‑130762 | Additional use cases related with GTP-c Overload or related with the need to have a more dynamic GTP-c Load control | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Verizon, Cisco, CMCC | Revised in S2-131293 |
| S2‑130763 | General Requirements for GTP-c Load / Overload Control | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Verizon, Cisco, CMCC | Revised in S2-131294 |
| S2‑130764 | - | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | - |
| S2‑130765 | - | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | - |
| S2‑130766 | - | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | - |
| S2‑130767 | - | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | - |
| S2‑130768 | Conclusion for GTP-c Load and Overload Control | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Verizon, Cisco, CMCC | Revised in S2-131295 |
| S2‑130769 | [DRAFT] LS on GTP-C Load/Overload Control | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | Revised in S2-131296 |
| S2‑130770 | LS from SA WG3LI: LS on Proximity Services and Lawful Interception | SA WG3-LI (SA3LI13_033r1) | Response in S2-131522 |
| S2‑130771 | LS from SA WG3LI: LS on enhancing IMEI based Lawful Interception in IMS. | SA WG3-LI (SA3LI13_034r2) | Response in S2-131521 |
| S2‑130772 | LS from TSG SA: LS on providing information on transcoding functions in 3GPP standards | TSG SA (SP-130161) | Noted |
| S2‑130773 | LS from TSG RAN: Reply LS on MPLS in Mobile backhaul study in BBF | TSG RAN (RP-130409) | Noted |
| S2‑130774 | LS Response to CT WG4 LS on Inter RAT handover, Inter RAT Release with redirection, Inter RAT Reject with redirection between E-UTRAN and UTRAN/GERAN | Cisco | Revised in parallel session in S2-131281 |
| S2‑130775 | New key issue on differentiated treatment for non-deducible service data flows in case of RAN user plane congestion | Telecom Italia, Deutsche Telekom, Motorola Mobility, Broadcom Corporation, Nokia | Revised in S2-131298 |
| S2‑130776 | Prioritization of IP flows mapped to the same QCI | Telecom Italia, AT&T, Deutsche Telekom, Huawei, Hisilicon, Broadcom Corporation | Revised in S2-131404 |
| S2‑130777 | Enhancement of Service Data Flow filters | Telecom Italia | Not Handled |
| S2‑130778 | Living document for IMS_RegCon | China Mobile | Noted |
| S2‑130779 | Proposal for IMS_RegCon | China Mobile | Revised in S2-131226 |
| S2‑130780 | 23.228 CR1029: Location-based IMS registration control | China Mobile | Noted |
| S2‑130781 | Adding GTP-C Overload Scenario | China Mobile | Noted (Merged) |
| S2‑130782 | A new GTP-C Overload Control Solution | China Mobile | Noted (Merged) |
| S2‑130783 | Clarification of the scenario of ULI reporting | China Mobile | Not Handled |
| S2‑130784 | - | China Mobile | - |
| S2‑130785 | Added solution details for Stateless Gateway solution | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | Not Handled |
| S2‑130786 | Updates for Small Data Solutions | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | Not Handled |
| S2‑130787 | RAN user plane congestion awareness in UE | NEC | Revised in S2-131359 |
| S2‑130788 | UPCON solution: congestion indication from core NW to UE | NEC | Not Handled |
| S2‑130789 | Group communications for LTE public safety discussion | Alcatel-Lucent, Alcatel-Shanghai Bell | Noted |
| S2‑130790 | Prose Communications Without discovery | Alcatel-Lucent, Alcatel-Shanghai Bell | Noted |
| S2‑130791 | Key issue: Prose identities and discovery | Alcatel-Lucent, Alcatel-Shanghai Bell | Not Handled (partially merged) |
| S2‑130792 | Connectionless solution adaptations for UTRAN | Alcatel-Lucent, Alcatel-Shanghai Bell | Not Handled |
| S2‑130793 | Access and Service Provider selection | Research In Motion UK Ltd | Revised in S2-131424 |
| S2‑130794 | Way forward on NS_WLAN mechanism options 3 and 4 | Research In Motion UK Ltd | Not Handled |
| S2‑130795 | Editorial clarifications | Research In Motion UK Ltd | Revised in S2-131414 |
| S2‑130796 | Additional pros and cons for solution#5 | Research In Motion UK Ltd | Noted |
| S2‑130797 | Support for RPLMN | Research In Motion UK Ltd | WITHDRAWN |
| S2‑130798 | 23.401 CR2517: Clarification that IMSVoPS is MMTEL | Research In Motion UK Ltd | Revised in parallel session in S2-131215 |
| S2‑130799 | 23.401 CR2518: Clarification that IMSVoPS is MMTEL | Research In Motion UK Ltd | Revised in parallel session in S2-131216 |
| S2‑130800 | 23.060 CR1761: Clarification that IMSVoPS is MMTEL | Research In Motion UK Ltd | Revised in parallel session in S2-131217 |
| S2‑130801 | 23.060 CR1762: Clarification that IMSVoPS is MMTEL | Research In Motion UK Ltd | Revised in parallel session in S2-131218 |
| S2‑130802 | 23.401 CR2519: Immediate Cancel Location ACK during HSS-initiated detach procedure | Nokia Siemens Networks, Alcatel-Lucent, Huawei | Not Handled |
| S2‑130803 | 23.401 CR2520: Immediate Cancel Location ACK during HSS-initiated detach procedure | Nokia Siemens Networks, Alcatel-Lucent, Huawei | Not Handled |
| S2‑130804 | 23.060 CR1763: Immediate Cancel Location ACK during HSS-initiated detach procedure | Nokia Siemens Networks, Alcatel-Lucent, Huawei | Not Handled |
| S2‑130805 | 23.060 CR1764: Immediate Cancel Location ACK during HSS-initiated detach procedure | Nokia Siemens Networks, Alcatel-Lucent, Huawei | Not Handled |
| S2‑130806 | Discussion Paper on Congestion Indication Options | NEC | Not Handled |
| S2‑130807 | Key issue on video delivery during congestion periods | NEC, Allot, Cisco, Sandvine, NTT DOCOMO, Verizon, KDDI | Revised in S2-131358 |
| S2‑130808 | Small data fast path Establishment | Ericsson, ST-Ericsson | Revised in S2-131435 |
| S2‑130809 | Evaluation of SDDTE transmission efficiency | Ericsson, ST-Ericsson | Not Handled |
| S2‑130810 | 23.221 CR0148R4: Enabling CS services when UE gets IMSI detached | Ericsson, ST-Ericsson | Not Handled |
| S2‑130811 | RAN based parameters tuning for small data transfer | Ericsson, ST-Ericsson | Revised in S2-131406 (withdrawn) |
| S2‑130812 | 23.682 CR0069R1: Triggering indication added in the CDR | Ericsson, ST-Ericsson | Approved |
| S2‑130813 | UPCON terminology | Ericsson, ST-Ericsson | Noted |
| S2‑130814 | Existing closed-loop congestion control mechanisms and their relation to UPCON | Ericsson, ST-Ericsson | Noted |
| S2‑130815 | Challenges for closed-loop UPCON solutions | Ericsson, ST-Ericsson | Noted (Merged) |
| S2‑130816 | Overload on GTP-C interfaces | Ericsson, ST-Ericsson, Huawei | Revised in S2-131410 |
| S2‑130817 | [DRAFT] LS Reply on proposed Diameter Routing Agent (DRA) enhancements | Ericsson | Revised in parallel session in S2-131330 |
| S2‑130818 | Proposed architectural enhancements and corrections | Ericsson | Not Handled |
| S2‑130819 | Clarification to control protocol in solution 1 'Tunneled approach with dedicated UE-TWAG control protocol' | Ericsson, ST-Ericsson, Qualcomm Incorporated, Alcatel-Lucent | Revised in parallel session in S2-131317 |
| S2‑130820 | - | Ericsson, ST-Ericsson | - |
| S2‑130821 | Applicability of pending policy counter status over Sy | Ericsson | Noted |
| S2‑130822 | 23.203 CR0794: Onetime reporting of the present Access Network Information | Ericsson | Revised in S2-131255 |
| S2‑130823 | 23.203 CR0795: Onetime reporting of the present Access Network Information | Ericsson | Revised in S2-131256 |
| S2‑130824 | 23.203 CR0796: Simplification of pending policy counter status provisioning over Sy | Ericsson | Not Handled |
| S2‑130825 | 23.203 CR0797: Simplification of pending policy counter status provisioning over Sy | Ericsson | Not Handled |
| S2‑130826 | 23.203 CR0783R1: S9 optional at local breakout | Ericsson, ST Ericsson, Telecom Italia | Revised in parallel session in S2-131344 |
| S2‑130827 | 23.203 CR0798: S9 optional at local breakout | Ericsson, ST Ericsson, Telecom Italia | Revised in parallel session in S2-1174 |
| S2‑130828 | 23.401 CR2521: ISR handling in SIPTO at local network | Ericsson, ST-Ericsson | Revised in parallel session in S2-131270 |
| S2‑130829 | Prose requirements | Ericsson, ST Ericsson | Noted |
| S2‑130830 | UPCON architecture requirements | Sprint | Not Handled |
| S2‑130831 | ECN based UPCON notification solution | Sprint | Not Handled |
| S2‑130832 | Solution for RAN USER Plan Congestion awareness and notification | Sprint | Not Handled |
| S2‑130833 | Classification of Public Safety ProSe requirements and architectural assumptions | EADS | Not Handled |
| S2‑130834 | Information-theory analysis of the Application vs. 3GPP functional split for group communications | EADS | Noted |
| S2‑130835 | 23.203 CR0799: Application Based Charging functionality added for TDF | Allot Communications, Openwave, Tekelec | Revised in parallel session in S2-131313 |
| S2‑130836 | Application based charging enhancements in case the PCEF performs application detection | Allot Communications | Noted |
| S2‑130837 | Policy Control and TDF based Charging corrections and clarifications | Allot Communications | Revised in parallel session in S2-131336 |
| S2‑130838 | 23.272 CR0864: Correction to detach procedure | New Postcom | Not Handled |
| S2‑130839 | 23.682 CR0073: Missing condition of delivery of Message Delivery Report | New Postcom | Revised in parallel session in S2-131266 |
| S2‑130840 | - | New Postcom | - |
| S2‑130841 | Additional procedure of Detach and PDN disconnection in WLAN on GTP S2a | New Postcom | Not Handled |
| S2‑130842 | 23.272 CR0861R1: Call Independent supplementary services with CSFB | Nokia Corp | Not Handled |
| S2‑130843 | Excessive Delay after Tracking Area Update Reject and Service Reject, cause codes #9, #10, #40 | Nokia Corp | Noted in JM1 |
| S2‑130844 | Updates to Small Data Transmission from RRC Idle Mode solution | NEC | Not Handled |
| S2‑130845 | Evaluation of efficient SD transmission solutions | NEC | Not Handled |
| S2‑130846 | Key issue and proposed solution: Prose Communication out of network coverage | General Dynamics Broadband UK | Noted (Merged) |
| S2‑130847 | Proposed GCSE Architecture Solution | General Dynamics Broadband UK | Noted |
| S2‑130848 | Control of WLAN access in solution #3 | Ericsson, ST-Ericsson | Revised in S2-131389 |
| S2‑130849 | - | Ericsson, ST-Ericsson | - |
| S2‑130850 | Clarification for Solution 1 | Ericson, ST-Ericsson | Revised in parallel session in S2-131307 |
| S2‑130851 | Study on architecture enhancements to support Proximity Services (ProSe) | Qualcomm (Rapporteur) | Noted |
| S2‑130852 | Key issue for architecture impacts | Qualcomm, HTC | Noted (Merged) |
| S2‑130853 | Key issue for direct discovery | Qualcomm, Motorola Mobility | Noted (Merged) |
| S2‑130854 | Key issue for configuration for direct discovery and communication | Qualcomm | Noted (Merged) |
| S2‑130855 | Key issue for authorisation for direct discovery and communication | Qualcomm | Noted (Merged) |
| S2‑130856 | Key issue for ProSe group communication | Qualcomm | Noted (Merged) |
| S2‑130857 | Key issues for direct communication | Qualcomm | Noted (Merged) |
| S2‑130858 | Key issue for ProSe operational aspects | Qualcomm | Noted (Merged) |
| S2‑130859 | Key issue for service continuity | Qualcomm | Noted (Merged) |
| S2‑130860 | Solution for direct discovery and communication | Qualcomm | Revised in S2-131428 |
| S2‑130861 | Additional details for ProSe discovery | Qualcomm | Not Handled |
| S2‑130862 | Discovery basics | Qualcomm | Not Handled |
| S2‑130863 | Types of discovery identifiers | Qualcomm | Not Handled |
| S2‑130864 | Reply LS on Proximity Services and Lawful Interception | Qualcomm | Revised in S2-131522 |
| S2‑130865 | Reply LS on UE's inconsistent behaviour when PS Back-off timer is running | Qualcomm | Revised in parallel session in S2-131283 |
| S2‑130866 | 23.401 CR2522: Disabling ISR when (E)MM backoff timer applies | Qualcomm | Revised in parallel session in S2-131261 |
| S2‑130867 | 23.401 CR2523: Disabling ISR when (E)MM backoff timer applies | Qualcomm | Revised in parallel session in S2-131262 |
| S2‑130868 | 23.401 CR2524: Disabling ISR when (E)MM backoff timer applies | Qualcomm | Revised in parallel session in S2-131263 |
| S2‑130869 | 23.682 CR0072R1: Making Device Trigger outcome to SCS optional | Qualcomm | Revised in parallel session in S2-131267 |
| S2‑130870 | Two scenario approach using DHCPv4 and Stateless DHCPv6 as control-plane and a TWAG VMAC user-plane | Cisco, Broadcom | Revised in parallel session in S2-131316 |
| S2‑130871 | Operator's View on UPCON (Problem Space and Use Case Examples) and Proposed Architectural Requirements | NTT DOCOMO, Orange, KDDI, China Mobile, Verizon | Revised in S2-131297 |
| S2‑130872 | C-Plane/PCC based Congestion Notification | NTT DOCOMO | Not Handled |
| S2‑130873 | S1 connection release when rejecting the UE | Huawei, Hisilicon, Samsung | Not Handled |
| S2‑130874 | 23.401 CR2525: Unidirectional TAD | Huawei, Hisilicon | Noted (Merged) |
| S2‑130875 | 23.401 CR2526: Unidirectional TAD | Huawei, Hisilicon | Noted (Merged) |
| S2‑130876 | 23.401 CR2527: Unidirectional TAD | Huawei, Hisilicon | Noted (Merged) |
| S2‑130877 | 23.203 CR0800: Disabling/re-enabling usage monitoring | Huawei, Hisilicon, Allot Communications, ZTE | Revised in parallel session in S2-131348 |
| S2‑130878 | Push Proxy/Device Agent Function for reducing heartbeat/keep-alive of applications | Huawei, Hisilicon, CATR, Ericsson, ST-Ericsson | Revised in S2-131353 |
| S2‑130879 | Control of Device Triggering in case of UE getting no UP establishment | Huawei, Hisilicon, CATR | Noted |
| S2‑130880 | Update the solution of Overload Control for Device Triggering | Huawei, Hisilicon, CATR | Revised in S2-131432 |
| S2‑130881 | P4C_F: AAA-based accounting | Huawei, Hisilicon | Revised in parallel session in S2-131324 |
| S2‑130882 | P4C_F: OFCS/OCS network element for PCC-based charging | Huawei, Hisilicon | Revised in parallel session in S2-131311 |
| S2‑130883 | P4C_F: reference point definitions | Huawei, Hisilicon | Revised in parallel session in S2-131312 |
| S2‑130884 | P4C_F: Proposal for deletion of editor's note no more applicable | Huawei, Hisilicon | Revised in parallel session in S2-131331 |
| S2‑130885 | P4C_F: implementation of revision based on reply from BBF | Huawei, Hisilicon | Revised in S2-131291 |
| S2‑130886 | Addition of Network Element Description for Alternative3 | Huawei, Hisilicon, ZTE | WITHDRAWN |
| S2‑130887 | Delete the NOTE for Additional IP-CAN Session for NSWO | Huawei, Hisilicon | WITHDRAWN |
| S2‑130888 | Addressing editor notes of solution # 4 | Huawei, Hisilicon | Noted (Merged) |
| S2‑130889 | Inbound and outbound threshold | Huawei, Hisilicon | Not Handled |
| S2‑130890 | Introduction of PLMN information in solution 3 | Huawei, Hisilicon, | Noted |
| S2‑130891 | Clarifications of WCS solution | Huawei, Hisilicon, CATT | Revised in S2-131254 |
| S2‑130892 | Way Forward Suggestion | Huawei, Hisilicon, ZTE, China Telecom, CATT, HTC, Renesas Mobile Europe | Noted |
| S2‑130893 | Eliminate keep-alive package by network-based always-on solution | China Mobile, ZTE, CATT | Revised in S2-131354 |
| S2‑130894 | RAN User Plane congestion awareness by GTP-U extension | China Mobile, AT&T | Revised in S2-131357 |
| S2‑130895 | Leverage SCI for RAN congestion mitigation | China Mobile | Noted (Merged) |
| S2‑130896 | Proposal for general architecture requirements of ProSe | HTC | Noted |
| S2‑130897 | Proposal for key issues based on the high-level ProSe procedure | HTC | Not Handled |
| S2‑130898 | Device Trigger Report handling for recall and replace | Acision | Revised in S2-131292 |
| S2‑130899 | 23.060 CR1739R1: Clarification of the packet filter precedence value | Samsung | Not Handled |
| S2‑130900 | 23.060 CR1765: Clarification of the packet filter precedence value | Samsung | Not Handled |
| S2‑130901 | Reply to LS on clarification of the packet filter precedence value | Samsung | Not Handled |
| S2‑130902 | 23.401 CR2494R1: S1AP: initial Context Setup Complete correction | Samsung | Not Handled |
| S2‑130903 | 23.401 CR2531: S1AP: initial Context Setup Complete correction | Samsung | Not Handled |
| S2‑130904 | 23.401 CR2493R1: Interoperation between MME and Gn/Gp SGSN | Samsung | Not Handled |
| S2‑130905 | 23.401 CR2528: Interoperation between MME and Gn/Gp SGSN | Samsung | Not Handled |
| S2‑130906 | 23.401 CR2529: Clarification on attach with handover type | Samsung | Not Handled |
| S2‑130907 | 23.401 CR2530: Clarification on attach with handover type | Samsung | Not Handled |
| S2‑130908 | E-UTRAN Discovery Model | Samsung | Not Handled |
| S2‑130909 | E-UTRAN ProSe one to one Communication Scenarios | Samsung | Revised in S2-131355 |
| S2‑130910 | Discussion on load information in WLAN | Samsung | Noted |
| S2‑130911 | Extended ANDSF for load-aware WLAN selection | Samsung | Revised in S2-131427 |
| S2‑130912 | Congestion mitigation based on traffic characteristics | Samsung | Not Handled |
| S2‑130913 | Optimizing congestion notification | Samsung | Noted (Merged) |
| S2‑130914 | Key issues - ProSe Discovery Contents | Samsung | Noted (Merged) |
| S2‑130915 | Key issues - ProSe Discovery Procedure | Samsung | Noted (Merged) |
| S2‑130916 | Architectural Requirements | Samsung | Noted |
| S2‑130917 | 23.402 CR1153: Reference correction for draft-ietf-mip6-bootstrapping-dhc to RFC 6611 | Samsung | Revised in parallel session in S2-131342 |
| S2‑130918 | 23.402 CR1154: Reference correction for draft-ietf-mip6-bootstrapping-dhc to RFC 6611 | Samsung | Revised in parallel session in S2-131343 |
| S2‑130919 | 23.401 CR2532: MME behavior in responding to S1 UE Context Release Request due to User Inactivity | AT&T, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | Noted |
| S2‑130920 | Discussion: Interaction between ANQP / GAS parameters and WLAN_NS | Broadcom Corporation, AT&T | Not Handled |
| S2‑130921 | Architecture Considerations for ProSE Discovery | Broadcom Corporation | Noted (Merged) |
| S2‑130922 | Architecture Consideration on EPC based ProSE Discovery Procedures using Presence Services | Broadcom Corporation | Not Handled |
| S2‑130923 | Solution to Key Issue EPC Based ProSe Discovery using Presence Service | Broadcom Corporation | Not Handled |
| S2‑130924 | Architecture Consideration for Service Continuity for ProSe-enabled UE | Broadcom Corporation | Noted (Merged) |
| S2‑130925 | - | Broadcom Corporation | - |
| S2‑130926 | Finalized Solution 2. | Juniper Networks | Revised in parallel session in S2-131319 |
| S2‑130927 | Proposed editor guidance for providing solution description in FS_WORM TR | RIM | Revised in parallel session in S2-131306 |
| S2‑130928 | Solution to FS_WORM Key Issue 2, Scenario's 1 and 2 for the case of CSFB | RIM | WITHDRAWN |
| S2‑130929 | Support of SRVCC for non detectable emergency calls | Research In Motion UK Ltd | Noted |
| S2‑130930 | 23.167 CR0221: Support of SRVCC for non detectable emergency calls | Research In Motion UK Ltd | WITHDRAWN |
| S2‑130931 | 23.167 CR0222: Support of SRVCC for non detectable emergency calls | Research In Motion UK Ltd | WITHDRAWN |
| S2‑130932 | 23.401 CR2533: Support of SRVCC for non detectable emergency calls | Research In Motion UK Ltd | Not Handled |
| S2‑130933 | 23.401 CR2534: Support of SRVCC for non detectable emergency calls | Research In Motion UK Ltd | Not Handled |
| S2‑130934 | Selection of Active ISMP/ISRP rule in Roaming Scenarios | Motorola Mobility, AT&T, Qualcomm Incorporated, Intel | Revised in S2-131366 |
| S2‑130935 | Update of Solution 3 for WLAN selection | Motorola Mobility | Revised in S2-131367 |
| S2‑130936 | ProSe Solution for direct discovery | Motorola Mobility | Revised in S2-131429 |
| S2‑130937 | Updated PPPoE solution | Motorola Mobility | Revised in parallel session in S2-131320 |
| S2‑130938 | Support for 2-phase SaMOG deployments | Motorola Mobility | Revised in S2-131368 |
| S2‑130939 | 23.402 CR1155: Avoid S2b/S2c over SaMOG capable WLANs | Motorola Mobility | Noted |
| S2‑130940 | 23.402 CR1156: Avoid S2b/S2c over SaMOG capable WLANs | Motorola Mobility | Noted |
| S2‑130941 | Solution for WLAN-NS Key Issue #4 | Vodafone | Revised in S2-131360 |
| S2‑130942 | Draft liaison to SA WG5 on PCC for convergence | Vodafone | Revised in parallel session in S2-131340 |
| S2‑130943 | Core Network assisted eNB parameters tuning for small data transfer | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, NEC, Samsung | Revised in S2-131405 |
| S2‑130944 | Clarification of UE state for efficient small data transmission | Samsung | Revised in S2-131351 |
| S2‑130945 | Small data detection for efficient small data transmission | Samsung | Revised in S2-131352 |
| S2‑130946 | 23.272 CR0805R1: Correction on mobile originating CSFB procedure | Samsung | Not Handled |
| S2‑130947 | 23.272 CR0806R1: Correction on mobile originating CSFB procedure | Samsung | Not Handled |
| S2‑130948 | connectionless data solution enhancements and addition of suboption | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, NTT DOCOMO | Revised in S2-131434 |
| S2‑130949 | Solution analysis and architectural requirements for RAN user plane congestion | KDDI, ZTE, Broadcom Corporation | Noted |
| S2‑130950 | Key issue on Push Service during RAN User Plane Congestion | KDDI, ZTE, Broadcom Corporation | Noted |
| S2‑130951 | Cleanup of PMIP based S2a alternative for P4C BBII | KDDI, Broadcom Corporation | Not Handled |
| S2‑130952 | Addition of Impacts and Evaluation on Small Data Fast Path Solution | China Unicom | Not Handled |
| S2‑130953 | Modification on Lean Service Request | China Unicom | Not Handled |
| S2‑130954 | Modification on Solution 5.1.1.3.6.3 Connectionless Mode | China Unicom | Not Handled |
| S2‑130955 | Modification on Solution 5.1.2.3 Keep the UE in connected mode | China Unicom | Not Handled |
| S2‑130956 | Reusing Keep UE in connected mode solution in MTCe for Signalling Overload mitigation | China Unicom | Not Handled |
| S2‑130957 | The old S-GW store the bearer context | China Unicom | Not Handled |
| S2‑130958 | Key Issue 5.1.1 Evaluation Criterion | Intel | Not Handled |
| S2‑130959 | 23.060 CR1766: Consistent description of allowed packet filter configurations | Intel | Noted |
| S2‑130960 | 23.060 CR1767: Consistent description of allowed packet filter configurations | Intel | Noted |
| S2‑130961 | 23.060 CR1768: Consistent description of allowed packet filter configurations | Intel | Noted |
| S2‑130962 | 23.401 CR2535: Consistent description of allowed packet filter configurations | Intel | Noted (Merged) |
| S2‑130963 | 23.401 CR2536: Consistent description of allowed packet filter configurations | Intel | Noted (Merged) |
| S2‑130964 | 23.401 CR2537: Consistent description of allowed packet filter configurations | Intel | Noted (Merged) |
| S2‑130965 | Way Forward for Rel-12 PMOC | NTT DOCOMO, KDDI, SOFTBANK MOBILE, Hitachi, NTC | Noted |
| S2‑130966 | LS on Way forward for Rel-12 PMOC | NTT DOCOMO | Noted |
| S2‑130967 | Gateway selection by SGSN depending on E-UTRAN roaming agreement | NTT DOCOMO | Revised in S2-131251 |
| S2‑130968 | Gateway selection by SGSN depending on E-UTRAN roaming agreement | NTT DOCOMO | Noted |
| S2‑130969 | Gateway selection by SGSN depending on E-UTRAN roaming agreement | NTT DOCOMO | Noted |
| S2‑130970 | Gateway selection by SGSN depending on E-UTRAN roaming agreement | NTT DOCOMO | Revised in parallel session in S2-131274 |
| S2‑130971 | Gateway selection by SGSN depending on E-UTRAN roaming agreement | NTT DOCOMO | Revised in parallel session in S2-131275 |
| S2‑130972 | Backwards Compatibility Issue of QoS Negotiation during the Update PDP Context Request Procedure Between SGSN and GGSN | NTT DOCOMO | Noted |
| S2‑130973 | Correction of SGSN behaviour during the Update PDP Context Request Procedure | NTT DOCOMO | Noted |
| S2‑130974 | Reply LS on S1 connection release when rejecting the UE | NTT DOCOMO | Not Handled |
| S2‑130975 | 23.402 CR1157: Missing IARP description | ZTE, LG Electronics, Motorola Mobility | Approved |
| S2‑130976 | Make stateful DHCPv6 optional in Solution 3 | ZTE | Revised in parallel session in S2-131321 |
| S2‑130977 | V-ANDSF Selection Solution | ZTE | Not Handled |
| S2‑130978 | Ping Pong Mobility Solution | ZTE | Not Handled |
| S2‑130979 | Solution for ProSe discovery and communication | ZTE | Noted |
| S2‑130980 | Key issue of Configuration and Capability Handling for ProSe | HTC | Revised in S2-131422 |
| S2‑130981 | Standalone TWAG scenario in SaMOG | China Telecom | Not Handled |
| S2‑130982 | Solution for Scenario 1&2 of Key Issue 2 | CATT | Noted (Merged) |
| S2‑130983 | Modification of roaming architecture with LBO | CATT | Not Handled |
| S2‑130984 | Key issue for relay discovery and selection | CATT | Noted (Merged) |
| S2‑130985 | Key issue of ProSe Discovery by network | CATT | Noted (Merged) |
| S2‑130986 | Key issue of direct communication bearer activation and deactivation | CATT | Noted |
| S2‑130987 | Key issue of service continuity | CATT | Noted (Merged) |
| S2‑130988 | Solution of ProSe service architecture | CATT | Not Handled |
| S2‑130989 | key issue-ProSe UE identifier | CATT | Noted |
| S2‑130990 | MTC-IWF selection for Uplink small data | CATT | Not Handled |
| S2‑130991 | Update to solution Downlink small data transfer using RRC message | CATT | Not Handled |
| S2‑130992 | 23.682 CR0071R1: Trigger information storage in SMS-SC | CATT | Not Handled |
| S2‑130993 | 23.402 CR1158: Clarification of the information provided by the ANDSF | CATT | Noted |
| S2‑130994 | Subscriber ID in PCRF discovery | CATT | Not Handled |
| S2‑130995 | Addition of routed mode RG without NAT case in IP-CAN session procedure | CATT | Not Handled |
| S2‑130996 | 23.139 CR0040: Correction of Figure 6.3.1-2 | CATT | Noted |
| S2‑130997 | SaMOG TR cleanup | ZTE(Rapporteur) | Revised in parallel session in S2-131326 |
| S2‑130998 | Alternate Solution for congestion awareness by centralized equipment | China Telecom | Noted (Merged) |
| S2‑130999 | Alternate Solution for congestion awareness by new procedure | China Telecom | Not Handled |
| S2‑131000 | 23.272 CR0867: SS service ID used in the Paging message | Huawei, Hisilicon, Telecom Italia | Not Handled |
| S2‑131001 | Further discussion of how CSFB UE return back to the former LTE | Huawei, Hisilicon | Noted in JM1 |
| S2‑131002 | Updates for T5 Small Data Service | Huawei, HiSilicon, Intel, Nokia Siemens Networks, ZTE, HTC, CATT, LG Electronics, Verizon, KT Corp, KPN, China Mobile | Revised in S2-131433 |
| S2‑131003 | Update of T5 Triggering | Huawei, HiSilicon, Intel, Nokia Siemens Networks, HTC, ZTE, LG Electronics, Verizon, KT Corp, KPN, China Mobile | Revised in S2-131407 |
| S2‑131004 | Authorization for ProSe Discovery | Huawei, Hisilicon | Noted |
| S2‑131005 | GCSE architecture proposal | Huawei, Hisilicon | Noted |
| S2‑131006 | 23.401 CR2538: Direct user plane path establishment for SIPTO at local network on eNodeB | Huawei, Hisilicon | Revised in parallel session in S2-131268 |
| S2‑131007 | 23.060 CR1775: Direct user plane path establishment for SIPTO at local network on HNB | Huawei, Hisilicon | Revised in parallel session in S2-131269 |
| S2‑131008 | GTP-C Overload Discussion | Huawei, Hisilicon, Ericsson | Not Handled |
| S2‑131009 | 23.401 CR2539: Clarification on operations related to dual priority | LG Electronics | Revised in parallel session in S2-131276 |
| S2‑131010 | 23.401 CR2540: Clarification on operations related to dual priority | LG Electronics | Revised in parallel session in S2-131277 |
| S2‑131011 | Proposed structure for Architectural Requirements section | LG Electronics | Noted |
| S2‑131012 | Architectural requirement proposal | LG Electronics | Noted |
| S2‑131013 | Discussion on conflict between H-ANDSF policies and V-ANDSF policies in roaming scenarios | LG Electronics | Noted |
| S2‑131014 | Recall/Replace for T5 device triggering | LG Electronics, Intel | Approved |
| S2‑131015 | 23.272 CR0847R1: Clarification on 'SMS in MME' | LG Electronics | Not Handled |
| S2‑131016 | 23.002 CR0261R1: Clarification on the reference of SGd and S6c | LG Electronics | Revised in parallel session in S2-131278 |
| S2‑131017 | 23.002 CR0262R1: Clarification on the reference of SGd and S6c | LG Electronics | Revised in parallel session in S2-131279 |
| S2‑131018 | 23.002 CR0263: Adding SIPTO at the Local Network | LG Electronics | Revised in parallel session in S2-131271 |
| S2‑131019 | 23.401 CR2541: Clarifying the definition on Correlation ID | LG Electronics | Noted |
| S2‑131020 | 23.060 CR1776: Clarifying the definition on Correlation ID | LG Electronics | Noted |
| S2‑131021 | Key Issue on the ProSe Discovery | LG Electronics | Noted (Merged) |
| S2‑131022 | Architectural requirements on ProSe Discovery | LG Electronics | Noted |
| S2‑131023 | Discussion for Key Issue 3, Ping Pong Offloading to WLAN | LG Electronics | Noted |
| S2‑131024 | Timer based solution for the Key Issue 3, Ping Pong Offloading to WLAN | LG Electronics | Revised in parallel session in S2-131305 |
| S2‑131025 | 23.204 CR0099: Clarification on handling for undelivered MSISDN-less SMS | HTC | Not Handled |
| S2‑131026 | Clarification on aspects of Small Data Fast Path Solution | ZTE, China Unicom | Not Handled |
| S2‑131027 | Measure Frequency of UE State Transitions | ZTE, China Unicom | Noted |
| S2‑131028 | PCRF discovery and binding mechanism | ZTE | Revised in parallel session in S2-131349 |
| S2‑131029 | P4C-TI Editor's note clean-up for alternative 3.v2 | ZTE | Not Handled |
| S2‑131030 | P4C-TI evaluation and conclusion | ZTE | Not Handled |
| S2‑131031 | P4C-TI alt 3 location information reporting.doc | ZTE | Not Handled |
| S2‑131032 | LS on Sustainable QoS Policy Control Support for BBF and 3GPP interworking | ZTE | Not Handled |
| S2‑131033 | UPCON congestion mitigation for non-deducible apps | ZTE | Not Handled |
| S2‑131034 | Solution on RAN User Plane Congestion awareness and mitigation | ZTE, KDDI | Noted (Merged) |
| S2‑131035 | ProSe IMS Architecture | NEC | Not Handled |
| S2‑131036 | GCSE IMS Architecture | NEC | Noted |
| S2‑131037 | D2D Communications: New frontier for LTE | NTT DOCOMO | Not Handled |
| S2‑131038 | Revised WID for Proximity Based Services | NTT DOCOMO | Not Handled |
| S2‑131039 | 23.060 CR1734R1: Correction on the definition of packet filter evaluation precedence index | MediaTek, ITRI | Noted |
| S2‑131040 | 23.060 CR1735R1: Correction on the definition of packet filter evaluation precedence index | MediaTek, ITRI | Noted |
| S2‑131041 | 23.060 CR1736R1: Correction on the definition of packet filter evaluation precedence index | MediaTek, ITRI | Noted |
| S2‑131042 | 23.060 CR1737R1: Correction on the definition of packet filter evaluation precedence index | MediaTek, ITRI | Noted |
| S2‑131043 | 23.060 CR1738R1: Correction on the definition of packet filter evaluation precedence index | MediaTek, ITRI | Revised in parallel session in S2-131301 |
| S2‑131044 | 23.060 CR1777: Correction on the definition of packet filter evaluation precedence index | MediaTek, ITRI | Revised in parallel session in S2-131302 |
| S2‑131045 | Draft liaison to SA WG5 on Application based charging | Vodafone | Revised in parallel session in S2-131315 |
| S2‑131046 | Add a Summary of the Impacts of solution 1 | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Ericsson, Qualcomm Incorporated | Revised in parallel session in S2-131318 |
| S2‑131047 | Network Element Description for SPR/UDR and AF | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell. | Revised in parallel session in S2-131332 |
| S2‑131048 | Priority Data Service of BBF Fixed Devices and WLAN UE NSWO | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, AT&T, Verizon | Not Handled |
| S2‑131049 | IP Edge Integrated TDF | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell. | Not Handled |
| S2‑131050 | IP Edge Support for 3GPP Based Gyd/Gzd Charging | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, | Not Handled |
| S2‑131051 | IP Edge Support for PCEF Based Charging - Reference Points and NE Description | Alcatel-Lucent, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Verizon | Revised in parallel session in S2-131323 |
| S2‑131052 | Network Element Description for Alternative-1 - GTP Based S2a Solution | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, | Not Handled |
| S2‑131053 | Reference Points for Alternative-1 - GTP Based S2a Solution | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, | Not Handled |
| S2‑131054 | Study on architecture enhancements to support Group Communication System Enablers for LTE (GCSE_LTE) | Nokia Siemens Networks | Approved |
| S2‑131055 | Scope for GCSE TR 23.768 | Nokia Siemens Networks | Revised in S2-131381 |
| S2‑131056 | GCSE high level work flow description | Nokia Siemens Networks | Noted |
| S2‑131057 | GCSE/Multipoint Service Architecture consideration | Nokia Siemens Networks | Noted |
| S2‑131058 | GCSE/Multipoint Service Architecture consideration | Nokia Siemens Networks | Revised in S2-131379 |
| S2‑131059 | LAU-less Emergency call with CSFB | Nokia Siemens Networks | Noted |
| S2‑131060 | 23.272 CR0854R1: LAU-less Emergency call with CSFB | Nokia Siemens Networks | Revised in parallel session in S2-131280 |
| S2‑131061 | 23.272 CR0862R1: LAU-less Emergency call with CSFB | Nokia Siemens Networks | Revised in parallel session in S2-131289 |
| S2‑131062 | 23.272 CR0863R1: LAU-less Emergency call with CSFB | Nokia Siemens Networks | Revised in parallel session in S2-131290 |
| S2‑131063 | Handling CS FB when PS Domain is backed off | Nokia Siemens Networks, Intel Corporation, HuaWei, HiSilicon, Vodafone, Samsung | Noted in JM1 |
| S2‑131064 | S-GW/P-GW overload prevention | Nokia Siemens Networks | Revised in S2-131411 |
| S2‑131065 | GTP-C enhancements for S-GW/P-GW overload control | Nokia Siemens Networks | Not Handled |
| S2‑131066 | 23.221 CR0155: Enabling terminating CS services for EPS/IMSI attached UE selecting a non-3GPP access | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | Not Handled |
| S2‑131067 | 23.272 CR0868: Enabling terminating CS services for EPS/IMSI attached UE selecting a non-3GPP access | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | Not Handled |
| S2‑131068 | Returning to original LTE PLMN after CSFB call | Alcatel-Lucent | Handled in JM1 |
| S2‑131069 | Discussion on Operator Group Central GGSN concept | Alcatel-Lucent | Noted |
| S2‑131070 | 23.060 CR1778: Introduction of Operator Group GGSN | Alcatel-Lucent | Revised in parallel session in S2-131303 |
| S2‑131071 | 23.060 CR1779: Introduction of Operator Group GGSN | Alcatel-Lucent | Revised in parallel session in S2-131304 |
| S2‑131072 | [DRAFT] LS on SIRIG Operator Group GGSN | Alcatel-Lucent | Not Handled |
| S2‑131073 | 23.272 CR0852R1: CSFB priority call handling in an eMLPP network | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | Not Handled |
| S2‑131074 | 23.272 CR0853R1: Clarification of procedure of Leaving EUTRAN for CSFB for Dual Rx 1xRTT/EUTRAN UE's | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | Not Handled |
| S2‑131075 | Solving FFS issues of solution #4 'ANDSF-based enhanced I-WLAN selection procedure' | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | Noted (Merged) |
| S2‑131076 | 23.401 CR2542: Correct inconsistency with Stage 1 regarding support for emergency bearer services in the serving network | Research In Motion UK Ltd | Not Handled |
| S2‑131077 | 23.401 CR2543: Correct inconsistency with Stage 1 regarding support for emergency bearer services in the serving network | Research In Motion UK Ltd | Not Handled |
| S2‑131078 | 23.060 CR1780: Correct inconsistency with Stage 1 regarding support for emergency bearer services in the serving network | Research In Motion UK Ltd | Not Handled |
| S2‑131079 | 23.060 CR1781: Correct inconsistency with Stage 1 regarding support for emergency bearer services in the serving network | Research In Motion UK Ltd | Not Handled |
| S2‑131080 | Modifications to the small data transmission over NAS solution | Research In Motion UK Limited | Noted |
| S2‑131081 | Deactivating SIPTO@LN PDN connection when UE leaves the Local Network | Research In Motion UK Limited | Noted |
| S2‑131082 | 23.401 CR2544: Deactivating SIPTO@LN PDN connection on mobility events | Research In Motion UK Limited | Not Handled |
| S2‑131083 | 23.060 CR1782: Deactivating SIPTO@LN PDP Context on mobility events | Research In Motion UK Limited | Not Handled |
| S2‑131084 | Initial Considerations on Group Call Architectural Aspects | Vodafone | Noted |
| S2‑131085 | PGW-SGW-charging-alignment in downlink | Ericsson, ST-Ericsson, Verizon, Cisco | Not Handled |
| S2‑131086 | Common Iu/S1 for Connectionless Data Transmission | Qualcomm Incorporated | Not Handled |
| S2‑131087 | Voice Centric UE behavior when backed-off while camping on E-UTRAN | Qualcomm Incorporated | Not Handled |
| S2‑131088 | 23.221 CR0154R1: Voice centric UE disabling E-UTRAN when receiving back-off timer | Qualcomm Incorporated | Not Handled |
| S2‑131089 | On moving PDN connections to a non-3GPP access (e.g. WLAN) and retaining voice/SMS services | Qualcomm Incorporated | Not Handled |
| S2‑131090 | Key Issue - Performance Differentiation | Qualcomm Incorporated | Noted |
| S2‑131091 | Key Issue - Uplink Traffic Prioritization | Qualcomm | Revised in S2-131399 |
| S2‑131092 | [DRAFT] Reply LS on S1 connection release when rejecting the UE | Qualcomm Incorporated | Not Handled |
| S2‑131093 | Default QoS for BBF fixed devices and 3GPP WLAN UE | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Verizon, Huawei, ZTE? | Revised in parallel session in S2-131322 |
| S2‑131094 | Further Architecture Consideration on EPC based ProSE Discovery Procedures using Presence Services | Broadcom Corporation | Not Handled |
| S2‑131095 | Presentation of TR 23.839 to TSG SA#60 for Information | Alcatel-Lucent (Rapporteur) | Not Handled |
| S2‑131096 | UPCON-RAN Congestion Aware Scheduling of Content | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, AT&T? Verizon? | Not Handled |
| S2‑131097 | UPCON-RAN Congestion Aware Fairness | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell.AT&T? Verizon? | Not Handled |
| S2‑131098 | Solution proposal for Key Issue 2, scenarios 1 and 2 | Qualcomm Incorporated | Noted (Merged) |
| S2‑131099 | Solution proposal for Key Issue 2, Scenario 3 'PS bearer suspension during CSFB' | Qualcomm Incorporated | Revised in parallel session in S2-131308 |
| S2‑131100 | Clarifications to solution #3 | Qualcomm Incorporated | Approved |
| S2‑131101 | Use of HPLMN information for PLMN selection in solution #3 | Qualcomm Incorporated, AT&T, Intel, Motorola Mobility, Broadcom | Revised in S2-131390 |
| S2‑131102 | Update on Key Issue #2 to reflect congestion abatement awareness | Intel, III | Revised in S2-131400 |
| S2‑131103 | S1-U Congestion Mitigation Solution | Intel, III | Not Handled |
| S2‑131104 | Architecture & functional requirements for GCSE_LTE | Qualcomm Incorporated | Revised in S2-131380 |
| S2‑131105 | Reducing extra Cx load with BusTI | Orange | Revised in parallel session in S2-131211 |
| S2‑131106 | 23.228 CR1030: Adding support for IP-PBX in static Mode on UNI or NNI | Orange | Noted |
| S2‑131107 | IMS registration control based on SAA to avoid functional impact on the HSS | Orange | Noted |
| S2‑131108 | ProSe key issue - Provisioning of ProSe related information | ITRI | Noted (Merged) |
| S2‑131109 | 23.060 CR1746R1: LAPI Enforcement | Ericsson, ST-Ericsson, Vodafone, Verizon Wireless | Noted |
| S2‑131110 | 23.060 CR1783: LAPI Enforcement | Ericsson, ST-Ericsson, Vodafone, Verizon Wireless | Noted |
| S2‑131111 | 23.401 CR2496R1: LAPI Enforcement | Ericsson, ST-Ericsson, Vodafone, Verizon Wireless | Noted |
| S2‑131112 | 23.401 CR2545: LAPI Enforcement | Ericsson, ST-Ericsson, Vodafone, Verizon Wireless | Noted |
| S2‑131113 | Discussion on RRC pre-redirect solutions | Ericsson, ST-Ericsson | Noted in JM1 |
| S2‑131114 | 23.216 CR0313: SRVCC Handover Cancellation corrections | Ericsson, ST-Ericsson | Revised in parallel session in S2-131213 |
| S2‑131115 | 23.216 CR0314: SRVCC Handover Cancellation corrections | Ericsson, ST-Ericsson | Revised in parallel session in S2-131214 |
| S2‑131116 | 23.228 CR1031: Adding support for IP-PBX in static Mode | Ericsson, ST-Ericsson | Revised in parallel session in S2-131210 |
| S2‑131117 | 23.237 CR0458: Correcting PS-CS Dual Radio flow | Ericsson, ST-Ericsson | Approved |
| S2‑131118 | 23.272 CR0869: CSFB interactions with IMS Emergency call | Ericsson, ST-Ericsson | Not Handled |
| S2‑131119 | 23.272 CR0870: CSFB interactions with IMS Emergency call | Ericsson, ST-Ericsson | Not Handled |
| S2‑131120 | 23.272 CR0871: CSFB interactions with IMS Emergency call | Ericsson, ST-Ericsson | Not Handled |
| S2‑131121 | 23.228 CR1032: Transit AS invocation corrections of reference point | Ericsson, ST-Ericsson | Approved |
| S2‑131122 | 23.228 CR1033: Transit AS invocation corrections of reference point | Ericsson, ST-Ericsson | Approved |
| S2‑131123 | 23.216 CR0315: PS-to-CS handover indicator for the E-UTRAN-to-1x SRVCC procedure | Ericsson, ST-Ericsson | Revised in parallel session in S2-131219 |
| S2‑131124 | 23.216 CR0316: Returning back to E-UTRAN after SRVCC | Ericsson, ST-Ericsson, Telecom Italia, AT&T, Deutsche Telekom, China Mobile | Noted |
| S2‑131125 | 23.272 CR0872: Release of SGs association in case of SRVCC | Ericsson, ST-Ericsson | Revised in S2-131249 |
| S2‑131126 | 23.272 CR0873: Handling of terminating CS services during IMS Call | Ericsson, ST-Ericsson | Revised in parallel session in S2-131225 |
| S2‑131127 | Default QoS for the Subscriber IP Session | Ericsson | Revised in parallel session in S2-131334 |
| S2‑131128 | Solution to reduce frequent state transitions | Nokia Siemens Networks, Intel | Noted |
| S2‑131129 | Evaluation of solutions | Nokia Siemens Networks, Nokia | Not Handled |
| S2‑131130 | Solution proposal to address 'lack of EPS subscription', 'lack of EPS roaming agreement' | Nokia Siemens Networks, NTT DoCoMo, Cisco, Research In Motion UK Ltd. | Noted in JM1 |
| S2‑131131 | Discussion on transfer of alerting session when there are multiple IMS voice sessions in source PS access | ZTE | Noted |
| S2‑131132 | 23.237 CR0459: Clarification on aSRVCC mid-call | ZTE | Revised in parallel session in S2-131207 |
| S2‑131133 | 23.237 CR0460: Clarification on aSRVCC mid-call | ZTE | Revised in parallel session in S2-131208 |
| S2‑131134 | 23.237 CR0461: Clarification on aSRVCC mid-call | ZTE | Revised in parallel session in S2-131209 |
| S2‑131135 | Solution for utilizing beacon signals and probe messages for WLAN network selection. | LG Electronics | Not Handled |
| S2‑131136 | Update of key issue on use of WLAN load Information for network selection. | LG Electronics | Not Handled |
| S2‑131137 | Key Issue on selection of a direct communication path when multiple paths are available. | LG Electronics | Noted |
| S2‑131138 | Solution for selecting a direct communication path when multiple paths are available. | LG Electronics | Not Handled |
| S2‑131139 | Key Issue on revocation of ProSe Discovery permission. | LG Electronics | Noted (Merged) |
| S2‑131140 | Three Key Issues: EPC-level ProSe Discovery, EPC Support for WLAN Direct Communications, Service Continuity | Intel, III, Radisys, Sony | Revised in S2-131418 |
| S2‑131141 | Solution for EPC-level ProSe Discovery | Intel, III, Radisys, Sony | Revised in S2-131393 |
| S2‑131142 | Solution for EPC Support for WLAN Direct Communications | Intel, III, Radisys, Sony | Not Handled |
| S2‑131143 | Solution for Service Continuity | Intel, III, Radisys, Sony | Not Handled |
| S2‑131144 | Key Issue on ProSe Group Communications | Intel | Noted (Merged) |
| S2‑131145 | Solution for ProSe Group Communications | Intel | Not Handled |
| S2‑131146 | Solution for Group-based ProSe Discovery for Public Safety | Intel | Revised in S2-131430 |
| S2‑131147 | OMA PoC as a Group Communication Service Enabler | Intel | Noted |
| S2‑131148 | PDN Deactivation inaccuracies and how to correct them | Intel | Noted |
| S2‑131149 | 23.401 CR2546: Correction to PDN Deactivation for SIPTO@LN | Intel | Revised in parallel session in S2-131272 |
| S2‑131150 | 23.060 CR1784: Incomplete specification text on link MTU size for IPv6 | Intel, Juniper Networks | Not Handled |
| S2‑131151 | Discussion on key issues for IMS registration control | ZTE | Noted |
| S2‑131152 | Solution how to consider load information during WLAN network selection | Nokia Siemens Networks, Nokia | Not Handled |
| S2‑131153 | Issues with standalone TWAG solution | Nokia Siemens Networks, Nokia | Noted |
| S2‑131154 | 23.401 CR2547: Handover clarification for SIPTO at the local network | Nokia Siemens Networks, Nokia | Noted |
| S2‑131155 | Discovery over Internet Protocol or Shared Access L2 Networks | Samsung | Not Handled |
| S2‑131156 | - | Orange | - |
| S2‑131157 | Modification text on 'BPCF Discovery and Selection' | Orange | - |
| S2‑131158 | Re add the FQDN in the signalling messages from the H(e)NB towards the core network | Orange | - |
| S2‑131159 | Modification text on 'BPCF Discovery and Selection' | Orange | - |
| S2‑131160 | Re add the FQDN in the signalling messages from the H(e)NB towards the core network | Orange | - |
| S2‑131161 | - | Orange | - |
| S2‑131162 | 23.401 CR2548: HSS subscription data migration | Alcatel-Lucent, AT&T, HP, Nokia Siemens Networks | Revised in S2-131361 |
| S2‑131163 | 23.401 CR2549: HSS subscription data migration | Alcatel-Lucent, AT&T, HP, Nokia Siemens Networks | Revised in S2-131362 |
| S2‑131164 | 23.060 CR1785: HSS subscription data migration | Alcatel-Lucent, AT&T, HP, Nokia Siemens Networks | Revised in S2-131363 |
| S2‑131165 | 23.060 CR1786: HSS subscription data migration | Alcatel-Lucent, AT&T, HP, Nokia Siemens Networks | Revised in S2-131364 |
| S2‑131166 | High-level Solution proposal for UPCON based on RAN and CN based Congestion Mitigation | NEC, AT&T, Broadcom, InterDigital, NTT DOCOMO, China Mobile, Allot | Revised in S2-131397 |
| S2‑131167 | Proposal for a user-plane congestion indication mechanism | NEC | Noted (Merged) |
| S2‑131168 | Solution for Key Issue #7 | Intel, AT&T, Huawei, Broadcom | Not Handled |
| S2‑131169 | Resolution of Editor's Note in Solution #3 | Intel | Revised in S2-131415 |
| S2‑131170 | UE configuration used in WLAN Network Selection | Gemalto | Not Handled |
| S2‑131171 | Correction of PCC based location reporting procedures | Nokia Siemens Networks | Noted |
| S2‑131172 | 23.203 CR0803: Correction of PCC based location reporting procedures | Nokia Siemens Networks | Revised in S2-131257 |
| S2‑131173 | 23.203 CR0804: Correction of PCC based location reporting procedures | Nokia Siemens Networks | Revised in S2-131258 |
| S2‑131174 | 23.203 CR0805: Corrections in sections describing the bearer binding and event triggering for GTP based EPC | Nokia Siemens Networks | Revised in parallel session in S2-131346 |
| S2‑131175 | 23.203 CR0806: Corrections in sections describing the bearer binding and event triggering for GTP based EPC | Nokia Siemens Networks | Revised in parallel session in S2-131347 |
| S2‑131176 | MTRR support in SCC AS | Nokia Siemens Networks | Noted |
| S2‑131177 | 23.292 CR0197: Support of MTRR feature for T-ADS | Nokia Siemens Networks | Revised in parallel session in S2-131227 |
| S2‑131178 | 23.292 CR0198: Support of MTRR feature for T-ADS | Nokia Siemens Networks | Revised in parallel session in S2-131228 |
| S2‑131179 | Solution alternative enhancing existing QoS bearer concept | Nokia Siemens Networks, Nokia Corp. | Not Handled |
| S2‑131180 | IMS registration control | Nokia Siemens Networks | Noted |
| S2‑131181 | Alternative Solution for Location Based IMS Registration Control | Nokia Siemens Networks | Noted |
| S2‑131182 | Key Issue for ProSe Identities | InterDigital Communications | Revised in S2-131300 |
| S2‑131183 | 23.060 CR1753R1: Prohibiting the MS from sending SMS and User Data in the PS domain while the mobility management back-off timer is running | InterDigital Communications | Noted |
| S2‑131184 | 23.060 CR1754R1: Prohibiting the MS from sending SMS and User Data in the PS domain while the mobility management back-off timer is running | InterDigital Communications | Noted |
| S2‑131185 | Discussion on ProSe server based architecture | InterDigital Communications | Not Handled |
| S2‑131186 | Revision of TR 23.839 scope for inclusion of P4C_TI scope | Huawei, Hisilicon | WITHDRAWN |
| S2‑131187 | Possible solutions in core network for congestion mitigation | Huawei, Hisilicon | Not Handled |
| S2‑131188 | Key Issue for ProSe Architecture | Renesas Mobile Europe Ltd. | Noted (merged) |
| S2‑131189 | Key Issue for ProSe Authorization and Operator Control of ProSe | Renesas Mobile Europe Ltd. | Noted (merged) |
| S2‑131190 | Key Issue for ProSe UE Discovery | Renesas Mobile Europe Ltd. | Noted (merged) |
| S2‑131191 | Key Issue for ProSe Communications when UEs are served by EUTRAN | Renesas Mobile Europe Ltd. | Noted (merged) |
| S2‑131192 | Key Issue for Charging in ProSe | Renesas Mobile Europe Ltd. | Noted (merged) |
| S2‑131193 | Key Issue for Relay for Public Safety ProSe | Renesas Mobile Europe Ltd. | Noted (merged) |
| S2‑131194 | Solution for ProSe UE Discovery | Renesas Mobile Europe Ltd. | Noted |
| S2‑131195 | Solution for ProSe Communications using EUTRA when UEs are served by EUTRAN | Renesas Mobile Europe Ltd. | Not Handled |
| S2‑131196 | 23.167 CR0223: Domain selection before UE detectable emergency session | NTT DOCOMO, NTC | Revised in S2-131212 |
| S2‑131197 | rSRVCC and HO restrictions to E-UTRAN | NTT DOCOMO | Noted |
| S2‑131198 | 23.216 CR0317: HO restriction to E-UTRAN for rSRVCC from UTRAN | NTT DOCOMO | Revised in parallel session in S2-131220 |
| S2‑131199 | DRAFT Enabling HO restrictions to E-UTRAN for rSRVCC | NTT DOCOMO | Revised in parallel session in S2-131221 |
| S2‑131200 | DRAFT LS Reply on Clarification of the setting of E-UTRAN Service Handover IE on CS bearer | NTT DOCOMO | Revised in parallel session in S2-131222 |
| S2‑131201 | Reference Architecture Model for ProSe | Renesas Mobile Europe Ltd. | Revised in S2-131231 |
| S2‑131202 | Architectural Requirements for ProSe | Renesas Mobile Europe Ltd. | Revised in S2-131232 |
| S2‑131203 | 23.216 CR0318: Inclusion of equipment identifier in normal mode of operation | Huawei, Hisilicon | Revised in parallel session in S2-131223 |
| S2‑131204 | SA WG2 Chairman's Report of TSG SA#59 | SA WG2 Chairman | Noted |
| S2‑131205 | Classification of IP flows mapped to the same QCI | Cygnus Broadband | Noted (Merged) |
| S2‑131206 | [DRAFT] Reply LS on enhancing IMEI based Lawful Interception in IMS. | SA WG2 | Revised in S2-131521 |
| S2‑131207 | 23.237 CR0459R1: Clarification on aSRVCC mid-call | ZTE | Approved |
| S2‑131208 | 23.237 CR0460R1: Clarification on aSRVCC mid-call | ZTE | Approved |
| S2‑131209 | 23.237 CR0461R1: Clarification on aSRVCC mid-call | ZTE | Approved |
| S2‑131210 | 23.228 CR1031R1: Adding support for IP-PBX in static Mode | Ericsson, ST-Ericsson | Revised in parallel session in S2-131372 |
| S2‑131211 | Reducing extra Cx load with BusTI | Orange | Approved |
| S2‑131212 | 23.167 CR0223R1: Domain selection before UE detectable emergency session | NTT DOCOMO, NTC, NEC | Approved |
| S2‑131213 | 23.216 CR0313R1: SRVCC Handover Cancellation corrections | Ericsson, ST-Ericsson | Approved |
| S2‑131214 | 23.216 CR0314R1: SRVCC Handover Cancellation corrections | Ericsson, ST-Ericsson | Approved |
| S2‑131215 | 23.401 CR2517R1: Clarification that IMSVoPS is MMTEL | Research In Motion UK Ltd | Approved |
| S2‑131216 | 23.401 CR2518R1: Clarification that IMSVoPS is MMTEL | Research In Motion UK Ltd | Approved |
| S2‑131217 | 23.060 CR1761R1: Clarification that IMSVoPS is MMTEL | Research In Motion UK Ltd | Approved |
| S2‑131218 | 23.060 CR1762R1: Clarification that IMSVoPS is MMTEL | Research In Motion UK Ltd | Revised in parallel session in S2-131229 |
| S2‑131219 | 23.216 CR0315R1: PS-to-CS handover indicator for the E-UTRAN-to-1x SRVCC procedure | Ericsson, ST-Ericsson | Approved |
| S2‑131220 | 23.216 CR0317R1: HO restriction to E-UTRAN for rSRVCC from UTRAN | NTT DOCOMO | Approved |
| S2‑131221 | DRAFT Enabling HO restrictions to E-UTRAN for rSRVCC | NTT DOCOMO | Revised in S2-131519 |
| S2‑131222 | DRAFT LS Reply on Clarification of the setting of E-UTRAN Service Handover IE on CS bearer | NTT DOCOMO | Revised in S2-131520 |
| S2‑131223 | 23.216 CR0318R1: Inclusion of equipment identifier in normal mode of operation | Huawei, Hisilicon | Approved |
| S2‑131224 | 23.272 CR0872R2: Release of SGs association in case of SRVCC | Ericsson, ST-Ericsson, NTT DOCOMO | Revised in parallel session in S2-131230 |
| S2‑131225 | 23.272 CR0873R1: Handling of terminating CS services during IMS Call | Ericsson, ST-Ericsson | Revised in parallel session in S2-131369 |
| S2‑131226 | Proposal for IMS_RegCon | China Mobile | Revised in parallel session in S2-131373 |
| S2‑131227 | 23.292 CR0197R1: Support of MTRR feature for T-ADS | Nokia Siemens Networks | Revised in parallel session in S2-131370 |
| S2‑131228 | 23.292 CR0198R1: Support of MTRR feature for T-ADS | Nokia Siemens Networks | Revised in parallel session in S2-131371 |
| S2‑131229 | 23.060 CR1762R2: Clarification that IMSVoPS is MMTEL | Research In Motion UK Ltd | Approved |
| S2‑131230 | 23.272 CR0872R3: Release of SGs association in case of SRVCC | Ericsson, ST-Ericsson, NTT DOCOMO | Approved |
| S2‑131231 | Reference Architecture Model for ProSe | Renesas Mobile Europe Ltd. | Not Handled |
| S2‑131232 | Architectural Requirements for ProSe | Renesas Mobile Europe Ltd. | Revised in S2-131356 |
| S2‑131233 | Key Issue for Charging in ProSe | Renesas Mobile Europe Ltd., Qualcomm Incorporated | Revised in S2-131420 |
| S2‑131234 | Key issue for direct discovery | Qualcomm Incorporated, Motorola Mobility, Renesas Mobile Europe Ltd, Samsung?, LG Electronics | Revised in S2-131416 |
| S2‑131235 | ProSe direct communication | Renesas Mobile Europe Ltd., Qualcomm Inc., LG Electronics, General Dynamic Broadband UK? | Revised in S2-131395 |
| S2‑131236 | ProSe service continuity | Qualcomm Incorporated, Intel, III, Sony, Radisys | Revised in S2-131419 |
| S2‑131237 | Key issue for configuration for direct discovery and communication | ITRI, Qualcomm Incorporated, HTC | Revised in S2-131394 |
| S2‑131238 | Key Issue - Authorization for ProSe capability feature | Huawei, Hisilicon, Renesas Mobile Europe Ltd., Qualcomm | Revised in S2-131396 |
| S2‑131239 | Key Issue on EPC-level ProSe Discovery | Intel, Broadcom Corporation, CATT, III, LG Electronics, Radisys, Sony | Revised in S2-131417 |
| S2‑131240 | Key Issue on Group Communication | Intel, General Dynamics Broadband UK, Qualcomm Incorporated | Revised in S2-131421 |
| S2‑131241 | Key issue for ProSe System Architecture | Renesas Mobile Europe Ltd., Qualcomm Incorporated, HTC | Revised in S2-131391 |
| S2‑131242 | 23.401 CR2525R1: Unidirectional TAD | Huawei, Hisilicon, Intel | Noted |
| S2‑131243 | 23.401 CR2526R1: Unidirectional TAD | Huawei, Hisilicon, Intel | Noted |
| S2‑131244 | 23.401 CR2527R1: Unidirectional TAD | Huawei, Hisilicon, Intel | Noted |
| S2‑131245 | LS from IEEE OmniRAN Study Group: Interpretations of assumptions in chapter 16 of 3GPP TS 23.402 V11.6.0 (2013-03) on the behavior of a Trusted WLAN Access Network | IEEE OmniRAN Study Group (omniran-13-0024-01-ecsg) | Postponed to meeting #97 |
| S2‑131246 | Analysis on TAU delay issue | NTT DOCOMO | Noted in JM1 |
| S2‑131247 | LS from BBF: LS on Verification of assumptions for supporting Fixed access as Trusted network in interworking scenario (S2-130680) | BBF (bbf2013.272.06) | Noted |
| S2‑131248 | LS from BBF: Response to 3GPP LS on Verification of assumptions for convergent scenario (bbf2013.084.00; S2-130725) | BBF (bbf2013.099.08) | Noted |
| S2‑131249 | 23.272 CR0872R1: Release of SGs association in case of SRVCC | Ericsson, ST-Ericsson, NTT DOCOMO | Revised in parallel session in S2-131224 |
| S2‑131250 | - | NTT DOCOMO, NTC, NEC | - |
| S2‑131251 | Gateway selection by SGSN depending on E-UTRAN roaming agreement | NTT DOCOMO | Noted |
| S2‑131252 | Draft Agenda for SA WG2#96 | SA WG2 Chairman | Approved |
| S2‑131253 | LS response on encoding issue on MS Classmark | SA WG2 | Approved |
| S2‑131254 | Clarifications of WCS solution | Huawei, Hisilicon, CATT | Approved |
| S2‑131255 | Onetime reporting of the present Access Network Information | Ericsson | - |
| S2‑131256 | Onetime reporting of the present Access Network Information | Ericsson | - |
| S2‑131257 | 23.203 CR0803R1: Correction of PCC based location reporting procedures | Nokia Siemens Networks | Revised in S2-131506 |
| S2‑131258 | 23.203 CR0804R1: Correction of PCC based location reporting procedures | Nokia Siemens Networks | Revised in S2-131507 |
| S2‑131259 | [Draft] LS on Way Forward for Rel-12 PMOC | SA WG2 | Noted |
| S2‑131260 | Solution on RAN User Plane Congestion awareness and mitigation | China Telecom, ZTE, KDDI, Intel, Broadcom Corporation | Not Handled |
| S2‑131261 | 23.401 CR2522R1: Disabling ISR when (E)MM backoff timer applies | Qualcomm | Revised in S2-131282 |
| S2‑131262 | 23.401 CR2523R1: Disabling ISR when (E)MM backoff timer applies | Qualcomm | Approved |
| S2‑131263 | 23.401 CR2524R1: Disabling ISR when (E)MM backoff timer applies | Qualcomm | Approved |
| S2‑131264 | - | Cisco | - |
| S2‑131265 | 23.401 CR2513R1: Rejection of Context Request when roaming restrictions are known | Cisco | Noted |
| S2‑131266 | 23.682 CR0073R1: Missing condition of delivery of Message Delivery Report | New Postcom | Approved |
| S2‑131267 | 23.682 CR0072R2: Making Device Trigger outcome to SCS optional | Qualcomm | Revised in parallel session in S2-131285 |
| S2‑131268 | 23.401 CR2538R1: Direct user plane path establishment for SIPTO at local network on eNodeB | Huawei, Hisilicon | Revised in S2-131518 |
| S2‑131269 | 23.060 CR1775R1: Direct user plane path establishment for SIPTO at local network on HNB | Huawei, Hisilicon | Approved |
| S2‑131270 | 23.401 CR2521R1: ISR handling in SIPTO at local network | Ericsson, ST-Ericsson | Revised in S2-131515 |
| S2‑131271 | 23.002 CR0263R1: Adding SIPTO at the Local Network | LG Electronics | Revised in S2-131516 |
| S2‑131272 | 23.401 CR2546R1: Correction to PDN Deactivation for SIPTO@LN | Intel, Cisco | Revised in S2-131517 |
| S2‑131273 | [DRAFT] LS on eNB UE Inactivity Timer Definition and the Usage | SA WG2 | Revised in parallel session in S2-131286 |
| S2‑131274 | Gateway selection by SGSN depending on E-UTRAN roaming agreement | NTT DOCOMO | Approved |
| S2‑131275 | Gateway selection by SGSN depending on E-UTRAN roaming agreement | NTT DOCOMO | Approved |
| S2‑131276 | 23.401 CR2539R1: Clarification on operations related to dual priority | LG Electronics | Approved |
| S2‑131277 | 23.401 CR2540R1: Clarification on operations related to dual priority | LG Electronics | Approved |
| S2‑131278 | 23.002 CR0261R2: Clarification on the reference of SGd and S6c | LG Electronics | Approved |
| S2‑131279 | 23.002 CR0262R2: Clarification on the reference of SGd and S6c | LG Electronics | Approved |
| S2‑131280 | 23.272 CR0854R2: LAU-less Emergency call with CSFB | Nokia Siemens Networks | Revised in parallel session in S2-131288 |
| S2‑131281 | LS Response to CT WG4 LS on Inter RAT handover, Inter RAT Release with redirection, Inter RAT Reject with redirection between E-UTRAN and UTRAN/GERAN | Cisco | Revised in parallel session in S2-131284 |
| S2‑131282 | 23.401 CR2522R2: Disabling ISR when (E)MM backoff timer applies | Qualcomm | Approved |
| S2‑131283 | Reply LS on UE's inconsistent behaviour when PS Back-off timer is running | SA WG2 | Approved |
| S2‑131284 | [DRAFT] LS Response to CT WG4 LS (C4-130417) on Inter RAT handover, Inter RAT Release with redirection, Inter RAT Reject with redirection between E-UTRAN and UTRAN/GERAN | Cisco | Revised in parallel session in S2-131495 |
| S2‑131285 | 23.682 CR0072R3: Making Device Trigger outcome to SCS optional | Qualcomm | Approved |
| S2‑131286 | [DRAFT] LS on eNB UE Inactivity Timer Definition and the Usage | SA WG2 | Revised in parallel session in S2-131287 |
| S2‑131287 | [DRAFT] LS on eNB UE Inactivity Timer Definition and the Usage | SA WG2 | Revised in parallel session in S2-131496 |
| S2‑131288 | 23.272 CR0854R3: LAU-less Emergency call with CSFB | Nokia Siemens Networks | Approved |
| S2‑131289 | 23.272 CR0862R2: LAU-less Emergency call with CSFB | Nokia Siemens Networks | Approved |
| S2‑131290 | 23.272 CR0863R2: LAU-less Emergency call with CSFB | Nokia Siemens Networks | Approved |
| S2‑131291 | P4C_F: implementation of revision based on reply from BBF | Huawei, Hisilicon | Revised in parallel session in S2-131335 |
| S2‑131292 | Device Trigger Report handling for recall and replace | Acision | Approved |
| S2‑131293 | Additional use cases related with GTP-c Overload or related with the need to have a more dynamic GTP-c Load control. | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Verizon, Cisco, CMCC | Revised in S2-131408 |
| S2‑131294 | General Requirements for GTP-c Load / Overload Control | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Verizon, Cisco, CMCC, AT&T | Revised in S2-131409 |
| S2‑131295 | - | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Verizon, Cisco, CMCC, AT&T | - |
| S2‑131296 | - | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | - |
| S2‑131297 | Operator's View on UPCON (Problem Space and Use Case Examples) and Proposed Architectural Requirements | NTT DOCOMO, Orange, KDDI, China Mobile, Verizon | Revised in S2-131490 |
| S2‑131298 | New key issue on differentiated treatment for non-deducible service data flows in case of RAN user plane congestion | Telecom Italia, Deutsche Telekom, Motorola Mobility, Broadcom Corporation, Nokia | Revised in S2-131491 |
| S2‑131299 | - | - | - |
| S2‑131300 | Key Issue for ProSe Identities | InterDigital Communications, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | Revised in S2-131423 |
| S2‑131301 | 23.060 CR1738R2: Correction on the definition of packet filter evaluation precedence index | MediaTek, ITRI | Approved |
| S2‑131302 | 23.060 CR1777R1: Correction on the definition of packet filter evaluation precedence index | MediaTek, ITRI | Approved |
| S2‑131303 | 23.060 CR1778R1: Introduction of Operator Group GGSN | Alcatel-Lucent | Revised in parallel session in S2-131437 |
| S2‑131304 | 23.060 CR1779R1: Introduction of Operator Group GGSN | Alcatel-Lucent | Revised in parallel session in S2-131438 |
| S2‑131305 | Timer based solution for the Key Issue 3, Ping Pong Offloading to WLAN | LG Electronics | Revised in parallel session in S2-131310 |
| S2‑131306 | Proposed editor guidance for providing solution description in FS_WORM TR | RIM | Approved |
| S2‑131307 | Clarification for Solution 1 | Ericson, ST-Ericsson | Approved |
| S2‑131308 | Solution proposal for Key Issue 2, Scenario 3 'PS bearer suspension during CSFB' | Qualcomm Incorporated | Approved |
| S2‑131309 | Solution proposal for Key Issue 2, scenarios 1 and 2 | Qualcomm Incorporated, CATT | Revised in S2-131513 |
| S2‑131310 | Timer based solution for the Key Issue 3, Ping Pong Offloading to WLAN | LG Electronics | Revised in S2-131514 |
| S2‑131311 | P4C_F: OFCS/OCS network element for PCC-based charging | Huawei, Hisilicon | Revised in parallel session in S2-131337 |
| S2‑131312 | P4C_F: reference point definitions | Huawei, Hisilicon | Revised in parallel session in S2-131339 |
| S2‑131313 | 23.203 CR0799R1: Application Based Charging functionality added for TDF | Allot Communications, Openwave, Tekelec | Revised in parallel session in S2-131350 |
| S2‑131314 | 23.203 CR0807: Other changes on Application Based Charging functionality added for TDF | Allot Communications, Openwave, Tekelec, Juniper Networks | Noted (endorsed) |
| S2‑131315 | [DRAFT] LS on Application Based Charging | SA WG2 | Revised in S2-131525 |
| S2‑131316 | Two scenario approach using DHCPv4 and Stateless DHCPv6 as control-plane and a TWAG VMAC user-plane | Cisco, Broadcom | Approved |
| S2‑131317 | Clarification to control protocol in solution 1 'Tunneled approach with dedicated UE-TWAG control protocol' | Ericsson, ST-Ericsson, Qualcomm Incorporated, Alcatel-Lucent | Approved |
| S2‑131318 | Add a Summary of the Impacts of solution 1 | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Ericsson, Qualcomm Incorporated | Revised in parallel session in S2-131446 |
| S2‑131319 | Finalized Solution 2. | Juniper Networks | Approved |
| S2‑131320 | Updated PPPoE solution | Motorola Mobility | Revised in parallel session in S2-131447 |
| S2‑131321 | Make stateful DHCPv6 optional in Solution 3 | ZTE | Noted |
| S2‑131322 | Default QoS for BBF fixed devices and 3GPP WLAN UE | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Verizon, Huawei, ZTE? | Revised in parallel session in S2-131439 |
| S2‑131323 | IP Edge Support for PCEF Based Charging - Reference Points and NE Description | Alcatel-Lucent, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Verizon, Huawei | Revised in parallel session in S2-131338 |
| S2‑131324 | P4C_F: AAA-based accounting | Huawei, Hisilicon | Revised in parallel session in S2-131333 |
| S2‑131325 | Support for two types of Rel-12 SaMOG UEs | Motorola Mobility, Cisco, Orange, Ericsson, ST-Ericsson, Nokia, Nokia Siemens Networks | Noted |
| S2‑131326 | SaMOG TR cleanup | ZTE(Rapporteur) | Revised in parallel session in S2-131448 |
| S2‑131327 | P4C-TI Conclusion | Alcatel-Lucent, AT&T, Ericsson, Huawei, ZTE | Revised in parallel session in S2-131328 |
| S2‑131328 | P4C-TI Conclusion | Alcatel-Lucent, AT&T, Ericsson, Huawei, ZTE | Revised in parallel session in S2-131445 |
| S2‑131329 | - | - | - |
| S2‑131330 | [DRAFT] LS Reply on proposed Diameter Routing Agent (DRA) enhancements | Ericsson | Revised in S2-131523 |
| S2‑131331 | P4C_F: Proposal for deletion of editor's note no more applicable | Huawei, Hisilicon | Approved |
| S2‑131332 | Network Element Description for SPR/UDR and AF | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell. | Revised in parallel session in S2-131440 |
| S2‑131333 | P4C_F: AAA-based accounting | Huawei, Hisilicon | Revised in parallel session in S2-131441 |
| S2‑131334 | Default QoS for the Subscriber IP Session | Ericsson | Approved |
| S2‑131335 | P4C_F: implementation of revision based on reply from BBF | Huawei, Hisilicon | Revised in S2-131546 |
| S2‑131336 | Policy Control and TDF based Charging corrections and clarifications | Allot Communications | Revised in parallel session in S2-131442 |
| S2‑131337 | P4C_F: OFCS/OCS network element for PCC-based charging | Huawei, Hisilicon | Revised in parallel session in S2-131443 |
| S2‑131338 | IP Edge Support for PCEF Based Charging - Reference Points and NE Description | Alcatel-Lucent, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Verizon, Huawei | Approved |
| S2‑131339 | P4C_F: reference point definitions | Huawei, Hisilicon | Revised in parallel session in S2-131444 |
| S2‑131340 | [DRAFT] LS on PCC for convergence (P4C-F) | SA WG2 | Revised in S2-131524 |
| S2‑131341 | [DRAFT] Response LS on Questions regarding BBAI procedures | SA WG2 | Revised in S2-131550 |
| S2‑131342 | 23.402 CR1153R1: Reference correction for draft-ietf-mip6-bootstrapping-dhc to RFC 6611 | Samsung | Approved |
| S2‑131343 | 23.402 CR1154R1: Reference correction for draft-ietf-mip6-bootstrapping-dhc to RFC 6611 | Samsung | Approved |
| S2‑131344 | 23.203 CR0783R2: S9 optional at local breakout | Ericsson, ST Ericsson, Telecom Italia | Revised in S2-131511 |
| S2‑131345 | 23.203 CR0798R1: S9 optional at local breakout | Ericsson, ST Ericsson, Telecom Italia | Revised in S2-131512 |
| S2‑131346 | 23.203 CR0805R1: Corrections in sections describing the bearer binding and event triggering for GTP based EPC | Nokia Siemens Networks | Approved |
| S2‑131347 | 23.203 CR0806R1: Corrections in sections describing the bearer binding and event triggering for GTP based EPC | Nokia Siemens Networks | Approved |
| S2‑131348 | 23.203 CR0800R1: Disabling/re-enabling usage monitoring | Huawei, Hisilicon, Allot Communications, ZTE | Approved |
| S2‑131349 | PCRF discovery and binding mechanism | ZTE | Approved |
| S2‑131350 | 23.203 CR0799R2: Application Based Charging functionality added for TDF | Allot Communications, Openwave, Tekelec | Approved |
| S2‑131351 | Clarification of UE state for efficient small data transmission | Samsung | WITHDRAWN |
| S2‑131352 | - | Samsung | - |
| S2‑131353 | Push Proxy/Device Agent Function for reducing heartbeat/keep-alive of applications | Huawei, Hisilicon, CATR, Ericsson, ST-Ericsson | Revised in S2-131498 |
| S2‑131354 | Eliminate keep-alive package by network-based always-on solution | China Mobile, CATT, China Telecom, ZTE, Huawei | Revised in S2-131499 |
| S2‑131355 | E-UTRAN ProSe one to one Communication Scenarios | Samsung | Approved |
| S2‑131356 | Architectural Requirements for ProSe | Renesas Mobile Europe Ltd. | Revised in S2-131476 |
| S2‑131357 | RAN User Plane congestion awareness by GTP-U extension | China Mobile, AT&T, Cisco | Revised in S2-131398 |
| S2‑131358 | Key issue on video delivery during congestion periods | NEC, Allot, Cisco, Sandvine, NTT DOCOMO, Verizon, KDDI | Approved |
| S2‑131359 | RAN user plane congestion awareness in UE | NEC | WITHDRAWN |
| S2‑131360 | WLAN-NS Key Issue #4 - Solution | AT&T, Broadcom, Intel, Vodafone | Revised in S2-131426 |
| S2‑131361 | 23.401 CR2548R1: HSS subscription data migration | Alcatel-Lucent, AT&T, HP, Nokia Siemens Networks | Not Handled |
| S2‑131362 | 23.401 CR2549R1: HSS subscription data migration | Alcatel-Lucent, AT&T, HP, Nokia Siemens Networks | Not Handled |
| S2‑131363 | 23.060 CR1785R1: HSS subscription data migration | Alcatel-Lucent, AT&T, HP, Nokia Siemens Networks | Not Handled |
| S2‑131364 | 23.060 CR1786R1: HSS subscription data migration | Alcatel-Lucent, AT&T, HP, Nokia Siemens Networks | Not Handled |
| S2‑131365 | LS from 3GPP2: 3GPP2 Structure and Leadership | 3GPP2 (Corr_to_EO_Re-Structure and Leadership) | Postponed to meeting #97 |
| S2‑131366 | Selection of Active ISMP/ISRP rule in Roaming Scenarios | Motorola Mobility, AT&T, Qualcomm Incorporated, Intel | Revised in S2-131388 |
| S2‑131367 | Update of Solution 3 for WLAN selection | Motorola Mobility | Revised in S2-131413 |
| S2‑131368 | Support for two types of Rel-12 SaMOG UEs | Motorola Mobility, Cisco, Orange, Ericsson, ST-Ericsson, Nokia, Nokia Siemens Networks | Revised in parallel session in S2-131325 |
| S2‑131369 | 23.272 CR0873R2: Handling of terminating CS services during IMS Call | Ericsson, ST-Ericsson | Approved |
| S2‑131370 | 23.292 CR0197R2: Support of MTRR feature for T-ADS | Nokia Siemens Networks | Revised in S2-131531 |
| S2‑131371 | 23.292 CR0198R2: Support of MTRR feature for T-ADS | Nokia Siemens Networks | Revised in S2-131532 |
| S2‑131372 | 23.228 CR1031R2: Adding support for IP-PBX in static Mode | Ericsson, ST-Ericsson | Revised in S2-131533 |
| S2‑131373 | Proposals for IMS_RegCon (To update the living document) | China Mobile (Rapporteur), Ericsson, Huawei, Nokia Siemens, ST-Ericsson, ZTE, Others(?) | Revised in S2-131545 |
| S2‑131374 | - | - | - |
| S2‑131375 | - | - | - |
| S2‑131376 | - | - | - |
| S2‑131377 | - | - | - |
| S2‑131378 | - | - | - |
| S2‑131379 | GCSE/Multipoint Service Architecture consideration | Nokia Siemens Networks | Revised in S2-131485 |
| S2‑131380 | Architecture & functional requirements for GCSE_LTE | Qualcomm Incorporated | Revised in S2-131509 |
| S2‑131381 | Scope for GCSE TR 23.768 | Nokia Siemens Networks | Revised in S2-131484 |
| S2‑131382 | Questions for discussion with SA WG1 | SA WG2 Chairman | Noted |
| S2‑131383 | - | - | - |
| S2‑131384 | - | - | - |
| S2‑131385 | - | - | - |
| S2‑131386 | - | - | - |
| S2‑131387 | - | - | - |
| S2‑131388 | Selection of Active ISMP/ISRP rule in Roaming Scenarios | Motorola Mobility, AT&T, Qualcomm Incorporated, Intel | Revised in S2-131488 |
| S2‑131389 | - | Ericsson, ST-Ericsson | - |
| S2‑131390 | Use of HPLMN information for PLMN selection in solution #3 | Qualcomm Incorporated, AT&T, Intel, Motorola Mobility, Broadcom | Approved |
| S2‑131391 | Key issue for ProSe System Architecture | Renesas Mobile Europe Ltd., Qualcomm, HTC | Approved |
| S2‑131392 | Classification of IP flows mapped to the same QCI | China Mobile, Cygnus Broadband, Intel | Not Handled |
| S2‑131393 | Solution for EPC-level ProSe Discovery | Intel, III, Radisys, Sony | Not Handled |
| S2‑131394 | Key issue for configuration for direct discovery and communication | ITRI, Qualcomm Incorporated, HTC | Approved |
| S2‑131395 | ProSe direct communication | Qualcomm, LG Electronics, General Dynamics Broadband UK, Renesas Mobile Europe Ltd. | Revised in S2-131477 |
| S2‑131396 | Key Issue - Authorization for ProSe capability feature | Huawei, Hisilicon, Renesas Mobile Europe Ltd., Qualcomm | Revised in S2-131478 |
| S2‑131397 | High-level Solution proposal for UPCON based on RAN and CN based Congestion Mitigation | NEC, AT&T, Broadcom Corporation, NTT DOCOMO, China Mobile, Allot Communications, Cisco, KDDI, ZTE, China Telecom, Verizon, Intel | Revised in S2-131403 |
| S2‑131398 | RAN User Plane congestion awareness by GTP-U extension | China Mobile, AT&T, Cisco, Samsung, NEC | Revised in S2-131402 |
| S2‑131399 | Key Issue - Uplink Traffic Prioritization | Qualcomm | Approved |
| S2‑131400 | Update on Key Issue #2 to reflect congestion abatement awareness | Intel, III | Approved |
| S2‑131401 | - | SA WG2 | - |
| S2‑131402 | RAN User Plane congestion awareness by GTP-U extension | China Mobile, AT&T, Cisco, Samsung, NEC | Revised in S2-131492 |
| S2‑131403 | High-level Solution proposal for UPCON based on RAN and CN based Congestion Mitigation | NEC, AT&T, Broadcom Corporation, NTT DOCOMO, China Mobile, Allot Communications, Cisco, KDDI, ZTE, China Telecom, Verizon, Intel | Revised in S2-131493 |
| S2‑131404 | Prioritization of IP flows mapped to the same QCI | Telecom Italia, AT&T, Deutsche Telekom, Huawei, Hisilicon, Broadcom Corporation | Revised in S2-131494 |
| S2‑131405 | Core Network assisted eNB parameters tuning for small data transfer | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, NEC, Samsung, Ericsson?, ST-Ericsson? | Revised in S2-131500 |
| S2‑131406 | - | Ericsson, ST-Ericsson | - |
| S2‑131407 | Update of T5 Triggering | Huawei, HiSilicon, Intel, Nokia Siemens Networks, HTC, ZTE, LG Electronics, Verizon, KT Corp, KPN, China Mobile, Telecom Italia | Revised in S2-131501 |
| S2‑131408 | Additional use cases related with GTP-c Overload or related with the need to have a more dynamic GTP-c Load control. | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Verizon, Cisco, CMCC | Revised in S2-131537 |
| S2‑131409 | General Requirements for GTP-c Load / Overload Control | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Verizon, Cisco, CMCC, AT&T | Revised in S2-131538 |
| S2‑131410 | Overload on GTP-C interfaces | Ericsson, ST-Ericsson, Huawei | Revised in S2-131544 |
| S2‑131411 | S-GW/P-GW overload prevention | Nokia Siemens Networks | Revised in S2-131510 |
| S2‑131412 | Solving FFS issues of solution #4 'ANDSF-based enhanced I-WLAN selection procedure' | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Huawei, HiSilicon | Revised in S2-131425 |
| S2‑131413 | Update of Solution 3 for WLAN selection | Motorola Mobility | Revised in S2-131489 |
| S2‑131414 | Editorial clarifications | Research In Motion UK Ltd | Approved |
| S2‑131415 | Resolution of Editor's Note in Solution #3 | Intel | Revised in S2-131486 |
| S2‑131416 | Key issue for direct discovery | Qualcomm Incorporated, Motorola Mobility, Renesas Mobile Europe Ltd, Samsung?, LG Electronics | Revised in S2-131480 |
| S2‑131417 | Key Issue on EPC-level ProSe Discovery | Intel, Broadcom Corporation, CATT, III, LG Electronics, Radisys, Sony | Revised in S2-131479 |
| S2‑131418 | Three Key Issues: EPC-level ProSe Discovery, EPC Support for WLAN Direct Communications, Service Continuity | Intel, III, Radisys, Sony | Revised in S2-131481 |
| S2‑131419 | ProSe service continuity | Qualcomm Incorporated, Intel, III, Sony, Radisys | Revised in S2-131482 |
| S2‑131420 | Key Issue for Charging in ProSe | Renesas Mobile Europe Ltd., Qualcomm Incorporated | Approved |
| S2‑131421 | Key Issue on Group Communication | Intel, General Dynamics Broadband UK, Qualcomm Incorporated | Revised in S2-131483 |
| S2‑131422 | Key issue of Configuration and Capability Handling for ProSe | HTC | Approved |
| S2‑131423 | Key Issue for ProSe Identities | InterDigital Communications, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | Revised in S2-131497 |
| S2‑131424 | Access and Service Provider selection | Research In Motion UK Ltd | Noted |
| S2‑131425 | Solving FFS issues of solution #4 'ANDSF-based enhanced I-WLAN selection procedure' | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Huawei, HiSilicon | Revised in S2-131540 |
| S2‑131426 | WLAN-NS Key Issue #4 - Solution | AT&T, Broadcom, Intel, Vodafone | Revised in S2-131541 |
| S2‑131427 | Extended ANDSF for load-aware WLAN selection | Samsung | Revised in S2-131487 |
| S2‑131428 | Solution for direct discovery and communication | Qualcomm | Revised in S2-131505 |
| S2‑131429 | ProSe Solution for direct discovery | Motorola Mobility | Approved |
| S2‑131430 | Solution for Group-based ProSe Discovery for Public Safety | Intel | Revised in S2-131504 |
| S2‑131431 | - | LG Electronics, Intel | - |
| S2‑131432 | Update the solution of Overload Control for Device Triggering | Huawei, Hisilicon, CATR | Revised in S2-131502 |
| S2‑131433 | Updates for T5 Small Data Service | Huawei, HiSilicon, Intel, Nokia Siemens Networks, ZTE, HTC, CATT, LG Electronics, Verizon, KT Corp, KPN, China Mobile | Revised in S2-131508 |
| S2‑131434 | connectionless data solution enhancements and addition of suboption | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, NTT DOCOMO | Approved |
| S2‑131435 | Small data fast path Establishment | Ericsson, ST-Ericsson | Revised in S2-131503 |
| S2‑131436 | - | - | - |
| S2‑131437 | 23.060 CR1778R2: Introduction of Operator Group GGSN | Alcatel-Lucent | Revised in S2-131529 |
| S2‑131438 | 23.060 CR1779R2: Introduction of Operator Group GGSN | Alcatel-Lucent | Revised in S2-131530 |
| S2‑131439 | Default QoS for BBF fixed devices and 3GPP WLAN UE | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Verizon, Huawei, ZTE? | Approved |
| S2‑131440 | Network Element Description for SPR/UDR and AF | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell. | Approved |
| S2‑131441 | P4C_F: AAA-based accounting | Huawei, Hisilicon | Revised in parallel sessions in S2-131449 |
| S2‑131442 | Policy Control and TDF based Charging corrections and clarifications | Allot Communications | Approved |
| S2‑131443 | P4C_F: OFCS/OCS network element for PCC-based charging | Huawei, Hisilicon | Approved |
| S2‑131444 | P4C_F: reference point definitions | Huawei, Hisilicon | Approved |
| S2‑131445 | P4C-TI Conclusion | Alcatel-Lucent, AT&T, Ericsson, Huawei, ZTE | Approved |
| S2‑131446 | Add a Summary of the Impacts of solution 1 | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Ericsson, Qualcomm Incorporated | Approved |
| S2‑131447 | Updated PPPoE solution | Motorola Mobility | Approved |
| S2‑131448 | SaMOG TR cleanup | ZTE(Rapporteur) | Approved |
| S2‑131449 | P4C_F: AAA-based accounting | Huawei, Hisilicon | Revised in S2-131548 |
| S2‑131450 | - | - | - |
| S2‑131451 | - | - | - |
| S2‑131452 | - | - | - |
| S2‑131453 | - | - | - |
| S2‑131454 | - | - | - |
| S2‑131455 | - | - | - |
| S2‑131456 | - | - | - |
| S2‑131457 | - | - | - |
| S2‑131458 | - | - | - |
| S2‑131459 | - | - | - |
| S2‑131460 | - | - | - |
| S2‑131461 | - | - | - |
| S2‑131462 | - | - | - |
| S2‑131463 | - | - | - |
| S2‑131464 | - | - | - |
| S2‑131465 | - | - | - |
| S2‑131466 | - | - | - |
| S2‑131467 | - | - | - |
| S2‑131468 | - | - | - |
| S2‑131469 | - | - | - |
| S2‑131470 | - | - | - |
| S2‑131471 | - | - | - |
| S2‑131472 | - | - | - |
| S2‑131473 | - | - | - |
| S2‑131474 | - | - | - |
| S2‑131475 | - | - | - |
| S2‑131476 | Architectural Requirements for ProSe | Renesas Mobile Europe Ltd., Samsung | Approved |
| S2‑131477 | Key issue for ProSe Direct Communication one-to-one and for Relay for Public Safety ProSe | Renesas Mobile Europe Ltd., Qualcomm Inc., LG Electronics, General Dynamic Broadband UK, CATT, Alcatel-Lucent | Approved |
| S2‑131478 | Key Issue - Authorization for ProSe capability feature | Huawei, Hisilicon, Renesas Mobile Europe Ltd., Qualcomm | Approved |
| S2‑131479 | Key Issue on EPC-level ProSe Discovery | Intel, Broadcom Corporation, CATT, III, LG Electronics, Radisys, Sony | Approved |
| S2‑131480 | Key issue for direct discovery | Qualcomm Incorporated, Motorola Mobility, Renesas Mobile Europe Ltd, Samsung?, LG Electronics | Approved |
| S2‑131481 | Three Key Issues: EPC-level ProSe Discovery, EPC Support for WLAN Direct Communications, Service Continuity | Intel, III, Radisys, Sony | Approved |
| S2‑131482 | ProSe service continuity | Qualcomm Incorporated, Intel, III, Sony, Radisys, CATT | Approved |
| S2‑131483 | Key Issue on Group Communication | Intel, General Dynamics Broadband UK, Qualcomm Incorporated | Approved |
| S2‑131484 | Scope for GCSE TR 23.768 | Nokia Siemens Networks | Approved |
| S2‑131485 | GCSE/Multipoint Service Architecture consideration | Nokia Siemens Networks | Revised in S2-131536 |
| S2‑131486 | Resolution of Editor's Note in Solution #3 | Intel | Approved |
| S2‑131487 | Extended ANDSF for load-aware WLAN selection | Samsung | Approved |
| S2‑131488 | Selection of Active ISMP/ISRP rule in Roaming Scenarios | Motorola Mobility, AT&T, Qualcomm Incorporated, Intel | Approved |
| S2‑131489 | Update of Solution 3 for WLAN selection | Motorola Mobility | Approved |
| S2‑131490 | Operator's View on UPCON (Problem Space and Use Case Examples) and Proposed Architectural Requirements | NTT DOCOMO, Orange, KDDI, China Mobile, Verizon, Sprint, AT&T | Revised in S2-131528 |
| S2‑131491 | New key issue on differentiated treatment for non-deducible service data flows in case of RAN user plane congestion | Telecom Italia, Deutsche Telekom, Motorola Mobility, Broadcom Corporation, Nokia | Approved |
| S2‑131492 | RAN User Plane congestion awareness by GTP-U extension | China Mobile, AT&T, Cisco, Samsung, NEC | Approved |
| S2‑131493 | High-level Solution proposal for UPCON based on RAN and CN based Congestion Mitigation | NEC, AT&T, Broadcom Corporation, NTT DOCOMO, China Mobile, Allot Communications, Cisco, KDDI, ZTE, China Telecom, Verizon, Intel | Approved |
| S2‑131494 | Prioritization of IP flows mapped to the same QCI | Telecom Italia, AT&T, Deutsche Telekom, Huawei, Hisilicon, Broadcom Corporation | Approved |
| S2‑131495 | [DRAFT] LS Response to CT WG4 LS (C4-130417) on Inter RAT handover, Inter RAT Release with redirection, Inter RAT Reject with redirection between E-UTRAN and UTRAN/GERAN | SA WG2 | Revised in S2-131526 |
| S2‑131496 | [DRAFT] LS on eNB UE Inactivity Timer Definition and the Usage | SA WG2 | Revised in S2-131527 |
| S2‑131497 | Key Issue for ProSe Identities | InterDigital Communications, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, CATT | Approved |
| S2‑131498 | Push Proxy/Device Agent Function for reducing heartbeat/keep-alive of applications | Huawei, Hisilicon, CATR, Ericsson, ST-Ericsson | Approved |
| S2‑131499 | Eliminate keep-alive package by network-based always-on solution | China Mobile, CATT, China Telecom, ZTE, Huawei | Noted |
| S2‑131500 | Core Network assisted eNB parameters tuning for small data transfer | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, NEC, Samsung, Ericsson?, ST-Ericsson? | Approved |
| S2‑131501 | Update of T5 Triggering | Huawei, HiSilicon, Intel, Nokia Siemens Networks, HTC, ZTE, LG Electronics, Verizon, KT Corp, KPN, China Mobile, Telecom Italia | Approved |
| S2‑131502 | Update the solution of Overload Control for Device Triggering | Huawei, Hisilicon, CATR | Approved |
| S2‑131503 | Small data fast path Establishment | Ericsson, ST-Ericsson | Revised in S2-131534 |
| S2‑131504 | Solution for Group-based ProSe Discovery for Public Safety | Intel | Revised in S2-131535 |
| S2‑131505 | Solution for direct discovery and communication | Qualcomm | Approved |
| S2‑131506 | 23.203 CR0803R2: Correction of PCC based location reporting procedures | Nokia Siemens Networks | Approved |
| S2‑131507 | 23.203 CR0804R2: Correction of PCC based location reporting procedures | Nokia Siemens Networks | Approved |
| S2‑131508 | Updates for T5 Small Data Service | Huawei, HiSilicon, Intel, Nokia Siemens Networks, ZTE, HTC, CATT, LG Electronics, Verizon, KT Corp, KPN, China Mobile | Approved |
| S2‑131509 | Architecture & functional requirements for GCSE_LTE | Qualcomm Incorporated | Approved |
| S2‑131510 | S-GW/P-GW overload prevention | Nokia Siemens Networks | Revised in S2-131547 |
| S2‑131511 | 23.203 CR0783R3: S9 optional at local breakout | Ericsson, ST Ericsson, Telecom Italia | Approved |
| S2‑131512 | 23.203 CR0798R2: S9 optional at local breakout | Ericsson, ST Ericsson, Telecom Italia | Approved |
| S2‑131513 | Solution proposal for Key Issue 2, scenarios 1 and 2 | Qualcomm Incorporated, CATT | Approved |
| S2‑131514 | Timer based solution for the Key Issue 3, Ping Pong Offloading to WLAN | LG Electronics | Approved |
| S2‑131515 | 23.401 CR2521R2: ISR handling in SIPTO at local network | Ericsson, ST-Ericsson | Approved |
| S2‑131516 | 23.002 CR0263R2: Adding SIPTO at the Local Network | LG Electronics | Approved |
| S2‑131517 | 23.401 CR2546R2: Correction to PDN Deactivation for SIPTO@LN | Intel, Cisco | Noted (endorsed) |
| S2‑131518 | 23.401 CR2538R2: Direct user plane path establishment for SIPTO at local network on eNodeB | Huawei, Hisilicon | Approved |
| S2‑131519 | DRAFT Enabling HO restrictions to E-UTRAN for rSRVCC | SA WG2 | Approved |
| S2‑131520 | LS Reply on Clarification of the setting of E-UTRAN Service Handover IE on CS bearer | SA WG2 | Approved |
| S2‑131521 | Reply LS on enhancing IMEI based Lawful Interception in IMS | SA WG2 | Approved |
| S2‑131522 | Reply LS on Proximity Services and Lawful Interception | SA WG2 | Approved |
| S2‑131523 | [DRAFT] LS Reply on proposed Diameter Routing Agent (DRA) enhancements | Ericsson | Revised in S2-131551 |
| S2‑131524 | LS on PCC for convergence (P4C-F) | SA WG2 | Approved |
| S2‑131525 | LS on Application Based Charging | SA WG2 | Approved |
| S2‑131526 | LS Response to CT WG4 LS (C4-130417) on Inter RAT handover, Inter RAT Release with redirection, Inter RAT Reject with redirection between E-UTRAN and UTRAN/GERAN | SA WG2 | Approved |
| S2‑131527 | LS on eNB UE Inactivity Timer Definition and the Usage | SA WG2 | Approved |
| S2‑131528 | Proposed Architectural Requirements for CN-based Solutions for RAN User Plane Congestion | NTT DOCOMO, Orange, KDDI, China Mobile, Verizon, Sprint, AT&T, Ericsson, NEC | Revised in S2-131539 |
| S2‑131529 | 23.060 CR1778R3: Introduction of Operator Group GGSN | Alcatel-Lucent | Approved |
| S2‑131530 | 23.060 CR1779R3: Introduction of Operator Group GGSN | Alcatel-Lucent | Approved |
| S2‑131531 | 23.292 CR0197R3: Support of MTRR feature for T-ADS | Nokia Siemens Networks | Approved |
| S2‑131532 | 23.292 CR0198R3: Support of MTRR feature for T-ADS | Nokia Siemens Networks | Approved |
| S2‑131533 | 23.228 CR1031R3: Adding support for IP-PBX in static Mode | Ericsson, ST-Ericsson | Approved |
| S2‑131534 | Small data fast path Establishment | Ericsson, ST-Ericsson | Approved |
| S2‑131535 | Solution for Group-based ProSe Discovery for Public Safety | Intel | Approved |
| S2‑131536 | GCSE/Multipoint Service Architecture consideration | Nokia Siemens Networks | Approved |
| S2‑131537 | Additional use cases related with GTP-c Overload or related with the need to have a more dynamic GTP-c Load control. | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Verizon, Cisco, CMCC | Revised in S2-131542 |
| S2‑131538 | General Requirements for GTP-c Load / Overload Control | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Verizon, Cisco, CMCC, AT&T | Revised in S2-131543 |
| S2‑131539 | Proposed Architectural Requirements for CN-based Solutions for RAN User Plane Congestion | NTT DOCOMO, Orange, KDDI, China Mobile, Verizon, Sprint, AT&T, Ericsson, NEC, ZTE, Cisco, Alcatel-Lucent, Allot Communications, Broadcom | Approved |
| S2‑131540 | Solving FFS issues of solution #4 'ANDSF-based enhanced I-WLAN selection procedure' | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Huawei, HiSilicon | Revised in S2-131549 |
| S2‑131541 | WLAN-NS Key Issue #4 - Solution | AT&T, Broadcom, Intel, Vodafone | Approved |
| S2‑131542 | Additional use cases related with GTP-c Overload or related with the need to have a more dynamic GTP-c Load control. | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Verizon, Cisco, CMCC | Approved |
| S2‑131543 | General Requirements for GTP-c Load / Overload Control | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Verizon, Cisco, CMCC, AT&T | Approved |
| S2‑131544 | Overload on GTP-C interfaces | Ericsson, ST-Ericsson, Huawei | Approved |
| S2‑131545 | Proposals for IMS_RegCon (To update the living document) | China Mobile (Rapporteur), Ericsson, Huawei, Nokia Siemens, ST-Ericsson, ZTE, Others(?) | Noted |
| S2‑131546 | P4C_F: implementation of revision based on reply from BBF | Huawei, Hisilicon | Approved |
| S2‑131547 | S-GW/P-GW overload prevention | Nokia Siemens Networks | Approved |
| S2‑131548 | P4C_F: AAA-based accounting | Huawei, Hisilicon | Approved |
| S2‑131549 | Solving FFS issues of solution #4 'ANDSF-based enhanced I-WLAN selection procedure' | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Huawei, HiSilicon | Approved |
| S2‑131550 | Response LS on Questions regarding BBAI procedures | SA WG2 | Approved |
| S2‑131551 | LS Reply on proposed Diameter Routing Agent (DRA) enhancements | SA WG2 | Approved |
page generated from database: 2024-04-13 13:51:47