Source:

3GPP TSG_CN_WG4, Meeting #07 Tdoc N4-010422

Sophia Antipolis, FRANCE, 26th February - 2nd March 2001



Source: 3GPP CN4 CHAIRMAN



Title: TDOC ALLOCATION



Agenda item: 2



Document for: APPROVAL









Tdoc Allocation updated till 25 Nov 2011 1:38 (CET)



Agenda Agenda item title Tdoc Title Source Result

item N4-01

1 Opening, approval of 0321 Agenda Ad Hoc Convenor 1. Approved

agenda



2 Document Allocation 0322 Tdoc allocation Ad Hoc Convenor 2. -> T-doc 422



3 Meeting Report 0324 CN4#06 Meeting Report - Beijing MCC 3. Approved



0323 CN4#06_01 Ad Hoc Meeting Report - Madrid MCC 4. Approved



0325 New Meeting Templates for CN groups MCC 5.



4 Liaison Statements 0326 LS on Problem with GPRS and Roaming (N4- N1 6. Section 9.1  Noted

010214)



0418 Reply to LS on Multiparty issues S1 7. Noted



0419 Response to Tdoc NJ-010107 (Control of IP S1 8. Noted

Multi Media services) probably to be discussed in joint meeting



0420 Removal of Visited Control S-CSCF option S2 9. Noted.

from Release 5 IPMM Architecture Nortel: Is this to be removed for Rel6? -> no idea

Vodafone: the Cx interface should be an open interface to allow

multivendor.

Agenda Agenda item title Tdoc Title Source Result

item N4-01



0421 LS on replacement of 23.121 for R4 onwards S2 10. We should check if there’s any reference to be changed

Motorola -> title of TS is Release 5, but we should refer to it

from release 4 docs =>> inconsistency

Vodafone -> intention is to remove details on release 5 from TS

so title is wrong.



5 Work Item Management 0349 3GPP workplan CN4 Chairman 11. To be studied and commented. On hold



0350 Work Item Description for Release 5: Motorola 12. YunChao ->Third point to be removed, since we should talk

"Feasibility study on SS7 signalling about technical solution.

transportation in the core network with SCCP- Vodafone -> at least some sketch of technical solutions should be

User Adaptation (SUA)”

provided to assess the possibloe problems.

F.Telecom -> is there time enough for release 5? Feasibility to be

approved in plenary 12 in June => there are only three CN

meetings (July, October, November) to complete the

standardization work for release 5. TR Draft must be presented

and approved by CN4 in May if it has to go to plenary 12.

Vodafone -> output should be a Technical Report containing a

recommendation go/nogo for the plenary to decide. This

feasibility study should not produce a CR against 29.202

France Telecom-> impacts on services to be considered: NP

CCBS

Vodafone-> security aspect none => wrong !! it should be

analyzed if IP-SEC instead of MAP security can be used.

Yun-Chao -> need for two more supporting companies to be

found for the plenary else WI will be rejected.



0424 Work Item Description for Release 5: Motorola 13. 350 modified => Agreed without presentation

"Feasibility study on SS7 signalling

transportation in the core network with SCCP-

User Adaptation (SUA)”



0376 Work Item Description for Bearer Independent Rapporteur 14. forwarded to CN3-CN4 meeting. Already reviewed in Madrid

Circuit-Switched Core Network



6 Release 4 (Yun-Chao)

6.1 Location Services 0334 CR 29.002 – 233 Rev 2 (Rel4) on MS NTC 15. Approved like this since we base on the current information on

presence notification procedure sa2 status. If SA2 changes their mind then they will have to do

the cleanup.



0338 CR 29.002 - 240 (Rel-4) on CR to 29.002 on Siemens 16. To be further investigated.

Clarification on the use of IMSI in

ProvideSubscriberLocationArg

Agenda Agenda item title Tdoc Title Source Result

item N4-01



