The 5G Standard

3GPP TDocs (written contributions) at meeting

Meeting: S3-54 - 2009-01-19 to 2009-01-23, Florence

meeting id: S3-54 (click id for more info on this meeting)

Click on the Tdoc to open its file.

TDoc Title Source Remarks
S3‑090001 - - imported from 3GU
S3‑090002 - - imported from 3GU
S3‑090003 - - imported from 3GU
S3‑090004 - - imported from 3GU
S3‑090005 - - imported from 3GU
S3‑090006 - - imported from 3GU
S3‑090007 - - imported from 3GU
S3‑090008 - - imported from 3GU
S3‑090009 test TB Officer -
S3‑090010 - - imported from 3GU
S3‑090011 - - imported from 3GU
S3‑090012 - - imported from 3GU
S3‑090013 - - imported from 3GU
S3‑090014 - - imported from 3GU
S3‑090015 - - imported from 3GU
S3‑090016 - - imported from 3GU
S3‑090017 CR to 33.401 NAS sequence number NEC Corporation -
S3‑090018 - - imported from 3GU
S3‑090019 CR to 33.401 Handover and keys NEC Corporation -
S3‑090020 - - imported from 3GU
S3‑090021 - - imported from 3GU
S3‑090022 - - imported from 3GU
S3‑090023 - - imported from 3GU
S3‑090024 - - imported from 3GU
S3‑090025 - - imported from 3GU
S3‑090026 pCR H(e)NB threat NEC Corporation -
S3‑090027 - - imported from 3GU
S3‑090028 - - imported from 3GU
S3‑090029 - - imported from 3GU
S3‑090030 - - imported from 3GU
S3‑090031 - - imported from 3GU
S3‑090032 - - imported from 3GU
S3‑090033 - - imported from 3GU
S3‑090034 - - imported from 3GU
S3‑090035 - - imported from 3GU
S3‑090036 - - imported from 3GU
S3‑090037 - - imported from 3GU
S3‑090038 - - imported from 3GU
S3‑090039 - - imported from 3GU
S3‑090040 - - imported from 3GU
S3‑090041 - - imported from 3GU
S3‑090042 - - imported from 3GU
S3‑090043 - - imported from 3GU
S3‑090044 Deleting editor's note in 33.224 Huawei,China Mobile -
S3‑090045 - - imported from 3GU
S3‑090046 - - imported from 3GU
S3‑090047 - - imported from 3GU
S3‑090048 - - imported from 3GU
S3‑090049 - - imported from 3GU
S3‑090050 - - imported from 3GU
S3‑090051 - - imported from 3GU
S3‑090052 - - imported from 3GU
S3‑090053 - - imported from 3GU
S3‑090054 - - imported from 3GU
S3‑090055 Clarification of CK and IK handling Nokia Corporation, Nokia Siemens Networks -
S3‑090056 - - imported from 3GU
S3‑090057 - - imported from 3GU
S3‑090058 - - imported from 3GU
S3‑090059 - - imported from 3GU
S3‑090060 - - imported from 3GU
S3‑090061 - - imported from 3GU
S3‑090062 - - imported from 3GU
S3‑090063 - - imported from 3GU
S3‑090064 - - imported from 3GU
S3‑090065 - - imported from 3GU
S3‑090066 - - imported from 3GU
S3‑090067 - - imported from 3GU
S3‑090068 - - imported from 3GU
S3‑090069 - - imported from 3GU
S3‑090070 - - imported from 3GU
S3‑090071 - - imported from 3GU
S3‑090072 - - imported from 3GU
S3‑090073 - - imported from 3GU
S3‑090074 - - imported from 3GU
S3‑090075 - - imported from 3GU
S3‑090076 - - imported from 3GU
S3‑090077 - - imported from 3GU
S3‑090078 - - imported from 3GU
S3‑090079 - - imported from 3GU
S3‑090080 - - imported from 3GU
S3‑090081 - - imported from 3GU
S3‑090082 - - imported from 3GU
S3‑090083 - - imported from 3GU
S3‑090084 - - imported from 3GU
S3‑090085 - - imported from 3GU
S3‑090086 - - imported from 3GU
S3‑090087 - - imported from 3GU
S3‑090088 - - imported from 3GU
S3‑090089 - - imported from 3GU
S3‑090090 - - imported from 3GU
S3‑090091 - - imported from 3GU
S3‑090092 - - imported from 3GU
S3‑090093 - - imported from 3GU
S3‑090094 - - imported from 3GU
S3‑090095 - - imported from 3GU
S3‑090096 - - imported from 3GU
S3‑090097 - - imported from 3GU
S3‑090098 - - imported from 3GU
S3‑090099 AKA when NAS COUNT about to wrap around Nokia Corporation, Nokia Siemens Networks -
S3‑090100 - - imported from 3GU
S3‑090101 - - imported from 3GU
S3‑090102 - - imported from 3GU
S3‑090103 - - imported from 3GU
S3‑090104 - - imported from 3GU
S3‑090105 TR33.812: pCR to 7.3 Analysis TeliaSonera -
S3‑090106 CR to 33.401 Correction of definition of direction bit TeliaSonera -
S3‑090107 - - imported from 3GU
S3‑090108 - - imported from 3GU
S3‑090109 - - imported from 3GU
S3‑090110 - - imported from 3GU
S3‑090111 - - imported from 3GU
S3‑090112 - - imported from 3GU
S3‑090113 - - imported from 3GU
S3‑090114 - - imported from 3GU
S3‑090115 - - imported from 3GU
S3‑090116 - - imported from 3GU
S3‑090117 - - imported from 3GU
S3‑090118 - - imported from 3GU
S3‑090119 - - imported from 3GU
S3‑090120 - - imported from 3GU
S3‑090121 - - imported from 3GU
S3‑090122 - - imported from 3GU
S3‑090123 - - imported from 3GU
S3‑090124 - - imported from 3GU
S3‑090125 - - imported from 3GU
S3‑090126 - - imported from 3GU
S3‑090127 - - imported from 3GU
S3‑090128 - - imported from 3GU
S3‑090129 - - imported from 3GU
S3‑090130 - - imported from 3GU
S3‑090131 - - imported from 3GU
S3‑090132 - - imported from 3GU
S3‑090133 - - imported from 3GU
S3‑090134 - - imported from 3GU
S3‑090135 - - imported from 3GU
S3‑090136 - - imported from 3GU
S3‑090137 - - imported from 3GU
S3‑090138 - - imported from 3GU
S3‑090139 - - imported from 3GU
S3‑090140 - - imported from 3GU
S3‑090141 - - imported from 3GU
S3‑090142 - - imported from 3GU
S3‑090143 - - imported from 3GU
S3‑090144 - - imported from 3GU
S3‑090145 - - imported from 3GU
S3‑090146 - - imported from 3GU
S3‑090147 - - imported from 3GU
S3‑090148 - - imported from 3GU
S3‑090149 - - imported from 3GU
S3‑090150 - - imported from 3GU
S3‑090151 - - imported from 3GU
S3‑090152 - - imported from 3GU
S3‑090153 - - imported from 3GU
S3‑090154 - - imported from 3GU
S3‑090155 - - imported from 3GU
S3‑090156 - - imported from 3GU
S3‑090157 - - imported from 3GU
S3‑090158 - - imported from 3GU
S3‑090159 - - imported from 3GU
S3‑090160 - - imported from 3GU
S3‑090161 CR to TR33.900 “A Guide to 3rd Generation Security” for addition of a clause on Prevention of Unsolicited Communication in IMS BT -
S3‑090162 - - imported from 3GU
S3‑090163 - - imported from 3GU
S3‑090164 - - imported from 3GU
S3‑090165 - - imported from 3GU
S3‑090166 - - imported from 3GU
S3‑090167 - - imported from 3GU
S3‑090168 - - imported from 3GU
S3‑090169 - - imported from 3GU
S3‑090170 - - imported from 3GU
S3‑090171 - - imported from 3GU
S3‑090172 - - imported from 3GU
S3‑090173 - - imported from 3GU
S3‑090174 - - imported from 3GU
S3‑090175 - - imported from 3GU
S3‑090176 - - imported from 3GU
S3‑090177 - - imported from 3GU
S3‑090178 - - imported from 3GU
S3‑090179 - - imported from 3GU
S3‑090180 - - imported from 3GU
S3‑090181 - - imported from 3GU
S3‑090182 - - imported from 3GU
S3‑090183 - - imported from 3GU
S3‑090184 - - imported from 3GU
S3‑090185 - - imported from 3GU
S3‑090186 - - imported from 3GU
S3‑090187 - - imported from 3GU
S3‑090188 - - imported from 3GU
S3‑090189 - - imported from 3GU
S3‑090190 - - imported from 3GU
S3‑090191 - - imported from 3GU
S3‑090192 - - imported from 3GU
S3‑090193 - - imported from 3GU
S3‑090194 - - imported from 3GU
S3‑090195 - - imported from 3GU
S3‑090196 - - imported from 3GU
S3‑090197 - - imported from 3GU
S3‑090198 - - imported from 3GU
S3‑090199 - - imported from 3GU
S3‑090200 - - imported from 3GU
S3‑090201 - - imported from 3GU
S3‑090202 - - imported from 3GU
S3‑090203 - - imported from 3GU
S3‑090204 - - imported from 3GU
S3‑090205 - - imported from 3GU
S3‑090206 - - imported from 3GU
S3‑090207 - - imported from 3GU
S3‑090208 - - imported from 3GU
S3‑090209 - - imported from 3GU
S3‑090210 - - imported from 3GU
S3‑090211 - - imported from 3GU
S3‑090212 comments_on_S3-090035_Network_access_threat_of_H(e)NB Airvana -
S3‑090213 - - imported from 3GU
S3‑090214 - - imported from 3GU
S3‑090215 - - imported from 3GU
S3‑090216 - - imported from 3GU
S3‑090217 - - imported from 3GU
S3‑090218 Questions on S3-090187 Orange -
S3‑090219 - - imported from 3GU
S3‑090220 - - imported from 3GU
S3‑090221 - - imported from 3GU
S3‑090222 - - imported from 3GU
S3‑090223 - - imported from 3GU
S3‑090224 - - imported from 3GU
S3‑090225 - - imported from 3GU
S3‑090226 - - imported from 3GU
S3‑090227 - - imported from 3GU
S3‑090228 - - imported from 3GU
S3‑090229 - - imported from 3GU
S3‑090230 - - imported from 3GU
S3‑090231 - - imported from 3GU
S3‑090232 - - imported from 3GU
S3‑090233 - - imported from 3GU
S3‑090234 - - imported from 3GU
S3‑090235 - - imported from 3GU
S3‑090236 - - imported from 3GU
S3‑090237 - - imported from 3GU
S3‑090238 - - imported from 3GU
S3‑090239 - - imported from 3GU
S3‑090240 - - imported from 3GU
S3‑090241 - - imported from 3GU
S3‑090242 - - imported from 3GU
S3‑090243 - - imported from 3GU
S3‑090244 Correction of EPS NAS Security Context definition NEC Corporation, NTT DOCOMO, Nokia Corporation, No -
S3‑090245 NAS COUNT for mapped security context NEC Corporation, Nokia Siemens Netowrks, NTT DOCOM -
S3‑090246 Storage of the EPS NAS security context in non-volatile memory of the UE Gemalto, Ericsson, NEC Corporation, NTT DOCOMO -
S3‑090247 - - -
S3‑090248 - - -
S3‑090249 - - -
S3‑090250 - - -
S3‑090251 Handling of security contexts in transition to EMM-DEREGISTERED state Nokia Corporation, Nokia Siemens Networks -
S3‑090252 Security context for transition to EMM DEREGISTERED NEC Corporation, NTT DOCOMO, Huawei -
S3‑090253 Clarification for KSIsgsn Huawei, Ericsson -
S3‑090254 Definition of UE security capabilities Nokia Corporation, Nokia Siemens Networks -
S3‑090255 Clarification on ciphering for GUTI confidentiality Nokia Corporation, Nokia Siemens Networks -
S3‑090256 AKA when NAS COUNT about to wrap around Nokia Corporation, Nokia Siemens Networks -
S3‑090257 Key derivation figures NEC Corporation, NTT DOCOMO -
S3‑090258 - - -
S3‑090259 Rekeying of the entire EPS key hierarchy NEC Corporation, NTT DOCOMO -
S3‑090260 Various corrections related to algorithm definitions, NAS token and P-TMSI signature Nokia Corporation, Nokia Siemens Networks, Ericsso -
S3‑090261 Adding EARFCN-DL to KeNB* derivation NTT DOCOMO, NEC Corporation -
S3‑090262 Forward security corrections related to R3-083569 (S3-09xxxx) Nokia Corporation, Nokia Siemens Networks, NEC Cor -
S3‑090263 - - -
S3‑090264 KeNB re-keying corrections Nokia Corporation, Nokia Siemens Networks -
S3‑090265 Removal of editorÆs note on key-change-on-the-fly for possible RLF Nokia Corporation, Nokia Siemens Networks -
S3‑090266 Multi-KeNB* forwarding for RRCConnectionRe-establishment Huawei -
S3‑090267 Response LS on Downlink integrity failure handling S3 -
S3‑090268 Handling of integrity protection failures Ericsson, Nokia Corporation, Nokia Siemens Network -
S3‑090269 LS on exception lists for integrity protection of NAS messages S3 -
S3‑090270 LS on protection of RRC messages S3 -
S3‑090271 Definition of NULL ciphering Ericsson -
S3‑090272 One ciphering algorithm and one integrity algorithm id in AS SMC Nokia Corporation, Nokia Siemens Networks -
S3‑090273 Correction of definition of direction bit DIR TeliaSonera -
S3‑090274 NAS COUNT start value NEC Corporation -
S3‑090275 Correction of NAS COUNTs reset to the start value Alcatel Shanghai Bell Co. Ltd., Alcatel-Lucent -
S3‑090276 Algorithm selection clarification NEC Corporation, NTT DOCOMO -
S3‑090277 Reply LS to "LS on Security parameter handling" (R2-087430/S3-090113) S3 -
S3‑090278 Verification of NONCEUE ZTE Corporation, China Mobile, HUAWEI -
S3‑090279 Removal of 4LSB and eKSI in the AS SMC Nokia Corporation, Nokia Siemens Networks -
S3‑090280 Removal of editorÆs note related 4LSB NAS downlink COUNT in the HO COMMAND Nokia Corporation, Nokia Siemens Networks -
S3‑090281 Correction of idle mode procedures in UTRAN Nokia Corporation, Nokia Siemens Networks -
S3‑090282 - - -
S3‑090283 Correcting the EPS security context fetching between MMEs Qualcomm Europe -
S3‑090284 Correction of description Alcatel Shanghai Bell Co. Ltd., Alcatel-Lucent -
S3‑090285 Correction of MAC-I NTT DOCOMO, Alcatel-Lucent -
S3‑090286 Transparent container in UTRAN to E-UTRAN handover NEC Corporation, ZTE Corporation, HUAWEI -
S3‑090287 UE keys for E-UTRAN and GERAN NEC Corporation -
S3‑090288 Handling of UE capabilities in Idle Mode Mobility and Handover to E-UTRAN Nokia Corporation, Nokia Siemens Networks, Ericsso -
S3‑090289 Making CK' and IK' NEC Corporation -
S3‑090290 Reply LS on Receive of ETWS outside home-PLMN S3 -
S3‑090291 LS on change of term from Cached to Native S3 -
S3‑090292 Adding definition of native contexts and clarifying the mapped and current definitions Qualcomm Europe -
S3‑090293 I-RAT handover E-UTRAN and UTRAN NEC Corporation, NTT DOCOMO -
S3‑090294 Clarification on security contexts and correction of protection of TAU requests in E-UTRAN , Handling of UE capabilities in Idle Mode Mobility Nokia Corporation, Nokia Siemens Networks, Qualcom -
S3‑090295 - - -
S3‑090296 Some corrections to the UTRAN to E-UTRAN handover procedure Qualcomm Europe -
S3‑090297 Selection of key set and security activation on Handover from GERAN/UTRAN to E-UTRAN Nokia Corporation, Nokia Siemens Networks -
S3‑090298 LS on preventing inter-RAT HO for UE with SIM access S3 -
S3‑090299 - - -
S3‑090301 Editorial corrections for 33.402 Huawei,ZTE -
S3‑090302 Clarification on MIPv4 Procedure Samsung -
S3‑090303 Correction of security requirements on eNodeB Alcatel Shanghai Bell Co. Ltd., Alcatel-Lucent -
S3‑090304 Replacing the cached security context with the mapped security context and setting START value in SRVCC Nokia Corporation, Nokia Siemens Networks, ZTE, Er -
S3‑090305 Add reference to ciphering indicator feature specification Vodafone -
S3‑090306 Add reference to ciphering indicator feature specification Vodafone -
S3‑090307 - - -
S3‑090308 Solution for NAT traversal in GPRS-IMS-Bundled Authentication. China Mobile, Alcatel-Lucent, HUAWEI,ZTE -
S3‑090309 Solution for NAT traversal in GPRS-IMS-Bundled Authentication. China Mobile, Alcatel-Lucent, HUAWEI -
S3‑090310 - - -
S3‑090311 - - -
S3‑090312 - - -
S3‑090313 Generation and use of the mapped security context in HSPA SRVCC Nokia Corporation, Nokia Siemens Networks -
S3‑090314 Update of definition of UMTS security context Ericsson -
S3‑090315 Improvement to sample C code, and removal of apparent keystream length limit Vodafone -
S3‑090316 Editorial corrections Huawei, China Mobile -
S3‑090317 Alignment of TS 33.223 with TS 33.220 Nokia Corporation, Nokia Siemens Networks -
S3‑090318 - - -
S3‑090319 - - -
S3‑090320 - - -
S3‑090321 - - -
S3‑090322 - - -
S3‑090323 Clarification and enhancement to ciphering indicator feature S3 -
S3‑090325 - - -
S3‑090326 - - -
S3‑090327 - - -
S3‑090328 - - -
S3‑090329 - - -
S3‑090330 - - -
S3‑090331 Reply LS on “IMS initiated and controlled PSS and MBMS User Service Architecture” S3 -
S3‑090332 LS on clarification on TS 33.203 from ETSI IOP and CONF test specification development and from 2nd IMS Interoperability Event S3 -
S3‑090333 Reply LS on ‘3G HNB Identity’ S3 -
S3‑090334 Reply LS on "Security issues in femtocell deployments" (FCG 20_018/S3-081429) S3 -
S3‑090335 LS on Security aspects relating to pre-Rel8 UE access control S3 -
S3‑090336 Reply LS on "LS on paging optimisation via allowed CSG list in paging message for LTE" (R3-083576/S3-090118) S3 -
S3‑090337 Corretions of DS-MIPv6 bootstrapping Huawei,ZTE, Qualcomm -
S3‑090338 - - -
S3‑090339 - - -
S3‑090340 - - -
S3‑090341 - - -
S3‑090342 - - -
S3‑090343 - - -
S3‑090344 - - -
S3‑090345 - - -
S3‑090346 - - -
S3‑090347 Handling of integrity protection failures Ericsson, Nokia Corporation, Nokia Siemens Network -
S3‑090348 Solution for NAT traversal in GPRS-IMS-Bundled Authentication. China Mobile, Alcatel-Lucent, HUAWEI,ZTE,Ericsson -
S3‑090349 LS on "Addition of informative annex to TS 33.203 on the NAT deployment considerations for GIBA" S3 -
S3‑090350 - - -
S3‑090351 Clarification for KSIsgsn Huawei -

page generated from database: 2024-03-25 09:25:51

Get news. Get knowledge. Get involved
Get news.
Get knowledge.
Get involved.
Image
The 5G Standard
3GPP General Enquiries:
info@3gpp.org 


Connect:

Quick Links