3GPP TDocs (written contributions) at meeting
Meeting: S2-100 - 2013-11-11 to 2013-11-15, San Francisco
meeting id: S2-100 (click id for more info on this meeting)Click on the Tdoc to open its file.
| TDoc | Title | Source | Remarks |
|---|---|---|---|
| S2‑133866 | Draft Agenda for SA WG2#100 | SA WG2 Chairman | Revised to S2-133916. |
| S2‑133867 | Draft Report of SA WG2 meeting #99 | SA WG2 Secretary | Revised to S2-134339. |
| S2‑133868 | LS from CT WG1: LS on UE Requirements for PSAP callback | CT WG1 (C1-132674) | Postponed S2-133148 from meeting #99. Response drafted in S2-134245, revised to S2-134341 (for e-mail approval, noted). This LS was then postponed to meeting #101. |
| S2‑133869 | LS from SA WG3: Reply LS on interaction of oneM2M with Underlying Networks | SA WG3 (S3-130842) | Postponed S2-133159 from meeting #99. Postponed to meeting #101 |
| S2‑133870 | LS from CT WG1: Reply LS on providing access network information for charging | CT WG1 (C1-133548) | Postponed S2-133166 from meeting #99. It was unclear last SA WG2 and some input for explaining the issue wanted. Postponed to meeting #101. |
| S2‑133871 | LS from CT WG3: LS on bearer binding for the PCC rule with application identifier | CT WG3 (C3-131299) | Postponed to meeting #101 Postponed S2-133170 from meeting #99. Response drafted in S2-134024. Postponed to meeting #101 |
| S2‑133872 | LS from CT WG4: LS OUT on Rollback Behaviour in EPC during TAU/RAU rejection | CT WG4 (C4-131514) | Postponed S2-133174 from meeting #99. Noted in parallel sessions |
| S2‑133873 | LS from oneM2M: LS on interactions of oneM2M with Underlying Networks | oneM2M (oneM2M-TP-2013-0307R01) | Postponed S2-133181 from meeting #99. Response drafted in S2-134122. Postponed to meeting #101 |
| S2‑133874 | LS from RAN WG2: Reply LS on Questions to RAN on UPCON | RAN WG2 (R2-133030) | The SA WG2 Chairman suggested this could be noted as there is no proposed reply and SA WG2 are not ready to answer it. Ericsson requested that this is not noted as long as there is no agreed conclusion to the TR. It was decided to postpone this LS to meet |
| S2‑133875 | LS from SA WG5: LS to SA WG2 and CT WG4 on Charging aspects for Network Sharing (MOCN GWCN) | SA WG5 (S5-131380) | Postponed S2-133196 from meeting #99. Response drafted in S2-133951, revised to S2-134534 (for e-mail approval, approved) |
| S2‑133876 | LS from BBF: LS on status of WT-291 work and request of feedback on S2a tunnel setup failure scenario | BBF (bbf2013.1051.01) | Postponed S2-133515 from meeting #99. Postponed to a future meeting. |
| S2‑133877 | LS from SA WG4: Reply LS on End-to-end QoS handling of MTSI | SA WG4 (S4-131105) | This LS was postponed and contribution on this was invited to the next meeting. Response drafted in S2-134253. This LS was postponed and contribution on this was invited to the next meeting. |
| S2‑133878 | LS from SA WG4: Reply to LS (S4-130755=STQ(13)43_056r1) on Delay values in 3GPP Release 12 | SA WG4 (S4-131145) | The SA WG2 Chairman proposed to note this LS. Noted |
| S2‑133879 | LS from RAN WG1: Response LS on Public Safety UE-Network Relays | RAN WG1 (R1-134922) | This LS was noted. Response to S2-133808 (S2#99). Noted |
| S2‑133880 | LS from RAN WG1: Response LS on GCSE with eMBMS | RAN WG1 (R1-134985) | Response to S2-133846 (S2#99). Review. Open if needed. Not Handled. Postponed to meeting #101 |
| S2‑133881 | LS from RAN WG2: Reply LS on security aspects of protocol architectures for small cell enhancements | RAN WG2 (R2-133650) | The SA WG2 Chairman proposed to note this LS. There was some discussion on whether information should be provided to RAN WG2 at this time. There was no agreement that this was necessary at this time and if RAN WG2 wish a review of their work, they can sen |
| S2‑133882 | LS from RAN WG2: Reply LS on UEPCOP considerations | RAN WG2 (R2-133695) | This was left for off-line review and was noted. Response to S2-133863 (S2#99). This was left for off-line review and was noted. |
| S2‑133883 | LS from RAN WG2: Response LS on Provisioning of E-UTRA Radio Capabilities in GERAN | RAN WG2 (R2-133696) | note?. Noted in parallel sessions |
| S2‑133884 | LS from RAN WG2: LS on Public Safety UE-Network Relays | RAN WG2 (R2-133720) | This LS was noted. Response to S2-133808 (S2#99). Noted |
| S2‑133885 | LS from RAN WG2: Response LS on GCSE with eMBMS | RAN WG2 (R2-133728) | Response to S2-133846 (S2#99). Review. Open if needed. Not Handled. Postponed to meeting #101 |
| S2‑133886 | LS from RAN WG2: Reply LS on Mitigating excessive signalling from frequent small data | RAN WG2 (R2-133729) | Postponed to meeting #101 |
| S2‑133887 | LS from RAN WG3: Reply LS on security aspects of protocol architectures for small cell enhancements | RAN WG3 (R3-131919) | Response to S2-133183 (S2#99). Noted |
| S2‑133888 | LS from RAN WG3: Reply LS on Public Safety UE-to-Network Relays | RAN WG3 (R3-131971) | This LS was noted. Response to S2-133808 (S2#99). Noted |
| S2‑133889 | LS from RAN WG3: Reply LS on GCSE with eMBMS | RAN WG3 (R3-131972) | Response to S2-133846 (S2#99). Review. Open if needed. Not Handled. This LS was postponed to meeting #101. |
| S2‑133890 | LS from RAN WG3: LS on Clarification on SIPTO at Local Network | RAN WG3 (R3-131980) | Alcatel-Lucent agreed to draft a response indicating that SA WG2 agree with this. This was drafted in S2-134344 (for e-mail approval). Result: approved. Response drafted in S2-134344 (for e-mail approval, approved) |
| S2‑133891 | LS from RAN WG3: Reply LS on CSFB-interaction between eMPS and emergency | RAN WG3 (R3-131974) | Noted in parallel sessions |
| S2‑133892 | LS from RAN WG3: LS on inbound mobility to shared H(e)NB | RAN WG3 (R3-131981) | Noted in parallel sessions |
| S2‑133893 | LS from CT WG1: Reply LS on End-to-end QoS handling of MTSI | CT WG1 (C1-134386) | The SA WG2 Chairman proposed to note this LS. Noted |
| S2‑133894 | LS from CT WG1: Reply LS on uplink packet filters | CT WG1 (C1-134387) | Response drafted in S2-134295. Final response in S2-134445 |
| S2‑133895 | LS from CT WG1: LS on default APN operation | CT WG1 (C1-134393) | Postpone to meeting #101 |
| S2‑133896 | LS from CT WG1: LS on merging ForServiceBased and ForFlowBased ISRP flow distribution containers | CT WG1 (C1-134394) | This was postponed to meeting #101. The SA WG2 Chairman proposed to postpone this LS. This was postponed to meeting #101. |
| S2‑133897 | LS from CT WG1: Reply LS on UEPCOP CT considerations | CT WG1 (C1-134490) | This was left for off-line review and was noted. Response to S2-133863 (S2#99). This was left for off-line review and was noted. |
| S2‑133898 | LS from CT WG1: LS on interaction between SIPTO at the local network and the CS fallback service in connected mode | CT WG1 (C1-134492) | Response drafted in S2-133973. Final response in S2-134546 Response drafted in S2-133973. Final response in S2-134546 |
| S2‑133899 | LS from CT WG1: Reply LS on CSFB priority call handling in a network supporting Multimedia Priority Service | CT WG1 (C1-134519) | Responses drafted in S2-133943 and S2-134155. This LS was postponed to meeting #101 |
| S2‑133900 | LS from CT WG3: Reply LS to SA WG4 LS on End-to-end QoS handling of MTSI. | CT WG3 (C3-131594) | The SA WG2 Chairman proposed to note this LS. Noted |
| S2‑133901 | LS from CT WG3: Reply LS on new work item on IMS support for RTP / RTCP transport multiplexing | CT WG3 (C3-131627) | This was postponed to meeting #101. The SA WG2 Chairman proposed to postpone this LS. This was postponed to meeting #101. |
| S2‑133902 | Clarification on C-plane signalling for RAN user plane congestion reporting solution | NTT DOCOMO, Intel | Not Handled |
| S2‑133903 | Evaluation of C-plane signalling for RAN user plane congestion reporting solution | NTT DOCOMO, Intel | There were a number of comments raised and some sections should be moved into clause 7. This was revised off-line in S2-134375 Revised to S2-134376. |
| S2‑133904 | WebRTC Solution 7 Update | Broadcom Corporation | Revised in parallel sessions to S2-134265. |
| S2‑133905 | - | Broadcom Corporation | [WITHDRAWN] [WITHDRAWN] [WITHDRAWN] [WITHDRAWN] |
| S2‑133906 | 23.002 CR0270: Introduction of Lgd | Cisco | Wrong spec in cover sheet, stage 3 alignment. Revised in parallel sessions to S2-134308. |
| S2‑133907 | 23.401 CR2625: Rollback Behaviour in EPC during TAU/RAU rejection | Cisco | Revised in parallel sessions to S2-134318. |
| S2‑133908 | LS from WiFi Alliance: Reply to WBA LS on Signaling Optimization | WiFi Alliance (Wi-Fi Alliance LS on HotSpot 2 0 20130802.) | We cannot discuss the LS itself in SA WG2 due to lack of general availability of the document. The SA WG2 Chairman proposed to note this LS. Qualcomm commented that merely noting this will result in it being sent again. The SA WG2 Chairman suggested other |
| S2‑133909 | Discussion on Core Network Type Selection based on the Subscription Information | NTT DOCOMO | Revised in parallel sessions to S2-134310. |
| S2‑133910 | 23.401 CR2606R3: Addition of Subscription Information for Selecting a Specific Network | NTT DOCOMO, Vodafone?, Telecom Italia?, China Mobile?, Verizon?, Deutsche Telekom? | Not Handled |
| S2‑133911 | 23.060 CR1816R3: Addition of Subscription Information for Selecting a Specific Network | NTT DOCOMO, Vodafone?, Telecom Italia?, China Mobile?, Verizon?, Deutsche Telekom? | Resubmission of S2-133743. Not Handled |
| S2‑133912 | LS from CT WG4: Reply LS on Normative work on overload handling for device triggering | CT WG4 (C4-131743) | Postponed to meeting #101 |
| S2‑133913 | LS from CT WG4: LS on Progress of Dia_SGSN_GMLC workitem for defining optimized LCS procedure for combined MME/SGSN | CT WG4 (C4-131752) | Asks stage 2 to align with stage 3. Noted in parallel sessions |
| S2‑133914 | LS from CT WG4: Reply LS on UEPCOP CT considerations | CT WG4 (C4-131869) | This was left for off-line review and was noted. Response to S2-133863 (S2#99). This was left for off-line review and was noted. |
| S2‑133915 | LS from : on Statement : | GSMA TSGWIF (TSGWIF_217) | The SA WG2 Chairman proposed to note this LS. This was postponed to meeting #101 |
| S2‑133916 | Draft Agenda for SA WG2#100 | SA WG2 Chairman | Revised to S2-134338. |
| S2‑133917 | LS from RAN WG2: LS on CN impacts in RAN WG2 solutions for WLAN/3GPP radio interworking | RAN WG2 (R2-133697) | Responses drafted in S2-133925, S2-133962, S2-134028, S2-134127, S2-134145 and S2-1304147. Final response in S2-134303 |
| S2‑133918 | Discussion on the problem of UE Radio Capability information size | NTT DOCOMO, Vodafone?, Telecom Italia?, China Mobile?, Verizon?, Deutsche Telekom? | for JM with RAN WG2? Not Handled |
| S2‑133919 | LS on the problem of UE Radio Capability information size | NTT DOCOMO | Not Handled |
| S2‑133920 | LS from SA WG5: LS on Standardization of a Diameter interface for Circuit Switched (CS) Domain Charging | SA WG5 (S5-131753) | The SA WG2 Chairman proposed to note this LS. Noted |
| S2‑133921 | LS from SA WG5: LS on providing Charging Characteristics to TDF | SA WG5 (S5-131800) | A related CR in S2-133969 was reviewed. A response was drafted in S2-134230 which was revised in S2-134536 (for e-mail approval). Final response in S2-134575 Response drafted in S2-134230, revised in S2-134536 (for e-mail approval). Final response in S2-1 |
| S2‑133922 | 23.203 CR0852: Clarification for application detection function of PCEF and TDF | China Mobile,Huawei | Revised in parallel sessions to S2-134292. |
| S2‑133923 | 23.203 CR0845R2: Correction of PCRF discovery and selection in the presence of NAT devices and overlapping address space | China Mobile, Huawei, ZTE | Resubmission of S2-133611. Revised in parallel sessions to S2-134296. |
| S2‑133924 | 23.203 CR0846R2: Correction of PCRF discovery and selection in the presence of NAT devices and overlapping address space | China Mobile, Huawei, ZTE | Resubmission of S2-133612. Revised in parallel sessions to S2-134297. |
| S2‑133925 | [DRAFT] Reply LS on CN impacts in RAN WG2 solutions for WLAN/3GPP radio interworking | NSN, Nokia | Response to S2-133917. Revised in parallel sessions to S2-134280. |
| S2‑133926 | 23.271 CR0400R3: Introduction of Lgd | Cisco, NSN | Resubmission of S2-133723. Revised in parallel sessions to S2-134309. |
| S2‑133927 | 23.401 CR2626: Correction to Gn-SGSN behavior during MME to Gn-SGSN handover procedure | Cisco | This may formally not work. The CR modifies steps that are copied from 23.060. So 23.060 would have to be changed. Revised in parallel sessions to S2-134332. |
| S2‑133928 | 23.402 CR1176R2: Access Network information reporting in case of a TWAN Access | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, China Telecom | Revised in parallel sessions to S2-134268. |
| S2‑133929 | 23.228 CR1043R1: Access Network information reporting in case of a TWAN Access | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, China Telecom | Resubmission of S2-133126. Revised in parallel sessions to S2-134270. |
| S2‑133930 | 23.203 CR0842R1: Access Network information reporting in case of a TWAN Access | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, China Telecom | Resubmission of S2-133127. Revised in parallel sessions to S2-134269. |
| S2‑133931 | NPLI retrieval by an IMS AS | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, China Telecom | Resubmission of S2-133329. Noted in parallel sessions |
| S2‑133932 | 23.402 CR1198R1: Access Network information fetching in case of a TWAN Access-use of Sh | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, China Telecom | Revised in parallel sessions to S2-134306. |
| S2‑133933 | 23.228 CR1045: Access Network information fetching in case of a TWAN Access-use of Sh | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, China Telecom | Revised in parallel sessions to S2-134305. |
| S2‑133934 | Updates to the variant of the off-path solution | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Cisco, Allot Communications, China Telecom, KDDI, ZTE, Broadcom Corporation, AT&T | Ericsson did not see the advantage of the averaging technique as this would provide less accurate information for each of the cells. Issues on the transfer of the congestion information were also raised. More clarification on the network sharing aspects s |
| S2‑133935 | 23.402 CR1199: Access Network information reporting in case of a TWAN Access: Nature of the information in TWAN Id | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, China Telecom | Noted in parallel sessions Merged into S2-134268. |
| S2‑133936 | Cover Sheet for TR 23.887 for approval at TSG SA | Intel | Intel reported that outstanding issues needed updating to take into account the issues which could not be resolved at this meeting. The SA WG2 Chairman replied that this depends on whether this is an issue which would be challenged. Vodafone commented tha |
| S2‑133937 | 23.402 CR1200: Bearer model for PDN connectivity service with PMIP based S2a | KDDI, Broadcom Corporation | Revised offline to S2-134263. |
| S2‑133938 | 23.402 CR1201: Detach Procedure in WLAN on PMIP S2a for Multi-connection Mode | KDDI, Broadcom Corporation | Revised offline to S2-134264. |
| S2‑133939 | 23.402 CR1202: PDN Connectivity Procedures in WLAN on PMIP S2a for Multi-connection Mode | KDDI, Broadcom Corporation | Revised in parallel sessions to S2-134284. |
| S2‑133940 | Refinement of integrated on-path off-path solution (6.1.5.4) | KDDI, China Telecom, ZTE, AT&T, Bell Canada | Ericsson commented that the accurate location is FFS and this does not really solve the real issue of detecting the UEs consuming high resources or which operator is the source of congestion in the network sharing scenario. AT&T commented that the paramet |
| S2‑133941 | Update of the solution D13 | Telecom Italia | There was some discussion and some clarifications were required. This was revised off-line in S2-134456 Revised to S2-134456. |
| S2‑133942 | Moving policy part from clause 6.1.5.1.4 to clause 6.1.6 | NTT DOCOMO, NEC, NSN, Intel | Not Handled |
| S2‑133943 | Reply to LS on CSFB priority call handling in a network supporting Multimedia Priority Service (to S2-133899/C1-134519) | Alcatel-Lucent | Response to S2-133899. Revised in parallel sessions to S2-134331. |
| S2‑133944 | 23.272 CR0908: CSFB priority call handling in an eMLPP/MPS network | Alcatel-Lucent | Not Handled |
| S2‑133945 | 23.272 CR0909: CSFB priority call handling in an eMLPP/MPS network | Alcatel-Lucent | Not Handled |
| S2‑133946 | 23.272 CR0910: CSFB priority call handling in an eMLPP/MPS network | Alcatel-Lucent | Not Handled |
| S2‑133947 | 23.401 CR2623R3: Reporting ULI and TimeZone at Network-initiated bearer release related procedures | Alcatel-Lucent, AT&T, KPN, Sprint, KDDI, China Mobile, ORANGE | Revision of approved of S2-133058. Is NAS cause reporting conditional?. Revised in parallel sessions to S2-134311. |
| S2‑133948 | 23.203 CR0850R2: Reporting ULI and TimeZone at MME-initiated bearer related procedures | Alcatel-Lucent, AT&T, KPN, Sprint, KDDI, China Mobile, ORANGE | Revision of S2-133536 from S2#99. Revised in parallel sessions to S2-134312. |
| S2‑133949 | 23.060 CR1819R2: Core Network Operator selection origin | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, TeliaSonera | Resubmission of S2-133522. Revised in parallel sessions to S2-134321. |
| S2‑133950 | 23.251 CR0096R2: Core Network Operator selection origin | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, TeliaSonera | Resubmission of S2-133523. Revised in parallel sessions to S2-134322. |
| S2‑133951 | Reply to LS (S2-133875/ S5-131380) on Charging aspects for Network Sharing (MOCN GWCN) | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | Response to S2-133875. Revised in parallel sessions to S2-134398. |
| S2‑133952 | New WID on Core Network Overload - User Location Information reporting improvements | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | The dates needed correction and this was revised in S2-134340 Revised to S2-134340. |
| S2‑133953 | 23.401 CR2627: Introduction of ULI reporting at PCC area level | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | Revised in parallel sessions to S2-134274. |
| S2‑133954 | 23.203 CR0853: Introduction of PCC area Event Reporting Function trigger | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | Revised in parallel sessions to S2-134275. |
| S2‑133955 | 23.060 CR1826: Introduction of ULI reporting at PCC area level | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | Revised in parallel sessions to S2-134276. |
| S2‑133956 | Discussion on eSaMOG Single-Connection Mode initial attach | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | Noted in parallel sessions |
| S2‑133957 | 23.402 CR1203: Single-Connection Mode Initial Attach | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Motorola Mobility, Broadcom Corporation | Noted in parallel sessions |
| S2‑133958 | 23.401 CR2628: End Marker Support for Handover Scenarios with SGW Relocation | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | Cover sheet is wrong, this marker was introduced SA WG2#97, so it may be considered a correction of that TEI12 Cat B feature. Revised in parallel sessions to S2-134313. |
| S2‑133959 | 23.865 CR0006: Solution #16 variant allowing the use of RPLMN WLANSP | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, AT&T, Intel, Broadcom Corporation | Noted in parallel sessions |
| S2‑133960 | 23.865 CR0007: Update of TR conclusions with solution #16 variant | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | Not Handled |
| S2‑133961 | 23.402 CR1204: Introduction of Home Operator S2a connectivity requirements rules from HPLMN for WLAN Selection | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, AT&T, Intel, Broadcom Corporation | Not Handled |
| S2‑133962 | Response to LS on CN impacts in RAN WG2 solutions for WLAN/3GPP radio interworking (S2-133917/R2-133697) | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | Response to S2-133917. Noted in parallel sessions |
| S2‑133963 | UPCON Core Network Solution Evaluation | Openet | evaluates 1.5.1-5 can any of this be merged into S2 134153? Not Handled |
| S2‑133964 | Preliminary UPCON conclusions for Rel-12 | Telecom Italia, Huawei, Hisilicon | There were some issues raised and this was left for further off-line discussion. Telecom Italia reported that they hoped to reach a compromise with this proposal to allow multiple levels of congestion indications which could be accepted by companies. The |
| S2‑133965 | 23.401 CR2629: Introduction of ULI reporting only when the UE is in 'CONNECTED' state | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | Revised in parallel sessions to S2-134277. |
| S2‑133966 | 23.203 CR0854: Introduction of ULI reporting only when the UE is in 'CONNECTED' state | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | Revised in parallel sessions to S2-134423. |
| S2‑133967 | 23.060 CR1827: Introduction of ULI reporting only when the UE is in 'CONNECTED' state | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | Revised in parallel sessions to S2-134278. |
| S2‑133968 | Exception sheet for Core Network Overload - User Location Information reporting improvements | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | Revised to S2-134496. |
| S2‑133969 | 23.203 CR0855: Addition of charging characteristics transfer to TDF | Allot Communications, ORANGE | This was reviewed off-line and revised in S2-134342 The SA WG2 Chairman proposed to postpone this LS. Revised to S2-134342. |
| S2‑133970 | Proposed conclusion | Allot,Openet,Cisco,Oracle,ALU,ALU- ShanghaiBell,ChinaTelecom,SPRINT,ZTE,Broadcom,KDDI,ChinaUnicom,USCellular,Comverse,Bell-Mobility,Hitachi,Sandvinen,Amdocs | Ericsson commented that their is absolutely no evaluation or justification for this conclusion, so no proof that the solution will work. Telecom Italia agreed that there is no justification for this included in the paper. It was commented that the solutio |
| S2‑133971 | 23.272 CR0867R5: SS service ID used in the Paging message | Huawei, Hisilicon, Telecom Italia | Revision of approved S2-133105. Corrects cover only? Agreed in parallel sessions. This CR was agreed |
| S2‑133972 | 23.272 CR0897R2: SS service ID used in the Paging message | Huawei, Hisilicon, Telecom Italia | Revision of approved S2-133559. Agreed in parallel sessions. This CR was agreed |
| S2‑133973 | Reply LS on interaction between SIPTO at the local network and the CS fallback service in connected mode | Huawei, Hisilicon, | Response to S2-133898. Revised in parallel sessions to S2-134317. |
| S2‑133974 | 23.272 CR0900R2: Correction of the extended service request procedure for SIPTO@LN | Huawei, Hisilicon, Intel, BlackBerry UK Ltd. | Resubmission of S2-133718. Agreed in parallel sessions. This CR was agreed |
| S2‑133975 | 23.203 CR0856: AAA-based accounting for Fixed Broadband Network | Huawei, ORANGE | Revised in parallel sessions to S2-134267. |
| S2‑133976 | Update the function description of WebRTC Signalling Function | Huawei | Not Handled |
| S2‑133977 | Removal of the authentication between WSF and S-CSCF related EN in solution 5 | Huawei | Not Handled |
| S2‑133978 | Removal of 401 auth_challenge related EN in solution 5 | Huawei | Not Handled |
| S2‑133979 | 23.402 CR1205: UE initiated PDN connectivity request procedure in WLAN on S2a for Multi-Connection Mode | Huawei, Hisilicon, China Telecom | Revised in parallel sessions to S2-134282. |
| S2‑133980 | Discussion of IP Address Allocation and DHCP Function | Huawei, Hisilicon | Not Handled |
| S2‑133981 | 23.402 CR1180R1: IP address Allocation and DHCP Function | Huawei, Hisilicon | Resubmission of S2-133290. Revised in parallel sessions to S2-134260. |
| S2‑133982 | 23.402 CR1207: Detach in WLAN for Multi-Connection Mode for GTP based S2a | China Telecom, Huawei, Hisilicon | Revised in parallel sessions to S2-134262. |
| S2‑133983 | Discussion of Transfer Mechanism of WLCP between the UE and the TWAN | Huawei, Hisilicon, Qualcomm Incorporated, Ericsson, BlackBerry UK Ltd, CATT, MediaTek, Intel | Noted in parallel sessions |
| S2‑133984 | 23.402 CR1179R1: WLCP Transport Mechanism | Huawei, Hisilicon | There was no agreement on the way forward and this was noted. Resubmission of S2-133288. Noted |
| S2‑133985 | Congestion control on Gs/SGs interface | Huawei, Hisilicon, | Noted in parallel sessions |
| S2‑133986 | 23.272 CR0843R3: Congestion control on the SGs interface | Huawei, Hisilicon, China Unicom, ORANGE,China Mobile, Interdigital | Resubmission of S2-133542. Not Handled |
| S2‑133987 | Technical Specification Group Services and System Aspects; Proximity based Services; Stage 2 | Qualcomm Incorporated (Rapporteur) | Ericsson commented that the Security aspects should be studied by SA WG3 and the SA WG3 LI Group. Qualcomm asked whether the section should be kept or a reference to the security TS added to the scope. It was decided to use a reference. Intel asked whethe |
| S2‑133988 | D2D Study Item: RAN WG Status | Qualcomm Incorporated (Rapporteur) | This was discussed and a number of clarifications on the status of the Study Item was provided. This was then noted. Noted |
| S2‑133989 | [DRAFT] LS on ProSe charging | Qualcomm Incorporated | Not Handled |
| S2‑133990 | On EPC level discovery | Qualcomm Incorporated, Motorola Mobility | There was no support for this in the drafting session. Qualcomm briefly presented the document to the main meeting. There were some issues raised with including this in the TR as the issues addressed and evaluation was not well understood by some companie |
| S2‑133991 | ProSe Communication 1-many decentralized mode- way forward | Qualcomm Incorporated, Alcatel-Lucent, Intel, U.S. Department of Commerce | Qualcomm clarified that the configuration is related to the resources and pre-configuration relates to the configuration before the operation begins rather than a fixed configuration in the UEs and the information is provided to ensure all devices will us |
| S2‑133992 | Direct discovery models | Qualcomm Incorporated | There was some discussion on the use of Model A or Model B as allowing Model B adds complexity. A number of other issues were raised and this was revised off-line in S2-134457 Revised to S2-134457. |
| S2‑133993 | ProSe Direct Discovery- way forward | Qualcomm Incorporated | This was merged in drafting sessions with S2-134207 and S2-134198 into S2-134358. Merged with S2-134207 and S2-134198 into S2-134358. |
| S2‑133994 | Evaluation of direct discovery solutions | Qualcomm Incorporated | This was covered by other discussions and was noted. Noted |
| S2‑133995 | Exception sheet for ProSe WID | Qualcomm Incorporated | Revised to S2-134486. |
| S2‑133996 | Update of Solution D1: Support of different discovery models | Qualcomm Incorporated | Not Handled |
| S2‑133997 | - | Qualcomm Incorporated | [WITHDRAWN] |
| S2‑133998 | Updates for solution D15 (EPC-level ProSe discovery) | LG Electronics | Not Handled |
| S2‑133999 | Exception sheet for IMS_WebRTC | Alcatel-Lucent, China Mobile, Alcatel-Lucent Shanghai Bell | Revised to S2-134359. |
| S2‑134000 | Exception sheet for NETLOC_TWAN | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | Revised to S2-134360. |
| S2‑134001 | Conclusion for Optimized Service Request | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | Vodafone suggested that this should be checked by SA WG3 to ensure there are no security issues. Alcatel-Lucent clarified that SA WG3 had not identified any issues in their TR. Orange indicated support for this conclusion. This was not considered enough s |
| S2‑134002 | Discussion on RAN LS response to SDDTE solutions 5.1.1.3.1-3 | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Qualcomm Incorporated, Ericsson | This was reviewed and discussed. Other contributions were considered. This was later noted. Noted |
| S2‑134003 | Evaluation of 5.1.1 solutions | Alcatel-Lucent | This was reviewed and other contributions were considered. This was later noted. Noted |
| S2‑134004 | 23.401 CR2630: Optimized Service Request | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | Not Handled |
| S2‑134005 | 23.060 CR1828: Optimized Service Request | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | Not Handled |
| S2‑134006 | 23.401 CR2594R4: Core Network assisted eNodeB parameters tuning | Ericsson | This was reviewed and discussed. Other contributions were considered. This was considered for inclusion in S2-134366 and was noted. Resubmission of S2-133842. Noted |
| S2‑134007 | 23.203 CR0849R3: Alignment of Fixed Broadband Access Annex with main specification body | Ericsson, Allot Communications, Huawei | Resubmission of S2-133703. Revised offline to S2-134258. |
| S2‑134008 | Evaluation of RAN-based solutions | Ericsson | Ericsson clarified that the bit-rate subscription is intended to allow operators to have some way of predicting the behaviour. If this is not needed in the FDI then a scalar can be sent to the RAN. Ericsson added that there is flexibility for differentiat |
| S2‑134009 | Downlink packet marking with PMIP | Ericsson, Allot Communications | solution 6.2.2 PMIP S5/S8 aspects merge with S2-134240? Not Handled |
| S2‑134010 | General issues with CN-based solutions | Ericsson | Movik Networks commented that the combined approach has a better chance of coexistence of different redundancy and load-balancing mechanisms. ZTE commented that there should be no issue with co-existence as long as there is a CN solution to provide adequa |
| S2‑134011 | Off-Path reporting Evaluation | Ericsson | AT&T did not agree with the conclusions reached in this document and did not agree that the information was useless to the operators. ZTE commented that the current text covers the functionality mentioned in the evaluation. Intel commented that roaming is |
| S2‑134012 | Performance of RAN-based and CN-based UPCON solutions | Ericsson | analysis of RAN and CN based solutions as input to conclusions. Not Handled |
| S2‑134013 | Solution 1- Procedures and Call flows | Ericsson | Not Handled |
| S2‑134014 | Solution 1- Roaming Scenarios | Ericsson | Not Handled |
| S2‑134015 | Access Line Identifier serving an AP as NPLI in TWAN | Ericsson | NOT A CR !. Noted in parallel sessions |
| S2‑134016 | UE registration into the IMS in case of rSRVCC | Ericsson | no CR?. Noted in parallel sessions |
| S2‑134017 | Returning back to E-UTRAN after SRVCC | Ericsson | Noted in parallel sessions |
| S2‑134018 | 23.216 CR0316R1: Returning back to E-UTRAN after SRVCC | Ericsson, Telecom Italia, AT&T?, Deutsche Telekom, China Mobile? | Resubmission of S2-131124 (S2#96). Revised in parallel sessions to S2-134389. |
| S2‑134019 | Enhancement of T-ADS to support also CS Voice Indication | Ericsson | no CR?. Noted in parallel sessions |
| S2‑134020 | 23.402 CR1177R3: Initial attach and handover attach call flows for single-connection mode | Ericsson, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Qualcomm Incorporated | Resubmission of S2-133695. Revised in parallel sessions to S2-134261. |
| S2‑134021 | 23.402 CR1209: Call flows for handover from WLAN to 3GPP | Ericsson | Revised in parallel sessions to S2-134285. |
| S2‑134022 | 23.402 CR1210: Detach and PDN disconnection call flows for single-connection mode | Ericsson | Agreed in parallel sessions. This CR was agreed |
| S2‑134023 | Link-model considerations | Ericsson | The following conclusions are endorsed: 1) When using SCM and MCM the UE sees the PDN Connection as a point-to-point link similar to how it is in 3GPP access. Shared link parameters such as netmask and default router address are not used. 2) Deferred I |
| S2‑134024 | Proposed reply LS on bearer binding for the PCC rule with application identifier | Ericsson | It is to be verified wether there are any charging issues to be checked with SA WG5. If that is the case, an LS to SA WG5 will be sent at SA WG2 101. Response to S2-133871. Revised in parallel sessions to S2-134291. |
| S2‑134025 | 23.203 CR0857: Corrections to handling of PCC rules with application identifier | Ericsson | Revised in parallel sessions to S2-134289. |
| S2‑134026 | 23.203 CR0858: Corrections to handling of PCC rules with application identifier | Ericsson | Revised in parallel sessions to S2-134290. |
| S2‑134027 | 23.203 CR0859: Delayed activation of PCC rules with Application ID | Ericsson | Revised in parallel sessions to S2-134386. |
| S2‑134028 | [DRAFT] Reply LS on CN impacts in RAN WG2 solutions for WLAN/3GPP radio interworking | Ericsson | Response to S2-133917. Noted in parallel sessions |
| S2‑134029 | Update for the solution C8 one-to-many communication | Ericsson | Intel asked what is layer 2 and what is layer 3 addressing in this proposal and suggested removing the C5/C6 parts. Alcatel-Lucent commented that this proposal does not involve the network in any processing and the handling of protocol stacks was unclear. |
| S2‑134030 | Tentative conclusions for ProSe UE-to-Network Relays | Ericsson | There was some discussion on this and many issues raised. This could not be agreed and was noted. Noted |
| S2‑134031 | 23.060 CR1799R1: Solution of restricting the USIM to specific UEs | Ericsson | Resubmission of S2-132386. Wait for SA WG3? Not Handled |
| S2‑134032 | 23.401 CR2568R1: Solution of restricting the USIM to specific UEs | Ericsson | Resubmission of S2-132387. Not Handled |
| S2‑134033 | SDDTE way forward | Intel, Huawei, HiSilicon, Interdigital, CATT, KPN, HTC, ZTE, LG Electronics, ITRI, Broadcom Corporation, China Mobile, KT Corp, China Unicom, China Telecom, NSN, Silver Spring Networks, Sierra Wireless, Telecom Italia, III, Sony, Acision | This was reviewed and discussed. There were a number of issues raised and no consensus on this contribution could be reached and it was noted. Ericsson raised the following concerns with the T5 small data solution. - We don't believe in fragmenting the sy |
| S2‑134034 | Solutions for WLAN/3GPP radio interworking and WLAN_NS | AT&T, Intel, Broadcom Corporation | Not Handled |
| S2‑134035 | Response to LS on CN impacts in RAN WG2 solutions for WLAN/3GPP radio interworking | AT&T | Noted in parallel sessions |
| S2‑134036 | WebRTC joint architecture proposal | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, China Mobile, Ericsson, Huawei, NSN, | Revised offline to S2-134259. |
| S2‑134037 | Procedures for WebRTC joint architecture proposal | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | Revised in parallel sessions to S2-134271. |
| S2‑134038 | Evaluation and conclusion proposal for key issue #7 ProSe direct discovery | HTC | Not Handled |
| S2‑134039 | Updates of D12 for network-assisted ProSe discovery | HTC | Not Handled |
| S2‑134040 | Evaluation and conclusion proposal for key issue #8 EPC-level ProSe discovery | HTC, LG Electronics | This was merged in the drafting session with S2-134128 into S2-134356. S2-134128 and S2-134040 merged in parallel sessions to S2-134356. |
| S2‑134041 | Considerations and Solution for Key Issue #9 | Motorola Mobility, Qualcomm Incorporated | Noted in parallel sessions |
| S2‑134042 | 23.865 CR0008: Conclusions for Key Issue #9 | Motorola Mobility, Qualcomm Incorporated | Revised in parallel sessions to S2-134279. |
| S2‑134043 | 23.402 CR1191R3: WLAN access network selection based on WLANSP rules | Motorola Mobilty, AT&T??, Qualcomm Incorporated, Intel??, Broadcom Corporation??, NSN??, Samsung?? | Revision of S2-133690. Revised offline to S2-134299. |
| S2‑134044 | 23.402 CR1211: Update ANDSF information to support WLAN access network selection and WORM | Motorola Mobilty, AT&T, Qualcomm Incorporated, Intel, NSN, Nokia, Samsung, LG Electronics | This CR is based on the approved CR1189rev2 in S2-133688 (ANDSF changes for WLAN_NS) and on the approved CR1194rev2 in S2-133698 (ISRP changes for WORM). These CRs should be un-approved if this CR is approved. This CR is nor implying any specific encodin |
| S2‑134045 | 23.402 CR1190R3: UE procedures based on ANDSF information | Motorola Mobilty, AT&T, Qualcomm Incorporated, Intel, Broadcom Corporation, NSN, Samsung, Nokia | Revision of S2-133689. Revised in parallel sessions to S2-134302. |
| S2‑134046 | Considering Malicious WLCP Implementations in the UE | Motorola Mobility, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | Noted in parallel sessions |
| S2‑134047 | Rel-12 Exceptions | SA WG2 Chairman | The SA WG2 Chairman clarified that he would produce an exception report to TSG SA for review at this meeting. If this can be agreed by SA WG2, this will be sent to TSG SA as an agreed SA WG2 input, otherwise he will produce a report as the SA WG2 Chairman |
| S2‑134048 | Pre-TSG SA#62 Work Planning Worksheet | SA WG2 Chairman | This was reviewed and updated at the Work Planning session and was revised in S2-134495 Revised at work planning session to S2-134495. |
| S2‑134049 | Improved SA WG1-SA WG2 Coordination | SA WG2 Chairman | This was reviewed at the work planning session and companies were asked to consider the points raised. This was then noted. Noted |
| S2‑134050 | Usability of congestion reporting in operator networks | Samsung, China Mobile | enhances 6.1.3 (basic 6.1.5 solution description) with vendor specific congestion reporting. Not Handled |
| S2‑134051 | Evaluation of RAN-based solution on the charging aspect | Samsung | After some discussion it was decided to take into account the charging principle in this document and the proposal was noted. Noted |
| S2‑134052 | Discussion on WLAN offloading decision | Samsung | Noted in parallel sessions |
| S2‑134053 | UE context release during handover | Samsung | Noted in parallel sessions |
| S2‑134054 | 23.401 CR2631: Correction in the End Marker packet delivery | Samsung | Noted in parallel sessions |
| S2‑134055 | Group communication with early DRB establishment | Samsung | This was discussed but no agreement to include this in the TR could be reached and the proposal was noted. Noted |
| S2‑134056 | Updated TR 23.701 (v0.2.2) | China Mobile | Noted in parallel sessions |
| S2‑134057 | Solutions analysis and way forward proposals for ProSe identifiers and system architecture | HTC | The SA WG2 Chairman asked whether any parts of the evaluation and conclusions could be agreed from this. Intel commented that this moves text from the Annex to the main body of the TR which had previously been discussed. It was decided to review other pro |
| S2‑134058 | LS from SA WG4: LS to SA WG2 on PSS DASH service | SA WG4 (S4-131258) | This was postponed to meeting #101. The SA WG2 Chairman proposed to postpone this LS. This was postponed to meeting #101. |
| S2‑134059 | update of Solution I3 | HTC | This was discussed and revised off-line in S2-134453 Revised to S2-134453. |
| S2‑134060 | Discussion on granularity of ProSe ID | CATT, CATR | Broadcom commented that UEs would need additional signalling to do Per-UE discovery. It was asked how the roaming user can prevent use of this identifier by unauthorized UEs and how unwanted UE tracking using this ID can be guarded against. There was some |
| S2‑134061 | clarification on solution D14 | CATT, CATR | Not Handled |
| S2‑134062 | Update of Solution R1 | CATT, CATR | This was reviewed and left for further off-line consideration. This was revised in S2-134477 Revised to S2-134477. |
| S2‑134063 | 23.402 CR1212: Handover in Multi-Connection Mode from 3GPP access to WLAN on GTP S2a | CATT | Revised in parallel sessions to S2-134286. |
| S2‑134064 | 23.401 CR2632: Modification on Inter-RAT Handover from UTRAN/GERAN to E-UTRAN | CATT | Revised in parallel sessions to S2-134391. |
| S2‑134065 | 23.402 CR1183R3: UE/TWAN requested PDN Disconnection Procedure in WLAN on GTP S2a for Multi-Connection Mode | CATT | Revision of S2-133696. Revised in parallel sessions to S2-134283. |
| S2‑134066 | Update and Evaluation on UE-to-network relay solution R12 | Huawei, Hisilicon | There were a number of issues highlighted and it was decided to review other contributions before making a decision on this proposal. No resolution of this was obtained in the meeting and this was noted. No resolution of this was obtained in the meeting a |
| S2‑134067 | Update and Evaluation on ProSe discovery solution D9 | Huawei, Hisilicon | Not Handled |
| S2‑134068 | Update of solution 7: Assign and Re-assign Priority and Pre-emption capability for the GC | Huawei, Hisilicon | There were a number of questions and clarifications provided. This was further reviewed off-line and revised in S2-134351 Revised to S2-134351. |
| S2‑134069 | Conclusion on the QoS aspects of GCSE | Huawei, Hisilicon | There were some questions on how the Group priority can be updated without GCSE AS involvement as proposed here. Huawei clarified that the Group Communication priority is assigned by the GCSE AS but this is the application priority level, not the priority |
| S2‑134070 | 23.865 CR0009: Update of TR conclusions with solution #14 | Huawei, Hisilicon | Noted in parallel sessions |
| S2‑134071 | 23.402 CR1189R3: Update ANDSF information to support WLAN access network selection | Huawei, Hisilicon | Revision of S2-133688 [WITHDRAWN] |
| S2‑134072 | 23.402 CR1191R4: WLAN access network selection based on WLANSP rules | Huawei, Hisilicon | Revision of S2-133690 [WITHDRAWN] |
| S2‑134073 | Ultra-Flash CSFB (SRVCC based CSFB) | Huawei, Hisilicon | Revised in parallel sessions to S2-134315. |
| S2‑134074 | 23.272 CR0911: Ultra-Flash CSFB (SRVCC based CSFB) | Huawei, HiSilicon,China Unicom | Revised in parallel sessions to S2-134316. |
| S2‑134075 | 23.402 CR1213: Handover procedure from 3GPP access to WLAN on PMIP S2a for Multi-connection Mode | KDDI, Broadcom Corporation | Revised in parallel sessions to S2-134287. |
| S2‑134076 | Cover Sheet for TR 23.701 presentation to TSG SA | China Mobile, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | Revised in parallel sessions to S2-134272. |
| S2‑134077 | NETLOC: extracts from 24.229 related with Netloc-TWAN | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | Noted in parallel sessions |
| S2‑134078 | 23.203 CR0860: Support of PCC in case of NAT | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | Noted in parallel sessions |
| S2‑134079 | 23.203 CR0861: Support of PCC in case of NAT | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | Not Handled |
| S2‑134080 | 23.402 CR1214: Clarification on multi-access network discovery and selection procedure | Gemalto | Not Handled |
| S2‑134081 | 23.402 CR1215: WLAN rules pre-configuration | Gemalto | Not Handled |
| S2‑134082 | LS from Broadband Forum: Reply to 3GPP LS S2-133830 (BBF2013.1076.00) | Broadband Forum (bbf2013.1082.01) | Response to S2-133830 (S2#99). Noted in parallel sessions |
| S2‑134083 | LS from Broadband Forum: Additional feedback on 3GPP LS S2-132329 (bbf2013.705.00) | Broadband Forum (bbf2013.1092.01) | Response to S2-132329 (S2#99). Noted in parallel sessions |
| S2‑134084 | Clarification of the Congestion Reporting Solution Based on GTP-U | China Mobile, NEC, AT&T, NSN | It was commented that TSG SA had clearly stated that roaming issues can be deferred to Rel 13 and suggested this should not be considered for this Rel 12 work. Ericsson commented that there is already a solution for Cell location using CNO-ULI and questio |
| S2‑134085 | - | NEC | [WITHDRAWN] |
| S2‑134086 | 23.682 CR0077R2: Introducing UE Power Saving Mode | Huawei, HiSilicon, ORANGE, NEC | There were some issues with this proposal and it was noted. Revision of S2-133647. Noted |
| S2‑134087 | 23.401 CR2603R2: Introducing UE Power Saving Mode | Huawei, HiSilicon, ORANGE, NEC | There were some issues with this proposal and it was noted. Revision of S2-133648. Noted |
| S2‑134088 | 23.060 CR1814R2: Introducing UE Power Saving Mode | Huawei, HiSilicon, ORANGE, NEC | There were some issues with this proposal and it was noted. Revision of S2-133649. Noted |
| S2‑134089 | Enhancement on Control Plane based reporting for UTRAN | Intel, NTT DOCOMO | This required further discussion off-line and was revised in S2-134345 Revised to S2-134345. |
| S2‑134090 | Clarification on GTP-U based congestion reporting solution | Intel, NTT DOCOMO | solution 1.5.1 PMIP S5/S8 aspects merge with S2 134206? Not Handled |
| S2‑134091 | Cover Sheet for TR 23.862 for approval at TSG SA | Intel | This was reviewed and approved. Resubmission of S2-133273.. Approved |
| S2‑134092 | Evaluation of solution P2 on ProSe configuration | NEC | This was reviewed and some comments and clarifications made. This was revised off-line in S2-134367 Revised to S2-134367. |
| S2‑134093 | ProSe configuration in EPC | NEC | This was reviewed and some comments and issues were raised. No consensus could be reached on this proposal and it was noted. Noted |
| S2‑134094 | 23.402 CR1216: Clarification on multi-access network discovery and selection procedure and pre-configuration | Gemalto | Noted in parallel sessions |
| S2‑134095 | Conclusion on RAN-based solutions for UPCON | NSN | AT&T raised an issue on the UE impacts of this solution. This was left for further off-line discussion. NSN commented that there had been no negative technical issues raised with this solution, which uses existing functionality. 8 companies indicated an o |
| S2‑134096 | RAN Congestion Awareness Information | NSN, NTT DOCOMO, AT&T, KDDI, China Mobile, Verizon, Samsung, NEC, China Unicom, Intel, ZTE, ORANGE | Ericsson asked how this can be evaluated and the performance be determined and asked who is responsible for problems when the mechanism is distributed. NSN replied that this is an issue for all solutions and it is up to the operators to configure the corr |
| S2‑134097 | Resolving Editor's Notes in solution 2 | NSN | Not Handled |
| S2‑134098 | Impacts and Evaluation part for Solution 2 | NSN | Not Handled |
| S2‑134099 | 23.060 CR1800R6: Definition for a valid state of the TFT setting | Ericsson | Revision of S2-133841. Revised in parallel sessions to S2-134293. |
| S2‑134100 | 23.060 CR1801R4: Definition for a valid state of the TFT setting | Ericsson | Resubmission of S2-133621. Revised in parallel sessions to S2-134294. |
| S2‑134101 | 23.203 CR0824R6: PCC support for unidirectional downlink flows in NW-initiated procedures | Ericsson | Revision of S2-133794. Agreed in parallel sessions. This CR was agreed |
| S2‑134102 | 23.203 CR0825R4: PCC support for unidirectional downlink flows in NW-initiated procedures | Ericsson | Revision of S2-133619. Agreed in parallel sessions. This CR was agreed |
| S2‑134103 | 23.401 CR2596R2: Handling of uplink packet filters and definition for a valid state of the TFT setting | Ericsson | Revision of S2-133616. Agreed in parallel sessions.. This CR was agreed |
| S2‑134104 | 23.401 CR2597R2: Handling of uplink packet filters and definition for a valid state of the TFT setting | Ericsson | Resubmission of S2-133617. Agreed in parallel sessions.. This CR was agreed |
| S2‑134105 | Applicability for 23.682 CR on 'CN assisted RAN parameters tuning' | Ericsson | This was reviewed and discussed. Other contributions were considered. This was considered for inclusion in S2-134366 and was noted. Noted |
| S2‑134106 | Updated conclusions of extended DRX solutions | Ericsson | There was some discussion on the conclusions for recommendations for power saving. There were a number of issues raised. Ericsson asked whether some of the text in 7.1 could be captured in the TR. This was discussed off-line and the evaluation part revise |
| S2‑134107 | Discussion on EPC impact on the introduction of UE power save mode | Ericsson, Huawei, HiSilicon | Alcatel-Lucent asked why this is not included in each TAU. Ericsson clarified that this points out that the UE should not try to request a new periodic time in the subsequent update, but this is not part of the proposed changes. Ericsson also clarified th |
| S2‑134108 | 23.682 CR0077R3: Introducing UE Power Saving Mode | Huawei, HiSilicon, Ericsson | This was reviewed and a number of clarifications requested. The related CRs were also reviewed. This was revised off-line in S2-134377 Revision of S2-133647. Revised to S2-134377. |
| S2‑134109 | 23.401 CR2603R3: Introducing UE Power Saving Mode | Ericsson | This was reviewed and a number of clarifications requested. The related CRs were also reviewed. This was revised off-line in S2-134378 Revision of S2-133648. Revised to S2-134378. |
| S2‑134110 | 23.060 CR1814R3: Introducing UE Power Saving Mode | Ericsson | This required similar handling as S2-134108 and was discussed off-line and revised in S2-134377 Revision of S2-133649. Revised to S2-134379. |
| S2‑134111 | CS/PS Coordination in GERAN shared network | Ericsson | way forward? Not Handled |
| S2‑134112 | 23.401 CR2623R4: Reporting ULI and TimeZone at Network-initiated bearer release related procedures | Ericsson | Revision of S2-133744. Not Handled |
| S2‑134113 | Support of inbound mobility to a shared CSG cell | TeliaSonera | Noted in parallel sessions |
| S2‑134114 | 23.251 CR0097: Support of inbound mobility to a shared CSG cell | TeliaSonera | Revised in parallel sessions to S2-134320. |
| S2‑134115 | Further clarifications to identities handling and way forward | Alcatel-lucent, Alcatel-Shanghai Bell | This was discussed and revised off-line to remove section 8 and take comments into account in S2-134452 Revised to S2-134452. |
| S2‑134116 | Comparison of polling vs. advertisement based methods for discovery | Alcatel lucent, Alcatel-Lucent Shanghai Bell | Not Handled |
| S2‑134117 | IP version in ProSe and in one-to-many communications | Alcatel lucent | This was discussed and clarification on the discriminator function was requested. This was discussed off-line and revised in S2-134354 Revised to S2-134354. |
| S2‑134118 | GCSE Roaming | ALU, Alcatel-Lucent shanghai bell, NSN, Qualcomm | It was clarified that the Mz interface is between BMSCs. There were a number of issues raised and requests to clarify and shorten the proposal. Ericsson commented that it is possible for all users to be in the VPLMN and for a few users to roam out of the |
| S2‑134119 | Direct one-to-many communications Authorization: rationale | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | Alcatel-Lucent clarified that this is will require authentication if required by the network. Intel asked whether this would be a 'once for all' authorization or a per session authorization. Alcatel-Lucent commented that there could be a large number of a |
| S2‑134120 | Evaluation of RAN user plane congestion reporting solutions (GTP-U, off-path and combined on-path and off-path) | NTT DOCOMO, Intel | evaluates 1.5.1, 1.5.3, 1.5.4, 1.5.5) Merge? Not Handled |
| S2‑134121 | Co-existence of ANDSF-based and RAN-based Traffic Steering | Motorola Mobility | Not Handled |
| S2‑134122 | [DRAFT] Reply LS on interaction of oneM2M with Underlying Networks | NEC | Response to S2-133873. Not Handled. The incoming LS was Postponed to meeting #101 |
| S2‑134123 | Make-before break' service continuity during MBMS and unicast switching | NEC | Not Handled |
| S2‑134124 | GCSE Call set up conclusions | Qualcomm Inc, NSN, Alcatel-Lucent | This was discussed and revised off-line in S2-134461 Revised to S2-134461. |
| S2‑134125 | GCSE Service Continuity conclusions | Qualcomm Inc, NSN, Alcatel-Lucent | This was discussed and it was considered too late to introduce new mechanism proposals, but this could be considered if no other solutions are found to be acceptable. This was further discussed off-line to determine if any can be agreed upon and was revis |
| S2‑134126 | RAN impacts and evaluation of Solution 1.5.1 | China Mobile, AT&T, NEC, Samsung, NSN | Ericsson raised some issues on what this is trying to solve and scalability statements made and added that the signalling mechanism is not designed for the use proposed here. There was extensive discussion of the proposals and this was further discussed o |
| S2‑134127 | [DRAFT] Reply LS on CN impacts in RAN WG2 solutions for WLAN/3GPP radio interworking | China Mobile | Response to S2-133917. Noted in parallel sessions |
| S2‑134128 | Proposed way forward on EPC-level discovery and EPC support for WLAN direct communication | Intel, Sony, CATT, III, TeleCommunication Systems, Broadcom Corporation, ITRI, Acer, NEC, MediaTek, ETRI, KPN | This was merged in the drafting session with S2-134040 into S2-134356. S2-134128 and S2-134040 merged in parallel sessions to S2-134356. |
| S2‑134129 | 23.401 CR2588R1: EPC-level discovery and EPC support for WLAN direct communication | Intel, Sony, CATT, III, TeleCommunication Systems, Broadcom Corporation, ITRI, Acer, NEC, MediaTek, ETRI, KPN | This was revised in the drafting session into S2-134357. Revision of S2-132721. Revised in drafting sessions to S2-134357. |
| S2‑134130 | 23.402 CR1217: EPC support for WLAN direct communication | Intel, Sony, CATT, III, TeleCommunication Systems, Broadcom Corporation, ITRI, Acer, NEC, MediaTek, ETRI, KPN, Motorola Mobility | It was considered premature to add this to the TS at this point in time. Intel commented that work should concentrate on P-CRs to the TR to make it ready for transfer to the TS via CRs when agreements have been reached. It was decided to create a P-CR to |
| S2‑134131 | Consolidated description of solutions for ProSe Discovery using ProSe Communication capability (D3, D6, D7) | Intel, Alcatel-Lucent | Not Handled |
| S2‑134132 | Interim conclusion on Relay for Public Safety ProSe | Intel, Alcatel-Lucent | There was some discussion and it was decided to review other contribution to get a better overview of the issues. The SA WG2 Chairman held an informal 'show of hands' to determine support for approaches B, C and D as listed in S2-134185. Approach Can 'li |
| S2‑134133 | A way forward on direct communication one-to-many: a synthesis of proposals | General Dynamics Broadband UK | It was clarified that the D2B will map 1 to 1 in the Radio layer, but this does not put any requirements upon the radio layer itself. Qualcomm suggested aligning the terminology woth the solutions and conclusions papers, in particular, the use of 'offline |
| S2‑134134 | Proposed updates to the common approach in the TR | General Dynamics Broadband UK | There were a number of issues raised and this was left for consideration of other contributions. It was decided to also capture the endorsed options of S2-134152 and this was revised accordingly in S2-134460 Revised to S2-134460. |
| S2‑134135 | Common architecture in current network based solutions | T-Mobile USA | Noted in parallel sessions |
| S2‑134136 | New IMS WebRTC Interworking Solution | T-Mobile USA INC, Deutsche Telecom AG | Not Handled |
| S2‑134137 | New IMS WebRTC Interworking Solution (Procedures) | T-Mobile USA INC, Deutsche Telecom AG | Not Handled |
| S2‑134138 | Possible way forward on ProSe Identifiers | Motorola Solutions | It was commented that it should not be assumed that things can be simply agreed in SA WG2 and passed to SA WG3 for encryption, as there are cases where this will not be simple to do. The SA WG2 Chairman commented that there were no concrete proposals whic |
| S2‑134139 | GCSE reliability support on the GC2 interface | Motorola Solutions | Not Handled |
| S2‑134140 | Need for EPC to be group aware (group management) for GCSE | U.S. Department of Commerce | EADS asked whether when a Unicast downlink is for a Group, the whole Group be dropped. The U.S. Department of Commerce clarified that the intention is to drop the link for the individual user. Qualcomm commented that the main need is for users using Unica |
| S2‑134141 | Group Management for GCSE_LTE | U.S. Department of Commerce | This required further discussion off-line to determine what can be taken into the evaluation section of the TR. This was revised off-line in S2-134349 Revised to S2-134349. |
| S2‑134142 | Evaluation on Solution R9 and partial conclusion on Relay for Public Safety ProSe | LG Electronics | There were a number of issues highlighted and this was left for off-line discussion and was revised in S2-134464 Revised to S2-134464. |
| S2‑134143 | Solution on ProSe Relay Selection and Re-selection | LG Electronics | Not Handled |
| S2‑134144 | - | Qualcomm Incorporated | LATE DOC: [WITHDRAWN] |
| S2‑134145 | [DRAFT] Reply LS to RAN WG2 LS on CN impacts in RAN WG2 solutions for WLAN/3GPP radio interworking (S2-133917/R2-133697) | Qualcomm Incorporated | Response to S2-133917. Noted in parallel sessions |
| S2‑134146 | 23.402 CR1218: Adding WLAN Load thresholds to ISRP | Intel, AT&T, Cisco, Broadcom Corporation | Not Handled |
| S2‑134147 | [DRAFT] Reply LS on CN impacts in RAN WG2 solutions for WLAN/3GPP radio interworking | Intel, AT&T, Broadcom Corporation | Response to S2-133917. Noted in parallel sessions |
| S2‑134148 | Discussion on applicability of T5-based SDT solution | Qualcomm Incorporated, Ericsson, Alcatel-Lucent | This was reviewed and other contributions were considered. This was later noted. Noted |
| S2‑134149 | 23.401 CR2603R4: Introducing UE Power Saving Mode | ??? Qualcomm Incorporated | There were some issues raised and clarifications and alignments were needed. This was further discussed off-line and merged into S2-134378. Revision of S2-133648. Merged into S2-134378 |
| S2‑134150 | 23.060 CR1814R4: Introducing UE Power Saving Mode | ???, Qualcomm Incorporated | There were some issues raised and clarifications and alignments were needed. This was further discussed off-line and merged into S2-134379. Revision of S2-133649. Merged into S2-134379 |
| S2‑134151 | Initial UPCON Conclusion Text for CN-Based Solutions | KDDI, NTT DoCoMo, China Unicom, AT&T, Bell Mobility | This was revised off-line into S2-134463. Revised into S2-134463. |
| S2‑134152 | GCSE Service Information Exchange | Qualcomm Inc | EADS asked why other another type of identifier is needed over the current identifier for MBMS. Alcatel-Lucent asked what the eMBMS USD information is. Qualcomm clarified that this is the XML information specified for subscription information transfer. Th |
| S2‑134153 | Proposed evaluation | Allot,Openet,Cisco,Oracle,ALU,ALU- ShanghaiBell,ChinaTelecom,SPRINT,ZTE,Broadcom,KDDI,ChinaUnicom,USCellular,Comverse,Bell-Mobility,Hitachi,Sandvinen,Amdocs | There were a number of comments and issues raised. It was decided to return to this when other proposals have been reviewed and attempt to merge acceptable parts of the proposals together. This was further discussed off-line and revised in S2-134375 Revis |
| S2‑134154 | Discussion on LS (from C1/C1-134519) on CSFB priority call handling in a network supporting Multimedia Priority Service | NSN | More discussion and evaluation needed. Noted in parallel sessions |
| S2‑134155 | [DRAFT] Reply LS on CSFB priority call handling in a network supporting Multimedia Priority Service | NSN | Response to S2-133899. Not Handled |
| S2‑134156 | 23.272 CR0912: CSFB priority call handling in a network supporting Multimedia Priority Service | NSN | Not Handled |
| S2‑134157 | 23.272 CR0913: CSFB priority call handling in a network supporting Multimedia Priority Service | NSN | Not Handled |
| S2‑134158 | 23.272 CR0914: CSFB priority call handling in a network supporting Multimedia Priority Service | NSN | Not Handled |
| S2‑134159 | 23.272 CR0904R1: Alignment of CSFB/emergency and eMPS (priority service) | NSN, Huawei | Revision of S2-133426. Revised in parallel sessions to S2-134329. |
| S2‑134160 | 23.272 CR0905R1: Alignment of CSFB/emergency and eMPS (priority service) | NSN, Huawei | Revision of S2-133427. Revised in parallel sessions to S2-134330. |
| S2‑134161 | Generic Pre-established MBMS bearer for GCSE | NSN | Not Handled |
| S2‑134162 | Group management and user interaction for GCSE | NSN, Qualcomm Inc, ALU | There was some discussion on this proposal. Ericsson suggested that the scope of the work should be reviewed and the SA WG3 security aspects should not be considered in the SA WG2 study. Alcatel-Lucent considered this as a step towards a solution and sugg |
| S2‑134163 | Common unicast uplink GBR for GCSE | NSN | Not Handled |
| S2‑134164 | 23.272 CR0902R1: CS MO indication to VLR via SGs | NSN, Ericsson | This was reviewed and approved. Revision of S2-133423. Wait for CT WG1 outcome? This CR was agreed |
| S2‑134165 | 23.272 CR0903R1: CS MO indication to VLR via SGs | NSN, Ericsson | This was reviewed and approved. Revision of S2-133424. This CR was agreed |
| S2‑134166 | eSaMOG WLCP Transport Layer Considerations and Comparisons | ZTE, Broadcom Corporation, KDDI, Samsung, LG | Noted in parallel sessions |
| S2‑134167 | Evaluation on CN-based mitigation for RAN congestion | Huawei, Hisilicon | This was reviewed and it was decided that further information from other WGs is needed before agreeing to this. This proposal was then noted. Noted |
| S2‑134168 | Discussion paper for comparison on WebRTC UE-to-Network interface signalling protocols | Huawei | Noted in parallel sessions |
| S2‑134169 | Clarification on the usage of SIP Digest in registration procedure | Huawei, Hisilicon | Not Handled |
| S2‑134170 | 23.272 CR0915: Congestion control on the SGs interface via the overload start message | Huawei, Hisilicon, | Not Handled |
| S2‑134171 | Mobile Terminated call optimization in case of Ultra-Flash CSFB(SRVCC based CSFB) | China Unicom, Huawei, Hisilicon | Not Handled |
| S2‑134172 | Update to solution I9 | InterDigital Communications | Not Handled |
| S2‑134173 | Proposal for consolidating allocation of ProSe Identifiers solutions for direct discovery in network-authorized mode | InterDigital Communications, Telecom Italia | This was reviewed and it was agreed to try to clarify the context of the tables to clearly identify what is being compared. Qualcomm suggested merging parts of S2-134057. This was revised off-line and merged with S2-134057 in S2-134368 Merged with S2-1340 |
| S2‑134174 | 23.401 CR2633: ECGI based location reporting for EPC-level ProSe discovery | InterDigital Communications, ... | Not Handled |
| S2‑134175 | Addressing FFS issues in solution D14 | InterDigital Communications | Not Handled |
| S2‑134176 | 23.402 CR1219: WLCP over UDP | ZTE, LG Electronics, Samsung, Broadcom, KDDI | There was no agreement on the way forward and this was noted. Noted |
| S2‑134177 | Removal of extended DRX cycle option for UEPCOP | NSN, Nokia Corporation | This was reviewed and approved. The Rapporteur was asked to only make the change in this document on the latest version of the TR. Approved |
| S2‑134178 | 23.401 CR2594R5: Core Network assisted eNodeB parameters tuning | NSN, Alcatel-Lucent?, Alcatel-Lucent Shanghai Bell?, NEC?, Ericsson? | This was reviewed and discussed. It was decided to discuss the contributions on this topic off-line to try to capture agreeable parts of each. This was revised off-line in S2-134366 Revision of S2-134006. Revised to S2-134366. |
| S2‑134179 | MME triggered S1 handover | NSN | Noted in parallel sessions |
| S2‑134180 | 23.203 CR0862: Activate PCC function per UE based on subscription information | China Unicom | no CR# in cover. Revised in parallel sessions to S2-134387. |
| S2‑134181 | 23.682 CR0077R4: Introducing UE Power Saving Mode | Huawei, HiSilicon, ORANGE, ZTE | There were some issues with this proposal and it was noted. Revision of S2-133647. Noted |
| S2‑134182 | 23.401 CR2603R5: Introducing UE Power Saving Mode | Huawei, HiSilicon, ORANGE, ZTE | Alcatel-Lucent supported the first change but did not support the second change to use separated active timers. Huawei commented that the second change is needed to make the first change efficient as the UE may otherwise need to wait a long time for a TAU |
| S2‑134183 | 23.060 CR1814R5: Introducing UE Power Saving Mode | Huawei, HiSilicon, ORANGE, ZTE | This was covered by other proposals and was noted. Revision of S2-133649. Noted |
| S2‑134184 | New ProSe communication solution | ZTE Corporation | Not Handled |
| S2‑134185 | Evaluation of ProSe Relay | ZTE Corporation | This was considered a useful evaluation and ZTE were thanked for providing this. This was then noted. Noted |
| S2‑134186 | Update Solution 1 to Clarify PCRF Usage | ZTE | Not Handled |
| S2‑134187 | Discussion on PCRF usage in Group Communication | ZTE | Not Handled |
| S2‑134188 | Remove the possibility of sharing eMBMS bearer between GCSE groups | ZTE | Not Handled |
| S2‑134189 | ProSe ID clarification | ZTE Corporation | Not Handled |
| S2‑134190 | New ProSe discovery solution | ZTE Corporation | Not Handled |
| S2‑134191 | Overview of normative changes for D15 (EPC-level ProSe discovery) | LG Electronics | Not Handled |
| S2‑134192 | 23.682 CR0078R3: Device trigger recall and replace | LG Electronics, Intel, Acision, Ericsson | Some clarifications to the text had been received off-line which should be added. Alcatel-Lucent asked whether the SCS should be authorized to send replace/recall requests if it has submitted the trigger. This should be checked off-line. This was revised |
| S2‑134193 | 23.401 CR2605R3: Addition of a note addressing the behavior of network side during inter-RAT 3GPP PS Handover | Huawei, Hisilicon, CATT?, LG Electronics?, Qualcomm Incorporated? | Revision of approved S2-133699. Not Handled |
| S2‑134194 | 23.060 CR1829: Modification to SGSN Initiated PDN connection Deactivation Procedure using S4 for WORM | Huawei, Hisilicon | Not Handled |
| S2‑134195 | Consideration on starvation problem of RAN-based solution | LG Electronics | There were questions on the advantage of adding this to the TR at this stage as this should be covered by the evaluation and will then need to be removed again. There was little support for this proposal and it was noted. Noted |
| S2‑134196 | Evaluation table for IMS WebRTC | ZTE | Noted in parallel sessions |
| S2‑134197 | Discussion for the Network-based WebRTC architecture | ZTE | [WITHDRAWN] |
| S2‑134198 | Proposed ProSe Discovery conclusions | Deutsche Telekom | This was briefly discussed and it was agreed that other contributions will cover this proposal. This was merged into S2-134358. Merged with S2-133393 and S2-134207 into S2-134358. |
| S2‑134199 | Overview of normative changes for the Small Data Service | Huawei, HiSilicon, Intel, China Unicom, China Telecom, China Mobile, ZTE, LG Electronics, ITRI, Broadcom Corporation, NSN, KPN, Silver Spring Networks, InterDigital, Sierra Wireless, HTC, KT Corp, III, CATT, Telecom Italia, Sony, Acision, ORANGE, NEC | Not Handled |
| S2‑134200 | Enhancement and evaluation of solution 2.2 | Huawei, Hisilicon | enhances solution 6.1.5.2. Not Handled |
| S2‑134201 | Cover sheet for TR 23.843 for approval at TSG SA | Huawei, Hisilicon | For e-mail approval. rev2 agreed. Revised to S2-134582. |
| S2‑134202 | Considerations on support of dedicated CNs | Huawei, HiSilicon | Noted in parallel sessions |
| S2‑134203 | 23.401 CR2598R5: PGW and SGW Charging alignment in downlink | Huawei, Ericsson, Alcatel Lucent, Cisco, Verizon | Revision of approved S2-133855. Not Handled |
| S2‑134204 | Evaluation on policy based congestion mitigation | NEC | There were a number of issues raised and the impacts and evaluation parts should be separated into their proper places. Allot Communications commented that this is not a stand-alone solution. The SA WG2 Chairman replied that parts of this can be taken out |
| S2‑134205 | Applicability of static congestion mitigation policies | NEC | Not Handled |
| S2‑134206 | PMIP variant of solution 1.5.1 (conveying RCI in the user plane) | NEC | Resubmission of S2-133487. solution 1.5.1 PMIP S5/S8 aspects merge with S2-134090? Not Handled |
| S2‑134207 | ProSe discovery conclusions | Telecom Italia | This was briefly discussed and it was agreed that other contributions will cover this proposal. This was merged into S2-134358. Merged with S2-133393 and S2-134198 into S2-134358. |
| S2‑134208 | Discussion of LS from RAN WG2 on WLAN/3GPP interworking | BlackBerry UK Ltd. | Noted in parallel sessions |
| S2‑134209 | 3GPP-WLAN interworking: Co-ordinating the work of RAN WG2 and SA WG2 | BlackBerry UK Ltd. | Not Handled |
| S2‑134210 | Evaluation criterion for ProSe UE-to-network relay | ITRI | The SA WG2 Chairman asked whether there was support for having the proposed criterion for the solution evaluations. Ericsson commented that this can be added but it needs to made clear that meeting the criterion should not be a prerequisite for accepting |
| S2‑134211 | Exception sheet for UPCON | NEC | Time budget estimates should be discussed over the e-mail following this meeting. This was revised to improve the text in S2-134502 Revised to S2-134502. |
| S2‑134212 | Exception sheet for MTCe-UEPCOP | Ericsson | Revised to S2-134466. |
| S2‑134213 | 23.167 CR0252: Addition of essential E-CSCF and IBCF functionality | NTT, NTT DOCOMO, Deutsche Telekom? | Revised in parallel sessions to S2-134324. |
| S2‑134214 | 23.167 CR0253: Addition of essential E-CSCF and IBCF functionality | NTT, NTT DOCOMO, Deutsche Telekom? | Revised in parallel sessions to S2-134325. |
| S2‑134215 | 23.167 CR0254: Addition of essential E-CSCF and IBCF functionality | NTT, NTT DOCOMO, Deutsche Telekom? | Revised in parallel sessions to S2-134326. |
| S2‑134216 | 23.167 CR0255: Addition of essential E-CSCF and IBCF functionality | NTT, NTT DOCOMO, Deutsche Telekom? | Revised in parallel sessions to S2-134327. |
| S2‑134217 | 23.228 CR1046: Addition of IBCF functionality for emergency session | NTT, NTT DOCOMO | Not Handled |
| S2‑134218 | 23.228 CR1047: Addition of IBCF functionality for emergency session | NTT, NTT DOCOMO | Not Handled |
| S2‑134219 | 23.228 CR1048: Addition of IBCF functionality for emergency session | NTT, NTT DOCOMO | Not Handled |
| S2‑134220 | 23.228 CR1049: Addition of IBCF functionality for emergency session | NTT, NTT DOCOMO | Not Handled |
| S2‑134221 | 23.228 CR1050: Addition of IBCF functionality for emergency session | NTT, NTT DOCOMO | Not Handled |
| S2‑134222 | Updates to Solution C7 | General Dynamics Broadband UK | [WITHDRAWN] |
| S2‑134223 | User location information for trusted WLAN | Cisco | Noted in parallel sessions. Usage of Civic Location is endorsed. |
| S2‑134224 | WLAN load thresholds in ISRP | Cisco, Intel, AT&T, Broadcom | Noted in parallel sessions |
| S2‑134225 | WLAN Selection Issues due to conflicting ANDSF and RAN rules | Cisco | Noted in parallel sessions |
| S2‑134226 | Introducing PCC rules with validity conditions | Cisco, Telecom Italia, AT&T, ORANGE, Verizon | Noted in parallel sessions |
| S2‑134227 | 23.203 CR0863: Introducing PCC rules with validity conditions | Cisco, Telecom Italia, AT&T, ORANGE, Verizon | Revised in parallel sessions to S2-134388. |
| S2‑134228 | Deferred Delivery of Content | Cisco, AT&T | enhances solution 6.1.5.1. Not Handled |
| S2‑134229 | Updates to ProSe Discovery solution D11 | Broadcom Corporation | Not Handled |
| S2‑134230 | Reply LS on providing Charging Characteristics to TDF | ORANGE | This was reviewed off-line and revised in S2-134343 Response to S2-133921. The SA WG2 Chairman proposed to postpone this LS. Revised to S2-134343. |
| S2‑134231 | 23.402 CR1220: Error code during WLCP procedure : NSWO Fallback and NSWO Prerequisite | ORANGE | Not Handled |
| S2‑134232 | 23.228 CR1051: Correction of inconsistency in proactive transcoding support | ORANGE | Revised in parallel sessions to S2-134384. |
| S2‑134233 | 23.228 CR1052: Correction of inconsistency in proactive transcoding support | ORANGE | Revised in parallel sessions to S2-134337. |
| S2‑134234 | 23.228 CR1053: Annex N scope alignment with stage 3 | ORANGE | related stage 3 is normative? An alignement?. Agreed in parallel sessions. This CR was agreed |
| S2‑134235 | 23.228 CR1054: Annex N scope alignment with stage 3 | ORANGE | Agreed in parallel sessions. This CR was agreed |
| S2‑134236 | 23.228 CR1055: Annex N scope alignment with stage 3 | ORANGE | Agreed in parallel sessions. This CR was agreed |
| S2‑134237 | Common architecture for IMS_WebRTC | ORANGE | Noted in parallel sessions |
| S2‑134238 | 23.228 CR1056: Mapping from user location to Geographical Identifier | ORANGE | A description of the functional entities should be found in TS 23.002? Noted in parallel sessions |
| S2‑134239 | 23.228 CR1057: Geographical Identifier for fixed access | ORANGE | Revised in parallel sessions to S2-134390. |
| S2‑134240 | Clarification on downlink packet marking for PMIP based S5/S8 | NTT DOCOMO | solution 6.2.1 and 6.2.2 PMIP S5/S8 aspects merge with S2-134009? Not Handled |
| S2‑134241 | Completion and evaluation of scenario 1 | Vodafone | This paper provoked a lot of discussion over the issues raised for processing the data in the scheduled time and the amount of frame decoding that will need to be done by the UE and the inherent speech latency introduced. This was further discussed off-li |
| S2‑134242 | Completion and evaluation of scenario 2, and conclusions update | Vodafone | There was some discussion and questions for clarification and additional text in the evaluation to explain why some data is more sensitive to delay than others was requested. This was further discussed off-line and revised in S2-134450 Revised to S2-13445 |
| S2‑134243 | Updates to UE to NW Relay following response LSs | Vodafone | LATE DOC: Rx 05/11, 16:05. Not Handled |
| S2‑134244 | PSAP callback detection requirement in the UE | Nokia Corporation, BlackBerry UK Ltd., NSN | There was some discussion over whether this functionality which had been removed from Rel-12 should be reintroduced into Rel-12 after all. Nokia Corporation commented that there was a LS proposal for this in S2-134245 , which proposes CT WG1 complete thei |
| S2‑134245 | [DRAFT] LS on UE requirements for PSAP callback | Nokia Corporation, BlackBerry UK Ltd. | Alcatel-Lucent commented that the call requirements are still in other TSs so the requirements for this already exist. Nokia Corporation replied that this is general requirements for callback but alignment with stage 3 can only be done via alignment when |
| S2‑134246 | 23.272 CR0861R3: Call Independent supplementary services with CSFB | Nokia Corporation | Resubmission of S2-131954. Revised in parallel sessions to S2-134385. |
| S2‑134247 | Power Saving Mode optimisation | Nokia Corporation | There were a number of issues raised with this and no agreement could be reached. This was then noted. Noted |
| S2‑134248 | One-to-many communication with centralised radio resource management and direct UE-to-UE communication | Intel | LATE DOC: Rx 05/11, 16:15. Not Handled |
| S2‑134249 | Identities for EPC-level discovery and EPC support for WLAN direct communication | Intel | Not Handled |
| S2‑134250 | Update of D4 call flows | Intel | Not Handled |
| S2‑134251 | Exception sheet for GCSE_LTE | NSN | Revised to S2-134501. |
| S2‑134252 | Exception sheet for eSaMOG | ZTE | Revised to S2-134467. |
| S2‑134253 | Reply LS on End-to-end QoS handling of MTSI | Alcatel-Lucent | Response to S2-133877. LATE DOC: Rx 07/11 17:50. Not Handled |
| S2‑134254 | LS from SA WG4: LS on Improved end-to-end QoS handling of MTSI | SA WG4 (S4-131308) | This LS was not handled and was postponed to meeting #101. This LS was not handled and was postponed to meeting #101. |
| S2‑134255 | LS from SA WG4: Reply LS on new work item on IMS support for RTP / RTCP transport multiplexing | SA WG4 (S4-131309) | This LS was not handled and was postponed to meeting #101. Response to S2-133825 (S2#99). This LS was not handled and was postponed to meeting #101. |
| S2‑134256 | LS from SA WG4: LS Response on Applicability of WI MI-MooD to Service Continuity Requirements for Group Communications | SA WG4 (S4-131318) | This LS was postponed to meeting #101. |
| S2‑134257 | LS from SA WG4: LS on the UE capabilities regarding support of simultaneous MBMS bearer reception | SA WG4 (S4-131406) | This LS was not handled and was postponed to meeting #101. This LS was not handled and was postponed to meeting #101. |
| S2‑134258 | 23.203 CR0849R4: Alignment of Fixed Broadband Access Annex with main specification body | Ericsson, Allot Communications, Huawei | Revision of S2-134007. Revised in parallel sessions to S2-134307. |
| S2‑134259 | WebRTC joint architecture proposal | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, China Mobile, Ericsson, Huawei, NSN, | Revision of S2-134036. Revised in parallel sessions to S2-134266. |
| S2‑134260 | 23.402 CR1180R2: IP address Allocation and DHCP Function | Huawei, Hisilicon | Revision of S2-133981. Revised in parallel sessions to S2-134419. |
| S2‑134261 | 23.402 CR1177R4: Initial attach and handover attach call flows for single-connection mode | Ericsson, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Qualcomm Incorporated | Revision of S2-134020. Revised in parallel sessions to S2-134420. |
| S2‑134262 | 23.402 CR1207R1: Detach in WLAN for Multi-Connection Mode for GTP based S2a | China Telecom, Huawei, Hisilicon | Revision of S2-133982. Agreed in parallel sessions. This CR was agreed |
| S2‑134263 | 23.402 CR1200R1: Bearer model for PDN connectivity service with PMIP based S2a | KDDI, Broadcom Corporation | Revision of S2-133937. Revised in parallel sessions to S2-134288. |
| S2‑134264 | 23.402 CR1201R1: Detach Procedure in WLAN on PMIP S2a for Multi-connection Mode | KDDI, Broadcom Corporation | Revision of S2-133938. Revised in parallel sessions to S2-134281. |
| S2‑134265 | WebRTC Solution 7 Update | Broadcom Corporation | Revision of S2-133904. Revised in parallel sessions to S2-134424. |
| S2‑134266 | WebRTC joint architecture proposal | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, China Mobile, Ericsson, Huawei, NSN, | Revision of S2-134259. Revised in parallel sessions to S2-134425. |
| S2‑134267 | 23.203 CR0856R1: AAA-based accounting for Fixed Broadband Network | Huawei, ORANGE | Revision of S2-133975. Revised in parallel sessions to S2-134434. |
| S2‑134268 | 23.402 CR1176R3: Access Network information reporting in case of a TWAN Access | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, China Telecom | Revision of S2-133928. Revised in parallel sessions to S2-134429. |
| S2‑134269 | 23.203 CR0842R2: Access Network information reporting in case of a TWAN Access | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, China Telecom | Revision of S2-133930. Revised in parallel sessions to S2-134430. |
| S2‑134270 | 23.228 CR1043R2: Access Network information reporting in case of a TWAN Access | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, China Telecom | Revision of S2-133929. Agreed in parallel sessions. This CR was agreed |
| S2‑134271 | Procedures for WebRTC joint architecture proposal | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | Revision of S2-134037. Revised in parallel sessions to S2-134426. |
| S2‑134272 | Cover Sheet for TR 23.701 presentation to TSG SA | China Mobile, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | Revision of S2-134076. Revised in parallel sessions to S2-134428. |
| S2‑134273 | LS to SA WG3 on Security aspects of IMS_WebRTC | SA WG2 | Revised in parallel sessions to S2-134427. |
| S2‑134274 | 23.401 CR2627R1: Introduction of ULI reporting at PCC area level | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | Revision of S2-133953. Revised to S2-134436. |
| S2‑134275 | 23.203 CR0853R1: Introduction of PCC area Event Reporting Function trigger | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | Revision of S2-133954. Revised to S2-134437. |
| S2‑134276 | 23.060 CR1826R1: Introduction of ULI reporting at PCC area level | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | Revision of S2-133955. Revised to S2-134438. |
| S2‑134277 | 23.401 CR2629R1: Introduction of ULI reporting only when the UE is in 'CONNECTED' state | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | Revision of S2-133965. Revised in parallel sessions to S2-134442. |
| S2‑134278 | 23.060 CR1827R1: Introduction of ULI reporting only when the UE is in 'CONNECTED' state | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | Revision of S2-133967. Revised to S2-134440. |
| S2‑134279 | 23.865 CR0008R1: Conclusions for Key Issue #9 | Motorola Mobility, Qualcomm Incorporated | Revision of S2-134042. Revised in parallel sessions to S2-134418. |
| S2‑134280 | [DRAFT] Reply LS on CN impacts in RAN WG2 solutions for WLAN/3GPP radio interworking | NSN, Nokia | Revision of S2-133925. Revised in parallel sessions to S2-134303. |
| S2‑134281 | 23.402 CR1201R2: Detach Procedure in WLAN on PMIP S2a for Multi-connection Mode | KDDI, Broadcom Corporation | Revision of S2-134264. Revised in parallel sessions to S2-134421. |
| S2‑134282 | 23.402 CR1205R1: UE initiated PDN connectivity request procedure in WLAN on S2a for Multi-Connection Mode | Huawei, Hisilicon, China Telecom | Revision of S2-133979. Revised in parallel sessions to S2-134422. |
| S2‑134283 | 23.402 CR1183R4: UE/TWAN requested PDN Disconnection Procedure in WLAN on GTP S2a for Multi-Connection Mode | CATT | Revision of S2-134065. Revised in parallel sessions to S2-134444. |
| S2‑134284 | 23.402 CR1202R1: PDN Connectivity Procedures in WLAN on PMIP S2a for Multi-connection Mode | KDDI, Broadcom Corporation | Revision of S2-133939. Agreed in parallel sessions. Revised to S2-134511. |
| S2‑134285 | 23.402 CR1209R1: Call flows for handover from WLAN to 3GPP | Ericsson | Revision of S2-134021. Agreed in parallel sessions. This CR was agreed |
| S2‑134286 | 23.402 CR1212R1: Handover in Multi-Connection Mode from 3GPP access to WLAN on GTP S2a | CATT | Revision of S2-134063. Agreed in parallel sessions. This CR was agreed |
| S2‑134287 | 23.402 CR1213R1: Handover procedure from 3GPP access to WLAN on PMIP S2a for Multi-connection Mode | KDDI, Broadcom Corporation | Revision of S2-134075. Agreed in parallel sessions. This CR was agreed |
| S2‑134288 | Bearer model for PDN connectivity service with PMIP based S2a | KDDI, Broadcom Corporation | Revision of S2-134263. [WITHDRAWN] |
| S2‑134289 | 23.203 CR0857R1: Corrections to handling of PCC rules with application identifier | Ericsson | More work is needed on this and the CR was noted. Revision of S2-134025. Agreed in parallel sessions. Noted |
| S2‑134290 | 23.203 CR0858R1: Corrections to handling of PCC rules with application identifier | Ericsson | More work is needed on this and the CR was noted. Revision of S2-134026. Agreed in parallel sessions. Noted |
| S2‑134291 | Proposed reply LS on bearer binding for the PCC rule with application identifier | Ericsson | More work is needed on this and the CR was noted. Revision of S2-134024. Noted |
| S2‑134292 | 23.203 CR0852R1: Clarification for application detection function of PCEF and TDF | China Mobile, Huawei | Revision of S2-133922. Agreed in parallel sessions. This CR was agreed |
| S2‑134293 | 23.060 CR1800R7: Definition for a valid state of the TFT setting | Ericsson | Revision of S2-134099. Revised in parallel sessions to S2-134433. |
| S2‑134294 | 23.060 CR1801R5: Definition for a valid state of the TFT setting | Ericsson | Revision of S2-134100. Agreed in parallel sessions. This CR was agreed |
| S2‑134295 | [DRAFT] Reply LS on uplink packet filters | SA WG2 | This was reviewed and revised to remove draft and add the correct attachment in S2-134445 Response to S2-133894. Revised in parallel sessions to S2-134445. |
| S2‑134296 | 23.203 CR0845R3: Correction of PCRF discovery and selection in the presence of NAT devices and overlapping address space | China Mobile, Huawei, ZTE, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | Revision of S2-133923. Agreed in parallel sessions. This CR was agreed |
| S2‑134297 | 23.203 CR0846R3: Correction of PCRF discovery and selection in the presence of NAT devices and overlapping address space | China Mobile, Huawei, ZTE, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | Revision of S2-133924. Agreed in parallel sessions. This CR was agreed |
| S2‑134298 | [Draft] PCC with NAT in roaming scenarios | SA WG2 | For e-mail approval. Agreed. Revised to remove 'draft' in S2-134576. |
| S2‑134299 | 23.402 CR1191R4: WLAN access network selection based on WLANSP rules | Motorola Mobilty, AT&T??, Qualcomm Incorporated, Intel??, Broadcom Corporation??, NSN??, Samsung?? | Revision of S2-134043. Revised in parallel sessions to S2-134300. |
| S2‑134300 | 23.402 CR1191R5: WLAN access network selection based on WLANSP rules | Motorola Mobilty, AT&T??, Qualcomm Incorporated, Intel??, Broadcom Corporation??, NSN??, Samsung?? | Revision of S2-134299. Revised in parallel sessions to S2-134416. |
| S2‑134301 | 23.402 CR1211R1: Update ANDSF information to support WLAN access network selection and WORM | Motorola Mobility, AT&T, Qualcomm Incorporated, Intel, NSN, Nokia, Samsung, LG Electronics | Revision of S2-134044. Agreed in parallel sessions. Merge of S2-133688 and S2-133698 from S2#099. This CR was agreed |
| S2‑134302 | 23.402 CR1190R4: UE procedures based on ANDSF information | Motorola Mobility, AT&T, Qualcomm Incorporated, Intel, Broadcom Corporation, NSN, Samsung, Nokia | Revision of S2-134045. Agreed in parallel sessions. This CR was agreed |
| S2‑134303 | Reply LS on CN impacts in RAN WG2 solutions for WLAN/3GPP radio interworking | SA WG2 | Revision of S2-134280. Agreed in parallel sessions. Approved |
| S2‑134304 | Editorial updates of TR 23.701 | China Mobile | This P-CR was created in the parallel session to capture the updates proposed by the rapporteur in S2-134056 Agreed in parallel sessions. Approved |
| S2‑134305 | 23.228 CR1045R1: Access Network information fetching in case of a TWAN Access-use of Sh | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, China Telecom | Revision of S2-133933. Revised in parallel sessions to S2-134432. |
| S2‑134306 | 23.402 CR1198R2: Access Network information fetching in case of a TWAN Access-use of Sh | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, China Telecom | Revision of S2-133932. Revised in parallel sessions to S2-134431. |
| S2‑134307 | 23.203 CR0849R5: Alignment of Fixed Broadband Access Annex with main specification body | Ericsson, Allot Communications, Huawei | Revision of S2-134258. Revised to S2-134435. |
| S2‑134308 | 23.002 CR0270R1: Introduction of Lgd | Cisco | Revision of S2-133906. Agreed in parallel sessions. This CR was agreed |
| S2‑134309 | 23.271 CR0400R4: Introduction of Lgd | Cisco, NSN | Revision of S2-133926. Agreed in parallel sessions. This CR was agreed |
| S2‑134310 | Discussion on Core Network Type Selection based on the Subscription Information | NTT DOCOMO | Revision of S2-133909. Should become a report on offline consolidation on this. Revised in parallel sessions to S2-134328. |
| S2‑134311 | 23.401 CR2623R4: Reporting ULI and TimeZone at Network-initiated bearer release related procedures | Alcatel-Lucent, AT&T, KPN, Sprint, KDDI, China Mobile, ORANGE | Revision of S2-133947. Agreed in parallel sessions. This CR was agreed |
| S2‑134312 | 23.203 CR0850R3: Reporting ULI and TimeZone at Network-initiated bearer release related procedures | Alcatel-Lucent, AT&T, KPN, Sprint, KDDI, China Mobile, ORANGE | Revision of S2-133948. Agreed in parallel sessions. This CR was agreed |
| S2‑134313 | End Marker Support for Handover Scenarios with SGW Relocation | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | Revision of S2-133958 [WITHDRAWN] |
| S2‑134314 | End Marker Support for Handover Scenarios with SGW Relocation | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | New CR for 23.402 PMIP. [WITHDRAWN] |
| S2‑134315 | Ultra-Flash CSFB (SRVCC based CSFB) | Huawei, Hisilicon | Revision of S2-134073. Noted in parallel sessions |
| S2‑134316 | 23.272 CR0911R1: Ultra-Flash CSFB (SRVCC based CSFB) | Huawei, HiSilicon,China Unicom | Revision of S2-134074. More discussion wanted. Noted in parallel sessions |
| S2‑134317 | Reply LS on interaction between SIPTO at the local network and the CS fallback service in connected mode | Huawei, Hisilicon, | This was revised to add the correct attachment, correct an editorial error and to remove 'draft' in S2-134546 Revision of S2-133973. Agreed in parallel sessions. Revised to S2-134546. |
| S2‑134318 | 23.401 CR2625R1: Rollback Behaviour in EPC during TAU/RAU rejection | Cisco | Revision of S2-133907. Revised in parallel sessions to S2-134396. |
| S2‑134319 | Rollback Behaviour in EPC during TAU/RAU rejection | NTT DOCOMO | New CR for 23.402 [WITHDRAWN] |
| S2‑134320 | 23.251 CR0097R1: Support of inbound mobility to a shared CSG cell | TeliaSonera | Revision of S2-134114. Revised in parallel sessions to S2-134397. |
| S2‑134321 | 23.060 CR1819R3: Core Network Operator selection origin | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, TeliaSonera | Revision of S2-133949. It is proposed to add this information in the cases when the SGSN has the information i.e. in all the cases except handover/relocation. These cases need CRs in a later meeting. Agreed in parallel sessions. This CR was agreed |
| S2‑134322 | 23.251 CR0096R3: Core Network Operator selection origin | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, TeliaSonera | Revision of S2-133950. Revised in parallel sessions to S2-134399. |
| S2‑134323 | [Draft] LS on Congestion control on Gs/SGs interface | SA WG2 | Preference to do more study; like under a WID. Noted in parallel sessions |
| S2‑134324 | 23.167 CR0252R1: Addition of essential E-CSCF and IBCF functionality | NTT, NTT DOCOMO, Deutsche Telekom? | Revision of S2-134313. Revised in parallel sessions to S2-134333. |
| S2‑134325 | 23.167 CR0253R1: Addition of essential E-CSCF and IBCF functionality | NTT, NTT DOCOMO, Deutsche Telekom? | Revision of S2-132414. Revised in parallel sessions to S2-134334. |
| S2‑134326 | 23.167 CR0254R1: Addition of essential E-CSCF and IBCF functionality | NTT, NTT DOCOMO, Deutsche Telekom? | Revision of S2-134215. Revised in parallel sessions to S2-134335. |
| S2‑134327 | 23.167 CR0255R1: Addition of essential E-CSCF and IBCF functionality | NTT, NTT DOCOMO, Deutsche Telekom? | Revision of S2-134216. Revised in parallel sessions to S2-134336. |
| S2‑134328 | Discussion on Core Network Type Selection based on the Subscription Information | NTT DOCOMO | Conclusions from the offline session - Full-set of functionality will be needed. - Multi-meeting work will be needed. -> (Potentially) a new WI for Rel-13 -> After SA WG2#100, NTT DOCOMO will initiate activities to progress the work / facilitate technical |
| S2‑134329 | 23.272 CR0904R2: Alignment of CSFB/emergency and eMPS (priority service) | NSN, Huawei | Revision of S2-134159. Agreed in parallel sessions. This CR was agreed |
| S2‑134330 | 23.272 CR0905R2: Alignment of CSFB/emergency and eMPS (priority service) | NSN, Huawei | Revision of S2-134160. Under other comments: R12 still open. Agreed in parallel sessions. This CR was agreed |
| S2‑134331 | - | Alcatel-Lucent | Revision of S2-133943. [WITHDRAWN] [WITHDRAWN] |
| S2‑134332 | 23.401 CR2626R1: Correction to Gn-SGSN behavior during MME to Gn-SGSN handover procedure | Cisco | Revision of S2-133927. Noted in parallel sessions |
| S2‑134333 | Addition of essential E-CSCF and IBCF functionality | NTT, NTT DOCOMO, Deutsche Telekom? | Revision of S2-134324 [WITHDRAWN] |
| S2‑134334 | Addition of essential E-CSCF and IBCF functionality | NTT, NTT DOCOMO, Deutsche Telekom? | Revision of S2-134325 [WITHDRAWN] |
| S2‑134335 | Addition of essential E-CSCF and IBCF functionality | NTT, NTT DOCOMO, Deutsche Telekom? | Revision of S2-134326 [WITHDRAWN] |
| S2‑134336 | Addition of essential E-CSCF and IBCF functionality | NTT, NTT DOCOMO, Deutsche Telekom? | Revision of S2-134327 [WITHDRAWN] |
| S2‑134337 | 23.228 CR1052R1: Correction of inconsistency in proactive transcoding support | ORANGE | Revision of S2-134233. Agreed in parallel sessions. This CR was agreed |
| S2‑134338 | Draft Agenda for SA WG2#100 | SA WG2 Chairman | There were a number of modifications introduced in this version and the agenda was reviewed and approved. Revision of S2-133916. Approved |
| S2‑134339 | Draft Report of SA WG2 meeting #99 | SA WG2 Secretary | Revision of S2-133867. Approved |
| S2‑134340 | New WID on Core Network Overload - User Location Information reporting improvements | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | Revision of S2-3952. Approved |
| S2‑134341 | [DRAFT] LS on UE requirements for PSAP callback | Nokia Corporation, BlackBerry UK Ltd. | Revision of S2-134245. For e-mail approval. Noted |
| S2‑134342 | 23.203 CR0855R1: Addition of charging characteristics transfer to TDF | Allot Communications, ORANGE | This required further clarification and was revised off-line in S2-134528 Revision of S2-133969. Revised to S2-134528. |
| S2‑134343 | Reply LS on providing Charging Characteristics to TDF | ORANGE | Revision of S2-134230. Revised to S2-134536. |
| S2‑134344 | Response LS on clarification on SIPTO at Local Network | SA WG2 | For e-mail approval. Approved |
| S2‑134345 | Enhancement on Control Plane based reporting for UTRAN | Intel, NTT DOCOMO | Reviewed and approved. Revision of S2-134089. Approved |
| S2‑134346 | Updates to the variant of the off-path solution | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Cisco, Allot Communications, China Telecom, KDDI, ZTE, Broadcom Corporation, AT&T | Ericsson asked about the semantics for network sharing for requests between operators and asked why a new node is needed in the architecture. Alcatel-Lucent replied that the RAN operator is responsible for the semantics. Ericsson asked to clarify this in |
| S2‑134347 | Clarification of the Congestion Reporting Solution Based on GTP-U | China Mobile, NEC, AT&T, NSN, Samsung | A number of changes were proposed and this was revised off-line in S2-134488 Revision of S2-134084. Revised to S2-134488. |
| S2‑134348 | Refinement of integrated on-path off-path solution (6.1.5.4) | KDDI, China Telecom, ZTE, AT&T, Bell Canada, Movik Networks, SoftBank Mobile, Sprint, Broadcom Corporation, NTT DoCoMo, NEC, Sandvine Technology, Samsung | Ericsson asked if there was a difference between off-path and on-path. ZTE clarified that there are differences in the reporting. This was revised in S2-134489 Revision of S2-133940. Revised to S2-134489. |
| S2‑134349 | Group Management for GCSE_LTE | U.S. Department of Commerce | EADS commented that there was no support in the solutions and architecture for Group Management. The tables were left FFS and U.S. Department of Commerce agreed to fill in the tables for the next meeting. Cisco suggested some items were either satisfied b |
| S2‑134350 | Group management and user interaction for GCSE | NSN, Qualcomm Inc, ALU | A number of clarifications were needed and this was discussed further off-line and revised in S2-134481 Revision of S2-134162. Revised to S2-134481. |
| S2‑134351 | Update of solution 7: Assign and Re-assign Priority and Pre-emption capability for the GC | Huawei, Hisilicon | A number of clarifications were needed and this was discussed further off-line and revised in S2-134482 Revision of S2-134068. Revised to S2-134482. |
| S2‑134352 | ProSe Communication 1-many decentralized mode- way forward | Qualcomm Incorporated, Alcatel-Lucent, Intel, U.S. Department of Commerce | This required more off-line discussion and was revised in S2-134529 Revision of S2-133991. Revised to S2-134529. |
| S2‑134353 | A way forward on direct communication one-to-many: a synthesis of proposals | General Dynamics Broadband UK | Alcatel-Lucent raised a concern with the note and this was removed and revised in S2-134530 Revision of S2-134133. Revised to S2-134530. |
| S2‑134354 | IP version in ProSe and in one-to-many communications | Alcatel lucent | Reviewed and approved Revision of S2-134117. Approved |
| S2‑134355 | Update for the solution C8 one-to-many communication | Ericsson | Reviewed and approved. Revision of S2-134029. Approved |
| S2‑134356 | Proposed way forward on EPC-level discovery and EPC support for WLAN direct communication | Intel, Sony, CATT, III, TeleCommunication Systems, Broadcom Corporation, ITRI, Acer, NEC, MediaTek, ETRI, KPN, LG Electronics | Some clarifications were needed and some terminology corrections were suggested. This was revised off-line in S2-134382 Merge of S2-134128 and S2-134040. Revised to S2-134382. |
| S2‑134357 | 23.401 CR2588R2: EPC-level discovery and EPC support for WLAN direct communication | Intel, Sony, CATT, III, TeleCommunication Systems, Broadcom Corporation, ITRI, Acer, NEC, MediaTek, ETRI, KPN, LG Electronics | There were a number of questions and clarifications provided. The parts of the HTC contribution (S2-134040) which can be included in this CR should be checked. This required further discussion off-line. . This CR was noted and a P-CR to 23.703 created in |
| S2‑134358 | ProSe Direct Discovery- way forward | Qualcomm Incorporated, Telecom Italia, Deutsche Telekom, | This was reviewed and further off-line discussion was needed. This was revised off-line in S2-134455 Merge of S2-133993, S2-134207 and S2-134198. Revised to S2-134455. |
| S2‑134359 | Exception sheet for IMS_WebRTC | Alcatel-Lucent, China Mobile, Alcatel-Lucent Shanghai Bell | This was reviewed and some changes were needed. This was revised off-line in S2-134498 Revision of S2-133999. Revised to S2-134498. |
| S2‑134360 | Exception sheet for NETLOC_TWAN | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | Some clean up was needed and this was revised in S2-134500 Revision of S2-134000. Revised to S2-134500. |
| S2‑134361 | [Draft] Minutes of joint RAN WG2/SA WG2 ad hoc on WLAN/3GPP Radio Interworking | ETSI MCC (RAN WG2 Secretary) | Noted |
| S2‑134362 | - | - | [WITHDRAWN] |
| S2‑134363 | - | - | [WITHDRAWN] |
| S2‑134364 | - | - | [WITHDRAWN] |
| S2‑134365 | - | - | [WITHDRAWN] |
| S2‑134366 | 23.401 CR2594R6: Core Network assisted eNodeB parameters tuning | NSN, Ericsson, Huawei | Alcatel-Lucent did not agree with the CN Generated Assistance Information text. There was some discussion on this and the proposal was further reviewed off-line and revised in S2-134473 Revision of S2-134178. Revised to S2-134473. |
| S2‑134367 | Evaluation of solution P2 on ProSe configuration | NEC | Qualcomm asked how the Annex relates with the solution to create a WLAN Direct Group already endorsed. NEC replied that solution can use the parameters or not and this has no impact. NSN suggested removing the Annex as it does not add anything to the solu |
| S2‑134368 | Proposal for consolidating allocation of ProSe Identifiers solutions for direct discovery in network-authorized mode | InterDigital Communications, Telecom Italia | It was decided to remove the table in section 7.2. Huawei commented that identities are only relevant to certain solutions. The title should be changed to clarify this. This was revised off-line in S2-134454 Merge of S2-134057 and S2-134173. Revised to S2 |
| S2‑134369 | Updated conclusions of extended DRX solutions | Ericsson | It was agreed to remove the last sentence and this was revised in S2-134468 |
| S2‑134370 | [DRAFT] LS on MTCe conclusions | SA WG2 | For e-mail approval. Noted |
| S2‑134371 | Conclusion on the QoS aspects of GCSE | Huawei, Hisilicon | A number of clarifications were needed and this was discussed further off-line and revised in S2-134483 Revision of S2-134069. Revised to S2-134483. |
| S2‑134372 | GCSE Roaming | ALU, Alcatel-Lucent shanghai bell, NSN, Qualcomm | Reviewed and approved. Revision of S2-134118. Approved |
| S2‑134373 | RAN impacts and evaluation of Solution 1.5.1 | China Mobile, AT&T, NEC, Samsung, NSN | Revision of S2-134126. Revised to S2-134540. |
| S2‑134374 | Off-Path reporting Evaluation | Ericsson | There were many issues raised and this was further discussed off-line and revised in S2-134490 Revision of S2-134011. Revised to S2-134490. |
| S2‑134375 | - | Allot,Openet,Cisco,Oracle,ALU,ALU- ShanghaiBell,ChinaTelecom,SPRINT,ZTE,Broadcom,KDDI,ChinaUnicom,USCellular,Comverse,Bell-Mobility,Hitachi,Sandvinen,Amdocs | Revision of S2-134153 [WITHDRAWN] |
| S2‑134376 | Evaluation of C-plane signalling for RAN user plane congestion reporting solution | NTT DOCOMO, Intel | Further changes were needed and this was revised off-line in S2-134491 Revision of S2-133903. Revised to S2-134491. |
| S2‑134377 | 23.682 CR0077R5: Introducing UE Power Saving Mode | Huawei, HiSilicon, Ericsson | Vodafone asked whether CT WG4 should be consulted on the [10] seconds for the message waiting flag. It was considered that as this is a note CT WG4 can inform SA WG2 of the value when they review the TS. Alcatel-Lucent suggested replacing the [10] with a |
| S2‑134378 | 23.401 CR2603R6: Introducing UE Power Saving Mode | Ericsson | This needed the same changes as S2-134379 and was revised in S2-134471 Merge of of S2-134109 and S2-134149. Revised to S2-134471. |
| S2‑134379 | 23.060 CR1814R6: Introducing UE Power Saving Mode | Qualcomm Incorporated, Ericsson | It was noted that the CR contained changes on changes and highlighting which should be removed. Vodafone commented that it should be clarified that the Active timer should be significantly longer than the TAU. This was discussed off-line and revised in S2 |
| S2‑134380 | 23.682 CR0078R4: Device trigger recall and replace | LG Electronics, Intel, Acision, Ericsson, Orange | Some grammatical errors were identified and changes on changes should be removed. This was revised in S2-134474 Revision of S2-134192. Revised to S2-134474. |
| S2‑134381 | Cover Sheet for TR 23.887 for approval at TSG SA | Intel | There was some discussion on the contentious issue and whether the objection should be listed there or not. This was further discussed off-line and revised in S2-134472 Revision of S2-133936. Revised to S2-134472. |
| S2‑134382 | Proposed way forward on EPC-level discovery and EPC support for WLAN direct communication | Intel, Sony, CATT, III, TeleCommunication Systems, Broadcom Corporation, ITRI, Acer, NEC, MediaTek, ETRI, KPN, LG Electronics | Further discussion was needed and this was revised off-line in S2-134535 Revision of S2-134356. Revised to S2-134535. |
| S2‑134383 | On EPC level discovery | Qualcomm Incorporated, Motorola Mobility | Intel commented that the reference to the location measurement accuracy should be removed. Qualcomm replied that this was not a simulation reference but a fact that the accuracy of location reporting will depend on the measurement methods that can be used |
| S2‑134384 | 23.228 CR1051R1: Correction of inconsistency in proactive transcoding support | ORANGE | Revision of S2-134232. Agreed in parallel sessions. This CR was agreed |
| S2‑134385 | 23.272 CR0861R4: Call Independent supplementary services with CSFB | Nokia Corporation | Revision of S2-134246. Revised in parallel sessions to S2-134400. |
| S2‑134386 | 23.203 CR0859R1: Delayed activation of PCC rules with Application ID | Ericsson | This CR was noted. Revision of S2-134027. Noted |
| S2‑134387 | 23.203 CR0862R1: Activate PCC function per UE based on subscription information | China Unicom | There were concerns with this and companies needed more time to consider this. This was then noted. Revision of S2-134180. Noted |
| S2‑134388 | 23.203 CR0863R1: Introducing PCC rules with validity conditions | Cisco, Telecom Italia, AT&T, ORANGE, Verizon | This was reviewed and approved. Revision of S2-134227. This CR was agreed |
| S2‑134389 | 23.216 CR0316R2: Returning back to E-UTRAN after SRVCC | Ericsson, Telecom Italia, AT&T?, Deutsche Telekom, China Mobile? | Revision of S2-134018. Revised in parallel sessions to S2-134401. |
| S2‑134390 | 23.228 CR1057R1: Geographical Identifier for fixed access | ORANGE | Revision of S2-134239. Revised in parallel sessions to S2-134405. |
| S2‑134391 | 23.401 CR2632R1: Modification on Inter-RAT Handover from UTRAN/GERAN to E-UTRAN | CATT | Revision of S2-134064. Agreed in parallel sessions. This CR was agreed |
| S2‑134392 | 23.167 CR0256: Addition of essential E-CSCF and IBCF functionality | NTT, NTTDOCOMO, Deutsche Telekom | Discrepancy between text and figure to be resolved by a CR for a later meeting. Revised in parallel sessions to S2-134395. |
| S2‑134393 | Reserved for Frank's parallel sessions | - | [WITHDRAWN] |
| S2‑134394 | 23.060 CR1830: Correction to Gn SGSN behavior during SRNS relocation procedure | Cisco | Agreed in parallel sessions. This CR was agreed |
| S2‑134395 | 23.167 CR0256R1: Addition of essential E-CSCF and IBCF functionality | NTT, NTTDOCOMO, Deutsche Telekom | Revision of S2-134392. [WITHDRAWN] |
| S2‑134396 | 23.401 CR2625R2: Rollback Behaviour in EPC during TAU/RAU rejection | Cisco | Revision of S2-134318. Agreed in parallel sessions.. This CR was agreed |
| S2‑134397 | 23.251 CR0097R2: Support of inbound mobility to a shared CSG cell | TeliaSonera | Revision of S2-134320. Agreed in parallel sessions.. This CR was agreed |
| S2‑134398 | Reply to LS (S2-133875/ S5-131380) on Charging aspects for Network Sharing (MOCN GWCN) | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | Revision of S2-133951. Revised in parallel sessions to S2-134403. |
| S2‑134399 | 23.251 CR0096R4: Core Network Operator selection origin | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, TeliaSonera | Revision of S2-134322. Revised in parallel sessions to S2-134402. |
| S2‑134400 | 23.272 CR0861R5: Call Independent supplementary services with CSFB | Nokia Corporation | Revision of S2-134385. Revised in parallel sessions to S2-134404. |
| S2‑134401 | 23.216 CR0316R3: Returning back to E-UTRAN after SRVCC | Ericsson, Telecom Italia, AT&T?, Deutsche Telekom, China Mobile? | Revision of S2-134389. Revised in parallel sessions to S2-134406. |
| S2‑134402 | 23.251 CR0096R5: Core Network Operator selection origin | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, TeliaSonera | Revision of S2-134399. Agreed in parallel sessions.. This CR was agreed |
| S2‑134403 | Reply to LS (S2-133875/ S5-131380) on Charging aspects for Network Sharing (MOCN GWCN) | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | Revision of S2-134398. Revised in parallel sessions to S2-134407. |
| S2‑134404 | 23.272 CR0861R6: Call Independent supplementary services with CSFB | Nokia Corporation | Revision of S2-134400. Revised in parallel sessions to S2-134408. |
| S2‑134405 | 23.228 CR1057R2: Geographical Identifier for fixed access | ORANGE | Revision of S2-134390. Agreed in parallel sessions. This CR was agreed |
| S2‑134406 | 23.216 CR0316R4: Returning back to E-UTRAN after SRVCC | Ericsson, Telecom Italia, AT&T?, Deutsche Telekom, China Mobile? | Revision of S2-134401. Agreed in parallel sessions. This CR was agreed |
| S2‑134407 | Reply to LS (S2-133875/ S5-131380) on Charging aspects for Network Sharing (MOCN GWCN) | SA WG2 | This needed further improvements and was discussed off-line and revised in S2-134534 Revision of S2-134403. Revised to S2-134534. |
| S2‑134408 | 23.272 CR0861R7: Call Independent supplementary services with CSFB | Nokia Corporation | This was reviewed and approved. Revision of S2-134404. This CR was agreed |
| S2‑134409 | - | - | [WITHDRAWN] |
| S2‑134410 | - | - | [WITHDRAWN] |
| S2‑134411 | - | - | [WITHDRAWN] |
| S2‑134412 | - | - | [WITHDRAWN] |
| S2‑134413 | - | - | [WITHDRAWN] |
| S2‑134414 | EPC-level discovery and EPC support for WLAN direct communication | Intel, Sony, CATT, III, TeleCommunication Systems, Broadcom Corporation, ITRI, Acer, NEC, MediaTek, ETRI, KPN, LG Electronics, HTC | This was reviewed and some issues were raised. This was further discussed off-line and revised in S2-134537 Generated from S2-134357. Revised to S2-134537. |
| S2‑134415 | - | Intel, Sony, CATT, III, TeleCommunication Systems, Broadcom Corporation, ITRI, Acer, NEC, MediaTek, ETRI, KPN, LG Electronics, HTC | Generated from S2-134357 [WITHDRAWN] |
| S2‑134416 | 23.402 CR1191R6: WLAN access network selection based on WLANSP rules | Motorola Mobilty, AT&T, Qualcomm Incorporated, Intel, Broadcom Corporation, NSN, Samsung, Nokia, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | Revision of S2-134300. Revised to S2-134510. |
| S2‑134417 | LS to CT WG1 on extensions to IEEE 802.11u Generic Comtainer | Motorola Mobility | Revised in parallel sessions to S2-134443. |
| S2‑134418 | 23.865 CR0008R2: Conclusions for Key Issue #9 | Motorola Mobility, Qualcomm Incorporated | Revision of S2-134279. Agreed in parallel sessions. This CR was agreed |
| S2‑134419 | 23.402 CR1180R3: IP address Allocation and DHCP Function | Huawei, Hisilicon | This was reviewed and approved. Revision of S2-134260.. This CR was agreed |
| S2‑134420 | 23.402 CR1177R5: Initial attach and handover attach call flows for single-connection mode | Ericsson, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Qualcomm Incorporated | This was reviewed and approved. Revision of S2-134261.. This CR was agreed |
| S2‑134421 | 23.402 CR1201R3: Detach Procedure in WLAN on PMIP S2a for Multi-connection Mode | KDDI, Broadcom Corporation | Revision of S2-134281. Agreed in parallel sessions. This CR was agreed |
| S2‑134422 | 23.402 CR1205R2: UE initiated PDN connectivity request procedure in WLAN on S2a for Multi-Connection Mode | Huawei, Hisilicon, China Telecom | This was reviewed and approved. Revision of S2-134282.. This CR was agreed |
| S2‑134423 | 23.203 CR0854R1: Introduction of ULI reporting only when the UE is in 'CONNECTED' state | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | This required further off-line discussion and was revised in S2-134439 Revision of S2-133966. Revised to S2-134439. |
| S2‑134424 | WebRTC Solution 7 Update | Broadcom Corporation | This was reviewed and approved. Revision of S2-134265. Approved |
| S2‑134425 | WebRTC joint architecture proposal | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, China Mobile, Ericsson, Huawei, NSN, | Revision of S2-134266. Agreed in parallel sessions. Approved |
| S2‑134426 | Procedures for WebRTC joint architecture proposal | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | Revision of S2-134271. Agreed in parallel sessions. Approved |
| S2‑134427 | LS to SA WG3 on Security aspects of IMS_WebRTC | SA WG2 | Revision of S2-134273. Agreed in parallel sessions. Approved |
| S2‑134428 | Cover Sheet for TR 23.701 presentation to TSG SA | China Mobile, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | Revision of S2-134272. Agreed in parallel sessions. Approved |
| S2‑134429 | 23.402 CR1176R4: Access Network information reporting in case of a TWAN Access | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, China Telecom | Revision of S2-134268. Agreed in parallel sessions. This CR was agreed |
| S2‑134430 | 23.203 CR0842R3: Access Network information reporting in case of a TWAN Access | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, China Telecom | Revision of S2-134269. Agreed in parallel sessions. This CR was agreed |
| S2‑134431 | 23.402 CR1198R3: Access Network information fetching in case of a TWAN Access-use of Sh | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, China Telecom | This was reviewed and approved. Revision of S2-134306.. This CR was agreed |
| S2‑134432 | 23.228 CR1045R2: Access Network information fetching in case of a TWAN Access-use of Sh | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, China Telecom | This was reviewed and approved. Revision of S2-134305.. This CR was agreed |
| S2‑134433 | 23.060 CR1800R8: Definition for a valid state of the TFT setting | Ericsson | Revision of S2-134293. Agreed in parallel sessions. This CR was agreed |
| S2‑134434 | 23.203 CR0856R2: AAA-based accounting for Fixed Broadband Network | Huawei, ORANGE | This was reviewed and approved. Revision of S2-134267. This CR was agreed |
| S2‑134435 | 23.203 CR0849R6: Alignment of Fixed Broadband Access Annex with main specification body | Ericsson, Allot Communications, Huawei | This was reviewed and revised to clean up the CR in S2-134441 Revision of S2-134307. Revised to S2-134441. |
| S2‑134436 | 23.401 CR2627R2: Introduction of ULI reporting at PCC area level | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | Ericsson raised an issue with the text where 'active mode' should replace 'idle mode'. Ericsson asked for it to be recorded that they have reservations with having per-PDN connection granularity in the PCC area reporting instead of having per-UE granulari |
| S2‑134437 | 23.203 CR0853R2: Introduction of PCC area Event Reporting Function trigger | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | Cisco asked for a correction on CSG text and asked for clarification in A.4.3.4. This was further discussed off-line and revised in S2-134508 Revision of S2-134275. Revised to S2-134508. |
| S2‑134438 | 23.060 CR1826R2: Introduction of ULI reporting at PCC area level | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | Revision of S2-134276. Revised in parallel sessions to S2-134509. |
| S2‑134439 | 23.203 CR0854R2: Introduction of ULI reporting only when the UE is in 'CONNECTED' state | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | This was reviewed and approved. Revision of S2-134423. This CR was agreed |
| S2‑134440 | 23.060 CR1827R2: Introduction of ULI reporting only when the UE is in 'CONNECTED' state | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | This was reviewed and approved. Revision of S2-134278. This CR was agreed |
| S2‑134441 | 23.203 CR0849R7: Alignment of Fixed Broadband Access Annex with main specification body | Ericsson, Allot Communications, Huawei | Revision of S2-134435. This CR was agreed |
| S2‑134442 | 23.401 CR2629R2: Introduction of ULI reporting only when the UE is in 'CONNECTED' state | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | This was reviewed and approved. Revision of S2-134277. This CR was agreed. |
| S2‑134443 | [DRAFT] LS on Extending IEEE 802.11u Generic Container | SA WG2 | Revision of S2-134417. For e-mail approval. Agreed. Revised to remove 'draft' in S2-134581. |
| S2‑134444 | 23.402 CR1183R5: UE/TWAN requested PDN Disconnection Procedure in WLAN on GTP S2a for Multi-Connection Mode | CATT | Reviewed and approved. Revision of S2-134283. This CR was agreed |
| S2‑134445 | Reply LS on uplink packet filters | SA WG2 | Revision of S2-134295. Approved |
| S2‑134446 | Evaluation of RAN-based solutions | Ericsson | Further drawbacks were mentioned and should be added. This was revised off-line in S2-134566 Revision of S2-134008. Revised to S2-134566. |
| S2‑134447 | Evaluation on policy based congestion mitigation | NEC | The conclusion should be removed and this was revised in S2-134567 Revision of S2-134204. Revised to S2-134567. |
| S2‑134448 | Completion and evaluation of scenario 1 | Vodafone | There was disagreement over the accuracy of bullet a). Intel disagreed with bullet b) and suggested awaiting the LS response before doing this evaluation. This was further discussed off-line and revised in S2-134484 Revision of S2-134241. Revised to S2-13 |
| S2‑134449 | [DRAFT] LS on the practical issues with simultaneous reception of multiple TMGIs and/or multiple MBSFN areas | SA WG2 | This was presented some suggestions for questions for RAN WG2 were made. This was left for further off-line discussion and revised off-line in S2-134462 Revised to S2-134462. |
| S2‑134450 | Completion and evaluation of scenario 2, and conclusions update | Vodafone | There were a number of issues raised and this was further discussed off-line and revised in S2-134485 Revision of S2-134242. Revised to S2-134485. |
| S2‑134451 | GCSE Service Continuity conclusions | Qualcomm Inc, NSN, Alcatel-Lucent | Revision of S2-134125. Revised to S2-134541. |
| S2‑134452 | Further clarifications to identities handling and way forward | Alcatel-lucent, Alcatel-Shanghai Bell | Reviewed and approved. Revision of S2-134115. Approved |
| S2‑134453 | update of Solution I3 | HTC | Reviewed and approved. Revision of S2-134059. Approved |
| S2‑134454 | Proposal for consolidating allocation of ProSe Identifiers solutions for direct discovery in network-authorized mode | InterDigital Communications, Telecom Italia | Alcatel-Lucent commented that some corrections were needed and this was revised off-line in S2-134476 Revision of S2-134368. Revised to S2-134476. |
| S2‑134455 | ProSe Direct Discovery- way forward | Qualcomm Incorporated, Telecom Italia, Deutsche Telekom, KDDI | It was suggested to change 'indicative' to more concrete text. Ericsson suggested removing the note. Broadcom commented that leaving the Prose Application Identities values and format 'out of scope of 3GPP' leaves this open for any body to specify, so it |
| S2‑134456 | Update of the solution D13 | Telecom Italia | Reviewed and approved. Revision of S2-133941. Approved |
| S2‑134457 | Direct discovery models | Qualcomm Incorporated | Some clarifications to the text were suggested. It was asked whether the UE should broadcast it's ProSe Application Identities. This should be clarified that depending on the solution, this may be the UE Identities. 'who is there' should be reinstated for |
| S2‑134458 | Technical Specification Group Services and System Aspects; Proximity based Services; Stage 2 | Qualcomm Incorporated (Rapporteur) | Endorsed as a basis for the TS development. Revision of S2-133987. Endorsed as a basis for the TS development. |
| S2‑134459 | EPC support for WLAN direct communication | Intel, Sony, CATT, III, TeleCommunication Systems, Broadcom Corporation, ITRI, Acer, NEC, MediaTek, ETRI, KPN, Motorola Mobility | Approved |
| S2‑134460 | Proposed updates to the common approach in the TR | General Dynamics Broadband UK | Revision of S2-134134. Revised to S2-134549. |
| S2‑134461 | GCSE Call set up conclusions | Qualcomm Inc, NSN, Alcatel-Lucent | This was discussed off-line and agreed changes reported. This was then revised in S2-134570 Revision of S2-134124. Revised to S2-134570. |
| S2‑134462 | [DRAFT] Further questions on GCSE with eMBMS | SA WG2 | Qualcomm commented that the LS should be re-phrased into the understanding that SA WG2 have and asking if this is correct. This was revised off-line in S2-134545 Revision of S2-134449. Revised to S2-134545. |
| S2‑134463 | UPCON Conclusion Text for CN-Based Solutions | KDDI, Verizon Wireless, AT&T, ZTE, Allot Communications, Sandvine Incorporated, Movik Networks, NEC, Samsung, Openet | This was reviewed and Telecom Italia raised concerns with the proposal to include the GTP-U solution. NSN commented that GTP-U is extensible, but the impacts of doing this should be studied further and added that an issue is the transport of large amounts |
| S2‑134464 | Evaluation on Solution R9 and partial conclusion on Relay for Public Safety ProSe | LG Electronics | Reviewed and approved Revision of S2-134142. Approved |
| S2‑134465 | Interim conclusion on Relay for Public Safety ProSe | Intel, Alcatel-Lucent | Revision of S2-134132. Revised to S2-134543. |
| S2‑134466 | Exception sheet for MTCe-UEPCOP | Ericsson | Some clean up was needed and this was revised in S2-134503 Revision of S2-134212. Revised to S2-134503. |
| S2‑134467 | Exception sheet for eSaMOG | ZTE | Some clean up was needed and this was revised in S2-134505 Revision of S2-134252. Revised to S2-134505. |
| S2‑134468 | Updated conclusions of extended DRX solutions | Ericsson | Revision of S2-134369. Approved |
| S2‑134469 | 23.682 CR0077R6: Introducing UE Power Saving Mode | Huawei, HiSilicon, Ericsson | Revision of S2-134377. This CR was agreed |
| S2‑134470 | 23.060 CR1814R7: Introducing UE Power Saving Mode | Qualcomm Incorporated, Ericsson | Revision of S2-134379. Revised to S2-134547. |
| S2‑134471 | 23.401 CR2603R7: Introducing UE Power Saving Mode | Ericsson | Revision of S2-134378. Revised to S2-134548. |
| S2‑134472 | Cover Sheet for TR 23.887 for approval at TSG SA | Intel | Revision of S2-134381. For e-mail approval. rev1 agreed. Revised to S2-134577. |
| S2‑134473 | 23.401 CR2594R7: Core Network assisted eNodeB parameters tuning | NSN, Ericsson, Huawei | InterDigital objected as this is not in agreement with the LS. Alcatel-Lucent objected because the LS asked SA WG2 only to consider removing the parameters. This was then noted and the original CR which was agreed at SA WG2#99 in S2-133842 will be forward |
| S2‑134474 | 23.682 CR0078R5: Device trigger recall and replace | LG Electronics, Intel, Acision, Ericsson, Orange | Revision of S2-134380. This CR was agreed |
| S2‑134475 | Evaluation of solution P2 on ProSe configuration | NEC | The references to the annex should be removed and the high level bullets reinstated. This was revised off-line in S2-134532 Revision of S2-134367. Revised to S2-134532. |
| S2‑134476 | Proposal for consolidating allocation of ProSe Identifiers solutions for direct discovery in network-authorized mode | InterDigital Communications, Telecom Italia | Revision of S2-134454. Approved |
| S2‑134477 | Update of Solution R1 | CATT, CATR | Further changes were required to try to make the table more accurate, or to remove the table if this cannot be achieved and this was revised off-line in S2-134531 Revision of S2-134062. Revised to S2-134531. |
| S2‑134478 | ProSe Direct Discovery- way forward | Qualcomm Incorporated, Telecom Italia, Deutsche Telekom, KDDI | Revision of S2-134455. Revised to S2-134538. |
| S2‑134479 | Direct discovery models | Qualcomm Incorporated | Revision of S2-134457. Approved |
| S2‑134480 | Group Management for GCSE_LTE | U.S. Department of Commerce | Further issues were raised and this was further discussed off-line and revised in S2-134544 Revision of S2-134349. Revised to S2-134544. |
| S2‑134481 | Group management and user interaction for GCSE | NSN, Qualcomm Inc, ALU | Reviewed and approved. Revision of S2-134350. Approved |
| S2‑134482 | Update of solution 7: Assign and Re-assign Priority and Pre-emption capability for the GC | Huawei, Hisilicon | Reviewed and approved. Revision of S2-134351. Approved |
| S2‑134483 | Conclusion on the QoS aspects of GCSE | Huawei, Hisilicon | Reviewed and approved. Revision of S2-134371. Approved |
| S2‑134484 | Completion and evaluation of scenario 1 | Vodafone | Alcatel-Lucent suggested removing the 'i.e. ...' in the editor's note. This was revised accordingly in S2-134542 Revision of S2-134448. Revised to S2-134542. |
| S2‑134485 | Completion and evaluation of scenario 2, and conclusions update | Vodafone | Reviewed and approved. Revision of S2-134450. Approved |
| S2‑134486 | Exception sheet for ProSe WID | Qualcomm Incorporated | This was reviewed and revised in S2-134497 Revision of S2-133995. Revised to S2-134497. |
| S2‑134487 | Updates to the variant of the off-path solution | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Cisco, Allot Communications, China Telecom, KDDI, ZTE, Broadcom Corporation, AT&T | A clarification was provided and this was approved. Revision of S2-134346. Approved |
| S2‑134488 | Clarification of the Congestion Reporting Solution Based on GTP-U | China Mobile, NEC, AT&T, NSN | Ericsson commented that the use of Cell ID is a concern as there is no rational for using it and preferred to keep this FFS and to determine why it is needed. This was further discussed off-line and revised in S2-134562 Revision of S2-134347. Revised to S |
| S2‑134489 | Refinement of integrated on-path off-path solution (6.1.5.4) | KDDI, China Telecom, ZTE, AT&T, Bell Canada, Movik Networks, SoftBank Mobile, Sprint, Broadcom Corporation, NTT DoCoMo, NEC, Sandvine Technology, Samsung | A modification was made and this was revised in S2-134563 Revision of S2-134348. Revised to S2-134563. |
| S2‑134490 | Off-Path reporting Evaluation | Ericsson | The Rapporteur was asked to remove redundant identical bullet where necessary. Other comments were made and this was further discussed off-line and revised in S2-134565 Revision of S2-134374. Revised to S2-134565. |
| S2‑134491 | Evaluation of C-plane signalling for RAN user plane congestion reporting solution | NTT DOCOMO, Intel | Reviewed and approved. Revision of S2-134376. Approved |
| S2‑134492 | SA WG1 Work planning and coordination output | SA WG1 Chairman | The SA WG1 Chairman reported that there is still work to do on this in SA WG1 to finalise this document. Telekom Deutschland commented that they did not support proposal 2 but proposals 1 and 3 were considered very good. Verizon also provided their commen |
| S2‑134493 | Cover Sheet for TR 23.768 | Vodafone | For e-mail approval. rev2 agreed. Revised to S2-134579. |
| S2‑134494 | Cover Sheet for TR 23.703 | Qualcomm Incorporated (Rapporteur) | For e-mail approval. rev1 agreed. Revised to S2-134578. |
| S2‑134495 | Pre-TSG SA#62 Work Planning Worksheet | SA WG2 Chairman | Revision of S2-134048. Noted, Endorsed. |
| S2‑134496 | Exception sheet for Core Network Overload - User Location Information reporting improvements | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | Some clean up was needed and this was revised in S2-134499 Revision of S2-133968. Revised to S2-134499. |
| S2‑134497 | Exception sheet for ProSe WID | Qualcomm Incorporated | Revision of S2-134486. For e-mail approval. rev9 agreed. Revised to S2-134583. |
| S2‑134498 | Exception sheet for IMS_WebRTC | Alcatel-Lucent, China Mobile, Alcatel-Lucent Shanghai Bell | Revision of S2-134359. For e-mail approval. rev1 agreed. Revised to S2-134584. |
| S2‑134499 | Exception sheet for Core Network Overload - User Location Information reporting improvements | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | Revision of S2-134496. For e-mail approval. rev9 agreed. Revised to S2-134588. |
| S2‑134500 | Exception sheet for NETLOC_TWAN | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | Revision of S2-134360. For e-mail approval. rev8 agreed. Revised to S2-134585. |
| S2‑134501 | Exception sheet for GCSE_LTE | NSN | Some clean up was needed and this was revised in S2-134504 Revision of S2-134251. Revised to S2-134504. |
| S2‑134502 | Exception sheet for UPCON | NEC | The SA WG2 Chairman asked to list the exact topics which will be done during the extension period if granted by TSG SA. The TSG SA Chairman commented that the reason for exception sheets is to allow work to complete which is near completion at the Release |
| S2‑134503 | Exception sheet for MTCe-UEPCOP | Ericsson | Revision of S2-134466. WITHDRAWN |
| S2‑134504 | Exception sheet for GCSE_LTE | NSN | Revision of S2-134501. For e-mail approval. rev2 agreed. Revised to S2-134586. |
| S2‑134505 | Exception sheet for eSaMOG | ZTE | Revision of S2-134467. For e-mail approval. rev4 agreed. Revised to S2-134587. |
| S2‑134506 | Proposed conclusion | Allot,Openet,Cisco,Oracle,ALU,ALU- ShanghaiBell,ChinaTelecom,SPRINT,ZTE,Broadcom,KDDI,ChinaUnicom,USCellular,Comverse,Bell-Mobility,Hitachi,Sandvinen,Amdocs | Companies asked for more time to consider this proposal. This was revised in S2-134568 Revision of S2-133970. Revised to S2-134568. |
| S2‑134507 | 23.401 CR2627R3: Introduction of ULI reporting at PCC area level | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | Alcatel-Lucent reported additional changes which had been requested and the terminology needed improvement. It was agreed that the terminology may be corrected at the next meeting. This was revised in S2-134512 Revision of S2-134436. Revised to S2-134512. |
| S2‑134508 | 23.203 CR0853R3: Introduction of PCC area Event Reporting Function trigger | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | Revision of S2-134437. Revised to S2-134513. |
| S2‑134509 | 23.060 CR1826R3: Introduction of ULI reporting at PCC area level | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | Revision of S2-134438. This CR was agreed |
| S2‑134510 | 23.402 CR1191R7: WLAN access network selection based on WLANSP rules | Motorola Mobilty, AT&T, Qualcomm Incorporated, Intel, Broadcom Corporation, NSN, Samsung, Nokia, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | Reviewed and approved. Revision of S2-134416. This CR was agreed |
| S2‑134511 | 23.402 CR1202R2: PDN Connectivity Procedures in WLAN on PMIP S2a for Multi-connection Mode | KDDI, Broadcom Corporation | Revision of S2-134284. This CR was agreed |
| S2‑134512 | 23.401 CR2627R4: Introduction of ULI reporting at PCC area level | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | Revision of S2-134507. This CR was agreed |
| S2‑134513 | 23.203 CR0853R4: Introduction of PCC area Event Reporting Function trigger | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | Revision of S2-134508. This CR was agreed |
| S2‑134514 | - | - | [WITHDRAWN] |
| S2‑134515 | - | - | [WITHDRAWN] |
| S2‑134516 | - | - | [WITHDRAWN] |
| S2‑134517 | - | - | [WITHDRAWN] |
| S2‑134518 | - | - | [WITHDRAWN] |
| S2‑134519 | - | - | [WITHDRAWN] |
| S2‑134520 | - | - | [WITHDRAWN] |
| S2‑134521 | - | - | [WITHDRAWN] |
| S2‑134522 | - | - | [WITHDRAWN] |
| S2‑134523 | - | - | [WITHDRAWN] |
| S2‑134524 | - | - | [WITHDRAWN] |
| S2‑134525 | - | - | [WITHDRAWN] |
| S2‑134526 | - | - | [WITHDRAWN] |
| S2‑134527 | SA WG2#100 Statement | SA WG2 Chairman | Noted |
| S2‑134528 | 23.203 CR0855R2: Addition of charging characteristics transfer to TDF | Allot Communications, ORANGE | Reviewed and approved. Revision of S2-134342. This CR was agreed |
| S2‑134529 | ProSe Communication 1-many decentralized mode- way forward | Qualcomm Incorporated, Alcatel-Lucent, Intel, U.S. Department of Commerce | Reviewed and approved. Revision of S2-134352. Approved |
| S2‑134530 | A way forward on direct communication one-to-many: a synthesis of proposals | General Dynamics Broadband UK | Revision of S2-134353. Approved |
| S2‑134531 | Update of Solution R1 | CATT, CATR | Revision of S2-134477. Noted |
| S2‑134532 | Evaluation of solution P2 on ProSe configuration | NEC | Revision of S2-134475. Approved |
| S2‑134533 | On EPC level discovery | Qualcomm Incorporated, Motorola Mobility | Revision of S2-134383. Approved |
| S2‑134534 | LS on Charging aspects for Network Sharing (MOCN GWCN) | SA WG2 | Revision of S2-134407. For e-mail approval. Approved. Revised to add correct attachments in S2-134589. |
| S2‑134535 | Proposed way forward on EPC-level discovery and EPC support for WLAN direct communication | Intel, Sony, CATT, III, TeleCommunication Systems, Broadcom Corporation, ITRI, Acer, NEC, MediaTek, ETRI, KPN, LG Electronics | Ericsson reported that the new FFS will have an impact on the exception sheet. This was then approved. Revision of S2-134382. Approved |
| S2‑134536 | [DRAFT] Reply LS on providing Charging Characteristics to TDF | ORANGE | Revision of S2-134343. For e-mail approval. rev2 is agreed. Revised to S2-134575. |
| S2‑134537 | EPC-level discovery and EPC support for WLAN direct communication | Intel, Sony, CATT, III, TeleCommunication Systems, Broadcom Corporation, ITRI, Acer, NEC, MediaTek, ETRI, KPN, LG Electronics, HTC | Ericsson asked it to be recorded that the IMS functionality is incomplete. This was then approved. Revision of S2-134414. Ericsson asked it to be recorded that the IMS functionality is incomplete Approved |
| S2‑134538 | ProSe Direct Discovery- way forward | Qualcomm Incorporated, Telecom Italia, Deutsche Telekom, KDDI | Revision of S2-134478. Revised to S2-134561. |
| S2‑134539 | Preliminary UPCON conclusions for Rel-12 | Telecom Italia, Huawei, Hisilicon | Revision of S2-133964. Noted |
| S2‑134540 | RAN impacts and evaluation of Solution 1.5.1 | China Mobile, AT&T, NEC, Samsung, NSN | The FFS to determine whether there is an advantage should be removed from the advantages list. The conclusion should be removed in accordance with agreements at this meeting. This was revised in S2-134564 Revision of S2-134373. Revised to S2-134564. |
| S2‑134541 | GCSE Service Continuity conclusions | Qualcomm Inc, NSN, Alcatel-Lucent | Reviewed and approved. Revision of S2-134451. Approved |
| S2‑134542 | Completion and evaluation of scenario 1 | Vodafone | Revision of S2-134484. Approved |
| S2‑134543 | Interim conclusion on Relay for Public Safety ProSe | Intel, Alcatel-Lucent | More comments were received and this was revised off-line in S2-134560 Revision of S2-134465. Revised to S2-134560. |
| S2‑134544 | Group Management for GCSE_LTE | U.S. Department of Commerce | Comments had been received off-line and this was revised again in S2-134569 Revision of S2-134480. Revised to S2-134569. |
| S2‑134545 | [DRAFT] Further questions on GCSE with eMBMS | SA WG2 | Revision of S2-134462. For e-mail approval. Agreed. Revised to remove 'draft' and revision marks in S2-134580. |
| S2‑134546 | Reply LS on interaction between SIPTO at the local network and the CS fallback service in connected mode | SA WG2 | Revision of S2-134317. Approved |
| S2‑134547 | 23.060 CR1814R8: Introducing UE Power Saving Mode | Qualcomm Incorporated, Ericsson | Some editorial corrections were needed and this was revised in S2-134572 Revision of S2-134470. Revised to S2-134572. |
| S2‑134548 | 23.401 CR2603R8: Introducing UE Power Saving Mode | Ericsson | Some editorial corrections were needed and this was revised in S2-134571 Revision of S2-134471. Revised to S2-134571. |
| S2‑134549 | Proposed updates to the common approach in the TR | General Dynamics Broadband UK | Some corrections were requested and this was revised in S2-134573 Revision of S2-134460. Revised to S2-134573. |
| S2‑134550 | SA WG2 Exception Report to TSG SA#62 | SA WG2 Chairman | This was provided after the meeting for information and is noted. Noted. |
| S2‑134551 | - | - | [WITHDRAWN] |
| S2‑134552 | - | - | [WITHDRAWN] |
| S2‑134553 | - | - | [WITHDRAWN] |
| S2‑134554 | - | - | [WITHDRAWN] |
| S2‑134555 | - | - | [WITHDRAWN] |
| S2‑134556 | - | - | [WITHDRAWN] |
| S2‑134557 | - | - | [WITHDRAWN] |
| S2‑134558 | - | - | [WITHDRAWN] |
| S2‑134559 | - | - | [WITHDRAWN] |
| S2‑134560 | Interim conclusion on Relay for Public Safety ProSe | Intel, Alcatel-Lucent | Revision of S2-134543. Revised to S2-134574. |
| S2‑134561 | ProSe Direct Discovery- way forward | Qualcomm Incorporated, Telecom Italia, Deutsche Telekom, KDDI | Reviewed and approved. Revision of S2-134538. Approved |
| S2‑134562 | Clarification of the Congestion Reporting Solution Based on GTP-U | China Mobile, NEC, AT&T, NSN | Reviewed and noted. Revision of S2-134488. Noted |
| S2‑134563 | Refinement of integrated on-path off-path solution (6.1.5.4) | KDDI, China Telecom, ZTE, AT&T, Bell Canada, Movik Networks, SoftBank Mobile, Sprint, Broadcom Corporation, NTT DoCoMo, NEC, Sandvine Technology, Samsung | Revision of S2-134489. Approved |
| S2‑134564 | RAN impacts and evaluation of Solution 1.5.1 | China Mobile, AT&T, NEC, Samsung, NSN | Reviewed and approved. Revision of S2-134540. Approved |
| S2‑134565 | Off-Path reporting Evaluation | Ericsson | Revision of S2-134490. For e-mail approval. Noted |
| S2‑134566 | Evaluation of RAN-based solutions | Ericsson | Revision of S2-134446. For e-mail approval. Noted |
| S2‑134567 | Evaluation on policy based congestion mitigation | NEC | Revision of S2-134447. For e-mail approval. Noted |
| S2‑134568 | Proposed conclusion | Allot,Openet,Cisco,Oracle,ALU,ALU- ShanghaiBell,ChinaTelecom,SPRINT,ZTE,Broadcom,KDDI,ChinaUnicom,USCellular,Comverse,Bell-Mobility,Hitachi,Sandvinen,Amdocs | There were a number of open issues identified and Ericsson commented that the evaluations are progressing well, but added that to make any progress on this the RAN WGs will need to be consulted on areas which are outside SA WG2 expertise. 3 companies indi |
| S2‑134569 | Group Management for GCSE_LTE | U.S. Department of Commerce | Reviewed and approved. Revision of S2-134544. Approved |
| S2‑134570 | GCSE Call set up conclusions | Qualcomm Inc, NSN, Alcatel-Lucent | Revision of S2-134461. Approved |
| S2‑134571 | 23.401 CR2603R9: Introducing UE Power Saving Mode | Huawei, HiSilicon, Orange, Qualcomm Incorporated, Ericsson | Revision of S2-134548. This CR was agreed |
| S2‑134572 | 23.060 CR1814R9: Introducing UE Power Saving Mode | Huawei, HiSilicon, Orange, Qualcomm Incorporated, Ericsson | Revision of S2-134547. This CR was agreed |
| S2‑134573 | Proposed updates to the common approach in the TR | General Dynamics Broadband UK | Revision of S2-134549. Approved |
| S2‑134574 | Interim conclusion on Relay for Public Safety ProSe | Intel, Alcatel-Lucent | Revision of S2-134560. Approved |
| S2‑134575 | Reply LS on providing Charging Characteristics to TDF | SA WG2 | e-mail revision 2 of S2-134536. Approved |
| S2‑134576 | PCC with NAT in roaming scenarios | SA WG2 | e-mail revision of S2-134298. Approved |
| S2‑134577 | Cover Sheet for TR 23.887 for approval at TSG SA | Intel | e-mail revision 1 of S2-134472. Approved |
| S2‑134578 | Cover Sheet for TR 23.703 | Qualcomm Incorporated (Rapporteur) | e-mail revision 1 of S2-134494. Approved |
| S2‑134579 | Cover Sheet for TR 23.768 | Vodafone | e-mail revision 2 of S2-134493. Approved |
| S2‑134580 | Further questions on GCSE with eMBMS | SA WG2 | e-mail revision of S2-134545. Approved |
| S2‑134581 | LS on Extending IEEE 802.11u Generic Container | SA WG2 | e-mail revision of S2-134443. Approved |
| S2‑134582 | Cover sheet for TR 23.843 for approval at TSG SA | Huawei, Hisilicon | e-mail revision 2 of S2-134201. Approved |
| S2‑134583 | Exception sheet for ProSe WID | Qualcomm Incorporated | e-mail revision 9 of S2-134497. Approved |
| S2‑134584 | Exception sheet for IMS_WebRTC | Alcatel-Lucent, China Mobile, Alcatel-Lucent Shanghai Bell | e-mail revision 1 of S2-134498. Approved |
| S2‑134585 | Exception sheet for NETLOC_TWAN | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | e-mail revision 8 of S2-134500. Approved |
| S2‑134586 | Exception sheet for GCSE_LTE | NSN | e-mail revision 2 of S2-134504. Approved |
| S2‑134587 | Exception sheet for eSaMOG | ZTE | e-mail revision 4 of S2-134505. Approved |
| S2‑134588 | Exception sheet for Core Network Overload - User Location Information reporting improvements | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | e-mail revision 9 of S2-134499. Approved |
| S2‑134589 | LS on Charging aspects for Network Sharing (MOCN GWCN) | SA WG2 | e-mail revision of S2-134534. Approved |
page generated from database: 2024-04-22 07:58:53