UMTS Release 99 corrections continued:
==========
R2-022113 Proposed CR to 25.331 [R'99] on Correction of Transmission Gap Distance semantics description Nokia
R2-022114 Proposed CR to 25.331 [Rel-4 shadow] on Correction of Transmission Gap Distance semantics description Nokia
R2-022115 Proposed CR to 25.331 [Rel-5 shadow] on Correction of Transmission Gap Distance semantics description Nokia
Presented by Gairn Kalla from Nokia. Initially sent for the Rel-4, but clarification to the TGL2 parameter was also needed for the R’99.
Discussion:
Decision: Agreed into R2-02 2304, R2-02 2305 and R2-022306. CR numbers in 1624, 1625 and 1626.
R2-022141 Proposed CR to 25.331 [R'99] on Active Set Update and simultaneous reconfiguration Motorola
R2-022142 Proposed CR to 25.331 [Rel-4 shadow] on Active Set Update and simultaneous reconfiguration Motorola
R2-022143 Proposed CR to 25.331 [Rel-5 shadow] on Active Set Update and simultaneous reconfiguration Motorola
Presented by Ravi.
Discussion:
Decision:
Agreed into R2-02 2307, R2-02 2308 and R2-022309. CR numbers in 1627, 1628 and 1629.
R2-022147 Proposed CR to 25.331 [R'99] on UE behaviour following RLC size change Motorola
R2-022148 Proposed CR to 25.331 [Rel-4 shadow] on UE behaviour following RLC size change Motorola
R2-022149 Proposed CR to 25.331 [Rel-5 shadow] on UE behaviour following RLC size change Motorola
Presented by Ravi.
Discussion:
The text needs to be re-phrased.
Comment: A cell update is performed when the UE change cells. RRC Info can be sent to the UE if it does not change cell and the SIB is updated.
Decision:
Revised into R2-02 2310, R2-02 2311 and R2-022312. CR numbers in 1630, 1631 and 1632.
R2-022310 Proposed CR 1630 to 25.331 [R'99] on UE behaviour following RLC size change Motorola
R2-022311 Proposed CR 1631 to 25.331 [Rel-4 shadow] on UE behaviour following RLC size change Motorola
R2-022312 Proposed CR 1632 to 25.331 [Rel-5 shadow] on UE behaviour following RLC size change Motorola
Presented by Ravi from Motorola.
Discussion:
Decision: The CRs are agreed as they are (‘desist’ means ‘avoid’).
R2-022160 Proposed CR to 25.331 [R'99] on RRC SN in uplink Qualcomm
R2-022161 Proposed CR to 25.331 [Rel-4 shadow] on RRC SN in uplink Qualcomm
R2-022162 Proposed CR to 25.331 [Rel-5 shadow] on RRC SN in uplink Qualcomm
Presented by Francesco from Qualcomm.
Discussion:
Question: Is the sequence number respective to the transaction Id or not ?
Answer: It is independent.
Question: Then what if the first message is repeated, with parallel transactions ?
Answer: This is incremented for repetitions in the uplink (8.5.10.2) for the UE.
Question: Has the UE to recalculate the message identification code ?
Answer: Yes, and this is put in the integrity info. The MAC-I has to be re-calculated every time.
Comment: the note looks like a duplication of the following section.
Comment: What does not work today if the UE implements it twice ?
Answer: If it implements it twice, you just increment the risk of going out of sync. But if you do not increment it at cell update, you would go out of sync immediately.
Comment: No, this is already covered by the cell update procedure.
The version number is incorrect.
Decision:
We just keep the note and delete the rest.
Agreed into R2-02 2313, R2-02 2314 and R2-02 2315. CR numbers in 1633, 1634 and 1635.
R2-022220 Proposed CR to 25.331 [R'99] on Multiplexing of Tr mode RBs of different CN domains on the same transport channel Qualcomm
R2-022164 Proposed CR to 25.331 [Rel-4 shadow] on Multiplexing of Tr mode RBs of different CN domains on the same transport channel Qualcomm
R2-022165 Proposed CR to 25.331 [Rel-5 shadow] on Multiplexing of Tr mode RBs of different CN domains on the same transport channel Qualcomm
Discussion:
Decision:
Agreed into R2-02 2316, R2-02 2317 and R2-02 2318. CR numbers in 1636, 1637 and 1638.
R2-022166 Proposed CR to 25.331 [R'99] on Uplink ciphering activation time info Qualcomm
R2-022167 Proposed CR to 25.331 [Rel-4 shadow] on Uplink ciphering activation time info Qualcomm
R2-022168 Proposed CR to 25.331 [Rel-5 shadow] on Uplink ciphering activation time info Qualcomm
Presented by Francesco from Qualcomm.
Discussion:
Decision: Withdrawn.
R2-022169 Proposed CR to 25.331 [R'99] on Security clarifications Qualcomm
R2-022170 Proposed CR to 25.331 [Rel-4 shadow] on Security clarifications Qualcomm
R2-022171 Proposed CR to 25.331 [Rel-5 shadow] on Security clarifications Qualcomm
Presented by Francesco from Qualcomm.
Discussion:
Decision:
We keep only one sentence saying in 6.3 that RB0 is not ciphered.
Agreed into R2-02 2319, R2-02 2320 and R2-02 2321. CR numbers in 1639, 1640 and 1641.
R2-022172 Proposed CR to 25.331 [R'99] on Association of compressed mode patterns to measurements Qualcomm
R2-022173 Proposed CR to 25.331 [Rel-4 shadow] on Association of compressed mode patterns to measurements Qualcomm
R2-022174 Proposed CR to 25.331 [Rel-5 shadow] on Association of compressed mode patterns to measurements Qualcomm
Presented by Francesco Grilli from Qualcomm.
Discussion:
Decision:
Withdrawn. The understanding of the CR is correct but no CR is needed.
R2-022183 Proposed CR to 25.331 [R'99] on Correction to the actions of Out of service area and In service area ASUSTeK
R2-022184 Proposed CR to 25.331 [Rel-4 shadow] on Correction to the actions of Out of service area and In service area ASUSTeK
R2-022185 Proposed CR to 25.331 [Rel-5 shadow] on Correction to the actions of Out of service area and In service area ASUSTeK
Discussion:
There is no need for the second change.
Decision:
Second change removed, first one kept.
Agreed into R2-02 2322, R2-02 2323 and R2-02 2324. CR numbers in 1642, 1643 and 1644.
R2-022190 Proposed CR to 25.331 [R'99] on TVM pending time after trigger and initial conditions Ericsson
R2-022191 Proposed CR to 25.331 [Rel-4 shadow] on TVM pending time after trigger and initial conditions Ericsson
R2-022192 Proposed CR to 25.331 [Rel-5 shadow] on TVM pending time after trigger and initial conditions Ericsson
Discussion:
Decision:
Agreed into R2-02 2325, R2-02 2326 and R2-02 2327. CR numbers in 1645, 1646 and 1647.
R2-022193 Proposed CR to 25.331 [R'99] on Handling of Downlink information for each RL in reconfiguration messages Ericsson
R2-022194 Proposed CR to 25.331 [Rel-4 shadow] on Handling of Downlink information for each RL in reconfiguration messages Ericsson
R2-022195 Proposed CR to 25.331 [Rel-5 shadow] on Handling of Downlink information for each RL in reconfiguration messages Ericsson
Presented by Gert-Jan from Ericsson.
Discussion:
A document from Qualcomm has one point that deals with that.
What does “the UE would remain” mean ?
In bullet 2, “which are all parts”: What is the intention ?
Decision:
Agreed into R2-02 2328, R2-02 2329 and R2-02 2330. CR numbers in 1648, 1649 and 1650.
Later-on during the week, those CRs were further revised by Motorola in R2-02 2442, R2-02 2443 and R2-02 2444. Agreed.
6.14 Proposed changes on 25.921
There was no input for this agenda item.
6.15 Proposed changes on 25.922
R2-022084 Proposed CR to 25.922 [R'99] on Aligment of the definition of the term "Active Set" with 21.905 and related text corrections Philips
R2-022085 Proposed CR to 25.922 [Rel-4 shadow] on Aligment of the definition of the term "Active Set" with 21.905 and related text corrections Philips
R2-022086 Proposed CR to 25.922 [Rel-5 shadow] on Aligment of the definition of the term "Active Set" with 21.905 and related text corrections Philips
Presented by Christoph Hermann from Philips.
Discussion: What is the system level problem that we are fixing with this CR ? This CR is not an essential correction. This could be done for the Rel-5 (but then this would be more than a section).
More generally, what is the purpose of this TR now ? What is the added value in maintaining it for the R’99 ?
The initial purpose of the TR was to provide guidelines on how the system was working.
This was a sort of Stage 2 for RRM and to gives examples on how RRM could be implemented by operators.
Decision: The change as it is was felt as not required for the R’99.
6.16 Proposed changes on 25.925
There was no input for this agenda item.
6.17 Proposed changes on 34.109
R2-021938 Proposed CR to 34.109 [R'99] on Correction of figure 5.3.2.6.1.1 Ericsson
Discussion:
Decision:
Agreed in Tdoc R2-02 2408 and CR 019.
(No shadow CRs were needed as the Rel-4 and Rel-5 are correct).
6.18 TSG-T WG1-related activities
6.18.1 Misalignments between Test Specifications and Core Specifications
There was no input for this agenda item.
6.18.2 Proposed additions of test cases
R2-021881 Proposed CR to 34.108 [R'99] for the Introduction of streaming 16/128 kbps PS RAB + Interactive or background 8/8 kbps PS RAB + 3.4 kbps SRB T-Mobile, Siemens
R2-021882 Proposed CR to 34.108 [Rel-4 shadow] for the Introduction of streaming 16/128 kbps PS RAB + Interactive or background 8/8 kbps PS RAB + 3.4 kbps SRB T-Mobile, Siemens
Discussion:
Question: Is there a real need for this ?
The PS RABs are not covered sufficiently enough in 34.108.
Decision: We ask RAN1 to endorse the CRs. RAN in copy to have the discussion at the plenary on what to do generally with 34.108. Shall we carry-on to add new RABs, or not ? The situation is that 34.108 has various uses. The LS is in tdoc R2-022412. We leave for the RAN plenary to decide. |
