S3-99380
Technical Specification Group Services and System Aspects	TSGS#5(99)244
Meeting #5, Kyongju, Korea, 11-13 October 1999	

Source:	TSG SA Secretary
Title:	Draft Report of TSG SA Meeting #5 - version 0.0.2

1	Opening of the meeting
The TSG SA Chairman, Mr. N. Andersen opened the meeting and Dr. S. K. Park welcomed delegates to the historic city of Kyongju, South Korea, on Behalf of TTA and Hosting companies. A LAN facility had been set up for the meeting and had already been used by the preceding TSG meetings where it had proven to be very convenient and a good step towards electronic meetings.
The Chairman thanked the hosts for hosting the meeting and providing the effective meeting facilities.
2	Approval of the Agenda
SP-99469: The agenda had been revised taking into account comments of editorial nature. The agenda was approved.
3	Approval of the meeting report of TSG-SA Meeting no. 4
TD SP‑99345: The Report of Meeting #4 was approved without change.
4	Letters / Reports from other groups
TD SP‑99378: Draft summary minutes from 3GPP PCG Meeting #2 (6-7 July 1999). This was provided for information and the Chairman summarised the main points of the meeting. Annex A of the document (TD SP‑99378) contains a list of decisions of the PCG.
It was noted that TSG SA have been delegated the responsibility for the maintenance of the 3GPP Working Methods and that a method had been agreed which will enable the ITU to reference 3GPP results before they are formally converted by the Partners.
With the summary, the document was noted.
4.1	TSG-T, TSG-CN, TSG-RAN
TD SP‑99346: Liaison statement response on IST for non-CAMEL subscribers from TSG CN for information. The CN Chairman reported that this item has already been dealt with by CN2. The document was noted as for information.
TD SP‑99350: LS on Use of Prioritising Channel Selection for Cell Selection Procedure from RAN WG2. The liaison explains the proposals made on scanning a list of pre-defined prioritised frequencies as defined by Network Operators. This is intended to reduce the scanning time and speed-up the selection process. It was reported that there may be some impact on Roaming, which should be investigated. In the liaison statement, SA1 are asked if there is a service requirement for the use of priority fields as described in the liaison. TSG SA supported the principles and encouraged RAN WG2 and SA WG1 to co-operate on this issue. The GSM Association representatives present at the meeting were asked to feed the document into their organisations for consideration and to liaise with RAN WG2 and SA WG1 in order to get the full picture, so that the work can be completed.
TD SP‑99352: Liaison statement to SA WG4 on Support of Speech Service in RAN. The document was noted by TSG SA and will be handles by SA WG4.
TD SP‑99360: LS to SA and N1 (CC) on required network functionality for usage of SIM in 3G mobiles from CN WG2. The CN Chairman explained that further details and clarification are requested by CN WG2 in order to complete their work accordingly. SA WG1 have been considering the SIM requirements in the 3G system. Further details were provided in the Report of SA WG1 (Agenda Item 5.1.1).
TD SP‑99361: LS to RAN WG2 and RAN WG1 on Physical Layer Measurements Requirements from RAN WG4. The document was copied to TSG SA for information. The Liaison was noted by TSG SA.
TD SP‑99362: Liaison statement to TSG-S4 on radio simulator capabilities from RAN WG4. The document was presented for information and noted by TSG SA. SA WG4 were asked to consider the consequences of the lack of ability of RAN WG4 to provide test sequences simulated by a reference radio environment.
TD SP‑99367: Review of 3GPP TS26.112 “Call Set-up Requirements for Circuit Switched Multimedia Telephony Service”, version 1.1.0. The document is provided to TSG SA for information and was noted by TSG SA. SA WG4 will deal with the document accordingly.
TD SP‑99368: LS regarding the scope of CAMEL Phase 3 from CN WG2. CN WG2 have agreed to split the scope of CAMEL Phase 3 work. It was noted that SA WG1 have seen the document and more information will be given in the report from SA WG1.
TD SP‑99376: Liaison statement on selected location service methods for Release '99. RAN WG2 ask for clarification on whether the LCS will be mandatory or optional for Release 1999. SA WG1 are describing 3 methods of Location and need to consider other services which may be impacted by LCS. The wish for consistent systems for LCS across many IMT-2000 family members was noted. This topic was detailed during the SA WG1 presentation.
TD SP‑99413: Liaison statement on freezing GSM Release 97 & Release 98. This informs other TSGs of the freezing of GSM release 1997 and GSM Release 1998 maintained by TSG CN such that no new features may be added to these Releases. Mr. Thomas (France Télécom) requested that the Operators should also participate in the decision for allowing changes, and not only the Manufacturers. TSG SA noted the document and the TSG SA Chairman reminded the WGs to follow the rules of only necessary corrections to Release 1997 and 1998 documents.
TD SP‑99414: Liaison to TSG SA on the ITU-R TG 8/1 revision of Recommendation M.1079 from TSG RAN. This liaison asks TSG SA to review the material in Annex 3 of the liaison and consider sending a liaison to ITU‑R before 14 October 1999. SA WG1, SA WG2 and SA WG4 Chairmen were asked to consider this document and determine if any significant modifications have to be made and to report back to the meeting. After the review period, no significant modifications were found needed. The proposed changes given in Annex 3 of TD SP‑99414 was found to correctly reflect the thinking of SA WG4. It was clarified that the latest version of TR 23.907 would be attached to the liaison to ITU‑R. 
TD SP‑99420: Liaison statement to TSG-SA on resource situation and the general strategy and status of the elaboration of test cases from TSG T. It reports a lack of resources for the production of Test Specifications, which will be responsible for delays to the finalisation of the documents and resulting in late availability of  test specifications for Release 1999. SA were asked if 3GPP Members could not provide resources, whether a Project Team should be set-up in order to produce the test specifications. It was clarified that this request is in addition to the requests already being made for resources for project teams for TTCN and SIM testing. TSG T was asked to consider how the work should be split between T WG1 and a potential project team. It was agreed that a description of the work split and cost estimates for the work should be specified before final decision on this can be taken.
TD SP‑99421: Regarding Position paper on “Supplement to Recommendation Q.1701” from ITU-T WP 3/11 from TSG T. This was presented for information, describing the TSG T position paper for the modifications proposed to Q.1701. The position paper was noted by TSG SA and interested parties are invited to use it as a basis for their contributions to ITU‑T. A request to ensure that all aspects of Q.1701 were covered was received. TSG CN have looked at the document from their viewpoint. It was decided that a side-meeting be convened to try to ensure that all areas of Q.1701 are covered by the various reviews and report back to the meeting. This resulted in TD SP‑99491, which was handles under agenda item 6.4.
TD SP‑99422: Regarding Position paper #2 on “Supplement to Recommendation Q.1701” from ITU-T WP 3/11 from TSG T. This document was considered in the same way as TD SP‑99421 and the same comments apply.
TD SP‑99457: Terminology and vocabulary in 3GPP. The principles for the production of vocabularies, provided by SA WG1 were agreed by TSG T and TSG T further propose a single common vocabulary document for 3GPP, maintained by TSG SA, in order to harmonise terminology across the system. SA WG1 have not had much time to consider this issue recently, and a commitment for resources for the production and maintenance of a vocabulary is required. The SA WG1 Chairman reported also that a common vocabulary could not be produced by a single group, but that each TSG/WG would need to provide information to the editor of such a document.
On this topic, the Chairman outlined a specific problem of terminology of UE/MS in specifications for 3GPP systems and GSM respectively. He suggested to avoid a large-scale update of specifications by, for example, inserting a note to indicate how the term UE/MS should be interpreted in a given specification in relation to 3GPP/GSM systems respectively. Interested parties were asked to try to find a solution before the end of the meeting and to report back.
It was agreed that when possible the GSM terms should be re-used before creating new terms in order to minimise the impact on existing specifications. For UE/MS a solution is required which does not require the update of all the GSM / 3GPP specifications. It was stressed that a generic approach is required for the vocabulary document in order to be flexible enough to accommodate future terminology in the different system domains where they will be used.
It was stated that 23.101 requires a verification and update because of contradictions and lack of definitions.
Summary: It was generally agreed that a single common vocabulary should be produced which all documents should reference. It was also agreed that GSM terminology should be used as far as possible to reduce the necessary changes to existing specifications. The principles of the contribution were agreed, except that it was not agreed that the definitions in the common vocabulary overrides local definitions.
TD SP‑99458: Liaison statement to TSG-SA on the distribution of a proposal for prioritisation of the elaboration of conformance test cases for 3G terminals from TSG T. The document was incomplete and is therefore presented for information and discussion rather than for action. Further information including the missing Annexes will be sent via the e-mail reflector. T WG1 would like to make a prioritised list of testing specification work and request help from TSG SA to identify the priorities for the work, with a highest priority for the tests needed for Regulatory purposes. TSG T will elaborate a first proposal which will be forwarded to the SDOs via the PCG for the SDOs to liaise with regulatory bodies for feed-back.

