3GPP TDocs (written contributions) at meeting
Meeting: S2-113 - 2016-01-25 to 2016-01-29, Saint Kitts
meeting id: S2-113 (click id for more info on this meeting)Click on the Tdoc to open its file.
| TDoc | Title | Source | Remarks |
|---|---|---|---|
| S2‑160001 | Draft Agenda for SA WG2#113 | SA WG2 Chairman | imported from 3GU |
| S2‑160002 | Draft Report of SA WG2 meeting #112 | SA WG2 Secretary | imported from 3GU |
| S2‑160003 | LS from Wi-Fi Alliance Operator Marketing Task Group: RE: Proposed requirements for carrier Wi-Fi networks | Wi-Fi Alliance Operator Marketing Task Group | imported from 3GU |
| S2‑160004 | LS from SA WG1: Reply LS on Set of Rel-13 features for the Support of Emergency sessions over WLAN | SA WG1 | imported from 3GU |
| S2‑160005 | LS from SA WG4: LS on QoS for EVS-VBR Codec Operation | SA WG4 | imported from 3GU |
| S2‑160006 | LS from RAN WG1: LS on resource allocation principles in PC5-based V2V | RAN WG1 | imported from 3GU |
| S2‑160007 | LS from RAN WG2: LS on V2X message characteristics | RAN WG2 | imported from 3GU |
| S2‑160008 | LS from CT WG3: LS on APN AMBR change at a certain time on Gx | CT WG3 | imported from 3GU |
| S2‑160009 | LS from CT WG4: LS on the Setting of Delay Tolerant Connection Indication | CT WG4 | imported from 3GU |
| S2‑160010 | LS from CT WG4: LS on the clarifications on the Revocation of Discovery Filters | CT WG4 | imported from 3GU |
| S2‑160011 | LS from CT WG4: LS on Network asserted WLAN Location Information for PDN connection establishment over S2b | CT WG4 | imported from 3GU |
| S2‑160012 | LS from CT WG1: Reply LS on eDRX EUTRA | CT WG1 | imported from 3GU |
| S2‑160013 | LS from CT WG1: LS on precedence of information in USIM | CT WG1 | imported from 3GU |
| S2‑160014 | LS from SA WG6: LS on potential need of PCC enhancement for MCPTT | SA WG6 | imported from 3GU |
| S2‑160015 | LS from ETSI SC EMTEL: LS on Total Conversation for Emergency Communications | ETSI SC EMTEL | imported from 3GU |
| S2‑160016 | LS from SA WG3: Reply LS to RAN2 for clarification of security overhead for LTE V2X | SA WG3 | imported from 3GU |
| S2‑160017 | LS from SA WG3: Reply LS on IPsec tunnelling mechanism for LTE-WiFi aggregation | SA WG3 | imported from 3GU |
| S2‑160018 | LS from SA WG3: LS on backoff timer | SA WG3 | imported from 3GU |
| S2‑160019 | LS from SA WG3: LS on new security work item for NB-IoT | SA WG3 | imported from 3GU |
| S2‑160020 | LS from SA WG3: LS on Security requirements for Public Safety Discovery messages | SA WG3 | imported from 3GU |
| S2‑160021 | LS from GSMA NG PACKET: NG PACKET LS to Standardization groups on PMIP removal | GSMA NG PACKET | imported from 3GU |
| S2‑160022 | LS from RAN WG3: Reply LS on paging coordination in extended idle mode DRX | RAN WG3 | imported from 3GU |
| S2‑160023 | LS from CT WG3: LS on TSSF Identity Information over Gx | CT WG3 | imported from 3GU |
| S2‑160024 | LS from GSMA RiLTE: LS on SIP deregistration in GERAN and UTRAN (no VOPSSI) | GSMA RiLTE | imported from 3GU |
| S2‑160025 | LS from CT WG1: LS on NBIFOM procedure in SCM and RAN rules handling parameter | CT WG1 | imported from 3GU |
| S2‑160026 | LS from CT WG1: LS on Non- Zero Discovery Entry ID for Restricted Discovery | CT WG1 | imported from 3GU |
| S2‑160027 | LS from CT WG1: LS on failure to set up the resources for VoLTE MO call | CT WG1 | imported from 3GU |
| S2‑160028 | LS from CT WG1: Reply LS on ProSe Direct Discovery out of coverage | CT WG1 | imported from 3GU |
| S2‑160029 | LS from CT WG1: Reply LS on ProSe UE-to-Network relay | CT WG1 | imported from 3GU |
| S2‑160030 | LS from CT WG3: Reply LS on OCS address for Gy and Gyn inter-PLMN | CT WG3 | imported from 3GU |
| S2‑160031 | LS from CT WG3: LS on the decision of NBIFOM mode | CT WG3 | imported from 3GU |
| S2‑160032 | LS from CT WG3: Reply LS on the Setting of Delay Tolerant Connection Indication | CT WG3 | imported from 3GU |
| S2‑160033 | LS from CT WG4: Reply LS on roaming scenario with selection of a WLAN that interworks with a service provider in EVSP | CT WG4 | imported from 3GU |
| S2‑160034 | LS from GERAN WG2: Follow Up LS on RAN assumptions from SA2 for FS_eDRX | GERAN WG2 | imported from 3GU |
| S2‑160035 | LS from GERAN WG2: LS on CS/PS coordination in GERAN Shared Networks | GERAN WG2 | imported from 3GU |
| S2‑160036 | LS from RAN WG1: LS on NB-IoT Evaluations | RAN WG1 | imported from 3GU |
| S2‑160037 | LS from RAN WG2: Reply LS on 3GPP Work on Explicit Congestion Notification for Lower Layer Protocols | RAN WG2 | imported from 3GU |
| S2‑160038 | LS from RAN WG2: LS on RAN2 agreements on extended DRX | RAN WG2 | imported from 3GU |
| S2‑160039 | LS from RAN WG2: LS on RAN WG2 agreements for inter-carrier/Inter-PLMN sidelink discovery | RAN WG2 | imported from 3GU |
| S2‑160040 | LS from RAN WG2: Reply LS for request for clarifications for WLAN deployments for LWA | RAN WG2 | imported from 3GU |
| S2‑160041 | LS from RAN WG2: Reply LS to S3-152467 on IPsec tunnelling mechanism for LTE-WiFi aggregation | RAN WG2 | imported from 3GU |
| S2‑160042 | LS from RAN WG2: LS on DRB Handling in LWRI | RAN WG2 | imported from 3GU |
| S2‑160043 | LS from RAN WG2: Reply LS on QoS for EVS-VBR Codec Operation | RAN WG2 | imported from 3GU |
| S2‑160044 | LS from RAN WG2: Reply LS on ProSe UE Relaying Support | RAN WG2 | imported from 3GU |
| S2‑160045 | LS from RAN WG3: LS on DECOR and MOCN rerouting | RAN WG3 | imported from 3GU |
| S2‑160046 | LS from RAN WG3: LS on RAN3 agreements on DC enhancement for LTE | RAN WG3 | imported from 3GU |
| S2‑160047 | LS from SA WG1: Reply LS on V2X message characteristics | SA WG1 | imported from 3GU |
| S2‑160048 | LS from SA WG5: LS on application based charging for applications identified by service data flow filters | SA WG5 | imported from 3GU |
| S2‑160049 | LS from SA WG5: LS on definition of Network Service | SA WG5 | imported from 3GU |
| S2‑160050 | LS from ONF: Progress toward SDN architecture issue 1.1 | Open Networking Foundation | imported from 3GU |
| S2‑160051 | LS from RAN WG2: LS on NB-IoT work progress in RAN WG2 | RAN WG2 | imported from 3GU |
| S2‑160052 | LS from TSG RAN: LS on S1 signalling solutions for non-NB-IoT UEs | TSG RAN | imported from 3GU |
| S2‑160053 | LS from TSG SA: Reply LS on 3GPP Work on Explicit Congestion Notification for Lower Layer Protocols | TSG SA | imported from 3GU |
| S2‑160054 | LS from TSG SA: LS on ePDG Selection versus LI requirements | TSG SA | imported from 3GU |
| S2‑160055 | LS from TSG SA: LS on LTE support for V2X services | TSG SA | imported from 3GU |
| S2‑160056 | LS from TSG SA: LS to WGs on Application Architecture related SI/WI proposals not related to Critical Communications | TSG SA | imported from 3GU |
| S2‑160057 | Support of Lawful intercept ePDG requirements (option A) | BlackBerry UK Ltd | imported from 3GU |
| S2‑160058 | Support of Lawful intercept ePDG requirements (option B) | BlackBerry UK Ltd | imported from 3GU |
| S2‑160059 | Support of Lawful intercept ePDG requirements | BlackBerry UK Limited | imported from 3GU |
| S2‑160060 | Evaluation and conclusion of Solution #1 | ORANGE | imported from 3GU |
| S2‑160061 | Traffic detection in case of encrypted traffic | Allot Communications Ltd. | imported from 3GU |
| S2‑160062 | Reply to LS on application based charging for applications identified by service data flow filters | Allot Communications Ltd. | imported from 3GU |
| S2‑160063 | Correction to ePDG selection for emergency bearer services | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| S2‑160064 | Sending an Emergency-Indication to the 3GPP AAA Server over S6b | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| S2‑160065 | Evaluation on the solutions related with “Determine Emergency Call Numbers” | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| S2‑160066 | solution &&Y for ePDG selection for emergency services | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| S2‑160067 | Solution: IMEI check in case of in case of an EPC session for emergency services | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| S2‑160068 | Update to solution 11 (Determine Emergency Call Numbers) | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| S2‑160069 | Update to solution 17 (mobility with EPC) | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| S2‑160070 | Update to solution 19 (un-authenticated UE) | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| S2‑160071 | Minor Update to solution 21 (Access Selection) & to § 7.2 (Evaluation) | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| S2‑160072 | Key issue: IMEI check in case of emergency sessions | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| S2‑160073 | Location of the resource allocation function (F-TEID, UE IP @) | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| S2‑160074 | New Solution: Usage of a sponsoring | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| S2‑160075 | LS on the Revocation of Discovery Filters | TELECOM ITALIA S.p.A. | imported from 3GU |
| S2‑160076 | New SID on Feasibility study on the Support of Emergency services over WLAN (FS_SEW2) | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| S2‑160077 | Reply LS on Set of Rel-13 features for the Support of Emergency sessions over WLAN | Alcatel-Lucent | imported from 3GU |
| S2‑160078 | New WID on the Support of Emergency services over WLAN –phase 2 (SEW2) | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| S2‑160079 | Control plane function providing pre-allocated GTP-U IP address and TEID to the user plane function (during restoration scenario) | Cisco Systems, Inc. | imported from 3GU |
| S2‑160080 | Considerations and solution for supporting extended buffering for the UE in power saving mode | Cisco Systems, Inc. | imported from 3GU |
| S2‑160081 | Consideration for performing LI functionality | Cisco Systems, Inc. | imported from 3GU |
| S2‑160082 | Considerations and solution for UE IP address management | Cisco Systems. Inc. | imported from 3GU |
| S2‑160083 | Considerations for the functionality supported by the user plane function | Cisco Systems, Inc. | imported from 3GU |
| S2‑160084 | Considerations for 3GPP specific information at the user plane function | Cisco Systems, Inc. | imported from 3GU |
| S2‑160085 | Architectural Requirements and Assumption for Grouped-based signalling delivery | KDDI Corporation | imported from 3GU |
| S2‑160086 | Key issue for signalling aggregation and optimization | KDDI Corporation | imported from 3GU |
| S2‑160087 | Adding Relay Service Code to Additional Information Message | Nokia Networks | imported from 3GU |
| S2‑160088 | Considerations on priority between ANDSF and LWA and CRLWI | Nokia Networks | imported from 3GU |
| S2‑160089 | [Draft] LS on Co-existence between LTE-WLAN Radio Level Integration and other WLAN offloading solutions (e.g. ANDSF) | Nokia Networks | imported from 3GU |
| S2‑160090 | Correction in MME triggered Serving GW relocation procedure | Nokia Networks | imported from 3GU |
| S2‑160091 | Correction in MME triggered Serving GW relocation procedure | Nokia Networks | imported from 3GU |
| S2‑160092 | Solution for Key Issue 1 | NEC Corporation | imported from 3GU |
| S2‑160093 | Key issue on Modular Logical Functions in the NextGen System | AT&T | imported from 3GU |
| S2‑160094 | New key issue: Interconnection model for the control plane functional entities of the core network | Cisco Systems, Inc. | imported from 3GU |
| S2‑160095 | UE IP Address Allocation | Samsung Research America | imported from 3GU |
| S2‑160096 | DHCP Role in IP Address Allocation | Samsung Research America | imported from 3GU |
| S2‑160097 | Solution to key issue# 2: SGW User plane selection by taking PGW User plane into account | NEC EUROPE LTD | imported from 3GU |
| S2‑160098 | NexGen TR Reference of TR 23.799 V0.1.1 | China Mobile | imported from 3GU |
| S2‑160099 | Provisioning sponsored data connectivity information via SCEF | China Mobile Com. Corporation | imported from 3GU |
| S2‑160100 | Detach procedure for CIoT optimization | China Mobile Com. Corporation | imported from 3GU |
| S2‑160101 | A mechanism of information storage for NB-IOT users | China Mobile Com. Corporation | imported from 3GU |
| S2‑160102 | SDCI Architectural Assumptions | Openet Telecom | imported from 3GU |
| S2‑160103 | SDCI Key Issue 2 – PCRF Management of Sponsor Packet Flow Descriptions | Openet Telecom | imported from 3GU |
| S2‑160104 | SDCI New Key Issue – Static Sponsorship | Openet Telecom | imported from 3GU |
| S2‑160105 | SDCI Rx Referencing Sponsor Packet Flow Descriptions | Openet Telecom | imported from 3GU |
| S2‑160106 | Issues on supporting SIPTO@LN and CSG functions for dual connectivity | Samsung | imported from 3GU |
| S2‑160107 | Support of CSG, LIPA, and SIPTO@LN functions for dual connectivity | Samsung | imported from 3GU |
| S2‑160108 | Support of CSG function for dual connectivity | Samsung | imported from 3GU |
| S2‑160109 | Reply LS on RAN3 agreements on DC enhancements for LTE | Samsung | imported from 3GU |
| S2‑160110 | Determination of MB2/Ns interface connection agreement | Samsung | imported from 3GU |
| S2‑160111 | eDecor Key Issue 1 Solution 3 - evaluation | NEC | imported from 3GU |
| S2‑160112 | eDecor Key Issue 1 - solutions evaluation and conclusion | NEC | imported from 3GU |
| S2‑160113 | Discussion on Lawful Interception in split architectures | OTD | imported from 3GU |
| S2‑160114 | Considerations on TWAN authorization | Nokia Networks | imported from 3GU |
| S2‑160115 | Clarification on TWAN authorization | Nokia Networks | imported from 3GU |
| S2‑160116 | Clarification on TWAN authorization | Nokia Networks | imported from 3GU |
| S2‑160117 | [draft] Reply LS on roaming scenario with selection of a WLAN that interworks with a service provider in EVSP | Nokia Networks | imported from 3GU |
| S2‑160118 | New Key Issue : S8 Home Routing in case of Non 3GPP access | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| S2‑160119 | S8 Home Routing in case of Non 3GPP access | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| S2‑160120 | How P-CSCF can detect emergency numbers in a VPLMN | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| S2‑160121 | How to progress the SEW feature | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| S2‑160122 | Selection of user plane functional entity deployed at the edge local network | Nokia Networks | imported from 3GU |
| S2‑160123 | Functional split for Pre-defined PCC/ADC rule storage and operation | Nokia Networks | imported from 3GU |
| S2‑160124 | Evaluation of Solution#1 | NEC | imported from 3GU |
| S2‑160125 | Evaluation of Solution#2 | NEC | imported from 3GU |
| S2‑160126 | Inbound roamer support | NEC | imported from 3GU |
| S2‑160127 | Outbound roamer support | NEC | imported from 3GU |
| S2‑160128 | CS Data support | NEC | imported from 3GU |
| S2‑160129 | Key issue of Group Creation and Modification | Convida Wireless, Samsung | imported from 3GU |
| S2‑160130 | First Conclusions of FS_SEW2 | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| S2‑160131 | Clarification to Solution 18 for Key issue 3 | Ericsson | imported from 3GU |
| S2‑160132 | Clarification to Solution 20 for Support of Emergency Services unauthenticated UE on S2b | Ericsson | imported from 3GU |
| S2‑160133 | Key issue 3: IKE-based, network initiated, WiFi Query for on-demand UE Location positioning mid-emergency session | Ericsson | imported from 3GU |
| S2‑160134 | Key issue 3: On-demand Network initiated UE Location Positioning mid-emergency session via the emergency signalling channel | Ericsson | imported from 3GU |
| S2‑160135 | Replacing Incorrect Reference for business trunking Specification TS | Ericsson | imported from 3GU |
| S2‑160136 | Replacing Incorrect Reference for business trunking Specification TS | Ericsson | imported from 3GU |
| S2‑160137 | Evaluation Criteria For S8HR | Ericsson | imported from 3GU |
| S2‑160138 | Clarification to Solution #7: Local Number Translation | Ericsson | imported from 3GU |
| S2‑160139 | Clarification to Solution #1: PCRF based VPLMN-ID and Local Database based non UE detectable emergency session | Ericsson | imported from 3GU |
| S2‑160140 | Clarification to Solution #2: Local Number Translation | Ericsson | imported from 3GU |
| S2‑160141 | Solution to KI#2: Managing sponsored data connectivity information inside the operator’s network | Ericsson | imported from 3GU |
| S2‑160142 | Bitrate variations | Ericsson | imported from 3GU |
| S2‑160143 | V2X Authorisation and parameter configurations | Ericsson | imported from 3GU |
| S2‑160144 | Impacts on 3GPP system for IMS handling for eCall | Ericsson | imported from 3GU |
| S2‑160145 | Reply LS:LS from SA WG6: LS on potential need of PCC enhancement for MCPTT | Ericsson | imported from 3GU |
| S2‑160146 | Charging identities wwhen NBIFOM is used | Ericsson | imported from 3GU |
| S2‑160147 | Charging identities with multiple default bearers | Ericsson | imported from 3GU |
| S2‑160148 | TAI List problem and User plane area mapping | Ericsson | imported from 3GU |
| S2‑160149 | UE IP address allocation | Ericsson | imported from 3GU |
| S2‑160150 | Correction to unsability indication | Ericsson | imported from 3GU |
| S2‑160151 | eDECOR Defintions | Ericsson | imported from 3GU |
| S2‑160152 | Load balancing and congestion control in eDECOR | Ericsson | imported from 3GU |
| S2‑160153 | Template Overall Evaluation | Ericsson | imported from 3GU |
| S2‑160154 | Solution #1: Solution Evaluation | Ericsson | imported from 3GU |
| S2‑160155 | Overall evaluation solution #2-#4 | Ericsson | imported from 3GU |
| S2‑160156 | Conclusion for eDECOR TR | Ericsson | imported from 3GU |
| S2‑160157 | LS on CS/PS coordination in GERAN Shared Networks | Ericsson | imported from 3GU |
| S2‑160158 | Removing CS/PS-NRI signalling from MSC/SGSN to RNC/BSC | Ericsson | imported from 3GU |
| S2‑160159 | Updates to solution 4 | Ericsson | imported from 3GU |
| S2‑160160 | Evaluation of Solution 4 | Ericsson | imported from 3GU |
| S2‑160161 | Key issue: 3GPP architecture impacts to support network slicing | Ericsson, Deutsche Telekom, Motorola Mobility, Lenovo, KDDI, ZTE, China Telecom, CATT, LG Electronics, China Unicom, AT&T, Qualcomm Incorporated, NTT DOCOMO, NEC, Cisco Systems, Inc., Samsung | imported from 3GU |
| S2‑160162 | NGMN terminology and conceptual outline for Network Slicing | Ericsson, Cisco Systems, Inc., NTT DOCOMO | imported from 3GU |
| S2‑160163 | New key issue: NexGen architecture impacts to support a mobility framework | Ericsson, CATT, NTT DOCOMO, China Telecom, NEC, Qualcomm Incorporated, Motorola Mobility, Lenovo, ZTE, Sprint, Intel, ETRI | imported from 3GU |
| S2‑160164 | Key issue: 3GPP architecture impacts to support logical CN/RAN split | Ericsson, NTT DOCOMO | imported from 3GU |
| S2‑160165 | Key issue: QoS Framework | Ericsson | imported from 3GU |
| S2‑160166 | Key issue: Base functions for a QoS framework | Ericsson | imported from 3GU |
| S2‑160167 | Requirements on optimized UE sleep state and state transitions | Ericsson | imported from 3GU |
| S2‑160168 | New key issue: 3GPP architecture impacts to support session management | Ericsson | imported from 3GU |
| S2‑160169 | Core and Access functional allocation | Ericsson | imported from 3GU |
| S2‑160170 | HSS Initiated update for Dedicated CN Information/Redirection | InterDigital | imported from 3GU |
| S2‑160171 | Solution for Congestion Control based on DCN Type | InterDigital, ZTE | imported from 3GU |
| S2‑160172 | A new NetLoc based solution for key issue#4 | Intel, CMCC, Huawei, ZTE | imported from 3GU |
| S2‑160173 | Evaluation and conclusion on solutions for key issue #4 | Intel | imported from 3GU |
| S2‑160174 | Solution to support multiple PRAs in EPS in a dynamic manner using User Location Reporting | Intel, China Unicom | imported from 3GU |
| S2‑160175 | Standalone SDCF based solution for key issue #1 and #2 | Intel | imported from 3GU |
| S2‑160176 | Update of reference to add a new SA1 TS | LG Electronics | imported from 3GU |
| S2‑160177 | Update of Key Issue#2 | LG Electronics | imported from 3GU |
| S2‑160178 | Solution for Key Issue#1 | LG Electronics | imported from 3GU |
| S2‑160179 | Solution for Key Issue#2 (direct between UEs) | LG Electronics | imported from 3GU |
| S2‑160180 | Solution for Key Issue#2 (via eNB-type RSU) | LG Electronics | imported from 3GU |
| S2‑160181 | Solution for Key Issue#2 (via UE-type RSU) | LG Electronics | imported from 3GU |
| S2‑160182 | Solution for Key Issue#5 (UE-type RSU) | LG Electronics | imported from 3GU |
| S2‑160183 | Solution for Key Issue#5 (eNB-type RSU) | LG Electronics | imported from 3GU |
| S2‑160184 | Operating scenarios considering spectrum usage options for LTE-based V2X | LG Electronics | imported from 3GU |
| S2‑160185 | ePDG selection enhancements related to LI requirements | Alcatel-Lucent | imported from 3GU |
| S2‑160186 | ePDG selection enhancements for the support of Lawful Interception | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| S2‑160187 | Discussion on Inactivity timer for eDRX | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| S2‑160188 | Inactivity timer for eDRX | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| S2‑160189 | Inactivity timer for eDRX | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| S2‑160190 | Evaluation of eDECOR solution#1 and proposal of a variant | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| S2‑160191 | Description of an eDECOR solution#1 variant | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| S2‑160192 | IMEI check for trusted WLAN access to EPC case | Alcatel-Lucent, Nokia Networks | imported from 3GU |
| S2‑160193 | IMEI check for untrusted WLAN access to EPC case | Alcatel-Lucent, Nokia Networks | imported from 3GU |
| S2‑160194 | Scenario for PLMN partitioning | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| S2‑160195 | Solution for PLMN partitioning scenario (key issue 2) | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| S2‑160196 | Managing sponsored data related information solution for key issue#2 | China Unicom, China Mobile, China Telecom, Huawei, HiSilicon | imported from 3GU |
| S2‑160197 | Overall evaluation addressing key issue #1 and #3 for AULC | China Unicom, Intel, Orange | imported from 3GU |
| S2‑160198 | Fix wrong wording on DNS procedure for DECORE | NEC | imported from 3GU |
| S2‑160199 | Add missing text for DNS procedure for DECORE | NEC | imported from 3GU |
| S2‑160200 | LS from CT WG1: LS on ProSe Group Management Parameters | CT WG1 | imported from 3GU |
| S2‑160201 | LS from CT WG1: LS on Extended coverage impact on NAS timers | CT WG1 | imported from 3GU |
| S2‑160202 | LS from CT WG1: LS on CT1 view on LS on SIP deregistration in GERAN and UTRAN (no VOPSSI) | CT WG1 | imported from 3GU |
| S2‑160203 | LS from CT WG1: Reply LS on RCC.14 Device Management Protocol | CT WG1 | imported from 3GU |
| S2‑160204 | LS from CT WG1: LS on NG eCall support for the EU | CT WG1 | imported from 3GU |
| S2‑160205 | LS from CT WG1: LS on the usage of QCI in eMBMS traffic relay | CT WG1 | imported from 3GU |
| S2‑160206 | LS from CT WG1: LS on issues related to MT SMS over SGs delivery in eDRX | CT WG1 | imported from 3GU |
| S2‑160207 | LS from CT WG1: LS on questions on CIoT | CT WG1 | imported from 3GU |
| S2‑160208 | LS from CT WG1: Reply LS on introduction of new establishment cause for mobile-originating calls | CT WG1 | imported from 3GU |
| S2‑160209 | Key issue on overall architecture design for next generation system | China Mobile, CATT, ZTE, CATR | imported from 3GU |
| S2‑160210 | Architecture Assumptions | China Mobile | imported from 3GU |
| S2‑160211 | Key issue on session management for 3GPP network | China Mobile, Qualcomm Incorporated, Ericsson, Intel | imported from 3GU |
| S2‑160212 | FS_RobVoLTE Scope of TR | Huawei, HiSilicon | imported from 3GU |
| S2‑160213 | Robovolte Architectural Requirements | Huawei | imported from 3GU |
| S2‑160214 | Key issue-Robust call in bad LTE coverage with 2G or 3G CS coverage | Huawei, HiSilicon, Intel, China Unicom | imported from 3GU |
| S2‑160215 | Solution for key issue- Robust call in bad LTE coverage with 2G or 3G CS coverage | Huawei, HiSilicon, China Mobile, China Unicom, Intel, China Telecom, KPN, CATT | imported from 3GU |
| S2‑160216 | Skeleton of TR Robovolte | Rapporteur (Huawei) | imported from 3GU |
| S2‑160217 | LS from NGNM Alliance: NGMN Description of Network Slicing Concept | NGMN Alliance | imported from 3GU |
| S2‑160218 | LS from ETSI TC ITS: LTE Support | ETSI TC ITS | imported from 3GU |
| S2‑160219 | LS from GSMA RILTE: LS on Re-Attempting a Voice Call on CS Access based on SIP Response | GSMA RILTE | imported from 3GU |
| S2‑160220 | LS from GSMA RILTE: RCC.14 Device Management Protocol | GSMA RILTE | imported from 3GU |
| S2‑160221 | LS from TSG RAN: LS on introduction of new establishment cause for mobile-originating calls | TSG RAN | imported from 3GU |
| S2‑160222 | Pre-configuration precedence UICC/ME | Gemalto N.V. | imported from 3GU |
| S2‑160223 | Updated Solution for ePDG Selection | Motorola Mobility, Lenovo | imported from 3GU |
| S2‑160224 | Updated ePDG Selection Procedure | Motorola Mobility, Lenovo | imported from 3GU |
| S2‑160225 | Coexistence between ANDSF and LWA | Motorola Mobility, Lenovo | imported from 3GU |
| S2‑160226 | Coexistence between ANDSF and LWA | Motorola Mobility, Lenovo | imported from 3GU |
| S2‑160227 | Clarification on ANDSF precedence | Motorola Mobility, Lenovo | imported from 3GU |
| S2‑160228 | TAU procedure update for CIoT EPS Optimisation | Huawei,HiSilicon | imported from 3GU |
| S2‑160229 | RAU procedure update for CIoT EPS Optimisation | Huawei,HiSilicon | imported from 3GU |
| S2‑160230 | Correction of the decision of NBIFOM mode_23161 | Huawei, HiSilicon | imported from 3GU |
| S2‑160231 | Correction of the decision of NBIFOM mode_23203 | Huawei, HiSilicon | imported from 3GU |
| S2‑160232 | [draft] Reply LS on the decision of NBIFOM mode | Huawei, HiSilicon | imported from 3GU |
| S2‑160233 | Discussion of NBIFOM procedure in SCM and RAN rules handling parameter | Huawei, HiSilicon | imported from 3GU |
| S2‑160234 | Correction of NBIFOM procedure in SCM and RAN rules handling parameter | Huawei, HiSilicon | imported from 3GU |
| S2‑160235 | Co-existence of ANDSF and LWA | Huawei, HiSilicon | imported from 3GU |
| S2‑160236 | Discussion of possible solutions to ePDG selection | Huawei, HiSilicon | imported from 3GU |
| S2‑160237 | Improvement of ePDG selection procedure | Huawei, HiSilicon | imported from 3GU |
| S2‑160238 | NexGen Traffic identification | ZTE | imported from 3GU |
| S2‑160239 | Considerations of GWU GTP-U TEID allocation and IP address Selection via Control Plane function | ZTE | imported from 3GU |
| S2‑160240 | CUPS Handover clarifications | ZTE, KDDI | imported from 3GU |
| S2‑160241 | CUPS Solutions for SGW Service Area | ZTE, KDDI | imported from 3GU |
| S2‑160242 | Key issue on access agnostic core network | LG Electronics | imported from 3GU |
| S2‑160243 | Key issue on energy efficiency of a device | LG Electronics | imported from 3GU |
| S2‑160244 | Update of High level Architectural Requirements | LG Electronics | imported from 3GU |
| S2‑160245 | CUPS Dynamic load consideration for user plane selection | ZTE, KDDI | imported from 3GU |
| S2‑160246 | Solution to Key Issues 3: MME triggered SGW relocation initiated by SGW-C | NEC | imported from 3GU |
| S2‑160247 | Solution to Key Issues 4: Relocation of UP functional based on the UE topological location | NEC | imported from 3GU |
| S2‑160248 | Impacts of network sharing in Solution 1 | TeliaSonera | imported from 3GU |
| S2‑160249 | Alignment of support for DECOR in shared networks | TeliaSonera AB | imported from 3GU |
| S2‑160250 | Introduction of Control Plane CIoT EPS optimization for HLcom | Sony | imported from 3GU |
| S2‑160251 | Key Issue on Architecture principle for Grouping of CP Entities | Sprint | imported from 3GU |
| S2‑160252 | Key Issue on Architecture principle for Interfaces between CP Entities | Sprint | imported from 3GU |
| S2‑160253 | Proposal for NexGen System Architecture Key Issue for Critical Communications Support | U.S. Department of Commerce | imported from 3GU |
| S2‑160254 | NAS Node Selection updates | Ericsson | imported from 3GU |
| S2‑160255 | Introducing support for Non-IP data for CIoT | Ericsson, Cisco? | imported from 3GU |
| S2‑160256 | Introduction of solution 18 – suspend and resume procedure | Ericsson, Alcatel-Lucent, Sony, Nokia Networks | imported from 3GU |
| S2‑160257 | Introducing support for Non-IP data for EC-EGPRS | Ericsson, Orange | imported from 3GU |
| S2‑160258 | EMM signalling for indicating SMS | Ericsson | imported from 3GU |
| S2‑160259 | High level description of Non-IP datadata | Ericsson | imported from 3GU |
| S2‑160260 | New work item on Non-IP for Cellular IoT for EC-EGPRS | Ericsson, Orange, MediaTek | imported from 3GU |
| S2‑160261 | Priority sharing for concurrent sessions, IMS | Ericsson | imported from 3GU |
| S2‑160262 | Priority sharing for concurrent sessions | Ericsson | imported from 3GU |
| S2‑160263 | Update Solution #1 | Ericsson | imported from 3GU |
| S2‑160264 | Updates to 3GPP-WLAN mobility procedure using GMLC/LRF | Ericsson | imported from 3GU |
| S2‑160265 | New Key Issue: Resource Management for Mission Critical Group Communications | Motorola Solutions | imported from 3GU |
| S2‑160266 | Priority Treatment based on RRC Establishment Cause | Applied Communication Sciences, OEC, AT&T | imported from 3GU |
| S2‑160267 | Location of the resource allocation function (F-TEID) | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| S2‑160268 | Priority Treatment based on RRC Establishment Cause | Applied Communication Sciences, OEC, AT&T | imported from 3GU |
| S2‑160269 | CIoT-centric single node EPS architecture | Intel, AT&T, Cisco Systems Inc, .… | imported from 3GU |
| S2‑160270 | ePDG Selection Update For LI | Rogers Communications | imported from 3GU |
| S2‑160271 | ePDG Selection Procedure Update for LI | Rogers Communications | imported from 3GU |
| S2‑160272 | ePDG selection consistency | BlackBerry UK Ltd. | imported from 3GU |
| S2‑160273 | Handling of a 5.12s eDRX cycle | INTERDIGITAL COMMUNICATIONS | imported from 3GU |
| S2‑160274 | Handling of a 5.12s eDRX cycle | INTERDIGITAL COMMUNICATIONS | imported from 3GU |
| S2‑160275 | Introduction of non-IP data delivery via the SCEF for cellular IoT | Intel, Cisco Systems Inc, AT&T, LG Electronics | imported from 3GU |
| S2‑160276 | Introduction of SCEF Connectivity Service for Control Plane CIoT EPS optimization | Cisco Systems Inc., Intel, AT&T | imported from 3GU |
| S2‑160277 | Options to establish SCEF connection for Non-IP data for CIoT | Cisco Systems Inc., Intel | imported from 3GU |
| S2‑160278 | Clarification on provisioning authorization information about PLMNs for ProSe UE-to-Network Relay and Remote UE | LG Electronics | imported from 3GU |
| S2‑160279 | Clarification for inter-PLMN discovery transmission support | LG Electronics | imported from 3GU |
| S2‑160280 | Update to TR Skeleton for the Study on Architecture for Next Generation System | Nokia Networks, China Mobile | imported from 3GU |
| S2‑160281 | Discussion on Solution Evaluation | T-Mobile USA INC | imported from 3GU |
| S2‑160282 | Solution for Key Issue#4 for PC5 based transmission | LG Electronics | imported from 3GU |
| S2‑160283 | Key issue: Architecture principle for next generation systems | Nokia Networks, Verizon, Huawei | imported from 3GU |
| S2‑160284 | Additional Architectural Assumption | T-Mobile USA INC | imported from 3GU |
| S2‑160285 | Discussion on treatment of 8YY numbers | T-Mobile USA INC | imported from 3GU |
| S2‑160286 | Key issue: QoS Framework | Nokia Networks, AT&T, Deutsche Telekom AG, China Mobile, Ericsson, Intel, Qualcomm Incorporated, ZTE, ETRI, KT | imported from 3GU |
| S2‑160287 | Evaluation Criteria for Key Issue 4 Solutions | T-Mobile USA INC | imported from 3GU |
| S2‑160288 | Key issue: Coexistence and Migration | Nokia Networks | imported from 3GU |
| S2‑160289 | Reference Version of TR 23.719 Service Domain Centralization | T-Mobile USA Inc. | imported from 3GU |
| S2‑160290 | Solution for Key Issue 3 (Inbound Roamers) | T-Mobile USA INC | imported from 3GU |
| S2‑160291 | Solution for Key Issue 4 (Outbound Roamers) | T-Mobile USA INC | imported from 3GU |
| S2‑160292 | Service Domain Centralization | T-Mobile USA | imported from 3GU |
| S2‑160293 | Discussion on ePDG selection | T-Mobile USA INC | imported from 3GU |
| S2‑160294 | UE IP Address Allocation | Samsung | imported from 3GU |
| S2‑160295 | GTP-U IP address assignment and TEIDs allocation | Samsung | imported from 3GU |
| S2‑160296 | SEW2-ePDG Selection Solution | Rogers Communications | imported from 3GU |
| S2‑160297 | Introduction of non-IP data delivery via the SCEF for cellular IoT | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| S2‑160298 | Correct Event and Trigger Name – Availability after DDN Failure | Alcatel-Lucent | imported from 3GU |
| S2‑160299 | Correction of 3GPP2 specification reference | Alcatel-Lucent | imported from 3GU |
| S2‑160300 | MT SMS procedures for UEs in extended idle mode DRX | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Nokia Networks | imported from 3GU |
| S2‑160301 | MT SM retransmission by the SMS GMSC to a UE in eDRX | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Nokia Networks | imported from 3GU |
| S2‑160302 | Prioritized SM retransmission by the SMS SC when the UE becomes reachable | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Nokia Networks | imported from 3GU |
| S2‑160303 | Remove T5 | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Nokia Networks | imported from 3GU |
| S2‑160304 | Remove IPv4 from ProSe UE-to-Network Relay operation | Qualcomm Incorporated | imported from 3GU |
| S2‑160305 | The assumptions for overall architecture | Huawei, HiSilicon | imported from 3GU |
| S2‑160306 | The definition for Network Function | Huawei, HiSilicon, China Mobile | imported from 3GU |
| S2‑160307 | Key Issues Related to Heterogeneous Access Networks Integration | Huawei, HiSilicon | imported from 3GU |
| S2‑160308 | Discussion on DCN selection based on Usage Type and DCN Type | Huawei, Hisilicon | imported from 3GU |
| S2‑160309 | DCN serving node overload control based on the congestion level | Huawei, Hisilicon | imported from 3GU |
| S2‑160310 | Prioritizing V2X study to align with RAN | Qualcomm Incorporated | imported from 3GU |
| S2‑160311 | Changes to ProSe Architecture for V2X support | Qualcomm Incorporated | imported from 3GU |
| S2‑160312 | V2X reference architecture and RSU discussion | Qualcomm Incorporated, LG Electronics | imported from 3GU |
| S2‑160313 | Solution proposal on Key Issue 2 “Congestion Control based on UE Usage Type” | LG Electronics | imported from 3GU |
| S2‑160314 | Introduction of Control Plane CIoT EPS optimization | Alcatel-lucent?, MediaTek?, NEC?, Intel?,Qualcomm | imported from 3GU |
| S2‑160315 | Correction on Targeted RPAUID in the monitor response message | Huawei, Hisilicon | imported from 3GU |
| S2‑160316 | Key issue for EPC impacts | Huawei, Hisilicon | imported from 3GU |
| S2‑160317 | Key issue for enhancing positioning precision | Huawei, Hisilicon | imported from 3GU |
| S2‑160318 | Solution for service authorization procedure | Huawei, Hisilicon | imported from 3GU |
| S2‑160319 | Feasibility Study on Wearable Device | Huawei, Hisilicon, | imported from 3GU |
| S2‑160320 | Mapping of ProSe Per Packet Priority to QCI | Qualcomm Incorporated | imported from 3GU |
| S2‑160321 | Discussion on UE-initiated IP flow mapping/access usability change/RAN rule indication procedure in GERAN/UTRAN, S2a MCM and S2b | ZTE | imported from 3GU |
| S2‑160322 | Introduction of attach procedure changes for CIoT EPS optimization | Alcatel-lucent?, Vodafone?, Qualcomm | imported from 3GU |
| S2‑160323 | Correction to UE-initiated IP flow mapping/access usability change/RAN rule indication procedure in GERAN/UTRAN, S2a MCM and S2b | ZTE | imported from 3GU |
| S2‑160324 | Evaluation of “HSS Initiated update for Dedicated CN Information/Redirection” & Conclusion | InterDigital | imported from 3GU |
| S2‑160325 | Evaluation of “Solution for Congestion based on DCN Type” & Conclusion | InterDigital | imported from 3GU |
| S2‑160326 | Clarification on Provisioning Mapping Rules of QCI and ProSe Per-Packet Priority in ProSe UE-to-Network Relay | LG Electronics France | imported from 3GU |
| S2‑160327 | Solution: ePDG Selection for emergency services in phase 2 | Qualcomm Inc. | imported from 3GU |
| S2‑160328 | Key Issue on Session Continuity and Mobility in the Next Generation System Architecture | Qualcomm Incorporated, Motorola Mobility, Lenovo, Cisco Systems, Inc. | imported from 3GU |
| S2‑160329 | Key Issue on feasibility study of a minimizing access dependencies of the NextGen core network and the Interface between access networks and the core network | Qualcomm Incorporated, ZTE, KDDI, Nokia Networks | imported from 3GU |
| S2‑160330 | Key Issue on Traffic Anchoring and Splitting | Qualcomm Incorporated | imported from 3GU |
| S2‑160331 | Key Issue on Traffic Offloading and User Plane Optimization in the Next Generation System Architecture | Qualcomm Incorporated | imported from 3GU |
| S2‑160332 | Discussion on treatment of 8YY numbers | T-Mobile USA INC | imported from 3GU |
| S2‑160333 | Skeleton of TR 23.773 on FS_GENCEF | Samsung | imported from 3GU |
| S2‑160334 | Clarification of solution #8 on using only TAI/SAI as the location information | China Mobile | imported from 3GU |
| S2‑160335 | Architectural Requirements on providing multiple connections | LG Electronics | imported from 3GU |
| S2‑160336 | 3GPP system aspects to support the connectivity via a relay UE | LG Electronics, Sony Mobile | imported from 3GU |
| S2‑160337 | Solutions for Key issue#3 | LG Electronics, LG Uplus | imported from 3GU |
| S2‑160338 | Conclusion proposal for Key issue #3 (Determination of the ID of the visited PLMN at IMS entities in HPLMN) | LG Electronics, LG Uplus, SK Telecom | imported from 3GU |
| S2‑160339 | Clarification on SRVCC support | China Mobile | imported from 3GU |
| S2‑160340 | Evaluation and conclusion on key issue 4 | China Mobile | imported from 3GU |
| S2‑160341 | Scope of TR 23.773 on FS_GENCEF | Samsung | imported from 3GU |
| S2‑160342 | Key issue: Vertical service accommodation | China Telecom, CATT, Nokia, Sumsung, Huawei | imported from 3GU |
| S2‑160343 | Key issue: Information storage and management | China Telecom, China Unicom | imported from 3GU |
| S2‑160344 | Key issue: network capability exposure | China Telecom, KDDI, CATT | imported from 3GU |
| S2‑160345 | MM procedure handling for CIoT UP Optimization | LG Electronics | imported from 3GU |
| S2‑160346 | Key issues on load balancing in DCN | ZTE Corporation, NEC | imported from 3GU |
| S2‑160347 | Solution of load balance in DCN | ZTE Corporation, NEC | imported from 3GU |
| S2‑160348 | SCEF solution for key issue#1 | ZTE | imported from 3GU |
| S2‑160349 | DL data handling for CP optimisation in TAU procedure | Huawei, Hisilicon | imported from 3GU |
| S2‑160350 | Bearer deactivation with Control Plane CIoT optimisation | Huawei, Hisilicon | imported from 3GU |
| S2‑160351 | Discussion on RSU | Huawei, Hisilicon | imported from 3GU |
| S2‑160352 | Consideration on the architecture options for V2X | Huawei, Hisilicon | imported from 3GU |
| S2‑160353 | V2X reference architecture | Huawei, Hisilicon | imported from 3GU |
| S2‑160354 | Key issue on V2X QoS | Huawei, Hisilicon | imported from 3GU |
| S2‑160355 | Introducing support for Non-IP data for CIoT | Ericsson?, Cisco?, ZTE | imported from 3GU |
| S2‑160356 | Key Issue on Unified Policy Framework | Huawei, Hisilicon | imported from 3GU |
| S2‑160357 | Evaluation of Solution #5 | Huawei, Hisilicon | imported from 3GU |
| S2‑160358 | [draft] Reply LS on NGMN Description of Network Slicing Concept | LG Electronics Inc. | imported from 3GU |
| S2‑160359 | Solution for key issue- Robust call in bad LTE coverage with 2G or 3G CS coverage | Huawei, HiSilicon, China Mobile, China Unicom, Intel, China Telecom, KPN, CATT, Deutsche Telekom, Teliasonera | imported from 3GU |
| S2‑160360 | Key issue-Robust call in bad LTE coverage with 2G or 3G CS coverage | Huawei, HiSilicon, Intel, China Unicom, Deutsche Telekom, China Mobile, Teliasonera | imported from 3GU |
| S2‑160361 | Update solution 4 of eDecor | CATT | imported from 3GU |
| S2‑160362 | Solution #4: Solution Evaluation | CATT | imported from 3GU |
| S2‑160363 | Definition of scale-in/scale-out | CATT | imported from 3GU |
| S2‑160364 | Intra-RAT mobility for NB-IoT UE in RRC connected state | Huawei, Hisilicon | imported from 3GU |
| S2‑160365 | Paging response for MT data with Control Plane Optimization | Huawei, Hisilicon | imported from 3GU |
| S2‑160366 | Discussion on issues on MT SMS delivery in eDRX | Huawei, HiSilicon | imported from 3GU |
| S2‑160367 | Removal of new SGs cause for MT SMS over SGs in eDRX | Huawei, HiSilicon | imported from 3GU |
| S2‑160368 | An extended NetLoc procedure for Geographical Information | ZTE, Intel | imported from 3GU |
| S2‑160369 | Evaluation and Conclusion on Determination of the ID of the visited PLMN | ZTE | imported from 3GU |
| S2‑160370 | Conclusion on Local Number Translation and Routing | ZTE | imported from 3GU |
| S2‑160371 | Key issue on the Registration and Authentication in the SeDoC | ZTE | imported from 3GU |
| S2‑160372 | Solution to the Key Issue 4 - Outbound Roamers to non-Enhanced Networks | ZTE | imported from 3GU |
| S2‑160373 | Discussion on the issues in the EIEI | ZTE | imported from 3GU |
| S2‑160374 | Modification of a Note in Match Report procedures for restricted discovery | ITRI | imported from 3GU |
| S2‑160375 | The procedure of removal of one access from the Multi-access PDN connection | ZTE | imported from 3GU |
| S2‑160376 | Evaluation of key issue3 | ZTE Corporation | imported from 3GU |
| S2‑160377 | Working Assumption: Support of Network Instances shared by multiple 3rd parties | ZTE | imported from 3GU |
| S2‑160378 | Prose withdrawal from HSS | Nokia Networks, Alcatel-Lucent | imported from 3GU |
| S2‑160379 | Working Assumption: LTE Radio Access continuation support in NextGen AN for LTE radio access | ZTE | imported from 3GU |
| S2‑160380 | Prose withdrawal from HSS | Nokia Networks, Alcatel-Lucent | imported from 3GU |
| S2‑160381 | Providing Subscriber ID – Anonymous IMS emergency call | Nokia Networks, Deutsche Telekom | imported from 3GU |
| S2‑160382 | Providing subscriber ID in case of anonymous emergency calls | Nokia Netorks, Deutsche Telekom | imported from 3GU |
| S2‑160383 | 3GPP architecture impacts on mobility management with session continuity | Huawei | imported from 3GU |
| S2‑160384 | Coexistence between ANDSF and LWA/LWIP | BlackBerry UK Ltd. | imported from 3GU |
| S2‑160385 | Local number translation conclusion | Nokia Networks, Alcatel-Lucent | imported from 3GU |
| S2‑160386 | Coexistence between ANDSF and LWA/LWIP | BlackBerry UK Ltd | imported from 3GU |
| S2‑160387 | Mobility aspect of WLAN and 3GPP CS | Nokia Networks, Alcatel-Lucent | imported from 3GU |
| S2‑160388 | Discussion on RAN2 LS concerning LWIP packet re-ordering | BlackBerry UK Ltd., | imported from 3GU |
| S2‑160389 | VoLTE – SRVCC temporary rejection | Nokia Networks, Alcatel-Lucent | imported from 3GU |
| S2‑160390 | Response to questions 6, 7 and 8 in CT WG1 LS on use of Release Assistance Information for CIoT | BlackBerry UK Ltd. | imported from 3GU |
| S2‑160391 | VPLMN ID solution selection considerations | Nokia Networks, Alcatel-Lucent | imported from 3GU |
| S2‑160392 | VPLMN ID to TAS in 3rd party registration | Nokia Networks, Alcatel-Lucent | imported from 3GU |
| S2‑160393 | RSU’s role in V2I and V2N | Nokia Networks, Alcatel-Lucent | imported from 3GU |
| S2‑160394 | QoS signalling for EVS-VBR | Qualcomm Incorporated | imported from 3GU |
| S2‑160395 | Introducing VBR parameter in PCC rules | Qualcomm Incorporated | imported from 3GU |
| S2‑160396 | Introducing VBR parameter in dedicated bearers | Qualcomm Incorporated | imported from 3GU |
| S2‑160397 | Reply LS on QoS for EVS-VBR Codec Operation | Qualcomm Incorporated | imported from 3GU |
| S2‑160398 | Mapping of ProSe Per Packet Priority to QCI | Qualcomm Incorporated | imported from 3GU |
| S2‑160399 | Discussion of a new AS Indicator for eCall over IMS in Release14 | Qualcomm Incorporated | imported from 3GU |
| S2‑160400 | Addition of eCall based on IMS Emergency Services | Qualcomm Incorporated | imported from 3GU |
| S2‑160401 | Addition of eCall for IMS Emergency Services | Qualcomm Incorporated | imported from 3GU |
| S2‑160402 | Comments on MSD Transfer for eCall over IMS | Qualcomm Incorporated | imported from 3GU |
| S2‑160403 | Introduction of Control Plane CIoT EPS optimization | Alcatel-lucent?, MediaTek?, NEC?, Intel?,Qualcomm | imported from 3GU |
| S2‑160404 | Mobility for UEs supporting CIOT optimisations | Qualcomm Incorporated | imported from 3GU |
| S2‑160405 | Queues at SCEF for non-IP traffic | Neul | imported from 3GU |
| S2‑160406 | Correction to Charging architecture | Alcatel-lucent, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| S2‑160407 | Updating Discoverer Request procedures to ensure latest metadata for the Discoverer UE | ITRI | imported from 3GU |
| S2‑160408 | Introducing CIoT Optimisations | Alcatel-Lucent?, Nokia Networks?, MediaTek?,Verizon?, Ericsson?, Vodafone, KPN | imported from 3GU |
| S2‑160409 | Proposed study of enhancements to Isolated E-UTRAN Operation for Public Safety (IOPS) | General Dynamics UK Ltd. | imported from 3GU |
| S2‑160410 | How SCEF connection established - EMM model | Samsung, CATT | imported from 3GU |
| S2‑160411 | New Study Item for Enhanced Isolated E-UTRAN Operation for Public Safety | General Dynamics UK Ltd. | imported from 3GU |
| S2‑160412 | Modification of match report procedures | Huawei, HiSilicon, LG Electronics | imported from 3GU |
| S2‑160413 | [DRAFT] Reply LS on RAN2 agreements for inter-carrier/Inter-PLMN sidelink discovery | Huawei, HiSilicon | imported from 3GU |
| S2‑160414 | Discussion on RAN2 agreements for inter-carrier/Inter-PLMN sidelink discovery | Huawei, HiSilicon | imported from 3GU |
| S2‑160415 | Modification of announcing alert procedures | Huawei, HiSilicon | imported from 3GU |
| S2‑160416 | Solution to Key Issue 4 | Huawei, HiSilicon | imported from 3GU |
| S2‑160417 | Consideration for TA List Management in MME | Huawei, HiSilicon | imported from 3GU |
| S2‑160418 | Lawful interception in split architectures | Huawei, HiSilicon | imported from 3GU |
| S2‑160419 | LS on Lawful interception in split EPC architecture | Huawei | imported from 3GU |
| S2‑160420 | proposal 1 under the DP 160410 on S2-154452 | Samsung | imported from 3GU |
| S2‑160421 | proposal 2 and 3 under the 160410 on S2-154451 | Samsung | imported from 3GU |
| S2‑160422 | DP support multiple SCS/AS connection for NIDD via SCEF | Samsung | imported from 3GU |
| S2‑160423 | Introduction of non-IP data delivery via the SCEF for cellular IoT | Samsung, Alcatel-Lucent, Cisco Systems Inc, Nokia Networks, Intel | imported from 3GU |
| S2‑160424 | Clarification on the Discovery Entry ID in Restricted discovery | Samsung | imported from 3GU |
| S2‑160425 | Update information storage of HSS | Samsung | imported from 3GU |
| S2‑160426 | Modification of the reporting of monitor update result | Samsung | imported from 3GU |
| S2‑160427 | V2X architecture reference model | Samsung | imported from 3GU |
| S2‑160428 | key issue update for vehicle identification | Samsung | imported from 3GU |
| S2‑160429 | Co-existence between ANDSF and LWA | Ericsson | imported from 3GU |
| S2‑160430 | Co-existence between ANDSF and LWA | Ericsson | imported from 3GU |
| S2‑160431 | Solution to Key Issue 1 – Single gateway controller | Huawei, HiSilicon | imported from 3GU |
| S2‑160432 | Skeleton of TR 23.773 on FS_GENCEF | Samsung | imported from 3GU |
| S2‑160433 | Scope of TR 23.773 on FS_GENCEF | Samsung | imported from 3GU |
| S2‑160434 | Key issue proposal: Minimization of signaling load | Samsung | imported from 3GU |
| S2‑160435 | Architectural assumptions and requirements for FS_GENCEF | Samsung | imported from 3GU |
| S2‑160436 | New solution: Group management via HSS | Samsung | imported from 3GU |
| S2‑160437 | New key issue proposal on network capability exposure | Samsung | imported from 3GU |
| S2‑160438 | No multiple External IDs or MSISDNs for monitoring event configuration | Samsung | imported from 3GU |
| S2‑160439 | List of External Identifiers in the Subscription Data | Samsung | imported from 3GU |
| S2‑160440 | List of External Identifiers in the Subscription Data | Samsung | imported from 3GU |
| S2‑160441 | List of External Identifiers in the Subscription Data | Samsung | imported from 3GU |
| S2‑160442 | Introduction of Control Plane CIoT EPS optimization | Alcatel-lucent, MediaTek, NEC, Intel,Qualcomm; Nokia Networks | imported from 3GU |
| S2‑160443 | Solution for Key Issue 1 (Transition to Single Service Profile in IMS) | Deutsche Telekom AG | imported from 3GU |
| S2‑160444 | Solution for Key Issue 2 (Emergency Calls Routed via IMS Service Domain) | Deutsche Telekom AG | imported from 3GU |
| S2‑160445 | Update to Solution 5 | Intel, Nokia, NTT DOCOMO | imported from 3GU |
| S2‑160446 | Evaluation and conclusion on Key Issue #1 | Intel, Nokia, NTT DOCOMO | imported from 3GU |
| S2‑160447 | NexGen Architectural Assumptions | Deutsche Telekom AG | imported from 3GU |
| S2‑160448 | Introduction of attach procedure changes for CIoT EPS optimization | Alcatel-lucent, Vodafone, Qualcomm; Nokia Networks | imported from 3GU |
| S2‑160449 | Non-roaming baseline architecture with C/U-plane split | Intel | imported from 3GU |
| S2‑160450 | Key Issue on Interworking and Migration | Intel | imported from 3GU |
| S2‑160451 | Key Issue on Service continuity | Intel | imported from 3GU |
| S2‑160452 | Key Issue on Efficient user plane paths | Intel | imported from 3GU |
| S2‑160453 | Solution to Key Issue on QoS Framework | Intel | imported from 3GU |
| S2‑160454 | Supporting eDRX in unsynchronized LTE Networks | NTT DOCOMO | imported from 3GU |
| S2‑160455 | Supporting eDRX in unsynchronized E-UTRAN networks | NTT DOCOMO | imported from 3GU |
| S2‑160456 | MT SMS for eDRX in unsynchronized E-UTRAN networks | NTT DOCOMO | imported from 3GU |
| S2‑160457 | Updates to Solution #3 | NTT DOCOMO, DT | imported from 3GU |
| S2‑160458 | Evaluation of Key Issue #3: PLMN-ID determination at IMS Entities | NTT DOCOMO | imported from 3GU |
| S2‑160459 | Evaluation and conclusions for Key Issue #4: Local number translation and routing | NTT DOCOMO | imported from 3GU |
| S2‑160460 | Key Issue on Integration of NexGen 3GPP RAT with NexGen Core | NTT DOCOMO | imported from 3GU |
| S2‑160461 | New Key issue proposal on CS data support by SeDoC architecture | Deutsche Telekom AG | imported from 3GU |
| S2‑160462 | SDCI Key Issue 1 – Provisioning of Sponsor Packet Flow Descriptions via SCEF and PCRF | Openet | imported from 3GU |
| S2‑160463 | SDCI Key Issue 1 and 2 Solution Discussion | Openet | imported from 3GU |
| S2‑160464 | SA WG2 Work Planning Worksheet | SA WG2 Chairman | imported from 3GU |
| S2‑160465 | Introduction of support for NB-IoT | Vodafone | imported from 3GU |
| S2‑160466 | UE Capability Handling for Control Plane CIoT EPS optimization | Vodafone | imported from 3GU |
| S2‑160467 | V8 Solution 1 update and evaluation | Orange, Telecom Italia | imported from 3GU |
| S2‑160468 | Solution to Key Issue 1 - User Plane Function Generating CDR | Huawei, HiSilicon | imported from 3GU |
| S2‑160469 | Considerations and Way Forward on SCEF and non-IP PDN connections | Vodafone | imported from 3GU |
| S2‑160470 | DRAFT response to LS on questions on CIoT | VODAFONE Group Plc | imported from 3GU |
| S2‑160471 | 5G Architectural requirement for energy efficiency | Orange | imported from 3GU |
| S2‑160472 | Addition of ProSe Per-Packet Priority & QCI in the TMGI Monitoring Request procedure | InterDigital | imported from 3GU |
| S2‑160473 | APN AMBR change at a certain time on Gx | Alcatel-Lucent, Verizon, Oracle, Huawei, Ericsson, Cisco | imported from 3GU |
| S2‑160474 | MT SM transmission to a UE in eDRX within the SM-Delivery-Start-Time/Timer | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Nokia Networks | imported from 3GU |
| S2‑160475 | New Study Item for Isolated E-UTRAN Operation for Public Safety in Limited Backhaul scenario | Orange, Telecom Italia | imported from 3GU |
| S2‑160476 | QoS for solution 2 and RRC establishment 'causes' for NB-IoT | Vodafone | imported from 3GU |
| S2‑160477 | Draft Reply to LS on NB-IoT work progress in RAN2 | VODAFONE Group Plc | imported from 3GU |
| S2‑160478 | [DRAFT] LS on transport option for downlink from eNB-type RSU for V2X services | LG Electronics | imported from 3GU |
| S2‑160479 | What is the meaning of access independence? | Intel | imported from 3GU |
| S2‑160480 | MT NIDD procedures for UEs in extended idle mode DRX | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| S2‑160481 | Introduction of non-IP data delivery via the SCEF for cellular IoT | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| S2‑160482 | 'UE reachability' event reports for UEs using extended idle mode DRX | Convida Wireless | imported from 3GU |
| S2‑160483 | 'UE reachability' event reports for UEs using extended idle mode DRX | Convida Wireless | imported from 3GU |
| S2‑160484 | List of Questions for SA WG2 asked during the CT WG4 Telco on CIoT | Alcatel-Lucent | imported from 3GU |
| S2‑160485 | LS from RAN WG3: LS on Multiple uplink NAS PDUs in CIoT optimization | RAN WG3 | imported from 3GU |
| S2‑160486 | LS from RAN WG2: Reply LS on questions on CIoT | RAN WG2 | imported from 3GU |
| S2‑160487 | LS from RAN WG3: LS on questions on NB-IoT | RAN WG3 | imported from 3GU |
| S2‑160488 | LS from RAN WG3: LS on Release of Control Plane for DONAS | RAN WG3 | imported from 3GU |
| S2‑160489 | LS from RAN WG3: LS on CIOT optimization | RAN WG3 | imported from 3GU |
| S2‑160490 | [DRAFT] Reply LS to LS on APN AMBR change at a certain time on Gx | Alcatel-Lucent | imported from 3GU |
| S2‑160491 | Introduction of Control Plane CIoT EPS optimization | BlackBerry UK Ltd. | imported from 3GU |
| S2‑160492 | Draft Agenda for SA WG2#113 | SA WG2 Chairman | imported from 3GU |
| S2‑160493 | New Study Item for Isolated E-UTRAN Operation for Public Safety in Limited Backhaul scenario | Orange, Telecom Italia | imported from 3GU |
| S2‑160494 | New Study Item for Enhanced Isolated E-UTRAN Operation for Public Safety | General Dynamics UK Ltd., Orange | imported from 3GU |
| S2‑160495 | New work item on Non-IP for Cellular IoT for EC-EGPRS | Ericsson, Orange, MediaTek | imported from 3GU |
| S2‑160496 | New SID on Feasibility study on the Support of Emergency services over WLAN (FS_SEW2) | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Deutsche Telekom, Broadcom, Sprint, Verizon, AT&T, Nokia Networks, Orange, T-Mobile USA, LG Electronics, TCS, Motorola Mobility, Lenovo, Ericsson | imported from 3GU |
| S2‑160497 | New WID on the Support of Emergency services over WLAN - phase 2 (SEW2) | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Deutsche Telekom, Broadcom, Sprint, Verizon, AT&T, Nokia Networks | imported from 3GU |
| S2‑160498 | Skeleton of TR 23.773 on FS_GENCEF | Samsung | imported from 3GU |
| S2‑160499 | Scope of TR 23.773 on FS_GENCEF | Samsung | imported from 3GU |
| S2‑160500 | Architectural assumptions and requirements for FS_GENCEF | Samsung | imported from 3GU |
| S2‑160501 | Key issue of Group Creation and Modification | Convida Wireless, Samsung | imported from 3GU |
| S2‑160502 | Key issue proposal: Minimization of signaling load | Samsung | imported from 3GU |
| S2‑160503 | List of External Identifiers in the Subscription Data | Samsung | imported from 3GU |
| S2‑160504 | Determination of MB2/Ns interface connection agreement | Samsung | imported from 3GU |
| S2‑160505 | [DRAFT] Response LS on RAN WG2 agreements on extended DRX | SA WG2 | imported from 3GU |
| S2‑160506 | [DRAFT] LS on issues related to MT SMS over SGs delivery in eDRX | SA WG2 | imported from 3GU |
| S2‑160507 | Alignment of support for DECOR in shared networks | TeliaSonera AB | imported from 3GU |
| S2‑160508 | Fix wrong wording on DNS procedure for DECORE | NEC | imported from 3GU |
| S2‑160509 | Add missing text for DNS procedure for DECORE | NEC | imported from 3GU |
| S2‑160510 | Support of CSG, LIPA, and SIPTO@LN functions for dual connectivity | Samsung | imported from 3GU |
| S2‑160511 | [DRAFT] Reply LS on RAN WG3 agreements on DC enhancements for LTE | SA WG2 | imported from 3GU |
| S2‑160512 | V2X reference architecture and RSU discussion | Qualcomm Incorporated, LG Electronics | imported from 3GU |
| S2‑160513 | New Key Issue#xx: Localized MBMS Support | Huawei, Hisilicon | imported from 3GU |
| S2‑160514 | V2X reference architecture | Huawei, Hisilicon | imported from 3GU |
| S2‑160515 | RSU's role in V2I and V2N | Nokia Networks, Alcatel-Lucent | imported from 3GU |
| S2‑160516 | Reserved for Puneet's parallel sessions | - | imported from 3GU |
| S2‑160517 | [DRAFT] LS on guidance by SA WG2 on CIOT | SA WG2 | imported from 3GU |
| S2‑160518 | eDECOR Defintions | Ericsson | imported from 3GU |
| S2‑160519 | Discussion on DCN selection based on Usage Type and DCN Type | Huawei, Hisilicon | imported from 3GU |
| S2‑160520 | Description of an eDECOR solution#1 variant | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| S2‑160521 | Solution #1: Solution Evaluation | Ericsson | imported from 3GU |
| S2‑160522 | eDecor Key Issue 1 - solutions evaluation and conclusion | NEC | imported from 3GU |
| S2‑160523 | CIoT Drafting Output | Intel (Convenor) | imported from 3GU |
| S2‑160524 | HSS Initiated update for Dedicated CN Information/Redirection | InterDigital | imported from 3GU |
| S2‑160525 | Inactivity timer for eDRX | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| S2‑160526 | Inactivity timer for eDRX | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| S2‑160527 | Handling of a 5.12s eDRX cycle | INTERDIGITAL COMMUNICATIONS | imported from 3GU |
| S2‑160528 | Handling of a 5.12s eDRX cycle | INTERDIGITAL COMMUNICATIONS | imported from 3GU |
| S2‑160529 | [DRAFT] LS on Handling of a 5.12s eDRX cycle | SA WG2 | imported from 3GU |
| S2‑160530 | [DRAFT] LS on issues related to MT SMS over SGs delivery in eDRX | SA WG2 | imported from 3GU |
| S2‑160531 | Update of Key Issue#2 | LG Electronics | imported from 3GU |
| S2‑160532 | Key issue on V2X QoS | Huawei, Hisilicon | imported from 3GU |
| S2‑160533 | Changes to ProSe Architecture for V2X support | Qualcomm Incorporated | imported from 3GU |
| S2‑160534 | V2X Authorisation and parameter configurations | Ericsson | imported from 3GU |
| S2‑160535 | Solution for Key Issue#2 (direct between UEs) | LG Electronics | imported from 3GU |
| S2‑160536 | Solution for Key Issue#2 (via eNB-type RSU) | LG Electronics | imported from 3GU |
| S2‑160537 | List of External Identifiers in the Subscription Data | Samsung | imported from 3GU |
| S2‑160538 | [DRAFT] Reply LS on RAN WG3 agreements on DC enhancements for LTE | SA WG2 | imported from 3GU |
| S2‑160539 | Architectural assumptions and requirements for FS_GENCEF | Samsung | imported from 3GU |
| S2‑160540 | LS on issues related to MT SMS over SGs delivery in eDRX | SA WG2 | imported from 3GU |
| S2‑160541 | CIoT Drafting Output | Intel (Convenor) | imported from 3GU |
| S2‑160542 | V2X reference architecture and RSU discussion | Qualcomm Incorporated, LG Electronics | imported from 3GU |
| S2‑160543 | V2X reference architecture | Huawei, Hisilicon | imported from 3GU |
| S2‑160544 | RSU's role in V2I and V2N | Nokia Networks, Alcatel-Lucent | imported from 3GU |
| S2‑160545 | Key issue on V2X QoS | Huawei, Hisilicon | imported from 3GU |
| S2‑160546 | Reserved for Puneet's parallel sessions | - | imported from 3GU |
| S2‑160547 | Reserved for Puneet's parallel sessions | - | imported from 3GU |
| S2‑160548 | Prose withdrawal from HSS | Nokia Networks, Alcatel-Lucent | imported from 3GU |
| S2‑160549 | Prose withdrawal from HSS | Nokia Networks, Alcatel-Lucent | imported from 3GU |
| S2‑160550 | LS on the Revocation of Discovery Filters | SA WG2 | imported from 3GU |
| S2‑160551 | Clarification on the Discovery Entry ID in Restricted discovery | Samsung | imported from 3GU |
| S2‑160552 | Addition of ProSe Per-Packet Priority & QCI in the TMGI Monitoring Request procedure | InterDigital | imported from 3GU |
| S2‑160553 | Modification of announcing alert procedures | Huawei, HiSilicon | imported from 3GU |
| S2‑160554 | Clarification on provisioning authorization information about PLMNs for ProSe UE-to-Network Relay and Remote UE | LG Electronics | imported from 3GU |
| S2‑160555 | Clarification for inter-PLMN discovery transmission support | LG Electronics | imported from 3GU |
| S2‑160556 | Correction on Targeted RPAUID in the monitor response message | Huawei, Hisilicon | imported from 3GU |
| S2‑160557 | Adding Relay Service Code to Additional Information Message | Nokia Networks | imported from 3GU |
| S2‑160558 | LS from ONF: Prepublication of SDN architecture issue 1.1 | Open Networking Foundation | imported from 3GU |
| S2‑160559 | Consideration for performing LI functionality | Cisco Systems, Inc. | imported from 3GU |
| S2‑160560 | Lawful interception in split architectures | Huawei, HiSilicon | imported from 3GU |
| S2‑160561 | [Draft] LS on Lawful interception in split EPC architecture | SA WG2 | imported from 3GU |
| S2‑160562 | Control plane function providing pre-allocated GTP-U IP address and TEID to the user plane function (during restoration scenario) | Cisco Systems, Inc. | imported from 3GU |
| S2‑160563 | Location of the resource allocation function (F-TEID) | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, ZTE | imported from 3GU |
| S2‑160564 | GTP-U IP address assignment and TEIDs allocation | Samsung | imported from 3GU |
| S2‑160565 | UE IP Address Allocation | Samsung | imported from 3GU |
| S2‑160566 | Key issue: IMEI check in case of emergency sessions | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Nokia Networks | imported from 3GU |
| S2‑160567 | Update to solution 19 (un-authenticated UE) | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Nokia Networks | imported from 3GU |
| S2‑160568 | Update to solution 17 (mobility with EPC) | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| S2‑160569 | Updates to 3GPP-WLAN mobility procedure using GMLC/LRF | Ericsson | imported from 3GU |
| S2‑160570 | Mobility aspect of WLAN and 3GPP CS | Nokia Networks, Alcatel-Lucent | imported from 3GU |
| S2‑160571 | Clarification to Solution 18 for Key issue 3 | Ericsson | imported from 3GU |
| S2‑160572 | Reply LS on Set of Rel-13 features for the Support of Emergency sessions over WLAN | SA WG2 | imported from 3GU |
| S2‑160573 | Correction to ePDG selection for emergency bearer services | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Nokia Networks | imported from 3GU |
| S2‑160574 | [draft] Reply LS on the decision of NBIFOM mode | SA WG2 | imported from 3GU |
| S2‑160575 | Correction of NBIFOM procedure in SCM and RAN rules handling parameter | Huawei, HiSilicon | imported from 3GU |
| S2‑160576 | Updated ePDG Selection Procedure | Motorola Mobility, Lenovo | imported from 3GU |
| S2‑160577 | Support of Lawful intercept ePDG requirements (option B) | BlackBerry UK Ltd, Qualcomm Incorporated | imported from 3GU |
| S2‑160578 | Support of Lawful intercept ePDG requirements | BlackBerry UK Ltd, Qualcomm Incorporated | imported from 3GU |
| S2‑160579 | SDCI New Key Issue - Static Sponsorship | Openet, Allot Communications | imported from 3GU |
| S2‑160580 | Solution for Key Issue 1 | NEC | imported from 3GU |
| S2‑160581 | Provisioning sponsored data connectivity information via SCEF | China Mobile, China Unicom, Huawei, ZTE | imported from 3GU |
| S2‑160582 | SDCI Rx Referencing Sponsor Packet Flow Descriptions | Openet, Allot Communications | imported from 3GU |
| S2‑160583 | New Solution: Usage of a sponsoring | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| S2‑160584 | SDCI Key Issue 2 - PCRF Management of Sponsor Packet Flow Descriptions | Openet, Allot Communications | imported from 3GU |
| S2‑160585 | Traffic detection in case of encrypted traffic | Allot Communications, Openet, KDDI, Ericsson | imported from 3GU |
| S2‑160586 | Correction to UE-initiated IP flow mapping/access usability change/RAN rule indication procedure in GERAN/UTRAN, S2a MCM and S2b | ZTE | imported from 3GU |
| S2‑160587 | The procedure of removal of one access from the Multi-access PDN connection | ZTE | imported from 3GU |
| S2‑160588 | [DRAFT] Reply LS on SIP deregistration in GERAN and UTRAN (no VOPSSI) | SA WG2 | imported from 3GU |
| S2‑160589 | Replacing Incorrect Reference for business trunking Specification TS | Ericsson | imported from 3GU |
| S2‑160590 | Replacing Incorrect Reference for business trunking Specification TS | Ericsson | imported from 3GU |
| S2‑160591 | [DRAFT] Reply LS on QoS for EVS-VBR Codec Operation | SA WG2 | imported from 3GU |
| S2‑160592 | Bitrate variations | Ericsson | imported from 3GU |
| S2‑160593 | Priority sharing for concurrent sessions | Ericsson | imported from 3GU |
| S2‑160594 | APN AMBR change at a certain time on Gx | Alcatel-Lucent, Verizon, Oracle, Huawei, Ericsson, Cisco | imported from 3GU |
| S2‑160595 | Reply LS to LS on APN AMBR change at a certain time on Gx | SA WG2 | imported from 3GU |
| S2‑160596 | LS Reply to LS on TSSF Identity Information over Gx | SA WG2 | imported from 3GU |
| S2‑160597 | Reply to LS on application based charging for applications identified by service data flow filters | SA WG2 | imported from 3GU |
| S2‑160598 | LS on potential need of PCC enhancement for MCPTT | SA WG2 | imported from 3GU |
| S2‑160599 | Coexistence between ANDSF and LWA | Motorola Mobility, Lenovo | imported from 3GU |
| S2‑160600 | [Draft] LS on Co-existence between LTE-WLAN Radio Level Integration and other WLAN offloading solutions (e.g. ANDSF) | SA WG2 | imported from 3GU |
| S2‑160601 | Clarification on ANDSF precedence | Motorola Mobility, Lenovo | imported from 3GU |
| S2‑160602 | [DRAFT] Reply LS on precedence of information in USIM | SA WG2 | imported from 3GU |
| S2‑160603 | Overall evaluation addressing key issue #1 and #3 for AULC | China Unicom, Intel, Orange | imported from 3GU |
| S2‑160604 | Solution to KI#2: Managing sponsored data connectivity information inside the operator's network | Ericsson, Orange | imported from 3GU |
| S2‑160605 | Standalone SDCF based solution for key issue #1 and #2 | Intel | imported from 3GU |
| S2‑160606 | Managing sponsored data related information solution for key issue#2 | China Unicom, China Mobile, China Telecom, Huawei, HiSilicon | imported from 3GU |
| S2‑160607 | SDCI New Architectural Assumption - Static Sponsorship | Openet, Allot Communications | imported from 3GU |
| S2‑160608 | SDCI Rx Referencing Sponsor Packet Flow Descriptions | Openet, Allot Communications | imported from 3GU |
| S2‑160609 | SDCI Key Issue 2 - PCRF Management of Sponsor Packet Flow Descriptions | Openet, Allot Communications | imported from 3GU |
| S2‑160610 | Updated ePDG Selection Procedure | Motorola Mobility, Lenovo | imported from 3GU |
| S2‑160611 | Coexistence between ANDSF and LWA | Motorola Mobility, Lenovo | imported from 3GU |
| S2‑160612 | [DRAFT] Reply LS on NBIFOM procedure in SCM and RAN rules handling parameter | SA WG2 | imported from 3GU |
| S2‑160613 | Correction of the decision of NBIFOM mode_23161 | Huawei, HiSilicon | imported from 3GU |
| S2‑160614 | Correction of the decision of NBIFOM mode_23203 | Huawei, HiSilicon | imported from 3GU |
| S2‑160615 | [draft] LS on Co-existence between LTE-WLAN Radio Level Integration and other WLAN offloading solutions (e.g. ANDSF) | SA WG2 | imported from 3GU |
| S2‑160616 | Reply LS on precedence of information in USIM | SA WG2 | imported from 3GU |
| S2‑160617 | Clarification on ANDSF precedence | Motorola Mobility, Lenovo | imported from 3GU |
| S2‑160618 | Reply LS on QoS for EVS-VBR Codec Operation | SA WG2 | imported from 3GU |
| S2‑160619 | Bitrate variations | Ericsson | imported from 3GU |
| S2‑160620 | Reserved for Krisztian's parallel sessions | - | imported from 3GU |
| S2‑160621 | Reserved for Krisztian's parallel sessions | - | imported from 3GU |
| S2‑160622 | Reserved for Krisztian's parallel sessions | - | imported from 3GU |
| S2‑160623 | Reserved for Krisztian's parallel sessions | - | imported from 3GU |
| S2‑160624 | Reserved for Krisztian's parallel sessions | - | imported from 3GU |
| S2‑160625 | Reserved for Krisztian's parallel sessions | - | imported from 3GU |
| S2‑160626 | Reserved for Krisztian's parallel sessions | - | imported from 3GU |
| S2‑160627 | Reserved for Krisztian's parallel sessions | - | imported from 3GU |
| S2‑160628 | Reserved for Krisztian's parallel sessions | - | imported from 3GU |
| S2‑160629 | Reserved for Krisztian's parallel sessions | - | imported from 3GU |
| S2‑160630 | Reserved for Krisztian's parallel sessions | - | imported from 3GU |
| S2‑160631 | Reserved for Krisztian's parallel sessions | - | imported from 3GU |
| S2‑160632 | Reserved for Krisztian's parallel sessions | - | imported from 3GU |
| S2‑160633 | Reserved for Krisztian's parallel sessions | - | imported from 3GU |
| S2‑160634 | Reserved for Krisztian's parallel sessions | - | imported from 3GU |
| S2‑160635 | Reserved for Krisztian's parallel sessions | - | imported from 3GU |
| S2‑160636 | Reserved for Krisztian's parallel sessions | - | imported from 3GU |
| S2‑160637 | Reserved for Krisztian's parallel sessions | - | imported from 3GU |
| S2‑160638 | Reserved for Krisztian's parallel sessions | - | imported from 3GU |
| S2‑160639 | Reserved for Krisztian's parallel sessions | - | imported from 3GU |
| S2‑160640 | Reserved for Krisztian's parallel sessions | - | imported from 3GU |
| S2‑160641 | Reserved for Krisztian's parallel sessions | - | imported from 3GU |
| S2‑160642 | Reserved for Krisztian's parallel sessions | - | imported from 3GU |
| S2‑160643 | Reserved for Krisztian's parallel sessions | - | imported from 3GU |
| S2‑160644 | Reserved for Krisztian's parallel sessions | - | imported from 3GU |
| S2‑160645 | Reserved for Krisztian's parallel sessions | - | imported from 3GU |
| S2‑160646 | Reserved for Krisztian's parallel sessions | - | imported from 3GU |
| S2‑160647 | Reserved for Krisztian's parallel sessions | - | imported from 3GU |
| S2‑160648 | Reserved for Krisztian's parallel sessions | - | imported from 3GU |
| S2‑160649 | Reserved for Krisztian's parallel sessions | - | imported from 3GU |
| S2‑160650 | Reserved for Krisztian's parallel sessions | - | imported from 3GU |
| S2‑160651 | Reserved for Krisztian's parallel sessions | - | imported from 3GU |
| S2‑160652 | Reserved for Krisztian's parallel sessions | - | imported from 3GU |
| S2‑160653 | Reserved for Krisztian's parallel sessions | - | imported from 3GU |
| S2‑160654 | Reserved for Krisztian's parallel sessions | - | imported from 3GU |
| S2‑160655 | Reserved for Krisztian's parallel sessions | - | imported from 3GU |
| S2‑160656 | Reserved for Krisztian's parallel sessions | - | imported from 3GU |
| S2‑160657 | Reserved for Krisztian's parallel sessions | - | imported from 3GU |
| S2‑160658 | Reserved for Krisztian's parallel sessions | - | imported from 3GU |
| S2‑160659 | Reserved for Krisztian's parallel sessions | - | imported from 3GU |
| S2‑160660 | Reserved for Krisztian's parallel sessions | - | imported from 3GU |
| S2‑160661 | Reserved for Krisztian's parallel sessions | - | imported from 3GU |
| S2‑160662 | Reserved for Krisztian's parallel sessions | - | imported from 3GU |
| S2‑160663 | Reserved for Krisztian's parallel sessions | - | imported from 3GU |
| S2‑160664 | Reserved for Krisztian's parallel sessions | - | imported from 3GU |
| S2‑160665 | [DRAFT] LS on potential need of PCC enhancement for MCPTT | SA WG2 | imported from 3GU |
| S2‑160666 | Draft Reply to LS on NB-IoT work progress in RAN WG2 | SA WG2 | imported from 3GU |
| S2‑160667 | DRAFT response to LS on questions on CIoT | SA WG2 | imported from 3GU |
| S2‑160668 | [DRAFT] Reply LS on Multiple uplink NAS PDUs in CIoT optimization | SA WG2 | imported from 3GU |
| S2‑160669 | Key Issue on Efficient user plane paths | Intel, Qualcomm Incorporated (?), Huawei (?) | imported from 3GU |
| S2‑160670 | Key issue on Modular Logical Functions in the NextGen System | AT&T, Qualcomm Inc., Deutsche Telekom, China Mobile, China Telecom, Sprint, Cisco, Nokia, Huawei, Vodafone, Allot Communication, Verizon, Alcatel -Lucent, Alcatel-Lucent Shanghai-Bell | imported from 3GU |
| S2‑160671 | New key issue: Interconnection model for the control plane functional entities of the core network | Cisco Systems, Inc., Vodafone, Allot Communications | imported from 3GU |
| S2‑160672 | Key issue: Architecture principle for next generation systems | Nokia Networks, Verizon, Huawei, China Mobile, CATT, ZTE, CATR | imported from 3GU |
| S2‑160673 | New key issue proposal on network capability exposure | Samsung, China Telecom, KDDI, CATT | imported from 3GU |
| S2‑160674 | The assumptions for overall architecture | Huawei, HiSilicon, China Mobile | imported from 3GU |
| S2‑160675 | Reserved for Tao's drafting sessions | - | imported from 3GU |
| S2‑160676 | Reserved for Tao's drafting sessions | - | imported from 3GU |
| S2‑160677 | Reserved for Tao's drafting sessions | - | imported from 3GU |
| S2‑160678 | Reserved for Tao's drafting sessions | - | imported from 3GU |
| S2‑160679 | Update to Solution 5 | Intel, Nokia, NTT DOCOMO | imported from 3GU |
| S2‑160680 | New Key Issue : S8 Home Routing in case of Non 3GPP access | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| S2‑160681 | Evaluation of Solution#1 | NEC | imported from 3GU |
| S2‑160682 | V8 Solution 1 update and evaluation | Orange, Telecom Italia | imported from 3GU |
| S2‑160683 | Updates to Solution #3 | NTT DOCOMO, DT, LG Electronics, LG Uplus | imported from 3GU |
| S2‑160684 | VPLMN ID to TAS in 3rd party registration | Nokia Networks, Alcatel-Lucent | imported from 3GU |
| S2‑160685 | Clarification to Solution #7: Local Number Translation | Ericsson | imported from 3GU |
| S2‑160686 | Local number translation conclusion | Nokia Networks, Alcatel-Lucent, NEC | imported from 3GU |
| S2‑160687 | Clarification of solution #8 on using only TAI/SAI as the location information | China Mobile | imported from 3GU |
| S2‑160688 | Evaluation of Key Issue #3: PLMN-ID determination at IMS Entities | NTT DOCOMO, Nokia Networks, Alcatel-Lucent, ZTE, LG Electronics, LG Uplus, SK Telecom | imported from 3GU |
| S2‑160689 | Evaluation and conclusion on key issue 4 | China Mobile, ZTE, Intel, NTT DOCOMO | imported from 3GU |
| S2‑160690 | solution &&Y for ePDG selection for emergency services | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Nokia Networks | imported from 3GU |
| S2‑160691 | Update to solution 11 (Determine Emergency Call Numbers) | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Nokia Networks | imported from 3GU |
| S2‑160692 | Minor Update to solution 21 (Access Selection) & to clause 7.2 (Evaluation) | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Nokia Networks | imported from 3GU |
| S2‑160693 | Evaluation on the solutions related with 'Determine Emergency Call Numbers' | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Nokia Networks | imported from 3GU |
| S2‑160694 | Report from parallel session on EIEI | Convenor (Ericsson) | imported from 3GU |
| S2‑160695 | Reserved for Frank's parallel sessions | - | imported from 3GU |
| S2‑160696 | Reserved for Frank's parallel sessions | - | imported from 3GU |
| S2‑160697 | Introduction of solution 18 - suspend and resume procedure | Ericsson, Alcatel-Lucent, Sony, Nokia Networks | imported from 3GU |
| S2‑160698 | Reserved for Frank's parallel sessions | - | imported from 3GU |
| S2‑160699 | Introducing CIoT Optimisations | Alcatel-Lucent, Nokia Networks, MediaTek, Ericsson, Vodafone, KPN, LG Electronics | imported from 3GU |
| S2‑160700 | Introduction of support for NB-IoT | Vodafone, Nokia Networks | imported from 3GU |
| S2‑160701 | CIoT-centric single node EPS architecture | Intel, AT&T, Cisco Systems Inc. | imported from 3GU |
| S2‑160702 | NAS Node Selection updates | Ericsson | imported from 3GU |
| S2‑160703 | Working Assumption: Support of Network Instances shared by multiple 3rd parties | ZTE | imported from 3GU |
| S2‑160704 | Update to TR Skeleton for the Study on Architecture for Next Generation System | Nokia Networks, China Mobile | imported from 3GU |
| S2‑160705 | NGMN terminology and conceptual outline for Network Slicing | Ericsson, Cisco Systems, Inc., NTT DOCOMO, Huawei, HiSilicon, China Mobile | imported from 3GU |
| S2‑160706 | Requirements on optimized UE sleep state and state transitions | Ericsson | imported from 3GU |
| S2‑160707 | Update of High level Architectural Requirements | LG Electronics | imported from 3GU |
| S2‑160708 | 5G Architectural requirement for energy efficiency | Orange | imported from 3GU |
| S2‑160709 | Architectural Requirements on providing multiple connections | LG Electronics | imported from 3GU |
| S2‑160710 | Core and Access functional allocation | Ericsson | imported from 3GU |
| S2‑160711 | Key issue: 3GPP architecture impacts to support network slicing | Ericsson, Deutsche Telekom, Motorola Mobility, Lenovo, KDDI, ZTE, China Telecom, CATT, LG Electronics, China Unicom, AT&T, Qualcomm Incorporated, NTT DOCOMO, NEC, Cisco Systems, Inc., Samsung | imported from 3GU |
| S2‑160712 | Key issue 1 update proposal on CS data support by SeDoC architecture | Deutsche Telekom AG | imported from 3GU |
| S2‑160713 | Key issue on the Registration and Authentication in the SeDoC | ZTE | imported from 3GU |
| S2‑160714 | Solution for Key Issue 1 (Transition to Single Service Profile in IMS) | Deutsche Telekom AG | imported from 3GU |
| S2‑160715 | Inbound roamer support | NEC, T-Mobile USA INC | imported from 3GU |
| S2‑160716 | Solution to the Key Issue 4 - Outbound Roamers to non-Enhanced Networks | ZTE | imported from 3GU |
| S2‑160717 | Outbound roamer support | NEC | imported from 3GU |
| S2‑160718 | Reserved for Chris' parallel sessions | - | imported from 3GU |
| S2‑160719 | Reserved for Chris' parallel sessions | - | imported from 3GU |
| S2‑160720 | Reserved for Chris' parallel sessions | - | imported from 3GU |
| S2‑160721 | Reserved for Chris' parallel sessions | - | imported from 3GU |
| S2‑160722 | Key issue on Modular Logical Functions in the NextGen System | AT&T, Qualcomm Inc., Deutsche Telekom, China Mobile, China Telecom, Sprint, Cisco, Nokia Networks, Huawei, Vodafone, Allot Communications, Verizon, Alcatel -Lucent, Alcatel-Lucent Shanghai-Bell | imported from 3GU |
| S2‑160723 | IMEI check for trusted WLAN access to EPC case | Alcatel-Lucent, Nokia Networks | imported from 3GU |
| S2‑160724 | IMEI check for untrusted WLAN access to EPC case | Alcatel-Lucent, Nokia Networks | imported from 3GU |
| S2‑160725 | Key issue 3: IKE-based, network initiated, WiFi Query for on-demand UE Location positioning mid-emergency session | Ericsson | imported from 3GU |
| S2‑160726 | SEW2-ePDG Selection Solution | Rogers Communications | imported from 3GU |
| S2‑160727 | Solution: ePDG Selection for emergency services in phase 2 | Qualcomm Inc. | imported from 3GU |
| S2‑160728 | How P-CSCF can detect emergency numbers in a VPLMN | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| S2‑160729 | An extended NetLoc procedure for Geographical Information | ZTE, Intel | imported from 3GU |
| S2‑160730 | A new NetLoc based solution for key issue#4 | Intel, CMCC, Huawei, ZTE | imported from 3GU |
| S2‑160731 | Clarification on SRVCC support | China Mobile | imported from 3GU |
| S2‑160732 | Evaluation of Key Issue #3: PLMN-ID determination at IMS Entities | NTT DOCOMO, LG Electronics, ZTE, Nokia Networks?, Alcatel-Lucent?, NEC, Ericsson? | imported from 3GU |
| S2‑160733 | Evaluation and conclusion on key issue 4 | China Mobile, ZTE, Intel, NTT DOCOMO | imported from 3GU |
| S2‑160734 | Proposed Soft Working Conclusion for Key Issue #4 | NTT DOCOMO | imported from 3GU |
| S2‑160735 | Evaluation and conclusion on Key Issue #1 | Intel, Nokia, NTT DOCOMO | imported from 3GU |
| S2‑160736 | Solution to support multiple PRAs in EPS in a dynamic manner using User Location Reporting | Intel, China Unicom | imported from 3GU |
| S2‑160737 | Scenario for PLMN partitioning | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| S2‑160738 | Solution for PLMN partitioning scenario (key issue 2) | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| S2‑160739 | Evaluation and conclusion of Solution #1 | Orange | imported from 3GU |
| S2‑160740 | Evaluation of Solution 4 | Ericsson | imported from 3GU |
| S2‑160741 | Reserved for AULC Drafting sessions | - | imported from 3GU |
| S2‑160742 | Reserved for AULC Drafting sessions | - | imported from 3GU |
| S2‑160743 | Reserved for AULC Drafting sessions | - | imported from 3GU |
| S2‑160744 | Skeleton of TR Robovolte | Rapporteur (Huawei) | imported from 3GU |
| S2‑160745 | FS_RobVoLTE Scope of TR | Huawei, HiSilicon | imported from 3GU |
| S2‑160746 | Robovolte Architectural Requirements | Huawei | imported from 3GU |
| S2‑160747 | Key issue-Robust call in bad LTE coverage with 2G or 3G CS coverage | Huawei, HiSilicon, Intel, China Unicom, Deutsche Telekom, China Mobile, Teliasonera | imported from 3GU |
| S2‑160748 | VoLTE - SRVCC temporary rejection | Nokia Networks, Alcatel-Lucent | imported from 3GU |
| S2‑160749 | Solution for key issue - Robust call in bad LTE coverage with 2G or 3G CS coverage | Huawei, HiSilicon, China Mobile, China Unicom, Intel, China Telecom, KPN, CATT, Deutsche Telekom, Teliasonera | imported from 3GU |
| S2‑160750 | The assumptions for overall architecture | Huawei, HiSilicon, China Mobile | imported from 3GU |
| S2‑160751 | Key issue: QoS Framework | Nokia Networks, AT&T, Deutsche Telekom AG, China Mobile, Ericsson, Intel, Qualcomm Incorporated, ZTE, ETRI, KT | imported from 3GU |
| S2‑160752 | Key issue on session management for 3GPP network | China Mobile, Qualcomm Incorporated, Ericsson, Intel | imported from 3GU |
| S2‑160753 | New key issue: NexGen architecture impacts to support a mobility framework | Ericsson, CATT, NTT DOCOMO, China Telecom, NEC, Qualcomm Incorporated, Motorola Mobility, Lenovo, ZTE, Sprint, Intel, ETRI | imported from 3GU |
| S2‑160754 | Key issue on Modular Logical Functions in the NextGen System | AT&T, Qualcomm Inc., Deutsche Telekom, China Mobile, China Telecom, Sprint, Cisco Systems, Nokia Networks, Huawei, Vodafone, Allot Communications, Verizon, Alcatel -Lucent, Alcatel-Lucent Shanghai-Bell, ZTE, KDDI, KPN, Broadcom, Sandvine, Telecom Italia, | imported from 3GU |
| S2‑160755 | Key Issue on feasibility study of a minimizing access dependencies of the NextGen core network and the Interface between access networks and the core network | Qualcomm Incorporated, ZTE, KDDI, Nokia Networks | imported from 3GU |
| S2‑160756 | Key Issue on Efficient user plane paths | Intel, Qualcomm Incorporated (?), Huawei (?) | imported from 3GU |
| S2‑160757 | New key issue proposal on network capability exposure | Samsung, China Telecom, KDDI, CATT, Qualcomm Incorporated, Allot Communications | imported from 3GU |
| S2‑160758 | Introduction of Control Plane CIoT EPS optimization | Alcatel-lucent, MediaTek, NEC, Intel, Qualcomm; Nokia Networks | imported from 3GU |
| S2‑160759 | Key Issue on Session Continuity in the Next Generation System Architecture | Qualcomm Incorporated, Motorola Mobility, Lenovo, Cisco Systems, Inc., Intel, Huawei | imported from 3GU |
| S2‑160760 | Introduction of attach procedure changes for CIoT EPS optimization | Alcatel-lucent, Vodafone, Qualcomm; Nokia Networks | imported from 3GU |
| S2‑160761 | Considerations and solution for UE IP address management | Cisco Systems, Inc., Samsung | imported from 3GU |
| S2‑160762 | TAU procedure update for CIoT EPS Optimisation | Huawei, HiSilicon | imported from 3GU |
| S2‑160763 | Introduction of attach procedure changes for CIoT EPS optimization | Alcatel-lucent, Vodafone, Qualcomm; Nokia Networks | imported from 3GU |
| S2‑160764 | Introduction of Control Plane CIoT EPS optimization | Alcatel-lucent, MediaTek, NEC, Intel, Qualcomm; Nokia Networks | imported from 3GU |
| S2‑160765 | TAU procedure update for CIoT EPS Optimisation | Huawei, HiSilicon | imported from 3GU |
| S2‑160766 | Detach procedure for CIoT optimization | China Mobile, Huawei, ZTE | imported from 3GU |
| S2‑160767 | Introduction of solution 18 - suspend and resume procedure | Ericsson, Alcatel-Lucent, Sony, Nokia Networks | imported from 3GU |
| S2‑160768 | Introducing support for Non-IP data for CIoT | Ericsson, Cisco Systems Inc, Intel, ZTE | imported from 3GU |
| S2‑160769 | UE Capability Handling for Control Plane CIoT EPS optimization | Vodafone | imported from 3GU |
| S2‑160770 | Introduction of non-IP data delivery via the SCEF for cellular IoT | Intel, Cisco Systems Inc, AT&T, LG Electronics, Samsung | imported from 3GU |
| S2‑160771 | [DRAFT] LS on guidance by SA WG2 on CIOT | SA WG2 | imported from 3GU |
| S2‑160772 | Presentation of TR 23.771 version 1.3.0: Study on system impacts of IMS emergency sessions over WLAN | Alcatel-Lucent | imported from 3GU |
| S2‑160773 | Considerations and solution for UE IP address management | Cisco Systems, Inc., Samsung, ZTE, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Ericsson | imported from 3GU |
| S2‑160774 | TAI List problem and User plane area mapping | Ericsson, ZTE, KDDI, Huawei, HiSilicon | imported from 3GU |
| S2‑160775 | Considerations for the functionality supported by the user plane function | Cisco Systems, Inc. | imported from 3GU |
| S2‑160776 | Solution to key issue# 2: SGW User plane selection by taking PGW User plane into account | NEC | imported from 3GU |
| S2‑160777 | CUPS Handover clarifications | ZTE, KDDI | imported from 3GU |
| S2‑160778 | Solution to Key Issue 4 | Huawei, HiSilicon | imported from 3GU |
| S2‑160779 | Considerations and solution for supporting extended buffering for the UE in power saving mode | Cisco Systems, Inc. | imported from 3GU |
| S2‑160780 | Considerations for 3GPP specific information at the user plane function | Cisco Systems, Inc. | imported from 3GU |
| S2‑160781 | Reserved for Puneet's parallel sessions | - | imported from 3GU |
| S2‑160782 | Reserved for Puneet's parallel sessions | - | imported from 3GU |
| S2‑160783 | Reserved for Puneet's parallel sessions | - | imported from 3GU |
| S2‑160784 | Reserved for Puneet's parallel sessions | - | imported from 3GU |
| S2‑160785 | Reserved for Puneet's parallel sessions | - | imported from 3GU |
| S2‑160786 | Reserved for Puneet's parallel sessions | - | imported from 3GU |
| S2‑160787 | Reserved for Puneet's parallel sessions | - | imported from 3GU |
| S2‑160788 | Reserved for Puneet's parallel sessions | - | imported from 3GU |
| S2‑160789 | Reserved for Puneet's parallel sessions | - | imported from 3GU |
| S2‑160790 | Reserved for Puneet's parallel sessions | - | imported from 3GU |
| S2‑160791 | Reserved for Puneet's parallel sessions | - | imported from 3GU |
| S2‑160792 | Reserved for Puneet's parallel sessions | - | imported from 3GU |
| S2‑160793 | Reserved for Puneet's parallel sessions | - | imported from 3GU |
| S2‑160794 | Reserved for Puneet's parallel sessions | - | imported from 3GU |
| S2‑160795 | Reserved for Puneet's parallel sessions | - | imported from 3GU |
| S2‑160796 | Reserved for Puneet's parallel sessions | - | imported from 3GU |
| S2‑160797 | Reserved for Puneet's parallel sessions | - | imported from 3GU |
| S2‑160798 | Reserved for Puneet's parallel sessions | - | imported from 3GU |
| S2‑160799 | Reserved for Puneet's parallel sessions | - | imported from 3GU |
| S2‑160800 | Reserved for Puneet's parallel sessions | - | imported from 3GU |
| S2‑160801 | Reserved for Puneet's parallel sessions | - | imported from 3GU |
| S2‑160802 | Reserved for Puneet's parallel sessions | - | imported from 3GU |
| S2‑160803 | Reserved for Puneet's parallel sessions | - | imported from 3GU |
| S2‑160804 | Reserved for Puneet's parallel sessions | - | imported from 3GU |
| S2‑160805 | Reserved for Puneet's parallel sessions | - | imported from 3GU |
| S2‑160806 | Update to Solution 5 | Intel, Nokia, NTT DOCOMO | imported from 3GU |
| S2‑160807 | Evaluation of Solution#1 | NEC | imported from 3GU |
| S2‑160808 | VPLMN ID to TAS in 3rd party registration | Nokia Networks, Alcatel-Lucent | imported from 3GU |
| S2‑160809 | Clarification to Solution #7: Local Number Translation | Ericsson | imported from 3GU |
| S2‑160810 | How P-CSCF can detect emergency numbers in a VPLMN | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| S2‑160811 | Clarification on SRVCC support | China Mobile | imported from 3GU |
| S2‑160812 | Evaluation of Key Issue #3: PLMN-ID determination at IMS Entities | NTT DOCOMO, LG Electronics, ZTE, Nokia Networks?, Alcatel-Lucent?, NEC, Ericsson? | imported from 3GU |
| S2‑160813 | Evaluation and conclusion on Key Issue #1 | Intel, Nokia, NTT DOCOMO | imported from 3GU |
| S2‑160814 | Update of High level Architectural Requirements | LG Electronics | imported from 3GU |
| S2‑160815 | 5G Architectural requirement for energy efficiency | Orange | imported from 3GU |
| S2‑160816 | Architectural Requirements on providing multiple connections | LG Electronics | imported from 3GU |
| S2‑160817 | Core and Access functional allocation | Ericsson, Qualcomm Incorporated, AT&T, CMCC, NTT DoCoMo | imported from 3GU |
| S2‑160818 | The assumptions for overall architecture | Huawei, HiSilicon, China Mobile | imported from 3GU |
| S2‑160819 | New Study Item for Enhanced Isolated E-UTRAN Operation for Public Safety | General Dynamics UK Ltd., Orange | imported from 3GU |
| S2‑160820 | New work item on Non-IP for Cellular IoT for EC-EGPRS | Ericsson, Orange, MediaTek | imported from 3GU |
| S2‑160821 | New SID on Feasibility study on the Support of Emergency services over WLAN (FS_SEW2) | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Deutsche Telekom, Broadcom, Sprint, Verizon, AT&T, Nokia Networks, Orange, T-Mobile USA, LG Electronics, TCS, Motorola Mobility, Lenovo, Ericsson, Huawei | imported from 3GU |
| S2‑160822 | New WID on the Support of Emergency services over WLAN - phase 2 (SEW2) | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Deutsche Telekom, Broadcom, Sprint, Verizon, AT&T, Nokia Networks | imported from 3GU |
| S2‑160823 | Presentation of TR 23.771 version 1.3.0: Study on system impacts of IMS emergency sessions over WLAN | Alcatel-Lucent | imported from 3GU |
| S2‑160824 | SA WG2 Work Planning Worksheet | SA WG2 Chairman | imported from 3GU |
| S2‑160825 | APN AMBR change at a certain time on Gx | Alcatel-Lucent, Verizon, Oracle, Huawei, Ericsson | imported from 3GU |
| S2‑160826 | DRAFT response to LS on questions on CIoT | SA WG2 | imported from 3GU |
| S2‑160827 | Introduction of solution 18 - suspend and resume procedure | Ericsson, Alcatel-Lucent, Sony, Nokia Networks | imported from 3GU |
| S2‑160828 | Reply LS on Multiple uplink NAS PDUs in CIoT optimization | SA WG2 | imported from 3GU |
| S2‑160829 | Draft Reply to LS on NB-IoT work progress in RAN WG2 | SA WG2 | imported from 3GU |
| S2‑160830 | DRAFT response to LS on questions on CIoT | SA WG2 | imported from 3GU |
| S2‑160831 | [DRAFT] LS on guidance by SA WG2 on CIOT | SA WG2 | imported from 3GU |
| S2‑160832 | Introduction of non-IP data delivery via the SCEF for cellular IoT | Intel, Cisco Systems Inc, AT&T, LG Electronics, Samsung | imported from 3GU |
| S2‑160833 | Introducing CIoT Optimisations | Alcatel-Lucent, Nokia Networks, MediaTek, Ericsson, Vodafone, KPN, LG Electronics | imported from 3GU |
| S2‑160834 | Introduction of support for NB-IoT | Vodafone, Nokia Networks | imported from 3GU |
| S2‑160835 | CIoT-centric single node EPS architecture | Intel, AT&T, Cisco Systems Inc | imported from 3GU |
| S2‑160836 | Introduction of attach procedure changes for CIoT EPS optimization | Alcatel-lucent, Vodafone, Qualcomm; Nokia Networks | imported from 3GU |
| S2‑160837 | TAU procedure update for CIoT EPS Optimisation | Huawei, HiSilicon | imported from 3GU |
| S2‑160838 | Detach procedure for CIoT optimization | China Mobile, Huawei, ZTE | imported from 3GU |
| S2‑160839 | Introduction of Control Plane CIoT EPS optimization | Alcatel-lucent, MediaTek, NEC, Intel, Qualcomm; Nokia Networks | imported from 3GU |
| S2‑160840 | Introduction of solution 18 - suspend and resume procedure | Ericsson, Alcatel-Lucent, Sony, Nokia Networks | imported from 3GU |
| S2‑160841 | Introducing support for Non-IP data for CIoT | Ericsson, Cisco Systems Inc, Intel, ZTE | imported from 3GU |
| S2‑160842 | Solution to support multiple PRAs in EPS in a dynamic manner using User Location Reporting | Intel, China Unicom | imported from 3GU |
| S2‑160843 | Evaluation and conclusion of Solution #1 | Orange | imported from 3GU |
| S2‑160844 | Evaluation of Solution 4 | Ericsson | imported from 3GU |
| S2‑160845 | Solution to support multiple PRAs in EPS in a dynamic manner using User Location Reporting | Intel, China Unicom | imported from 3GU |
| S2‑160846 | Provisioning sponsored data connectivity information via SCEF | China Mobile, China Unicom, Huawei, ZTE | imported from 3GU |
| S2‑160847 | Solution for Key Issue 1 | NEC | imported from 3GU |
| S2‑160848 | SDCI Rx Referencing Sponsor Packet Flow Descriptions | Openet, Allot Communications | imported from 3GU |
| S2‑160849 | New Solution: Usage of a sponsoring | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| S2‑160850 | Solution to KI#2: Managing sponsored data connectivity information inside the operator's network | Ericsson, Orange, ZTE | imported from 3GU |
| S2‑160851 | Standalone SDCF based solution for key issue #1 and #2 | Intel | imported from 3GU |
| S2‑160852 | Managing sponsored data related information solution for key issue#2 | China Unicom, China Mobile, China Telecom, Huawei, HiSilicon | imported from 3GU |
| S2‑160853 | Lawful interception in split architectures | Huawei, HiSilicon | imported from 3GU |
| S2‑160854 | Consideration for performing LI functionality | Cisco Systems, Inc. | imported from 3GU |
| S2‑160855 | [Draft] LS on Lawful interception in split EPC architecture | SA WG2 | imported from 3GU |
| S2‑160856 | Control plane function providing pre-allocated GTP-U IP address and TEID to the user plane function (during restoration scenario) | Cisco Systems, Inc. | imported from 3GU |
| S2‑160857 | Location of the resource allocation function (F-TEID) | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, ZTE | imported from 3GU |
| S2‑160858 | TAI List problem and User plane area mapping | Ericsson, ZTE, KDDI, Huawei, HiSilicon | imported from 3GU |
| S2‑160859 | Solution to key issue# 2: SGW User plane selection by taking PGW User plane into account | NEC | imported from 3GU |
| S2‑160860 | CUPS Handover clarifications | ZTE, KDDI | imported from 3GU |
| S2‑160861 | Solution to Key Issue 4 | Huawei, HiSilicon | imported from 3GU |
| S2‑160862 | Description of an eDECOR solution#1 variant | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| S2‑160863 | Inbound roamer support | NEC, T-Mobile USA INC | imported from 3GU |
| S2‑160864 | Outbound roamer support | NEC | imported from 3GU |
| S2‑160865 | Solution for Key Issue 1 (Transition to Single Service Profile in IMS) | Deutsche Telekom AG | imported from 3GU |
| S2‑160866 | Evaluation of Solution#1 | NEC | imported from 3GU |
| S2‑160867 | Clarification on SRVCC support | China Mobile | imported from 3GU |
| S2‑160868 | Evaluation of Key Issue #3: PLMN-ID determination at IMS Entities | NTT DOCOMO, ZTE, LG Electronics, Nokia Networks, Alcatel-Lucent, NEC, Ericsson | imported from 3GU |
| S2‑160869 | Evaluation and conclusion on Key Issue #1 | Intel, Nokia, NTT DOCOMO, KDDI | imported from 3GU |
| S2‑160870 | [DRAFT] LS on Security aspect for a solution #5 | SA WG2 | imported from 3GU |
| S2‑160871 | Key issue of Group Creation and Modification | Convida Wireless, Samsung | imported from 3GU |
| S2‑160872 | Requirements on optimized UE sleep state and state transitions | Ericsson | imported from 3GU |
| S2‑160873 | Update of High level Architectural Requirements | LG Electronics | imported from 3GU |
| S2‑160874 | Key issue: QoS Framework | Nokia Networks, AT&T, Deutsche Telekom AG, China Mobile, Ericsson, Intel, Qualcomm Incorporated, ZTE, ETRI, KT, Allot Communications | imported from 3GU |
| S2‑160875 | Key issue: 3GPP architecture impacts to support network slicing | Ericsson, Deutsche Telekom, Motorola Mobility, Lenovo, KDDI, ZTE, China Telecom, CATT, LG Electronics, China Unicom, AT&T, Qualcomm Incorporated, NTT DOCOMO, NEC, Cisco Systems, Inc., Samsung | imported from 3GU |
| S2‑160876 | Key Issue on Efficient user plane paths | Intel, Qualcomm Incorporated (?), Huawei (?) | imported from 3GU |
| S2‑160877 | New key issue: NexGen architecture impacts to support a mobility framework | Ericsson, CATT, NTT DOCOMO, China Telecom, NEC, Qualcomm Incorporated, Motorola Mobility, Lenovo, ZTE, Sprint, Intel, ETRI | imported from 3GU |
| S2‑160878 | Key Issue on Session Continuity in the Next Generation System Architecture | Qualcomm Incorporated, Motorola Mobility, Lenovo, Cisco Systems, Inc., Intel, Huawei | imported from 3GU |
| S2‑160879 | Key Issue on feasibility study of a minimizing access dependencies of the NextGen core network and the Interface between access networks and the core network | Qualcomm Incorporated, ZTE, KDDI, Nokia Networks | imported from 3GU |
| S2‑160880 | New key issue proposal on network capability exposure | Samsung, China Telecom, KDDI, CATT, Qualcomm Incorporated, Allot Communications, AT&T | imported from 3GU |
| S2‑160881 | NGMN terminology and conceptual outline for Network Slicing | Ericsson, Cisco Systems, Inc., NTT DOCOMO, Huawei, HiSilicon, China Mobile | imported from 3GU |
| S2‑160882 | Reply LS on the usage of QCI in eMBMS traffic relay | SA WG2 | imported from 3GU |
| S2‑160883 | LS on the Revocation of Discovery Filters | SA WG2 | imported from 3GU |
| S2‑160884 | Correction on Targeted RPAUID in the monitor response message | Huawei, Hisilicon | imported from 3GU |
| S2‑160885 | Reply LS on the usage of QCI in eMBMS traffic relay | SA WG2 | imported from 3GU |
| S2‑160886 | Reply LS on RAN WG3 agreements on DC enhancements for LTE | SA WG2 | imported from 3GU |
| S2‑160887 | Handling of a 5.12s eDRX cycle | INTERDIGITAL COMMUNICATIONS | imported from 3GU |
| S2‑160888 | Handling of a 5.12s eDRX cycle | INTERDIGITAL COMMUNICATIONS | imported from 3GU |
| S2‑160889 | Reply LS on NBIFOM procedure in SCM and RAN rules handling parameter | SA WG2 | imported from 3GU |
| S2‑160890 | The procedure of removal of one access from the Multi-access PDN connection | ZTE | imported from 3GU |
| S2‑160891 | Correction to UE-initiated IP flow mapping/access usability change/RAN rule indication procedure in GERAN/UTRAN, S2a MCM and S2b | ZTE | imported from 3GU |
| S2‑160892 | Updated ePDG Selection Procedure | Motorola Mobility, Lenovo | imported from 3GU |
| S2‑160893 | Coexistence between ANDSF and LWA | Motorola Mobility, Lenovo | imported from 3GU |
| S2‑160894 | LS on Co-existence between LTE-WLAN Radio Level Integration and other WLAN offloading solutions (e.g. ANDSF) | SA WG2 | imported from 3GU |
| S2‑160895 | Clarification on ANDSF precedence | Motorola Mobility, Lenovo | imported from 3GU |
| S2‑160896 | Reply LS on precedence of information in USIM | SA WG2 | imported from 3GU |
| S2‑160897 | [DRAFT] LS on potential need of PCC enhancement for MCPTT | SA WG2 | imported from 3GU |
| S2‑160898 | Reply to LS on application based charging for applications identified by service data flow filters | SA WG2 | imported from 3GU |
| S2‑160899 | Reply LS to LS on APN AMBR change at a certain time on Gx | SA WG2 | imported from 3GU |
| S2‑160900 | Replacing Incorrect Reference for business trunking Specification TS | Ericsson | imported from 3GU |
| S2‑160901 | Replacing Incorrect Reference for business trunking Specification TS | Ericsson | imported from 3GU |
| S2‑160902 | Key issue-Robust call in bad LTE coverage with 2G or 3G CS coverage | Huawei, HiSilicon, Intel, China Unicom, Deutsche Telekom, China Mobile, Teliasonera | imported from 3GU |
| S2‑160903 | Introduction of support for NB-IoT | Vodafone, Nokia Networks | imported from 3GU |
| S2‑160904 | New work item on Non-IP for Cellular IoT for EC-EGPRS | Ericsson, Orange, MediaTek | imported from 3GU |
| S2‑160905 | Reply to LS on NB-IoT work progress in RAN WG2 | SA WG2 | imported from 3GU |
| S2‑160906 | Response to LS on questions on CIoT | SA WG2 | imported from 3GU |
| S2‑160907 | Introduction of support for NB-IoT | Vodafone, Nokia Networks | imported from 3GU |
| S2‑160908 | Detach procedure for CIoT optimization | China Mobile, Huawei, ZTE | imported from 3GU |
| S2‑160909 | Introduction of Control Plane CIoT EPS optimization | Alcatel-lucent, MediaTek, NEC, Intel, Qualcomm; Nokia Networks | imported from 3GU |
| S2‑160910 | LS on guidance by SA WG2 on CIOT | SA WG2 | imported from 3GU |
| S2‑160911 | LS on potential need of PCC enhancement for MCPTT | SA WG2 | imported from 3GU |
| S2‑160912 | The procedure of removal of one access from the Multi-access PDN connection | ZTE | imported from 3GU |
| S2‑160913 | Solution for Key Issue 1 | NEC | imported from 3GU |
| S2‑160914 | SDCI Rx Referencing Sponsor Packet Flow Descriptions | Openet, Allot Communications | imported from 3GU |
| S2‑160915 | Solution to KI#2: Managing sponsored data connectivity information inside the operator's network | Ericsson, Orange, ZTE | imported from 3GU |
| S2‑160916 | Standalone SDCF based solution for key issue #1 and #2 | Intel | imported from 3GU |
| S2‑160917 | Managing sponsored data related information solution for key issue#2 | China Unicom, China Mobile, China Telecom, Huawei, HiSilicon | imported from 3GU |
| S2‑160918 | Lawful interception in split architectures | Huawei, HiSilicon | imported from 3GU |
| S2‑160919 | Consideration for performing LI functionality | Cisco Systems, Inc. | imported from 3GU |
| S2‑160920 | LS on Lawful interception in split EPC architecture | SA WG2 | imported from 3GU |
| S2‑160921 | Control plane function providing pre-allocated GTP-U IP address and TEID to the user plane function (during restoration scenario) | Cisco Systems, Inc. | imported from 3GU |
| S2‑160922 | TAI List problem and User plane area mapping | Ericsson, ZTE, KDDI, Huawei, HiSilicon | imported from 3GU |
| S2‑160923 | Solution to Key Issue 4 | Huawei, HiSilicon | imported from 3GU |
| S2‑160924 | Key issue 1 update proposal on CS data support by SeDoC architecture | Deutsche Telekom AG | imported from 3GU |
| S2‑160925 | Evaluation of Solution#1 | NEC | imported from 3GU |
| S2‑160926 | Clarification on SRVCC support | China Mobile | imported from 3GU |
| S2‑160927 | Evaluation of Key Issue #3: PLMN-ID determination at IMS Entities | NTT DOCOMO, ZTE, LG Electronics, Nokia Networks, Alcatel-Lucent, NEC, Ericsson | imported from 3GU |
| S2‑160928 | Evaluation and conclusion on Key Issue #1 | Intel, Nokia, NTT DOCOMO, KDDI | imported from 3GU |
| S2‑160929 | LS on Security aspects of solution #5 for making UE-detected IMS emergency session successful with S8HR as a roaming architecture for VoLTE | SA WG2 | imported from 3GU |
| S2‑160930 | Key issue: QoS Framework | Nokia Networks, AT&T, Deutsche Telekom AG, China Mobile, Ericsson, Intel, Qualcomm Incorporated, ZTE, ETRI, KT, Allot Communications, Samsung, Mediatek | imported from 3GU |
| S2‑160931 | Key Issue on Session Continuity in the Next Generation System Architecture | Qualcomm Incorporated, Motorola Mobility, Lenovo, Cisco Systems, Inc., Intel, Huawei | imported from 3GU |
| S2‑160932 | Architectural assumptions and requirements for FS_GENCEF | Samsung | imported from 3GU |
page generated from database: 2024-04-13 13:51:47