3GPP TDocs (written contributions) at meeting
Meeting: S2-93 - 2012-10-08 to 2012-10-12, Sofia
meeting id: S2-93 (click id for more info on this meeting)Click on the Tdoc to open its file.
| TDoc | Title | Source | Remarks |
|---|---|---|---|
| S2‑123432 | Draft Agenda for SA WG2#93 | SA WG2 Chairman | Approved |
| S2‑123433 | Draft Report of SA WG2 meeting #92 | SA WG2 Secretary | Approved |
| S2‑123434 | SA WG2 chairman's report on TSG SA#57 | SA WG2 Chairman | Noted |
| S2‑123435 | LS from 3GPP2 TSG-A: Improvements to S102 Information Element | 3GPP2 TSG A (A-04_TSG-A LS to CT4 on GCSNA Status Improvements) | Noted |
| S2‑123436 | LS from GSMA: LS to OMA on Push Server Requirements | GSMA (ANEFF Doc 03_004) | Noted |
| S2‑123437 | LS from BBF: Answer to 3GPP liaison S2-123383 (bbf2012.769.00) on P4C/P4C-F Questions for fixed device support | BBF (bbf2012.1075.02) | Noted |
| S2‑123438 | LS from ETSI TC M2M: Clarification on External Identifier | ETSI TC M2M (M2M(12)21_115r1) | Postponed to meeting #94 |
| S2‑123439 | LS from ETSI TC M2M: Triggering functionality and relation to CT WG3 working assumption | ETSI TC M2M (M2M(12)21_116r1) | Noted |
| S2‑123440 | LS from Wi-Fi Alliance: Reply to 3GPP LS on approval of WID WLAN Network Selection for 3GPP Terminals | Wi-Fi Alliance (LS 3GPP 090412) | Noted |
| S2‑123441 | LS from CT WG1: LS on exception of NAS level congestion control in UTRAN/GERAN | CT WG1 (C1-122521) | Noted. Rel-11 CR approved |
| S2‑123442 | LS from CT WG4: LS on Modified H(e)NB local IP address after NAT remapping | CT WG4 (C4-121275) | Postponed to meeting #94 |
| S2‑123443 | LS from BBF: Answer to 3GPP liaison SP-120412 (bbf2012.742.00) on 3GPP P4C work structuring in Release 12 | BBF (SP-120626/bbf2012.1072.01) | Noted |
| S2‑123444 | LS from CT WG1: Reply LS on handover to a CSG cell with emergency call | CT WG1 (C1-123055) | Noted |
| S2‑123445 | LS from CT WG1: Reply LS on IMS node blocking the identity of originating party | CT WG1 (C1-123330) | Noted |
| S2‑123446 | LS from CT WG1: Reply to LS on Notification of IMS Information for CS to PS SRVCC | CT WG1 (C1-123376) | Noted |
| S2‑123447 | LS from CT WG1: Reply LS to LS (C1-122576/TSGWIF_111) on Publication of GSMAs Recommendations for Minimal Wi-Fi Capabilities of Terminals v1 | CT WG1 (C1-123401) | Noted |
| S2‑123448 | LS from CT WG1: LS on GSMA Application Network Efficiency Task Force 'whitepaper and actions' | CT WG1 (C1-123409) | Noted |
| S2‑123449 | LS from CT WG1: Reply LS on PWS key distribution | CT WG1 (C1-123453) | Noted |
| S2‑123450 | LS from CT WG1: Reply LS on border control concepts for VINE | CT WG1 (C1-123454) | Response in S2-124157 |
| S2‑123451 | LS from CT WG3: LS on the redirection functionality of SAPP | CT WG3 (C3-121581) | Response in S2-124158 |
| S2‑123452 | LS from CT WG3: LS on Charging issue regarding PCC and ADC Rules | CT WG3 (C3-121582) | Response in S2-124110 |
| S2‑123453 | LS from CT WG3: LS on PCC support for rSRVCC | CT WG3 (C3-121584) | Response in S2-124168 |
| S2‑123454 | LS from CT WG3: LS on QoS parameters that can be upgraded and downgraded | CT WG3 (C3-121668) | Response in S2-124143 |
| S2‑123455 | LS from CT WG3: Reply LS on Questions regarding BBAI procedures | CT WG3 (C3-121735) | Postponed to meeting #94 |
| S2‑123456 | LS from CT WG3: Reply LS on TFT usage for the primary PDP context when access to the PGW | CT WG3 (C3-121755) | Postponed to meeting #94 |
| S2‑123457 | LS from CT WG4: LS on Emergency registration clarification | CT WG4 (C4-121670) | Response in S2-123915 |
| S2‑123458 | LS from CT WG4: Reply LS on SIRIG | CT WG4 (C4-121774) | Response in S2-124107 |
| S2‑123459 | LS from CT WG4: Reply LS on DIAMETER-based Lg (SGSN - GMLC) interface | CT WG4 (C4-121788) | Response in S2-124186 |
| S2‑123460 | LS from CT WG4, CT WG1: LS on Stage 2 solution for Registration of MME for SMS in MME | CT WG4, CT WG1 (C4-121803) | Noted |
| S2‑123461 | LS from CT WG4: Reply LS on Inter-RAT handover, Inter-RAT Release with Redirection between an E-UTRAN and a UTRAN | CT WG4 (C4-121806) | Postponed to meeting #94 |
| S2‑123462 | LS from GERAN WG2: Reply LS on Capability Indicator for SRVCC from UTRAN/GERAN to E-UTRAN/HSPA | GERAN WG2 (GP-121163) | Response in S2-124139 |
| S2‑123463 | LS from GERAN WG2: Reply LS on contents of Handover Required message for rSRVCC | GERAN WG2 (GP-121164) | Noted |
| S2‑123464 | LS from GERAN WG2: Reply LS on PWS key distribution | GERAN WG2 (GP-121170) | Noted |
| S2‑123465 | LS from GERAN WG2: LS on reporting the UE E-UTRAN Capabilities for rSRVCC from GERAN to E-UTRAN | GERAN WG2 (GP-121171) | Noted |
| S2‑123466 | LS from TSG GERAN: Reply LS on CN Stage 3 for Full Support of Multi-Operator Core Network by GERAN | TSG GERAN (GP-121180) | Noted |
| S2‑123467 | LS from TSG GERAN: Reply LS on Notification of IMS Information for CS to PS SRVCC | TSG GERAN (GP-121181) | Noted |
| S2‑123468 | LS from TSG GERAN: LS on SIRIG | TSG GERAN (GP-121182) | Noted |
| S2‑123469 | LS from RAN WG2: Reply LS on Contents of Handover Required message for rSRVCC | RAN WG2 (R2-124194) | Noted |
| S2‑123470 | LS from RAN WG2: Reply LS on CS AMR type change during relocation | RAN WG2 (R2-124199) | Response in S2-124177 |
| S2‑123471 | LS from RAN WG2: LS on Access control for UEs in RRC CONNECTED mode | RAN WG2 (R2-124296) | Postponed to meeting #94 |
| S2‑123472 | LS from RAN WG2: LS on GSMA Application Network Efficiency Task Force 'whitepaper and actions' | RAN WG2 (R2-124349) | Noted |
| S2‑123473 | LS from RAN WG2: Reply LS to S5-121295 = R2-122096 and S2-121921 = R2-122014 on MDT positioning | RAN WG2 (R2-124360) | Noted |
| S2‑123474 | LS from RAN WG3: LS response on contents of Handover Required message for rSRVCC | RAN WG3 (R3-121963) | Response in S2-124044 |
| S2‑123475 | LS from RAN WG3: LS response on PWS key distribution | RAN WG3 (R3-121966) | Noted |
| S2‑123476 | LS from RAN WG3: LS on References for EAB | RAN WG3 (R3-121995) | Postponed to meeting #94 |
| S2‑123477 | LS from RAN WG3: LS response on IMS information Notification for CS to PS SRVCC | RAN WG3 (R3-122010) | Noted |
| S2‑123478 | LS from RAN WG3: LS on UE Radio Capability Match Indicator for Voice Continuity | RAN WG3 (R3-122013) | Postponed to meeting #94 |
| S2‑123479 | LS from TSG RAN: LS on GSMA Application Network Efficiency Task Force 'whitepaper and actions' | TSG RAN (RP-121454) | Noted |
| S2‑123480 | LS from SA WG1: LS on exception of NAS level congestion control in UTRAN/GERAN | SA WG1 (S1-122357) | Noted |
| S2‑123481 | LS from SA WG1: LS Response on GSMA Application Network Efficiency Task Force 'whitepaper and actions' | SA WG1 (S1-122510) | Noted |
| S2‑123482 | LS from SA WG1: LS on Clarification on group related service requirements for Machine Type Communications | SA WG1 (S1-122515) | Noted |
| S2‑123483 | LS from SA WG1: External Identifier availability | SA WG1 (S1-122524) | Postponed to meeting #94 |
| S2‑123484 | LS from SA WG1: LS on Usage Monitoring Control Enhancements | SA WG1 (S1-122526) | Postponed to meeting #94 |
| S2‑123485 | LS from SA WG3: LS on S6a security | SA WG3 (S3-120771) | Response in S2-124144 |
| S2‑123486 | LS from SA WG3: Reply LS on border control concepts for VINE | SA WG3 (S3-120801) | Noted |
| S2‑123487 | LS from SA WG3: LS on PWS key distribution | SA WG3 (S3-120805) | Noted |
| S2‑123488 | LS from SA WG4: LS on GSMA Application Network Efficiency Task Force 'whitepaper and actions' | SA WG4 (S4-121237) | Noted |
| S2‑123489 | LS from SA WG5: LS Response to Response liaison statement to SA WG5 and 3GPP CT WG1 on VoLTE charging requirements | SA WG5 (S5-122029) | Noted |
| S2‑123490 | LS from SA WG5: Reply LS on IMS node blocking the identity of originating party | SA WG5 (S5-122030) | Noted |
| S2‑123491 | LS from TSG SA: LS to GSMA on 3GPP activities related to Application Network efficiency Task | TSG SA (SP-120655) | Noted |
| S2‑123492 | LS from TSG GERAN: Reply LS on NAS vs AS alternatives for FULL-MOCN-GERAN issues at handovers to shared GERAN and at CSFB | TSG GERAN (GP-121168) | Postponed to meeting #94 |
| S2‑123493 | LS from SA WG5: LS on GSMA Application Network Efficiency Task Force 'whitepaper and actions' | SA WG5 (S5-122172) | Noted |
| S2‑123494 | MPS considerations for Core Network Overload Control | Applied Communication Sciences, NCS, NTT DOCOMO | Revised in S2-124015 |
| S2‑123495 | LS from BBF: Answer to 3GPP liaison S2-122623 (bbf2012.691.00) on 3GPP BBAI status updates and assumptions | BBF (bbf2012.1070.02) | Postponed to meeting #94 |
| S2‑123496 | TEI12 Planning | SA WG2 Chairman | Noted |
| S2‑123497 | Best Current Practice for Work Plan Percentages | SA WG2 Chairman | Not Handled |
| S2‑123498 | Best Current Practices for Rapporteurship | SA WG2 Chairman | Not Handled |
| S2‑123499 | Best Current Practices for Assignment of Version Numbers to TRs or TSs | SA WG2 Chairman | Not Handled |
| S2‑123500 | Draft WID for Better Management of Traffic Offloading | KDDI | Revised in S2-124088 |
| S2‑123501 | Key Issue of Intelligent WLAN Network Selection Policies | AT&T, Intel, Huawei | Merged in S2-124040 |
| S2‑123502 | Editorial Cleanups of TR 23.843 | NTC, NTT DOCOMO | Approved |
| S2‑123503 | A Cleanup of the Conclusion section in 23.843 | NTC, NTT DOCOMO | Noted |
| S2‑123504 | Access network priority based on QoS | ZTE | Noted |
| S2‑123505 | Access network priority based on APN | ZTE | Noted |
| S2‑123506 | Hotspot 2.0 capability report | ZTE | Not Handled |
| S2‑123507 | Access network discovery and selection based on Operator Friendly Name | ZTE | Not Handled |
| S2‑123508 | Access network discovery and selection based on Venue Name | ZTE | Not Handled |
| S2‑123509 | Access network discovery and selection based on BSS Load | ZTE | Merged into S2-123721 |
| S2‑123510 | Relationship between ANDSF policy and OSU Server policy | ZTE | Not Handled |
| S2‑123511 | 23.402 CR1126: Detach and PDN Disconnection for NSWO in SaMOG R11 | ZTE | Noted |
| S2‑123512 | 23.402 CR1127: Clarification for the IPv4 and IPv6 PDN connections | ZTE | Noted |
| S2‑123513 | 23.402 CR1128: Clarification for the policy control of Rel-11 SaMOG_WLAN | ZTE | Noted |
| S2‑123514 | FS_ABC architecture requirements correction | Allot Communications, Tekelec | Not Handled |
| S2‑123515 | Scenarios for FS_ABC | Allot Communications | Noted |
| S2‑123516 | WITHDRAWN | Allot Communications, Tekelec | WITHDRAWN |
| S2‑123517 | Alternative solutions for application based charging only | Allot Communications, Tekelec | Revised in parallel session in S2-123971 |
| S2‑123518 | Alternative solutions for sdf based charging only | Allot Communications, Tekelec | Revised in parallel session in S2-123972 |
| S2‑123519 | Alternative solutions for sdf and application based charging required per same IP-CAN session | Allot Communications, Tekelec | Revised in parallel session in S2-123973 |
| S2‑123520 | Corrections and requirements related to the reference architecture, reference points and functional entities definition | Allot Communications | Revised in parallel session in S2-123989 |
| S2‑123521 | WITHDRAWN | Allot Communications | WITHDRAWN |
| S2‑123522 | Reply LS on DIAMETER-based Lg (SGSN - GMLC) interface | Cisco | Revised in S2-124012 |
| S2‑123523 | Proposal related to GTP-C Overload handling | Cisco | Noted |
| S2‑123524 | Transmission delay until better coverage conditions | NEC | Not Handled |
| S2‑123525 | IMS PDN connection deactivation while the UE in the idle state | Samsung | Noted |
| S2‑123526 | 23.401 CR2460: IMS PDN connection deactivation while the UE in the idle state | Samsung, KT, LG Uplus, SKT | Noted |
| S2‑123527 | 23.401 CR2461: IMS PDN connection deactivation while the UE in the idle state | Samsung, KT, LG Uplus, SKT | Noted |
| S2‑123528 | 23.401 CR2462: IMS PDN connection deactivation while the UE in the idle state | Samsung, KT, LG Uplus, SKT | Noted |
| S2‑123529 | 23.060 CR1711: Correction on NAS level congestion for priority services | Samsung | Noted |
| S2‑123530 | 23.060 CR1712: Correction on NAS level congestion for priority services | Samsung | Noted |
| S2‑123531 | Avoiding MT paging loss for CSFB | Samsung | Noted |
| S2‑123532 | 23.272 CR0837: Avoiding MT paging loss for CSFB | Samsung | Noted |
| S2‑123533 | 23.272 CR0838: Avoiding MT paging loss for CSFB | Samsung | Noted |
| S2‑123534 | Reducing application heartbeats by network-based always-online. | China Mobile | Noted |
| S2‑123535 | Adding requirements of detecting and reporting failure causes of communication | China Mobile | Revised in S2-124129 |
| S2‑123536 | Select the IP interface based on the routing configuration in IPv6 | China Mobile | Revised in parallel session in S2-123946 |
| S2‑123537 | Architecture assumption and solution clarifications on WLAN Selection | China Mobile | Not Handled |
| S2‑123538 | Support hotspot 2.0 MO by ANDSF | China Mobile | Not Handled |
| S2‑123539 | Solution for policy coordination | China Mobile | Not Handled |
| S2‑123540 | Network triggered flow mobility | China Mobile | Revised in S2-124094 |
| S2‑123541 | 23.682 CR0061: Node congestion over the T4 interface | ZTE, HTC, Panasonic | Noted |
| S2‑123542 | 23.682 CR0062: Clarification on trigger message interworking with value added services for SMS | ZTE | Not Handled |
| S2‑123543 | Detect and reduce high frequent UE state transition | ZTE | Noted |
| S2‑123544 | Report MTC Monitoring Event via MTC-IWF | ZTE, LG Electronics | Merged in S2-124004 |
| S2‑123545 | Enhanced DRX Mode for UE Power Saving | ZTE | Revised in S2-124092 |
| S2‑123546 | Using Group MSISDN as Identifier for Group Charging | ZTE | Merged into S2-124046 |
| S2‑123547 | Clarifications on Group Policy Control | ZTE | Merged into S2-124003 |
| S2‑123548 | Distribute Group Trigger Message through Specific SIB | ZTE | Merged into S2-124001 |
| S2‑123549 | T5 based downlink small data transfer using RRC message | CATT | Not Handled |
| S2‑123550 | Conditions for start overload control over Tsp Interface | CATT | Not Handled |
| S2‑123551 | 23.060 CR1691R1: Correction of indication of 'SMS support' | CATT | Revised in S2-124022 |
| S2‑123552 | LS Reply to exception of NAS level congestion control in GERAN and UTRAN | CATT | Noted |
| S2‑123553 | 23.060 CR1713: Remove exception on NAS level congestion control for priority service | CATT | Noted |
| S2‑123554 | 23.060 CR1714: Remove exception on NAS level congestion control for priority service | CATT | Noted |
| S2‑123555 | Key issue of use Connection Capability during WLAN network selection | CATT | Not Handled |
| S2‑123556 | Sp reference point enhancement for fixed device and fixed access line | CATT | WITHDRAWN |
| S2‑123557 | Single IP-CAN session over Gxd for fixed access session and NSWO | CATT | Revised in parallel session in S2-123977 |
| S2‑123558 | Key issue of relationship between IP-CAN session over Gxd and fixed subscriber session and 3GPP UE | CATT | Revised in parallel session in S2-123955 |
| S2‑123559 | Multiple IP-CAN session over Gxd | CATT | Merged in S2-123984 |
| S2‑123560 | Device based detection for MTC monitoring purpose | CATT | Noted |
| S2‑123561 | H(e)NB providing LIPA and SIPTO@LN feature information to MME/SGSN | CATT | Noted |
| S2‑123562 | Scenario and solution for LIPA PDN deactivation | CATT | Not Handled |
| S2‑123563 | 23.203 CR0754R1: OCS dynamic update of list of currently available policy counters | Ericsson, ST-Ericsson, Openet | Not Handled |
| S2‑123564 | 23.203 CR0766: Correction of Redirection Functionality | Ericsson, ST-Ericsson | Revised in parallel sessions to S2-123941 |
| S2‑123565 | Indicating cell identifier in a shared GERAN network | Ericsson, ST-Ericsson | Noted |
| S2‑123566 | 23.251 CR0076: Indicating cell identifier operator in a shared GERAN network | Ericsson, ST-Ericsson | Revised in S2-123994 |
| S2‑123567 | WITHDRAWN | Ericsson, ST-Ericsson | WITHDRAWN |
| S2‑123568 | WITHDRAWN | Ericsson, ST-Ericsson | WITHDRAWN |
| S2‑123569 | Architecture for SIPTO@LN | Ericsson, ST Ericsson | Revised in S2-124061 |
| S2‑123570 | [DRAFT] LS response on ULI reporting during detach with ISR activated procedure | Ericsson, ST Ericsson | Noted |
| S2‑123571 | Additions to Diameter overload analysis related to policy | Ericsson, ST-Ericsson | Revised in S2-124016 |
| S2‑123572 | LS on Clarification on authentication and policy control procedures for 3GPP UE roaming | Ericsson | Not Handled |
| S2‑123573 | IP-CAN session in fixed broadband access | Ericsson | Revised in parallel session in S2-123956 |
| S2‑123574 | Way forward for BBAI H(e)NB IP address issue | Ericsson | Noted |
| S2‑123575 | Solution alternative for P4C BB2 | Ericsson | Revised in S2-123907 |
| S2‑123576 | Solution alternative for P4C BB6 | Ericsson | Revised in parallel session in S2-123953 |
| S2‑123577 | Corrections to description of key issue 1 | Ericsson, ST-Ericsson | Approved |
| S2‑123578 | Corrections to architectural requirements for ABC | Ericsson, ST-Ericsson | Revised in parallel session in S2-123969 |
| S2‑123579 | Key issue for multiple VPLMN | Ericsson, ST-Ericsson | Revised in S2-124059 |
| S2‑123580 | 23.402 CR1129: Clarification on IPMS over S2a | New Postcom | Approved |
| S2‑123581 | 23.402 CR1130: Corrections to HSS-initiated Subscribed QoS Modification Procedure | New Postcom | Noted |
| S2‑123582 | 23.402 CR1131: Corrections to HSS-initiated Subscribed QoS Modification Procedure | New Postcom | Noted |
| S2‑123583 | 23.402 CR1132: Corrections to HSS-initiated Subscribed QoS Modification Procedure | New Postcom | Noted |
| S2‑123584 | 23.402 CR1133: Corrections to HSS-initiated Subscribed QoS Modification Procedure | New Postcom | Noted |
| S2‑123585 | 23.682 CR0063: Addition of S6c in architectural reference model | New Postcom | Not Handled |
| S2‑123586 | Correction to BB1 reference architecture | New Postcom | Revised in parallel session in S2-124096 |
| S2‑123587 | BBAI H(e)NB Local IP Transport Resolution | ZTE | Noted |
| S2‑123588 | BBAI Addressing RAN WG3's concern for TS 23.139 solution for transporting H(e)NB's Local IP address via IKEv2 Configuration Payload | ZTE | Noted |
| S2‑123589 | BBAI VPLMN Selection in BBAI | ZTE | Not Handled |
| S2‑123590 | Reply LS on VPLMN Selection in BBAI | ZTE | Not Handled |
| S2‑123591 | [DRAFT] Reply LS on QoS parameters that can be upgraded and downgraded | ZTE | Revised in S2-123909 |
| S2‑123592 | 23.203 CR0767: PCC Clarification of the QoS parameters that can be upgraded and downgraded(Rel-7) | ZTE | Not Handled |
| S2‑123593 | 23.203 CR0768: PCC Clarification of the QoS parameters that can be upgraded and downgraded(Rel-8) | ZTE | Not Handled |
| S2‑123594 | 23.203 CR0769: PCC Clarification of the QoS parameters that can be upgraded and downgraded(Rel-9) | ZTE | Not Handled |
| S2‑123595 | 23.203 CR0770: PCC Clarification of the QoS parameters that can be upgraded and downgraded(Rel-10) | ZTE | Not Handled |
| S2‑123596 | 23.203 CR0771: PCC Clarification of the QoS parameters that can be upgraded and downgraded(Rel-11) | ZTE | Not Handled |
| S2‑123597 | NB_IFOM 23.861 skeleton update.v1 | ZTE | Approved |
| S2‑123598 | NB-IFOM Solution | ZTE | Revised in S2-124095 |
| S2‑123599 | P4C-F: IP-CAN Session Establishment procedures | ZTE | Merged in S2-123984 |
| S2‑123600 | P4C-F: IP-CAN Session Modification procedures | ZTE | Merged in S2-123984 |
| S2‑123601 | P4C-F: IP-CAN Session Termination procedures | ZTE | Merged in S2-123984 |
| S2‑123602 | P4C-F: key issues | ZTE | WITHDRAWN |
| S2‑123603 | P4C-F: Reference architecture correction | ZTE | Revised in parallel session in S2-124097 |
| S2‑123604 | Discussions on P4C-TC&TI Policy and QoS Control design options for SaMOG | ZTE | Not Handled |
| S2‑123605 | P4C-TI attachment procedure-option 1 - PCRF initiated GCS over S9a | ZTE | Revised in parallel session in S2-123981 |
| S2‑123606 | P4C-TI Attachment procedure-option 2 - BPCF initiated GCS over S9a | ZTE | Revised in parallel session in S2-123980 |
| S2‑123607 | P4C-TI additional Gateway control session operation over S9a | ZTE | Revised in parallel session in S2-123982 |
| S2‑123608 | P4C-TI Policy and QoS Control design for Alternative 1(S2a-GTP) for SaMOG | ZTE | Merged into S2-123978 |
| S2‑123609 | P4C-TI Reference architecture (alt3) correction | ZTE | Revised in parallel session in S2-123979 |
| S2‑123610 | P4C-TI S9a function description | ZTE | Noted |
| S2‑123611 | P4C-TC attachment procedure-option 1 - PCRF-initiated GCS over Gxd | ZTE | Not Handled |
| S2‑123612 | P4C-TC attachment procedure-option 2 - IP Edge Initiated GCS over Gxd | ZTE | Not Handled |
| S2‑123613 | P4C-TC additional Gateway control session operation over Gxd | ZTE | Not Handled |
| S2‑123614 | P4C-TC Gxd function description | ZTE | Not Handled |
| S2‑123615 | [DRAFT] Response LS on Questions regarding BBAI procedures | Orange | Not Handled |
| S2‑123616 | BusTI WI not limited to peering based business trunking | Alcatel-Lucent | Revised in IMS Sessions to S2-123926 |
| S2‑123617 | Business Trunking, Architecture with P-CSCF | Alcatel-Lucent | Revised in IMS Sessions to S2-123927 |
| S2‑123618 | 23.228 CR1018: Keep alive between UE and P-CSCF | China Mobile | Noted |
| S2‑123619 | 23.228 CR1019: Network Initiated De-registration, Signalling Connection Loss | China Mobile | WITHDRAWN |
| S2‑123620 | Stage 2 aspects of location based IMS registration control | China Mobile | Revised in IMS Sessions to S2-123924 |
| S2‑123621 | Key Issue Consideration for SDDTE | Samsung | Noted |
| S2‑123622 | Small Data Detection for SDDTE | Samsung | Not Handled |
| S2‑123623 | 23.401 CR2463: Reference correction on EAB for CN overload | Samsung | Not Handled |
| S2‑123624 | 23.060 CR1715: Reference correction on EAB for CN overload | Samsung | Not Handled |
| S2‑123625 | ULI reporting clarification | Huawei, Hisilicon | Noted |
| S2‑123626 | [Draft] LS out ULI reporting during detach with ISR activated procedure | Huawei, Hisilicon | Revised in S2-124033 |
| S2‑123627 | 23.060 CR1700R1: Restrict initiating priority service when BO timer is running for GERAN/UTRAN | Huawei, Hisilicon | Noted |
| S2‑123628 | 23.060 CR1701R1: Restrict initiating priority service when BO timer is running for GERAN/UTRAN | Huawei, Hisilicon | Noted |
| S2‑123629 | 23.401 CR2448R1: UE supporting dual priority | Huawei, Hisilicon | Revised in S2-124025 |
| S2‑123630 | 23.060 CR1702R1: MS supporting dual priority | Huawei, Hisilicon | Revised in S2-124026 |
| S2‑123631 | Network sharing impact on the CSFB | Huawei, Hisilicon | Noted |
| S2‑123632 | 23.272 CR0810R2: Network sharing impact on the CSFB | Huawei, Hisilicon | Revised in S2-124011 |
| S2‑123633 | 23.251 CR0067R2: Network sharing impact on the CSFB | Huawei, Hisilicon | Revised in S2-124128 |
| S2‑123634 | 23.203 CR0758R1: Correction on ADC functionality description | Huawei, Hisilicon, Allot Communications | Revised in parallel sessions to S2-123945 |
| S2‑123635 | Draft Reply LS on the redirection functionality of SAPP | Huawei, Hisilicon | Revised in parallel sessions to S2-123942 |
| S2‑123636 | 23.060 CR1716: Roaming support in SIRIG | Huawei, Hisilicon | Approved |
| S2‑123637 | [Draft] LS out Reply LS on SIRIG | Huawei, Hisilicon | Revised in parallel sessions to S2-123940 |
| S2‑123638 | Draft Reply LS on PCC support for rSRVCC | Huawei, Hisilicon | Revised in S2-124038 |
| S2‑123639 | 23.228 CR1020: Correction of reference point between MSC Server and ATCF to the RAVEL | Huawei, Hisilicon | Revised in S2-124039 |
| S2‑123640 | 23.228 CR1021: Network Provided Location Information Distributed at Registration Procedure | Huawei, Hisilicon | Noted |
| S2‑123641 | [Draft] LS response on Capability Indicator for SRVCC from UTRAN/GERAN to E-UTRAN/HSPA | Huawei, Hisilicon | Revised in S2-124014 |
| S2‑123642 | Taxonomy of MTC enhancements for optimising signalling no UP establishment | Huawei, Hisilicon | Revised in parallel session in S2-123997 |
| S2‑123643 | Control of Device Triggering in case of UE getting no UP establishment | Huawei, Hisilicon | Not Handled |
| S2‑123644 | Use SCS as Push Proxy to reduce heartbeat/keep-alive data of Applications | Huawei, Hisilicon | Revised in S2-124037 |
| S2‑123645 | Event Reporting by the UE | Huawei, Hisilicon | Not Handled |
| S2‑123646 | A reference architecture for monitoring | Huawei, Hisilicon | Revised in S2-124131 |
| S2‑123647 | Power Saving State for Devices | Huawei, Hisilicon, Orange | Revised in S2-124032 |
| S2‑123648 | Enforcing group level policy | Huawei, Hisilicon | Not Handled |
| S2‑123649 | Key issue update and Solution for group charging | Huawei, Hisilicon | Revised in S2-124046 |
| S2‑123650 | Solution for group based messaging with MBMS | Huawei, Hisilicon | Merged into S2-124000 |
| S2‑123651 | BB1 Policy and Charging for NSWO traffic | Huawei, Hisilicon | Not Handled |
| S2‑123652 | BB1: Fixed subscriber session definition | Huawei, Hisilicon | Revised in S2-123903 |
| S2‑123653 | BB1: NSWO considerations | Huawei, Hisilicon | Revised in parallel session in S2-123966 |
| S2‑123654 | BB1: Fixed subscriber session Procedures | Huawei, Allot Communications, Hisilicon | Revised in parallel session in S2-123951 |
| S2‑123655 | BB1: Static and dynamic fixed session | Huawei, Hisilicon | Noted |
| S2‑123656 | BB2 architecture alternatives for trust WLAN QoS interworking | Huawei, Hisilicon | Revised in S2-123907 |
| S2‑123657 | BB6 General architecture assumption | Huawei, Hisilicon | Not Handled |
| S2‑123658 | New OPIIS scenario for consideration | Huawei, Hisilicon | Noted |
| S2‑123659 | Optimized ISRP for OPIIS without addition of Filter Rules for inter-APN routing | Huawei, Hisilicon | Revised in parallel session in S2-123947 |
| S2‑123660 | WLAN_NS architecture reference model | Huawei, Hisilicon | Not Handled |
| S2‑123661 | New parameter for WLAN selection | Huawei, Hisilicon | Not Handled |
| S2‑123662 | 3GPP centric policy and information provision | Huawei, Hisilicon | Not Handled |
| S2‑123663 | UE 802.11u and HS2.0 capability based policy and information | Huawei, Hisilicon | Not Handled |
| S2‑123664 | Diameter Server Agent | Huawei, Hisilicon | Revised in S2-124018 |
| S2‑123665 | TR 23.843 0.5.1 | Huawei, Hisilicon | Noted |
| S2‑123666 | WORM architecture assumption | Huawei, Hisilicon | Revised in parallel session in S2-123974 |
| S2‑123667 | Solution of IP flow mobility for PMIPv6 based S2b | Huawei, Hisilicon | Not Handled |
| S2‑123668 | Solution of IP flow mobility for GTP based S2b | Huawei, Hisilicon | Not Handled |
| S2‑123669 | 23.237 CR0437: Bring back normal SRVCC procedure 6.3.2.1.4 which was mis-removed | Huawei, Hisilicon, NEC | Revised in parallel sessions to S2-123917 |
| S2‑123670 | Discussion Paper for Service Domain selection for mobile terminated calls from IMS | Huawei, Hisilicon | Noted |
| S2‑123671 | 23.221 CR0138: Service Domain selection for mobile terminated calls from IMS | Huawei, Hisilicon | Not Handled |
| S2‑123672 | BusTI Alternative under eIBCF architecture-Origination | Huawei, Hisilicon | Noted |
| S2‑123673 | BusTI Alternative under eIBCF architecture-Termination | Huawei, Hisilicon | Noted |
| S2‑123674 | Network name display & Charging for CSFB with multiple PLMNs | Huawei, Hisilicon | Noted |
| S2‑123675 | 23.216 CR0306: Correction on the relation between the MSC Server enhancements for rSRVCC and ICS | Orange | WITHDRAWN |
| S2‑123676 | 23.002 CR0255: Clarifying that MSC Server assisted mid-call feature does not imply I2 interface | Orange | Revised in IMS Sessions to S2-123931 |
| S2‑123677 | 23.002 CR0256: Clarifying that MSC Server assisted mid-call feature does not imply I2 interface | Orange | Revised in IMS Sessions to S2-123932 |
| S2‑123678 | 23.237 CR0438: Correction of the requirements for I2 interface and SRVCC corrections | Orange | Revised in IMS Sessions to S2-123934 |
| S2‑123679 | 23.237 CR0439: Correction of the requirements for I2 interface and SRVCC corrections | Orange | Revised in IMS Sessions to S2-123935 |
| S2‑123680 | 23.228 CR1022: Correction of Proactive transcoding support to preserve voice quality | Orange | Revised in IMS Sessions to S2-123929 |
| S2‑123681 | Additional requirements for robustness and scalability | Orange | Revised in IMS Sessions to S2-123925 |
| S2‑123682 | Reasons for introducing the support of PCP in 3GPP | Orange, KT corp, China Mobile, Cisco, Movik Networks, Juniper Networks, ZTE, Nokia, Benu Networks, Alcatel-Lucent, China Telecom | Noted |
| S2‑123683 | Providing control to UE for inbound/outbound connections with PCP (Port Control Protocol) | Orange, KT corp, China Mobile, Cisco, Movik Networks, Juniper Networks, ZTE, Nokia, Benu Networks, Alcatel-Lucent, China Telecom | Revised in S2-123938 |
| S2‑123684 | Preview of changes to TS 23.002 for PCP | Orange | Not Handled |
| S2‑123685 | Preview of changes to TS 23.060 for PCP | Orange | Not Handled |
| S2‑123686 | Preview of changes to TS 23.401 for PCP | Orange | Not Handled |
| S2‑123687 | Preview of changes to TS 23.228 for PCP | Orange | Not Handled |
| S2‑123688 | LCS session continuation for EPS after S1 connection release | Qualcomm Inc | Noted. Problem acknowledged |
| S2‑123689 | 23.271 CR0393: Continuation of LCS Session in EPS after S1 Connection Release | Qualcomm Incorporated | Not Handled |
| S2‑123690 | 23.271 CR0394: Continuation of LCS Session in EPS after S1 Connection Release | Qualcomm Incorporated | Not Handled |
| S2‑123691 | 23.271 CR0395: Continuation of LCS Session in EPS after S1 Connection Release | Qualcomm Incorporated | Not Handled |
| S2‑123692 | 23.203 CR0772: Time Usage notification and reporting to PCRF | China Telecom, Tekelec | Not Handled |
| S2‑123693 | Clean-up of remaining open issues in Solution 2 | LG Electronics | Revised in parallel session in S2-123948 |
| S2‑123694 | Clean-up of Editor's notes related to non-seamless WLAN offloading issue | LG Electronics | Approved |
| S2‑123695 | Analysis and conclusions of OPIIS | LG Electronics | Revised in parallel session in S2-123950 |
| S2‑123696 | Charging for fixed device in BB1 | CATT | Noted |
| S2‑123697 | Proposed solution for L-GW selection and connection (re)establishment trigger | ZTE | Not Handled |
| S2‑123698 | A new option of discovery of the LIPA mobility area | ZTE | Not Handled |
| S2‑123699 | [DRAFT] LS on Charging issue regarding PCC and ADC Rules | Allot Communications | Revised in parallel sessions to S2-123944 |
| S2‑123700 | 23.203 CR0773: Clarification on Charging issue regarding PCC and ADC Rules | Allot Communications | Noted |
| S2‑123701 | Solution of delivering group based message over T4/T5 | HTC | Revised in parallel session in S2-124001 |
| S2‑123702 | Internal group identifiers for group based message delivery over T4/T5 | HTC | Not Handled |
| S2‑123703 | Requirement for Monitoring Service Provisioning | HTC | Revised in S2-124130 |
| S2‑123704 | 23.682 CR0064: Clarification on device triggering procedure when routing information is absent | HTC | Not Handled |
| S2‑123705 | Optimization for transmission of infrequent or frequent small data | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | Not Handled |
| S2‑123706 | Optimization for UP data transmissions | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | Not Handled |
| S2‑123707 | Group Triggering and Messaging Considerations | Alcatel-Lucent Shanghai Bell, Alcatel-Lucent | Not Handled |
| S2‑123708 | Distribution of MTC Group Messages | Alcatel-Lucent Shanghai Bell, Alcatel-Lucent | Merged into S2-123999 |
| S2‑123709 | Corrections on Home-routed Roaming Architecture Figure | Intel, Verizon, Cisco | Revised in parallel session in S2-123959 |
| S2‑123710 | Non-IMS AS Discovery Procedure for Architecture #1 | Intel, Verizon, Cisco | Revised in parallel session in S2-123957 |
| S2‑123711 | Non-IMS Online Charging Procedures for Architecture #1 | Intel, Verizon, Cisco | Revised in parallel session in S2-123958 |
| S2‑123712 | Non-IMS Re-authentication Procedure for Architecture #1 | Intel, Verizon, Cisco | Revised in parallel session in S2-123960 |
| S2‑123713 | Policy Interaction Procedures for MNO Owned and Collaborative Cases for Architecture #1 | Intel, Verizon, Cisco | Revised in parallel session in S2-123961 |
| S2‑123714 | Non-IMS Procedures for Home-routed Roaming Case for Architecture #1 | Intel, Verizon, Cisco | Approved |
| S2‑123715 | Attributes of Mh Interface Messages | Intel, Verizon, Cisco | Revised in parallel session in S2-123962 |
| S2‑123716 | Interface Enhancements for Architecture #1 | Intel, Verizon, Cisco | Not Handled |
| S2‑123717 | Impacts on Existing Nodes or Functionality for Architecture #1 | Intel, Verizon, Cisco | Not Handled |
| S2‑123718 | Conclusion for Release 12 | Intel, Verizon, Cisco | Revised in parallel session in S2-123963 |
| S2‑123719 | Solution for Key Issue - Efficient Small Data Transmission with Null User plane | NTT DOCOMO, NEC | Not Handled |
| S2‑123720 | Architectural Assumptions | Intel, AT&T | Not Handled |
| S2‑123721 | Key Issue: WLAN Load Info | Intel, AT&T, Orange | Revised in S2-124060 |
| S2‑123722 | Key Issue: Venue, Access Type Info | Intel, AT&T, Orange, Alcatel-Lucent | Not Handled |
| S2‑123723 | Architectural requirements and solution for group based policy control | LG Electronics | Not Handled |
| S2‑123724 | LIPA PDN connection activation | Samsung | Revised in S2-124066 |
| S2‑123725 | MTC group based messaging solution | Samsung | Merged into S2-124000 |
| S2‑123726 | Network Optimization for Infrequent Communication | Ericsson, ST-Ericsson | Not Handled |
| S2‑123727 | Attach/detach using existing procedures | Ericsson, ST-Ericsson | Not Handled |
| S2‑123728 | Extended Paging Cycles | Nokia Siemens Networks, Nokia, Ericsson, ST-Ericsson, | Revised in S2-124029 |
| S2‑123729 | UEPCOP Key issue cleanup | Ericsson, ST-Ericsson | Revised in parallel session in S2-123998 |
| S2‑123730 | 23.272 CR0839: Registration of MME for SMS | Ericsson, ST-Ericsson, Alcatel-Lucent, Hitachi | Revised in S2-124021 |
| S2‑123731 | Device Triggering identification | Ericsson, ST-Ericsson | Noted |
| S2‑123732 | Group Policing Solution for MTC groups | Ericsson, ST-Ericsson | Not Handled |
| S2‑123733 | Architecture Requirements updates | Ericsson, ST-Ericsson | Partially Merged into S2-124003 |
| S2‑123734 | First attach event monitoring and notification to SCS | Ericsson, ST-Ericsson | Revised in S2-124132 |
| S2‑123735 | Extend UE involved Relocation Case | Huawei, Hisilicon | Not Handled |
| S2‑123736 | How to handle and adopt changed SMS in MME functionality | Huawei, Hisilicon | Noted |
| S2‑123737 | Idle state mobility for Local PDN connection | Huawei, Hisilicon | Not Handled |
| S2‑123738 | Connected state mobility for local PDN connection | Huawei, Hisilicon | Not Handled |
| S2‑123739 | Local PDN connection QoS management | Huawei, Hisilicon,CATT | Revised in S2-124065 |
| S2‑123740 | 23.292 CR0191: Add a note for managing communication service settings data | Huawei, Hisilicon | Not Handled |
| S2‑123741 | Group based policy control requirements and assumptions | KPN | Revised in parallel session in S2-124003 |
| S2‑123742 | Background for group based charging requirements | KPN | Not Handled |
| S2‑123743 | Solution for group based messaging using cell broadcast | KPN | Revised in parallel session in S2-123999 |
| S2‑123744 | Charging requirements for group based messaging | KPN | Not Handled |
| S2‑123745 | WITHDRAWN | KPN | WITHDRAWN |
| S2‑123746 | Solutions for keeping UE in detached state | Panasonic | Not Handled |
| S2‑123747 | Solutions for monitoring action 'reduce services' | Panasonic | Not Handled |
| S2‑123748 | Solutions for monitoring action 'restrict access' | Panasonic | Not Handled |
| S2‑123749 | PCC handling for bearers without TFT | Ericsson, ST Ericsson | Noted |
| S2‑123750 | [DRAFT] Reply LS on TFT usage for the primary PDP context when access to the PGW | Ericsson, ST Ericsson | Noted |
| S2‑123751 | rSRVCC information exchange between MSC and UE | Ericsson, ST-Ericsson, Huawei, Hisilicon, ZTE | Noted |
| S2‑123752 | BUSTI reuse of existing functions v2 | Ericsson, ST-Ericsson | Approved |
| S2‑123753 | 23.237 CR0440: Dynamic STN for DRVCC | Ericsson, ST-Ericsson | Approved |
| S2‑123754 | DRVCC for incoming calls in alerting state | Ericsson, ST-Ericsson | Noted |
| S2‑123755 | 23.237 CR0441: Incoming alerting for DRVCC | Ericsson, ST-Ericsson | Revised in IMS Sessions to S2-123922 |
| S2‑123756 | 23.216 CR0307: SRVCC clarification of Failure after responding to PS to CS HO request | Ericsson, ST-Ericsson | Revised in S2-123990 |
| S2‑123757 | 23.216 CR0308: SRVCC clarification of Failure after responding to PS to CS HO request | Ericsson, ST-Ericsson | Revised in S2-123991 |
| S2‑123758 | UE Power Saving in Passive State | NEC | Not Handled |
| S2‑123759 | Key Issue on associating an MTC device to a single Group ID across the network | NEC | Not Handled |
| S2‑123760 | Use of ULI Age | Ericsson, ST Ericsson | Not Handled |
| S2‑123761 | 23.401 CR2464: Clarification on SDU Error Ratio value when mapping EPS QCI=4 to Release 99 QoS parameters | Nokia Siemens Networks | Revised in parallel session in S2-124104 |
| S2‑123762 | 23.401 CR2465: Clarification on SDU Error Ratio value when mapping EPS QCI=4 to Release 99 QoS parameters | Nokia Siemens Networks | Revised in parallel session in S2-124105 |
| S2‑123763 | 23.401 CR2466: Clarification on SDU Error Ratio value when mapping EPS QCI=4 to Release 99 QoS parameters | Nokia Siemens Networks | Revised in parallel session in S2-124106 |
| S2‑123764 | 23.167 CR0218: Defining S-CSCF procedures for registration and emergency registration relationships | Nokia Siemens Networks | Revised in IMS Sessions to S2-123912 |
| S2‑123765 | 23.167 CR0219: Defining S-CSCF procedures for registration and emergency registration relationships | Nokia Siemens Networks | Revised in IMS Sessions to S2-123913 |
| S2‑123766 | 23.167 CR0220: Defining S-CSCF procedures for registration and emergency registration relationships | Nokia Siemens Networks | Revised in IMS Sessions to S2-123914 |
| S2‑123767 | MTC Device Triggering Issues | Motorola Mobility | Noted |
| S2‑123768 | 23.682 CR0055R1: Device Triggering corrections | Motorola Mobility | Not Handled |
| S2‑123769 | Key Issue: Supporting Different MTC Enablement Frameworks | Motorola Mobility | Noted |
| S2‑123770 | Solution for Canceling Previously Submitted Trigger Messages | Motorola Mobility | Not Handled |
| S2‑123771 | WITHDRAWN | Motorola Mobility | WITHDRAWN |
| S2‑123772 | Key Issue: Applicability of I-WLAN PLMN Selection | Motorola Mobility | Revised in S2-124030 |
| S2‑123773 | Key Issue: NAI Selection | Motorola Mobility | Not Handled |
| S2‑123774 | Solution: Combining I-WLAN and ANDSF Selection Procedures | Motorola Mobility | Not Handled |
| S2‑123775 | Amendments to Solution 1: Inter-APN Routing Policies | Motorola Mobility | Noted |
| S2‑123776 | CN overload due to flood of User Location Information (ULI) reporting | Alcatel-Lucent, Allot Communications | Revised in S2-124019 |
| S2‑123777 | Discussion on trusted WLAN operator identification for EPC access | Alcatel-Lucent | Noted |
| S2‑123778 | 23.402 CR1134: Trusted WLAN operator identification for EPC access | Alcatel-Lucent | Revised in parallel session in S2-124099 |
| S2‑123779 | Draft LS on Trusted WLAN operator identification | Alcatel-Lucent | WITHDRAWN |
| S2‑123780 | Indicating SIPTO/LIPA support at a Local GW | Alcatel-Lucent | Not Handled |
| S2‑123781 | Operator steering for IWLAN selection | Alcatel-Lucent, AT&T | Not Handled |
| S2‑123782 | ANDSF usage when a UE is attached to a 3GPP access | Alcatel-Lucent | Not Handled |
| S2‑123783 | WITHDRAWN | Alcatel-Lucent | WITHDRAWN |
| S2‑123784 | 23.251 CR0077: Using NRI for CS/PS Coordination in MOCN | SA WG2 | Revised in S2-124010 |
| S2‑123785 | Mobility into GERAN GWCN | TeliaSonera | Noted |
| S2‑123786 | Modifications to solution 6.17 of TR 23.888 | ITRI | Not Handled |
| S2‑123788 | On termination of CS calls when the UE moves to WLAN using rel-8 EPS mobility | Alcatel-Lucent | Noted |
| S2‑123789 | 23.402 CR1135: Correction to enable terminated CS services when UE moves to WLAN | Alcatel-Lucent | Noted |
| S2‑123790 | 23.402 CR1136: Correction to enable terminated CS services when UE moves to WLAN | Alcatel-Lucent | Noted |
| S2‑123791 | 23.402 CR1137: Correction to enable terminated CS services when UE moves to WLAN | Alcatel-Lucent | Noted |
| S2‑123792 | 23.402 CR1138: Correction to enable terminated CS services when UE moves to WLAN | Alcatel-Lucent | Noted |
| S2‑123793 | LIPA Deactivation at handover | Alcatel-Lucent | Not Handled |
| S2‑123794 | Solution for Group based Charging | Juniper Networks | Merged into S2-124046 |
| S2‑123795 | Solution for Group based Policing | Juniper Networks | Not Handled |
| S2‑123796 | Link layer aggregation model for NB-IFOM | Intel | Revised in S2-124093 |
| S2‑123797 | Architecture for SIPTO@LN | Intel, Verizon, Cisco, Alcatel-Lucent, Huawei | Revised in S2-124062 |
| S2‑123798 | LIPA Deactivation in Connected State | Intel | Not Handled |
| S2‑123799 | Indication of L-GW's support for SIPTO@LN | Intel | Not Handled |
| S2‑123800 | Toward Better Management of Traffic Offload | KDDI | Noted |
| S2‑123801 | Discussion about MOSAP Non-Collaborative Case | InterDigital, ZTE | Not Handled |
| S2‑123802 | HotSpot 2.0 network selection and discovery in case of no IP connectivity or no 3GPP coverage | InterDigital | Revised in S2-124049 |
| S2‑123803 | Key issue - 3GPP UE having out-dated or no ANDSF PLMN selection policies due to no IP connectivity or no 3GPP coverage | InterDigital | Revised in S2-124050 |
| S2‑123804 | per APN SIPTO@LN mobility support | InterDigital | Revised in S2-124063 |
| S2‑123805 | per APN SIPTO@LN disconnection | InterDigital | Revised in S2-124064 |
| S2‑123806 | Use case for optimised WLAN offloading based on location area and/or time of day policies | InterDigital | Noted |
| S2‑123807 | Update of CNO TR scope clause | NTT DOCOMO, NEC, AT&T, China Mobile, NTC | Approved |
| S2‑123808 | Criteria for network to initiate per APN SIPTO@LN | InterDigital Communications, LG Electronics | Revised in S2-124067 |
| S2‑123809 | Device Trigger Service Models | Research In Motion UK Limited | Noted |
| S2‑123810 | Routing a Device Trigger to the target application | Research In Motion UK Limited | Noted |
| S2‑123811 | 23.682 CR0012R2: Trigger payload message format | Research In Motion UK Limited | Not Handled |
| S2‑123812 | Signalling overhead reduction for small data transmission over user plane (UMTS) | Qualcomm Incorporated | Not Handled |
| S2‑123813 | Signalling overhead reduction for small data transmission over user plane (LTE) | Qualcomm Incorporated | Not Handled |
| S2‑123814 | Framework for evaluation of UE power consumption optimizations | Qualcomm Incorporated | Revised in S2-124028 |
| S2‑123815 | Large data for Group Based Communication | Qualcomm Incorporated | Not Handled |
| S2‑123816 | eSRVCC before ringing (brSRVCC) | NTT DOCOMO | Noted |
| S2‑123817 | 23.237 CR0442: eSRVCC before ringing (brSRVCC) | NTT DOCOMO | Noted |
| S2‑123818 | 23.237 CR0443: eSRVCC before ringing (brSRVCC) | NTT DOCOMO | Noted |
| S2‑123819 | 23.237 CR0444: eSRVCC before ringing (brSRVCC) | NTT DOCOMO | Revised in IMS Sessions to S2-123918 |
| S2‑123820 | T5 based device triggering - Open issues | Intel, Nokia Siemens Networks, ZTE | Not Handled |
| S2‑123821 | Extending DRX based on UE Low Power Preference Indication | Intel | Revised in S2-124031 |
| S2‑123822 | Monitoring using Tsp and T5 | Intel | Merged in S2-124004 |
| S2‑123823 | Solution for Trigger recall/replace on Tsp | Intel | Not Handled |
| S2‑123824 | Solution for key issue - canceling previously submitted trigger messages | LG Electronics | Not Handled |
| S2‑123825 | Renaming key issue 2 | Research In Motion UK Limited | Approved |
| S2‑123826 | Proposed WORM scenario on CSFB | Research In Motion UK Limited | Revised in parallel session in S2-123975 |
| S2‑123827 | Informal description of current I-WLAN PLMN selection | Research In Motion UK Limited | Not Handled |
| S2‑123828 | Key Issue - Use of ANDSF ISMP/ISRP To Identify WLAN Networks for I-WLAN PLMN Selection | Research In Motion UK Limited | Revised in S2-124040 |
| S2‑123829 | Annex A (Figure A.3.3) Corrections | III | Not Handled |
| S2‑123830 | Annex A (Figure A.3.4) Corrections | III | Not Handled |
| S2‑123831 | 23.060 CR1641R3: Restriction of Inter RAT handover/release with redirection between E-UTRAN and UTRAN/GERAN | NTT DOCOMO | Not Handled |
| S2‑123832 | WITHDRAWN | NTT DOCOMO | WITHDRAWN |
| S2‑123833 | WITHDRAWN | NTT DOCOMO | WITHDRAWN |
| S2‑123834 | WITHDRAWN | NTT DOCOMO | WITHDRAWN |
| S2‑123835 | WITHDRAWN | NTT DOCOMO | WITHDRAWN |
| S2‑123836 | 23.221 CR0139: Restriction of Inter RAT handover/release with redirection between E-UTRAN and UTRAN/GERAN | NTT DOCOMO | Not Handled |
| S2‑123837 | 23.221 CR0140: Restriction of Inter RAT handover/release with redirection between E-UTRAN and UTRAN/GERAN | NTT DOCOMO | Not Handled |
| S2‑123838 | 23.221 CR0141: Restriction of Inter RAT handover/release with redirection between E-UTRAN and UTRAN/GERAN | NTT DOCOMO | Not Handled |
| S2‑123839 | 23.221 CR0142: Restriction of Inter RAT handover/release with redirection between E-UTRAN and UTRAN/GERAN | NTT DOCOMO | Not Handled |
| S2‑123840 | 23.401 CR2467: Restriction of Inter RAT handover/release with redirection between E-UTRAN and UTRAN/GERAN | NTT DOCOMO | Not Handled |
| S2‑123841 | 23.401 CR2468: Restriction of Inter RAT handover/release with redirection between E-UTRAN and UTRAN/GERAN | NTT DOCOMO | Not Handled |
| S2‑123842 | 23.401 CR2469: Restriction of Inter RAT handover/release with redirection between E-UTRAN and UTRAN/GERAN | NTT DOCOMO | Not Handled |
| S2‑123843 | 23.401 CR2470: Restriction of Inter RAT handover/release with redirection between E-UTRAN and UTRAN/GERAN | NTT DOCOMO | Not Handled |
| S2‑123844 | [DRAFT] LS on Inter RAT handover and Inter RAT Release with redirection between E-UTRAN and UTRAN | NTT DOCOMO | Noted |
| S2‑123845 | Solution for improved efficiency of User Location Information reporting | NEC | Noted |
| S2‑123846 | WITHDRAWN | Renesas Mobile Europe Ltd. | WITHDRAWN |
| S2‑123847 | Propose to use NAS as way forward for rSRVCC | Nokia Siemens Networks, Renesas Mobile Europe Ltd | Noted |
| S2‑123848 | T4 Device Trigger via IMS clarification/ Missing pieces | Nokia Siemens Networks | Not Handled |
| S2‑123849 | 23.682 CR0065: Add IP-SM-GW identifier to S6m and T4 messages | Nokia Siemens Networks, LG Electronics | Revised in S2-124023 |
| S2‑123850 | 23.204 CR0095: T4 trigger via IMS | Nokia Siemens Networks, LG Electronics | Revised in S2-124024 |
| S2‑123851 | Use cases for overload due to Location Request | Nokia Siemens Networks | Revised in S2-124020 |
| S2‑123852 | 23.251 CR0078: Incorrect definition of Anchor PLMN | Nokia Siemens Netowrks | Revised in S2-124041 |
| S2‑123853 | Background information and Considerations on the Signalling of PLMN ID when using MOCN/GWCN | Vodafone | Noted |
| S2‑123854 | HPLMN needs to be unaware of network sharing in VPLMN | Vodafone | Revised in S2-123993 |
| S2‑123855 | WITHDRAWN | Vodafone | WITHDRAWN |
| S2‑123856 | WITHDRAWN | Vodafone | WITHDRAWN |
| S2‑123857 | GWCN UTRAN and charging | Vodafone | Noted |
| S2‑123858 | 23.401 CR2471: Removal of cause code from Delete Session Request sent to PDN GW | Nokia Siemens Networks | Noted |
| S2‑123859 | 23.401 CR2472: Removal of cause code from Delete Session Request sent to PDN GW | Nokia Siemens Networks | Noted |
| S2‑123860 | 23.401 CR2473: PDN disconnection when ISR is active | Nokia Siemens Networks | Revised in S2-124034 |
| S2‑123861 | 23.401 CR2474: PDN disconnection when ISR is active | Nokia Siemens Networks | Revised in S2-124035 |
| S2‑123862 | 23.060 CR1717: PDN disconnection when ISR is active | Nokia Siemens Networks | Noted |
| S2‑123863 | 23.060 CR1718: PDN disconnection when ISR is active | Nokia Siemens Networks | Noted |
| S2‑123864 | WID for User Plane Congestion Management (UPCON) | NEC, KDDI, NTT DOCOMO | Revised in S2-123939 |
| S2‑123865 | Alternative Way-Forward for Rel-11 BBAI H(e)NB local IP address signalling | NEC | Noted |
| S2‑123866 | Off-path Policy Routing Signalling for network-based IP Flow Mobility | NEC | Noted |
| S2‑123867 | 23.060 CR1654R3: Clarification of UE behaviour that needs PS only services and NAS based SMS | LG Electronics, Ericsson, ST- Ericsson | Approved |
| S2‑123868 | [DRAFT] LS response on charging issue regarding PCC and ADC Rules | Deutsche Telekom | Noted |
| S2‑123869 | 23.203 CR0761R1: Correction of enforcement order of PCC and ADC rules for PCEF enhanced with ADC | Deutsche Telekom, Cisco | Revised in parallel sessions to S2-123943 |
| S2‑123870 | 23.060 CR1719: Correction of priority services | Nokia Siemens Networks, Nokia Corporation | Revised in S2-124126 |
| S2‑123871 | Group based policy control requirements | Nokia Siemens Networks, Nokia | Not Handled |
| S2‑123872 | Internal group identifier | Nokia Siemens Networks, Nokia | Noted |
| S2‑123873 | CBS based Group Messaging solutions | Nokia Siemens Networks, Nokia | Merged into S2-123999 |
| S2‑123874 | MBMS based Group Messaging solutions | Nokia Siemens Networks, Nokia | Merged in S2-124000 |
| S2‑123875 | WITHDRAWN | Nokia Siemens Networks, Nokia | WITHDRAWN |
| S2‑123876 | PLMN selection issues for WLANs | Nokia Siemens Networks, Nokia | Not Handled |
| S2‑123877 | Standalone TWAG | Nokia Siemens Networks | Not Handled |
| S2‑123878 | Network LAPI enforcement | Ericsson, ST-Ericsson | Not Handled |
| S2‑123879 | Notification of the IMS Information for rSRVCC | Renesas Mobile Electronics Ltd, Nokia Siemens Networks | Not Handled |
| S2‑123880 | 23.216 CR0302R1: Notification of the IMS Information | Renesas Mobile Europe Ltd, Nokia Siemens Networks | Not Handled |
| S2‑123881 | Handover of the PS bearers during rSRVCC | Renesas Mobile Electronics Ltd | Noted |
| S2‑123882 | A new Architecture alternative for BusTI (Business Trunking for IP-PBX in Static mode of operation) | ZTE | Revised in IMS Sessions to S2-123928 |
| S2‑123883 | Discussion of ACTF failure | ZTE | Noted |
| S2‑123884 | 23.237 CR0445: Add the capability to handle ATCF failure | ZTE | Revised in IMS Sessions to S2-123923 |
| S2‑123885 | 23.401 CR2475: UE capabilities in the UE Radio Capability Match Request procedure | Ericsson, ST-Ericsson | Revised in S2-123937 |
| S2‑123886 | Additions to Diameter overload analysis related to charging | Ericsson, ST-Ericsson | Revised in S2-124017 |
| S2‑123887 | Solution for Frequent Small Data with S1/S5/S8 Bearer Aggregation | NEC | Not Handled |
| S2‑123888 | Converge Policy Control and Charging Rules | Alcatel-Lucent | Not Handled |
| S2‑123889 | Fixed Device and WLAN UE NSWO Procedures | Alcatel-Lucent | Merged in S2-123983 |
| S2‑123890 | S2a 23.402 based architecture alternative for P4C-TC (BB6) | Alcatel-Lucent | Revised in parallel session in S2-123907 |
| S2‑123891 | S2a 23.402 based architecture alternative for P4C-TI (BB2) | Alcatel-Lucent | Not Handled |
| S2‑123892 | Way forward for the H(e)NB BBAI Feature | Alcatel-Lucent | Noted |
| S2‑123893 | 23.139 CR0029: Removal of the IKEv2 related requirements | Alcatel-Lucent | Not Handled |
| S2‑123894 | Multiple group message delivery mechanisms | Qualcomm Incorporated | Not Handled |
| S2‑123895 | Group Communication identifiers | Qualcomm Incorporated | Not Handled |
| S2‑123896 | Stand-alone L-GW selection/reselection | HTC | Not Handled |
| S2‑123897 | 23.237 CR0446: Correction to avoid the ATCF's STN-SR to be overwritten when a registration over I2 or non-3GPP access occurs | Orange | Revised in IMS Sessions to S2-123919 |
| S2‑123898 | 23.237 CR0447: Correction to avoid the ATCF's STN-SR to be overwritten when a registration over I2 or non-3GPP access occurs | Orange | Revised in IMS Sessions to S2-123920 |
| S2‑123899 | 23.237 CR0448: Correction to avoid the ATCF's STN-SR to be overwritten when a registration over I2 or non-3GPP access occurs | Orange | Revised in IMS Sessions to S2-123921 |
| S2‑123900 | 23.237 CR0449: Definition of the MSC Assisted Mid-call feature | Orange | Revised in IMS Sessions to S2-124068 |
| S2‑123901 | 23.237 CR0450: Definition of the MSC Assisted Mid-call feature | Orange | Revised in IMS Sessions to S2-124069 |
| S2‑123902 | WITHDRAWN | Orange | WITHDRAWN |
| S2‑123903 | BB1: Fixed subscriber session definition | Huawei, Hisilicon | Revised in parallel session in S2-123965 |
| S2‑123904 | 23.401 CR2476: Notifying UE on specific PDN disconnection while the UE is in the idle state | Alcatel-Lucent | Not Handled |
| S2‑123905 | 23.401 CR2477: Notifying UE on specific PDN disconnection while the UE is in the idle state | Alcatel-Lucent | Revised in S2-124042 |
| S2‑123906 | 23.401 CR2478: Notifying UE on specific PDN disconnection while the UE is in the idle state | Alcatel-Lucent | Revised in S2-124043 |
| S2‑123907 | Solution alternative for P4C BB2 | Alcatel-Lucent, Alcatel-Lucent-Shanghai-Bell | Revised in parallel session in S2-123952 |
| S2‑123908 | 23.272 CR0840: Clarification for enabling terminating CS services when UE moves to WLAN | Alcatel-Lucent | Noted |
| S2‑123909 | [DRAFT] Reply LS on QoS parameters that can be upgraded and downgraded | SA WG2 | Revised in S2-124143 |
| S2‑123910 | WITHDRAWN | Ericsson, ST Ericsson | WITHDRAWN |
| S2‑123911 | [DRAFT] Reply LS on CS AMR type change during relocation | SA WG2 | Revised in S2-124177 |
| S2‑123912 | 23.167 CR0218R1: Defining S-CSCF procedures for registration and emergency registration relationships | Nokia Siemens Networks | Approved |
| S2‑123913 | 23.167 CR0219R1: Defining S-CSCF procedures for registration and emergency registration relationships | Nokia Siemens Networks | Approved |
| S2‑123914 | 23.167 CR0220R1: Defining S-CSCF procedures for registration and emergency registration relationships | Nokia Siemens Networks | Approved |
| S2‑123915 | Reply LS on Emergency registration clarification | SA WG2 (IMS) | Approved |
| S2‑123916 | [DRAFT] Reply LS on border control concepts for VINE | SA WG2 (IMS) | Revised in S2-124157 |
| S2‑123917 | 23.237 CR0437R1: Bring back normal SRVCC procedure 6.3.2.1.4 which was mis-removed | Huawei, Hisilicon, NEC | Approved |
| S2‑123918 | 23.237 CR0444R1: eSRVCC before ringing (brSRVCC) | NTT DOCOMO | Revised in parallel session in S2-124070 |
| S2‑123919 | 23.237 CR0446R1: Correction to avoid the ATCF's STN-SR to be overwritten when a registration over I2 or non-3GPP access occurs | Orange | Approved |
| S2‑123920 | 23.237 CR0447R1: Correction to avoid the ATCF's STN-SR to be overwritten when a registration over I2 or non-3GPP access occurs | Orange | Revised in IMS Sessions to S2-124071 |
| S2‑123921 | 23.237 CR0448R1: Correction to avoid the ATCF's STN-SR to be overwritten when a registration over I2 or non-3GPP access occurs | Orange | Revised in IMS Sessions to S2-124072 |
| S2‑123922 | 23.237 CR0441R1: Incoming alerting for DRVCC | Ericsson, ST-Ericsson | Revised in IMS Sessions to S2-124076 |
| S2‑123923 | WITHDRAWN | ZTE | WITHDRAWN |
| S2‑123924 | Stage 2 aspects of location based IMS registration control | China Mobile | Revised in IMS Sessions to S2-124080 |
| S2‑123925 | Additional requirements for robustness and scalability | Orange | Approved |
| S2‑123926 | BusTI WI not limited to peering based business trunking | Alcatel-Lucent | Approved |
| S2‑123927 | Business Trunking, Architecture with P-CSCF | Alcatel-Lucent | Approved |
| S2‑123928 | A new Architecture alternative for BusTI (Business Trunking for IP-PBX in Static mode of operation) | ZTE | Revised in IMS Sessions to S2-124077 |
| S2‑123929 | 23.228 CR1022R1: Correction of Proactive transcoding support to preserve voice quality | Orange | Approved |
| S2‑123930 | Clarifying that MSC Server assisted mid-call feature does not imply I2 interface | Orange | Approved |
| S2‑123931 | 23.002 CR0255R1: Clarifying that MSC Server assisted mid-call feature does not imply I2 interface | Orange | Approved |
| S2‑123932 | 23.002 CR0256R1: Clarifying that MSC Server assisted mid-call feature does not imply I2 interface | Orange | Approved |
| S2‑123933 | 23.237 CR0451: Correction of the requirements for I2 interface and SRVCC corrections | Orange | Approved |
| S2‑123934 | 23.237 CR0438R1: Correction of the requirements for I2 interface and SRVCC corrections | Orange | Approved |
| S2‑123935 | 23.237 CR0439R1: Correction of the requirements for I2 interface and SRVCC corrections | Orange | Approved |
| S2‑123936 | 23.237 CR0452: Definition of the MSC Assisted Mid-call feature | Orange | Revised in IMS Sessions to S2-124073 |
| S2‑123937 | WITHDRAWN | Ericsson, ST-Ericsson | WITHDRAWN |
| S2‑123938 | Study on Providing control to UE for inbound/outbound connections with PCP (Port Control Protocol) | Orange, KT corp, China Mobile, Cisco, Movik Networks, Juniper Networks, ZTE, Nokia, Benu Networks, Alcatel-Lucent, China Telecom | Revised in S2-124191 |
| S2‑123939 | WID for User Plane Congestion Management (UPCON) | NEC, KDDI, NTT DOCOMO | Revised in S2-124145 |
| S2‑123940 | [Draft] LS out Reply LS on SIRIG | Huawei, Hisilicon | Revised in parallel session in S2-124107 |
| S2‑123941 | 23.203 CR0766R1: Correction of Redirection Functionality | Ericsson, ST-Ericsson | Revised in parallel session in S2-124108 |
| S2‑123942 | Draft Reply LS on the redirection functionality of SAPP | SA WG2 | Revised in S2-124158 |
| S2‑123943 | 23.203 CR0761R2: Correction of enforcement order of PCC and ADC rules for PCEF enhanced with ADC | Deutsche Telekom, Cisco | Revised in parallel session in S2-124109 |
| S2‑123944 | [DRAFT] LS on Charging issue regarding PCC and ADC Rules | Allot Communications | Revised in parallel session in S2-124110 |
| S2‑123945 | 23.203 CR0758R2: Correction on ADC functionality description | Huawei, Hisilicon, Allot Communications | Approved |
| S2‑123946 | Select the IP interface based on the routing configuration in IPv6 | China Mobile | Revised in parallel session in S2-124112 |
| S2‑123947 | Optimized ISRP for OPIIS without addition of Filter Rules for inter-APN routing | Huawei, Hisilicon | Noted |
| S2‑123948 | Clean-up of remaining open issues in Solution 2 | LG Electronics | Approved |
| S2‑123949 | Consolidation of Solution 1 and Solution 2 | Motorola Mobility, LG Electronics | Revised in parallel session in S2-124111 |
| S2‑123950 | Analysis and conclusions of OPIIS | LG Electronics | Noted |
| S2‑123951 | BB1: Fixed subscriber session Procedures | Huawei, Allot Communications, Hisilicon, ZTE, CATT?? | Revised in parallel session in S2-123984 |
| S2‑123952 | Solution alternative for P4C BB2 | Ericsson, Alcatel-Lucent(?), Alcatel-Lucent-Shanghai-Bell(?), Huawei(?), ZTE(?) | Revised in parallel session in S2-123978 |
| S2‑123953 | Solution alternative for P4C BB6 | Ericsson | Not Handled |
| S2‑123954 | S2a 23.402 based architecture alternative for P4C-TC (BB6) | Alcatel-Lucent | Not Handled |
| S2‑123955 | Key issue of relationship between IP-CAN session over Gxd and fixed subscriber session and 3GPP UE | CATT | Revised in parallel session in S2-123976 |
| S2‑123956 | IP-CAN session in fixed broadband access | Ericsson | Merged in parallel session in S2-123983 |
| S2‑123957 | Non-IMS AS Discovery Procedure for Architecture #1 | Intel, Verizon, Cisco | Approved |
| S2‑123958 | Non-IMS Online Charging Procedures for Architecture #1 | Intel, Verizon, Cisco | Approved |
| S2‑123959 | Corrections on Home-routed Roaming Architecture Figure | Intel, Verizon, Cisco | Revised in parallel session in S2-124100 |
| S2‑123960 | Non-IMS Re-authentication Procedure for Architecture #1 | Intel, Verizon, Cisco | Approved |
| S2‑123961 | Policy Interaction Procedures for MNO Owned and Collaborative Cases for Architecture #1 | Intel, Verizon, Cisco | Approved |
| S2‑123962 | Attributes of Mh Interface Messages | Intel, Verizon, Cisco | Revised in parallel session in S2-124101 |
| S2‑123963 | Conclusion for Release 12 | Intel, Verizon, Cisco | Revised in parallel session in S2-124102 |
| S2‑123964 | Cover Sheet for TR 23.862 for information in TSG SA | MOSAP Rapporteur (Intel) | Revised in parallel session in S2-124103 |
| S2‑123965 | BB1: Fixed subscriber session definition | Huawei, Hisilicon | WITHDRAWN |
| S2‑123966 | BB1: NSWO considerations | Huawei, Hisilicon | WITHDRAWN |
| S2‑123967 | P4C_F: Editorial revision of TR 23.869 for capturing IP-CAN key issue alternatives | - | Noted |
| S2‑123968 | FS_ABC architecture requirements correction | Allot Communications, Tekelec | Approved |
| S2‑123969 | Corrections to architectural requirements for ABC | Ericsson, ST-Ericsson | Approved |
| S2‑123970 | [DRAFT] LS on charging requirements for traffic redirection | SA WG2 | Revised in parallel session in S2-124098 |
| S2‑123971 | Alternative solutions for application based charging only | Allot Communications, Tekelec | Approved |
| S2‑123972 | Alternative solutions for sdf based charging only | Allot Communications, Tekelec | Approved |
| S2‑123973 | Alternative solutions for sdf and application based charging required per same IP-CAN session | Allot Communications, Tekelec | Approved |
| S2‑123974 | WORM architecture assumption | Huawei, Hisilicon | Approved |
| S2‑123975 | Proposed WORM scenario on CSFB | Research In Motion UK Limited | Approved |
| S2‑123976 | Key issue of relationship between IP-CAN session over Gxd and fixed subscriber session and 3GPP UE | CATT | Approved |
| S2‑123977 | Single IP-CAN session over Gxd for fixed access session and NSWO | CATT | Revised in parallel session in S2-123985 |
| S2‑123978 | Solution alternative for P4C BB2 | Ericsson, Alcatel-Lucent, Alcatel-Lucent-Shanghai-Bell, Huawei, ZTE | Approved |
| S2‑123979 | P4C-TI Reference architecture (alt3) correction | ZTE | Approved |
| S2‑123980 | P4C-TI Attachment procedure-option 2 - BPCF initiated GCS over S9a | ZTE | Revised in S2-124162 |
| S2‑123981 | P4C-TI attachment procedure-option 1 - PCRF initiated GCS over S9a | ZTE | Revised in S2-124161 |
| S2‑123982 | P4C-TI additional Gateway control session operation over S9a | ZTE | Revised in S2-124163 |
| S2‑123983 | IP-CAN session in fixed broadband access | Ericsson, Alcatel-Lucent? | Revised in parallel session in S2-123987 |
| S2‑123984 | BB1: Fixed subscriber session Procedures | Huawei, Allot Communications, Hisilicon, ZTE, CATT?? | Revised in parallel session in S2-123986 |
| S2‑123985 | Single IP-CAN session over Gxd for fixed access session and NSWO | CATT | Approved |
| S2‑123986 | BB1: Fixed subscriber session Procedures | Huawei, Allot Communications, Hisilicon, ZTE, CATT?? | Revised in parallel session in S2-123988 |
| S2‑123987 | IP-CAN session in fixed broadband access | Ericsson, Alcatel-Lucent | Revised in S2-124176 |
| S2‑123988 | BB1: Fixed subscriber session Procedures | Huawei, Allot Communications, Hisilicon, ZTE, CATT?? | Approved |
| S2‑123989 | Corrections and requirements related to the reference architecture, reference points and functional entities definition | Allot Communications | Approved |
| S2‑123990 | 23.216 CR0307R1: SRVCC clarification of Failure after responding to PS to CS HO request | Ericsson, ST-Ericsson | Approved |
| S2‑123991 | 23.216 CR0308R1: SRVCC clarification of Failure after responding to PS to CS HO request | Ericsson, ST-Ericsson | Approved |
| S2‑123992 | [DRAFT] LS response on contents of Handover Required message for rSRVCC | SA WG2 | Revised in S2-124044 |
| S2‑123993 | HPLMN needs to be unaware of network sharing in VPLMN | Vodafone | Noted |
| S2‑123994 | 23.251 CR0076R1: Indicating cell identifier operator in a shared GERAN network | Ericsson, ST-Ericsson | Noted |
| S2‑123995 | MTCe-Group preprocessing | MTCe-GROUP Rapporteur | Noted |
| S2‑123996 | [DRAFT] LS on Device Triggering Identification | SA WG2 | Revised in S2-124136 |
| S2‑123997 | Taxonomy of MTC enhancements for optimising signalling no UP establishment | Huawei, Hisilicon | Revised in S2-124036 |
| S2‑123998 | UEPCOP Key issue cleanup | Ericsson, ST-Ericsson | Revised in S2-124027 |
| S2‑123999 | Solution for group based messaging using cell broadcast | KPN, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Nokia-Siemens-Networks | Revised in S2-124047 |
| S2‑124000 | MBMS based Group Messaging solutions | Nokia Siemens Networks, Huawei, Hisilicon, Samsung | Revised in S2-124048 |
| S2‑124001 | Solution of delivering group based message over T4/T5 | HTC, ZTE | Revised in S2-124051 |
| S2‑124002 | SIMTC and MTCe Drafting | Convenor (Intel) | Noted |
| S2‑124003 | Group based policy control requirements and assumptions | KPN, ZTE, Ericsson, ST-Ericsson | Revised in S2-124052 |
| S2‑124004 | Report MTC Monitoring Event using T5 and Tsp | ZTE, LG Electronics, Intel | Revised in S2-124127 |
| S2‑124005 | WITHDRAWN | - | WITHDRAWN |
| S2‑124006 | WITHDRAWN | - | WITHDRAWN |
| S2‑124007 | WITHDRAWN | - | WITHDRAWN |
| S2‑124008 | WITHDRAWN | - | WITHDRAWN |
| S2‑124009 | WITHDRAWN | - | WITHDRAWN |
| S2‑124010 | 23.251 CR0077R1: Using NRI for CS/PS Coordination in MOCN | SA WG2 | Noted |
| S2‑124011 | 23.272 CR0810R3: Network sharing impact on the CSFB | Huawei, Hisilicon | Noted |
| S2‑124012 | [DRAFT] Reply LS on DIAMETER-based Lg (SGSN - GMLC) interface | Cisco | Revised in S2-124142 |
| S2‑124013 | Reply LS on S6a security | SA WG2 | Revised in S2-124144 |
| S2‑124014 | LS response on Capability Indicator for SRVCC from UTRAN/GERAN to E-UTRAN/HSPA | SA WG2 | Revised in S2-124045 |
| S2‑124015 | MPS considerations for Core Network Overload Control | Applied Communication Sciences, NCS, NTT DOCOMO | Approved |
| S2‑124016 | Additions to Diameter overload analysis related to policy | Ericsson, ST-Ericsson | Approved |
| S2‑124017 | Additions to Diameter overload analysis related to charging | Ericsson, ST-Ericsson | Approved |
| S2‑124018 | Diameter Load Balancing Agent | Huawei, Hisilicon | Approved |
| S2‑124019 | CN overload due to flood of User Location Information (ULI) reporting | Alcatel-Lucent, Allot Communications | Revised in S2-124141 |
| S2‑124020 | Use cases for overload due to Location Request | Nokia Siemens Networks | Approved |
| S2‑124021 | 23.272 CR0839R1: Registration of MME for SMS | Ericsson, ST-Ericsson, Alcatel-Lucent, Hitachi | Revised in S2-124135 |
| S2‑124022 | 23.060 CR1691R2: Correction of indication of 'SMS support' | CATT | Revised in S2-124182 |
| S2‑124023 | 23.682 CR0065R1: Add IP-SM-GW identifier to S6m and T4 messages | Nokia Siemens Networks, LG Electronics | Approved |
| S2‑124024 | 23.204 CR0095R1: T4 trigger via IMS | Nokia Siemens Networks, LG Electronics | Revised in S2-124137 |
| S2‑124025 | 23.401 CR2448R2: UE supporting dual priority | Huawei, Hisilicon | Approved |
| S2‑124026 | 23.060 CR1702R2: MS supporting dual priority | Huawei, Hisilicon | Revised in S2-124138 |
| S2‑124027 | UEPCOP Key issue cleanup | Ericsson, ST-Ericsson | Approved |
| S2‑124028 | Framework for evaluation of UE power consumption optimizations | Qualcomm Incorporated | Revised in S2-124147 |
| S2‑124029 | Extended Paging Cycles | Nokia Siemens Networks, Nokia, Ericsson, ST-Ericsson, | Approved |
| S2‑124030 | Key Issue: Applicability of I-WLAN PLMN Selection | Motorola Mobility, Alcatel Lucent, AT&T, Intel | Revised in S2-124056 |
| S2‑124031 | Extending DRX based on UE Low Power Preference Indication | Intel | Approved |
| S2‑124032 | Power Saving State for Devices | Huawei, Hisilicon, Orange | Revised in S2-124184 |
| S2‑124033 | WITHDRAWN | Huawei, Hisilicon | WITHDRAWN |
| S2‑124034 | 23.401 CR2473R1: PDN disconnection when ISR is active | Nokia Siemens Networks | Noted |
| S2‑124035 | 23.401 CR2474R1: PDN disconnection when ISR is active | Nokia Siemens Networks | Noted |
| S2‑124036 | Taxonomy of MTC enhancements for optimising signalling no UP establishment | Huawei, Hisilicon | Approved |
| S2‑124037 | Use SCS as Push Proxy to reduce heartbeat/keep-alive data of Applications | Huawei, Hisilicon | Revised in S2-124171 |
| S2‑124038 | Draft Reply LS on PCC support for rSRVCC | SA WG2 | Revised in S2-124168 |
| S2‑124039 | 23.228 CR1020R1: Correction of reference point between MSC Server and ATCF to the RAVEL | Huawei, Hisilicon | Approved |
| S2‑124040 | Key Issue - Use of ANDSF ISMP/ISRP To Identify WLAN Networks for I-WLAN PLMN Selection | Research In Motion Ltd., UK, AT&T, Intel, Cisco, Huawei | Revised in S2-124057 |
| S2‑124041 | 23.251 CR0078R1: Incorrect definition of Anchor PLMN | Nokia Siemens Networks | Approved |
| S2‑124042 | 23.401 CR2477R1: Notifying UE on specific PDN disconnection while the UE is in the idle state | Alcatel-Lucent, Samsung, KT, LG Uplus, SKT, Orange, Ericsson, ST-Ericsson | Revised in S2-124054 |
| S2‑124043 | 23.401 CR2478R1: Notifying UE on specific PDN disconnection while the UE is in the idle state | Alcatel-Lucent, Samsung, KT, LG Uplus, SKT, Orange, Ericsson, ST-Ericsson | Revised in S2-124055 |
| S2‑124044 | LS response on contents of Handover Required message for rSRVCC | SA WG2 | Approved |
| S2‑124045 | LS response on Capability Indicator for SRVCC from UTRAN/GERAN to E-UTRAN/HSPA | SA WG2 | Revised in S2-124139 |
| S2‑124046 | Key issue update and Solution for group charging | Huawei, Hisilicon, ZTE? Juniper Networks? | Revised in S2-124053 |
| S2‑124047 | Solution for group based messaging using cell broadcast | KPN, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Nokia-Siemens-Networks | Approved |
| S2‑124048 | MBMS based Group Messaging solutions | Nokia Siemens Networks, Huawei, Hisilicon, Samsung | Revised in S2-124152 |
| S2‑124049 | HotSpot 2.0 network selection and discovery in case of no IP connectivity or no 3GPP coverage | InterDigital | Not Handled |
| S2‑124050 | Key issue - 3GPP UE having out-dated or no ANDSF PLMN selection policies due to no IP connectivity or no 3GPP coverage | InterDigital | Not Handled |
| S2‑124051 | Solution of delivering group based message over T4/T5 | HTC, ZTE | Noted |
| S2‑124052 | Group based policy control requirements and assumptions | KPN, ZTE, Ericsson, ST-Ericsson | Revised in S2-124151 |
| S2‑124053 | Key issue update and Solution for group charging | Huawei, Hisilicon, ZTE, Juniper Networks | Revised in S2-124154 |
| S2‑124054 | 23.401 CR2477R2: Notifying UE on specific PDN disconnection while the UE is in the idle state | Alcatel-Lucent, Samsung, KT, LG Uplus, SKT, Orange, Ericsson, ST-Ericsson | Revised in S2-124090 |
| S2‑124055 | 23.401 CR2478R2: Notifying UE on specific PDN disconnection while the UE is in the idle state | Alcatel-Lucent, Samsung, KT, LG Uplus, SKT, Orange, Ericsson, ST-Ericsson | Revised in S2-124089 |
| S2‑124056 | Key Issue: Applicability of I-WLAN PLMN Selection | Motorola Mobility, Alcatel Lucent, AT&T, Intel | Approved |
| S2‑124057 | Key Issue - Use of ANDSF ISMP/ISRP To Identify WLAN Networks for I-WLAN PLMN Selection | Research In Motion Ltd., UK, AT&T, Intel, Cisco, Huawei | Revised in S2-124155 |
| S2‑124058 | LS from GSMA RiLTE: LS to 3GPP SA WG2 and CT WG4 on IMS PDN connection deletion | GSMA RiLTE (RILTE Doc 27_029) | Response in S2-124178 |
| S2‑124059 | Key issue for multiple VPLMN | Ericsson, ST-Ericsson | Revised in S2-124156 |
| S2‑124060 | Key Issue: WLAN Load Info | Intel, AT&T, Orange | Approved |
| S2‑124061 | Architecture for SIPTO@LN | Ericsson, ST Ericsson | Revised in S2-124153 |
| S2‑124062 | Architecture for SIPTO@LN | Intel, Verizon, Cisco, Alcatel-Lucent, Huawei | Approved |
| S2‑124063 | per APN SIPTO@LN mobility support | InterDigital | Approved |
| S2‑124064 | per APN SIPTO@LN disconnection | InterDigital | Approved |
| S2‑124065 | Local PDN connection QoS management | Huawei, Hisilicon,CATT | Approved |
| S2‑124066 | LIPA PDN connection activation | Samsung | Revised in S2-124149 |
| S2‑124067 | Criteria for network to initiate per APN SIPTO@LN | InterDigital Communications, LG Electronics | Revised in S2-124150 |
| S2‑124068 | 23.237 CR0449R1: Definition of the MSC Assisted Mid-call feature | Orange | Revised in IMS Sessions to S2-124074 |
| S2‑124069 | 23.237 CR0450R1: Definition of the MSC Assisted Mid-call feature | Orange | Revised in IMS Sessions to S2-124075 |
| S2‑124070 | 23.237 CR0444R2: eSRVCC before ringing (brSRVCC) | NTT DOCOMO | Revised in parallel session in S2-124078 |
| S2‑124071 | 23.237 CR0447R2: Correction to avoid the ATCF's STN-SR to be overwritten when a registration over I2 or non-3GPP access occurs | Orange | Approved |
| S2‑124072 | 23.237 CR0448R2: Correction to avoid the ATCF's STN-SR to be overwritten when a registration over I2 or non-3GPP access occurs | Orange | Approved |
| S2‑124073 | 23.237 CR0452R1: Definition of the MSC Assisted Mid-call feature | Orange | Approved |
| S2‑124074 | 23.237 CR0449R2: Definition of the MSC Assisted Mid-call feature | Orange | Approved |
| S2‑124075 | 23.237 CR0450R2: Definition of the MSC Assisted Mid-call feature | Orange | Approved |
| S2‑124076 | 23.237 CR0441R2: Incoming alerting for DRVCC | Ericsson, ST-Ericsson | Approved |
| S2‑124077 | A new Architecture alternative for BusTI (Business Trunking for IP-PBX in Static mode of operation) | ZTE | Approved |
| S2‑124078 | 23.237 CR0444R3: eSRVCC before ringing (brSRVCC) | NTT DOCOMO | Approved |
| S2‑124079 | Report of the IMS parallel session | IMS Parallel sessions Convenor (T. Towle) | Noted |
| S2‑124080 | Stage 2 aspects of location based IMS registration control | China Mobile | Approved |
| S2‑124081 | WITHDRAWN | - | WITHDRAWN |
| S2‑124082 | WITHDRAWN | - | WITHDRAWN |
| S2‑124083 | WITHDRAWN | - | WITHDRAWN |
| S2‑124084 | WITHDRAWN | - | WITHDRAWN |
| S2‑124085 | WITHDRAWN | - | WITHDRAWN |
| S2‑124086 | WITHDRAWN | - | WITHDRAWN |
| S2‑124087 | WITHDRAWN | - | WITHDRAWN |
| S2‑124088 | Draft WID for Better Management of Traffic Offloading | KDDI | Noted |
| S2‑124089 | 23.401 CR2478R3: Notifying UE on specific PDN disconnection while the UE is in the idle state | Alcatel-Lucent, Samsung, KT, LG Uplus, SKT, Orange, Ericsson, ST-Ericsson, NEC | Approved |
| S2‑124090 | 23.401 CR2477R3: Notifying UE on specific PDN disconnection while the UE is in the idle state | Alcatel-Lucent, Samsung, KT, LG Uplus, SKT, Orange, Ericsson, ST-Ericsson, NEC | Revised in S2-124134 |
| S2‑124091 | [DRAFT] Reply LS on IMS PDN connection deletion | SA WG2 | Revised in S2-124133 |
| S2‑124092 | WITHDRAWN | ZTE | WITHDRAWN |
| S2‑124093 | Link layer aggregation model for NB-IFOM | Intel | Approved |
| S2‑124094 | Network triggered flow mobility | China Mobile | Revised in S2-124159 |
| S2‑124095 | NB-IFOM Solution | ZTE | Revised in S2-124165 |
| S2‑124096 | Correction to BB1 reference architecture | New Postcom | Revised in S2-124160 |
| S2‑124097 | P4C-F: Reference architecture correction | ZTE | Approved |
| S2‑124098 | [DRAFT] LS on charging requirements for traffic redirection | SA WG2 | Revised in S2-124148 |
| S2‑124099 | 23.402 CR1134R1: Trusted WLAN operator identification for EPC access | Alcatel-Lucent | Noted |
| S2‑124100 | Corrections on Home-routed Roaming Architecture Figure | Intel, Verizon, Cisco | Approved |
| S2‑124101 | Attributes of Mh Interface Messages | Intel, Verizon, Cisco | Approved |
| S2‑124102 | Conclusion for Release 12 | Intel, Verizon, Cisco | Approved |
| S2‑124103 | Cover Sheet for TR 23.862 for information in TSG SA | MOSAP Rapporteur (Intel) | Revised in S2-124164 |
| S2‑124104 | 23.401 CR2464R1: Clarification on SDU Error Ratio value when mapping EPS QCI=4 to Release 99 QoS parameters | Nokia Siemens Networks | Approved |
| S2‑124105 | 23.401 CR2465R1: Clarification on SDU Error Ratio value when mapping EPS QCI=4 to Release 99 QoS parameters | Nokia Siemens Networks | Approved |
| S2‑124106 | 23.401 CR2466R1: Clarification on SDU Error Ratio value when mapping EPS QCI=4 to Release 99 QoS parameters | Nokia Siemens Networks | Approved |
| S2‑124107 | LS response on Reply LS on SIRIG | SA WG2 | Approved |
| S2‑124108 | 23.203 CR0766R2: Correction of Redirection Functionality | Ericsson, ST-Ericsson | Approved |
| S2‑124109 | 23.203 CR0761R3: Correction of enforcement order of PCC and ADC rules for PCEF enhanced with ADC | Deutsche Telekom, Cisco | Approved |
| S2‑124110 | LS on Charging issue regarding PCC and ADC Rules | SA WG2 | Approved |
| S2‑124111 | Consolidation of Solution 1 and Solution 2 | Motorola Mobility, LG Electronics | Approved |
| S2‑124112 | Select the IP interface based on the routing configuration in IPv6 | China Mobile | Revised in S2-124166 |
| S2‑124113 | Non-IMS parallel sessions report | Convenor (Ivano Guardini) | Noted |
| S2‑124114 | WITHDRAWN | - | WITHDRAWN |
| S2‑124115 | WITHDRAWN | - | WITHDRAWN |
| S2‑124116 | WITHDRAWN | - | WITHDRAWN |
| S2‑124117 | WITHDRAWN | - | WITHDRAWN |
| S2‑124118 | WITHDRAWN | - | WITHDRAWN |
| S2‑124119 | WITHDRAWN | - | WITHDRAWN |
| S2‑124120 | WITHDRAWN | - | WITHDRAWN |
| S2‑124121 | WITHDRAWN | - | WITHDRAWN |
| S2‑124122 | WITHDRAWN | - | WITHDRAWN |
| S2‑124123 | WITHDRAWN | - | WITHDRAWN |
| S2‑124124 | WITHDRAWN | - | WITHDRAWN |
| S2‑124125 | WITHDRAWN | - | WITHDRAWN |
| S2‑124126 | 23.060 CR1719R1: Correction of priority services | Nokia Siemens Networks, Nokia Corporation | Approved |
| S2‑124127 | Report MTC Monitoring Event using T5 and Tsp | ZTE, LG Electronics, Intel | Revised in S2-124173 |
| S2‑124128 | 23.251 CR0067R3: Network sharing impact on the CSFB | Huawei, Hisilicon | Noted |
| S2‑124129 | Adding requirements of detecting and reporting failure causes of communication | China Mobile | Approved |
| S2‑124130 | Requirement for Monitoring Service Provisioning | HTC | Revised in S2-124170 |
| S2‑124131 | A reference architecture for monitoring | Huawei, Hisilicon | Revised in S2-124174 |
| S2‑124132 | First attach event monitoring and notification to SCS | Ericsson, ST-Ericsson | Revised in S2-124175 |
| S2‑124133 | [DRAFT] Reply LS on IMS PDN connection deletion | SA WG2 | Revised in S2-124169 |
| S2‑124134 | 23.401 CR2477R4: Notifying UE on specific PDN disconnection while the UE is in the idle state | Alcatel-Lucent, Samsung, KT, LG Uplus, SKT, Orange, Ericsson, ST-Ericsson, NEC | Approved |
| S2‑124135 | 23.272 CR0839R2: Registration of MME for SMS | Ericsson, ST-Ericsson, Alcatel-Lucent, Hitachi | Revised in S2-124181 |
| S2‑124136 | [DRAFT] LS on Device Triggering Identification | SA WG2 | Revised in S2-124183 |
| S2‑124137 | 23.204 CR0095R2: T4 trigger via IMS | Nokia Siemens Networks, LG Electronics | Approved |
| S2‑124138 | 23.060 CR1702R3: MS supporting dual priority | Huawei, Hisilicon | Approved |
| S2‑124139 | LS response on Capability Indicator for SRVCC from UTRAN/GERAN to E-UTRAN/HSPA | SA WG2 | Approved |
| S2‑124140 | GERAN Network Sharing working assumptions | Ericsson | Revised in S2-124167 |
| S2‑124141 | CN overload due to flood of User Location Information (ULI) reporting | Alcatel-Lucent, Allot Communications, Orange | Revised in S2-124146 |
| S2‑124142 | [DRAFT] Reply LS on DIAMETER-based Lg (SGSN - GMLC) interface | SA WG2 | Revised in S2-124186 |
| S2‑124143 | Reply LS on QoS parameters that can be upgraded and downgraded | SA WG2 | Approved |
| S2‑124144 | Reply LS on S6a security | SA WG2 | Approved |
| S2‑124145 | WID for User Plane Congestion Management (UPCON) | NEC, KDDI, NTT DOCOMO | Approved |
| S2‑124146 | CN overload due to flood of User Location Information (ULI) reporting | Alcatel-Lucent, Allot Communications, Orange | Approved |
| S2‑124147 | Framework for evaluation of UE power consumption optimizations | Qualcomm Incorporated | Approved |
| S2‑124148 | [DRAFT] LS on charging requirements for traffic redirection | SA WG2 | Approved |
| S2‑124149 | LIPA PDN connection activation | Samsung | Approved |
| S2‑124150 | Criteria for network to initiate per APN SIPTO@LN | InterDigital Communications, LG Electronics | Approved |
| S2‑124151 | Group based policy control requirements and assumptions | KPN, ZTE, Ericsson, ST-Ericsson | Revised in S2-124180 |
| S2‑124152 | MBMS based Group Messaging solutions | Nokia Siemens Networks, Huawei, Hisilicon, Samsung | Approved |
| S2‑124153 | Architecture for SIPTO@LN | Ericsson, ST Ericsson | Approved |
| S2‑124154 | Key issue update and Solution for group charging | Huawei, Hisilicon, ZTE, Juniper Networks | Approved |
| S2‑124155 | Key Issue - Use of ANDSF ISMP/ISRP To Identify WLAN Networks for I-WLAN PLMN Selection | Research In Motion Ltd., UK, AT&T, Intel, Cisco, Huawei | Approved |
| S2‑124156 | Key issue for multiple VPLMN | Ericsson, ST-Ericsson | Approved |
| S2‑124157 | Reply LS on border control concepts for VINE | SA WG2 | Approved |
| S2‑124158 | Reply LS on the redirection functionality of SAPP | SA WG2 | Approved |
| S2‑124159 | Network triggered flow mobility | China Mobile | Approved |
| S2‑124160 | Correction to BB1 reference architecture | New Postcom | Approved |
| S2‑124161 | P4C-TI attachment procedure-option 1 - PCRF initiated GCS over S9a | ZTE | Revised in S2-124187 |
| S2‑124162 | P4C-TI Attachment procedure-option 2 - BPCF initiated GCS over S9a | ZTE | Merged into S2-124187 |
| S2‑124163 | P4C-TI additional Gateway control session operation over S9a | ZTE | Approved |
| S2‑124164 | Cover Sheet for TR 23.862 for information in TSG SA | MOSAP Rapporteur (Intel) | Approved |
| S2‑124165 | NB-IFOM Solution | ZTE | Revised in S2-124189 |
| S2‑124166 | Select the IP interface based on the routing configuration in IPv6 | China Mobile | Revised in S2-124185 |
| S2‑124167 | GERAN Network Sharing working assumptions | Ericsson, TeliaSonera?, Huawei?, Nokia Siemens Networks?, Vodafone? | Revised in S2-124179 |
| S2‑124168 | Draft Reply LS on PCC support for rSRVCC | SA WG2 | Approved |
| S2‑124169 | [DRAFT] Reply LS on IMS PDN connection deletion | SA WG2 | Revised in S2-124178 |
| S2‑124170 | Requirement for Monitoring Service Provisioning | HTC | Revised in S2-124172 |
| S2‑124171 | Use SCS as Push Proxy to reduce heartbeat/keep-alive data of Applications | Huawei, Hisilicon | Noted |
| S2‑124172 | Requirement for Monitoring Service Provisioning | HTC | Approved |
| S2‑124173 | Report MTC Monitoring Event using T5 and Tsp | ZTE, LG Electronics, Intel | Approved |
| S2‑124174 | A reference architecture for monitoring | Huawei, Hisilicon | Approved |
| S2‑124175 | First attach event monitoring and notification to SCS | Ericsson, ST-Ericsson | Approved |
| S2‑124176 | IP-CAN session in fixed broadband access | Ericsson, Alcatel-Lucent | Approved |
| S2‑124177 | Reply LS on CS AMR type change during relocation | SA WG2 | Approved |
| S2‑124178 | Reply LS on IMS PDN connection deletion | SA WG2 | Approved |
| S2‑124179 | GERAN Network Sharing working assumptions | Ericsson, TeliaSonera?, Huawei?, Nokia Siemens Networks?, Vodafone? | Agreed |
| S2‑124180 | Group based policy control requirements and assumptions | KPN, ZTE, Ericsson, ST-Ericsson | Approved |
| S2‑124181 | 23.272 CR0839R3: Registration of MME for SMS | Ericsson, ST-Ericsson, Alcatel-Lucent, Hitachi | Approved |
| S2‑124182 | 23.060 CR1691R3: Correction of indication of 'SMS support' | CATT | Approved |
| S2‑124183 | LS on Device Triggering Identification | SA WG2 | Revised in S2-124190 |
| S2‑124184 | Power Saving State for Devices | Huawei, Hisilicon, Orange | Approved |
| S2‑124185 | Select the IP interface based on the routing configuration in IPv6 | China Mobile | Revised in S2-124188 |
| S2‑124186 | Reply LS on DIAMETER-based Lg (SGSN - GMLC) interface | SA WG2 | Approved |
| S2‑124187 | P4C-TI attachment procedure-option 1 - PCRF initiated GCS over S9a | ZTE | Approved |
| S2‑124188 | Select the IP interface based on the routing configuration in IPv6 | China Mobile | Approved |
| S2‑124189 | NB-IFOM Solution | ZTE | Approved |
| S2‑124190 | LS on Device Triggering Identification | SA WG2 | Approved |
| S2‑124191 | Study on Providing control to UE for inbound/outbound connections with PCP (Port Control Protocol) | Orange, KT corp, China Mobile, Cisco, Movik Networks, Juniper Networks, ZTE, Nokia, Benu Networks, Alcatel-Lucent, China Telecom, Sierra Wireless, Intel | Approved |
page generated from database: 2024-04-13 13:51:47