4.2	Partners and their bodies
TD SP‑99347: Liaison on 3GPP handling of the OHG Proposal from T1P1. T1P1 expresses it's support for a single DS-carrier mode. This has been overtaken by events and was noted by TSG SA.
TD SP‑99348: Supporting the concept of an All-IP Network Architecture and offering to support the relevant groups with hosting of the meetings in North America. The document was noted.
TD SP‑99370: Liaison statement on PLMN selection for GPRS MS from SMG2. In this ETSI SMG2 indicates that they can not support the proposal from TSG CN on introduction of GPRS-specific PLMN selection. It was noted that as a consequence, TSG CN, for the time being, had abandoned the proposal. More generally SMG2 expressed concern on the impact on radio issues of service-specific PLMN selection. SA WG1 were asked to note that ETSI SMG2 would like to be kept informed on their work on PLMN selection. The document was noted by TSG SA.
SP-99372: LS concerning the GSM/EDGE RAN from SMG2. SMG2 and SA WG1/SA WG2 are asked to discuss the possible roadmap from Release 1999 to Release 2000 and the related deployment scenarios for GSM/EDGE RAN. The Draft of GSM/EDGE RAN radio requirements was provided for information in TD SP‑99371. It was clarified that the liaison was sent to TSG SA because 3GPP has taken over the work on Service, Architecture and Core Network definition for Release 2000. One requirement for Release 2000 is for an All-IP Core Network. SMG2 indicated that for the Release 2000 GSM/EDGE RAN to interwork with this will require very close cooperation with SA WG1, SA WG2 and TSG CN. The document was noted as a request for close cooperation between SA WG1, SA WG2, TSG CN and ETSI SMG2. SA WG1 and SA WG2 were asked to establish close cooperation with ETSI SMG2 to ensure the GSM/EDGE system also are covered by the requirements and architectures being elaborated.
TD SP‑99371: Draft of GSM/EDGE RAN Radio Requirements. This was provided by ETSI SMG2 for information. The document was noted.
TD SP‑99385: GSM LCS Charging from T1P1.5. T1P1.5 ask that SA WG5 undertakes the charging standards work of GSM LCS. The SA WG5 Chairman reported that SA WG5 is willing to take on the subject, but they need to look at the resource availability for the work. If sufficient resource is available then SA WG5 will start work on this and co-operate with the GSM Association. It was noted that whenever a service is being specified, then the Charging aspects should automatically be dealt with as a part of that work.
TD SP‑99403: Liaison statement to 3GPP concerning Global Certification or Type Approval from the UMTS Forum. The Liaison suggests that the test specifications for the 3G specifications should be worked out according to the following principles:
-	There should be only one set of test requirements for each 3GPP core specification world-wide,
-	All relevant demands, including operator and regulator demands, should be incorporated, so that no additional specific requirements are needed (except such horizontal demands as EMC requirements and user safety requirements),
-	Handover situations with other standards must be covered,
-	Test requirements must be produced as soon as possible after the specification is finished so they can be taken into account in the industrial development process.
The regulatory requirements should be a subset of the total test requirements.
It is not the task of 3GPP to decide how much of the test requirements that should be regulatory requirements. To arrive at such a decision there must be consultations between regulatory bodies.
It was clarified that the first bullet intended that there should be a single set of test specifications world-wide for the 3GPP core specifications. The document was noted recognising that the liaisons from TSG T, which had identified resourcing problems and the need for prioritisation in the Testing work, is in alignment with the concerns raised in this liaison from the UMTS Forum. TSG T are expected to deal with the details and concerns of Testing for 3GPP specifications.
TD SP‑99404: VCS Principles from the GSM Association. A presentation of this document is contained in TD SP‑99405. A short presentation was given on the principles of the Voluntary Certification Scheme. The VCS Programme is planned as follows:
-	Secretariat in place by 1 December 99
	-	Program “Organisationally” functional
-	Program “functionally operational” by GSM World Congress in February 2000
	-	Begin accepting Declarations of Conformity from manufacturers if certified
-	Program fully operational by 1 April 2000
	-	Prior to 8 April 2000 start of R&TTE Directive
The agreed process is intended to be used as a basis for a 3GPP certification scheme. Further information is available at: http://www.industry.gsm.org 
TSG SA noted the presentation of the VCS programme as for information.
TD SP‑99472: UMTS Forum Report to 3GPP SA#5 (Presentation). The UMTS Forums Current Activities are New Market Forecast Study, Exhibition at ITU CPM/WRC2000, InfoCom Technology/Regulatory Workshop - Singapore and Globalisation Activities. The presentation provided information about the Market Research activities and Lobbying/Representation planned by the UMTS Forum to promote the adoption of the 3GPP system world-wide. The document was noted by TSG SA.
TD SP‑99406: Liaison Statement on Inter PLMN Handover principles from the GSM Association. The GSM Association asked for confirmation of their assumption that the responsibility for all handovers, which occur during a connection will stay with the Serving PLMN. TSG SA confirmed this assumption. The GSM Association also asked TSG SA to specify more precisely to which type of scenarios the principles for inter PLMN handover as described in the contribution are actually applicable. This contribution also recommends that the standard GSM charging architecture should be enhanced to cater for inter-MSC and inter PLMN handover appropriately, in order to support inter carrier accounting between the Anchor and the Access PLMN. TSG SA agreed to forward the document to SA WG5 for consideration of the charging principles Other groups were asked to also take this into account in their work.

4.3	Others
TD SP‑99416: Co-ordination between 3GPP TSG SA and ETSI SPAN3, related to OSA. Alcatel presented this contribution which informs TSG SA of the work that ETSI SPAN3 have started on Open Service Architecture (OSA) and proposes a joint meeting with CN WG2 to discuss the OSA requirements. The TSG CN Chairman reported that this issue would be dealt with at a workshop at the end of October and did not wish to drain any resources from the ongoing specification work for Release 1999. TSG SA noted that CN WG2 would meet with ETSI SPAN3 to make an assessment on the available material from ETSI SPAN3, SA WG1 and SA WG2, and to determine the time scales and workload involved in this item. TSG SA noted that the results are not to be expected to be part of Release 1999. Further, it was noted that the VHE specification still does not cover the handling of services in foreign networks.

5	Reports from TSG-SA Working Groups
5.1	TSG-SA WG1
5.1.1	Report from TSG-SA WG1 (including release 2000 planning)
TD SP‑99429 is the report to TSG SA from SA WG1, which was presented using the slides given in TD SP‑99430. 
SA WG1 has had a busy schedule since the last TSG SA meeting and have made good progress in many areas. A new work item has been identified: MS and Network-Resident Execution Environments (MS/N-RExE), given in document TD SP‑99470 and TSG SA was asked to approve this. Another work item was proposed for deletion from the SA WG1 list: MS in Protected Zone.
-	One unresolved item on emergency calls in TD SP‑99481 was brought to TSG SA for decision on a way forward. NTT DoCoMo proposed this in anticipation of a possible regulatory requirement. However, some other delegates at SA WG1 had opposed this.
A number of CRs were presented to TSG SA which are detailed under Agenda Item 5.1.3.
3 Specifications submitted for approval to TSG SA and 1 specification was submitted for Information. This is detailed under agenda item 5.1.3.
It was questioned whether it is reasonable to include the Follow-Me service in the 3G specification set. (ref 3G TS 22.094 / GSM 02.94). After some debate and exchange of views it was decided that the follow-Me specification should be re-considered by SA WG1 and a recommendation made on the suitability for 3GPP.
For the presentation of specifications for approval, the TSG SA Chairman requested that all are accompanied by a cover note explaining the content of the document and clearly indicating any open issues under discussion or for further study.

5.1.2	Questions for advice and decisions from TSG-SA WG1
TD SP‑99349: Liaison statement concerning requirements for all-IP option for release 2000. This had been overtaken by events and was therefore not discussed in detail, and noted by TSG SA.
5.1.3	Approval of contributions from TSG-SA WG1
Specifications presented for Information:
TD SP‑99431: TS 22.140 Multimedia Messaging Service - Stage 1. This specification was noted.
TD SP‑99432: TS 22.094 Follow Me Service description - Stage 1. This specification was presented for Information and not approved. Based on the discussion on Follow-Me described above, SA WG1 will reconsider the applicability of the service for 3GPP.
Specifications presented for Approval:
TD SP‑99433: TS 22.135 - Multicall; Service description - Stage 1. The specification was approved and placed under TSG SA Change Control as version 3.0.0. It was requested that other groups consider the specification and comment to SA WG1, if they have any problems with the specification.
TD SP‑99434: TS 22.038 - SIM Application Toolkit (SAT); Service description - Stage 1. The specification was based on the SIM rather than the USIM, and some work is still to be done and SA WG1 are willing to do this while the specification is under change control. This specification was approved and placed under TSG SA Change Control as version 3.0.0. SA WG1 was asked to reconsider sections 5, 7.6 and 8.2 (see TD SP-99415).
It was requested that the next TSG SA Plenary determine whether the SIM Application Toolkit is included in Release 1999.

TD SP‑99415: "User Control" requirements for SIM toolkit stage 1 from France Telecom. France Télécom consider that TSG SA can not approve the current version of TS 22.038 (SAT stage 1), unless the sections described in TD SP‑99415 are deleted (or marked as “for further study”). Further, it is suggested that the document is given back to SA WG1 and T WG3 for further elaboration on the “user control” requirements.
TSG SA noted the points raised in TD SP‑99450 and asked SA WG1 to reconsider the sections 5, 7.6 and 8.2 as outlined in TD SP‑99415.

TD SP‑99470: Work Item description for MS and Network-Resident Execution Environments (MS/N-RExE). The Principle of a such work item in this area was agreed by TSG SA and the SA WG1 Chairman was asked to update the Work Item to cater for the comments and re-present it to TSG SA for approval.
The description was later updated and presented as TD SP‑99494. There were further comments and objections to the approval of the work item at this time and clarification of the proposals was requested. Based on the comments the TSG SA Chairman requested that the work item description was reworked and split in two, so the issue of traceability will become a separate work item. SA WG1 were asked to elaborate this for the next meeting of TSG SA. (Work Item Not Approved at this time).

TD SP‑99456: All IP option for Release 2000. This presentation gives the thoughts of SA WG1 at the moment and the details are subject to further elaboration. SA WG1 are creating an ad-hoc group to look at All-IP requirements for Release 2000. For email discussions there is an e-mail reflector list: mailto:S1_IP@LIST.ETSI.FR . The incompatibilities in the text of the slides were questioned, it was explained that the ideas presented have not yet been consolidated within SA WG1. It was further clarified that the presentation was only concerning the IP Part of the Release 2000 networks. The subject of Number Portability was questioned and it was concluded that the study should concentrate on a service basis rather than on a technology-basis (NP is related to telephony and not specific to IP). After much discussion over the points given in the presentation, it was emphasised that the presentation is a preliminary view and is subject to change and should not be seen as a stable document. It was agreed that SA WG1 are to concentrate on the User point of View and to discuss the User requirements for services, as is usual for their work. The detailed specification of the Services belongs to other groups.
SA WG1 were asked to note the comments received during the discussion of the presentation and consider them in the further elaboration of their ideas.

