3GPP TDocs (written contributions) at meeting
Meeting: N4-26 - 2005-02-14 to 2005-02-18, Sydney
meeting id: N4-26 (click id for more info on this meeting)Click on the Tdoc to open its file.
| TDoc | Title | Source | Remarks |
|---|---|---|---|
| N4‑050001 | Preliminary Agenda for CN4 #26 | Chairman, TSG-CN WG4 | - |
| N4‑050003 | Proposed Agenda for CN4 #26 status at document deadline | Chairman, TSG-CN WG4 | - |
| N4‑050005 | Proposed allocation of documents to agenda items for TSG-CN WG4 Meeting #26, status after document deadline | Chairman, TSG-CN WG4 | - |
| N4‑050006 | - | - | - |
| N4‑050007 | List of approved output documents | Chairman, TSG-CN WG4 | - |
| N4‑050008 | - | - | - |
| N4‑050009 | - | - | - |
| N4‑050010 | Response LS to GSMA IREG on Reservation of two new sub domains under ".3gppnetwork.org" | TSG CN | - |
| N4‑050011 | Reply LS on Security aspects of early IMS systems | 3GPP TSG CN1 | - |
| N4‑050012 | LS on a new Enhanced NSAPI IE for MBMS | CN1 | - |
| N4‑050013 | LS on Assignment of the Diameter codes and identifiers for the Rel-6 Gx interface | CN3 | - |
| N4‑050014 | LS on Allocation of 3GPP specific AVP numbers and Experimental Result Codes for Gmb interface | CN3 | - |
| N4‑050015 | Reply LS on MBMS information elements | CN3 | - |
| N4‑050016 | LS on completion of network initiated SCUDIF support | CN3 | - |
| N4‑050017 | LS on Cooperation on TISPAN NGN supplementary services | 3GPP WG CN3 | - |
| N4‑050018 | LS on MBMS Information Elements over Iu interface | RAN3 | - |
| N4‑050019 | REPLY LS on 23.060 CR on RIM-NACC clean up | RAN3 | - |
| N4‑050020 | LS Response on LS on Indication of Selected CN operator in connected mode in Shared Networks | RAN3 | - |
| N4‑050021 | Reply on LS on GERAN Assumptions on common MBMS Information Elements | SA2 | - |
| N4‑050022 | LS on Security Aspects of Early IMS Systems | SA2 | - |
| N4‑050023 | LS on CRs needed for Circuit Switched Voice-Video Switching | SA 2 | - |
| N4‑050024 | Reply LS on MBMS Information Element coding | SA2 | - |
| N4‑050025 | Reply on LS on GERAN Assumptions on common MBMS Information Elements | SA2 | - |
| N4‑050026 | Reply LS on Revisiting forwards compatibility towards TLS based access security | TSG_SA WG2. | - |
| N4‑050027 | LS on Control of simultaneous accesses for WLAN 3GPP IP access | SA3 | - |
| N4‑050028 | LS on impacts of early IMS security mechanisms | SA3 | - |
| N4‑050029 | Reply to LS on The relationship between Scenario 2 and Scenario 3 authentication procedures | SA3 | - |
| N4‑050030 | Reply to LS on Need for the IMSI at the PDG | SA3 | - |
| N4‑050031 | LS on GUP Security and the Proposed Changes to TS 23.240 | SA3 | - |
| N4‑050032 | LS on Session Repetition | SA4 | - |
| N4‑050033 | LS on Clarifications on AMR | SA4 | - |
| N4‑050034 | Reply to TISPAN on Workshop on “IMS over Fixed Access” | TSG SA | - |
| N4‑050035 | [A9] Enter the source of the CR. This is either (a) one or several companies or, (b) if a (sub)working group has already reviewed and agreed the CR, then list the group as the source. | NEC | - |
| N4‑050036 | [A9] Enter the source of the CR. This is either (a) one or several companies or, (b) if a (sub)working group has already reviewed and agreed the CR, then list the group as the source. | NEC | - |
| N4‑050037 | [A9] Enter the source of the CR. This is either (a) one or several companies or, (b) if a (sub)working group has already reviewed and agreed the CR, then list the group as the source. | NEC | - |
| N4‑050039 | Discussion on Problem found in GTP with re^^using RAI IE to convey MNC & MCC to GGSNs | Vodafone | - |
| N4‑050040 | Corrections to table 14.2 | - | - |
| N4‑050041 | Corrections to table 14.2 | - | - |
| N4‑050042 | Corrections to table 14.2 | - | - |
| N4‑050043 | - | Vodafone, Nokia, Ericsson, Nortel | - |
| N4‑050044 | - | Vodafone, Nokia, Ericsson, Nortel | - |
| N4‑050045 | - | Vodafone, Nokia, Ericsson, Nortel | - |
| N4‑050046 | Completion of specification of UMTS Packages | - | - |
| N4‑050047 | - | - | - |
| N4‑050048 | - | - | - |
| N4‑050049 | Correction of implied option for Embedded Signals and Events | - | - |
| N4‑050050 | Correction of implied option for Embedded Signals and Events | - | - |
| N4‑050051 | - | Vodafone, Ericsson, Nokia, Nortel | - |
| N4‑050052 | - | Vodafone, Ericsson, Nokia, Nortel | - |
| N4‑050054 | - | Vodafone, Ericsson, Nokia, Nortel | - |
| N4‑050055 | - | Vodafone, Ericsson, Nokia, Nortel | - |
| N4‑050056 | Removal of the Multiplex descriptor | - | - |
| N4‑050057 | Removal of the Multiplex descriptor | - | - |
| N4‑050058 | Removal of the Modem descriptor | - | - |
| N4‑050059 | Removal of the Modem descriptor | - | - |
| N4‑050060 | - | Vodafone, Ericsson, Nokia, Nortel | - |
| N4‑050061 | - | Vodafone, Ericsson, Nokia, Nortel | - |
| N4‑050062 | - | Vodafone, Ericsson, Nokia, Nortel | - |
| N4‑050063 | - | Vodafone, Ericsson, Nokia, Nortel | - |
| N4‑050064 | - | Vodafone, Ericsson, Nokia, Nortel | - |
| N4‑050066 | Open issues in 29.240 | Nokia | - |
| N4‑050067 | GAA Error Codes | - | - |
| N4‑050068 | - | Nokia | - |
| N4‑050069 | - | Nokia | - |
| N4‑050070 | - | - | - |
| N4‑050071 | - | - | - |
| N4‑050072 | - | - | - |
| N4‑050073 | - | Nokia | - |
| N4‑050074 | - | Nokia | - |
| N4‑050075 | - | Nokia | - |
| N4‑050076 | - | Nokia | - |
| N4‑050077 | - | Nokia | - |
| N4‑050078 | - | Nokia | - |
| N4‑050079 | - | Nokia | - |
| N4‑050080 | - | Nokia | - |
| N4‑050081 | - | Nokia | - |
| N4‑050082 | - | Nokia | - |
| N4‑050083 | Removal of the Error Descriptor usage in NotifyRequest | - | - |
| N4‑050084 | Removal of the Error Descriptor usage in NotifyRequest | - | - |
| N4‑050085 | Updating incomplete parameter definition for MGW Resource congestion handling procedures | - | - |
| N4‑050086 | Updating incomplete parameter definition for MGW Resource congestion handling procedures | - | - |
| N4‑050087 | Removal of Signals on ROOT | - | - |
| N4‑050088 | Removal of usage of Stream ID in Topology descriptor | - | - |
| N4‑050089 | H.248.1 version contradiction | - | - |
| N4‑050090 | Directionality of tones and announcements | - | - |
| N4‑050091 | Directionality of tones and announcements | - | - |
| N4‑050092 | - | Vodafone | - |
| N4‑050093 | Clarification of the TMGI | - | - |
| N4‑050094 | Only one AV from HSS to BSF | - | - |
| N4‑050095 | Clarification of LifeTime/ExpiryTime terminology | - | - |
| N4‑050096 | - | Nokia | - |
| N4‑050097 | - | Nokia | - |
| N4‑050098 | - | Nokia | - |
| N4‑050099 | - | Alcatel | - |
| N4‑050100 | - | Alcatel | - |
| N4‑050101 | - | Alcatel | - |
| N4‑050102 | DISC, Packetisation time of PCM codec speech over Nb | ALCATEL | - |
| N4‑050103 | - | Alcatel | - |
| N4‑050104 | - | Alcatel | - |
| N4‑050105 | - | Alcatel | - |
| N4‑050106 | - | Alcatel | - |
| N4‑050107 | - | Alcatel | - |
| N4‑050108 | - | Alcatel | - |
| N4‑050109 | - | T-Mobile, Siemens | - |
| N4‑050110 | Operator Determined Barring HPLMN data | Siemens | - |
| N4‑050111 | - | Siemens | - |
| N4‑050112 | Preventing Endless Relaying of Messages | Siemens, Vodafone | - |
| N4‑050113 | - | Siemens, Vodafone | - |
| N4‑050114 | - | Siemens, Vodafone | - |
| N4‑050115 | - | - | - |
| N4‑050116 | - | Siemens | - |
| N4‑050117 | - | Lucent Technologies, Nortel, FT, Ericsson, Vodafone | - |
| N4‑050118 | - | Lucent Technologies, Nortel, FT, Ericsson, Vodafone | - |
| N4‑050119 | Align UML Model and the XML schema for Public Identity | - | - |
| N4‑050120 | Align UML Model and the XML schema for Public Identity | - | - |
| N4‑050121 | Incorrect AVP Code for Public-Identity in Table 6.3.1 | - | - |
| N4‑050122 | - | Lucent Technologies | - |
| N4‑050123 | Removal of Wn reference point Definition from the Stage 3 | - | - |
| N4‑050124 | Wa Interface RADIUS profile corrections | - | - |
| N4‑050125 | Wd Interface RADIUS profile corrections | - | - |
| N4‑050126 | - | TeliaSonera | - |
| N4‑050127 | Information Element corrections on Wd | - | - |
| N4‑050128 | Correction of partly implemented CR 108 | - | - |
| N4‑050129 | GUP security | Lucent Technologies, Arnaud SAHUGUET, Bell Labs research | - |
| N4‑050130 | Request for latest Liberty documents re: “data services” | Lucent Technologies, Arnaud SAHUGUET, Bell Labs research | - |
| N4‑050131 | Schema management for 3GPP GUP | Lucent Technologies, Arnaud SAHUGUET, Bell Labs research | - |
| N4‑050132 | Update of references to PS charging specification | - | - |
| N4‑050133 | - | Orange | - |
| N4‑050134 | Discussion on the usage of possible reason code for the Network initiates deregistration toward the S-CSCF | Orange | - |
| N4‑050135 | - | Alcatel | - |
| N4‑050136 | - | Alcatel | - |
| N4‑050137 | Providing the BM-SC with approximate UE location information at MBMS context activation | - | - |
| N4‑050138 | - | Vodafone | - |
| N4‑050139 | - | Ericsson | - |
| N4‑050140 | - | Ericsson | - |
| N4‑050141 | - | Ericsson | - |
| N4‑050142 | - | - | - |
| N4‑050143 | - | Ericsson | - |
| N4‑050144 | - | - | - |
| N4‑050145 | - | - | - |
| N4‑050146 | - | - | - |
| N4‑050147 | Avoiding undesired deregistration | - | - |
| N4‑050148 | Avoiding undesired deregistration | - | - |
| N4‑050149 | - | Nokia | - |
| N4‑050150 | - | Nokia | - |
| N4‑050151 | Sh Diameter AVP Mapping Correction | - | - |
| N4‑050152 | Sh Diameter AVP Mapping Correction | - | - |
| N4‑050153 | - | Nokia | - |
| N4‑050154 | TEL-URI reference update | - | - |
| N4‑050156 | Removal of AMR-WB codec | - | - |
| N4‑050157 | Correction of the condition for the insertion of a transcoder | - | - |
| N4‑050158 | Correction of the condition for the insertion of a transcoder | - | - |
| N4‑050159 | - | HP, Ericsson | - |
| N4‑050160 | - | - | - |
| N4‑050161 | - | Nokia | - |
| N4‑050162 | - | Source:?[H9] | - |
| N4‑050163 | - | Source:?[H9] | - |
| N4‑050164 | - | HuaWei | - |
| N4‑050165 | - | HuaWei | - |
| N4‑050166 | Editorial corrections | - | - |
| N4‑050167 | - | - | - |
| N4‑050168 | - | Huawei | - |
| N4‑050169 | - | - | - |
| N4‑050170 | Correction of Type values | - | - |
| N4‑050171 | GUP Security Sections | Ericsson | - |
| N4‑050172 | Clarification of GUP Resource Identifier | Ericsson | - |
| N4‑050173 | GUP Editorial and References | Ericsson | - |
| N4‑050174 | DST Tables | Ericsson | - |
| N4‑050175 | GUP HSS IMS Data | Ericsson | - |
| N4‑050177 | - | Nokia | - |
| N4‑050178 | - | - | - |
| N4‑050179 | - | Nokia | - |
| N4‑050180 | - | Ericsson | - |
| N4‑050181 | - | Ericsson | - |
| N4‑050182 | - | Ericsson | - |
| N4‑050183 | - | - | - |
| N4‑050184 | Addition of RIM Routing Address for GERAN | - | - |
| N4‑050185 | - | Ericsson | - |
| N4‑050186 | - | - | - |
| N4‑050187 | - | - | - |
| N4‑050188 | Introduction of CAMEL support for Trunk Originated Calls | Nortel Networks | - |
| N4‑050189 | - | - | - |
| N4‑050190 | - | - | - |
| N4‑050191 | - | Nortel | - |
| N4‑050192 | - | Nortel | - |
| N4‑050193 | - | Nortel | - |
| N4‑050194 | - | Nortel | - |
| N4‑050195 | - | Nortel | - |
| N4‑050196 | - | Nortel | - |
| N4‑050197 | Distribution of Cipher key and integrity Key | - | - |
| N4‑050198 | - | Nortel | - |
| N4‑050199 | - | Nortel | - |
| N4‑050200 | - | Nortel | - |
| N4‑050201 | - | Nortel | - |
| N4‑050202 | - | Nortel | - |
| N4‑050204 | Allocations for Gx interface | - | - |
| N4‑050205 | Solving contradiction for Release Cause in Release Bearer Procedure between stage 2 and stage 3 | - | - |
| N4‑050206 | Solving contradiction for Release Cause in Release Bearer Procedure between stage 2 and stage 3 | - | - |
| N4‑050207 | - | Nokia | - |
| N4‑050208 | - | Nokia | - |
| N4‑050209 | - | - | - |
| N4‑050210 | - | Ericsson | - |
| N4‑050211 | Management Based Activation Impacts | - | - |
| N4‑050212 | Management Based Activation Impacts | - | - |
| N4‑050216 | Page: 1 | LM Ericsson, Vodafone | - |
| N4‑050217 | Page: 1 | LM Ericsson, Vodafone | - |
| N4‑050218 | - | LM Ericsson, Vodafone | - |
| N4‑050219 | - | LM Ericsson, Vodafone | - |
| N4‑050220 | Page: 1 | LM Ericsson, Vodafone | - |
| N4‑050221 | Page: 1 | LM Ericsson, Vodafone | - |
| N4‑050222 | Service Change Reasons | - | - |
| N4‑050223 | Service Change Reasons | - | - |
| N4‑050224 | Page: 1 | LM Ericsson, Vodafone | - |
| N4‑050225 | Page: 1 | LM Ericsson, Vodafone | - |
| N4‑050226 | - | LM Ericsson, Vodafone | - |
| N4‑050227 | - | LM Ericsson, Vodafone | - |
| N4‑050228 | Page: 1 | LM Ericsson, Vodafone | - |
| N4‑050229 | Page: 1 | LM Ericsson, Vodafone | - |
| N4‑050230 | Service Change for Failover not defined for Mc Interface | - | - |
| N4‑050231 | Service Change for Failover not defined for Mc Interface | - | - |
| N4‑050232 | VPF Type Removal | - | - |
| N4‑050233 | VPF Type Removal | - | - |
| N4‑050234 | VPF Type Removal | - | - |
| N4‑050235 | Alignment of TFO Actvation Procedure and associated parameters | - | - |
| N4‑050236 | Alignment of TFO Actvation Procedure and associated parameters | - | - |
| N4‑050237 | Alignment of TFO Actvation Procedure and associated parameters | - | - |
| N4‑050238 | Page: 1 | LM Ericsson, Vodafone | - |
| N4‑050239 | - | - | - |
| N4‑050240 | - | - | - |
| N4‑050241 | Inclusion Of TISPAN Requirements In Mn Profile | LM Ericsson | - |
| N4‑050242 | Handover and Rate Control in MGW :Improved Handover Description to MGW | LM Ericsson | - |
| N4‑050243 | - | Nortel, | - |
| N4‑050244 | DISC; usage of Topology | Siemens | - |
| N4‑050245 | Pseudonym support in MO-LR | Huawei | - |
| N4‑050246 | - | Huawei | - |
| N4‑050247 | - | Huawei | - |
| N4‑050248 | - | - | - |
| N4‑050249 | - | HP, Ericsson | - |
| N4‑050250 | - | - | - |
| N4‑050251 | - | TeliaSonera | - |
| N4‑050252 | - | - | - |
| N4‑050253 | Reply LS on MBMS Information Element coding (S2-043862) | GERAN | - |
| N4‑050254 | LS on bit rate/delay requirements in the GERAN for an MBMS session | GERAN2 | - |
| N4‑050255 | Reply LS on Session Repetition (S4-040841) | GERAN2 | - |
| N4‑050256 | - | - | - |
| N4‑050257 | Response LS on the PS Handover work | TSG GERAN WG2 | - |
| N4‑050258 | Response LS on 23.060 CR on RIM-NACC clean up | TSG GERAN WG2 | - |
| N4‑050259 | Reply LS on Session Repetition | RAN2 | - |
| N4‑050260 | Reply LS on the PS Handover work | RAN WG2 | - |
| N4‑050261 | Response LS on the PS Handover Work | RAN3 | - |
| N4‑050262 | Misalignment between VGCS stage 1 and stage2 | SA1 | - |
| N4‑050263 | Reply to LS on Need for the IMSI at the PDG | SA3 LI | - |
| N4‑050264 | Response LS on the PS Handover Work | GERAN2 | - |
| N4‑050265 | [A9] Enter the source of the CR. This is either (a) one or several companies or, (b) if a (sub)working group has already reviewed and agreed the CR, then list the group as the source. | Research in Motion | - |
| N4‑050266 | - | Nokia | - |
| N4‑050267 | - | HP, Ericsson | - |
| N4‑050268 | - | Lucent Technologies | - |
| N4‑050269 | - | Lucent Technologies | - |
| N4‑050270 | LS to CN1, CN4, RAN3 on Rel-7 WID for Trace Management | SA5 SWGD | - |
| N4‑050271 | LS reply to CN4 on Open issues for Subscriber Trace | SA5 SWGD | - |
| N4‑050272 | Response LS on Impact of Shared Public User Identities on the Sh Interface | SA5 | - |
| N4‑050273 | - | - | - |
| N4‑050274 | - | - | - |
| N4‑050275 | 2005 Meeting Calendar | MCC | - |
| N4‑050276 | - | - | - |
| N4‑050277 | - | HP, Ericsson | - |
| N4‑050278 | - | HP, Ericsson | - |
| N4‑050279 | WLAN Diameter AVP and result codes | - | - |
| N4‑050280 | Addressing limitations of TCAP handshake for SMS transfer | Vodafone, Siemens | - |
| N4‑050281 | - | Nokia | - |
| N4‑050282 | - | Nokia | - |
| N4‑050283 | - | Nokia | - |
| N4‑050284 | - | Nokia | - |
| N4‑050285 | - | - | - |
| N4‑050287 | - | Vodafone | - |
| N4‑050288 | Reply LS on Impact of Shared Public User Identities on the Sh Interface | SA2 | - |
| N4‑050289 | RE:LS on Control of simultaneous accesses for WLAN 3GPP IP access | SA2 | - |
| N4‑050290 | REPLY LS on 23.060 CR on RIM-NACC clean up | SA2 | - |
| N4‑050291 | LS on transport of HSS address | SA2 | - |
| N4‑050292 | Reply LS on the Workshop on "IMS over Fixed Access" (30th – 31st March 2005) | 3GPP SA2 | - |
| N4‑050293 | LS on Reporting Velocity | TSG_SA WG2. | - |
| N4‑050294 | LS on Allocation of Diameter Command Codes and AVP codes | T2 | - |
| N4‑050295 | Allocations for Gmb | - | - |
| N4‑050296 | - | Orange | - |
| N4‑050297 | - | Orange | - |
| N4‑050298 | Clarification on mapping of eMLPP priorities | - | - |
| N4‑050299 | Addition of the Trace package | - | - |
| N4‑050300 | - | Ericsson, Vodafone, Nortel | - |
| N4‑050301 | - | Ericsson, Vodafone, Nortel | - |
| N4‑050302 | - | Nortel, Vodafone | - |
| N4‑050303 | - | Nokia | - |
| N4‑050304 | Addition of the Trace package | - | - |
| N4‑050305 | Additional Trace information | - | - |
| N4‑050306 | Adding trace control and configuration parameters to subscriber data in HSS | - | - |
| N4‑050307 | - | - | - |
| N4‑050308 | Management Based Activation Impacts | - | - |
| N4‑050309 | Management Based Trace Activation Signalling | - | - |
| N4‑050310 | LS Response to LS on Allocation of Diameter Command Codes and AVP codes | CN4 | - |
| N4‑050311 | Allocation of Diameter Command Codes and AVP codes | - | - |
| N4‑050312 | - | Huawei | - |
| N4‑050313 | Reply LS on Impact of Shared User Identities on the Sh Interface | CN4 | - |
| N4‑050314 | Clarification on requested identity set | - | - |
| N4‑050315 | - | Nokia, Vodafone, Ericsson, HP, Nortel | - |
| N4‑050316 | - | Lucent Technologies, Nortel, FT, Ericsson, Vodafone | - |
| N4‑050317 | - | Lucent Technologies, Nortel, FT, Ericsson, Vodafone | - |
| N4‑050318 | Sh-Update needs to include Data-Reference to be future proof | - | - |
| N4‑050319 | Sh-Update needs to include Data-Reference to be future proof | - | - |
| N4‑050320 | Conditional Service indication in Sh-Subs-Notif | - | - |
| N4‑050321 | Conditional Service indication in Sh-Subs-Notif | - | - |
| N4‑050322 | Clarification of Sh Access Keys | - | - |
| N4‑050323 | Clarification of Sh Access Keys | - | - |
| N4‑050324 | Introduction of Failed AVP | - | - |
| N4‑050325 | Introduction of Failed AVP | - | - |
| N4‑050326 | - | Nokia | - |
| N4‑050327 | - | Nokia | - |
| N4‑050328 | LS on completion of network initiated SCUDIF support | RAN3 | - |
| N4‑050329 | - | Nortel, Vodafone, Nokia, Ericsson, HP, FT | - |
| N4‑050330 | - | Orange | - |
| N4‑050331 | HSS initiated deregistration using the network initiated de-registration procedure | - | - |
| N4‑050332 | - | Alcatel | - |
| N4‑050333 | - | Alcatel | - |
| N4‑050334 | Correction to authentication procedures in not registered case | - | - |
| N4‑050335 | Correction to authentication procedures in not registered case | - | - |
| N4‑050336 | Introduction of Failed AVP | - | - |
| N4‑050337 | Introduction of Failed AVP | - | - |
| N4‑050338 | Add reference to implicitlyregistered public user identities set definition | - | - |
| N4‑050339 | CR on WLAN Alternative NAI | - | - |
| N4‑050340 | Enhanced NSAPI for MBMS | - | - |
| N4‑050341 | Adding missing parameters to the MBMS Session Start Request message | - | - |
| N4‑050342 | Change of newly added Ies in Rel-6 to type TLV | - | - |
| N4‑050343 | notes of the MBMS session | CN4 Vice-Chair | - |
| N4‑050344 | Reply to Reply LS on Need for the IMSI at the PDG | CN4 | - |
| N4‑050345 | Removal of material duplicating 23.234 in 29.234 | - | - |
| N4‑050346 | Addition to WLAN Stage 2 Ruling Wn Out of Scope for 3GPP | CN4 | - |
| N4‑050347 | Removal of unnecessary attributes on Wa | - | - |
| N4‑050348 | WID on Trace Management, stage3, IMS | CN1 | - |
| N4‑050349 | Editorial corrections | - | - |
| N4‑050350 | [DRAFT] LS on Mandating functionality in WLAN ANs | CN4 | - |
| N4‑050351 | Description of the RADIUS session termination procedure | - | - |
| N4‑050352 | WLAN Diameter AVP and result codes | - | - |
| N4‑050353 | WLAN Diameter AVP table and chapters coherence revision | - | - |
| N4‑050354 | PDG behaviour on Wm interface | - | - |
| N4‑050355 | - | Huawei | - |
| N4‑050356 | Release 6 Submission form, Exception for WLAN for Rel-6 | Lucent Technologies | - |
| N4‑050357 | Wa Interface RADIUS profile Information Element corrections | - | - |
| N4‑050358 | Application identifiers to Z-interfaces | - | - |
| N4‑050359 | Modification of key lifetime material | - | - |
| N4‑050360 | CAMEL, LCS and MAP session report | Vice Chairman, TSG-CN WG4 | - |
| N4‑050361 | CR 693 not implemented | - | - |
| N4‑050362 | Correction of IETF Reference in TS 29.278 | - | - |
| N4‑050363 | Correction of IETF Reference in TS 29.278 | - | - |
| N4‑050364 | Miss alignment with stage 2 on reuse mechanism | - | - |
| N4‑050365 | Miss alignment with stage 2 on reuse mechanism | - | - |
| N4‑050366 | Pseudonym indicator support in MO-LR | - | - |
| N4‑050367 | Pseudonym indicator support in MO-LR | - | - |
| N4‑050368 | - | Huawei | - |
| N4‑050369 | Addition of LAI to SendIdentification Request | - | - |
| N4‑050370 | GUP Editorial and References | Ericsson | - |
| N4‑050371 | Reply LS on "S-CSCF client address comparisons and their affect on de-registrations" | CN1 | - |
| N4‑050372 | LS on Allocation of 3GPP specific AVP numbers and Experimental Result Codes for Gx interface | CN3 | - |
| N4‑050373 | Page: 1 | LM Ericsson, Vodafone | - |
| N4‑050374 | - | Vodafone, Ericsson, Nokia, Nortel | - |
| N4‑050375 | - | Vodafone, Ericsson, Nokia, Nortel | - |
| N4‑050376 | Removal of the usage of the ContextAttributeAuditReq construct | - | - |
| N4‑050377 | Removal of the usage of the ContextAttributeAuditReq construct | - | - |
| N4‑050378 | GUP Security Sections | Ericsson | - |
| N4‑050379 | GUP Editorial and References | Ericsson | - |
| N4‑050380 | DST Tables | Ericsson | - |
| N4‑050381 | GUP HSS IMS Data | Ericsson | - |
| N4‑050382 | GUP SOAP Headers | Ericsson | - |
| N4‑050383 | LS on 3GPP Diameter allocations for Gx interface | CN4 | - |
| N4‑050384 | Requirements for support of H.248 packages | - | - |
| N4‑050385 | Requirements for support of H.248 packages | - | - |
| N4‑050386 | Requirements for support of H.248 packages | - | - |
| N4‑050387 | Completion of specification of UMTS Packages | - | - |
| N4‑050388 | Completion of specification of UMTS Packages | - | - |
| N4‑050389 | - | Vodafone, Ericsson, Nokia, Nortel | - |
| N4‑050390 | - | Vodafone, Ericsson, Nokia, Nortel | - |
| N4‑050391 | - | Vodafone, Ericsson, Nokia, Nortel | - |
| N4‑050392 | - | Alcatel | - |
| N4‑050393 | - | Alcatel | - |
| N4‑050394 | - | Alcatel | - |
| N4‑050395 | Commands on ROOT | - | - |
| N4‑050396 | Commands on ROOT | - | - |
| N4‑050397 | - | Nokia | - |
| N4‑050398 | - | Nokia | - |
| N4‑050399 | Correction to Radio Priority LCS IE | - | - |
| N4‑050400 | - | Nokia | - |
| N4‑050401 | - | Nokia | - |
| N4‑050402 | TFO activation without TFO Codec List | - | - |
| N4‑050403 | TFO activation without TFO Codec List | - | - |
| N4‑050404 | TFO activation without TFO Codec List | - | - |
| N4‑050405 | Solving contradiction for Release Cause in Release Bearer Procedure between stage 2 and stage 3 | - | - |
| N4‑050406 | Use Of Audit Value | - | - |
| N4‑050407 | Use Of Audit Value | - | - |
| N4‑050408 | Page: 1 | LM Ericsson, Vodafone | - |
| N4‑050409 | Page: 1 | LM Ericsson, Vodafone | - |
| N4‑050410 | Descriptors In Replies | - | - |
| N4‑050411 | Descriptors In Replies | - | - |
| N4‑050412 | Introduction of formal profile name for Mc interface | - | - |
| N4‑050413 | Introduction of formal profile name for Mc interface | - | - |
| N4‑050414 | New ‘TFO status’ event | - | - |
| N4‑050415 | - | Alcatel | - |
| N4‑050416 | TFO procedure clarification | - | - |
| N4‑050417 | TFO procedure clarification | - | - |
| N4‑050418 | TFO procedure clarification | - | - |
| N4‑050419 | Formal Profile Of Mn Interface | - | - |
| N4‑050420 | - | - | - |
| N4‑050424 | GUP Security Sections | Ericsson, Lucent | - |
| N4‑050425 | Access to Liberty Alliance data schemas | CN4 | - |
| N4‑050426 | Clarification of GUP Resource Identifier | Ericsson | - |
| N4‑050428 | Release 6 Submission form, Exception for GUP for Rel-6 | Lucent Technologies | - |
| N4‑050429 | Clarification to error handling of IEs of type TV | - | - |
| N4‑050430 | Subscribed Charging Characteristics | - | - |
| N4‑050431 | LS on Clarification on deletion of "Subscribed Charging Characteristics" | CN4 (CT4 after CN#27) | - |
| N4‑050432 | Clarification of IPv4 and IPv6 node addresses in the SRNS Relocation Procedure. | - | - |
| N4‑050433 | Support of IPv4 and IPv6 node addresses in Inter-SGSN RAU procedure | - | - |
| N4‑050434 | Add the Common Flags IE to GGSN-Initiated Update PDP Context Request message | - | - |
| N4‑050435 | - | - | - |
| N4‑050436 | - | - | - |
| N4‑050437 | - | Lucent | - |
| N4‑050438 | - | Lucent | - |
| N4‑050439 | Add Source RNC PDCP context info IE in Forward SRNS Context message | - | - |
| N4‑050440 | Add Source RNC PDCP context info IE in Forward SRNS Context message | - | - |
| N4‑050441 | Clarification of PCO IE in Update PDP context response | - | - |
| N4‑050442 | Clarification of PCO IE in Update PDP context response | - | - |
| N4‑050443 | Addition of Selected PLMN-ID for network sharing | - | - |
| N4‑050444 | Addition of TCAP-Handshake for MO-ForwardSM | - | - |
| N4‑050445 | Introduction of Hop Counter for Send Identification | - | - |
| N4‑050446 | Introduction of Hop Counter for Send Identification | - | - |
| N4‑050447 | Introduction of Hop Counter to Identification Request and SGSN Context Request | - | - |
| N4‑050448 | Improvements of VGCS in public networks for parallel use of services | T-Mobile | - |
| N4‑050449 | Addition to WLAN Stage 2 Ruling Wn Out of Scope for 3GPP | CN4 | - |
| N4‑050450 | LS on Mandating functionality in WLAN ANs | CN4 (CT4 after CN#27 March 2005) | - |
| N4‑050451 | Release 6 Submission form, Exception for WLAN for Rel-6 | Lucent Technologies, Huawei Technologies | - |
| N4‑050452 | Access to Liberty Alliance data schemas | CN4 (CT4 after CN#27 March 2005) | - |
| N4‑050453 | - | Nortel, Vodafone, Nokia | - |
| N4‑050454 | GUP Security Sections | Ericsson, Lucent | - |
| N4‑050455 | LS on Cooperation with TISPAN NGN for IMS-CS MGW protocol | 3GPP WG CN4 | - |
| N4‑050456 | Correction of Authentication-related AVPs | - | - |
| N4‑050457 | Correction of Authentication-related AVPs | - | - |
| N4‑050458 | Sh-Update needs to include Data-Reference to be future proof | - | - |
| N4‑050459 | Sh-Update needs to include Data-Reference to be future proof | - | - |
| N4‑050460 | Clarification of Behaviour of Shared Public User Identities | - | - |
| N4‑050461 | Multiple Terminals in Sh | - | - |
| N4‑050462 | LS Response to LS on Allocation of Diameter Command Codes and AVP codes | CN4 (CT4 after CN#27 march 2005) | - |
| N4‑050463 | Rel-6 trace management additions to trace activation and deactivation procedures | - | - |
| N4‑050464 | Release 6 Submission form, Exception for WLAN for Rel-6 | Lucent Technologies, Huawei Technologies, Nokia | - |
| N4‑050465 | Corrections to Mn Specification | - | - |
| N4‑050466 | LS on Cooperation with TISPAN NGN for IMS-CS MGW protocol | 3GPP CN WG4 | - |
| N4‑050467 | Pseudonym indicator support in MO-LR | - | - |
| N4‑050468 | Reply LS on Impact of Shared User Identities on the Sh Interface | CN4 | - |
| N4‑050469 | - | - | - |
| N4‑050470 | New ‘TFO status’ event | - | - |
| N4‑050471 | Continuity Test | - | - |
| N4‑050472 | Stage 2 Procedure for Emergency Call Indication | - | - |
| N4‑050473 | Stage 2 Procedure for Emergency Call Indication | - | - |
| N4‑050474 | Procedure for Emergency Call Indication | - | - |
| N4‑050475 | Procedure for Emergency Call Indication | - | - |
| N4‑050476 | Removal of the ‘Test’ ServiceStates value from the TerminationState Descriptor Events | - | - |
| N4‑050477 | Removal of the ‘Test’ ServiceStates value from the TerminationState Descriptor Events | - | - |
| N4‑050478 | Addition to WLAN Stage 2 Ruling Wn Out of Scope for 3GPP | CN4 (CT4 after CN#27 March 2005) | - |
| N4‑050479 | Reply LS on Impact of Shared User Identities on the Sh Interface | N4 | - |
| N4‑050480 | Requirements for support of procedures | - | - |
| N4‑050481 | Requirements for support of procedures | - | - |
| N4‑050482 | Requirements for support of procedures | - | - |
page generated from database: 2024-04-13 13:51:47