3GPP TDocs (written contributions) at meeting
Meeting: C1-46 - 2007-03-26 to 2007-03-30, Warsaw
meeting id: C1-46 (click id for more info on this meeting)Click on the Tdoc to open its file.
| TDoc | Title | Source | Remarks |
|---|---|---|---|
| C1‑070645 | Title | Source | - |
| C1‑070646 | - after radio and terrestrial resources for the group call channel have been released but the group call is ongoing – subject to certain conditions | Nortel | - |
| C1‑070647 | - after radio and terrestrial resources for the group call channel have been released but the group call is ongoing – subject to certain conditions | Nortel | - |
| C1‑070648 | - after radio and terrestrial resources for the broadcast call channel have been released but the broadcast call is ongoing – subject to certain conditions | Nortel | - |
| C1‑070649 | CR to TR 24.801: SAE/LTE Bearer concept | Ericsson | - |
| C1‑070650 | CR to 24.801: SAE/LTE Bearer level QoS parameters | Ericsson | - |
| C1‑070651 | CR to 24.801: SAE/LTE Authentication | Ericsson | - |
| C1‑070652 | CR to 24.801: SAE/LTE Security key handling | Ericsson | - |
| C1‑070653 | CR to 24.801: Mobility management and Session management for SAE/LTE | Ericsson | - |
| C1‑070654 | Disabling of emergency calls provedures over IMS | - | - |
| C1‑070655 | CR against TS 23.259 – Clause 2 References | Vodafone | - |
| C1‑070656 | CR against TS 23.259 – Clause 3 Definitions and Abbreviations | Vodafone | - |
| C1‑070657 | CR against TS 23.259 – Clause 4 PNM overview | Vodafone | - |
| C1‑070658 | CR against TS 23.259 – Clause 5 Procedures and Information Flows for UE Redirection Service (5/5.1) | Vodafone | - |
| C1‑070659 | CR against TS 23.259 – Clause 5 Procedures and Information Flows for UE Redirection Service (5.2) | Vodafone | - |
| C1‑070660 | CR against TS 23.259 – Clause 6.1 | Vodafone | - |
| C1‑070661 | CR against TS 23.259 – Clause 6 tidy-up | Vodafone | - |
| C1‑070662 | One or more organizations (3GPP Individual Members) which drafted the CR and are presenting it to the Working Group. | Siemens Networks, Nokia | - |
| C1‑070663 | h)the Security-Client header field set to specify the security mechanism the UE supports, the IPsec layer algorithms the UE supports and the parameters needed for the security association setup. The UE shall support the setup of two pairs of security | Siemens Networks, Nokia | - |
| C1‑070664 | One or more organizations (3GPP Individual Members) which drafted the CR and are presenting it to the Working Group. | Siemens Networks, Nokia | - |
| C1‑070665 | One or more organizations (3GPP Individual Members) which drafted the CR and are presenting it to the Working Group. | Siemens Networks, Nokia | - |
| C1‑070666 | h)the Security-Client header field set to specify the security mechanism the UE supports, the IPsec layer algorithms the UE supports and the parameters needed for the security association setup. The UE shall support the setup of two pairs of security | Siemens Networks, CableLabs | - |
| C1‑070667 | One or more organizations (3GPP Individual Members) which drafted the CR and are presenting it to the Working Group. | LM Ericsson | - |
| C1‑070668 | Clarification of the handling of ICSI | - | - |
| C1‑070669 | One or more organizations (3GPP Individual Members) which drafted the CR and are presenting it to the Working Group. | LM Ericsson | - |
| C1‑070670 | One or more organizations (3GPP Individual Members) which drafted the CR and are presenting it to the Working Group. | LM Ericsson | - |
| C1‑070671 | One or more organizations (3GPP Individual Members) which drafted the CR and are presenting it to the Working Group. | LM Ericsson | - |
| C1‑070673 | One or more organizations (3GPP Individual Members) which drafted the CR and are presenting it to the Working Group. | LM Ericsson | - |
| C1‑070674 | One or more organizations (3GPP Individual Members) which drafted the CR and are presenting it to the Working Group. | LM Ericsson | - |
| C1‑070675 | One or more organizations (3GPP Individual Members) which drafted the CR and are presenting it to the Working Group. | LM Ericsson | - |
| C1‑070676 | One or more organizations (3GPP Individual Members) which drafted the CR and are presenting it to the Working Group. | LM Ericsson | - |
| C1‑070677 | One or more organizations (3GPP Individual Members) which drafted the CR and are presenting it to the Working Group. | LM Ericsson | - |
| C1‑070678 | One or more organizations (3GPP Individual Members) which drafted the CR and are presenting it to the Working Group. | LM Ericsson | - |
| C1‑070679 | One or more organizations (3GPP Individual Members) which drafted the CR and are presenting it to the Working Group. | LM Ericsson | - |
| C1‑070680 | - | - | - |
| C1‑070681 | Dynamic Service Activation Info | - | - |
| C1‑070682 | TCRT: Silent (re-)joining dipatcher, immediately talking dispatcher | Siemens Networks, Nortel Networks // C1 | - |
| C1‑070683 | TCRT: Silent (re-)joining dipatcher, immediately talking dispatcher | Siemens Networks, Nortel Networks // C1 | - |
| C1‑070684 | TCRT: Definition of BSSAP procedure for release of VGCS call controlling connections | Nortel, Siemens Networks | - |
| C1‑070685 | One or more organizations (3GPP Individual Members) which drafted the CR and are presenting it to the Working Group. | Siemens Networks | - |
| C1‑070686 | One or more organizations (3GPP Individual Members) which drafted the CR and are presenting it to the Working Group. | Siemens Networks | - |
| C1‑070687 | Increase of the maximum bitrate and guaranteed bit rate in the QoS IE | - | - |
| C1‑070688 | - | - | - |
| C1‑070689 | - | - | - |
| C1‑070690 | Emergency indication in QoS IE | - | - |
| C1‑070691 | Alignment between VBS and VGCS call establishment | - | - |
| C1‑070692 | One or more organizations (3GPP Individual Members) which drafted the CR and are presenting it to the Working Group. | Alcatel-Lucent | - |
| C1‑070693 | One or more organizations (3GPP Individual Members) which drafted the CR and are presenting it to the Working Group. | Alcatel-Lucent | - |
| C1‑070694 | One or more organizations (3GPP Individual Members) which drafted the CR and are presenting it to the Working Group. | Alcatel-Lucent | - |
| C1‑070695 | One or more organizations (3GPP Individual Members) which drafted the CR and are presenting it to the Working Group. | Alcatel-Lucent | - |
| C1‑070696 | One or more organizations (3GPP Individual Members) which drafted the CR and are presenting it to the Working Group. | Alcatel-Lucent | - |
| C1‑070697 | One or more organizations (3GPP Individual Members) which drafted the CR and are presenting it to the Working Group. | Alcatel-Lucent | - |
| C1‑070698 | One or more organizations (3GPP Individual Members) which drafted the CR and are presenting it to the Working Group. | Alcatel-Lucent | - |
| C1‑070699 | One or more organizations (3GPP Individual Members) which drafted the CR and are presenting it to the Working Group. | Alcatel-Lucent | - |
| C1‑070700 | One or more organizations (3GPP Individual Members) which drafted the CR and are presenting it to the Working Group. | Alcatel-Lucent | - |
| C1‑070701 | One or more organizations (3GPP Individual Members) which drafted the CR and are presenting it to the Working Group. | Alcatel-Lucent | - |
| C1‑070702 | One or more organizations (3GPP Individual Members) which drafted the CR and are presenting it to the Working Group. | Alcatel-Lucent | - |
| C1‑070703 | Discussion Document on GRUUs for AS’s acting on behalf of a Public User Identity. | CableLabs | - |
| C1‑070704 | One or more organizations (3GPP Individual Members) which drafted the CR and are presenting it to the Working Group. | Cablelabs | - |
| C1‑070705 | One or more organizations (3GPP Individual Members) which drafted the CR and are presenting it to the Working Group. | CableLabs | - |
| C1‑070706 | Discussion of Number Portability and Carrier Routing | CableLabs | - |
| C1‑070707 | Enhancements to Support Preferred Circuit Carrier Access and Dial-Around for Cable Networks | - | - |
| C1‑070708 | IMS Enhancements to Support Number Portability (NP) for Cable Networks | - | - |
| C1‑070709 | One or more organizations (3GPP Individual Members) which drafted the CR and are presenting it to the Working Group. | CableLabs | - |
| C1‑070710 | One or more organizations (3GPP Individual Members) which drafted the CR and are presenting it to the Working Group. | CableLabs | - |
| C1‑070711 | One or more organizations (3GPP Individual Members) which drafted the CR and are presenting it to the Working Group. | Siemens Networks, Nokia | - |
| C1‑070712 | IMS Communication Service Identifier (ICSI) | Qualcomm Japan | - |
| C1‑070713 | IMS Communication Service Identifier | - | - |
| C1‑070714 | NOTE 3:The SIP AS that implements the DTF acting as a B2BUA - which performs the third-party call control - needs to be the last located application server to ensure that all application servers that need to remain in the path of a call after domain | Qualcomm Japan | - |
| C1‑070715 | One or more organizations (3GPP Individual Members) which drafted the CR and are presenting it to the Working Group. | Qualcomm Japan | - |
| C1‑070716 | Corrections to HOLD with annoucement | - | - |
| C1‑070717 | Study: Private network implementation in IMS | Panasonic Mobile Communications | - |
| C1‑070718 | CR against TS 23.259 – Clause 6.5: Access List configuration | Panasonic Mobile Communications | - |
| C1‑070719 | CR against TS 23.259 – Clause 7: Procedures and Information Flows for Private Network Services | Panasonic Mobile Communications | - |
| C1‑070720 | One or more organizations (3GPP Individual Members) which drafted the CR and are presenting it to the Working Group. | ZTE | - |
| C1‑070721 | Extension of Original Dialog Identifier | ZTE | - |
| C1‑070722 | One or more organizations (3GPP Individual Members) which drafted the CR and are presenting it to the Working Group. | ZTE | - |
| C1‑070723 | Modification of the conference ability of MGCF | - | - |
| C1‑070724 | LS on a new IMTC IMS Activity Group | IMTC IMS Activity Group | - |
| C1‑070725 | Reply LS to “LS on protected MBMS services over MBMS broadcast" | CT3 | - |
| C1‑070726 | LS on SIP Forking | CT3 | - |
| C1‑070727 | LS on Location Of Floor Control Server | CT4 | - |
| C1‑070728 | LS on Check of TS 23.333 Specification and MRFC/AS Requirements | CT4 | - |
| C1‑070729 | Clarification on ISDN address string request | CT6 | - |
| C1‑070730 | Reply LS on security for PS emergency sessions | SA3 | - |
| C1‑070731 | LS on Continuity of IMS Services | SA2 | - |
| C1‑070732 | LS on “Specification Update of GBR and MBR due to MIMO” | RAN3 | - |
| C1‑070733 | LS on Radio Access Network Sharing in SAE/LTE | RAN3 | - |
| C1‑070734 | LS on NAS signalling for E-UTRAN | RAN2 | - |
| C1‑070735 | LS on Maximum SDU size | TSG RAN WG2 | - |
| C1‑070736 | LS on PingPong problem in case of search for higher priority PLMN | RAN2 | - |
| C1‑070737 | LS on RRC connected mode during MBMS enhanced broadcast | RAN WG2 | - |
| C1‑070738 | Reply LS on Registration in Densely-populated area | RAN2 | - |
| C1‑070739 | - | - | - |
| C1‑070740 | - | - | - |
| C1‑070741 | LS on GERAN – LTE interworking | TSG GERAN | - |
| C1‑070742 | LS on feasibility of GAN enhancements | 3GPP TSG GERAN | - |
| C1‑070743 | LS on Flexible Timeslot Assignment support indication | GERAN | - |
| C1‑070744 | LS on Introduction of Latency Reduction capabilities | GERAN | - |
| C1‑070745 | One or more organizations (3GPP Individual Members) which drafted the CR and are presenting it to the Working Group. | Ericsson | - |
| C1‑070746 | Corrections to example flows | - | - |
| C1‑070747 | One or more organizations (3GPP Individual Members) which drafted the CR and are presenting it to the Working Group. | Ericsson | - |
| C1‑070748 | One or more organizations (3GPP Individual Members) which drafted the CR and are presenting it to the Working Group. | Ericsson | - |
| C1‑070749 | One or more organizations (3GPP Individual Members) which drafted the CR and are presenting it to the Working Group. | Ericsson | - |
| C1‑070750 | TR, Current Reference Version 3GPP TR 24.880 | Hewlett-Packard | - |
| C1‑070751 | Discussion, SCXML description | Hewlett-Packard | - |
| C1‑070752 | Discussion, SIP Control Framework and packages description | Hewlett-Packard | - |
| C1‑070753 | One or more organizations (3GPP Individual Members) which drafted the CR and are presenting it to the Working Group. | IAEI | - |
| C1‑070754 | One or more organizations (3GPP Individual Members) which drafted the CR and are presenting it to the Working Group. | IAEI | - |
| C1‑070755 | Correction of place of message flows for EVA | Siemens Networks | - |
| C1‑070757 | One or more organizations (3GPP Individual Members) which drafted the CR and are presenting it to the Working Group. | CableLabs | - |
| C1‑070758 | Support of Emergency Public User Tel URIs | QUALCOMM Europe | - |
| C1‑070759 | One or more organizations (3GPP Individual Members) which drafted the CR and are presenting it to the Working Group. | QUALCOMM Europe | - |
| C1‑070760 | One or more organizations (3GPP Individual Members) which drafted the CR and are presenting it to the Working Group. | QUALCOMM Europe | - |
| C1‑070761 | One or more organizations (3GPP Individual Members) which drafted the CR and are presenting it to the Working Group. | QUALCOMM Europe | - |
| C1‑070762 | One or more organizations (3GPP Individual Members) which drafted the CR and are presenting it to the Working Group. | Samsung, Vodafone | - |
| C1‑070763 | One or more organizations (3GPP Individual Members) which drafted the CR and are presenting it to the Working Group. | Samsung | - |
| C1‑070764 | One or more organizations (3GPP Individual Members) which drafted the CR and are presenting it to the Working Group. | Samsung | - |
| C1‑070765 | One or more organizations (3GPP Individual Members) which drafted the CR and are presenting it to the Working Group. | Samsung | - |
| C1‑070766 | One or more organizations (3GPP Individual Members) which drafted the CR and are presenting it to the Working Group. | Samsung | - |
| C1‑070767 | One or more organizations (3GPP Individual Members) which drafted the CR and are presenting it to the Working Group. | Samsung | - |
| C1‑070768 | 1)If a 181 (Call Is Being Forwarded) response is received indicating call is being forwarded, the CSI AS shall take further implementation specific actions which may be based on local policy. Such implementation specific actions are not specified in | Samsung | - |
| C1‑070769 | One or more organizations (3GPP Individual Members) which drafted the CR and are presenting it to the Working Group. | Samsung | - |
| C1‑070770 | Inclusion of addressing an amplification vulnerability in session initiation protocol forking proxies (draft-ietf-sip-fork-loop-fix) in the SIP profile | - | - |
| C1‑070771 | Inclusion of addressing an amplification vulnerability in session initiation protocol forking proxies (draft-ietf-sip-fork-loop-fix) in the SIP profile | - | - |
| C1‑070772 | Summary of current IETF documents on SIPPING | Alcatel-Lucent | - |
| C1‑070773 | Summary of current IETF documents on SIP | Alcatel-Lucent | - |
| C1‑070774 | Summary of current IETF documents on MMUSIC | Alcatel-Lucent | - |
| C1‑070775 | Summary of current IETF documents on SIMPLE | Alcatel-Lucent | - |
| C1‑070776 | Summary of current IETF documents on XCON | Alcatel-Lucent | - |
| C1‑070777 | Summary of current IETF documents on GEOPRIV | Alcatel-Lucent | - |
| C1‑070778 | Summary of current IETF documents on ECRIT | Alcatel-Lucent | - |
| C1‑070779 | Further alignment with phonebcp draft | Alcatel-Lucent / Keith Drage | - |
| C1‑070780 | Profile support for the P-Answer-State header extension to the session initiation protocol for the open mobile alliance push to talk over cellular (draft-allen-sipping-poc-p-answer-state-header) | - | - |
| C1‑070781 | Profile support for a session initiation protocol event package and data format for various settings in support for the push-to-talk over cellular service (RFC4354) | Alcatel-Lucent / Keith Drage | - |
| C1‑070782 | -if only one SIP dialog exists for the user identified in the P-Asserted-Identity and a 2xx response has been sent and there is active audio media, then continue the domain transfer procedures; | Alcatel-Lucent | - |
| C1‑070783 | NOTE 2:The final decision on the CAP message sent by the gsmSCF depends on the further service logic associated with the service key. | Alcatel-Lucent | - |
| C1‑070784 | One or more organizations (3GPP Individual Members) which drafted the CR and are presenting it to the Working Group. | Alcatel-Lucent | - |
| C1‑070785 | CR to 24.8bc: Impact on other specifications due to SAE | Alcatel-Lucent | - |
| C1‑070786 | Inclusion of extending the session initiation protocol Reason header for preemption events (RFC4411) in the SIP profile | - | - |
| C1‑070787 | Inclusion of communications resource priority for the session initiation protocol (RFC4412) in the SIP profile | - | - |
| C1‑070788 | Authentication to use the multimedia priority service | Alcatel-Lucent | - |
| C1‑070789 | Namespace usage in the multimedia priority service | Alcatel-Lucent | - |
| C1‑070790 | IMS functional entity support in the multimedia priority service | Alcatel-Lucent | - |
| C1‑070791 | Miscellaneous issues in using RFC 4412 in the multimedia priority service | Alcatel-Lucent | - |
| C1‑070792 | One or more organizations (3GPP Individual Members) which drafted the CR and are presenting it to the Working Group. | Source to WG:?[H9] | - |
| C1‑070795 | a)dialogs for which a 2xx response has not been sent are not considered; | Alcatel-Lucent | - |
| C1‑070796 | Correction for single slot DTM capability | - | - |
| C1‑070797 | a)dialogs for which a 2xx response has not been sent are not considered; | NEC | - |
| C1‑070798 | Adding a new media to a call after domain transfer to the IM CN subsystem | NEC | - |
| C1‑070799 | a)dialogs for which a 2xx response has not been sent are not considered; | NEC | - |
| C1‑070800 | CR 24.801: multi-TA registration in SAE | NEC | - |
| C1‑070801 | Endorsement of early media draft | Orange, Alcatel-Lucent, Ericsson // C1 | - |
| C1‑070802 | Correction of Routeing B2BUA and initiating B2BUA procedures to cover all possible AS routing scenarios documented at stage 2. | Orange // C1 | - |
| C1‑070803 | Report of new transit scenario documented in stage 2 | Orange // C1 | - |
| C1‑070804 | What is the age of consent? | Alcatel-Lucent | - |
| C1‑070806 | Adding RTSP Interface to the MRF Functional Unit | Alcatel-Lucent | - |
| C1‑070807 | In this example, when the VCC Application receives the indication that delivery of the terminating call through the selected IM CN subsystem cannot be completed, the VCC application performs an implementation option to attempt delivery of the termina | Alcatel-Lucent | - |
| C1‑070809 | One or more organizations (3GPP Individual Members) which drafted the CR and are presenting it to the Working Group. | Nokia, Siemens Networks | - |
| C1‑070810 | One or more organizations (3GPP Individual Members) which drafted the CR and are presenting it to the Working Group. | Nokia, Siemens Networks | - |
| C1‑070813 | One or more organizations (3GPP Individual Members) which drafted the CR and are presenting it to the Working Group. | Nokia, Siemens Networks | - |
| C1‑070814 | One or more organizations (3GPP Individual Members) which drafted the CR and are presenting it to the Working Group. | Nokia, Siemens Networks | - |
| C1‑070815 | Mobile Terminal Reporting of Network Performance | Vodafone Group | - |
| C1‑070816 | MS Reporting of Network Performance in the PS domain | - | - |
| C1‑070817 | MS Reporting of Network Performance in the CS domain | - | - |
| C1‑070818 | [DRAFT] LS on steering of roaming | CT1 | - |
| C1‑070819 | [DRAFT] LS on steering of roaming | CT1 | - |
| C1‑070820 | One or more organizations (3GPP Individual Members) which drafted the CR and are presenting it to the Working Group. | Vodafone | - |
| C1‑070821 | One or more organizations (3GPP Individual Members) which drafted the CR and are presenting it to the Working Group. | Source to TSG:?[H10] | - |
| C1‑070822 | One or more organizations (3GPP Individual Members) which drafted the CR and are presenting it to the Working Group. | Vodafone | - |
| C1‑070823 | One or more organizations (3GPP Individual Members) which drafted the CR and are presenting it to the Working Group. | Orange | - |
| C1‑070824 | Minor miscellaneous clean-up | Orange | - |
| C1‑070826 | Figure A.5.2-1: Terminating call directed to IM CN subsystem | Nortel | - |
| C1‑070827 | DISCUSSION: Additions to SAE task list for CT1 | Nortel, Samsung | - |
| C1‑070828 | Additional call flow for establishing a session when both endpoints do not need to reserve resources | - | - |
| C1‑070829 | One or more organizations (3GPP Individual Members) which drafted the CR and are presenting it to the Working Group. | Nortel | - |
| C1‑070830 | Discussion of Assignment of Temporary User Identity in SAE/LTE | Huawei | - |
| C1‑070831 | TR 24.801, CT1 open issues related to tracking area concept | Huawei | - |
| C1‑070832 | INFO, CT protocol aspects of non-3GPP accesses mobility management | Huawei | - |
| C1‑070833 | CR against TS 23.259 – Clause 6 Procedures and Information Flows for UE Deregistration | Huawei | - |
| C1‑070834 | CR against TS 23.259 – Clause 6.4 Procedures and Information Flows for Deactivation (6.4) | Huawei | - |
| C1‑070835 | 3)if the session is subject to anchoring, the DTF shall operate as an application server providing 3rd party call control, and specifically as a routeing B2BUA, as specified in subclause 5.7.5 of 3GPP TS 24.229 [8] for this request and all future req | Huawei | - |
| C1‑070836 | e)not all calls are suitable for domain transfer, and application of domain transfer to other calls might be against subscriber or operator preferences. 3GPP TS 22.101 [1] Clause 21 provides the requirements for this. Subclause 5.5 of the present doc | Huawei | - |
| C1‑070837 | One or more organizations (3GPP Individual Members) which drafted the CR and are presenting it to the Working Group. | Huawei | - |
| C1‑070838 | e)not all calls are suitable for domain transfer, and application of domain transfer to other calls might be against subscriber or operator preferences. 3GPP TS 22.101 [1] Clause 21 provides the requirements for this. Subclause 5.5 of the present doc | Huawei | - |
| C1‑070839 | NOTE 2:The final decision on the CAP message sent by the gsmSCF depends on the further service logic associated with the service key. | Huawei | - |
| C1‑070840 | One or more organizations (3GPP Individual Members) which drafted the CR and are presenting it to the Working Group. | Huawei | - |
| C1‑070841 | According to this stage3 description, if the DTF does not Record-Route on the requests of the calls without anchoring, then it will not get the final domain used by this session, and then it will lead that another incoming call anchored at the DTF ma | Huawei | - |
| C1‑070844 | Reply LS from SA3 to TISPAN on Co-existence between TISPAN and 3GPP Authentication Schemes | Huawei | - |
| C1‑070845 | One or more organizations (3GPP Individual Members) which drafted the CR and are presenting it to the Working Group. | Huawei | - |
| C1‑070846 | Location of Floor Control Server | Huawei | - |
| C1‑070847 | One or more organizations (3GPP Individual Members) which drafted the CR and are presenting it to the Working Group. | Huawei | - |
| C1‑070848 | Discussion on Alias Identities | Huawei | - |
| C1‑070850 | One or more organizations (3GPP Individual Members) which drafted the CR and are presenting it to the Working Group. | RIM | - |
| C1‑070851 | One or more organizations (3GPP Individual Members) which drafted the CR and are presenting it to the Working Group. | RIM | - |
| C1‑070852 | One or more organizations (3GPP Individual Members) which drafted the CR and are presenting it to the Working Group. | RIM | - |
| C1‑070853 | Cleanup of GRUU | - | - |
| C1‑070855 | One or more organizations (3GPP Individual Members) which drafted the CR and are presenting it to the Working Group. | RIM | - |
| C1‑070856 | IMS Communication Service ID 24.229 | - | - |
| C1‑070857 | One or more organizations (3GPP Individual Members) which drafted the CR and are presenting it to the Working Group. | Ericsson | - |
| C1‑070858 | Similarities between Cr and Mp | Ericsson | - |
| C1‑070859 | One or more organizations (3GPP Individual Members) which drafted the CR and are presenting it to the Working Group. | Huawei | - |
| C1‑070860 | Detailed procedures about session combining | - | - |
| C1‑070861 | LS from STF304 on “AT Commands for Assistive Mobile Device Interfaces” | STF 304 on AT Commands for Assistive Mobile Device Interfaces | - |
| C1‑070862 | Introduction and overview of STF 304 on "ATCommands for Assistive Mobile Device Interfaces" | STF 304 on AT Commands for Assistive Mobile Device Interfaces | - |
| C1‑070863 | Draft TS 102 511, Human Factors (HF); AT Commands for Assistive Mobile Device Interfaces | STF 304 on AT Commands for Assistive Mobile Device Interfaces | - |
| C1‑070864 | One or more organizations (3GPP Individual Members) which drafted the CR and are presenting it to the Working Group. | Alcatel-Lucent | - |
| C1‑070865 | One or more organizations (3GPP Individual Members) which drafted the CR and are presenting it to the Working Group. | Alcatel-Lucent | - |
| C1‑070866 | Profiling IMS inter-operator service interconnection interface and relation with ITU-T | Telecom Italia | - |
| C1‑070867 | Indication of Flexible Timeslot Assignment support | GERAN | - |
| C1‑070868 | Introduction of Latency Reduction capabilities | - | - |
| C1‑070869 | One or more organizations (3GPP Individual Members) which drafted the CR and are presenting it to the Working Group. | Ericsson | - |
| C1‑070870 | One or more organizations (3GPP Individual Members) which drafted the CR and are presenting it to the Working Group. | Ericsson | - |
| C1‑070871 | One or more organizations (3GPP Individual Members) which drafted the CR and are presenting it to the Working Group. | RIM | - |
| C1‑070872 | Draft TS 102 511, Human Factors (HF); AT Commands for Assistive Mobile Device Interfaces | STF 304 on AT Commands for Assistive Mobile Device Interfaces | - |
| C1‑070873 | - after radio and terrestrial resources for the group call channel have been released but the group call is ongoing – subject to certain conditions | Nortel | - |
| C1‑070874 | - after radio and terrestrial resources for the group call channel have been released but the group call is ongoing – subject to certain conditions | Nortel | - |
| C1‑070875 | - after radio and terrestrial resources for the broadcast call channel have been released but the broadcast call is ongoing – subject to certain conditions | Nortel | - |
| C1‑070876 | LS on GERAN – LTE interworking | 3GPP TSG CT | - |
| C1‑070877 | - | - | - |
| C1‑070878 | - | - | - |
| C1‑070879 | - | - | - |
| C1‑070880 | Reply to LS on Usage of Tracking Areas (TA) in LTE/SAE | RAN3 | - |
| C1‑070881 | LS on SIP Forking | CT1 | - |
| C1‑070882 | Reply LS on Location of Floor Control Server | CT1 | - |
| C1‑070883 | LS on Check of TS 23.333 Specification and MRFC/AS Requirements | CT1 | - |
| C1‑070884 | Reply LS on "Clarification on ISDN address string request" | CT1 | - |
| C1‑070885 | [Draft] SAE NAS tolerance of message loss | CT1 | - |
| C1‑070886 | LS on Maximum SDU size | CT1 | - |
| C1‑070887 | LS on RRC connected mode during MBMS enhanced broadcast | CT1 | - |
| C1‑070888 | Reply LS on new Management Object for Communication Continuity | CT1 | - |
| C1‑070889 | One or more organizations (3GPP Individual Members) which drafted the CR and are presenting it to the Working Group. | Alcatel-Lucent | - |
| C1‑070890 | One or more organizations (3GPP Individual Members) which drafted the CR and are presenting it to the Working Group. | Alcatel-Lucent | - |
| C1‑070891 | Discussion, SIP Control Framework and packages description | Hewlett-Packard | - |
| C1‑070892 | One or more organizations (3GPP Individual Members) which drafted the CR and are presenting it to the Working Group. | IAEI | - |
| C1‑070894 | Enhancements to Support Preferred Circuit Carrier Access and Dial-Around for Cable Networks | - | - |
| C1‑070895 | IMS Enhancements to Support Number Portability (NP) for Cable Networks | - | - |
| C1‑070896 | CR against TS 23.259 – Clause 4 PNM overview | Vodafone | - |
| C1‑070897 | CR against TS 23.259 – Clause 5 Procedures and Information Flows for UE Redirection Service (5/5.1) | Vodafone | - |
| C1‑070898 | CR against TS 23.259 – Clause 5 Procedures and Information Flows for UE Redirection Service (5.2) | Vodafone | - |
| C1‑070900 | CR against TS 23.259 – Clause 3 Definitions and Abbreviations | Vodafone | - |
| C1‑070901 | One or more organizations (3GPP Individual Members) which drafted the CR and are presenting it to the Working Group. | Alcatel-Lucent | - |
| C1‑070903 | CR against TS 23.259 – Clause 6.5: Access List configuration | Panasonic Mobile Communications | - |
| C1‑070904 | CR against TS 23.259 – Private network Concepts: Introduction and information flows | Panasonic Mobile Communications | - |
| C1‑070906 | CR against TS 23.259 – Clause 6.4 Procedures and Information Flows for Deactivation (6.4) | Huawei | - |
| C1‑070907 | CR to TR 24.801: SAE/LTE Bearer concept | Ericsson | - |
| C1‑070908 | CR to 24.801: SAE/LTE Bearer level QoS parameters | Ericsson | - |
| C1‑070909 | CR to 24.801: SAE/LTE Authentication | Ericsson | - |
| C1‑070910 | CR to 24.801: SAE/LTE Security key handling | Ericsson | - |
| C1‑070911 | CR to 24.801: Mobility management and Session management for SAE/LTE | Ericsson | - |
| C1‑070912 | CR 24.801: multi-TA registration in SAE | NEC | - |
| C1‑070913 | CR to 24.8bc: Impact on other specifications due to SAE | Alcatel-Lucent | - |
| C1‑070915 | TR 24.801, CT1 open issues related to tracking area concept | Huawei | - |
| C1‑070916 | [DRAFT] Reply LS on a new IMTC IMS Activity Group | CT1 | - |
| C1‑070917 | One or more organizations (3GPP Individual Members) which drafted the CR and are presenting it to the Working Group. | Source to WG:?[H9] | - |
| C1‑070918 | Inclusion of extending the session initiation protocol Reason header for preemption events (RFC4411) in the SIP profile | Alcatel-Lucent / Keith Drage | - |
| C1‑070919 | Inclusion of communications resource priority for the session initiation protocol (RFC4412) in the SIP profile | - | - |
| C1‑070920 | One or more organizations (3GPP Individual Members) which drafted the CR and are presenting it to the Working Group. | LM Ericsson | - |
| C1‑070921 | One or more organizations (3GPP Individual Members) which drafted the CR and are presenting it to the Working Group. | LM Ericsson | - |
| C1‑070923 | One or more organizations (3GPP Individual Members) which drafted the CR and are presenting it to the Working Group. | LM Ericsson | - |
| C1‑070924 | One or more organizations (3GPP Individual Members) which drafted the CR and are presenting it to the Working Group. | LM Ericsson | - |
| C1‑070925 | One or more organizations (3GPP Individual Members) which drafted the CR and are presenting it to the Working Group. | LM Ericsson | - |
| C1‑070926 | One or more organizations (3GPP Individual Members) which drafted the CR and are presenting it to the Working Group. | LM Ericsson | - |
| C1‑070927 | One or more organizations (3GPP Individual Members) which drafted the CR and are presenting it to the Working Group. | LM Ericsson | - |
| C1‑070928 | Clarification of the handling of ICSI | - | - |
| C1‑070929 | One or more organizations (3GPP Individual Members) which drafted the CR and are presenting it to the Working Group. | Ericsson | - |
| C1‑070930 | One or more organizations (3GPP Individual Members) which drafted the CR and are presenting it to the Working Group. | Vodafone | - |
| C1‑070931 | One or more organizations (3GPP Individual Members) which drafted the CR and are presenting it to the Working Group. | Samsung, Vodafone | - |
| C1‑070932 | Detailed procedures about session combining. | LM Ericsson,Huawei // C1 | - |
| C1‑070933 | One or more organizations (3GPP Individual Members) which drafted the CR and are presenting it to the Working Group. | Samsung | - |
| C1‑070934 | One or more organizations (3GPP Individual Members) which drafted the CR and are presenting it to the Working Group. | LM Ericsson | - |
| C1‑070935 | One or more organizations (3GPP Individual Members) which drafted the CR and are presenting it to the Working Group. | Samsung | - |
| C1‑070936 | One or more organizations (3GPP Individual Members) which drafted the CR and are presenting it to the Working Group. | Samsung | - |
| C1‑070937 | One or more organizations (3GPP Individual Members) which drafted the CR and are presenting it to the Working Group. | Samsung | - |
| C1‑070938 | One or more organizations (3GPP Individual Members) which drafted the CR and are presenting it to the Working Group. | Samsung | - |
| C1‑070939 | One or more organizations (3GPP Individual Members) which drafted the CR and are presenting it to the Working Group. | Samsung | - |
| C1‑070940 | One or more organizations (3GPP Individual Members) which drafted the CR and are presenting it to the Working Group. | Huawei | - |
| C1‑070941 | One or more organizations (3GPP Individual Members) which drafted the CR and are presenting it to the Working Group. | Vodafone | - |
| C1‑070942 | One or more organizations (3GPP Individual Members) which drafted the CR and are presenting it to the Working Group. | Ericsson | - |
| C1‑070943 | -if only one SIP dialog exists for the user identified in the P-Asserted-Identity header field and a 2xx response has been sent and there is active audio media, then continue the domain transfer procedures; | Alcatel-Lucent | - |
| C1‑070944 | One or more organizations (3GPP Individual Members) which drafted the CR and are presenting it to the Working Group. | Alcatel-Lucent | - |
| C1‑070945 | a)dialogs for which a 2xx response has not been sent are not considered; | Alcatel-Lucent | - |
| C1‑070947 | Figure A.5.2-1: Terminating call directed to IM CN subsystem | Nortel | - |
| C1‑070948 | 3)if the session is subject to anchoring, the DTF shall operate as an application server providing 3rd party call control, and specifically as a routeing B2BUA, as specified in subclause 5.7.5 of 3GPP TS 24.229 [8] for this request and all future req | Huawei | - |
| C1‑070949 | e)not all calls are suitable for domain transfer, and application of domain transfer to other calls might be against subscriber or operator preferences. 3GPP TS 22.101 [1] Clause 21 provides the requirements for this. Subclause 5.5 of the present doc | Huawei | - |
| C1‑070951 | One or more organizations (3GPP Individual Members) which drafted the CR and are presenting it to the Working Group. | Huawei | - |
| C1‑070952 | According to this stage3 description, if the DTF does not Record-Route on the requests of the calls without anchoring, then it will not get the final domain used by this session, and then it can not apply this information to another new incoming call | Huawei | - |
| C1‑070953 | One or more organizations (3GPP Individual Members) which drafted the CR and are presenting it to the Working Group. | Nokia, Siemens Networks | - |
| C1‑070954 | Request-uri as Called Party Number | Qualcomm Japan // C1 | - |
| C1‑070955 | Corrections to example flows | Ericsson / Atle | - |
| C1‑070956 | One or more organizations (3GPP Individual Members) which drafted the CR and are presenting it to the Working Group. | Nokia, Siemens Networks | - |
| C1‑070957 | One or more organizations (3GPP Individual Members) which drafted the CR and are presenting it to the Working Group. | Siemens Networks, Nokia | - |
| C1‑070958 | One or more organizations (3GPP Individual Members) which drafted the CR and are presenting it to the Working Group. | LM Ericsson | - |
| C1‑070959 | One or more organizations (3GPP Individual Members) which drafted the CR and are presenting it to the Working Group. | QUALCOMM Europe | - |
| C1‑070960 | One or more organizations (3GPP Individual Members) which drafted the CR and are presenting it to the Working Group. | QUALCOMM Europe | - |
| C1‑070961 | LS on NAS Handling during intra-LTE handover | RAN3 | - |
| C1‑070962 | LS on Handover with CN Node Change | RAN3 | - |
| C1‑070963 | One or more organizations (3GPP Individual Members) which drafted the CR and are presenting it to the Working Group. | ZTE Corporation | - |
| C1‑070964 | One or more organizations (3GPP Individual Members) which drafted the CR and are presenting it to the Working Group. | ZTE Corporation | - |
| C1‑070966 | One or more organizations (3GPP Individual Members) which drafted the CR and are presenting it to the Working Group. | RIM | - |
| C1‑070967 | The emergency call control procedures are specified in 3GPP TS 24.008 [3]. | Ericsson | - |
| C1‑070968 | One or more organizations (3GPP Individual Members) which drafted the CR and are presenting it to the Working Group. | RIM | - |
| C1‑070969 | One or more organizations (3GPP Individual Members) which drafted the CR and are presenting it to the Working Group. | Vodafone | - |
| C1‑070970 | Reply LS on handling of communication service identifiers | SA2 | - |
| C1‑070971 | Reply to: “List of IMS communication services supported by the network” | SA2 | - |
| C1‑070972 | TCRT: Silent (re-)joining dipatcher, immediately talking dispatcher | Siemens Networks, Nortel Networks // C1 | - |
| C1‑070973 | TCRT: Silent (re-)joining dipatcher, immediately talking dispatcher | Siemens Networks, Nortel Networks // C1 | - |
| C1‑070974 | - after radio and terrestrial resources for the group call channel have been released but the group call is ongoing – subject to certain conditions | Nortel | - |
| C1‑070975 | - after radio and terrestrial resources for the group call channel have been released but the group call is ongoing – subject to certain conditions | Nortel | - |
| C1‑070976 | Retry of the VBS Assignment procedure | Nortel | - |
| C1‑070977 | One or more organizations (3GPP Individual Members) which drafted the CR and are presenting it to the Working Group. | Telecom Italia, Huawei | - |
| C1‑070978 | CR 24.801: multi-TA registration in SAE | NEC | - |
| C1‑070979 | Introduction of Latency Reduction capabilities | GERAN | - |
| C1‑070980 | h)the Security-Client header field set to specify the security mechanism the UE supports, the IPsec layer algorithms the UE supports and the parameters needed for the security association setup. The UE shall support the setup of two pairs of security | Siemens Networks, CableLabs | - |
| C1‑070981 | Response LS on "Specification Update of GBR and MBR due to MIMO" | CT1 | - |
| C1‑070982 | One or more organizations (3GPP Individual Members) which drafted the CR and are presenting it to the Working Group. | Alcatel-Lucent | - |
| C1‑070983 | Multiple Registrations | CT1 | - |
| C1‑070984 | One or more organizations (3GPP Individual Members) which drafted the CR and are presenting it to the Working Group. | Alcatel-Lucent | - |
| C1‑070985 | One or more organizations (3GPP Individual Members) which drafted the CR and are presenting it to the Working Group. | CableLabs | - |
| C1‑070986 | Endorsement of early media draft | Orange, Alcatel-Lucent, Ericsson // C1 | - |
| C1‑070987 | Profile support for the P-Answer-State header extension to the session initiation protocol for the open mobile alliance push to talk over cellular (draft-allen-sipping-poc-p-answer-state-header) | Alcatel-Lucent / Keith Drage | - |
| C1‑070988 | - | - | - |
| C1‑070989 | One or more organizations (3GPP Individual Members) which drafted the CR and are presenting it to the Working Group. | Huawei | - |
| C1‑070990 | CR to TR 24.801: SAE/LTE Bearer concept | Ericsson | - |
| C1‑070991 | CR to 24.801: SAE/LTE Bearer level QoS parameters | Ericsson | - |
| C1‑070992 | CR to 24.801: SAE/LTE Authentication | Ericsson | - |
| C1‑070993 | Enhancements to Support Preferred Circuit Carrier Access and Dial-Around for Cable Networks | - | - |
| C1‑070994 | IMS Enhancements to Support Number Portability (NP) for Cable Networks | CableLabs | - |
| C1‑070995 | One or more organizations (3GPP Individual Members) which drafted the CR and are presenting it to the Working Group. | CableLabs | - |
| C1‑070996 | One or more organizations (3GPP Individual Members) which drafted the CR and are presenting it to the Working Group. | Vodafone | - |
| C1‑070997 | Additional call flow for establishing a session when both endpoints do not need to reserve resources | - | - |
| C1‑070998 | Reply LS on new IMTC IMS Activity Group | CT1 | - |
| C1‑070999 | CR to 24.801: SAE/LTE Authentication | Ericsson | - |
| C1‑071000 | LS on steering of roaming | CT1 | - |
| C1‑071001 | LS on steering of roaming | CT1 | - |
| C1‑071002 | Reply LS on Location of Floor Control Server | CT1 | - |
| C1‑071003 | LS on "Clarification on ISDN address string request" | CT1 | - |
| C1‑071004 | SAE NAS tolerance of message loss | CT1 | - |
| C1‑071005 | CR against TS 23.259 – Private network Concepts: Introduction and information flows | Panasonic Mobile Communications | - |
| C1‑071006 | LS on identifying Alias Identities | CT1 | - |
| C1‑071007 | One or more organizations (3GPP Individual Members) which drafted the CR and are presenting it to the Working Group. | ZTE Corporation | - |
| C1‑071008 | One or more organizations (3GPP Individual Members) which drafted the CR and are presenting it to the Working Group. | ZTE Corporation | - |
| C1‑071009 | One or more organizations (3GPP Individual Members) which drafted the CR and are presenting it to the Working Group. | CableLabs | - |
| C1‑071010 | One or more organizations (3GPP Individual Members) which drafted the CR and are presenting it to the Working Group. | CableLabs | - |
| C1‑071011 | Reply LS on new IMTC IMS Activity Group | CT1 | - |
| C1‑071012 | LS on identifying Alias Identities | CT1 | - |
| C1‑071013 | One or more organizations (3GPP Individual Members) which drafted the CR and are presenting it to the Working Group. | LM Ericsson | - |
| C1‑071014 | Detailed procedures about session combining | - | - |
| C1‑071015 | One or more organizations (3GPP Individual Members) which drafted the CR and are presenting it to the Working Group. | LM Ericsson | - |
| C1‑071016 | One or more organizations (3GPP Individual Members) which drafted the CR and are presenting it to the Working Group. | Samsung | - |
| C1‑071017 | Enhancements to Support Preferred Circuit Carrier Access and Dial-Around for Cable Networks | - | - |
page generated from database: 2024-04-22 07:58:53