From: Christian Toche [christian.toche@HUAWEI.COM]
Sent: 07 December 2006 23:50
To: 3GPP_TSG_SA_WG5
Subject: SA5 Results at SA#34

Dear SA5 colleagues,

Please find below a summary of SA5 results at SA#34 in Budapest, Hungary, December 4-7, 2006, hosted by EF3.

All documents are available at:
http://www.3gpp.org/ftp/tsg_sa/TSG_SA/TSGS_34/

The SA5 presentation to SA#34 can be found at:
http://www.3gpp.org/ftp/tsg_sa/TSG_SA/TSGS_34/Docs/SP-060701.zip

Post-SA#34 updated SA5 specs are available for final checking at:
ftp://www.3gpp.org/tsg_sa/WG5_TM/TSGS5_50/_specs_for_checking

Deadline for feedback: 22 December 2006

Thanks to Adrian for the preparation of the SA5 report and SA5 deliverables.

Best Regards,

Christian
SA5 Chairman

All SA5 contributions to SA#34 have been approved
It is to be noted that we had less quality issues this time. This is a confirmation we are on the right track with the recent changes in our working methods, mainly the introduction of the CR quality session. I believe that with the (re-)empowerment of RGs and RG Rapporteurs, we will definitively get rid of quality issues. Even though this is impacting very few documents, only SA5 has such issues in SA. Fixing the quality issue remains a first priority objective.

Statistics
2 new WIs: approved
1 revised WI: approved
14 TSs for approval: approved
2 TSs for information: noted
1 TR for approval: approved
5 TRs for information: noted
45 Charging CRs: approved
46 OAM&P CRs: approved

SP-060705 Rel-6/7 CRs 32.298
S5-061718, Rel-7 mirror of the Rel-6 CR S5-061717, was missing in the package SP-060705. In fact, S5-061718 had been submitted in a separate document SP-060719 because of a bad work item code (CH7, should have been IMS2-CH) and a bad CR category (F, should have been A). Consequently, S5-061718 was considered as a stand-alone Rel-7 CR, not as a mirror CR.

SP-060705 was withdrawn and replaced with SP-060908, SP-060908 including S5-061718. SP-060908 was then approved.
S5-061718 was verbally withdrawn from SP-060719. SP-060719 was then approved.

SP-060840 TR 32.808 v100 Study of Common Profile Storage (CPS) Framework of User Data for network services and management

It was commented that this draft TR does not contain a conclusion and it would be difficult for other WGs to gain any useful information from it. It was also requested that the document is reduced in size, e.g. by removal of the architectural diagrams and other text copied from other documents. The SA5 Secretary reported that this had been agreed by e-mail just prior to this TSG SA meeting and it was requested that a LS is agreed here in order that it can be sent to other WGs for comments on the technical feasibility. There was some support for this proposal.

This TS was noted and Members were asked to review the document and provide any comments to SA5. A LS to SA1, SA2 and CT4 was drafted in SP-060929 and was approved.

SP-060753 WID Study of Management for LTE and SAE
Following an issue raised in the RAN Report to SA, it was clarified that the OAM specifications should use the normal OAM specification set and not be in the 36.xxx series, which are reserved for RAN LTE specifications. This WI description was approved.

SP-060701 SA5 Presentation to SA#34
It was noted by SA that some Rel-7 work items are likely not to be completed in March 2007, closure date of Rel-7. An explicit status is expected from RG Rapporteurs at SA5#51 on whether those work items are canceled, maintained in Rel-7 or moved to Rel-8. SA#35 will expect an exception sheet for any Rel-7 work item that cannot be completed in March 2007 but is still planned to be part of Rel-7. The form can be found in SP-060939.

Slide 18: ServID Charging. It was commented that the selection of a solution is a CT1 decision which will need to be followed by SA5. It was reported that CT1 hoped to make a decision for an outline solution at their next meeting. The CT1 Chairman commented that the use of an IETF-based solution would depend upon the progress in the IETF and CT1 will choose a solution which will be available in the Rel-7 timescale, rather than delay the work to use a particular solution.

SP-060717 Rel-7 CRs 32.260
It was commented that some CR titles have changed compared to that agreed in SA5 and some other changes had been made to clarify the CRs, including removal of text around tables and unaffected rows of tables being modified. It was clarified that the SA5 Secretary made some editorial clean-ups of the CRs as requested by SA5. It was requested that the CRs presented to Plenary are equivalent to those agreed in SA5 in order to reduce confusion and uncertainty about the CRs. If the CRs are modified, it should be indicated in a clear way that this is not the original WG document (e.g. by revision of the TD number). The full text of clauses should be included in the changed areas in accordance with the CR drafting guidelines. These CRs were then approved.

SP-060927 New Work Item: Subscriber Identification
The objective of this work item is to define a mechanism to more easily identify subscribers belonging to a certain type, or a particular MVNO, without necessarily having to analyze the IMSI and /or MCC+MNC, especially for service differentiation, routing, charging and subscription management purposes. It could be envisaged that a suitable identifier might be included in the subscriber data information message distributed by the HLR/HSS. Subject to operator roaming agreements, the identifier might also be sent in this way to a VPLMN. The VPLMN could use the identifier for routing and barring purposes, but would not be expected to analyze or understand the identifier to the same level of detail as the HPLMN and hosting PLMN. If present, the VPLMN could simply include it in CDRs, and in TAP messages sent to the HPLMN for accounting purposes.

It was asked whether this, along with the approval of the related CR, was the completion of the work in SA1. It was acknowledged that this was the case and it was suggested that the lead WG should therefore be changed to SA5 as the remaining work is for charging. It was asked why the charging functionality is needed and it cannot be done by simple post-processing. It was clarified that having a simple identifier would reduce the processing needed in the charging systems. It was agreed that this should be a SA5 WID, and the first paragraph of the objective could be removed. It was therefore decided that the supporting companies should present this WID to SA5 for agreement. Vodafone agreed to do this. The WID was therefore rejected. A request was made to include the WI Code for the related CR which had been approved at this meeting in the CR database when the WI Code is available. The MCC specifications manager agreed to take care of this.

SP-060857 Reply LS from SA5 on 3GPP SAE and LTE Work Plan
The LS was presented. SA5 asked TSG SA for feedback if deemed required. It was agreed that SA WG5 should proceed as they have planned. The LS was then noted.

SP-060922 TSG CT Report
Slide 25: SIP enhancements to Trace. The TSG CT Chairman reported that there seemed to be some reluctance in the IETF to work on such services. It was reported that if 3GPP Members want this work progressed then they need to contribute actively to the IETF. It was agreed to remove this feature from Rel-7 for the moment and to verify support for the Work Item in 3GPP. It was acknowledged that some CRs will be needed to remove this from the Rel-7 specifications. SA5 was asked to verify the support for this work, the supporting companies are expected to actively progress the work in the IETF.

SP-060911 Review of the work plan
TSG SA#33 decision was that the Rel-7 Freeze Date is March 2007. This decision was confirmed at SA#34. It was proposed that TSG#34 decide about a freezing date for Rel-8 Stage 1. However, it was considered too early to finalize this date and companies were asked to discuss this before the next TSG meetings, where views can be reviewed and a date agreed.