TD SP‑99411: Some requirements for an « all IP» option for UMTS, from France Telecom and Vodafone. This discusses the requirements for an all-IP Network and recommends that if an all IP option is to be included in Release 2000 of UMTS, the different working groups shall be instructed to specify it according to the principles outlined in the contribution. The contribution was considered and TSG SA requested that this type of contribution is input to the relevant working groups, rather than directly into TSG SA.

<<CRs will be added later as an annex using the contents of the updated CR Database >>

The following CR to 22.101 version 3.6.0 was presented in TD SP‑99435: 
CR number	Subject	SA Decision	
22.101-022	Emergency Call	Approved	

The following CRs to 22.129 version 3.0.0 were presented in TD SP‑99436: 
CR number	Subject	SA Decision
(see comments)	
22.129-002	SMS handover requirement clarification	Approved	
22.129-003	GSM UMTS Handover	Approved	
22.129-004	Revised terminology to 22.129	Approved	
22.129-005	For R99 there can only be one target PLMN for HO in addition to the serving PLMN for R99 in a given geographical area.	Approved	
22.129-006	Clarification of the scope of mandatory requirements	Approved	
22.129-007r1	Removes all non-R99 requirements, by changing them into Cross phase compatibility requirements which apply to R99.	Approved with modification (1)	
(1)	The changes to add section 8.2.2  and Annex A.1 shall be removed from the CR and SA WG1 should reconsider the Inter-PLMN handover issues. The removal of this is not the removal of the Inter-PLMN handover. (Resubmitted as TD SP-99483 as CR007r1).
The following CR to 02.71 version 7.0.0 was presented in TD SP‑99437: 
CR number	Subject	SA Decision	
02.71-A001r1	Changes to the LCS stage 1 to add support for mobile originated positioning requests, and velocity as a service parameter. U.S. specific Emergency Services accuracy requirements removed.	Approved (2)	
(2)	Velocity requirements needed correct specification or removal (Updated in TD SP-99486 and approved).
The following CR to 22.071 version 3.0.0 was presented in TD SP‑99437: 
CR number	Subject	SA Decision	
22.071-001r1	UMTS LCS service requirements support for mobile originated positioning requests, and velocity as a service parameter	Postponed (3)	
(3)	Velocity requirements need correct specification or removal.

The following CR to 22.071 version 3.0.0 was presented in TD SP‑99438: 
CR number	Subject	SA Decision	
22.071-002	This CR introduces LCS service requirements identified previously for UMTS in other 3GPP specifications.	Approved (4)	
(4)	The question was raised and unclear from the requirements document what were the terminal requirements for Release 1999.

The following CR to 22.030 version 3.0.0 was presented in TD SP‑99439: 
CR number	Subject	SA Decision	
22.030-001	Indication to user in case of an error during Data Download	Approved	

The following CR to 22.100 version 3.3.0 was presented in TD SP‑99439: 
CR number	Subject	SA Decision	
22.100-022	Support of SAT by USIM	Approved	

The following CR to 22.101 version 3.6.0 was presented in TD SP‑99439: 
CR number	Subject	SA Decision	
22.101-024	Clarification on the usage on 2G SIM and 3G USIM	Approved	

The following CR to 02.60 version 6.2.0 was presented in TD SP‑99440: 
CR number	Subject	SA Decision	
02.60-A021	Class B mode of operation	Approved	

The following CR to 02.60 version 7.2.0 was presented in TD SP‑99440: 
CR number	Subject	SA Decision	
02.60-A022	Class B mode of operation	Approved	

The following CR to 22.060 version 3.0.0 was presented in TD SP‑99440: 
CR number	Subject	SA Decision	
22.060-001	Class B mode of operation	Approved	

The following CR to 22.060 version 3.0.0 was presented in TD SP‑99441: 
CR number	Subject	SA Decision	
22.060-002	The function that gives the notification of the server IP address from the GPRS network to the subscriber.	Approved	
22.060-003	Introduction of Barring for GPRS.	Approved	

The following CR to 22.041 version 3.0.0 was presented in TD SP‑99441: 
CR number	Subject	SA Decision	
22.041-001	Addition of explicit requirements for Packet Oriented Services	Approved	

The following CR to 22.121 version 3.0.0 was presented in TD SP‑99442: 
CR number	Subject	SA Decision	
22.121-002	Virtual Home Environment.	Approved	
22.121-003	Addition of IP4 Addressing	Approved	
22.121-004	Charging capabilities	Approved	

The following CR to 22.105 version 3.5.0 was presented in TD SP‑99442: 
CR number	Subject	SA Decision	
22.105-015	Service Capabilities and Service Capabilities Features.	Approved	

The following CR to 22.078 version 3.0.0 was presented in TD SP‑99443: 
CR number	Subject	SA Decision	
22.078-001	Camel control of packet switched MO SMS	Approved	
22.078-002	Removal Initial Service Events in case of Unsuccessful MO call establishment	Approved	
22.078-003	Work Item Camel Phase 3 CSE Related overload control	Approved	
22.078- 004	Referenced by LS in 344	Approved	
22.078-005	Inclusion of Service Key in Mobility Management event notifications + editorial modifications	Approved	
22.078-006	Clarification the behaviour when network provided dialled services are used.	Approved	
22.078-007	279 > 341	Approved	
22.078-008	284 > 342	Approved	
22.078-009	336 > 345 CR Rev Jeremy	Approved	
22.078-010	Editorial update of references for GSM/3GPP use	Approved	
22.078-011	Proposed CR for CAMEL3 interworking with GPRS; Change of position	Approved	
22.078-012	Proposed CR for CAMEL3 DTMF Mid-Call corrections and clarifications	Approved	
22.078-013	Proposed CR for CAMEL3 clean-up of IPLMN and VPLMN references	Approved	
22.078-014	CR Defining successful SM submission to SMSC as EDP	Approved	
22.078-015	CR SAT/MExE  interworking	Approved	
22.078-016	Correction Annex A.2; Information sent by the CSE	Approved	
22.078-017	Correction on GPRS handling (Version 2)	Approved	
22.078-018	Short Message Submission Handling (version2)	Approved	
22.078-019	CR O-CSI Information	Approved	
22.078-020	CR Free formatted information	Approved	
22.078-021	Defining Successful SM submission and Unsuccessful SM submission as EDP-N and EDP-R.	Approved	
22.078-022	Proposed CR for CAMEL3 corrections to new Trigger Detection Points (TDP) (2nd version)	Approved	
22.078-023	CR CSI description	Approved	
22.078-024	Proposed CR for CAMEL3 corrections and clarifications to dialled services (subscribed & serving network) 	Approved	
22.078-025	Charging clarifications for MO-SMS (New Version)	Approved	
22.078-026	Proposed CR for CAMEL3 Call Forwarding and new TDP interworking (2nd Version)	Approved	
22.078-027	CLI modification	Approved	
22.078-028	CCBS Service interaction	Approved	
22.078-029	CR Network based CAMEL service invocation	Approved	

<<<479 approved as replaces Doc 444  >>>   479 All CRs Approved except - Remove CR 22.068-A001, CR 22.069-A001 which was rejected as TSG SA decided that the ASCI services VBS and VGS were not to be a part of the 3GPP services
TABLE MISSING <<NIELS COMMENT>>
Sent back to SA1 for consideration ??? - according to the minutes ??  - << I need to clarify this with MCC >>.<<DELETED BY NIELS WITH CLARIFICATION ABOVE>>
The following CR to 02.78 version 6.3.0 was presented in TD SP‑99443: 
CR number	Subject	SA Decision	
02.78 A 041	Introduction of a “Health Warning” on type of numbers sent by the mobile other than “unknown” or “international” CR	Approved	

The following CR to 02.60 version 6.2.0 was presented in TD SP‑99444: <<<479 approved as replaces Doc 444  >>>CR HERE IN 440??, not in 479 (replace with good table from 479)
CR number	Subject	SA Decision	
02.60 A 021	Class B mode of operation		

The following CR to 02.43 version 7.1.0 was presented in TD SP‑99445: 
CR number	Subject	SA Decision	
02.43 A 002	Maximum number of LSAs allowed for a subscriber.	Approved	

The following CR to 22.002 version 3.0.0 was presented in TD SP‑99446: 
CR number	Subject	SA Decision	
22.002-002	Bearer Services	Approved	

The following CR to 22.030 version 3.0.0 was presented in TD SP‑99447: 
CR number	Subject	SA Decision	
22.030-002	Data services streamlining	Approved	
22.030-003	Support for Anonymous Call Rejection	Approved	

The following CR to 22.034 version 3.0.0 was presented in TD SP‑99448: 
CR number	Subject	SA Decision	
22.034-002	Channel coding asymmetry for ECSD	Approved	

The following CR to 22.083 version 3.0.0 was presented in TD SP‑99449: 
CR number	Subject	SA Decision	
22.083-002	Multicall	Approved	

The following CR to 22.086 version 3.0.0 was presented in TD SP‑99450: 
CR number	Subject	SA Decision	
22.086-002	Multicall	Approved	

The following CR to 22.097 version 3.0.0 was presented in TD SP‑99451: 
CR number	Subject	SA Decision	
22.097-002	MSP	Approved (5)	
(5)	SA WG1 to check if this was really intended to be used for 3GPP

The following CR to 22.100 version 3.3.0 was presented in TD SP‑99451: 
CR number	Subject	SA Decision	
22.100-025	Release 99 alignments and corrections	Approved	
22.100 	UMTS Phase 1 future releases	Approved	

TD SP‑99452 CRs Approved.
TD SP‑99453 CRs Approved.
TD SP‑99454 CRs Approved.
TD SP‑99455 CRs Approved.
TD SP‑99481: This CR was not approved at SA WG1 and NTT DoCoMo presented it to SA directly. It was stated that the CR foresees a National Variation on MS implementations. In the case that there is a specific need for additional emergency numbers due to local regulation, this should then be raised again at TSG SA in order have it included in the standard in order to avoid unnecessary local variation of terminals. The CR was Not Approved.

TD SP‑99349: Liaison statement concerning requirements for all-IP option for Release 2000. This was noted but had already been covered by the previous discussions.