0375 CR 29.002 - 232 Rev 1 (R4) on Maximum NTC 17. postponed until 0462 is ready showing the calculation of max nbr

numbers of LCS Clients lcs clients

0462 Calculation of maximum numbers of LCS NTC 18.

Clients



6.2 Network Security 0330 CR 23.012 - 007 (Rel4) on Positive Vodafone 19. Approved according to CN4 except if SA3 brings an LS to stop

authentication reporting it. Another impacted spec (new on CR 33.102 needed)



Withdrawn because SA3 doesn’t have a clear view and has

postponed positive authentication to release 5



0331 CR 23.018 - 066 (Rel4) on Positive Vodafone 20. A number of changes to done  0463

authentication reporting



0463 Revised 0331 Vodafone 21. Withdrawn because SA3 doesn’t have a clear view



0332 CR 29.002 - 235 (Rel4) on Positive Vodafone 22. Revised to Tdoc N4-010348

authentication reporting



0333 CR 29.002 - 236 (Rel4) on Requesting node Vodafone 23. Changes needed in asn.1 notation to show that some parameters

type and address in authentication set request are optional



0465 Revised 0333 Vodafone 24. To be seen



0337 CR 29.002 - 168 Rev 2 (Rel4) on Security Siemens 25. Only reference to be added to ???? + change cover sheet because

Header modification of wrong form used.

Put on hold to wait for the LS response from SA3



0466 Revised 0337 Siemens 26.



0348 CR 29.002 – 235 Rev 1 (Rel4) on Positive Vodafone 27. Potential impacts discovered on the GLR stage 2/3 specs.23.117

authentication reporting 29.119 Need to investigate and make cr’s. To be discussed with

SA3 now timeframes and possibility to get this into release 4

still.

Vodafone + Yun-Chao  CN4 might propose to accept a partial

package without GLR if the companies not needing GLR agree.

CR’s will be prepared by our japanese lady Sujima-san to be

presented in May.

Agenda Agenda item title Tdoc Title Source Result

item N4-01

Editorial changes to 23.205 (v1.2.0) Ericsson L.M. 28. Presented by Ian Park (Vodafone)

0471



Kevin (Nortel) comment Initial Address Message changed to

IAM but he thinks it is less clear since it hints to C7 signalling.

Elena (Ericsson) reminds that it was agreed that messages can

have ISUP names. Alf (Ericsson) comments that IAM is

tup/isup/bicc.

Comment rejected 



Ian (Vodafone)  watch out that still some editorials might

have slipped in. He asks rapporteur to just correct editorials if she

spots any. Meeting agrees 



Chairman  Meeting agrees to delete references 8, 9, 10 and

any reference to SIP-T in the document? Yes 



Document approved, no new T-doc necessary as there only

straighforward changes that rapporteur will do in TS directly.



0464 Revised 0348 Vodafone 29. Withdrawn because SA3 doesn’t have a clear view



6.3 Bearer Independent

Architecture

6.3.1 Stage 2 0377 23.205 Editor's version including agreed Rapporteur 30.

contributions in CN4 Ad Hoc



0379 Modifications to TS 23.205 version 1.2.0 Ericsson L.M. 31. presented by Peka (??) (Ericsson)



Ian (Vodafone)  comment on punctuation of Through-

Connection. Sometimes there’s a space between Trough and

Connection. Edzo (Lucent) points out another editorial “requests

without the s” 

Document approved



0380 Modification of section 8 (Handover) Ericsson L.M. 32. presented by Peka (??) (Ericsson)



Document approved without comments

Agenda Agenda item title Tdoc Title Source Result

item N4-01



0381 Enhancements to service modification Ericsson L.M. 33. presented by Peka (??) (Ericsson)



John (Lucent)  16.2.42 where is the associated message ??

msword played some trick on John…. Question withdrawn 



Document approved with no comments



0382 Alignment of Tunnelling with ITU-T last Ericsson L.M. Withdrawn

