3GPP TDocs (written contributions) at meeting
Meeting: C3-36 - 2005-04-25 to 2005-04-29, Cancun
meeting id: C3-36 (click id for more info on this meeting)Click on the Tdoc to open its file.
TDoc | Title | Source | Remarks |
---|---|---|---|
C3‑050238 | Title | Source | - |
C3‑050239 | Title | Source | - |
C3‑050240 | Title | Source | - |
C3‑050241 | Title | Source | - |
C3‑050242 | Title | Source | - |
C3‑050243 | Title | Source | - |
C3‑050244 | Title | Source | - |
C3‑050245 | Title | Source | - |
C3‑050246 | - | - | - |
C3‑050247 | Brief notes from CN#27/CT#27 relevant to CN3/CT3 | CT3 Convenor | - |
C3‑050248 | Hilites from CN#27/SA#27 (from the SA chairman) | CT3 Convenor | - |
C3‑050249 | - | - | - |
C3‑050250 | - | - | - |
C3‑050251 | Meeting Calendar for 2005/2006 | MCC | - |
C3‑050252 | Reply LS on MBMS Session Repetition (S4-050198) | GERAN2 | - |
C3‑050253 | LS on MBMS Session Duration IE | GERAN2 | - |
C3‑050254 | Reply LS (to R3-041648) on MBMS Information Elements over Iu interface | CN1 | - |
C3‑050255 | LS on service based inter-system hand over | CN1 | - |
C3‑050256 | LS on Cooperation with TISPAN NGN for IMS-CS MGW protocol | 3GPP CN WG4 (CT4 after CN#27 March 2005) | - |
C3‑050257 | Reply to LS on Session Repetition | RAN2 | - |
C3‑050258 | Response on LS on network-initiated SCUDIF support | RAN3 | - |
C3‑050259 | Liaison statement MBMS User Service finalization | 3GPP TSG SA4 | - |
C3‑050260 | Reply LS on Session Repetition (GP-050573, R2-050273, R2-050641, S2-050486) | SA4 | - |
C3‑050261 | Reply LS on MBMS Session Repetition (S2-050489) | SA4 | - |
C3‑050262 | Reply LS on AoC and SCUDIF interaction | SA5 SWGB | - |
C3‑050263 | LS on Diameter Credit Control (DCC) Session Handling | SA5 SWGB | - |
C3‑050264 | Reply LS on tracing information for MBMS services | SA5 SWG-D | - |
C3‑050265 | Response on MBMS Common IE encoding | RAN3 | - |
C3‑050266 | Draft contribution for ITU-R WP8F on current 3GPP activities toward IP applications over mobile systems | ITU-R Ad Hoc | - |
C3‑050267 | LS on service based inter-system hand over | TSG GERAN [WG2] | - |
C3‑050268 | - | ALCATEL | - |
C3‑050269 | - | Alcatel | - |
C3‑050270 | - | ALCATEL | - |
C3‑050271 | - | ALCATEL | - |
C3‑050272 | - | ALCATEL | - |
C3‑050273 | - | Siemens | Revisedin354 |
C3‑050274 | - | Siemens | Revisedin353 |
C3‑050275 | - | Siemens | - |
C3‑050276 | TPF/CRF dialogues and DCC subsessions at the Gx interface | Siemens | - |
C3‑050277 | - | Siemens | - |
C3‑050278 | Page: 1 | Siemens | - |
C3‑050279 | Charging Implications for Network Initiated service Change | Siemens | - |
C3‑050280 | Page: 1 | Nokia | - |
C3‑050281 | Page: 1 | Nokia | - |
C3‑050282 | - | Nokia, Orange | - |
C3‑050283 | Page: 1 | Nokia, Orange | - |
C3‑050284 | Page: 1 | Nokia | - |
C3‑050285 | - | - | - |
C3‑050286 | - | - | - |
C3‑050287 | - | - | - |
C3‑050288 | - | Nortel Networks, Vodafone | - |
C3‑050289 | - | Nortel Networks, Vodafone | - |
C3‑050290 | Unnecessary IMSI information | Nortel Networks, Vodafone | - |
C3‑050291 | Correction to missing AVP code values | Nortel Networks | - |
C3‑050292 | MBMS-Session-Identity is optional | Nortel Networks, Ericsson | - |
C3‑050293 | Problem with Auth-Application-Id in several TSs | Nortel Networks | - |
C3‑050294 | - | - | Withdrawn |
C3‑050295 | Mobile Originated Call: | NTT DoCoMo | - |
C3‑050296 | Mobile Originated Call: | NTT DoCoMo | - |
C3‑050297 | Mobile Originated Call: | NTT DoCoMo | - |
C3‑050298 | Mobile Originated Call: | NTT DoCoMo | - |
C3‑050299 | TR 24.819v010 Protocol impact from providing IMS services via fixed broadband | Siemens | - |
C3‑050300 | - | T-Mobile | - |
C3‑050301 | - | T-Mobile | - |
C3‑050302 | - | - | - |
C3‑050303 | - | Vodafone, Nortel Networks, Siemens, Orange | - |
C3‑050304 | Addition of the PLMN change value in the Event-Trigger AVP | Vodafone | - |
C3‑050305 | Correction to charging information for MBMS | Vodafone | - |
C3‑050306 | - | Vodafone | - |
C3‑050307 | CT3 Terms of Reference | CT3 Convenor | - |
C3‑050308 | Discussion: Removal of company-specific header | ERICSSON | - |
C3‑050309 | Proposal, provision of P-CSCF address in case of GPRS | Ericsson | - |
C3‑050310 | - | Ericsson | - |
C3‑050311 | [H11] Enter the source of the CR. This is either (a) one or several companies or, (b) if a (sub)working group has already reviewed and agreed the CR, then list the group as the source. | Ericsson | - |
C3‑050312 | Correction of references | Ericsson | - |
C3‑050313 | Correction of reference | Ericsson | - |
C3‑050314 | DCCA Sub-sessions | Ericsson | - |
C3‑050315 | - | Ericsson, Nortel Networks | - |
C3‑050316 | - | Ericsson | - |
C3‑050317 | Rx Packet Flows | Ericsson | - |
C3‑050318 | Rx Reference Model | Ericsson | - |
C3‑050319 | - | Ericsson | - |
C3‑050320 | - | Ericsson, Nortel Networks | - |
C3‑050321 | - | Ericsson, Nortel Networks | - |
C3‑050322 | [D1]LS on use sub-sessions | CT3 | - |
C3‑050323 | - | - | - |
C3‑050324 | - | LM Ericsson | - |
C3‑050325 | - | LM Ericsson | - |
C3‑050326 | - | LM Ericsson | - |
C3‑050327 | Page: 1 | Lucent Technologies | - |
C3‑050328 | Page: 1 | Lucent Technologies | - |
C3‑050329 | PSTN bridging scenarios during redirection | Lucent Technologies | - |
C3‑050330 | Page: 1 | Lucent Technologies | - |
C3‑050331 | Redirection and ISUP transparency | Lucent Technologies | - |
C3‑050332 | IMS SIP profile for ISUP transparency | Lucent Technologies | - |
C3‑050333 | - | Huawei, Lucent, China Mobile | - |
C3‑050334 | - | - | - |
C3‑050335 | - | Nortel Networks, Ericsson | - |
C3‑050336 | 2.If needed, information from step 1 is used to access a proper set of UMTS QoS Parameters. See 3GPP TS 26.236 [6] for Conversational Codec Applications and 3GPP TS 26.234 [5] for Streaming Codec Applications. | Siemens | - |
C3‑050337 | 2.If needed, information from step 1 is used to access a proper set of UMTS QoS Parameters. See 3GPP TS 26.236 [6] for Conversational Codec Applications and 3GPP TS 26.234 [5] for Streaming Codec Applications. | Siemens | - |
C3‑050338 | Reply LS on MBMS Session Repetition | RAN2 | - |
C3‑050339 | LS reply on service based inter-system hand over | SA1 | - |
C3‑050340 | Reply to Reply LS on AoC and SCUDIF interaction | SA1 | - |
C3‑050341 | LS reply on service based inter-system hand over | SA2 | - |
C3‑050342 | Reply to LS on MBMS Session Duration IE | SA2 | - |
C3‑050343 | Reply LS on MBMS User Service finalization from SA4 | SA2 | - |
C3‑050344 | Reply LS on MBMS Session Repetition from SA4 | SA2 | - |
C3‑050345 | LS on DCC session handling | TSG_SA WG2. | - |
C3‑050346 | LS on GPRS P-CSCF discovery procedure | TSG_SA WG2 | - |
C3‑050347 | Network initiated upgrade procedures for SCUDIF | LM Ericsson | - |
C3‑050348 | - | Siemens | - |
C3‑050349 | - | Siemens | - |
C3‑050350 | - | Siemens | - |
C3‑050351 | - | Siemens | - |
C3‑050352 | - | Siemens | - |
C3‑050353 | - | Siemens | - |
C3‑050354 | - | Siemens | - |
C3‑050357 | Corrections to Flow identifiers for Forking | Siemens | - |
C3‑050358 | CT3 Terms of Reference | CT3 Convenor | - |
C3‑050359 | - | Vodafone | - |
C3‑050360 | CT3 Terms of Reference | CT3 Convenor | - |
C3‑050361 | MBMS-Session-Duration is mandatory | Nortel Networks | - |
C3‑050362 | [DRAFT][D1] Reply LS on tracing information for MBMS services | CT3 | - |
C3‑050363 | Mobile Originated Call: | NTT DoCoMo | - |
C3‑050364 | Mobile Originated Call: | NTT DoCoMo | - |
C3‑050365 | Mobile Originated Call: | NTT DoCoMo | - |
C3‑050366 | Mobile Originated Call: | NTT DoCoMo | - |
C3‑050367 | Various Corrections | Siemens | - |
C3‑050368 | - | Siemens | - |
C3‑050369 | - | Huawei, Lucent, China Mobile | - |
C3‑050370 | Correction to MBMS-2G-3G-Indicator AVP | Nortel Networks, Vodafone | - |
C3‑050371 | - | Vodafone | - |
C3‑050372 | - | T-Mobile | - |
C3‑050374 | - | Nokia, | - |
C3‑050375 | - | Nokia | - |
C3‑050377 | Page: 1 | Nokia, Orange | - |
C3‑050378 | Page: 1 | Lucent Technologies | - |
C3‑050379 | Page: 1 | Lucent Technologies | - |
C3‑050380 | Page: 1 | Ericsson | - |
C3‑050381 | - | - | - |
C3‑050382 | - | Vodafone | - |
C3‑050383 | Gx Auth-Application-Id AVP use | Ericsson, Nortel Networks | - |
C3‑050384 | Correction to the use of Auth-Application-Id in Gmb | Nortel Networks, Ericsson | - |
C3‑050385 | Gq Auth-Application-Id AVP use | Ericsson, Nortel Networks | - |
C3‑050386 | Rx Auth-Application-Id AVP use | Ericsson, Nortel Networks | - |
C3‑050387 | - | - | - |
C3‑050388 | Page: 1 | Nokia, Orange | - |
C3‑050389 | Page: 1 | Nokia | - |
C3‑050390 | Page: 1 | Nokia | - |
C3‑050391 | Page: 1 | Ericsson, Nokia, Orange | - |
C3‑050392 | Charging Implications of SCUDIF | CT3 | - |
C3‑050393 | Flow AVP only needed when ICID present | Nortel Networks, Vodafone | - |
C3‑050394 | - | Ericsson | - |
C3‑050395 | - | Ericsson | - |
C3‑050396 | Sending AAA after provisioning | Siemens | - |
C3‑050397 | - | Siemens | - |
C3‑050398 | Clarifications on Binding | Siemens | - |
C3‑050399 | Unnecessary AVPs in RAA | Siemens | - |
C3‑050400 | - | Siemens | - |
C3‑050401 | 2.If needed, information from step 1 is used to access a proper set of UMTS QoS Parameters. See 3GPP TS 26.236 [6] for Conversational Codec Applications and 3GPP TS 26.234 [5] for Streaming Codec Applications. | Siemens | - |
C3‑050402 | Various Corrections | Siemens | - |
C3‑050403 | - | T-Mobile | - |
C3‑050404 | [DRAFT][D1] LS on IMS support of TISPAN NGN supplementary services | CT3 | - |
C3‑050405 | Mobile Originated Call: | NTT DoCoMo | - |
C3‑050406 | - | - | - |
C3‑050407 | Various Corrections | Siemens | - |
C3‑050408 | - | - | - |
C3‑050409 | Page: 1 | Nokia | - |
C3‑050410 | CT3 Terms of Reference | CT3 Convenor | - |
C3‑050411 | Tracing information for MBMS | Vodafone | - |
C3‑050412 | Page: 1 | Nokia, | - |
C3‑050413 | Rx Abbreviations | Ericsson | - |
C3‑050414 | Provision of Service Information at session establishment | Siemens | - |
C3‑050415 | - | Siemens | - |
C3‑050416 | Re-binding of IP Flows at Bearer Removal | Siemens | - |
C3‑050417 | Pp Interface | Huawei, Lucent, China Mobile | - |
C3‑050418 | Code allocation for Gx interface | - | - |
C3‑050419 | Page: 1 | Nokia, Orange, Ericsson, Siemens | - |
C3‑050420 | Charging Implications of SCUDIF | CT3 | - |
C3‑050421 | - | T-Mobile | - |
C3‑050422 | [DRAFT][D1] LS on IMS support of TISPAN NGN supplementary services | CT3 | - |
C3‑050423 | [DRAFT][D1] Reply LS on tracing information for MBMS services | CT3 | - |
C3‑050424 | [D1]LS on use of the Auth-Application-Id AVP | CT3 | - |
C3‑050425 | - | Vodafone, Nortel Networks, Siemens, Orange | - |
C3‑050426 | - | - | - |
C3‑050427 | CT3 Terms of Reference | CT3 Convenor | - |
C3‑050428 | Removal of DCC sub-sessions | Vodafone, Nortel Networks, Siemens, Orange | - |
C3‑050429 | - | Ericsson | - |
C3‑050430 | - | - | - |
C3‑050431 | Page: 1 | Lucent Technologies | - |
C3‑050432 | Transparent data call request in dual mode case | - | - |
C3‑050433 | [DRAFT][D1] Reply LS on network initiated SCUDIF support | CT3 | - |
C3‑050434 | Page: 1 | Nokia, Orange, Ericsson, Siemens, Vodafone, Nortel | - |
C3‑050435 | Charging Implications of SCUDIF | CT3 | - |
C3‑050436 | Reply LS on tracing information for MBMS services | CT3 | - |
C3‑050438 | [D1]LS on IMS support of TISPAN NGN supplementary services | CT3 | - |
C3‑050439 | Rx Request of Charging Rule flow | Ericsson | - |
C3‑050440 | Reply LS on network initiated SCUDIF support | CT3 | - |
page generated from database: 2024-04-13 13:51:47