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
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 September 2003 in Frankfurt, Germany.
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.
Well, within 3GPP, a Release is a full set of technical specifications (and supporting documents) that define a mobile system. A mobile system can be constructed based on the set of all specifications that comprise a given Release. And a specific Release differs from the previous Release by having added functionality introduced as a result of ongoing standardization work.
In order to permit an effective project management of the work, the task is made up of Work Items, each usually resulting in a specification or some other document. Three levels of Work Items are recognised. The top level is a Feature: each feature can be considered as an optional extra, which can be added or not to a system as a function of market demand. Normally a feature embodies an improved service to the customer and/or increased revenue generation potential to the supplier.
The next level of Work Item a Building Block, several of which make up a Feature. Building Blocks are composed of the lowest level, Work Tasks. TSG Highlights will mostly just refer to Features.
Release '99 was functionally frozen (i.e. the functionality defined by the specifications included in this Release was frozen) at the end of 1999, Release 4 was frozen in March 2000, and Release 5 was frozen during the first half of 2002. Release 6 is expected to be functionally frozen around the end of 2003 or early in 2004.
Like the previous Releases, there are several hundred specifications in Release 5, so it's impossible to give a concise answer here. The best thing to do is to take a look at specification 21.101 v5.4.0 (or later) or, if you want more complete detail, the current 3GPP workplan: http://www.3gpp.org/Management/WorkPlan.htm
The expected contents of Release 6 (and even what lies beyond Release 6) can be found in the 3GPP workplan .
At its recent meeting in September 2003 in Frankfurt, Germany, 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).
Some maintenance work was performed on the existing Releases of MMS specifications but the major part of the work was about introducing new functionality into Release 6. MMS Release 6 will add new functionality to the existing MMS standard in several areas which will further enhance the user experience. A revised Work Item Description for Multimedia Message Service (MMS) enhancements was approved (TP-030175) with some items being removed due to lack of interest.The functional enhancements approved at this meetings were on enhancements to DRM support in MMS (addition of Forward Lock and Combined Delivery and other enhancements), addition of size in Retrieval Request (within a retrieval request the recipient MMS User Agent may indicate a size restriction of the returned MM), more detailed MM3 specification extension of MM4 interface for delivery report enabling the originator MMS Relay/Server to request a delivery report for the MM, Reply charging in case of forwarding. The approved CRs can be found in TP-030174.
A long discussion took place on the proposal to use MMS as a data transport mechanism for USAT. It was pointed out that the MMS client is designed in a way that it is not an integral part of the UE. Therefore an interface of any MMS client to the UICC cannot be guaranteed. Furthermore there is currently no specified way to address MMS clients on the UICC and in the UE separately. After studying the reply from SA2, TSG-T felt that a more detailed analysis on the potential impact on the 3GPP system is required if the new requirement of enhancing the data bandwidth to and from the USAT was supported, before concluding that “MMS” is the best method. A Liaison Statement (LS) to SA1, SA2 was approved in TP-030228.
TSG-T agreed to propose a joint 3GPP, 3GPP2, OMA workshop on MMS Standardisation Management and the Terms of Reference (ToR) for such a workshop were endorsed by TSG-T (and later by TSG-SA). An LS was sent from TSG-SA to 3GPP2 and OMA (SP‑030554). Individual Members would be responsible for proposing anything coming from this to the respective bodies.
Change requests were approved enabling the support of additional SMS message indications e.g. for a waiting video message (TP-030173).
The work on Generic User Profile (GUP) is progressing. 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.
A discussion took place on a company proposal to mandate Release 5 and later terminals to support the SIM. The discussion was later continued in TSG-SA where a decision was made regarding the requirement (see TSG-SA section).
A new work item on USIM enhancements for WLAN Interworking was approved (TP-030185). Investigations are planned on optional enhancements to the smart card application specifications to properly leverage USIM advanced capabilities for WLAN Interworking. This work item will cover investigations across possible use cases in the areas of security and provisioning, in order to facilitate possible interworking scenarios.
TSG-T informed TSG-RAN on their documents to be considered for the Revision 4 of Recommendation ITU-R M.1457 (TP-030221).
TSG-T has reviewed TR 22.952, Priority Service Guide and offered comments to SA1 for consideration (TP-030229).
Good progress was reported on the area of TTCN test case development. 82 P1 TTCN test cases are now verified by T1 to March 02 baseline, 21 P2 test cases are now verified by T1 to March 02 baseline. TTCN is now moving to March 03 baseline. Major effort will be undertaken by industry to re-verify all test cases on new baseline. TS 34.123-3 TTCN V3.3.0 will be based on March 03 core specifications. In the background Motorola has now verified 89 P1 and 65 P2 test cases against the June 02 baseline.
A three phase integration plan was agreed by T1 to reduce regression test time and further optimise the TTCN verification process against the new baseline.
At the previous meeting, TSG-T endorsed in principle T1’s approach of having one specification TS 34.121 “Terminal Conformance Specification, Radio Transmission and Reception (FDD) for all Releases (R99, Rel-4, Rel-5)”. Rel4 & Rel5 versions have now been created. Furthermore, a single Release of TS 34.121 had been prepared.
The WI for conformance testing of HSDPA was approved (TP-030198). The technical objective of this work item is the conformance testing of HSDPA to prepare a conformance test specification for the signalling layer 2 and 3 aspects. Also prepare a conformance test specification for the various RF characteristics of the HSDPA feature as they impact the mobile station performance and the radio resource management aspects.
TSG-T endorsed the request for 2004 by STF 160 (details in the STF 160 report TP-030195). For FDD, to keep the same funding level as 2003 (58 mm). For TDD, 2/3 capacities of FDD (39 mm). Within the TTCN project higher priority should be given to earlier committed tests. New functionality should be given higher priority in terms of funding than extending the general test coverage. Additional inventive ways of raising funds should be encouraged. This will be reported to the Project Coordination Group (PCG).
This group held its ultimate meeting, devoted to finalise the Technical Report TR 21.902. This goal was achieved, and the TR was approved in SP-030518. This Release 6 TR is now under control of SA (i.e. CRs should be brought to SA meetings).
The core part of this document consists in identifying End User, Network Operators and Manufacturer/Application Developer expectations, and grouping them into "Focus Areas". It lists the potential technology evolutions that 3G might use.
The minutes of the Future Evolution ad-hoc were issued as SP-030523.
A one-day joint meeting between OMA and 3GPP took place the week prior to SA meeting. The purpose was to make a mutual presentation of structure and activities and clarify the aspects for cooperation. The results, presented to SA#21 in SP-030516, are that there should be a periodic exchange of information (e.g. monthly/quarterly) to maximise the efficiency of the cooperation. The items of common interest are listed in SP-030501. Among them are Push to Talk over Cellular (PoC), Multimedia Messaging Service (for the requirements), Digital Rights Management, etc. On PoC, a dedicated LS was sent to clarify the rules for further collaboration in SP-030530 (see also 505 and 370).
Information was also exchanged with:
A long discussion, related to the LSs sent by GSMA SCAG (SP-030367 and 368), took place on the management of MMS by UICC applications. SCAG ask SA1 and T3 not to stop their work on it, and not to limit it to what was proposed by SA1 in SP-030355 at previous SA meeting. At this SA meeting, SA1 now provide a CR in SP-030461 stating that a Multimedia Message (MM) can also be sent by the UICC (in addition of the ME). The CR was split into SP-03550, revised to SP-030552, stating that it shall be able possible for the MMS client to store and retrieve (elements of) MMs in the USIM, and into SP-030551, on actually sending/receiving (elements of) MMs by/to the UICC. SP-030551 is postponed to next meeting to leave time to T3 to check it.
One of the most controversial points of the meeting was the discussion on establishing the rules for Audio Codec selection (specification format), and more specifically on whether the C source code of the codec has to be provided for it to be a valid candidate for 3GPP system. The conclusion was that indeed, the source code has to be provided both for the encoder and the decoder, but this decision is valid just for this codec and is not binding future codec selections (see SP-030506 and SP-030555).
The traditional report on work progress and related conclusions was made by MCC in SP-030524 for the Work Plan, and in SP-030525 for the corresponding slides, revised in SP-030556. They conclude that the Rel-6 freezing date might be March or June 2004, to be clarified at next TSG. As an independent proposal, O2 asked for a relatively late date for completion of Release 6, i.e. September or December 2004. It was finally agreed that MCC will identify at SA#22 the status of Stages 1, 2 and 3 of the features presently being defined by 3GPP to decide which ones will belong to Rel-6 and what completion date would be appropriate for Rel-6.
Note that “Rel-6 features” used in this report has to be understood as “features presently planned to belong to Rel-6”.
The most important point involving SA1 was on MMS storage on the USIM mentioned above. Apart from this point, SA1 proposed lots of CRs to refine the Rel-6 features requirements.
One can note however the discussion on SP-030514 stating that a Rel 5 UE shall support SIM cards of previous Releases in addition to support of USIM. Given the strong opposition from TIM and 3, the CR was revised in SP-030533 where the requirement was changed into a “strong recommendation”, applicable for UEs supporting GERAN, and placed in a note. SP-030533 was approved.
The following technical documents were submitted by SA1 and approved (for v.2.0.0) or noted (for v.1.0.0) by SA#21:
In addition to CRs to cover Stage 2 of the Rel-6 features, SA2 proposed the following WID, all approved:
SA2 also submitted the following technical documents, all approved or noted:
The last document proposed by SA2 was the TS 23.234 v2.0.0 on "WLAN interworking", in SP-030391. There was no agreement to raise it to version 6. There is full support for the work only up to and including scenario 2. For scenario 3, the current end-to-end Tunnelling Solution has to be considered only as a Working Assumption, as it might lead to specific problems listed in the SA report. SA2 should provide answer to these points by next SA plenary.
There was no controversial issue raised by SA3. In addition
to the CRs, SA approved one new WID (Feature): “Key Management of group keys
for Voice Group Call Services” in SP-030491 [Note from the redactor: this item
seems too specific to be considered as a stand-alone Feature, and SA3 will be
asked to confirm that this is not a Building Block under “Rel-6 Security
Enhancements”].
SA3 will also start a Feasibility Study on (U)SIM Security
Reuse by Peripheral Devices on Local Interfaces (see SP-030397).
The most controversial item related to SA4 activities was the Codec issue mentioned above.
In addition, SA4 proposed some test plans for AMR Narrow-Band and Wide-Band Packet Switched Conversation tests (SP-030435 and 436). Tests are also proposed for default codec evaluation for speech-enabled services (SES) in SP-030434, with associated recommendation criteria in SP-030440, approved by SA (see also SP-030369 on SES codecs). Other selection tests and processing plans are for AMR-WB+ and PSS/MMS Low-Rate Audio (in SP 030437) and for PSS/MMS High-Rate Audio in SP 030438. The Funding of Audio Codec Testing was presented in SP 030439.
None of the CRs was controversial. Finally, SA4 proposed in SP 030443 the TR 26.937 on "RTP usage model" v2.0.0, which was approved for Release 5.
Good progress noted in Charging Management work with new delegates.
Not least than 14 draft TS/TR were presented by SA5 and approved or noted by SA (see full list in SA report).
The document provided by MCC to describe Release 5 was available in a stable version in SP-030526. Now MCC will work on a corresponding document for Release 99, with the aim to provide a stable draft by SA#23.
TSG RAN meeting #21 took place Hotel Intercontinental in Frankfurt, Germany. The meeting started at 9:00 on Tuesday 16th September 2003 and finished at 11:00 on Friday 19th. 92 participants were registered and 181 documents were presented.
The group reviewed the documentation to be forwarded to ITU WP8F for the Revision 4 of Recommendation M.1457. The documents presented include the overview of the radio interface, for both FDD and TDD modes. The new extension bands (850MHz and 1.7/2.1 GHz for the US and 800MHz for Japan) are introduced. A preliminary list of the specifications to be provided was presented, and further modified with the comments from TSG T. The list may be further modified by TSG SA if this group believes that some other specifications are still missing.
Additional accompanying papers where presented and approved. After the comments from TSG SA, the set of documents will be sent for 3GPP PCG approval and then forwarded to ITU-R before 1st October.
Additional documents to be forwarded to ITU-R WP8F on the deployment of UTRAN in the 2500-2690 MHz bands (RP-030511), and on the co-existence of UTRA FDD and TDD in that same band (RP-030537) were approved and sent to 3GPP PCG.
A methodology for the handling of errors on Early UEs was presented by Vodafone for discussion (RP-030509). It was commented that any of the existing 3GPP working methods, and also other means like conference calls or dedicated reflectors, can be used depending on each particular problem. It was argued that establishing a tight and predefined procedure was undesirable.
There was a short discussion on the need to create tests for a 768kbps RAB, multicode. WG2 is tasked to study the issue.
CRs were presented to correct an identified problem when a NodeB loses synchronization of its RL when in SofHO. The proposed CRs to 25.214 R99 and onwards add a recommendation for implementation of the NodeB, but it was found that a proper solution should be studied in WG3.
It was noted that a number of LSs had been exchange between GERAN and RAN WG2 on Iur-g issues, which was found by many companies a very ineffective way of working. It was proposed that a single group handled the issue, GERAN being more likely as it is more affected, but companies where reluctant to let RNC requirements be defined in that group. It is proposed that experts from both groups hold a session together (RP-030543).
On the "Out of Service Issue", a Rel-5 CRs mandating a single behaviour was presented. It was the subject of an informal vote after which is was rejected, so the allowed behaviours in R99 and Rel-4 are kept in Rel-5. The CR was however approved for Rel-6.
A long discussion took place on the definition of the "Minimum UE capability class". A CR was proposed, requiring the support of turbocoding in the downlink in that minimum class. It was objected that if any, it should be required in both downlink and uplink, but this lead to a debate on the actual need to define any kind of "minimum class". Finally, RAN WG2 will have to study the issue again on the basis of the last revision of the CR presented (RP-030552)
The Work Item " Improving Receiver Performance Requirements for the FDD UE" was finished. Additional work has been presented in WG4 under this WI, but finally considered to be out of its scope. Companies suggested that work on the area will be proposed in the future.
A first set of CRs has been approved to TS25.101, TS25.104 and TS25.141 for the introduction of the naming convention and frequency ranges of the new bands. (UMTS800, UMTS850, UMTS1.7/2.1).
The Work Item "Improvement of RRM across RNS and RNS/BSS" is closed due to the lack of activity.
The last CR under the WI " Open SMLC-SRNC Interface within the UTRAN to support UTRAN Rel-4 positioning methods" is presented, the Work Item is now finished.
TR25.992 v2.0.2 "MBMS; UTRAN/GERAN requirements" was presented and approved. It will be set under change control
TR25.803 v1.0.0 "S-CCPCH performance for MBMS" was presented for information.
A Joint meeting with SA WG1 & WG2, RAN WGs and GERAN WG1 & WG2 for MBMS issues is under schedule. The invitation will be made available to RAN WGs.
The Study on "Improvement of inter-frequency and inter-system measurements for 1.28 Mcps TDD" is finished, with the conclusion that no additions to the specifications are required, the improvements discussed can be achieved with changes to the RNC implementation.
TR25.888 v2.0.0 " Improvement of inter frequency and inter system measurement for 1,28 Mcps TDD" is approved and put under change control.
The Study "Enhancements to OTDOA Positioning using advanced blanking methods" was closed since the last proposal presents a substantial change and instead of a new feature it can be considered an enhancement to existing IPDL method. Hence, it was agreed to continue the work under the basket WI "UE Positioning Enhancements".
The Study on "Improved access to UE measurement data for CRNC to support TDD RRM" was finished and concluded on the creation on a WI with the same name. The associated TR25.801 v2.0.0 " Feasibility study for improved access to User Equipment (UE) measurement data for Controlling Radio Network Controller (CRNC) to support Time Division Duplex (TDD) Radio Resource Management (RRM)" was approved and set under change control.
The following new WIs have been approved:
It was agreed to start the backwards compatibility for the changes on Rel-4 RRC protocol, and that WG3 will consider the same approach for the Rel-5 versions of its protocols (RP-030523).
TSG CN#21 meeting took place in Frankfurt Germany from 17th to 18th September 2003. 53 participants were registered and 131 documents were treated in two full days.
This was a highly productive meeting with CRs being approved that concluded several previously contentious issues:
Change to Parlay-X and Java appear in 3GPP OSA Specifications:
As Jain SPA is no longer a supported activity, 3GPP CN5 references in the Rel-5 OSA Specifications to it are being replaced by contributions based on the Java rulebook.
CN Plenary agreed to the use of the term “Parlay X” in the 3GPP specifications? This is already a brand name, and it using the term in our OSA specifications avoids confusion with the existing WSDL realization of the OSA APIs.
An LS was received from GSMA IREG identifying inconsistencies within the "Numbering, Addressing and Identification" document, 3GPP TS 23.003. This had been seen and reviewed in CN4 and a company contribution presented to NP#21.
A response LS was sent to GSMA requesting confirmation of their understanding of the use of the ".gprs" and ".3gppnetwork.org" domains for DNS queries for IMS identities constructed from a subscriber IMSI.
An exception until CN#22 is given to the CRs associated with this topic (NP-030370 and NP-030389).
In response to an LS received from OMA on upcoming work on PoC, TSG_CN discussed and formulated a position that it forwarded to TSG_SA in order to provide a coordinated 3GPP response to OMA.
In SA#21, Stephen Hayes formulated a response LS to OMA that detailed 3GPP's position and a proposed plan of action for working with OMA on PoC.
Also a SA2 led WID on PoC enablers was approved in SA#21.
OMA will give a PoC presentation in the October WG meetings in Bangkok.
The following work items were approved:
The following new specification was approved: