What
is a Release? | What's
in Release 5?|
What's in Release 6?
| TSG T
| TSG
CN | TSG
SA | TSG
RAN |
Previous Highlights: TSG#15 | TSG#16 | TSG#19 | TSG#20 | TSG#21
Welcome to the latest edition of TSG Highlights! The aim is to provide you with a concise summary of the decisions and actions of the most recent 3GPP Technical Specification Group meetings in December 2004 in Hawaii, USA.
3GPP has five TSGs: CN (Core Network); RAN (Radio Access Network); T (Terminals); SA (Services and Systems Aspects); and GERAN (GSM EDGE Radio Access Network). This summary reports on the first four of these, as GERAN meetings take place separately from the other TSGs.
Please note, these summaries to do not constitute formal, approved reports of the meetings – they are opinions only and also may not be complete. They are offered for guidance only.
For an overview of 3GPP Release 5 please have a look at this document which has been produced by the ETSI Mobile Competence Centre and which is a summary of all Release 5 Features>
The expected contents of Release 6 (and even what lies beyond Release 6) can be found in the 3GPP workplan .
Once again this was a highly productive meeting with Change Requests (CR) being approved that concluded several issues:
The freeze date for the stage 2 specification (the date at which no further category B,C CRs are accepted to stage 2 specifications) is set for March. There may of course be exceptions to this rule taken on a case by case basis. No overall freeze date (stage 3 freeze) was agreed in TSG-SA.
It was agreed by TSG-SA that relative timing MAY be used in stage 3 Work Item Descriptions (WIDs) (at the Working Groups' discretion). This recommendation was taken from NP-030586. This may save having to update WIDs especially in the case where there is slippage in stage 1 or stage 2, yet stage 3 work hasn't actually started.
An Liaison Statement (LS) was received from ETSI Electronic Communications Networks and Services Directives (ECN&S) Specialist Task Force STF254, requesting information relating to the European Commission's Framework Directive Article 17 "List of Standards".
TSG-CN briefly examined the list during the meeting and found a number of major errors. Although there was some level of reticence to complete the list, it was agreed by CN to discuss the list on the CN email exploder, in order to provide a best effort list for Article 17.
However TSG-SA took a decision that reviewing the candidate 3GPP specifications for inclusion in Article 17 list of standards (NP-030573) was outside of the scope of 3GPP. Based upon this decision 3GPP will not pursue the CN plan of providing comments on the CN reflector.
Stephen Hayes (CN Chair) agreed to provide Marie-Michele Vassiliou (ETSI STF254) with the input already received from the Working Group CN2 and CN5 chairs but indicate that no additional information should be expected. Individual companies are however welcome to send comments directly to Marie-Michele Vassiliou.
An agreement was reached with the GSM Association (GSMA) on the proper use of ".3gppnetwork.org" for non-Legacy services and maintenance of the ".3gppnetwork.org" domain. A LS from CN was sent to GSMA IREG (NP-030587) to inform them of the following TSG-CN conclusions:
TSG_SA agreed that charging will not move into TSG_CN. SA5 Sub-Working Group SWGB was urged to coordinate more closely with other WGs. This may include additional joint meetings
The recent 3GPP Project Co-ordination Group recommendation states that only one WG meeting is allowed between the Plenary meetings. It is however possible to ask for support for extra meetings.
TSG CN requested MCC support for the following additional WG meetings:
This meeting
approved 317 Change Requests (CR) (216 excluding Category A).
The following
Technical Specifications (TS) were also approved:
TR 25.833 (R99), Physical layer
items not for inclusion in Release 99
TR 25.840 (Release-4), Terminal
power saving features
TSG RAN Working Groups WG2
and WG3 have planned to have six meetings next year (four is the general rule
for 3GPP WGs). WG1 and WG4 will aim for co-located meeting to ensure optimum
co-ordination for new work.
TSG RAN will produce
Release-6 versions of most of its specifications after this meeting (December
2003) due to the requirements for Update 4 of ITU-R Recommendation M.1457.
The Terms of
Reference of WG3 have been updated to align with the current focus of the work,
to include UTRAN synchronisation, Iupc protocols and the application of Radio
Access Network Application Part (RANAP) to the E-interface.
Update 5 of ITU-R
Recommendation M.1457 was presented. An action plan to comply with the schedule
for submission in ITU-R was shown., and a first proposal for this update,
presenting a top level description of open features in UTRAN, was presented and
endorsed.
A proposal for
improving the accuracy of the Work Plan was presented by the 3GPP support.
Basically, it is suggested to estimate the duration of a WI instead of its
completion date. No objections were raised
Certain Release '99
CRs that had been agreed by the WGs were rejected by the TSG, on the basis of
the guidelines approved in document RP-020448, as it was not proven that they
were essential for the system to work.
The freezing of
Abstract Syntax Notation No.1 (ASN.1) documents in WG2 and WG3 was discussed.
Freezing of the ASN.1 for 25.331 (Radio Resource Control, RRC) required
alignment between WG2 and WG3 (RP-030666).
Companies expressed
different views concerning the need for Time Division Duplex Uplink Shared
Channel (TDD USCH) to operate with Release-5 High Speed Downlink Packet Access,
HSDPA (RP-030708). Consequently, HSDPA/USCH operation in Release 6, still an
open Release, will be considered. Proposals in this sense are welcome in the
future.
Interworking solution
3, for the interworking of ATM based and IP based UTRAN nodes, is still
unspecified in Release-5. Proposals to use ITU-T Q.2631.1 or IETF PWE3, the
latter still in draft, were considered, and WG3 was tasked to recommend a
solution for the next meeting (RP-030667).
A joint WG1-WG4 Ad
Hoc will be convened to examine issues related to analysis in WG4 that has shown
that a significant increase in Peak-to-Average Ratio (PAR) is produced when High
Speed Dedicated Physical Control Channel (HS-DPCCH) is transmitted, due to the
introduction of a new code. The meeting will consider a WG4 proposal to reduce the
maximum output power when the HS-DPCCH is transmitted, given the possible
impacts this could have on other areas.
The Work
Item on Beamforming Enhancements has been completed and the necessary CRs have
been approved.
The Work Items for the introduction of UMTS in the 800 MHz band in Japan and the 850 MHz band in the US are completed and CRs have been approved. Only a minor CR for the introduction of the signalling in 25.331 to support UMTS850 is missing. Although using the same frequencies, some of the RF requirements are different in each UMTS band due to the different regional conditions and co-existence analysis performed.
The work
on Assisted Global Positioning System (A-GPS) performance requirements is
progressing in WG4, and a new specification is being drafted. The completion
date is June 2004.
The
scope of the Orthogonal Frequency Division Multiplexing (OFDM) feasibility study
has been reduced in order to comply with the June 2004 time schedule. It was
agreed to conclude a first stage where the feasibility of the technique within
the UTRAN was proved, and to start extensive evaluation and simulation
afterwards, once a Work Item has been approved by the Project Co-ordination
Group.
A new
Building Block, under the responsibility of WG4, has been approved:
Improved Receiver Performance
Requirements for HSDPA (RP-030732)
Under this Building Block, a Work Task has been also approved:
Performance Requirements of
Receive Diversity for HSDPA (RP-030731)
Completion date for both items is September 2004.
The TSG took note of ongoing work in WG4 on defining the means to perform Node B RF tests over the Iub interface (RP-030714).
At its
recent meeting in December 2003 in Maui, Hawaii, USA, TSG-T has been working on
the maintenance of the existing Releases, and has continued work on Release 6.
Work on testing always follows the main specification task, and this is so for
User Equipment (UE) testing, which is ongoing for Release 99, Release 4, and for
Release 5 (see the "Testing" section below).
Maintenance
work was performed on the existing Releases of Multimedia Messaging Service
(MMS) specifications and some new functionality has been added to Release 6. MMS
Release 6 will add new functionality to the existing MMS standard in several
areas which will further enhance the user experience. Two new work items related
to MMS were approved. The new work item on handling
of private addressing schemes in MMS will support use cases for Virtual Private
Network (VPN) addressing and Address Hunting services (document TP-030299).
The work item on
the Multiple MMS Relay/Server Architecture will result in a Feasibility Study analysing
the impacts of multiple MMS Relay/Servers in one Multimedia
Messaging Service Environment (MMSE) on the MMS Reference
Architecture, and investigating potential alternative architectures that support
multiple MMS Relay/Servers within one MMSE which ensures backwards compatibility
(TP-030301). The functional enhancement approved at this meetings was on the
conditional delivery mechanism for MMS. This addition considers the fact that in certain situations, different delivery mechanisms
are needed to improve the user experience.
A discussion took place again on the proposal to use MMS as a data
transport mechanism for the Universal SIM Application Toolkit (USAT) and several Liaison
Statements (LSs) were reviewed on this issue. TSG T noted that
there seems to be a clear preference from Working Group (WG) T3 for using the
Bearer Independent Protocol (BIP) as the high bandwidth bearer for communication
between the USAT and the appropriate network element, as was mentioned in the LS
from WG T3 (second use case in TP-030262).
TSG T endorsed this view. TSG
T also endorsed the concept of non-chargeable delivery of data to and from the
USAT where appropriate. Hence WG SA5 have been included as one of the addressed
committees on the outgoing LS in TP-030297
A set of Change Requests (CR) on Cell Broadcast
Service (CBS) data download was approved.
The
outcome of the 3GPP/3GPP2/OMA workshop was reported and Nokia presented a
proposal on MMS transfer in TP-030295. During
the discussion, four proposals were developed and agreed:
Post
Release 6 technical discussions on MMS Technical Specification TS 23.140
should be moved to the Open Mobile Alliance (OMA) now
3GPP Project Co-ordination Group (PCG) should be invited to consider Intellectual Property Rights (IPR) and copyright issues
Further
consideration is needed concerning transfer of ownership of TS 23.140
material, including splitting and rewriting specifications.
In
addition, as a separate matter discussions should begin on recommendations on
the future structure of WG T2 and possibly TSG-T. WG T2 was invited to create a
proposal on its future structure. Input on further details of the work transfer
e.g. split of specifications are also welcome. WG T3 was actioned to make a
proposal on where to treat MMS smart card aspects in future.
The
work on Generic User Profile (GUP) is progressing. TS
23.241 v1.0.0 Generic User Profile (GUP) – Stage 2; Data Description Method
was presented for information (TP-030271). The document describes the Data
Description Method (DDM) and the Datatype Definition Method (DtDM) of the 3GPP
Generic User Profile. It specifies the method for describing the logical
structure of the data description, Generic User Profile, Profile Components,
methods for describing Datatypes and other constructs for use in 3GPP. It
is planned to complete this specification by March 2004. GUP will provide easy access and sharing of end-user profile data,
including data about the user's devices, services enabled, billing arrangements,
address, calendar and preferences. This will lead to better service experience
for the user.
3GPP
reviewed a document from ETSI Electronic
Communications Networks and Services Directives (ECN&S) Specialist Task
Force STF254 which includes candidates
3GPP specifications for inclusion in the European Commission's Framework
Directive Article 17 “List of Standards”. TSG-T’s preference was to handle
this in ETSI's Mobile Standards Group (MSG) as it seems only to affect ETSI for
the time being.
TSG-SA decided on a similar view. This does not prevent individual companies to
comment directly to ETSI ECN&S STF254 (Marie-Michèle Vasiliou).
Several
CRs were approved on SIM/USIM related subjects.
A new Work Item on USAT Conformance Test
Specification was approved (TP-030259).
This was Claus Dietze’s last meeting. The T3
chairman and TSG-T thanked Claus for the excellent work he did as Mobile
Competence Centre support for T3 and ETSI SCP. From January 2004, T3 will be
supported by Andrijana Jurisic.
Progress was reported on the area of Tree &
Tabular Combined Notation (TTCN) test case development. TTCN
has now moved to March 2003 baseline. 83 Package 1 (P1) test cases verified by
WG T1 to March 2003, 22 Package 2 test cases verified by WG T1 to March 2003 baseline. Major
effort by industry to re-verify all test cases to new baseline completed in late
October. Approved test cases will be published in version 3.4.0 of TS 34.123-3.
Motorola has verified internally 92 P1, 74 P2 and 43 P3 test cases against the
September 2002 base line which has given rise to many corrections to the
‘live’ suite.
The need was
identified by WG T1 for a specific release and configuration manager within MCC
Task 160. The Global Certification Forum (GCF) offered to co-fund the post (up to
the equivalent of 6 man-months). The remaining funding is to be found from the
allocation of 58 man-months already approved for MCC Task 160. TSG-T endorsed
the creation of this post.
In order to increase the TTCN maintenance
capabilities and change traceability, MCC Task 160 reported that they installed
a chain of TTCN-2 tools for editing,
analysing/compiling, merging and comparisons, the configuration management tool,
and a series of working procedures for TTCN configuration management, error
handling /corrections and deliveries.
Based
on the WG T1 recommendations, all 3GPP funding for 2004 will be allocated to
Frequency Division Duplex (FDD) TTCN (details in the STF 160
report TP-030195). Target is to complete
all GCF high priority by late 2004.
The
proportion of complete Radio Resource Management (RRM) tests is approximately
24%. Completion of the outstanding RRM test cases is required within 9 months
for subsequent validation/ approval by GCF before the end of 2004. The RF
Convener is putting into place a strategic plan to cover the work but more
offers of assistance are always welcome.
CRs to TS 34.121 introduced testing for the 800MHz band were approved.
Rapid contributions were made in time for approval at T#22 in order to meet
Japanese Regulatory conditions for the introduction of DS CDMA for the testing
of band VI frequencies.
A single Release of TS 34.122 has been prepared for approval as a result
of a T1 study into the best method of a maintaining a single release document
based on Release-5 to cover Release '99, Release-4 and Release-5. It has been
made clear to the customer where the specifications refer to the different core
specification releases. Updated versions of the Release '99 & Release-4 docs
(for approval) contain pointers to the new (Release-5) Single Release
specification.
Problems
of potential misalignment of inter Radio Access technology (RAT) test cases
between WG T1 and TSG GERAN are being addressed. GERAN has responsibility for GERAN to UTRAN handover prose tests but
T1/ETSI MCC 160 is responsible for the TTCN development. GERAN is reviewing its
approval process and WG T1 will liaise closely to provide assistance as
required.
A work item for Conformance Testing A-GPS Rel 6 Minimum Performance Requirements was
approved (TP-030288).
TR 34.902 v1.0.0
Derivation of test tolerances for multi-cell Radio Resource Management (RRM)
conformance tests was presented for information (TP-030289).
The first subject addressed by SA#22 was the request for 3GPP to study the means to drop back from a video call to a voice call. This was triggered by an LS from GSMA SERG (SP-030744) and stressed to be a critical and urgent problem. It resulted in a new Work Item, originated by Vodafone, which approved WID is in SP-030788.
The conclusions on a workshop on Multimedia Messaging Service was reported to SA#22 (SP-030571). In summary, the principle of work share between OMA and 3GPP for MMS is as follows: the MMS parts independent of the cellular system are transferred to OMA, whereas the parts specific to an individual cellular system belong to the corresponding forum (e.g. 3GPP). This principle is endorsed by SA.
ETSI
TISPAN envisage to
use 3GPP IMS as the base of the service platform in their wired NGN
architecture. In this context, they inquire SA about 3GPP Service Definition and
Service Creation. SA1 have already reacted to this LS, so SA provide a more
global answer on setting the basis for future cooperation TISPAN/3GPP in this
area. (SP-030564 answered in SP-030786).
OCG
EMTEL and SA2 are
communicating on the review of ETSI SR 002 180 V0.3.2 (SP-030568). Answering to
a specific point, SA stressed that SMS (including "Priority SMS")
cannot be used for emergency situations as there is no guarantee on when the SMS
would reach the receiver.
Finally,
SA answered to ETSI ECN&S STF 254 on
the “candidates 3GPP specifications for inclusion in Art 17 list of
standards”: this is not a matter for SA (SP-030717 answered in SP-030758).
GSMA-WLAN has contacted 3GPP on how to incorporate GSM Association requirements for I-WLAN scenario 3 in the standard (SP-030608, 609). This will be answered by SA2 with potential SA1 involvement.
Regarding Push to talk over Cellular (PoC), OMA Req WG has sent an LS in SP-030566 on solving specific issues and on the principles to avoid overlaps between the two committees. A draft answer elaborated by SA2 (SP-030666) was completed by SA in SP-030787 to tell that SA2 has started the analysis of the implications of PoC on the 3GPP system in TR 23.979. SA1 did not find new requirements, but will follow closely the development of the work in SA2.
GSMA/IREG asks for the ability for an operator to prevent access of 2G subscribers with a 3G handset to its 3G coverage, whether the home network uses one or two PLMN codes for his 2G and 3G networks/subscribers. The solution has to be extensible to other access technologies, e.g. WLAN (SP-030748). This requirement is covered by CR in SP-030695 from SA1.
The other subjects, quickly addressed, were:
TS 22.246 on MBMS User Services was approval for Release 6 (i.e. raised to version 6.0.0), as well as the TR 22.952 on Priority Service guide.
Some problems have been identified in SP-030729 on the approved TR 22.952 (Priority Services) on "9 times overload", access class control and interaction with packet services. CRs are invited to resolve them.
No particular controversial CR from SA1 was presented. Some WIDs have been updated, but no new one was proposed.
As proposed by SA2, SA decided that the work on IP Flow Based Charging, presently covered in TR 23.825, will now be handled in a dedicated TS.
The TR 23.877 on Speech Enabled Services was provided for information and noted in SP-030663, as well as TR 23.977 on Bandwidth and Resource Savings and Speech Enhancements for CS Networks (BARS) in SP-030713.
The most controversial issue was once again the problem of whether scenario 3 of WLAN-3GPP interworking should be part or not of Release 6 in TS 23.234 (see LS in SP-030664). Even though the problems of network selection and GSMA concerns can be resolved (because the first one belong to S1 and the second one can be covered by CRs), it remains the fact that the requirements of scenario 3 are still not properly addressed, according to the SA1 chairman. So the final decision was not to raise 23.234 to version 6.0.0 at this meeting.
There was no controversial CR from SA2.
One WID was revised, no new one was submitted.
A set of documents was presented for information and noted.
There was no particular controversial
issue raised by SA3, and no new WID.
Two new TSs were presented for information: TS 26.244 on "Transparent end-to-end packet switched streaming service (PSS); 3GPP file format (3GP)” (SP-030672) and TS 26.246 on "Transparent end-to-end packet switched streaming service (PSS);3GPP SMIL Language Profile” (SP 030673).
There was no controversial CR. One WID was slightly revised and no new one was presented.
Four new
TSs were approved to be raised to version 6.0.0:
Not less
than thirteen new TS were presented for information by SA5 to SA.
There
was no controversial CR and no activity on the WID side.
The review of the global 3GPP Work Plan, including RAN, T and CN#22 comments, was presented by ETSI/MCC in SP-030791. It concludes that the Stage 2 is still not complete for most of the features being defined by 3GPP and almost all of their Foreseen Completion Dates have been postponed 3 to 6 months during the last 6 months. So a freezing date prior to June 2004 would miss most of them. Whether Release 6 is to be frozen by June 2004 or September 2004 (or later) will be decided in March 2004, on the basis of the progress made on the Stage 2.
A proposal was made by MCC to improve the accuracy of the Work Plan in SP-030750. It resulted mainly in that BB WIs should use relative target date (i.e. how long it will take to complete them) rather than a fixed completion date.
The list of 3GPP Dependencies on OMA Deliverables was provided in SP-030760.
A draft description of the content of the Release 99 was provided by MCC in SP-030767, similar to what was done for Release 5 some months ago. This initial draft was presented to enable companies to comment on the structure of the document, as the concept of Features did not exist in this Release.
Some global areas that SA will have to solve in the medium term have been identified: