3GPP TDocs (written contributions) at meeting
Meeting: S1-62 - 2013-05-06 to 2013-05-10, New Delhi
meeting id: S1-62 (click id for more info on this meeting)Click on the Tdoc to open its file.
TDoc | Title | Source | Remarks |
---|---|---|---|
S1‑133000 | - | - | imported from 3GU |
S1‑133001 | - | - | imported from 3GU |
S1‑133002 | - | - | imported from 3GU |
S1‑133003 | - | - | imported from 3GU |
S1‑133004 | - | - | imported from 3GU |
S1‑133005 | - | - | imported from 3GU |
S1‑133006 | - | - | imported from 3GU |
S1‑133007 | - | - | imported from 3GU |
S1‑133008 | - | - | imported from 3GU |
S1‑133009 | - | - | imported from 3GU |
S1‑133010 | - | - | imported from 3GU |
S1‑133011 | - | - | imported from 3GU |
S1‑133012 | - | - | imported from 3GU |
S1‑133013 | - | - | imported from 3GU |
S1‑133014 | - | - | imported from 3GU |
S1‑133015 | - | - | imported from 3GU |
S1‑133016 | - | - | imported from 3GU |
S1‑133017 | - | - | imported from 3GU |
S1‑133018 | - | - | imported from 3GU |
S1‑133019 | - | - | imported from 3GU |
S1‑133020 | - | - | imported from 3GU |
S1‑133021 | - | - | imported from 3GU |
S1‑133022 | - | - | imported from 3GU |
S1‑133023 | - | - | imported from 3GU |
S1‑133024 | - | - | imported from 3GU |
S1‑133025 | - | - | imported from 3GU |
S1‑133026 | Clarification of Dynamic RAN Sharing Use Case | Intel & NEC | - |
S1‑133027 | - | - | imported from 3GU |
S1‑133028 | - | - | imported from 3GU |
S1‑133029 | - | - | imported from 3GU |
S1‑133030 | - | - | imported from 3GU |
S1‑133031 | - | - | imported from 3GU |
S1‑133032 | - | - | imported from 3GU |
S1‑133033 | - | - | imported from 3GU |
S1‑133034 | - | - | imported from 3GU |
S1‑133035 | - | - | imported from 3GU |
S1‑133036 | - | - | imported from 3GU |
S1‑133037 | - | - | imported from 3GU |
S1‑133038 | - | - | imported from 3GU |
S1‑133039 | - | - | imported from 3GU |
S1‑133040 | - | - | imported from 3GU |
S1‑133041 | - | - | imported from 3GU |
S1‑133042 | - | - | imported from 3GU |
S1‑133043 | - | - | imported from 3GU |
S1‑133044 | - | - | imported from 3GU |
S1‑133045 | - | - | imported from 3GU |
S1‑133046 | - | - | imported from 3GU |
S1‑133047 | - | - | imported from 3GU |
S1‑133048 | - | - | imported from 3GU |
S1‑133049 | - | - | imported from 3GU |
S1‑133050 | - | - | imported from 3GU |
S1‑133051 | - | - | imported from 3GU |
S1‑133052 | - | - | imported from 3GU |
S1‑133053 | - | - | imported from 3GU |
S1‑133054 | - | - | imported from 3GU |
S1‑133055 | - | - | imported from 3GU |
S1‑133056 | - | - | imported from 3GU |
S1‑133057 | - | - | imported from 3GU |
S1‑133058 | - | - | imported from 3GU |
S1‑133059 | - | - | imported from 3GU |
S1‑133060 | - | - | imported from 3GU |
S1‑133061 | - | - | imported from 3GU |
S1‑133062 | - | - | imported from 3GU |
S1‑133063 | - | - | imported from 3GU |
S1‑133064 | - | - | imported from 3GU |
S1‑133065 | - | - | imported from 3GU |
S1‑133066 | - | - | imported from 3GU |
S1‑133067 | Edits for Proposed CR to 21.905 | TPS | - |
S1‑133068 | - | - | imported from 3GU |
S1‑133069 | - | - | imported from 3GU |
S1‑133070 | - | - | imported from 3GU |
S1‑133071 | - | - | imported from 3GU |
S1‑133072 | - | - | imported from 3GU |
S1‑133073 | - | - | imported from 3GU |
S1‑133074 | - | - | imported from 3GU |
S1‑133075 | - | - | imported from 3GU |
S1‑133076 | - | - | imported from 3GU |
S1‑133077 | - | - | imported from 3GU |
S1‑133078 | - | - | imported from 3GU |
S1‑133079 | - | - | imported from 3GU |
S1‑133080 | - | - | imported from 3GU |
S1‑133081 | - | - | imported from 3GU |
S1‑133082 | - | - | imported from 3GU |
S1‑133083 | - | - | imported from 3GU |
S1‑133084 | - | - | imported from 3GU |
S1‑133085 | - | - | imported from 3GU |
S1‑133086 | - | - | imported from 3GU |
S1‑133087 | - | - | imported from 3GU |
S1‑133088 | - | - | imported from 3GU |
S1‑133089 | - | - | imported from 3GU |
S1‑133090 | - | - | imported from 3GU |
S1‑133091 | - | - | imported from 3GU |
S1‑133092 | - | - | imported from 3GU |
S1‑133093 | - | - | imported from 3GU |
S1‑133094 | - | - | imported from 3GU |
S1‑133095 | - | - | imported from 3GU |
S1‑133096 | - | - | imported from 3GU |
S1‑133097 | - | - | imported from 3GU |
S1‑133098 | Editorial Updates to ProSe Requirements | Intel | - |
S1‑133099 | - | - | imported from 3GU |
S1‑133100 | - | - | imported from 3GU |
S1‑133101 | - | - | imported from 3GU |
S1‑133102 | - | - | imported from 3GU |
S1‑133103 | - | - | imported from 3GU |
S1‑133104 | - | - | imported from 3GU |
S1‑133105 | - | - | imported from 3GU |
S1‑133106 | - | - | imported from 3GU |
S1‑133107 | - | - | imported from 3GU |
S1‑133108 | - | - | imported from 3GU |
S1‑133109 | - | - | imported from 3GU |
S1‑133110 | - | - | imported from 3GU |
S1‑133111 | - | - | - |
S1‑133112 | Addressing uncertainties in deployment of Public Safety ProSe | General Dynamics Broadband UK Limited | - |
S1‑133113 | Correction of in / out of E-UTRAN coverage and editorials | Renesas Mobile Europe Ltd, Vodafone | - |
S1‑133114 | - | - | - |
S1‑133115 | - | - | - |
S1‑133116 | - | - | - |
S1‑133117 | - | - | - |
S1‑133118 | - | - | - |
S1‑133119 | - | - | - |
S1‑133120 | - | - | - |
S1‑133121 | - | - | - |
S1‑133122 | - | - | - |
S1‑133123 | - | - | - |
S1‑133124 | - | - | - |
S1‑133125 | - | - | - |
S1‑133126 | - | - | - |
S1‑133127 | - | - | - |
S1‑133128 | - | - | - |
S1‑133129 | - | - | - |
S1‑133130 | - | - | - |
S1‑133131 | - | - | - |
S1‑133132 | - | - | - |
S1‑133133 | - | - | - |
S1‑133134 | - | - | - |
S1‑133135 | - | - | - |
S1‑133136 | Clarification of supplementary services suppression on callbacks | Deutsche Telekom, NTT DOCOMO, SoftBank Mobile, Chi | - |
S1‑133137 | - | - | - |
S1‑133140 | - | - | - |
S1‑133141 | - | - | - |
S1‑133142 | - | - | - |
S1‑133143 | - | - | - |
S1‑133144 | - | - | - |
S1‑133145 | - | - | - |
S1‑133146 | - | - | - |
S1‑133147 | - | - | - |
S1‑133148 | - | - | - |
S1‑133149 | - | - | - |
S1‑133150 | - | - | - |
S1‑133151 | - | - | - |
S1‑133152 | - | - | - |
S1‑133153 | - | - | - |
S1‑133154 | - | - | - |
S1‑133155 | - | - | - |
S1‑133156 | - | - | - |
S1‑133157 | ProSe System means ProSe | Huawei, Orange | - |
S1‑133158 | - | - | - |
S1‑133159 | - | - | - |
S1‑133160 | - | - | - |
S1‑133161 | - | - | - |
S1‑133162 | - | - | - |
S1‑133163 | - | - | - |
S1‑133164 | - | - | - |
S1‑133165 | - | - | - |
S1‑133166 | - | - | - |
S1‑133170 | - | - | - |
S1‑133171 | - | - | - |
S1‑133172 | - | - | - |
S1‑133173 | - | - | - |
S1‑133174 | - | - | - |
S1‑133175 | - | - | - |
S1‑133176 | - | - | - |
S1‑133177 | - | - | - |
S1‑133178 | - | - | - |
S1‑133179 | - | - | - |
S1‑133180 | - | - | - |
S1‑133181 | - | - | - |
S1‑133182 | - | - | - |
S1‑133183 | - | - | - |
S1‑133184 | - | - | - |
S1‑133191 | - | - | - |
S1‑133192 | - | - | - |
S1‑133193 | - | - | - |
S1‑133194 | - | - | - |
S1‑133195 | Removal of IMS Emergency Callback requirements from Rel-11 | Huawei | - |
S1‑133196 | Removal of IMS Emergency Callback requirements from Rel-11 | Huawei | - |
S1‑133197 | - | - | - |
S1‑133198 | - | - | - |
S1‑133199 | - | - | - |
S1‑133200 | - | - | - |
S1‑133201 | - | - | - |
S1‑133202 | - | - | - |
S1‑133203 | - | - | - |
S1‑133204 | - | - | - |
S1‑133205 | - | - | - |
S1‑133206 | - | - | - |
S1‑133207 | - | - | - |
S1‑133208 | - | - | - |
S1‑133209 | - | - | - |
S1‑133210 | - | - | - |
S1‑133211 | - | - | - |
S1‑133212 | - | - | - |
S1‑133213 | - | - | - |
S1‑133214 | - | - | - |
S1‑133215 | - | - | - |
S1‑133216 | - | - | - |
S1‑133217 | - | - | - |
S1‑133218 | - | - | - |
S1‑133219 | - | - | - |
S1‑133220 | - | - | - |
S1‑133221 | - | - | - |
S1‑133222 | - | - | - |
S1‑133223 | - | - | - |
S1‑133224 | Requirement on emergency IM CN service | Telecom Italia, Huawei, Ericsson,Orange, Qualcomm, | - |
S1‑133225 | - | - | - |
S1‑133226 | - | - | - |
S1‑133227 | - | - | - |
S1‑133228 | - | - | - |
S1‑133229 | - | - | - |
S1‑133230 | - | - | - |
S1‑133231 | - | - | - |
S1‑133232 | - | - | - |
S1‑133233 | - | - | - |
S1‑133234 | - | - | - |
S1‑133236 | - | - | - |
S1‑133237 | - | - | - |
S1‑133238 | - | - | - |
S1‑133239 | - | - | - |
S1‑133240 | - | - | - |
S1‑133241 | - | - | - |
S1‑133242 | - | - | - |
S1‑133243 | - | - | - |
S1‑133244 | - | - | - |
S1‑133245 | Correction of ProSe Services to ProSe | LG Electronics, Inc. | - |
S1‑133246 | - | - | - |
S1‑133247 | Update to Requirement on EPC Proximity Detection | Intel | - |
S1‑133248 | - | - | - |
S1‑133249 | Setting Up and Handling for ProSe UE-to-UE Relay | LG Electronics, Inc. | - |
S1‑133250 | - | - | - |
S1‑133251 | - | - | - |
S1‑133252 | ProSe Discovery Definition Update | Intel, KPN, Sony, UK Home Office, Huawei, HiS | - |
S1‑133253 | - | - | - |
S1‑133254 | - | - | - |
S1‑133255 | - | - | - |
S1‑133256 | LS on eCall for IMS | S1 | - |
S1‑133257 | Control of resource applies also when UEs are served by the same eNB. | Huawei, Orange | - |
S1‑133258 | - | - | - |
S1‑133259 | On dimensioning requirements for ProSe UE-to-UE Relay | General Dynamics Broadband UK Limited | - |
S1‑133260 | Charging for the use of EPC Path in ProSe | LG Electronics, Inc. | - |
S1‑133261 | - | - | - |
S1‑133262 | - | - | - |
S1‑133263 | - | - | - |
S1‑133264 | - | - | - |
S1‑133265 | - | - | - |
S1‑133266 | - | - | - |
S1‑133267 | Clarifying the Requirement on Pre-Configuring Public Safety ProSe-enabled UEs for operations without any connection to the E-UTRAN | U.S. Department of Commerce | - |
S1‑133268 | - | - | - |
S1‑133269 | - | - | - |
S1‑133270 | - | - | - |
S1‑133271 | - | - | - |
S1‑133272 | Clarification for the use of ProSe UE-to-Network Relay - Network Reachability Indication by ProSe-enabled Public Safety UE Served by E-UTRAN | LG Electronics, Inc. | - |
S1‑133273 | - | - | - |
S1‑133274 | - | - | - |
S1‑133275 | - | - | - |
S1‑133276 | - | - | - |
S1‑133277 | - | - | - |
S1‑133278 | - | - | - |
S1‑133279 | Reply LS on “LS on Notifications on Firewall Traversal from LS Reply SA2 S2-130722 and CT1 C1-130773” | S1 | - |
S1‑133280 | LS on the release for the requirement on the Use of Dialled Digit Information in Emergency Calls | S1 | - |
S1‑133281 | Requirement on emergency IM CN service | Telecom Italia, Huawei, Ericsson,Orange, Qualcomm, | - |
S1‑133282 | Requirement on emergency IM CN service | Telecom Italia, Huawei, Ericsson,Orange, Qualcomm, | - |
S1‑133283 | - | - | - |
S1‑133284 | LS on PSAP callback requirements | S1 | - |
S1‑133285 | - | - | - |
S1‑133286 | - | - | - |
S1‑133287 | - | - | - |
S1‑133288 | - | - | - |
S1‑133289 | - | - | - |
S1‑133290 | Rel-11 alignment regarding disabling and enabling of PWS Notifications | Ericsson, ST-Ericsson | - |
S1‑133291 | - | - | - |
S1‑133292 | PWS integrity protection when roaming internationally | Ericsson, ST-Ericsson | - |
S1‑133293 | - | - | - |
S1‑133294 | - | - | - |
S1‑133295 | Discovery can be requested by any application | Huawei, Intel | - |
S1‑133296 | Add a ProSe API requirement and two requirement fixes for Proximity Services | Qualcomm Inc., China Mobile, Deutsche Telekom, U.S | - |
S1‑133297 | Remaining details in consistent usage of range terminology | General Dynamics Broadband UK | - |
S1‑133298 | LS on HPLMN selection in network sharing | S1 | - |
S1‑133299 | Service description for ProSe Discovery and ProSe Communication | Vodafone | - |
S1‑133300 | Add common definitions from ProSe | Alcatel-Lucent, Qualcomm, Renesas Mobile Europe Lt | - |
S1‑133301 | Clarifying the use of the term range | General Dynamics Broadband UK Limited | - |
S1‑133302 | - | - | - |
S1‑133304 | Support of WebRTC client access to IMS | Alcatel-Lucent, Huawei, Orange, AT&T, Intel, Telec | - |
S1‑133305 | - | - | - |
S1‑133306 | - | - | - |
S1‑133307 | Broadening of Prose Communication Defintion to include ProSe Group and ProSe Broadcast Communications for Public Safety. | US Department of Commerce, Telecom Italia, Huawei, | - |
S1‑133308 | - | - | - |
S1‑133309 | - | - | - |
S1‑133310 | Broadening of ProSe Communication Definition to include ProSe Group and ProSe Broadcast Communications for Public Safety. | US Department of Commerce, Telecom Italia, Huawei, | - |
S1‑133311 | The addition of a definition for communication range | General Dynamics Broadband UK | - |
page generated from database: 2024-04-22 07:58:53