3GPP TSG-T2 #5 / ETSI SMG4
Helsinki, FINLAND, 6-9 September 1999	TSGT2#5(99)643	

Agenda Item:	4

Source:	T2 secretary

Title:	SMG4 issues at SMG#29 (excerpt of the report)

Document for:	Information

___________________________________________________________________________

6.1	SMG1
...
6.1.5	Liaison statements
Tdoc SMG P‑99‑380 is a Liaison Statement from SMG1 to 3GPP-SA, SMG AAE (Applications and Automatic Execution Workshop), SMG, SMG2, SMG3, SMG4, SMG6, SMG7, SMG8, SMG9, SMG10, SMG11, SMG12, SERG on Applications and Automatic Execution Workshop. 

The applications and automatic execution workshop had been installed prior to SMG#28. Starting point had been the intended feature to allow the SIM to use AT commands at the SIM-ME interface. SMG AAE had reported to SMG#28. 

SMG#28 had agreed a work item description sheet for MS and Network-Resident Execution Environments (MS/N-RExE). SMG1 had studied the results of SMG AAE in the scope of this work item without reaching consensus with these results. The liaison statement identifies several immediate concerns of SMG1. 

During SMG#29, a proposal was worked out in a side meeting how to proceed. As a result, Tdoc SMG P‑99‑533, Proposal for the way forward on Applications and Automatic Execution, source: BT, Ericsson, Nokia, Motorola, NEC Technologies was presented by Kevin Holley. 

Discussion of Tdoc SMG P‑99‑533 at SMG#29: There was a discussion on section 4 of Tdoc SMG P‑99‑533. It was concluded that SMG plenary encourages the delegates to discuss work performed by subgroups in a positive light. This does not preclude the possibility to propose changes of decisions.

Decision of SMG#29: SMG#29 approved the Tdoc SMG P‑99‑533 with the modification to remove section 4.
SMG1 will convene another workshop on applications and automatic execution to start some more detailed work from the service perspective, and companies, in particular those disagreeing with the results reported at SMG#28, should make constructive contributions.

(Note after the meeting: AAE workshop to be held from Tuesday 21st to Wednesday 22nd of September, 1999 in Sophia Antipolis)

6.4	SMG4
The SMG4 status report to SMG#29 in Tdoc SMG P‑99‑478 was presented by the SMG4 Chairman, Kevin Holley (the presentation slides are in Tdoc SMG P‑99‑479). The SMG4 status report was approved by SMG#29. 
6.4.1	General
SMG4 has SMG4 has held two plenary meetings (both jointly with 3GPP TSG T2) and several ad hoc meetings since SMG#28.
The transfer of work on data interworking and GPRS to SMG3 WPD has been completed. 3GPP TSG-T WG2 “Services and Capabilities” took over SMG4’s UMTS work. 
6.4.2	Change requests
All change requests presented by SMG4 to SMG#29 were approved by SMG#29: They concern
•	EDGE in Tdoc SMG P‑99‑504;
•	the indication of WAP data coding scheme for USSD and CB; clarifications concerning SMSC address checking in the MS; SMS-CB message identifiers indicating secured data download; moving AT commands from GSM 07.60 to GSM 07.07, syntax error in +CHSN command, additional result codes for +CLIP and +CCWA; clarification of how to handle the length filed in basic mode, in Tdoc SMG P‑99‑482.
Comments at SMG#29: CR 03.40-A087 has an impact on GSM 11.10 where the SMS address field is tested.
6.4.3	New specifications
GSM 03.57, Mobile Station Application Execution Environment (MExE), Functional description; Stage 2, Version 2.0.0, in Tdoc SMG P‑99‑506 was approved. 
6.4.4	Work items/areas
EDGE: Before the transfer of several specifications to SMG3 / TSG CN, SMG4 had elaborated CRs to these specifications for introduction of EDGE.. These were therefore submitted to SMG#29 by SMG4.
Mobile Station Application Execution Environment (MExE): GSM 03.57, stage 2 of Mobile Station Application Execution Environment (MExE) had been completed, see 6.4.3. Concerning the security issues the group received good support from SMG10. The work on MExE R99 stage 2 (3G TS 23.057) will now be progressed. 
Facsimile services in UMTS: GSM 22.45, the “Study on provision of facsimile services in GSM and UMTS” was completed. Main conclusion of this report is that Fax can be provided in GSM and UMTS as an IP based solution. The report was transferred to TSG T2 as 22.945.
6.4.5	Liaison statements
Tdoc SMG P‑99‑437, Cell Broadcast Technical Note (TWG Doc 225/99), source: TWG, is a liaison statement from GSMA TWG to SMG4. It will be studied by SMG4.
6.9	SMG10
...
MExE security: There had been a joint meeting with SMG4 on MExE security at SMG10 plenary #1/99. After that, SMG10 had been represented at subsequent MExE meetings. SMG10 now satisfied with security for MExE. For MExE R99, security requirements are:
•	four level trust model to be retained ; 
•	untrusted applications are permitted to make calls provided explicit user permission is given ;
•	support for ‘single action permission’ is mandatory. This gives the MExE application user permission for a single action only; repeated actions required repeated requests for user permission.
•	Applications can only transfer or forward calls to numbers which are controlled by the user.
•	Applications can only add numbers to a multiparty call if the numbers are controlled by the user 
•	Use of SIM for security will be considered in later releases

