3GPP TDocs (written contributions) at meeting
Meeting: S1-61 - 2013-01-28 to 2013-02-01, Prague
meeting id: S1-61 (click id for more info on this meeting)Click on the Tdoc to open its file.
| TDoc | Title | Source | Remarks |
|---|---|---|---|
| S1‑130013 | - | - | imported from 3GU |
| S1‑130016 | - | - | imported from 3GU |
| S1‑130017 | - | - | imported from 3GU |
| S1‑130018 | - | - | imported from 3GU |
| S1‑130019 | - | - | imported from 3GU |
| S1‑130024 | - | - | imported from 3GU |
| S1‑130031 | - | - | imported from 3GU |
| S1‑130033 | - | - | imported from 3GU |
| S1‑130034 | - | - | imported from 3GU |
| S1‑130036 | - | - | imported from 3GU |
| S1‑130049 | FS_ProSe: Operator A uses ProSe to Enhance Location and Presence Services - use case description in 5.1.7.1 is incorrectly phrased | General Dynamics Broadband UK | imported from 3GU |
| S1‑130071 | - | - | imported from 3GU |
| S1‑130076 | - | - | imported from 3GU |
| S1‑130077 | - | - | imported from 3GU |
| S1‑130082 | - | - | imported from 3GU |
| S1‑130083 | - | - | imported from 3GU |
| S1‑130086 | - | - | imported from 3GU |
| S1‑130093 | - | - | imported from 3GU |
| S1‑130105 | - | - | - |
| S1‑130112 | New WLAN Requirement: Accounting Data Collection | China Mobile, ITRI | - |
| S1‑130117 | - | - | - |
| S1‑130119 | - | - | - |
| S1‑130120 | - | - | - |
| S1‑130128 | Clarify what configured stands for | Huawei, Hisilicon | - |
| S1‑130130 | - | - | - |
| S1‑130134 | Definitions for ProSe relay types | General Dynamics Broadband UK | - |
| S1‑130155 | - | - | - |
| S1‑130157 | On missing statements pertaining to Network coverage (or otherwise) of UEs in the Public Safety use cases | General Dynamics Broadband UK | - |
| S1‑130158 | - | - | - |
| S1‑130160 | UE with Multiple One-to-One Direct User Traffic Sessions in Public Safety Spectrum Dedicated to ProSe - use case potential requirement clarification | General Dynamics Broadband UK | - |
| S1‑130161 | The ProSe Communication path is a E-UTRAN path | Huawei, Hisilicon | - |
| S1‑130162 | ProSe Group - use case has orphaned text in the potential requirements section | General Dynamics Broadband UK | - |
| S1‑130163 | Remaining details of the Co-existence of ProSe Communication and E-UTRAN communication Public Safety use case | General Dynamics Broadband UK | - |
| S1‑130165 | - | - | - |
| S1‑130166 | - | - | - |
| S1‑130167 | - | - | - |
| S1‑130168 | - | - | - |
| S1‑130169 | - | - | - |
| S1‑130170 | - | - | - |
| S1‑130171 | Correction to Control paths for ProSe Communication | ETRI, ITRI, Institute for Information Industry (II | - |
| S1‑130172 | Clarification in discussion of control paths for ProSe Communications in section 4.2 | General Dynamics Broadband UK | - |
| S1‑130174 | - | - | - |
| S1‑130178 | Definition of range class | Telecom Italia, Deutsche Telecom | - |
| S1‑130179 | Clarify network coverage means E-UTRAN coverage | Vodafone, Renesas Mobile Europe Ltd | - |
| S1‑130180 | Service Continuity between Infrastructure and E-UTRA ProSe Communication paths - use case is missing a description section | General Dynamics Broadband UK | - |
| S1‑130181 | Merge similar Potential requirement | Huawei, Hisilicon, China Mobile | - |
| S1‑130182 | Remove requirement that the id of the 3rd party applications developer needs to be stored | Motorola Solutions | - |
| S1‑130184 | Editorial Updates to Requirements | Intel | - |
| S1‑130185 | - | - | - |
| S1‑130187 | - | - | - |
| S1‑130189 | - | - | - |
| S1‑130195 | Additional clarifying text for public safety potential requirements | US Department of Commerce | - |
| S1‑130196 | Potential requirements consolidation - editorial changes | Qualcomm | - |
| S1‑130199 | - | - | - |
| S1‑131000 | - | - | imported from 3GU |
| S1‑131001 | - | - | imported from 3GU |
| S1‑131002 | - | - | imported from 3GU |
| S1‑131003 | - | - | imported from 3GU |
| S1‑131004 | - | - | imported from 3GU |
| S1‑131005 | - | - | imported from 3GU |
| S1‑131006 | - | - | imported from 3GU |
| S1‑131007 | Minutes of SA1 GCSE_LTE ad hoc | ETSI Secretariat | - |
| S1‑131008 | - | - | imported from 3GU |
| S1‑131009 | - | - | imported from 3GU |
| S1‑131010 | - | - | imported from 3GU |
| S1‑131011 | - | - | imported from 3GU |
| S1‑131012 | - | - | imported from 3GU |
| S1‑131013 | - | - | imported from 3GU |
| S1‑131014 | - | - | imported from 3GU |
| S1‑131015 | - | - | imported from 3GU |
| S1‑131016 | - | - | imported from 3GU |
| S1‑131017 | - | - | imported from 3GU |
| S1‑131018 | - | - | imported from 3GU |
| S1‑131019 | Prioritization of ACDC Applications | Intel and Sony Mobile Communication | - |
| S1‑131020 | Regional Differences in ACDC | Intel | - |
| S1‑131021 | - | - | imported from 3GU |
| S1‑131022 | - | - | imported from 3GU |
| S1‑131023 | - | - | imported from 3GU |
| S1‑131024 | - | - | imported from 3GU |
| S1‑131025 | - | - | imported from 3GU |
| S1‑131026 | - | - | imported from 3GU |
| S1‑131027 | - | - | imported from 3GU |
| S1‑131028 | - | - | imported from 3GU |
| S1‑131029 | - | - | imported from 3GU |
| S1‑131030 | - | - | imported from 3GU |
| S1‑131031 | - | - | imported from 3GU |
| S1‑131032 | Q&A exchanges for Rel-12 WI Application specific Congestion control for Data Communication applied to heavy congestion scenarios and for Rel-12 WI Suppression of | NTT DOCOMO | - |
| S1‑131033 | - | - | imported from 3GU |
| S1‑131034 | Reply LS to oneM2M on service-layer interworking | S1 | imported from 3GU |
| S1‑131035 | - | - | imported from 3GU |
| S1‑131036 | - | - | imported from 3GU |
| S1‑131037 | - | - | imported from 3GU |
| S1‑131038 | - | - | imported from 3GU |
| S1‑131039 | - | - | imported from 3GU |
| S1‑131040 | - | - | imported from 3GU |
| S1‑131041 | IMS_WebRTC: CR to 22.101 | Intel | - |
| S1‑131042 | - | - | imported from 3GU |
| S1‑131043 | - | - | imported from 3GU |
| S1‑131044 | - | - | imported from 3GU |
| S1‑131045 | - | - | imported from 3GU |
| S1‑131046 | - | - | imported from 3GU |
| S1‑131047 | - | - | imported from 3GU |
| S1‑131048 | - | - | imported from 3GU |
| S1‑131049 | - | - | imported from 3GU |
| S1‑131050 | - | - | imported from 3GU |
| S1‑131051 | - | - | imported from 3GU |
| S1‑131052 | - | - | imported from 3GU |
| S1‑131053 | - | - | imported from 3GU |
| S1‑131054 | - | - | imported from 3GU |
| S1‑131055 | - | - | imported from 3GU |
| S1‑131056 | HeNB in the Shared RAN use case | Sprint | - |
| S1‑131057 | - | - | imported from 3GU |
| S1‑131058 | - | - | imported from 3GU |
| S1‑131059 | - | - | imported from 3GU |
| S1‑131060 | derived from Use Case 10 in TR22.805 | Telecom Italia | - |
| S1‑131061 | - | - | imported from 3GU |
| S1‑131062 | - | - | imported from 3GU |
| S1‑131063 | - | - | imported from 3GU |
| S1‑131064 | - | - | imported from 3GU |
| S1‑131065 | - | - | imported from 3GU |
| S1‑131066 | Cleanup of OAM access to hosting RAN requirement | Sprint | - |
| S1‑131067 | Proposal to address editor's note on application to connected and/or idle mode UEs | Sprint | - |
| S1‑131068 | LS on bulk charging | S1 | imported from 3GU |
| S1‑131069 | - | - | imported from 3GU |
| S1‑131070 | - | - | imported from 3GU |
| S1‑131071 | - | - | imported from 3GU |
| S1‑131072 | - | - | imported from 3GU |
| S1‑131073 | - | - | imported from 3GU |
| S1‑131074 | - | - | imported from 3GU |
| S1‑131075 | - | - | imported from 3GU |
| S1‑131076 | - | - | imported from 3GU |
| S1‑131077 | - | - | imported from 3GU |
| S1‑131078 | - | - | imported from 3GU |
| S1‑131079 | - | - | imported from 3GU |
| S1‑131080 | - | - | - |
| S1‑131081 | - | - | - |
| S1‑131082 | - | - | - |
| S1‑131083 | - | - | - |
| S1‑131084 | - | - | - |
| S1‑131085 | - | - | - |
| S1‑131086 | - | - | - |
| S1‑131087 | - | - | - |
| S1‑131088 | - | - | - |
| S1‑131089 | - | - | - |
| S1‑131090 | - | - | - |
| S1‑131099 | - | - | - |
| S1‑131100 | - | - | - |
| S1‑131101 | - | - | - |
| S1‑131102 | - | - | - |
| S1‑131103 | - | - | - |
| S1‑131104 | - | - | - |
| S1‑131105 | - | - | - |
| S1‑131106 | - | - | - |
| S1‑131107 | - | - | - |
| S1‑131108 | - | - | - |
| S1‑131109 | - | - | - |
| S1‑131110 | - | - | - |
| S1‑131111 | - | - | - |
| S1‑131112 | - | - | - |
| S1‑131113 | - | - | - |
| S1‑131114 | - | - | - |
| S1‑131115 | - | - | - |
| S1‑131116 | - | - | - |
| S1‑131117 | - | - | - |
| S1‑131118 | - | - | - |
| S1‑131120 | - | - | - |
| S1‑131121 | - | - | - |
| S1‑131122 | - | - | - |
| S1‑131123 | - | - | - |
| S1‑131124 | - | - | - |
| S1‑131125 | - | - | - |
| S1‑131127 | - | - | - |
| S1‑131128 | - | - | - |
| S1‑131129 | - | - | - |
| S1‑131130 | - | - | - |
| S1‑131131 | - | - | - |
| S1‑131132 | - | - | - |
| S1‑131133 | - | - | - |
| S1‑131134 | - | - | - |
| S1‑131135 | - | - | - |
| S1‑131136 | - | - | - |
| S1‑131137 | - | - | - |
| S1‑131140 | - | - | - |
| S1‑131141 | - | - | - |
| S1‑131143 | - | - | - |
| S1‑131144 | - | - | - |
| S1‑131145 | - | - | - |
| S1‑131146 | - | - | - |
| S1‑131147 | - | - | - |
| S1‑131148 | - | - | - |
| S1‑131149 | - | - | - |
| S1‑131150 | - | - | - |
| S1‑131151 | - | - | - |
| S1‑131155 | - | - | - |
| S1‑131156 | - | - | - |
| S1‑131157 | - | - | - |
| S1‑131158 | - | - | - |
| S1‑131159 | - | - | - |
| S1‑131160 | - | - | - |
| S1‑131162 | - | - | - |
| S1‑131163 | - | - | - |
| S1‑131164 | - | - | - |
| S1‑131165 | - | - | - |
| S1‑131166 | - | - | - |
| S1‑131167 | - | - | - |
| S1‑131168 | - | - | - |
| S1‑131169 | - | - | - |
| S1‑131170 | - | - | - |
| S1‑131171 | - | - | - |
| S1‑131172 | - | - | - |
| S1‑131173 | - | - | - |
| S1‑131174 | - | - | - |
| S1‑131175 | - | - | - |
| S1‑131176 | - | - | - |
| S1‑131177 | - | - | - |
| S1‑131178 | - | - | - |
| S1‑131179 | - | - | - |
| S1‑131180 | - | - | - |
| S1‑131181 | LS on Network Resilience for Public Safety communications. | S1 | - |
| S1‑131182 | - | - | - |
| S1‑131183 | - | - | - |
| S1‑131184 | - | - | - |
| S1‑131185 | - | - | - |
| S1‑131186 | - | - | - |
| S1‑131187 | - | - | - |
| S1‑131188 | - | - | - |
| S1‑131189 | - | - | - |
| S1‑131190 | - | - | - |
| S1‑131191 | - | - | - |
| S1‑131192 | - | - | - |
| S1‑131193 | Rewording of direct link into proSe Communication | Huawei, Hisilicon, China Mobile | - |
| S1‑131194 | - | - | - |
| S1‑131195 | - | - | - |
| S1‑131196 | - | - | - |
| S1‑131197 | - | - | - |
| S1‑131198 | - | - | - |
| S1‑131199 | - | - | - |
| S1‑131200 | - | - | - |
| S1‑131201 | - | - | - |
| S1‑131202 | - | - | - |
| S1‑131203 | - | - | - |
| S1‑131204 | - | - | - |
| S1‑131205 | - | - | - |
| S1‑131206 | - | - | - |
| S1‑131207 | - | - | - |
| S1‑131208 | - | - | - |
| S1‑131209 | - | - | - |
| S1‑131210 | - | - | - |
| S1‑131211 | - | - | - |
| S1‑131212 | - | - | - |
| S1‑131213 | Language and Modality Information for communications | Orange, France Telecom, Huawei, Qualcomm, Sprint | - |
| S1‑131214 | - | - | - |
| S1‑131216 | - | - | - |
| S1‑131217 | - | - | - |
| S1‑131218 | - | - | - |
| S1‑131219 | General corrections to section 5.2 | General Dynamics Broadband UK | - |
| S1‑131220 | - | - | - |
| S1‑131221 | - | - | - |
| S1‑131222 | - | - | - |
| S1‑131223 | - | - | - |
| S1‑131224 | - | - | - |
| S1‑131226 | Add Requirement on emergency IM CN subsystem | Telecom Italia, Huawei, Ericsson,Orange, Qualcomm, | - |
| S1‑131227 | Reply LS on Use of Dialled Digit Information in Emergency Calls (S1-131100/C1-124133) | S1 | - |
| S1‑131228 | - | - | - |
| S1‑131229 | - | - | - |
| S1‑131230 | - | - | - |
| S1‑131231 | - | - | - |
| S1‑131232 | - | - | - |
| S1‑131233 | - | - | - |
| S1‑131234 | - | - | - |
| S1‑131235 | - | - | - |
| S1‑131236 | - | - | - |
| S1‑131237 | Answer to SA2's questions for JM2 SA2 95 / SA1 61 in S2-130532 | S1 | - |
| S1‑131238 | - | - | - |
| S1‑131239 | - | - | - |
| S1‑131240 | - | - | - |
| S1‑131241 | - | - | - |
| S1‑131242 | - | - | - |
| S1‑131243 | - | - | - |
| S1‑131244 | - | - | - |
| S1‑131245 | - | - | - |
| S1‑131246 | - | - | - |
| S1‑131247 | - | - | - |
| S1‑131248 | - | - | - |
| S1‑131249 | - | - | - |
| S1‑131250 | - | - | - |
| S1‑131251 | - | - | - |
| S1‑131252 | - | - | - |
| S1‑131253 | - | - | - |
| S1‑131254 | - | - | - |
| S1‑131255 | - | - | - |
| S1‑131256 | Public Safety end-user visibility of path switch | Huawei, Hisilicon | - |
| S1‑131257 | - | - | - |
| S1‑131258 | - | - | - |
| S1‑131259 | Addition of ProSe relay dimensioning requirements to TR 22.803 | General Dynamics Broadband UK | - |
| S1‑131260 | - | - | - |
| S1‑131262 | Clarification of what ProSe capability feature stands for | Huawei, Hisilicon | - |
| S1‑131263 | - | - | - |
| S1‑131264 | - | - | - |
| S1‑131265 | Potential requirements consolidation with some clarification | Qualcomm, Intel | - |
| S1‑131266 | - | - | - |
| S1‑131267 | - | - | - |
| S1‑131268 | - | - | - |
| S1‑131269 | - | - | - |
| S1‑131270 | - | - | - |
| S1‑131272 | General corrections to sections 1, 2, and 4 | General Dynamics Broadband UK | - |
| S1‑131273 | General corrections to section 5.1 | General Dynamics Broadband UK | - |
| S1‑131274 | - | - | - |
| S1‑131275 | Stabilty of link requirement for ProSE | Motorola Solutions | - |
| S1‑131276 | Updates to the Requirement Related to Charging for Service Continuity | Intel | - |
| S1‑131277 | - | - | - |
| S1‑131278 | Response LS on on reporting PWS Indication for users in connected mode. | S1 | - |
| S1‑131279 | Prevention of mobile-originating signalling and/or data traffic of UEs in E-UTRAN in connected mode based on the criteria for the access barring mechanisms | NTT DOCOMO, KDDI, KT, SOFTBANK MOBILE, TeliaSonera | - |
| S1‑131280 | - | - | - |
| S1‑131281 | - | - | - |
| S1‑131282 | - | - | - |
| S1‑131283 | - | - | - |
| S1‑131284 | - | - | - |
| S1‑131285 | - | - | - |
| S1‑131286 | General corrections to section 6 | General Dynamics Broadband UK | - |
| S1‑131287 | Overriding extended access barring | Qualcomm Inc, Huawei, Renesas Mobile Europe Ltd, K | - |
| S1‑131288 | FS_ProSe additional clarifying text for security related requirements | Renesas Mobile Europe Ltd | - |
| S1‑131289 | Clarification and merge of Mobile Originated Only and Infrequent Mobile Terminated | KPN | - |
| S1‑131290 | Moving MTC Priority Alarm into a generic requirement | KPN | - |
| S1‑131291 | - | - | - |
| S1‑131292 | - | - | - |
| S1‑131293 | - | - | - |
| S1‑131294 | - | - | - |
| S1‑131295 | Barring of Premium Rate Numbers | Orange, Alcatel-Lucent | - |
| S1‑131296 | Reply LS on Barring of Premium Rate Numbers | S1 | - |
| S1‑131297 | - | - | - |
| S1‑131298 | - | - | - |
| S1‑131299 | - | - | - |
| S1‑131300 | - | - | - |
| S1‑131301 | - | - | - |
| S1‑131302 | Clarification of requirements for the support of multiple service enablement frameworks | Telecom Italia | - |
| S1‑131303 | - | - | - |
| S1‑131304 | - | - | - |
| S1‑131305 | - | - | - |
| S1‑131306 | - | - | - |
| S1‑131307 | General Requirements for Proximity Services | Deutsche Telekom | - |
| S1‑131308 | Incorporation of ProSe Security, Authorization & Privacy Requirements | Qualcomm | - |
| S1‑131309 | Public Safety Specific Requirements for Proximity Services | Deutsche Telekom | - |
| S1‑131310 | Add WLAN assisted communication requirements | Qualcomm | - |
| S1‑131311 | Add charging requirements | Qualcomm | - |
| S1‑131312 | - | - | - |
| S1‑131313 | - | - | - |
| S1‑131314 | - | - | - |
| S1‑131315 | - | - | - |
| S1‑131316 | - | - | - |
| S1‑131317 | - | - | - |
| S1‑131318 | - | - | - |
| S1‑131319 | Add definitions and abbreviations | Qualcomm | - |
| S1‑131320 | - | - | - |
| S1‑131321 | - | - | - |
| S1‑131322 | LS on status of GCSE_LTE and ProSe work in SA1. | S1 | - |
| S1‑131323 | - | - | - |
page generated from database: 2024-04-13 13:51:47