continued "...elements of R4 are completed and frozen and it is about to be published..." continued
----------
Eric,
Here is an excerpt from the Jan 15 3GPP TSG-RAN WG1 draft minutes as submitted at March 2, Las Vegas meeting (I don't have URL - received via email - will send it to you if you like.)
----------
Report from TSG RAN#10 From Bangkok (R1-01-0067)
1. Release 99 CRs
All Release '99 CRs WG1 presented were approved by TSG RAN.
2. Open item for release 99
1st interleaver memory with the UE capabilities was reported to TSG RAN as an open Release'99 item under
discussion in WG1
3. TS on UE capabilities
New Release'99 specification was created out of TR 25.926. TS 25.306 replaced TR 25.926, with the first version
3.0.0 as agreed in TSG RAN. Thus any UE capability issue (FDD or TDD) is to be reflected for TS 25.306.
The 1.28 Mcps TDD UE capabilities need to be reflected to this TS as well. The TR on 1.28 Mcps TDD UE
capabilities is for 3GPP internal use only (as all 25.8xx series).
(Chairman clarified this because there had been a question in the RAN WG1#17 meeting whether there would be a
separated specific TR on 1.28 TDD UE capabilities. Now it was clarified that all UE capabilities issues should
finally go to TS 25.306.)
4. How to proceed with CRs for release 99 and release 4
- In case we produce CRs which would impact both releases then 2 sets of agreed CRs need to be created - i.e. one
per release.
- But before release 4 specifications have been created, even if the change will impact on both release, the only CR
for release 99 is to be made. MCC will implement release 99 CRs until release 4 specifications have been
created. When creating release 4 specifications, all TSG approved CRs for release 99 shall also be implemented
in the release 4 version.
- Once release 4 specifications have been created, then those release 4 specifications would deviate from release 99
specifications by being applied release 4 specific CRs
5. Release 4/5 issues
1) Terminal power saving feature (DPCCH gating)
- The WG1 TR 25.840 was presented to TSG RAN as 2.0.0.
- The milestone remained 03/01.
- WG2 reported uncertainty whether they have conclusions/consensus on all the aspects of this feature for
03/01. WG1 TR stayed as 2.0.0
- Impact of compressed mode (on the gains) was mentioned as one issue which WG1 should cover as well.
2) DSCH power control improvement in soft handover
- TR 25.841 was presented and approved by TSG RAN.
- TR is now version 4.0.0 and under CR process if there is need for change.
- WG3 has draft TR on this under preparation
3) TDD Node B synchronization
- The TR 25.836 was presented and approved by TSG RAN to 4.0.0
- The milestone was kept as 03/01
4) Uplink Synchronous Transmission Scheme
- WG1 indicated that study report would be delivered 03/01
- The milestone for the study report was kept was 03/01
5) 1.28Mcps (Low Chip Rate) UTRA TDD Physical Layer
- There was not much discussion on RAN WG1 issues.
- Issues to work with still as reported to TSG RAN
o l: Uplink synchronization
o2: Handover measurements for GSM for data rates above 32 kbits/s
- TDD status of co-existence studies were briefly discussed in TSG RAN.
It was decided that the base station to base station interference scenario needs to be further analysed
and solutions for interworking needs to be found. RAN WG4 was tasked to do this work.
- RAN WG1 was requested to submit TR 25.928 for approval for RAN for RAN #11 although we are now
working on Working CRs.
6) Smart Antennas
Work item was deleted. There was no topic identified to be worked on under this work item.
7) High Speed Downlink Packet Access (HSDPA)
- There had been activity only in RAN WG1 on this topic (since TSG RAN#9).
- RAN WG2 expected to address the topic beginning of this week (Jan 15 -16).
oSome inputs from RAN WG2 could be expected during RAN WG1#18 meeting.
- Joint Ad Hoc between RAN WG1 and RAN WG2 was suggested by TSG RAN. This will be coordinated with
RAN WG2 chairman after the RAN WG2 has addressed HSDPA during their current meeting.
8) Other Topics
-Hybrid ARQ
No activity reported, most likely to be covered as part of HSDPA
- Improved cell FACH state
No activity reported
- Positioning
WG1 chairman's understanding is that OTDOA-PE method is not for Release 4 time frame.
- Tx Diversity
We aim to have our conclusion for June for release 5.
9) TSG RAN/SA level workshops agreed
- TSG RAN Workshop UTRAN Evolution, Feb. 5-6
Based on the contributions presented in TSG RAN#10, TSG RAN felt that there is a need to organize a
2-day workshop discussing the UTRAN evolution beyond Release 4, i.e., on IP based UTRAN architecture,
Iub, Iur, Iu and possible new internal UTRAN interfaces. The goal of the workshop is to identify
requirements for the UTRAN evolution in co-operation with other groups that may have requirements or
otherwise are linked to the UTRAN evolution. In addition, individual companies are invited to provide their
vision of the UTRAN evolution.
- TSG SA workshop UE in idle mode, Feb 7-8
The goal of the workshop is to review and address the following topics, both from a requirement and
functional point of view:
oPLMN selection
oCell selection and reselection
oHandovers
----------
The document continues with a mind numbing on these outstanding issues. My sincere impression is that they are far from frozen.
The 03/01 R4 milestone was noted to have remained "in place" for portions of the work.
But if they can keep so many participants in line and achieve this deadline - without postponing the majority of the issues to R5, they should herd cats for a hobby.
I can attest with confidence that my earlier statements regarding progress, or more accurately the lack thereof, are accurate as regards HSDPA development.
ben |
