To: foundation who wrote (32792 ) 2/24/2003 11:24:33 AM From: foundation Read Replies (1) | Respond to of 196809 Release 99 corrections - continued: ========== R2-030182 Proposed CR to 25.331 [R99] on PS service continuity when moving between 3G and 2G Qualcomm R2-030183 Proposed CR to 25.331 [Rel-4 shadow] on PS service continuity when moving between 3G and 2G Qualcomm R2-030184 Proposed CR to 25.331 [Rel-5 shadow] on PS service continuity when moving between 3G and 2G Qualcomm This document was presented by Francesco Grilli from Qualcomm. Discussion: First issue: Is there a need to add the target cell not supporting GPRS ? Answer: In case of GPRS maintenance, the UE may be sent to a cell not supporting GPRS. Question: In 8.3.10.2, what was the reason for the deletion of the sentence (the establishment cause) ? Answer: Because this contredicts the layering independency between the NAS and the AS. Which cause shall be sent first ? This cause value will be prioritised over the NAS value, for those two procedures. The cell change order procedure reference on the coversheet is not necessary. The note should be changed. Question: What is the meaning of “release all UTRAN specific information in the IE” ? Answer: Deleting the U-RNTI. Comment: We should refer to the state transition clause instead. Decision: The CR was revised into R2-030459. R2-030459 Proposed CR to 25.331 [R99] on PS service continuity when moving between 3G and 2G Qualcomm This document was presented by Francesco Grilli from Qualcomm. Discussion: Decision: The CR was revised into R2-030583, R2-030584 and R2-030585. CR numbers 1888, 1889, 1890. R2-030583 Proposed CR 1888 to 25.331 [R99] on PS service continuity when moving between 3G and 2G Qualcomm R2-030584 Proposed CR 1889 to 25.331 [Rel-4 shadow] on PS service continuity when moving between 3G and 2G Qualcomm R2-030585 Proposed CR 1890 to 25.331 [Rel-5 shadow] on PS service continuity when moving between 3G and 2G Qualcomm This document was presented by Francesco Grilli from Qualcomm. Discussion: Decision: The CRs were agreed (as they were). R2-030512 Proposed CR 1869 to 25.331 [R99] on Start time of Security NEC R2-030513 Proposed CR 1870 to 25.331 [Rel-4 shadow] on Start time of Security NEC R2-030514 Proposed CR 1871 to 25.331 [Rel-5 shadow] on Start time of Security NEC This document was presented by Michael Roberts from NEC. Discussion: Decision: The CRs were revised into R2-030602, R2-030603 and R2-030604. R2-030602 Proposed CR 1869rev1 to 25.331 [R99] on Start time of Security NEC R2-030603 Proposed CR 1870rev1 to 25.331 [Rel-4 shadow] on Start time of Security NEC R2-030604 Proposed CR 1871rev1 to 25.331 [Rel-5 shadow] on Start time of Security NEC Those documents were withdrawn. R2-030185 Proposed CR to 25.331 [R99] on Multiple activations of the same compressed mode pattern Qualcomm R2-030186 Proposed CR to 25.331 [Rel-4 shadow] on Multiple activations of the same compressed mode pattern Qualcomm R2-030187 Proposed CR to 25.331 [Rel-5 shadow] on Multiple activations of the same compressed mode pattern Qualcomm This document was presented by Francesco Grilli from Qualcomm. Discussion: There are other possible cases. 2 companies preferred to keep the “shall” for the Rel-4. 1 company thought this was not needed for the Rel-4 and Rel-5. It was decided not to specify this scenario. This will be merged with another CR. Decision: The document was noted. Later on, it was decided to revise the documents instead. In R2-030533, R2-030534 and R2-030535. R2-030533 Proposed CR to 25.331 [R99] on Multiple activations of the same compressed mode pattern Qualcomm R2-030534 Proposed CR to 25.331 [Rel-4 shadow] on Multiple activations of the same compressed mode pattern Qualcomm R2-030535 Proposed CR to 25.331 [Rel-5 shadow] on Multiple activations of the same compressed mode pattern Qualcomm This document was presented by Francesco Grilli from Qualcomm. Discussion: Decision: The CRs were agreed into R2-030586, R2-030587 and R2-030588. CRs 1891, 1892 and 1893. Following the meeting, an updated was deemed required and the CRs were revised again into R2-030631, R2-030632 and R2-030633 (CRs 1891rev1, 1892rev1 and 1893rev1). R2-030207 Proposed CR to 25.331 [R99] on Correction on RRC integrity protection procedure LG Electronics Inc. R2-030208 Proposed CR to 25.331 [Rel-4 shadow] on Correction on RRC integrity protection procedure LG Electronics Inc. R2-030209 Proposed CR to 25.331 [Rel-5 shadow] on Correction on RRC integrity protection procedure LG Electronics Inc. This document was presented by Sung Duck Chun from LG Electronics. Discussion: The text could be simplified. The sentence (on the storage) will be changed. Decision: The CRs were revised into R2-030462, R2-030463 and R2-030464. CR numbers are 1832, 1833 and 1834. R2-030462 Proposed CR 1832 to 25.331 [R99] on Correction on RRC integrity protection procedure LG Electronics Inc. R2-030463 Proposed CR 1833 to 25.331 [Rel-4 shadow] on Correction on RRC integrity protection procedure LG Electronics Inc. R2-030464 Proposed CR 1834 to 25.331 [Rel-5 shadow] on Correction on RRC integrity protection procedure LG Electronics Inc. This document was presented by Sung Duck Chun from LG Electronics. Discussion: The requirement on the storage was challenged. There is several unnecessary text. Decision: The CRs were revised into R2-030589, R2-030590 and R2-030591. R2-030589 Proposed CR 1832rev1 to 25.331 [R99] on Correction on RRC integrity protection procedure LG Electronics Inc. R2-030590 Proposed CR 1833rev1 to 25.331 [Rel-4 shadow] on Correction on RRC integrity protection procedure LG Electronics Inc. R2-030591 Proposed CR 1834rev1 to 25.331 [Rel-5 shadow] on Correction on RRC integrity protection procedure LG Electronics Inc. This document was presented by Sung Duck Chun from LG Electronics. 8.5.10.1: change needed. Discussion: The CRs were agreed into R2-030614, R2-030615 and R2-030616. R2-030219 Proposed CR to 25.331 [R99] on Reporting cell status and event 2A Nokia R2-030220 Proposed CR to 25.331 [Rel-4 shadow] on Reporting cell status and event 2A Nokia R2-030221 Proposed CR to 25.331 [Rel-5 shadow] on Reporting cell status and event 2A Nokia This document was presented by Thomas Balon from Nokia. Discussion: Decision: The CRs were agreed into R2-030465, R2-030466 and R2-030467. CR numbers are 1835, 1836 and 1837. R2-030222 Proposed CR to 25.331 [R99] on Invalid CM configuration and number of supported number of CM patterns Nokia R2-030223 Proposed CR to 25.331 [Rel-4 shadow] on Invalid CM configuration and number of supported number of CM patterns Nokia R2-030224 Proposed CR to 25.331 [Rel-5 shadow] on Invalid CM configuration and number of supported number of CM patterns Nokia This document was presented by Thomas Balon from Nokia. Discussion: Do we need to allow to alternate between patterns, or not ? Two companies felt that the restriction was unacceptable. Decision: The document was noted. R2-030249 Proposed CR to 25.331 [R99] on Correction to measurement related procedures ASUSTeK R2-030250 Proposed CR to 25.331 [Rel-4 shadow] on Correction to measurement related procedures ASUSTeK R2-030251 Proposed CR to 25.331 [Rel-5 shadow] on Correction to measurement related procedures ASUSTeK This document was presented by Rex Chen from ASUSTeK. Discussion: Are the two flags needed ? Decision: The CRs were agreed into R2-030468, R2-030469 and R2-030470. CRs 1838, 1839 and 1840. R2-030257 Proposed CR to 25.331 [R99] on Hard handover with pending ciphering activation times Ericsson R2-030258 Proposed CR to 25.331 [Rel-4 shadow] on Hard handover with pending ciphering activation times Ericsson R2-030259 Proposed CR to 25.331 [Rel-5 shadow] on Hard handover with pending ciphering activation times Ericsson This document was presented by Anders from Ericsson. Discussion: The wording needs to be refined. The consequences if not approved needs to be improved. Do we keep a “should” or a “shall” for the R’99 ? Comment: The L1 would still work correctly, so the call would not fail. What does the “immediately” mean ? It could cause out_of_sync if UE and UTRAN understand it differently ? Decision: The CRs were agreed into R2-030471, R2-030472 and R2-030473. CR numbers are 1841, 1842 and 1843. Later-on, they were revised (Rev1) in order to be merged with the revision of the Motorola CRs. In tdocs R2-030480, R2-030481 and R2-030482. R2-030270 Proposed CR to 25.331 [R99] on Correction to default configurations Motorola R2-030271 Proposed CR to 25.331 [Rel-4 shadow] on Correction to default configurations Motorola R2-030272 Proposed CR to 25.331 [Rel-5 shadow] on Correction to default configurations Motorola This document was presented by Richard Burbidge from Motorola. Discussion: The consequences if not approved need to be improved. Decision: The CRs were agreed into R2-030474, R2-030475 and R2-030476. CR numbers are 1844, 1845 and 1846. R2-030334 Proposed CR to 25.331 [R'99] on UE behaviour on entering RRC Connected mode Ericsson R2-030335 Proposed CR to 25.331 [Rel-4 shadow] on UE behaviour on entering RRC Connected mode Ericsson R2-030336 Proposed CR to 25.331 [Rel-5 shadow] on UE behaviour on entering RRC Connected mode Ericsson This document was presented by Anders from Ericsson. Discussion: Isolated impact. Decision: The CRs were agreed into R2-030477, R2-030478 and R2-030479. CRs numbers are 1847 1848 and 1849. R2-030400 Proposed CR to 25.331 [R99] on Integrity Protection Activation in case of lost messages Motorola R2-030348 Proposed CR to 25.331 [Rel-4 shadow] on Integrity Protection Activation in case of lost messages Motorola R2-030349 Proposed CR to 25.331 [Rel-5 shadow] on Integrity Protection Activation in case of lost messages Motorola This document was presented by Ravi K. from Motorola. Discussion: The term “greater” was challenged. Decision: The CRs were agreed into R2-030480, R2-030481 and R2-030482. CR numbers are 1841Rev1, 1842Rev1 and 1843Rev1 (because the revision was merged later-on with the revision of the Ericsson CRs that were R2-030471, R2-030472 and R2-030473). R2-030401 Proposed CR to 25.331 [R99] on HFN increment in HHO Motorola R2-030377 Proposed CR to 25.331 [Rel-4 shadow] on HFN increment in HHO Motorola R2-030378 Proposed CR to 25.331 [Rel-5 shadow] on HFN increment in HHO Motorola This document was presented by Ravi K. from Motorola. Discussion: Decision: The CRs will be merged with the (previous) CR on integrity protection. R2-030402 Proposed CR to 25.331 [R99] on START value updates in USIM when transitioning to GSM Motorola R2-030380 Proposed CR to 25.331 [Rel-4 shadow] on START value updates in USIM when transitioning to GSM Motorola R2-030381 Proposed CR to 25.331 [Rel-5 shadow] on START value updates in USIM when transitioning to GSM Motorola This document was presented by Ravi K. from Motorola. Discussion: The UE “should” will be used instead, in the first paragraph in 8.5.8. Also, the ciphering key will not be deleted anymore when going to GSM. But then, what if we have a selection back to the UTRAN ? This is a Network Operator setting to change the keys. If the SIM is present (…) “store this value” will be changed. Decision: The CRs were revised into R2-030483, R2-030484 and R2-030485. CRs 1853, 1854 and 1855. They will be presented after the Nokia document on this subject (R2-030458). R2-030483 Revised CR 1853 to 25.331 [R99] on START value updates in USIM when transitioning to GSM Motorola R2-030484 Revised CR 1854 to 25.331 [Rel-4 shadow] on START value updates in USIM when transitioning to GSM Motorola R2-030485 Revised CR 1855 to 25.331 [Rel-5 shadow] on START value updates in USIM when transitioning to GSM Motorola This document was presented by Ravi K. from Motorola. Discussion: Comment on subclause 8.5.2. Discussion: The CRs were agreed (as they were). R2-030387 Proposed CR to 25.331 [R99] on Corrections to Channelisation Code TFCI Mapping for TDD Interdigital R2-030388 Proposed CR to 25.331 [Rel-4 shadow] on Corrections to Channelisation Code TFCI Mapping for TDD Interdigital R2-030389 Proposed CR to 25.331 [Rel-5 shadow] on Corrections to Channelisation Code TFCI Mapping for TDD Interdigital This document was presented by Daniel Tsui from Interdigital. Discussion: This CR is linked with a CR in RAN WG3. Decision: The CRs were agreed into R2-030486, R2-030487 and R2-030488. CR numbers are 1856, 1857 and 1858. R2-030395 Withdrawn CR to 25.331 [R99] on Cell update and URA update when moving back to inservice NEC R2-030396 Proposed CR to 25.331 [Rel-4 shadow] on Cell update and URA update when moving back to inservice NEC R2-030397 Proposed CR to 25.331 [Rel-5 shadow] on Cell update and URA update when moving back to inservice NEC This document was withdrawn before presentation. R2-030508 Proposed CR to 25.331 on Setting of Ciphering activation time for TM bearers Nortel This document was presented by Tania Godard from Nortel. This CR is linked with the CR in R2-030507. Discussion: Comments on the wording were received. Decision: We will come-back on it. The document was then revised into R2-030527. R2-030527 Revised CR to 25.331 on Setting of Ciphering activation time for TM bearers Nortel This document was presented by Tania Godard from Nortel. Discussion: Alignment in 8.2.2.3 is needed in the Rel-5. Decision: The CRs were agreed into R2-030592, R2-030593 and R2-030594. CR numbers 1894, 1895, 1896. Separate CR for the Rel-5 (correction to subclause 8.2.2.3): R2-030595. CR number 1897 (agreed). 6.14 Proposed changes on 25.921 There was no input for this agenda item. 6.15 Proposed changes on 25.922 R2-030243 Proposed CR to 25.922 [R99] on Power control during RRC Connection release procedure Nokia R2-030244 Proposed CR to 25.922 [Rel-4 shadow] on Power control during RRC Connection release procedure Nokia R2-030245 Proposed CR to 25.922 [Rel-5 shadow] on Power control during RRC Connection release procedure Nokia This document was presented by Luis Barreto from Nokia. Discussion: Decision: The understanding of the CR was considered correct, however this did not justified a Change Request. The document was noted. 6.16 Proposed changes on 25.925 There was no input for this agenda item. 6.17 Proposed changes on 25.993 on RAB/RB examples R2-030171 Proposed CR to 25.993 [R99] on Streaming and interactive/background RAB combinations Nokia This document was presented by Juha Mikola from Nokia. Discussion: What is the difference between the streaming and the interactive/background RAB, in this case ? The RBs are decoupled with the RABs in this report. Only the uplink/downlink combination is new. Do we really need 32, or 64 classes ? The number of classes needs to be checked. Why do we need 5 new RAB combinations in table 5.1 ? Decision: The CR was approved into R2-030489, CR 001. 6.18 Proposed changes on 34.109 R2-030428 Agreed CR 023 to 34.109 [R99] on the Removal of uplink dummy DCCH transmission function in UE Panasonic R2-030429 Agreed CR 024 to 34.109 [Rel-4 shadow] on the Removal of uplink dummy DCCH transmission function in UE Panasonic R2-030430 Agreed CR 025 to 34.109 [Rel-5 shadow] on the Removal of uplink dummy DCCH transmission function in UE Panasonic Those CRs were agreed following the LS in R2-030398.