The 5G Standard

3GPP TDocs (written contributions) at meeting

Meeting: S2-44 - 2005-01-26 to 2005-02-02, Budapest

meeting id: S2-44 (click id for more info on this meeting)

Click on the Tdoc to open its file.

TDoc Title Source Remarks
S2 050512 - - -
S2_44_Tdo - - -
S2‑050001 - - -
S2‑050002 - - -
S2‑050003 - - -
S2‑050004 - - -
S2‑050005 - - -
S2‑050006 - - -
S2‑050007 - - -
S2‑050008 - - -
S2‑050009 - - -
S2‑050010 - - -
S2‑050011 - - -
S2‑050012 - - -
S2‑050013 - - -
S2‑050014 - - -
S2‑050015 - - -
S2‑050016 - - -
S2‑050017 - - -
S2‑050018 - - -
S2‑050019 - - -
S2‑050020 - - -
S2‑050021 - - -
S2‑050022 - - -
S2‑050023 - - -
S2‑050024 - - -
S2‑050025 - - -
S2‑050026 - - -
S2‑050027 - - -
S2‑050028 - - -
S2‑050029 - - -
S2‑050030 - - -
S2‑050031 - - -
S2‑050032 - - -
S2‑050033 - - -
S2‑050034 - - -
S2‑050035 - - -
S2‑050036 - - -
S2‑050037 - - -
S2‑050038 - - -
S2‑050039 - - -
S2‑050040 - - -
S2‑050041 - - -
S2‑050042 - - -
S2‑050043 Removal of Obsolete Annexes - -
S2‑050044 Charging in WAG - -
S2‑050045 Removal of WLAN UE from Core Network entities - -
S2‑050046 Inclusion of WLAN functionality in HSS description - -
S2‑050047 Inclusion of WLAN entities in PS domain - -
S2‑050048 Generalising Subscriber Location Function (SLF) to support WLAN - -
S2‑050049 Removal of WLAN charging reference points and functional entities - -
S2‑050050 - - -
S2‑050051 Parameter storage for I-WLAN - -
S2‑050052 Charging in WAG - -
S2‑050053 Removal of Obsolete Annexes - -
S2‑050054 Inclusion of WLAN functionality in HSS description - -
S2‑050055 Generalising Subscriber Location Function (SLF) to support WLAN and Removal of WLAN charging reference points and functional entities - -
S2‑050056 Correction of Requirements for 3GPP PS based services - -
S2‑050057 Correction of Requirements for 3GPP PS based services CR - -
S2‑050058 Add the functionality of subscriber profile updating description - -
S2‑050059 - - -
S2‑050060 Correction of Requirements for 3GPP PS based services - -
S2‑050061 - - -
S2‑050062 Add the functionality of subscriber profile updating description - -
S2‑050063 Inclusion of WLAN functionality in HSS description - -
S2‑050064 Generalising Subscriber Location Function (SLF) to support WLAN and Removal of WLAN charging reference points and functional entities - -
S2‑050065 - - -
S2‑050066 - - -
S2‑050090 - - -
S2‑050091 - - -
S2‑050092 Input information from AF to CRF - -
S2‑050093 Check of AF’s subscription - -
S2‑050094 Clarification of record indicator and charging key - -
S2‑050095 Introduction of predefined handling in TPF - -
S2‑050096 Introduction of charging instruction info - -
S2‑050097 Changes to requirements on contacting CRF - -
S2‑050098 FBC flows for bearer event reporting - -
S2‑050099 - - -
S2‑050100 Update of Annex B.4 - -
S2‑050101 - - -
S2‑050102 Protection of Rx and Gx interfaces - -
S2‑050103 Updates to service data flow identification - -
S2‑050104 FBC and MBMS - -
S2‑050105 FBC and MBMS and collection of statistics - -
S2‑050106 Removal of the Ry reference point - -
S2‑050107 Editorial and readability amendments - -
S2‑050108 FBC and SBLP for Release 6 - -
S2‑050109 - - -
S2‑050111 FBC flows for bearer event reporting - -
S2‑050112 - - -
S2‑050113 Update of Annex B.4 - -
S2‑050114 FBC and MBMS - -
S2‑050115 FBC and MBMS and collection of statistics - -
S2‑050116 Check of AF’s subscription - -
S2‑050117 Changes to requirements on contacting CRF - -
S2‑050118 Introduction of predefined handling in TPF - -
S2‑050119 Application Function Record information - -
S2‑050120 - - -
S2‑050121 - - -
S2‑050122 - - -
S2‑050123 - - -
S2‑050124 - - -
S2‑050125 - - -
S2‑050126 - - -
S2‑050127 - - -
S2‑050128 - - -
S2‑050129 - - -
S2‑050130 - - -
S2‑050131 - - -
S2‑050132 - - -
S2‑050133 - - -
S2‑050134 - - -
S2‑050135 - - -
S2‑050136 - - -
S2‑050137 - - -
S2‑050139 - - -
S2‑050140 - - -
S2‑050141 - - -
S2‑050142 - - -
S2‑050155 - - -
S2‑050156 - - -
S2‑050157 Teardown Ind in MBMS Multicast Service Deactivation Procedure - -
S2‑050158 Restrict the registration of SGSN - -
S2‑050159 Alignment of BM-SC subfunctions to MBMS User Service level (SA4) - -
S2‑050160 MBMS and the use of FBC - -
S2‑050161 - - -
S2‑050162 - - -
S2‑050163 - - -
S2‑050164 - - -
S2‑050165 Corrections to section 8.7 - -
S2‑050166 Alignment of BM-SC subfunctions to MBMS User Service level (SA4 & SA3) - -
S2‑050167 - - -
S2‑050168 - - -
S2‑050170 - - -
S2‑050171 Reply to Liaison Statement on MBMS User Service architecture S2 -
S2‑050172 - - -
S2‑050173 Corrections to MBMS Multicast Service Deactivation Procedure - -
S2‑050174 Reply to Liaison Statement on Status of OMA Mobile Broadcast Services S2 -
S2‑050175 Providing the BM-SC with approximate UE location information at MBMS context activation - -
S2‑050176 - - -
S2‑050205 - - -
S2‑050206 - - -
S2‑050207 - - -
S2‑050208 - - -
S2‑050209 - - -
S2‑050210 - - -
S2‑050211 - - -
S2‑050212 Load re-distribution with A/Gb/Iu flex. - -
S2‑050213 - - -
S2‑050214 - - -
S2‑050215 Incorrect sequence of events in 4..3.1.1 - -
S2‑050216 Correction on Sh interface - -
S2‑050217 Delete the capability information from the re-registration initiated by the UE - -
S2‑050218 Corrections to the Network initiated Application de-registration - -
S2‑050219 Correction to the Refer operation - -
S2‑050220 Editorial corrections in the identity procedures - -
S2‑050222 - - -
S2‑050223 - - -
S2‑050224 - - -
S2‑050225 - - -
S2‑050226 - - -
S2‑050227 - - -
S2‑050228 Update of IETF related references - -
S2‑050229 - - -
S2‑050230 Clarification to the re-assignment of Serving-CSCF - -
S2‑050231 Impact on Charging Correlation - -
S2‑050232 - - -
S2‑050233 - - -
S2‑050234 - - -
S2‑050235 - - -
S2‑050236 - - -
S2‑050237 - - -
S2‑050238 - - -
S2‑050239 - - -
S2‑050240 - - -
S2‑050241 - - -
S2‑050242 Velocity Request and Reporting - -
S2‑050243 - - -
S2‑050244 Clarification of LDR reference number - -
S2‑050245 - - -
S2‑050246 - - -
S2‑050247 - - -
S2‑050248 - - -
S2‑050249 - - -
S2‑050250 - - -
S2‑050251 - - -
S2‑050252 - - -
S2‑050253 - - -
S2‑050254 Optional sending of GCID for complete charging correlation - -
S2‑050255 Application Function Record information - -
S2‑050256 - - -
S2‑050257 - - -
S2‑050258 - - -
S2‑050259 - - -
S2‑050260 - - -
S2‑050261 - - -
S2‑050262 - - -
S2‑050263 - - -
S2‑050264 - - -
S2‑050267 - - -
S2‑050268 - - -
S2‑050269 - - -
S2‑050270 - - -
S2‑050271 - - -
S2‑050272 Forward HSS name - -
S2‑050273 - - -
S2‑050274 - - -
S2‑050275 - - -
S2‑050276 Use of Discovery Service as Trusted Authority - -
S2‑050277 - - -
S2‑050278 - - -
S2‑050279 - - -
S2‑050280 Corrections for errors introduced in 23.228 reorganization - -
S2‑050281 Corrections to flow for codec change - -
S2‑050282 - - -
S2‑050283 - - -
S2‑050284 P-CSCF discovery - -
S2‑050285 QoS of pre-established PDP context - -
S2‑050286 - - -
S2‑050287 Update of reference to TEL URI RFC 3966 - -
S2‑050288 Update of reference to TEL URI RFC 3966 - -
S2‑050289 Update of I-WLAN configuration and reference points in TS 23.002 - -
S2‑050290 - - -
S2‑050291 - - -
S2‑050292 Redirection in network sharing - -
S2‑050293 Correction of references - -
S2‑050294 - - -
S2‑050295 - - -
S2‑050296 Correction in Location Report Procedure - -
S2‑050297 - - -
S2‑050298 - - -
S2‑050299 - - -
S2‑050300 RIM-NACC clean up - -
S2‑050301 RIM-NACC clean up - -
S2‑050302 Correction of Packet Flow ID Allocation - -
S2‑050303 Correction of Packet Flow ID Allocation - -
S2‑050304 - - -
S2‑050305 - - -
S2‑050306 - - -
S2‑050307 - - -
S2‑050308 - - -
S2‑050309 RAB Allocation/Retention Priority - -
S2‑050310 SBLP interactions correction - -
S2‑050311 - - -
S2‑050312 - - -
S2‑050313 - - -
S2‑050314 - - -
S2‑050315 - - -
S2‑050316 - - -
S2‑050317 - - -
S2‑050318 - - -
S2‑050319 - - -
S2‑050320 - - -
S2‑050321 Alignment of 23.979 with OMA architecture - -
S2‑050322 - - -
S2‑050323 - - -
S2‑050324 - - -
S2‑050325 - - -
S2‑050326 - - -
S2‑050327 - - -
S2‑050328 - - -
S2‑050329 - - -
S2‑050330 - - -
S2‑050331 - - -
S2‑050332 - - -
S2‑050333 - - -
S2‑050334 - - -
S2‑050335 Update of reference to TEL URI RFC 3966 - -
S2‑050336 Correction of Packet Flow ID Allocation - -
S2‑050337 Correction of Packet Flow ID Allocation - -
S2‑050338 - - -
S2‑050339 Corrections to flow for codec change - -
S2‑050340 SBLP interactions correction - -
S2‑050341 - - -
S2‑050342 - - -
S2‑050343 - - -
S2‑050344 - - -
S2‑050345 Impact on Charging Correlation - -
S2‑050346 QoS of pre-established PDP context - -
S2‑050347 Alignment of 23.979 with OMA architecture - -
S2‑050348 Corrections to the Network initiated Application de-registration - -
S2‑050349 Correction to the Refer operation - -
S2‑050350 - - -
S2‑050351 LS on OSA Stage 2 - A cross-releases Overview S2 -
S2‑050352 - - -
S2‑050353 - - -
S2‑050354 - - -
S2‑050355 - - -
S2‑050356 - - -
S2‑050357 - - -
S2‑050358 - - -
S2‑050359 - - -
S2‑050360 - - -
S2‑050361 - - -
S2‑050362 - - -
S2‑050363 Correction in Location Report Procedure - -
S2‑050364 Clarification of LDR reference number - -
S2‑050365 Velocity Request and Reporting - -
S2‑050366 - - -
S2‑050367 - - -
S2‑050368 - - -
S2‑050369 - - -
S2‑050370 - - -
S2‑050371 - - -
S2‑050372 - - -
S2‑050373 - - -
S2‑050374 - - -
S2‑050375 - - -
S2‑050376 - - -
S2‑050377 - - -
S2‑050378 - - -
S2‑050379 - - -
S2‑050380 - - -
S2‑050381 - - -
S2‑050382 - - -
S2‑050383 - - -
S2‑050384 Redirection in network sharing - -
S2‑050385 - - -
S2‑050386 - - -
S2‑050387 Velocity Request and Reporting - -
S2‑050388 - - -
S2‑050389 Editorial corrections in the identity procedures - -
S2‑050390 - - -
S2‑050391 - - -
S2‑050392 - - -
S2‑050393 - - -
S2‑050394 - - -
S2‑050395 P-CSCF discovery - -
S2‑050397 - - -
S2‑050398 - - -
S2‑050399 - - -
S2‑050400 Redirection in network sharing - -
S2‑050401 Correction of references - -
S2‑050402 Update of IETF related references - -
S2‑050403 RIM-NACC clean up - -
S2‑050404 RIM-NACC clean up - -
S2‑050405 Velocity Request and Reporting - -
S2‑050406 - - -
S2‑050407 - - -
S2‑050408 - - -
S2‑050409 - - -
S2‑050410 Indication of Charging Unit y - -
S2‑050411 Updates to service data flow identification - -
S2‑050412 - - -
S2‑050413 Removal of the Ry reference point - -
S2‑050414 - - -
S2‑050415 FBC flows for bearer event reporting - -
S2‑050416 Editorial and readability amendments - -
S2‑050417 Clarification on the handling of the CRF to the input from the AF - -
S2‑050418 Changes to requirements on contacting CRF - -
S2‑050421 - - -
S2‑050422 - - -
S2‑050423 Corrections to the Network initiated Application de-registration - -
S2‑050424 Correction to the Refer operation - -
S2‑050425 - - -
S2‑050426 Reply LS on Impact of Shared Public User Identities on the Sh Interface S2 -
S2‑050427 Forward HSS name - -
S2‑050428 - - -
S2‑050429 Reply LS on Application Charging ID S2 -
S2‑050430 RE:LS on Control of simultaneous accesses for WLAN 3GPP IP access S2 -
S2‑050431 - - -
S2‑050432 Add the functionality of subscriber profile updating description - -
S2‑050433 Generalising Subscriber Location Function (SLF) to support WLAN and Removal of WLAN charging reference points and functional entities - -
S2‑050434 - - -
S2‑050435 RIM-NACC clean up - -
S2‑050436 RIM-NACC clean up - -
S2‑050437 REPLY LS on 23.060 CR on RIM-NACC clean up S2 -
S2‑050438 - - -
S2‑050439 - - -
S2‑050440 - - -
S2‑050441 - - -
S2‑050442 - - -
S2‑050443 - - -
S2‑050444 - - -
S2‑050445 - - -
S2‑050446 RAB Allocation/Retention Priority - -
S2‑050447 Impact on Charging Correlation - -
S2‑050448 Velocity Request and Reporting - -
S2‑050449 LS on transport of HSS address S2 -
S2‑050450 - - -
S2‑050451 - - -
S2‑050452 - - -
S2‑050453 - - -
S2‑050454 - - -
S2‑050455 - - -
S2‑050456 - - -
S2‑050457 - - -
S2‑050458 - - -
S2‑050459 - - -
S2‑050460 - - -
S2‑050461 - - -
S2‑050462 - - -
S2‑050463 - - -
S2‑050464 - - -
S2‑050465 RAB Allocation/Retention Priority - -
S2‑050466 - - -
S2‑050467 - - -
S2‑050468 - - -
S2‑050469 - - -
S2‑050470 Update of Annex B.4 - -
S2‑050471 LS on interactions between FBC and SBLP S2 -
S2‑050472 FBC and MBMS - -
S2‑050473 Clarification on the handling of the CRF to the input from the AF - -
S2‑050474 FBC and MBMS and collection of statistics - -
S2‑050475 Introduction of predefined handling in TPF - -
S2‑050476 Application Function Record information - -
S2‑050477 Removal of the Ry reference point - -
S2‑050478 LS on removal of Ry reference point S2 -
S2‑050479 FBC flows for bearer event reporting - -
S2‑050480 Editorial and readability amendments - -
S2‑050481 LS on protection of Rx and Gx interfaces S2 -
S2‑050482 - - -
S2‑050483 - - -
S2‑050484 - - -
S2‑050485 Reply to Reply LS (to N1-041944) on AS-NAS interaction for MBMS S2 -
S2‑050486 Reply LS on Session Repetition S2 -
S2‑050487 MBMS and the use of FBC - -
S2‑050488 Reply to LS on NAS signalling load at MBMS Session Start/Stop S2 -
S2‑050489 Response LS on MBMS session repetition S2 -
S2‑050490 - - -
S2‑050491 - - -
S2‑050492 - - -
S2‑050493 - - -
S2‑050495 - - -
S2‑050496 - - -
S2‑050497 - - -
S2‑050498 - - -
S2‑050499 - - -
S2‑050500 LS on the ACBOP TR status S2 -
S2‑050501 - - -
S2‑050502 - - -
S2‑050503 - - -
S2‑050504 Reply LS on the Workshop on "IMS over Fixed Access" (30th – 31st March 2005) S2 -
S2‑050505 LS on E112 Specifications S2 -
S2‑050506 LS on status of 3GPP System PS domain services over WLAN 3GPP IP access in Rel-6 S2 -
S2‑050507 LS on Reporting Velocity S2 -
S2‑050508 LS on protocol aspects for CSI S2 -
S2‑050509 Reply to LS on AMR multi-rate operation of VoIMS S2 -
S2‑050510 Reply to LS on Status of current work in SA1 on the Combining CS and IMS services S2 -
S2‑050511 - - -
S2‑050512 - - -
S2‑050513 - - -
S2‑050514 - - -
S2‑050515 - - -
S2‑050516 - - -
S2‑050517 - - -
S2‑050518 Clarification on the handling of the CRF to the input from the AF - -
S2‑050519 - - -
S2‑050520 - - -
S2‑050521 - - -
S2‑050522 Generalising Subscriber Location Function (SLF) to support WLAN and Removal of WLAN charging reference points and functional entities - -
S2‑050523 - - -
S2‑050524 FBC and MBMS and changes to requirements on contacting CRF - -
S2‑050525 Corrections to the Network initiated Application de-registration - -
S2‑050526 Clarification of LDR reference number - -
S2‑050527 - - -

page generated from database: 2024-04-22 07:58:53

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