3GPP TDocs (written contributions) at meeting
Meeting: S2-103 - 2014-05-19 to 2014-05-23, Phoenix
meeting id: S2-103 (click id for more info on this meeting)Click on the Tdoc to open its file.
TDoc | Title | Source | Remarks |
---|---|---|---|
S2‑141512 | Draft Agenda for SA WG2#103 | SA WG2 Chairman | Revised in S2-142024 |
S2‑141513 | Draft Report of SA WG2 meeting #102 | SA WG2 Secretary | Approved |
S2‑141514 | LS from CT WG1: LS on default APN operation | CT WG1 | Response in S2-142264 |
S2‑141515 | LS from CT WG1: LS on selection of transport for USSD signalling | CT WG1 | Noted |
S2‑141516 | LS from CT WG4: LS on HRPD to LTE Optimized HO | CT WG4 | Postponed |
S2‑141517 | LS from OMA: LS to 3GPP SA1 about SEES work item | OMA | Response in S2-142221 |
S2‑141518 | LS from oneM2M: LS to 3GPP on support of alternate device triggering scheme for non-SMS capable devices | oneM2M | Noted |
S2‑141519 | LS from RAN WG2: LS on Core Network assisted eNodeB parameters tuning | RAN WG2 | Response in S2-142263 |
S2‑141520 | LS from SA WG3: LS on removal of SA3 text in TS 23.682 | SA WG3 | Noted |
S2‑141521 | LS from SA WG3LI: MTC Device Identification for LI | SA WG3LI | Noted |
S2‑141522 | LS from TSG SA: LS on 3GPP activities on Network Functions Virtualisation | TSG SA | Postponed |
S2‑141523 | An off-path solution for user plane congestion reporting | Alcatel-Lucent | Noted |
S2‑141524 | Clarifying when the PGW can set ULI reporting, CSG reporting and PRA reporting | Alcatel-Lucent | Revised |
S2‑141525 | Clarifying when the PGW can set ULI reporting, CSG reporting and PRA reporting | Alcatel-Lucent | Revised |
S2‑141526 | Rel13 WID on IMS webRTC | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, China Mobile, AT&T, NTT DoCoMo, ZTE, Huawei, Orange | Revised |
S2‑141527 | Correction of HS2.0 reference | BlackBerry UK Ltd | Revised |
S2‑141528 | On the selection of equivalent PLMNs | BlackBerry UK Ltd | Withdrawn |
S2‑141529 | Correction on EPLMN selection with ANDSF | BlackBerry UK Ltd | Withdrawn |
S2‑141530 | Introduce missing ATGW into architecture | BlackBerry UK Ltd. | Revised |
S2‑141531 | Introduce missing ATGW into architecture | BlackBerry UK Ltd. | Noted |
S2‑141532 | Introduce missing ATGW into architecture | BlackBerry UK Ltd. | Noted |
S2‑141533 | 380 - Emergency call clarification | BlackBerry UK Ltd. | Revised |
S2‑141534 | 380 - Emergency call clarification | BlackBerry UK Ltd. | Revised |
S2‑141535 | 380 - Emergency call clarification | BlackBerry UK Ltd. | Revised |
S2‑141536 | Pre-TSG SA#64 Work Planning Worksheet | SA WG2 Chairman | Revised |
S2‑141537 | SA WG2 Release 13 Time Budgeting Approach | SA WG2 Chairman | Noted |
S2‑141538 | WID for enhanced CSFB | China Unicom, Qualcomm Incorporated, Deutsche Telekom, ZTE, Huawei, HiSilicon, CATR, CATT, Mediatek, III, Broadcom Corporation, Telefonica | Revised |
S2‑141539 | Draft LS on 3GPP Rel12 Trusted WLAN access to EPC | Alcatel-Lucent | Revised |
S2‑141540 | Draft LS on Next Hop policy rule use case | Alcatel-Lucent | Revised |
S2‑141541 | Paging Policy Differentiation for Voice over LTE | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Verizon, Oracle, LG Electronics | Revised |
S2‑141542 | Paging Policy Differentiation for Voice over LTE | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Verizon, Oracle | Not Handled |
S2‑141543 | Paging Policy Differentiation for Voice over LTE | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Verizon, Oracle | - |
S2‑141544 | Paging Policy Differentiation for Voice over LTE | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | - |
S2‑141545 | LS from BBF: Release of TR-291 - Nodal Requirements for Interworking between Next Generation Fixed and 3GPP Wireless Access | BBF | Response in S2-141974 |
S2‑141546 | LS from BBF: Reply to 3GPP/SA WG2 liaison regarding Next Hop policy rule use case | BBF | Response in S2-142148 |
S2‑141547 | LS from CT WG1: Reply LS on removing source IP port from ISPR and IARP | CT WG1 | Noted |
S2‑141548 | LS from CT WG1: LS on precedence of UICC over ME for ProSe configuration information in a public safety ProSe enabled UE | CT WG1 | Noted |
S2‑141549 | LS from CT WG1: Reply LS on GCSE QCIs and connected mode DRX | CT WG1 | Noted |
S2‑141550 | LS from CT WG1: LS on impact of PC3 transport protocol on PC3 security | CT WG1 | Response in S2-142275 |
S2‑141551 | LS from CT WG1: LS on session management back-off timer in UE connected to TWAN | CT WG1 | Response in S2-142197 |
S2‑141552 | LS from CT WG1: Reply LS on BCM handling in NW init procedures | CT WG1 | Noted |
S2‑141553 | LS from CT WG1: Reply LS on IMS registration using I2 and CSFB interaction | CT WG1 | Noted |
S2‑141554 | LS from CT WG1: LS on PS services resuming after CSFB failure | CT WG1 | Response in S2-142139 |
S2‑141555 | LS from CT WG3: Reply LS on credit management session failure handling for the TDF | CT WG3 | Noted |
S2‑141556 | LS from CT WG3: Reply LS on providing parameters to TDF | CT WG3 | Noted |
S2‑141557 | LS from CT WG4: Reply LS on GCSE QCIs and connected mode DRX | CT WG4 | Noted |
S2‑141558 | LS from CT WG4: Reply LS on MTC Device Identification for LI | CT WG4 | Noted |
S2‑141559 | LS from RAN WG2: Answer on: LS on eMBMS broadcast areas with EUTRAN Cell Granularity | RAN WG2 | Postponed |
S2‑141560 | LS from RAN WG2: Reply LS on Choice of scheduling period for MBMS | RAN WG2 | Postponed |
S2‑141561 | LS from RAN WG2: LS on WLAN signal measurements for WLAN/3GPP Radio interworking | RAN WG2 | Noted |
S2‑141562 | LS from RAN WG3: LS on S1-U tunnel switch for DC | RAN WG3 | Noted |
S2‑141563 | LS from RAN WG3: Reply LS on choice of scheduling period for MBMS | RAN WG3 | Postponed |
S2‑141564 | LS from RAN WG3: Reply LS on GCSE QCIs and connected mode DRX | RAN WG3 | Noted |
S2‑141565 | LS from RAN WG3: LS on the fast return after CSFB | RAN WG3 | Noted |
S2‑141566 | LS from RAN WG3: LS on the ProSe authorized indication | RAN WG3 | Postponed |
S2‑141567 | LS from SA WG3: LS on scope of ProSe in Rel-12 | SA WG3 | Response in S2-142087 |
S2‑141568 | LS from SA WG3: Reply LS on security aspects of protocol architectures for small cell enhancements | SA WG3 | Noted |
S2‑141569 | LS from SA WG3: LS on securing the interface between a Proximity Service UE and the SLP server. | SA WG3 | Noted |
S2‑141570 | Paging Policy Differentiation for Voice over LTE : EPC layer | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | Not Handled |
S2‑141571 | LS from SA WG3-LI: Reply LS on new work item on “IMS Support for RTP/RTCP transport multiplexing | SA WG3-LI | Noted |
S2‑141572 | LS from SA WG3-LI: Reply LS on ProSe Lawful Interception | SA WG3-LI | Noted |
S2‑141573 | LS from SA WG3-LI: LI for GCSE | SA WG3-LI | Postponed |
S2‑141574 | Key issue#3 description alignment with the current standardization status | Allot Communications | Revised |
S2‑141575 | RCAF solution evaluation's extension | Allot Communications, Cisco Systems, Openet Telecom, Oracle, Rogers Wireless, Movik Networks, AT&T, ZTE, KDDI, Comverse, NTT Docomo, IAESI, Bell Mobility, China Telecom | Noted |
S2‑141576 | Extension of Evaluation section | Allot Communications | Revised |
S2‑141577 | Homogeneous support of PRA reporting in a network | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | Revised |
S2‑141578 | Release of the User Identities allocated from a pool of Public User Identities at the WWSF | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | Noted |
S2‑141579 | MME control for consistence of S1-U and S1-MME address type | China Telecom, Huawei, ZTE, NSN | Noted |
S2‑141580 | Clarification on MME behaviour on roaming situation | Orange | Revised |
S2‑141581 | Clarification on MME behaviour on roaming situation | Orange | Revised |
S2‑141582 | Clarification on SGSN behaviour on roaming situation | Orange | Revised |
S2‑141583 | Clarification on SGSN behaviour on roaming situation | Orange | Revised |
S2‑141584 | Modify Related MBMS Bearers | Alcatel-Lucent | Noted |
S2‑141585 | Discussion on new bearer characteristics | Alcatel-Lucent | Noted |
S2‑141586 | Discussion on MCPTT architecture | Alcatel-Lucent | Not Handled |
S2‑141587 | AESE Architecture | Alcatel-Lucent | Revised |
S2‑141588 | Stage 2 MCPTT Work Planning | U.S. Department of Commerce (SA WG2 MCPTT Rapporteur) | Noted |
S2‑141589 | Proposed TR 23.8xx Outline for Stage 2 MCPTT | U.S. Department of Commerce (SA WG2 MCPTT Rapporteur) | Revised |
S2‑141590 | Proposed Scope for Stage 2 MCPTT in TR 23.8xx | U.S. Department of Commerce, U.K. Home Office, Alcatel-Lucent, Deutsche Telekom, General Dynamics, NSN, Motorola Solutions | Revised |
S2‑141591 | LS from ETSI TC TCCE: TCCE Analysis on the scope of GCSE and the PTT Application. | ETSI TC TCCE | Noted |
S2‑141592 | LS from OMA COM: LS to 3GPP TSG SA, SA WG1 and SA WG2 on MCPTT | OMA COM | Noted |
S2‑141593 | Editorial corrections to clause 4 | General Dynamics UK Limited, Alcatel-Lucent | - |
S2‑141594 | Editorial corrections to clause 5.1 | General Dynamics UK Limited, Alcatel-Lucent | - |
S2‑141595 | Editorial corrections to clauses 5.2, 5.3, and 5.4 | General Dynamics UK Limited, Alcatel-Lucent | - |
S2‑141596 | Editorial corrections to Annex A | General Dynamics UK Limited, Alcatel-Lucent | - |
S2‑141597 | Minor corrections and clarifications to clauses 5.1 and 5.2 | General Dynamics UK Limited | - |
S2‑141598 | Clarification of actions consequent upon TMGI expiry | General Dynamics UK Limited, Alcatel-Lucent, Huawei | Revised |
S2‑141599 | Editorial corrections to clauses 1 and 3.1 | General Dynamics UK Limited | - |
S2‑141600 | Editorial corrections to clauses 4.1 - 4.4 | General Dynamics UK Limited | - |
S2‑141601 | Editorial corrections to clauses 4.5 and 4.6 | General Dynamics UK Limited | - |
S2‑141602 | Editorial corrections to clauses 5.1 and 5.2 | General Dynamics UK Limited | - |
S2‑141603 | Editorial corrections to clause 5.3 | General Dynamics UK Limited | - |
S2‑141604 | Editorial corrections to clause 5.4 | General Dynamics UK Limited | - |
S2‑141605 | Editorial corrections to clause 5.5 | General Dynamics UK Limited | - |
S2‑141606 | Editorial corrections to clauses 5.6, 5.7 and Annex A | General Dynamics UK Limited | - |
S2‑141607 | Revised NBIFOM scope in TR 23.861 | Verizon, Oracle | Not Handled |
S2‑141608 | Revised functionality for current NB_IFOM TR | Qualcomm Incorporated | Not Handled |
S2‑141609 | UE-Initiated S2a NB_IFOM | Qualcomm Incorporated | Not Handled |
S2‑141610 | Traffic steering for solution without ANDSF | Qualcomm Incorporated | Noted |
S2‑141611 | Traffic steering for solution without ANDSF | Qualcomm Incorporated | Revised |
S2‑141612 | Traffic steering for solution without ANDSF | Qualcomm Incorporated | Revised |
S2‑141613 | Discussion paper on QCI values for Public Safety services | Motorola Solutions | Noted |
S2‑141614 | QCI values for Public Safety services | Motorola Solutions | - |
S2‑141615 | QCI values for Public Safety services | Motorola Solutions | Merged into S2-142048 |
S2‑141616 | [DRAFT] LS on the scope of the 3GPP MCPTT specifications | Motorola Solutions | Noted |
S2‑141617 | Clarification on authorization policy for ProSe Direct Discovery | LG Electronics, CATT | Revised |
S2‑141618 | Abbreviations - addition and correction | LG Electronics | - |
S2‑141619 | Clarification on roaming subscription corresponding to specific RAT for 23.401 | China Mobile, Huawei | Noted |
S2‑141620 | Clarification on roaming subscription corresponding to specific RAT for 23.221 | China Mobile, Huawei | Revised |
S2‑141621 | PGW Identity Notification in TAU procedure | Huawei, HiSilicon, China Mobile, China Unicom | Noted |
S2‑141622 | Update of WebRTC architecture to align with SA3 | Huawei | Revised |
S2‑141623 | Usage of RAN Assistance Parameters in ANDSF Policy | Huawei, Hisilicon | Noted |
S2‑141624 | Usage of RAN Assistance Parameters in ANDSF Policy | Huawei, HiSilicon | - |
S2‑141625 | Usage of OPI in ANDSF Policy | Huawei, Hisilicon | Not Handled |
S2‑141626 | Usage of OPI in ANDSF Policy | Huawei, HiSilicon | - |
S2‑141627 | Consideration on Rel-13 WebRTC enhancement work | Huawei | Noted |
S2‑141628 | Discussion on synchronizing service settings data management between CS and IMS | China Mobile, ZTE, Huawei | Noted |
S2‑141629 | Synchronizing service settings data management between CS and IMS | China Mobile, ZTE, Huawei | Revised |
S2‑141630 | Inter PLMN handover for emergency bearer service | ZTE | Revised |
S2‑141631 | Clarification on EPS bearer used for GCS | ZTE | Noted |
S2‑141632 | Architecture Proposal for AESE | ZTE | Not Handled |
S2‑141633 | Correction to the SGSN initiated bearer setup during the RAU procedure. | NEC | Revised |
S2‑141634 | Correction to the MME initiated bearer setup during the TAU procedure. | NEC | Revised |
S2‑141635 | PGW initiated bearer request message arrival during the TAU. | NEC | Revised |
S2‑141636 | Evaluation of policy based congestion mitigation | NEC, Cisco, Allot Communications, NTT DOCOMO | Not Handled |
S2‑141637 | Clarification on the use of CELL ID for policy-based congestion mitigation | NEC, Huawei, China Mobile, Samsung | Noted |
S2‑141638 | Applicability and evaluation of static congestion mitigation policies | NEC, NSN | Revised |
S2‑141639 | Introduction of Dual Connectivity Function | Ericsson, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Huawei | Revised |
S2‑141640 | Update of GC1reference point for GCSE | Ericsson | Revised |
S2‑141641 | Improvement for PS-to-CS SRVCC in Conjunction with ATCF/ATGW | Ericsson, ATT, Rogers | Noted |
S2‑141642 | ATCF-Optimization for Transcoder Free Operation after PS-to-CS SRVCC | Ericsson. ATT, Rogers | - |
S2‑141643 | MSC-Optimization for Transcoder Free Operation after PS-to-CS SRVCC | Ericsson, ATT, Rogers | - |
S2‑141644 | Improvement for CSFB with I2 Registration for Handling of Terminating Calls | Ericsson | Noted |
S2‑141645 | Correction of ULI reporting only when the UE is in 'CONNECTED' state. | Ericsson, Cisco | Revised |
S2‑141646 | Correction of ULI reporting only when the UE is in 'CONNECTED' state. | Ericsson, Cisco | Revised |
S2‑141647 | Correction of ULI reporting only when the UE is in 'CONNECTED' state. | Ericsson, Cisco | Revised |
S2‑141648 | Sharing resources for IMS sessions | Ericsson | Noted |
S2‑141649 | PCC Rules sharing resources | Ericsson | Revised |
S2‑141650 | Sharing Resources For Sessions on Hold | Ericsson | Revised |
S2‑141651 | Offloadability indication for RAN-based solution without ANDSF | Ericsson, NSN, Nokia | Noted |
S2‑141652 | Traffic steering for RAN-based WLAN interworking solution | Ericsson, NSN, Nokia | Revised |
S2‑141653 | Co-existences of ANDSF solution and solution without ANDSF | Ericsson, NSN, Nokia | Noted |
S2‑141654 | Co-existence between ANDSF and RAN-based solution without ANDSF | Ericsson, NSN, Nokia | - |
S2‑141655 | Policy based on OPI | Ericsson, NSN, Nokia | Noted |
S2‑141656 | Thresholds in ANDSF | Ericsson | Noted |
S2‑141657 | Further evaluation of solution 2.3 (Existing Bearer Approach) | Ericsson, NSN | Not Handled |
S2‑141658 | Enhancements to solution 1.5.3 | Ericsson | Revised |
S2‑141659 | Updates to solution 1.5.5 | Ericsson | Merged into S2-142098 |
S2‑141660 | Design choices in the Np interface | Ericsson | Revised |
S2‑141661 | Resolution of editor's note on the use of GTP-U cell-id | Ericsson | Noted |
S2‑141662 | Congestion based rules at TDF and AF | Ericsson | Revised |
S2‑141663 | Evaluation of integrated solution | Ericsson | Not Handled |
S2‑141664 | RAN congestion mitigation function | Ericsson | Revised |
S2‑141665 | Solution for CSPS coordination issues | Ericsson | Revised |
S2‑141666 | Conclusion to TR23.704 | Ericsson | Not Handled |
S2‑141667 | Correction of SRVCC Scenarios | Ericsson | Revised |
S2‑141668 | Update to PLMN list handling | Ericsson | Revised in S2-142089 |
S2‑141669 | Update the interface description | Huawei, Hisilicon, Ericsson | Revised |
S2‑141670 | Corrections in the description of functional entities | NSN, Nokia, Ericsson | Revised |
S2‑141671 | BCM handling in NW init procedures | Ericsson, LG Electronics | Revised |
S2‑141672 | Paging enhancements for Low Complexity UE | Ericsson | Noted |
S2‑141673 | PSM indication | Ericsson | Noted |
S2‑141674 | CN assisted eNB parameter tuning | Ericsson, KDDI, NTT DOCOMO | Noted |
S2‑141675 | Completing specification of the CN Assistance information for eNB parameters tuning function | Ericsson, KDDI, NTT DOCOMO, NSN, Nokia, BlackBerry UK Ltd, U.S. Cellular | - |
S2‑141676 | Re-routing before NAS security setup | Ericsson | Not Handled |
S2‑141677 | Internet-of-Things (IoT) Messaging | Ericsson | Not Handled |
S2‑141678 | New WID on IoT messaging | Ericsson | Not Handled |
S2‑141679 | Maintenance of I-WLAN specifications | Broadcom Corporation, Intel, Deutsche Telekom | Not Handled |
S2‑141680 | De-coupling of WLAN interworking and I-WLAN at UE | Broadcom Corporation | - |
S2‑141681 | Maintenance of I-WLAN specifications | Broadcom Corporation | Revised |
S2‑141682 | RAN rules and ANDSF use cases | Broadcom Corporation | Noted |
S2‑141683 | Assumptions and Requirements for RAN Rules for Network selection use case | Broadcom Corporation | Revised |
S2‑141684 | WLAN Interworking: OPI | Broadcom Corporation, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | Not Handled |
S2‑141685 | Revised functionality for current NB_IFOM TR | Qualcomm Incorporated | Withdrawn |
S2‑141686 | UE-Initiated S2a NB_IFOM | Qualcomm Incorporated | Withdrawn |
S2‑141687 | Traffic steering for solution without ANDSF | Qualcomm Incorporated | Withdrawn |
S2‑141688 | Traffic steering for solution without ANDSF | Qualcomm Incorporated | Withdrawn |
S2‑141689 | Traffic steering for solution without ANDSF | Qualcomm Incorporated | Withdrawn |
S2‑141690 | Discussion on proposed LS OUT to CT, RAN WGs re notifications | Motorola Solutions | Noted |
S2‑141691 | [DRAFT] LS on notifications of (non)availability of eMBMS resources and service | Motorola Solutions | Noted |
S2‑141692 | Proposed change of terminology for used TMGIs over MB2 | Motorola Solutions | Revised |
S2‑141693 | Reuse of static TMGI values | Motorola Solutions | Noted |
S2‑141694 | Lift restriction GBR=MBR for MBMS when GCSE is used | Motorola Solutions | Revised |
S2‑141695 | Revised scope for IP Flow Mobility support for S2a and S2b Interfaces (NB-IFOM) | ZTE, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Broadcom Corporation, | Revised |
S2‑141696 | Clarification on RCAF solution as documented in clause 6.1.5.5. based on the agreement from SA WG2#102 | China Telecom, KDDI, ZTE | Revised |
S2‑141697 | PGW relocation due to SIPTO for IMS-based service | China Telecom, KDDI, ZTE | Noted |
S2‑141698 | PGW relocation due to SIPTO for IMS-based service | China Telecom, KDDI, ZTE | Noted |
S2‑141699 | Addressing EN related to tunnelling between PGW/GGSN and AF | China Telecom | Merged into S2-142042 |
S2‑141700 | The NAT trasversal related clarification for eP-CSCF and corrections | III | Noted |
S2‑141701 | The eIMS_AGW clarification for NAT trasversal | III | Noted |
S2‑141702 | Correction of the Proximity Alert procedure | Apple Inc. | Revised |
S2‑141703 | Cost-aware WLAN offloading | Apple Inc. | Not Handled |
S2‑141704 | PCRF discovery for the HNB CS Service | ZTE | Revised |
S2‑141705 | PCRF discovery for the HNB CS Service | ZTE | Revised |
S2‑141706 | IPv6 address in IP-CAN session establishment | ZTE | Revised |
S2‑141707 | Architecture Enhancements for Dedicated Networks | NTT DOCOMO | Revised |
S2‑141708 | Scope for Decor TR | NTT DOCOMO | Revised |
S2‑141709 | Some Architecture Requirements for Decor | NTT DOCOMO | Not Handled |
S2‑141710 | P-CR on Solution 1: Redirection Solution | NTT DOCOMO | Not Handled |
S2‑141711 | Consideration for different deployment scenarios | NTT DOCOMO | Revised |
S2‑141712 | TR Skeleton for AESE | Intel | Revised |
S2‑141713 | AESE TR Scope | Intel | Revised |
S2‑141714 | Key issue - Service Capability Exposure Framework | Intel | Revised |
S2‑141715 | TR Skeleton for MONTE | Intel | Revised |
S2‑141716 | MONTE TR Scope | Intel | Revised |
S2‑141717 | Key issue - Monitoring Enhancements | Intel | Merged into S2-142061 |
S2‑141718 | Correction to AESE WID timelines | Intel | Approved |
S2‑141719 | Correction to MONTE WID timelines | Intel | Approved |
S2‑141720 | Issues with the transmission of SMS and LCS messages via E-UTRAN when a PS MM back-off timer is running | Intel | Noted |
S2‑141721 | Transport of SMS and LCS messages while the MM back-off timer is running | Intel | - |
S2‑141722 | Transport of SMS and LCS messages while the MM back-off timer is running | Intel | - |
S2‑141723 | Transport of SMS and LCS messages while the MM back-off timer is running | Intel | - |
S2‑141724 | Issue on location reporting in emergency 1xSRVCC | Samsung | Not Handled |
S2‑141725 | Correction on location reporting in emergency 1xSRVCC | Samsung | Agreed |
S2‑141726 | Correction on location reporting in emergency 1xSRVCC | Samsung | Agreed |
S2‑141727 | Correction on location reporting in emergency 1xSRVCC | Samsung | Revised |
S2‑141728 | Correction on location reporting in emergency 1xSRVCC | Samsung | Revised |
S2‑141729 | [DRAFT] LS on location reporting in emergency 1xSRVCC | Samsung | Revised |
S2‑141730 | Handling of invalid Proximity Request due to exceeding time window | HTC | Revised |
S2‑141731 | Clarification of ProSe Function Feature for EPC assisted WLAN direct communication | HTC | Noted |
S2‑141732 | Handling of invalid EPC assisted WLAN direct communication | HTC | Noted |
S2‑141733 | The usage of Source Layer-2 ID and Destination Layer-2 ID | CATT | Noted |
S2‑141734 | Correction of authorization and provisioning for ProSe | CATT | - |
S2‑141735 | Correction of PC6 and PC7 interface | CATT | Merged into S2-142065 |
S2‑141736 | Update to RAN and CN Assistance Information | CATT | Withdrawn |
S2‑141737 | Correction to section 4.1 | CATT | - |
S2‑141738 | Clarification on PSPL | CATT | Revised |
S2‑141739 | Introduction of RAN assistance parameters in ANDSF rules | CATT | - |
S2‑141740 | Discussion of OPI: FFS and possible solution | CATT | Not Handled |
S2‑141741 | Introduction of OPI into TS 23.402 | CATT | - |
S2‑141742 | IP flow mobility routing rules negotiation in Single-Connection mode for S2a | CATT | Not Handled |
S2‑141743 | Addition of Network-initiated NB-IFOM trigger | CATT | Not Handled |
S2‑141744 | Usage of RAN assistance parameters in ANDSF rules | Motorola Mobility, Qualcomm Incorporated, Intel, Broadcom Corporation | Revised |
S2‑141745 | Usage of RAN assistance parameters in ANDSF rules | Motorola Mobility, Qualcomm Incorporated, Intel, Broadcom Corporation | Noted |
S2‑141746 | Co-existence between ANDSF rules and RAN rules | Motorola Mobility, Qualcomm Incorporated, Intel | Not Handled |
S2‑141747 | Correcting the reference to IEEE 802.11 | Motorola Mobility | Revised |
S2‑141748 | WLAN Interworking: RAN Sharing aspects | Cisco, Bell Mobility | Not Handled |
S2‑141749 | Clarification on VPLMN ID | ZTE | - |
S2‑141750 | Optimization of monitor request procedure | ZTE | - |
S2‑141751 | Clarification on the announcing authorisation policy | ZTE | Revised |
S2‑141752 | Clarification of MSISDN usage | ZTE | Revised |
S2‑141753 | ProSe Application ID authorization | ZTE | Noted |
S2‑141754 | Missing indication of TWAG WLCP IP version | ZTE | Revised |
S2‑141755 | Impact of TMSI reallocation on CS/PS coordination for SRVCC | TeliaSonera | Noted |
S2‑141756 | CS/PS coordination in the RAN based on additional information from the CN for the operator-centric approach | TeliaSonera | Revised |
S2‑141757 | Extension of Conclusions section | Allot Communications, Cisco Systems, Openet Telecom, Oracle, Rogers Wireless, Movik Networks, AT&T, ZTE, KDDI, Comverse, NTT Docomo, IAESI, Bell Mobility, Intel, China Telecom | Revised |
S2‑141758 | Discussion of PS service resuming after CSFB failure | Huawei, Hisilicon | Noted |
S2‑141759 | Discussion on ProSe Authorised Indication Transmitted in S1-MME interface | Huawei, Hisilicon, Ericsson, HTC, CATT | Noted |
S2‑141760 | Interaction between the ProSe and EPC procedures | Huawei, Hisllicon, Ericsson, HTC, CATT | Revised |
S2‑141761 | ProSe Subscription Data Stored in HSS | Huawei, Hisilicon | - |
S2‑141762 | Revocation Procedures for ProSe Direct Service | Huawei, Hisillicon | Revised |
S2‑141763 | Deactivate the MBMS bearer procedure | Huawei, Hisilicon | Revised |
S2‑141764 | Priority of Default Bearer | Huawei, Hisilicon | Revised |
S2‑141765 | Clarification on Timers in the open discovery procedure | Huawei, Hisilicon | Noted |
S2‑141766 | Clarification on Provisioning information | Huawei, Hisilicon | - |
S2‑141767 | Clarification on Match Report Procedure | Huawei, Hisilicon | - |
S2‑141768 | Introduction of Dual Connectivity Operation | Huawei, Hisilicon, Ericsson | Revised |
S2‑141769 | GROUPE TR Skeleton | Huawei, Hisilicon | Revised |
S2‑141770 | Adding scope section for GROUPE work | Huawei, Hisilicon | Approved |
S2‑141771 | Discussion of Group-specific congestion control | NTT DOCOMO, KDDI | Noted |
S2‑141772 | Group-specific congestion control | NTT DOCOMO, KDDI | - |
S2‑141773 | Group-specific congestion control | NTT DOCOMO, KDDI | - |
S2‑141774 | On the provision of core network assistance information to the eNB | BlackBerry UK Ltd. | Noted |
S2‑141775 | Usage of RAN assistance parameters in ANDSF | BlackBerry UK Ltd. | Noted |
S2‑141776 | Usage of RAN assistance parameters in ANDSF | BlackBerry UK Ltd | - |
S2‑141777 | Discovery Range Class definition and terminology alignment | NEC | Noted |
S2‑141778 | Revised NBIFOM service and architectural requirements in TR 23.861 | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | Revised |
S2‑141779 | Proper throttling of Downlink Data Notification requests | Orange | Noted |
S2‑141780 | Proper throttling of Downlink Data Notification requests | Orange | Noted |
S2‑141781 | Proper throttling of Downlink Data Notification requests | Orange | Noted |
S2‑141782 | Proper throttling of Downlink Data Notification requests | Orange | Noted |
S2‑141783 | Proper throttling of Downlink Data Notification requests | Orange | Noted |
S2‑141784 | Proper throttling of Downlink Data Notification requests | Orange | Noted |
S2‑141785 | CS breakout after T-ADS | Orange | Noted |
S2‑141786 | CS breakout after T-ADS | Orange | Noted |
S2‑141787 | Key Issue - Monitoring of unexpected data exchange | Orange | Withdrawn |
S2‑141788 | Study Phase TR Work Considerations | Samsung, Qualcomm Incorporated, Alcatel-Lucent | Noted |
S2‑141789 | Addressing Editor's Notes | Cisco Systems, AT&T, Bell, China Telecom, KDDI, NTT Docomo, Rogers Wireless, Allot Communications, Comverse, IAESI, Openet Telecom, Oracle, Movik Networks, ZTE | Revised |
S2‑141790 | Clarification on OAM parameter usage | Cisco Systems, AT&T, Bell, China Telecom, KDDI, NTT Docomo, Rogers Wireless, Allot Communications, Comverse, IAESI, Openet Telecom, Oracle, Movik Networks, ZTE | Revised |
S2‑141791 | Addressing ENs related to Rx | Intel, Huawei | Not Handled |
S2‑141792 | Addressing EN related to Gx and PMIP for solution 1.5.1 | Intel, NTT DOCOMO | Withdrawn |
S2‑141793 | CN Assistance information for eNB parameters setting | Alcatel-Lucent, NEC, Huawei, Vodafone, Orange,ZTE, Interdigital, Qualcomm | Withdrawn |
S2‑141794 | Rationale of the proposed way forward for the CN assisted eNB parameters setting. | Alcatel-Lucent, Orange, Vodafone, Huawei, NEC, ZTE, Interdigital, Qualcomm | Noted |
S2‑141795 | General corrections and removal of wrong statements | NSN, Nokia, Alcatel-Lucent, Huawei | Revised |
S2‑141796 | Re-assignment of user identities by the WWSF | NSN, Nokia | Revised |
S2‑141797 | Resolves editor's notes in solution proposing direct RCI transfer to TDF/AF | NSN | Merged into S2-142042 |
S2‑141798 | Using pre-configured congestion mitigation measures in PCEF | NSN, Nokia | Merged into S2-142046 |
S2‑141799 | Completing Solution 1.5.3: RPPF based RAN user plane congestion reporting | NSN | Revised |
S2‑141800 | Support of Load and Overload Control over S2a and S2b | Ericsson, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | Revised |
S2‑141801 | OPI usage with ANDSF | Ericsson, NSN, Nokia | Noted |
S2‑141802 | Priority and pre-emption for GCS | Ericsson | Revised |
S2‑141803 | IPX & ProSe Function implications | Ericsson | Withdrawn |
S2‑141804 | [DRAFT] Reply LS on default APN operation | Ericsson | Revised |
S2‑141805 | QCI considerations | Ericsson | Noted |
S2‑141806 | Correction to ANDSF for the use of service providers in PSPL | Qualcomm Incorporated | Revised |
S2‑141807 | Discussed Way Forward of NFV/SDN in EPC | China Mobile, CATR | Not Handled |
S2‑141808 | Add implicitly triggered flow mobility from network | China Mobile | Not Handled |
S2‑141809 | Clarify FPI+SCI Solution | China Mobile | Revised |
S2‑141810 | Addressing Issue for HPLMN to control policy when RAN rules used in VPLMN | T-Mobile USA Inc. | Not Handled |
S2‑141811 | Precedence on ANDSF and RAN based WLAN rules | T-Mobile USA | - |
S2‑141812 | Potential conflict scenarios between ANDSF & RAN Rules | T-Mobile USA Inc. | Not Handled |
S2‑141813 | HPLMN control of WLAN rules when roaming in network with RAN-based solution | T-Mobile USA | - |
S2‑141814 | Evaluations of RAN congestion reporting solutions | T-Mobile USA Inc. | Not Handled |
S2‑141815 | TCP Header insertion method for UPCON | T-Mobile USA Inc. | Noted |
S2‑141816 | Correction to MBMS Broadcast Area | Qualcomm Incorporated, Vodafone? | Noted |
S2‑141817 | [DRAFT] Reply LS on scope of ProSe in Rel-12 | Qualcomm Incorporated | Revised |
S2‑141818 | Completion of definitions | Qualcomm Incorporated, Broadcom Corporation? | Revised |
S2‑141819 | ProSe Application Code fix | Qualcomm Incorporated, CATT | Agreed |
S2‑141820 | Clarification of MSISDN usage | ZTE?, Qualcomm Incorporated | Merged into S2-142066 |
S2‑141821 | Wildcarded PLMN IDs in ProSe Application IDs and ProSe Application Codes | Qualcomm Incorporated | Noted |
S2‑141822 | Clarifications on the use of wild-carded ProSe App. IDs/ProSe App. Codes | Qualcomm Incorporated | Revised |
S2‑141823 | Completes the numbers of RAN and CT references | Qualcomm Incorporated | Revised |
S2‑141824 | UE provisioning and UICC support | Qualcomm Incorporated | - |
S2‑141825 | On using SIP without IMS on PC3 | Qualcomm Incorporated | Noted |
S2‑141826 | [DRAFT] Reply LS on impact of PC3 transport protocol on PC3 security | Qualcomm Incorporated | Revised |
S2‑141827 | Extended ProSe WID | Qualcomm Incorporated, Deutsche Telekom, ZTE, UK Home Office, CATT, US Department of Commerce, AT&T | Revised |
S2‑141828 | Coexistence between RAN rules and ANDSF rules | AT&T, InterDigital Communications | Not Handled |
S2‑141829 | Coexistence between RAN rules and ANDSF rules | AT&T, InterDigital Communications, | - |
S2‑141830 | Use of OPI in ANDSF | AT&T, InterDigital Communications, | Noted |
S2‑141831 | Use of OPI in ANDSF | AT&T, InterDigital Communications, | - |
S2‑141832 | Use of RAN Assistance Thresholds in ANDSF | AT&T, InterDigital Communications | Not Handled |
S2‑141833 | Use of RAN Assistance Thresholds in ANDSF | AT&T, InterDigital Communications, | - |
S2‑141834 | Editorial Corrections | InterDigital Communications | Revised |
S2‑141835 | Some insight on Core Network assistance information | Qualcomm Incorporated | Noted |
S2‑141836 | CN Assistance information for eNB parameters setting | Qualcomm, Alcatel-Lucent?, NEC?, Huawei?, Vodafone?, Orange?,ZTE?, Interdigital?, | Revised |
S2‑141837 | Uplink Congestion Relevance | Qualcomm Incorporated | Not Handled |
S2‑141838 | Uplink UPCON Solution for per bearer/user Performance Differentiation | Qualcomm Incorporated | Not Handled |
S2‑141839 | Uplink UPCON Solution for in-bearer Performance Differentiation | Qualcomm Incorporated | Not Handled |
S2‑141840 | Key issue on group message delivery selection | Qualcomm Incorporated | Revised |
S2‑141841 | [DRAFT] Reply LS on PS services resuming after CSFB failure | Qualcomm Incorporated | Revised |
S2‑141842 | Clarification on ProSe Direct Discovery Procedures in Roaming Case | HTC | Revised |
S2‑141843 | From CT3: GCSE stage 2 related discussion points | NSN | Noted |
S2‑141844 | New QCI for GCSE | NSN | Noted |
S2‑141845 | New QCI for GCSE | NSN | Noted |
S2‑141846 | TMGI de-allocation by BM-SC | NSN | Merged into S2-142093 |
S2‑141847 | Clarifications to security requirements | NSN | Revised |
S2‑141848 | Clarifications to service description from BM-SC | NSN | Revised |
S2‑141849 | Clarifications to roaming models and MBMS Delivery media flow in the figures | NSN | - |
S2‑141850 | Flow ID allocation by BM-SC only | NSN | Revised |
S2‑141851 | adding MB2 to TS 23.002 due to GCSE_LTE feature. | NSN | Revised |
S2‑141852 | T-ADS handling with MTRR/MTRF | NSN | Noted |
S2‑141853 | T-ADS handling with MTRR/MTRF | NSN | Noted |
S2‑141854 | Handling CSFB request when VoLTE call is on-going in non SRVCC capable network/UE | NSN | Revised |
S2‑141855 | Handling CSFB request when VoLTE call is on-going in non SRVCC capable network/UE | NSN | Revised |
S2‑141856 | Handling CSFB request when VoLTE call is on-going in non SRVCC capable network/UE | NSN | Revised |
S2‑141857 | CS/PS coordination for PS Attach after CS mobility | NSN | Revised |
S2‑141858 | Solution-x (HSS based) for 'PS Attach after CS mobility' | NSN | Revised |
S2‑141859 | Solution-y (RAN based) for 'PS Attach after CS mobility' | NSN | Revised |
S2‑141860 | Solution evaluation extensions to CN-based reporting solutions | KDDI, ZTE | Not Handled |
S2‑141861 | Correction on Match Report handling for Roaming Case | LG Electronics | Noted |
S2‑141862 | Usage Monitoring Control PCC Extension | China Telecom, ZTE, Orange, KDDI, Allot communications, Huawei, China Unicom, CATT | Revised |
S2‑141863 | Clarification on ProSe UE functionality | LG Electronics | - |
S2‑141864 | Clarification on the design issues | LG Electronics | Noted |
S2‑141865 | Coexistence between ANDSF policies and RAN rules and roaming for WLAN/3GPP radio interworking | LG Electronics | - |
S2‑141866 | Correction to use of masks and filters | Huawei, Hisilicon | Revised |
S2‑141867 | Missing RPLMN during SRVCC for CS/ PS coordination | Huawei, Hisilicon | Revised |
S2‑141868 | Key issue for Group based policing | Huawei, Hisilicon | Revised |
S2‑141869 | Key issue for Group based messaging | Huawei, Hisilicon | Revised |
S2‑141870 | Key issue for Group based addressing and identifiers | Huawei, Hisilicon | Not Handled |
S2‑141871 | Updated WID timeline: Group based enhancements | Huawei, Hisilicon | Approved |
S2‑141872 | Use of BSSload in traffic routing policies | NSN, Nokia | Noted |
S2‑141873 | Combined MME/SGSN selection function in eNB and LAC/MMEGI configuration issue | NSN | Noted |
S2‑141874 | Bitmap approach OPI design | ITRI | Noted |
S2‑141875 | Introduce bitmap approach OPI | ITRI | - |
S2‑141876 | On the selection of equivalent PLMNs | BlackBerry UK Ltd. | Noted |
S2‑141877 | Correction on EPLMN selection with ANDSF | BlackBerry UK Ltd. | - |
S2‑141878 | Clarification of high level service authorization diagram | Deutsche Telekom | Merged to S2-142089 |
S2‑141879 | Clarification of overall procedure for ProSe Direct Discovery in case the UE is not roaming | Deutsche Telekom | - |
S2‑141880 | Inter PLMN handover for emergency bearer service | ZTE | Withdrawn |
S2‑141881 | Corrections for clause 5.3.3.3 | ITRI | - |
S2‑141882 | Corrections for clauses 5.3.3.4 and 5.3.3.5 | ITRI | - |
S2‑141883 | Dedicated Core Networks | NTT DOCOMO | Revised |
S2‑141884 | Paging Optimization for the low mobility devices | NTT DOCOMO | Noted |
S2‑141885 | Paging Optimization for the low mobility devices | NTT DOCOMO | Revised |
S2‑141886 | Select held session as the first transferred session for alerting + held session scenario with Mid-call feature | ZTE | Revised |
S2‑141887 | Select held session as the first transferred session for alerting + held session scenario with Mid-call feature | ZTE | Revised |
S2‑141888 | Select held session as the first transferred session for alerting + held session scenario with Mid-call feature | ZTE | Revised |
S2‑141889 | Clarification on the MSC behavoir in the eSRVCC procedure. | ZTE | Noted |
S2‑141890 | Discussion on the key issues of DRuMS | ZTE | Not Handled |
S2‑141891 | Charging for PCC rules with application identifier | Huawei, Hisilicon | Noted |
S2‑141892 | Charging for PCC rules with application identifier | Huawei, Hisilicon | Noted |
S2‑141893 | Enhancements for the FPI solution | Huawei, Hisilicon, Telecom Italia | Revised |
S2‑141894 | Evaluation of the FPI solution | Huawei, Hisilicon, Telecom Italia | Revised |
S2‑141895 | Proposed Service Capability Exposure Framework Model | Huawei | Revised |
S2‑141896 | Monitoring Enhancements related Transfer from TR 23.887 | Huawei | Revised |
S2‑141897 | Approach for support of dedicated CNs | Huawei, HiSilicon | Not Handled |
S2‑141898 | Correction on WIC initiation and delivery of user identities from WWSF | Samsung | Noted |
S2‑141899 | Missing procedures for WebRTC IMS Client | Samsung | Revised |
S2‑141900 | Handling of the 2nd terminating call when an IMS emergency call is ongoing | Samsung | Noted |
S2‑141901 | Handling of the 2nd terminating call when an IMS emergency call is ongoing | Samsung | Noted |
S2‑141902 | Operability for Group Calls | Vodafone | Noted |
S2‑141903 | Operability for Group Calls | Vodafone | - |
S2‑141904 | QCI for bearer for PTT group call | Vodafone | Merged into S2-142048 |
S2‑141905 | Mapping between EPS and Release 99 QoS parameters for new QCIs | Vodafone | - |
S2‑141906 | Scope of Dedicated Core Networks (Gn/GP, CS domain) | Vodafone | Withdrawn |
S2‑141907 | [DRAFT] Reply to OMA LS on SEES work item | Telecom Italia | Revised |
S2‑141908 | Correction on the description of Location Service function | China Unicom | Noted |
S2‑141909 | Correction on the description of Location Service function | China Unicom | Revised |
S2‑141910 | SA WG2 Architectural Views on GCSE and MCPTT | UK Home Office | Not Handled |
S2‑141911 | Supporting WiFi offloading without ANDSF | Samsung | Noted |
S2‑141912 | Supporting WiFi offloading without ANDSF | Samsung | Noted |
S2‑141913 | Clarification of how triggering deferred ULI reporting | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | - |
S2‑141914 | Support of Load and Overload Control over S2a and S2b | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Samsung | Withdrawn |
S2‑141915 | Discussion on preventing EPS detach | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | Not Handled |
S2‑141916 | Discussion on RAN-based WLAN interworking solution | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | Noted |
S2‑141917 | Introduction of traffic steering for RAN-based WLAN interworking solution | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | - |
S2‑141918 | Discussion on co-existence between ANDSF rules and RAN rules | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | Not Handled |
S2‑141919 | Co-existence between ANDSF rules and RAN rules | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | - |
S2‑141920 | Usage of RAN assistance parameters in ANDSF | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | Not Handled |
S2‑141921 | Short discussion on OPI | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | Not Handled |
S2‑141922 | Introduction of Offload Preference Indicator (alt.1) | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | - |
S2‑141923 | Introduction of Offload Preference Indicator (alt.2) | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | - |
S2‑141924 | Introduction of Offload Preference Indicator (alt.3) | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | - |
S2‑141925 | Definitions for DECOR | NEC | Not Handled |
S2‑141926 | Assumptions and Requirements for CN nodes pooling for DECOR | NEC | Not Handled |
S2‑141927 | Editorial corrections in EPC-level discovery procedures | Intel, Ericsson | Agreed |
S2‑141928 | Incomplete text on priority handling for one-to-many communication | Intel, Alcatel-Lucent | Noted |
S2‑141929 | Missing text on Layer-3 Protocol Data Unit Type | Intel, Alcatel-Lucent | Revised |
S2‑141930 | Usage of Source Layer-2 ID and Destination Layer-2 ID | Intel, Alcatel-Lucent | Revised |
S2‑141931 | Missing procedure on ProSe Application Code revocation | Intel | Revised |
S2‑141932 | On MCPTT interaction with ProSe and GCSE | Intel | Not Handled |
S2‑141933 | Clarification of combined MME/SGSN selection function | NSN | - |
S2‑141934 | Proposals for adding key issues for MONTE | HTC | Merged into S2-142061 |
S2‑141935 | Turning descriptive text related to MB2 reference point into stage-2 requirements | Orange, KPN | - |
S2‑141936 | Assumptions and Requirements for RAN Rules for Network selection use case | Broadcom Corporation | Noted |
S2‑141937 | LS to TSG SA on Maintenance of I-WLAN specifications | Broadcom Corporation | Revised |
S2‑141938 | Maintenance of I-WLAN specifications | Broadcom Corporation | Revised |
S2‑141939 | Clarification on PSPL | CATT | Noted |
S2‑141940 | Correction to ANDSF for the use of service providers in PSPL | Qualcomm Incorporated | Agreed |
S2‑141941 | Correction of HS2.0 reference | BlackBerry UK Ltd | Revised |
S2‑141942 | Revised NBIFOM service and architectural requirements in TR 23.861 | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | Revised |
S2‑141943 | Sharing Resources For Sessions on Hold | Ericsson | Noted |
S2‑141944 | PCC Rules sharing resources | Ericsson | Revised |
S2‑141945 | Revised scope for IP Flow Mobility support for S2a and S2b Interfaces (NB-IFOM) | ZTE, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Broadcom Corporation, | Approved |
S2‑141946 | Revised NBIFOM service and architectural requirements in TR 23.861 | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, LG Electronics , Qualcomm Corporation, ZTE, Broadcom Qualcomm Incorporated, Samsung | Revised |
S2‑141947 | Update of WebRTC architecture to align with SA3 | Huawei | Revised |
S2‑141948 | Re-assignment of user identities by the WWSF | NSN, Nokia | Revised |
S2‑141949 | General corrections and removal of wrong statements | NSN, Nokia, Alcatel-Lucent, Huawei | Agreed |
S2‑141950 | Missing procedures for WebRTC IMS Client | Samsung | Revised |
S2‑141951 | Clarification on SGSN behaviour on roaming situation | Orange | Revised |
S2‑141952 | Clarification on SGSN behaviour on roaming situation | Orange | Revised |
S2‑141953 | Clarification on MME behaviour on roaming situation | Orange | Revised |
S2‑141954 | Clarification on MME behaviour on roaming situation | Orange | Revised |
S2‑141955 | BCM handling in NW init procedures | Ericsson, LG Electronics | Agreed |
S2‑141956 | PCRF discovery for the HNB CS Service | ZTE | Revised |
S2‑141957 | PCRF discovery for the HNB CS Service | ZTE | Revised |
S2‑141958 | Clarifying when the PGW can set ULI reporting, CSG reporting and PRA reporting | Alcatel-Lucent | Agreed |
S2‑141959 | Clarifying when the PGW can set ULI reporting, CSG reporting and PRA reporting | Alcatel-Lucent | Agreed |
S2‑141960 | Traffic steering for RAN-based WLAN interworking solution | Ericsson, NSN, Nokia | Revised |
S2‑141961 | Traffic steering for solution without ANDSF | Qualcomm Incorporated | Revised |
S2‑141962 | Usage of RAN assistance parameters in ANDSF rules | Motorola Mobility, Qualcomm Incorporated, Intel, Broadcom Corporation | Revised |
S2‑141963 | Homogeneous support of PRA reporting in a network | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | Revised |
S2‑141964 | Select held session as the first transferred session for alerting + held session scenario with Mid-call feature | ZTE | Agreed |
S2‑141965 | Select held session as the first transferred session for alerting + held session scenario with Mid-call feature | ZTE | Agreed |
S2‑141966 | Select held session as the first transferred session for alerting + held session scenario with Mid-call feature | ZTE | Agreed |
S2‑141967 | Synchronizing service settings data management between CS and IMS | China Mobile, ZTE, Huawei | Revised |
S2‑141968 | Correction of ULI reporting only when the UE is in 'CONNECTED' state. | Ericsson, Cisco | Revised |
S2‑141969 | Correction of ULI reporting only when the UE is in 'CONNECTED' state. | Ericsson, Cisco | Revised |
S2‑141970 | Correction of ULI reporting only when the UE is in 'CONNECTED' state. | Ericsson, Cisco | Revised |
S2‑141971 | Draft LS on Next Hop policy rule use case | Alcatel-Lucent | Revised |
S2‑141972 | IPv6 address in IP-CAN session establishment | ZTE | Revised |
S2‑141973 | Homogeneous support of PRA reporting in a network | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | Agreed |
S2‑141974 | LS on 3GPP Rel12 Trusted WLAN access to EPC | SA WG2 | Approved |
S2‑141975 | Missing indication of TWAG WLCP IP version | ZTE | Agreed |
S2‑141976 | Support of Load and Overload Control over S2a and S2b | Ericsson, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | Agreed |
S2‑141977 | [DRAFT] Reply LS on session management back-off timer in UE connected to TWAN | SA WG2 | Revised |
S2‑141978 | Correcting the reference to IEEE 802.11 | Motorola Mobility | Agreed |
S2‑141979 | Traffic steering for solution without ANDSF | Qualcomm Incorporated | Noted |
S2‑141980 | [Draft] LS to RAN WG2 on availability of RAN assistance information | Qualcomm Incorporated | Revised |
S2‑141981 | Usage of WLAN thresholds for traffic steering | SA WG2 | Revised |
S2‑141982 | Usage of RAN assistance parameters in ANDSF rules | Motorola Mobility, Qualcomm Incorporated, Intel, Broadcom Corporation | Revised |
S2‑141983 | Correction of ULI reporting only when the UE is in 'CONNECTED' state. | Ericsson, Cisco | Revised |
S2‑141984 | Correction of ULI reporting only when the UE is in 'CONNECTED' state. | Ericsson, Cisco | Revised |
S2‑141985 | Correction of ULI reporting only when the UE is in 'CONNECTED' state. | Ericsson, Cisco | Agreed |
S2‑141986 | Correction of ULI reporting only when the UE is in 'CONNECTED' state. | Ericsson, Cisco | Revised |
S2‑141987 | Paging Optimization for the low mobility devices | NTT DOCOMO | Noted |
S2‑141988 | [DRAFT] Reply LS on PS services resuming after CSFB failure | Qualcomm Incorporated | Revised |
S2‑141989 | [DRAFT] Reply LS on default APN operation | Ericsson | Revised |
S2‑141990 | Inter PLMN handover for emergency bearer service | ZTE | Revised |
S2‑141991 | Correction of SRVCC Scenarios | Ericsson | Approved |
S2‑141992 | CS/PS coordination for PS Attach after CS mobility | NSN | Revised |
S2‑141993 | Missing RPLMN during SRVCC for CS/ PS coordination | Huawei, Hisilicon | Noted |
S2‑141994 | Solution for CSPS coordination issues | Ericsson | Revised |
S2‑141995 | CS/PS coordination in the RAN based on additional information from the CN for the operator-centric approach | TeliaSonera | Approved |
S2‑141996 | Solution-x (HSS based) for 'PS Attach after CS mobility' | NSN | Approved |
S2‑141997 | Solution-y (RAN based) for 'PS Attach after CS mobility' | NSN | Approved |
S2‑141998 | Cover Sheet | Rapporteur | Revised |
S2‑141999 | Draft LS on Issues with the transmission of SMS and LCS messages via E-UTRAN when a PS MM back-off timer is running | Intel | Revised |
S2‑142000 | Handling CSFB request when VoLTE call is on-going in non SRVCC capable network/UE | NSN | Revised |
S2‑142001 | Handling CSFB request when VoLTE call is on-going in non SRVCC capable network/UE | NSN | Agreed |
S2‑142002 | Handling CSFB request when VoLTE call is on-going in non SRVCC capable network/UE | NSN | Agreed |
S2‑142003 | Correction on the description of Location Service function | China Unicom | Revised |
S2‑142004 | Introduction of Dual Connectivity Operation | Huawei, Hisilicon, Ericsson | Revised |
S2‑142005 | Clarification on roaming subscription corresponding to specific RAT for 23.221 | China Mobile, Huawei | Revised |
S2‑142006 | Correction to the SGSN initiated bearer setup during the RAU procedure. | NEC | Revised |
S2‑142007 | Correction to the MME initiated bearer setup during the TAU procedure. | NEC | Revised |
S2‑142008 | PGW initiated bearer request message arrival during the TAU. | NEC | Agreed |
S2‑142009 | LS on MME control for consistence of S1-U and S1-MME address type | SA WG2 | Approved |
S2‑142010 | Introduce missing ATGW into architecture | BlackBerry UK Ltd. | Agreed |
S2‑142011 | 380 - Emergency call clarification | BlackBerry UK Ltd. | Revised |
S2‑142012 | 380 - Emergency call clarification | BlackBerry UK Ltd. | Revised |
S2‑142013 | 380 - Emergency call clarification | BlackBerry UK Ltd. | Revised |
S2‑142014 | Correction on location reporting in emergency 1xSRVCC | Samsung | Revised |
S2‑142015 | Correction on location reporting in emergency 1xSRVCC | Samsung | Revised |
S2‑142016 | [DRAFT] LS on location reporting in emergency 1xSRVCC | Samsung | Revised |
S2‑142017 | LS from SA WG5: LS to RAN3 - Clarifications about MOCN and GWCN | SA WG5 | Noted |
S2‑142018 | LS from SA WG5: LS on co-ordination of response LS to ITU JCA-SDN | SA WG5 | Noted |
S2‑142019 | LS from SA WG5: Reply LS on Maintenance of I-WLAN Solution | SA WG5 | Noted |
S2‑142020 | LS from SA WG1: Reply LS on MTC Device Identification for LI | SA WG1 | Noted |
S2‑142021 | LS from SA WG1: Reply to OMA about SEES work item | SA WG1 | Noted |
S2‑142022 | LS from SA WG1: LS on MCPTT Requirements | SA WG1 | Noted |
S2‑142023 | Information about TSDSI | Telecommunications Standards Development Society, India (TSDSI) | Not Handled |
S2‑142024 | Draft Agenda for SA WG2 meeting #103 | SA WG2 Chairman | Revised |
S2‑142025 | LS from SA WG3: Reply to LS on Maintenance of I-WLAN Solution (SA2-140554/S3-140728) and Reply to LS on Maintenance of I-WLAN Solution (SP-140149/S3-140731) | SA WG3 | Noted |
S2‑142026 | LS from SA WG3: LS on GCSE security | SA WG3 | Noted |
S2‑142027 | LS from SA WG3: Reply LS on impact of PC3 transport protocol on PC3 security | SA WG3 | Postponed |
S2‑142028 | LS from SA WG3: LS on discovery message format for ProSe/D2D | SA WG3 | Postponed |
S2‑142029 | LS from SA WG3: Reply LS on Provisioning of ProSe configuration information in a public safety ProSe enabled UE | SA WG3 | Noted |
S2‑142030 | LS from SA WG3: Reply LS on WLCP security aspects | SA WG3 | Noted |
S2‑142031 | LS from SA WG4: LS on TR 26.924 Study on improved end-to-end QoS handling | SA WG4 | Postponed |
S2‑142032 | LS from SA WG4: LS on introducing the EVS codec in MTSI | SA WG4 | Postponed |
S2‑142033 | LS from IEEE 802.11 WG: Reply Liaison on WLAN signal measurements for WLAN/3GPP Radio interworking | IEEE 802.11 WG | Noted |
S2‑142034 | Draft Agenda for SA WG2 meeting #103 | SA WG2 Chairman | Revised |
S2‑142035 | [DRAFT] Reply LS on impact of PC3 transport protocol on PC3 security | Qualcomm Incorporated | Revised |
S2‑142036 | WID for enhanced CSFB | China Unicom, Qualcomm Incorporated, Deutsche Telekom, ZTE, Huawei, HiSilicon, CATR, CATT, Mediatek, III, Broadcom Corporation, Telefonica | Revised |
S2‑142037 | Rel13 WID on IMS webRTC | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, China Mobile, AT&T, NTT DoCoMo, ZTE, Huawei, Orange | Revised |
S2‑142038 | Extended ProSe WID | Qualcomm Incorporated, Deutsche Telekom, ZTE, UK Home Office, CATT, US Department of Commerce, AT&T, HTC, General Dynamics UK Ltd, Telefonica, Motorola Mobility, KDDI, ITRI, LG Electronics, Interdigital, Intel | Revised |
S2‑142039 | Usage Monitoring Control PCC Extension | China Telecom, ZTE, Orange, KDDI, Allot communications, Huawei, China Unicom, CATT, Oracle | Revised |
S2‑142040 | Paging Policy Differentiation for Voice over LTE | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Verizon, Oracle, LG Electronics | Revised |
S2‑142041 | Dedicated Core Networks | NTT DOCOMO | Withdrawn |
S2‑142042 | Addressing EN related to tunnelling between PGW/GGSN and AF | China Telecom, NSN | Revised |
S2‑142043 | Key issue#3 description alignment with the current standardization status | Allot Communications | Revised |
S2‑142044 | Clarification on the use of CELL ID for policy-based congestion mitigation | Ericsson, NEC, Huawei, China Mobile, Samsung | Withdrawn |
S2‑142045 | Congestion based rules at TDF and AF | Ericsson | Revised |
S2‑142046 | Applicability and evaluation of static congestion mitigation policies | NEC, NSN | Withdrawn |
S2‑142047 | Draft Agenda for SA WG2 meeting #103 | SA WG2 Chairman | Approved |
S2‑142048 | QCI values for Public Safety services | Motorola Solutions | Withdrawn |
S2‑142049 | Addressing EN related to tunnelling between PGW/GGSN and AF | China Telecom, NSN | Withdrawn |
S2‑142050 | Enhancements to solution 1.5.3 | Ericsson | Withdrawn |
S2‑142051 | Completing Solution 1.5.3: RPPF based RAN user plane congestion reporting | NSN | Withdrawn |
S2‑142052 | Design choices in the Np interface | Ericsson | Approved |
S2‑142053 | Addressing Editor's Notes | Cisco Systems, AT&T, Bell, China Telecom, KDDI, NTT Docomo, Rogers Wireless, Allot Communications, Comverse, IAESI, Openet Telecom, Oracle, Movik Networks, ZTE | Approved |
S2‑142054 | Clarification on OAM parameter usage | Cisco Systems, AT&T, Bell, China Telecom, KDDI, NTT Docomo, Rogers Wireless, Allot Communications, Comverse, IAESI, Openet Telecom, Oracle, Movik Networks, ZTE | Approved |
S2‑142055 | Extension of Evaluation section | Allot Communications | Revised |
S2‑142056 | UPCON drafting session report | Rapporteur (Allot Communications) | Noted |
S2‑142057 | Reserved for UPCON Drafting session | - | Withdrawn |
S2‑142058 | Reserved for UPCON Drafting session | - | Withdrawn |
S2‑142059 | Reserved for UPCON Drafting session | - | Withdrawn |
S2‑142060 | Reserved for UPCON Drafting session | - | Withdrawn |
S2‑142061 | Key issue - Monitoring Enhancements | Intel, HTC | Revised |
S2‑142062 | Interaction between the ProSe and EPC procedures | Huawei, Hisllicon, Ericsson, HTC, CATT | Revised |
S2‑142063 | Revocation Procedures for ProSe Direct Service | Huawei, Hisillicon | Revised |
S2‑142064 | Missing procedure on ProSe Application Code revocation | Intel | Agreed |
S2‑142065 | Update the interface description | Huawei, Hisilicon, Ericsson, CATT | Revised |
S2‑142066 | Clarification of MSISDN usage | ZTE, Qualcomm Incorporated | Revised |
S2‑142067 | Reserved for ProSe drafting session | - | Withdrawn |
S2‑142068 | Reserved for ProSe drafting session | - | Withdrawn |
S2‑142069 | Reserved for ProSe drafting session | - | Withdrawn |
S2‑142070 | Reserved for ProSe drafting session | - | Withdrawn |
S2‑142071 | Reserved for ProSe drafting session | - | Withdrawn |
S2‑142072 | LS from RAN WG1: LS on D2D Multicarrier Capabilities | RAN WG1 | Postponed |
S2‑142073 | LS from SA WG5: Reply LS on ProSe Lawful Interception | SA WG5 | Postponed |
S2‑142074 | [DRAFT] Reply to OMA LS on SEES work item | SA WG2 | Revised |
S2‑142075 | TR Skeleton for AESE | Intel | Approved |
S2‑142076 | AESE TR Scope | Intel | Approved |
S2‑142077 | Key issue - Service Capability Exposure Framework | Intel | Revised |
S2‑142078 | TR Skeleton for MONTE | Intel | Approved |
S2‑142079 | MONTE TR Scope | Intel | Approved |
S2‑142080 | Monitoring Enhancements related Transfer from TR 23.887 | Huawei | Approved |
S2‑142081 | Key issue - Monitoring Enhancements | Intel, HTC | Approved |
S2‑142082 | AESE Architecture | Alcatel-Lucent | Approved |
S2‑142083 | Proposed Service Capability Exposure Framework Model | Huawei | Revised |
S2‑142084 | Completion of definitions | Qualcomm Incorporated, Broadcom Corporation? | Agreed |
S2‑142085 | Clarification on authorization policy for ProSe Direct Discovery | LG Electronics, CATT | Agreed |
S2‑142086 | Corrections in the description of functional entities | NSN, Nokia, Ericsson | Agreed |
S2‑142087 | Reply LS on scope of ProSe in Rel-12 | SA WG2 | Approved |
S2‑142088 | Completes the numbers of RAN and CT references | Qualcomm Incorporated | Agreed |
S2‑142089 | Update to PLMN list handling | Ericsson, LG Electronics | Revised |
S2‑142090 | Clarification on PC4a between the HSS and ProSe Function | LG Electronics | Merged into S2-142207 |
S2‑142091 | Clarifications to service description from BM-SC | NSN | Agreed |
S2‑142092 | Flow ID allocation by BM-SC only | NSN | Agreed |
S2‑142093 | Clarification of actions consequent upon TMGI expiry | General Dynamics UK Limited, Alcatel-Lucent, Huawei, NSN | Agreed |
S2‑142094 | Proposed change of terminology for used TMGIs over MB2 | Motorola Solutions | Agreed |
S2‑142095 | Deactivate the MBMS bearer procedure | Huawei, Hisilicon | Agreed |
S2‑142096 | Lift restriction GBR=MBR for MBMS when GCSE is used | Motorola Solutions | Agreed |
S2‑142097 | Updates to solution 1.5.5 | Ericsson | Withdrawn |
S2‑142098 | Clarification on RCAF solution as documented in clause 6.1.5.5. based on the agreement from SA WG2#102 | China Telecom, KDDI, ZTE, Ericsson, Allot, Cisco | Revised |
S2‑142099 | Clarify FPI+SCI Solution | China Mobile | Revised |
S2‑142100 | Enhancements for the FPI solution | Huawei, Hisilicon, Telecom Italia | Noted |
S2‑142101 | Evaluation of the FPI solution | Huawei, Hisilicon, Telecom Italia | Revised |
S2‑142102 | Proposed TR 23.8xx Outline for Stage 2 MCPTT | U.S. Department of Commerce (SA WG2 MCPTT Rapporteur) | Approved |
S2‑142103 | Proposed Scope for Stage 2 MCPTT in TR 23.8xx | U.S. Department of Commerce, U.K. Home Office, Alcatel-Lucent, Deutsche Telekom, General Dynamics, NSN, Vodafone | Approved |
S2‑142104 | LS from RAN WG3: LS on Introducing the ProSe Authorized IE | RAN WG3 | Response in S2-142277 |
S2‑142105 | DRAFT Resply on Introducing the ProSe Authorized IE | SA WG2 | Revised |
S2‑142106 | Interaction between the ProSe and EPC procedures | Huawei, Hisllicon, Ericsson, HTC, CATT | Revised |
S2‑142107 | Correction to use of masks and filters | Huawei, Hisilicon | Revised |
S2‑142108 | Clarification on the announcing authorisation policy | ZTE | Agreed |
S2‑142109 | Editorial Corrections | InterDigital Communications | Revised |
S2‑142110 | Clarification on ProSe Direct Discovery Procedures in Roaming Case | HTC | Agreed |
S2‑142111 | Clarifications on the use of wild-carded ProSe App. IDs/ProSe App. Codes | Qualcomm Incorporated | Revised |
S2‑142112 | Correction of the Proximity Alert procedure | Apple Inc. | Revised |
S2‑142113 | Handling of invalid Proximity Request due to exceeding time window | HTC, Intel | Revised |
S2‑142114 | Missing text on Layer-3 Protocol Data Unit Type | Intel, Alcatel-Lucent | Revised |
S2‑142115 | Usage of Source Layer-2 ID and Destination Layer-2 ID | Intel, Alcatel-Lucent, CATT | Revised |
S2‑142116 | Scope for Decor TR | NTT DOCOMO | Approved |
S2‑142117 | Consideration for different deployment scenarios | NTT DOCOMO | Revised |
S2‑142118 | Architecture Enhancements for Dedicated Networks | NTT DOCOMO | Approved |
S2‑142119 | GROUPE TR Skeleton | Huawei, Hisilicon | Approved |
S2‑142120 | Key issue for Group based policing | Huawei, Hisilicon | Revised |
S2‑142121 | Key issue for Group based messaging | Huawei, Hisilicon | Approved |
S2‑142122 | Key issue on group message delivery selection | Qualcomm Incorporated | Revised |
S2‑142123 | Reserved for Erik's parallel sessions | - | Withdrawn |
S2‑142124 | Reserved for Erik's parallel sessions | - | Withdrawn |
S2‑142125 | Reserved for Erik's parallel sessions | - | Withdrawn |
S2‑142126 | RAN congestion mitigation function | Ericsson | Approved |
S2‑142127 | Extension of Evaluation section | Allot Communications | Revised |
S2‑142128 | Extension of Conclusions section | Allot Communications, Cisco Systems, Openet Telecom, Oracle, Rogers Wireless, Movik Networks, AT&T, ZTE, KDDI, Comverse, NTT Docomo, IAESI, Bell Mobility, Intel, China Telecom | Revised |
S2‑142129 | CN Assistance information for eNB parameters setting | Qualcomm, Alcatel-Lucent, NEC, Huawei, Vodafone, Orange, ZTE, InterDigital, KDDI | Revised |
S2‑142130 | [DRAFT] Reply LS on default APN operation | Ericsson | Revised |
S2‑142131 | Inter PLMN handover for emergency bearer service | ZTE | Revised |
S2‑142132 | Draft LS on Issues with the transmission of SMS and LCS messages via E-UTRAN when a PS MM back-off timer is running | Intel | Revised |
S2‑142133 | Introduction of Dual Connectivity Function | Ericsson, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Huawei | Revised |
S2‑142134 | Introduction of Dual Connectivity Operation | Huawei, Hisilicon, Ericsson | Revised |
S2‑142135 | Cover Sheet | Rapporteur | Approved |
S2‑142136 | CS/PS coordination for PS Attach after CS mobility | NSN | Approved |
S2‑142137 | Solution for CSPS coordination issues | Ericsson | Approved |
S2‑142138 | [DRAFT] Reply LS on default APN operation | SA WG2 | Revised |
S2‑142139 | Reply LS on PS services resuming after CSFB failure | SA WG2 | Approved |
S2‑142140 | Inter PLMN handover for emergency bearer service | ZTE | Agreed |
S2‑142141 | Handling CSFB request when VoLTE call is on-going in non SRVCC capable network/UE | NSN | Agreed |
S2‑142142 | Correction to the SGSN initiated bearer setup during the RAU procedure. | NEC | Revised |
S2‑142143 | Correction to the MME initiated bearer setup during the TAU procedure. | NEC | Revised |
S2‑142144 | Correction to the MME initiated bearer setup during the TAU procedure. | NEC | Revised |
S2‑142145 | QCI values for Public Safety services | Motorola Solutions, Vodafone | Agreed |
S2‑142146 | Correction of ULI reporting only when the UE is in 'CONNECTED' state. | Ericsson, Cisco | Revised |
S2‑142147 | IPv6 address in IP-CAN session establishment | ZTE | Agreed |
S2‑142148 | LS on Next Hop policy rule use case | SA WG2 | Approved |
S2‑142149 | Clarification on MME behaviour on roaming situation | Orange | Agreed |
S2‑142150 | Clarification on MME behaviour on roaming situation | Orange | Agreed |
S2‑142151 | Clarification on SGSN behaviour on roaming situation | Orange | Agreed |
S2‑142152 | Clarification on SGSN behaviour on roaming situation | Orange | Agreed |
S2‑142153 | PCRF discovery for the HNB CS Service | ZTE | Agreed |
S2‑142154 | PCRF discovery for the HNB CS Service | ZTE | Agreed |
S2‑142155 | Update of WebRTC architecture to align with SA3 | Huawei | Agreed |
S2‑142156 | Re-assignment of user identities by the WWSF | NSN, Nokia | Agreed |
S2‑142157 | Missing procedures for WebRTC IMS Client | Samsung | Agreed |
S2‑142158 | Traffic steering for RAN-based WLAN interworking solution | Ericsson, NSN, Nokia | Revised |
S2‑142159 | PCC Rules sharing resources | Ericsson | Revised |
S2‑142160 | Synchronizing service settings data management between CS and IMS | China Mobile, ZTE, Huawei | Agreed |
S2‑142161 | PCC Rules sharing resources | Ericsson | Revised |
S2‑142162 | Correction of HS2.0 reference | BlackBerry UK Ltd | Agreed |
S2‑142163 | Maintenance of I-WLAN specifications | Broadcom Corporation, Qualcomm Inc., Motorola Mobility, Intel, T-Mobile, AT&T, Huawei, China Mobile, Ericsson, Deutsche Telekom, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | Agreed |
S2‑142164 | Traffic steering for RAN-based WLAN interworking solution | Ericsson, NSN, Nokia, Samsung, Qualcomm Incorporated, Broadcom Corporation, Huawei, Hisilicon, Intel | Revised |
S2‑142165 | Usage of RAN assistance parameters in ANDSF rules | Motorola Mobility, Qualcomm Incorporated, Intel, Broadcom Corporation, Huawei, HiSilicon, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | Agreed |
S2‑142166 | CN Assistance information for eNB parameters setting | Qualcomm, Alcatel-Lucent, NEC, Huawei, Vodafone, Orange, ZTE, InterDigital, KDDI | Revised |
S2‑142167 | [DRAFT] Reply LS on Core Network assisted eNodeB parameters tuning | SA WG2 | Revised |
S2‑142168 | Update of GC1reference point for GCSE | Ericsson | Agreed |
S2‑142169 | adding MB2 to TS 23.002 due to GCSE_LTE feature. | NSN | Agreed |
S2‑142170 | Clarifications to security requirements | NSN | Agreed |
S2‑142171 | Priority and pre-emption for GCS | Ericsson | Revised |
S2‑142172 | Priority of Default Bearer | Huawei, Hisilicon | Withdrawn |
S2‑142173 | Correction on the description of Location Service function | China Unicom | Agreed |
S2‑142174 | LS on Issues with the transmission of SMS and LCS messages via E-UTRAN when a PS MM back-off timer is running | SA WG2 | Approved |
S2‑142175 | Correction to the SGSN initiated bearer setup during the RAU procedure. | NEC | Agreed |
S2‑142176 | Correction to the MME initiated bearer setup during the TAU procedure. | NEC | Revised |
S2‑142177 | 380 - Emergency call clarification | BlackBerry UK Ltd. | Agreed |
S2‑142178 | 380 - Emergency call clarification | BlackBerry UK Ltd. | Agreed |
S2‑142179 | 380 - Emergency call clarification | BlackBerry UK Ltd. | Agreed |
S2‑142180 | Correction on location reporting in emergency 1xSRVCC | Samsung | Agreed |
S2‑142181 | Correction on location reporting in emergency 1xSRVCC | Samsung | Agreed |
S2‑142182 | [DRAFT] LS on location reporting in emergency 1xSRVCC | Samsung | Revised |
S2‑142183 | Introduction of Dual Connectivity Function | Ericsson, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Huawei | Agreed |
S2‑142184 | Introduction of Dual Connectivity Operation | Huawei, Hisilicon, Ericsson, Alcatel-Lucent | Revised |
S2‑142185 | LS on location reporting in emergency 1xSRVCC | SA WG2 | Approved |
S2‑142186 | Correction to the MME initiated bearer setup during the TAU procedure. | NEC | Agreed |
S2‑142187 | Reserved for Frank's parallel sessions | - | Withdrawn |
S2‑142188 | Reserved for Frank's parallel sessions | - | Withdrawn |
S2‑142189 | Reserved for Frank's parallel sessions | - | Withdrawn |
S2‑142190 | Reserved for Frank's parallel sessions | - | Withdrawn |
S2‑142191 | Reserved for Frank's parallel sessions | - | Withdrawn |
S2‑142192 | Reserved for Frank's parallel sessions | - | Withdrawn |
S2‑142193 | LS to TSG SA on Maintenance of I-WLAN specifications | SA WG2 | Revised |
S2‑142194 | Usage of WLAN thresholds for traffic steering | SA WG2 | Revised |
S2‑142195 | Correction of ULI reporting only when the UE is in 'CONNECTED' state. | Ericsson, Cisco | Agreed |
S2‑142196 | Correction of ULI reporting only when the UE is in 'CONNECTED' state. | Ericsson, Cisco | Agreed |
S2‑142197 | Reply LS on session management back-off timer in UE connected to TWAN | SA WG2 | Approved |
S2‑142198 | Traffic steering for solution without ANDSF | Qualcomm Incorporated | Agreed |
S2‑142199 | LS to RAN WG2 on availability of RAN assistance information | Qualcomm Incorporated | Approved |
S2‑142200 | Usage of WLAN thresholds for traffic steering | SA WG2 | Approved |
S2‑142201 | Revised NBIFOM service and architectural requirements in TR 23.861 | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, LG Electronics , Qualcomm Corporation, ZTE, Broadcom Qualcomm Corporation, Samsung | Revised |
S2‑142202 | Maintenance of I-WLAN specification | SA WG2 | Approved |
S2‑142203 | Revocation Procedures for ProSe Direct Service | Huawei, Hisillicon | Revised |
S2‑142204 | - | - | Withdrawn |
S2‑142205 | Update to PLMN list handling | Ericsson, LG Electronics | Agreed |
S2‑142206 | Revocation Procedures for ProSe Direct Service | Huawei, Hisillicon | Agreed |
S2‑142207 | Update the interface description | Huawei, Hisilicon, Ericsson, CATT | Agreed |
S2‑142208 | Clarification of MSISDN usage | ZTE, Qualcomm Incorporated | Agreed |
S2‑142209 | Editorial Corrections | InterDigital Communications | Agreed |
S2‑142210 | Clarifications on the use of wild-carded ProSe App. IDs/ProSe App. Codes | Qualcomm Incorporated | Revised |
S2‑142211 | Extension of Evaluation section | Allot Communications | Approved |
S2‑142212 | Extension of Conclusions section | Allot Communications, Cisco Systems, Openet Telecom, Oracle, Rogers Wireless, Movik Networks, AT&T, ZTE, KDDI, Comverse, NTT Docomo, IAESI, Bell Mobility, Intel, China Telecom | Revised |
S2‑142213 | Clarification on RCAF solution as documented in clause 6.1.5.5. based on the agreement from SA WG2#102 | China Telecom, KDDI, ZTE, Ericsson, Allot, Cisco | Approved |
S2‑142214 | Extension of Conclusions section | Allot Communications, Cisco Systems, Openet Telecom, Oracle, Rogers Wireless, Movik Networks, AT&T, ZTE, KDDI, Comverse, NTT Docomo, IAESI, Bell Mobility, Intel, China Telecom | Approved |
S2‑142215 | Congestion based rules at TDF and AF | Ericsson | Approved |
S2‑142216 | Key issue#3 description alignment with the current standardization status | Allot Communications | Approved |
S2‑142217 | Clarify FPI+SCI Solution | China Mobile | Approved |
S2‑142218 | Pre-TSG SA#64 Work Planning Worksheet | SA WG2 Chairman | Endorsed |
S2‑142219 | CN Assistance information for eNB parameters setting | Qualcomm, Alcatel-Lucent, NEC, Huawei, Vodafone, Orange, ZTE, InterDigital, KDDI, NTT DOCOMO, Intel | Revised |
S2‑142220 | Consideration for different deployment scenarios | NTT DOCOMO | Approved |
S2‑142221 | Reply to OMA LS on SEES work item | SA WG2 | Approved |
S2‑142222 | Key issue - Service Capability Exposure Framework | Intel | Approved |
S2‑142223 | Correction to use of masks and filters | Huawei, Hisilicon | Revised |
S2‑142224 | Proposed Service Capability Exposure Framework Model | Huawei | Approved |
S2‑142225 | Key issue on group message delivery selection | Qualcomm Incorporated | Approved |
S2‑142226 | WID for enhanced CSFB | China Unicom, Qualcomm Incorporated, Deutsche Telekom, ZTE, Huawei, HiSilicon, CATR, CATT, Mediatek, III, Broadcom Corporation, Telefonica | Revised |
S2‑142227 | Rel13 WID on IMS webRTC | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, China Mobile, AT&T, NTT DoCoMo, ZTE, Huawei, Orange | Revised |
S2‑142228 | Extended ProSe WID | Qualcomm Incorporated, Deutsche Telekom, ZTE, UK Home Office, CATT, US Department of Commerce, AT&T, HTC, General Dynamics UK Ltd, Telefonica, Motorola Mobility, KDDI, ITRI, LG Electronics, Interdigital, Intel | Approved |
S2‑142229 | Usage Monitoring Control PCC Extension | China Telecom, ZTE, Orange, KDDI, Allot communications, Huawei, China Unicom, CATT, Oracle | Approved |
S2‑142230 | Paging Policy Differentiation for Voice over LTE | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Verizon, Oracle, LG Electronics | Revised |
S2‑142231 | DRAFT Reply on Introducing the ProSe Authorized IE | SA WG2 | Revised |
S2‑142232 | Reserved for Ivano's parallel sessions | - | Withdrawn |
S2‑142233 | Reserved for Ivano's parallel sessions | - | Withdrawn |
S2‑142234 | Reserved for Ivano's parallel sessions | - | Withdrawn |
S2‑142235 | Reserved for Ivano's parallel sessions | - | Withdrawn |
S2‑142236 | Reserved for Ivano's parallel sessions | - | Withdrawn |
S2‑142237 | Reserved for Ivano's parallel sessions | - | Withdrawn |
S2‑142238 | Reserved for Ivano's parallel sessions | - | Withdrawn |
S2‑142239 | Reserved for Ivano's parallel sessions | - | Withdrawn |
S2‑142240 | Reserved for Ivano's parallel sessions | - | Withdrawn |
S2‑142241 | Reserved for Ivano's parallel sessions | - | Withdrawn |
S2‑142242 | Reserved for Ivano's parallel sessions | - | Withdrawn |
S2‑142243 | Reserved for Ivano's parallel sessions | - | Withdrawn |
S2‑142244 | Reserved for Ivano's parallel sessions | - | Withdrawn |
S2‑142245 | Reserved for Ivano's parallel sessions | - | Withdrawn |
S2‑142246 | Reserved for Ivano's parallel sessions | - | Withdrawn |
S2‑142247 | CN Assistance information for eNB parameters setting | Qualcomm, Alcatel-Lucent, NEC, Huawei, Vodafone, Orange, ZTE, InterDigital, KDDI, NTT DOCOMO, Intel | Revised |
S2‑142248 | [DRAFT] Reply LS on Core Network assisted eNodeB parameters tuning | SA WG2 | Revised |
S2‑142249 | Correction to use of masks and filters | Huawei, Hisilicon | Agreed |
S2‑142250 | Key issue for Group based policing | Huawei, Hisilicon | Approved |
S2‑142251 | [DRAFT] Reply LS on impact of PC3 transport protocol on PC3 security | SA WG2 | Revised |
S2‑142252 | Handling of invalid Proximity Request due to exceeding time window | HTC, Intel | Agreed |
S2‑142253 | Usage of Source Layer-2 ID and Destination Layer-2 ID | Intel, Alcatel-Lucent, CATT | Agreed |
S2‑142254 | Missing text on Layer-3 Protocol Data Unit Type | Intel, Alcatel-Lucent | Agreed |
S2‑142255 | Clarification on roaming subscription corresponding to specific RAT for 23.221 | China Mobile, Huawei | Agreed |
S2‑142256 | Correction of the Proximity Alert procedure | Apple Inc. | Revised |
S2‑142257 | Priority and pre-emption for GCS | Ericsson | Agreed |
S2‑142258 | Evaluation of the FPI solution | Huawei, Hisilicon, Telecom Italia | Revised |
S2‑142259 | Introduction of Dual Connectivity Operation | Huawei, Hisilicon, Ericsson, Alcatel-Lucent | Agreed |
S2‑142260 | Traffic steering for RAN-based WLAN interworking solution | Ericsson, NSN, Nokia, Samsung, Qualcomm Incorporated, Broadcom Corporation, Huawei, Hisilicon, Intel | Agreed |
S2‑142261 | PCC Rules sharing resources | Ericsson | Revised |
S2‑142262 | CN Assistance information for eNB parameters setting | Qualcomm, Alcatel-Lucent, NEC, Huawei, Vodafone, Orange, ZTE, InterDigital, KDDI, NTT DOCOMO, Intel | Agreed |
S2‑142263 | Reply LS on Core Network assisted eNodeB parameters tuning | SA WG2 | Approved |
S2‑142264 | Reply LS on default APN operation | SA WG2 | Approved |
S2‑142265 | WID for enhanced CSFB | China Unicom, Qualcomm Incorporated, Deutsche Telekom, ZTE, Huawei, HiSilicon, CATR, CATT, Mediatek, III, Broadcom Corporation, Telefonica | Approved |
S2‑142266 | Rel13 WID on IMS webRTC | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, China Mobile, AT&T, NTT DoCoMo, ZTE, Huawei, Orange | Approved |
S2‑142267 | Paging Policy Differentiation for Voice over LTE | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Verizon, Oracle, LG Electronics | Approved |
S2‑142268 | Evaluation of the FPI solution | Huawei, Hisilicon, Telecom Italia | Approved |
S2‑142269 | PCC Rules sharing resources | Ericsson | Agreed |
S2‑142270 | Interaction between the ProSe and EPC procedures | Huawei, Hisllicon, Ericsson, HTC, CATT | Revised |
S2‑142271 | Clarifications on the use of wild-carded ProSe App. IDs/ProSe App. Codes | Qualcomm Incorporated | Agreed |
S2‑142272 | Correction of the Proximity Alert procedure | Apple Inc. | Revised |
S2‑142273 | Interaction between the ProSe and EPC procedures | Huawei, Hisllicon, Ericsson, HTC, CATT | Agreed |
S2‑142274 | Correction of the Proximity Alert procedure | Apple Inc. | Agreed |
S2‑142275 | Reply LS on impact of PC3 transport protocol on PC3 security | SA WG2 | Approved |
S2‑142276 | Revised NBIFOM service and architectural requirements in TR 23.861 | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, LG Electronics , Qualcomm Corporation, ZTE, Broadcom Qualcomm Corporation, Samsung | Approved |
S2‑142277 | Reply LS on Introducing the ProSe Authorized IE | SA WG2 | Approved |
page generated from database: 2024-07-20 12:15:34