3GPP TDocs (written contributions) at meeting
Meeting: S3-18 - 2001-05-21 to 2001-05-24, Phoenix
meeting id: S3-18 (click id for more info on this meeting)Click on the Tdoc to open its file.
| TDoc | Title | Source | Remarks |
|---|---|---|---|
| S3‑010140 | - | - | - |
| S3‑010141 | - | - | - |
| S3‑010142 | - | - | - |
| S3‑010143 | - | - | - |
| S3‑010144 | - | - | - |
| S3‑010145 | - | - | - |
| S3‑010146 | - | - | - |
| S3‑010147 | - | - | - |
| S3‑010148 | - | - | - |
| S3‑010149 | - | - | - |
| S3‑010150 | - | - | - |
| S3‑010151 | - | - | - |
| S3‑010152 | - | - | - |
| S3‑010153 | - | - | - |
| S3‑010154 | - | - | - |
| S3‑010155 | - | - | - |
| S3‑010156 | - | - | - |
| S3‑010157 | - | - | - |
| S3‑010158 | - | - | - |
| S3‑010159 | - | - | - |
| S3‑010160 | - | - | - |
| S3‑010161 | - | - | - |
| S3‑010162 | - | - | - |
| S3‑010163 | - | - | - |
| S3‑010164 | - | - | - |
| S3‑010165 | - | - | - |
| S3‑010166 | - | - | - |
| S3‑010167 | - | - | - |
| S3‑010168 | - | - | - |
| S3‑010169 | - | - | - |
| S3‑010170 | - | - | - |
| S3‑010171 | - | - | - |
| S3‑010172 | - | - | - |
| S3‑010173 | - | - | - |
| S3‑010174 | - | - | - |
| S3‑010175 | - | - | - |
| S3‑010176 | - | - | - |
| S3‑010177 | - | - | - |
| S3‑010178 | - | - | - |
| S3‑010179 | Correction to periodic local authentication | - | - |
| S3‑010180 | Correction to periodic local authentication | - | - |
| S3‑010181 | Correction to COUNT-C description | - | - |
| S3‑010182 | Correction to COUNT-C description | - | - |
| S3‑010183 | - | - | - |
| S3‑010184 | - | - | - |
| S3‑010185 | The multiplicity of Data integrity symbols | - | - |
| S3‑010186 | The multiplicity of Data integrity symbols | - | - |
| S3‑010187 | Deletion of the maximum size of a RRC message | - | - |
| S3‑010188 | Deletion of the maximum size of a RRC message | - | - |
| S3‑010189 | - | - | - |
| S3‑010190 | - | - | - |
| S3‑010191 | - | - | - |
| S3‑010192 | - | - | - |
| S3‑010193 | - | - | - |
| S3‑010194 | - | - | - |
| S3‑010195 | - | - | - |
| S3‑010196 | - | - | - |
| S3‑010197 | - | - | - |
| S3‑010198 | - | - | - |
| S3‑010199 | - | - | - |
| S3‑010200 | - | - | - |
| S3‑010201 | - | - | - |
| S3‑010202 | - | - | - |
| S3‑010203 | - | - | - |
| S3‑010204 | - | - | - |
| S3‑010205 | - | - | - |
| S3‑010206 | - | - | - |
| S3‑010207 | - | - | - |
| S3‑010208 | - | - | - |
| S3‑010209 | - | - | - |
| S3‑010210 | - | - | - |
| S3‑010211 | - | - | - |
| S3‑010212 | - | - | - |
| S3‑010213 | - | - | - |
| S3‑010214 | - | - | - |
| S3‑010215 | - | - | - |
| S3‑010216 | - | - | - |
| S3‑010217 | - | - | - |
| S3‑010218 | - | - | - |
| S3‑010219 | - | - | - |
| S3‑010220 | - | - | - |
| S3‑010221 | - | - | - |
| S3‑010222 | - | - | - |
| S3‑010223 | - | - | - |
| S3‑010225 | - | - | - |
| S3‑010226 | Response to LS S5-010114 (S3- 010168) on MExE and User Equipment Management | S3 | - |
| S3‑010227 | - | - | - |
| S3‑010228 | - | - | - |
| S3‑010229 | - | - | - |
| S3‑010230 | Reply LS on the handling of retransmitted authentication requests | S3 | - |
| S3‑010231 | - | - | - |
| S3‑010232 | Reply to LS on rejection of 2G authentication and key agreement by 3G ME with USIM in UTRAN | S3 | - |
| S3‑010233 | Reply LS on authentication test algorithm to be implemented in test USIM | S3 | - |
| S3‑010234 | - | - | - |
| S3‑010235 | - | - | - |
| S3‑010236 | Include reference to TS 43.041 GERAN Stage 2 specification | - | - |
| S3‑010237 | - | - | - |
| S3‑010238 | - | - | - |
| S3‑010239 | - | - | - |
| S3‑010240 | Correction to integrity protection when the user is attached to a UTRAN with R99+ ME with a SIM inserted | - | - |
| S3‑010241 | Correction to integrity protection when the user is attached to a UTRAN with R99+ ME with a SIM inserted | - | - |
| S3‑010246 | - | - | - |
| S3‑010247 | Reply to LS on revised working assumptions made at joint GERAN/S3 meeting | S3 | - |
| S3‑010248 | - | - | - |
| S3‑010249 | - | - | - |
| S3‑010250 | - | - | - |
| S3‑010251 | - | - | - |
| S3‑010252 | - | - | - |
| S3‑010253 | - | - | - |
| S3‑010254 | - | - | - |
| S3‑010255 | - | - | - |
| S3‑010256 | - | - | - |
| S3‑010257 | - | - | - |
| S3‑010259 | - | - | - |
| S3‑010260 | - | - | - |
| S3‑010261 | - | - | - |
| S3‑010262 | - | - | - |
| S3‑010263 | - | - | - |
| S3‑010264 | - | - | - |
| S3‑010265 | Reply LS on Security Associations for IMS functional elements | S3 | - |
| S3‑010266 | - | - | - |
| S3‑010267 | - | - | - |
| S3‑010268 | Reply LS on Wrap around of the calculated START value | S3 | - |
| S3‑010269 | Calculation and Wrap-around of START value | - | - |
| S3‑010270 | Calculation and Wrap-around of START value | - | - |
| S3‑010271 | THRESHOLD Check at RRC connection establishment | - | - |
| S3‑010272 | THRESHOLD Check at RRC connection establishment | - | - |
| S3‑010273 | Reply LS on THRESHOLD Check at RRC connection establishment | S3 | - |
| S3‑010274 | Reply to LS on "Handling of ICMP messages by 3GPP SIP Implementations" | S3 | - |
| S3‑010275 | - | - | - |
| S3‑010276 | - | - | - |
| S3‑010277 | - | - | - |
| S3‑010278 | - | - | - |
| S3‑010279 | - | - | - |
| S3‑010280 | - | - | - |
| S3‑010281 | - | - | - |
| S3‑010282 | - | - | - |
| S3‑010283 | - | - | - |
| S3‑010284 | - | - | - |
| S3‑010285 | - | - | - |
| S3‑010286 | - | - | - |
| S3‑010287 | Using a generic authentication scheme for SIP | S3 | - |
| S3‑010288 | - | - | - |
| S3‑010289 | Security and UE functionality split | S3 | - |
| S3‑010290 | - | - | - |
| S3‑010291 | Reply to LSs: "Security for IM SIP session Signaling" (Tdoc N1?010588, received as S3?010152) AND IM User Identities (Tdoc S2-010757, received as S3-010160) | S3 | - |
| S3‑010292 | Response to Liaison Statement on the IM Call Transfer Service N1-010890 (S3-010249) | S3 | - |
| S3‑010293 | Reply LS on extended streaming service and user profiles | S3 | - |
| S3‑010294 | - | - | - |
| S3‑010295 | - | - | - |
page generated from database: 2024-04-13 13:51:47