3GPP TDocs (written contributions) at meeting
Meeting: C3-80 - 2015-02-02 to 2015-02-06, Sorrento
meeting id: C3-80 (click id for more info on this meeting)Click on the Tdoc to open its file.
| TDoc | Title | Source | Remarks |
|---|---|---|---|
| C3‑150001 | Draft Agenda for the CT3#80 Meeting | CT3 Chairman | - |
| C3‑150002 | Proposed Schedule for CT3#80 | CT3 Chairman | - |
| C3‑150003 | Allocation of documents to agenda items (at Deadline) | CT3 Chairman | - |
| C3‑150004 | Allocation of documents to agenda items (Start of Day 1) | CT3 Chairman | - |
| C3‑150005 | Allocation of documents to agenda items (Start of Day 2) | CT3 Chairman | - |
| C3‑150006 | Allocation of documents to agenda items (Start of Day 3) | CT3 Chairman | - |
| C3‑150007 | Allocation of documents to agenda items (Start of Day 4) | CT3 Chairman | - |
| C3‑150008 | Allocation of documents to agenda items (Start of Day 5) | CT3 Chairman | - |
| C3‑150009 | Allocation of documents to agenda items (End of Day 5) | CT3 Chairman | - |
| C3‑150010 | Summary of CT#66 related to CT3 | CT3 Chairman | - |
| C3‑150011 | Status of CT3 Work Items | CT3 Chairman | - |
| C3‑150012 | LS on TFT for default bearer | SA2 | - |
| C3‑150013 | LS on Introducing the feature of excluding Usage of a Service/Application from IP-CAN session/TDF session Usage into the specification | SA2 | - |
| C3‑150014 | LS on a study on Diameter load control mechanisms | CT4 | - |
| C3‑150015 | Reply LS on Maintenance of I-WLAN Solution | CT4 | - |
| C3‑150016 | Reply LS on discontinuance of I-WLAN related TS 29.161 | CT | - |
| C3‑150017 | LS on Introducing the feature of excluding Usage of a Service/Application from IP-CAN session/TDF session Usage into the specification. | SA2 | - |
| C3‑150018 | LS response on introducing new QCI Values | SA2 | - |
| C3‑150019 | LS to SA on 3GPP work organization for Mission Critical Push to Talk | SA | - |
| C3‑150020 | Candidate Release Available | SA | - |
| C3‑150021 | LS on Establishment of new working group TSG SA WG6 | SA | - |
| C3‑150022 | CT3-79 Draft Meeting report | MCC | - |
| C3‑150023 | Draft references in CT3 specifications | Ericsson | - |
| C3‑150024 | Bugfix: do not send negative-delivery IMDN after sending SIP 4xx/5xx response | Comverse Network Systems | - |
| C3‑150025 | Bugfix: do not send negative-delivery IMDN after sending SIP 4xx/5xx response | Comverse | - |
| C3‑150026 | Bugfix: do not send negative-delivery IMDN after sending SIP 4xx/5xx response | Comverse | - |
| C3‑150027 | Bugfix: do not send negative-delivery IMDN after sending SIP 4xx/5xx response | Comverse | - |
| C3‑150028 | Bugfix: do not send negative-delivery IMDN after sending SIP 4xx/5xx response | Comverse | - |
| C3‑150029 | Bugfix: do not send negative-delivery IMDN after sending SIP 4xx/5xx response | Comverse Network Systems | - |
| C3‑150030 | Clarification on the II-NNI requirement for CDIV regarding Privacy header field. | NTT | - |
| C3‑150031 | Clarification on the II-NNI requirement for CDIV regarding Privacy header field. | NTT | - |
| C3‑150032 | Clarification on the II-NNI requirement for CDIV regarding Privacy header field. | NTT | - |
| C3‑150033 | Clarification on the II-NNI requirement for CDIV regarding Privacy header field. | NTT | - |
| C3‑150034 | Addition of "mp" header field parameter into CDIV section. | NTT | - |
| C3‑150035 | Clarification on the II-NNI requirement regarding cause-param URI parameter. | NTT | - |
| C3‑150036 | Clarification on the II-NNI requirement regarding cause-param URI parameter. | NTT | - |
| C3‑150037 | Clarification on the II-NNI requirement regarding cause-param URI parameter. | NTT | - |
| C3‑150038 | Clarification on the II-NNI requirement regarding cause-param URI parameter. | NTT | - |
| C3‑150039 | Addition of an optional capability regarding a new cause-param value for service number translation. | NTT | - |
| C3‑150040 | Correction of a minor error in subclause C.3.1. | NTT | - |
| C3‑150041 | ICS call: reference correction | MCC | - |
| C3‑150042 | Announcement suppression for IMS hold request | MCC | - |
| C3‑150043 | Adding support for EVS codec | MCC | - |
| C3‑150044 | Note 4 in Table 3 for mapping to CLI parameter | MCC | - |
| C3‑150045 | Appearance of Redirection Number Restriction parameter | MCC | - |
| C3‑150046 | Inclusion of RFC7044 | MCC | - |
| C3‑150047 | NAS/RAN cause handling | MCC | - |
| C3‑150048 | Presence Reporting Area Indication on TDF Session | MCC | - |
| C3‑150049 | Mute-Notification Status on Gx and Sd Session | MCC | - |
| C3‑150050 | Correction to the PC to CS handover indication | MCC | - |
| C3‑150051 | RESOURCE_ALLOCATION_FAILURE error response not to be sent upon PCRF-initiated PCC rule | MCC | - |
| C3‑150052 | Number of standard QCI values | MCC | - |
| C3‑150053 | QCI code values “spare for future use” | MCC | - |
| C3‑150054 | 3GPP2 reference correction | MCC | - |
| C3‑150055 | Support for IPv6 prefix retrieve by the HSGW during the eHRPD pre-registration procedure | MCC | - |
| C3‑150056 | TFT handling correction | MCC | - |
| C3‑150057 | Correction of the REVALIDATION_TIMEOUT event trigger | MCC | - |
| C3‑150058 | IPCAN Session modification after bearer procedure | MCC | - |
| C3‑150059 | P-CSCF Restoration Procedure for Local Breakout | MCC | - |
| C3‑150060 | Priority Consideration for Diameter Overload Control | MCC | - |
| C3‑150061 | Correction to the Gateway Control Session establishment procedure | MCC | - |
| C3‑150062 | PCRF discovery for the HNB CS Service | MCC | - |
| C3‑150063 | Access network information reporting during the IP-CAN session termination | MCC | - |
| C3‑150064 | Reporting RAN/NAS cause during bearer creation/modification failure scenarious | MCC | - |
| C3‑150065 | Removal of Editor’s Note | MCC | - |
| C3‑150066 | Access network information reporting during the IP-CAN session termination | MCC | - |
| C3‑150067 | Introduction of a reference to the Rest-Rx interface | MCC | - |
| C3‑150068 | Inclusion of RAN/NAS cause values into SIP signalling by P-CSCF | MCC | - |
| C3‑150069 | Precedence derivation for ADC rule | MCC | - |
| C3‑150070 | Support for IPv6 prefix retrieve by the HSGW during the eHRPD pre-registration procedure | MCC | - |
| C3‑150071 | revised WID on IMS Signalling Activated Trace (ISAT) | Vodafone GmbH | - |
| C3‑150072 | Corrections to the Gateway Control and QoS rules Provision procedure | China Telecom,ZTE,Huawei | - |
| C3‑150073 | Corrections to the Gateway Control and QoS rules Provision procedure | China Telecom,ZTE,Huawei | - |
| C3‑150074 | Corrections to the Gateway Control and QoS rules Provision procedure | China Telecom,ZTE,Huawei | - |
| C3‑150075 | Corrections to the Gateway Control and QoS rules Provision procedure | China Telecom,ZTE,Huawei | - |
| C3‑150076 | Corrections to the Gateway Control and QoS rules Provision procedure | China Telecom,ZTE,Huawei | - |
| C3‑150077 | Corrections to the Gateway Control and QoS rules Provision procedure | China Telecom,ZTE,Huawei | - |
| C3‑150078 | Corrections to the Gateway Control and QoS rules Provision procedure | China Telecom,ZTE,Huawei | - |
| C3‑150079 | Corrections to the Used-Service-Unit AVP when UMCH feature is supported | China Telecom,ZTE,Huawei | - |
| C3‑150080 | Corrections to the Used-Service-Unit AVP when UMCH feature is supported | China Telecom,ZTE,Huawei | - |
| C3‑150081 | Corrections to the Used-Service-Unit AVP when UMCH feature is supported | China Telecom,ZTE,Huawei | - |
| C3‑150082 | Enhanced NGCN based MCPTT architecture | Huawei, Hisilicon,TD-Tech | - |
| C3‑150083 | DMO/DMO-R Group call setup | Huawei, Hisilicon,TD-Tech | - |
| C3‑150084 | Layer 3 UE-to-network relay solution for NMO-R | Huawei, Hisilicon,TD-Tech | - |
| C3‑150085 | MCPTT deployment scenarios | Huawei, Hisilicon,TD-Tech | - |
| C3‑150086 | Roaming scenarios for MCPTT service | Huawei, Hisilicon,TD-Tech | - |
| C3‑150087 | SIP over eMBMS bearer | Huawei, Hisilicon,TD-Tech | - |
| C3‑150088 | TDF support for downlink packet marking | Allot Communications Ltd., Huawei | - |
| C3‑150089 | Adapt PCC architecture diagrams to include Np reference point | Huawei | - |
| C3‑150090 | Mitigating RAN user plane congestion over Rest Rx | Huawei | - |
| C3‑150091 | Add missing definition of RAN user plane congestion | Huawei | - |
| C3‑150092 | DRA procedure to support PCRF selection by the RCAF | Huawei | - |
| C3‑150093 | Adding UE location information in aggregated RUCI reporting | Huawei | - |
| C3‑150094 | Remove editor's note on optimization of UE identity in aggregated RUCI reporting | Huawei | - |
| C3‑150095 | Clarifying the congestion level value in AVP defintion | Huawei | - |
| C3‑150096 | Cleanup of definitions and abbreviations | Huawei | - |
| C3‑150097 | Editor's note cleanup | Huawei | - |
| C3‑150098 | Remove access type attribute in table of Np reused Diameter AVPs | Huawei | - |
| C3‑150099 | New AVP and experimental result code in TS 29.214 | Huawei | - |
| C3‑150100 | Roaming applicability in EPC-level ProSe discovery | Huawei | - |
| C3‑150101 | Reference update to align with the published BBF documents | Huawei | - |
| C3‑150102 | Reference update to align with the published BBF documents | Huawei | - |
| C3‑150103 | Remove editor's note on access line identifier | Huawei | - |
| C3‑150104 | Remove editor's note on access line identifier | Huawei | - |
| C3‑150105 | Reference update to align with the published BBF documents | Huawei | - |
| C3‑150106 | Reference update to align with the published BBF documents | Huawei | - |
| C3‑150107 | TWAN release cause for trusted WLAN | Huawei | - |
| C3‑150108 | TWAN release cause for trusted WLAN | Huawei | - |
| C3‑150109 | Correction on volumn and time threshold provisioning | Huawei | - |
| C3‑150110 | Correction on volumn and time threshold provisioning | Huawei | - |
| C3‑150111 | Paging policy differentiation for IMS voice | Alcatel-Lucent, Verizon | - |
| C3‑150112 | Correction to attribute “a=inactive” in initial INVITE | Deutsche Telekom AG | - |
| C3‑150113 | Correction to attribute “a=inactive” in initial INVITE | Deutsche Telekom AG | - |
| C3‑150114 | Introducing EVS over 3G CS networks – CT impacts | Qualcomm Incorporated | - |
| C3‑150115 | New WID on CT aspects of EVS in 3G Circuit-Switched Networks | Qualcomm Incorporated | - |
| C3‑150116 | Request RAT type reporting over Rx interface | China Telecom, Huawei | - |
| C3‑150117 | Instance-number value for secondary-realm | Ericsson | - |
| C3‑150118 | Instance-number value for secondary-realm | Ericsson | - |
| C3‑150119 | Instance-number value for secondary-realm | Ericsson | - |
| C3‑150120 | Checksum calculation | Ericsson | - |
| C3‑150121 | Checksum calculation | Ericsson | - |
| C3‑150122 | Checksum calculation | Ericsson | - |
| C3‑150123 | Correcting UA procedure | Ericsson | - |
| C3‑150124 | Correcting UA procedure | Ericsson | - |
| C3‑150125 | Correcting UA procedure | Ericsson | - |
| C3‑150126 | Reference update: draft-ietf-mmusic-sctp-sdp | Ericsson | - |
| C3‑150127 | Reference update: draft-holmberg-sipcore-received-realm | Ericsson | - |
| C3‑150128 | Incorrect implementation of CRs | MCC | - |
| C3‑150129 | Reference update: draft-holmberg-dispatch-iotl | Ericsson | - |
| C3‑150130 | Annex A corrections | Ericsson LM | - |
| C3‑150131 | Restoration-Info header field applicability | Ericsson | - |
| C3‑150132 | Relayed-Charge header field | Ericsson LM | - |
| C3‑150133 | Applying drafting rules | Ericsson LM | - |
| C3‑150134 | PS to CS SRVCC after access transfer is completed interworking | Ericsson LM | - |
| C3‑150135 | Procedures to avoid changes in OMR outcome | Ericsson | - |
| C3‑150136 | Procedures for avoiding changes in the OMR algorithm outcome on subsequent SDP offer/answer transactions | Ericsson | - |
| C3‑150137 | Procedures for avoiding changes in the OMR algorithm outcome on subsequent SDP offer/answer transactions | Ericsson LM | - |
| C3‑150138 | Procedures for avoiding changes in the OMR algorithm outcom on subsequent SDP offer/answer transactions | Ericsson LM | - |
| C3‑150139 | Reference update: draft-ietf-insipid-session-id | Ericsson | - |
| C3‑150140 | Reference update: draft-holmberg-dispatch-iotl | Ericsson | - |
| C3‑150141 | Reference update: draft-holmberg-dispatch-iotl | Ericsson | - |
| C3‑150142 | LS on new cause URI parameter value for IN numbers interworking | ORANGE | - |
| C3‑150143 | Reference update: draft-mohali-dispatch-cause-for-service-number | ORANGE | - |
| C3‑150144 | Correction to the usage monitoring control for sponsored data connectivity | ZTE | - |
| C3‑150145 | Correction to the usage monitoring control for sponsored data connectivity | ZTE | - |
| C3‑150146 | Correction to the usage monitoring control for sponsored data connectivity | ZTE | - |
| C3‑150147 | Correction to the usage monitoring control for sponsored data connectivity | ZTE | - |
| C3‑150148 | Access network information report in case of IP-CAN bearer/IP-CAN session termination | ZTE | - |
| C3‑150149 | Access network information report in case of IP-CAN bearer/IP-CAN session termination | ZTE | - |
| C3‑150150 | Access network information report in case of IP-CAN bearer/IP-CAN session termination | ZTE | - |
| C3‑150151 | Correction to temporary network failure handling | ZTE | - |
| C3‑150152 | Correction to temporary network failure handling | ZTE | - |
| C3‑150153 | Correction to temporary network failure handling | ZTE | - |
| C3‑150154 | TWAN supports access network information report | ZTE | - |
| C3‑150155 | TWAN supports access network information report | ZTE | - |
| C3‑150156 | TWAN supports access network information report | ZTE | - |
| C3‑150157 | TWAN supports access network information report | ZTE | - |
| C3‑150158 | Correction to the PRA reporting | ZTE | - |
| C3‑150159 | Correction to the PRA reporting | ZTE | - |
| C3‑150160 | Clarify the condition where the RCAF reports the RUCI | ZTE | - |
| C3‑150161 | M bit set for the specific AVPs | ZTE | - |
| C3‑150162 | Remove the access capability in re-used AVP table | ZTE | - |
| C3‑150163 | Remove the redundant references | ZTE | - |
| C3‑150164 | Resolve the editor's notes | ZTE | - |
| C3‑150165 | Resolve the race conditions related to UE mobility between RCAFs | ZTE | - |
| C3‑150166 | Excluding Usage of a ServiceApplication from IP-CAN sessionTDF session Usage | ZTE, China Telecom, Huawei | - |
| C3‑150167 | Excluding Usage of a ServiceApplication from IP-CAN sessionTDF session Usage for roaming case | ZTE, China Telecom, Huawei | - |
| C3‑150168 | New WID on Extended Overload Control for PCC based Diameter applications | ZTE | - |
| C3‑150169 | Correction of APRI Mapping for Generic Number | Deutsche Telekom, Nokia Networks | - |
| C3‑150170 | Correction of APRI Mapping for Generic Number | Deutsche Telekom, Nokia Networks | - |
| C3‑150171 | Correction of APRI Mapping for Generic Number | Deutsche Telekom, Nokia Networks | - |
| C3‑150172 | Correction of APRI Mapping for Generic Number | Deutsche Telekom, Nokia Networks | - |
| C3‑150173 | Correction of APRI Mapping for Generic Number | Deutsche Telekom, Nokia Networks | - |
| C3‑150174 | Adding missing abbreviations | Fujitsu Limited | - |
| C3‑150175 | Editorial correction and incorrect implementation of CRs | Alcatel-Lucent Deutschland AG | - |
| C3‑150176 | Correction of applicability of P-Charging-Vector header field in NOTIFY method | Fujitsu Limited | - |
| C3‑150177 | Correction of applicability of P-Charging-Vector header field in NOTIFY method | Fujitsu Limited | - |
| C3‑150178 | Correction of applicability of P-Charging-Vector header field in NOTIFY method | Fujitsu Limited | - |
| C3‑150179 | Double resource reuse support over S9 | Ericsson | - |
| C3‑150180 | Completion of Double Resource Reuse support over Gx | Ericsson | - |
| C3‑150181 | Uniqueness of Sharing Key for resource sharing over Rx | Ericsson | - |
| C3‑150182 | LS on New AVPs and range of transient failure result codes in TS 29.214 | Ericsson | - |
| C3‑150183 | Reply LS on End-to-end QoS handling of MTSI | Ericsson | - |
| C3‑150184 | Charging correlation identifier for the IP-CAN session in Gx | Ericsson | - |
| C3‑150185 | Charging correlation identifier for the IP-CAN session in Gx | Ericsson | - |
| C3‑150186 | Charging correlation identifier for the IP-CAN session in S9 | Ericsson | - |
| C3‑150187 | Charging correlation identifier for the IP-CAN session in S9 | Ericsson | - |
| C3‑150188 | QoS change of default bearer | Ericsson | - |
| C3‑150189 | QoS change of default bearer | Ericsson | - |
| C3‑150190 | Correction about conditions for filter restrictions | Ericsson, Huawei | - |
| C3‑150191 | Correction about conditions for filter restrictions | Ericsson, Huawei | - |
| C3‑150192 | Correction about conditions for filter restrictions | Ericsson, Huawei | - |
| C3‑150193 | LS on New AVPs in TS 29.061 | Ericsson | - |
| C3‑150194 | Protocol enhancements to indicate support of device recall and replace by SMS-SC | Ericsson, Huawei | - |
| C3‑150195 | Removal of UE context procedure | Ericsson | - |
| C3‑150196 | Conditional and Unconditional reporting restrictions | Ericsson | - |
| C3‑150197 | UE context removal in IP-CAN session termination procedure | Ericsson | - |
| C3‑150198 | Enable MB2 procedures authorization | Ericsson | - |
| C3‑150199 | Discussion of Called-Station-Id | China Mobile Com. Corporation | - |
| C3‑150200 | Clarification of the Called-Station-Id | China Mobile Com. Corporation | - |
| C3‑150201 | Clarification of the Called-Station-Id | China Mobile Com. Corporation | - |
| C3‑150202 | Clarification of the Called-Station-Id | China Mobile Com. Corporation | - |
| C3‑150203 | Clarification of the Called-Station-Id | China Mobile Com. Corporation | - |
| C3‑150204 | AF session termination | Huawei | - |
| C3‑150205 | Provisioning of Access Network Charging Identifier | Huawei | - |
| C3‑150206 | Provisioning of Access Network Charging Identifier | Huawei | - |
| C3‑150207 | Correction of TFT handling on default bearer | Huawei | - |
| C3‑150208 | Correction of TFT handling on default bearer | Huawei | - |
| C3‑150209 | Correction of TFT handling on default bearer | Huawei | - |
| C3‑150210 | TMGI and Flow ID Handling | Huawei, Nokia Networks | - |
| C3‑150211 | Calendar of forthcoming CT3 meetings | MCC | - |
| C3‑150212 | TWAN release cause for REST-Rx interface | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Huawei | - |
| C3‑150213 | WORK PLAN- 3GPP Work Plan extract for CT3 | MCC | - |
| C3‑150214 | QoS mapping for RS and RR | ZTE Corporation | - |
| C3‑150215 | Correction of APRI Mapping for Generic Number | Deutsche Telekom, Nokia Networks, Orange | - |
| C3‑150216 | Correction of APRI Mapping for Generic Number | Deutsche Telekom, Nokia Networks, Orange | - |
| C3‑150217 | Correction of APRI Mapping for Generic Number | Deutsche Telekom, Nokia Networks, Orange | - |
| C3‑150218 | Correction of APRI Mapping for Generic Number | Deutsche Telekom, Nokia Networks, Orange | - |
| C3‑150219 | Correction of APRI Mapping for Generic Number | Deutsche Telekom, Nokia Networks, Orange | - |
| C3‑150220 | Reference update for UUSIW | Alcatel-Lucent , Alcatel-Lucent Shanghai Bell | - |
| C3‑150221 | Reference update for UUSIW | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | - |
| C3‑150222 | Reference update for UUSIW | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | - |
| C3‑150223 | Reference update for UUSIW | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | - |
| C3‑150224 | Reference update for UUSIW | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | - |
| C3‑150225 | Reference update for UUSIW | Alcatel-Lucent, ALcatel-Lucent Shanghai Bell | - |
| C3‑150226 | Reference update for UUSIW | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | - |
| C3‑150227 | Reference update for UUSIW | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | - |
| C3‑150228 | Reference update for UUSIW | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | - |
| C3‑150229 | Reference update for UUSIW | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | - |
| C3‑150230 | Correction to the session establishment and notification URIs | Oracle Corporation | - |
| C3‑150231 | Allowing for forward compatibility and miscellaneous corrections | Oracle Corporation | - |
| C3‑150232 | Corrections in the definition of MBMS Service Area AVP | Motorola Solutions Danmark A/S | - |
| C3‑150233 | The inclusion of Flow Identifier in the MBMS Bearer activation request | Motorola Solutions Danmark A/S | - |
| C3‑150234 | Opptional MBMS Session Identity | Motorola Solutions Danmark A/S | - |
| C3‑150235 | Enabling the AF for defining the ToS-Traffic-Class AVP | Motorola Solutions Danmark A/S | - |
| C3‑150236 | Add the ToS-Traffic-Class AVP to the message sent by AF over Rx | Motorola Solutions Danmark A/S | - |
| C3‑150237 | Add the ToS-Traffic-Class AVP to the Rx to be sent by AF | Motorola Solutions Danmark A/S | - |
| C3‑150238 | Enable the ToS-Traffic-Class AVP to be provided by AF | Motorola Solutions Danmark A/S | - |
| C3‑150239 | Location information in case of non-3GPP access | Alcatel-Lucent | - |
| C3‑150240 | Clarification of the Called-Station-Id | China Mobile Com. Corporation, Huawei | - |
| C3‑150241 | Clarification of the Called-Station-Id | China Mobile Com. Corporation | - |
| C3‑150242 | Location information in case of non-3GPP access | Alcatel-Lucent | - |
| C3‑150243 | Clarification of the Called-Station-Id | China Mobile Com. Corporation, Huawei | - |
| C3‑150244 | Correction of EVS reference bumber | Nokia Networks | - |
| C3‑150245 | Correction of EVS related reference number | Nokia Networks | - |
| C3‑150246 | Correction of EVS related reference number | Nokia Networks | - |
| C3‑150247 | Adding support for EVS codec | Nokia Networks | - |
| C3‑150248 | Note 4 in Table 3 for mapping to CLI parameter | Nokia Networks | - |
| C3‑150249 | Appearance of Redirection Number Restriction parameter | Nokia Networks | - |
| C3‑150250 | The inclusion of Flow Identifier in the MBMS Bearer activation request | Motorola Solutions Danmark A/S | - |
| C3‑150251 | Opptional MBMS Session Identity | Motorola Solutions Danmark A/S | - |
| C3‑150252 | LS related to Mobile VoIP IMS Roaming | SA3-LI | - |
| C3‑150253 | Reply LS on TLS and DTLS terminology | SA3 | - |
| C3‑150254 | LS on TR 26.924 Study on improved end-to-end QoS handling | SA4 | - |
| C3‑150255 | LS on CT Impacts of the ROI WI | SA4 | - |
| C3‑150256 | Reply to: LS related to Mobile VoIP IMS Roaming | Orange | - |
| C3‑150257 | LS on New AVPs and range of transient failure result codes in TS 29.214 | Ericsson | - |
| C3‑150258 | New WID on CT aspects of EVS in 3G Circuit-Switched Networks | Qualcomm Incorporated | - |
| C3‑150259 | New WID on Extended Overload Control for PCC based Diameter applications | ZTE | - |
| C3‑150260 | Incorrect implementation of CRs | MCC | - |
| C3‑150261 | Bugfix: do not send negative-delivery IMDN after sending SIP 4xx/5xx response | Comverse Network Systems | - |
| C3‑150262 | Bugfix: do not send negative-delivery IMDN after sending SIP 4xx/5xx response | Comverse | - |
| C3‑150263 | Bugfix: do not send negative-delivery IMDN after sending SIP 4xx/5xx response | Comverse | - |
| C3‑150264 | Bugfix: do not send negative-delivery IMDN after sending SIP 4xx/5xx response | Comverse | - |
| C3‑150265 | Bugfix: do not send negative-delivery IMDN after sending SIP 4xx/5xx response | Comverse | - |
| C3‑150266 | Reference update for UUSIW | Alcatel-Lucent , Alcatel-Lucent Shanghai Bell | - |
| C3‑150267 | Reference update for UUSIW | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | - |
| C3‑150268 | Reference update for UUSIW | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | - |
| C3‑150269 | Reference update for UUSIW | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | - |
| C3‑150270 | Reference update for UUSIW | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | - |
| C3‑150271 | Reference update for UUSIW | Alcatel-Lucent, ALcatel-Lucent Shanghai Bell | - |
| C3‑150272 | Reference update for UUSIW | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | - |
| C3‑150273 | Reference update for UUSIW | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | - |
| C3‑150274 | Reference update for UUSIW | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | - |
| C3‑150275 | Reference update for UUSIW | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | - |
| C3‑150276 | Correction of APRI Mapping for Generic Number | Deutsche Telekom, Nokia Networks, Orange | - |
| C3‑150277 | Correction of APRI Mapping for Generic Number | Deutsche Telekom, Nokia Networks, Orange | - |
| C3‑150278 | Correction of APRI Mapping for Generic Number | Deutsche Telekom, Nokia Networks, Orange | - |
| C3‑150279 | Correction of APRI Mapping for Generic Number | Deutsche Telekom, Nokia Networks, Orange | - |
| C3‑150280 | Correction of APRI Mapping for Generic Number | Deutsche Telekom, Nokia Networks, Orange | - |
| C3‑150281 | Clarification on the II-NNI requirement for CDIV regarding Privacy header field. | NTT | - |
| C3‑150282 | Clarification on the II-NNI requirement for CDIV regarding Privacy header field. | NTT | - |
| C3‑150283 | Clarification on the II-NNI requirement for CDIV regarding Privacy header field. | NTT | - |
| C3‑150284 | Clarification on the II-NNI requirement for CDIV regarding Privacy header field. | NTT | - |
| C3‑150285 | Clarification on the II-NNI requirement regarding cause-param URI parameter. | NTT | - |
| C3‑150286 | Clarification on the II-NNI requirement regarding cause-param URI parameter. | NTT | - |
| C3‑150287 | Clarification on the II-NNI requirement regarding cause-param URI parameter. | NTT | - |
| C3‑150288 | Clarification on the II-NNI requirement regarding cause-param URI parameter. | NTT | - |
| C3‑150289 | Procedures for avoiding changes in the OMR algorithm outcome on subsequent SDP offer/answer transactions | Ericsson | - |
| C3‑150290 | Procedures for avoiding changes in the OMR algorithm outcome on subsequent SDP offer/answer transactions | Ericsson LM | - |
| C3‑150291 | Procedures for avoiding changes in the OMR algorithm outcom on subsequent SDP offer/answer transactions | Ericsson LM | - |
| C3‑150292 | Correction about conditions for filter restrictions | Ericsson, Huawei | - |
| C3‑150293 | Correction about conditions for filter restrictions | Ericsson, Huawei | - |
| C3‑150294 | Correction about conditions for filter restrictions | Ericsson, Huawei | - |
| C3‑150295 | Correction of TFT handling on default bearer | Huawei | - |
| C3‑150296 | Correction of TFT handling on default bearer | Huawei | - |
| C3‑150297 | Correction of TFT handling on default bearer | Huawei | - |
| C3‑150298 | Access network information report in case of IP-CAN bearer/IP-CAN session termination | ZTE | - |
| C3‑150299 | Access network information report in case of IP-CAN bearer/IP-CAN session termination | ZTE | - |
| C3‑150300 | Access network information report in case of IP-CAN bearer/IP-CAN session termination | ZTE | - |
| C3‑150301 | Correction to temporary network failure handling | ZTE | - |
| C3‑150302 | Corrections to the Used-Service-Unit AVP when UMCH feature is supported | China Telecom,ZTE,Huawei | - |
| C3‑150303 | Corrections to the Used-Service-Unit AVP when UMCH feature is supported | China Telecom,ZTE,Huawei | - |
| C3‑150304 | Corrections to the Used-Service-Unit AVP when UMCH feature is supported | China Telecom,ZTE,Huawei | - |
| C3‑150305 | revised WID on IMS Signalling Activated Trace (ISAT) | Vodafone GmbH | - |
| C3‑150306 | Remove editor's note on optimization of UE identity in aggregated RUCI reporting | Huawei | - |
| C3‑150307 | Adding UE location information in aggregated RUCI reporting | Huawei | - |
| C3‑150308 | Resolve the race conditions related to UE mobility between RCAFs | ZTE | - |
| C3‑150309 | Mitigating RAN user plane congestion over Rest Rx | Huawei, China Telecom, Cisco | - |
| C3‑150310 | DRA procedure to support PCRF selection by the RCAF | Huawei, China Telecom | - |
| C3‑150311 | Clarifying the congestion level value in AVP defintion | Huawei | - |
| C3‑150312 | Editor's note cleanup | Huawei | - |
| C3‑150313 | Remove the access capability in re-used AVP table | ZTE | - |
| C3‑150314 | Clarify the condition where the RCAF reports the RUCI | ZTE | - |
| C3‑150315 | M bit set for the specific AVPs | ZTE | - |
| C3‑150316 | Removal of UE context procedure | Ericsson | - |
| C3‑150317 | Conditional and Unconditional reporting restrictions | Ericsson | - |
| C3‑150318 | UE context removal in IP-CAN session termination procedure | Ericsson | - |
| C3‑150319 | Paging policy differentiation for IMS voice | Alcatel-Lucent, Verizon | - |
| C3‑150320 | Reply LS on End-to-end QoS handling of MTSI | Ericsson | - |
| C3‑150321 | Double resource reuse support over S9 | Ericsson | - |
| C3‑150322 | Uniqueness of Sharing Key for resource sharing over Rx | Ericsson | - |
| C3‑150323 | Excluding Usage of a ServiceApplication from IP-CAN sessionTDF session Usage | ZTE, China Telecom, Huawei | - |
| C3‑150324 | Excluding Usage of a ServiceApplication from IP-CAN sessionTDF session Usage for roaming case | ZTE, China Telecom, Huawei | - |
| C3‑150325 | TDF support for downlink packet marking | Allot Communications Ltd., Huawei | - |
| C3‑150326 | Reference update: draft-ietf-mmusic-sctp-sdp | Ericsson | - |
| C3‑150327 | Correction to attribute “a=inactive” in initial INVITE | Deutsche Telekom AG, AT&T, Telefonica, NTT | - |
| C3‑150328 | Correction to attribute “a=inactive” in initial INVITE | Deutsche Telekom AG, AT&T, Telefonica, NTT | - |
| C3‑150329 | Relayed-Charge header field | Ericsson LM | - |
| C3‑150330 | Reference update: draft-ietf-insipid-session-id | Ericsson | - |
| C3‑150331 | Reference update: draft-holmberg-dispatch-iotl | Ericsson | - |
| C3‑150332 | Addition of "mp" header field parameter into CDIV section. | NTT | - |
| C3‑150333 | Restoration-Info header field applicability | Ericsson | - |
| C3‑150334 | TWAN release cause for trusted WLAN | Huawei | - |
| C3‑150335 | TWAN release cause for trusted WLAN | Huawei | - |
| C3‑150336 | QoS mapping for RS and RR | ZTE Corporation | - |
| C3‑150337 | Charging correlation identifier for the IP-CAN session in Gx | Ericsson, Huawei | - |
| C3‑150338 | Charging correlation identifier for the IP-CAN session in Gx | Huawei | - |
| C3‑150339 | Adding support for EVS codec | Nokia Networks | - |
| C3‑150340 | QoS change of default bearer | Ericsson | - |
| C3‑150341 | QoS change of default bearer | Ericsson | - |
| C3‑150342 | Editorial correction and incorrect implementation of CRs | Alcatel-Lucent Deutschland AG | - |
| C3‑150343 | Correction to the session establishment and notification URIs | Oracle Corporation | - |
| C3‑150344 | Allowing for forward compatibility and miscellaneous corrections | Oracle Corporation | - |
| C3‑150345 | Reference update to align with the published BBF documents | Huawei | - |
| C3‑150346 | Reference update to align with the published BBF documents | Huawei | - |
| C3‑150347 | Reference update to align with the published BBF documents | Huawei | - |
| C3‑150348 | TWAN supports access network information report | ZTE | - |
| C3‑150349 | TWAN supports access network information report | ZTE | - |
| C3‑150350 | Roaming applicability in EPC-level ProSe discovery | Huawei | - |
| C3‑150351 | Correction to the PRA reporting | ZTE | - |
| C3‑150352 | Correction to the PRA reporting | ZTE | - |
| C3‑150353 | LS on Enable MB2 procedures authorization | CT3 | - |
| C3‑150354 | TMGI and Flow ID Handling | Huawei, Nokia Networks | - |
| C3‑150355 | Corrections in the definition of MBMS Service Area AVP | Motorola Solutions Danmark A/S | - |
| C3‑150356 | Activation of an additional MBMS Bearer for a TMGI with already an active MBMS Bearer | Motorola Solutions Danmark A/S | - |
| C3‑150357 | Opptional MBMS Session Identity | Motorola Solutions Danmark A/S | - |
| C3‑150358 | Correction on volumn and time threshold provisioning | Huawei | - |
| C3‑150359 | Correction on volumn and time threshold provisioning | Huawei | - |
| C3‑150360 | Add the ToS-Traffic-Class AVP to the Rx to be sent by AF | Motorola Solutions Danmark A/S | - |
| C3‑150361 | Location information in case of non-3GPP access | Alcatel-Lucent | - |
| C3‑150362 | Location information in case of non-3GPP access | Alcatel-Lucent | - |
| C3‑150363 | Relayed-Charge header field | Ericsson LM | - |
| C3‑150364 | Removal of duplicated refrence | Nokia Networks | - |
| C3‑150365 | Correction of applicability of P-Charging-Vector header field in NOTIFY method | Fujitsu Limited | - |
| C3‑150366 | Addition of an optional capability regarding a new cause-param value for service number translation. | NTT | - |
| C3‑150367 | Reference update: draft-mohali-dispatch-cause-for-service-number | ORANGE | - |
| C3‑150368 | Applying drafting rules | Ericsson LM | - |
| C3‑150369 | Adding missing abbreviations | Fujitsu Limited, NTT | - |
| C3‑150370 | LS on new cause URI parameter value for IN numbers interworking | ORANGE | - |
| C3‑150371 | Reference update: draft-mohali-dispatch-cause-for-service-number | ORANGE | - |
| C3‑150372 | LS on new cause URI parameter value for IN numbers interworking | ORANGE | - |
| C3‑150373 | Applying drafting rules | Ericsson LM | - |
| C3‑150374 | Bugfix: do not send negative-delivery IMDN after sending SIP 4xx/5xx response | Comverse Network Systems | - |
| C3‑150375 | Bugfix: do not send negative-delivery IMDN after sending SIP 4xx/5xx response | Comverse | - |
| C3‑150376 | Bugfix: do not send negative-delivery IMDN after sending SIP 4xx/5xx response | Comverse | - |
| C3‑150377 | Bugfix: do not send negative-delivery IMDN after sending SIP 4xx/5xx response | Comverse | - |
| C3‑150378 | Bugfix: do not send negative-delivery IMDN after sending SIP 4xx/5xx response | Comverse | - |
| C3‑150379 | Correction about conditions for filter restrictions | Ericsson, Huawei | - |
| C3‑150380 | Correction about conditions for filter restrictions | Ericsson, Huawei | - |
| C3‑150381 | Correction about conditions for filter restrictions | Ericsson, Huawei | - |
| C3‑150382 | Correction of TFT handling on default bearer | Huawei | - |
| C3‑150383 | Correction of TFT handling on default bearer | Huawei | - |
| C3‑150384 | Correction of TFT handling on default bearer | Huawei | - |
| C3‑150385 | Correction to the session establishment and notification URIs | Oracle Corporation | - |
| C3‑150386 | Allowing for forward compatibility and miscellaneous corrections | Oracle Corporation | - |
| C3‑150387 | Clarification on the II-NNI requirement for CDIV regarding Privacy header field. | NTT | - |
| C3‑150388 | Clarification on the II-NNI requirement for CDIV regarding Privacy header field. | NTT | - |
| C3‑150389 | Clarification on the II-NNI requirement for CDIV regarding Privacy header field. | NTT | - |
| C3‑150390 | Clarification on the II-NNI requirement for CDIV regarding Privacy header field. | NTT | - |
| C3‑150391 | DRA procedure to support PCRF selection by the RCAF | Huawei, China Telecom | - |
| C3‑150392 | Adding UE location information in aggregated RUCI reporting | Huawei | - |
| C3‑150393 | Clarifying the congestion level value in AVP defintion | Huawei, China Telecom | - |
| C3‑150394 | Clarify the condition where the RCAF reports the RUCI | ZTE | - |
| C3‑150395 | Resolve the race conditions related to UE mobility between RCAFs | ZTE | - |
| C3‑150396 | Paging policy differentiation for IMS voice | Alcatel-Lucent, Verizon | - |
| C3‑150397 | Reference update to align with the published BBF documents | Huawei | - |
| C3‑150398 | Reference update to align with the published BBF documents | Huawei | - |
| C3‑150399 | Reply LS on End-to-end QoS handling of MTSI | Ericsson | - |
| C3‑150400 | Uniqueness of Sharing Key for resource sharing over Rx | Ericsson | - |
| C3‑150401 | TDF support for downlink packet marking | Allot Communications Ltd., Huawei | - |
| C3‑150402 | New WID on Extended Overload Control for PCC based Diameter applications | ZTE | - |
| C3‑150403 | Add the ToS-Traffic-Class AVP to the Rx to be sent by AF | Motorola Solutions Danmark A/S | - |
| C3‑150404 | Access network information report in case of IP-CAN bearer/IP-CAN session termination | ZTE | - |
| C3‑150405 | Access network information report in case of IP-CAN bearer/IP-CAN session termination | ZTE | - |
| C3‑150406 | Access network information report in case of IP-CAN bearer/IP-CAN session termination | ZTE | - |
| C3‑150407 | Corrections to the Used-Service-Unit AVP when UMCH feature is supported | China Telecom,ZTE,Huawei | - |
| C3‑150408 | Corrections to the Used-Service-Unit AVP when UMCH feature is supported | China Telecom,ZTE,Huawei | - |
| C3‑150409 | Corrections to the Used-Service-Unit AVP when UMCH feature is supported | China Telecom,ZTE,Huawei | - |
| C3‑150410 | Charging correlation identifier for the IP-CAN session in Gx | Ericsson, Huawei | - |
| C3‑150411 | Charging correlation identifier for the IP-CAN session in Gx | Huawei | - |
| C3‑150412 | Correction to the session establishment and notification URIs | Oracle Corporation | - |
| C3‑150413 | Correction to the PRA reporting | ZTE | - |
| C3‑150414 | LS on Enable MB2 procedures authorization | CT3 | - |
| C3‑150415 | Allowing for forward compatibility and miscellaneous corrections | Oracle Corporation | - |
| C3‑150416 | Corrections in the definition of MBMS Service Area AVP | Motorola Solutions Danmark A/S | - |
| C3‑150417 | Activation of an additional MBMS Bearer for a TMGI with already an active MBMS Bearer | Motorola Solutions Danmark A/S | - |
| C3‑150418 | Location information in case of non-3GPP access | Alcatel-Lucent | - |
| C3‑150419 | Location information in case of non-3GPP access | Alcatel-Lucent | - |
| C3‑150420 | Adding UE location information in aggregated RUCI reporting | Huawei | - |
| C3‑150421 | Conditional and Unconditional reporting restrictions | Ericsson | - |
| C3‑150422 | Correction to the PRA reporting | ZTE | - |
| C3‑150423 | Correction of TFT handling on default bearer | Huawei | - |
| C3‑150424 | LS on Enable MB2 procedures authorization | CT3 | - |
| C3‑150425 | Corrections in the definition of MBMS Service Area AVP | Motorola Solutions Danmark A/S | - |
| C3‑150426 | Adding UE location information in aggregated RUCI reporting | Huawei, China Telecom | - |
| C3‑150427 | Clarifying the congestion level value in AVP defintion | Huawei, China Telecom | - |
| C3‑150428 | Clarify the condition where the RCAF reports the RUCI | ZTE | - |
| C3‑150429 | Add the ToS-Traffic-Class AVP to the Rx to be sent by AF | Motorola Solutions Danmark A/S | - |
| C3‑150430 | Correction to the PRA reporting | ZTE | - |
| C3‑150431 | UE context removal in IP-CAN session termination procedure | Ericsson | - |
| C3‑150432 | Resolve the race conditions related to UE mobility between RCAFs | ZTE | - |
| C3‑150433 | LS on Flow ID supplied by AS for GCSE | Nokia Networks | - |
| C3‑150434 | Proposed Schedule for CT3#80 | CT3 Chairman | - |
| C3‑150435 | Relayed-Charge header field | Ericsson LM | - |
| C3‑150436 | Adding support for EVS codec | Nokia Networks | - |
| C3‑150437 | Clarify the condition where the RCAF reports the RUCI | ZTE | - |
| C3‑150438 | Resolve the race conditions related to UE mobility between RCAFs | ZTE | - |
| C3‑150439 | LS on new cause URI parameter value for IN numbers interworking | ORANGE | - |
| C3‑150440 | Applying drafting rules | Ericsson LM | - |
| C3‑150441 | Clarifying the congestion level value in AVP defintion | Huawei, China Telecom | - |
| C3‑150442 | Status of CT3 Work Items | CT3 Chairman | - |
| C3‑150443 | LS on Flow ID supplied by AS for GCSE | Nokia Networks | - |
| C3‑150444 | Reply LS on End-to-end QoS handling of MTSI | Ericsson | - |
| C3‑150445 | Adding UE location information in aggregated RUCI reporting | Huawei, China Telecom | - |
| C3‑150446 | LS on Flow ID supplied by GCS AS | Nokia Networks | - |
| C3‑150447 | Reply LS on End-to-end QoS handling of MTSI | Ericsson | - |
| C3‑150448 | Providing TS 29.217 v2.0.0 | Huawei | - |
| C3‑150449 | Presentation sheet for TS 29.217 | Huawei | - |
| C3‑150450 | Reply LS on End-to-end QoS handling of MTSI | Ericsson | - |
page generated from database: 2024-04-13 13:51:47