changes in Gold Coast BICC editor's meeting



0406 Editorial updates on 23.205v1.2.0 to be Rapporteur 34.  0438

aligned with BICC CS2 last version issued in

Gold Coast meeting



0438 Editorial updates on 23.205v1.2.0 to be Rapporteur 35.  0473

aligned with BICC CS2 last version issued in

Gold Coast meeting



0473 Editorial updates on 23.205v1.2.0 to be Rapporteur 36. approved

aligned with BICC CS2 last version issued in

Gold Coast meeting

Agenda Agenda item title Tdoc Title Source Result

item N4-01



0407 23.205, Multiparty alternative Nortel Networks 37. presented by Kevin (Nortel)



John (Lucent)  is this introducing a second implementation of

MultyParty??

Yun-Chao: why does Nortel wants to introduce this?? Kevin

(Nortel) replies that the new implementation is done using

existing messaging with no impact .

Peka (Ericsson): why changing the normative part? Answer

Kevin: it’s all informative.

John (Lucent) there comes inconsistency between normative and

informative sections; Kevin: no because it’s all informative.

Ericsson: remove the examples since they could be vendor

implementation specific. John (Lucent) if it does not matter the

vendor implementation then remove it from standards.

Yun-Chao: Meeting feels that procedure described before the

example should only be one.

John (Lucent) if this new procedure brings saving in signalling

and complexity then it should be extimated how much and if it’s

enough then the new procedure should just replace the old one,

not be an option.

Edzo (Lucent) why is signalling in Handover increased? Alf and

Peka reply (??).

Consensus that MGW must be able to respond to H.248

commands, so the server can implement the service as it wants.

This means that the text from 13.7.2 to the example should be

normative and example and charts are informative  reaction

(Ericsson and Lucent) that this means two normative ways of

implementing MultiParty. This is not acceptable. There should be

only one clause for Multiparty and maybe more example of

implementation in the informative section of the clause.

John (Lucent): Current text does not prevent Nortel to implement

multiparty with single context. 



For now the example can be added to Multiparty clause, and

Nortel will propose generic text (if not generic enough) for clause

13.7 



document revised to 476

Agenda Agenda item title Tdoc Title Source Result

item N4-01



0400 TS 23.205 v1.2.0, Corrections Nortel Networks 38. presented by Kevin (Nortel)



Elena (Ericsson)  why not using the last version of the

23.205? because now changes are not really easy to spot into the

figure 17.2. Kevin to help Elena to spot the changes. .



Peka (Ericsson)  the prepare bearer procedure has two

optional parameter that should be mandatory if non tunnelling is

used. These parameters should then be conditional.

Elena asks for a text proposal to Kevin: “these information

elements shall not be included if bearer information tunnelling is

done

Alf says that the MGW might always decide not to use tunnelling

; the MSC Server knows only if tunnelling might be used by the

MGW, so parameters should be Mandatory.

Decision: these parameter must be mandatory 



Document approved with 1 comment.



0402 TS 23.205v1.2.0, (G)MSC Gateway Nortel Networks 39. presented by Kevin (Nortel)

Tandeming

Ian (Vodafone)  replace Gateway Tandeming with Media

Gateway . Cooment accepted 



Alf (Ericsson)  can the MGS be controlled by more than one

server? YES 



Alf (Ericsson)  when is the ACM sent? It should be decided

by MSC Server A. Some changes to introductory text of figure

18.2

“…In the example, after the signalling towards MSC server

A and then bearer towards the MGW B is established,

MSC server A requests …..” text agreed 



Document approved with above change.

6.3.2 Stage 3 - Nc interface 0378 29.205 Editor's version including agreed Rapporteur 40. Noted

contributions in CN4 Ad Hoc

Agenda Agenda item title Tdoc Title Source Result

item N4-01



0387 Updates of TS 29.205 version 1.20 Ericsson L.M. 41. Presented by Alf (Ericsson)