7	G-UMTS matters
Ian Doig presented Tdoc SMG P‑99‑519, Proposal for 3G and SMG Specification Handling, source MCC. This document had been approved by all four 3GPP TSGs. Main proposals:
•	To avoid divergence of the 3G and GSM specifications, the responsibility for maintenance (technical corrections) of earlier GSM Releases and the future GSM evolution of those specifications affected should be the prime responsibility of one Technical Body.
•	To avoid duplication of work, further GSM evolution (GSM R99 onwards) should be incorporated into the 3rd Generation Core Network specifications as GSM specific parts if necessary. Note that the evolution of the GSM Radio access specifications, MS test specifications and BSS test specifications, are for the most part, unaffected by the 3rd Generation evolution.
•	The way forward:
•	TSG WGs and corresponding SMG STCs co-locate meetings as much as possible.
•	GSM Specifications modified in any way for the 3rd Generation system are transferred to the 3GPP.
•	The 3GPP produce a complete set of 3rd Generation “R99” specifications.
•	Prime responsibility for maintenance of all previous releases of the Specifications is transferred to and carried out by 3GPP TSGs.
•	All relevant SMG e-mail lists are advised of all CRs to <R99 specifications prior to TSG approval (if possible and if meeting timing permits).
•	SMG approve all modifications (TSG CRs) to earlier releases of the GSM specifications, which are ETSI deliverables, if necessary by correspondence, following the co-located TSG Plenary meetings.
•	SMG reviews all modifications (TSG CRs) to R99 and later releases of the 3GPP specifications which impact on GSM, if necessary by correspondence, following approval at the co-located TSG Plenary meetings, and provides comments if necessary back to the TSG meetings.
•	All GSM R99 versions of specifications transferred to 3GPP becoming part of the 3rd Generation specifications R99, are deleted. The remaining GSM specifications will continue to be maintained and developed within SMG. The specifications transferred at TSG#3, proposed for future transfer and those which should remain in SMG only are listed in Annex A. The provisional list given in annex A should be further elaborated and reviewed by SMG STCs and TSG WGs in detail. In general, the specifications remaining in SMG include:
•	05 series GSM Radio Aspects and specifications linked to or directly related the GSM Radio. 
•	GSM Security Specifications (to be confirmed)
•	Non-AMR GSM 06 series (the AMR specifications may require specific GSM and 3G handling which will need to be further elaborated by SA3 and SMG11)
•	Most of GSM 11 series (to be confirmed)
•	3rd Generation specifications may contain GSM R99 Specific parts e.g. 29.002.
•	The GSM specifications CR database(s) and GSM status lists are maintained.
•	Current versions of all Releases <99 and the specifications only relevant for GSM are maintained on the SMG ftp site. 
•	ETSI SMG approves the 3rd Generation specifications that are released to the Partner Organisations (POs), which are appropriate and necessary to become ETSI deliverables.
•	ETSI SMG decide the ETSI deliverable type (EN, TS etc) of the 3rd Generation specifications approved by SMG.
•	ETSI SMG provide only a replacement cover, Foreword and History to the 3rd Generation specifications, leaving the 3GPP version number intact.
•	SMG provide ETSI Public Enquiry approval procedure comments on 3rd Generation specifications to the appropriate 3GPP TSGs.
•	These principles apply after SMG#29 (if SMG#29 and TSG#4 agree) and following GSM R98.
•	Annex A contains the specifications and equivalent GSM versions transferred from SMG to the TSGs.

Discussion at SMG#29:
•	Tony Wiener and Rémi Thomas stated that (e.g., for GSM only interested ETSI members) it must be possible to comment in SMG meetings on specifications like MAP and possibly to reject change requests.
•	Jeremy Fuller (Nortel) stated that in order to keep a consistent protocol, changes for inclusion of UMTS only functionality lead to changes in the protocol which would have to be implemented by GSM only implementations of the same MAP version.
•	It was discussed how the complete set of GSM R99 specifications will be identified. It was argued that in 3GPP specifications continuing GSM specifications (e.g., 29.002 continuing 09.02) GSM should be indicated in the scope (and title). Another view was that this information should not be given in the 3GPP specifications but in separate SMG specifications.

Clarifications at SMG#29:
•	It is part of the proposal that it shall be documented in a permanent document which specifications belong to the UMTS R99, ... set of specifications.
•	The list of specifications can be changed whenever the relevant bodies agree. In particular several speakers recommended not to move the VBS / VGCS specifications to 3GPP.
•	It was clarified that SMG9 intents to split GSM 11.11 into a specification of the common parts and a specification of the SIM application.

Decision at SMG#29: Tdoc SMG P‑99‑546, revising Tdoc SMG P‑99‑519, was approved by SMG#29.