3GPP TDocs (written contributions) at meeting
Meeting: S1-51 - 2010-08-23 to 2010-08-27, Seoul
meeting id: S1-51 (click id for more info on this meeting)Click on the Tdoc to open its file.
TDoc | Title | Source | Remarks |
---|---|---|---|
S1‑102000 | Agenda draft 1 | TB Chairman | imported from 3GU |
S1‑102001 | Agenda for SA1#51 draft 2 | TB Chairman | imported from 3GU |
S1‑102002 | Agenda for SA1#51 draft 3 | TB Chairman | imported from 3GU |
S1‑102003 | Agenda for SA1#51 final version | TB Chairman | imported from 3GU |
S1‑102004 | Draft Minutes of SA1#50 | ETSI Secretariat | imported from 3GU |
S1‑102005 | Minutes of SA1#50 Final version | ETSI Secretariat | imported from 3GU |
S1‑102006 | SA1 extract of the Work Plan as of beginning of SA1#51 | ETSI Secretariat | imported from 3GU |
S1‑102007 | Draft WID on Operator-Independent Public User Identities | Vodafone | imported from 3GU |
S1‑102008 | Operator-Independent Public User Identities Use Cases | Vodafone | imported from 3GU |
S1‑102009 | CR to 22.228 on Alphanumeric SIP URI Addressing | Vodafone | imported from 3GU |
S1‑102010 | Draft WID on Optimised Service Charging and Allocation of Resources in IMS whilst Roaming | Vodafone | imported from 3GU |
S1‑102011 | IMS Roaming Enhancements | Vodafone, Ericsson | imported from 3GU |
S1‑102012 | Draft Reply LS on Handling of Hybrid cells | Vodafone | imported from 3GU |
S1‑102013 | Draft Reply LS on LIPA/SIPTO stage 1 clarification | Vodafone | imported from 3GU |
S1‑102014 | CR to 22.101 on User interaction for SIPTO for H(e)NB subsystems | Vodafone | imported from 3GU |
S1‑102015 | CR to 22.220 on User awareness of SIPTO for H(e)NB subsystems | Vodafone | imported from 3GU |
S1‑102016 | Use cases for 3GPP voice and IP-PBX interworking | Vodafone, Verizon Wireless | imported from 3GU |
S1‑102017 | Draft WID on LIPA/SIPTO-related Mobility | Vodafone, Verizon Wireless | imported from 3GU |
S1‑102018 | CR to 22.101 on SIPTO mobility | Vodafone | imported from 3GU |
S1‑102019 | Alignment on ACB for CSFB | TSG SA1 | imported from 3GU |
S1‑102020 | Pseudo-CR on TR 22.8yz 'Support for 3GPP Voice Interworking with Enterprise IP-PBX'- enterprise-based service control | Alcatel-Lucent | imported from 3GU |
S1‑102021 | Pseudo-CR on TR 22.8yz 'Support for 3GPP Voice Interworking with Enterprise IP-PBX'- definitions for LIPA and RIPA | Alcatel-Lucent | imported from 3GU |
S1‑102022 | Pseudo-CR on TR 22.8yz 'Support for 3GPP Voice Interworking with Enterprise IP-PBX'- LIPA/RIPA-based VPN | Alcatel-Lucent | imported from 3GU |
S1‑102023 | Pseudo-CR on TR 22.8yz 'Support for 3GPP Voice Interworking with Enterprise IP-PBX'- business trunking | Alcatel-Lucent | imported from 3GU |
S1‑102024 | Pseudo-CR on TR 22.8yz 'Support for 3GPP Voice Interworking with Enterprise IP-PBX'- hosted enterprise services | Alcatel-Lucent | imported from 3GU |
S1‑102025 | Pseudo-CR on TR 22.8yz 'Support for 3GPP Voice Interworking with Enterprise IP-PBX'- roaming | Alcatel-Lucent | imported from 3GU |
S1‑102026 | Pseudo-CR on TR 22.8yz 'Support for 3GPP Voice Interworking with Enterprise IP-PBX'- conclusions | Alcatel-Lucent | imported from 3GU |
S1‑102027 | NOVES updates | AT&T | imported from 3GU |
S1‑102028 | Alignment of Transfer of Control requirements | Huawei, Orange | imported from 3GU |
S1‑102029 | Removing the distinction between MTC Feature subscription and activation | Huawei, Samsung | imported from 3GU |
S1‑102030 | Proposed updates to the system-wide BBAI WID (revision of SP-100222) | Huawei, Telecom Italia | imported from 3GU |
S1‑102031 | Adding refernece for H(e)NB in Fixed Mobile Interworking requirements | Huawei, Telecom Italia | imported from 3GU |
S1‑102032 | Adding a H(e)NB use case to FMC use cases | Huawei, Telecom Italia | imported from 3GU |
S1‑102033 | Adding a Application Mobility use case to FMC use cases | Huawei, Telecom Italia | imported from 3GU |
S1‑102034 | Adding a Common Quota use case to FMC use cases | Huawei, Telecom Italia, | imported from 3GU |
S1‑102035 | Clarifications on FMC use cases | Huawei, Telecom Italia | imported from 3GU |
S1‑102036 | New Requirements for Fixed Mobile Convergence scenario | Huawei, Telecom Italia, | imported from 3GU |
S1‑102037 | Removal of unfulfilled requirements | Research In Motion, Samsung, Nokia, Nokia Siemens Networks | imported from 3GU |
S1‑102038 | NOVES section 3.1 updates | RIM | imported from 3GU |
S1‑102039 | NOVES section 4 updates | RIM | imported from 3GU |
S1‑102040 | Validation of OpenID/AKA business scenarios | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | imported from 3GU |
S1‑102041 | Clarification of regulatory requirements and enablement/disablement policies for LIPA/SIPTO | Alcatel-Lucent | imported from 3GU |
S1‑102042 | Charging considerations for MMTel when Optimal Media Routeing is used | Deutsche Telekom | imported from 3GU |
S1‑102043 | MTCe TR skeleton | Huawei technologies | imported from 3GU |
S1‑102044 | Intfroduction and scope for FS-MTCe | Huawei technologies | imported from 3GU |
S1‑102045 | Draft FS_VINE TR skeleton | Tatara Systems | imported from 3GU |
S1‑102046 | Draft FS_VINE Scope | Tatara Systems | imported from 3GU |
S1‑102047 | NOVES Requirements Section Updates | AT&T | imported from 3GU |
S1‑102048 | NOVES Annex A Updates | AT&T | imported from 3GU |
S1‑102049 | CR to 22.071 Rel-9 - Removal of references to 3GPP OSA | NEC | imported from 3GU |
S1‑102050 | CR to 22.105 Rel-9 - Removal of references to 3GPP OSA | NEC | imported from 3GU |
S1‑102051 | CR to 22.127 Rel-9 - Removal of references to 3GPP OSA | NEC | imported from 3GU |
S1‑102052 | CR to 22.228 Rel-9 - Removal of references to 3GPP OSA | NEC | imported from 3GU |
S1‑102053 | CR to 22.228 Rel-10 - Removal of references to 3GPP OSA | NEC | imported from 3GU |
S1‑102054 | CR to 22.240 Rel-9 - Removal of references to 3GPP OSA | NEC | imported from 3GU |
S1‑102055 | CR to 22.278 Rel-9 - Removal of references to 3GPP OSA | NEC | imported from 3GU |
S1‑102056 | CR to 22.278 Rel-10 - Removal of references to 3GPP OSA | NEC | imported from 3GU |
S1‑102057 | CR to 22.934 Rel-9 - Removal of references to 3GPP OSA | NEC | imported from 3GU |
S1‑102058 | CR to 22.935 Rel-9 - Removal of references to 3GPP OSA | NEC | imported from 3GU |
S1‑102059 | CR to 22.949 Rel-9 - Removal of references to 3GPP OSA | NEC | imported from 3GU |
S1‑102060 | Checking Rapporteurship of SA1 specs | NEC | imported from 3GU |
S1‑102061 | CR to 22.220 Correction on HNB Name | NEC | imported from 3GU |
S1‑102062 | Reply LS on supplementary services classification on II-NNI | Orange | imported from 3GU |
S1‑102063 | Clarification of LIPA requirements | Huawei technologies | imported from 3GU |
S1‑102064 | H(e)NB Hosting Party USIM use | Gemalto, Sagem Orga | imported from 3GU |
S1‑102065 | Terminal supporting 3GPP Management Objects | Gemalto, Sagem Orga | imported from 3GU |
S1‑102066 | UICC Access to IMS use cases | Gemalto, Sagem Orga | imported from 3GU |
S1‑102067 | TR_U2e: Revision of document structure | Sagem Orga | imported from 3GU |
S1‑102068 | TR_U2e: Chapter 4 – Update of Use Cases | Sagem Orga | imported from 3GU |
S1‑102069 | TR_U2e: Chapter 6 (new) - Use Case evaluation | Sagem Orga | imported from 3GU |
S1‑102070 | Discussion on high scalability service category for Machine Type Communication (MTC) | Alcatel-Lucent Shanghai Bell, Alcatel-Lucent | imported from 3GU |
S1‑102071 | Discussion on high correlation service category for Machine Type Communication (MTC) | Alcatel-Lucent Shanghai Bell, Alcatel-Lucent | imported from 3GU |
S1‑102072 | Discussion on content-based service category for Machine Type Communication (MTC) | Alcatel-Lucent Shanghai Bell, Alcatel-Lucent | imported from 3GU |
S1‑102073 | Discussion paper: MTC Clarifications | KDDI | imported from 3GU |
S1‑102074 | CR to 22 368 5 1 2 | KDDI | imported from 3GU |
S1‑102075 | CR to 22 368 7 1 5 | KDDI | imported from 3GU |
S1‑102076 | CR to 22 368 7 2 1 | KDDI | imported from 3GU |
S1‑102077 | CR to 22 368 7 2 2 | KDDI | imported from 3GU |
S1‑102078 | CR to 22 368 7 2 4 | KDDI | imported from 3GU |
S1‑102079 | CR to 22 368 7 2 6 | KDDI | imported from 3GU |
S1‑102080 | CR to 22 368 7 2 7 | KDDI | imported from 3GU |
S1‑102081 | CR to 22 368 7 2 8 | KDDI | imported from 3GU |
S1‑102082 | CR to 22 368 7 2 9 | KDDI | imported from 3GU |
S1‑102083 | CR to 22 368 7 2 11 | KDDI | imported from 3GU |
S1‑102084 | CR to 22 368 7 2 12 | KDDI | imported from 3GU |
S1‑102085 | CR to 22 368 7 2 14 | KDDI | imported from 3GU |
S1‑102086 | Mobility/Continuity Aspects for LIPA | Vodafone | imported from 3GU |
S1‑102087 | SIPTO mobility/continuity use cases | Vodafone | imported from 3GU |
S1‑102088 | Draft Reply LS on Inhibiting the Allowed CSG List | Vodafone | imported from 3GU |
S1‑102089 | Proposal for Inhibiting Allowed CSG List | Vodafone, Deutsche Telekom, Qualcomm Incorporated | imported from 3GU |
S1‑102090 | CR to 22.220 (Rel-9) on Removal of requirement to inhibit Allowed CSG List | Vodafone, Qualcomm Incorporated | imported from 3GU |
S1‑102091 | CR to 22.220 (Rel-10) on Removal of requirement to inhibit Allowed CSG List | Vodafone, Qualcomm Incorporated | imported from 3GU |
S1‑102092 | Addition of alternative flows for NOVES Use Cases 5 & 6 | China Mobile, ZTE | imported from 3GU |
S1‑102093 | Use cases for 3GPP voice and IP-PBX interworking | China Mobile | imported from 3GU |
S1‑102094 | Unsolicited communication alignment with SA3 | Ericsson, ST-Ericsson | imported from 3GU |
S1‑102095 | Paper discussion on E.164 number shortage for M2M | France Telecom | imported from 3GU |
S1‑102096 | Use case proposal | France Telecom | imported from 3GU |
S1‑102097 | Use cases and suggested requirements for key issue 3 in TR 23.813 | Ericsson | imported from 3GU |
S1‑102098 | CR to TS22.011: Access control for MTC | Samsung | imported from 3GU |
S1‑102099 | Clarification on NOVES Definition | ZTE, CMCC | imported from 3GU |
S1‑102100 | Proposed Requirement for PSAP Selection | ZTE, CMCC, Motorola | imported from 3GU |
S1‑102101 | Clarification of Time Tolerant MTC Feature | ZTE | imported from 3GU |
S1‑102102 | Discussion on possible MTC Gateway Communication Scenarios | ZTE | imported from 3GU |
S1‑102103 | Addition of communication via MTC GW Scenario | ZTE | imported from 3GU |
S1‑102104 | Addition of definition for communication via MTC GW | ZTE | imported from 3GU |
S1‑102105 | Discussion on MTC Device-to-Device Communication Scenarios | ZTE | imported from 3GU |
S1‑102106 | Addition of MTC Device-to-Device Communication Scenarios | ZTE, China Mobile | imported from 3GU |
S1‑102107 | Discussion on requirements for the behaviour of H(e)NB with removal of H(e)NB Hosting Party USIM | ZTE | imported from 3GU |
S1‑102108 | Behavior of H(e)NB with removal of H(e)NB Hosting Party USIM | ZTE | imported from 3GU |
S1‑102109 | Discussion on access mode of H(e)NB for LIPA_SIPTO application | ZTE | imported from 3GU |
S1‑102110 | LIPA_SIPTO requirement clarification when considering access mode of H(e)NB | ZTE | imported from 3GU |
S1‑102111 | Correction to ATSI and ATM for missing SS codes | Vodafone, Nokia Siemens Networks, | imported from 3GU |
S1‑102112 | Prepay service enhancement - Qos Change triggering | Alcatel-Lucent, AT&T | imported from 3GU |
S1‑102113 | Comments on NOVES | Alcatel-Lucent | imported from 3GU |
S1‑102114 | NIMTC - Removal of Activation Requirements | Sierra Wireless | imported from 3GU |
S1‑102115 | NIMTC - Add Access Class Baring for MTC Devices | Sierra Wireless | imported from 3GU |
S1‑102116 | Avoiding Abuse of Priority Alarm | Panasonic, China Mobile, ZTE | imported from 3GU |
S1‑102117 | Use Case for Co-located MTC Devices | Panasonic, Alcatel Lucent Shanghai Bell, Alcatel Lucent, China Mobile, ZTE, Motorola | imported from 3GU |
S1‑102118 | Use Case for Location Tracking | Panasonic, Alcatel Lucent Shanghai Bell, Alcatel Lucent, China Mobile, ZTE, Motorola | imported from 3GU |
S1‑102119 | Use Case for Capillary Networks | Panasonic, China Mobile, Alcatel Lucent Shanghai Bell, Alcatel Lucent | imported from 3GU |
S1‑102120 | Reflections on Remote Access initiative from TISPAN (LS C1-101756) | Ericsson | imported from 3GU |
S1‑102121 | Clarification of note on Group Based MTC features | Samsung Electronics | imported from 3GU |
S1‑102122 | MTC Group Features definition clarification | Samsung | imported from 3GU |
S1‑102123 | MTC Infrequent Transmission clarification | Samsung | imported from 3GU |
S1‑102124 | MTC Secure Connection | Samsung | imported from 3GU |
S1‑102125 | MTC Time Controlled clarification | Samsung | imported from 3GU |
S1‑102126 | discussion paper about APN storage on USIM | Giesecke & Devrient | imported from 3GU |
S1‑102127 | APN storage on the USIM | Giesecke & Devrient, Sagem Orga, Telecom Italia | imported from 3GU |
S1‑102128 | TR_U2e: Chapter 5 - Editorial corrections | Sagem Orga | imported from 3GU |
S1‑102129 | FS_U2_e use cases | Giesecke & Devrient | imported from 3GU |
S1‑102130 | Reply LS to ' LS on Network provided Location information for IMS Charging' | Nokia Siemens Networks | imported from 3GU |
S1‑102131 | Draft Reply LS on Handling of Hybrid Cells | Motorola | imported from 3GU |
S1‑102132 | New Use Case for NOVES | Motorola | imported from 3GU |
S1‑102133 | Withdrawn | - | imported from 3GU |
S1‑102134 | Withdrawn | - | imported from 3GU |
S1‑102135 | Analysis Current Standards from SID perspective | Ericsson | imported from 3GU |
S1‑102136 | Use cases for 3GPP voice and IP-PBX interworking | Ericsson | imported from 3GU |
S1‑102137 | PWS - Security Limitations of Cell Broadcast Service | Vodafone, Telefonica S.A. | imported from 3GU |
S1‑102138 | draft LS to SA3 on Security for PWS | Vodafone | imported from 3GU |
S1‑102139 | Business Model for 3GPP Voice Interworking with Enterprise IP-PBX | Verizon Wireless | imported from 3GU |
S1‑102140 | Reference Architecture for 3GPP Voice Interworking with Enterprise IP-PBX | Verizon Wireless | imported from 3GU |
S1‑102141 | Pseudo CR to TR 'Study on Alternatives to E.164 for MTC' | Telefonica | imported from 3GU |
S1‑102142 | IMS application services across IMS-NNI | KPN | imported from 3GU |
S1‑102143 | Discussion on MTC gateway for capillary network | ITRI | imported from 3GU |
S1‑102144 | On MTC Features and MTC functionality | KPN | imported from 3GU |
S1‑102145 | CR 22.368: clarification of subscription | KPN | imported from 3GU |
S1‑102146 | MTC use case: multiple applications on a device | KPN | imported from 3GU |
S1‑102147 | MTC Use case: limited user interface | KPN | imported from 3GU |
S1‑102148 | NIMTC - Congestion Requirement Discussion | Sierra Wireless | imported from 3GU |
S1‑102149 | NIMTC - CR Congestion Control Requirements | Sierra Wireless | imported from 3GU |
S1‑102150 | Withdrawn | - | imported from 3GU |
S1‑102151 | FS_MTCe - LTE Use Case | Sierra Wireless | imported from 3GU |
S1‑102152 | Clarification for SIPTO in HNB Subsystem | Huawei technologies | imported from 3GU |
S1‑102153 | Clarification on roaming in shared networks | Vodafone | imported from 3GU |
S1‑102154 | Proposed WID on Remote Local IP Access (RIPA) | NEC | imported from 3GU |
S1‑102155 | LS Response to CT1 and GERAN on introduction of RAN Sharing for GERAN | Vodafone/SA1 | imported from 3GU |
S1‑102156 | Supplemental Audio in NOVES | Qualcomm Inc. | imported from 3GU |
S1‑102157 | Withdrawn | - | imported from 3GU |
S1‑102158 | Withdrawn | - | imported from 3GU |
S1‑102159 | Withdrawn | - | imported from 3GU |
S1‑102160 | Use case: Usage of IPv4/6 addresses in MTC Services, and corresponding Requirements | InterDigital, Communications, LLC | imported from 3GU |
S1‑102161 | Use case: MTC Group-based/Co-located MTC Devices, and corresponding Requirements | InterDigital, Communications, LLC | imported from 3GU |
S1‑102162 | Use case: MTC Service Classes for MTC Devices, and corresponding Requirements | InterDigital, Communications, LLC | imported from 3GU |
S1‑102163 | Reply LS to C1-102890 on inhibiting the allowed CSG list | Telecom Italia | imported from 3GU |
S1‑102164 | Discussion about CSG Cell Reselection Testing | Telecom Italia | imported from 3GU |
S1‑102165 | LS on CSG reselection and performances | Telecom Italia | imported from 3GU |
S1‑102166 | Comments on Business Model for FS_VINE | Tatara Systems | imported from 3GU |
S1‑102167 | Comments on Reference Architecture for FS_VINE | Tatara Systems | imported from 3GU |
S1‑102168 | Use Cases for FS_VINE | Tatara Systems | imported from 3GU |
S1‑102169 | Clarification for SIPTO for HNB subsystem | Huawei | Withdrawn |
S1‑102170 | NOVES updates | AT&T | Handled by NOVES |
S1‑102171 | NOVES Requirements Section Updates | AT&T | Handled by NOVES |
S1‑102172 | NOVES Annex A Updates | AT&T | Handled by NOVES |
S1‑102173 | Use cases and suggested requirements for key issue 3 in TR 23.813 | Ericsson | See related CR in S1-102181.Revised to S1-102396 |
S1‑102174 | Draft Work Item on Network Resource Usage Control | Vodafone, Verizon Wireless | Revised to S1-102395. |
S1‑102175 | LS to GSMA IWG on Advanced IP Interconnect Requirements | SA1 | Approved. |
S1‑102176 | Discussion about CSG Cell Reselection Testing | Telecom Italia | Handled by HNB |
S1‑102177 | LS on CSG reselection and performances | Telecom Italia | Revised to S1-102184 |
S1‑102178 | Alignment on ACB for CSFB | NTT DOCOMO, NTC | Agreed. |
S1‑102179 | LS to CT3 on supplementary services classification on II-NNI | Orange | Revised to S1-102185 |
S1‑102180 | Priority for data bearer services | Qualcomm Incorporated | Agreed. |
S1‑102181 | QoS and gating based on spending limit | Ericsson, Vodafone, Verizon Wireless, Alcatel-Lucent, AT&T | Revised to S1-102394 |
S1‑102182 | Reply LS to ' LS on Network provided Location information for IMS Charging' | Nokia Siemens Networks | Revised to S1-102183 |
S1‑102183 | Reply LS to SA5 (Cc SA2, CT1) on Network provided Location information for IMS Charging | SA1 | Approved. |
S1‑102184 | LS on CSG reselection and performances | Telecom Italia | Withdrawn. |
S1‑102185 | LS to CT3 on supplementary services classification on II-NNI | SA1 | Approved. |
S1‑102186 | Proposed Study Item related to S1-102040. | Alcatel-Lucent | Revised to S1-102295 |
S1‑102187 | LS CT6 (Cc CT1) on Clarification of TS 21.101 requirements for UICC access to IMS | Gemalto/SA1 | Revised to S1-102393 |
S1‑102188 | Removal of unfulfilled requirements | Research In Motion, Samsung, Nokia, Nokia Siemens Networks | Agreed. |
S1‑102189 | Not used | - | Not used |
S1‑102190 | Removal of requirement to inhibit Allowed CSG List | Vodafone, Qualcomm Incorporated, Deutsche Telekom, Telecom Italia | Agreed. |
S1‑102191 | Removal of requirement to inhibit Allowed CSG List and VPLMN Autonomous CSG Roaming clarifications | Vodafone, Qualcomm Incorporated, Deutsche Telekom, Telecom Italia | Revised off-line to S1-102386 |
S1‑102192 | CR to 22.220 (Rel-10) on Removal of requirement to inhibit Allowed CSG List | Vodafone, QC | Handled by HNB |
S1‑102193 | Clarification of LIPA requirements | Huawei, Verizon Wireless, Vodafone, Alcatel-Lucent | Revised to S1-102402 |
S1‑102194 | SIPTO mobility/continuity | Vodafone, Verizon Wireless | Revised to S1-102403 |
S1‑102195 | Correction on HNB Name | NEC | Revised to S1-102399 |
S1‑102196 | Draft Reply LS on LIPA/SIPTO stage 1 clarification | Vodafone | Handled by HNB |
S1‑102197 | SIPTO for H(e)NB Subsystems Policy and User Interaction | Vodafone, Verizon Wireless | Agreed |
S1‑102198 | SWG report | SWG chair | Approved. |
S1‑102199 | Proposed updates to the system-wide BBAI WID (revision of SP-100222) | Huawei, T. Italia, Ericsson | Agreed |
S1‑102200 | LS on M2M Numbering Concerns | 3GPP2 Steering Committee | Noted. The answer (if any) will be drafted in M2M SWG. |
S1‑102201 | LS on Remote Access CPNs | C1-101756 | Postponed, check at next meeting if SA1 is also going to work on this topic. |
S1‑102202 | LS on EU-Alert requirements | C1-102552 | Noted. |
S1‑102203 | Reply LS on CSG access in VPLMN | C1-102887 | Noted without presentation. |
S1‑102204 | LS on Inhibiting the Allowed CSG List | C1-102890 | Handled by HNB |
S1‑102205 | Reply LS on Access Control for CSFB | C1-102893 | Noted, see S1-102220. |
S1‑102206 | Response LS on introduction of RAN Sharing for GERAN | C1-102902 | See proposed related CR in S1-102153. |
S1‑102207 | LS on supplementary services classification on II-NNI | C3-100689 | See the proposed answer in S1-102062. |
S1‑102208 | LS on Clarification of TS 21.101 requirements for UICC access to IMS | C6-100262 | See related document in S1-102066. |
S1‑102209 | LS on CSG access in VPLMN | C6-100291 | Noted without presentation. |
S1‑102210 | LS on European Public Warning System (EU-Alert) using the CBS | CP-100429 | Noted without presentation. |
S1‑102211 | LS on ECMA TR/101 – NGCN Emergency Calls | EMTEL(10)0053 | Noted without presentation. |
S1‑102212 | LS on TS 102 900 on European Public Warning System (EU-ALERT) using the Cell Broadcast Service | EMTEL(10)0054 | Noted. |
S1‑102213 | LS on introduction of RAN Sharing for GERAN | GP-100969 | See CT1's answer in S1-102206. |
S1‑102214 | LS on Handling of Hybrid cells | GP-101089 | Handled by HNB |
S1‑102215 | LS on Advance requirements for IP Interconnect of Services | GSMA IWG Doc 12_020 | See proposed naswer in S1-102175. |
S1‑102216 | LS on Consent of Recommendation G.9971 “Requirements of transport functions in IP home networks” | ITU COM 15 – LS 183 | Noted without presentation. |
S1‑102217 | LS on Responses to questions on Service User Profile Management | OMA-LS_867 | Noted. |
S1‑102218 | Response LS on CSG Cell Reselection testing | R2-103459 | Handled by HNB |
S1‑102219 | Reply LS on Handling of Hybrid Cells (GP-101089/R2-103487) | R2-104125 | Handled by HNB |
S1‑102220 | Reply LS on Access Control for CSFB | R2-104127 | Noted. See S1-102019 on this topic. |
S1‑102221 | LS to 3GPP CT1 on mechanism to disable the use of SIGCOMP. | GSMA RILTE Doc 08_019 | See CT1's answer in S1-102234. |
S1‑102222 | LS on LIPA/SIPTO stage 1 clarification | S2-102940 | Handled by HNB |
S1‑102223 | LS on Emergency Call | S2-103042 | Noted. |
S1‑102224 | LS on Work on second edition ECMA TR/101 on Emergency Calls | S2-103043 | Noted without presentation. |
S1‑102225 | LS on Network provided Location information for IMS Charging | S5-101958 | See proposed answer in S1-102182. |
S1‑102226 | LS on H(e)NB related LI requirements | SA3LI10_056r2 | Noted without presentation. |
S1‑102227 | LS on CAT and CRS related LI requirements | SA3LI10_057 | Noted without presentation. |
S1‑102228 | LS on Study on SSO Application Security for IMS - based on SIP Digest | SP-100439 | Noted. |
S1‑102229 | LS on Guidance on NIMTC Security | SP-100443 | Noted. |
S1‑102230 | LS on “Mobile Wireless access systems providing telecommunications for a large number of ubiquitous sensors and/or actuators scattered over wide areas in the land mobile service” | RT-100054 | Noted/agreed. |
S1‑102231 | Clarification of TS 21.101 requirements for UICC access to IMS | C6-100262 | Withdrawn, duplicated. |
S1‑102232 | LS on Remote Access CPNs | C1-101756 | Withdrawn, duplicated. |
S1‑102233 | LS on LIPA/SIPTO stage 1 clarification | S2-102940 | Withdrawn, duplicated. |
S1‑102234 | Reply to CT1 on mechanism to disable SIGCOMP on the UE. | GSMA 09_013r2 | Noted. |
S1‑102235 | 3GPP2 Status on M2M Numbering | 3GPP2 Steering Committee TIA | Noted, to be handled with S1-102200. |
S1‑102236 | IREG LS_038 to 3GPP on OMR drawbacks | GSMA RILTE 10_007r1 | Noted. |
S1‑102237 | Not used | - | Not used |
S1‑102238 | Not used | - | Not used |
S1‑102239 | Not used | - | Not used |
S1‑102240 | Not used | - | Not used |
S1‑102241 | Not used | - | Not used |
S1‑102242 | Not used | - | Not used |
S1‑102243 | Not used | - | Not used |
S1‑102244 | Not used | - | Not used |
S1‑102245 | Not used | - | Not used |
S1‑102246 | Not used | - | Not used |
S1‑102247 | Not used | - | Not used |
S1‑102248 | Not used | - | Not used |
S1‑102249 | Not used | - | Not used |
S1‑102250 | SWG presentation (PPT) | SWG chair | Noted. |
S1‑102251 | Report of NIMTC SWG | Chairman | Handled by M2M |
S1‑102252 | Draft agenda for M2M SWG | M2M SWG Chair | Handled by M2M |
S1‑102253 | 22.368: Clarification of subscription | KPN (rapporteur) | Handled by M2M |
S1‑102254 | LS to SA (Cc SA2) on MTC Features and MTC Functionality | KPN | Revised to S1-102291 |
S1‑102255 | 22.368: Clarification on MTC Server relationship to network operator | KDDI | Handled by M2M |
S1‑102256 | Study on alternatives for E.164 for machine type communications | T-Mobile | Handled by M2M |
S1‑102257 | MTC Time Controlled clarification | Samsung | Revised to S1-102290 |
S1‑102258 | Simplification of Mobile Originated Only feature | KDDI | Agreed |
S1‑102259 | Simplification of Infrequent Mobile Terminated feature | KDDI | Agreed |
S1‑102260 | Clarification of MTC Monitoring feature | KDDI | Agreed |
S1‑102261 | Addition of definition and Scenarios for communication via MTC Gateway | ZTE Corporation, Panasonic, Alcatel-Lucent Shanghai Bell, Alcatel-Lucent, ITRI | Handled by M2M |
S1‑102262 | 22.368: Avoiding Abuse of Priority Alarm | Panasonic, China Mobile, ZTE | Withdrawn |
S1‑102263 | 22.368: Clarification of Location Specific Trigger | KDDI | Handled by M2M |
S1‑102264 | Clarification of Group Based MTC Features | KDDI, Samsung | Agreed |
S1‑102265 | LS on Congestion Control Requirements in TS 22.368 | Sierra Wireless | Handled by M2M |
S1‑102266 | Study on alternatives for E.164 for machine type communications | T-Mobile | Handled by M2M |
S1‑102267 | Paper discussion on E.164 number shortage for M2M | France Telecom - Orange | Handled by M2M |
S1‑102268 | Text for TR 'Study on Alternatives to E.164 for MTC' | Telefónica S.A. | Handled by M2M |
S1‑102269 | Use case: Usage of IPv4/6 addresses in MTC Services, and corresponding | InterDigital Communications, LLC | Handled by M2M |
S1‑102270 | Study on Alternatives to E.164 for Machine-Type Communications | Rapporteur (T-Mobile) | Approved as a basis for future contributions. |
S1‑102271 | LTE UE for MTC Use Case | Sierra Wireless | Handled by M2M |
S1‑102272 | LS to SA(Cc SA2) on SA1#52 process regarding Release 10 and Release 11 versions of TS 22.368 | Rapporteur | Noted. |
S1‑102273 | Draft LS to CT, CT1, CT3, CT4 (Cc SA, SA2) on Direct stage 3 work for NIMTC functionality | Rapporteur | Revised to S1-102292 |
S1‑102274 | Addition of definition and Scenarios for communication via MTC Gateway | ZTE Corporation, Panasonic, Alcatel-Lucent Shanghai Bell, Alcatel-Lucent, ITRI | Handled by M2M |
S1‑102275 | Addition of MTC Device-to-Device Communication Scenarios | ZTE Corporation, China Mobile, Panasonic | Handled by M2M |
S1‑102276 | Use Case for Co-located MTC Devices | Panasonic, Alcatel-Lucent Shanghai Bell, Alcatel-Lucent, China Mobile, | Handled by M2M |
S1‑102277 | Use Case for Location Tracking | Panasonic, Alcatel-Lucent Shanghai Bell, Alcatel-Lucent, China Mobile, ZTE, | Handled by M2M |
S1‑102278 | MTC use case: multiple applications on a device | KPN | Handled by M2M |
S1‑102279 | Intfroduction and scope for FS-MTCe | Huawei technologies | Handled by M2M |
S1‑102280 | Clarification of subscription | KPN (rapporteur) | Agreed |
S1‑102281 | Clarification on MTC Server relationship to network operator | KDDI | Agreed |
S1‑102282 | Clarification of Location Specific Trigger | KDDI | Agreed |
S1‑102283 | LS to SA2 on Congestion Control Requirements in TS 22.368 | Sierra Wireless | Revised to S1-102293 |
S1‑102284 | Use case: Usage of IPv4/6 addresses in MTC Services, and corresponding | InterDigital Communications, LLC | Handled by M2M |
S1‑102285 | Draft LS to 3GPP2 (Cc SA) on Study Item on Alternatives for E.164 for Machine Type Communications | Rapporteur | Revised to S1-102294 |
S1‑102286 | Study on Machine Type Communication Enhancements | Rapporteur (Huawei) | Approved as a basis for future contributions. |
S1‑102287 | MTC Group Features definition clarification | Samsung | Agreed. |
S1‑102288 | MTC Infrequent Transmission clarification | Samsung | Agreed. |
S1‑102289 | MTC Secure Connection | Samsung | Agreed. |
S1‑102290 | MTC Time Controlled clarification | Samsung | Agreed. |
S1‑102291 | LS to SA (Cc SA2) on MTC Features and MTC Functionality | SA1 | Approved. |
S1‑102292 | LS to CT, CT1, CT3, CT4 (Cc SA, SA2) on Direct stage 3 work for NIMTC functionality | SA1 | Approved. |
S1‑102293 | LS to SA2 on Congestion Control Requirements in TS 22.368 | SA1 | Approved. |
S1‑102294 | Draft LS to 3GPP2 (Cc SA) on Study Item on Alternatives for E.164 for Machine Type Communications | SA1 | Approved. |
S1‑102295 | Proposed Study Item related to S1-102040. | Alcatel-Lucent | Revised to S1-102409 |
S1‑102296 | Not used | - | Not used |
S1‑102297 | Not used | - | Not used |
S1‑102298 | Not used | - | Not used |
S1‑102299 | Not used | - | Not used |
S1‑102300 | SWG presentation (PPT) | SWG chair | Noted. |
S1‑102301 | Not used | - | Not used |
S1‑102302 | 22.278: Clarifications on FMC use cases | Huawei, T. Italia | Handled by BBAI |
S1‑102303 | Adding a Application Mobility use case to FMC use cases | Huawei, Telecom Italia | Agreed |
S1‑102304 | 22.278: Adding a Common Quota use case to FMC use cases | Huawei, T. Italia | Handled by BBAI |
S1‑102305 | 22.278: Adding refernece for H(e)NB in Fixed Mobile Interworking requirements | Huawei, T. Italia | Handled by BBAI |
S1‑102306 | 22.278: New Requirements for Fixed Mobile Convergence scenario | Huawei, Telecom Italia, Vodafone | Handled by BBAI |
S1‑102307 | Clarifications on FMC use cases | Huawei, Telecom Italia | Agreed |
S1‑102308 | Adding a Common Quota use case to FMC use cases | Huawei, Telecom Italia | Agreed |
S1‑102309 | New Requirements for Fixed Mobile Convergence scenario | Huawei, Telecom Italia, Vodafone | Agreed. |
S1‑102310 | Report of SWG H(e)NB | SWG chair | Approved. |
S1‑102311 | Presentation of SWG H(e)NB | SWG chair | Noted. |
S1‑102312 | Agenda for H(e)NB SWG | H(e)NB Chairman | Handled by HNB |
S1‑102313 | Agenda for H(e)NB SWG | H(e)NB Chairman | Handled by HNB |
S1‑102314 | LS to CT1, CT4, CT6, SA2 on Inhibiting the Allowed CSG List | SA1/Vodafone | Approved. |
S1‑102315 | Clarification of SIPTO user interaction | Vodafone | Agreed. |
S1‑102316 | CR to 22.220 on User awareness of SIPTO for H(e)NB subsystems | Vodafone | Handled by HNB |
S1‑102317 | CR to 22.220 on LIPA_SIPTO requirement clarification when considering access mode of H(e)NB | ZTE | Handled by HNB |
S1‑102318 | Draft WID on LIPA/SIPTO-related Mobility | VF, VZ | Handled by HNB |
S1‑102319 | CR to 22.220 on LIPA_SIPTO requirement clarification when considering access mode of H(e)NB | ZTE | WITHDRAWN |
S1‑102320 | Clarification of regulatory requirements and enablement/disablement policies for LIPA/SIPTO | ALU, VF | Handled by HNB |
S1‑102321 | CR to 22.220 Correction on HNB Name | NEC | Handled by HNB |
S1‑102322 | Clarification of regulatory requirements and enablement/disablement policies for LIPA/SIPTO | Alcatel-Lucent, Vodafone | Revised to S1-102400 |
S1‑102323 | Draft WID on SIPTO Service Continuity of IP Data Session | Vodafone, Verizon | Revised to S1-102401 |
S1‑102324 | Proposed WID on Remote Local IP Access (RIPA) | NEC | WITHDRAWN |
S1‑102325 | LS to GERAN (Cc RAN2) on Handling of Hybrid cells | Vodafone | Approved. |
S1‑102326 | Draft Reply LS on LIPA/SIPTO stage 1 clarification | Vodafone | Handled by HNB |
S1‑102327 | Clarification of LIPA requirements | Huawei | Handled by HNB |
S1‑102328 | CR to 22.220 on User awareness of SIPTO for H(e)NB subsystems | Vodafone | Handled by HNB |
S1‑102329 | Clarification of regulatory requirements and enablement/disablement policies for LIPA/SIPTO | Alcatel-Lucent, Vodafone | Handled by HNB |
S1‑102330 | SWG presentation (PPT) | SWG chair | Revised to S1-102339 |
S1‑102331 | Contribution to TR 22.817 “UICC/USIM enhancements Study” – Chapter 4 – Update of Use Cases – User Experience | Sagem Orga (Morpho) | Handled by U2 |
S1‑102332 | Contribution to TR 22.817 “UICC/USIM enhancements Study” – Chapter 4 – Update of Use Cases – Update of an UE application | Sagem Orga (Morpho) | Handled by U2 |
S1‑102333 | Contribution to TR 22.817 “UICC/USIM enhancements Study” – Chapter 4 – Update of Use Cases – Secure Application | Sagem Orga (Morpho) | Handled by U2 |
S1‑102334 | Allocated by U2 | - | WITHDRAWN |
S1‑102335 | Contribution to TR 22.817 “UICC/USIM enhancements Study” – Revision of document structure | Sagem Orga (Morpho) | Handled by U2 |
S1‑102336 | TR 22.817 v.0.2.0 on Study on UICC/USIM enhancements | Editor | Handled by U2 |
S1‑102337 | Temporary version of TR 22.817 | Editor | Handled by U2 |
S1‑102338 | TR 22.817 v.0.2.0 | Editor | Agreed as a basis for future contribution |
S1‑102339 | SWG presentation (PPT) | SWG chair | Noted. |
S1‑102340 | SWG presentation (PPT) | SWG chair | Noted. |
S1‑102341 | SWG agenda | SWG | Handled by NOVES |
S1‑102342 | New definitions | SWG | Handled by NOVES |
S1‑102343 | Revised 2030 | RIM | Handled by NOVES |
S1‑102344 | Revised 2096 | FT | Handled by NOVES |
S1‑102345 | Revised 2113 | ALU | Handled by NOVES |
S1‑102346 | Revised 2132 | Motorola | Handled by NOVES |
S1‑102347 | Revised 2100 | ZTE et al | Handled by NOVES |
S1‑102348 | Revised 2170 | AT&T | Handled by NOVES |
S1‑102349 | Revised 2171 | AT&T | Handled by NOVES |
S1‑102350 | STF399 presentation | STF399 | Handled by NOVES |
S1‑102351 | Conclusion text for non session | RIM | Handled by NOVES |
S1‑102352 | Revised 2342 | SWG | Handled by NOVES |
S1‑102353 | Revised 2346 | Motorola | Handled by NOVES |
S1‑102354 | Modifications to use case 4.6 | RIM | Handled by NOVES |
S1‑102355 | TR22.871 v1.1.0 | SWG | Agreed as a basis for future contributions. |
S1‑102356 | Report of NOVES | SWG Chair | Revised to S1-102357 |
S1‑102357 | Report of NOVES | SWG Chair | Agreed. |
S1‑102358 | Not used | - | Not used |
S1‑102359 | Not used | - | Not used |
S1‑102360 | SWG presentation (PPT) | SWG chair | Noted. |
S1‑102361 | VINE SWG Report | SWG Chair | Handled by VINE |
S1‑102362 | VINE SWG Agenda | SWG Chair | Handled by VINE |
S1‑102363 | Revised 2045 | Tatara Systems | Handled by VINE |
S1‑102364 | Revised 2140 | Verizon Wireless, Vodafone, Deutsche Telekom, Cisco, Tatara | Handled by VINE |
S1‑102365 | Revised 2093 | China Mobile | Handled by VINE |
S1‑102366 | Revised 2136 | Ericsson | Handled by VINE |
S1‑102367 | Revised 2016 | Vodafone, Verizon Wireless | Handled by VINE |
S1‑102368 | Revised 2362 | SWG Chair | Handled by VINE |
S1‑102369 | Revised 2020 | Alcatel-Lucent | Handled by VINE |
S1‑102370 | Revised 2023 | Alcatel-Lucent | Withdrawn |
S1‑102371 | Revised 2366 | Ericsson | Handled by VINE |
S1‑102372 | Revised 2365 | China Mobile | Handled by VINE |
S1‑102373 | Revised 2367 | Vodafone, Verizon Wireless | Handled by VINE |
S1‑102374 | Revised 2364 | Verizon Wireless, Vodafone, Deutsche Telekom, Cisco, Tatara | Handled by VINE |
S1‑102375 | Revised 2374 | Verizon Wireless, Vodafone, Deutsche Telekom, Cisco, Tatara | Handled by VINE |
S1‑102376 | Proposed text for Background (Sect. 4) | Tatara Systems | Handled by VINE |
S1‑102377 | Revised 2369 | Alcatel-Lucent | Handled by VINE |
S1‑102378 | Revised 2376 | Tatara Systems | Handled by VINE |
S1‑102379 | TR22.8de v0.1.0 | Rapporteur | Approved as a basis for future contribution. |
S1‑102380 | Not used | - | Not used |
S1‑102381 | Not used | - | Not used |
S1‑102382 | Not used | - | Not used |
S1‑102383 | Not used | - | Not used |
S1‑102384 | Not used | - | Not used |
S1‑102385 | LS to SA3 on Security for PWS | SA1/Vodafone | Approved. |
S1‑102386 | Removal of requirement to inhibit Allowed CSG List and VPLMN Autonomous CSG Roaming clarifications | Vodafone, Qualcomm Incorporated, Deutsche Telekom, Telecom Italia | Revised to S1-102388 |
S1‑102387 | Alignment of Transfer of Control requirements | Huawei, Orange | Agreed. |
S1‑102388 | Removal of requirement to inhibit Allowed CSG List and VPLMN Autonomous CSG Roaming clarifications | Vodafone, Qualcomm Incorporated, Deutsche Telekom, Telecom Italia | Agreed. |
S1‑102389 | Charging considerations for MMTel when Optimal Media Routeing is used | Deutsche Telekom | Revised to S1-102391 |
S1‑102390 | Correction to ATSI and ATM for missing SS codes | Vodafone, Nokia Siemens Networks, | Agreed. |
S1‑102391 | Charging considerations for MMTel when Optimal Media Routeing is used | Deutsche Telekom | Agreed. |
S1‑102392 | Checking Rapporteurship of SA1 specs | NEC | Revised to S1-102410 |
S1‑102393 | LS CT6 (Cc CT1) on Clarification of TS 21.101 requirements for UICC access to IMS | Gemalto/SA1 | Revised to S1-102397 |
S1‑102394 | QoS and gating based on spending limit | Ericsson, Vodafone, Verizon Wireless, Alcatel-Lucent, AT&T | Agreed. |
S1‑102395 | Draft Work Item on Network Resource Usage Control | Vodafone, Verizon Wireless | Agreed |
S1‑102396 | LS to SA2, SA5 on Use cases and suggested requirements for key issue 3 in TR 23.813 (QoS and gating based on spending limits) | Ericsson/SA1 | Approved. |
S1‑102397 | LS CT6 (Cc CT1, SA3) on Clarification of TS 21.101 requirements for UICC access to IMS | Gemalto/SA1 | Approved. |
S1‑102398 | Reply LS to CT 1, TISPAN 5 (Cc SA2, SA3, CT3, CT, SA) to “LS on Remote Access CPNs” | Ericsson | Approved. |
S1‑102399 | Correction on HNB Name | NEC | Agreed. |
S1‑102400 | Clarification of regulatory requirements and enablement/disablement policies for LIPA/SIPTO | Alcatel-Lucent, Vodafone | Agreed. |
S1‑102401 | Draft WID on SIPTO Service Continuity of IP Data Session | Vodafone, Verizon | Agreed. |
S1‑102402 | Clarification of LIPA requirements | Huawei, Verizon Wireless, Vodafone, Alcatel-Lucent | Revised to S1-102404 |
S1‑102403 | SIPTO mobility/continuity | Vodafone, Verizon Wireless | Agreed. |
S1‑102404 | Clarification of LIPA requirements | Huawei, Verizon Wireless, Vodafone, Alcatel-Lucent | Agreed. |
S1‑102405 | IMS application services across IMS-NNI | KPN | Revised to S1-102407 |
S1‑102406 | Draft WID on Operator-Independent Public User Identities | Vodafone | Noted. |
S1‑102407 | IMS application services across IMS-NNI | KPN | Agreed. |
S1‑102408 | Not allocated | - | Not allocated |
S1‑102409 | Study on Integration of Single Sign-On (SSO) frameworks with 3GPP networks | Alcatel-Lucent | Agreed. |
S1‑102410 | Checking Rapporteurship of SA1 specs | NEC | Agreed. |
page generated from database: 2024-04-22 07:58:53