The Mobile
Broadband Standard

3GPP TDocs (written contributions) at meeting

Meeting: N4-13 - 2002-04-08 to 2002-04-12, Fort Lauderdale

meeting id: N4-13 (click id for more info on this meeting)

Click on the Tdoc to open its file.

TDoc Title Source Remarks
N4‑020311 PROPOSED AGENDA FOR CN4 #13 CN4 CHAIRMAN -
N4‑020312 Proposed allocation of documents to agenda items for TSG-CN WG4 Meeting #13 Chairman, TSG-CN WG4 -
N4‑020314 Summary report of CN #15 & SA #15, Jeju, March 2002 CN4 Chairman -
N4‑020315 - - -
N4‑020316 - - -
N4‑020317 Page: 1 Alcatel S.A. -
N4‑020318 Check of NAM and Requesting Node Type on receipt of SendAuthenticationInfo - -
N4‑020319 [H8] 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. Alcatel -
N4‑020320 [H8] 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. Alcatel -
N4‑020321 [H8] 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. Alcatel -
N4‑020323 3GPP TS 29.328 IP Multimedia Subsystem Sh Interface Lucent Technologies -
N4‑020324 3GPP TS 29.329 IP Multimedia Subsystem Sh Interface Lucent Technologies -
N4‑020325 R5 CR29.002 for support of MAP Si interface Lucent Technologies -
N4‑020326 - - -
N4‑020327 - - -
N4‑020328 Correction on the handling of S field - -
N4‑020329 Clarification on create PDP context for existing - -
N4‑020330 - - -
N4‑020331 DETAILED AGENDA & TIME PLAN FOR CN4 #13 CN4 CHAIRMAN -
N4‑020332 Handling the MNRR flag in the HLR & SMS-GMSC - -
N4‑020333 Handling the MNRR flag in the HLR & SMS-GMSC - -
N4‑020334 Proposed WI: MBMS Hutchison 3G -
N4‑020335 [H8] 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. Hutchison 3G -
N4‑020336 [H8] 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. Hutchison 3G -
N4‑020337 Presence Service Clarifications needed for work split and scope Hutchison 3G -
N4‑020338 Version Control for IMS protocols Nortel Networks -
N4‑020339 Inclusion of Version information in User Profile Nortel Networks -
N4‑020340 S-CSCF selection options for the operator Nortel Networks -
N4‑020341 Addition of parameter to Inter-SGSN RAU - -
N4‑020342 Page: 1 Lucent Technologies -
N4‑020343 Page: 1 Lucent Technologies -
N4‑020344 Page: 1 Lucent Technologies -
N4‑020346 [H8] 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. Vodafone -
N4‑020347 [H8] 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. Nokia -
N4‑020348 - - -
N4‑020349 [H8] 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. Nokia -
N4‑020350 MSC server GTT enhancement - -
N4‑020351 [H8] 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. Nokia, L.M. Ericsson -
N4‑020353 - - -
N4‑020354 - - -
N4‑020355 Page: 1 Siemens -
N4‑020356 Adaptation of the Mc Interface specification for the interface between IMS-MGW and MGCF Siemens -
N4‑020357 Complement to the Answer Liaison Statement on MSISDN Address resolution for MMS using MAP operations CN4 -
N4‑020358 [H8] 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, NTT DoCoMo -
N4‑020359 [H8] 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, NTT DoCoMo -
N4‑020360 [H8] 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, NTT DoCoMo -
N4‑020361 [H8] 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, NTT DoCoMo -
N4‑020362 User Profile description Nokia -
N4‑020363 XML Schema of Subscriber Profile Nokia -
N4‑020364 User Profile downloading Nokia -
N4‑020365 S-CSCF change Nokia -
N4‑020366 S-CSCF name handling in HSS Nokia -
N4‑020367 Optimisation of Registration Authorisation Nokia -
N4‑020368 Result-Code value DIAMETER_UNABLE_TO_COMPLY for UAA and LIA commands Nokia -
N4‑020369 Addresses of the Charging Functions Nokia -
N4‑020370 Correction to TS 23.008 - -
N4‑020371 3GPP Diameter Cx Application vs. IETF Nokia -
N4‑020372 [DRAFT] Liaison Statement on Immediate Service Termination TSG-CN WG4 -
N4‑020373 [H8] 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. NTT DoCoMo, NTT Comware -
N4‑020374 [H8] 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. NTT DoCoMo, NTT Comware -
N4‑020375 Clarification of introducing Session related and unrelated class - -
N4‑020376 Clarification of introducing Session related and unrelated class - -
N4‑020378 The use of IPv4 and IPv6 in the transport plane Ericsson, Nokia -
N4‑020379 - L.M. Ericsson -
N4‑020380 - L.M. Ericsson -
N4‑020381 Clarification on User registration status query procedure Ericsson -
N4‑020382 TS 29.228 - Clarification of User location query procedures Ericsson -
N4‑020383 Clarification on Authentication procedure Ericsson & Nokia -
N4‑020384 Clarification on S-CSCF registration/de-registration notification Ericsson -
N4‑020385 Clarifications on implicit registration Ericsson -
N4‑020386 Clarification of Network Initiated Deregistration Ericsson -
N4‑020387 Clarification on Update of User Profile Ericsson -
N4‑020388 Download relevant end user profile Ericsson -
N4‑020389 Updates to the user profile Ericsson -
N4‑020391 Update to TFO package to explicitly reference TS 26.103 for 3GPP codecs - -
N4‑020392 Work Required To Complete AMR-WB WI L.M.Ericsson -
N4‑020393 [H8] 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. L.M.Ericsson -
N4‑020394 Framing Protocol Interworking L.M.Ericsson -
N4‑020395 - - -
N4‑020396 Introduction of Preferred Framing Protocol request in Q.765.5 SOURCE*:LM Ericsson -
N4‑020397 Introduction of Preferred Framing Protocol request in Q.1902.4 SOURCE*:LM Ericsson -
N4‑020398 “Long FTN Supported” to be transferred from VLR to HLR - -
N4‑020399 “Long FTN Supported” to be transferred from VLR to HLR - -
N4‑020400 - - -
N4‑020402 - - -
N4‑020403 - - -
N4‑020404 - - -
N4‑020405 LCS : Codeword and Service Type - -
N4‑020406 LCS : Codeword and Service Type - -
N4‑020407 [H8] 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. Ericsson -
N4‑020408 CAMEL4 : Clarification of handling of MT-SMS-TPDU-Type and SMS-TDP - -
N4‑020409 LCS : Clarify conditions to trigger restart of MTLR-Deferred procedure - -
N4‑020410 LCS : Clarify conditions to trigger restart of MTLR-Deferred procedure - -
N4‑020411 [H8] 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. Ericsson -
N4‑020412 [H8] 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. Ericsson -
N4‑020413 - - -
N4‑020414 [H8] 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. Ericsson -
N4‑020415 [H8] 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. L.M. Ericsson and Nokia -
N4‑020416 [H8] 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. Siemens -
N4‑020417 [H8] 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. Siemens -
N4‑020418 Use of COPS protocol in Ze interface Nokia -
N4‑020419 [H8] 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. Nokia -
N4‑020420 [H8] 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. Nokia -
N4‑020421 [H8] 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. Nokia -
N4‑020422 The MAP Dialogue PDU requirements for MAP Security Nokia -
N4‑020423 Response to "Response Liaison Statement on Trace and Availability of IMSI and IMEI" GERAN 2 -
N4‑020424 Liaison Statement on PSTN/CS domain originated call CN1 -
N4‑020425 Liaison statement on the definition and usage of Filter Criteria CN1 -
N4‑020426 Liaison Statement on DTMF CN1 -
N4‑020427 Mandatory use of Transport Addresses sent by the MSC in a RAB Modification Request RAN3 -
N4‑020428 Reply to the LS “Liaison Statement on Handover Indication solution” RAN3 -
N4‑020429 Liaison Statement on Service change and fallback for UDI/RDI multimedia calls SA1 -
N4‑020430 Liaison Statement on Interworking of AMR-WB with G.722.1 SA1 -
N4‑020431 Response LS on Shared network scenarios considered by TSG-RAN3 SA 2 -
N4‑020432 Liaison Statement Reply to "Status of the Generic User Profile Work" SA2 -
N4‑020433 Liaison Statement Reply to "Comments on UP-010141 and relationship of GUP to Subscription Management" SA2 -
N4‑020434 Liaison Statement on The Provision of an Inter-GMLC Interface SA2 -
N4‑020435 Liaison Statement on “Introduction of IPv6 prefix allocation in TS 23.003” TSG SA2 -
N4‑020436 LS on Stage 2 for use of USIMs and ISIMs for IMS SA 2 -
N4‑020437 LS on S-CSCF change TSG SA2 -
N4‑020438 LS on adapting to IETF improvements contained in “unified draft” TSG SA2 -
N4‑020439 Response to email “NP-010710: AMR-WB TSs from SA4” SA3 -
N4‑020440 Ze interface security SA3 -
N4‑020441 Reply to N4-020302: Response Liaison Statement on Trace and Availability of IMSI and IMEI SA3 -
N4‑020442 Reply LS on support for subscriber certificates S3 -
N4‑020443 Liaison Statement on coordination of data definitions, identified in GUP development T2 -
N4‑020444 Response to Liaison Statement on Cx User Profile (N4-020197) T2 GUP Ad-hoc -
N4‑020445 Reply to “Liaison Statement on The addition of the H.324 M codec to TS 26.103” SA4 -
N4‑020446 - - -
N4‑020447 LS reply on: Priority Service Feasibility Study - draft TR 22.950 v1.0.0 SA5 -
N4‑020448 Reply to Liaison Statement on Availability of IMSI and IMEI in the BSC SA5 SWG-B -
N4‑020449 [H8] 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. Ericsson -
N4‑020450 3GPP TS 23.xyz "Technical Realisation of CS Multimedia Service; UDI/RDI Fallback and Service Modification; Stage 2 (Release 5)" L.M. ERICSSON -
N4‑020451 Updates to the user profile Ericsson -
N4‑020453 Allocation of unique prefixes to IPv6 terminals - -
N4‑020454 LS on “Transport of IMS-AKA Material” SA WG3 -
N4‑020457 Future Meetings MCC -
N4‑020458 DETAILED AGENDA & TIME PLAN FOR CN4 #13 CN4 CHAIRMAN -
N4‑020459 Proposed allocation of documents to agenda items for TSG-CN WG4 Meeting #13 Chairman, TSG-CN WG4 -
N4‑020460 XML Schema of Subscriber Profile, revised Nokia -
N4‑020461 [H8] 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. L.M. Ericsson and Nokia -
N4‑020462 Discussion Paper: Mobile Network Evolution Ericsson -
N4‑020463 DRAFT Response to Liaison Statement on coordination of data definitions, identified in GUP development CN4 -
N4‑020464 [H8] 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. Hutchison 3G -
N4‑020465 LS on Priority Service Feasibility Study TR - draft SA1 -
N4‑020466 Proposed Liaison Statement to SA2 on handling of user profile data Nokia (TSG CN4) -
N4‑020467 - - -
N4‑020468 Corrections to the handling of Any Time Interrogation and Provide Subscriber Info - -
N4‑020469 - - -
N4‑020470 - - -
N4‑020471 29.328 IMS Sh Interface, Signalling Flows and Message contents Ericsson -
N4‑020472 Liaison Statement on Distribution of IMS charging ID (ICID) from GGSN to SGSN SA5 -
N4‑020473 - L.M. Ericsson -
N4‑020474 Reply to ”IP version inter-working on the transport plane” from SA2 SA5 -
N4‑020475 Correction of the DP criteria table for T-CSI and VT-CSI on the Rel05 - -
N4‑020476 Change PS-connected to PS-PDPactive - -
N4‑020477 Work Item Description for the Support of CAMEL by the IMS Lucent Technologies -
N4‑020478 Subscriber Information Management in IMS Siemens -
N4‑020479 [H8] 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. Lucent Technologies -
N4‑020480 [H8] 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. Lucent Technologies -
N4‑020481 [H8] 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. Lucent Technologies -
N4‑020482 3GPP TS 23.172, UDI/RDI Fallback and Service Modification L.M. Ericsson -
N4‑020483 CAMEL4 : Triggering of gsmSCF for MT-SMS-CSI - -
N4‑020484 [DRAFT] Liaison Statement on Mandatory Use Of Transport Addresses sent by the MSC in a RAB Modification Request CN4 -
N4‑020485 Transferring the MS classmark & IMEI to the fgsmSCF - -
N4‑020486 LS on availability of MS Radio Access Capability in for MS in Iu-Mode CN4 -
N4‑020488 Allocation of unique prefixes to IPv6 terminals - -
N4‑020489 Allocation of unique prefixes to IPv6 terminals - -
N4‑020490 - - -
N4‑020491 GTT enhancement on Mc - -
N4‑020492 CTM Text Transport package - -
N4‑020494 Liaison Statement Response on "Distribution of IMS charging ID (ICID) from GGSN to SGSN" CN4 -
N4‑020495 Reply to LS on ”IP version inter-working on the transport plane” from SA2 (S2^^020291) SA5 -
N4‑020496 Response to LS (N1-020666) on DTMF RAN2 -
N4‑020497 Response to LS (N4-020302) on Trace and Availability of IMSI and IMEI RAN2 -
N4‑020498 Clarfication of introducing Session related and unrelated class - -
N4‑020499 Clarfication of introducing Session related and unrelated class - -
N4‑020500 - - -
N4‑020501 Page: 1 Siemens -
N4‑020502 LCS: Mapping BSSMAP-RANAP for request of - -
N4‑020503 LCS: clarification of mapping for Location Acquisition - -
N4‑020504 LCS: clarification of mapping for Location Acquisition - -
N4‑020505 LCS : on error handling if shape not supported by GMLC - -
N4‑020506 - - -
N4‑020507 - - -
N4‑020508 LCS : Error handling if wrong method requested in LCS-MOLR - -
N4‑020509 LCS : Error handling if wrong method requested in LCS-MOLR - -
N4‑020510 Corrections on the introduction of LCS for PS domain - -
N4‑020511 Corrections on the introduction of LCS for PS domain - -
N4‑020512 Complement to the Answer Liaison Statement on MSISDN Address resolution for MMS using MAP operations CN4 -
N4‑020513 IuFlex support for determining old SGSN during handover/relocation - -
N4‑020514 - - -
N4‑020515 - - -
N4‑020516 Page: 1 Alcatel S.A. -
N4‑020517 Liaison Statement on Mandatory Use Of Transport Addresses sent by the MSC in a RAB Modification Request CN4 -
N4‑020520 - - -
N4‑020521 Check of NAM and Requesting Node Type on receipt of SendAuthentication - -
N4‑020522 Liaison Statement on “The use of IPv4 and IPv6 in the transport plane” TSG CN4 -
N4‑020523 - - -
N4‑020524 Liaison Statement on “The use of IPv4 and IPv6 in the transport plane” TSG CN4 -
N4‑020525 Filter Criteria Modifications - -
N4‑020526 Liaison Statement Response on "Distribution of IMS charging ID (ICID) from GGSN to SGSN" CN4 -
N4‑020527 - - -
N4‑020528 Check of NAM and Requesting Node Type on receipt of SendAuthenticationInfo - -
N4‑020529 LCS : on error handling if shape not supported by GMLC - -
N4‑020530 LCS : on error handling if shape not supported by GMLC - -
N4‑020531 Liaison Statement on TS 23.008 Organization of subscriber data SA5 SWG-A -
N4‑020532 [DRAFT] Liaison Statement on TS 23.008: Organisation of subscriber data CN4 -
N4‑020533 [H8] 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. Nokia -
N4‑020534 Proposed WI: Network Sharing Ericsson -

page generated from database: 2019-12-06 10:39:20