Ian (Vodafone)  two clauses 4.4. Agreed 



Document approved. And TS 29.205 is also approved in version

2.0.0

6.3.3 Stage 3 - Mc interface 0383 Updates of TS 29.232 version 1.2.0 Ericsson L.M. 42. Withdrawn



0384 Additions to the CSD package Ericsson L.M. 43. Approved



0385 Corrections To Modify Char Procedure Ericsson L.M. 44.  Replaced by 0472





0472 Corrections To Bearer Modification Ericsson L.M. 45. Approved

Procedure







0386 Enhancements to service modification Ericsson L.M. 46. Withdrawn, is addressed by 0384



0401 TS 29.232v1.2.0, Mc interface Nortel Networks 47. Approved onòly for some parts. New text encoding removed.

clarifications/improvements Yun-Chao to say in his status report that there are problems open

for text encoding, and that Ericsson objects requiring a note in

the TS saying that. No consensus on whether text encoding is

necessary or not.

0416 Editorial updates on 29.232 Rapporteur 48. Noted. Small editorials needed: reference to RFC on SIP-T to be

removeed. Reference to releaqse 2000 to be changed.

6.4 Supplementary Services

6.4.1 Call Waiting 0357 CR 23.018 - 067 (R4) on Removal of CW Vodafone 49.

descriptions



0358 CR 23.083 - 007 (R4) on Enhancement of Vodafone 50.

CW procedures



6.4.2 MPTY and ECT 0355 CR 23.018 - 065 Rev 1 (R4) on Incorporation Vodafone 51.

of MPTY and ECT into the Subs_FSM

process.



6.4.3 Call Hold 0356 CR 23.083 - 006 Rev 1 (R4) on Enhancement Vodafone 52.

of procedures for Call Hold



0426 Revised 0356 53.

0415 Editorial updates on 29.202 Rapporteur 54.

6.5 IP Signalling

Agenda Agenda item title Tdoc Title Source Result

item N4-01

0425 Editorial updates of 415 Rapporteur 55. Some editorials in Annex A. Wrong template used.



7 Release 5 (Yun-Chao)

7.1. HSS-CSCF i/f 0363 Cx interface protocol selection Siemens 56.



0373 Capability negotiation in DIAMETER Ericsson 57.



0423 from SA2 Reply LS on the Work Item “Cx Ericsson 58. tCN4 will work on the detailed information flows. And on two

Interface specification” documents that are going to be generated: stage2 23.cde, stage3

29.cde



8 Release 99 (Teemu)

8.1 CAMEL Phase 3 0335 CR 29.002 – 237 (Rel-4) on CR to 29.002 on Siemens 59. Withdrawn

SS-CSI editing error correction from CR 115r1



0336 CR 29.002 – 238 (R99) on CR to 29.002 on Siemens 60. Withdrawn

SS-CSI editing error correction from CR 115r1



0360 CR 29.002 – 246 (Rel-4) on Adding EXPORT Ericsson 61.

definition for LSAIdentity



0361 CR 29.002 – 247 (Rel-4) on Removing Ericsson 62.

duplicate parameters from SS-CSI



0362 CR 29.002 – 248 (Rel-4) on Correction to Ericsson 63.

description of SS-CSI in HLR to VLR

information flow



0427 CR 29.002 Adding EXPORT definition for Nokia 64. Approved

GeographicalInformation



0428 CR 29.002 Adding EXPORT definition for Nokia 65. Approved

GeographicalInformation



0469 Cr 261 Correction to D-CSI Alcatel 66.



0470 Cr 261 Correction to D-CSI Alcatel 67.



8.2 Security 0340 CR 29.002 – 225 Rev 1 (R99) on Addition of Nokia 68.

selected UMTS algorithm indication to the

handover procedures



0429 340 revised 69. agreed by consensus category to be presented

Approved

Agenda Agenda item title Tdoc Title Source Result