5.2	TSG-SA WG2
5.2.1	Report from TSG-SA WG2 (including release 2000 planning)
TD SP‑99386: The status report of SA WG2 was presented by the SA WG2 Chairman. 
SA WG2 presentation of new technical documents:
-	TR 23.922 v.1.0.0, Architecture for an all-IP network, in TD SP‑99388
-	TR 23.923 v.1.0.0, Combined GSM and Mobile IP Mobility Handling in UMTS IP CN, in TD SP‑99389
-	TS 23.171 v.1.0.0, Location Services (LCS) in UMTS - Stage 2, in TD SP‑99408
Note	It is proposed to have two different TSs for LCS stage 2 CN for Release 99: one for GSM in 03.71 v.8.0.0 and one for UMTS, 23.171
-	TS 23.127 v.0.2.1, Virtual Home Environment (VHE)/Open Service Architecture (OSA) - Stage 2, in SP-99409 including a proposed process of way forward (TSG-SA approval for V.1.0.0 by correspondence proposed).
The critical issues were reported as being:
-	Classmark issues (CS&PS, HO handling with GSM/GPRS) are not sufficiently addressed (several groups involved).
-	In core network (N1) changes to 24.008 as due to the removal of LLC and stream identifier concept are essential for R99. In case of timing problem, multicall could be moved to future releases.
It was questioned whether it was of importance to complete Multicall for December 1999. It was stated that it is undesirable to remove WIs from the December 1999 target date, but to flag the problems to the TSG for resolution before the next TSG meetings and then decide whether or not to include the item in the Release 1999 specification set.
The status of the work of SA WG2 was noted by TSG SA as providing a good overview. Some more detailed discussion of some of the items took place under the relevant under agenda item.
It was stated that in LCS, the location methods are not specified and it was asked if it is intended to leave positioning methods out of the study. The SA WG2 chairman responded that it has not yet been included in Release 1999, due to the requirements for LCS in the 3G system
It was stated that CBS specifications requires more discussion between T WG2 and TSG RAN.
Full integration of most security features on schedule but correction CRs to some R99 specifications envisaged until March/April 2000. This was questioned and it was clarified that in this period it is unavoidable that some specifications will need corrections of the Release 1999.
The lack of input reported from N3 is due to the lack of dedicated expertise in this area and CN WG3 would welcome delegates who knowledgeable in these areas.
It was asked whether the Co-ordination ad-hoc groups had considered the current WI set of various groups. It was explained that the work is being defined in sets of work packages and building blocks rather than in Work Items. Some linking of the current work items is needed in order to allow the project management required from the overall 3GPP Work Programme.
TD SP‑99387: TS 23.107 v2.0.0 (which was previously allocated as 23.917): "QoS Concept and Architecture" was presented for approval as a TS and not as earlier planned a TR. It was Approved as a TS.
TD SP‑99388: TR 23.922 version 1.0.0: "Architecture for an All IP network" was presented for information.
TD SP‑99389: TR 23.923 version 1.0.0: "Combined GSM and Mobile IP Mobility Handling in UMTS IP CN" was presented for information.
TD SP‑99408: TS 23.171 version 1.0.0: "Functional stage 2 description of location services in UMTS" was presented for information. It was proposed to have two separate specifications for LCS, one GSM specific (GSM 03.71, handled by ETSI SMG) and one 3GPP specific(TS 23.171). The document was noted.
TD SP‑99409:TS 23.127 v0.2.1: "Virtual Home Environment / Open Service Architecture" was provided for comment. Version 0.3.0 was also provided, but had not yet been approved by SA WG2 due to technical reasons. When approved by SA WG2 (by e-mail approval) it will be sent out to the TSG SA e‑mail reflector as version 1.0.0 for information for presentation in December 1999 for Approval by TSG SA.
It was remarked that currently the specification could not be considered as a VHE specification, because it did not really provide any new means for provision of service in foreign networks and it was necessary to rely on CAMEL.
During the presentation the following question in relation to the work on the architecture for Release 2000 was raised by SA WG2 to TSG SA:
-	Should Release 99 CS-terminals be supported in Release 2000 networks?
	Assumption is yes, architecture option proposed in the TR
TSG SA agreed that the answer is Yes.

The following Project Plan documents were presented during the presentation and was noted as for information by TSG SA:
-	SP-99390: TR 30.801 v.1.0.0, Overall Project Plan.
-	SP-99391: TR 30.802 v.1.0.0, Project plan on Bearer Services and QoS
-	SP-99392: TR 30.804 v.1.0.0, Project plan on GSM/UMTS Interoperation and Mobility Management
-	SP-99393: TR 30.806 v.1.0.0, Project plan on Location based services
-	SP-99394: TR 30.808 v.1.0.0, Project plan on Packet Architecture and Circuit Architecture
-	SP-99395: TR 30.810 v.1.0.0, Project plan on Security
-	SP-99396: TR 30.812 v.1.0.0, Project plan on Services and Service Platforms
Delegates are encouraged to read the documents received for information and noted and to forward comments to SA WG2.
As a reaction to the high number of Liaison Statements in TSG SA, which was also reported to be the case in SA WG2, the TSG SA Chairman commented that the large numbers of liaison statements to TSG SA and its working groups should be avoided wherever possible, by use of direct contact with the Chairman, Vice-Chairmen and Colleagues, or via MCC Support Team members.

5.2.2	Questions for advice and decisions from TSG-SA WG2
TD SP‑99351: Liaison statement concerning the work plan for all-IP option for release 2000. This contribution was noted as being overtaken by events and was noted by TSG SA.
5.2.3	Approval of contributions from TSG-SA WG2
408, 409
TD SP‑99387: TS 23.107 v2.0.0 (which was previously allocated as 23.917) was presented for approval. The document was approved and placed under TSG SA Change Control.
The following documents were provided to TSG SA for information and were noted:
TD SP‑99389: TR 23.923 v.1.0.0, Combined GSM and Mobile IP Mobility Handling in UMTS IP CN
TD SP‑99390: TR 30.801 v.1.0.0, Overall Project Plan
TD SP‑99391: TR 30.802 v.1.0.0, Project plan on Bearer Services and QoS
TD SP‑99392: TR 30.804 v.1.0.0, Project plan on GSM/UMTS Interoperation and Mobility Management
TD SP‑99393: TR 30.806 v.1.0.0, Project plan on Location based services
TD SP‑99394: TR 30.808 v.1.0.0, Project plan on Packet Architecture and Circuit Architecture
TD SP‑99395: TR 30.810 v.1.0.0, Project plan on Security
TD SP‑99396: TR 30.812 v.1.0.0, Project plan on Services and Service Platforms
The following CRs were presented for approval:
-	SP-99397: CRs to 23.002 v.3.0.0, Network architecture
Approved
-	SP-99398: CRs to 23.060 v.3.0.0, General Packet Radio Service (GPRS); Service description; Stage 2
Approved
	It was noted that an impact is expected on the work of CN WG1.
-	SP-99399: CRs to 23.110 v.3.1.0, UMTS Access Stratum; Services and Functions
Approved
-	SP-99400: CRs to 23.121 v.3.0.0, Architectural Requirements for Release 1999
Approved (only those approved by SA WG2)
-	SP-99401: CRs to 23.920 v.3.0.0, Evolution of the GSM platform towards UMTS
Approved

The SA WG2 Chairman reported that there were a number of CRs which were not available at the meeting due to problems the previous week with the E-mail reflector, which had made it impossible to have a final SA WG2 approval by e‑mail. In order to make the stage 2 ready as quickly as possible, he asked for the possibility of e‑mail reflector approval by TSG SA. It was agreed that, due to the urgency, that TSG SA would conditionally approve the CRs in TD SP‑99485, subject to e‑mail acceptance by SA WG2. Meaning that the CRs which receive no objection from SA WG2 have received TSG SA approval.

TD SP‑99388: TR 23.922 V 1.0.0, Architecture for an all-IP network 
This document was presented to TSG SA by the editor using the slides from the SA WG2 report TD (SP‑99386).
As a comment to the report, TD SP‑99474: Comments on the R00 All‑IP TR v 0.1.4,  was then introduced by Telia. The document requests, amongst other things, that clear references are made to the supported Release 99 features, as well as a clear list of the features supported for Release 2000. Furthermore, the document suggests that the architecture work is stopped until SA WG1 have established a clear set of requirements for the services and features to be supported.
It was noted that a brief discussion in SA WG1 on the stage 1 had already taken place and TSG SA agreed that the requirements from SA WG1 needed to be completed before the architecture can be completed by SA WG2. However, it was not felt that there was a need to stop the work of SA WG2 fully until the Stage 1 is completed, but simply ask SA WG2 to prioritise assisting SA WG1 in completing the requirements.
As a response to the questions on services supported and the real benefit of the new architecture, it was remarked that TD SP‑99283 from the SA#4 meeting gives a description of All‑IP networks and service advantages that can be gained.
In summary, the report of SA WG2 was accepted by TSG SA noting that the presented architecture can not yet be considered final. SA WG2 was tasked to continue the work on the release 2000 architecture and with priority to assist SA WG1 to complete their requirements specifications, which need to be completed before the architecture specifications can be considered as complete. It was stressed that support for Release 1999 terminals and services is seen as an important priority by TSG SA.
The document TD SP‑99388 was noted and SA WG2 thanked for all of their work and progress on the document.

5.3	TSG-SA WG3
5.3.1	Report from TSG-SA WG3
TD SP‑99426: Report from SA WG3 to TSG SA. The SA WG3 Chairman presented the report, given in TD SP‑99480. 11 CRs to TS 33.102 and TS 33.105 were presented to TSG SA for approval. TS 33.103 and TR 33.902 were presented to TSG SA for approval (TD SP‑99424 and TD SP‑99423).
It was reported that the core network signalling security for INAP over SS7 and GTP security might be moved into Release 2000 as it will not be finalised in time for Release 1999. Security of MAP over IP will be addressed in Release 2000 and detailed specification of security features for this will not be available until Release 2000. There has been some contributions in the area of security for mobile IP. On this background it might be possible to progress this already for Release 1999. For the other areas, SA WG3 is on schedule.
There was some concern over the stability of the approved security documents due to the indication that there might be additional changes caused by implementation. The TSG SA Chairman clarified that even for approved documents which are considered complete, it is likely that some corrective changes will occur as a result of the detailed work, in other groups or by real life implementations. In this case, it means that changes are expected only for corrective reasons and that no additions to the features and functions of the specification can be made.
It was concluded that SA3 have completed their work to the extent of their responsibility. It was noted that an overall project plan for security related issues had been provided by TD SP‑99395. Delegates were asked to consider this report and concentrate on the critical areas and to contribute to the relevant groups on these areas to speed up the work.
If no input is received by any working group, then the issues will inevitably be postponed. Anyone with concerns about the progress of any work area should ensure that the responsible group receives the necessary contribution and support to complete the work on time.
The Algorithm design has been based on MISTY (but the algorithm is not the MISTY algorithm). It has been decided to use external evaluators for the algorithm and their selection will be done at SA3#7 Meeting based on the advice of ETSI-SAGE. The evaluation period has been set for 15 November to 13 December 1999. This ends just before the December 1999 TSG Meetings, and it is expected that if are any major problems show up they will be signalled before this date. If a problem is found with the algorithm, then it is inevitable that the work will be delayed to allow the problem to be corrected or a new algorithm to be designed. The Authentication mechanism has been submitted to 3GPP2 who are about to select their mechanism from a number of candidates.
It was reported that the approval of the Lawful Interception architecture has been delayed until SA#6 Meeting. More regulator involvement is required in the work of SA WG3, only regulators from UK and Germany are currently represented in the group.
The meeting report of the last two meetings were provided for information in TD SP‑99477 and TD SP‑99478.

5.3.2	Questions for advice and decisions from TSG-SA WG3
No document was allocated to this agenda item.

