
| TSG CT | TSG SA | TSG RAN | TSG GERAN
Previous Highlights: TSG#38
| TSG#37
| TSG#36
|TSG#35
|
TSG#34
|
TSG#33
|
TSG#32 |
TSG#31
|
TSG#30
|
TSG#29 |
TSG#28 | TSG#27 |
TSG#26 |
TSG#25 |
TSG#24 |
TSG#23 | TSG#22
TSG#21 | TSG#20 | TSG#19
| TSG#16
| TSG#15
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.
3GPP has four TSGs: CT (Core Networks and Terminals); RAN (Radio Access Network); SA (Services and Systems Aspects) and GERAN (GSM EDGE Radio Access Network).
Please note, these summaries 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.
TSG CT meeting #39 took place in Puerto Vallarta, Mexico. The meeting started on the 5th March 2008 and finished on the 7th March 2008.
No changes in R99
1 correction to a Rel-4 conformance test case
Corrections on Rel-5:
Correction to DTMF handling and to BNC event event handling in bearer establishment procedures
Both CRs were made under WI CSSPLIT
10 Rel-6 CRs, 2 of which were Cat A
Cat F corrections were made on the following work items:
IMS2: Mn profile, Removal of remote user from conference, correction of OMA DM reference
TEI-6: XML correction, Addition of insufficient memory error code for MBMS security procedures on the USIM
MMS6: Reference correction, addition of references to OMA DM procedures and MMS management object
MBMS: TMGI misalignment
- Rel-7 CR count is 31 % down since previous CT
- The number of Rel-7 Cat F CRs is expected to go down
- Changes and corrections on the following WIs:
- IMS related:
- IMS emergency calls
- Stage 3 IETF protocol alignment
- GRUU
- Service ID
- Multimedia telephony (Cat B. CR)
- Mp interface
- Voice Call Continuity
- Interworking between IMS and CS
- Fixed NGN (Packet Cable)
- PCC
- SMS over IP
- CSI
- other items:
- OSA
- WLAN QoS
- REDHOT, HUGE (capability indication only, no CT WID)
- TEI7
Rel-7 CR count is 64 % down since previous CT
The number of Rel-7 Cat F CRs is still expected to go down
No contentious or critical issues to report
Corrections were made on the following WIs:
IMS related:
IMSProtoc
Mp interface
MIWIMS (MM interworking)
PCC
ServID
MTSI
FBI
TEI-7
Other items:
EVGCS
SDoUE
NSP-CR
IMS-CCR-IWCS
MBMS
TEI-7
Rel-8 CR count is a bit less than in the previous CT
30 new Rel-8 TSs were approved in CT #39
17 new Rel-8 TSs were provided for information to CT #39
11 new SAE specifications have been started recently
Main part of CT WG Rel-8 work is not yet seen as CRs in CT plenary
10 new WIDs and 8 updated ones were approved
Turkish SMS alphabet solution was approved
This is needed already in pre-Rel-8 UEs due to July 2008 deadline
SMS SENDING using locking shift cannot be implemented yet due to legacy
Contributions were received against several Rel-8 WIs:
Interface based on the SIP-I protocol
SAES (planning documents, WIDs)
Enhancements for VGCS applications
IMS items stage 3 IETF protocol alignment, IMS enhancements for packet cable access, NBA, MGCF interworking between UUS and SIP, Media server control using the IMS, PCC, TISPAN redoc, IMS-CS interworking, IMS for corporate access networks
TEI-8
SAE Status
SAE work has shifted from TR to TS mode
Separate WIDs from all affected WGs were approved
Protocol and interface mapping to TSs is done
PMIP vs. DSMIP
EMM and ESM are separate protocols with new PD assigned
New TSs have been started
TS numbers were already assigned by MCC
Transfer of material from TRs to TSs is ongoing
The whole CT SAE work has been planned
The identified new TSs either start now or have already been started
TRs 24.801, 29.803, 29.804 will continue as placeholders for material intended for already approved specifications until 09/2008
SAE work planning
CT is planning to complete SAE by Dec 2008
Full stage 2 of the included functionality is needed in SA #40
Any new functionality (Cat B or C CRs) introduced to Stage 2 after SA #40 should be considered as Rel-9 item or otherwise Rel-8 schedule will slip
Any new CT WID in SAE area would cause the Rel-8 schedule to slip
Dependencies (mainly) on SA groups
Dependencies to SA groups affect CT WG planning
CT agreed to continue to use 3GPP work plan as planning tool
Possibility to add TS maturity summary is being considered
Working group scheduling
CT1 and CT4 are running parallel IMS and SAE subgroups most of the time
CT1 and CT4 will have 6 more meetings this year
CT3 has (exceptionally!) 5 more meetings this year
SAE related informal phone conferences between the meetings
CT6 can accommodate SAE work in their normal meeting cycles
New CT related SAE Technical Specifications
TS number
Contents
WG
24.301
NAS protocol for the EPS; stage 3
CT1
24.302
Access to the EPC via non-3GPP access networks; stage 3
CT1
24.303
Mobility management based on Dual-Stack Mobile IPv6;
stage 3CT1
24.304
Mobility management based on Mobile IPv4;
UE - foreign agent interface; stage 3CT1
29.272
MME Related Interfaces Based on Diameter Protocol
CT4
29.273
3GPP EPS AAA interfaces
CT4
29.274
General Packet Radio Service (GPRS); Evolved GPRS Tunnelling Protocol (eGTP) for EPS
CT4
29.275
PMIP based Mobility and Tunnelling protocols
CT4
29.276
Optimized Handover Procedures and Protocols between EUTRAN Access and cdma2000 HRPD Access
CT4
29.277
Optimized Handover Procedures and Protocols between EUTRAN Access and 1xRTT Access
CT4
29.125
PCC within System Architecture Evolution
CT3
Common IMS
TISPAN transfer
Adopted TISPAN specification have been re-documented as 3GPP TSs
TISPAN R1 corresponds to 3GPP Rel-7 (TSs are in major version 7)
TISPAN R2 corresponds to 3GPP Rel-8 (TSs are in major version 8)
What was frozen by TISPAN is still frozen after transfer
28 re-documented TSs approved and 14 noted, see tdoc SP-080178
The transfer is now almost complete but 2 more TSs are expected for CT #40
CT4 proposes deprecation of Mp profile in ES 283 031 to TISPAN
3GPP MMD harmonisation
WG level workshop was held on the 24 25 Jan 2008
New work items related with MMD harmonisation were approved in CT #39
One framework WID and 2 more WIDs for individual features
New TS 24.238 SIP based user configuration
New TS 24.239 Flexible alerting supplementary service
New TS 24.182 IMS customised alerting tones
The first CRs have already been approved, but more work is expected under the new WIDs and related with the new TSs
TSG RAN meeting #39 took place in Puerto Vallarta, Mexico. The meeting started at 9:00 on the 4th of March 2008 and finished on the 7th March 2008.
The following number of CRs were approved at TSG-RAN#39:
Category A CRs are excluded from this table and from the graphic below:
|
Release |
RAN1 |
RAN2 |
RAN3 |
RAN4 |
RAN5 |
Total Of CRs |
|
R99 |
|
1 |
|
1 |
|
2 |
|
Rel-4 |
|
1 |
|
1 |
|
2 |
|
Rel-5 |
|
1 |
|
|
|
1 |
|
Rel-6 |
|
10 |
2 |
10 |
93 |
115 |
|
Rel-7 |
12 |
38 |
27 |
13 |
34 |
124 |
|
Rel-8 |
5 |
24 |
15 |
15 |
186 |
245 |
|
Total of CRs |
17 |
75 |
44 |
40 |
313 |
489 |

