3GPP TDocs (written contributions) at meeting
Meeting: T2-16 - 2002-02-11 to 2002-02-15, Sophia Antipolis
meeting id: T2-16 (click id for more info on this meeting)Click on the Tdoc to open its file.
| TDoc | Title | Source | Remarks |
|---|---|---|---|
| T2‑020001 | - | - | - |
| T2‑020002 | - | - | - |
| T2‑020003 | - | - | - |
| T2‑020004 | - | - | - |
| T2‑020005 | - | - | - |
| T2‑020006 | - | - | - |
| T2‑020007 | - | - | - |
| T2‑020008 | - | - | - |
| T2‑020009 | - | - | - |
| T2‑020010 | - | - | - |
| T2‑020011 | - | - | - |
| T2‑020012 | - | - | - |
| T2‑020013 | - | - | - |
| T2‑020014 | - | - | - |
| T2‑020015 | - | - | - |
| T2‑020016 | - | - | - |
| T2‑020017 | - | - | - |
| T2‑020018 | - | - | - |
| T2‑020019 | - | - | - |
| T2‑020020 | - | - | - |
| T2‑020021 | - | - | - |
| T2‑020022 | - | - | - |
| T2‑020023 | - | - | - |
| T2‑020024 | - | - | - |
| T2‑020025 | - | - | - |
| T2‑020026 | - | - | - |
| T2‑020027 | - | - | - |
| T2‑020028 | - | - | - |
| T2‑020029 | - | - | - |
| T2‑020030 | - | - | - |
| T2‑020031 | - | - | - |
| T2‑020032 | - | - | - |
| T2‑020033 | - | - | - |
| T2‑020035 | Liaison Statement on routing of MMS traffic via MM4 | T2 | - |
| T2‑020036 | - | - | - |
| T2‑020037 | - | - | - |
| T2‑020038 | Liaison Statement on VASP MMS Connectivity | T2 | - |
| T2‑020039 | - | - | - |
| T2‑020040 | - | - | - |
| T2‑020041 | - | - | - |
| T2‑020042 | - | - | - |
| T2‑020043 | - | - | - |
| T2‑020044 | - | - | - |
| T2‑020045 | - | - | - |
| T2‑020046 | - | - | - |
| T2‑020047 | Liaison Statement on charging support for VAS MMS Connectivity Interface | T2 | - |
| T2‑020048 | - | - | - |
| T2‑020049 | - | - | - |
| T2‑020050 | - | - | - |
| T2‑020051 | - | - | - |
| T2‑020052 | - | - | - |
| T2‑020053 | - | - | - |
| T2‑020054 | Adding ARPK to the abbreviation list | - | - |
| T2‑020055 | - | - | - |
| T2‑020057 | - | - | - |
| T2‑020058 | - | - | - |
| T2‑020059 | - | - | - |
| T2‑020060 | - | - | - |
| T2‑020061 | - | - | - |
| T2‑020062 | - | - | - |
| T2‑020063 | - | - | - |
| T2‑020064 | - | - | - |
| T2‑020065 | - | - | - |
| T2‑020066 | - | - | - |
| T2‑020067 | - | - | - |
| T2‑020068 | - | - | - |
| T2‑020069 | - | - | - |
| T2‑020070 | Updating the references | - | - |
| T2‑020071 | - | - | - |
| T2‑020072 | - | - | - |
| T2‑020073 | Replacing MExE application with MExE executable | - | - |
| T2‑020074 | - | - | - |
| T2‑020075 | - | - | - |
| T2‑020076 | - | - | - |
| T2‑020077 | - | - | - |
| T2‑020078 | Changing the urls for the CLDC/MIDP references | - | - |
| T2‑020079 | - | - | - |
| T2‑020080 | - | - | - |
| T2‑020081 | - | - | - |
| T2‑020083 | - | - | - |
| T2‑020084 | - | - | - |
| T2‑020085 | - | - | - |
| T2‑020086 | - | - | - |
| T2‑020087 | - | - | - |
| T2‑020088 | - | - | - |
| T2‑020089 | Classmark 4 security | - | - |
| T2‑020090 | - | - | - |
| T2‑020091 | - | - | - |
| T2‑020093 | Incorrect explanation of length indicator bit | - | - |
| T2‑020094 | Incorrect explanation of length indicator bit | - | - |
| T2‑020095 | Incorrect explanation of length indicator bit | - | - |
| T2‑020096 | Incorrect explanation of length indicator bit | - | - |
| T2‑020097 | - | - | - |
| T2‑020098 | Alignment of UE architecture with 23.101 | - | - |
| T2‑020099 | - | - | - |
| T2‑020100 | - | - | - |
| T2‑020102 | Alignment of UE architecture with 23.101 | - | - |
| T2‑020103 | Alignment of UE architecture with 23.101 | - | - |
| T2‑020104 | Alignment of UE architecture with 23.101 | - | - |
| T2‑020105 | Alignment of UE architecture with 23.101 | - | - |
| T2‑020106 | - | - | - |
| T2‑020107 | - | - | - |
| T2‑020108 | - | - | - |
| T2‑020109 | - | - | - |
| T2‑020110 | - | - | - |
| T2‑020111 | - | - | - |
| T2‑020112 | - | - | - |
| T2‑020113 | - | - | - |
| T2‑020114 | Liaison Statement on Relationship of GUP to Subscription Management | T2 | - |
| T2‑020115 | Liaison Statement on coordination of GUP work | T2 | - |
| T2‑020116 | LS on response to S5-020027 (T2-020240) UEM Feasibility Study (TR 32.802) | T2 | - |
| T2‑020117 | - | - | - |
| T2‑020118 | - | - | - |
| T2‑020119 | Alignment of UE architecture with 23.101 | - | - |
| T2‑020120 | Alignment of UE architecture with 23.101 | - | - |
| T2‑020121 | - | - | - |
| T2‑020130 | - | - | - |
| T2‑020131 | - | - | - |
| T2‑020132 | - | - | - |
| T2‑020133 | - | - | - |
| T2‑020134 | - | - | - |
| T2‑020135 | - | - | - |
| T2‑020136 | - | - | - |
| T2‑020137 | - | - | - |
| T2‑020138 | - | - | - |
| T2‑020139 | - | - | - |
| T2‑020140 | Correction on the SMTP-address address encoding | - | - |
| T2‑020141 | Correction on the SMTP-address encoding | - | - |
| T2‑020142 | - | - | - |
| T2‑020143 | - | - | - |
| T2‑020144 | Introduction of SMTP service extensions over MM4 | - | - |
| T2‑020145 | MM4 forward routing failure | - | - |
| T2‑020146 | Clarification of existing request status codes over MM4 | - | - |
| T2‑020147 | - | - | - |
| T2‑020148 | Delivery report definition correction | - | - |
| T2‑020149 | VASP abbreviation | - | - |
| T2‑020150 | Correction on the MIME Content-Type Message format on MM4 | - | - |
| T2‑020151 | Correction on the MIME Content-Type Message format on MM4 | - | - |
| T2‑020152 | - | - | - |
| T2‑020153 | - | - | - |
| T2‑020154 | Correction of the Forwarding Feature | - | - |
| T2‑020155 | Correction of addressing on MM1_Submit.REQ | - | - |
| T2‑020156 | Correction of the Forwarding Feature | - | - |
| T2‑020157 | Detection of duplicate MMs | - | - |
| T2‑020158 | Submission Description Enhancement regarding the IE “Date and Time” | - | - |
| T2‑020159 | - | - | - |
| T2‑020160 | - | - | - |
| T2‑020161 | Adding a reference to 3GPP TS 32.235 | - | - |
| T2‑020162 | Terminal Capability Negotiation | - | - |
| T2‑020163 | - | - | - |
| T2‑020164 | - | - | - |
| T2‑020165 | - | - | - |
| T2‑020166 | - | - | - |
| T2‑020167 | - | - | - |
| T2‑020168 | - | - | - |
| T2‑020169 | - | - | - |
| T2‑020170 | - | - | - |
| T2‑020171 | - | - | - |
| T2‑020172 | - | - | - |
| T2‑020173 | - | - | - |
| T2‑020175 | - | - | - |
| T2‑020176 | - | - | - |
| T2‑020177 | - | - | - |
| T2‑020178 | - | - | - |
| T2‑020180 | - | - | - |
| T2‑020181 | - | - | - |
| T2‑020182 | - | - | - |
| T2‑020183 | - | - | - |
| T2‑020185 | - | - | - |
| T2‑020186 | - | - | - |
| T2‑020187 | - | - | - |
| T2‑020188 | - | - | - |
| T2‑020189 | - | - | - |
| T2‑020192 | - | - | - |
| T2‑020193 | - | - | - |
| T2‑020194 | - | - | - |
| T2‑020195 | - | - | - |
| T2‑020196 | - | - | - |
| T2‑020197 | - | - | - |
| T2‑020198 | - | - | - |
| T2‑020199 | - | - | - |
| T2‑020200 | - | - | - |
| T2‑020201 | - | - | - |
| T2‑020202 | - | - | - |
| T2‑020203 | - | - | - |
| T2‑020204 | - | - | - |
| T2‑020205 | - | - | - |
| T2‑020206 | - | - | - |
| T2‑020207 | - | - | - |
| T2‑020208 | - | - | - |
| T2‑020209 | - | - | - |
| T2‑020210 | - | - | - |
| T2‑020211 | Recipient MSISDN address resolution | - | - |
| T2‑020212 | - | - | - |
| T2‑020213 | - | - | - |
| T2‑020214 | - | - | - |
| T2‑020215 | Reply-charging bug fixes | - | - |
| T2‑020216 | - | - | - |
| T2‑020217 | Liaison Statement on Billing and network aspects concerning Multimedia Messaging Interworking | T2 | - |
| T2‑020218 | - | - | - |
| T2‑020219 | Support of Reply-Charging in MM7 | - | - |
| T2‑020221 | - | - | - |
| T2‑020222 | - | - | - |
| T2‑020223 | - | - | - |
| t2‑020224 | - | - | - |
| T2‑020225 | MO-SMS duplicate message response | - | - |
| T2‑020226 | MO-SMS duplicate message response | - | - |
| T2‑020227 | MO-SMS duplicate message response | - | - |
| T2‑020228 | - | - | - |
| T2‑020229 | Subaddressing scheme for SMS | - | - |
| T2‑020230 | Alternate Reply Address Element | - | - |
| T2‑020231 | User Data Header support over CBS | - | - |
| T2‑020232 | - | - | - |
| T2‑020233 | - | - | - |
| T2‑020234 | - | - | - |
| T2‑020235 | - | - | - |
| T2‑020236 | - | - | - |
| T2‑020237 | Extended Object Data Request Command | - | - |
| t2‑020238 | - | - | - |
| T2‑020240 | - | - | - |
| T2‑020241 | - | - | - |
| T2‑020242 | - | - | - |
| T2‑020243 | - | - | - |
| T2‑020244 | - | - | - |
| T2‑020245 | Liaison Statement on Recipient MSISDN Address Resolution | T2 | - |
| T2‑020246 | - | - | - |
| T2‑020247 | - | - | - |
| T2‑020248 | - | - | - |
| T2‑020249 | - | - | - |
| T2‑020250 | - | - | - |
| T2‑020251 | The transfer of responsibility for MMS formats and codecs from T2 to SA4 | T2 | - |
| T2‑020252 | Liaison Statement on MMS availability and USIM/UICC portability | T2 | - |
| T2‑020253 | - | - | - |
| T2‑020254 | Liaison Statement on coordination of data definitions, identified in GUP development | T2 | - |
| T2‑020255 | Liaison Statement on GUP/DDF timescales | T2 | - |
| T2‑020256 | Response to Liaison Statement on Cx User Profile (N4-020197) | T2 | - |
| T2‑020257 | - | - | - |
| T2‑020258 | - | - | - |
| T2‑020259 | - | - | - |
| T2‑020260 | - | - | - |
| T2‑020261 | VASP-related CDR generation | - | - |
| T2‑020262 | Persistent Networked-Based Storage Functions | - | - |
| T2‑020263 | Functional Description and Abstract Messages for MM7 realization | - | - |
| T2‑020264 | Liaison Statement on reply to T3 on MMS related changes for Rel-4 | T2 | - |
| T2‑020265 | MMS UA behaviour with respect to handling MMS parameters on the USIM | - | - |
| T2‑020266 | - | - | - |
| T2‑020267 | - | - | - |
| T2‑020268 | - | - | - |
| T2‑020269 | - | - | - |
| T2‑020270 | MM1 <-> MM4 header mapping | - | - |
| T2‑020271 | Editorial changes | - | - |
| T2‑020272 | Correction to Call Data Records definitions | - | - |
| T2‑020273 | Liaison Statement on User Privacy on MM7 | T2 | - |
| T2‑020274 | - | - | - |
| T2‑020275 | Reference point MM8 to billing system | - | - |
| T2‑020276 | - | - | - |
| T2‑020277 | MM7 Addressing | - | - |
| T2‑020278 | Clarification about Streaming in MMS | - | - |
| T2‑020279 | Clarifications on responsibilities of MMS User Agent and MMS Relay/Server | - | - |
| T2‑020280 | - | - | - |
| T2‑020281 | - | - | - |
| T2‑020282 | - | - | - |
| T2‑020283 | - | - | - |
| T2‑020285 | Classmark 4 non-security | - | - |
| T2‑020286 | Adding MSISDN to the security table | - | - |
| T2‑020287 | Making storage of ORPK in ME optional | - | - |
| T2‑020288 | Interpretation of user control | - | - |
| T2‑020289 | Specify more explicitly the MExE executable definition | - | - |
| T2‑020290 | Remove unused abbreviations | - | - |
| T2‑020291 | - | - | - |
| T2‑020292 | - | - | - |
| T2‑020293 | - | - | - |
| T2‑020294 | - | - | - |
| T2‑020295 | - | - | - |
| T2‑020296 | Liaison Statement on Change Requests for 22.057 | T2 | - |
| T2‑020297 | MM1 addressing formats | - | - |
| T2‑020298 | Liaison Statement on MM7 Security Mechanisms for Release 5 | T2 | - |
| T2‑020299 | - | - | - |
| T2‑020300 | Liaison Statement on MMS provisioning and data consistency | T2 | - |
| T2‑020301 | Wireless Vector Graphics in EMS | - | - |
| T2‑020302 | Polyphonic Extended Object | - | - |
page generated from database: 2024-04-13 13:51:47