5.3.3	Approval of contributions from TSG-SA WG3
CRs approved:
TD SP‑99417:  33.102v 3.1.0: "Security Architecture". CRs- CR012, 013, 014, 015, 016, 017, 018, 019 
Approved.
TD SP‑99418: 33.105 v3.0.0: "Cryptographic Algorithm Requirements". CRs - CR001, 002, 003
Approved.
The impact of increasing the ciphering length of the MAC from 24 to 32 was questioned. It was stated that there should be very little if any impact, however, RAN WG2 were asked to look at the messages affected by 33.105 CR002 and check that the critical messages are adequately protected.
TD SP‑99424 (replaces TD SP‑99410): TS 33.102 - 3G Security; Integration Guidelines. This TS was presented to SA for approval. This TS was approved and placed under TSG SA Change Control as version 3.0.0. A typographical error in Figure 1 (at bottom of UE block, DCUE should be DCDI. Other minor changes might be needed. It was agreed that these changes could be done by CRs for the next TSG SA meeting.
TD SP‑99423: TR 33.902 v0.1.0 - Formal Analysis of the 3G Authentication Protocol with Modified Sequence number Management. This was originally presented for information, due to lack of time to change the order of clauses editorially. But this was reconsidered as the information was already stable and found very useful for others outside SA WG3. Therefore the report was suggested to be approved noting that changes are expected for the next meeting of TSG SA. The document was approved and placed under TSG SA Change Control as version 3.0.0.
TD SP‑99425: Draft LS to TIA TR-45 AHAG on 3GPP authentication mechanism as a candidate for ESA. It was noted that Vodafone Airtouch had proposed the 3GPP authentication mechanism to be used by 3GPP and that this was supported by SA WG3 as it would simplify network interworking and roaming across the systems developed by 3GPP and 3GPP2. Based on this argument, the draft liaison statement indicating TSG SA support for the proposal had been drafted. The liaison statement was approved by TSG SA and will be sent TIA TR45 AHAG.
Finally, it was noted that the All-IP security aspects have not yet been studied by SA WG3 and contributions and support relating to this will be welcomed by the group.

5.4	TSG-SA WG4
5.4.1	Report from TSG-SA WG4
TD SP‑99363: The Chairman of SA WG4 presented the status report given in TD SP‑99363. TS 26.094 v. 2.0.0 was presented for Approval, in TD SP‑99353. TS 26.073 v 1.0.0 and TS 26.101 v. 1.4.0 were presented for information, in TD SP‑99355 and TD SP‑99356. A Work Item description for the Wideband Codec was presented for approval, in TD SP‑99354. CRs to TS 26.911 and 26.111 were presented for approval in TD SP‑99357, TD SP‑99358 and TD SP‑99259.
SA WG4 informed  TSG SA that the joint SA WG1, SA WG2, CN WG1, CN WG2 meeting on Multimedia had reviewed the content of the proposed specification on Call set-up Requirements for Circuit Switched Multimedia Telephony Service (TS 26.112) and had suggested to give CN WG3 the responsibility of the content of this specification, e.g., by including it in the existing CN specifications. As a result, this specification will be deleted from the list of SA WG4 deliverables.
The AMR Speech Codec is expected to be ready for Release 1999 and approved at the TSG SA #6 meeting, except for the Characterisation Phase Test Report, which should be ready for approval at the TSG SA #7 Meeting.

5.4.2	Questions for advice and decisions from TSG-SA WG4
No document was allocated to this agenda item.

5.4.3	Approval of contributions from TSG-SA WG4
Specifications presented for approval:
TD SP‑99353: TS 26.094 v. 2.0.0 - AMR speech codec; Voice Activity Detector (VAD). This specification was approved and placed under TSG SA Change Control as version 3.0.0.
Specifications presented for information:
TD SP‑99355: TS 26.073 v 1.0.0 ANSI-C code for the AMR speech codec. This was provided for information and the document was noted. Noting that the document contained the ANSI C-code, which in the ETSI document is protected by a copyright statement, it was questioned if a similar copyright statement would be applied to the cover page of the 3GPP specifications. MCC reported that there had been discussions with Lawyers on this issue and that a copyright statement will be added to all documents on the server. The copyright statement as it will appear on 3GPP documents in the future was displayed on the screen in the meeting room for delegates to check.
TD SP‑99356: Updated version of TS 26.101 (v. 1.4.0): "Mandatory Speech Codec speech processing functions; AMR Speech Codec Frame Structure". The document was presented for information and noted.

CRs presented for approval:
TD SP‑99357 and TD SP‑99358: : CR 001 and CR002r1 to TR 26.911 v. 3.0.1: "Codec(s) for Circuit Switched Multimedia Telephony Service Terminal Implementor’s Guide".
Approved.
TD SP‑99359: CR 001 to TS 26.111 v. 3.0.1: "Codec for Circuit Switched Multimedia Telephony Service; Modifications to H.324".
Approved.

WIs presented for approval:
TD SP‑99354: A WI description for the Wideband Codec. This WI has been updated from the similar WI agreed earlier in ETSI SMG and was presented to TSG SA for approval. The revised WI description was approved.
5.5	TSG-SA WG5
5.5.1	Report from TSG-SA WG5
TD SP‑99380: Summary Report of SA WG5 Activities. The SA WG5 Chairman presented his report to TSG SA. SA WG5 presented 2 CRs to GSM 12.15 v 7.2.1 for approval (TD SP‑99381), and 3G TS 32.104 V1.0.0, 3G TS 32.106 V1.0.0 and 3G TS 32.111 V1.0.0 for information (TD SP‑99382 TD SP‑99383 and TD SP‑99384).

The TSG SA Chairman indicated that the planning for SA WG5 Meeting #8 was considered unacceptable as it overlaps with part of the TSG SA Meeting and even if reduced by 1 day is too close to the TSG SA meeting. As meetings in the days leading up to a TSG meeting does not leave the support team enough time to prepare the inputs to TSG SA from the meeting. SA WG5 were requested to move the meeting. This view was supported by TSG CN Chairman, who reported that a 1‑week rule is in force in TSG CN to allow delegates time to check CRs before the presentation to the TSG and for the support team to prepare the material. The SA WG5 Chairmen undertook to change the meeting date.

5.5.2	Questions for advice and decisions from TSG-SA WG5
SA WG5 asked TSG SA to give direction on the following question:
SA WG5 outputs of the charging information and management information model specification work for the 3G under the existing SA5 Work Items: Should those SA5 specifications (to come in 2000) be considered as a part of Release-99 or Release-2000?
Those outputs, although delivered in 2000 due to the normal “O&M standards delay”, will be based on the Release-99 package. For the sake of a logical synchronisation, SA5 wishes them to be considered as a part of Release-99.
It was considered reasonable to allow the O&M specifications to be part of Release 1999 even if their delivery date is later than December 1999, this was already decided at TSG SA#04.
It was questioned whether some of the specifications elaborated by SA WG5 should be forwarded to ITU as a part of the overall package for IMT‑2000. After some discussion on the relevance of the documents in relation to ITU‑R (Radio Interface only or more wide-ranged), it was decided that there was no need to forward the SA WG5 documents to ITU‑R for the time being.
TD SP‑99484: LS to TSG-SA "Liaisons between SA5 and the TMF". TSG SA noted that SA WG5 requested to liaise with TMF and requested that in the future such questions are dealt with by simple communication between Chairmen, rather than requesting the approval at the SA Plenary.
SA WG5 asked about the Charging requirements for Release 1999. Representatives of the GSM Association responded that the GSM Associations 3GPP Working Party are working on the issue and that the Chairman of this group is aware of the timing of SA WG5 charging documents. It was noted that SA WG5 can expect that the GSM Association will forward their requirements to SA WG5.

5.5.3	Approval of contributions from TSG-SA WG5
CRs presented for Approval:
TD SP‑99381: CRs to GSM 12.15 V7.2.1: "General Packet Radio Service (GPRS); GPRS Charging".
Approved.
Specifications presented for Information:
TSG SA were requested to take note of the following documents.
TD SP‑99382: 3G TS 32.104 V1.0.0. This was noted by TSG SA. It was also noted that this specification is planned to be presented to SA#6 for approval.
TD SP‑99383: 3G TS 32.106 V1.0.0. This was noted by TSG SA. It was also noted that this specification is planned to be presented to SA#6 for approval, but may be delayed to TSG SA#7.
TD SP‑99384: 3G TS 32.111 V1.0.0. This was noted by TSG SA. It was also noted that this specification is planned to be presented to SA#6 for approval, but that there is some risk that it may be delayed to TSG SA#7.

5.6	Review of TSG-SA work programme (including release 2000 planning)
This was dealt with during the presentations of SA WG2 and other WGs.

5.7	Letters to other groups
There were no contributions under this agenda item.

5.8	Other issues
There were no contributions under this agenda item.

6	Technical co-ordination with TSG-CN, TSG-RAN and TSG-T
6.1	TSG-CN
6.1.1	Report from TSG-CN
TD SP‑99462: Report from TSG CN to TSG SA. The report from CN to TSG SA was presented by the TSG CN Chairman (Presentation slides in TD SP‑99461).
TSG CN have tentatively reserved the 1st week of February 2000 for a kick-off meeting on IP activities.
There are still a large number of GPRS CRs and confirmation on the request to freeze these specifications is given in TD SP‑99413. TSG CN believes that the removal of LLC has consequences on GSM-UMTS Handover if different ciphering algorithms are used. The concerned groups (SA WG3 and TSG RAN) have been contacted.
TSG CN have completed the Pre-Paging work and non-CAMEL IST for release 1999. CAMEL Phase 3 Scope has been reduced and this has been communicated to SA WG1 (CN document NP-99255).
A new WI for a Feasibility Study on CAMEL control of Voice over IP services (Release 2000, NP-99287) has been approved.
The Feasibility Study on Out-of-Band Transcoder -Control has been completed (NP-99288). TSG CN decided to go for an implementation along the lines of Alternative 4, based on ITU-T BICC protocol. This is still to be specified.
The high density of WG meetings was noted. The additional support received from the MCC Support Team since the last TSG meetings has been appreciated by all WGs.
TSG CN request information from SA WG1 on work related to SIM Toolkit initiated transactions. CN WG1 are stuck due to the lack of guidance in this area and SA WG1 are requested to provide information. SA WG1 were asked to check the requirements and report to CN WG2.

6.1.2	Questions for discussion in TSG-SA
TD SP‑99466: LS TSG_SA on information flow improvement towards TSG_CN. The resources of TSG CN are stretched due to the large frequency of meetings and cross-group reporting is difficult. This contribution proposes that the relevant SA working groups (SA WG1, SA WG2 and maybe SA WG3) ensures that liaison persons are present and provide reports and background for liaison statements to TSG CN meetings.
The TSG SA Chairman commented that there are many meetings of the working groups in all TSGs. It is becoming critical to ensure that unnecessary liaison statements should be minimised, using another communication channel instead. The MCC Support Team is asked to facilitate this by internal information exchange about the status of the work in the other groups. Issues affecting other groups should be brought to the attention of those groups, without awaiting the next meeting of the TSGs.
This was endorsed by the RAN Vice Chairman, who added that internal company communication was also an important option for reducing the liaisons issued to meetings. 
SA WG2 Chairman reported that somebody would be made available for attendance to the TSG CN meetings and effectively form a liaison between the groups.
It was summarised that persons providing explanations of the problems or issues of one group to another is always welcomed, and should be aimed for in the case of more substantial matters. Generally, the MCC staff, delegates, or e‑mail should be used to inform groups of issues arising instead of waiting for groups to meet.
TD SP‑99465: Chairman's letter to TSG_SA and S2: Ownership of GPRS stage2 specification (03.60 and 23.060). TSG SA was invited to consider:
-	The specification responsibility for GSM 03.60 and TS 23.060 have to be kept together in one group.
-	SA WG2 is responsible for both specifications.
The TSG CN working groups are willing to assist SA WG2 by refining the more detailed part of the specifications, i.e. to be subcontracted.
It is recommended that SA WG2 produces along a table of contents, a "section specific responsibility list" to prevent further "competence/responsibility conflicts".
TSG CN is informed that TS 23.060 might have undergone severe modifications on the recent ad-hoc meeting. This may have consequences for work on specifications in TSG CN domain for Release 1999. But since TS 23.060 now seems to be under modification anyhow SA WG2 may consider either to split the specification in two distinct parts or two separate specifications to cater for future clean responsibility allocation.
The meeting emphasised that the R98 and R99 work areas should remain in one group and not split across the groups. Therefore it was decided that GSM 03.60 and TS 23.060 shall be the responsibility of SA WG2 co-ordinating with TSG CN on necessary items.
TD SP‑99467: Draft ToR for ITU-T ad-hoc group. TSG CN have agreed to create an ad-hoc group for consideration of the ITU‑T work in IMT 2000. This gives 3GPP a link to both ITU‑T and ITU‑R (with the RAN ITU‑R ad-hoc group). TSG CN asked TSG SA to endorse the following:
-	The need for the ITU-T Ad-hoc activities.
-	The draft Terms of Reference for the ITU-T Ad-hoc Group.
-	To support the assignment of this ITU-T Ad-hoc Group to TSG CN.
From the comments made, it was noted that TSG T, TSG RAN, and TSG SA are also dealing with matters of relevance to ITU‑T. The TSG SA Chairman commented that it seemed a good idea to create the suggested group, but that the group would have to deal with all 3GPP matters related to ITU‑T to avoid conflicting positions towards ITU‑T. 
It was agreed to set up the ITU‑T ad-hoc group. It was decided that the group should report to TSG CN for practical issues, and to TSG SA for more policy and strategic matters. Furthermore, it was requested that the relevant working groups of the different TSGs appoint a contact-person for the ITU-T ad-hoc group. There were some concerns over some points of the draft Terms of Reference and a revised version was provided in TD SP‑99492. Delegates were invited to provide comments to TSG CN on the proposed terms of reference. Final approval will be made at the next round of TSG meetings.
TD SP‑99471: Handling of GSM only specifications. This document is a proposal from TSG CN to adopt the approach for the adoption of Change Requests, given in CN TD NP‑99251. TSG CN are willing to accept the responsibility for the maintenance of GSM Specifications in the domain of ETSI SMG3, which are not common GSM/3G specifications.
It was noted that to accept this would require a change to the Scope of 3GPP, and should therefore be raised to the PCG and to the Partner Organisations. From the comments made, TSG SA saw no major problem with the idea, if the Partner Organisations accept to take on the work in 3GPP. It was agreed to forward this to the PCG for decision.

6.1.3	Information on status and changes to deliverables
TD SP‑99463: List of Specifications under the responsibility of TSG CN. This document outlines the status of the CN documents and was noted by TSG SA.
TD SP‑99464: TSG CN Work Item Status List. TSG CN have made an assessment of the maturity of documents for Release 1999 inclusion. This is provided for consideration in the discussions about the content of Release 1999.
6.2	Report from TSG-RAN
6.2.1	Report from TSG-RAN
TD SP‑99460: Status Report on RAN#5. The Chairman of TSG RAN presented his report to TSG SA.
The RAN Chairman reported that for the RAN WG4 the categorisation as not for Release 99 of the open issue "Coexistence with GSM900 and DCS1800" had provoked several objections in TSG RAN and will be discussed further within TSG RAN.
The rapid progress on the Hooks and Extensions was noted.
The T WG2 chairman indicated that terminology SMS Cell Broadcast (SMSCB) as used by RAN WG2 had already been changed by ETSI SMG4 some years ago to "Cell Broadcast Service (CBS)" and T WG2 are using this terminology. The comment was noted and it was agreed that only one term should be used and the RAN WG2 and T WG2 Chairmen were asked to ensure the alignment between the two groups.
The TSG RAN Chairman gave an explanation of the items considered as not complete for Release 1999, but important features for Release 1999 were given. He explained the philosophy that the important features for Release 1999 would be included in the release, but some of the work items would not, due to the work load, be finalised until March 2000, but would then be included in the Release 1999 specification set. A list of these items is included in Attachment 1 of TD SP‑99460. The reason for this approach is to minimise the delay of the completion of the work by targeting these items for a realistic completion date (RAN #7 meeting). It was noted that the full content of Release 1999 would become clear when the Release status forms are completed by each TSG for the TSG SA #6 meeting.
TDD work has been progressed and the proposal from CWTS taken into account. This work is considered as important towards the Harmonisation between 3G systems. The TSG RAN Chairman encouraged delegates to help the CWTS delegates to attend their meetings, by providing the hosting information in good time to allow the necessary Visas and permits to be obtained. The TSG SA Chairman reminded the meeting that the fact that some delegates need Visas to participate in meetings should be kept in mind and information of meeting venues should be provide as early as possible. It would also be very helpful if hosts could assist the delegates with appropriate information/assistance to obtain Visas.
It was reported that the intention of TSG RAN is to complete all essential Release 1999 items by December 1999.

6.2.2	Questions for discussion in TSG-SA
TD SP‑99377: LS on the simultaneous connection of the UTRAN to two Core Networks. This liaison was received from RAN WG2. RAN WG2 would like guidance as to whether a UTRAN should be able to simultaneously support two Core Networks types (e.g. GSM MAP and ANSI-41)?
The SA WG1 Chairman stated that this was not a requirement for Release 1999, but may be a requirement for the Release 2000 work. It was further noted that there should be the flexibility to allow connection in different Core Networks in the future, which would require ongoing checks of the development of the specifications to ensure this is not excluded by developments.
In summary, the response from TSG SA to this question is "Yes", recognising that this is not a Release 1999 requirement, but such a requirement can be foreseen and the specifications should be left open to allow this possibility. Delegates are requested to make regular checks and contributions to ensure that the option is kept in the specifications. 

6.2.3	Information on status and changes to deliverables
Information on status and changes to deliverables was provided as a part of the report given by the TSG RAN Chairman in TD SP‑99460.

6.3	Report from TSG-T
6.3.1	Report from TSG-T
TD SP‑99476: The TSG T Chairman presented his report to TSG SA using the presentation contained in TD SP‑99475.
TSG T suggest that the term "mandatory" in testing specifications should be replaced with the "core" specification. This caused some comments and questions from the TSG SA delegates. It was suggested  that these comments are made directly to TSG T, as they consider this to be the best solution. In general, TSG T believes the term "mandatory" should be avoided in test specifications and should only be used for regulatory mandates.
It was noted that the combination of the 3GPP Radio and 3GPP2 Core Network is for the time being not considered by TSG T, and might need some further investigation, if such test specifications are to be developed in the future. It was noted that the issue of terminal testing was covered by the OHG proposal received at the TSG SA#4 meeting.
TSG-T reported that the issue of audio testing for regulatory type approval testing and future codec testing is subject for discussion with the ETSI STQ meeting (October 18 1999).
TSG T endorsed the T WG2 decision that 3GPP should not produce any technical specifications for a physical interface from the terminal to other devices, except for the Radio and USIM interfaces. This position was not supported by TIM, who believe that there should be a standardised physical interface from UMTS terminals to other devices.
It was noted that, as usual, all members have the right to raise the issue again in T WG2. It was clarified that the presentation slides on this issue only reflect the work area of T WG2.
TSG T inform TSG SA that there is an interaction with PLMN selection in draft report TR 21.910. TSG SA delegates are invited to review this report and to participate in the Workshop proposed by T WG2. A number of comments to the content of the report on multi-mode and system terminals was made. TSG SA noted that this work is ongoing and that the report covers a number of cross TSG issues. Further, the concern of the quality of the current content of report was noted. After some off-line discussions, it was agreed that RAN WG2 would ensure that an input document containing comments and proposals for improvement of the report will be provide to the next T WG2 meeting for consideration. T WG2 should then review the report based on the comments received and forward the resulting version of the report to SA WG2 for further consideration and review.
TSG T informed TSG SA that there had been some discussion on the need for a specifying a linkage of the maximum output power parameter with the type of terminal usage (e.g. hand-held). However, no consensus had been reached on the matter in TSG T. There were a few comments made, indicating an interest in knowing what the most likely power classes would be in practice when different requirements on the terminal, such as maximum output power and SAR is considered. Operators would need to take this into account when planning their networks.
T WG2 have agreed to be responsible for Terminal Management. The views of TSG SA were invited. The SA WG5 chairman reported that the management model needs to be carefully designed and that SA WG5 has the expertise on building the management model. SA WG5 suggest that T WG2 should be responsible for the work but should co-operate with SA WG5 on the overall management model issues. TSG SA agreed this suggestion.
It was reported that TSG T had approved a new work item on USIM Application Toolkit as a part of Release 1999 with March 2000 as the completion date.
The report was concluded by a very detailed overview of the maturity of TSG T work items, the overview tables clearly indicated the planned content of Release 1999 and when finalisation is expected.
The TSG T Chairman requested that support for their work is provided by any means possible in order to allow the maximum progress before TSG T#6 meeting, especially in the areas in danger of not being completed for TSG T#06.

6.3.2	Questions for discussion in TSG-SA
TD SP‑99419: Liaison Statement from TSG T on how to handle approval of MS Conformance Test Specifications coupled to a certain 3GPP release. The liaison statement suggested that test specifications can be delayed relative to the base standards, as they need to be based on the core specifications elaborated by other groups. Further, it suggested that despite the delay relative to the rest of the specifications, the test specifications are kept as part of the Release 1999 package. TSG SA confirmed the principle of the inclusion of particular specifications in the Release set even if they are not ready for the Release deadline. However, it was clearly indicated that any delay should be sought to be minimised.

TD SP‑99458: This was dealt with under Agenda Item 4.1.
TD SP‑99420: This was dealt with under Agenda Item 4.1.
TD SP‑99407: This has been superseded by other discussions on terminology (see TD SP‑99493).
TD SP‑99493: Proposal for UE definition and handling of the GSM references. This proposes that:
-	The definition of UE, comprising the text and both figures above, should be included in TR 25.990.
-	The sentence explaining the relationship to GSM should be included in all relevant specifications.
-	In 3GPP specifications the term MS shall be replaced by the term UE or any of the other relevant abbreviations as specified in the definition of UE above. This can be implemented gradually.
This proposal was accepted and it was noted that "agreeable" proposals for improvement of the definition can be accepted by TSG SA in the future. The proposal was approved.

6.3.3	Information on status and changes to deliverables
TSG T had created a list of it's work items which they consider will be included in Release 1999. This list was provided as a part of the report from TSG T to TSG SA (TD SP‑99475 and TD SP‑99476).
It was clarified that the dates, given in slide 19 of the presentation "Expected qualification for R99 in Dec ’99", is the target dates for version 3.0.0 as before the TSG T#5 meeting. This has now been updated to take into account the potential delay (but are still in the same category for Release 1999 planning).
Concern was expressed over the non-inclusion of USIM Application Toolkit and requested that a first release of the USIM Toolkit be included in December 1999. The Chairman of T WG3 responded that although the group has been working very hard it has not been possible to complete the work for inclusion in Release 1999 in December 1999. It was stated that it may be possible to complete the work in time for December 1999, and if this is done, there is no reason why it should not be in Release 1999 in the set of specifications released in December 1999. It was noted, that T WG3 will attempt to identify everything needed for finalisation and then they will decide whether or not it can be completed by the end of 1999.
It is expected that the final list of Release 1999 status tables will be presented to TSG SA in TSG SA#6 by each of the TSGs as well as from the TSG SA WGs.

6.4	Letters to others groups
TD SP‑99490: 3GPP Radio Interface Specifications (Section 5.x.3). The TSG SA Vice Chairman presented the document which proposes a contribution to be sent to Task Group 8/1 by October 15. It is also proposed to send the contribution to all Organisational Partners and to ask them to fill in the tables with the relevant references and to forward it to ITU-R TG 8/1 in time for the opening of the meeting.
The method proposed, had already been agreed by RAN as a way of referencing the 3GPP material. It was clarified, that the TSG SA contributions are only intended to contain items related to the Radio interface.
The proposed list of 3GPP specifications related to IMT‑2000 Radio Interface Specifications were considered and it was agreed to approve this contribution and to forward it with the equivalent contribution from TSG RAN. The Chairman of the RAN ITU Ad‑hoc group would be asked to handle the forwarding of this.
TD SP‑99491: Proposed position to “Supplement to Recommendation Q.1701” from ITU-T SG XI WP 3/11. This proposes a liaison to ITU‑T on their future role in the IMT‑2000 work, to act as a guiding body for the family members of IMT‑2000. The meeting supported this as being the position of 3GPP TSG SA and the members were invited to base contributions to ITU‑T on this position paper. Further it was noted that TSG CN would need to consider this position paper in their work.

6.5	Content of October specification set
TD SP‑99489: Draft status list for October 1999. All delegates are encouraged to make comments by 20 October 1999 in order to allow it to be included in the TSG SA Meeting report.

6.6	Release ‘99
TD SP‑99468: Definition and completion of Release 1999: The SA Chairman presented the proposal from the TSG Chairmen on the handling of the completion of Release 1999. TD SP‑99468 describes the proposal in textual form and provides a form to be filled in by the TSGs for each work item. The key elements of the proposal are listed below:
Definition of Release 1999
•	R99 is a consistent set of Specifications targeted for finalisation in Dec 1999.
•	R99 identified by a major version 3.x.y
•	R00 identified by a major version 4.x.y
Completion of Release 1999
•	R99 Specifications will be functionally frozen at TSG#6.
•	No further functionality/feature  incorporated into the set of specifications.
•	Corrective CRs are allowed and will continue to be introduced into the R99 version 3.x.y.
Completion of Release 1999
•	Some R99 Specifications may not be completely stable at TSG#6  
•	Specifications belong to R99 and will be become version 3.x.y
Non-completed Release 1999 work
•	In principle, incomplete Release 1999 work should be reallocated to Release 2000
Completion of Release 1999
•	Exceptionally, if the functionality of the late work is essential:
•	TSGs permit CRs introducing the functionality to R99 after TSG#6.
•	Progress and its continued applicability to R99 should be reviewed at every following TSG meeting.
Identification of Incomplete work at TSG#6
•	Work area/Item:
•	Affects :	UE/MS:	CN:	UTRAN:
•	Compatibility issues:
•	Expected completion date:
•	Services impacted:
•	Specifications affected:
•	Tasks within work which are not complete:
•	Consequences if not included in R99:
The proposal for handling of freezing and completion of Release 1999 was approved by TSG SA (noting that the version number given in the document is only intended as an example). 
The TSGs are expected to agree independently the items included in or excluded from Release 1999. This will be forwarded to TSG SA in order to allow TSG SA to co-ordinate the content of Release 1999 and finally define the overall Release 1999 package (avoiding conflicting content between the items in each TSG).

6.7	Release 2000 and beyond
TD SP‑99373: GSM Radio work co-ordination for Release 2000 and beyond. This contribution highlights the current situation of development of 3GPP and GSM Radio related specifications, and perceives a co-ordination and consistency problem with the separate working of the related groups. Some proposals for potential solutions are proposed:
Enhance current organization
-	Joint meetings of SMG radio-related STC’s (primarily SMG2 and its work groups) with 3GPP TSG’s
-	Co-ordination groups to assure that the GSM radio access matters are fully considered
-	Joint Release and WI planning between 3GPP SA and SMG radio-related STC’s (SMG2 and others), under the lead of 3GPP SA.
-	Consider further consolidation or practical joint operation of SMG STC’s with 3GPP TSG’s
Change organization
Include GSM radio access in the Terms of Reference of 3GPP TSG’s.
-	This would effectively move the work of SMG2 and other radio-related STC’s into 3GPP.
-	Organization within 3GPP should be considered. One option is formation of a new GSM RAN TSG.
-	Handling of maintenance activities as distinct from development activities should be considered.

The TSG SA Chairman commented that it could be noted that the Release 2000 work is already closely co-ordinated. SA WG2 have been given the role of specifying the architecture, taking into account that the core network is common for UTRAN and the GSM/EDGE RAN. There are already examples of joint meetings between 3GPP groups and ETSI SMG2 for cases where close co-operation is required. There is a common Support Team for the two systems (MCC), and the TSG SA Chairman believes that we already have a common work planning for the systems. It was also pointed out that a Change to the Scope of 3GPP is outside the scope of the TSGs, and in this case requires agreement of both ETSI (for GSM) and PCG/Partner Organisations (for TSG Scope changes). These comments were agreed by the contributors, but explained that it was considered necessary to inform TSG SA of their ideas and ask delegates to take them back to their companies for further consideration.
It was concluded that TSG SA cannot consider the change of Scope of the project, but that the co-ordination of services and architectures between the 3GPP groups and the ETSI SMG groups should be considered by SA WG1 and SA WG2 as they are tasked to define these in common for both systems. Requests to change the work of ETSI SMG should go to ETSI management bodies, and for the change of Scope of 3GPP to the PCG and Partner Organisations for consideration.
TD SP‑99411: This was discussed under Agenda Item 5.2.
TD SP‑99412: Purposes and documentation of Release 2000. This contribution asks for clarification on how different 3GPP Releases will be identified. The contribution provides a proposal for the identification: For Annual Releases, to produce a document listing all specifications and Reports defining the Release. It suggests that release 1999 specifications will be numbered version 3.x.y, Release 2000 as version 4.x.y, etc. It further states that Release 2000 shall be a superset of Release 1999, containing all of these specifications and Reports.
It was commented that it may not be possible to include all Release 1999 features in an All-IP option Release 2000 network, due to the changes necessary for All-IP.  It was clarified that the France Telecom proposal intended to get clarification of the identification of 3GPP Releases.
A comment was made that the backward compatibility problems experienced in Phase 1 / Phase 2 of GSM should not be repeated in 3GPP.
TSG SA considered the principles of the contribution in turn:
1)	For each annual releases, a document shall contain the list of all specifications and reports defining this release. …
		This has already been accepted by TSG SA.
	Moreover an architecture document shall describe the global architecture, …
	A common architecture description is the responsibility of SA WG2 and TSG SA take note of this request.
	The specification 22.100 contains all the service requirements for Release 99, a similar document shall state the service requirements for Release 2000. 
	There are already plans to keep this type of documentation listing the content of Release 2000. It was noted that there is a desire to have a clear record of the content of planned Releases.
2)	Today the Release 99 specifications are allocated version numbers the general format of which is 3.x.y.
	This has been discussed already, and will be subject to a proposal from MCC, who need to handle the specifications. It was agreed that a clear indication of which Release a document belongs to is required.
