3GPP TDocs (written contributions) at meeting
Meeting: C4-64b - 2014-03-31 to 2014-04-04, Dubrovnik
meeting id: C4-64b (click id for more info on this meeting)Click on the Tdoc to open its file.
TDoc | Title | Source | Remarks |
---|---|---|---|
C4‑140424 | Agenda & Timetable for CT4 #64bis – Status: Preliminary | Chairman TSG-CT WG4 | - |
C4‑140425 | Agenda & Timetable for CT4 #64bis – Status: Document Submission Deadline | Chairman TSG-CT WG4 | - |
C4‑140426 | Agenda & Timetable for CT4 #64bis – Status: Eve of Meeting | Chairman TSG-CT WG4 | - |
C4‑140427 | Proposed Allocation of Documents to Agenda Items for CT4 #64bis: Status at Document Submission Deadline | Chairman, TSG-CT WG4 | - |
C4‑140428 | Proposed Allocation of Documents to Agenda Items for CT4 #64bis: Status on Eve of Meeting | Chairman, TSG-CT WG4 | - |
C4‑140429 | - | - | - |
C4‑140430 | Status Report for CT#63 and SA#63 | CT4 Chairman | - |
C4‑140431 | - | - | - |
C4‑140432 | Support of RTP transport multiplexing (Iq, stage 2) | Alcatel-Lucent | - |
C4‑140433 | Support of RTP transport multiplexing (Iq, stage 3) | Alcatel-Lucent | - |
C4‑140434 | SGmb path failure recovery | one2many, Alcatel-Lucent, ALU Shanghai Bell, Ericsson, Huawei | - |
C4‑140435 | Pseudo-CR on General clean-up of the TR | Cisco | - |
C4‑140436 | Pseudo-CR on Conclusion on definition of Load Control Information | Cisco, Ericsson, Verizon, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | - |
C4‑140437 | Pseudo-CR on Conclusion on interaction between Load Control Info and information received from DNS | Cisco, Ericsson, Verizon, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | - |
C4‑140438 | Pseudo-CR on Conclusion on maximum number of Load Control Info instances | Cisco, Ericsson, Verizon | - |
C4‑140439 | Pseudo-CR on Conclusion on message throttling algorithm | Cisco, Ericsson, Verizon, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | - |
C4‑140440 | Pseudo-CR on Description and conclusion on message prioritization based on procedure | Cisco | - |
C4‑140441 | Pseudo-CR on Conclusion on propagation of MME/SGSN identity to the PGW | Cisco, Ericsson, Verizon | - |
C4‑140442 | Pseudo-CR on Conclusion on updating PGW with overload control info of the target MME/SGSN | Cisco, Ericsson, Verizon | - |
C4‑140443 | Pseudo-CR on Conclusion on interaction between APN back-off timer and overload control information | Cisco, Ericsson, Verizon, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | - |
C4‑140444 | Pseudo-CR on Conclusion on maximum number of Overload Control Info instances | Cisco, Ericsson, Verizon | - |
C4‑140445 | Pseudo-CR on Conclusion on the discovery of the support of the feature by peer node | Cisco, Ericsson, Verizon, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | - |
C4‑140446 | Pseudo-CR on Conclusion on partial support of load and overload control in the network | Cisco, Ericsson, Verizon, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | - |
C4‑140447 | Pseudo-CR on Summary of conclusion in clause 9 | Cisco, Ericsson, Verizon, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | - |
C4‑140448 | Information on the Progress of the GTP-C Overload Control Mechanism workitem | Cisco | - |
C4‑140449 | Skeleton for capturing various aspects of GTP-C overload control solution | Cisco | - |
C4‑140450 | UE Time Zone information for TWAN S2a access | Cisco | - |
C4‑140451 | TWAN Identifier Timestamp in PDN disconnection procedure | Cisco | - |
C4‑140452 | TWAN ID Timestamp in Bearer Revocation Ack message for PGW initiated bearer deactivation procedure in Trusted WLAN | Cisco | - |
C4‑140453 | UE Time Zone for PMIP | Cisco | - |
C4‑140454 | TWAN Identifier Timestamp for PMIP | Cisco | - |
C4‑140455 | Introduction of SGSN Number, SGSN Lgd Identifier and MME SLg identifier | Cisco | - |
C4‑140456 | Handling of E-RAB Release due to GTPU error indication for default bearer at MME | Cisco | - |
C4‑140457 | - | - | - |
C4‑140458 | Progress of the eMediasec work item | Alcatel-Lucent | - |
C4‑140459 | Pseudo-CR on Editorial Clean-up | Alcatel-Lucent | - |
C4‑140460 | Pseudo-CR on e2ae media security – Iq procedures for TCP-based media | Alcatel-Lucent | - |
C4‑140461 | Pseudo-CR on e2e media security – Iq & Ix procedures for TCP-based media | Alcatel-Lucent | - |
C4‑140462 | Pseudo-CR on Conclusions and Recommendations | Alcatel-Lucent | - |
C4‑140463 | e2e media security for TCP-based media using TLS Functional requirements | Alcatel-Lucent | - |
C4‑140464 | e2ae media security for TCP-based media using TLS Functional requirements | Alcatel-Lucent | - |
C4‑140465 | e2ae media security for UDP-based media using DTLS Functional requirements | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | - |
C4‑140466 | PWS Restart Indication parameters | MCC, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | - |
C4‑140467 | HeNB ID verification in the PWS Restart Indication message | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Huawei, one2many, AT&T, NEC | - |
C4‑140468 | Routing of PWS messages to HeNBs | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Huawei, one2many, AT&T | - |
C4‑140469 | Routing of PWS messages to HeNBs | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Huawei, one2many, AT&T | - |
C4‑140470 | MBMS session re-establishment with modified M1 IP multicast addresses | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | - |
C4‑140471 | MCE failure | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | - |
C4‑140472 | Pseudo-CR on Conclusions for enforcement of overload control | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Verizon | - |
C4‑140473 | Pseudo-CR on Conclusions on the applicable 3GPP interfaces for load and overload control | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Verizon, Cisco, Huawei | - |
C4‑140474 | Pseudo-CR on Conclusions on the applicable non-3GPP access interfaces for overload control | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Verizon | - |
C4‑140475 | HRPD Sector ID definition | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | - |
C4‑140476 | TWAN Identifier Timestamp | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | - |
C4‑140477 | Civic address encoding | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | - |
C4‑140478 | Reporting changes of UE presence in Presence Reporting Area | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | - |
C4‑140479 | Presence Reporting Area Action | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | - |
C4‑140480 | ULI change reporting when E-RAB/RAB/PFC is established | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | - |
C4‑140481 | Alternate LMAA or IPv4-LMAA | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Cisco | - |
C4‑140482 | Alternate LMA address for user plane | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Cisco | - |
C4‑140483 | DISC on LTE to GERAN SRVCC Handover | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | - |
C4‑140484 | SRVCC Handover to GERAN | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | - |
C4‑140485 | SRVCC Handover to GERAN | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | - |
C4‑140486 | SRVCC Handover to GERAN | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | - |
C4‑140487 | SRVCC Handover to GERAN | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | - |
C4‑140488 | Number of authentication vectors in the MM Context IE | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | - |
C4‑140489 | Number of authentication vectors in the MM Context IE | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | - |
C4‑140490 | DISC on Context Response with P-TMSI Signature Mismatch | Alcatel-Lucent | - |
C4‑140491 | Context Response with P-TMSI Signature Mismatch | Alcatel-Lucent | - |
C4‑140492 | Context Response with P-TMSI Signature Mismatch | Alcatel-Lucent | - |
C4‑140494 | Restoring the (S)Gs associations during tracking/routing area update procedures | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | - |
C4‑140495 | Pseudo-CR on final conclusions | Ericsson, Verizon, Alcatel Lucent, Cisco, NSN, Oracle, Telecom Italia, AT&T, KDDI, Rogers Wireless Inc., HP, LG Electronics | - |
C4‑140496 | Update cause to indicate downlink message delivery failure due to crash with mobility event | ZTE | - |
C4‑140497 | MDT configuration during inter-MME handover | ZTE | - |
C4‑140498 | MDT configuration during inter-MME handover | ZTE | - |
C4‑140499 | Sm path failure recovery | one2many, Alcatel-Lucent, ALU Shanghai Bell | - |
C4‑140500 | - | - | - |
C4‑140501 | ICE support in Iq interface | Huawei | - |
C4‑140502 | ICE support in Iq interface | Huawei | - |
C4‑140503 | ICE support in Ix interface | Huawei | - |
C4‑140504 | ICE support for MRF in Mp interface | Huawei | - |
C4‑140505 | ICE support for MRF in Mp interface | Huawei | - |
C4‑140506 | ICE support in Mn interface | Huawei | - |
C4‑140507 | ICE support in Mc interface | Huawei | - |
C4‑140508 | Private User Identity retrieval | NSN | - |
C4‑140509 | Private User Identity retrieval | NSN | - |
C4‑140510 | Overload Control | NSN | - |
C4‑140511 | IP-SM-GW address handling clarification | NSN | - |
C4‑140512 | IP-SM-GW address handling clarification | NSN | - |
C4‑140513 | Pseudo-CR on Requirements for Scopes and Report Types | NSN | - |
C4‑140514 | CS to PS SRVCC | NSN | - |
C4‑140515 | CS to PS SRVCC | NSN | - |
C4‑140516 | CS to PS SRVCC | NSN | - |
C4‑140517 | CS to PS SRVCC | NSN | - |
C4‑140518 | Wildcarded Public Identity in SAA | NSN | - |
C4‑140519 | UE Reachability for IP | NSN | - |
C4‑140520 | SGmb path failure | Ericsson | - |
C4‑140521 | Including CSG change reporting for Change Notification procedure | Ericsson | - |
C4‑140522 | Discussion on SGs path failure | Ericsson | - |
C4‑140523 | Enhancement on MSC initiated SGs restoration | Ericsson | - |
C4‑140524 | STa Authentication for Trusted WLAN access | ZTE, Ericsson, NSN, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | - |
C4‑140525 | Revised WID on CT aspects of Proximity-based Services (ProSe) | Qualcomm Incorporated | - |
C4‑140526 | Proximity-based Services (ProSe) CT4 impacts | Qualcomm Incorporated | - |
C4‑140527 | Addition of ProSe Application ID format | Qualcomm Incorporated | - |
C4‑140528 | Addition of ProSe Application Code format | Qualcomm Incorporated | - |
C4‑140529 | Pseudo-CR on Overload Control Information parameters & evaluation | NSN, Cisco, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Verizon | - |
C4‑140530 | Transparent container ambiguity | NSN | - |
C4‑140531 | Indirect Data Forwarding | NSN | - |
C4‑140532 | Indirect Data Forwarding | NSN | - |
C4‑140534 | Response LS on New version of ES 283 035 | 3GPP TSG CT WG1 | - |
C4‑140535 | LS on Registration of new TS 29.214 protocol identifiers in TS 29.230 | CT3 | - |
C4‑140536 | LS on PWS service restoration | CT | - |
C4‑140537 | Reply LS on system aspects for Small Cell Enhancement work in RAN | RAN2 | - |
C4‑140538 | LS on Core Network assisted eNodeB parameters tuning | RAN WG2 | - |
C4‑140539 | Reply LS on ULI reporting enhancements | RAN3 | - |
C4‑140540 | LS on agreed CRs for LTE-HRPD SON | RAN3 | - |
C4‑140541 | Reply LS on error handling in eMBMS | RAN3 | - |
C4‑140542 | Reply LS on system aspects for Small Cell Enhancement work in RAN | RAN3 | - |
C4‑140543 | Reply LS on CSFB priority call handling in a network supporting Multimedia Priority Service | SA2 | - |
C4‑140544 | LS on system aspects for Small Cell Enhancement work in RAN | SA2 | - |
C4‑140545 | LS on Maintenance of I-WLAN Solution | SA2 | - |
C4‑140546 | LS response on Roaming Forwarding of signalling for CS fall back | SA2 | - |
C4‑140547 | LS on GCSE QCIs and connected mode DRX | SA 2 | - |
C4‑140548 | MTC Device Identification for LI | SA3LI | - |
C4‑140549 | Reply LS on Maintenance of I-WLAN Solution | TSG SA | - |
C4‑140550 | LS on contact persons and maintenance of 3GPP TS 29.234 | TSG SA | - |
C4‑140551 | Diameter overload control mechanism | Ericsson | - |
C4‑140552 | Retrieval of TWAN-Id over Sh | China Telecom, Huawei | - |
C4‑140553 | Retrieval of TWAN-Id over Sh | China Telecom, Huawei | - |
C4‑140554 | - | - | - |
C4‑140555 | Correction on XML Schema for IMS CAMEL Services | Huawei | - |
C4‑140556 | Pseudo-CR on Conclusions on frequency of inclusion of overload control | Huawei, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Cisco | - |
C4‑140557 | Pseudo-CR on Conclusions on frequency of inclusion of load control | Huawei, Cisco, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | - |
C4‑140558 | Pseudo-CR on Extension to Solution B | Huawei, NEC, NTT DOCOMO, NTC, HiSilicon | - |
C4‑140559 | Discussion on Comparison of Sol-B and Sol-D | Huawei, NTT DOCOMO, NEC, NTC, HiSilicon | - |
C4‑140560 | Pseudo-CR on Comparison and Conclusion | Huawei, NEC, NTT DOCOMO, NTC, HiSilicon | - |
C4‑140561 | Pseudo-CR on Editor’s Notes with Solution B | Huawei, HiSilicon | - |
C4‑140562 | Pseudo-CR on Existing Mechanisms and Drawbacks | Huawei | - |
C4‑140563 | Pseudo-CR on Alternative Solutions | Huawei | - |
C4‑140564 | Pseudo-CR on Recommendation and Conclusion | Huawei | - |
C4‑140565 | Protocol enhancements to indicate support of device recall and replace by SMS-SC | Huawei | - |
C4‑140566 | UE Initiated Connectivity to Additional PDN procedures | Huawei | - |
C4‑140567 | PCO in the HO to TWAN procedures | Huawei | - |
C4‑140568 | PCO in the HO to TWAN procedures | Huawei | - |
C4‑140569 | Encoding of the civic address | China Telecom, Huawei | - |
C4‑140570 | The civic address IE | China Telecom, Huawei | - |
C4‑140571 | Skeleton for TS 29.344 | Huawei | - |
C4‑140572 | Pseudo-CR on TS 29.344 scope | Huawei | - |
C4‑140573 | Spare bits in MM context | Huawei | - |
C4‑140574 | Temporarily rejected case for Create/Update Bearer Response | Huawei | - |
C4‑140575 | Modify Bearer Request with PDN Charging Pause Stop Indication | Huawei | - |
C4‑140576 | User CSG Information reporting in rollback case | Huawei | - |
C4‑140577 | Corrections to Node Type | Huawei | - |
C4‑140578 | Update the condition of TimeZone IE | Huawei | - |
C4‑140579 | IMSI for BBF convergence | Huawei | - |
C4‑140580 | Reflective QoS in BBF architecture | Huawei | - |
C4‑140581 | PGW triggered SGW restoration on S5 path failure | Huawei | - |
C4‑140582 | PGW triggered SGW restoration on S5 path failure | Huawei | - |
C4‑140583 | Exteneded priority is missing in UML model | Huawei | - |
C4‑140584 | Exteneded priority is missing in UML model | Huawei | - |
C4‑140585 | Pseudo-CR on Diameter overload over S6a/d | Alcatel-Lucent | - |
C4‑140586 | Diameter overload over S6a/d | Alcatel-Lucent | - |
C4‑140587 | Adding Codes for 29.214 | NSN | - |
C4‑140588 | Adding Codes for 29.214 | NSN | - |
C4‑140589 | Adding Codes for 29.214 | NSN | - |
C4‑140590 | Adding Codes for 29.214 | NSN | - |
C4‑140591 | Adding Codes for 29.214 | NSN | - |
C4‑140592 | Fix inconsistency with 3GPP2 based PDN disconnection procedure | NEC | - |
C4‑140593 | Fix inconsistency with 3GPP2 based PDN disconnection procedure | NEC | - |
C4‑140596 | DISC on CLUE handling in MRF for IMS telepresence | Huawei | - |
C4‑140597 | Pseudo-CR on e2ae media security: Iq procedures for UDP-based media using TLS | Ericsson | - |
C4‑140598 | Pseudo-CR on Indication of covered annex B - SA3 requirements | Ericsson | - |
C4‑140599 | Cleanup the pre-Release-8 DNS procedure on Release-8 SGSN | NTT DOCOMO, NTC | - |
C4‑140600 | Cleanup the pre-Release-8 DNS procedure on Release-8 SGSN | NTT DOCOMO, NTC | - |
C4‑140601 | Cleanup the pre-Release-8 DNS procedure on Release-8 SGSN | NTT DOCOMO, NTC | - |
C4‑140602 | Cleanup the pre-Release-8 DNS procedure on Release-8 SGSN | NTT DOCOMO, NTC | - |
C4‑140603 | Cleanup the pre-Release-8 DNS procedure on Release-8 SGSN | NTT DOCOMO, NTC | - |
C4‑140604 | Pseudo-CR on Conclusion on the support of APN level load control feature | Cisco | - |
C4‑140605 | [DRAFT] LS on Progress of GTP-C Overload Control mechanism | CT4 | - |
C4‑140606 | SS-Status AVP definition | Ericsson | - |
C4‑140607 | SS-Status AVP definition | Ericsson | - |
C4‑140608 | Consistency of ICS Indicator | Ericsson | - |
C4‑140609 | Consistency of ICS Indicator | Ericsson | - |
C4‑140610 | Proposal to support ICE Lite | NSN | - |
C4‑140611 | Support for Interactive Connectivity Establishment (ICE) | NSN | - |
C4‑140612 | Support for Interactive Connectivity Establishment (ICE) | NSN | - |
C4‑140613 | Pseudo-CR on E2e security procedures for TCP-based media using TLS | NSN | - |
C4‑140615 | Discussion Paper on Civic Address Encoding for Netloc-TWLAN | Ericsson | - |
C4‑140616 | Civic Address Encoding | Ericsson | - |
C4‑140617 | Definition of AVPs for Network Location in TWLAN | Ericsson | - |
C4‑140618 | Error mapping for "Data Missing" | Ericsson | - |
C4‑140619 | Functional requirements clarification of "stage 2" convention | Alcatel-Lucent | - |
C4‑140620 | Diameter Overload Control | Orange | - |
C4‑140621 | Pseudo-CR on Removal of Editor's notes | Orange | - |
C4‑140622 | Pseudo-CR on Update of the section 6.5 "3GPP-IETF Requirements Gap Analysis" | Orange | - |
C4‑140623 | Pseudo-CR on Completion of the TR | Orange | - |
C4‑140624 | Pseudo-CR on Skeleton | Orange | - |
C4‑140629 | Authorized media capabilities per Service Id | Orange | - |
C4‑140630 | - | - | - |
C4‑140631 | PGW Back-off Time | NSN | - |
C4‑140632 | Aligning Mandatory Feature with stage 2 | NSN | - |
C4‑140633 | Aligning Mandatory Features with stage 2 | NSN | - |
C4‑140634 | Aligning Mandatory Features with stage 2 | NSN | - |
C4‑140635 | Extension to the TWAN Identifier contents: new Line Identifier (Logical Access ID) | Orange | - |
C4‑140636 | Extension to the ANI Option IE / TWAN Identifier contents: new Line Identifier (Logical Access ID) | Orange | - |
C4‑140637 | Add a Cause Value in case MME refuses to setup/modify a bearer | Orange | - |
C4‑140638 | Pseudo-CR on Diameter overload control mechanism impacts on existing 3GPP applications | Ericsson | - |
C4‑140639 | Handling of error scenarios on trigger replace | Huawei | - |
C4‑140640 | New WID on CT aspects of Group Communication System Enablers for LTE | NSN | - |
C4‑140641 | Pseudo-CR on Comparison and Conclusion | NTT DOCOMO, NTT, Deutsche Telekom, Huawei, NEC, NTC, Oki Electronics, HiSilicon, Hitachi, Fujitsu | - |
C4‑140642 | Reply LS on new work item on "IMS support for RTP / RTCP transport multiplexing" | 3GPP SA WG2 | - |
C4‑140643 | Correction of MME/SGSN Behaviour when ODB is not supported | NTT DOCOMO | - |
C4‑140644 | Correction of MME/SGSN Behaviour when ODB is not supported | NTT DOCOMO | - |
C4‑140645 | Correction of MME/SGSN Behaviour when ODB is not supported | NTT DOCOMO | - |
C4‑140646 | Correction of MME/SGSN Behaviour when ODB is not supported | NTT DOCOMO | - |
C4‑140647 | Correction of MME/SGSN Behaviour when ODB is not supported | NTT DOCOMO | - |
C4‑140648 | LS on the problem of UE Radio Capability information size | SA2 | - |
C4‑140649 | - | - | - |
C4‑140650 | LS on device trigger recall and replace support | SA2 | - |
C4‑140651 | Reply LS on Overload Control for WLAN accesses | SA2 | - |
C4‑140652 | LS on eMBMS broadcast areas with EUTRAN Cell Granularity | SA2 | - |
C4‑140653 | Reply LS on Charging aspects for Network Sharing (MOCN GWCN) | SA2 | - |
C4‑140654 | [DRAFT] Reply LS on GCSE QCIs and connected mode DRX | 3GPP TSG CT4 | - |
C4‑140655 | [DRAFT] LS on Reply LS on MTC Device Identification for LI | 3GPP TSG CT4 | - |
C4‑140656 | Diameter Overload Control | Orange | - |
C4‑140657 | New WID on CT aspects of Group Communication System Enablers for LTE | NSN | - |
C4‑140658 | STa Authentication for Trusted WLAN access | ZTE, Ericsson, NSN, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | - |
C4‑140659 | UE Initiated Connectivity to Additional PDN procedures | Huawei | - |
C4‑140660 | Pseudo-CR on e2ae media security – Iq procedures for TCP-based media | Alcatel-Lucent | - |
C4‑140661 | Protocol enhancements to indicate support of device recall and replace by SMS-SC | Huawei | - |
C4‑140662 | Handling of error scenarios on trigger replace | Huawei | - |
C4‑140663 | Pseudo-CR on Requirements for Scopes and Report Types | NSN | - |
C4‑140664 | Pseudo-CR on Diameter overload over S6a/d | Alcatel-Lucent | - |
C4‑140665 | Pseudo-CR on Extension to Solution B | Huawei, NEC, NTT DOCOMO, NTC, HiSilicon | - |
C4‑140666 | Pseudo-CR on Editor’s Notes with Solution B | Huawei, HiSilicon | - |
C4‑140667 | - | - | - |
C4‑140668 | Pseudo-CR on Existing Mechanisms and Drawbacks | Huawei | - |
C4‑140669 | Pseudo-CR on Alternative Solutions | Huawei | - |
C4‑140670 | Correction on XML Schema for IMS CAMEL Services | Huawei | - |
C4‑140671 | Revised WID on CT aspects of Proximity-based Services (ProSe) | Qualcomm Incorporated | - |
C4‑140672 | Addition of ProSe Application ID format | Qualcomm Incorporated | - |
C4‑140673 | Addition of ProSe Application Code format | Qualcomm Incorporated | - |
C4‑140674 | Retrieval of TWAN-Id over Sh | China Telecom, Huawei | - |
C4‑140675 | Private User Identity retrieval | NSN | - |
C4‑140676 | Wildcarded Public Identity in SAA | NSN | - |
C4‑140677 | Retrieval of TWAN-Id over Sh | China Telecom, Huawei | - |
C4‑140678 | Authorized media capabilities per Service Id | Orange | - |
C4‑140679 | IP-SM-GW address handling clarification | NSN | - |
C4‑140680 | IP-SM-GW address handling clarification | NSN | - |
C4‑140681 | Exteneded priority is missing in UML model | Huawei | - |
C4‑140682 | Exteneded priority is missing in UML model | Huawei | - |
C4‑140683 | SS-Status AVP definition | Ericsson | - |
C4‑140684 | SS-Status AVP definition | Ericsson | - |
C4‑140685 | SS-Status AVP definition | Ericsson | - |
C4‑140686 | SS-Status AVP definition | Ericsson | - |
C4‑140687 | SS-Status AVP definition | Ericsson | - |
C4‑140688 | SS-Status AVP definition | Ericsson | - |
C4‑140689 | SS-Status AVP definition | Ericsson | - |
C4‑140690 | SS-Status AVP definition | Ericsson | - |
C4‑140691 | SS-Status AVP definition | Ericsson | - |
C4‑140692 | SS-Status AVP definition | Ericsson | - |
C4‑140693 | Pseudo-CR on Diameter overload control mechanism considerations on existing 3GPP applications | Ericsson | - |
C4‑140694 | IMSI for BBF convergence | Huawei | - |
C4‑140695 | Reflective QoS in BBF architecture | Huawei | - |
C4‑140696 | CS to PS SRVCC | NSN | - |
C4‑140697 | CS to PS SRVCC | NSN | - |
C4‑140698 | Diameter overload control mechanism | Ericsson | - |
C4‑140699 | LS on inconsistency with 3GPP2 based PDN disconnection procedure | 3GPP TSG CT4 | - |
C4‑140700 | Adding Codes for 29.214 | NSN | - |
C4‑140701 | Diameter overload control mechanism | Ericsson | - |
C4‑140703 | Pseudo-CR on Diameter overload over S6a/d | Alcatel-Lucent | - |
C4‑140704 | Pseudo-CR on Diameter overload control mechanism considerations on existing 3GPP applications | Ericsson | - |
C4‑140705 | Pseudo-CR on Skeleton | Orange | - |
C4‑140706 | Skeleton for TS 29.344 | Huawei | - |
C4‑140707 | Pseudo-CR on TS 29.344 scope | Huawei | - |
C4‑140708 | Addition of ProSe Application ID format | Qualcomm Incorporated | - |
C4‑140709 | Addition of ProSe Application Code format | Qualcomm Incorporated | - |
C4‑140710 | Diameter overload control mechanism | Ericsson | - |
C4‑140712 | Consistency of ICS Indicator | Ericsson | - |
C4‑140713 | Reply LS on GCSE QCIs and connected mode DRX | C4 | - |
C4‑140714 | Reply LS on MTC Device Identification for LI | C4 | - |
C4‑140715 | LS on Possible Impacts on SIP for P-CSCF restoration | C4 | - |
C4‑140716 | ICE support in Ix interface | Huawei | - |
C4‑140717 | LS on inconsistency with 3GPP2 based PDN disconnection procedure | 3GPP TSG CT4 | - |
C4‑140718 | Diameter Overload Control | Orange | - |
C4‑140719 | - | - | - |
C4‑140720 | Pseudo-CR on Extension to Solution B | Huawei, NEC, NTT DOCOMO, NTC, HiSilicon | - |
C4‑140721 | Pseudo-CR on Editor’s Notes with Solution B | Huawei, HiSilicon | - |
C4‑140722 | - | - | - |
C4‑140723 | Pseudo-CR on Alternative Solutions | Huawei | - |
C4‑140724 | Pseudo-CR on Diameter overload over S6a/d | Alcatel-Lucent, Verizon | - |
C4‑140725 | Retrieval of TWAN-Id over Sh | China Telecom, Huawei | - |
C4‑140726 | - | - | - |
C4‑140727 | Private User Identity retrieval | NSN | - |
C4‑140728 | Wildcarded Public Identity in SAA | NSN | - |
C4‑140729 | Consistency of ICS Indicator | Ericsson | - |
C4‑140730 | LS on inconsistency with 3GPP2 based PDN disconnection procedure | C4 | - |
C4‑140731 | Pseudo-CR on e2e media security – Iq & Ix procedures for TCP-based media | Alcatel-Lucent, NSN | - |
C4‑140732 | HeNB ID verification in the PWS Restart Indication message | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Huawei, one2many, AT&T, NEC | - |
C4‑140733 | Handling of E-RAB Release due to GTPU error indication for default bearer at MME | Cisco | - |
C4‑140734 | SGmb path failure recovery | one2many, Alcatel-Lucent, ALU Shanghai Bell, Ericsson, Huawei | - |
C4‑140735 | MBMS session re-establishment with modified M1 IP multicast addresses | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | - |
C4‑140736 | Sm path failure recovery | one2many, Alcatel-Lucent, ALU Shanghai Bell | - |
C4‑140737 | SGmb path failure | Ericsson | - |
C4‑140738 | Introduction of SGSN Number, SGSN Lgd Identifier and MME SLg identifier | Cisco | - |
C4‑140739 | Number of authentication vectors in the MM Context IE | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | - |
C4‑140740 | Number of authentication vectors in the MM Context IE | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | - |
C4‑140742 | TWAN Identifier Timestamp in PDN disconnection procedure | Cisco | - |
C4‑140743 | TWAN ID Timestamp in Bearer Revocation Ack message for PGW initiated bearer deactivation procedure in Trusted WLAN | Cisco | - |
C4‑140744 | UE Time Zone for PMIP | Cisco | - |
C4‑140745 | TWAN Identifier Timestamp for PMIP | Cisco | - |
C4‑140746 | TWAN Identifier Timestamp | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | - |
C4‑140747 | Encoding of the civic address | China Telecom, Huawei | - |
C4‑140748 | Pseudo-CR on Conclusion on definition of Load Control Information | Cisco, Ericsson, Verizon, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Huawei | - |
C4‑140749 | Pseudo-CR on Conclusion on interaction between Load Control Info and information received from DNS | Cisco, Ericsson, Verizon, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Huawei | - |
C4‑140750 | Pseudo-CR on Conclusion on message throttling algorithm | Cisco, Ericsson, Verizon, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Huawei | - |
C4‑140751 | Pseudo-CR on Description and conclusion on message prioritization based on procedure | Cisco | - |
C4‑140752 | Pseudo-CR on Summary of conclusion in clause 9 | Cisco, Ericsson, Verizon, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | - |
C4‑140753 | Information on the Progress of the GTP-C Overload Control Mechanism workitem | Cisco | - |
C4‑140754 | Skeleton for capturing various aspects of GTP-C overload control solution | Cisco | - |
C4‑140755 | Support for Interactive Connectivity Establishment (ICE) | NSN | - |
C4‑140756 | e2e media security for TCP-based media using TLS Functional requirements | Alcatel-Lucent | - |
C4‑140758 | - | - | - |
C4‑140759 | Pseudo-CR on e2ae media security: Iq procedures for UDP-based media using TLS | Ericsson | - |
C4‑140760 | Pseudo-CR on Conclusions on the applicable non-3GPP access interfaces for overload control | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Verizon | - |
C4‑140761 | Pseudo-CR on Overload Control Information parameters & evaluation | NSN, Cisco, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Verizon, KDDI | - |
C4‑140762 | Pseudo-CR on Conclusions on frequency of inclusion of overload control | Huawei, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Cisco | - |
C4‑140763 | Pseudo-CR on Conclusions on frequency of inclusion of load control | Huawei, Cisco, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | - |
C4‑140764 | Pseudo-CR on Conclusion on the support of APN level load control feature | Cisco | - |
C4‑140765 | Skeleton for capturing various aspects of GTP-C overload control solution | Cisco | - |
C4‑140766 | - | - | - |
C4‑140767 | Reporting changes of UE presence in Presence Reporting Area | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | - |
C4‑140768 | Presence Reporting Area Action | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | - |
C4‑140769 | Alternate LMAA or IPv4-LMAA | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Cisco, NSN | - |
C4‑140770 | Alternate LMA address for user plane | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Cisco | - |
C4‑140771 | Context Response with P-TMSI Signature Mismatch | Alcatel-Lucent | - |
C4‑140772 | Context Response with P-TMSI Signature Mismatch | Alcatel-Lucent | - |
C4‑140773 | Update cause to indicate downlink message delivery failure due to crash with mobility event | ZTE, Huawei | - |
C4‑140774 | Including CSG change reporting for Change Notification procedure | Ericsson | - |
C4‑140775 | Functional requirements clarification of "stage 2" convention | Alcatel-Lucent | - |
C4‑140776 | Support of RTP transport multiplexing (Iq, stage 2) | Alcatel-Lucent | - |
C4‑140777 | - | - | - |
C4‑140778 | - | - | - |
C4‑140779 | Aligning Mandatory Features with stage 2 | NSN | - |
C4‑140780 | Cleanup the pre-Release-8 DNS procedure on Release-8 SGSN | NTT DOCOMO, NTC | - |
C4‑140781 | Cleanup the pre-Release-8 DNS procedure on Release-8 SGSN | NTT DOCOMO, NTC | - |
C4‑140782 | Cleanup the pre-Release-8 DNS procedure on Release-8 SGSN | NTT DOCOMO, NTC | - |
C4‑140783 | Cleanup the pre-Release-8 DNS procedure on Release-8 SGSN | NTT DOCOMO, NTC | - |
C4‑140784 | Cleanup the pre-Release-8 DNS procedure on Release-8 SGSN | NTT DOCOMO, NTC | - |
C4‑140785 | Extension to the TWAN Identifier contents: new Line Identifier (Logical Access ID) | Orange | - |
C4‑140786 | LS on SRVCC Handover to GERAN | CT4 | - |
C4‑140787 | Spare bits in MM context | Huawei | - |
C4‑140788 | Support for Interactive Connectivity Establishment (ICE) | NSN, Huawei | - |
C4‑140789 | LS on Charging Pause Stop indication | 3GPP TSG CT4 | - |
C4‑140790 | User CSG Information reporting in rollback case | Huawei | - |
C4‑140791 | Corrections to Node Type | MCC, Huawei | - |
C4‑140792 | Update the condition of TimeZone IE | Huawei | - |
C4‑140793 | MDT configuration during inter-MME handover | ZTE | - |
C4‑140794 | MDT configuration during inter-MME handover | ZTE | - |
C4‑140795 | Error mapping for "Data Missing" | Ericsson | - |
C4‑140796 | Add a Cause Value in case MME refuses to setup/modify a bearer | Orange | - |
C4‑140797 | - | - | - |
C4‑140798 | Pseudo-CR on Conclusion on interaction between Load Control Info and information received from DNS | Cisco, Ericsson, Verizon, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Huawei | - |
C4‑140799 | Pseudo-CR on Summary of conclusion in clause 9 | Cisco, Ericsson, Verizon, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | - |
C4‑140800 | Skeleton for capturing various aspects of GTP-C overload control solution | Cisco | - |
C4‑140801 | Pseudo-CR on Overload Control Information parameters & evaluation | NSN, Cisco, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Verizon, KDDI | - |
C4‑140802 | Pseudo-CR on Conclusions on frequency of inclusion of overload control | Huawei, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Cisco | - |
C4‑140803 | Pseudo-CR on Conclusions on frequency of inclusion of load control | Huawei, Cisco, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | - |
C4‑140804 | IMSI for BBF convergence | Huawei, NSN | - |
C4‑140805 | UE Initiated Connectivity to Additional PDN procedures | Huawei | - |
C4‑140806 | Pseudo-CR on Conclusion on definition of Load Control Information | Cisco, Ericsson, Verizon, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Huawei | - |
C4‑140807 | - | - | - |
C4‑140808 | MDT configuration during inter-MME handover | ZTE | - |
C4‑140809 | MDT configuration during inter-MME handover | ZTE | - |
C4‑140810 | TWAN Identifier Timestamp in PDN disconnection procedure | Cisco | - |
C4‑140811 | TWAN ID Timestamp in Bearer Revocation Ack message for PGW initiated bearer deactivation procedure in Trusted WLAN | Cisco | - |
C4‑140812 | Encoding of the civic address | China Telecom, Huawei | - |
C4‑140813 | Extension to the TWAN Identifier contents: new Line Identifier (Logical Access ID) | Orange | - |
C4‑140814 | IMSI for BBF convergence | Huawei, NSN | - |
C4‑140815 | IP-SM-GW address handling clarification | NSN | - |
C4‑140816 | IP-SM-GW address handling clarification | NSN | - |
C4‑140817 | Diameter Overload Control | Orange | - |
C4‑140818 | Handling of error scenarios on trigger replace | Huawei | - |
C4‑140819 | Retrieval of TWAN-Id over Sh | China Telecom, Huawei | - |
C4‑140820 | List of Output Documents | Chairman, TSG-CT WG4 | - |
page generated from database: 2024-04-22 07:58:53