S2-113
|
|
|
Evaluation and conclusion on Key Issue #1
|
|
S2 160928
|
Intel, Nokia, NTT DOCOMO, KDDI
|
Approved
|
|
S2-113
|
|
Rel-14
|
Key issue 1 update proposal on CS data support by SeDoC architecture
|
|
S2 160924
|
Deutsche Telekom AG
|
Approved
|
|
S2-113
|
|
Rel-14
|
Considerations for 3GPP specific information at the user plane function
|
|
S2 160780
|
Cisco Systems, Inc.
|
Approved
|
|
S2-113
|
|
Rel-14
|
SDCI Key Issue 2 - PCRF Management of Sponsor Packet Flow Descriptions
|
|
S2 160609
|
Openet, Allot Communications
|
Approved
|
|
S2-113
|
|
Rel-14
|
Control plane function providing pre-allocated GTP-U IP address and TEID to the user plane function (during restoration scenario)
|
|
S2 160921
|
Cisco Systems, Inc.
|
Approved
|
|
S2-113
|
|
Rel-14
|
Considerations for the functionality supported by the user plane function
|
|
S2 160775
|
Cisco Systems, Inc.
|
Approved
|
|
S2-113
|
|
Rel-14
|
SDCI New Architectural Assumption - Static Sponsorship
|
|
S2 160607
|
Openet, Allot Communications
|
Approved
|
|
S2-113
|
|
Rel-14
|
Key issue on Modular Logical Functions in the NextGen System
|
|
S2 160754
|
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, Mediatek
|
Approved
|
|
S2-113
|
|
|
Key Issue on Efficient user plane paths
|
|
S2 160876
|
Intel, Qualcomm Incorporated (?), Huawei (?)
|
Approved
|
|
S2-113
|
|
|
Update to Solution 5
|
|
S2 160806
|
Intel, Nokia, NTT DOCOMO
|
Approved
|
|
S2-113
|
|
Rel-14
|
Consideration for performing LI functionality
|
|
S2 160919
|
Cisco Systems, Inc.
|
Approved
|
|
S2-113
|
|
|
Managing sponsored data related information solution for key issue#2
|
|
S2 160917
|
China Unicom, China Mobile, China Telecom, Huawei, HiSilicon
|
Approved
|
|
S2-113
|
|
Rel-14
|
SDCI Rx Referencing Sponsor Packet Flow Descriptions
|
|
S2 160914
|
Openet, Allot Communications
|
Approved
|
|
S2-113
|
|
|
Solution for Key Issue 1
|
|
S2 160913
|
NEC
|
Approved
|
|
S2-113
|
|
Rel-14
|
Considerations and solution for supporting extended buffering for the UE in power saving mode
|
|
S2 160779
|
Cisco Systems, Inc.
|
Approved
|
|
S2-113
|
23.710
|
Rel-14
|
Updates to solution 4
|
0.2.0
|
S2 160159
|
Ericsson
|
Approved
|
FS_AULC
|
S2-113
|
23.710
|
Rel-14
|
Scenario for PLMN partitioning
|
0.2.0
|
S2 160737
|
Alcatel-Lucent, Alcatel-Lucent Shanghai Bell
|
Approved
|
FS_AULC
|
S2-113
|
23.710
|
Rel-14
|
Evaluation of Solution #5
|
0.2.1
|
S2 160357
|
Huawei, Hisilicon
|
Approved
|
FS_AULC
|
S2-113
|
23.710
|
Rel-14
|
Solution for PLMN partitioning scenario (key issue 2)
|
0.2.0
|
S2 160738
|
Alcatel-Lucent, Alcatel-Lucent Shanghai Bell
|
Approved
|
FS_AULC
|
S2-113
|
23.710
|
Rel-14
|
Evaluation of Solution 4
|
0.2.0
|
S2 160844
|
Ericsson
|
Approved
|
FS_AULC
|
S2-113
|
23.711
|
Rel-14
|
eDECOR Defintions
|
0.2.0
|
S2 160518
|
Ericsson
|
Approved
|
FS_eDecor
|
S2-113
|
23.711
|
Rel-14
|
Discussion on DCN selection based on Usage Type and DCN Type
|
0.2.0
|
S2 160519
|
Huawei, Hisilicon
|
Approved
|
FS_eDecor
|
S2-113
|
23.711
|
Rel-14
|
Description of an eDECOR solution#1 variant
|
0.2.0
|
S2 160862
|
Alcatel-Lucent, Alcatel-Lucent Shanghai Bell
|
Approved
|
FS_eDecor
|
S2-113
|
23.711
|
Rel-14
|
HSS Initiated update for Dedicated CN Information/Redirection
|
0.2.0
|
S2 160524
|
InterDigital
|
Approved
|
FS_eDecor
|
S2-113
|
23.714
|
Rel-14
|
Solution to key issue# 2: SGW User plane selection by taking PGW User plane into account
|
0.2.0
|
S2 160859
|
NEC
|
Approved
|
FS_CUPS
|
S2-113
|
23.714
|
Rel-14
|
CUPS Handover clarifications
|
0.2.0
|
S2 160860
|
ZTE, KDDI
|
Approved
|
FS_CUPS
|
S2-113
|
23.714
|
Rel-14
|
Solution to Key Issue 4
|
0.2.0
|
S2 160923
|
Huawei, HiSilicon
|
Approved
|
FS_CUPS
|
S2-113
|
23.714
|
Rel-14
|
Lawful interception in split architectures
|
0.2.0
|
S2 160918
|
Huawei, HiSilicon
|
Approved
|
FS_CUPS
|
S2-113
|
23.714
|
Rel-14
|
Considerations and solution for UE IP address management
|
0.2.0
|
S2 160773
|
Cisco Systems, Inc., Samsung, ZTE, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Ericsson
|
Approved
|
FS_CUPS
|
S2-113
|
23.714
|
Rel-14
|
Location of the resource allocation function (F-TEID)
|
0.2.0
|
S2 160857
|
Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, ZTE
|
Approved
|
FS_CUPS
|
S2-113
|
23.714
|
Rel-14
|
TAI List problem and User plane area mapping
|
0.2.0
|
S2 160922
|
Ericsson, ZTE, KDDI, Huawei, HiSilicon
|
Approved
|
FS_CUPS
|
S2-113
|
23.719
|
Rel-14
|
Outbound roamer support
|
0.1.1
|
S2 160864
|
NEC
|
Approved
|
|
S2-113
|
23.719
|
Rel-14
|
Inbound roamer support
|
0.1.1
|
S2 160863
|
NEC, T-Mobile USA INC
|
Approved
|
|
S2-113
|
23.719
|
Rel-14
|
Solution to the Key Issue 4 - Outbound Roamers to non-Enhanced Networks
|
0.1.0
|
S2 160716
|
ZTE
|
Approved
|
FS_SeDoC
|
S2-113
|
23.719
|
Rel-14
|
Key issue on the Registration and Authentication in the SeDoC
|
0.1.0
|
S2 160713
|
ZTE
|
Approved
|
FS_SeDoC
|
S2-113
|
23.721
|
Rel-14
|
Solution to KI#2: Managing sponsored data connectivity information inside the operator's network
|
0.1.1
|
S2 160915
|
Ericsson, Orange, ZTE
|
Approved
|
FS_SDCI
|
S2-113
|
23.721
|
Rel-14
|
Standalone SDCF based solution for key issue #1 and #2
|
|
S2 160916
|
Intel
|
Approved
|
FS_SDCI
|
S2-113
|
23.721
|
Rel-14
|
Traffic detection in case of encrypted traffic
|
0.1.0
|
S2 160585
|
Allot Communications, Openet, KDDI, Ericsson
|
Approved
|
FS_SDCI
|
S2-113
|
23.721
|
Rel-14
|
New Solution: Usage of a sponsoring
|
0.1.1
|
S2 160849
|
Alcatel-Lucent, Alcatel-Lucent Shanghai Bell
|
Approved
|
FS_SDCI
|
S2-113
|
23.721
|
Rel-14
|
Provisioning sponsored data connectivity information via SCEF
|
0.1.1
|
S2 160846
|
China Mobile, China Unicom, Huawei, ZTE
|
Approved
|
FS_SDCI
|
S2-113
|
23.749
|
Rel-14
|
Clarification to Solution #7: Local Number Translation
|
1.0.0
|
S2 160809
|
Ericsson
|
Approved
|
FS_V8
|
S2-113
|
23.749
|
Rel-14
|
Clarification to Solution #2: Local Number Translation
|
1.0.0
|
S2 160140
|
Ericsson
|
Approved
|
FS_V8
|
S2-113
|
23.749
|
Rel-14
|
An extended NetLoc procedure for Geographical Information
|
0.3.0
|
S2 160729
|
ZTE, Intel
|
Approved
|
FS_V8
|
S2-113
|
23.749
|
Rel-14
|
A new NetLoc based solution for key issue#4
|
|
S2 160730
|
Intel, CMCC, Huawei, ZTE
|
Approved
|
FS_V8
|
S2-113
|
23.749
|
Rel-14
|
Evaluation and conclusion on key issue 4
|
1.0.0
|
S2 160733
|
China Mobile, ZTE, Intel, NTT DOCOMO
|
Approved
|
FS_V8
|
S2-113
|
23.749
|
Rel-14
|
Clarification on SRVCC support
|
1.0.0
|
S2 160926
|
China Mobile
|
Approved
|
FS_V8
|
S2-113
|
23.749
|
Rel-14
|
How P-CSCF can detect emergency numbers in a VPLMN
|
1.0.0
|
S2 160810
|
Alcatel-Lucent, Alcatel-Lucent Shanghai Bell
|
Approved
|
FS_V8
|
S2-113
|
23.749
|
Rel-14
|
VPLMN ID to TAS in 3rd party registration
|
0.3.0
|
S2 160808
|
Nokia Networks, Alcatel-Lucent
|
Approved
|
FS_V8
|
S2-113
|
23.749
|
Rel-14
|
V8 Solution 1 update and evaluation
|
1.0.0
|
S2 160682
|
Orange, Telecom Italia
|
Approved
|
FS_V8
|
S2-113
|
23.749
|
Rel-14
|
Clarification of solution #8 on using only TAI/SAI as the location information
|
1.0.0
|
S2 160687
|
China Mobile
|
Approved
|
FS_V8
|
S2-113
|
23.749
|
Rel-14
|
Local number translation conclusion
|
1.0.0
|
S2 160686
|
Nokia Networks, Alcatel-Lucent, NEC
|
Approved
|
FS_V8
|
S2-113
|
23.749
|
Rel-14
|
Updates to Solution #3
|
1.0.0
|
S2 160683
|
NTT DOCOMO, DT, LG Electronics, LG Uplus
|
Approved
|
FS_V8
|
S2-113
|
23.749
|
Rel-14
|
Evaluation of Solution#1
|
1.0.0
|
S2 160925
|
NEC
|
Approved
|
FS_V8
|
S2-113
|
23.749
|
Rel-14
|
Evaluation of Key Issue #3: PLMN-ID determination at IMS Entities
|
1.0.0
|
S2 160927
|
NTT DOCOMO, ZTE, LG Electronics, Nokia Networks, Alcatel-Lucent, NEC, Ericsson
|
Approved
|
FS_V8
|
S2-113
|
23.750
|
Rel-14
|
Robovolte Architectural Requirements
|
0.0.0
|
S2 160746
|
Huawei
|
Approved
|
FS_RobVoLTE
|
S2-113
|
23.750
|
Rel-14
|
Key issue-Robust call in bad LTE coverage with 2G or 3G CS coverage
|
0.0.0
|
S2 160902
|
Huawei, HiSilicon, Intel, China Unicom, Deutsche Telekom, China Mobile, Teliasonera
|
Approved
|
FS_RobVoLTE
|
S2-113
|
23.750
|
Rel-14
|
Solution for key issue - Robust call in bad LTE coverage with 2G or 3G CS coverage
|
0.0.0
|
S2 160749
|
Huawei, HiSilicon, China Mobile, China Unicom, Intel, China Telecom, KPN, CATT, Deutsche Telekom, Teliasonera
|
Approved
|
FS_RobVoLTE
|
S2-113
|
23.750
|
Rel-14
|
VoLTE - SRVCC temporary rejection
|
0.0.0
|
S2 160748
|
Nokia Networks, Alcatel-Lucent
|
Approved
|
FS_RobVoLTE
|
S2-113
|
23.750
|
Rel-14
|
Skeleton of TR Robovolte
|
0.0.0
|
S2 160744
|
Rapporteur (Huawei)
|
Approved
|
FS_RobVoLTE
|
S2-113
|
23.750
|
Rel-14
|
FS_RobVoLTE Scope of TR
|
0.0.0
|
S2 160745
|
Huawei, HiSilicon
|
Approved
|
FS_RobVoLTE
|
S2-113
|
23.771
|
Rel-14
|
Clarification to Solution 18 for Key issue 3
|
1.2.0
|
S2 160571
|
Ericsson
|
Approved
|
FS_SEW
|
S2-113
|
23.771
|
Rel-14
|
Mobility aspect of WLAN and 3GPP CS
|
1.2.0
|
S2 160570
|
Nokia Networks, Alcatel-Lucent
|
Approved
|
FS_SEW2
|
S2-113
|
23.771
|
Rel-14
|
Key issue: IMEI check in case of emergency sessions
|
1.2.0
|
S2 160566
|
Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Nokia Networks
|
Approved
|
FS_SEW
|
S2-113
|
23.771
|
Rel-14
|
Minor Update to solution 21 (Access Selection) & to clause 7.2 (Evaluation)
|
1.2.0
|
S2 160692
|
Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Nokia Networks
|
Approved
|
FS_SEW
|
S2-113
|
23.771
|
Rel-14
|
Updates to 3GPP-WLAN mobility procedure using GMLC/LRF
|
1.2.0
|
S2 160569
|
Ericsson
|
Approved
|
FS_SEW2
|
S2-113
|
23.771
|
Rel-14
|
Update to solution 11 (Determine Emergency Call Numbers)
|
1.2.0
|
S2 160691
|
Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Nokia Networks
|
Approved
|
FS_SEW
|
S2-113
|
23.771
|
Rel-14
|
solution &&Y for ePDG selection for emergency services
|
1.2.0
|
S2 160690
|
Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Nokia Networks
|
Approved
|
FS_SEW
|
S2-113
|
23.771
|
Rel-14
|
Evaluation on the solutions related with 'Determine Emergency Call Numbers'
|
1.2.0
|
S2 160693
|
Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Nokia Networks
|
Approved
|
FS_SEW
|
S2-113
|
23.771
|
Rel-14
|
Update to solution 17 (mobility with EPC)
|
1.2.0
|
S2 160568
|
Alcatel-Lucent, Alcatel-Lucent Shanghai Bell
|
Approved
|
FS_SEW
|
S2-113
|
23.771
|
Rel-14
|
Update to solution 19 (un-authenticated UE)
|
1.2.0
|
S2 160567
|
Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Nokia Networks
|
Approved
|
FS_SEW
|
S2-113
|
23.771
|
Rel-14
|
Solution: ePDG Selection for emergency services in phase 2
|
1.2.0
|
S2 160727
|
Qualcomm Inc.
|
Approved
|
FS_SEW2
|
S2-113
|
23.771
|
Rel-14
|
SEW2-ePDG Selection Solution
|
1.2.0
|
S2 160726
|
Rogers Communications
|
Approved
|
FS_SEW2
|
S2-113
|
23.771
|
Rel-14
|
Key issue 3: IKE-based, network initiated, WiFi Query for on-demand UE Location positioning mid-emergency session
|
1.2.0
|
S2 160725
|
Ericsson
|
Approved
|
FS_SEW
|
S2-113
|
23.771
|
Rel-14
|
Key issue 3: On-demand Network initiated UE Location Positioning mid-emergency session via the emergency signalling channel
|
1.2.0
|
S2 160134
|
Ericsson
|
Approved
|
FS_SEW
|
S2-113
|
23.773
|
Rel-14
|
Architectural assumptions and requirements for FS_GENCEF
|
|
S2 160932
|
Samsung
|
Approved
|
FS_GENCEF
|
S2-113
|
23.773
|
Rel-14
|
Scope of TR 23.773 on FS_GENCEF
|
|
S2 160499
|
Samsung
|
Approved
|
FS_GENCEF
|
S2-113
|
23.773
|
Rel-14
|
Key issue of Group Creation and Modification
|
0.0.0
|
S2 160871
|
Convida Wireless, Samsung
|
Approved
|
FS_GENCEF
|
S2-113
|
23.773
|
Rel-14
|
Key issue proposal: Minimization of signaling load
|
|
S2 160502
|
Samsung
|
Approved
|
FS_GENCEF
|
S2-113
|
23.785
|
Rel-14
|
New Key Issue#xx: Localized MBMS Support
|
0.1.1
|
S2 160513
|
Huawei, Hisilicon
|
Approved
|
FS_V2XARC
|
S2-113
|
23.785
|
Rel-14
|
Update of Key Issue#2
|
0.1.1
|
S2 160531
|
LG Electronics
|
Approved
|
FS_V2XARC
|
S2-113
|
23.785
|
Rel-14
|
V2X reference architecture and RSU discussion
|
0.1.1
|
S2 160542
|
Qualcomm Incorporated, LG Electronics
|
Approved
|
FS_V2XARC
|
S2-113
|
23.785
|
Rel-14
|
Key issue on V2X QoS
|
0.1.1
|
S2 160545
|
Huawei, Hisilicon
|
Approved
|
FS_V2XARC
|
S2-113
|
23.785
|
Rel-14
|
Consideration on the architecture options for V2X
|
0.1.1
|
S2 160352
|
Huawei, Hisilicon
|
Approved
|
FS_V2XARC
|
S2-113
|
23.785
|
Rel-14
|
Solution for Key Issue#2 (via eNB-type RSU)
|
0.1.1
|
S2 160536
|
LG Electronics
|
Approved
|
FS_V2XARC
|
S2-113
|
23.785
|
Rel-14
|
Solution for Key Issue#2 (direct between UEs)
|
0.1.1
|
S2 160535
|
LG Electronics
|
Approved
|
FS_V2XARC
|
S2-113
|
23.785
|
Rel-14
|
V2X Authorisation and parameter configurations
|
0.1.1
|
S2 160534
|
Ericsson
|
Approved
|
FS_V2XARC
|
S2-113
|
23.785
|
Rel-14
|
Changes to ProSe Architecture for V2X support
|
0.1.1
|
S2 160533
|
Qualcomm Incorporated
|
Approved
|
FS_V2XARC
|
S2-113
|
23.785
|
Rel-14
|
RSU's role in V2I and V2N
|
0.1.1
|
S2 160544
|
Nokia Networks, Alcatel-Lucent
|
Approved
|
FS_V2XARC
|
S2-113
|
23.785
|
Rel-14
|
Update of reference to add a new SA1 TS
|
0.1.1
|
S2 160176
|
LG Electronics
|
Approved
|
FS_V2XARC
|
S2-113
|
23.785
|
Rel-14
|
V2X reference architecture
|
0.1.1
|
S2 160543
|
Huawei, Hisilicon
|
Approved
|
FS_V2XARC
|
S2-113
|
23.799
|
Rel-14
|
Update to TR Skeleton for the Study on Architecture for Next Generation System
|
0.1.0
|
S2 160704
|
Nokia Networks, China Mobile
|
Approved
|
FS_NextGen
|
S2-113
|
23.799
|
Rel-14
|
Key issue on session management for 3GPP network
|
0.1.1
|
S2 160752
|
China Mobile, Qualcomm Incorporated, Ericsson, Intel
|
Approved
|
FS_NextGen
|
S2-113
|
23.799
|
Rel-14
|
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
|
0.1.1
|
S2 160879
|
Qualcomm Incorporated, ZTE, KDDI, Nokia Networks
|
Approved
|
FS_NextGen
|
S2-113
|
23.799
|
Rel-14
|
Requirements on optimized UE sleep state and state transitions
|
0.1.1
|
S2 160872
|
Ericsson
|
Approved
|
FS_NextGen
|
S2-113
|
23.799
|
Rel-14
|
Update of High level Architectural Requirements
|
0.1.1
|
S2 160873
|
LG Electronics
|
Approved
|
FS_NextGen
|
S2-113
|
23.799
|
Rel-14
|
Key issue: 3GPP architecture impacts to support network slicing
|
0.1.1
|
S2 160875
|
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
|
Approved
|
FS_NextGen
|
S2-113
|
23.799
|
Rel-14
|
New key issue: NexGen architecture impacts to support a mobility framework
|
0.1.1
|
S2 160877
|
Ericsson, CATT, NTT DOCOMO, China Telecom, NEC, Qualcomm Incorporated, Motorola Mobility, Lenovo, ZTE, Sprint, Intel, ETRI
|
Approved
|
FS_NextGen
|
S2-113
|
23.799
|
Rel-14
|
NGMN terminology and conceptual outline for Network Slicing
|
0.1.1
|
S2 160881
|
Ericsson, Cisco Systems, Inc., NTT DOCOMO, Huawei, HiSilicon, China Mobile
|
Approved
|
FS_NextGen
|
S2-113
|
23.799
|
Rel-14
|
The assumptions for overall architecture
|
0.1.1
|
S2 160818
|
Huawei, HiSilicon, China Mobile
|
Approved
|
FS_NextGen
|
S2-113
|
23.799
|
Rel-14
|
Key issue: QoS Framework
|
|
S2 160930
|
Nokia Networks, AT&T, Deutsche Telekom AG, China Mobile, Ericsson, Intel, Qualcomm Incorporated, ZTE, ETRI, KT, Allot Communications, Samsung, Mediatek
|
Approved
|
FS_NextGen
|
S2-113
|
23.799
|
Rel-14
|
Key Issue on Session Continuity in the Next Generation System Architecture
|
0.1.1
|
S2 160931
|
Qualcomm Incorporated, Motorola Mobility, Lenovo, Cisco Systems, Inc., Intel, Huawei
|
Approved
|
FS_NextGen
|
S2-113
|
23.799
|
Rel-14
|
New key issue proposal on network capability exposure
|
0.1.0
|
S2 160880
|
Samsung, China Telecom, KDDI, CATT, Qualcomm Incorporated, Allot Communications, AT&T
|
Approved
|
FS_NextGen
|
