The 5G Standard

3GPP TDocs (written contributions) at meeting

Meeting: S1-28 - 2005-04-04 to 2005-04-08, Beijing

meeting id: S1-28 (click id for more info on this meeting)

Click on the Tdoc to open its file.

TDoc Title Source Remarks
S1‑050147 - - -
S1‑050257 - - imported from 3GU
S1‑050258 - - imported from 3GU
S1‑050260 - - imported from 3GU
S1‑050261 - - imported from 3GU
S1‑050262 - - imported from 3GU
S1‑050263 USE case for CSiCS 3 -
S1‑050264 - - imported from 3GU
S1‑050265 - - imported from 3GU
S1‑050266 - - imported from 3GU
S1‑050267 - - imported from 3GU
S1‑050268 - - imported from 3GU
S1‑050269 - - imported from 3GU
S1‑050270 - - imported from 3GU
S1‑050271 - - imported from 3GU
S1‑050272 - - imported from 3GU
S1‑050273 - - imported from 3GU
S1‑050274 - - imported from 3GU
S1‑050275 - - imported from 3GU
S1‑050276 - - imported from 3GU
S1‑050277 - - imported from 3GU
S1‑050278 - - imported from 3GU
S1‑050279 - - imported from 3GU
S1‑050280 - - imported from 3GU
S1‑050281 - - imported from 3GU
S1‑050282 - - imported from 3GU
S1‑050283 - - imported from 3GU
S1‑050284 - - imported from 3GU
S1‑050285 - - imported from 3GU
S1‑050286 - - imported from 3GU
S1‑050287 - - imported from 3GU
S1‑050288 - - imported from 3GU
S1‑050289 - - imported from 3GU
S1‑050290 - - imported from 3GU
S1‑050291 - - imported from 3GU
S1‑050292 - - imported from 3GU
S1‑050293 LS reply on service based inter-system hand over S1 imported from 3GU
S1‑050294 - - imported from 3GU
S1‑050295 Requirements for the handling of SIP URIs with Presence or IM prefixes Lucent Technologies -
S1‑050296 - - imported from 3GU
S1‑050297 - - imported from 3GU
S1‑050298 Proposed text for multicast service Panasonic -
S1‑050299 - - imported from 3GU
S1‑050300 - - imported from 3GU
S1‑050301 - - imported from 3GU
S1‑050302 - - imported from 3GU
S1‑050303 - - imported from 3GU
S1‑050304 - - imported from 3GU
S1‑050305 - - imported from 3GU
S1‑050306 - - imported from 3GU
S1‑050307 - - imported from 3GU
S1‑050308 - - imported from 3GU
S1‑050309 - - imported from 3GU
S1‑050310 - - imported from 3GU
S1‑050311 - - imported from 3GU
S1‑050312 - - imported from 3GU
S1‑050313 - - imported from 3GU
S1‑050314 - - imported from 3GU
S1‑050315 - - imported from 3GU
S1‑050316 - - imported from 3GU
S1‑050317 - - imported from 3GU
S1‑050318 - - imported from 3GU
S1‑050319 - - imported from 3GU
S1‑050320 - - imported from 3GU
S1‑050321 - - imported from 3GU
S1‑050322 GUP Rel-7 WI Lucent Technologies -
S1‑050323 - - imported from 3GU
S1‑050324 - - imported from 3GU
S1‑050325 - - imported from 3GU
S1‑050326 - - imported from 3GU
S1‑050327 - - imported from 3GU
S1‑050328 - - imported from 3GU
S1‑050329 - - imported from 3GU
S1‑050330 CSICS draft TS22.xxx - UE & Radio Capability detection John Watson Vodafone -
S1‑050331 - - imported from 3GU
S1‑050332 - - imported from 3GU
S1‑050333 - - imported from 3GU
S1‑050334 - - imported from 3GU
S1‑050335 Addressing SMS to a Group Nortel Networks -
S1‑050336 - - imported from 3GU
S1‑050337 Improvements to Key Aspects of an AIPN AIPN Rapporteur (NTT DoCoMo Inc.) -
S1‑050338 - - imported from 3GU
S1‑050339 - - imported from 3GU
S1‑050340 - - imported from 3GU
S1‑050341 - - imported from 3GU
S1‑050342 - - imported from 3GU
S1‑050343 TR Skeleton for NSP Research In Motion -
S1‑050344 - - imported from 3GU
S1‑050345 - - imported from 3GU
S1‑050346 - - imported from 3GU
S1‑050347 - - imported from 3GU
S1‑050348 - - imported from 3GU
S1‑050349 - - imported from 3GU
S1‑050350 - - imported from 3GU
S1‑050351 - - imported from 3GU
S1‑050352 - - imported from 3GU
S1‑050353 - - imported from 3GU
S1‑050354 - - imported from 3GU
S1‑050355 - - imported from 3GU
S1‑050356 - - imported from 3GU
S1‑050357 - - imported from 3GU
S1‑050358 - - imported from 3GU
S1‑050359 - - imported from 3GU
S1‑050360 - - imported from 3GU
S1‑050361 - - imported from 3GU
S1‑050362 - - imported from 3GU
S1‑050363 - - imported from 3GU
S1‑050364 - - -
S1‑050365 - - -
S1‑050366 - - -
S1‑050367 - - -
S1‑050368 - - -
S1‑050369 - - -
S1‑050370 - - -
S1‑050371 - - -
S1‑050372 - - -
S1‑050373 - - -
S1‑050374 - - -
S1‑050376 - - -
S1‑050377 - - -
S1‑050378 - - -
S1‑050379 - - -
S1‑050380 - - -
S1‑050381 - - -
S1‑050382 - - -
S1‑050383 - - -
S1‑050384 - - -
S1‑050386 - - -
S1‑050387 - - -
S1‑050388 - - -
S1‑050389 - - -
S1‑050390 - - -
S1‑050391 - - -
S1‑050392 - - -
S1‑050394 - - -
S1‑050395 - - -
S1‑050396 AoC for SCUDIF - -
S1‑050397 AoC for SCUDIF - -
S1‑050398 AoC for SCUDIF - -
S1‑050399 AoC for SCUDIF - -
S1‑050400 - - -
S1‑050401 - - -
S1‑050402 - - -
S1‑050403 - - -
S1‑050404 - - -
S1‑050405 - - -
S1‑050406 - - -
S1‑050407 - - -
S1‑050408 - - -
S1‑050410 - - -
S1‑050411 - - -
S1‑050412 - - -
S1‑050413 - - -
S1‑050414 - - -
S1‑050415 - - -
S1‑050416 - - -
S1‑050417 - - -
S1‑050418 - - -
S1‑050419 - - -
S1‑050420 - - -
S1‑050421 - - -
S1‑050422 - - -
S1‑050423 - - -
S1‑050424 - - -
S1‑050425 - - -
S1‑050426 - - -
S1‑050429 - - -
S1‑050430 - - -
S1‑050431 - - -
S1‑050432 - - -
S1‑050433 - - -
S1‑050434 - - -
S1‑050435 - - -
S1‑050436 - - -
S1‑050437 - - -
S1‑050438 - - -
S1‑050439 - - -
S1‑050440 - - -
S1‑050441 - - -
S1‑050442 - - -
S1‑050443 - - -
S1‑050444 - - -
S1‑050445 - - -
S1‑050446 - - -
S1‑050447 - - -
S1‑050448 - - -
S1‑050449 - - -
S1‑050450 - - -
S1‑050451 - - -
S1‑050452 Requirements for the handling of SIP URIs with Presence or IM prefixes - -
S1‑050453 - - -
S1‑050454 - - -
S1‑050455 - - -
S1‑050456 - - -
S1‑050457 - - -
S1‑050458 - - -
S1‑050459 - - -
S1‑050460 - - -
S1‑050463 - - -
S1‑050464 - - -
S1‑050465 - - -
S1‑050469 Correction on the use of calling subscriber and destination subscriber - -
S1‑050470 Correction on the use of calling subscriber and destination subscriber - -
S1‑050471 Correction on the use of calling subscriber and destination subscriber - -
S1‑050472 Correction on the use of calling subscriber and destination subscriber - -
S1‑050473 Correction on the use of calling subscriber and destination subscriber - -
S1‑050474 Correction on the use of calling subscriber and destination subscriber - -
S1‑050475 Correction on the use of calling subscriber and destination subscriber - -
S1‑050476 Correction on the use of calling subscriber and destination subscriber - -
S1‑050477 Correction on the use of calling subscriber and destination subscriber - -
S1‑050479 Correction of WLAN into I-WLAN - -
S1‑050480 Explicit wording of requirements for access to 3GPP PS services - -
S1‑050481 Reply to Reply LS on AoC and SCUDIF interaction S1 -
S1‑050482 - - -
S1‑050483 Add requirement for OSA Service Broker - -
S1‑050484 - - -
S1‑050485 - - -
S1‑050486 Removal of requirements for emergency calls for IMS in Rel-6 - -
S1‑050487 Correction of OSA acronym - -
S1‑050488 Correction of OSA acronym - -
S1‑050489 - - -
S1‑050490 - - -
S1‑050491 Sending or receiving of short messages in parallel to an active group call - -
S1‑050492 Support of the use of GPRS for individual VGCS subscribers in parallel to an active group call - -
S1‑050493 Addressing SMS to a Group - -
S1‑050494 - - -
S1‑050495 - - -
S1‑050496 Corrections to TR 22.978 - -
S1‑050497 Improvements to Key Aspects of an AIPN - -
S1‑050498 Improvement of TR 22.978 Annexes - -
S1‑050499 Alignment and improvement of recommended requirements and conclusions of TR 22.978 - -
S1‑050500 - - -
S1‑050501 - - -
S1‑050502 Content-based Charging between Operators - -
S1‑050503 Modification of AIPN session adaptation - -
S1‑050504 - - -
S1‑050505 - - -
S1‑050506 - - -
S1‑050507 - - -
S1‑050508 - - -
S1‑050509 Reply to LS on video telephony activity in GSM Association S1 -
S1‑050510 - - -
S1‑050511 - - -
S1‑050512 Mandatory functionality in W-LAN S1 -
S1‑050513 - - -
S1‑050514 - - -
S1‑050515 - - -
S1‑050516 - - -
S1‑050517 Reply LS on GPRS Network Selection S1 -
S1‑050518 Clarification on optionality of Service Provider Name indication - -
S1‑050519 Clarification on optionality of Service Provider Name indication - -
S1‑050520 Response to LS on Service Parameters management from T3/CT6 S1 -
S1‑050521 LS on Long Term Evolution for the UTRA and UTRAN S1 -
S1‑050522 - - -
S1‑050523 - - -
S1‑050524 Removal of reference to requirement for emergency calls in Rel-6 - -
S1‑050525 Correction of a faulty reference in 22.234 - -
S1‑050526 - - -
S1‑050527 - - -
S1‑050528 Clarification on requirements for talker change - -
S1‑050529 Multiple Public Addresses for Single User - -
S1‑050530 - - -
S1‑050531 Introducing notification based on current location of target UE - -
S1‑050532 Clarification of LCS in I-WLAN - -
S1‑050533 Response to LS on Service Provider Name from T3/CT6 S1 -
S1‑050534 Correction to interworking between CAMEL and SCUDIF calls - -
S1‑050535 Correction to interworking between CAMEL and SCUDIF calls - -
S1‑050536 - - -
S1‑050537 LS on service connectivity provisioning S1 -
S1‑050538 Enabling integrated services in AIPN - -
S1‑050539 Introduce Group Communication Services to AIPN - -
S1‑050581 Voice call continuity requirements - imported from 3GU
S1‑050582 LS on requirements for voice call continuity S1 imported from 3GU

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