3GPP TDocs (written contributions) at meeting
Meeting: C3-76 - 2014-01-20 to 2014-01-24, Guangzhou
meeting id: C3-76 (click id for more info on this meeting)Click on the Tdoc to open its file.
| TDoc | Title | Source | Remarks |
|---|---|---|---|
| C3‑140001 | Agenda | Chairman | approved |
| C3‑140002 | Proposed Schedule for CT3#76 | CT3 Chairman | revised |
| C3‑140003 | Allocation of documents to agenda items (at Deadline) | CT3 Chairman | noted |
| C3‑140004 | Allocation of documents to agenda items (Start of Day 1) | CT3 Chairman | noted |
| C3‑140005 | Allocation of documents to agenda items (Start of Day 2) | CT3 Chairman | noted |
| C3‑140006 | Allocation of documents to agenda items (Start of Day 3) | CT3 Chairman | noted |
| C3‑140007 | Allocation of documents to agenda items (Start of Day 4) | CT3 Chairman | noted |
| C3‑140008 | Allocation of documents to agenda items (Start of Day 5) | CT3 Chairman | noted |
| C3‑140009 | Allocation of documents to agenda items (End of Day 5) | CT3 Chairman | revised |
| C3‑140010 | MTCe Small Data and Device Triggering Enhancements (MTCe-SDDTE) | Huawei, HiSilicon | noted |
| C3‑140011 | WID for CT aspects of Small Data and Device Triggering Enhancements | Huawei, HiSilicon | revised |
| C3‑140012 | Protocol enhancements for the support of device recall and replace procedure | Huawei, Intel | revised |
| C3‑140013 | Additional parameters’ transfer to TDF for the purpose of charging reports | Allot Communications, Huawei | revised |
| C3‑140014 | Additional parameters’ transfer to TDF for the purpose of charging reports | Allot Communications, Huawei | revised |
| C3‑140015 | Reference update of draft-vanelburg-dispatch-private-network-ind | NTT | revised |
| C3‑140016 | Reference update of draft-vanelburg-dispatch-private-network-ind | NTT | revised |
| C3‑140017 | Reference update of draft-vanelburg-dispatch-private-network-ind | NTT | revised |
| C3‑140018 | Reference update of draft-vanelburg-dispatch-private-network-ind | NTT | revised |
| C3‑140019 | Notation codes for the dynamic view table | NTT | revised |
| C3‑140020 | Notation codes for the dynamic view table | NTT | revised |
| C3‑140021 | Consideration on generic number over the ISUP interface supporting ITU-T Q.767 | NTT | postponed |
| C3‑140022 | Description about how to indicate the type of IOI | NTT | revised |
| C3‑140023 | The transit-ioi contains an indexed value | NTT | revised |
| C3‑140024 | Correction of Feature-Caps header fields example | NTT | agreed |
| C3‑140025 | User location information timestamp reporting | Huawei | revised |
| C3‑140026 | User location information timestamp reporting | Huawei | revised |
| C3‑140027 | User location information timestamp reporting in case of PMIP based 3GPP access | Huawei | rejected |
| C3‑140028 | User location information timestamp reporting in case of PMIP based 3GPP access | Huawei | rejected |
| C3‑140029 | Discussion on PCC session binding in LBO when the AF is in the HPLMN | Huawei | noted |
| C3‑140030 | Addition of charging characteristics transfer to the TDF | Huawei, Allot Communications | revised |
| C3‑140031 | Addition of charging characteristics transfer to the TDF | Huawei | revised |
| C3‑140032 | Reply LS on providing charging characteristics to the TDF | Huawei | revised |
| C3‑140033 | Discussion on enhancement to IMS restoration | Huawei | noted |
| C3‑140034 | Further consideration on security over XML based Rx | Huawei, Alcatel-Lucent, Verizon | revised |
| C3‑140035 | Further consideration on charging over XML based Rx | Huawei | revised |
| C3‑140036 | Editor’s Note cleanup proposal | Huawei, Alcatel-Lucent | revised |
| C3‑140037 | Figure consistency correction for PCRF addressing procedures | Huawei | revised |
| C3‑140038 | Reply LS on providing charging parameters to TDF | Huawei | revised |
| C3‑140039 | Correction on subscribing to credit management session failure | Huawei, Allot Communications | revised |
| C3‑140040 | Alignment correction on reference architecture and function entities | Huawei | revised |
| C3‑140041 | Alignment correction on general part in PCC procedures | Huawei | revised |
| C3‑140042 | Alignment correction on reference architecture and function entities | Huawei | revised |
| C3‑140043 | Alignment correction on S9 session procedures | Huawei | revised |
| C3‑140044 | Introduction of ULI reporting only when the UE is in 'CONNECTED' state | Huawei | revised |
| C3‑140045 | Introduction of ULI reporting at presence reporting area | Huawei | revised |
| C3‑140046 | Introduction of ULI reporting at presence reporting area | Huawei | revised |
| C3‑140047 | Introduction of ULI reporting at presence reporting area | Huawei | postponed |
| C3‑140048 | Introduction of ULI reporting at presence reporting area | Huawei | postponed |
| C3‑140049 | Introduction of device trigger recall/replace functions | Intel Corporation | revised |
| C3‑140050 | Proximity-based Services (ProSe) stage 2 status | Qualcomm Incorporated | noted |
| C3‑140051 | New WID on CT aspects of Proximity-based Services (ProSe) | Qualcomm Incorporated | revised |
| C3‑140052 | Correction of message examples related to the request routeing | NTT | revised |
| C3‑140053 | Figure showing two types of II-NNI | Fujitsu, NTT | noted |
| C3‑140054 | Addition of figure showing two types of II-NNI | Fujitsu, NTT | revised |
| C3‑140055 | Discussion on the signalling impact on the II-NNI between the home IMS network and the transit network providing IPXS | Fujitsu, NTT | noted |
| C3‑140056 | Access network information reporting in case of a TWAN access | China Telecom, Huawei | revised |
| C3‑140057 | Access network information reporting in case of a TWAN access | China Telecom, Huawei | revised |
| C3‑140058 | Clarification for application detection function of PCEF and TDF(R12 29.212) | China Mobile, Huawei | revised |
| C3‑140059 | Clarifications to the values of IP-CAN-Type in case of 3GPP2 access (29212 R8) | China Telecom,ZTE,Huawei | revised |
| C3‑140060 | Clarifications to the values of IP-CAN-Type in case of 3GPP2 access (29212 R9) | China Telecom,ZTE,Huawei | revised |
| C3‑140061 | Clarifications to the values of IP-CAN-Type in case of 3GPP2 access (29212 R10) | China Telecom,ZTE,Huawei | revised |
| C3‑140062 | Clarifications to the values of IP-CAN-Type in case of 3GPP2 access (29212 R11) | China Telecom,ZTE,Huawei | revised |
| C3‑140063 | Clarifications to the values of IP-CAN-Type in case of 3GPP2 access (29212 R12) | China Telecom,ZTE,Huawei | revised |
| C3‑140064 | Correction to the Event Report Indication over Sd interface(29212 R11) | China Telecom,ZTE, Allot Communications,Huawei | revised |
| C3‑140065 | Correction to the Event Report Indication over Sd interface(29212 R12) | China Telecom,ZTE, Allot Communications,Huawei | revised |
| C3‑140066 | APN-AMBR validation correction | ZTE | revised |
| C3‑140067 | APN-AMBR validation correction | ZTE | revised |
| C3‑140068 | APN-AMBR validation correction | ZTE | revised |
| C3‑140069 | APN-AMBR validation correction | ZTE | revised |
| C3‑140070 | APN-AMBR validation correction | ZTE | revised |
| C3‑140071 | Event-Report-Indication is not applicable to the S9 interface | ZTE | revised |
| C3‑140072 | Event-Report-Indication is not applicable to the S9 interface | ZTE | revised |
| C3‑140073 | Event-Report-Indication is not applicable to the S9 interface | ZTE | revised |
| C3‑140074 | Including uplink SDF filter in the PCC/QoS rule | ZTE | merged with C3-140112 to C3-140309 |
| C3‑140075 | Including uplink SDF filter in the PCC/QoS rule | ZTE | merged with C3-140112 to C3-140310 |
| C3‑140076 | Procedures of Protocol converter by using two TCP connections | ZTE | revised |
| C3‑140077 | The numbers of the protocol converter | ZTE | revised |
| C3‑140078 | Even trigger of local IP address and UDP port number change | ZTE | revised |
| C3‑140079 | Even trigger of local IP address and UDP port number change | ZTE | revised |
| C3‑140080 | Event-Report-Indication usage for EPC-routed scenario | ZTE | revised |
| C3‑140081 | Event-Report-Indication usage for EPC-routed scenario | ZTE | revised |
| C3‑140082 | Event-Report-Indication usage for EPC-routed scenario over S9a | ZTE | revised |
| C3‑140083 | Event-Report-Indication usage for EPC-routed scenario over S9a | ZTE | revised |
| C3‑140084 | Architecture figure update for ABC | ZTE, Allot Commuications | revised |
| C3‑140085 | Including Credit-Management-Status in the Subsession-Enforcement-Info AVP over S9 interface | ZTE, Allot communications | revised |
| C3‑140086 | Alignment correction on binding mechanism | ZTE | revised |
| C3‑140087 | Alignment correction on PCC procedures | ZTE | revised |
| C3‑140088 | Alignment correction on PCRF addressing | ZTE | revised |
| C3‑140089 | Conditional APN-related policy provisioning and enforcement | ZTE | merged with C3-140140 into C3-140306 |
| C3‑140090 | Conditional APN-related policy provisioning and enforcement in roaming case | ZTE | revised |
| C3‑140091 | Discussion: Support of IPv4/IPv6 interworking | Ericsson | noted |
| C3‑140092 | Draft references in CT3 specifications | Ericsson | noted |
| C3‑140093 | Alignment of IE name for CVO | Ericsson | revised |
| C3‑140094 | Support of terminating ICS calls | Ericsson | agreed |
| C3‑140095 | Explaining 1xx, 18x and 2xx-6xx responses | Ericsson | revised |
| C3‑140096 | Removing EN about security issues | Ericsson | revised |
| C3‑140097 | TF and IPXS clarifications | Ericsson | revised |
| C3‑140098 | Clarifying backward compatibility in the FC solution | Ericsson | revised |
| C3‑140099 | Resolving editor's note in B.2.1 | Ericsson | agreed |
| C3‑140100 | Decision proposal resolving EN in 9.4 | Ericsson | revised |
| C3‑140101 | Correcting the Registration of the user | Ericsson, Deutsche Telekom | revised |
| C3‑140102 | PANI corrections | Ericsson | revised |
| C3‑140103 | Originating roaming without loopback corrections | Ericsson, Deutsche Telekom | revised |
| C3‑140104 | Originating roaming with loopback corrections | Ericsson | revised |
| C3‑140105 | Additional minor corrections | Ericsson | agreed |
| C3‑140106 | VPLMN and HPLMN usage | Ericsson | revised |
| C3‑140107 | Additional IOI reference points | Ericsson | revised |
| C3‑140108 | PS to CS SRVCC access transfer scenarios, registration | Ericsson | revised |
| C3‑140109 | PS to CS SRVCC access transfer scenarios without loopback | Ericsson | revised |
| C3‑140110 | PS to CS SRVCC access transfer with loopback | Ericsson | revised |
| C3‑140111 | Incorrect AVP name for ULI age | Ericsson | revised |
| C3‑140112 | Inclusion of uplink service data flow filter in PCC/QoS rules | Ericsson | revised |
| C3‑140113 | Inclusion of uplink service data flow filter in PCC/QoS rules | Ericsson | revised |
| C3‑140114 | Default QoS handling for Fixed Broadband Access Convergence | Ericsson | revised |
| C3‑140115 | Event Trigger applicability for Fixed Broadband Access | Ericsson | revised |
| C3‑140116 | Completion of IP-CAN session procedures for Fixed Broadband Access Convergence | Ericsson | revised |
| C3‑140117 | PCC Rule Removal error handling | Ericsson, Cisco, ZTE | revised |
| C3‑140118 | PCC Rule Removal error handling | Ericsson, Cisco, ZTE | revised |
| C3‑140119 | Applicability of event triggers within the IP-CAN session | Ericsson | revised |
| C3‑140120 | Applicability of event triggers within the IP-CAN session | Ericsson | revised |
| C3‑140121 | Applicability of event triggers within the IP-CAN session | Ericsson | revised |
| C3‑140122 | Applicability of event triggers within the IP-CAN session | Ericsson | revised |
| C3‑140123 | Applicability of event triggers within the IP-CAN session | Ericsson | revised |
| C3‑140124 | Correction of IMS emergency procedures for SIP Registration | Ericsson | revised |
| C3‑140125 | Correction of IMS emergency procedures for SIP Registration | Ericsson | revised |
| C3‑140126 | Correction of IMS emergency procedures for SIP Registration | Ericsson | revised |
| C3‑140127 | Correction of IMS emergency procedures for SIP Registration | Ericsson | revised |
| C3‑140128 | Correction of IMS emergency procedures for SIP Registration | Ericsson | revised |
| C3‑140129 | Correction of IMS emergency procedures for SIP Registration | Ericsson | revised |
| C3‑140130 | Correction of IMS emergency procedures for SIP Registration | Ericsson | revised |
| C3‑140131 | Correction of IMS emergency procedures for SIP Registration | Ericsson | revised |
| C3‑140132 | LS on Registration of new TS 29.214 protocol identifiers in TS 29.230 | Ericsson | revised |
| C3‑140133 | Editor’s notes in section 6.2.4 | Intel Corporation, Alcatel-Lucent | revised |
| C3‑140134 | Support for both-way early media for UID | Alcatel-Lucent, Ericsson | revised |
| C3‑140135 | Calling Party Category mapping when no Calling Party Number | ORANGE | revised |
| C3‑140136 | Updating IMEI URN draft reference | BlackBerry | revised |
| C3‑140137 | Updating IMEI URN draft reference | BlackBerry | revised |
| C3‑140138 | Updating IMEI URN draft reference | BlackBerry | agreed |
| C3‑140139 | Updating IMEI URN draft reference | BlackBerry | agreed |
| C3‑140140 | APN policy info with condition | Cisco, Verizon | revised |
| C3‑140141 | Reporting the RAN/NAS release cause on Gx interface | Alcatel-Lucent | revised |
| C3‑140142 | Reporting the RAN/NAS release cause on Rx interface | Alcatel-Lucent | revised |
| C3‑140143 | CT aspects of Core Network Overload – User Location Information reporting improvements | Alcatel-Lucent | revised |
| C3‑140144 | Proposal section “description of scenarios” for TR29.949 Registration Option 2 | Deutsche Telekom | revised |
| C3‑140145 | Proposal section “Invocation of Services during Roaming in VPLMN” for TR29.949 | Deutsche Telekom | revised |
| C3‑140146 | Inter Operator Identifier improvement of section | Deutsche Telekom | revised |
| C3‑140147 | New Section on URI naming for TR 29.949 | Deutsche Telekom | revised |
| C3‑140148 | Proposal for Section " Insertion of service related media in the originating home network " | Deutsche Telekom | revised |
| C3‑140149 | nn | Deutsche Telekom | withdrawn |
| C3‑140150 | nn | Deutsche Telekom | withdrawn |
| C3‑140151 | Corrections to handling of PCC rules with application identifier | NSN | revised |
| C3‑140152 | Corrections to handling of PCC rules with application identifier | NSN | revised |
| C3‑140153 | Corrections to handling of PCC rules with application identifier | NSN | revised |
| C3‑140154 | Corrections to handling of PCC rules with application identifier | NSN | revised |
| C3‑140155 | Work on Group Communication System Enablers for LTE (GCSE_LTE) | NSN | noted |
| C3‑140156 | Possible work item to add procedures for ICE support to H.248 profiles | NSN | noted |
| C3‑140157 | New WID on ICE impacts on IMS H.248 profiles | NSN | revised |
| C3‑140158 | LS on BBF next hop use case | Broadband Forum | noted |
| C3‑140159 | LS on ALT-C for indication of IPv4 and IPv6 addresses in SDP | CT1 | noted |
| C3‑140160 | Reply LS on error handling when the PCC rule is removed due to the S-GW restoration support | CT4 | noted |
| C3‑140161 | S on New MBMS Heartbeat procedure | CT4 | noted |
| C3‑140162 | LS on SMSC Usage Restriction | CT4 | noted |
| C3‑140163 | LS on New version of ES 283 035 | ETS NTECH | noted |
| C3‑140164 | Reply LS on SMS Barring | SA1 | noted |
| C3‑140165 | Reply LS on uplink packet filters | SA2 | noted |
| C3‑140166 | Reply LS on providing Charging Characteristics to TDF | SA2 | replied to |
| C3‑140167 | LS on PCC with NAT in roaming scenarios | SA2 | replied to |
| C3‑140168 | LS on the handling of QoS parameters between IPv4 and IPv6 systems | SA4 | replied to |
| C3‑140169 | LS on providing parameters to TDF | SA5 | noted |
| C3‑140170 | Status of CT3 work items | Chairman | revised |
| C3‑140171 | Brief Notes from CT#62 relevant to CT3 | Chairman | noted |
| C3‑140172 | Draft Meeting Report from CT3#75 | Secretary | approved |
| C3‑140173 | Latest Version of 3GPP Workplan | Secretary | noted |
| C3‑140174 | Status of CT3 Specifications following CT#62 meeting | Secretary | noted |
| C3‑140175 | Meeting Calendar for 2014 - 2015 | Secretary | noted |
| C3‑140176 | Adjustment of SDP bandwidth modifier during IP version | NSN | revised |
| C3‑140177 | Introduction of device trigger recall/replace functions | Intel Corporation | withdrawn |
| C3‑140178 | Proposed Schedule for CT3#76 | CT3 Chairman | agreed |
| C3‑140179 | Reply to: LS on the handling of QoS parameters between IPv4 and IPv6 systems | current meeting | revised |
| C3‑140180 | CT aspects of Core Network Overload – User Location Information reporting improvements | Alcatel-Lucent | revised |
| C3‑140181 | WID for CT aspects of Small Data and Device Triggering Enhancements | Huawei, HiSilicon | endorsed |
| C3‑140182 | New WID on CT aspects of Proximity-based Services (ProSe) | Qualcomm Incorporated | endorsed |
| C3‑140183 | New WID on ICE impacts on IMS H.248 profiles | NSN | endorsed |
| C3‑140184 | Reference update of draft-vanelburg-dispatch-private-network-ind | NTT | agreed |
| C3‑140185 | Reference update of draft-vanelburg-dispatch-private-network-ind | NTT | agreed |
| C3‑140186 | Reference update of draft-vanelburg-dispatch-private-network-ind | NTT | agreed |
| C3‑140187 | Reference update of draft-vanelburg-dispatch-private-network-ind | NTT | agreed |
| C3‑140188 | Notation codes for the dynamic view table | NTT | agreed |
| C3‑140189 | Notation codes for the dynamic view table | NTT | agreed |
| C3‑140190 | Explaining 1xx, 18x and 2xx-6xx responses | Ericsson | agreed |
| C3‑140191 | Alignment of IE name for CVO | Ericsson | agreed |
| C3‑140192 | Updating IMEI URN draft reference | BlackBerry | agreed |
| C3‑140193 | Updating IMEI URN draft reference | BlackBerry | agreed |
| C3‑140194 | nn | breakout | withdrawn |
| C3‑140195 | nn | breakout | withdrawn |
| C3‑140196 | nn | breakout | withdrawn |
| C3‑140197 | nn | breakout | withdrawn |
| C3‑140198 | nn | breakout | withdrawn |
| C3‑140199 | nn | breakout | withdrawn |
| C3‑140200 | nn | breakout | withdrawn |
| C3‑140201 | nn | breakout | withdrawn |
| C3‑140202 | nn | breakout | withdrawn |
| C3‑140203 | nn | breakout | withdrawn |
| C3‑140204 | nn | breakout | withdrawn |
| C3‑140205 | nn | breakout | withdrawn |
| C3‑140206 | nn | breakout | withdrawn |
| C3‑140207 | nn | breakout | withdrawn |
| C3‑140208 | nn | breakout | withdrawn |
| C3‑140209 | nn | breakout | withdrawn |
| C3‑140210 | nn | breakout | withdrawn |
| C3‑140211 | nn | breakout | withdrawn |
| C3‑140212 | nn | breakout | withdrawn |
| C3‑140213 | nn | breakout | withdrawn |
| C3‑140214 | Further consideration on security over XML based Rx | Huawei, Alcatel-Lucent, Verizon | agreed |
| C3‑140215 | Further consideration on charging over XML based Rx | Huawei | revised |
| C3‑140216 | Editor’s Note cleanup proposal | Huawei, Alcatel-Lucent | agreed |
| C3‑140217 | The numbers of the protocol converter | ZTE | agreed |
| C3‑140218 | Procedures of Protocol converter by using two TCP connections | ZTE | revised |
| C3‑140219 | Alt-C for indication of IPv4 and IPv6 addresses in SDP | ORANGE | revised |
| C3‑140220 | Figure consistency correction for PCRF addressing procedures | Huawei | agreed |
| C3‑140221 | Editor’s notes in section 6.2.4 | Intel Corporation, Alcatel-Lucent | agreed |
| C3‑140222 | Correction to the Event Report Indication over Sd interface(29212 R11) | China Telecom,ZTE, Allot Communications,Huawei | agreed |
| C3‑140223 | Correction to the Event Report Indication over Sd interface(29212 R12) | China Telecom,ZTE, Allot Communications,Huawei | agreed |
| C3‑140224 | Even trigger of local IP address and UDP port number change | ZTE | agreed |
| C3‑140225 | Even trigger of local IP address and UDP port number change | ZTE | revised |
| C3‑140226 | Event-Report-Indication usage for EPC-routed scenario over S9a | ZTE | agreed |
| C3‑140227 | Event-Report-Indication usage for EPC-routed scenario | ZTE | agreed |
| C3‑140228 | Event-Report-Indication usage for EPC-routed scenario | ZTE | agreed |
| C3‑140229 | Event-Report-Indication usage for EPC-routed scenario over S9a | ZTE | agreed |
| C3‑140230 | Incorrect AVP name for ULI age | Ericsson | agreed |
| C3‑140231 | PCC Rule Removal error handling | Ericsson, Cisco, ZTE | agreed |
| C3‑140232 | PCC Rule Removal error handling | Ericsson, Cisco, ZTE | agreed |
| C3‑140233 | Reply on PCC session binding in LBO when the AF is in the HPLMN | CT3 | revised |
| C3‑140234 | Protocol enhancements for the support of device recall and replace procedure | Huawei, Intel | revised |
| C3‑140235 | Introduction of device trigger recall/replace functions | Intel Corporation | revised |
| C3‑140236 | Removing EN about security issues | Ericsson | revised |
| C3‑140237 | TF and IPXS clarifications | Ericsson | agreed |
| C3‑140238 | Clarifying backward compatibility in the FC solution | Ericsson | agreed |
| C3‑140239 | Decision proposal resolving EN in 9.4 | Ericsson | agreed |
| C3‑140240 | Description about how to indicate the type of IOI | NTT | revised |
| C3‑140241 | Correction of message examples related to the request routeing | NTT | agreed |
| C3‑140242 | Correcting the Registration of the user | Ericsson, Deutsche Telekom | revised |
| C3‑140243 | PANI corrections | Ericsson | agreed |
| C3‑140244 | Applicability of event triggers within the IP-CAN session | Ericsson | revised |
| C3‑140245 | Applicability of event triggers within the IP-CAN session | Ericsson | revised |
| C3‑140246 | Applicability of event triggers within the IP-CAN session | Ericsson | revised |
| C3‑140247 | Applicability of event triggers within the IP-CAN session | Ericsson | revised |
| C3‑140248 | Applicability of event triggers within the IP-CAN session | Ericsson | revised |
| C3‑140249 | LS on Registration of new TS 29.214 protocol identifiers in TS 29.230 | Ericsson | approved |
| C3‑140250 | Clarifications to the values of IP-CAN-Type in case of 3GPP2 access (29212 R8) | China Telecom,ZTE,Huawei | agreed |
| C3‑140251 | Clarifications to the values of IP-CAN-Type in case of 3GPP2 access (29212 R9) | China Telecom,ZTE,Huawei | agreed |
| C3‑140252 | Clarifications to the values of IP-CAN-Type in case of 3GPP2 access (29212 R10) | China Telecom,ZTE,Huawei | agreed |
| C3‑140253 | Clarifications to the values of IP-CAN-Type in case of 3GPP2 access (29212 R11) | China Telecom,ZTE,Huawei | agreed |
| C3‑140254 | Clarifications to the values of IP-CAN-Type in case of 3GPP2 access (29212 R12) | China Telecom,ZTE,Huawei | agreed |
| C3‑140255 | APN-AMBR validation correction | ZTE | agreed |
| C3‑140256 | APN-AMBR validation correction | ZTE | agreed |
| C3‑140257 | APN-AMBR validation correction | ZTE | agreed |
| C3‑140258 | APN-AMBR validation correction | ZTE | agreed |
| C3‑140259 | APN-AMBR validation correction | ZTE | agreed |
| C3‑140260 | Event-Report-Indication is not applicable to the S9 interface | ZTE | agreed |
| C3‑140261 | Event-Report-Indication is not applicable to the S9 interface | ZTE | agreed |
| C3‑140262 | Event-Report-Indication is not applicable to the S9 interface | ZTE | revised |
| C3‑140263 | Correction of IMS emergency procedures for SIP Registration | Ericsson | revised |
| C3‑140264 | Correction of IMS emergency procedures for SIP Registration | Ericsson | revised |
| C3‑140265 | Correction of IMS emergency procedures for SIP Registration | Ericsson | revised |
| C3‑140266 | Correction of IMS emergency procedures for SIP Registration | Ericsson | revised |
| C3‑140267 | Correction of IMS emergency procedures for SIP Registration | Ericsson | agreed |
| C3‑140268 | Correction of IMS emergency procedures for SIP Registration | Ericsson | agreed |
| C3‑140269 | Correction of IMS emergency procedures for SIP Registration | Ericsson | agreed |
| C3‑140270 | Correction of IMS emergency procedures for SIP Registration | Ericsson | agreed |
| C3‑140271 | nn | breakout | withdrawn |
| C3‑140272 | nn | breakout | withdrawn |
| C3‑140273 | nn | breakout | withdrawn |
| C3‑140274 | Originating roaming without loopback corrections | Ericsson, Deutsche Telekom | agreed |
| C3‑140275 | Originating roaming with loopback corrections | Ericsson | revised |
| C3‑140276 | VPLMN and HPLMN usage | Ericsson | revised |
| C3‑140277 | Additional IOI reference points | Ericsson | revised |
| C3‑140278 | PS to CS SRVCC access transfer scenarios, registration | Ericsson | revised |
| C3‑140279 | Addition of charging characteristics transfer to the TDF | Huawei, Allot Communications | revised |
| C3‑140280 | Addition of charging characteristics transfer to the TDF | Huawei | revised |
| C3‑140281 | Reply LS on providing charging characteristics to the TDF | Huawei | revised |
| C3‑140282 | Additional parameters’ transfer to TDF for the purpose of charging reports | Allot Communications, Huawei | revised |
| C3‑140283 | Reply LS on providing charging parameters to TDF | Huawei | withdrawn |
| C3‑140284 | Correction on subscribing to credit management session failure | Huawei, Allot Communications | revised |
| C3‑140285 | Architecture figure update for ABC | ZTE, Allot Commuications | agreed |
| C3‑140286 | Including Credit-Management-Status in the Subsession-Enforcement-Info AVP over S9 interface | ZTE, Allot communications | agreed |
| C3‑140287 | Alignment correction on reference architecture and function entities | Huawei | revised |
| C3‑140288 | Alignment correction on general part in PCC procedures | Huawei | agreed |
| C3‑140289 | Default QoS handling for Fixed Broadband Access Convergence | Ericsson | agreed |
| C3‑140290 | PS to CS SRVCC access transfer scenarios without loopback | Ericsson | revised |
| C3‑140291 | PS to CS SRVCC access transfer with loopback | Ericsson | revised |
| C3‑140292 | Proposal section “description of scenarios” for TR29.949 Registration Option 2 | Deutsche Telekom | revised |
| C3‑140293 | Proposal section “Invocation of Services during Roaming in VPLMN” for TR29.949 | Deutsche Telekom | revised |
| C3‑140294 | Inter Operator Identifier improvement of section | Deutsche Telekom | revised |
| C3‑140295 | New Section on URI naming for TR 29.949 | Deutsche Telekom | revised |
| C3‑140296 | Proposal for Section " Insertion of service related media in the originating home network " | Deutsche Telekom | revised |
| C3‑140297 | Addition of figure showing two types of II-NNI | Fujitsu, NTT | revised |
| C3‑140298 | Access network information reporting in case of a TWAN access | China Telecom, Huawei | revised |
| C3‑140299 | Access network information reporting in case of a TWAN access | China Telecom, Huawei | revised |
| C3‑140300 | Alignment correction on reference architecture and function entities | Huawei | agreed |
| C3‑140301 | Alignment correction on S9 session procedures | Huawei | agreed |
| C3‑140302 | Alignment correction on binding mechanism | ZTE | agreed |
| C3‑140303 | Alignment correction on PCC procedures | ZTE | revised |
| C3‑140304 | Alignment correction on PCRF addressing | ZTE | agreed |
| C3‑140305 | Event Trigger applicability for Fixed Broadband Access | Ericsson | revised |
| C3‑140306 | APN policy info with condition | Cisco, Verizon, Telecom Italia, ZTE, ORANGE | revised |
| C3‑140307 | Conditional APN-related policy provisioning and enforcement in roaming case | ZTE | postponed |
| C3‑140308 | Completion of IP-CAN session procedures for Fixed Broadband Access Convergence | Ericsson | agreed |
| C3‑140309 | Inclusion of uplink service data flow filter in PCC/QoS rules | Ericsson, ZTE | revised |
| C3‑140310 | Inclusion of uplink service data flow filter in PCC/QoS rules | Ericsson, ZTE | revised |
| C3‑140311 | Introduction of ULI reporting only when the UE is in 'CONNECTED' state | Huawei | agreed |
| C3‑140312 | Clarification for application detection function of PCEF and TDF(R12 29.212) | China Mobile, Huawei | agreed |
| C3‑140313 | Reporting the RAN/NAS release cause on Gx interface | Alcatel-Lucent | withdrawn |
| C3‑140314 | Revised WID on IMS-based Telepresence | Huawei | revised |
| C3‑140315 | Revised Work Item Description on CT Aspects of IMS Business Trunking for IP-PBX in Static Mode of Operation | Deutsche Telekom | endorsed |
| C3‑140316 | Reporting the RAN/NAS release cause on Rx interface | Alcatel-Lucent | withdrawn |
| C3‑140317 | Corrections to handling of PCC rules with application identifier | NSN | revised |
| C3‑140318 | Corrections to handling of PCC rules with application identifier | NSN | revised |
| C3‑140319 | Corrections to handling of PCC rules with application identifier | NSN | postponed |
| C3‑140320 | Corrections to handling of PCC rules with application identifier | NSN | postponed |
| C3‑140321 | The transit-ioi contains an indexed value | NTT | revised |
| C3‑140322 | New WID for Web Real Time Communication (WebRTC) Access to IMS | Huawei | noted |
| C3‑140323 | Calling Party Category mapping when no Calling Party Number | ORANGE | revised |
| C3‑140324 | Removing EN about security issues | Ericsson | agreed |
| C3‑140325 | Support for both-way early media for UID | Alcatel-Lucent, Ericsson | agreed |
| C3‑140326 | Calling Party Category mapping when no Calling Party Number | ORANGE | postponed |
| C3‑140327 | Adjustment of SDP bandwidth modifier during IP version | NSN | revised |
| C3‑140328 | Reply to: LS on the handling of QoS parameters between IPv4 and IPv6 systems | current meeting | revised |
| C3‑140329 | Alt-C for indication of IPv4 and IPv6 addresses in SDP | ORANGE | revised |
| C3‑140330 | Introduction of ULI reporting at presence reporting area | Huawei | revised |
| C3‑140331 | Introduction of ULI reporting at presence reporting area | Huawei | revised |
| C3‑140332 | ULI reporting at presence reporting area | |CT3 | postponed |
| C3‑140333 | User location information timestamp reporting | Huawei | revised |
| C3‑140334 | User location information timestamp reporting | Huawei | agreed |
| C3‑140335 | Even trigger of local IP address and UDP port number change | ZTE | agreed |
| C3‑140336 | Further consideration on charging over XML based Rx | Huawei | revised |
| C3‑140337 | Procedures of Protocol converter by using two TCP connections | ZTE | revised |
| C3‑140338 | Revised WID on IMS-based Telepresence | Huawei | endorsed |
| C3‑140339 | IMS Signalling Activated Trace | Vodafone | revised |
| C3‑140340 | Adjustment of SDP bandwidth modifier during IP version | NSN | revised |
| C3‑140341 | Description about how to indicate the type of IOI | NTT | agreed |
| C3‑140342 | The transit-ioi contains an indexed value | NTT, Ericsson | agreed |
| C3‑140343 | Correcting the Registration of the user | Ericsson, Deutsche Telekom | agreed |
| C3‑140344 | Originating roaming with loopback corrections | Ericsson | agreed |
| C3‑140345 | VPLMN and HPLMN usage | Ericsson | agreed |
| C3‑140346 | Additional IOI reference points | Ericsson | agreed |
| C3‑140347 | PS to CS SRVCC access transfer scenarios, registration | Ericsson | agreed |
| C3‑140348 | PS to CS SRVCC access transfer scenarios without loopback | Ericsson | agreed |
| C3‑140349 | PS to CS SRVCC access transfer with loopback | Ericsson | revised |
| C3‑140350 | Inter Operator Identifier improvement of section | Deutsche Telekom | agreed |
| C3‑140351 | New Section on URI naming for TR 29.949 | Deutsche Telekom | agreed |
| C3‑140352 | Proposal for Section " Insertion of service related media in the originating home network " | Deutsche Telekom | agreed |
| C3‑140353 | Addition of figure showing two types of II-NNI | Fujitsu, NTT | agreed |
| C3‑140354 | Adjustment of SDP bandwidth modifier during IP version | NSN | agreed |
| C3‑140355 | Reply to: LS on the handling of QoS parameters between IPv4 and IPv6 systems | current meeting | approved |
| C3‑140356 | Alignment correction on PCC procedures | ZTE | agreed |
| C3‑140357 | Event Trigger applicability for Fixed Broadband Access | Ericsson | agreed |
| C3‑140358 | CT aspects of Core Network Overload – User Location Information reporting improvements | Alcatel-Lucent | agreed |
| C3‑140359 | Introduction of ULI reporting at presence reporting area | Huawei | revised |
| C3‑140360 | Introduction of ULI reporting at presence reporting area | Huawei | agreed |
| C3‑140361 | Applicability of event triggers within the IP-CAN session | Ericsson | agreed |
| C3‑140362 | Applicability of event triggers within the IP-CAN session | Ericsson | agreed |
| C3‑140363 | Applicability of event triggers within the IP-CAN session | Ericsson | agreed |
| C3‑140364 | Applicability of event triggers within the IP-CAN session | Ericsson | agreed |
| C3‑140365 | Applicability of event triggers within the IP-CAN session | Ericsson | agreed |
| C3‑140366 | Event-Report-Indication is not applicable to the S9 interface | ZTE | agreed |
| C3‑140367 | Correction of IMS emergency procedures for SIP Registration | Ericsson | agreed |
| C3‑140368 | Correction of IMS emergency procedures for SIP Registration | Ericsson | agreed |
| C3‑140369 | Correction of IMS emergency procedures for SIP Registration | Ericsson | agreed |
| C3‑140370 | Correction of IMS emergency procedures for SIP Registration | Ericsson | agreed |
| C3‑140371 | Inclusion of uplink service data flow filter in PCC/QoS rules | Ericsson, ZTE | revised |
| C3‑140372 | Inclusion of uplink service data flow filter in PCC/QoS rules | Ericsson, ZTE | revised |
| C3‑140373 | Further consideration on charging over XML based Rx | Huawei | agreed |
| C3‑140374 | Protocol enhancements for the support of device recall and replace procedure | Huawei, Intel | revised |
| C3‑140375 | Introduction of device trigger recall/replace functions | Intel Corporation | agreed |
| C3‑140376 | User location information timestamp reporting | Huawei | agreed |
| C3‑140377 | Addition of charging characteristics transfer to the TDF | Huawei, Allot Communications | revised |
| C3‑140378 | Addition of charging characteristics transfer to the TDF | Huawei | revised |
| C3‑140379 | Reply LS on providing charging characteristics to the TDF | Huawei | revised |
| C3‑140380 | Procedures of Protocol converter by using two TCP connections | ZTE | agreed |
| C3‑140381 | Corrections to handling of PCC rules with application identifier | NSN | postponed |
| C3‑140382 | Corrections to handling of PCC rules with application identifier | NSN | postponed |
| C3‑140383 | Additional parameters’ transfer to TDF for the purpose of charging reports | Allot Communications, Huawei | revised |
| C3‑140384 | Alignment correction on reference architecture and function entities | Huawei | agreed |
| C3‑140385 | PS to CS SRVCC access transfer with loopback | Ericsson | agreed |
| C3‑140386 | Access network information reporting in case of a TWAN access | China Telecom, Huawei | revised |
| C3‑140387 | Access network information reporting in case of a TWAN access | China Telecom, Huawei | revised |
| C3‑140388 | IMS Signalling Activated Trace | Vodafone | endorsed |
| C3‑140389 | Introduction of ULI reporting at presence reporting area | Huawei | revised |
| C3‑140390 | Protocol enhancements for the support of device recall and replace procedure | Huawei, Intel | agreed |
| C3‑140391 | Addition of charging characteristics transfer to the TDF | Huawei, Allot Communications | agreed |
| C3‑140392 | Addition of charging characteristics transfer to the TDF | Huawei | agreed |
| C3‑140393 | Alt-C for indication of IPv4 and IPv6 addresses in SDP | ORANGE | endorsed |
| C3‑140394 | Additional parameters’ transfer to TDF for the purpose of charging reports | Allot Communications, Huawei | revised |
| C3‑140395 | APN policy info with condition | Cisco, Verizon, Telecom Italia, ZTE, ORANGE | revised |
| C3‑140396 | Proposal section “description of scenarios” for TR29.949 Registration Option 2 | Deutsche Telekom | agreed |
| C3‑140397 | Proposal section “Invocation of Services during Roaming in VPLMN” for TR29.949 | Deutsche Telekom | agreed |
| C3‑140398 | Introduction of ULI reporting at presence reporting area | Huawei | postponed |
| C3‑140399 | APN policy info with condition | Cisco, Verizon, Telecom Italia, ZTE, ORANGE | revised |
| C3‑140400 | Inclusion of uplink service data flow filter in PCC/QoS rules | Ericsson, ZTE | agreed |
| C3‑140401 | Inclusion of uplink service data flow filter in PCC/QoS rules | Ericsson, ZTE | agreed |
| C3‑140402 | nn | - | [not addressed] |
| C3‑140403 | Reply on PCC session binding in LBO when the AF is in the HPLMN | CT3 | revised |
| C3‑140404 | Additional parameters’ transfer to TDF for the purpose of charging reports | Allot Communications, Huawei | agreed |
| C3‑140405 | Correction on subscribing to credit management session failure | Huawei, Allot Communications | agreed |
| C3‑140406 | APN policy info with condition | Cisco, Verizon, Telecom Italia, ZTE, ORANGE | agreed |
| C3‑140407 | Reply on PCC session binding in LBO when the AF is in the HPLMN | CT3 | revised |
| C3‑140408 | Reply LS on providing charging characteristics to the TDF | Huawei | approved |
| C3‑140409 | Additional parameters’ transfer to TDF for the purpose of charging reports | Allot Communications, Huawei | agreed |
| C3‑140410 | Access network information reporting in case of a TWAN access | China Telecom, Huawei | agreed |
| C3‑140411 | Access network information reporting in case of a TWAN access | China Telecom, Huawei | revised |
| C3‑140412 | TR 24.802 WG agreed for approval by TSG | rapporteur | [not addressed] |
| C3‑140413 | TR 29.817 WG agreed for approval by TSG | rapporteur | [not addressed] |
| C3‑140414 | TR 29.949 latest draft | rapporteur | [not addressed] |
| C3‑140415 | Status of CT3 work items | Chairman | agreed |
| C3‑140416 | Reply on PCC session binding in LBO when the AF is in the HPLMN | CT3 | approved |
| C3‑140417 | Access network information reporting in case of a TWAN access | China Telecom, Huawei | agreed |
| C3‑140418 | Allocation of documents to agenda items (End of Day 5) | CT3 Chairman | noted |
page generated from database: 2024-04-13 13:51:47