3GPP TDocs (written contributions) at meeting
Meeting: C3-77 - 2014-05-19 to 2014-05-23, Phoenix
meeting id: C3-77 (click id for more info on this meeting)Click on the Tdoc to open its file.
TDoc | Title | Source | Remarks |
---|---|---|---|
C3‑142004 | Title | Source | - |
C3‑142005 | Title | Source | - |
C3‑142006 | Title | Source | - |
C3‑142007 | Title | Source | - |
C3‑142008 | Title | Source | - |
C3‑142009 | Status of CT3 work items | CT3 Chairman | - |
C3‑142010 | - | - | - |
C3‑142011 | - | - | - |
C3‑142012 | - | - | - |
C3‑142013 | - | - | - |
C3‑142014 | - | - | - |
C3‑142015 | Maintaining the rules for TFT filter setting | Ericsson | - |
C3‑142016 | - | - | - |
C3‑142017 | - | - | - |
C3‑142018 | - | - | - |
C3‑142019 | Draft references in CT3 specifications | Ericsson | - |
C3‑142020 | Conference creation | Ericsson | - |
C3‑142021 | Conference creation | Ericsson | - |
C3‑142022 | Conference creation | Ericsson | - |
C3‑142023 | Conference creation | Ericsson | - |
C3‑142024 | Conference creation | Ericsson | - |
C3‑142025 | Removal of CDIVN | Ericsson | - |
C3‑142026 | Removal of CDIVN | Ericsson | - |
C3‑142027 | Removal of CDIVN | Ericsson | - |
C3‑142028 | Removal of CDIVN | Ericsson | - |
C3‑142029 | Removal of CDIVN | Ericsson | - |
C3‑142030 | Removal of CDIVN | Ericsson | - |
C3‑142031 | Removal of CDIVN | Ericsson | - |
C3‑142032 | Removal of CDIVN | Ericsson | - |
C3‑142033 | Removal of CDIVN | Ericsson | - |
C3‑142034 | Reference update: RFC 7090 (draft-ietf-ecrit-psap-callback) | Ericsson | - |
C3‑142035 | Reference update: RFC 7090 (draft-ietf-ecrit-psap-callback) | Ericsson | - |
C3‑142036 | - | - | - |
C3‑142037 | - | - | - |
C3‑142038 | ?[H4] | ?[H5] | - |
C3‑142039 | ?[H4] | ?[H5] | - |
C3‑142040 | ?[H4] | ?[H5] | - |
C3‑142041 | ?[H4] | ?[H5] | - |
C3‑142043 | ?[H4] | ?[H5] | - |
C3‑142044 | ?[H4] | ?[H5] | - |
C3‑142045 | ?[H4] | ?[H5] | - |
C3‑142046 | ?[H4] | ?[H5] | - |
C3‑142047 | ?[H4] | ?[H5] | - |
C3‑142048 | NOTE 2: An IPv6 address provided over Rx matches an IPv6 prefix stored in the DRA binding if the IPv6 address belongs to the IPv6 (sub-)network prefix. | ZTE | - |
C3‑142049 | NOTE 2: An IPv6 address provided over Rx matches an IPv6 prefix stored in the DRA binding if the IPv6 address belongs to the IPv6 (sub-)network prefix. | ZTE | - |
C3‑142050 | NOTE 2: An IPv6 address provided over Rx matches an IPv6 prefix stored in the DRA binding if the IPv6 address belongs to the IPv6 (sub-)network prefix. | ZTE | - |
C3‑142051 | NOTE 2: An IPv6 address provided over Rx matches an IPv6 prefix stored in the DRA binding if the IPv6 address belongs to the IPv6 (sub-)network prefix. | ZTE | - |
C3‑142052 | NOTE 2: An IPv6 address provided over Rx matches an IPv6 prefix stored in the DRA binding if the IPv6 address belongs to the IPv6 (sub-)network prefix. | ZTE | - |
C3‑142053 | - | - | - |
C3‑142054 | - | - | - |
C3‑142055 | Corrections to access network information reporting during the PCC rule removal and bearer deactivation/IP-CAN session termination | ZTE, Oracle | - |
C3‑142056 | Corrections to access network information reporting during the PCC rule removal and bearer deactivation/IP-CAN session termination | ZTE, Oracle | - |
C3‑142057 | - | - | - |
C3‑142058 | - | - | - |
C3‑142059 | - | - | - |
C3‑142060 | - | - | - |
C3‑142061 | - | - | - |
C3‑142062 | - | - | - |
C3‑142063 | ?[H4] | ?[H5] | - |
C3‑142064 | ?[H4] | ?[H5] | - |
C3‑142065 | ?[H4] | ?[H5] | - |
C3‑142066 | ?[H4] | ?[H5] | - |
C3‑142067 | ?[H4] | ?[H5] | - |
C3‑142068 | - | - | - |
C3‑142069 | * * * End of Changes * * * | ZTE | - |
C3‑142070 | ?[H4] | ?[H5] | - |
C3‑142071 | ?[H4] | ?[H5] | - |
C3‑142072 | ?[H4] | ?[H5] | - |
C3‑142073 | ?[H4] | ?[H5] | - |
C3‑142074 | ?[H4] | ?[H5] | - |
C3‑142075 | [DRAFT][D1] Reply LS on TFT for default bearer | CT3 | - |
C3‑142077 | - | - | - |
C3‑142078 | ?[H4] | ?[H5] | - |
C3‑142079 | - | - | - |
C3‑142080 | Reply LS on handling of QoS parameters between IPv4 and IPv6 systems | C3 | - |
C3‑142081 | - | - | - |
C3‑142082 | - | - | - |
C3‑142083 | Revised WID on CT aspects of Proximity-based Services (ProSe) | Qualcomm Incorporated | - |
C3‑142084 | Proximity-based Services (ProSe) CT3 impacts | Qualcomm Incorporated | - |
C3‑142085 | GCSE stage 2 related discussion points | NSN | - |
C3‑142086 | ?[H4] | ?[H5] | - |
C3‑142087 | ?[H4] | ?[H5] | - |
C3‑142088 | ?[H4] | ?[H5] | - |
C3‑142089 | ?[H4] | ?[H5] | - |
C3‑142090 | Design Considerations for GCSE Diameter Application | NSN | - |
C3‑142091 | ?[H4] | ?[H5] | - |
C3‑142092 | - | - | - |
C3‑142093 | ?[H4] | ?[H5] | - |
C3‑142094 | ?[H4] | ?[H5] | - |
C3‑142095 | ?[H4] | ?[H5] | - |
C3‑142096 | ?[H4] | ?[H5] | - |
C3‑142097 | ?[H4] | ?[H5] | - |
C3‑142098 | ?[H4] | ?[H5] | - |
C3‑142099 | ?[H4] | ?[H5] | - |
C3‑142100 | ?[H4] | ?[H5] | - |
C3‑142101 | ?[H4] | ?[H5] | - |
C3‑142102 | ?[H4] | ?[H5] | - |
C3‑142103 | ?[H4] | ?[H5] | - |
C3‑142104 | ?[H4] | ?[H5] | - |
C3‑142105 | ?[H4] | ?[H5] | - |
C3‑142106 | [DRAFT][D1] LS on Allocation of Diameter Protocol Numbers for MB2-C Protocol for GCSE | CT3 | - |
C3‑142107 | [DRAFT][D1] LS on on Security for GCSE MB2 reference point | CT3 | - |
C3‑142108 | New WID on ICE impacts on IMS H.248 profiles | NSN | - |
C3‑142110 | Reply LS on GCSE QCIs and connected mode DRX | 3GPP TSG CT WG1 | - |
C3‑142111 | LS on handling of QoS parameters between IPv4 and IPv6 systems | 3GPP TSG CT WG1 | - |
C3‑142112 | Answer on: LS on eMBMS broadcast areas with EUTRAN Cell Granularity | RAN2 | - |
C3‑142113 | LS on device trigger recall and replace support | SA2 | - |
C3‑142114 | LS on device trigger recall and replace support | SA2 | - |
C3‑142115 | Reply LS on providing access network information for charging | SA2 | - |
C3‑142116 | LS on TFT for default bearer | SA2 | - |
C3‑142117 | Reply LS on providing access network information for charging | 3GPP SA2 | - |
C3‑142118 | Reply LS on new work item on “IMS Support for RTP/RTCP transport multiplexing | 3GPP SA WG3-LI | - |
C3‑142119 | Discussion on a possible XML schema structure | Alcatel-Lucent, Verizon | - |
C3‑142120 | ?[H4] | ?[H5] | - |
C3‑142121 | Clean-up of TR 29.817 based on MCC comments | Alcatel-Lucent, Huawei, Verizon | - |
C3‑142122 | - | - | - |
C3‑142123 | - | - | - |
C3‑142124 | - | - | - |
C3‑142125 | - | - | - |
C3‑142126 | - | - | - |
C3‑142127 | - | - | - |
C3‑142128 | - | - | - |
C3‑142129 | - | - | - |
C3‑142130 | - | - | - |
C3‑142131 | - | - | - |
C3‑142132 | - | - | - |
C3‑142133 | - | - | - |
C3‑142134 | - | - | - |
C3‑142135 | - | - | - |
C3‑142136 | - | - | - |
C3‑142137 | Discussion on session binding in visited access with AF located in HPLMN | Huawei | - |
C3‑142138 | NOTE 5:An IPv6 address provided over Rx matches an IPv6 prefix provided over Gx or S9 if the IPv6 address belongs to the IPv6 (sub-)network prefix. | Huawei | - |
C3‑142139 | ?[H4] | ?[H5] | - |
C3‑142140 | ?[H4] | ?[H5] | - |
C3‑142141 | ?[H4] | ?[H5] | - |
C3‑142142 | ?[H4] | ?[H5] | - |
C3‑142143 | ?[H4] | ?[H5] | - |
C3‑142144 | NOTE x: How the location information of the subscriber becomes available to the PCEF located in the IP Edge is out of the 3GPP scope. | Huawei | - |
C3‑142145 | - | - | - |
C3‑142146 | Clarification on bitmask | Huawei, NSN | - |
C3‑142147 | Discussion on application protocol over PC2 | Huawei | - |
C3‑142148 | - | - | - |
C3‑142149 | - | - | - |
C3‑142150 | - | - | - |
C3‑142151 | New WID on Overload Control for PCC based Diameter applications | Huawei | - |
C3‑142152 | - | - | - |
C3‑142153 | - | - | - |
C3‑142156 | Conference Call Minutes on Protocol for the GCSE MB2-C Reference Point | CT3 Chairman | - |
C3‑142157 | - | - | - |
C3‑142158 | Correction of the option item table format | NTT | - |
C3‑142159 | - | - | - |
C3‑142160 | Reference update of draft-vanelburg-dispatch-private-network-ind | NTT | - |
C3‑142161 | Reference update of draft-vanelburg-dispatch-private-network-ind | NTT | - |
C3‑142162 | Reference update of draft-vanelburg-dispatch-private-network-ind | NTT | - |
C3‑142163 | Reference update of draft-vanelburg-dispatch-private-network-ind | NTT | - |
C3‑142164 | Discussion on solution for editor's note related to draft-ietf-sipcore-rfc4244bis-00 | NTT | - |
C3‑142165 | - | - | - |
C3‑142166 | - | - | - |
C3‑142167 | - | - | - |
C3‑142168 | - | - | - |
C3‑142169 | ?[H4] | ?[H5] | - |
C3‑142170 | - | - | - |
C3‑142171 | - | - | - |
C3‑142172 | - | - | - |
C3‑142173 | - | - | - |
C3‑142174 | - | - | - |
C3‑142175 | - | - | - |
C3‑142176 | - | - | - |
C3‑142177 | INFOMeeting Calendar for 2014 - 2015 | Secretary | - |
C3‑142178 | - | - | - |
C3‑142179 | - | - | - |
C3‑142180 | - | - | - |
C3‑142181 | - | - | - |
C3‑142182 | - | - | - |
C3‑142183 | - | - | - |
C3‑142184 | Packet filter handling | Huawei | - |
C3‑142185 | Proposed schedule for CT3#77 | CT3 Chairman | - |
C3‑142186 | - | - | - |
C3‑142187 | New WID on Overload Control for PCC based Diameter applications | Huawei | - |
C3‑142188 | ?[H4] | ?[H5] | - |
C3‑142189 | ?[H4] | ?[H5] | - |
C3‑142190 | Correction on the ISUP parameter name in the mapping table | FUJITSU, NTT | - |
C3‑142191 | Correction on the ISUP parameter name in the mapping table | FUJITSU, NTT | - |
C3‑142192 | Correction on the ISUP parameter name in the mapping table | FUJITSU, NTT | - |
C3‑142193 | Correction on the ISUP parameter name in the mapping table | FUJITSU, NTT | - |
C3‑142194 | Correction on the ISUP parameter name in the mapping table | FUJITSU, NTT | - |
C3‑142195 | Reference update for "mp" header field parameter in History-Info header field | NTT | - |
C3‑142196 | Reference update for "mp" header field parameter in History-Info header field | NTT | - |
C3‑142197 | Reference update for "mp" header field parameter in History-Info header field | NTT | - |
C3‑142198 | - | - | - |
C3‑142199 | - | - | - |
C3‑142200 | - | - | - |
C3‑142201 | - | - | - |
C3‑142202 | Correcting the status of a major capability over II-NNI | NTT | - |
C3‑142203 | Reply LS on Removal of option to subscribe for a notification of diversion occurrence | 3GPP SA WG1 | - |
C3‑142204 | Reply LS to CT1 and CT3 on handling of QoS between Ipv4 and IPv6 systems | TSG SA WG4 | - |
C3‑142205 | LS on TR 26.924 Study on improved end-to-end QoS handling | 3GPP TSG SA WG4 | - |
C3‑142206 | LS on introducing the EVS codec in MTSI | TSG SA WG4 | - |
C3‑142207 | LS on Renaming of TWAN-SSID and TWAN-BSSID AVPs | SA5 | - |
C3‑142208 | Reply LS on XML based access of AF to the PCRF | SA3 | - |
C3‑142209 | LS on GCSE security | SA3 | - |
C3‑142210 | - | - | - |
C3‑142211 | Diameter Overload Control for Gx | Oracle, Huawei, Orange | - |
C3‑142212 | Diameter Overload Control for Rx | Oracle, Huawei, Orange | - |
C3‑142213 | ?[H4] | ?[H5] | - |
C3‑142214 | [DRAFT][D1] Reply LS on GCSE security | CT3 | - |
C3‑142215 | ?[H4] | ?[H5] | - |
C3‑142216 | ?[H4] | ?[H5] | - |
C3‑142217 | ?[H4] | ?[H5] | - |
C3‑142218 | ?[H4] | ?[H5] | - |
C3‑142219 | ?[H4] | ?[H5] | - |
C3‑142220 | ?[H4] | ?[H5] | - |
C3‑142221 | ?[H4] | ?[H5] | - |
C3‑142222 | LS on Allocation of Diameter Protocol Numbers for MB2-C Protocol for GCSE | C3 | - |
C3‑142223 | Correction to the subscription of specific actions in AA-Request | China Telecom, ZTE, Huawei | - |
C3‑142224 | Correction to the subscription of specific actions in AA-Request | China Telecom, ZTE, Huawei | - |
C3‑142225 | QoS rule only for access network information retrieve | ZTE | - |
C3‑142226 | - | - | - |
C3‑142227 | Correction to the call flows of access network information reporting | ZTE | - |
C3‑142228 | Correction to the call flows of access network information reporting | ZTE | - |
C3‑142229 | - | - | - |
C3‑142230 | - | - | - |
C3‑142231 | ?[H4] | ?[H5] | - |
C3‑142232 | ?[H4] | ?[H5] | - |
C3‑142233 | ?[H4] | ?[H5] | - |
C3‑142234 | ?[H4] | ?[H5] | - |
C3‑142235 | ?[H4] | ?[H5] | - |
C3‑142236 | ?[H4] | ?[H5] | - |
C3‑142237 | ?[H4] | ?[H5] | - |
C3‑142238 | - | - | - |
C3‑142239 | Corrections to include missed information in the non-seamless WLAN offload scenario | Ericsson, Huawei | - |
C3‑142240 | Enhancement to NSWO traffic functionality | Huawei | - |
C3‑142241 | Introduction of ULI reporting at presence reporting area | Huawei, Ericsson, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, China Telecom | - |
C3‑142242 | - | - | - |
C3‑142243 | - | - | - |
C3‑142244 | II-NNI traversal scenario identification | Ericsson | - |
C3‑142245 | New WID on Indication of NNI Routeing scenarios in SIP requests | Ericsson | - |
C3‑142246 | ?[H4] | ?[H5] | - |
C3‑142247 | ?[H4] | ?[H5] | - |
C3‑142248 | ?[H4] | ?[H5] | - |
C3‑142249 | ?[H4] | ?[H5] | - |
C3‑142250 | ?[H4] | ?[H5] | - |
C3‑142251 | - | - | - |
C3‑142252 | Ix requirements/procedures for e2e media security | NSN | - |
C3‑142253 | - | - | - |
C3‑142254 | ICE support for Mn interface stage 2 | Huawei, NSN | - |
C3‑142255 | ICE support for MSC Server enhanced for ICS | Huawei, NSN | - |
C3‑142256 | - | - | - |
C3‑142257 | Improvement on the format of option item tables | NTT | - |
C3‑142258 | Correction of the option item table format | NTT | - |
C3‑142259 | Proposed schedule for CT3#77 | CT3 Chairman | - |
C3‑142260 | NOTE 2: An IPv6 address provided over Rx matches an IPv6 prefix stored in the DRA binding if the IPv6 address belongs to the IPv6 (sub-)network prefix. | ZTE | - |
C3‑142261 | NOTE 2: An IPv6 address provided over Rx matches an IPv6 prefix stored in the DRA binding if the IPv6 address belongs to the IPv6 (sub-)network prefix. | ZTE | - |
C3‑142262 | NOTE 2: An IPv6 address provided over Rx matches an IPv6 prefix stored in the DRA binding if the IPv6 address belongs to the IPv6 (sub-)network prefix. | ZTE | - |
C3‑142263 | NOTE 3: An IPv6 address provided over Rx matches an IPv6 prefix stored in the DRA binding if the IPv6 address belongs to the IPv6 (sub-)network prefix. | ZTE | - |
C3‑142264 | NOTE 3: An IPv6 address provided over Rx matches an IPv6 prefix stored in the DRA binding if the IPv6 address belongs to the IPv6 (sub-)network prefix. | ZTE | - |
C3‑142265 | Application detection and control in the roaming case | ZTE | - |
C3‑142266 | Application detection and control in the roaming case | ZTE | - |
C3‑142267 | Corrections to handling of PCC rules with application identifier | Huawei | - |
C3‑142268 | - | - | - |
C3‑142269 | Corrections to handling of PCC rules with application identifier | Huawei | - |
C3‑142270 | - | - | - |
C3‑142271 | Corrections to trigger recall and replace procedures | Ericsson | - |
C3‑142272 | ?[H4] | ?[H5] | - |
C3‑142273 | ?[H4] | ?[H5] | - |
C3‑142274 | ?[H4] | ?[H5] | - |
C3‑142275 | ?[H4] | ?[H5] | - |
C3‑142276 | ?[H4] | ?[H5] | - |
C3‑142277 | ?[H4] | ?[H5] | - |
C3‑142278 | - | - | - |
C3‑142279 | - | - | - |
C3‑142280 | - | - | - |
C3‑142281 | Remove the IP domain Id by the V-PCRF | China Telecom, ZTE, Huawei | - |
C3‑142282 | Remove the IP domain Id by the V-PCRF | China Telecom, ZTE, Huawei | - |
C3‑142283 | - | - | - |
C3‑142284 | - | - | - |
C3‑142285 | - | - | - |
C3‑142286 | NOTE 5:An IPv6 address provided over Rx matches an IPv6 prefix provided over Gx or S9 if the IPv6 address belongs to the IPv6 (sub-)network prefix. | Huawei | - |
C3‑142288 | - | - | - |
C3‑142289 | Correcting IP addresses on OMR call flow examples | Huawei, NSN | - |
C3‑142290 | Correcting IP addresses on OMR call flow examples | Huawei, NSN | - |
C3‑142291 | Additional clarifications on solution and conclusion clauses | Ericsson | - |
C3‑142292 | - | - | - |
C3‑142293 | Reference update for overload control | Alcatel-Lucent | - |
C3‑142294 | Reference update for overload control | Alcatel-Lucent | - |
C3‑142295 | ?[H4] | ?[H5] | - |
C3‑142296 | ?[H4] | ?[H5] | - |
C3‑142297 | - | - | - |
C3‑142298 | - | - | - |
C3‑142299 | NOTE 2: An IPv6 address provided over Rx matches an IPv6 prefix stored in the DRA binding if the IPv6 address belongs to the IPv6 (sub-)network prefix. | ZTE | - |
C3‑142300 | NOTE 2: An IPv6 address provided over Rx matches an IPv6 prefix stored in the DRA binding if the IPv6 address belongs to the IPv6 (sub-)network prefix. | ZTE | - |
C3‑142301 | NOTE 2: An IPv6 address provided over Rx matches an IPv6 prefix stored in the DRA binding if the IPv6 address belongs to the IPv6 (sub-)network prefix. | ZTE | - |
C3‑142302 | NOTE 3: An IPv6 address provided over Rx matches an IPv6 prefix stored in the DRA binding if the IPv6 address belongs to the IPv6 (sub-)network prefix. | ZTE | - |
C3‑142303 | NOTE 3: An IPv6 address provided over Rx matches an IPv6 prefix stored in the DRA binding if the IPv6 address belongs to the IPv6 (sub-)network prefix. | ZTE | - |
C3‑142304 | - | - | - |
C3‑142305 | QoS rule only for access network information retrieve | ZTE | - |
C3‑142306 | Corrections to access network information reporting during the IP-CAN session termination | ZTE | - |
C3‑142307 | Corrections to access network information reporting during IP-CAN session termination | ZTE | - |
C3‑142308 | ?[H4] | ?[H5] | - |
C3‑142309 | ?[H4] | ?[H5] | - |
C3‑142310 | ?[H4] | ?[H5] | - |
C3‑142311 | ?[H4] | ?[H5] | - |
C3‑142312 | ?[H4] | ?[H5] | - |
C3‑142313 | ?[H4] | ?[H5] | - |
C3‑142314 | ?[H4] | ?[H5] | - |
C3‑142315 | Reuse of AN-Trusted AVP to cover Trusted and Untrusted RAT separately | Allot Communications, Huawei, ZTE | - |
C3‑142316 | Corrections to handling of PCC rules with application identifier | Huawei | - |
C3‑142317 | Corrections to handling of PCC rules with application identifier | Huawei | - |
C3‑142318 | ?[H4] | ?[H5] | - |
C3‑142319 | - | - | - |
C3‑142320 | - | - | - |
C3‑142321 | Onetime reporting of the present Access Network Information | China Telecom, Huawei | - |
C3‑142322 | Onetime reporting of the present Access Network Information | China Telecom, Huawei | - |
C3‑142323 | NOTE 5:An IPv6 address provided over Rx matches an IPv6 prefix provided over Gx or S9 if the IPv6 address belongs to the IPv6 (sub-)network prefix. | Huawei | - |
C3‑142324 | ?[H4] | ?[H5] | - |
C3‑142325 | ?[H4] | ?[H5] | - |
C3‑142326 | ?[H4] | ?[H5] | - |
C3‑142327 | ?[H4] | ?[H5] | - |
C3‑142328 | ?[H4] | ?[H5] | - |
C3‑142329 | ?[H4] | ?[H5] | - |
C3‑142330 | - | - | - |
C3‑142331 | * * * End of Changes * * * | ZTE | - |
C3‑142332 | ?[H4] | ?[H5] | - |
C3‑142333 | Reply LS on GCSE security | CT3 | - |
C3‑142334 | - | - | - |
C3‑142335 | - | - | - |
C3‑142336 | ICE support of IBCF for Ix interface stage 2 | Huawei, NSN | - |
C3‑142337 | ICE support for Ix towards SIP-I based CS CN | Huawei, NSN | - |
C3‑142338 | Revised WID on P-CSCF_RES WID Update | Alcatel-Lucent | - |
C3‑142339 | Correction to the PCRF selection and discovery by DRA | ZTE | - |
C3‑142340 | Correction to the PCRF selection and discovery by DRA | ZTE | - |
C3‑142341 | Usage clarification on QoS-Negotiation AVP | Huawei | - |
C3‑142342 | Session binding in visited access with AF located in HPLMN | Huawei | - |
C3‑142343 | Identifying the II-NNI traversal scenario | Ericsson | - |
C3‑142344 | ?[H4] | ?[H5] | - |
C3‑142345 | - | - | - |
C3‑142346 | - | - | - |
C3‑142347 | - | - | - |
C3‑142348 | IPv6 address for PCRF selection and discovery | ZTE | - |
C3‑142349 | IPv6 address in IP-CAN session establishment | ZTE | - |
C3‑142350 | Reply LS on GCSE security | C3 | - |
C3‑142351 | - | - | - |
C3‑142352 | Status of CT3 work items | CT3 Chairman | - |
C3‑142353 | Diameter Overload Control impacts on PCC | Oracle, Huawei, Orange, Acision, ZTE | - |
page generated from database: 2024-09-26 11:02:35