3)	Additional features to add to Release 1999 will become part of Release 2000 and upgrade the version number to version 4.x.y
	This is subject to MCC proposals, but is considered likely result.
4)	Generally all the specifications of Release 99 shall be part of Release 2000.
	This is generally expected, but it is not ruled out that Release 2000 can delete some features (although unlikely).
5)	The previous rules imply that the specifications of Release 2000 will be in some ways a superset of Release 1999 specifications.
	This is the expected content of the Releases, and will be taken into account by SA WG1 and SA WG2 in their definition of the Service requirements and Architecture for each Release.
Further comments were received requesting early knowledge of the content of Release 2000 and for prioritisation of the Features in order to allow good planning of the work.

TD SP‑99427: Cross border co-ordination and inter-network soft handover. This contribution outlines problems with cross border co-ordination and handover.
The principle of creating such a work item for Release 2000, to outline the requirements and evaluate the feasibility of different solutions was agreed. More study on the requirements and a work item should be created to develop the requirements and solutions.
TD SP‑99474 (revision of TD SP‑99459): This had been dealt with under agenda item 5.2.3. See the summary of the discussions under agenda item 5.2.3.
TD SP‑99482: Call for Global Unification of IP Network Standardisation for the Wireless Industry. This contribution from Vodafone/Airtouch outlines the developments within the 3G.IP Consortium on All-IP network requirements. Further, it asks for a unification of the New Generation Networks to be developed in 3GPP and 3GPP2.
It was noted that the level of co-operation with 3GPP2 suggested by this contribution, is clearly outside the current mandate for TSG SA. Therefore TSG SA could not take a formal position, but the originator would have to raise this to the PCG and the Partner Organisations for consideration. The contribution was noted, as well as the concern expressed on the potential delay on the current work if such an undertaking was made, and a contrary view, that it could be advantageous to have unified packet-based calls.