item N4-01



0341 CR 29.002 - 226 Rev 1 (R99) on Addition of Nokia 70. change in wording of reference to gsm 08.08

allowed GSM algorithms indication to the

handover procedures



0434 Revised 0341 71. agreed with no presentation



0342 CR 29.002 – 238 (Rel-4) on Addition of Nokia 72. mirror cr of 343

selected UMTS algorithm indication to the

handover procedures



0430 Revised 0342 73. to be presented



0343 CR 29.002 – 241 (Rel-4) on Addition of Nokia 74.

allowed GSM algorithms indication to the

handover procedures



0431 Revised 0343 75. approved



0344 CR 29.002 – 242 (R99) on Addition of allowed Nokia 76. categorized as Essential correction

UMTS algorithms indication to the handover

procedures



0432 Revised 344 Nokia 77. to be seen again  Approved



0345 CR 29.002 – 243 (R99) on Addition of Nokia 78. categorized as “agreed by consensus”. Change in 7.6 as for 0341

selected GSM algorithm indication to the

handover procedures



0435 Revised 0345 79. approved with no further presentation



0346 CR 29.002 – 244 (Rel-4) on Addition of Nokia 80.

allowed UMTS algorithms indication to the

handover procedures



0433 Revised 346 Nokia 81. to be seen again  Approved



0347 CR 29.002 - 245 (Rel-4) on Addition of Nokia 82. mirror of 345. Plus change reference to 08.08 to 48.008

selected GSM algorithm indication to the

handover procedures



0436 Revised 0347 83. approved with no further presentation



8.3 GPRS 0339 CR 29.060 - 155 Rev 3 (R99) on Adding Up- Nokia 84.

link TEID Data I and user plane GGSN

address to PDP Context IE



0351 CR 29.060 - 179 Rev 1 on Clarifications to the Motorola 85.

GTP-U protocol

Agenda Agenda item title Tdoc Title Source Result

item N4-01



0359 CR 29.060 - 181 (R99) on Fix an ambiguous NEC 86.

description on the treatment for the PDP Type

PPP in PDP context creation procedure



0372 CR 23.003 - 026 (99) on Forbidden APN Ericsson 87.

network identifier labels



0374 CR 23.060 - 170 Rev 1 (R99) on Clarification Fujitsu 88.

on the TEID value of the signalling messages



0388 CR 29.060 - 182 on GSN Address in Error Ericsson 89.

Indication



0457 Revised 0388 Ericsson 90. last added sentence to be replaced with sentence copied from ???



0458 Revised 0457 Ericsson 91. approved with no presentation



0389 CR 29.060 - 183 on Clarifications on the Ericsson 92. postponed, to be discussed by e-mail; problem is the possible

mapping of cause codes towards 24.008 interwork of rel4 MSC with rel99 MS if the cr would not be

accepted for release 99. Concern from Japan on implementing it

in rel99



0390 Proposed LS to N1 on Cause Code mappings Ericsson 93.



0391 CR 29.060 - 185 on Clarification on the use of Ericsson 94.

the term G-PDU



0398 CR 29.060 - 186 on Clarification of Error Ericsson Handled later when 0459 has circulated

Indication Replace description of error handling with reference to stage 2 23.060



0460 0398 revised Ericsson Agreed with no further presentation.



0459 CR in SA2 for Clarification of Error Indication Ericsson



0399 CR 29.060 - 227 on Indication of relocation Nortel Networks 95. Withdrawn

requirement in Forward Relocation Request



0404 CR 29.060 – 187 on Clarification

on the Lucent technologies 96. approved with category Agreed by consensus

handling of sequence numbers in the

GTP user plane

0405 CR 29.060 - 188 on Clarificationsand Lucent technologies 97. approved with category Agreed by consensus

clean up of the error handling section

0412 CR 29.060 – 189 on Cause in Relocation Motorola 98. Vodafone + Ericsson + Lucent  Why do we need in the target

Cancel Request RNC to distinguish why the old SGSN has asked for a cancel

relocation.

REJECTED

Agenda Agenda item title Tdoc Title Source Result

item N4-01

0417 CR 29.060 – 190 on Clarification of Delete Ericsson 99.

PDP context response

CR 29.060 – 192 on Clarifications on the GTP Motorola 100. some rewording to be done.

0454 message treatment

Revised 0454 Motorola 101. to be presented again

0461

8.4 Handover 0364 CR 29.002 – 249 (R99) on GSM to UMTS Siemens 102. Approved with category change (agreed by consensus)

handover: addition of MAP parameter Target

RNC ID GSM to UMTS handover: addition of

MAP parameter Target RNC ID



0365 CR 29.002 - 250 (REL-4) on GSM to UMTS Siemens 103. Approved with category change (agreed by consensus)

handover: addition of MAP parameter Target

RNC ID



0366 CR 29.010 - 012 (R99) on GSM to UMTS Siemens 104. Comment to be added that Target RNC Id should be derived from

handover: addition of MAP parameter Target the Target Cell nId passed in the BSSMAP message by MSC-A.

RNC ID check in 23.009 if MSC-A is supposed to translate Target Cell Id

into Target RNC Id.

Finally approved with cover sheet category change after checks.



0367 CR 29.010 - 013 (R99) on Inter MSC Siemens 105. approved

relocation: addition of MAP parameter Target

RNC ID



0396 CR 29.002 - 255 (R99) on Addition of GSM Nokia 106. to be investigated iif 23.009 is impacted; if 29.010 is impacted.

channel type and GSM chosen channel Siemens in case of UMTS to GSM handover BSSMAP should

indications to handover procedures be used, while the CR implies a change of interface to RANAP.

Ericsson it has to be more clear what traffic case it is:

UMTS(interMSC HO)UMTS(IntraMSC HO)GSM

Ericsson  is there a link to a CN1 CR doing the same kind of

changes n1-010336(366)?

Postponed. To Friday morning.



Withdrawn



0397 CR 29.002 - 256 (Rel-4) on Addition of GSM Nokia 107. Withdrawn

channel type and GSM chosen channel

indications to handover procedures



0403 CR 29.010 - 015 on Alignment of cause Nortel Networks 108. Approved with category change

mapping for 08.08 and 25.413 (Directed

Retry)



0437 CR 29.010 - 015 on Alignment of cause Ericsson 109. Approved with category change

mapping for 08.08 and 25.413 (Directed

Retry)



8.5 Multicall 0392 CR 29.002 - 251 (R99) on Clarification of the Nokia 110. Approved

use of multicall bearer information

Agenda Agenda item title Tdoc Title Source Result

item N4-01



0393 CR 29.002 - 252 (Rel-4) on Clarification of the Nokia 111. Approved

use of multicall bearer information



0394 CR 29.002 - 253 (R99) on Addition of radio Nokia 112. Handover experts to be contacted. Do we need the CR at all? Can

resource list to the handover procedures MSC-B must be able to do the selection of bearers in case MSC-

B’ does not support multibearer



0395 CR 29.002 - 254 (Rel-4) on Addition of radio Nokia 113.

resource list to the handover procedures

0413 CR 23.018 – 068 on Paging not via the SGSN Vodafone 114. “agreed by consensus” category.

8.6 LCS

correction

0414 CR 23.018 – 068 on Paging not via the Vodafone 115. “agreed by consensus” category.

SGSN correction

9 GSM Maintenance (Teemu)

9.1 GPRS 0327 CR 09.10 – A011 (R97) on Mapping of Vodafone 116. complementary to 0369. Category must be essential correction on

unknown HLR error to access interface cause the cover sheet. Approved

code.



0328 CR 09.10 - A012 (R98) on Mapping of Vodafone 117. mirror of 327. Approved

unknown HLR error to access interface cause

