3GPP TDocs (written contributions) at meeting
Meeting: S2-108 - 2015-04-13 to 2015-04-17, San Jose del Cabo
meeting id: S2-108 (click id for more info on this meeting)Click on the Tdoc to open its file.
| TDoc | Title | Source | Remarks |
|---|---|---|---|
| S2‑150699 | Draft Agenda for SA WG2#108 | SA WG2 Chairman | - |
| S2‑150700 | SA WG2 Chairman's Report on TSG SA#67 | SA WG2 Chairman | - |
| S2‑150701 | SA WG2 Specification Adoption | SA WG2 Chairman | - |
| S2‑150702 | Draft Report of SA WG2 meeting #107 | SA WG2 Secretary | - |
| S2‑150703 | TD Handling Report of SA WG2 meeting #107E | SA WG2 Secretary | - |
| S2‑150704 | LS from GSMA PSMC: LS on VoLTE Roaming Architecture | GSMA PSMC | - |
| S2‑150705 | LS from GSMA RILTE: LS to 3GPP on IMS Emergency Session over WLAN | GSMA RILTE | - |
| S2‑150706 | LS from CT WG1: Reply LS on provision of WLAN identifiers for RAN rule | CT WG1 | - |
| S2‑150707 | LS from CT WG1: LS on Addition of proximity services group identifier | CT WG1 | - |
| S2‑150708 | LS from CT WG1: Clarification regarding change of active time value and periodic TAU or RAU timer value for UE supporting PSM | CT WG1 | - |
| S2‑150709 | LS from CT WG1: Reply LS on PLMN reselection for ProSe | CT WG1 | - |
| S2‑150710 | LS from CT WG3: LS Reply to LS related to Mobile VoIP IMS Roaming | CT WG3 | - |
| S2‑150711 | LS from CT WG3: LS on Enable MB2 authorization | CT WG3 | - |
| S2‑150712 | LS from CT WG3: LS on Flow ID supplied by GCS AS | CT WG3 | - |
| S2‑150713 | LS from CT WG3: Reply LS on End-to-end QoS handling of MTSI | CT WG3 | - |
| S2‑150714 | LS from TSG GERAN: LS on New WID on RAN aspects for improvements to CS/PS coordination in GERAN Shared Networks | TSG GERAN | - |
| S2‑150715 | LS from GERAN WG2: LS on extended DRX in idle mode | GERAN WG2 | - |
| S2‑150716 | LS from TSG GERAN: Reply LS on paging for MTC | TSG GERAN | - |
| S2‑150717 | LS from TSG GERAN: Reply LS on MBMS for Message delivery to Group of devices | TSG GERAN | - |
| S2‑150718 | LS from GERAN WG2: Reply LS on Security Framework for Cellular IoT | GERAN WG2 | - |
| S2‑150719 | LS from GERAN WG2: Response LS on work split for Study on Cellular IoT | GERAN WG2 | - |
| S2‑150720 | LS from RAN WG1: Reply LS on Paging for MTC | RAN WG1 | - |
| S2‑150721 | LS from RAN WG1: Response LS on public safety discovery | RAN WG1 | - |
| S2‑150722 | LS from RAN WG2: Reply LS on provision of WLAN identifiers for RAN rule | RAN WG2 | - |
| S2‑150723 | LS from RAN WG2: Reply LS on eMPS-eMLPP in CSFB to GERAN | RAN WG2 | - |
| S2‑150724 | LS from RAN WG2: LS reply on PLMN reselection for ProSe | RAN WG2 | - |
| S2‑150725 | LS from RAN WG2: LS on ProSe direct discovery announcements | RAN WG2 | - |
| S2‑150726 | LS from RAN WG2: LS on SC-PTM transmission | RAN WG2 | - |
| S2‑150727 | LS from RAN WG2: LS reply on support for ProSe one-to-one communication in Release 13 | RAN WG2 | - |
| S2‑150728 | LS from RAN WG3: Response LS on Paging Optimization | RAN WG3 | - |
| S2‑150729 | LS from RAN WG3: Response LS on Support of a mix of IPv4 and IPv6 eNBs and Backhauls in eMBMS | RAN WG3 | - |
| S2‑150730 | LS from RAN WG4: LS on impact of optional preconfigured parameters for D2D out of Network coverage mode | RAN WG4 | - |
| S2‑150731 | LS from TSG RAN: LS on Consequence of RAN WI prioritisation for UPCON work in SA2 | TSG RAN | - |
| S2‑150732 | LS from TSG RAN: LS on D2D off network operations | TSG RAN | - |
| S2‑150733 | LS from SA WG1: Reply LS on eCall implementation in IMS | SA WG1 | - |
| S2‑150734 | LS from SA WG1: Reply LS on end-to-end WebRTC-IMS security | SA WG1 | - |
| S2‑150735 | LS from SA WG1: LS reply on service continuity | SA WG1 | - |
| S2‑150736 | LS from SA WG1: LS on MCPTT core items selection | SA WG1 | - |
| S2‑150737 | LS from SA WG3: LS on end-to-end WebRTC-IMS security | SA WG3 | - |
| S2‑150738 | LS from SA WG3: Reply LS on Security Framework for Cellular IoT | SA WG3 | - |
| S2‑150739 | LS from SA WG3: LS on work split for Study on Cellular IoT | SA WG3 | - |
| S2‑150740 | LS from SA WG4: LS on TR 26.924 Study on improved end-to-end QoS handling | SA WG4 | - |
| S2‑150741 | LS from SA WG4: LS reply on codec support in IMS-WebRTC | SA WG4 | - |
| S2‑150742 | LS from SA WG6: LS on support for ProSe one-to-one communication in Release 13 | SA WG6 | - |
| S2‑150743 | LS from SA WG6: LS on service continuity | SA WG6 | - |
| S2‑150744 | LS from TSG SA: LS on I-WLAN specification maintenance | TSG SA | - |
| S2‑150745 | LS from TSG SA: Reply LS on work split for Study on Cellular IoT | TSG SA | - |
| S2‑150746 | Tutorial for use of the 3G Ultimate TD allocation tools | SA WG2 Secretary | - |
| S2‑150747 | Enhancements to Solution 2 | Ericsson | - |
| S2‑150748 | Evaluation Criteria For Solution 2 | Ericsson | - |
| S2‑150749 | High Level Solution 2 Description | Ericsson | - |
| S2‑150750 | Mandatory use of Geographical Areas | Ericsson, Sprint, Qualcomm Incorporated, LG Electronics, U.S. Department of Commerce, Home Office | - |
| S2‑150751 | LS reply on End to End QoS handling | Ericsson | - |
| S2‑150752 | Monitoring via PCRF | Ericsson | - |
| S2‑150753 | Semantics of the Traffic Steering Policy | Ericsson, AT&T, Nokia Networks, Orange | - |
| S2‑150754 | Clarifications for QoS change of default bearer | Huawei, Hisilicon | - |
| S2‑150755 | Clarifications for QoS change of default bearer | Huawei, Hisilicon | - |
| S2‑150756 | Priority of Default Bearer | Huawei, Hisilicon, Applied Communication Sciences, OEC | - |
| S2‑150757 | Priority of Default Bearer | Huawei, Hisilicon, Applied Communication Sciences, OEC | - |
| S2‑150758 | Solution update for setting up an AS session with required QoS | Huawei, HiSilicon, Alcatel-Lucent, Intel | - |
| S2‑150759 | Solution update for change of chargeable party | Huawei, HiSilicon | - |
| S2‑150760 | Solution update for informing about UE’s connection properties | Huawei, HiSilicon | - |
| S2‑150761 | Solution update for background data transfer | Huawei, HiSilicon, NTT DOCOMO | - |
| S2‑150762 | IOPS network configuration/establishment | General Dynamics UK Ltd. | - |
| S2‑150763 | Clarification of applicable UE mobility procedures | General Dynamics UK Ltd. | - |
| S2‑150764 | Support of public safety services over an IOPS network | General Dynamics UK Ltd. | - |
| S2‑150765 | [DRAFT] LS on support of public safety services over an IOPS network | General Dynamics UK Limited | - |
| S2‑150766 | NBIFOM operation Modes | Verizon, Oracle | - |
| S2‑150767 | APN and group specific NAS Level congestion control | NTT DOCOMO | - |
| S2‑150768 | APN and group specific NAS level congestion control | NTT DOCOMO | - |
| S2‑150769 | Issue for eDRX | Acer Incorporated, ITRI | - |
| S2‑150770 | Discussion of Match report issue for User permission change | Acer Incorporated, ITRI | - |
| S2‑150771 | PCRF obligations at Default EPS Bearer QoS change | Ericsson | - |
| S2‑150772 | PCRF obligations at Default EPS Bearer QoS change | Ericsson | - |
| S2‑150773 | Updates to Annex on PC5 interface | Ericsson | - |
| S2‑150774 | PLMN Selection | Ericsson | - |
| S2‑150775 | IOPS PDN/APN handling | Ericsson | - |
| S2‑150776 | Restriction of UEs not allowed in IOPS PLMN | Ericsson | - |
| S2‑150777 | Discussion on High Latency communication | Ericsson | - |
| S2‑150778 | Conclusions for HL_Com | Ericsson, Qualcomm Incorporated | - |
| S2‑150779 | Clean-up on HL_Com TR | Ericsson | - |
| S2‑150780 | Way forward on DECOR | Ericsson | - |
| S2‑150781 | Introduce the Dedicated Core Network (DECOR) feature | Ericsson | - |
| S2‑150782 | Introduce the Dedicated Core Network (DECOR) feature | Ericsson | - |
| S2‑150783 | Load rebalancing within Dedicated Core Network (DECOR) | Ericsson | - |
| S2‑150784 | Handling of UE-initiated and NW-initiated NBIFOM modes | Ericsson, Huawei, HiSilicon | - |
| S2‑150785 | Updates to solution with policy steering interface | Ericsson, AT&T, KDDI, Nokia Networks, Orange | - |
| S2‑150786 | Call flows for the solution with service steering policy interface | Ericsson | - |
| S2‑150787 | ProSe UE to network Relay & Service continuity solution | Ericsson | - |
| S2‑150788 | Application reporting functionality for FMSS solution | Cisco, Allot Communications, Huawei, HiSilicon, Sprint, Comverse, Sandvine Incoporated, US cellular, Broadcom Corporation | - |
| S2‑150789 | Mandatory functionality over the Sd interface | Cisco, Allot Communications, Sprint, Comverse, Sandvine Incoporated, US cellular, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | - |
| S2‑150790 | Enforcement of traffic steering policy | Cisco, Allot Communications, Huawei, HiSilicon, Sprint, Comverse, Sandvine Incoporated, US cellular, Broadcom Corporation, Alcatel-Lucent and Alcatel-Lucent Shanghai Bell | - |
| S2‑150791 | Procedures, interface details and evaluation details for Sd/Gx based solutions | Allot Communications, Cisco, Huawei, Hisilicon, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, SPRINT, Comverse, Sandvine Incorporated, US Cellular, Broadcom Corporation, Openet Telecom | - |
| S2‑150792 | Steering Rule for Uplink/Downlink Traffic | Huawei, Hisilicon, Cisco, Allot Communications, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Sprint, Comverse, Openet Telecom | - |
| S2‑150793 | Add Location report action into delete bearer procedure | Huawei, HiSilicon | - |
| S2‑150794 | Add Location report action into delete bearer procedure | Huawei, HiSilicon | - |
| S2‑150795 | Infinite loop in rerouting to dedicated networks - discussion | NEC | - |
| S2‑150796 | Rerouting when dedicated network is not available | NEC | - |
| S2‑150797 | Correction to the NAS message rerouting | NEC | - |
| S2‑150798 | Correction to the NAS message rerouting | NEC | - |
| S2‑150799 | Proposed assumption for ProSe Service Continuity | Qualcomm Incorporated, Ericsson, Huawei, U.S. Department of Commerce | - |
| S2‑150800 | Extended DRX in Idle mode | Ericsson | - |
| S2‑150801 | Correcting SM re-activation attempts at PLMN change when only one IP version is supported by the network | TeliaSonera, Ericsson | - |
| S2‑150802 | Correcting SM re-activation attempts at PLMN change when only one IP version is supported by the network | TeliaSonera, Ericsson | - |
| S2‑150803 | Correcting ESM re-activation attempts at PLMN change when only one IP version is supported by the network | TeliaSonera, Ericsson | - |
| S2‑150804 | Correcting ESM re-activation attempts at PLMN change when only one IP version is supported by the network | TeliaSonera, Ericsson | - |
| S2‑150805 | Configuration of extended DRX for connected mode | Ericsson | - |
| S2‑150806 | Solution for Handling of Mobile Terminated Data (Idle mode) | Ericsson | imported from 3GU |
| S2‑150807 | GTP-C re-transmissions (Connected mode) | Ericsson | - |
| S2‑150808 | GTP-C re-transmissions (Idle mode) | Ericsson | - |
| S2‑150809 | Interaction between eDRX and PSM (Power Saving Mode) | Ericsson | - |
| S2‑150810 | Identity used in NAS level congestion control | Ericsson | - |
| S2‑150811 | Identity used in NAS level congestion control | Ericsson | - |
| S2‑150812 | Group Priority | Ericsson | - |
| S2‑150813 | Predictable UE communication pattern | Ericsson | - |
| S2‑150814 | Reflections on monitoring events from MME | Ericsson | imported from 3GU |
| S2‑150815 | Reference Version of FMSS TR 23.718 | Ericsson | - |
| S2‑150816 | Clarification and Evaluation of Policy Based TCF Solution | China Mobile, Broadcom Corporation, CATR, KDDI | - |
| S2‑150817 | Cleanup of the Loss of an Access from a PDN Connection | Huawei, HiSilicon, China Telecom | - |
| S2‑150818 | NBIFOM Indications in Call Flows | Huawei, HiSilicon, China Telecom | - |
| S2‑150819 | Adding Architecture alternative for S2a | Huawei, HiSilicon | - |
| S2‑150820 | Adding Architecture alternative for S2a | Huawei, HiSilicon | - |
| S2‑150821 | Clarification of ePDG selection function | Huawei, HiSilicon | - |
| S2‑150822 | Service Continuity for ProSe | Huawei | - |
| S2‑150823 | Solution for ProSe Group Priority | Huawei | - |
| S2‑150824 | Update of Group Info | Huawei | - |
| S2‑150825 | ProSe Open Discovery Enhancement for Dynamic Metadata | Huawei, Hisilicon | imported from 3GU |
| S2‑150826 | eMBMS traffic relay enhancement | Huawei, HiSilicon | imported from 3GU |
| S2‑150827 | Solution 3 Clarification | China Mobile | - |
| S2‑150828 | ProSe Open Discovery Enhancement for Dynamic Metadata | Huawei, Hisilicon | - |
| S2‑150829 | eMBMS traffic relay enhancement | Huawei, Hisilicon | - |
| S2‑150830 | Discussion on Shortening SRVCC HO voice interruption | Huawei, HiSilicon, China Unicom, Intel | - |
| S2‑150831 | Clarification of CS user plane restoration during SRVCC HO | Huawei, HiSilicon, Intel, China Unicom | - |
| S2‑150832 | Security between Public Safety Ues and Isolated E-UTRAN | Huawei | - |
| S2‑150833 | Notify UE conference event package after SRVCC | Huawei, Hisilicon | - |
| S2‑150834 | Discussion of the UE-initiated NBIFOM | CATT | - |
| S2‑150835 | Solution to the FFS related to SCM | CATT, ZTE, Broadcom Corporation | - |
| S2‑150836 | ProSe Discovery UE ID update | CATT | - |
| S2‑150837 | IP address preservation | CATT | - |
| S2‑150838 | Update of UE attach afresh to the macro EPC procedure | CATT | imported from 3GU |
| S2‑150839 | Update of UE attach afresh to the macro EPC procedure | CATT | - |
| S2‑150840 | Options for delivering network parameters to correct MME | CATT | - |
| S2‑150841 | Optimize EPS bearer management using communication patterns | CATT | - |
| S2‑150842 | Group message delivery function and procedure | Huawei, Hisilicon, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Samsung, KPN | - |
| S2‑150843 | Architecture update for GROUPE | Huawei, Hisilicon, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Intel | - |
| S2‑150844 | Cover Sheet for TR 23.769 for Approval at TSG SA | GROUPE Rapporteurs (Huawei) | - |
| S2‑150845 | GTP-C retransmission in eDRX | Huawei | - |
| S2‑150846 | RAN FS_LTE_SC_PTM consideration within SA2 MBMS_enh scope | Huawei, Hisilicon | - |
| S2‑150847 | LS on SC-PTM transmission feedback | Huawei | - |
| S2‑150848 | Consideration of PCO vs. APCO for S2b NBIFOM parameters Transport (Open issue 5) | ZTE | - |
| S2‑150849 | Clarification of Impacts when Gxx is not used for eHRPD Access | China Telecom, Huawei, HiSilicon | - |
| S2‑150850 | Conclusions for App ID Support | ZTE | - |
| S2‑150851 | Conclusion for keeping “Handover Indication” in the enhanced handover procedure when adding addition access to multi-access PDN connection | ZTE, Huawei(?), HiSilicon(?) | - |
| S2‑150852 | Miscellaneous NBIFOM Editor’s Notes Cleanup | ZTE | - |
| S2‑150853 | Conclusions for NBIFOM Open Issues 6 and 7 | ZTE | - |
| S2‑150854 | AS allowing non-international format Request-URI when RAVEL is used | China Mobile | - |
| S2‑150855 | Notify UE conference event package after SRVCC | Huawei, Hisilicon | - |
| S2‑150856 | AS allowing non-international format Request-URI when RAVEL is used | China Mobile | - |
| S2‑150857 | AS allowing non-international format Request-URI when RAVEL is used | China Mobile | - |
| S2‑150858 | TRF supporting geo-local service number normalization | China Mobile | - |
| S2‑150859 | TRF supporting geo-local service number normalization | China Mobile | - |
| S2‑150860 | TRF supporting geo-local service number normalization | China Mobile | - |
| S2‑150861 | Resolving the Default access negotiation and determination | ZTE | - |
| S2‑150862 | Conclusion for NBIFOM study in Rel-13 | ZTE | - |
| S2‑150863 | Key issues: UE location | Huawei | - |
| S2‑150864 | Solution: How LRF retrieve location information for s2a | Huawei , Hisilicon | - |
| S2‑150865 | Solution: How LRF retrieve location information for s2b | Huawei | - |
| S2‑150866 | Solution: how UE knows its location and how can sent it | Huawei | - |
| S2‑150867 | Architectural Considerations | NTT DOCOMO, AT&T, Alcatel-Lucent, Intel | - |
| S2‑150868 | Clause 5 update | NTT DOCOMO | - |
| S2‑150869 | Reflections on monitoring events from MME | Ericsson | - |
| S2‑150870 | Solution 2 update | NTT DOCOMO | - |
| S2‑150871 | AESE – Solution 5 Corrections and Evaluations | NEC | - |
| S2‑150872 | Update to PSM to support monitoring events | Huawei, HiSilicon, Intel | - |
| S2‑150873 | Update to PSM to support monitoring events | Huawei, HiSilicon, Intel | - |
| S2‑150874 | Update to PSM to support monitoring events | Huawei, HiSilicon, Intel | - |
| S2‑150875 | Introduction of monitoring procedures | Huawei, HiSilicon, Intel, Alcatel-Lucent | - |
| S2‑150876 | Introduction of monitoring event removal and recall procedures | Huawei, HiSilicon | - |
| S2‑150877 | Architectural updates for Monitoring feature | Intel, Alcatel-Lucent, Huawei | - |
| S2‑150878 | Monitoring Feature Description | Intel, Huawei, Alcatel-Lucent | - |
| S2‑150879 | Support for Monitoring Events | Intel | - |
| S2‑150880 | Support for Monitoring Events | Intel | - |
| S2‑150881 | Resolution of the open issue in Model B Discovery | Huawei, HiSilicon | - |
| S2‑150882 | Conclusion Supplements on ProSe Restricted Discovery | Huawei, HiSilicon | - |
| S2‑150883 | Clarification on the Configurations in Service Authorization | Huawei, HiSilicon | - |
| S2‑150884 | Clarification on geo-local number handling | China Mobile, NTT DOCOMO | - |
| S2‑150885 | Reference update | China Mobile | - |
| S2‑150886 | Obtaining ProSe Discovery info Public Safety discovery | Qualcomm Incorporated | - |
| S2‑150887 | APN information in ProSe UE-NW Relay discovery | Qualcomm Incorporated | imported from 3GU |
| S2‑150888 | Support for ProSe in multicarrier across PLMNs | Qualcomm Incorporated, Ericsson | - |
| S2‑150889 | Updating SRVCC operation possible in E-UTRAN | Qualcomm Incorporated, Huawei, HiSilicon | - |
| S2‑150890 | Codecs for WebRTC | Qualcomm Incorporated, Telecom Italia, BlackBerry UK Limited, Nokia Networks | - |
| S2‑150891 | Codecs for WebRTC | Qualcomm Incorporated, Telecom Italia, BlackBerry UK Limited, Nokia Networks | - |
| S2‑150892 | ProSe Group Priority | Qualcomm Incorporated | - |
| S2‑150893 | ProSe QoS | Qualcomm Incorporated | - |
| S2‑150894 | Update of SRVCC capability | Qualcomm Incorporated, Huawei, HiSilicon | - |
| S2‑150895 | Removal of long expired reference to draft-kaplan-enum-sip-routing | BlackBerry | - |
| S2‑150896 | Removal of long expired reference to draft-kaplan-enum-sip-routing | BlackBerry | - |
| S2‑150897 | Removal of long expired reference to draft-kaplan-enum-sip-routing | BlackBerry | - |
| S2‑150898 | Removal of long expired reference to draft-kaplan-enum-sip-routing | BlackBerry | - |
| S2‑150899 | Correction of WIC definition | BlackBerry UK Limited | - |
| S2‑150900 | Correction of WIC definition | BlackBerry UK Limited | - |
| S2‑150901 | Draft Reply LS on “Clarification regarding change of active time value and periodic TAU or RAU timer value for UE supporting PSM” | LG Electronics Inc. | - |
| S2‑150902 | Solution Updates on Solution 3 | LG Electronics | - |
| S2‑150903 | Solution Updates on Solution 5 | LG Electronics | - |
| S2‑150904 | New issue for idle mode eDRX: Maximizing Idle Period in regard to period TAU | LG Electronics | - |
| S2‑150905 | Procedures for solution in section 6.1.4 | China Unicom, Intel | - |
| S2‑150906 | Solution for idle mode eDRX: Adjustable execution of P-TAU for further power saving | LG Electronics | - |
| S2‑150907 | Update the solution 2.1 of semantics of traffic steering policy in section 6.2 | Intel, China Unicom | - |
| S2‑150908 | Further description on avoiding SRVCC trigger | Samsung | - |
| S2‑150909 | Reply LS on addition of proximity services group identifier | QUALCOMM UK Ltd | - |
| S2‑150910 | Handling of PSM timer | HTC | - |
| S2‑150911 | Handling of PSM timer | HTC | - |
| S2‑150912 | Consideration on "WLAN offloadability” indication provided via NAS | LG Electronics | - |
| S2‑150913 | NBIFOM Suspend/Resume Procedures | LG Electronics | - |
| S2‑150914 | Co-existence with RAN rule solution in case of an access loss | LG Electronics | - |
| S2‑150915 | Update of MME load balancing for Dedicated Core Networks | Huawei, HiSilicon | - |
| S2‑150916 | Update of load balancing functionality for DECOR | Huawei, HiSilicon | - |
| S2‑150917 | Discussion on various aspects | Huawei, HiSilicon | - |
| S2‑150918 | ProSe APN Configuration | Huawei, HiSilicon | - |
| S2‑150919 | ProSe APN Configuration | Huawei, HiSilicon | - |
| S2‑150920 | Solutions for the location related Key Issue | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | - |
| S2‑150921 | Discussion on whether DÉCOR applies to Gn-SGSN | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | - |
| S2‑150922 | New UE-initiated update procedures for Open Direct Discovery | Qualcomm Incorporated | - |
| S2‑150923 | Conclusions for Model B discovery | Qualcomm Incorporated | - |
| S2‑150924 | Metadata upload for Open and Restricted Discovery | Qualcomm Incorporated | - |
| S2‑150925 | UE-to-Network Relay conclusions | Qualcomm Incorporated | - |
| S2‑150926 | Proximity estimation | Qualcomm Incorporated | - |
| S2‑150927 | Introduce the Dedicated Core Network (DECOR) feature | NTT DOCOMO, Huawei | - |
| S2‑150928 | Introduce the Dedicated Core Network (DECOR) feature | NTT DOCOMO, Huawei | - |
| S2‑150929 | Discussion on intra-DECOR offloading | NTT DOCOMO, Huawei | - |
| S2‑150930 | Intra-decor MME offloading | NTT DOCOMO | - |
| S2‑150931 | Introduce the Dedicated Core Network (DECOR) feature of intra-DECOR offloading | NTT DOCOMO | imported from 3GU |
| S2‑150932 | WID update on DECOR | NTT DOCOMO | - |
| S2‑150933 | [DRAFT] Request specification of Dedicated Core Network (DECOR) feature | NTT DOCOMO | - |
| S2‑150934 | [DRAFT] Request for specification of Dedicated Core Network (DECOR) feature | NTT DOCOMO | imported from 3GU |
| S2‑150935 | Adding ProSe related introductions and definitions | Qualcomm Incorporated | - |
| S2‑150936 | Introducing HSS-SCEF and MME/SGSN-SCEF Reference Points | Intel, Huawei, Alcatel-Lucent | - |
| S2‑150937 | Solution 4 - Corrections and Evaluation | Alcatel-Lucent, Intel | - |
| S2‑150938 | AESE – Solution 5 Corrections and Evaluations | Alcatel-Lucent | - |
| S2‑150939 | AESE – Solution 6 Evaluation | Alcatel-Lucent, Cisco Systems Inc | - |
| S2‑150940 | AESE – Solution 8 Evaluation | Alcatel-Lucent | - |
| S2‑150941 | AESE - Evaluation | Alcatel-Lucent | - |
| S2‑150942 | AESE - Conclusions | Alcatel-Lucent, Intel | - |
| S2‑150943 | GROUPE Conclusions | Alcatel-Lucent | - |
| S2‑150944 | Remove Editor’s Notes | Alcatel-Lucent | - |
| S2‑150945 | [DRAFT] LS on APIs for using MBMS | Alcatel-Lucent | - |
| S2‑150946 | Solution A for Key Issue 1 | Alcatel-Lucent, Nokia Networks | - |
| S2‑150947 | Solution 1 – Impacts and Evaluation | Alcatel-Lucent | - |
| S2‑150948 | HLCom – Solution 4 – add SCEF, additional evaluation text | Alcatel-Lucent | - |
| S2‑150949 | HLCom – Solution 6 impacts and evaluation | Alcatel-Lucent | - |
| S2‑150950 | eDRX – Idle Mode Issue 2: Solution A | Alcatel-Lucent, Qualcomm Incorporated | - |
| S2‑150951 | MBMS Session Start procedure correction and editorial corrections | China Telecom | - |
| S2‑150952 | OMR handling of SDP offer-answer exchanges after media path has been selected | Nokia Networks, Ericsson | - |
| S2‑150953 | OMR handling of SDP offer-answer exchanges after media path has been selected | Nokia Networks, Ericsson | - |
| S2‑150954 | OMR handling of SDP offer-answer exchanges after media path has been selected | Nokia Networks, Ericsson | - |
| S2‑150955 | OMR handling of SDP offer-answer exchanges after media path has been selected | Nokia Networks, Ericsson | - |
| S2‑150956 | High Level Description Solution 3 | Nokia Networks, Huawei | - |
| S2‑150957 | Support of Procedures requiring the IMSI | Nokia Networks | - |
| S2‑150958 | Potential reduction of scope of the WID | Nokia Networks | - |
| S2‑150959 | Resiliency Aspects for Solution 3 | Nokia Networks | - |
| S2‑150960 | Evaluation of Solution 3 +5 | Nokia Networks, Huawei | - |
| S2‑150961 | Text for the Overall Evaluation Section | Nokia Networks | - |
| S2‑150962 | Skeletton and scope for TR 23.771 (FS_SEW) | Alcatel-Lucent, Alcatel-Lucent ShangHai Bell | - |
| S2‑150963 | Evaluation Comparison of Solutions in Section 5 | T-Mobile USA | - |
| S2‑150964 | Key issues: UE Location Information | T-Mobile USA | - |
| S2‑150965 | First list of Key issues: AAA server knowledge of emergency & Location | Alcatel-Lucent, Alcatel-Lucent ShangHai Bell, Qualcom Inc | - |
| S2‑150966 | Key issue: QoS | Alcatel-Lucent, Alcatel-Lucent ShangHai Bell | - |
| S2‑150967 | A solution for ePDG selection | Alcatel-Lucent, Alcatel-Lucent ShangHai Bell | - |
| S2‑150968 | Update to the SID on Feasibility study on the Support of Emergency services over WLAN | Alcatel-Lucent, Alcatel-Lucent ShangHai Bell | - |
| S2‑150969 | Handling of UE-initiated and NW-initiated NBIFOM modes | Alcatel-Lucent, Alcatel-Lucent ShangHai Bell, Verizon, Broadcom Corporation | - |
| S2‑150970 | Clarification on Solution 1 in § 5.2: forking | Alcatel-Lucent, Alcatel-Lucent ShangHai Bell | - |
| S2‑150971 | Clarification on Solution 1 in § 5.2: routing of terminating sessions | Alcatel-Lucent, Alcatel-Lucent ShangHai Bell | - |
| S2‑150972 | Clarification on Solution 1 in § 5.2: scalability and service resiliency | Alcatel-Lucent, Alcatel-Lucent ShangHai Bell | - |
| S2‑150973 | Evaluation Criteria For Solution 5.2.1 | Alcatel-Lucent, Alcatel-Lucent ShangHai Bell | - |
| S2‑150974 | Reduction of eWebRTCi scope | Alcatel-Lucent, Alcatel-Lucent ShangHai Bell | - |
| S2‑150975 | Modifications to issues for extended DRX | Qualcomm Incorporated, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | - |
| S2‑150976 | Extended I-DRX and PSM coexistence | Qualcomm Incorporated | - |
| S2‑150977 | RAN and CN coordination for extended C-DRX (Issue 1) | Qualcomm Incorporated | - |
| S2‑150978 | Extended C-DRX: New connected mode substate in the core network to handle NAS retransmissions and MT SMS (Issues 2 and 3) | Qualcomm Incorporated | - |
| S2‑150979 | GROUPE Conclusions | Qualcomm Incorporated | - |
| S2‑150980 | [DRAFT] LS on RAN assumptions from SA2 for FS_eDRX | Qualcomm Incorporated | - |
| S2‑150981 | [DRAFT] Reply LS on Clarification regarding change of active time value and periodic TAU or RAU timer value for UE supporting PSM | Qualcomm Incorporated | - |
| S2‑150982 | Consideration for the GCSE_LTE Architecture to include the ProSe UE-Network Relay | U.S. Department of Commerce | - |
| S2‑150983 | MCC CR Implementation correction: Group specific NAS Level congestion control | MCC | - |
| S2‑150984 | Removing alternatives from S2b call flows | Apple Inc. | - |
| S2‑150985 | Discussion on _x00B_S8HR VoLTE Roaming | NTT DOCOMO INC. | - |
| S2‑150986 | [DRAFT] Reply LS on VoLTE Roaming Architecture | NTT DOCOMO INC. | - |
| S2‑150987 | Conclusions for indication of 3GPP access loss in SCM | LG Electronics | - |
| S2‑150988 | Proposed Solution for Key Issue 1 using Application-level Zones | Motorola Solutions | - |
| S2‑150989 | Discussion on unauthenticated IMS Emergency Call | NTT DOCOMO INC. | - |
| S2‑150990 | Update of the solution using IP multicast in the UE-to-NW Relay | Nokia Networks | - |
| S2‑150991 | Enable ISR for PS-only UE | CATT | - |
| S2‑150992 | Correction of IMS Emergency Call without IMS emergency registration | NTT DOCOMO | - |
| S2‑150993 | Per-PLMN configuration in P-CSCF for Non UE Detectable Emergency Call Handling | NTT DOCOMO | - |
| S2‑150994 | Enable ISR for PS-only UE | CATT | - |
| S2‑150995 | Support of Session Continuity with UE-Network Relays | Nokia Networks | - |
| S2‑150996 | Removing alternatives from S2a call flows | Apple Inc., Huawei, Hisilicon | - |
| S2‑150997 | Supporting a roaming scenario where ATCF/ATGW in HPLMN | NTT DOCOMO | - |
| S2‑150998 | Corrections in ProSe UE-NW Relay discovery | Nokia Networks, Qualcomm Incorporated | - |
| S2‑150999 | Clarification of the meaning of 'VPLMN Address Allowed' flag | NTT DOCOMO | - |
| S2‑151000 | Netloc for IMS Registration | NTT DOCOMO | - |
| S2‑151001 | Clarification regarding change of active time value and periodic TAU or RAU timer value for UE supporting PSM | HTC Corporation | - |
| S2‑151002 | LS response on “Flow ID supplied by GCS AS” | Motorola Solutions Germany | - |
| S2‑151003 | Problems and solutions for Co-existing of 'SMSoverSGs', 'SMSinSGSN', 'SMSinMME' | CATT | - |
| S2‑151004 | LS response for SC-PTM transmission | Motorola Solutions Germany | - |
| S2‑151005 | Clarification on MBMS based solution | ZTE | - |
| S2‑151006 | Mapping Geographic Area to MBMS SAI and Cell IDs | ZTE | - |
| S2‑151007 | Discussion on the how to avoid SRVCC | ZTE | - |
| S2‑151008 | Clarification to the solution 4 | ZTE | - |
| S2‑151009 | Way forward on the key issue - Architectural aspects for minimizing the need for bearer level protocol conversion | ZTE | - |
| S2‑151010 | Service Continuity via a ProSe UE-to-Network Relay | LG Electronics | - |
| S2‑151011 | Radio resource usage for Stateless ProSe UE-to-UE Relay | LG Electronics | - |
| S2‑151012 | Alternative proposal for monitoring event configuration procedure to cover removal/replace | LG Electronics | - |
| S2‑151013 | Need for more reliable MBMS signalling for Public Safety | Motorola Solutions | - |
| S2‑151014 | A clarification for Gx based solution | China Unicom, China Telecom, Intel | imported from 3GU |
| S2‑151015 | LS from GSMA RAG: LS on VoLTE Roaming Architecture (Reply to 'LS related to Mobile VoIP IMS Roaming' / S3i150073) | GSMA RAG | - |
| S2‑151016 | Authorisation update: Additional info in context of announcing UE | Samsung | - |
| S2‑151017 | Correction to Monitor request procedure with application controlled extension | Samsung | - |
| S2‑151018 | Destination address for one-to-one communication | Samsung | - |
| S2‑151019 | Inform monitoring UE of PLMNs to monitor | Samsung | - |
| S2‑151020 | Update of MBMS design requirements for Public Safety | Motorola Solutions | - |
| S2‑151021 | Use of Group Info/Connectivity Info in UE2NW Relay discovery | Samsung | - |
| S2‑151022 | Proposal for evaluation categorization for Scenario A of FS_HLCom | Qualcomm Incorporated | - |
| S2‑151023 | Clarification of ProSe Layer 2 Group ID provisioning | Samsung | - |
| S2‑151024 | Correction for consistency description | Samsung | - |
| S2‑151025 | Mobility management considering IOPS operation | Samsung | - |
| S2‑151026 | way forward on some unsolved FFS issues | Samsung | - |
| S2‑151027 | ProSe Discovery UE ID Renewal | Huawei, HiSilicon | imported from 3GU |
| S2‑151028 | Coarse proximity estimation | Deutsche Telekom | - |
| S2‑151029 | Way forward on ProSe communications Priority | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Intel | - |
| S2‑151030 | Way forward on UE to UE relays | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | - |
| S2‑151031 | Closing Editor’s notes in Solution 8 | Intel | - |
| S2‑151032 | Resolve FFS for UE-to-Network Relay Discovery | HTC | - |
| S2‑151033 | Resolve FFS for IP Multicast on Relay | HTC | - |
| S2‑151034 | Discovery and association to Local EPC | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | - |
| S2‑151035 | FS_HLCom conclusion | Intel | - |
| S2‑151036 | Solution to provide ECGI and SAI over GC1 interface | Nokia Networks | - |
| S2‑151037 | Proposals for Open ProSe Direct Discovery Enhancement | HTC | - |
| S2‑151038 | FS_HLCom conclusion (pCR) | Intel | - |
| S2‑151039 | Support of NB_IFOM for S2a SCM | Qualcomm Incorporated | - |
| S2‑151040 | General Key Issues: Proposed Assumptions for phase 1 | Qualcomm Incorporated, Alcatel Lucent, Alcatel Lucent Shanghai Bell | - |
| S2‑151041 | Key Issues on Connectivity Establishment | Qualcomm Incorporated | - |
| S2‑151042 | Solution for Key Issues on Location Information | Qualcomm Incorporated | - |
| S2‑151043 | Key Issues on Location Information | Qualcomm Incorporated | - |
| S2‑151044 | SC-PTM Architecture | Qualcomm Incorporated | - |
| S2‑151045 | Cover Sheet for TR 23.708 for Approval at TSG SA | AESE Rapporteurs (Intel) | - |
| S2‑151046 | On MME control on number of DL packets to be stored in SGW | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | - |
| S2‑151047 | MBMS bearer establishment with ECGI list | Nokia Networks, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | - |
| S2‑151048 | Changes to content of Connectivity Info for UE-to-Network Relay Discovery | ITRI | - |
| S2‑151049 | MBMS bearer establishment with ECGI list | Nokia Networks, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | - |
| S2‑151050 | Enhanced proximity estimation with logged location information | NEC | - |
| S2‑151051 | On ProSe UE ID and ProSe Layer-2 Group ID format (preventing future backwards compatibility issues) | Intel | - |
| S2‑151052 | Solution to address interaction between eDRX and PSM | Nokia Networks | - |
| S2‑151053 | Solution for FMSS: Signalling procedures for supporting traffic steering policy solicitation over St interface | KDDI, ZTE | - |
| S2‑151054 | DL data transmission from an AS to an out-of-network coverage PS terminal via UE-Network Relay | ITRI | - |
| S2‑151055 | Component of Traffic Steering Policy over St interface | KDDI, ZTE | - |
| S2‑151056 | Clarification on ProSe UE ID and ProSe Layer-2 Group ID | Intel | - |
| S2‑151057 | Remove FFS in Clause 7.4.4 | ITRI | - |
| S2‑151058 | Stateful ProSe UE-to-UE Relay | Intel | - |
| S2‑151059 | Layer-2 ID Uniqueness for One-to-One Direct Communication | ITRI | - |
| S2‑151060 | Way forward on ProSe service continuity | Intel, Alcatel-Lucent, BlackBerry UK Ltd | - |
| S2‑151061 | Fixes to Public Safety Discovery procedures | Intel | - |
| S2‑151062 | Permission of location reporting | NEC | - |
| S2‑151063 | User consent handling during UE Registration | NEC | - |
| S2‑151064 | Solution for GUTI Sync issue for DECOR | NTT DOCOMO INC. | - |
| S2‑151065 | UE Usage Type clarifications | NEC | - |
| S2‑151066 | Solution principles for S2b | Intel | - |
| S2‑151067 | UE Usage Type clarifications | NEC | imported from 3GU |
| S2‑151068 | Group based NAS Level congestion control for multiple APNs | NEC | - |
| S2‑151069 | Group based NAS Level congestion control for multiple APNs | NEC | - |
| S2‑151070 | Conclusions on ProSe UE-to-UE Relay | Intel | - |
| S2‑151071 | Conclusion for key issue 6 | China Mobile | - |
| S2‑151072 | Procedures of TCF Solution | China Mobile, CATR | - |
| S2‑151073 | Resolution of Editor's note in clause 7.2.2.4 | Intel | - |
| S2‑151074 | Paging priority and ARP Priority level: extension of CR2812r2 to CR2840r2 | Rapporteur (Vodafone) | - |
| S2‑151075 | A clarification for Gx or Sd based solution | China Unicom, China Telecom, Intel | - |
| S2‑151076 | Discussion on the support of QoS in trusted and untrusted WLAN | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Broadcom Corporation | - |
| S2‑151077 | Draft Response to Reply LS on Security Framework for Cellular IoT | VODAFONE Group Plc | - |
| S2‑151078 | Cleanup for Solution: Use of MBMS for Group Message Delivery | Samsung | - |
| S2‑151079 | NNSF and initial UE message population | Samsung | - |
| S2‑151080 | Correction in the HSS-initiated CN reselection | Samsung | - |
| S2‑151081 | Correction in the HSS-initiated CN reselection | Samsung | - |
| S2‑151082 | Stage 2 cleanup regarding the WIC registration with a security token | Samsung | - |
| S2‑151083 | MBMS Congestion Mitigation for Rel-13 | Motorola Solutions | - |
| S2‑151084 | Stage 2 cleanup regarding the WIC registration with a security token | Samsung | - |
| S2‑151085 | MBMS broadcast area and cell identities | General Dynamics UK Ltd. | - |
| S2‑151086 | [DRAFT] Response LS on SC-PTM transmission | General Dynamics UK Limited | - |
| S2‑151087 | Updating solutions 2 and 6 | Huawei, HiSilicon | - |
| S2‑151088 | MS Info Change Reporting Action at change of Serving Node (MME <--> SGSN): Update of call Flows | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | - |
| S2‑151089 | MS Info Change Reporting Action at change of Serving Node (MME <--> SGSN): Update of call Flows | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | - |
| S2‑151090 | Avoiding SRVCC in case of webRTC calls | Alcatel-Lucent, Alcatel-Lucent ShangHai Bell | - |
| S2‑151091 | Draft Response to Reply LS on paging for MTC | VODAFONE Group Plc | - |
| S2‑151092 | Key Issue proposal: Routing of Session Start/Stop/Update Request messages to valid nodes | Samsung | - |
| S2‑151093 | [DRAFT] Reply LS on paging for MTC | Samsung | - |
| S2‑151094 | Additional SA WG2 #110ah Meeting Proposal | SA WG2 Chairman | - |
| S2‑151095 | LS from GSMA RiLTE: LS on ePDG selection when UE is roaming | GSMA RiLTE | - |
| S2‑151096 | [DRAFT] LS on SC-PTM transmission feedback | SA WG2 | - |
| S2‑151097 | Solution A for Key Issue 1 | Alcatel-Lucent, Nokia Networks | - |
| S2‑151098 | MBMS broadcast area and cell identities | General Dynamics UK Ltd. | - |
| S2‑151099 | Key Issue proposal: Routing of Session Start/Stop/Update Request messages to valid nodes | Samsung | - |
| S2‑151100 | [DRAFT] LS on Flow ID supplied by GCS AS | SA WG2 | - |
| S2‑151101 | MBMS broadcast area and cell identities | General Dynamics UK Ltd. | - |
| S2‑151102 | LS on SC-PTM transmission feedback | SA WG2 | - |
| S2‑151103 | Key Issue proposal: Routing of Session Start/Stop/Update Request messages to valid nodes | Samsung | - |
| S2‑151104 | Solution A for Key Issue 1 | Alcatel-Lucent, Nokia Networks | - |
| S2‑151105 | Reserved for Curt's parallel sessions | - | imported from 3GU |
| S2‑151106 | Codecs for WebRTC | Qualcomm Incorporated, Telecom Italia, BlackBerry UK Limited, Nokia Networks | - |
| S2‑151107 | Codecs for WebRTC | Qualcomm Incorporated, Telecom Italia, BlackBerry UK Limited, Nokia Networks | - |
| S2‑151108 | Stage 2 cleanup regarding the WIC registration with a security token | Samsung | - |
| S2‑151109 | Stage 2 cleanup regarding the WIC registration with a security token | Samsung | - |
| S2‑151110 | Updating SRVCC operation possible in E-UTRAN | Qualcomm Incorporated, Huawei, HiSilicon | - |
| S2‑151111 | Notify UE conference event package after SRVCC | Huawei, Hisilicon | - |
| S2‑151112 | Notify UE conference event package after SRVCC | Huawei, Hisilicon | - |
| S2‑151113 | Reserved for Gyuri's parallel sessions | - | imported from 3GU |
| S2‑151114 | Updating SRVCC operation possible in E-UTRAN | Qualcomm Incorporated, Huawei, HiSilicon, Samsung | - |
| S2‑151115 | Reserved for Gyuri's parallel sessions | - | imported from 3GU |
| S2‑151116 | Reserved for Gyuri's parallel sessions | - | imported from 3GU |
| S2‑151117 | Reserved for Gyuri's parallel sessions | - | imported from 3GU |
| S2‑151118 | Reserved for Gyuri's parallel sessions | - | imported from 3GU |
| S2‑151119 | Reserved for Gyuri's parallel sessions | - | imported from 3GU |
| S2‑151120 | Reserved for Gyuri's parallel sessions | - | imported from 3GU |
| S2‑151121 | [DRAFT] Reply LS on VoLTE Roaming Architecture | NTT DOCOMO INC. | imported from 3GU |
| S2‑151122 | Clarification on geo-local number handling | China Mobile, NTT DOCOMO | imported from 3GU |
| S2‑151123 | TRF supporting geo-local service number normalization | China Mobile | - |
| S2‑151124 | TRF supporting geo-local service number normalization | China Mobile | - |
| S2‑151125 | TRF supporting geo-local service number normalization | China Mobile | - |
| S2‑151126 | Reserved for Krisztian's parallel sessions | - | imported from 3GU |
| S2‑151127 | Reserved for Krisztian's parallel sessions | - | imported from 3GU |
| S2‑151128 | Reserved for Krisztian's parallel sessions | - | imported from 3GU |
| S2‑151129 | Reserved for Krisztian's parallel sessions | - | imported from 3GU |
| S2‑151130 | Reserved for Krisztian's parallel sessions | - | imported from 3GU |
| S2‑151131 | Handling of PSM timer | HTC, Spreadtrum Communications, Qualcomm Incorporated, LG Electronics, Ericsson | - |
| S2‑151132 | Handling of PSM timer | HTC, Spreadtrum Communications, Qualcomm Incorporated, LG Electronics, Ericsson | - |
| S2‑151133 | [DRAFT] Reply LS on Clarification regarding change of active time value and periodic TAU or RAU timer value for UE supporting PSM | Qualcomm Incorporated | - |
| S2‑151134 | Add Location report action into delete bearer procedure | Huawei, HiSilicon | - |
| S2‑151135 | Enable ISR for PS-only UE | CATT | - |
| S2‑151136 | Enable ISR for PS-only UE | CATT | - |
| S2‑151137 | Paging priority and ARP Priority level: extension of CR2812r2 to CR2840r2 | Vodafone | - |
| S2‑151138 | MBMS Session Start procedure correction and editorial corrections | China Telecom | - |
| S2‑151139 | Support for ProSe in multicarrier across PLMNs | Qualcomm Incorporated, Ericsson | - |
| S2‑151140 | Solution update for setting up an AS session with required QoS | Huawei, HiSilicon, Alcatel-Lucent, Intel, China Mobile | - |
| S2‑151141 | AESE - Solution 6 Evaluation | Alcatel-Lucent, Cisco Systems Inc | - |
| S2‑151142 | Solution update for background data transfer | Huawei, HiSilicon, NTT DOCOMO | - |
| S2‑151143 | Reserved for Puneet's parallel sessions | - | imported from 3GU |
| S2‑151144 | Reserved for Puneet's parallel sessions | - | imported from 3GU |
| S2‑151145 | Enable ISR for PS-only UE | CATT | - |
| S2‑151146 | Application reporting functionality for FMSS solution | Cisco, Allot Communications, Huawei, HiSilicon, Sprint, Comverse, Sandvine Incoporated, US cellular, Broadcom Corporation | - |
| S2‑151147 | Updates to solution with policy steering interface | Ericsson, AT&T, KDDI, Nokia Networks | - |
| S2‑151148 | Procedures, interface details and evaluation details for Sd/Gx based solutions | Allot Communications, Cisco, Huawei, Hisilicon, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, SPRINT, Comverse, Sandvine Incorporated, US Cellular, Broadcom Corporation, Openet Telecom | - |
| S2‑151149 | A clarification for Gx or Sd based solution | China Unicom, China Telecom, Intel | imported from 3GU |
| S2‑151150 | Mandatory functionality over the Sd interface | Cisco, Allot Communications, Sprint, Comverse, Sandvine Incoporated, US cellular, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | - |
| S2‑151151 | Reduction of eWebRTCi scope | Alcatel-Lucent, Alcatel-Lucent ShangHai Bell | - |
| S2‑151152 | Clarification on Solution 1 in 5.2: scalability and service resiliency | Alcatel-Lucent, Alcatel-Lucent ShangHai Bell | - |
| S2‑151153 | Enhancements to Solution 2 | Ericsson | - |
| S2‑151154 | Evaluation of "ePSM" proposal in FS_Hlcom | Qualcomm Incorporated, LGE | - |
| S2‑151155 | Clean-up on HL_Com TR | Ericsson | - |
| S2‑151156 | GROUPE Conclusions | Qualcomm Incorporated | - |
| S2‑151157 | Remove Editor's Notes | Alcatel-Lucent | - |
| S2‑151158 | Clarification on MBMS based solution | ZTE | imported from 3GU |
| S2‑151159 | Cover Sheet for TR 23.769 for Approval at TSG SA | GROUPE Rapporteurs (Huawei) | - |
| S2‑151160 | Group message delivery function and procedure | Huawei, Hisilicon, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Samsung, KPN | - |
| S2‑151161 | Procedures of TCF Solution | China Mobile, CATR | - |
| S2‑151162 | Enforcement of traffic steering policy | Cisco, Allot Communications, Huawei, HiSilicon, Sprint, Comverse, Sandvine Incoporated, US cellular, Broadcom Corporation, Alcatel-Lucent and Alcatel-Lucent Shanghai Bell | - |
| S2‑151163 | Clarification and Evaluation of Policy Based TCF Solution | China Mobile, Broadcom Corporation, CATR, KDDI | - |
| S2‑151164 | Call flows for the solution with service steering policy interface | Ericsson | - |
| S2‑151165 | Procedures of TCF Solution | China Mobile, CATR | - |
| S2‑151166 | Semantics of the Traffic Steering Policy | Ericsson, AT&T, Nokia Networks | - |
| S2‑151167 | Clarification to the solution 4 | ZTE | - |
| S2‑151168 | Evaluation Criteria For Solution 5.2.1 | Alcatel-Lucent, Alcatel-Lucent ShangHai Bell | - |
| S2‑151169 | Evaluation Criteria For Solution 2 | Ericsson | - |
| S2‑151170 | Evaluation of Solution 3 +5 | Nokia Networks, Huawei | - |
| S2‑151171 | Evaluation Comparison of Solutions in Section 5 | T-Mobile USA | - |
| S2‑151172 | APN and group specific NAS Level congestion control | NTT DOCOMO | - |
| S2‑151173 | APN and group specific NAS level congestion control | NTT DOCOMO | - |
| S2‑151174 | Cleanup for Solution: Use of MBMS for Group Message Delivery | Samsung | - |
| S2‑151175 | Updating solutions 2 and 6 | Huawei, HiSilicon | - |
| S2‑151176 | Conclusions for HL_Com | Ericsson, Qualcomm Incorporated | - |
| S2‑151177 | HLCom - Solution 4 - add SCEF, additional evaluation text | Alcatel-Lucent | - |
| S2‑151178 | Solution Updates on Solution 3 | LG Electronics | - |
| S2‑151179 | Steering Rule for Uplink/Downlink Traffic | Huawei, Hisilicon, Cisco, Allot Communications, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Sprint, Comverse, Openet Telecom | - |
| S2‑151180 | Application reporting functionality for FMSS solution | Cisco, Allot Communications, Huawei, HiSilicon, Sprint, Comverse, Sandvine Incoporated, US cellular, Broadcom Corporation | - |
| S2‑151181 | Procedures, interface details and evaluation details for Sd/Gx based solutions | Allot Communications, Cisco, Huawei, Hisilicon, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, SPRINT, Comverse, Sandvine Incorporated, US Cellular, Broadcom Corporation, Openet Telecom | - |
| S2‑151182 | Mandatory functionality over the Sd interface | Cisco, Allot Communications, Sprint, Comverse, Sandvine Incoporated, US cellular, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | - |
| S2‑151183 | Enforcement of traffic steering policy | Cisco, Allot Communications, Huawei, HiSilicon, Sprint, Comverse, Sandvine Incoporated, US cellular, Broadcom Corporation, Alcatel-Lucent and Alcatel-Lucent Shanghai Bell, Openet Telecom | - |
| S2‑151184 | Discussion on the how to avoid SRVCC | ZTE | - |
| S2‑151185 | Way forward on the key issue - Architectural aspects for minimizing the need for bearer level protocol conversion | ZTE | - |
| S2‑151186 | [DRAFT] Request confirmation on OMR-based solution for end-to-end transparent media in eWebRTCi | SA WG2 | - |
| S2‑151187 | Conclusions for key issue 1 | Alcatel-Lucent, Alcatel-Lucent ShangHai Bell | - |
| S2‑151188 | Clean-up on HL_Com TR | Ericsson | - |
| S2‑151189 | HLCom - Solution 4 - add SCEF, additional evaluation text | Alcatel-Lucent | - |
| S2‑151190 | Conclusions for HL_Com | Ericsson, Qualcomm Incorporated | - |
| S2‑151191 | GROUPE Conclusions | Qualcomm Incorporated | - |
| S2‑151192 | Group message delivery function and procedure | Huawei, Hisilicon, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Samsung, KPN | - |
| S2‑151193 | APN and group specific NAS Level congestion control | NTT DOCOMO | - |
| S2‑151194 | APN and group specific NAS level congestion control | NTT DOCOMO | - |
| S2‑151195 | Evaluation Criteria For Solution 5.2.1 | Alcatel-Lucent, Alcatel-Lucent ShangHai Bell | - |
| S2‑151196 | Evaluation Comparison of Solutions in Section 5 | T-Mobile USA | - |
| S2‑151197 | Evaluation Criteria For Solution 2 | Ericsson | - |
| S2‑151198 | Evaluation of Solution 3 +5 | Nokia Networks, Huawei | - |
| S2‑151199 | Clarification and Evaluation of Policy Based TCF Solution | China Mobile, Broadcom Corporation, CATR, KDDI | - |
| S2‑151200 | Call flows for the solution with service steering policy interface | Ericsson | - |
| S2‑151201 | Semantics of the Traffic Steering Policy | Ericsson, AT&T, Nokia Networks | - |
| S2‑151202 | Procedures of TCF Solution | China Mobile, CATR | - |
| S2‑151203 | Steering Rule for Uplink/Downlink Traffic | Huawei, Hisilicon, Cisco, Allot Communications, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Sprint, Comverse, Openet Telecom | - |
| S2‑151204 | Updates to solution with policy steering interface | Ericsson, AT&T, KDDI, Nokia Networks | - |
| S2‑151205 | Reserved for Ivano's parallel sessions | - | imported from 3GU |
| S2‑151206 | Clarifications for QoS change of default bearer | Huawei, Hisilicon | - |
| S2‑151207 | Clarifications for QoS change of default bearer | Huawei, Hisilicon | - |
| S2‑151208 | MS Info Change Reporting Action at change of Serving Node (MME <--> SGSN): Update of call Flows | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | - |
| S2‑151209 | MS Info Change Reporting Action at change of Serving Node (MME <--> SGSN): Update of call Flows | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | - |
| S2‑151210 | [DRAFT] Reply to LS on ePDG selection when UE is roaming | SA WG2 | - |
| S2‑151211 | Clarification of Impacts when Gxx is not used for eHRPD Access | China Telecom, Huawei, HiSilicon | - |
| S2‑151212 | Architectural updates for Monitoring feature | Intel, Alcatel-Lucent, Huawei, Cisco | - |
| S2‑151213 | Introducing HSS-SCEF and MME/SGSN-SCEF Reference Points | Intel, Huawei, Alcatel-Lucent | - |
| S2‑151214 | Monitoring Feature Description | Intel, Huawei, Alcatel-Lucent | - |
| S2‑151215 | Monitoring via PCRF | Ericsson | - |
| S2‑151216 | Support for Monitoring Events | Intel | - |
| S2‑151217 | Support for Monitoring Events | Intel | - |
| S2‑151218 | Introduction of monitoring procedures | Huawei, HiSilicon, Intel, Alcatel-Lucent | - |
| S2‑151219 | Update to PSM to support monitoring events | Huawei, HiSilicon, Intel | - |
| S2‑151220 | Update to PSM to support monitoring events | Huawei, HiSilicon, Intel | - |
| S2‑151221 | Update to PSM to support monitoring events | Huawei, HiSilicon, Intel | - |
| S2‑151222 | Solution update for setting up an AS session with required QoS | Huawei, HiSilicon, Alcatel-Lucent, Intel | - |
| S2‑151223 | Predictable UE communication pattern | Ericsson | - |
| S2‑151224 | NBIFOM operation Modes | Verizon, Oracle | - |
| S2‑151225 | Handling of UE-initiated and NW-initiated NBIFOM modes | Ericsson, Huawei, HiSilicon | - |
| S2‑151226 | Support of NB_IFOM for S2a SCM | Qualcomm Incorporated | - |
| S2‑151227 | Cleanup of the Loss of an Access from a PDN Connection | Huawei, HiSilicon, China Telecom | - |
| S2‑151228 | Conclusions for indication of 3GPP access loss in SCM | LG Electronics | - |
| S2‑151229 | Conclusions for NBIFOM Open Issues 6 and 7 | ZTE | - |
| S2‑151230 | Issue for eDRX | Acer Incorporated, ITRI | - |
| S2‑151231 | Extended DRX in Idle mode | Ericsson | - |
| S2‑151232 | eDRX - Idle Mode Issue 2: Solution A | Alcatel-Lucent, Qualcomm Incorporated | - |
| S2‑151233 | GTP-C retransmission in eDRX | Huawei | - |
| S2‑151234 | Extended I-DRX and PSM coexistence | Qualcomm Incorporated | - |
| S2‑151235 | AESE drafting session report | AESE Rapporteurs (Intel) | - |
| S2‑151236 | Solution update for setting up an AS session with required QoS | Huawei, HiSilicon, Alcatel-Lucent, Intel | - |
| S2‑151237 | Predictable UE communication pattern | Ericsson | - |
| S2‑151238 | Architectural Considerations | NTT DOCOMO, AT&T, Alcatel-Lucent, Intel | - |
| S2‑151239 | Solution update for change of chargeable party | Huawei, HiSilicon | - |
| S2‑151240 | Solution update for informing about UE's connection properties | Huawei, HiSilicon | - |
| S2‑151241 | AESE - Solution 6 Evaluation | Alcatel-Lucent, Cisco Systems Inc | - |
| S2‑151242 | Solution update for background data transfer | Huawei, HiSilicon, NTT DOCOMO | - |
| S2‑151243 | First list of Key issues: AAA server knowledge of emergency & Location | Alcatel-Lucent, Alcatel-Lucent ShangHai Bell, Qualcom Inc | - |
| S2‑151244 | Solutions for the location related Key Issue | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | - |
| S2‑151245 | [DRAFT] Reply to LS to 3GPP on IMS Emergency Session over WLAN | SA WG2 | - |
| S2‑151246 | Skeleton and scope for TR 23.771 (FS_SEW) | Alcatel-Lucent, Alcatel-Lucent ShangHai Bell | - |
| S2‑151247 | General Key Issues: Proposed Assumptions for phase 1 | Qualcomm Incorporated, Alcatel Lucent, Alcatel Lucent Shanghai Bell | - |
| S2‑151248 | Key Issues on Connectivity Establishment | Qualcomm Incorporated | - |
| S2‑151249 | First list of Key issues: AAA server knowledge of emergency & Location | Alcatel-Lucent, Alcatel-Lucent ShangHai Bell, Qualcom Inc | - |
| S2‑151250 | Key issue: QoS | Alcatel-Lucent, Alcatel-Lucent ShangHai Bell | - |
| S2‑151251 | Handling of UE-initiated and NW-initiated NBIFOM modes | Ericsson, Huawei, HiSilicon | - |
| S2‑151252 | Removing alternatives from S2a call flows | Apple Inc., Huawei, Hisilicon | - |
| S2‑151253 | Removing alternatives from S2b call flows | Apple Inc. | - |
| S2‑151254 | Consideration of PCO vs. APCO for S2b NBIFOM parameters Transport (Open issue 5) | ZTE | - |
| S2‑151255 | Conclusions for App ID Support | ZTE | - |
| S2‑151256 | Conclusion for NBIFOM study in Rel-13 | ZTE | - |
| S2‑151257 | AESE - Conclusions | Alcatel-Lucent, Intel | - |
| S2‑151258 | Configuration of extended DRX for connected mode | Ericsson | - |
| S2‑151259 | Extended C-DRX: New connected mode substate in the core network to handle NAS retransmissions and MT SMS (Issues 2 and 3) | Qualcomm Incorporated | - |
| S2‑151260 | Key issues: UE Location Information | T-Mobile USA | - |
| S2‑151261 | Solutions for the location related Key Issue | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | - |
| S2‑151262 | Solution: How LRF retrieve location information for s2a | Huawei , Hisilicon | - |
| S2‑151263 | A solution for ePDG selection | Alcatel-Lucent, Alcatel-Lucent ShangHai Bell | - |
| S2‑151264 | MS Info Change Reporting Action at change of Serving Node (MME <--> SGSN): Update of call Flows | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | - |
| S2‑151265 | MS Info Change Reporting Action at change of Serving Node (MME <--> SGSN): Update of call Flows | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | - |
| S2‑151266 | Clarifications for QoS change of default bearer | Huawei, Hisilicon, Ericsson, Alcatel-Lucent | - |
| S2‑151267 | Clarifications for QoS change of default bearer | Huawei, Hisilicon, Ericsson, Alcatel-Lucent | - |
| S2‑151268 | Priority of Default Bearer | Huawei, Hisilicon, Applied Communication Sciences, OEC | - |
| S2‑151269 | Priority of Default Bearer | Huawei, Hisilicon, Applied Communication Sciences, OEC | - |
| S2‑151270 | Conclusions for App ID Support | ZTE | - |
| S2‑151271 | Introducing HSS-SCEF and MME/SGSN-SCEF Reference Points | Intel, Huawei, Alcatel-Lucent, Cisco | - |
| S2‑151272 | Monitoring Feature Description | Intel, Huawei, Alcatel-Lucent | - |
| S2‑151273 | Monitoring via PCRF | Ericsson | - |
| S2‑151274 | Support for Monitoring Events | Intel | - |
| S2‑151275 | Support for Monitoring Events | Intel, Cisco | - |
| S2‑151276 | Introduction of monitoring procedures | Huawei, HiSilicon, Intel, Alcatel-Lucent | - |
| S2‑151277 | Cleanup of the Loss of an Access from a PDN Connection | Huawei, HiSilicon, China Telecom | - |
| S2‑151278 | Conclusions for indication of 3GPP access loss in SCM | LG Electronics | - |
| S2‑151279 | Conclusions for NBIFOM Open Issues 6 and 7 | ZTE | - |
| S2‑151280 | General Key Issues: Proposed Assumptions for phase 1 | Qualcomm Incorporated, Alcatel Lucent, Alcatel Lucent Shanghai Bell | - |
| S2‑151281 | First list of Key issues: AAA server knowledge of emergency & Location | Alcatel-Lucent, Alcatel-Lucent ShangHai Bell, Qualcom Inc | - |
| S2‑151282 | Key issues: UE Location Information | T-Mobile USA | - |
| S2‑151283 | Solution: How LRF retrieve location information for s2a | Huawei , Hisilicon | - |
| S2‑151284 | eDRX - Idle Mode Issue 2: Solution A | Alcatel-Lucent, Qualcomm Incorporated | - |
| S2‑151285 | Extended I-DRX and PSM coexistence | Qualcomm Incorporated | - |
| S2‑151286 | Configuration of extended DRX for connected mode | Ericsson | - |
| S2‑151287 | Extended C-DRX: New connected mode substate in the core network to handle NAS retransmissions and MT SMS (Issues 2 and 3) | Qualcomm Incorporated | - |
| S2‑151288 | [DRAFT] LS on RAN assumptions from SA WG2 for FS_eDRX | Qualcomm Incorporated | - |
| S2‑151289 | Reserved for Frank's parallel sessions | - | imported from 3GU |
| S2‑151290 | Reserved for Frank's parallel sessions | - | imported from 3GU |
| S2‑151291 | Reserved for Frank's parallel sessions | - | imported from 3GU |
| S2‑151292 | Reserved for Frank's parallel sessions | - | imported from 3GU |
| S2‑151293 | Reserved for Frank's parallel sessions | - | imported from 3GU |
| S2‑151294 | Reserved for Frank's parallel sessions | - | imported from 3GU |
| S2‑151295 | Reserved for Frank's parallel sessions | - | imported from 3GU |
| S2‑151296 | Reserved for Frank's parallel sessions | - | imported from 3GU |
| S2‑151297 | Reserved for Frank's parallel sessions | - | imported from 3GU |
| S2‑151298 | Reserved for Frank's parallel sessions | - | imported from 3GU |
| S2‑151299 | Reserved for Frank's parallel sessions | - | imported from 3GU |
| S2‑151300 | Reserved for Frank's parallel sessions | - | imported from 3GU |
| S2‑151301 | Reserved for Frank's parallel sessions | - | imported from 3GU |
| S2‑151302 | Reserved for Frank's parallel sessions | - | imported from 3GU |
| S2‑151303 | Reserved for Frank's parallel sessions | - | imported from 3GU |
| S2‑151304 | Reserved for Frank's parallel sessions | - | imported from 3GU |
| S2‑151305 | Reserved for Frank's parallel sessions | - | imported from 3GU |
| S2‑151306 | LS from SA WG4: LS on codec support in IMS-WebRTC for WLAN and fixed access | SA WG4 | - |
| S2‑151307 | Draft Agenda for SA WG2#108 | SA WG2 Chairman | - |
| S2‑151308 | [DRAFT] Reply LS on Study on improved end-to-end QoS handling | SA WG2 | - |
| S2‑151309 | Update to the SID on Feasibility study on the Support of Emergency services over WLAN | Alcatel-Lucent, Alcatel-Lucent ShangHai Bell | - |
| S2‑151310 | Additional SA WG2 #110ah Meeting Proposal | SA WG2 Chairman | - |
| S2‑151311 | Draft Response to Reply LS on Security Framework for Cellular IoT | SA WG2 | - |
| S2‑151312 | Fixes to Public Safety Discovery procedures | Intel | - |
| S2‑151313 | Use of Group Info/Connectivity Info in UE2NW Relay discovery | Samsung | - |
| S2‑151314 | Updates to Annex on PC5 interface | Ericsson | - |
| S2‑151315 | IOPS network configuration/establishment | General Dynamics UK Ltd. | - |
| S2‑151316 | PLMN Selection | Ericsson | - |
| S2‑151317 | way forward on some unsolved FFS issues | Samsung | - |
| S2‑151318 | [DRAFT] LS on proposed method of restricting access to IOPS cells | SA WG2 | - |
| S2‑151319 | Restriction of UEs not allowed in IOPS PLMN | Ericsson | - |
| S2‑151320 | Way Forward on service continuity | T-Mobile Austria | - |
| S2‑151321 | Introduce the Dedicated Core Network (DECOR) feature | NTT DOCOMO, Huawei | - |
| S2‑151322 | Update of MME load balancing for Dedicated Core Networks | Huawei, HiSilicon, NTT DOCOMO | - |
| S2‑151323 | Introduce the Dedicated Core Network (DECOR) feature | NTT DOCOMO, Huawei | - |
| S2‑151324 | Mandatory use of Geographical Areas | Ericsson, Sprint, Qualcomm Incorporated, LG Electronics, U.S. Department of Commerce, Home Office, Alcatel-Lucent | - |
| S2‑151325 | Support for ProSe in multicarrier across PLMNs | Qualcomm Incorporated, Ericsson | - |
| S2‑151326 | Reply LS on addition of proximity services group identifier | SA WG2 | - |
| S2‑151327 | Clarification of ProSe Layer 2 Group ID provisioning | Samsung | - |
| S2‑151328 | Conclusion Supplements on ProSe Restricted Discovery | Huawei, HiSilicon | - |
| S2‑151329 | ProSe Discovery UE ID update | CATT | - |
| S2‑151330 | Correction to Monitor request procedure with application controlled extension | Samsung | - |
| S2‑151331 | ProSe Open Discovery Enhancement for Dynamic Metadata | Huawei, Hisilicon, Qualcomm Incorporated | - |
| S2‑151332 | Metadata upload for Restricted Discovery | Qualcomm Incorporated | - |
| S2‑151333 | Way Forward on service continuity | T-Mobile Austria | - |
| S2‑151334 | Correction for consistency description | Samsung | - |
| S2‑151335 | Update of the solution using IP multicast in the UE-to-NW Relay | Nokia Networks | - |
| S2‑151336 | Corrections in ProSe UE-NW Relay discovery | Nokia Networks, Qualcomm Incorporated | - |
| S2‑151337 | Resolve FFS for UE-to-Network Relay Discovery | HTC | - |
| S2‑151338 | Clarification of applicable UE mobility procedures | General Dynamics UK Ltd. | - |
| S2‑151339 | Support of public safety services over an IOPS network | General Dynamics UK Ltd. | - |
| S2‑151340 | [DRAFT] LS on support of public safety services over an IOPS network | General Dynamics UK Limited | - |
| S2‑151341 | Correction for consistency description | Samsung | - |
| S2‑151342 | Metadata upload for Restricted Discovery | Qualcomm Incorporated | - |
| S2‑151343 | New UE-initiated update procedures for Open Direct Discovery | Qualcomm Incorporated | - |
| S2‑151344 | Proximity estimation | Qualcomm Incorporated | - |
| S2‑151345 | Coarse proximity estimation | Deutsche Telekom | - |
| S2‑151346 | Reserved for Ivano's parallel sessions | - | imported from 3GU |
| S2‑151347 | Reserved for Ivano's parallel sessions | - | imported from 3GU |
| S2‑151348 | Reserved for Ivano's parallel sessions | - | imported from 3GU |
| S2‑151349 | Reserved for Ivano's parallel sessions | - | imported from 3GU |
| S2‑151350 | Reserved for Ivano's parallel sessions | - | imported from 3GU |
| S2‑151351 | Reserved for Ivano's parallel sessions | - | imported from 3GU |
| S2‑151352 | Reserved for Ivano's parallel sessions | - | imported from 3GU |
| S2‑151353 | [DRAFT] Status of UE-UE relays in SA WG2 | SA WG2 | - |
| S2‑151354 | Draft Response to Reply LS on paging for MTC | VODAFONE Group Plc | - |
| S2‑151355 | Reserved for Puneet's parallel sessions | - | imported from 3GU |
| S2‑151356 | Reserved for Puneet's parallel sessions | - | imported from 3GU |
| S2‑151357 | Reserved for Puneet's parallel sessions | - | imported from 3GU |
| S2‑151358 | Reserved for Puneet's parallel sessions | - | imported from 3GU |
| S2‑151359 | Reserved for Puneet's parallel sessions | - | imported from 3GU |
| S2‑151360 | Reserved for Puneet's parallel sessions | - | imported from 3GU |
| S2‑151361 | Reserved for Puneet's parallel sessions | - | imported from 3GU |
| S2‑151362 | Reserved for Puneet's parallel sessions | - | imported from 3GU |
| S2‑151363 | Reserved for Puneet's parallel sessions | - | imported from 3GU |
| S2‑151364 | Reserved for Puneet's parallel sessions | - | imported from 3GU |
| S2‑151365 | Reserved for Puneet's parallel sessions | - | imported from 3GU |
| S2‑151366 | Reserved for Puneet's parallel sessions | - | imported from 3GU |
| S2‑151367 | Reserved for Puneet's parallel sessions | - | imported from 3GU |
| S2‑151368 | Reserved for Puneet's parallel sessions | - | imported from 3GU |
| S2‑151369 | Reserved for Puneet's parallel sessions | - | imported from 3GU |
| S2‑151370 | Draft Response to Reply LS on paging for MTC | SA WG2 | - |
| S2‑151371 | Introduce the Dedicated Core Network (DECOR) feature | NTT DOCOMO, Huawei | - |
| S2‑151372 | Introduce the Dedicated Core Network (DECOR) feature | NTT DOCOMO, Huawei | - |
| S2‑151373 | Clarification of ProSe Layer 2 Group ID provisioning | Samsung | - |
| S2‑151374 | Correction to Monitor request procedure with application controlled extension | Samsung | - |
| S2‑151375 | Fixes to Public Safety Discovery procedures | Intel | - |
| S2‑151376 | Corrections in ProSe UE-NW Relay discovery | Nokia Networks, Qualcomm Incorporated | - |
| S2‑151377 | way forward on some unsolved FFS issues | Samsung | - |
| S2‑151378 | Restriction of UEs not allowed in IOPS PLMN | Ericsson | - |
| S2‑151379 | [DRAFT] LS on proposed method of restricting access to IOPS cells | SA WG2 | - |
| S2‑151380 | Clarification of applicable UE mobility procedures | General Dynamics UK Ltd. | - |
| S2‑151381 | [DRAFT] LS on support of public safety services over an IOPS network | SA WG2 | - |
| S2‑151382 | Response to Reply LS on Security Framework for Cellular IoT | SA WG2 | - |
| S2‑151383 | Response to Reply LS on paging for MTC | SA WG2 | - |
| S2‑151384 | Reply LS on Clarification regarding change of active time value and periodic TAU or RAU timer value for UE supporting PSM | SA WG2 | - |
| S2‑151385 | Discussion on the how to avoid SRVCC | ZTE | - |
| S2‑151386 | Way forward on the key issue - Architectural aspects for minimizing the need for bearer level protocol conversion | ZTE | - |
| S2‑151387 | LS on OMR-based solution for end-to-end transparent media in eWebRTCi | SA WG2 | - |
| S2‑151388 | Stage 2 cleanup regarding the WIC registration with a security token | Samsung | - |
| S2‑151389 | Stage 2 cleanup regarding the WIC registration with a security token | Samsung | - |
| S2‑151390 | Support of NB_IFOM for S2a SCM | Qualcomm Incorporated | - |
| S2‑151391 | Cleanup of the Loss of an Access from a PDN Connection | Huawei, HiSilicon, China Telecom | - |
| S2‑151392 | Conclusions for NBIFOM Open Issues 6 and 7 | ZTE | - |
| S2‑151393 | Removing alternatives from S2a call flows | Apple Inc., Huawei, Hisilicon | - |
| S2‑151394 | Conclusion for NBIFOM study in Rel-13 | ZTE | - |
| S2‑151395 | Reply LS on ePDG selection | SA WG2 | - |
| S2‑151396 | Enforcement of traffic steering policy | Cisco, Allot Communications, Huawei, HiSilicon, Sprint, Comverse, Sandvine Incoporated, US cellular, Broadcom Corporation, Alcatel-Lucent and Alcatel-Lucent Shanghai Bell, Openet Telecom | - |
| S2‑151397 | Clarification and Evaluation of Policy Based TCF Solution | China Mobile, Broadcom Corporation, CATR, KDDI | - |
| S2‑151398 | Semantics of the Traffic Steering Policy | Ericsson, AT&T, Nokia Networks | - |
| S2‑151399 | Introduce the Dedicated Core Network (DECOR) feature | NTT DOCOMO, Huawei | - |
| S2‑151400 | eDRX - Idle Mode Issue 2: Solution A | Alcatel-Lucent, Qualcomm Incorporated | - |
| S2‑151401 | Conclusions for HL_Com | Ericsson, Qualcomm Incorporated | - |
| S2‑151402 | Updating solutions 2 and 6 | Huawei, HiSilicon | - |
| S2‑151403 | HLCom - Solution 4 - add SCEF, additional evaluation text | Alcatel-Lucent | - |
| S2‑151404 | AESE - Conclusions | Alcatel-Lucent, Intel | - |
| S2‑151405 | Solution update for setting up an AS session with required QoS | Huawei, HiSilicon, Alcatel-Lucent, Intel, China Mobile | - |
| S2‑151406 | Solution update for change of chargeable party | Huawei, HiSilicon | - |
| S2‑151407 | Solution update for background data transfer | Huawei, HiSilicon, NTT DOCOMO | - |
| S2‑151408 | Monitoring Feature Description | Intel, Huawei, Alcatel-Lucent | - |
| S2‑151409 | Monitoring via PCRF | Ericsson | - |
| S2‑151410 | Update to PSM to support monitoring events | Huawei, HiSilicon, Intel | - |
| S2‑151411 | Update to PSM to support monitoring events | Huawei, HiSilicon, Intel | - |
| S2‑151412 | Update to PSM to support monitoring events | Huawei, HiSilicon, Intel | - |
| S2‑151413 | Cover Sheet for TR 23.769 for Approval at TSG SA | GROUPE Rapporteurs (Huawei) | - |
| S2‑151414 | Group message delivery function and procedure | Huawei, Hisilicon, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Samsung, KPN | - |
| S2‑151415 | Cleanup for Solution: Use of MBMS for Group Message Delivery | Samsung | - |
| S2‑151416 | MS Info Change Reporting Action at change of Serving Node (MME <--> SGSN): Update of call Flows | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | - |
| S2‑151417 | MS Info Change Reporting Action at change of Serving Node (MME <--> SGSN): Update of call Flows | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | - |
| S2‑151418 | [DRAFT] Reply to LS to 3GPP on IMS Emergency Session over WLAN | SA WG2 | - |
| S2‑151419 | First list of Key issues: AAA server knowledge of emergency & Location | Alcatel-Lucent, Alcatel-Lucent ShangHai Bell, Qualcom Inc | - |
| S2‑151420 | Solutions for the location related Key Issue | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | - |
| S2‑151421 | A solution for ePDG selection | Alcatel-Lucent, Alcatel-Lucent ShangHai Bell | - |
| S2‑151422 | Update to the SID on Feasibility study on the Support of Emergency services over WLAN | Alcatel-Lucent, Alcatel-Lucent ShangHai Bell | - |
| S2‑151423 | LS on proposed method of restricting access to IOPS cells | SA WG2 | - |
| S2‑151424 | LS on support of public safety services over an IOPS network | SA WG2 | - |
| S2‑151425 | Reply LS on Study on improved end-to-end QoS handling | SA WG2 | - |
| S2‑151426 | Solution update for background data transfer | Huawei, HiSilicon, NTT DOCOMO | - |
| S2‑151427 | AESE - Conclusions | Alcatel-Lucent, Intel | - |
| S2‑151428 | Discussion on the how to avoid SRVCC | ZTE | - |
| S2‑151429 | Conclusions for HL_Com | Ericsson, Qualcomm Incorporated | - |
| S2‑151430 | LS on RAN assumptions from SA WG2 for FS_eDRX | SA WG2 | - |
| S2‑151431 | Reply LS on IMS Emergency Session over WLAN | SA WG2 | - |
page generated from database: 2024-04-13 13:51:47