3GPP TDocs (written contributions) at meeting
Meeting: T2-21 - 2003-05-12 to 2003-05-16, San Diego
meeting id: T2-21 (click id for more info on this meeting)Click on the Tdoc to open its file.
| TDoc | Title | Source | Remarks |
|---|---|---|---|
| T2‑03+447 | - | - | - |
| T2‑030200 | - | - | - |
| T2‑030201 | - | - | - |
| T2‑030202 | - | - | - |
| T2‑030203 | - | - | - |
| T2‑030205 | - | - | - |
| T2‑030206 | - | - | - |
| T2‑030207 | - | - | - |
| T2‑030208 | - | - | - |
| T2‑030209 | - | - | - |
| T2‑030210 | - | - | - |
| T2‑030211 | - | - | - |
| T2‑030212 | - | - | - |
| T2‑030213 | - | - | - |
| T2‑030214 | - | - | - |
| T2‑030215 | - | - | - |
| T2‑030216 | - | - | - |
| T2‑030217 | - | - | - |
| T2‑030218 | - | - | - |
| T2‑030219 | - | - | - |
| T2‑030220 | - | - | - |
| T2‑030221 | - | - | - |
| T2‑030222 | - | - | - |
| T2‑030223 | - | - | - |
| T2‑030224 | - | - | - |
| T2‑030225 | - | - | - |
| T2‑030226 | - | - | - |
| T2‑030227 | - | - | - |
| T2‑030228 | - | - | - |
| T2‑030229 | - | - | - |
| T2‑030230 | - | - | - |
| T2‑030231 | - | - | - |
| T2‑030232 | - | - | - |
| T2‑030233 | - | - | - |
| T2‑030234 | - | - | - |
| T2‑030235 | - | - | - |
| T2‑030236 | - | - | - |
| T2‑030237 | - | - | - |
| T2‑030238 | - | - | - |
| T2‑030239 | - | - | - |
| T2‑030240 | - | - | - |
| T2‑030241 | - | - | - |
| T2‑030242 | - | - | - |
| T2‑030243 | - | - | - |
| T2‑030244 | - | - | - |
| T2‑030245 | - | - | - |
| T2‑030246 | - | - | - |
| T2‑030247 | - | - | - |
| T2‑030248 | - | - | - |
| T2‑030249 | - | - | - |
| T2‑030250 | - | - | - |
| T2‑030251 | - | - | - |
| T2‑030252 | - | - | - |
| T2‑030253 | - | - | - |
| T2‑030254 | - | - | - |
| T2‑030255 | - | - | - |
| T2‑030256 | - | - | - |
| T2‑030257 | - | - | - |
| T2‑030258 | - | - | - |
| T2‑030259 | Correction of references | - | - |
| T2‑030260 | - | - | - |
| T2‑030261 | - | - | - |
| T2‑030262 | - | - | - |
| T2‑030263 | UE security aspects of the GUP architecture | T2 | - |
| T2‑030264 | - | - | - |
| T2‑030265 | - | - | - |
| T2‑030266 | - | - | - |
| T2‑030267 | LS to TSG-T3 about the +CGQREQ AT command use in TS 31.111 | T2 | - |
| T2‑030280 | - | - | - |
| T2‑030281 | - | - | - |
| T2‑030282 | - | - | - |
| T2‑030283 | - | - | - |
| T2‑030284 | Reserved values in TP-Status | - | - |
| T2‑030285 | - | - | - |
| T2‑030286 | - | - | - |
| T2‑030287 | - | - | - |
| T2‑030288 | - | - | - |
| T2‑030289 | - | - | - |
| T2‑030290 | - | - | - |
| T2‑030291 | - | - | - |
| T2‑030292 | - | - | - |
| T2‑030293 | - | - | - |
| T2‑030294 | - | - | - |
| T2‑030295 | - | - | - |
| T2‑030296 | - | - | - |
| T2‑030297 | - | - | - |
| T2‑030298 | - | - | - |
| T2‑030299 | - | - | - |
| T2‑030300 | - | - | - |
| T2‑030301 | - | - | - |
| T2‑030302 | - | - | - |
| T2‑030303 | - | - | - |
| T2‑030305 | - | - | - |
| T2‑030306 | - | - | - |
| T2‑030307 | - | - | - |
| T2‑030308 | - | - | - |
| T2‑030309 | - | - | - |
| T2‑030310 | - | - | - |
| T2‑030311 | - | - | - |
| T2‑030312 | - | - | - |
| T2‑030313 | - | - | - |
| T2‑030314 | - | - | - |
| T2‑030315 | LS - Clarification on "Restriction of Service Area List" | T2 | - |
| T2‑030316 | Re: LS on SMS/MMS Interworking from WLANs | T2 | - |
| T2‑030318 | - | - | - |
| T2‑030319 | - | - | - |
| T2‑030320 | Missing SMSs over MSC even if the MS is capable of such sending | - | - |
| T2‑030321 | Missing SMSs over MSC even if the MS is capable of such sending | - | - |
| T2‑030322 | Missing SMSs over MSC even if the MS is capable of such sending | - | - |
| T2‑030323 | Missing SMSs over MSC even if the MS is capable of such sending | - | - |
| T2‑030324 | LS on missing SMS transmission via MSC | T2 | - |
| T2‑030325 | Updating references | - | - |
| T2‑030326 | Updating references | - | - |
| T2‑030327 | Updating references | - | - |
| T2‑030329 | - | - | - |
| T2‑030331 | - | - | - |
| T2‑030332 | - | - | - |
| T2‑030333 | - | - | - |
| T2‑030334 | - | - | - |
| T2‑030335 | LS on MMS for Deferred Mode IMS Messaging | T2 | - |
| T2‑030336 | - | - | - |
| T2‑030337 | Extension of the X-Mms-MM-Status-Code “reject”, in the MM4_Delivery_report.REQ (CR) | - | - |
| T2‑030338 | Addition of IEs that currently exist in MM1/MM4 but not in MM7 | - | - |
| T2‑030339 | Over the air provisioning in MMS | - | - |
| T2‑030340 | Addition of information regarding encrypted or obfuscated address in MM7 | - | - |
| T2‑030341 | Addition of Service Provider Identification to the MM7 reference point | - | - |
| T2‑030342 | - | - | - |
| T2‑030344 | Charged Party ID (CR) | - | - |
| T2‑030345 | - | - | - |
| T2‑030346 | - | - | - |
| T2‑030347 | Correction of RFC 2821 reference | - | - |
| T2‑030348 | Correction of RFC 2821 reference | - | - |
| T2‑030349 | Correction of RFC 2821 reference | - | - |
| T2‑030355 | - | - | - |
| T2‑030356 | - | - | - |
| T2‑030357 | Support for DRM in MMS | - | - |
| T2‑030358 | - | - | - |
| T2‑030359 | - | - | - |
| T2‑030360 | Re: LS on terminal MMS capability discovery prior MM notification | T2 | - |
| T2‑030361 | - | - | - |
| T2‑030362 | - | - | - |
| T2‑030364 | LS - Proposal for Interconnection between a FSMSC and SMSCs/FSMSCs in other networks | T2 | - |
page generated from database: 2024-04-22 07:58:53