The following table lists the approved CRs per category and per Release:
|
Release |
Cat |
Number of CRs |
|
R99 |
B |
1 |
|
R99 |
F |
1 |
|
Rel-4 |
B |
1 |
|
Rel-4 |
F |
1 |
|
Rel-5 |
A |
1 |
|
Rel-5 |
B |
1 |
|
Rel-6 |
A |
1 |
|
Rel-6 |
B |
53 |
|
Rel-6 |
F |
62 |
|
Rel-7 |
A |
19 |
|
Rel-7 |
B |
3 |
|
Rel-7 |
C |
1 |
|
Rel-7 |
F |
120 |
|
Rel-8 |
A |
50 |
|
Rel-8 |
B |
29 |
|
Rel-8 |
C |
1 |
|
Rel-8 |
F |
215 |
Following an LS from the WiMax Forum on interworking of the EPC with WiMAX it will be reported to TSG-SA that the work on interworking with WiMax cannot be concluded in due time for Release 8.
The ITU-ad hoc has been tasked to elaborate the update on M.1801 by September. ITU-R ad-hoc has also been tasked to elaborate a proposal initial submission towards Revision 9 of M.1457 and to update the material on M.1580 and M.1581by May.
- Further Improved Minimum Performance Requirements for HSDPA UE (FDD) - Two-Branch Interference Cancellation
- CS Voice Service over HSPA
- Performance requirements for 15 code reception with 16QAM/QPSK (FDD)
- 3G Long Term Evolution Physical Layer
- RF/RRM Conformance Test Aspects MBMS (FDD) (Rel-6)
- Conformance test aspects 64QAM for HSDPA (FDD)
- Conformance test aspects Improved L2 support for high data rates
- Conformance test aspects Multiple Input Multiple Output antennas (MIMO) for FDD
- Conformance Test Aspects - Minimum UE performance requirement for downlink physical channels in support of MTCH and MCCH operation based on type 1 enhanced receiver (Rx-Diversity)
Synchronised E-DCH for UTRA FDD
HS-PDSCH serving cell change enhancementsLong Term Evolution
The Study items remains open for the RAN3 part in order to find a solution on the remaining architectural issues.
A new Work Item on the support of UTRA HNB was in principle approved and needs to be reviewed
A new Work Item for FDD Home Node B RF requirements was approved
TSG-RAN tasked all WG to review all LTE specifications in order to reduce the number of options.
The RAN1 part of the Long Term Evolution Work Item was closed, The Work Item remains open for all other WGs. The target for closure of the Work Item is June 2008.
Continuous Connectivity for packet data users for 1.28Mcps TDD WID in RP-080085
HSPA VoIP to WCDMA/GSM CS continuity WID in RP-080229
HS-DSCH Serving Cell Change Enhancements WID in RP-080227
Support of UTRA HNB WID in RP-080159, to be reviewed
FDD Home NodeB RF requirements WID in RP-080234
Conformance Test Aspects - Network Selection Enhancements WID in RP-080135
Conformance Test Aspects MBSFN for HCR and VHCR TDD WID in RP-080155
Conformance test aspects CS Voice Service over HSPA WID in RP-080160
SI LTE-Advanced RP-080137
SI Dual-Cell HSDPA operation RP-080228
TSG SA meeting #39 took place in Puerto Vallarta, Mexico. The meeting started on the 10 March 2008 and finished on the 13th March 2008.
The target for the Rel 8 stage 2 freeze is June 2008. The overall freeze target for Rel 8 is Dec 2008.
Further pruning was done on the list of SAE functionality for Rel 8. The following SAE functionality was retained in Rel 8 (in addition to the essential functionality defined in SP-070699):
The following SAE functionality was removed from release 8:
In addition it was agreed that any of the above features that do not become part of Release 8 will be considered as candidates for early completion (target date December 2009). Note this does not make any assumption about the Release 9 completion date.
This guidance can be found in SP-080218. Additional investigation is required as to how to support ETWS and how to provide cell ID for lawful intercept purposes (SP-080223).
A massive number of CRs were approved related to SAE. In addition, the list of items that are candidates for Rel 9 is substantial and growing so there is considerable work still in the 3GPP pipeline.
A successful workshop on common IMS with 3GPP2 was held and that transfer is in progress (SP-080169). The transfer of TISPAN work is proceeding well. The principle that 3GPP will maintain the transferred specs was reconfirmed. The transfer target is Rel 8, but the common IMS transfer will not be allowed to jeopardize the Rel 8 completion. In addition, a dialog was started with ATIS PTSC (SP-080219). It was also agreed to create a specification listing the common IMS specifications.
TSG-SA confirmed the principle of transferring the OSA API work to OMA (TSG-SA is responsible for requirements, while TSG-CT handles the API). This is documented in SP-080186.
It became clear in the plenary that different groups are applying consensus differently. There are currently process discussions ongoing as part of a PCG/OP initiative to improve 3GPP efficiency (SP-080166). It is hoped these will address this issue. Member feedback on the process issues is encouraged.
The following new TSs were approved: TS 22.142 Value Added Services for SMS Requirements (SP-080047), TS 22.186 Earthquake and Tsunami Warning System (ETWS) Requirements (SP-080185), TS 32.121 Advanced Alarm Management (AAM) Integration Reference Point (IRP) Requirements (SP-080071), TS 32.122 Advanced Alarm Management (AAM) Integration Reference Point (IRP) Information Service (SP-080072).
The following new TRs were approved: TR 22.892 Study on IMS Centralized Services (ICS) Requirements (SP-080050), TR 22.968 Study for requirements for a Public Warning System (PWS) Service (SP-080049), TR 22.983 Services Alignment and Migration (SP-080164), TR 23.811 Service Level Interworking for Messaging Services Stage 2 (SP-080101), TR 23.892 IMS Centralized Services (SP-080102)
Several new work items (WIDs) were approved: Enhancements to Multimedia Priority Service Requirements (SP-080051), 3GPP2 Input to Common IMS (SP-080220), System enhancements for the use of IMS services through local breakout (SP-080090), CS Fallback in EPS (SP-080097), IMS Service Continuity (SP-080092), Generic Bootstrapping Architecture Push Function (SP-080133), Requirements and Test methods for Wideband Terminals (SP-080004), IMS initiated and controlled PSS and MBMS User Service (SP-080201), Performance measurements for EPC (SP-080061), Performance measurements for E-UTRAN (SP-080062), Key Performance Indicators (KPIs) for E-UTRAN (SP-080063), Management of Self-Organizing Networks (SON) and associated work tasks (SP-080064-SP-080067), Alignment with eTOM and M.3060 architectural concepts (SP-080068).
Several WIDs were updated: Charging for Multi-Phase Services to clarify that it was multi phase (SP-080053), System enhancements for corporate network access - changing completion dates (SP-080095), 3GPP System Architecture Evolution Specification (SAES) - including H(e)NB aspects (SP-080132), Study on support of a Public Warning System (PWS) - removing gap analysis (SP-080054).
Two new study items (SIDs) were approved: Study on Self-healing of SON (SP-080076), Intra Domain Connection of RAN Nodes to Multiple CN Nodes (SP-080094).
One SIDs was updated: System enhancements for the use of IMS services in local breakout and optimal routing of media - changing dates and indicating non-Rel 8 scope (SP-080091).
After much deliberation by the network operator members of 3GPP, the services to be offered as top priority by LTE wre refined to ensure a consistent package will be ready within the Release time frame.