Source: cn2 chairman Title: Allocation of documents to agenda items Agenda item: 2 Document for: information



Download 423.8 Kb.
Page1/4
Date conversion05.12.2017
Size423.8 Kb.
  1   2   3   4
3GPP TSG CN WG2 Tdoc N2-030002

Dublin, Ireland



Source: CN2 chairman

Title: Allocation of documents to agenda items

Agenda item: 2

Document for: INFORMATION
Colour scheme:


White: Handled

To be handled

Needs early handling

Late / not available




TDoc # N2-010

Agenda item

Title

Source

Discussion

Conclusion







Action points








018




Clarify information flow tables for CLIR/CLIP








033




Add to open items the timer handling in IMS.








120




Add open iten: CPH and Resume_counter for Call Segment.








151




Ask opinion about resumption counters








065


Add open item of Rel-6 priorization TDP RSF/DP3.









061/078




Update open issue list to next meeting



























1

Opening of the meeting & Agenda








001

1

Agenda

CN2 Chair



  • Approved


2

Tdoc list








002

2

Allocation of documents to agenda item

CN2 Chair



  • noted 

003

2

CN2-CN4 Joint meeting Tdoc list

CN2 Chair



  • Noted




3

Reports








005

3

CN2#27 Draft Meeting Report

MCC

  • e-mail approved documents are marked as approved.

  • Approved


006

3

CN#18 Draft Meeting Report

MCC

  • No editorial CRs allowed for Rel-5

  • ASN.1 corrections are seen as critical enough.

  • WID needs to be seen by CN2 and CN4, to be sent to CN#19. (enhanced dialled services).

  • No merge 2003 with CN4. Show of hands needed in CN2 in interest areas.

  •  noted




4

Input Liaison statements








008

4

LS on Enhanced Dialled Services

SA1

  • A bit outdated document. SA plenary then decided to approve the service requirement.

  • Noted

009

4

LS on SMS over PS in Iu mode


SA2

  • Attachement is missing.

  •  Noted

010

4

Response on CN2 conclusion on CAMEL_PS_Notification procedure

SA2

  • There is no problem currently in spec.

  •  Response in 099.

  • Noted

099

4

Response to SA2 on CN2 conclusion on CAMEL_PS_Notification procedure

Siemens

  • Result of 010.

  • CN4 shall be replaced by CN2. Andrijana corrected off-line.

  • Approved.




5

Work Item Management & miscellaneous












IPR call





  • Reminder to Individuals Members and the persons making the technical proposals about their obligations under their respective Organizational Partners IPR Policy

  • IPRs do not need to be declared at the WG meeting but should go to the respective organization.



004

5

Query on interest area of delegates

CN2 Chair

  • A new editor will be needed for 23.278 and 29.278.

  • 1: 10 people non-IMS

  • 2: 7 (IMS)

  • 6 (both)

  • 4: 14 (Rel-6 onwards)

  • half of the group follows both topics.

  •  

007

5.2

Latest version of the work plan

MCC

  • No change to CN2 topics (Rel-6 is not yet included)

  • All CN2 items “complete”
  • Enhanced Dialled Services will appear in the March plenary


  • Noted




6.2

CAMEL2











7

CAMEL3











7.1

CAMEL3 / miscellaneous








034

7.1

R99 29.078-CR299 ASN.1 syntax basic corrections

Alcatel
  • Subcategory shall be in the cover page. (Essential correction)


  • Rel-5 CR has different content.

  • Reference to 23.278 is incorrect. 29.278 is correct.

  • CAP modules still use CCITT instead of ITU. The 3 mistakes cause a warning during compilation.

  • Revised to 100

100

7.1

R99 29.078-CR299 ASN.1 syntax basic corrections

Alcatel

  • Revision of 034

035

8.1

Rel4 29.078-CR300 ASN.1 syntax basic corrections

Alcatel



  •  Approved

025

9.2

R99 23.078-CR521 Correction to SRI Information Flow

Ericsson

  • Rel-4 and Rel-5 copies will be required.

  • Sumio asks if this is a problem because present in the MAP.

  • What is the condition for for sending criteria. For DP12 the criteria is different. S is then the correct specifier for Rel-5. E.g. C1 with description.


  • 4.3.3 should be 4.3.4

  • Subcategory is missing.

  • Revised to 115

115

9.2

R99 23.078-CR521 Correction to SRI Information Flow

Ericsson

  • Revision of 025

  • Approved w/o presentation

116

9.2

Rel-4 23.078-CR543 Correction to SRI Information Flow

Ericsson

  • Revision of 025 for Rel-4

  • Approved w/o presentation

117

9.2

Rel-5 23.078-CR544 Correction to SRI Information Flow

Ericsson

  • Revision of 025 for Rel-5

  • Approved w/o presentation

127





CR 23.018-116 (R99) on Correction to wrong implementation of approved CR 089r2 and 096

Orange

  • N4-030182

  • Exactly same content as original CRs. It was N4-011412 and N4-021033.

  • Is this problem also an error in later releases.

  • Same error is not returned consistently.

  • Cover page: indicate other specs.

  • WI could be CAMEL3.

  • CN2 noted, left to CN4

  • CN4 put this on e-mail approval.

136




CR 29.002-552 (R99) on Incorrect handling of TDP-Criteria for VT-CSI

Ericsson

  • N4-030134

  • This handling only for VT-CSI. This covers the case when HLR is handling wrong.

  • Can the same error happen to D-CSI?

  • Why “data missing”, we send too much data? Jari proposes “unexpected data”.

  • Ulrich says that if no error is sent back, it does not make any difference. The entire dialogue the VT-CSI may be received later on in the same dialogue.

  • If VT-CSI criteria without VT-CSI then VLR can silently discard the criteria.

  • Nokia, Siemens and Nortel wants to reject, even to Rel-5.

  • Withdrawn





7.2

CAMEL3 / ATM&ATSI











7.3

CAMEL3 / GPRS








011

7.3

Handling of AC and ACR in GPRS (revision of N2-021032)

Vodafone

  • According to Rogier reported value may be higher than the requested value.

  • Concept is correct in this document.

  • We’ll have a Rel-5 CR (informative text)

  • We could have a note that reported value is higher than threshold

  • AP: Ask PS core opinion

  • Noted

  • CR in 101

101


7.3

Rel-5 23.078-CR542: Handling of AC and ACR in GPRS (revision of N2-021032)

Vodafone

  • Result of 011

  • Threshold could also exceed due to packet size. This shall be an example.

  • CR# is incorrect.

  • Sumio proposes a informational note in chapter 6.

  • Revised to 152

152

7.3

Rel-5 23.078-CR542: Handling of AC and ACR in GPRS (revision of N2-021032)

Vodafone

  • Revision of 101

  • Approved w/o presentation

063

7.3

Rel5 23.078-CR533 Buffering of TC messages in the SGSN while waiting for the first SCP response

Nokia

  • Sheet 1, output “all saved signals” is not needed because they are handled in the active state anyway. This may have a different result
  • Christian says this changes current behaviour. TC-user should handle the situation. He was convinced later on.


  • Rogier agrees with the principle of the CR.

  • In Opening state TC layer may send Abort to dialogue handler.

  • Active, opening state names could be in a extension box.

  • No change to R99.

  • On cover page state what is correct behaviour.

  •  Revised to 102

102

7.3

Rel5 23.078-CR533 Buffering of TC messages in the SGSN while waiting for the first SCP response

Nokia

  • Revision of 063

  • Rogier: If SCP sends TC-Abort or TC-END then the dialogue handler shall discard all buffered messages (a task box to be introduced, only in the opening state, in other states it will go to the end of queue). The outcome: no new dialogue will be opened. In opening & active state have the discard, in active state there isn’t any -> does not hurt. Christian: discard does not apply to TC-END.-> We discard the save messages if SCP sends TC-ABORT or TC-END in opening state.



  • Revised to 154

154

7.3

Rel5 23.078-CR533 Buffering of TC messages in the SGSN while waiting for the first SCP response

Nokia
  • Revision of 102




  • Approved w/o presentation




7.4

CAMEL3 / MO SMS








049

7.4

R99 29.002-CR  xxx Correction to interactions between CAMEL control of MO SMS and barring

Vodafone

  • N4-030099

  • In the proposal all barring classes are checked after triggering.

  • Nokia, Ericsson want to check unconditional barring classes before triggering, conditional barrings after triggering.

  • 22.078 clause 18.8.1.3 states that no CAMEL is invoked when BAOC.

  • In the text CAMEL is not informed of errors. No true, not triggered yet. There may be if MAP dialogue fallback.

  • Whenever process terminates then SCP shall be informed.

  • In the abandon case MSC shall wait for SMSC response.

  • The spec number could be mentioned, especially when also 29.002 has same input name. Or different message name could be used.

  • Replace O-CSI by SMS-CSI
  • SDL does not show how Suppress-SMS-CSI is handled in the VLR. Christian says it is taken care in the text.


  • Unconditional barrings prior triggering, conditional after triggering.

  • Revised to 103

103

7.4

R99 29.002-CRxxx Correction to interactions between CAMEL control of MO SMS and barring

Vodafone

  • N4-030205, revision of 049

  • Barring done in this CR in 2 phases.

  • Input for MS-A clear is removed -> ignored -> SMSC response is waited for.

  • Ericsson says that other changes but CAMEL need to be postponed. This more limited than the clean-up CR. If all CRs are approved then the spec editing is laborious but can be handled.

  • Sumio wants to know the CN4 result.

  • CN4 e-mail approval, 28.2. deadline for rejection. Next version available 21.2.

  • CN2 endorsed.

050

7.4

Rel4 29.002-CRxxx Correction to interactions between CAMEL control of MO SMS and barring

Vodafone

  • N4-030100

  • Revised to in CN4. CN4 endorsed the revision.

051


7.4

Rel5 29.002-CRxxx Correction to interactions between CAMEL control of MO SMS and barring

Vodafone

  • N4-030101

052

7.4

Rel6 29.002-CRxxx Correction to interactions between CAMEL control of MO SMS and barring

Vodafone

  • N4-030102

  • Revised to in CN4. CN4 endorsed the revision.

053

7.4

R99 23.078-CR527 Correction to interactions between CAMEL control of MO SMS and barring

Vodafone

  • The message name change may impact here.

  • Use of suffixes: Names swapped on each side.

  • R99 uses name SMS-CSI, no MO-SMS-CSI

  • Revised to 104

104


7.4

R99 23.078-CR527 Correction to interactions between CAMEL control of MO SMS and barring

Vodafone

  • Revision of 053

  • Conditionaly approved, condition is 29.002-CR542 approval in CN4

054

7.4

Rel4 23.078-CR528 Correction to interactions between CAMEL control of MO SMS and barring

Vodafone



  •  Revised to 105

105

7.4

Rel4 23.078-CR528 Correction to interactions between CAMEL control of MO SMS and barring

Vodafone

  • Revision of 054

  • Tdoc 054 was Rel-5!!!

  • Conditionally approved. R99 shall be approved.

055

7.4

Rel5 23.078-CR529 Correction to interactions between CAMEL control of MO SMS and barring

Vodafone

  • Wrong tdoc# on the top.



  • Conditionally approved. Condition is CN4 approval for 29.002-CR for Rel-5.






  1   2   3   4


The database is protected by copyright ©hestories.info 2017
send message

    Main page