code.



0329 CR 29.010 - 011 (R99) on Mapping of Vodafone 118. mirror of 327. Approved

unknown HLR error to access interface cause

code.



0352 CR 29.060 - 180 Rev 1 (-) on Clarification on Motorola 119. category is “agreed by consensus”. Rephrase the new text

IMSI Encoding



0447 Revised 0352 120. 448 and 449 numbers for the mirror cr’s. Approved.



0353 CR 09.60 - A100 Rev 1 (-) on Clarification on Motorola 121.

IMSI Encoding



0354 CR 09.60 - A101 Rev 1 (-) on Clarification on Motorola 122.

IMSI Encoding



0368 CR 09.60 - A102 (R98) on Re-configure the Siemens 123.

IEs in the PDU Notification Request and in

Create PDP Context Request to make it in

ascending order



0369 CR 09.10 - A013 (R97) on Roaming Siemens 124. complementary to 0327. Category must be essential correction on

restrictions for GPRS service the cover sheet. Approved



0370 CR 09.10 - A014 (R98) on Roaming Siemens 125. mirror of 0369. Approved

restrictions for GPRS service

Agenda Agenda item title Tdoc Title Source Result

item N4-01



0371 CR 29.010 - 014 (R99) on Roaming Siemens 126. mirror of 0369. Approved

restrictions for GPRS service



0408 Failure of Authentication Parameter GPRS France Télécom 127.

when HLR is not reachable



0409 CR 09.02 on Failure of Authentication France Télécom 128. Some editorials (remove text in brackets concerning ss7 links)

Parameter GPRS when HLR is not reachable (remove french quotes)



0443 Revised 0409 129. Mirror cr’s are 444 (release 98) 445 (release 99) 446 (release 4).

443 + mirror cr’s approved without further presentation.



0410 CR 09.10 on Failure of Authentication France Télécom 130. withdrawn since it’s the same as 327

Parameter GPRS when HLR is not reachable



0411 CR 03.60 – A185 on Failure of Authentication France Télécom 131. liasion statement (tdoc 439) to be prepared towards sa2 to show

Parameter GPRS when HLR is not reachable the problem with attached mirror CR’s for relase 98 (441) release

99 (442)



0439 LS to SA2 on handling of an error case for 132. approved

authentication set retrieval



0440 Revised 0411 133. endorsed by CN 4 (see 0411)



10 AOB





11 Future Meetings



12.1 Output Documents

12.2 Approved CRs

12.3 Approved LS

12.3 Approved TS/TR



13 Close



NYA



Late contributions 0360 CR 29.002 - 246 (Rel-4) on Adding EXPORT Ericsson 134. Approved with correction in cover sheet

definition for LSAIdentity



(will be only discussed if 0361 CR 29.002 - 247 (Rel-4) on Removing Ericsson 135. Approved with correction in cover sheet. General comment:

time permits) duplicate parameters from SS-CSI category A cr’s should be presented to the plenary with the

corresponding F Change requests in one package.

Agenda Agenda item title Tdoc Title Source Result

item N4-01



0362 CR 29.002 - 248 (Rel-4) on Correction to Ericsson 136.

description of SS-CSI in HLR to VLR

information flow



0398 CR 29.060 - 186 on Clarification of Error Ericsson 137.

Indication



0386 Enhancements to service modification Ericsson L.M. 138. Withdrawn



0382 Alignment of Tunnelling with ITU-T last Ericsson L.M. 139. Withdrawn

changes in Gold Coast BICC editor's meeting



0412 CR 29.060 – 189 on Cause in Relocation Motorola 140.

Cancel Request

0413 CR 23.018 – 068 on Paging not via the SGSN Vodafone 141.

correction

0414 CR 23.018 – 068 on Paging not via the Vodafone 142.

SGSN correction

0417 CR 29.060 – 190 on Clarification of Delete Ericsson 143. withdrawn

PDP context response