6.8	Other issues
TD SP‑99369: Maintenance of earlier releases of 2G GSM versions of specifications. This contribution was provided by MCC for information on the procedures to be proposed to SMG. The document was noted.

The Chairman summarised that the Project seemed to be moving ahead with great progress in the 9 months of it's existence. Hard decisions are expected to be made at TSG #6 meetings on the handling of the items which are not on target at that time.

7	Project Management
7.1	Review of work programme
TD SP‑99374: 3GPP Programme Management for R99 and R2000. BT propose that each TSG discusses and provides a summary (as part of the TSG chairman’s report) to SA#5 of the status of all deliverables to the best of our knowledge at this time.  This should be issued by SA#5 in a compiled form (i.e. a single document).
The first requirement had been fulfilled by the TSGs who had provided information of current status and targets. MCC agreed to compile this information into the status lists produced after the TSG meetings, but will rely upon the information coming from the TSGs and WGs.
A full set of this information is expected at TSG#6 meeting, and time is needed by the TSGs to compile such a detailed list.
It was agreed to wait until TSG SA#6 meeting to have this output document, taking into account that there is much work to be done until then and this should not delay the work up until then. Comments to the status list will be used to give an interim list this time.
TD SP‑99488: Global Roadmap for UMTS and GSM. This contribution outlines the features of GSM and UMTS classified by their status and was provided for information. Each group is asked how to classify the 3GPP items and forward comments to MCC. 
Comments on the content should be forwarded to Alain Sultan, MCC mailto:alain.sultan@etsi.fr. MCC are asked to forward this to all groups for information.

7.2	Handling of October specification set
As for the previous specification sets (June, April 1999) MCC will make a directory available on the ftp server containing the full set of specifications at their approval status after the October 1999 meeting. The usual request for latest drafts of all specifications was made as these are proving difficult to obtain. Chairmen are asked to forward this request down though their groups' organisation, to the rapporteurs and editors.

7.3	Working methods
General:
The TSG SA Chairman requested that any specifications for approval submitted to TSG SA have a cover sheet with a short introduction of the content of the document and a clear list of open issues in the document. Furthermore, as more and more CRs are being produced, delegates who intend to object to a CR are requested inform the Secretary of the WG (MCC Support person) in order to allow these CRs to be separated out from the non-contentious CRs. In order to assist the delegates to prepare such information, the documents should be made available in good time before the meetings.
The Chairman commented that we have made good progress up to this meeting. Delegates are requested to continue with this hard work to ensure the success of the project.
Contributions:
TD SP‑99487: Model for Technical project co-ordination and management. The Chairman presented a plan for management of 3GPP work items.
The ideas of managing the work items using features and building blocks with recorded links between them was generally well received. It was added that MCC could not be expected to identify the level or interactions of the work items currently created and this is a task for SA WG2. It was considered necessary to have very good visibility at the high level. The model had been designed to be simple to allow all members working on the 3GPP project to be aware and understand the model existence.
TSG SA was asked to produce an example of the use of the model using a relatively simple feature, in order to demonstrate the model at all 3GPP working levels. It was recognised that commitment is required from all groups to make the model work.
This model is intended for use for Release 2000 work, so it is intended to start using the model as soon as possible, in order not to have to fit too many existing items into the model. The intention is to create future work items with the position in the model already considered.
It was accepted to try to use the model and to implement it as soon as possible. An example is considered necessary and TSG SA Chairman and SA WG2 chairman will co-operate to produce a simple example.
MCC were asked to provide a Change Request to the Working Methods document containing an elaboration of this model.
7.4	Other issues
There were no contributions to this Agenda Item.
8	Project support
TD SP‑99365: 3GPP Specification 21.101 version 1.0.0. MCC introduced this document which is considered 60% stable and will be input for approval to the TSG SA#6 meeting. TSG SA is invited to assume responsibility for this Specification.
Everyone is asked to review this document and forward comments to MCC for inclusion before the next TSG SA Meeting.
TD SP‑99366: GSM Specification 01.01 version 0.4.0. This was provided as an example of the equivalent to TD SP‑99365 in ETSI SMG.
TD SP‑99364: Report of Support Team activities. A Scrase, MCC, presented the report of the activities of MCC since the last TSG SA Meeting.
SA were asked to consider agreeing some voluntary guidelines on the length of a working day for 3GPP meetings. TSG SA agreed that a 10 hour maximum meeting days should be taken as a guideline.
The SA WG4 Chairman questioned the Task funding for AMR characterisation. He added that work needs to start the preparation for this. It was clarified that the preparation could still go ahead but the actual work requiring funding should not start until the funding is confirmed.
TSG and WG chairmen are asked to forward publicity material and news items to MCC.
There was a request for the replacement of paper copies with CD production. Some delegates requested a quicker distribution of the CD‑ROMs during the meeting. It was explained that CD production was more time-consuming than LAN and that the request for faster distribution of CDs would be noted.
It was decided that any documents used by the 3GPP TSGs and WGs should be available on the 3GPP FTP server.
TD SP‑99379: "New ASN.1 Syntax Checking Service from PTCC", was provided for information.
TD SP‑99428: CR003 to 21.900: "Working Methods".
Approved.

9	Postponed issues from earlier in the meeting
These are covered under their relevant agenda items.

10	Workplan and future meetings
Next meeting : Nice, France  <<Update list >> This is likely to start at 13.00 Wednesday and run late on the evenings and end afternoon on the Friday (20.00 finish). 

11	Any other business
A poll on the electronic working habits of delegates was made with the following results:

LAN only = 50
CD only = 60-63
would NOT USE LAN = 17
would NOT USE CD = 0
would use PC Memory card = 14
HAVE TO USE PAPER = 0
Decision to not ask hosts to print paper copies at future meetings of TSGs. Printers should be made available at electronic meetings and it is preferable to have English language versions of Software on the PCs (Windows, Applications, etc.)
12	Closing of meeting
Thanked host and secretariat support for excellent working conditions and electronic facilities 
Delegates for patience and declared meeting closed.

NOTES TO M.POPE
Request from RAN Chairman to set up a Leaders e-mail list - Chairs/ViceChairs/Secretaries of TSG/WG/SWG only, where informal reports from meetings, if possible containing exec summary of important issues can be disseminated (can help with the informal liaison request from Niels). Set this up and announce it to members of the list.
Need ITU-R list of specs on web next week.
Need report out within 2 weeks (1 week if possible)
Need list of October specs with links on web by next week (20 October for comments to Ians list)