SPECIAL MOBILE GROUP - 株式会社QT · SPECIAL MOBILE GROUP ... A-bis Management of Alarms/faults on the BTS site, ... chosen codec, the Ericsson/Nokia/Siemens 1 (ENS1) Codec,

EUROPEAN TELECOMMUNICATIONS ETSI/TC SMG (98) 4STANDARDS INSTITUTE

ETSI TECHNICAL COMMITTEE SMG

SPECIAL MOBILE GROUP

Report of Meeting No. 27 held in Praha12-16 October 1998

ETSI SMG ETSI/SMG(98)4Meeting n°27Praha, 12th - 17th of October, 1998

(Part A)

Executive Summary SMG#27The SMG#27 Plenary Meeting was held in Praha, Czech Republic. It was hosted by Paegas and EuroTel. SMG#27 wasattended by 212 delegates, including delegations from America, Asia, Africa and Europe, from 25 countries in total.

1 GSM MattersSMG#27 approved 39 Change Requests to GSM Phase 2, 51 Change Requests to Release 96, 242 Change Requests toRelease 97 and 36 Change Requests to Release 98.

Release 97: GSM Release 97 Core Specifications had been completed at SMG#25, with some last actions at SMG#26.Release 97 includes:

A-bis Management of Alarms/faults on the BTS site, A-bis Management of Measure on the BTS site, A-bisManagement of reconfiguration of BTS site, ASCI Phase 2, Calling Name Presentation - US (CNAP-US),CAMEL phase 2, Characteristics and test methods for handsfree mobile station, Completion of Calls to BusySubscriber (CCBS), Enhancement of MAP Extensibility Mechanisms, Enhancements of Fault ManagementServices, General Packet Radio Service Phase 1 (GPRS) - network part, General Packet Radio Service Phase 1(GPRS) - radio part, Mobile Assisted Frequency Allocation (MAFA), Modelling of Fault Management Services,Network Indication of Alerting in the MS, New Multiplexing Protocol on the ME-TE Interface, North AmericanEqual Access, SIM - Security mechanisms for the SIM Application Toolkit, SMS enhancements phase 1, SMSMobile Busy, Support of Private Numbering Plan (SPNP), Support of Shared Interworking Function (SIWF).

Release 98: Work is progressing for Release 98. The core specifications are scheduled for completion until SMG#28.The feature list for Release 98 includes:

Access to auxiliary devices, integrated into the ME platform, through the use of the SIM Application Toolkit;Access to ISPs and Intranets in GPRS Phase 2 – Separation of GPRS Bearer Establishment and ISP ServiceEnvironment Setup; Adaptive Multi-Rate (AMR); BTS performance requirements for very small cell scenarios(Picocells); Call Deflection; Call Forwarding Enhancements (CFE); Calling line identification enhancements(CLIe); Connecting an octet stream to a port on an Internet host (R98); Enhanced Data rates for GSM Evolution(EDGE) - BSS Part; Enhanced Data rates for GSM Evolution (EDGE) - NSS Part; Enhanced QoS Support inGPRS; Follow Me; Fraud Information Gathering System(FIGS); General Packet Radio Service Phase 2 (GPRS)- network part; General Packet Radio Service Phase 2 (GPRS) - radio part; GPRS for PCS1900; GPRS MobileIP Interworking; GSM - Cordless Telephony System (CTS); GSM Mobile Number Portability (EURO) MNP;GSM-API for SIM-Toolkit; Harmonization of the PCS1900 Standards with the GSM Base Specification;Immediate Service Termination (IST); LAPDm performance enhancement; Lawful Interception (LI); LocationServices (LCS); Mobile Station Execution Environment (MExE); Modem and ISDN interworking for GPRS; MSAntenna Test Method; Multiple Subscriber Profile (MSP); Service Provider Number Portability (USA); Supportof Localized Service Area (SoLSA); Tandem Free Operation of speech codecs in Mobile-to-Mobile Calls(MMCs); Unstructured octet stream GPRS PDP Type (R98); User-to-User Signalling (UUS); USSDEnhancements.

In particular, the AMR Selection Phase has been successfully completed in schedule. A Verification Phase for thechosen codec, the Ericsson/Nokia/Siemens 1 (ENS1) Codec, will follow. Completion of the specifications is planned forSMG#28. The Characterisation Phase for the adopted AMR codec is planned for completion by SMG#29. Major benefitsof AMR were again demonstrated, especially

• in FR mode, an increase of C/I tolerance of 4 dB to 6 dB

• in HR mode, at low error conditions – quality equal to G.728 or G.729 ("wireline")

• in FR dynamic conditions - over 1 delta MOS compared to GSM EFR.

ETSI/ SMG(98)4 Part A, page 2 98/11/23

Release 99: In addition to the Release 99 work items:

Low Voltage SIM/ME Specification; Service Continuity and Provision of VHE via GSM/UMTS;Architecture of the GSM-UMTS Platform; Architecture overview of the GSM-UMTS System; CAMELPhase 3; Noise Suppression for AMR speech codec,

SMG#27 approved the following new Release 99 work items:

Access to ISPs and Intranets in GPRS Phase 2 – Wireless/Remote Access to LANs (R99); BSS co-ordination of Core Network Resource allocation for class A GPRS services -GSM-UMTS CoreNetwork (R99); BSS co-ordination of Radio Resource allocation for class A GPRS services - GSMRadio Access (R99); Charging and Billing for GPRS – Advice of Charge; Charging and Billing forGPRS – Hot Billing; Charging and Billing for GPRS – Pre-Paid; Fraud Information Gathering Systemapplied to GPRS; GPRS - Point-To-Multipoint Services; MExE Release 99; Provision of texttelephony service in GSM and UMTS; Study on Combined GSM and Mobile IP Mobility Handling inUMTS IP CN.

2 UMTS MattersSMG#27 approved 4 Change Requests to UMTS Specifications (a fifth CR is circulated for approval by correspondenceby 18 Nov 1998).

Work items: In addition to the UMTS Work Items:

Service Continuity and Provision of VHE via GSM/UMTS; ; Advanced Addressing; Architecture of theGSM-UMTS Platform; Architecture overview of the GSM-UMTS System; Automatic Establishment ofRoaming Relations; New Access Network to Core Network (BSS-NSS) interface,

SMG#27 approved the following new UMTS work items:

Charging and Billing for GPRS – Hot Billing; End to End UMTS QoS Management; GPRS - Point-To-Multipoint Services; IP-in-IP tunneling in GPRS backbone for UMTS, phase 1; Provision of texttelephony service in GSM and UMTS; Study on Combined GSM and Mobile IP Mobility Handling inUMTS IP CN; UMTS Charging & Billing; UMTS Core based on ATM Transport; UMTS Numbering,Addressing and Identities; UMTS Open Service Architecture; Virtual Home Environment.

ETSI SMG ETSI/SMG(98)4Meeting n°27Praha, 12th - 16th October, 1998Status: approved

(Part B)

CONTENTS

1 GSM MATTERS.................................................................................................................................1

2 UMTS MATTERS...............................................................................................................................2

0 ADOPTION OF AGENDA ..................................................................................................................4

1 MEETING REPORT OF SMG#26........................................................................................................4

2 CHAIRMAN’S REPORT......................................................................................................................4

3 TARGETS OF SMG#27.......................................................................................................................5

4 LIAISONS WITH OTHER BODIES......................................................................................................54.1 T1P1 ........................................................................................................................................................................54.2 INFORMATION FROM ECTEL TMS......................................................................................................................6

5 SMG MATTERS.................................................................................................................................75.1 LIAISON STATEMENTS TO SMG..........................................................................................................................75.2 [DELETED AGENDA ITEM]...................................................................................................................................75.3 [DELETED AGENDA ITEM]...................................................................................................................................75.4 PT SMG STATUS REPORT.....................................................................................................................................75.5 REPORT VOLUNTARY FUNDING TASK FORCE................................................................................................85.6 AD HOC GROUP ON WORKING METHODS........................................................................................................9

5.6.1 Main activities..............................................................................................................................................................95.6.2 Decisions of SMG#27................................................................................................................................................11

5.7 REPORT ON GLOBALISATION...........................................................................................................................12

6 GSM MATTERS............................................................................................................................... 136.1 SMG1 ......................................................................................................................................................................13

6.1.1 General 136.1.2 Change requests..........................................................................................................................................................136.1.3 New specifications.....................................................................................................................................................146.1.4 Work items/areas........................................................................................................................................................146.1.5 Liaison statements ......................................................................................................................................................15

6.2 SMG2 ......................................................................................................................................................................156.2.1 General ......................................................................................................................................................................156.2.2 Change requests..........................................................................................................................................................156.2.3 New specifications.....................................................................................................................................................166.2.4 Work items, feasibility studies and other work areas.................................................................................................166.2.5 Liaison statements ......................................................................................................................................................17

6.3 SMG3 ......................................................................................................................................................................176.3.1 General ......................................................................................................................................................................176.3.2 Change requests..........................................................................................................................................................176.3.3 New specifications.....................................................................................................................................................196.3.4 Work items/areas........................................................................................................................................................196.3.5 Liaison statements ......................................................................................................................................................206.3.6 Other issues................................................................................................................................................................20

6.4 SMG4 ......................................................................................................................................................................206.4.1 General ......................................................................................................................................................................206.4.2 Change requests..........................................................................................................................................................206.4.3 New specifications.....................................................................................................................................................216.4.4 Work items/areas........................................................................................................................................................216.4.5 Liaison statements ......................................................................................................................................................21

6.5 T1P1 WORK ITEMS...............................................................................................................................................216.6 SMG6 ......................................................................................................................................................................22

ETSI/SMG(98)4 Part B, page 2 98/11/23

6.6.1 General; confirmation of Chair...................................................................................................................................226.6.2 Change requests..........................................................................................................................................................226.6.3 New specifications.....................................................................................................................................................236.6.4 Work items .................................................................................................................................................................23

6.7 SMG7 AND TYPE APPROVAL MATTERS..........................................................................................................246.7.1 General ......................................................................................................................................................................246.7.2 Change requests to GSM 11.10 ..................................................................................................................................246.7.3 New specifications.....................................................................................................................................................246.7.4 Regulatory issues........................................................................................................................................................246.7.5 Work items .................................................................................................................................................................256.7.6 R&TTE Directive.......................................................................................................................................................266.7.7 Voluntary Certification Scheme..................................................................................................................................276.7.8 Liaison Statements......................................................................................................................................................27

6.8 SMG8 ......................................................................................................................................................................276.8.1 General ......................................................................................................................................................................276.8.2 Change requests..........................................................................................................................................................276.8.3 Specifications.............................................................................................................................................................276.8.4 Releases .....................................................................................................................................................................276.8.5 Liaison with other bodies...........................................................................................................................................27

6.9 SMG9 ......................................................................................................................................................................276.9.1 General; new scope of SMG9 ....................................................................................................................................276.9.2 Change requests..........................................................................................................................................................286.9.3 New specifications.....................................................................................................................................................306.9.4 Work items .................................................................................................................................................................306.9.5 SMG9 areas outside GSM and UMTS........................................................................................................................306.9.6 Other issues................................................................................................................................................................30

6.10 SMG10 ..................................................................................................................................................................306.10.1 General.....................................................................................................................................................................306.10.2 Change requests........................................................................................................................................................316.10.3 New specifications...................................................................................................................................................316.10.4 Work items/areas......................................................................................................................................................316.10.5 Liaison statements ....................................................................................................................................................33

6.11 SMG11 ..................................................................................................................................................................336.11.1 General.....................................................................................................................................................................336.11.2 Change requests........................................................................................................................................................336.11.3 New specifications...................................................................................................................................................336.11.4 Presentation of AMR Selection Phase Results. ........................................................................................................336.11.5 AMR Implementability aspects ................................................................................................................................346.11.6 IPR matters on AMR................................................................................................................................................356.11.7 Other aspects of AMR Selection phase evaluation...................................................................................................356.11.8 AMR Selection.........................................................................................................................................................356.11.9 AMR Project scheduling and open issues.................................................................................................................35

6.11.9.1 Optimisation phase......................................................................................................................................................356.11.9.2 Other issues.................................................................................................................................................................36

6.11.10 Work items except AMR ........................................................................................................................................376.12 SMG12 ..................................................................................................................................................................37

6.12.1 General.....................................................................................................................................................................376.12.2 Change requests........................................................................................................................................................376.12.3 New specifications...................................................................................................................................................376.12.4 Work items ...............................................................................................................................................................376.12.5 Other issues..............................................................................................................................................................38

6.13 GSM PROGRAM MANAGEMENT.....................................................................................................................386.13.1 Phase 2+ Work item list and Phase 2+ Roadmap .....................................................................................................386.13.2 GSM Work Items......................................................................................................................................................38

7 UMTS MATTERS............................................................................................................................. 387.1 SMG1 ......................................................................................................................................................................38

7.1.1 Change requests..........................................................................................................................................................387.1.2 New Specifications ....................................................................................................................................................397.1.3 UMTS Phase 1............................................................................................................................................................397.1.4 Work items .................................................................................................................................................................40

7.2 SMG2 ......................................................................................................................................................................42


7.2.1 General ......................................................................................................................................................................427.2.2 Evaluation report to ITU-R.........................................................................................................................................427.2.3 UTRAN work plan .....................................................................................................................................................437.2.4 SMG2 UMTS groups..................................................................................................................................................437.2.5 Specification structure................................................................................................................................................437.2.6 Liaisons......................................................................................................................................................................447.2.7 IMT-2000 RTT harmonisation and convergence........................................................................................................457.2.8 Other issues................................................................................................................................................................47

7.3 SMG3 ......................................................................................................................................................................487.4 SMG4 ......................................................................................................................................................................48

7.4.1 General ......................................................................................................................................................................487.4.2 New work items .........................................................................................................................................................497.4.3 Standardising embedded applications in UTMS.........................................................................................................49

7.5 T1P1 MATTERS ON IMT 2000 .............................................................................................................................507.6 SMG6 ......................................................................................................................................................................507.7 REPORTS FROM UMTS FORUM, 3 GIG, PROGRESS REPORT ON IPR ISSUES............................................50

7.7.1 UMTS Forum..............................................................................................................................................................507.7.2 3GIG ......................................................................................................................................................................507.7.3 Progress report on IPR issues.....................................................................................................................................51

7.7.3.1 Report from ETSI legal adviser....................................................................................................................................517.7.3.2 IPR Statements of QUALCOMM..................................................................................................................................517.7.3.3 UMTS IPR Working Group...........................................................................................................................................52

7.8 UMTS PROGRAM MANAGEMENT.....................................................................................................................527.9 SMG9 ......................................................................................................................................................................547.10 SMG10 ..................................................................................................................................................................54

7.10.1 Change requests........................................................................................................................................................547.10.2 New specifications...................................................................................................................................................557.10.3 SMG10 work plan for UMTS...................................................................................................................................55

7.11 SMG11 ..................................................................................................................................................................557.11.1 Liaison statements ....................................................................................................................................................56

7.12 SMG12 ..................................................................................................................................................................567.12.1 New specifications...................................................................................................................................................567.12.2 Work areas ...............................................................................................................................................................567.12.3 Work Items...............................................................................................................................................................57

8 NEXT MEETINGS............................................................................................................................ 57

Annex 1: LIST OF PARTICIPANTS...................................................................................................... 59

Annex 2: STATUS OF CRS AND NEW SPECIFICATIONS PRESENTED TO THE MEETING.............. 59

Annex 3: LIST OF DOCUMENTS......................................................................................................... 59

Annex 4: LIAISON STATEMENTS....................................................................................................... 59

Annex 5: STATUS OF SMG SPECIFICATIONS AFTER THE MEETING.............................................. 59

Annex 6: ROADMAP AND WI STATUS OF GSM PHASE 2+ WORK ITEMS AFTER THEMEETING .................................................................................................................................. 59

Annex 7: PT SMG STATUS REPORT................................................................................................... 59

Annex 8: STRUCTURE OF SMG AND SUBGROUPS........................................................................... 59

Annex 9: TOKYO, 7-9 OCTOBER 1998 ARIB, ETSI, T1, TTA AND TTC AGREED FRAMEWORK(TDOC SMG P-98-574)............................................................................................................... 59


Fred Hillebrand, Chairman of SMG, opened the meeting and thanked the hosts, EuroTel and Paegas (RadioMobil), thetwo GSM operators in the Czech Republic, for hosting the meeting.

Robert Chvátal, Marketing Director of Paegas, addressed the meeting and welcomed the delegates on behalf of both hosts,Paegas (RadioMobil) and EuroTel. He informed SMG, among others, about the immediate success of GSM in the CzechRepublic (1996: 1,3% penetration; 1997: 5%; 1998: 10% to be expected), and about the innovations taken by the Czechoperators (first mobile operators in the world to launch Internet telephony; wide usage of SIM toolkit, e.g. for banking).

Fred Hillebrand gave a special welcome to the Korean, Japanese, Chinese and North-American delegations, as well as -last but not least - to all other delegations having carried out the work for all the time.

0 Adoption of agendaThe agenda in Tdoc SMG P-98-571 was approved with the following modifications:

• Agenda items 5.2 and 5.3 were deleted;

• to agenda item 5.7, a sub-item “discussion of future work organisation” was added.The importance of an in depth discussion of the globalisation issues including the way ahead before closure of the GSMmatters at SMG#27 was stressed, in view of the importance of a continuation of work without delay and in view of thefact that SMG#27 would probably be the last meeting of SMG in the present form and with the present scope.

1 MEETING report of SMG#26The SMG#26 report had been approved by correspondence. SMG#27 plenary noted that approval.

2 Chairman’s reportFred Hillebrand, SMG Chairman, presented the Chairman's Report - From SMG#26 in June 98 to SMG#27 in October98, source SMG Chairman, in Tdoc SMG P-98-570. Main activities and results of the time between SMG#26 andSMG#27:

• good progress on GSM Release 98;

• AMR process ready for codec selection;

• good progress on G-UMTS;

• Release 99 contents agreed in principle;

• UTRA evaluation report for ITU completed;

• first specifications on UMTS system architecture prepared by SMG12 forinformation.

He also reported on the main developments on globalisation of G-UMTS, cf. section 5.7.


3 Targets of SMG#27The targets of SMG#27 in Tdoc SMG P-98-570 were approved by SMG#27:

• GSM Progress for Release 98∗ content and progress of Release 98∗ guidance to STCs for selected questions∗ AMR selection

• UMTS Progress∗ content of Release 99∗ basic concepts on network aspects

• Secure future technical support by voluntary funding

• Globalization of specification work∗ information of SMG∗ guidance for SMG representatives in UGG.

4 Liaisons with other bodiesNote: There has been no report from GSM MoU to SMG#27, since GSM MoU had its meeting a week after SMG#27.

4.1 T1P1The T1P1.5 Status Report to SMG#27 in Tdoc SMG P-98-572 was presented by Ed Ehrlich, T1P1.5 Chairman. Hereported on

• progress on Location Services (LCS) (see section 6.5);

• progress on GSM/PCS harmonization activities (see section 6.5);

• a new T1P1 Work Item proposed for GPRS / EDGE (see section 6.5);

• progress on Number Portability:∗ expectation to approve or ballot draft proposed ANSI standard on Number Portability for PCS

1900 SMS and Other Services at December T1P1 meeting;∗ next focus on a Phase 2 version of the existing NP stand T1.708 on PCS 1900 Service Provider

Number Portability;∗ new SCCP translation type to support SMS agreed by T1S1;

• progress on UMTS / IMT- 2000:∗ T1P1.5 work efforts in the UMTS ad hoc Group:

◊ Proponent for WCDMA/ NA RTT in TG 8/1;◊ Drafting proposed T1P1 positions on 3GPP;

• progress on Harmonization: T1P1 ad hoc Group on Harmonization completesReport: Focused on US CDMA RTT proposals;

• the agreement of T1P1 and TR46 to converge WCDMA/ NA and WIMS (Wideband ISDN Multi-media Services):∗ primary technical motivation to improve Packet Data performance∗ WP- CDMA Committee established (Joint T1P1.5 and TR46.1);∗ working toward short term deliverable for November 1998 TG8/1 meeting.


Discussion of the T1P1.5 Status Report to SMG#27:

• The SMG4 Chairman, Kevin Holley, commented that, due to the too lateavailability at the last SMG4 plenary, SMG4 had not been able to review the T1P1proposals on GPRS enhancements, and plan to do that at their next plenary.

• Concerning convergence activities for UTRA, WCDMA/NA and for WIMS,Ed Ehrlich explained that the T1P1 WCDMA/NA will be brought into 3GPP forconvergence; if TIA joins 3GPP in future, they could bring WIMS into 3GPP aswell, but this is currently not intended by TIA.

• Handling of GSM/PCS Harmonization CRs: Around 50 CRs have been adoptedby T1P1 to their PCS 1900 (=GSM 1900) specifications in order to harmonisewith the SMG specifications on GSM. T1P1 hopes that these CRs can be preparedby the SMG STCs for approval at SMG#28, so that Release 98 can base oncommon specifications on GSM 900/1800/1900.

4.2 Information from ECTEL TMSHeinz Blankenfeld, succeeding François Grassot as Chairman of ECTEL TMS for the next 2 years, presented the reportfrom ECTEL TMS in Tdoc SMG P-98-573.

ECTEL, the European Telecommunications and Professional Electronics Industry, is a European organisation of nationalassociations of electronic and telecommunications manufacturers, recognised by CEC as the manufacturers’ body inEurope.1

TMS, the Task group for Mobile Services reporting to the ECTEL Mobile Radio Specialists Group (MRSG), has almostall European, American and Japanese GSM infrastructure and terminal manufacturers as members, covering more than95% of the market.

The terms of reference of ECTEL TMS include advising on regulations, standards, technical issues, promulgatinginformation, liaison with all parties concerned with GSM/UMTS.

Voluntary Certification Scheme (VCS): The ECTEL TMS policy on the Voluntary Certification Scheme is to startVCS as soon as possible, but with the proviso of a global scheme, recognised and accepted by all operators.,based on SMG7 test specifications, focusing on essential requirements (where the exact meaning of“essential” has to be elaborated). ECTEL TMS proposes a trial year when all vital requirements have beenmet. The idea of VCS labels on the mobile stations is not much liked in ECTEL TMS. So far the proposed VCSorganisation seems quite bureaucratic and will require changes. It is not the intention of the manufacturers tojoin the GSM MoU for VCS in the organisation and to contribute to the budget.Automotive Directive: SMG had been earlier made aware that the application of Directive 95/54/EC could be a seriousthreat to install mobile phones in cars.

More support from GSM MoU, in particular from GSM MoU Terminal Working Group and GSM MoU European InterestGroup, has to be sought in this matter. ETSI, the Association des Constructeurs Européens d’Automobiles (ACEA) andTMS agreed to implement the directive, but asked for better interpretation by the Commission. A next meeting is plannedfor end 1998.

Network Incompatibilities: There are still some GSM networks (even within the European Area) not complying to GSM09.90 and not supporting the signalling related to the Half Rate (HR) codec / Enhanced Full Rate (EFR) codec, so thatcall establishment is even rejected for mobile stations attempting to establish Full Rate (FR) codec calls.

1 The acronym ECTEL is not an abbreviation of “European Telecommunications and Professional Electronics Industry”, it combines names of predecessororganisations.


5 SMG matters

5.1 Liaison statements to SMGA liaison statement from ERC TG1 in Tdoc SMG P-98-629 had been answered by SMG2, see Tdoc SMG P-98-630.

5.2 [deleted Agenda Item]

5.3 [deleted Agenda Item]

5.4 PT SMG status reportThe PT SMG Status Report to SMG#27 in Tdoc SMG P-98-746 was presented by Ansgar Bergmann.

Clarifications at SMG#27: GSM 10.00: It was clarified that GSM 10.00 Draft 0.1 of version 7 had been sent to SMG12,but hadn’t been discussed in SMG12 due to lack of time. It is available on smg/document/smg/specs/draft on the ETSIserver since some time.

SMG#27 decisions:

• The PT SMG Status Report to SMG#27 in Tdoc SMG P-98-746 was approved bySMG#27. (The approved version is annex 7 of this report.)

• The following specifications shall be published by ETSI:

• The creation of an STF for dealing with the SMG related parts for the DRAFTMANDATE TO CEN/CENELEC/ETSI FOR STANDARDIZATION in the field ofRAILWAY EQUIPMENT on the INTEROPERABILITY OF THE TRANS-EUROPEAN HIGH-SPEED RAIL SYSTEM, (see Tdoc SMG P-98-750) and theTerms of Reference in Tdoc SMG P-98-749 were approved by SMG#27.

• SMG#27 approved Stuart Cooke (Nokia) to succeed Makis Kokkos as ITU-R Co-ordinator. SMG#27 thanked Makis Kokkos for his work and achievements.

• SMG#27 approved the ToR for TBR merging and new TBR modules inTdoc SMG P-98-748.

• SMG#27 agreed that a PT SMG Status Report will be distributed in December1998 for agreement by correspondence in SMG.

• SMG#27 approved the updated PT SMG job description in Tdoc SMG P-98-764.

• SMG#27 asked that updates of the PT SMG job description should have revisionmarks in future.

• The file structure on ETSI server below SMG/document/SMG was endorsed bySMG#27.

21.02 High level requirements relevant for the definition of the UMTS Terrestrial Radio AccessUTRA concept

3.0.0

30.04 Definition of the limited number of UTRA concepts 3.0.0

30.00 SMG - UMTS Work programme 3.5.0


5.5 Report Voluntary Funding Task ForcePer Björndahl, STF Voluntary Funding Task Force Chairman, presented the Report on activities between June 1998 andSeptember 1998 in Tdoc SMG P-98-778 (annex 5 of the document is Tdoc SMG P-98-785).

Since SMG#26, The STF SMG Voluntary Funding Task Force has met two times, on September 7th, 1998 in SophiaAntipolis and on October 1st, 1998 in Copenhagen.

Proposed way forward: The STF SMG FTF proposes that

• an MoU for Voluntary Funding (MoU VFS) should be set up.

• That MoU VFS would agree on financial support of STF SMG activities notcovered from other sources.

• The MoU VFS would be open to all parties and ideally all active SMG membersshould participate, however it is anticipated that initially a few larger playerswould be involved and thus take the lead.

Horst Domeier emphasized that all SMG members should be encouraged to participate in the MoU.

The group has elaborated budget estimates for 1999 (included as annex 2 of Tdoc SMG P-98-778) for the support of thefull present scope of SMG (including GSM and UMTS). A draft MoU VFS for Voluntary Funding has been elaborated(included as annex 3 of Tdoc SMG P-98-778) as a starting point for negotiations.

The necessary funding per year could be any sum lower or equal to 3,2 Million Ecu, depending on the budget from ETSIFunded Work Programme, from EC, GSM MoU and others.

A realistic estimation for 1999 would be around 1 Million Ecu, depending on events until the end of the year.

It was clarified that ETSI Secretariat has regularly participated in the group and incorporated their views in the outputs ofthe group.

Armin Toepfer presented Tdoc SMG P-98-773, MoU for Voluntary Funding – Key Issues, MannesmannMobilfunk, expressing support for the voluntary funding scheme and a corresponding reduction of ETSI membership fees,and indicating that the results of 3GPP activities need to be considered when available.

Rémi Thomas expressed the support of the scheme by France Télécom.

Alistair Urie and Peter Adams expressed their view that further proceedings should await results on 3GPP. Asan answer it was clarified that the scheme of voluntary funding was in response to a 2 years old decision of GA on thestep by step reduction of the Funded Work Programme.

It was commented that the nature of future activities would not so well fit into the scope of an SMG group, thatexpertise required in a MoU starter group would be more on legal aspects; also more parties should be involved now.

SMG#27 decisions on the matter:

• SMG#27 acknowledged the results of the group as an excellent basis for futurework.

• SMG#27 noted the next step that interested parties get together and determine theway forward.

• SMG#27 decided that the task force should stay in office in order to follow thefuture development and to become active if necessary.

SMG#27 thanked Per Björndahl and his group for their work.

Note:A starter group of interested parties met on 14th of October, 1998, 14:00 - 14:30.


5.6 Ad hoc Group on Working MethodsThe status report of the ad hoc group on WOrking MEthods (WOME) in Tdoc SMG P-98-563 was presented by theWOME Chairman, Peter Donat. It was approved.

WOME had 3 meetings since SMG#26 (WOME#3, WOME#4 and WOME#5). At WOME#5, an ARIB/TTC delegationparticipated.

5.6.1 Main activities

Main activities of WOME concerned:

Specifications and Version management: The current working assumption is that every release is specified in one majorversion of specifications. In particular, WOME endorsed to issue all outstanding specifications to Version 6 untilSMG#28. The version management of TBRs may still have outstanding problems; also, WOME identified that the versionmanagement in SMG8 is in contradiction to the version management applied in the other STCs. For GSM 10.00, seeSMG#27 decisions in section 5.6.2.

GSM/UMTS 01.00: For changes to GSM/UMTS 01.00, a general aim should be to reduce duplications with ETSI TWP(task for PT SMG); also, when finding general agreements in WOME, GSM/UMTS 01.00 should be examined to identifythe necessary changes to be elaborated by PT SMG.

Electronic handling of documents:

• Automatic download: WOME discussed a problem of the compcopy sub-directories which were automatically created by ETSI secretariat: Havingrestricted access, they stopped automatic downloading of directories whenentered. WOME suggested removal of the directories, which was accepted byETSI secretariat.

• Access to e-mail reflectors for non ETSI members: WOME sees the responsibilitywith the owner of the list, typically the chairman or secretary of the correspondinggroup.

Discussion in SMG#27: Kevin Holley reported on the SMG4 principles for accessto e-mail groups: Access is granted if the company has participation rights, or isgoing to have participation rights, or if the person is intending to contribute to thework.

Electronic Tools:

• Compatibility problems between Word versions: SMG#26 had asked WOMEto study the problem of versions of electronic tools like word processors and toreport back to SMG#27.

In particular, PT SMG had had to discover that documents when converted fromWord 97 to Word 7, may loose text and revisions of figures. As a consequence, aCR had lost essential parts when converted from Word 97 to Word 7.

The ETSI policy doesn’t help here, it is to accept Word 6, Word 7, Word forOffice 97.

Discussion in SMG#27: It was commented by Robert Tompkins that ITU acceptdocuments in WORD for Office 97, but discourage the use of WORD for Office97 for contributions, because of the problems with compatibility already known toSMG,

Decision of SMG#27: see section 5.6.2.


• Other tools: The discussion on other tools like Access was postponed to WOME#6. A potential problem of Access 2 with the year 2000 had been reported inWOME. It was suggested that WOME should try to create a roadmap for changeof software tools.

Work item management: See SMG#27 decisions in section 5.6.2.

Rules for document numbering: See SMG#27 decisions in section 5.6.2.

Storage of meeting reports: Rules where to find a meeting report: WOME is studying some ways for a logical locationof meeting reports.

File structure on the FTP server: WOME discussed a proposal from PT SMG, and endorsed it; see the PT SMG statusreport to SMG#27 in Annex 7.

Document Structure of GSM and UMTS Release 99 Specifications: SMG1 had asked WOME to look into proposalsfor a Release 99 specification structure (for GSM and UMTS). WOME studied the requirements, in particular it agreed asa working assumption that the set of specifications for UMTS together with all referenced documents shall be self-contained for an educated reader, and that the referenced documents shall be publicly available. WOME concluded that acentral problem is the maintenance, improvement and correction of the common kernel where the same changes have to beadopted for GSM and UMTS. For the Japanese side when there is a common Core Network protocol for UMTS andGSM, modifications of the common kernel must be in the responsibility of 3GPP. Further considerations are necessary.For stage 3 specifications in particular, i.e. the actual protocols, it is very important to have only one specification for oneprotocol.

An initial examination of Methods A, B, B’ and C were made:

• Method A: The specification structure is based on the GSM structure and theUMTS functionality is included into the GSM specifications. The result will becommon GSM/UMTS specifications. The default is that everything is valid forboth GSM and UMTS. GSM specific parts are marked and UMTS specific partsare marked, respectively.

• Method B: A new, separate specification series for UMTS is used which includesreferences to appropriate GSM specifications.

• Method B’: A new, separate specification series for UMTS is used. The GSM setof specifications includes references to appropriate UMTS specifications.

• Method C: A new, separate specification series for UMTS is used but instead ofreferences to GSM specifications the appropriate parts of GSM specifying text arecopied into those UMTS specification(s).

WOME did not conclude on one of the methods (or a mixture of some of them). WOME reported to SMG#27 that it wouldbe ready to continue the investigation if SMG so wishes.

Note: As a side event during SMG#27, a discussion between SMG, T1P1 andARIB/TTC delegates tool place on the UMTS specification structure, see thereport in Tdoc SMG P-98-783 which was made available at SMG#27.

Roadmap: It was asked whether the GSM Phase 2+ Roadmap should be extended to include the UMTS Work Items orwhether there should be a stand-alone UMTS roadmap.

WOME conclusion: WOME advised PT SMG to process the information in such a way that both - separate and integrated- roadmaps can be produced.

Logical e-mail addresses: PT SMG was encouraged to create additional logical e-mail addresses (for example:“[email protected]”) to indicate the PT SMG expert responsible for a certain group.

UMTS terminology: SMG1, SMG2 and SMG12 are elaborating definitions for UMTS. Compatibility between GSM andUMTS terminology and acronyms should be an issue for WOME, but was postponed.


Access to ETSI server: It was reported that access to the ETSI server is often restricted to the SMG directory. It wasclarified that the GA had decided that every ETSI member should be able to get read-access to all non-restricted areas,e.g. the Board documents. In such a case, the help desk should be contacted.

Access rights for writing and deleting: WOME recommends that write/delete access should normally be limitedto the chairmen of the groups and PT SMG.

Proper Releases: The problem of Release x+1, …, x+n descriptions in Release x specifications was discussed. WOMEsees it as a work for the rapporteurs and PT SMG to remove such descriptions by CRs, however for big specifications,resources may not be available.

Terms of reference for WG WOME: WOME prepared Terms of Reference, see SMG#27 decision below.

Comments to 3GPP Working Procedures: SMG AG had asked WOME to comment on the draft 3GPP workingprocedures. This was done in WOME#5 and the results were presented to SMG-CG and SMG#27, see SMG#27 decisionbelow.2

Members database: For technical reasons, it was not possible to run a demonstration up to now. The matter should bedecided at one of the next WOME meeting.

Change requests to 01.00:

A first walk through the relevant paper showed that it seems to be easier to rewrite some parts in order to come to a morecomprehensive description. So a new draft version of 01.00 is expected for SMG#28.

5.6.2 Decisions of SMG#27

SMG#27 approved the Terms of Reference for WOME in Annex A of Tdoc SMG P-98-563 with the modification todelete “ad hoc” in the name of the group.

SMG#27 approved the following proposals from WOME:

• GSM 10.00 should be issued in the major version of the current Release (thismeans, e.g., to use versions 7.x.y for GSM 10.00 until a completion of Release 98).

• The reference version for Word should be version 6 until a new decision has beenmade. This means that in case of discrepancies, the Word 6 version is thedefinitive one.

• For every work item XXX, either the prime responsible STC generates explicitphases (like ASCI phase 1, ASCI phase 2), preferably with a new Work ItemDescription sheet; if not, enhancements of a completed work item belong to an(automatically created) Work item XXX-98 etc. (98 meaning Release 98).

• The rules for document numbering proposed by WOME were endorsed bySMG#27:

<Tdoc number> ::= <group> <year> <Tdoc identifier><group> ::= <main group> {<subgroup> | <plenary>}<main group> = P | 1 | 2 | … | 9 | A | B | C | W

(standing for SMG Plenary, SMG1, …, SMG11, SMG12, WOME)<subgroup> = <letter-or-digit> | -<plenary> ::= -<year> ::= <digit> <digit><Tdoc identifier> = <hyphen-or-digit-above-0> < digit> < digit> < digit>

(the “-” stands for 0 and is used for better readability)<hyphen-or-digit-above-0> ::= - | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9<digit> ::= 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9

2 A mistake in the WOME status report to SMG#27 was corrected during presentation at SMG#27: It was clarified that SMG AG had asked WOME topresent the comments on the 3GPP Working Procedures to SMG#27, not to 3GPP, and that had been done (Tdoc SMG P-98-565).


For SMG, the following subgroups exist:Advisory group: letter “A”Co-ordination group: letter “C”

The abbreviation for a subgroup of an STC subgroup is to be decided by the STC, and to bedocumented by PT SMG.

Examples:

◊ P-98-900 is SMG Plenary Tdoc no. 900 of year 1998.◊ P-981601 is SMG Plenary Tdoc no. 1601 of year 1998.◊ 2B99-001 is Tdoc 1 of SMG2 WPB in the year 1999.

• SMG#27 approved the comments on the 3GPP Working Procedures inTdoc SMG P-98-565 to be sent to 3GPP.

5.7 Report on globalisationFrançois Grassot, member of UGG, presented Tdoc SMG P-98-577, Extraordinary GA decisions on EPP scope, source:UGG Chairman (same as Tdoc 11 from the Extraordinary ETSI General Assembly, 29 September 1998).

François Grassot presented also Tdoc SMG P-98-574, title: During the meeting held in Tokyo, 7-9 October 1998 ARIB,ETSI, T1, TTA and TTC agreed this framework document, source: ETSI Director General/UGG Chairman, inTdoc SMG P-98-574, which is Annex 9 of this meeting report.

Discussion and clarifications in SMG#27:

• “One Individual company Member, one vote” (slide 44): It was explained thatweighted votes don’t exist in other SDOs. It was explained that the 3GPPagreement was to review this point on its fairness after 6 months.3

• “ETSI will absorb the initial cost of establishing the 3GPP, if required.Thereafter, the costs will be shared by the Organizational Partners. There will beno direct 3GPP membership fee for Individual Members.” (slide 28): It wasexplained that this is a commitment from ETSI, accepted by ETSI Board.

• How are the PCG delegates elected, which power do they have? How can theyrepresent the members? Answer: The PCG has a management role. There couldbe one representative per partner, e.g., the Director (General) of each partner.Andrew Watson quoted experiences from UMTS Forum which had originallybeen set up in a similar way but then had to change the structure because thesteering group had been felt undemocratic.

• If the members want influence on management issues, would they have to gothrough GA and Board? Answer: Yes, or other available means like through TSGchairs and vice chairs after the 3GPP has been set up.

• The proposals are presented to GA in November 1998, whereas the fulldocumentation is planned for December.

• Duplication of work: The necessary means to avoid it (i.e. share of work) willhave to be defined.

• The view was expressed that SMG and its sub-groups should continue business asusual until further notice.

3 Note: Gunnar Sandegren stated that Ericsson considers subject to other companies applying the same principle, throughETSI, to only apply for one membership (i.e., have one vote); possibly it will go to further memberships throughother partner organizations.


• A common technical group is not foreseen in the 3GPP structure. The TSGs willorganise and co-ordinate their work.

• Concern was expressed by Tony Wiener (ONE-2-ONE) and David Barnes (DTI)that there was no Plenary body of the TSGs to provide an overall technical co-ordination and an overall review of the output produced by the TSGs. They gavereasons why it was necessary to have a Plenary of TSGs and the view wassupported by other delegates. Delegates were informed that they should raise thismatter with their ETSI Board members.

• The practical arrangements concerning the first meetings in 3GPP have not yetbeen discussed by UGG.

• Is the number of TSG and their scope fixed? E.g., could there be a separate TSGon UMTS smart cards? Answer: The number and scope of TSG can be changed bythe Organisational Partners meeting.

• ETSI Board decided on 13 October the creation of a starter group for EP UMTS.

• If a company (e.g., a small operator) wants to fully participate in the work, itmight be obliged to send delegates to each TSG.

• The view was expressed that at the next GA, a decision on acceptance orrejection of the 3GPP concept would have to be made; modifications would notbe possible during the GA.

• It was explained that it is foreseen that regional requirements will be included inthe 3GPP work.

• It was explained that the work areas listed in Tdoc SMG P-98-574 can be changedby PCG.

6 GSM matters

6.1 SMG1Alan Cox, SMG1 Chairman, presented the GSM relevant parts of the SMG1 status report to SMG#27 inTdoc SMG P-98-547. The SMG1 status report was approved by SMG#27.

6.1.1 General

Since SMG#26, SMG1 has held two plenary meetings, one covering both GSM and UMTS matters, the second onefocusing on UMTS Phase 1 specifications, as well as a number of ad-hoc meetings.

The SMG1 work on GSM features is more and more included in the work on the corresponding UMTS features.

6.1.2 Change requests

All GSM-relevant CRs presented by SMG1 to SMG#27 were approved by SMG#27. They concern

• Support of Local Service Area (SoLSA) in Tdoc SMG P-98-548 concerning CRGSM 02.07-A019 and CR GSM 02.11-A011

• Call progress indications in Tdoc SMG P-98-549 concerning CR GSM 02.40-A002 relating to Harmonization between GSM 02.40 version 5.0.0 and J-STD-007Volume 7


• Call deflection in Tdoc SMG P-98-550 concerning CR GSM 02.72-A001 relatingto CD’s interaction with other supplementary services .

6.1.3 New specifications

• GSM 02.43, Support of Localised Service Area (SoLSA); Service description;Stage 1, V2.0.0 in Tdoc SMG P-98-557 was approved by SMG#27 as aRelease 98 specification.

• GSM 02.56, GSM Cordless Telephony System (CTS), Phase 1; Servicedescription; Stage 1, v2.0.0 in Tdoc SMG P-98-680 was approved by SMG#27 asa Release 98 specification.

6.1.4 Work items/areas

General Packet Radio Services Phase 2: Tdoc SMG P-98-556 proposes a break-down of GPRS Phase 2 into 11 workitems, prepared by SMG1 together with other STCs. Some are proposed for Release 98, others Release 99.

Harald Dettner and François Courau commented that SMG3 is still working on GPRS Phase 1, so that for SMG#28 tofinalise GPRS Phase 2 Work Items is not realistic.

Decision of SMG#27: SMG#27 approved the work items in Tdoc SMG P-98-556 and asked the engaged STCs, inparticular SMG3, SMG4, SMG6 and SMG12 to comment on the completion dates and on other parts of the Work ItemDescription sheets, taking into account comments from GSM MoU (in particular CAGE 2+) on charging/billing issues.

GSM - Cordless Telephony System (CTS): See section 6.1.3 for approval of stage 1. At SMG#27, some delegatesasked whether the CTS Work Item had still sufficient support in SMG to justify the Work Item to be kept alive, afterseveral CTS rapporteurs had resigned. It was confirmed that replacements had been found, and that the Work Item cancontinue.

Location services (under T1P1 leadership): A joint T1P1 and SMG1, SMG2, SMG3, SMG10, SMG12 meeting will takeplace in Sophia Antipolis from 26-29 October in order to progress LCS Stage 1. See section 6.5 for further details onlocation services.

Multiple Service Profile (MSP): Although the stage 1 has been stable for some time, there has been little progress inSMG3 recently, so a new approach is being examined in SMG1.

Impact of Telecommunications Data Protection Directive on GSM Standards: This work item, proposed in annex 2 ofTdoc SMG P-98-417, means to identify and study possible impacts of the Telecomms Data Protection Directive(97/66/EC) on GSM Standards. SMG#26 had approved this work item in principle and had asked SMG1 to study itfurther with the aim to approve necessary changes to the GSM standards at SMG#27. Work item rapporteur is BarbaraReed, BT.

SMG1 concluded

• that the GSM specifications are in line with that directive;

• that therefore, at present, no additional GSM standardisation work is needed tosupport the directive;

• that the work item is not closed as SMG1 are aware of activities in the fixednetwork (Barbara Reed is also rapporteur in NA2) and will watch developments.

SMG1 identified in Tdoc SMG P-98-560 the following points from the Directive as relevant for GSM:

• Article 8 - Presentation and restriction of calling and connected line: In particular,the requirement (in item 3 of article 8) for rejection of calls by the called partywhere the Calling Line Identification (CLI) has been restricted (i.e. withheld) bythe caller is fulfilled in GSM, since the radio interface signalling supports this,permitting mobile stations to be designed to support the feature.


• • Article 10 - Automatic call forwarding: Article 10 can be fulfilled by the calleduser observing the forwarded indicator and rejecting the call. The following shouldhowever be noted: Not all handsets support forwarded call indication - so a usermay have to buy a new handset should they wish to have this facility or if theywant the feature to be automatic.

See also section 6.1.5 for a liaison statement from SMG1 to ECTEL TMS on the issue.

Comments at SMG#27: Mikko Kanerva, Nokia, commented that network based solutions would significantly reduce ortotally remove the signalling load from the radio interface, and would even work with old handsets.

Decision of SMG#27: The work item is approved as pending in order to allow SMG1 to watch developments. The WorkItem Description in Tdoc SMG P-98-417 shall be sent to SMG12 for revision and approval.

SIM application toolkit: SMG1 is preparing a stage 1 description to be presented to SMG#28 for information.

Support of Localized Service Area (SoLSA): See section 6.1.3 for approval of stage 1.

Work items for deletion: On proposal from SMG1, SMG#27 approved deletion of the following work items:

• Forwarding of SMSs (it was commented at SMG#27 that the servicerequirements remain but there is no plan to carry on the current Work Item.)

• Network Alerting (SMS) - an outstanding sub-feature of work item NetworkIndication of Alerting in the MS for which core specifications had beencompleted in SMG#25.

• Completion of Call when No Reply (CCNRy), Completion of Call whenSubscriber Not Reachable (CCNRc) (see also Tdoc SMG P-98-561).

6.1.5 Liaison statements

A liaison statement on Impact of Telecomms Data Protection Directive on GSM Standards from SMG1 to ECTEL-TMSin Tdoc SMG P-98-560 was noted by SMG#27. See section 6.1.4 for further information on the work item.

6.2 SMG2The GSM relevant parts of the SMG2 status report to SMG#27 in Tdoc SMG P-98-706 were presented by the SMG2Chairman, Niels Peter Skov Andersen. The SMG2 status report was approved by SMG#27.

6.2.1 General

Since SMG#26, SMG2 held one plenary and several working party and ad hoc meetings.

François Courau resigned as Chairman of SMG2 WPA and as Vice Chairman of SMG2. As interim SMG2 WPAChairman, SMG2 appointed Andrew Howell (Motorola) until a decision at SMG2 when consequences from restructuringare clearer.

Rémi Thomas emphasised the view of France Télécom that this group should continue.


With the exception of CR05.02-A043r2 in Tdoc SMG P-98-709 (see further below), all Change Requests inTdoc SMG P-98-662, Tdoc SMG P-98-663, Tdoc SMG P-98-709, Tdoc SMG P-98-710, Tdoc SMG P-98-711 andTdoc SMG P-98-712 were approved by SMG#27, including one Phase 2 Change request, CR 05.08-A078 rev 2 inTdoc SMG P-98-711, clarifying how the Mobile Station determines the complete BA(SACCH).

The corresponding CRs in Tdoc SMG P-98-711 (see table below) should be categorised as category F:


05.08-A074 R97 Clarification of Complete BA(SACCH) F05.08-A073 R96 Clarification of Complete BA(SACCH) F05.02-A078 Ph2 Clarification of Complete BA(SACCH) F

Concerning Tdoc SMG P-98-709, CR05.02-A043r2 (Release 97) on MS multislot classes and GPRS dynamicallocations, it was asked at SMG#27 whether this also relates to HSCSD, where however the requirement should alreadybe a consequence of the current specification.

The CR was analysed during SMG#27 by Niels Peter Skov Andersen and Mikko Kanerva: They identified that the CRwas necessary for Type 1 mobiles and elaborated a revision of the CR, CR05.02-A043r3 in Tdoc SMG P-98-639, whichwas approved by SMG#27. (SMG2 might want to further examine aspects of HSCSD and Type 2 mobiles.)


GSM 03.52, Lower layers of the GSM Cordless Telephony System (CTS) radio interface - Stage 2: SMG2 has put thisspecification in its version 0.1.1 under STC change control.

It was clarified that SMG2 is not intending to merge this specification with other specifications now nor in the future.

GSM 10.59 v. 1.3.0, Project scheduling and open issues for EDGE: This specification in Tdoc SMG P-98-707 waspresented to SMG#27 for information.

6.2.4 Work items, feasibility studies and other work areas

Adaptive Multi Rate (AMR): SMG2 members produced an AMR radio simulator that was used for the generation ofstatic and dynamic error patterns for the selection phase of AMR work. In this period SMG2 have communicated withSMG11 on several aspects of the AMR. Following the approval of one candidate as the selected Adaptive Multi Ratecodec standard by SMG#27 (see section 6.11.8), SMG2 will initiate the necessary work to include support for AMR inthe standard. Considering the experience from the introduction of HR and EFR in the standard, SMG2 does not believe itpossible to finalise the work in within Release 98.

Enhanced Data rates for GSM Evolution (EDGE) - BSS Part: The definition for the frame work for EDGE hasprogressed. For GSM 10.59, see section 6.2.3.

Feasibility study for GSM450: At SMG#26 (Helsinki, 22-26 June 1998), a proposal had been made to study thepossibility of deploying GSM within frequency bands currently used for NMT450 cellular networks. SMG#26had asked SMG2 for a feasibility study. After SMG#26 a liaison statement had been sent from SMG to ERM onthe possibility of deployment of GSM systems in frequency bands currently allocated to other cellularsystems. SMG2 WPB had been informed about the existence of NMT450 Digital Requirements specification.SMG2 presented the draft feasibility study to SMG2#27 for information and will continue work on the feasibility study.

SMG2 identified key areas that need further study (impact of 450 MHz frequency allocations in different countries; rangerequirements; minimum spectrum requirement to operate GSM on 450 MHz band - the interim requirements proposalindicates 2.4 MHz spectrum availability for GSM technology).

General Packet Radio Service Phase 1 (GPRS) - radio part: After the Change Requests approved by SMG#27, anumber of corrections and alignments of the GPRS standard will still be necessary. In particular, a review of BCCH andcorrections on RLC/MAC are envisaged.

GSM - Cordless Telephony System (CTS): SMG2 have progressed the work item. The radio functionality requirementsof a GSM CTS have been analysed and the future work has been structured based on this analysis. SMG2 agreed upon thebasic working assumption for the CTS radio aspects. GSM 03.52 has been put under change control within SMG2 (cf.section 6.2.3).

MS Antenna Test Method: SMG2 have received a few contributions on the subject of mobile station antennaperformance and methods of measurements.

Support of Localized Service Area (SoLSA): The work on SoLSA has been started. Proposals for detailedimplementation have been received and are being studied in detail. For SoLSA once again the BCCH capacity seems tobe a critical item, which needs to be studied carefully.



A Liaison Statement on Proposed feasibility study for GSM 450 from SMG2 to SMG in Tdoc SMG P-98-713 was notedby SMG, see section 6.2.4 for further information.

Tdoc SMG P-98-683, a draft Co-operation agreement with Universal Wireless Communications Consortium's GlobalTDMA Forum (GTF) for EDGE prepared by the ETSI Secretariat, was endorsed by SMG#27.

6.3 SMG3The GSM relevant parts of the SMG3 status report to SMG#27 in Tdoc SMG P-98-717 were presented by the SMG3Chairman, Harald Dettner (the presentation slides are in Tdoc SMG P-98-585). The SMG3 status report was approved bySMG#27.

Missing hosts: The hosting situation is critical. SMG3 is lacking hosts for a lot of meetings. If no parties are willing tohost SMG3 meetings then it can be foreseen that stage 3 material for Release 99 will not be available in due time.

For the following meetings, SMG3 urgently needs hosts:

27 to 29 January 1999 SMG3 plenary #1/99; NO HOST YET

week 23 1999 SMG3 plenary #2/99; NO HOST YET


25 to 26 January 1999 SMG3-WPA; Just before SMG3 plenary #1/99 NO HOST YET

25 to 26 January 1999 SMG3-WPB #1/99: Just before SMG3 plenary #1/99 NO HOST YET

17 to 21 May 1999 SMG3-WPB #2/99: NO HOST YET

11 to 15 January 1999 SMG3-WPC; NO HOST YET

13 and 14 January 1999 Joint SPS3/SMG3-WPC on CAMEL Phase 3 during SMG3-WPC

25 to 26 January 1999 SMG3-WPC; Just before SMG3 plenary #1/99 NO HOST YET

13 to 17 September 1999 SMG3-WPC; NO HOST YET

15 and 16 September 1999 Joint SPS3/SMG3-WPC on CAMEL Phase 3 during SMG3-WPC

15 to 19 November 1999 SMG3-WPC; NO HOST YET.

Companies willing to host a meeting should contact Peter van der Arend (e-mail: [email protected], fax: + 33 493 65 28 17).

6.3.1 General

Between SMG#26 and SMG#27, SMG3 had one plenary and several working party / ad-hoc meetings.

Vice Chairs will be elected at next SMG3 plenary in January 1999. In the mean time, the WP chairmen act as vicechairmen.


All change requests presented by SMG3 to SMG#27 were approved by SMG#27 with the following exceptions:


• CR 04.08-A355, a Phase 2 CR with Category F on Clarification of CM3 and ESIND bit handling in classmark 1 and 2 in Tdoc SMG P-98-715: This CR had beenagreed in SMG3; corresponding CRs for Release 96 and Release 97 had alreadybeen approved by SMG#26. However, SMG2 had rejected the CR as being notnecessary.

On CR 04.08-A355, SMG2/3 should check whether the changes introduced by thecorresponding CRs for Release 96 and Release 97 are to be improved.

• CR 03.78-A037r1, a Release 97 Category C Change Request on Removal ofO_Not_Reachable and T_Not_Reachable detection points inTdoc SMG P-98-724: SMG#27 discussed whether the deletion of the detectionpoints on “not reachable” in this CR could lead to unwanted service restrictions.

The CR was further examined during SMG#27. Result: Tdoc SMG P-98-627 waspresented by Harald Dettner. It proposes acceptance of the CR, because ITU-Thad not accepted the new detection points for not Reachable so far.

Then, a further discussion in SMG#27 took place.

One view was that in a world of fixed-mobile convergence, it wouldn’t beunderstandable that specification of a detection point which is the consequence ofmobility is rejected; if ‘not reachable’ had to be merged with another detectionpoint, the latter one should be ‘no reply’ instead of ‘busy’.

Another opinion, expressed by several speakers, was that under the signs of fixed-mobile convergence, ITU-T might change their mind.

SMG#27 asked SMG3 to study the CR again with regard of the concerns raised.

CR 03.78-A037r1 was postponed at SMG#27.

• On CR 04.08-A365, the following revision was approved by SMG#27: Allrevisions except the revision of Annex K4 were approved by SMG#27. Therevision of Annex K4 was not approved, as annex K is only an informative annexdocumenting default IEIs specified before the new coding principle to make IEIscontext sensitive (i.e., the meaning of an IEI depends on the message in which itoccurs). A modified CR 04.08-A365 rev. 1 was made available inTdoc SMG P-98-588.

• A CR to GSM 04.08 in Tdoc SMG P-98-698 on re-numbering of tables andsections, CR 04.08-A357r1, has been postponed to be further discussed in SMG2and SMG3.

Accepted CRs include:

• Release 96 CRs on Voice Broadcast Service (VBS) in Tdoc SMG P-98-678

• Release 96 CRs on Voice Broadcast Service (VGCS) in Tdoc SMG P-98-679

• Release 96 CRs on CAMEL Phase 1 in Tdoc SMG P-98-723

• • Remaining Release 97 CRs on CAMEL Phase 2 in Tdoc SMG P-98-724 exceptCR 03.78-A037r1 (Release 97-C) on Removal of O_Not_Reachable andT_Not_Reachable detection points

• on CAMEL Phase 2/CCBS, the CR in Tdoc SMG P-98-722


• on CCBS, CRs in Tdoc SMG P-98-720 and Tdoc SMG P-98-721, except CR04.08-A365 in Tdoc SMG P-98-716, where SMG#27 approved a revision inTdoc SMG P-98-588.

• on GPRS, CRs in Tdoc SMG P-98-677, Tdoc SMG P-98-725,

• on Support for Optimal Routing (SOR): CRs in Tdoc SMG P-98-768

• CRs 04.08-A359 and 04.08-367 on re-numbering of tables and figures inTdoc SMG P-98-698 (whereas CR 04.08-A357r1 has been postponed at SMG#27,see above)

• Release 96 and Release 97 CRs on TEI in Tdoc SMG P-98-726 (GSM 03.18 andGSM 09.02).


GSM 04.72, Call Deflection (CD) Supplementary Service; Stage 3, V1.0.0 (Release 98), in Tdoc SMG P-98-718, waspresented for information to SMG#27.

GSM 09.13, Signalling interworking between ISDN supplementary services Application Service Element (ASE) andMobile Application Part (MAP) protocols, version 2.0.0 in Tdoc SMG P-98-719 was approved by SMG#27 forRelease 97.


Calling Name Presentation - US (CNAP-US), Calling Name Presentation - Euro (CNAP-EU): The specifications forCalling Name Presentation - US (CNAP-US) are available now and will be published:

Stage 1 (02.96) is neutral to the implementation, but for Calling Name Presentation - Euro (CNAP-EU), a separatearchitecture has to be chosen. Problems are identified with the proposal to make use of UUS. Other alternatives are understudy.

CAMEL Phase 2: Tdoc SMG P-98-579, EDP-R for Abandon detection point in CAMEL phase 2, source FranceTélécom, explains that the CAMEL phase 2 stage 1 description requires the Abandon Detection Point as a EDP-R4, andthat such a functionality is not provided in the stage 2; it proposes not to change stage 2.

In this matter, later during SMG#27, P-98-607, with the same title EDP-R for Abandon detection point in CAMEL phase2, source France Télécom and Nokia, was presented by Rémi Thomas. This document proposes, that either GSM 02.78requirement for charging operations in abandon DP is moved to CAMEL phase 3, or SMG3 WPC is allowed to ignore therequirement for CAMEL phase 2. An attached draft CR shows the change needed in GSM 02.78 if SMG1 is to remove therequirement from CAMEL phase 2.

Decisions of SMG#27: SMG#27 approved not to modify GSM 03.78 for CAMEL phase 2 to include the EDP-R AbandonDP. SMG#27 further approved that SMG1 should move the GSM 02.78 requirement for charging operations in abandonDP into CAMEL phase 3.

CAMEL Phase 3: Co-operation with SPS3 has started on the common development of the CAMEL Phase 3 standard. SeeAnnex A in Tdoc SMG P-98-717 Annex F of GSM 10.78.

The danger was pointed at in SMG#27, to loose important functions if detection points are removed for the sake offixed/mobile convergence just because it doesn’t exist for fixed networks.

4 EDP-R = Event Detection Point - Request: A detection point which is leads to a notification of the gsmSCF; the gsmSSF then waits for instructions from thegsmSCF. See GSM 03.78.

GSM_NO GSM_TITLE CURRENTVERSION

PHASE

02.96 Name Identification Supplementary Services; Stage 1 6.0.0 R97




Immediate Service Termination (IST): The development of a non CAMEL implementation solution for IST wasrequested by SMG10. SMG3 reported to SMG#27

• that guidance on this work is needed;

• that the non CAMEL approach for the service might be very time consuming forSMG3-WPC;

• that there was no support in SMG3 for the development of a non CAMEL basedsolution for IST.

During SMG#27, a small group looked into the issue. The SMG3 and SMG10 chairman agreed to raise the issue in theSTCs again to attract the proponents to actively work on this subject.

SMG#27 was informed that Alcatel had committed to contribute to the non CAMEL solution for IST.

SMG#27 decision: non-CAMEL based IST is postponed to Release 99.


Co-operation with SPS: A Liaison Statement from SPS3 on SMG3 - SPS3 co-operation for the production of commonCAMEL Phase 3 specifications was presented to SMG#27 in annex A of P-98-717.

Note: In annex A of P-98-717 the dates of that LS have been updated.

Decision of SMG#27: Annex F of GSM 10.78 shown on the last page of P-98-717 was approved by SMG#27.

6.3.6 Other issues

Sub-System Numbers: After rejection of allocation of SSN for GSM by ITU, SMG3 prepared CRs to GSM 03.03 whichwill be sent to SMG12 (the prime responsible STC for GSM 03.03). See also section 6.12.5.

6.4 SMG4The GSM relevant parts of the SMG4 status report to SMG#27 in Tdoc SMG P-98-775 were presented by the SMG4Chairman, Kevin Holley (the presentation slides are in Tdoc SMG P-98-566). The SMG4 status report was approved bySMG#27.

Missing hosts: SMG4 is missing hosts for the following plenary meetings:

• 1st-5th March 1999,

• 20th-24th September 1999.The last SMG4 meeting was attended by 70 delegates. During the opening and closing plenary, usually about 50 delegatesare present. In between up to four subgroups are running in parallel with 10 to 35 delegates.

Companies willing to host a meeting should contact Friedhelm Rodermund (e-mail: [email protected], fax: +

33 4 93 65 28 17).6.4.1General

Since SMG#26, SMG4 has held one plenary meeting and several sub-group/ad hoc meetings as well as joint meetingswith SMG1 and SMG12.


All CRs in Tdoc SMG P-98-735, Tdoc SMG P-98-736, Tdoc SMG P-98-737, Tdoc SMG P-98-738 andTdoc SMG P-98-739 were approved by SMG#27. Amongst them, there are two phase 2 CRs:

• CR 07.07-A061, Corrections to +CR and +CREG commands inTdoc SMG P-98-737


• CR-09.07-A042 on V.24 signalling in Tdoc SMG P-98-739.On CR 03.40-A83 in Tdoc SMG P-98-738, possible compatibility problems with Release 98 Mobile Stations innetworks of Release 97 or earlier were indicated.

Change requests in Tdoc SMG P-98-739 correct compatibility problems between various implementations of V.24signalling in the Mobile Station, Inter-Working Function and fixed network V.110 ISDN Terminal Adapter that may causepremature release of calls. A complete solution has been elaborated for Release 98, some corrections are also made tothe Phase 2, Release 96 and Release 97 specifications.


GSM 03.57, Mobile Station Application Execution Environment (MExE); Functional description; Stage 2, Version1.0.2 (R98), in Tdoc SMG P-98-776 was presented to SMG#27 for information.


Phase 2:

• AT commands: For a correction to GSM 07.07 regarding the +CR and +CREGcommands, see section 6.4.2 (there is a corresponding minor error in the +MRcommand in ITU-T V.250).

• V.24: See section 6.4.2 (CRs in Tdoc SMG P-98-739).New work items:

Provision of text telephony service in GSM and UMTS: This work item, proposed in section 13.5 of the SMG4 statusreport (Tdoc SMG P-98-775) led to some discussion in SMG#27:

Comments of the work item:

• Additional supporting companies (e.g., regulators) are needed. SMG#27 wasinformed that the Swedish regulator as well as Alcatel support the WI.

• Steven Hayes commented that there might come a mandate from FCC.

• SMG#27 was informed that in Denmark, the feature has been implementedwithout impact on GSM standards.

Decision of SMG#27: The work item was approved. It should be further studied by SMG12, which will be the primeresponsible STC at least in the initial phase.


A Liaison Statement on maintenance of ETSI GSM specifications in section 14 of the SMG4 status report was forwardedby SMG#27 to WOME.

6.5 T1P1 work items

GPRS for PCS 1900: Ed Ehrlich presented Tdoc SMG P-98-583, containing a new work item GPRS for PCS 1900,under leadership of T1P1. It was approved.

Comments:

• T1P1 should also consider performance evaluations etc. for GPRS radio.

• The text in section 1.4 seems not to raise new service requirements.Harmonization of the PCS1900 Standards with the GSM Base Specification: Ed Ehrlich presentedTdoc SMG P-98-582, Harmonisation CRs for Release 98, source Asok Chatterjee, Chairman, T1P1, expressing the needfor feasible arrangements to obtain common standards soon.


Location Services (LCS): Tdoc SMG P-98-727, Standardisation of Commercial Location Based Services, source:Cellnet, Motorola, Nokia, Nortel, Omnitel Pronto Italia and Tdoc SMG P-98-728, Background Information aboutLocation Services Standardization, source: Nokia, were presented by Teuvo Järvelä. The documents propose E-OTDand GPS as the solution for the commercial services, and TOA as the solution for the FCC requirement. Both areproposed to be specified in parallel, for R98.

Clarifications and further information:

• Ed Ehrlich explained that stage 1 and stage 2 are developed so that they areapplicable to any of the three methods.

• A joint meeting between SMG STCs and T1P1 on localisation is planned for 26-29October, 1998 in Sophia Antipolis.

Views on the matter:

• Linda Melvin, Director of GSM MoU North American Interest Group, expressedthe need of all GSM North America operators for an in time solution (inRelease 98) based on TOA.

• One main reason for proposing TOA is that it works with existing mobile stations.

• Views supporting the E-OTD or GPS or TOA solutions were expressed by somedelegates.

Conclusion of SMG#27:

• SMG recognised the first priority for an in-time solution based on TOA withoutdelay (mainly for regulatory requirements on emergency calls).

• SMG recognises the need for other solutions (mainly for commercial servicesusing localisation).

• The lead for localisation including all methods should be with T1P1.

• It was noted that T1P1 intends to take measures to speed up the work on theadditional methods.

6.6 SMG6The GSM relevant parts of the SMG6 status report to SMG#27 in Tdoc SMG P-98-664 were presented by the SMG6Chairperson, Gisela Hertel. The SMG6 status report was approved by SMG#27.

6.6.1 General; confirmation of Chair

Between SMG#26 and SMG#27, SMG6 had one plenary and several working party/ad-hoc meetings.

SMG#27 was informed that Gisela Hertel has changed affiliation. She now represents Iridium. She was confirmed asSMG6 Chairperson.


All CRs presented by SMG6 to SMG#27 for approval were approved by SMG#27:

Tdoc SMG P-98-667 - CRs to GSM 12.05:

• a CR to GSM 12.05 proposing an enhancement of HSCSD parameters in callrecords;

• a CR to GSM 12.05 proposing the addition of speech codec related information.Tdoc SMG P-98-665 - CR to GSM 12.11: a CR to GSM 12.11 containing several clarifications.


Tdoc SMG P-98-666 - CRs to GSM 12.15

• a CR to GSM 12.15 that contains several clarification and editorial improvements.

• CR 12.15-A001r10 is a CR to GSM 12.15 proposing the addition of a chargingprotocol. Earlier versions of this CR have been discussed at SMG6 GPRS meetingfor some time, and the status of the CR had been questioned in SMG6; MichaelSanders confirmed that the version presented to SMG#27 was the one approved inSMG6. After longer discussions in SMG#27, the CR was approved.


No new specification was presented to SMG#27.

6.6.4 Work items

General Packet Radio Service (GPRS): SMG6 established the following work plan:

GPRS charging:

• High Priority∗ Completion of charging protocols∗ Prepaid service (study + specification if time allows)∗ Reverse charging∗ Study of itemised billing∗ Enhancements to 12.15

• Medium Priority∗ Hot billing∗ Study of enhancements to charging criteria∗ PTM-M (depends on service description)

• Low Priority & On Hold∗ PTM-G (depends on service description)∗ AoC (depends on service description)

GPRS O&M:

• High Priority∗ Clarification of the responsible SMG group(s) for Legal Interception issues.∗ General O&M descriptions and requirements, Enhancements to 10.18;∗ GPRS Functions.∗ GPRS Elements.∗ GPRS Exception Management. Problem resolution.∗ Study of Gb interface O&M requirements and level of standardisation.∗ NSS interface issues relating to GPRS O&M.∗ NSS Functional issues relating to GPRS O&M∗ BSS interfaces and issues relating to GPRS O&M.∗ BSS Functional issues relating to GPRS O&M.

• Medium Priority∗ Study of DNS and Border gateway O&M.∗ GPRS Trace.

• Low Priority & On Hold∗ PTM Service centre is not applicable at this time. When the specifications are available for this

node it will be prioritised.∗ Network QoS Management. When specifications are stable this item will be prioritised.∗ Study for Network Parameter Distribution in GPRS.


6.7 SMG7 and type approval matters

The SMG7 status report at SMG#27 in Tdoc SMG P-98-541 were presented by the SMG7 Chairman, Rémi Thomas. TheSMG7 status report was approved by SMG#27.

6.7.1 General

SMG7 held one plenary since SMG#26 as well as two GPRS testing drafting sessions and a meeting on evaluation of thenew R&TTE directive of the European Commission.

6.7.2 Change requests to GSM 11.10

All Change Requests to GSM 11.10 presented to SMG#27 were approved by SMG#27.


SMG#27 approved the following specifications:

• GSM 13.01-1 (TS 101 419-1), Attachment requirements for Global System forMobile communications (GSM) mobile stations; Access, version 2.0.0, inTdoc SMG P-98-544;

• GSM 13.01-2 (TS 101 431-1), Attachment requirements for mobile stations in theDCS 1800 band and additi onal GSM 900 band; Access, version 2.0.0, inTdoc SMG P-98-545;

• GSM 13.67, Attachment requirements for Global System for Mobilecommunications (GSM); Railways Band (R-GSM); Mobile Stations; Access,version 1.0.0, in Tdoc SMG P-98-792 revising Tdoc SMG P-98-542;5

• GSM 13.68, Attachment requirements for Global System for Mobilecommunications (GSM); Advanced Speech Call Items (GSM-ASCI) MobileStations; Access, version 1.0.0, in Tdoc SMG P-98-543.

See also section 6.7.4.

6.7.4 Regulatory issues

The new R&TTE directive will presumably be applied from January 2000 onwards.

Still under the present type approval regime (98/13/EC Directive), the TBRs have to be transposed into HarmonisedStandards, and ACTE has requested that the corresponding Harmonised Standards for GSM 900 and GSM 1800 aremerged (that is, ex-TBR19 with ex-TBR 31, and ex-TBR 20 with ex-TBR 32); also it has been agreed to add the phase 2+TBR modules as further parts of these Harmonised Standards.

Base TBRs: SMG#27 approved

• a new versions for TBR 19 as GSM 13.01-1 (TS 101 419) in Tdoc P-98-544

• a new version of TBR 31 as GSM 13.01-1 (TS 101 431) in Tdoc P-98-545Both specifications were approved at SMG#27 as TS, not yet as EN; after SMG#27, they include

• the necessary alignment with the requirements of the present directive (98/13/EC)and

5 Tdoc SMG P-98-542 showed the wrong specification number GSM 13.69 instead of the correct number, GSM 13.67.


• the implementation of CRs that had been previously approved by SMG (but hadnot been implemented because of the expected transition to Harmonisedstandards).

At SMG#28, SMG7 intends to present merged versions of these specifications for approval as Harmonised Standards asfollows:

TBR 19 + 31 => EN 301-419-1 (GSM 13.01)

TBR 20 + 32 => EN 301 420-1 (GSM 13.02).

GSM 13.67, the “TBR-Module” for R-GSM Band, was presented as version 1.0.0 to SMG#27 for information. SMG#27concluded that the specification was stable enough and approved GSM 13.67.

GSM 13.68, the “TBR-Module” for ASCI (Access) was presented as version 1.0.0 to SMG#27 for information. SMG#27concluded that the specification was stable enough and approved GSM 13.68.

Schedule for the “TBR Modules”:

Phase 2+ Work Item

Harmonised Standard EN No.

Core Specs SMG approved

GSM 11.10-1 SMG

approved

Document SMG

approved HSCSD 301-419-2

(GSM13.34)

SMG#23 Sep 1997

SMG#24 Dec 1998

SMG#26 25 Jun 98

ASCI 301 419-3 (GSM13.68)

SMG#24 Dec 1997

SMG#26 June 1998

target:SMG#28 Feb 1999

R-GSM 301 419-4 (GSM13.67)

SMG#24 Dec 1997

SMG#26 June 1998

target:SMG#28 Feb 1999

GPRS 301 419-5 (GSM13.60)

target: SMG#28 Feb 1999

target: SMG#29 June 1999

target:SMG#29 June 1999

CTS-MS 301 419-6 (GSM13.55)


target: SMG#30 Oct 1999

target:SMG#31 Dec 1999

CTS-FP 301 419-7 (GSM13.56)




EDGE 301 419-8 (GSM13.59)

target :SMG#29 June1999

target: SMG#30 Oct1999


AMR 301 419-9 (GSM13.70)

target: SMG#29 June1999



At SMG#27 it was not clear whether the ETSI secretariat will investigate the usage of the One Step Approval Procedure(OAP) for updated Harmonised Standards and TBR modules.

SMG#27 approved the approach and schedule in section 5.1.3 of the SMG7 status report.

6.7.5 Work items

Release 96: Mobile Station Test Specifications for the following work items are considered stable:

• EFR,

• HSCSD,

• R-GSM and


• ASCI Phase 1.Mobile Station Test Specifications for the following work items are to be completed:

• CBCH extension;

• New Cell reselection mechanisms;

• New System Information Type 9, BCCH scheduling,

• Use of Progress Indicator 64,

• ECT (Explicit Call Transfer): some aspects linked to compatibili ty and to callcontrol may need to be tested,

• CCBS (Call Completion to Busy Subscriber) some aspects will be part of theTBRs because call control is affected.

Release 97:

SMG7 has started work on Mobile Station test specifications for two Release 97 features:

• GPRS and

• CTS.GPRS Phase 1 testing: The drafting of the GPRS test cases is made very difficult by the instability of GSM 04.60;therefore the first priority to ensure the completion of the GPRS test cases is the availability of a stable GSM 04.60.

PT SMG is editing and maintaining a document which outlines the status of the work for the GPRS MS testing. Theseinformation are provided for each testing domain, hence this document allows to monitor accurately the progress of thework. The editors for each chapter and the documents which contain the draft tests are identified as well. For the timebeing this document remains inside SMG7 (318/98), it is available upon request.

It is expected that the first GPRS tests will be brought to SMG#28 for approval.

Cordless Telephony System (CTS) testing: SMG7 started to review documents on CTS.

Release 98 and beyond:

AMR testing: A presentation on AMR will be made during the next SMG7 plenary, this will allow SMG7 to organise thework for AMR testing;

EDGE testing: A presentation on EDGE will be made during the next SMG7 plenary, this will allow SMG7 to organisethe work for EDGE testing.

6.7.6 R&TTE Directive

Possible consequences of the R&TTE directive are described in Tdoc P-98-595, source Mark Bogers.

Hans Hauser presented Tdoc SMG P-98-581, Input of the SMG community to the preparation work of the R&TTEDirective, Source: T-Mobil. The document presents an analysis of essential requirements under the R&TTE. SMG#27expressed support for the concepts in the document and concluded that the document is a valuable input document for thefurther work in SMG7 and GSM MoU European Interest Group on “living under the R&TTE”.

Later in the meeting, Hans Hauser presented Tdoc SMG P-98-640, LS to GSM MoU EIG and SMG7; Common positionon Article 3 “Essential Requirements” of the draft R&TTE Directive.

This Liaison Statement was approved by SMG#27 with the following modification:

“SMG#27 has endorsedadopted the position on Article 3 “Essential Requirements” of the draftR&TTE Directive described in Tdoc SMG#27 98-581 in principle.”

The approved version of this Liaison Statement is Tdoc SMG#27 98-789.


6.7.7 Voluntary Certification Scheme

Armin Toepfer confirmed that also under a VCS scheme, GSM 11.10 will continue to be the reference for mobile stationtesting.

6.7.8 Liaison Statements

SMG#27 approved a Liaison Statement to TRAC on CTS (“work goes on”) in Tdoc SMG P-98-610, see section 6.13.

6.8 SMG8The SMG8 status report to SMG#27 in Tdoc SMG P-98-743 were presented by the SMG8 Chairman, Simon Pike. TheSMG8 status report was approved by SMG#27.

6.8.1 General

SMG8 has held one plenary meeting since SMG#26. The remaining work on GSM 11.24 has been completed andpresented to SMG#27 for approval for Vote. SMG8 is making good progress in developing tests of GPRS and pico BTSin GSM 11.21.


SMG8 presented tests of pico-BTS to SMG#27 for information in Tdoc SMG P-98-741 - for information because thepico-BTS is in Release 98.

CRs in Tdoc SMG P-98-740 and Tdoc SMG P-98-742 were approved by SMG#27.

6.8.3 Specifications

GSM 11.24, GSM Transcoding and Rate Adaptation: Base Station System Equipment Specification, will be sent forvote. The chairmen of SMG8 and SMG11 will discuss the future maintenance of GSM 11.24.

6.8.4 Releases

BSS tests for Release 96 are considered as completed. (Some issues concerning Base station configurations might have tobe added.)

6.8.5 Liaison with other bodies

TC ERM: The last TC ERM meeting approved ETS 300 342-3 to commence the vote stage of the approval process,subject to some changes being made.

This specification is only directly applicable to Phase 2 GSM infrastructure. To extend the scope to include Phase 2+, anew edition will be required. A work item for this will be presented to the next meeting of TC ERM.

6.9 SMG9The GSM relevant parts of the SMG9 status report to SMG#27 in Tdoc SMG P-98-668 were presented by the SMG9Chairman, Klaus Vedder. The SMG9 status report was approved by SMG#27. The slides of the presentation were madeavailable in Tdoc SMG P-98-676.

6.9.1 General; new scope of SMG9

SMG9 had one plenary and several sub-group meetings since SMG#26.


At the ETSI Board meeting from the 9th to 11th June, it was decided that the ETSI TC ICC should close and that existingwork items from that committee should be transferred to SMG9. This makes SMG9 the main focus of ETSI cardstandardisation activities. SMG9 reported at SMG#26 that this would require a review of their terms of reference.

This review took place at the last SMG9 plenary meeting and resulted in a new version which can be found in annex D ofTdoc SMG P-98-668.

SMG#27 approved the Terms of reference with the following modifications:

• to add liaison with WAP Forum to the liaisonsSMG9 activities outside GSM and UMTS are reported in section 6.9.5.


For change request CR A001 rev 1 to ETSI Guide EG 201 220 version 1.2.1, see section 6.9.5.

Change requests to GSM specifications:

GSM 11.11, SIM/ME interface specification: All CRs in Tdoc SMG P-98-671 were approved by SMG#27:

- CR 11.11-A071(Release 98) introduces an enhance image coding scheme that willenable colour icons to be stored on the SIM in a standardised manner.

- CR 11.11-A072 (Release 98) is a harmonisation CR that adds reference to PCS 1900.This is done at the request of ANSI T1P1.

GSM 11.14, SIM Application Toolkit: All CRs in Tdoc SMG P-98-669 except CR 11.14-A111r1 (see further below)and all CRs in Tdoc SMG P-98-670 were approved by SMG#27:

- CR 11.14-A084 (Release 96), CR 11.14-A087 (Release 97) and CR 11.14-A112(Release 98), introducing a new class 1bis to reduce the number of MEs on the marketoffering only partial and differing support of class 2.

- CR 11.14-A091r1 (Release 98): "Yes/No" response for GET INKEY. Most of SIMToolkit applications using the GET INKEY command actually expect only a "YES" or"NO" response. This new feature simplifies the SIM Toolkit application and providesan improved user MMI.

- CR 11.14-A092 (Release 98): Alignment of coding of card reader status event. Thiscorrects the encoding of card reader status event thus aligning it with the encoding ofthe other events.

- CR 11.14-A093 (Release 97): Additional information field mandatory in case of USSDReturn Error result. This clarifies that if result code '37' is returned, the ME shallprovide a specific cause value as additional information.

- CR 11.14-A094 (Release 98): This is the Release 98 version of CR 11.14-A093.

- CR 11.14-A095 (Release 97): This CR corrects the omission of the SET UP EVENTLIST command from the table that shows all possible result values for all commands.

- CR 11.14-A096 (Release 96), CR 11.14-A097 (Release 97), CR 11.14-A098(Release 98): These CRs clarify that in the case where the SIM issues an instruction tothe ME to initiate a Mobile Originated transaction (e.g. SEND SMS, SEND USSD), thecontent supplied by the SIM for onward transmission by the ME shall not be altered bythe ME unless explicitly stated elsewhere in GSM 11.14 or in GSM 11.11.


- CR 11.14-A099 (Release 97), CR 11.14-A100 (Release 98): Clarification about USSDreturn result.

- CR 11.14-A101 (Release 97), CR 11.14-A102 (Release 96), CR 11.14-A103(Release 98): These CRs clarify the handling of the ‘9300’ status response for theenvelope command for SMS Data download, Call Control and SMS Call Control. Allother cases are already defined in GSM 11.11.

- CR 11.14-A104 (Release 98): This CR introduces a new command SET UP IDLEMODE TEXT. The text supplied by the command is not allowed to overwriteinformation of higher importance such as the service provider's name.

CR 11.14-A108 (Release 98): This CR clarifies that the ME shall not locally generateaudible DTMF tones and play them to the user during a SET UP CALL command.

- CR 11.14-A109 (Release 97): This change describes the handling of the TERMINALRESPONSE command in the case where CALL CONTROL by SIM is triggered after aproactive command SET UP CALL, SEND SS or SEND USSD.

- CR 11.14-A110 (Release 98): This is the Release 98 version of CR 11.14-A109.

CR 11.14-A111r4 (Release 98) in Tdoc SMG P-98-605, introducing a new command to the SIM application toolkit"RUN AT COMMAND" was also approved by SMG#27. This allows the application to issue AT commands to the ME.This may include those specified in GSM 07.07 as well as manufacturer specific commands. Typical uses for suchfunctionality are remote diagnostics, customer care and control of unattended terminals.

The original CR, CR 11.14-A111r1, presented in Tdoc SMG P-98-669, had been revised by SMG#27:

During discussion at SMG9 plenary, some concerns had arisen:

(1) that AT commands would allow the possibili ty for ME and network operatorspecific actions to be introduced. One such action could be the setting up of a callwithout the user’s knowledge or confirmation;

(2) that the SIM toolkit would now be promoting the opportunity for non-standardisedME/service behaviour to be introduced;

(3) that the feature would effectively bypass the current concept of toolkit classeswhich fully define an ME’s toolkit behaviour.

SMG9 therefore had sent the CR to SMG#27 together with a Liaison Statement in annex B of Tdoc SMG P-98-668explaining the backgrounds.

During SMG#27, the revision CR 11.14-A111r4 in Tdoc SMG P-98-605 was elaborated requiring control by thesubscriber through the ME for this feature.

SMG#27 approved Tdoc SMG P-98-625, Handling of AT Commands via SIM Toolkit, source: BT, Vodafone, FranceTelecom, Nokia, Ericsson, Siemens, Motorola. This document concludes that SMG4 should provide a subset of ATcommands which is recommended for operators to use with SIM Toolkit.

In this context, Nigel Barnes presented Tdoc SMG P-98-245, General guidelines for Automatic Call and SMS execution,source: Ad Hoc Group of SMG#25, to SMG#27. This document indicates possible problem areas when certain servicesand application execution environments cause the GSM ME to initiate calls or send SMS automatically or as a result ofuser interaction or interaction by external equipment with the application. It had already presented at SMG#25, andSMG#25 had decided further actions (including further discussions in SMG1, SMG12, MoU SCAG).

Again in the same context, SMG#27 approved Tdoc SMG P-98-626, Applications and Automatic Execution, source: BT,Vodafone, Nokia, Ericsson, Motorola, Siemens. Following the proposals of this document, an SMG Workshop onApplications and Automatic Execution will be convened (planned place and date: ETSI Headquarters, Sophia Antipolis,30th November to 1st December 1998), chaired by Kevin Holley. This workshop will allow experts to identify all theproblem areas, including those identified in Tdoc SMG P-98-245 and annex B of Tdoc SMG P-98-668 (=SMG9 98p373),


and to propose a programme structure for resolution of the problems, possibly via further study in the individual STCs.The workshop is mandated to offer guidance directly to the STCs.

Fred Hillebrand will take Tdoc SMG P-98-625 and Tdoc SMG P-98-626 to GSM MoU.

GSM 02.17, SIM functional characteristics: A complete revision of GSM 02.17 to align it with the changes made toGSM 11.11 and GSM 11.14 over the last years had been presented to SMG#26 for information and comment. As nocomments had been received, SMG9 had agreed to present the "new" GSM 02.17 to SMG#27 for approval. The two CRsestablishing the new version of GSM 02.17 in Tdoc SMG P-98-672 were approved by SMG#27: CR 02.17-A001(Release 96) and the corresponding Release 98 CR 02.17-A003.


GSM 02.19, Subscriber Identity Module Application Programming Interface (SIM API); Service description; Stage 1,version 2.0.0 in Tdoc SMG P-98-674 was approved by SMG#27 for Release 98.

6.9.4 Work items

Interworking with non-GSM applications : SMG#27 confirmed the deletion of the work item Interworking with non-GSM applications.

6.9.5 SMG9 areas outside GSM and UMTS

CR A001 rev 1 to EG 201 220 version 1.2.1 in Tdoc P-98-673 was approved by SMG#27. Background:

SMG9 has recently become responsible for the documents previously in the control of TC ICC. ETSI Guide EG 201 220,ETSI numbering system for telecommunication application providers (AID), is one such document. (For the completelist, see the status list of SMG specifications.) The change request contained in Tdoc P-98-673 was elaborated as a resultof work being done on GSM 02.19, the SIM API. The implementation of the SIM API requires that an application residingon the smart card is referenced by the operating system by an Application Identifier (AID). This change allows cardapplications to be administered by the card issuer, using a generic PIX structure6, without the necessity for a plethora ofapplications for AIDs to the ETSI Secretariat.

6.9.6 Other issues

Application identifiers: SMG#27 endorsed the SMG9 application for two application identifiers to be allocated by ETSI(see request in annex A of Tdoc SMG P-98-668; cf. also section 6.9.5).

Error handling for SIM toolkit: A potential problem of missing error handling for SIM toolkit procedures was raised atSMG#27, e.g., when a PLMN change occurs.

SMG9 working party on SMG9 Generics: SMG#27 noted that a new SMG9 working party called "SMG9 Generics"had been formed at the last SMG9 plenary. The chairman is Rune Lindholm from Nokia.

6.10 SMG10The GSM relevant parts of the SMG10 status report to SMG#27 in Tdoc SMG P-98-531 were presented by the SMG10Chairman, Mike Walker. The SMG10 status report was approved by SMG#27.

6.10.1 General

Since SMG#26, SMG10 had one plenary and several working party/ad-hoc meetings.

6 AID consists of a Registered application provider IDentifier (RID) and a Proprietary application Identifier eXtension (PIX).



All change requests presented by SMG10 to SMG#27 were approved by SMG#27:

• CR 02.33-A002r2 on Lawful Interception - Location Dependent Interception inTdoc SMG P-98-532;

• CR 02.33-A003r2 on Lawful Interception - Security in Tdoc SMG P-98-532.


• GSM 03.33, Lawful Interception stage 2, version 1.0.0 (R98), inTdoc SMG -98-533 was presented to SMG#27 for information (rapporteur: DavidMiles, Cellnet).

• GSM 03.35, Immediate Service Termination (IST); Stage 2, version 2.0.0 (R98),in Tdoc SMG P-98-534, was approved by SMG#27. SMG12 should review thespecification for architectural issues.


6.10.4.1 Work items

ASCI security: After studying of an input document on ASCI (Advanced Speech Call Items) SMG10 had concluded:

• With suitable internal security and procedures, a network operator has a minimalrisk of fraud with eMLPP. If the network postpones the authentication for fastcall set-up, rather than not performing it, there seems to be no risk. The subscriberto eMLPP can be made responsible for any fraud conducted in return for theprivilege of fast call set-up. The subscriber should accept the risk ofeavesdropping on the unciphered link and the possibility of masquerade withintent to misinform.

• VGCS and VBS can only be used within defined areas. The motivation for calloriginated fraud by an outsider therefore seems low. Again, there is a risk ofeavesdropping and masquerade, which subscribers should be aware of and haveaccepted as a risk.

• eMLPP, VGCS and VBS do not represent sources of technical fraud. With carefulmanagement, they do not represent a risk to network operators. Their users shouldbe made aware of the small risks of eavesdropping and masquerade.

• The task of making users aware of the risks, and of implementing good operatorcontrol of the services, is the responsibility of operators offering the service. Thesending of a liaison to MoU SG regarding the risks with the ASCI services istherefore recommended.

For a Liaison Statement to GSM MoU Security Group, see section 6.10.5.

Fraud Information Gathering System(FIGS): The rating information in FIGS was removed. It was agreed with SMG3-WPC that no stage 3 for FIGS is required. Stage 2 contains the requirements for implementation of FIGS by CAMEL.FIGS level 1 gives a possibility for implementing FIGS without CAMEL, but this principle is not worked out in detail.

General Packet Radio Service (GPRS) - Security issues: SMG10 has checked CR GSM 04.64-A023 inTdoc SMG P-98-422 (which had been approved by SMG#26). SMG10 concluded that there is no major security impact;that, however, a default value of Input Offset Value (IOV) should only be used once per authentication. SMG10 requestedthat CRs to GSM 04.64/Annex A first to be checked by SMG10 before SMG approval.


GSM - Cordless Telephony System (CTS): SMG10 considered several open issues and agreed on some principles.Two issues need to be checked with SMG12:

• Should the Fixed Part (FP) systematically pass information to the network atinitialisation?

• What kind of mechanism should be introduced to prevent non type approved FPs?Main concerns are the misuse of the spectrum and the commercial abuse. This has to be solved by the requirements inAnnex E/GSM 03.20.

For a Liaison Statement sent by SMG10 to SAGE on the use of public key for CTS, see section 6.10.5.

As requested by SMG1, stage 1 of CTS was checked. The result of this review has been forwarded to SMG1.

Immediate Service Termination (IST): The non-CAMEL IST proposal from Alcatel was agreed in SMG10 withoutmuch support. SMG3 was informed on this decision. See section 6.3.4.

No modifications were made to the stage 2 description of IST (GSM 03.35), which was approved by SMG#27, seesection 6.10.3.

Lawful Interception (LI): CR 02.33-A002r2, introducing Location Dependent Interception as a new feature into stage 1,has been approved by SMG#27, see section 6.10.2. Stage 2 will have to be amended correspondingly.

Location Services (LCS): SMG10 had checked a liaison statement from SMG4 to T1P1 and had informed T1P1 andSMG4 about the SMG10 point of view: The frequency of information updating has impact on the signalling load. If theservice is to be supported for a roaming subscriber then this would require changes for MAP signalling. It must be asubscribed service, where the customer subscribes and has given permission for his location information to be given tonetwork or service provider. That information would only be collected for those subscribers that gave permission. Theremay be problems for roaming customers in giving this permission. It was considered acceptable that subscribing couldtake place as a supplementary service.

Mobile Station Execution Environment (MExE): The security related sections of stage 2 were checked. It wasrecommended again that the work on MExE security should be moved to SMG10. In particular, SMG10 think that theIMEI, classmark, authentication, etc. should not be possible to be changed. SMG4 delegates are invited to SMG10-WPAmeetings on MExE.

Discussion at SMG#27: Mike Walker commented that SMG10 might not be able to finalise their work on MExE untilSMG#28.

The SMG4 Chairman, Kevin Holley, emphasised that if companies want MExE completed in time, they should provideenough support for SMG10.

SMG#27 confirmed that SMG10 should complete their work on MExE.

Support of Localized Service Area (SoLSA): SMG10 had identified that the SoLSA related user data is not secure andthat some applications of the SIM Application Toolkit might be insecure. SMG1 and SMG12 have been informed.

6.10.4.2 Other work areas

A3 (authentication algorithm): Press statements have been issues by GSM MoU related to security issues. It is advisedby the MoU that algorithm A3 should be an own development of each operator. A new example algorithm (COMP 128/2)will be made available soon by the GSM MoU Association. Distribution will be performed by the GSM MoU secretariat.

A5 (ciphering algorithm): SMG10 is studying proposals to further improve the handling the ciphering security, includingusage of longer keys (where also support by SIM-ME interface has to be checked). Tetra, for example, is using anencryption key with a length of 80 bit.

Automatic calls: Several documents were studied and an answer was sent to SMG9.

SS7 security: SMG10 has identified major security risks with SS7. A collection was made of all detected problems. Thestudy needs to be carried out by SMG10 with assistance from SMG3.

Clarifications at SMG#27: Peter van der Arend clarified that SPS had already been informed about the problem.


Decision of SMG#27: SMG confirmed that SMG10 should continue work on SS7 security.

See also section 6.10.5 on a Liaison statement to SMG#27 on this issue.


SMG#27 endorsed the Proposed LS to MoU-SG on ASCI fraud issues in Annex A of Tdoc SMG P-98-531.SMG noted a LS to TMN5 & Network Management Forum Mobile Team on Introduction of Roaming and FraudManagement to the TelOpsMap in Annex B of Tdoc SMG P-98-531, presented by SMG10 to SMG#27 for information.

SMG noted a LS to ETSI SAGE on CTS in Annex C of Tdoc SMG P-98-531 to SMG#27 for information. It concerns theuse of public key for CTS, presented by SMG10 to SMG#27 for information.

Concerning the LS to SMG#27 on SS7 network security in Annex D of Tdoc SMG P-98-531, see section 6.10.4.

6.11 SMG11The GSM relevant parts of the SMG11 status report to SMG#27 in Tdoc SMG P-98-700 were presented by the SMG11Chairman, Kari Järvinen. The SMG11 status report was approved by SMG#27.

The following scheduled meetings need to find a Host:

Plenary:

SMG11#9 11th –15th January, 1999 Host required

SMG11#10 3rd –7th May, 1999 Host required

Companies willing to host a meeting should contact Paolo Usai (e-mail: [email protected], fax: + 33 4 93 65 28 17).

6.11.1 General

Since SMG#26, SMG11 has held one plenary meeting, one extraordinary plenary meeting (with agenda limited to AMRmatters), and ad hoc group meetings on Adaptive Multi Rate codec (AMR), Speech Quality (SQ) and Tandem FreeOperation (TFO) matters.


Two CRs to GSM 03.50 Phase 2 and 2+ (correction of reference) in Tdoc SMG P-98-704 were approved by SMG#27.


GSM 04.53, Inband Tandem Free Operation (TFO) of Speech Codecs; Service Description; Stage 3, v. 1.6.0 inTdoc SMG P-98-703 was presented by William Navarro to SMG#27 for information.

GSM 10.70, AMR Project scheduling and open issues, v. 0.0.1, in Tdoc SMG P-98-701 was presented to SMG#27 byKari Järvinen. See section 6.11.9.

6.11.4 Presentation of AMR Selection Phase Results.

The AMR Selection Phase has been completed on schedule. Substantial performance improvements have beendemonstrated. All five candidates on the short list from the Qualification Phase had submitted their codec for selectiontests. Following the completion of the subjective tests, one candidate decided to withdraw. All remaining four candidatesprovided the required deliverables and two of them passed the Selection Rules.

Kari Järvinen presented in detail the AMR Selection Phase results given in Tdoc SMG P-98-562 (slides inTdoc SMG P-98-731).


SMG11 agreed to recommend the adoption of the ENS1 codec proposed by Ericsson, Nokia and Siemens, subject to twoconditions being met:

1) that appropriate resources are allocated by (but not limited to) ENS1 proponentsto complete the AMR specifications in time for Release 98;

2) that a “reasonable” proportion of GSM BSS manufacturers indicate that the ENS1codec can be implemented on their existing, HR compatible BTS hardware.

Discussion in SMG#27:

• Several comments on implementability aspects were made.

• A question was raised on condition 2), i.e. whether this issue (regarding differentversions of existing BTSs) was considered with the necessary importance.

• Another view was that condition 2) was useless because as it would be met bymajor manufacturers by all means.

• Others stated that information concerning condition 2), was needed by operators.

• Alain Ohana stated that the same condition 2) about the implementability wasvalid as well for the other candidate ABCFNR.

• Others felt the requirement of condition 2) strange and inappropriate as involvingcommercial issues, and not to be a matter for SMG11.

• It was clarified that this condition is related to complexity requirements andcontained in Tdoc SMG P-98-562.

6.11.5 AMR Implementability aspects

• Tdoc SMG P-98-592, Ericssons comments on AMR, source: Ericsson, andTdoc SMG P-98-596, AMR Implementability and Commitment to Further Work,source: Siemens, claimed both conditions 1) and 2) to be met by Ericsson andSiemens.

• Tdoc SMG P-98-591, Commitment for finalizing AMR specifications, source:Nokia, contains the commitment from Nokia to raise resources for condition 1)but no commitment for condition 2) on implementability aspects. On condition 2),Nokia commented at SMG#27 that a number of different BTS exist in the market;and that Nokia felt the implementability aspects as not to be problematic for mostmanufacturers.


• Niels Peter Skov Andersen felt commitments from ENS1 for condition 1)appreciable, but nevertheless he felt difficult or at least not straightforward allAMR specifications to be ready in time for Release 98. The concern was sharedby other delegates.

• The SMG Chairman reminded that three companies had already committed onconditions set by SMG11 for the approval of the proposed ENS1 codec andproposed to conclude that complexity constraints were met by AMR ENS1.

• Others expressed the worry that the two conditions set by SMG11 might not besatisfied in practice.


6.11.6 IPR matters on AMR

Commitments to comply with the ETSI IPR policy had been given to ETSI from the candidates. The ETSI Legal Adviser,Stéphane Tronchon, confirmed at SMG#27 that the three ENS1 proponents have declared to be ready to grant licences.

6.11.7 Other aspects of AMR Selection phase evaluation.

Tdoc SMG P-98-575 was presented by Wang Zhiqin; the document stated that AMR candidate ENS1 did not showproblems for the Chinese language and was the best in their evaluation.

The latter conclusion was not shared by William Navarro, but was felt in line with all the other results by Alain Ohana.The subject was left to be dealt with off-line.

Tdoc SMG P-98-590 was presented by Su Huan-yu (Rockwell), raising the doubt that the ENS1 candidate in Half ratechannel (in adverse noisy conditions) would perform even worse that the current Half Rate codec; the conclusions in thisdocument were derived by an indirect comparison of the present round of AMR subjective results and results on GSM HRcontained in GSM 06.85.

It was reported that SMG11 felt the performance of AMR proposal in HR better than the current GSM HR codec and feltthe conclusions from the Rockwell document not applicable, since the comparison given therein was not feasible due todifferent contexts.

Phil Gaskell reminded the text in the report from SMG11 stating that the AMR exercise represented the best ‘state of theart’ codec contest, and asked to include HR tests in the set of characterisation tests.

William Navarro pointed out that nevertheless the results in HR were lower than expected.

Decision of SMG#27: The Selection Phase of testing performed by the subjective testing (for the listening and theprocessing laboratories) was unanimously approved (no abstention, no objection).

6.11.8 AMR Selection.

Alain Ohana presented Tdoc SMG P-98-589 (North America GSM Alliance) and asked to select the ENS1proposal as the AMR standard codec.

Niels Peter Skov Andersen commented that in adverse conditions there will be no advantage in capacity sincehandover to the FR channel would be needed, and asked how this handover should be dealt with.

Alain Ohana stated that how the BSC and/or the handset would measure the channel quality might not bestandardised but that in any case the control would be kept in the network, and that the in-band signalling was anintegral part of the AMR standard.

SMG#27 decision: ENS1 was unanimously selected as the AMR standard codec (no abstention, no objection).

6.11.9 AMR Project scheduling and open issues

6.11.9.1 Optimisation phase

AMR Project plan: Tdoc SMG P-98-701, GSM 10.70, AMR Project scheduling and open issues, V0.0.1, was presentedto SMG#27 by Kari Järvinen (cf. section 6.11.3).

Tdoc SMG P-98-578, Optimisation of the AMR codec, source: France Télécom and Cegetel, was presented by RémiThomas, asking for an optimisation phase of the AMR codec to be conducted. He stressed the importance of the linkadaptation part of the specifications (studied by SMG2) and stated that the costs of implementing AMR would fully justifya period of time dedicated to an optimisation phase. He reminded also that the second codec in ranking ABCFNRperformed better than the winner ENS1 in noisy and adverse conditions.

David Cooper presented Tdoc SMG P-98-617, Benefits of AMR Codec Optimisation Phase, source: NEC Technologies(UK) Ltd. This paper proposes an optimisation phase with at least the objective of identifying the optimum number ofmodes for use with GSM, including the removal of unnecessary modes and a re-characterisation of the performance of theresulting optimised codec.


It was commented that SMG11 could fulfil the goals of Tdoc SMG P-98-617 within their time schedules.

William Navarro presented Tdoc SMG P-98-593, Completion of the AMR standard, source: Nortel, proposing anoptimisation phase to be carried out until January 1999, which would lead to approve the final version by SMG PlenaryNo. 29 (still being considered as part of the Release 98).

Phil Gaskell presented verbally Tdoc SMG Tdoc P-98-597, Selection of the AMR codec, source: BT, Cellnet, CSELT,E-Plus, Ericsson, Finnet Group, GSM North America, Italtel, Mannesmann Mobilfunk, Marconi, Motorola, Nokia,Omnitel Pronto Italia, One2One, Siemens, Smartone, Telia, Telital, TIM. He argued prolonging the optimisation phase asnot appropriate, due to the short time frame available (anyway, he agreed on the 6 weeks optimisation phase foreseen bySMG11).

Pietro Porzio Giusto supported this intervention and stressed the importance of development on schedule.

At this point in time, the SMG Chairman asked for a show of hands in favour of the two alternatives. Result:

• Support of a “complete” optimisation phase: 13

• Support of an optimisation phase of maximally 6 weeks as proposed by SMG11:27.

Availability of C source code: Erik Ekudden, Ericsson, stated that for verification purposes, the actual C code will beprovided to the AMR verification group at their next meeting in October under an NDA agreement.

Decision of SMG#27: With this clarification, SMG#27 agreed that the optimisation phase should be planned as proposedby SMG11.

6.11.9.2 Other issues

Simon Pike drew the attention to two aspects of the ENS1 codec which had not been mentioned in previous discussions:

• The ENS1 codec proposal includes modes for which the performance had notbeen presented.

• It appeared that one of these modes had no channel coding defined for GSM.He proposed that modes within ENS1 should not be included in the AMR standards until some evaluation of theirperformance had been done and they could be implemented in the GSM system (e.g., the channel coding is defined).

The SMG11 Chairman clarified that these modes could of course be used for some scenario reasons in the real world andbe better characterised in the future characterisation phase of testing, already foreseen by SMG11.

Simon Pike pointed out that the completion of the AMR standards would require work in other STCs (especially channelcoding and TRAU frames, in SMG2). Gunnar Sandegren asked the issue to be debated in SMG11 if not done yet. SimonPike replied that he believed that these matters were appropriate for discussion in SMG Plenary; the completion of AMRrequired co-ordination between STCs, and the choice of codec modes to be included was not a purely technical matter(especially if there is no channel coding for GSM). Phil Gaskell commented that such issues were already dealt with inSMG11, and that remaining open issues will be dealt with as well.

It was commented that

• impacts on GSM 11.10, GSM 11.21 and GSM 11.24 are missing

• the time plan is very optimisticSimon Pike presented Tdoc SMG P-98-612, Testability of AMR in the BSS, source: SMG8 Chairman, and acorresponding Liaison Statement from SMG to SMG2 (cc. SMG8, SMG11) on Testability of AMR in the BSS inTdoc SMG P-98-642.

Decisions of SMG#27:

• SMG#27 approved the Liaison Statement in Tdoc SMG P-98-642.

• SMG#27 confirmed AMR in Release 98, even if it should turn out that some partsneed to be completed after SMG#28.


6.11.10 Work items except AMR

• Tandem Free Operation of speech codecs in Mobile-to-Mobile Calls(MM Cs): See 6.11.9 for GSM 04.53, Inband Tandem Free Operation (TFO) ofSpeech Codecs; Service Description; Stage 3, v. 1.6.0 in Tdoc SMG P-98-703.

• Test methods for handset and headset mobile station: SMG#27 approved todelete this work item.

6.12 SMG12The GSM relevant parts of the SMG12 status report to SMG#27 in Tdoc SMG P-98-734 were presented by the SMG12Chairman, François Courau. The SMG12 status report was approved by SMG#27.

6.12.1 General

SMG12 had held three meetings since SMG#27. It does not convene subgroup meetings. Participants (around 85) includedelegates from Japan and USA. Progress had been made on all subjects, GSM as well as UMTS. Need for joint sessionswith other STCs has been seen, one joint meeting had already been organised with SMG2 UMTS ARC.

Teuvo Järvelä from Nokia is co-chairing SMG12. The co-chairing, with a 50-50 work split between the two chairmen, asdescribed in P-98-784, was approved by SMG#27.


All change requests presented by SMG12 to SMG#27 in Tdoc SMG P-98-752 (GPRS) and Tdoc SMG P-98-753 (GPRS)were approved by SMG#27.

The following Change Requests to GSM 03.03 in document P-98-730 have been withdrawn:

03.03 A009 3 R96 5.1.0 Definition of SSN for MAP signalling to the gsmSCF F 98S874 CAMEL 1

03.03 A011 1 R97 6.0.0 Definition of SSN for MAP signalling to the gsmSCF A 98S874 CAMEL 2

03.03 A010 3 R97 6.0.0 Definition of national SSNs for GPRS F 98S874 GPRS


The following specifications were presented by SMG12 to SMG#27 for information (both Release 98):

• GSM 03.73, Support of Locali sed Service Area (SoLSA); Stage 2, version 1.0.0,in Tdoc SMG P-98-756;

• GSM 03.56, GSM Cordless Telephony System (CTS), Phase 1; CTS ArchitectureDescription; Stage 2, version 1.0.0, in Tdoc SMG P-98-757.

SMG#27 approved GSM 10.56, Project scheduling and open issues: GSM Cordless Telephony System CTS, Phase 1,version 2.0.2 (Release 98), in Tdoc SMG P-98-586, which was presented by Michel Galligo (Alcatel).

6.12.4 Work items

GSM Mobile Number Portability (EURO) MNP: SMG12 drafted a report on advantages and drawbacks of the currentsolutions; it has been forwarded to SMG3 for comments and is planned for presentation at SMG#28.

An architecture providing a single long term solution has not been identified so far. It was felt necessary to wait forresults of the specifications by SMG3 of the current proposals. The current version of the report is forwarded forenhancement to SMG3.


6.12.5 Other issues

Sub-System Numbers: SSN allocation for entities inside the GSM networks has been elaborated, seeTdoc SMG P-98-737. SMG#27 endorsed the proposal that MoU shall handle this documentation in the long term to ensurethat no contradicting allocation is done outside of Europe. This will have to be also indicated to SPS1.

SMG#27 approved Tdoc SMG P-98-602, a Liaison Statement to GSM MoU on SSN with the proposal described above.Fred Hillebrand will discuss the proposal at the next GSM MoU plenary.

6.13 GSM Program Management

6.13.1 Phase 2+ Work item list and Phase 2+ Roadmap

Updated versions of Phase 2+ Work item list and Phase 2+ Roadmap are available on the ETSI server under tech-org/smg/document/smg/Databases/work_items.

6.13.2 GSM Work Items

GSM - Cordless Telephony System (CTS): Michel Galligo (Alcatel) presented GSM 10.56, Project scheduling andopen issues: GSM Cordless Telephony System CTS, Phase 1, version 2.0.2, in Tdoc SMG P-98-586. It was approved bySMG#27.

David Barnes, Chairman of the GSM Type Approval Advisory Board (GTAAB), informed SMG#27 that the TBR moduleon CTS FP had not yet been accepted ACTE, because they feared that CTS had no support in SMG.

Later in the meeting, SMG#27 approved a Liaison Statement to TRAC on CTS (“work goes on”) in Tdoc SMG P-98-610.

7 UMTS matters

7.1 SMG1The UMTS relevant part of the SMG1 status report to SMG#27 in Tdoc SMG P-98-547 was presented by Alan Cox.SMG#27 approved the SMG1 status report to SMG#27, see also section 6.1.

SMG1 has made useful progress on a number of key UMTS issues, especially in specifying the contents of the first phaseof UMTS.


• CR UMTS 22.01A-A007 in Tdoc SMG P-98-551 was approved by SMG#27. Itremoves the Role Model in order to improve clarity. Both concepts of ServiceProvider and Network Operator are replaced by Home Environment and ServingNetwork respectively. A Home Environment is responsible for enabling a user toobtain UMTS services in a consistent manner regardless of the user’s location orterminal used (within the limitations of the serving network and current terminal)while a Serving Network provides the user with access to the services of homeenvironment.

• CR UMTS 22.01-A008 on network selection in Tdoc SMG P-98-552 waspostponed by SMG#27. SMG1 and SMG12 should further work on this CR.Amongst the comments given in SMG#27:∗ In GSM, it has been seen as important to make the possibility of manual network selection

mandatory in the mobile station.


∗ Comments on the download of automatic selection procedure to the USIM were presented inTdoc SMG P-98-604 by Teuvo Järvelä.

∗ The removal of the role model should be reflected in the CR.

• CR UMTS 22.01A-A009 in Tdoc SMG P-98-553 on removal of references to INand B-ISDN was approved by SMG#27.

• CR UMTS 22.01A-A010 in Tdoc SMG P-98-682 on multiple user profiles wasapproved by SMG#27. It improves the clarity of service requirements for multipleuser profiles.

• CR UMTS 22.07A-A001 in Tdoc SMG P-98-554 introduces clarifications into thisreport on security aspects relating to USIM & Payment methods. It was approvedby SMG#27.

7.1.2 New Specifications

UMTS 22.00, UMTS Phase 1, V1.0.0, in Tdoc SMG P-98-555 was presented to SMG#27 for information. See section7.1.3.

UMTS 22.75, Service aspects; Advanced Addressing, V2.3.0 in Tdoc SMG P-98-558 was approved by SMG#27.

UMTS 22.71, Service aspects; Automatic Establishment of Roaming Relationships, version 3.0.1: SMG#27 approvedthat this is a Report, not a TS as incorrectly shown on the previously approved version; see Tdoc SMG P-98-559.

7.1.3 UMTS Phase 1

SMG1 examined the inter-dependence between the GSM 02 series and the UMTS 22 series, avoiding duplication in thespecifications between GSM and UMTS while ensuring a consistent approach to separate or combined GSM and UMTSnetworks. SMG1 presented UMTS 22.00 V1.0.0 to SMG#27 for information, see also section 7.1.2. This lists the servicerequirements for the initial phase of UMTS and is a top level document containing references to the 02 and 22 series asappropriate. It was also proposed that 22 series documents may refer to the 02 series where necessary. This was to bestudied by WOME, see section 5.6. An updated list of UMTS Work Items is attached to the specification.

The content of UMTS 22.00 was regarded by SMG1 important to give clear service requirements to other STCs forUMTS phase 1.

Comments in SMG#27:

It was explained to SMG#27 that an annex on UMTS Bearer Services, of earlier versions of the document had beenremoved by SMG1 because it was felt not to be of a high enough level to be included into UMTS 22.00. SMG1 willinvestigate inclusion of the annex in another specification.

Comments from SMG4 given to SMG#27: Kevin Holley reported that SMG4 saw problems when Fax T30 is notsupported in UMTS. Further comments are contained in a liaison statement to SMG1 presented at SMG#27 asTdoc SMG P-98-615.

There are also some comments from SERG in Tdoc SMG P-98-774 on Transcoders and TFO in UMTS, Cross Phasecompatibility in UMTS, Core network aspects and mobility management.

SMG2 had seen the document, and welcomed it. SMG2 sent detailed comments in a liaison statement to SMG1. SMG2expressed the wish to have at least the spirit of an agreement of UMTS phase 1 scope, so that SMG2 is sure to fulfil therequirements.

Further comments at SMG#27:

• Some concerns on the time plan in annex A were expressed.

• In section 5, packet data services are missing.

• It was clarified that SMG1 work is strongly based on the work of delegatesknowing the business interests of their companies.


• Comment that some descriptions in the document are too much implementationoriented.

• At the ETSI General Assembly, the term “initial phase of UMTS” has beenintroduced, and it has consciously been avoided to use UMTS phase 1 in order toavoid confusion with the term “UMTS phase 1” in SMG.

Decision of SMG#27: The basic lines and main direction of UMTS 22.00 are approved in principle. The documentshould be commented in the STCs further and present an updated version to SMG#28 for approval.

7.1.4 Work items

7.1.4.1 UMTS Phase 1 Work Items resulting from UMTS 22.00

UMTS Phase 1 Work Items had been updated by SMG1 in Tdoc SMG P-98-681 to reflect the contents of UMTS 22.00;the Work Items under primary responsibility of SMG1 were presented to SMG#27 for approval, while the others werepresented to SMG#27 for information.

Comments of SMG#27:

• Instead of the terms “WCDMA” and “TD-CDMA”, “FDD” and “TDD” shouldbe used.

• François Courau indicated further work items, e.g. in the scope of SMG12.Decisions of SMG#27:

1. SMG#27 approved the work items under SMG1 prime responsibility and theirWIDs in Tdoc SMG P-98-681:

WORK ITEM Rel Rapporteur SupportingCompanies

Prime resp.STC

Secondaryresp. STC

Comments

Virtual Home Environment 99 E.PostmannMotorola, FT,Ericsson, MMO,Siemens, T-Mobil,Fujitsu, Lucent

SMG1 SMG12,SMG4,SMG9,SMG3

UMTS Numbering, Addressingand Identities

99 S.Kleier Motorola, FT,Ericsson, MMO,Siemens, T-Mobil,Fujitsu, Lucent

SMG1 SMG3 This WI may involveother ETSI TCs andexternal bodies.

UMTS Charging & Billing 99 D.ChambersMotorola, FT,Ericsson, MMO,Siemens, T-Mobil,Fujitsu, Lucent

SMG1 SMG6


2. SMG#27 asked the STCs indicated as prime responsible to consider the otherwork items in Tdoc SMG P-98-681:

WORK ITEM Rel Rapporteur SupportingCompanies

Prime resp.STC

Secondaryresp. STC

Comments

UMTS Bearer ServiceNegotiation & Teleservice

99 Motorola, FT,Ericsson, MMO,Siemens, T-Mobil,Fujitsu, Lucent

SMG3,SMG4

SMG1,SMG12

UTRAN Bearer Capabilities 99 Motorola, FT,Ericsson, MMO,Siemens, T-Mobil,Fujitsu, Lucent

SMG2 SMG1

UTRAN & GSM BSSRelationship

99 Motorola, FT,Ericsson, MMO,Siemens, T-Mobil,Fujitsu, Lucent

SMG2 SMG1

UMTS Mobility Management 99 Motorola, FT,Ericsson, MMO,Siemens, T-Mobil,Fujitsu, Lucent

SMG12 SMG1,SMG3

MAP over TCP/UDP/IP 99 Motorola SMG3 To be addressed byGPRS experts

Virtual Home Environment 99 E.PostmannMotorola, FT,Ericsson, MMO,Siemens, T-Mobil,Fujitsu, Lucent

SMG1 SMG12,SMG4,SMG9,SMG3

UMTS Service Management 99 Motorola, FT,Ericsson, MMO,Siemens, T-Mobil,Fujitsu, Lucent

SMG6 SMG12,SMG1

UMTS Access Security 99 Motorola, FT,Ericsson, MMO,Siemens, T-Mobil,Fujitsu, Lucent

SMG10 SMG1,SMG3

SMG10 will completethis WI if access inUMTS phase 1requires improvedsecurity.

UMTS Internetwork Security 99 SMG10 to decidewhether improvedsecurity is neededbetween networksfor UMTS phase 1.

SMG10 SMG1,SMG3

SMG10 will draft thisWI if it is needed.

UMTS Numbering, Addressingand Identities

99 S.Kleier Motorola, FT,Ericsson, MMO,Siemens, T-Mobil,Fujitsu, Lucent

SMG1 SMG3 This WI may involveother ETSI TCs andexternal bodies.

UMTS Charging & Billing 99 D.ChambersMotorola, FT,Ericsson, MMO,Siemens, T-Mobil,Fujitsu, Lucent

SMG1 SMG6

QoS support in GPRS forUMTS Phase 1

99 Motorola, FT,Ericsson, MMO,Siemens, T-Mobil,Fujitsu

SMG12 SMG1,SMG4

7.1.4.2 Further work items

SMS Cell Broadcast Service: Armin Toepfer presented Tdoc SMG P-98-772, UMTS Phase 1: Support of SMS CellBroadcast Service, source: Mannesmann Mobilfunk, proposing to add SMS Cell Broadcast to the UMTS phase 1services.


Comments in SMG#27: Information on capacity etc. is essential for the work on stage 2 and 3.

Decision of SMG#27: The document should be further processed in SMG1.

Service Continuity and Provision of VHE via GSM/UMTS: SMG1 is drafting a Stage 1 specification on Virtual HomeEnvironment, to be contained in UMTS 22.20.

UMTS 22.70, Virtual Home Environment, approved at SMG#25, the Report on VHE, is not being progressed at thisstage.

Clarifications in SMG#27: It was clarified that there is a good co-ordination with other ETSI activities on VHE (taskforce on VHE installed by OCG).

Multi-Media: A first joint meeting on multi-media between SMG1, SMG4 and SMG12 had been held. At this meetingthere have been essentially 3 schools of thought:

• Companies in favour of standardising ITU H.323 multimedia solution, designed tooperate in a packet switched environment, e.g. Motorola, Bosch, … It was alsonoted that TIPHON supports this solution.

• Companies in favour of standardising ITU H.324 multimedia solution, designed tooperate in a circuit switched environment, e.g. Siemens, …

• Companies against standardising a specific technology, but in favour ofstandardising a set of generic bearers associated with a range of QoS parametersin order to accommodate above standards in a flexible manner, hence having aminimal impact on the network. Companies supporting this approach are Ericsson,Nokia, Telia and Siemens, …

The joint meeting had defined work items on multimedia messaging and on real time multimedia.

SMG1 reported to SMG#27 that they would welcome guidance on whether to follow all three of the above approaches orto select just one or two of these.

SMG#27 concluded later in the meeting that the approval of Work Items proposed by SMG4 (see section 7.4.1) givesenough guidelines.

7.2 SMG2The UMTS relevant parts of the SMG2 status report to SMG#27 in Tdoc SMG P-98-706 were presented by the SMG2Chairman, Niels Peter Skov Andersen. The SMG2 status report was approved by SMG#27, cf. section 6.2.

7.2.1 General

Following the decision of SMG on the UMTS Terrestrial Radio Access (UTRA) summarised inTdoc SMG P-98-039 (SMG#24bis), SMG2 had continued the work on the refinement of the selectedconcept. The SMG2 proposal of the radio access part of IMT-2000 was presented to SMG#26 inTdoc SMG P-98-391 and Tdoc SMG P-98-390 contained a list of IPRs updated until 22 May 1998 (forinformation). SMG/ETSI had provided UTRA as a candidate for IMT-2000 to ITU by June 30, 1998.

7.2.2 Evaluation report to ITU-R

In the period after SMG#26, SMG2 had - as earlier mandated by SMG - elaborated the self-evaluation report of UTRArequired by ITU. This Self-evaluation report to ITU was sent to ITU by September 30 1998. Tdoc SMG P-98-714contains information on how to access and obtain an electronic version of the evaluation report. The evaluation reportwas also made available in electronic form during SMG#27 and will be on the SMG#27 CD ROM.

In addition to the contributions on evaluation of UTRA, SMG2 had received an evaluation report on IMT-2000 candidateUWC-136 for commenting. SMG2 had noted that parts of the UWC-136 proposal are similar to techniques under study inSMG2 and that the evaluation report for these parts seems reasonable. These observations had been forwarded to ITUtogether with the evaluation report.


7.2.3 UTRAN work plan

As earlier reported in order to provide the standard for the UMTS Terrestrial Radio Access Network (UTRAN) part ofUMTS, SMG2 have decided that the work should consist of the following events and phases:

• A first phase is to elaborate technical descriptions and evaluate performance ofthe final solutions of UTRAN. This phase is concluded with a detailed descriptionof UTRAN including the mobile station. This includes all radio protocolsterminated in UTRAN, the UTRAN internal protocols and the Iu interface as wellas descriptions of the functionality requirements of the network nodes and in theterminal. It should be the goal to complete this phase ultimo 1998.

• A second phase would be to write the actual specifications/standards based on thematerial elaborated in the first phase. It should be the goal to freeze thespecifications/standards ultimo 1999.

• The third phase is the iterative correction phase, where the specification/standardis corrected based on the experience gained with the standard during developmentand implementation of UMTS. This phase in principle never ends, but shouldconsidered done ultimo 2001.

• The fourth part would be further development of UMTS towards the UMTS phase2 to be introduced 2005. This work can be commenced primo 2002.

Clarifications/Comments at SMG#27:

• It was clarified that a delay is not visible in this SMG2 work plan.

• It was commented that a more detailed information on the UTRA groups in SMG2should be given to SMG.

7.2.4 SMG2 UMTS groups

Work has continued in the four ad hoc groups (see Annex 8).

7.2.5 Specification structure

To get all UTRA descriptions finalised during 1998, a detailed work plan for the UMTS documentation in SMG2 hadbeen agreed. SMG2 had identified a number of documents for the description of UTRAN. Some of these documents areexpert group internal documents, and some will be SMG2 deliverables for end 1998 (“The UTRAN description”documents). Below the identified documents are listed (with temporary document numbers). These descriptions will beused as the basis for the specification work during 1999. It is the plan that before the specification work start, thecorresponding UTRA description should be under change request control. This implies that all descriptions must beapproved and put under change request control during 1998. When a document is put under change request control, thechanges are “per item” based.


UMTS-L1 Document Document titleXX.01 UTRA layer 1 documentation planXX.02 UTRA physical layer - general description*XX.03 UTRA FDD, Transport and physical channels descriptionXX.04 UTRA FDD, multiplexing, channel coding and interleaving descriptionXX.05 UTRA FDD, spreading and modulation descriptionXX.06 UTRA FDD, Radio transmission and reception descriptionXX.07 UTRA FDD, physical layer procedures descriptionXX.08 UTRA FDD : additional features and option descriptionXX.09 UTRA TDD : transport channels and physical channels descriptionXX.10 UTRA TDD, multiplexing, channel coding and interleaving descriptionXX.11 UTRA TDD, spreading and modulation descriptionXX.12 UTRA TDD, Radio transmission and reception description*XX.13 UTRA TDD, Physical layer procedures descriptionXX.14 UTRA TDD, additional features description*XX.15 UTRA handoverXX.16 UTRA inter operability descriptionXX.17 System scenariosXX.18 UMTS layer 1 documentation status and study itemsXX.19 UTRA Link level simulations results*XX.20 Collection of UTRA system level simulation resultsXX.21 UTRA MS capability*

Title ScopeYY.01 MS-UTRAN Radio Interface

Protocol ArchitectureThis document contains :1. a layered view of the radio interface1. the services of each (sub-)layer, with service primitives1. the functions of each (sub-)layer and functions of correspondingprotocol1. the termination point of protocol entities

YY.02 Layer 1 : general requirements andservices

This document contains :1. services of the physical layer1. interfaces to the physical layer (primitives)1. description of transport channels1. performance requirements

YY.03 Description of procedures in RRCconnected mode

This document contains the principles and procedures for the RRC connectedmode

YY.04 Description of procedures in idlemode

This document contains the principles of the MS behaviour and procedures whenin idle mode.

YY.31 Description of RRC protocol See definition of « description document »YY.22 Description of RLC protocol See definition of « description document »YY.21 Description of MAC protocol See definition of « description document »

Document EditorWork Plan, SMG2 UMTS-ARC Chairman

ZZ.01 UTRAN Architecture Description Nortel / Jean-Marie CalmelZZ.02 UTRAN Functions: Examples on

Signalling ProceduresCSELT / Flavio Piolini

Requirements Relevant for UTRANArchitecture

Ericsson / Björn Ehrstedt

Manifestations of Handover andStreamlining

BT / Richard Townend

ZZ..11 Description of Iu interface Nokia / Atte LänsisalmiZZ.12 Description of Iur interface Ericsson / Björn EhrstedtZZ.13 Description of Iub interface Lucent / Urs Bernhard

7.2.6 Liaisons

ERC TG1: ERC TG1 SMG2 has answered to a LS from ERC TG1, see section 5.1. In the mean time their meetings havebeen opened for participation of SMG2 experts, and SMG2 delegates will participate so that an information transfer(earlier via liaison Statements) has been improved.


TC ERM: Simon Pike presented a draft Liaison Statement to TC ERM in Tdoc SMG P-98-611, System description ofUTRA, informing ERM about the progress of SMG work on UTRA. It was approved by SMG#27.

7.2.7 IMT-2000 RTT harmonisation and convergence

Tdoc SMG P-98-564, Recommendation for Pursuit of Convergence of Radio Access Standards within ETSI, source:QUALCOMM Europe, was presented by Ron Foerster. The document recommends

(1) to establish as a high priority and work toward convergence of the W-CDMAand cdma2000 Radio Access standards;

(2) to form a Convergence Working Group;

(3) the new Convergence Work group to produce a report by the end of 1998which summarises the open convergence issues, and contains a plan for theirresolution in early 1999.

This document argues, among others, SMG2 members to have shown too little interest and no results in harmonization ofIMT2000 RTTs.

Annex 1 reminds that Qualcomm previously proposed SMG to set up a convergence experts group in June of 1998.

Annex 2 is a letter from the CDMA Development Group to US Senator John McCain endorsing convergence of, anddetailing the benefits of, IMT2000 RTT harmonisation, specifically cdma2000 and W-CDMA.

Annex 3 is a summary of the Qualcomm IPR Position. It quotes the letter to ETSI, dated August 5, 1998, in whichQUALCOMM stated

• that it is "not prepared to grant irrevocable licenses under IPRs on terms andconditions in accordance with Clause 6.1 of the ETSI Interim IPR Policy."

• that, however, QUALCOMM continues to work with ETSI and its members aswell as other bodies world-wide on convergence of cdma2000, proposed byQUALCOMM and other members of the CDMA Development Group, and W-CDMA.

• that QUALCOMM would not agree to license its IPR for the W-CDMA standard.

• that QUALCOMM would license its CDMA IPR on fair, reasonable and non-discriminatory terms only for standards meeting a set of technical criteria basedon three fairness principles:1. A single converged world-wide CDMA standard should be selected for 3G;2. the converged CDMA standard must accommodate equally the two dominant network standards

in use today (IS-41 and GSM-MAP);3. disputes on specific technological points should be resolved by selecting the proposal that either

is demonstrably superior in terms of performance, features, or cost, or, in the case ofalternatives with no demonstrable material difference, the choice that is most compatible withexisting technology.

Annex 4 lists QUALCOMM’s contributions to SMG2-L1 since May 1998 (13 documents).

In a two hour discussion on this subject, many members (including Peter Adams, British Telecom; Alan Cox, Vodafone;Akio Sasaki, ARIB; Chris Friel, Cellnet; Alistair Urie, Alcatel; Simon Pike, Lucent; Linda Melvin, N. American OperatorCommunity; Paola Tonelli, AirTouch) strongly commented in favour of convergence, in particular to resolve outstandingIPR issues.

Differing opinions on the appropriate forum for those discussions were expressed. The following were all suggested:

• ITU-R;

• a working group within SMG2;

• generally outside of ETSI, e.g., by arbitration from outside.


Discussion at SMG#27: The SMG2 Chairman, Niels Peter Skov Andersen, pointed out that Qualcomm delegates hadaccepted SMG2 conclusions and did not object them. Further views expressed in SMG#27:

• The importance of time schedules was stressed.

• It was reported that Qualcomm contributions were treated in the same way as allother contributions, however Gunnar Sandegren commented that Qualcomm's IPRblocking policy makes it very difficult to include contributions from Qualcomm inthe UMTS standards.

• Pressure with IPR for changing technical parameters was criticised.

• Joint Motorola and Nokia results (introduced in Tdoc SMG P-98-779) werequoted concluding that for dual mode terminal implementations, complexity dueto two chip rates etc. to be insignificant, the real issue being the added complexityand cost in RF due to different frequency allocations and bandwidths. Based onthe result Nokia and Motorola were also proposing new topics for harmonization,that would have a greater impact to the terminal, than the issues discussed earlierlike chip rate etc..

• Peter Adams commented the correct place to achieve convergence between thedifferent W-CDMA systems for IMT-2000 to be in ITU-R TG 8/1.

• Akio Sasaki, ARIB, reported on the work of ARIB’s Coordination Groups (CG),Ad Hoc CR and Ad Hoc S, towards harmonization of IMT2000 RTT’s. A reportsummarizing ARIB and TR45.5 harmonization activities between cdma2000 andW-CDMA, started in June 1997, was included. ARIB’s CG requests ETSI SMG,TIA and TTA to facilitate coordination between each other to achieve a singleworldwide common (CDMA) standard including choice of the chip rate. SeeTdoc SMG P-98-641.

• The view was expressed SMG to have achieved already a high degree ofharmonisation.

• It was stated that SMG is not a proper forum for negotiation on IPR issues.The SMG2 Chairman Niels Peter Skov Andersen commented that from the discussion of the contribution(Tdoc SMG P-98-564) from Qualcomm, it is clear that SMG wants to continue harmonisation and convergence of RTTs.However, as indicated by Qualcomm the handling of the harmonisation and convergence issues on an per technical itembasis, has shown not necessarily to be the optimum way forward.

On this background, the SMG2 Chairman proposed:

Proposal: Next SMG2 plenary (16 - 20 November 1998) will have a separate agenda item on harmonisation andconvergence, where an analysis of the whole field in a top down approach is done, noting that this as normally would be acontribution driven process.

Ron Foerster agreed with this proposal with some caveats.

Caveats:

1. that sufficient time is allocated in the SMG2 meeting

2. SMG#27 to reconfirm the decisions of SMG#26 on the intention of convergence of theproposed IMT 2000 CDMA standards.

3. To encourage ETSI members and other parties working in the field of IMT 2000(including members of ARIB, TIA, TTA and T1) to participate in the discussion at thatmeeting.

SMG#27 agreed with these caveats. The SMG2 Chairman commented that it would be possible to allocate sufficient timeat the next SMG2 plenary, as non urgent items may be postponed to the following SMG2 plenary in January if necessary.


Rémi Thomas proposed that under these circumstances, Qualcomm should review their position on IPRs. Ron Foersterstated that this has to be discussed in the company.

It was clarified that since some time by a formal agreement, participation in SMG2 meetings on IMT 2000 related issuesis open to TIA, ARIB, TTA, T1 delegates.

The SMG Chairman Fred Hillebrand commented that TIA delegates had been invited to and had participated in the lastSMG2 plenary.

7.2.8 Other issues

TDD mode: Fred Harrison presented Tdoc SMG P-98-765, The use of UTRA in TDD mode in the unpaired frequencybands, source BT, emphasising the importance to support the elaboration of the TDD mode.

ITU-R Task Group 8/1 Activities: Pamela Davidsson presented Tdoc SMG P-98-777, Guidelines for a CEPT positionon the ITU-R TG 8/1 process for defining IMT-2000 recommendations, source (Swedish) National Post & TelecomAgency.

Clarifications at SMG#27:

• It was explained that the document aimed at provision of guidelines for theTelecom administrations and of European delegations for a commonunderstanding at the next TG8/1.

• The annexes of the document have not been approved by TG1, because they wereseen to be outside of the mandate of CEPT.

SMG#27 noted the document. Delegates can study the document and approach their national administrations for comments.

David McFarlane introduced Tdoc SMG P-98-729, IMT.KEY Contribution to ITU-R TG 8/1, source Nokia and UK,proposing proposes a structure and text for a Draft New Recommendation on Key Characteristics for the IMT-2000Radio Interfaces (IMT.RKEY).

The document advocates the family approach; concerning the technical details, it seems to be inline with the SMG2 work.

The document, presented for information to SMG#27, was noted. Delegates supporting the paper should contact theirrepresentatives in TG8/1.

Stuart Cooke, the newly appointed ITU-R Co-ordinator for SMG (cf. section 5.4), presented a report on ITU-R activities,see Tdoc SMG P-98-637.

He reported that the next meetings are critical because they will determine the direction of the ITU TG8/1 IMT-2000radio interface development process. Participation will be important to ensure that UTRA, as submitted and furtherrefined by SMG2, is recognised as an IMT-2000 RTT. It was suggested that a large and active participation of SMGmembers is required. These meetings are as follows:

• 4-6 November 1998, London: ITU-R TG8/1 Working Group 5 - Development ofthe IMT-2000 Radio Interface(s);

• 9-20 November 1998, Jersey: ITU-R TG8/1. An IMT-2000 Workshop will be heldon the 10-11 Nov in Jersey.

• 1-12 March 1999, Brazil: ITU-R TG8/1

• It was reported 15 Technologies have been submitted, 10 of which are terrestrial.It is an objective of TG8/1 and WG5 to encourage the reduction of the number oftechnologies through consensus. It was anticipated that the family concept will bedeveloped further.

• A close dialogue and common understanding with the European nationaldelegations is important and SMG and its members should encourage the


European delegations to develop a common understanding in promoting UTRA asan IMT-2000 SRTT (or RTT).

SMG#27 noted Tdoc SMG P-98-777 and Tdoc SMG P-98-729 and encouraged members to examine these documents andlet their views be known to their respective national administrations.

Global 3rd generation terminal: Teuvo Järvelä presented Tdoc SMG P-98-779, On the implementation of a global 3rdgeneration terminal, source: Motorola and Nokia. It was noted by SMG#27. The paper argues, for dual mode terminalimplementations, complexity due to two chip rates etc. to be insignificant, the real issue being the added complexity andcost in RF due to different frequency allocations and bandwidths. This document is also proposing new topics forharmonization, that would have a greater impact to the terminal, than the issues discussed earlier like chip rate etc. It wasnoted, that the document had been introduced also at the previous SMG2 Plenary including the proposals for newharmonization topics.

7.3 SMG3The UMTS relevant parts of the SMG3 status report to SMG#27 in Tdoc SMG P-98-717 were presented by the SMG3Chairman, Harald Dettner. The SMG3 status report was approved by SMG#27, cf. section 6.3.

SMG3 is reviewing UMTS specifications including UMTS 30.00, UMTS 30.01, UMTS 22.00, UMTS 23.01 GeneralUMTS Architecture, UMTS 23.10, UMTS 23.20, UMTS 23.30 and the draft specification on Description of Iu Interface.

Pre-paging in UMTS: This is a requirement by the Japanese TTC for the support of pre-paging in UMTS Phase 1. Abroad range of features was identified already on the meeting which would benefit from such a mechanism. SMG3 willstudy the proposal.

Gateway Location Register in the UMTS core network: SMG12 had endorsed a proposal to include appropriate textin UMTS 23.20. Contributions are required. NEC is planning a new WI description for SMG12. SMG1 and SMG3 wererequested to continue analysis of such a new entity between HLR and VLR or between HLR and SGSN.

Interaction between MExE and GSM/UMTS Networks: Exchange of capabilities between the terminal and thenetwork, in both direction, is needed to ensure a proper handling of interaction between the network and the terminalservices. It had been concluded that this information should be stored in the network. SMG3 will give guidance on thisstorage. Another issue is the protocol to be used in the network for direct communication. This is an issue for the futurediscussion on CAMEL Phase 3.

Organisation of UMTS work in SMG3: An SMG3 ad-hoc meeting on UMTS is planned on 18 to 20 November 1998 inHelsinki, hosted by Nokia. The goal of this meeting is to get SMG3 more involved in UMTS. Issues for this meeting arethe TTC proposals, MExE, work split, protocol (GSM 04.08/GSM 09.02) evolution towards UMTS.

In summary, SMG3 is just starting its activities on UMTS. The SMG3 Chairman pointed out that SMG3 needs a stabilisedenvironment in terms of requirements (e.g. UMTS 22.00) and architecture (e.g. UMTS 23.20) to organise work on UMTS.

7.4 SMG4The UMTS relevant parts of the SMG4 status report to SMG#27 in Tdoc SMG P-98-775 were presented by the SMG4Chairman, Kevin Holley. The SMG4 status report was approved by SMG#27, cf. section 6.4.

7.4.1 General

SMG4 had started work on UMTS 21.04, Requirements for the support of data services in UMTS, which identifies someof the work required in SMG4 for the support of data services. The report covers UMTS changes required for the supportof fax, store and forward fax, applet fax end to end, applet fax with interworking, data services (modem access, internetprotocol, services of internet protocol), SMS (GSM SMS, UMTS SMS base level, UMTS SMS advanced, SMS routing),and Cell broadcast. The work on this document is currently on hold pending greater clarity in the detailed structure ofUMTS, although it is likely to be updated for SMG#28.

SMG4 have also prepared UMTS Work Items for approval at SMG#27, see section 7.4.2.


7.4.2 New work items

The following work items in Tdoc SMG P-98-775 were approved by SMG#27:

• Support of non-realtime Multimedia Messaging Service

• Multimedia in UMTS

• Study on provision of facsimile services in GSM and UMTS

• Work Item Description for MExE Release 99

7.4.3 Standardising embedded applications in UTMS

Kevin Holley presented Tdoc SMG P-98-567, STANDARDISING EMBEDDED APPLICATIONS IN UMTS, Source:SMG4 Chairman, to SMG#27. This document has not been seen by SMG4. Kevin Holley wrote it on suggestion of theSMG-CG. The document addresses the philosophies to standardise

• “generic bearers” with the objective of avoiding limitations in upgrading theUMTS network for future applications

• teleservices, including entities like codecs.It argues that the GSM bearer services are in general under-used for many reasons, mostly to do with usability andavailability of applications.

The document invited SMG to examine the following two heterogeneous positions:

1. The market for UMTS applications will start and grow without the need for standardisedapplications. Different needs will be fulfilled by a variety of implementations. In the first few yearsusers will experience extreme difficulty with trying to communicate using an application which isnot supported on the other party’s terminal. Operators can provide downloadable applications butto do this will require a much higher level of training for Customer Care operators than is the casetoday. Eventually the market will settle on the most appropriate solutions.

2. The market for UMTS applications is dependent on a common set of basic embedded applicationswhich provide something better than “standard” facilities on today’s mobiles, for example videotelephony, text telephony, email capability, fax capability. SMG needs to identify the appropriateembedded applications and mandate support of particular standards (pre-existing or new standards)in various classes of mobile.


• Some views in support of approach 2 were expressed.

• Development in TIPHON was quoted (where there is no standard codec).

• Armin Toepfer indicated interest of the GSM MoU.

• Another view was that activities as in approach 2 can be performed outside ofETSI.

Based on further discussions in a side meeting of SMG#27, Kevin Holley proposed later in the meeting thatTdoc SMG P-98-567 should be modified in accordance with the discussion in SMG#27; the revision inTdoc SMG P-98-791 will be sent out for agreement by correspondence.7 The document will suggest that a new email [email protected] is set up on the ETSI email reflector and that this will be used as a virtual meeting to agreeapplication related elements for inclusion in the standardisation process. Kevin Holley will co-ordinate the activity on thelist.

This proposal was approved by SMG#27.

7 After SMG#27, the revision of Tdoc SMG P-98-791 in Tdoc SMG P-98-793, taking into account all comments received, has been agreed bycorrespondence by SMG.


7.5 T1P1 matters on IMT 2000T1P1 is working on WIMS W-CDMA (TIA TR46) and W-CDMA NA harmonization. Steven Hayes indicated that therewas not more to report.

7.6 SMG6SMG6 are progressing their work, however nothing needs to be reported.

Tdoc SMG P-98-613, Importance of Standardising O&M in UMTS, source Vodafone, MMO, Cellnet, Telia, waspresented by Alan Cox. This paper asks SMG6 to start and complete their work on an open Iub interface.

SMG#27 decision: SMG#27 asked SMG6 to start work on the Iub interface and to prepare a work item description and awork plan (including the necessary liaisons).

7.7 Reports from UMTS FORUM, 3 GIG, Progress report onIPR issues

7.7.1 UMTS Forum

Alan Hadden, Programme Manager, stated that the UMTS Forum GA approved at its September 1998 meeting the releaseof four new reports:

• Report #2, The Path towards UMTS: Technologies for the Information Society

• Report #3, The impact of Licence Cost levels on the UMTS business case

• Report #4, Consideration of Licensing Conditions for UMTS NetworkOperations

• Report #5, Minimum Spectrum Demand per Public Terrestrial UMTS Operatorin the Initial Phase

Printed copies of these reports, as well as Report #1, A Regulatory Framework for UMTS (published June 1997) can beobtained on application to the UMTS Forum secretariat.

With the release of these reports Fred Hillebrand noted that he believed that Administrations now have sufficientinformation and material on which to base their licensing policies and actions.

With the completion of this phase of its work, the UMTS Forum has initiated a period of reflection about its future roleand tasks. A study group “Quo Vadis” has been established and has had its first meeting. First provisional indications arethat the future direction of the UMTS Forum could focus on three broad areas:

• Promotion of the UMTS Vision on a global basis

• Service Portability and Interoperability issues, in particular in support of VHE

• Building bridges to the ICT and Content ProvidersQuo Vadis will deliver its report to UMTS Forum GA in early December.

7.7.2 3GIG

Armin Toepfer presented the 3rd. Generation Interest Group Report in Tdoc SMG P-98-771 on behalf of the 3GIGChairman, Neil Lilly.

Activities:

3GIG will present the following permanent documents to GSM MoU Plenary (next week) for approval:


• TG.34,

• TG.36,

• TG.50, Technical Requirements for Operations Support,

• TG.60, Technical Migration of GSM to 3G,

• TG.70, 3G Terminal Certification Requirements.All PRDs now on http://www.gsmworld.com. Over 22000 document downloads occurred in the first 10 weeks.

3GIG - SMG co-operation

• Good co-operation between 3GIG and most SMG STCs - requirements / conceptsare usually accepted

• But cause for concern in SMG12 … manufacturers are rejecting MoUrequirements (“no time to consider …”)

• Likely consequence - the UMTS standards in 2002 could fall short of operatorrequirements

Future activities

• In a general restructuring of GSM MoU working groups, all existing groups will bedisbanded and 4 new working groups will be installed. 3GIG has completed itsmajor task - the PRDS will now be taken over by other WGs.

• MoU is now evaluating its WG structure with a view to rationalisation

• 3G activities will become more strategic

• Future 3G reports to SMG plenary will come from the MoU, rather than 3GIG.Discussion in SMG#27: As a response to 3GIG report stating some concerns related to co-operation with SMG12,SMG12 co-chair, Teuvo Järvelä explained what had happened at the SMG12 meeting related to the 3GIG input. Heapologised that the handling of 3GIG input was not felt to be sufficient, and promised to carry it over (Tdoc SMG1298S833) to the next SMG12 Plenary to be handled again.

7.7.3 Progress report on IPR issues

7.7.3.1 Report from ETSI legal adviser

Stéphane Tronchon, ETSI legal adviser, presented the Report on Essential IPRs declared in relation to the work ofSMG#27 in Tdoc SMG P-98-786 (revision of Tdoc SMG P-98-732), including references of IPRs which have beennotified to ETSI as being essential to UMTS by 9 October, 1998.

Note: All references pertaining to essential IPRs declared to ETSI are publicly availableon the ETSI web site http\\www.etsi.fr.

7.7.3.2 IPR Statements of QUALCOMM

The following statements were made at SMG#27 by Dr. Ronald Foerster, Managing Director of QUALCOMM EuropeSARL and Sr. Vice President of QUALCOMM Inc.:

"The UMTS IPR issue is a very serious matter, and is getting more serious as time passes. Little progress has been madesince the last SMG Plenary meeting in June, 1998 related to QUALCOMM's IPR position. This lack of progress is due tono progress of technical work toward the convergence of the Radio Access aspects of the W-CDMA and cdma2000standard proposals for third generation IMT2000. QUALCOMM's IPR position is that the company will only license itsextensive IPR on fair, reasonable, and non-discriminatory terms for a converged W-CDMA/cdma2000 standard.Otherwise it will only license its IPR for cdma2000 systems. The converged standard will equally support bothGSM/MAP and ANSI-41 networks without compromising performance.


Because of this lack of progress toward convergence of the W-CDMA and cdma2000 standards, QUALCOMMhas sent a letter to the ITU outlining its IPR position. This position is summarised in TDOC SMG 601/98. QUALCOMMhas also withdrawn from the UMTS IPR Working Group since this group is not the right group to work on convergence,and until meaningful work on convergence happens, QUALCOMM has nothing to contribute to this process.

Convergence of W-CDMA and cdma2000 is receiving increasing support from around the world outside ofEurope. It is recognised as not only a solution to the IPR issue, but also a way to get the best standard for the industry anda method to resolve trade and other issues which are surfacing within the US and European governments.

QUALCOMM recognises that ETSI cannot resolve IPR licensing issues between companies. However,QUALCOMM believes that ETSI must work toward standards, which are free of IPR issues. Without resolution of thisissue, both ETSI and the ITU, according to their own rules, must stop working on a standard that cannot becommercialised on an open basis.

QUALCOMM will introduce a contribution TDOC SMG 564/98 which proposes a way forward onconvergence. We hope that all members of the SMG Plenary will review this contribution and endorse it."

See also section 7.2.7.

7.7.3.3 UMTS IPR Working Group

Alistair Urie presented Tdoc SMG P-98-608, Interim Report of the UMTS IPR Working Group (September 1998),source: UMTS IPR Working Group.

Following SMG#24bis, this group, chaired by B. Kearsey, Alcatel, has defined three approaches for handling the IPRissues for third generation mobile systems (Option 1 : ETSI IPR Policy; Option 2 : Patent Pool; Option 3 : Patent Forum).

As a next step the UMTS IPR WG will catalyse an Industry Reflection Period (October – December 1998) for furtherposition finding.

7.8 UMTS program managementUMTS 30.01: SMG#27 decided to change the scheme for updating UMTS 30.01: the version representing the decisionsof last plenary shall be approved in a similar process as the meeting report.

CR UMTS 30.01-A001 in Tdoc SMG P-98-782: SMG#27 decided that a revision of the CR should be sent in the week19-23 October, 1998 to SMG for agreement by correspondence. The revision shall be to add the results of the extra-ordinary GA on 3GPP.

UMTS 30.00: An update of the UMTS work program will be issued 10 days after the approval of the SMG#27 report.

UMTS document structure: See section 5.6.1 on activities of WOME, and the note in section 5.6.1 on a side meetingduring SMG#27 on the issue.

Tdoc SMG P-98-569, Guidelines for the Planning, Development and Documentation of UMTS Phase 1 Standards,source BT, was presented by Steve Mecrow. He explained the contribution to be based upon the assumptions that Phase 1UMTS will be based upon a GSM release 99 core network in conjunction with the UTRAN, and that UMTSspecifications will be documented separately from GSM. The contribution had already been submitted to SMG1; it hasbeen submitted to SMG in view of the issues being of a broader nature than SMG1.

The key views highlighted during the presentation were:

• The services supported by UMTS phase 1 to be similar to those of GSM release 99(as a result of using the GSM Core Network) and therefore the Service Capabilityspecifications currently under development within SMG1 to represent a statementof the capabilities that UMTS Phase 1 will deliver, rather than a statement ofrequirements for a “top down” design process;

• the developments required for specifying the UMTS Phase 1 network (interfaces,protocols) to be largely as a result of adopting the UTRA in place of the GSM airinterface.


The key requirements highlighted during the presentation were:

• The SMG Project Team in conjunction with individual SMG groups shouldanalyse the existing SMG work programme with a view to identifying aspects ofexisting works items that are specific to UMTS, the need for new UMTS specificwork items, and the dependencies between the work items to ensure UMTSspecifications are available by end 1999.;

• The UMTS specifications should be documented separately from those for GSM.Steve Mecrow concluded that, in view of the recent decisions within the GA relating to the establishment of the 3GPP, theabove guidelines and observations will be of relevance to the future work of both the 3GPP and the new SMG.

During discussion the following points were raised:

• In order to achieve the goal of no duplication of work, the common parts of GSMand G-UMTS should be described in common specifications.

• Alan Cox reported that in an earlier NA2 meeting, it was preferred to base UMTSSupplementary Services (SS) on GSM SS rather than ISDN SS.

• Section 2 has been treated in the 7.2 slot. Section 3 will have a value in thedocuments coming after next GA. Section 4: More intensive program managementis of course needed; but the PT SMG resources are unclear. Section 5: Referenceto a meeting on document structure on 14 October 1998 (side event of SMG#27)evening was made (see section 5.6.1). The handling of the section is premature.

• The document should be treated when 3GPP has been created.SMG#27 concluded that all points required in section 2 are covered in the SMG work and therefore noted Section 2.

Section 3: The view of BT is that the progressing of work needs to be structured in the following way:

• Changes to GSM Release 99 network standards needed as a result of using theUTRA;

• Enhancements to GSM Release 99 standards as a direct consequence of specificUMTS service/capability requirements, as determined by SMG1, that can beaccommodated within GSM Release 99.

It was commented that in this view, fixed mobile convergence is not mentioned, that an integrated approach is missing.Section 3 was noted by SMG#27.

Section 4: It is proposed that the SMG Project Team, in conjunction with individual SMG groups, analyse the currentSMG Work Programme with a view to identifying:

∗ aspects of existing SMG work items that are specific to UMTS;∗ the need for new UMTS specific work items;∗ the dependencies between these works items and the dates for their completion to ensure UMTS

standards are available as planned (end 1999).It was clarified that these points are covered as there is 30.00, the UMTS work program, as SMG approves UMTS workitems and maintains the dates for completion. Also, WOME#3 has discussed (with the participation of BT) the question ofseparated and integrated work programs for GSM and UMTS and had proposed to SMG#27 that the tools shall allow toproduce both an integrated and separate representations of the work program; SMG#27 had approved this proposal.

It was explained that improvements of the work methods are discussed in WOME (where BT is participating).

Section 5: It was reminded that WOME has taken the working assumption that the UMTS specifications should be a self-contained set of specifications (for the educated reader) with the possibility to refer to other specifications.


7.9 SMG9Klaus Vedder presented Position Paper on the UICC for early UMTS systems, a Liaison Statement from SMG9 to SMGin Tdoc SMG P-98-668, p.14. Later in the meeting, a modification of the third paragraph was prepared. The resultingTdoc SMG P-98-624 was approved by SMG#27. It shall be included in UMTS 30.01, the UMTS Baseline Document.Tdoc SMG P-98-624 is quoted below (with the modification to replace “SMG9” by “SMG” in the last paragraph):

Begin quotation:

SMG have been looking at the requirements for the UMTS (Third Generation) USIM,noting particularly, the requirement that UMTS evolves from GSM. As part of theevolutionary approach from GSM to Third generation systems, it is a requirement that3G terminals support existing (Phase 2) SIMs (at three volts, but not five volt SIMs),but it is not a requirement that GSM terminals support 3G USIMs. It is the strongopinion of SMG that the UICC (UMTS Integrated Circuit Card) is a mandatoryelement of Third Generation systems.

It is recognised that the existing physical interface should remain unchanged (toaccommodate the need for interworking with GSM), however, that there may be theneed to enhance the interface, both in terms of protocol (for example, employing theT=1 protocol), and speeding up the bit transmission rate across the interface.

It is recognised that the existing two physical sizes may prove to be limiting to mobileequipment (ME) designs for 3G mobiles, so consideration is being given to a thirdphysical size of SIM, (e.g. a cut down version of existing "Plug-in" SIM, withoutaffecting the existing mandatory physical interface). The UICC / terminal interfaceremains mandatory.

The other important feature of the SIM is the SIM Application Toolkit; this is apowerful tool for operators, and can be easily exploited and enhanced for 3Goperations, especially in the area of Virtual Home Environment. Allied to this is thesecurity for the Toolkit, where end-to-end messaging between the Application area inthe SIM and its partner entity in, or behind, the network, can be secured, to preventfraud or interception. Enhancements exploiting newer bearer services will be includedfor the Toolkit.

The next generation SIM will be a multi-application card, including support forapplication loading; SMG fully expect this work to be completed and approved in June1999.

It is the opinion of SMG that the existing SIM technology and functionality is an idealbaseline platform for early third generation systems; it is recognised that there will ofnecessity be alterations and additions to the file structure in the existing SIM toaccommodate UMTS functionality, but this is believed to be easily undertaken.

End quotation.

7.10 SMG10The UMTS relevant parts of the SMG10 status report to SMG#27 in Tdoc SMG P-98-531 were presented by the SMG10Chairman, Mike Walker. The SMG10 status report was approved by SMG#27, cf. section 6.10.


UMTS 33.20, UMTS Security Principles version 3.1.0 as a CR in Tdoc SMG P-98-535; this version replaces thealready approved version 3.0.1 (old 09.01). It is a complete revision of the security principles for UMTS.


Therefore, SMG#27 noted the CR, asked SMG12 to review the specification for architectural issues and asked SMG10for presentation for approval at SMG#28.


UMTS 33.21, UMTS Security Requirements, version 1.0.0, in Tdoc SMG P-98-536, was presented to SMG#27 forinformation.

7.10.3 SMG10 work plan for UMTS

Scope of UMTS security

• All GSM security features

• Solution of all GSM security problems

• at least one new security featureExplanations of SMG10:

• This is not in line with UMTS 22.00 which foresees more, but seen as realistic inSMG10.

• Time schedules, when also consultation with SMG12 is included, risk to bedelayed, SMG10 is aware of this danger.

Role model: The removal of the role model in UMTS 22.01 was discussed in SMG10. SMG10 had already adopted anown role model in UMTS 33.20 which already referred to Home Environment and Serving Network.

UMTS 22.07: The CR from SMG1 to UMTS 22.07 was checked. The view on the USIM presence is forwarded to SMG1.

UMTS 33.21: The protection of the USIM-ME interface is indicated to SMG9. Other issues of study are: End-to-endsecurity and Security features for UMTS Phase 1. SMG12 is requested to deliver the requirements for UMTS Phase 1.UMTS 33.21 is forwarded to SMG#27 for information in Tdoc SMG P-98-536.

UMTS Work program : The work program for UMTS in UMTS 30.00 was checked. According to this work plan SMG10has to deliver the SMG10 related parts for UMTS Phase 1. It was found that a more detailed work plan for SMG10 isrequired.

For the moment the following planning was made:

UMTS 33.20: version 3.1.0 at SMG#27;

UMTS 33.21: version 1.0.0 at SMG#27; approval at SMG#28;

UMTS 33.22: version 1.0.0 at SMG#29; approval at SMG#30;

UMTS 33.23: version 1.0.0 at SMG#29; approval at SMG#30.

7.11 SMG11Kari Järvinen presented the UMTS relevant parts in Tdoc SMG P-98-700.

SMG11 has initiated co-operation with ARIB, as requested at SMG#26. ARIB are currently evaluating a short list of sixspeech codecs, G.729, GSM EFR, GSM AMR, MPEG4 (narrowband), IS.641, EVRC (IS127), in order to select a defaultspeech codec for W-CDMA. ARIB is planning to complete subjective tests on these codecs by February 1999. Seesection 7.11.1 for a liaison statement to ARIB.



SMG#27 endorsed the intended Liaison Statement on Collaboration on the evaluation of AMR for UMTS from SMG11to ARIB IMT-2000 Codec Work Group (cc: SMG, SMG2) in Annex 1 of Tdoc SMG P-98-700. It contains a proposal forthe Terms of Reference for the collaboration between ARIB and SMG11.

7.12 SMG12The UMTS relevant parts of the SMG12 status report to SMG#27 in Tdoc SMG P-98-734 were presented by the SMG12Co-Chairmen, François Courau and Teuvo Järvelä. The SMG12 status report was approved by SMG#27, cf. section 6.12.

Other issues: Tdoc SMG Tdoc SMG P-98-774, UMTS Phase 1 Issues from MoU SERG, Source: MoU GSMRepresentative in SMG, presented by Armin Toepfer, was noted; it should be studied by SMG12.


UMTS 23.01, General UMTS Architecture, V1.0.0 in Tdoc SMG P-98-754 was presented for information to SMG#27. Itis quite stable and foreseen for approval at SMG#28.

UMTS 23.10, UMTS Access Stratum; Services and Functions, V1.0.0 in Tdoc SMG P-98-755 was presented forinformation to SMG#27. The content is not fully stable. But completion is foreseen for SMG#28.

UMTS 23.20, Evolution of the GSM platform towards UMTS, V1.0.0 in Tdoc SMG P-98-758 was presented forinformation to SMG#27. It is not stable yet, but forwarded to SMG#27 for a full visibility.

7.12.2 Work areas

Iu interface: At the last meeting it was found that IWF between UTRAN and SGSN was very difficult to specify.Therefore several proposals were made. No decision has been made so far. One of the proposal is to use directly the Iutowards the SGSN. A decision is expected to be taken at the November meeting. Following the joint meeting with SMG2UMTS ad hoc several improvements have been incorporated in the Iu requirements report. Furthermore a protocolarchitecture split has been agreed that allows SMG2 UMTS groups to carry on their work.

It is expected that the report on Iu requirement, at least for the part concerning UTRAN will be provided to SMG forSMG#28.

Comments in SMG#27: SMG#27 confirmed the strong requirement to connect UTRAN to SGSN and for service continuityin packet mode between GSM and UTRA. This is planned to be achieved by an interworking function which is not trivial,as the functional split between access network and core network is different in GSM and UMTS.

Evolution of the GSM core network towards UMTS (UMTS 23.20): Since the April meeting of SMG12 majorprogress has been achieved. 19 different scenarios have been discussed and the main task is now to reduce this number byanalysing the commonalities and highlighting the differences in order to reduce this number. So far it remains only 10 ofthem. September 1998 had been the deadline for new scenarios.

François Courau and Teuvo Järvelä informed SMG#27 that, to let UMTS phase 1 in the Release 99 time frame happen,they will Chairmen propose the following as a way forward on UMTS Architecture (UMTS 23.20) to SMG12:

• The Scenario work has been fruitful in putting together opinions on how to evolveGSM towards UMTS and also identifying some key issues and differencesbetween opinions.

• It would be possible to define 2-3 main approaches derived from the existing 10scenarios

• Therefore it is proposed to define and concentrate the work on the key questions(MM etc.) arising from these scenarios (hopefully at the next SMG12 Plenary, Oct20-22).


• Detailed work can be started based on each of the agreed solutions, rather thanpossibly delaying the work of other STCs until the whole scenario is fixed.

In the discussion, goals like service continuity, seamless handover between GSM and UMTS, evolution from GSM toUMTS, in-time delivery of UMTS Release 99, an architecture that is not just beauty but also implementable, servicedifferentiation, where discussed. It was argued that it can be acceptable to have a limited number of evolution scenarios(or one scenario consisting of several options), and that SMG12 should have the hands free for very urgent work on theUMTS architecture to be used for Release 99 and is future proof and ready in time. It was also clarified that EP UMTSwill look to the long term aspects.

7.12.3 Work Items

The following work items were approved by SMG#27:

• UMTS Core based on ATM Transport (in Tdoc SMG P-98-759)

• Study on Combined GSM and Mobile IP Mobility Handling in UMTS IP CN(in Tdoc SMG P-98-760)

• Open Service Architecture (in Tdoc SMG P-98-761)

• IP-in-IP tunnelling in the GPRS backbone for UMTS phase 1 (inTdoc SMG P-98-780)

• End to End UMTS QoS Management (in Tdoc SMG P-98-781)SMG12 has created an internal document for planning of specification delivery. It is expected that it will be provided toSMG for information on a regular basis (as soon as validated information will have been incorporated). SMG12 hasagreed to approve a SMG12 Work Plan for 1999 at the November meeting.

8 Next meetingsMeeting No. SMG Co-ord. Group Plenary Date Plenary Venue

SMG#28 3 February 99AIRPORT CONFERENCE CENTERFrankfurt(Host: Siemens)

8 - 12 February 99 Milan, ItalyHost: Italtel

SMG#29 16 June 99

Stockholm, Ericsson

21 - 25 June 99 Miami, USAHost: GSM North America

SMG#30 13 October 99 18 - 22 October 99

SMG#31 February 2000

Frankfurt (Siemens)

February 2000

First 3GPP meeting (including TSGs): 7 - 8 December, 1998, Sophia Antipolis.

ETSI/SMG(98)4 Part B, Annexes 98/11/23

Annex 1: List of participants

Annex 2: Status of CRs and new Specifications presented tothe meeting

Annex 3: List of documents

Annex 4: Liaison statements

Annex 5: Status of SMG specifications after The meeting

Annex 6: Roadmap and WI status of GSM phase 2+ workitems after the meeting

Annex 7: PT SMG STATUS Report

Annex 8: Structure of smg and subgroups

Annex 9: Tokyo, 7-9 October 1998 ARIB, ETSI, T1, TTA andTTC agreed framework (Tdoc SMG P-98-574)

ETSI/SMG(98)4 Part B, Annex 1, Page 1 16/11/98

03-Nov-98

LIST OF PARTICIPANTS TO ETSI/TC/SMG#2712-16 October 1998, Praha

Name: ADAMS Peter.M. Tel 1: +44 1 473 227 684Company: BRITISH TELECOM Tel 2:

Address: PP2-02 Bibb Way Mob : +44 802 471 234IPSWICH Fax 1: +44 1 473 227 884SUFFOLK IP1 2EQ Fax 2:UNITED KINGDOM

E-Mail Internet: [email protected]

Name: ALARD Michel Tel 1: +33 1 4629 0802Company: WAVECOM Tel 2:

Address: 39 Rue du Gouverneur General Eboué Mob : +33 0734 1064Fax 1: +33 1 4629 0808

92130 ISSY-LES-MOULINEAUX Fax 2:FRANCE


Name: AMARA Elie Tel 1: +33 1 41 97 67 41Company: CEGETEL Tel 2:

Address: Tour Cèdre - Faubourg de l'Arche Mob : + 33 6 09 16 80 897, Allée de l'Arche Fax 1: +33 1 56 37 27 4892677 COURBEVOIE CEDEX Fax 2:FRANCE


Name: AMMER Gerhard Tel 1: +49 89 95086 312Company: LUCENT TECHNOLOGIES Tel 2:

Address: Medienallee 6 Mob : +49 172 976 7892Fax 1: +49 89 95086 255

85774 UNTERFÖHRING Fax 2:GERMANY


Name: ANDERSEN Niels Peter SkovSMG 2 Chairman - SMG 2 WPB Chairman - SMG 2 UMTS Chairman

Tel 1: +45 4358 6378Company: TELE DANMARK A/S Tel 2:

Address: Spotorno Allé 12 Fax 1: +45 43 71 03 822630 TAASTRUP Fax 2:DENMARK


Participants to ETSI/TC/SMG#27 - 12-16 October 1998 in Praha


Name: ANSALDI Renato Tel 1: +39 02 4388 6384Company: ITALTEL Tel 2:

Address: Via Padana Km 158 Fax 1: +39 02 4388 655020060 CASSINA DE PECCHI (MILAN) Fax 2:ITALY


Name: ARAKI Michiko Tel 1: +81 3 5563 7252Company: NTT DoCoMo Tel 2:

Address: Shin-nikko Bldg, East Tower Mob :10-1 TORANOMON 2-chome Fax 1: +81 3 5572 6526MINATO-KU, TOKYO 105 8436 Fax 2:JAPAN

E-Mail Internet: araki_m@docomo_tokai.co.jp

Name: ASSOR Jean-Luc Tel 1: +33 1 3926 6255Company: BOUYGUES TELECOM Tel 2:

Address: Europa Mob :51, avenue de l'Europe Fax 1: +33 1 39 26 86 1378944 VELIZY CEDEX Fax 2:FRANCE


Name: BARNES David Tel 1: +44 171 215 1818Company: DTI Tel 2:

Address: 151 Buckingham Palace Road Mob : +44 385 316 985Room 2/126 Fax 1: +44 171 931 7194LONDON SW1W 9SS Fax 2:UNITED KINGDOM


Name: BARNES NigelSMG 9 Vice Chairman - SMG 9 SIM Toolkit Security ChairmanSMG1 SIM Toolkit Stage 1 Chairman

Tel 1: +44 1256 790 169Company: MOTOROLA Tel 2: +44 1256 790 319

Address: European Standards Sector Mob : +44 385 318 631Midpoint, Alencon Link Fax 1: +44 1256 790 190BASINGSTOKE RG21 7PL Fax 2:UNITED KINGDOM




Name: BEER Stephen Tel 1: +44 1684 894 088Company: DERA Tel 2:

Address: St. Andrews Road Mob :Malvern Fax 1: +44 1684 895 646WORCS WR14 3PS Fax 2:UNITED KINGDOM


Name: BENNINK Rob Tel 1: +31 70 343 7105Company: KPN TELECOM Tel 2:

Address: PO Box 30150 Mob :Fax 1: +31 70 343 7237

2500 GD THE HAGUE Fax 2:THE NETHERLANDS


Name: BERGMANN AnsgarPT SMG Coordinator Tel 1: +33 4 92 94 43 22

Company: ETSI/PT SMG Tel 2:Address: 650 Route des Lucioles Mob : +49 171 2000 921

Fax 1: +33 4 93 65 28 1706921 SOPHIA ANTIPOLIS CEDEX Fax 2:FRANCE


Name: BERGS Hans-Joachim Tel 1: +49 711 821 45776Company: ALCATEL SEL AG Tel 2:

Address: Switching System Division Mob :Lorenzstrasse 10 Fax 1: +49 711 821 4766170430 STUTTGART Fax 2:GERMANY


Name: BERNARD André Tel 1: +33 1 55 22 23 10Company: FRANCE TELECOM MOBILES Tel 2:

Address: 45-47 Bd Romain Rolland Mob : +33 6 07 77 10 27Fax 1: +33 1 55 22 23 23

92000 MONTROUGE Fax 2:FRANCE


Name: BERRY Athol Tel 1: +49 89 4129 3675Company: ROHDE & SCHWARZ GmbH Tel 2:

Address: Dept.1SP2 Postfach 801469 Mob :Mühldorfstr. 15 Fax 1: +49 89 4129 360181671 MÜNCHEN Fax 2:GERMANY




Name: BJÖRNDAHL PerSTF Voluntary Funding Task Force Chairman

Tel 1: +46 8 757 2602Company: ERICSSON RADIO SYSTEMS AB Tel 2:

Address: KI/ERA/UX/SC Mob : +46 70 591 2602Fax 1: +46 8 404 8040

16480 STOCKHOLM Fax 2:SWEDEN


Name: BLANKENFELD HeinzECTEL TMS Chairman Tel 1: +49 89 722 26655

Company: SIEMENS AG Tel 2:Address: Hofmannstraße 51 Mob : +49 171 3403150

Fax 1: +49 89 722 2754681359 MUNICH Fax 2:GERMANY


Name: BOCAERT Bruno Tel 1: +33 4 9296 11 04Company: VLSI TECHNOLOGY Tel 2:

Address: 505 Route des Lucioles Mob : +33 6 09 55 50 65SOPHIA ANTIPOLIS Fax 1: +33 4 9296 110106560 VALBONNE Fax 2:FRANCE


Name: BOGH Jan Tel 1: +45 405 872 231Company: SONOFON Tel 2:

Address: Skelagervej 1 Fax 1: +45 9936 70709100 AALBORG Fax 2:DENMARK


Name: BRANDÉN JonasWAP Consortium Liaison Officer Tel 1: +46 46 19 41 04

Company: ERICSSON MOBILE COMMUNICATIONS AB Tel 2:Address: Nya Vattentornet Mob : +46 70 650 83 45

Fax 1: +46 46 19 38 1022183 LUND Fax 2:SWEDEN




Name: BRATT Gunilla Tel 1: +46 46 193729Company: ERICSSON MOBILE COMMUNICATIONS AB Tel 2:

Address: Nya Vattentornet Mob :Fax 1: +46 46 193 136

22183 LUND Fax 2:SWEDEN


Name: BROUWERS Eric Tel 1: +31 43 355 7717Company: LIBERTEL Tel 2:

Address: Avenue Ceramique 300 Mob : +31 654 670 617Fax 1: +31 43 355 7444

6221 KX MAASTRICHT Fax 2:THE NETHERLANDS


Name: CABRERA InakiTMN WG5 Chairman

Tel 1: +34 907 13 33 91Company: AIRTEL MOVIL SA Tel 2:

Address: Av. de Europa, 1 Mob : +34 910 51 3391Parque Tecnologico "La Moraleja" Fax 1: +34 907 13305828108 ALCOBENDAS (MADRID) Fax 2:SPAIN


Name: CANDEO Silvano Tel 1: +39 06 5958 2660Company: MINISTERIO DELLE COMUNICAZIONI Tel 2:

Address: I.S.P.T Mob : +39 348 2270116Viale America 201 Fax 1: +39 06 5410 90400144 ROMA Fax 2:ITALY


Name: CARIOU Hubert Tel 1: +33 1 39 26 6004Company: BOUYGUES TELECOM Tel 2:

Address: Europa Mob : +33 6 60 31 60 0451, avenue de l'Europe Fax 1: +33 1 39 26 640278944 VELIZY CEDEX Fax 2:FRANCE




Name: CASSEN QuentT1P1 Secretary Tel 1: +1 949 221 4177

Company: ROCKWELL INTL CORP. Tel 2:Address: Wireless Communications Division Mob : +1 714 606 7433

4311 Jamboree Road Fax 1: +1 949 221 5890NEWPORT BEACH CA 92660-3095 Fax 2:UNITED STATES


Name: CAVIGIOLI Chris Tel 1: +49 89 76903 400Company: ANALOG DEVICES Tel 2: +1 781 461 3058

Address: Am Westpark 1-3 Mob : +49 172 705 2026Fax 1: +49 89 76903 404

81373 MUENCHEN Fax 2:GERMANY


Name: CHANDLER Colin Tel 1:Company: QUALCOMM EUROPE SARL Tel 2:

Address: 2000 Route des Lucioles Mob :BP 126 Fax 1:06903 SOPHIA ANTIPOLIS CEDEX Fax 2:FRANCE

E-Mail Internet:

Name: CHAUVEAU Didier Tel 1: +33 1 40 47 71 25Company: ART Tel 2:

Address: 7 Square Max Hymans Mob :Fax 1: +33 1 40 47 71 90

75730 PARIS CEDEX 15 Fax 2:FRANCE


Name: CHEN Kwang-Chen Tel 1: +886 2 2363 5251Company: NATIONAL TAIWAN UNIVERSITY Tel 2: +886 2 2363 5246

Address: Institute of Communications Engineering Mob : +886 90 292048Fax 1: +886 2 2368 3824

TAIPEI, TAIWAN 10617 Fax 2:TAIWAN


Name: CHOMET Patrick Tel 1: +44 181 600 1083Company: ICO GLOBAL COMMUNICATIONS Tel 2:

Address: 1 Queen Caroline Street Mob :Hammersmith Fax 1: +44 181 563 9413LONDON W6 9BN Fax 2:UNITED KINGDOM




Name: COOKE Stuart Tel 1: +44 1276 68616Company: NOKIA R&D Tel 2:

Address: St Georges Court, St Georges Rd Mob : +44 370 647030Camberley Fax 1: +44 1276 677151SURREY GU15 3QZ Fax 2:UNITED KINGDOM


Name: COOPER David Tel 1: +44 1189 654 511Company: NEC TECHNOLOGIES (UK) LTD Tel 2: +44 1189 257 190

Address: Level 3, the Imperium Mob :Imperial Way, Worton Grange Fax 1: +44 1189 257 191READING RG2 0TD Fax 2:UNITED KINGDOM


Name: CORFIELD Simon Tel 1: +44 1684 896 082Company: DERA PC 131 Tel 2:

Address: St. Andrews Road Mob :Malvern Fax 1: +44 1684 896 121WORCS WR14 3PS Fax 2:UNITED KINGDOM


Name: COURAU FrancoisSMG12 Chairman Tel 1: +33 1 30 77 94 68

Company: ALCATEL Tel 2:Address: 10, rue Latécoère Mob : +33 6 08 82 20 22

Fax 1: +33 1 30 77 94 3078141 VELIZY CEDEX Fax 2:FRANCE


Name: COX Alan SMG Vice Chairman - SMG 1 Chairman Tel 1: +44 1635 503 332

Company: VODAFONE LTD Tel 2:Address: The Courtyard Mob : +44 385 200 147

2-4 London Road Fax 1: +44 1635 583 019NEWBURY, BERKSHIRE RG14 1JX Fax 2: +44 1635 31127UNITED KINGDOM




Name: CRUCHANT Laurent Tel 1: +33 1 30 77 82 75Company: ALCATEL Tel 2:

Address: 10, rue Latécoère Mob : +33 6 07 64 09 90Fax 1: +33 1 30 77 94 30

78141 VELIZY CEDEX Fax 2:FRANCE


Name: DAAS Benjamin M. Tel 1: +49 211 5296 209Company: TOSHIBA ELECTRONICS EUROPE GmbH Tel 2:

Address: Hansaallee 181 Mob : +49 171 323 9669Fax 1: +49 211 5296 404

40549 DUSSELDORF Fax 2:GERMANY


Name: DAVIDIAN Jean-Jacques Tel 1: +33 4 92 94 42 71Company: ETSI/PT SMG Tel 2:

Address: 650 Route des Lucioles Mob :Fax 1: +33 4 93 65 28 17

06921 SOPHIA ANTIPOLIS CEDEX Fax 2:FRANCE


Name: DAVIDSSON Pamela Tel 1: +46 8 678 55 93Company: NATIONAL POST & TELECOM Tel 2:

Address: Birger Jarlsgatan 16 Mob :Box 5398 Fax 1: +46 8 678 55 09102 49 STOCKHOLM Fax 2:SWEDEN


Name: DAVIES John I. Tel 1: +44 171 830 1948Company: SEMA GROUP TELECOMS Tel 2:

Address: 233 High Holborn Mob :Fax 1: +44 1 71 830 1830

LONDON WC1V 7DJ Fax 2:UNITED KINGDOM


Name: DAY Brian Tel 1: +44 1 628 434 153Company: NORTEL Tel 2:

Address: 3 Roxborough Way Mob :Foundation Park Fax 1: +44 1 628 434 034MAIDENHEAD BERKSHIRE SL6 3UD Fax 2:UNITED KINGDOM




Name: DE RYCK Francois Tel 1: +33 2 99 84 11 27Company: MITSUBISHI ELECTRIC ITE Tel 2:

Address: Immeuble Germanium Mob :80 avenue des Buttes de Coesmes Fax 1: +33 2 99 87 21 1535700 RENNES Fax 2:FRANCE


Name: DESPLANQUE Jacques Tel 1: +33 1 55 22 2352Company: FRANCE TELECOM MOBILES Tel 2:

Address: Mob : +33 6 07 53 30 6341-45 Bld Romain Rolland Fax 1: +33 1 55 22 23 6975672 PARIS CEDEX 14 Fax 2:FRANCE


Name: DETTNER HaraldSMG 3 Chairman Tel 1: +49 6621 169169

Company: SIEMENS AG Tel 2:Address: Dep.MN P24 Mob : +49 171 3340 784

Landecker Strasse 11 Fax 1: +49 6621 16912236251 BAD HERSFELD Fax 2:GERMANY


Name: DOIG Ian Tel 1: +33 4 9294 4226Company: ETSI/SMS Dept Tel 2:

Address: 650 Route des Lucioles Fax 1: +33 4 93 65 47 1606921 SOPHIA ANTIPOLIS CEDEX Fax 2:FRANCE


Name: DOMEIER Horst Tel 1: +49 211 533 3656Company: MANNESMANN MOBILFUNK GmbH Tel 2:

Address: Am Seestern 1 Mob : +49 0172 890 4114Fax 1: +49 211 583 3357

40543 DÜSSELDORF Fax 2:GERMANY




Name: DONAT PeterSMG WG WOME Chairman Tel 1: +43 1 1707 22 300

Company: FEEI Tel 2:Address: C/O SIEMENS AG Mob : +43 664 162 4383

Siemenstrasse 92 Fax 1: +43 1 1707 54 4501211 WIEN Fax 2:AUSTRIA


Name: DORGELO Albert J.G. Tel 1: +31 356 872 879Company: LUCENT TECH. Emea B.V Tel 2:

Address: Department GSS-EMEA Mob : +31 65 339 4658PO Box 1168/Room BG 502 Fax 1: +31 356 875 8331200 BD HILVERSUM Fax 2:THE NETHERLANDS


Name: EHRLICH EdT1P1.5 Chairman Tel 1: +1 973 292 5724

Company: NORTEL Tel 2:Address: 465 South St. Mob :

Suite 100 Fax 1: +1 973 292 4160MORRISTOWN, NJ 07960 Fax 2:UNITED STATES


Name: EIGLER Karl Tel 1: +49 228 700 1665Company: DETECON GmbH Tel 2:

Address: SBM621 Mob :Oberkasseler Strasse 2 Fax 1: +49 228 700 160753227 BONN Fax 2:GERMANY


Name: EKEN Semith Koray Tel 1: +90 312 385 1900Company: ASELSAN ING Tel 2:

Address: Mehmet Akif Ersoy Mah 16 Cad Mob : +90 532 312 6063No. 16 Fax 1: +90 312 354 167906372 Y.Makalle-Ankara Fax 2:TURKEY




Name: EKUDDEN Erik Tel 1: +46 8 757 2168Company: ERICSSON RADIO SYSTEMS AB Tel 2:

Address: T/VAT Torshamnsgatan 23 Mob :KISTA Fax 1: +46 8 757 555016480 STOCKHOLM Fax 2:SWEDEN


Name: EL-HOIYDI Amre Tel 1: +41 32 327 55 11Company: OFCOM Tel 2:

Address: Rue de l'Avenir 44 Fax 1: +41 32 327 57772501 BIENNE Fax 2:SWITZERLAND


Name: ELKON Stéphane Tel 1: +33 1 4047 7092Company: ART Tel 2:

Address: 7 Square Max Hymans Fax 1: +33 1 4047720675730 PARIS CEDEX 15 Fax 2:FRANCE


Name: ERIKSEN Tom Tel 1: +33 4 92 94 43 12Company: ETSI/M&D Tel 2:



Name: FAGAN John Tel 1: +353 1 808 2784Company: TELTEC IRELAND Tel 2:

Address: FORBAIRT Mob :Glasnevin Fax 1: +353 1 837 7648DUBLIN 9 Fax 2:IRELAND


Name: FENN John Tel 1: +44 1784 428 600Company: SAMSUNG ELECTRONIC RES.INST. Tel 2: ext 684

Address: Communication House Mob : +44 802 339070South Street Fax 1: +44 1784 428 629STAINES TW18 4QE Fax 2:UNITED KINGDOM




Name: FENYVES Alessandro Tel 1: +39 02 4388 9337Company: ITALTEL Tel 2:

Address: BURM(BM) C26 Mob : +39 335 800 4180Via Reiss Romoli Fax 1: +39 02 4388 244220019 SETTIMO MILANESE (MI) Fax 2:ITALY


Name: FOERSTER Molly Tel 1: +33 4 92 38 82 20Company: QUALCOMM EUROPE SARL Tel 2:

Address: Algorithmes, Aristote B Mob : +33 6 80 35 21 872000 Route des Lucioles, BP 126 Fax 1: +33 4 92 38 82 3006903 SOPHIA ANTIPOLIS Fax 2:FRANCE


Name: FOERSTER Ronald E. Tel 1: +33 4 92 38 82 20Company: QUALCOMM EUROPE SARL Tel 2:

Address: 2000 Route des Lucioles Mob : +33 6 12 14 12 38BP 126 Fax 1: +33 4 92 38 82 3006903 SOPHIA ANTIPOLIS CEDEX Fax 2:FRANCE


Name: FOXMAN Arne Tel 1: +45 4358 6460Company: TELE DANMARK A/S Tel 2:

Address: Networks division, NM-F Mob : +45 4013 0082Telegade 2 Fax 1: +45 43 71 08 412630 TAASTRUP Fax 2:DENMARK


Name: FREDERIKSEN Jesper Ledet Tel 1: +45 96 738 000Company: BOSCH TELECOM DANMARK A/S Tel 2:

Address: Bransagervej 30 Mob : +45 40 64 7250Fax 1: +45 96 738 002

9490 PANDRUP Fax 2:DENMARK


Name: FRIEL Chris Tel 1: +44 1 753 565 874Company: CELLNET Tel 2:

Address: 260 Bath Road Mob : +44 860 552 060Slough Fax 1: +44 1 753 565 029BERKSHIRE SL1 4DX Fax 2:UNITED KINGDOM




Name: FUKUDA Eisuke Tel 1: +44 181 606 4473Company: FUJITSU EUROPE TELECOM Tel 2:

Address: 2 Longwalk Road, Stockley Park Mob :Uxbridge Fax 1: +44 181 606 4539MIDDLESEX UB11 1AB Fax 2:UNITED KINGDOM


Name: GALLIGO Michel Tel 1: +33 1 55 66 39 73Company: ALCATEL BUSINESS SYSTEMS Tel 2:

Address: 32 Avenue Kleber Mob : +336 8085 8806Fax 1: +33 1 55 66 78 26

92700 COLOMBES CEDEX Fax 2:FRANCE


Name: GARBA Roman Tel 1: +420 603 620 301Company: RADIOMOBIL AS / PAEGAS Tel 2:

Address: Londýnská 59 Mob :Fax 1: +420 603 620 306

12021 PRAHA 2 Fax 2:CZECH REPUBLIC

E-Mail Internet:

Name: GARRAMONE Saverio Tel 1: +39 010 600 2812Company: MARCONI SpA Tel 2:

Address: Via A. Negrone, 1A Fax 1: +39 010 600 204416153 GENOVA Fax 2:ITALY

E-Mail Internet:

Name: GASKELL Philip Tel 1: +44 1 81 214 2230Company: ONE-2-ONE Tel 2:

Address: Imperial Place Mob : +44 956 235 468Maxwell Road, Borehamwood Fax 1: +44 1 81 9051 671HERTS WD6 1EA Fax 2:UNITED KINGDOM


Name: GEUENS Leopold Tel 1: +32 1 425 2973Company: SIEMENS ATEA NV Tel 2:

Address: Atealaan 34 Fax 1: +32 1 425 32122200 HERENTALS Fax 2:BELGIUM




Name: GIEFING Gerald Tel 1: +43 1 331 61 6110Company: MOBILKOM AUSTRIA AG Tel 2:

Address: Mob : +43 664 331 6110Obere Donaustrasse 23-27 Fax 1: +43 1 331 61 60091020 VIENNA Fax 2:AUSTRIA


Name: GRASSOT Francois Tel 1: +33 1 39444099Company: NORTEL Tel 2:

Address: c/o NMC 1, Place des Frères Montgolfier Mob : +33 6 85 32 53 95BP 50 Fax 1: +33 1 39 44 501278042 GUYANCOURT CEDEX Fax 2:FRANCE


Name: GREEN Steve Tel 1: +44 171 211 0321Company: DTI Tel 2:

Address: Auction team - 8S/8.2 Mob : +44 802 33834122 Upper Ground Fax 1: +44 171 211 0123LONDON SE1 9SA Fax 2:UNITED KINGDOM


Name: GUENTHER Holger Tel 1: +420 603 620 301Company: RADIOMOBIL AS / PAEGAS Tel 2:

Address: Londýnská 59 Fax 1: +420 603 620 30612021 PRAHA 2 Fax 2:CZECH REPUBLIC

E-Mail Internet:

Name: HAAVISTO Petri Tel 1: +358 3 272 5836Company: NOKIA RESEARCH CENTRE Tel 2:

Address: Sinitaival 6 Mob : +358 500 830 838PO Box 100 Fax 1: +358 3 272 589733721 TAMPERE Fax 2:FINLAND


Name: HADDEN Alan Tel 1: +44 1 279 435 483Company: UMTS FORUM Tel 2:

Address: C/O FEI Mob : +44 788 764 512610-12 Russell Square Fax 1: +44 1279 435 443LONDON WC1B 5EE Fax 2:UNITED KINGDOM




Name: HADDEN Alan Tel 1: +44 1279 435 483Company: GSA Tel 2:

Address: 20 Hampton Gardens, Sawridgeworth Fax 1: +44 1 279 435 443HERTFORDSHIRE CM21 0AN Fax 2:UNITED KINGDOM


Name: HALL Steven Tel 1: +1 760 634 6115Company: COMMQUEST Tel 2:

Address: 527 Encinitas Blvd Mob : +1 760 809 0284Encinitas Blvd Fax 1: +1 760 634 6110ENCINITAS CA Fax 2:UNITED STATES


Name: HAN Yeongchong Tel 1:Company: LG INFORMATION & COM. Tel 2:

Address: Mob :Fax 1:Fax 2:

KOREAE-Mail Internet:

Name: HANGSTRUP Lars Tel 1: +45 9635 5500Company: MAXON CELLULAR SYSTEMS Tel 2:

Address: Niels Jernesvey 8 Mob : +45 4040 8142Fax 1: +45 9635 5600

9220 AALBORG EAST Fax 2:DENMARK


Name: HARO ABAD Albert Tel 1: +33 1 39 26 6517Company: BOUYGUES TELECOM Tel 2:

Address: RED - Europa A Mob : +33 6 61 89 90 4351 Avenue de l'Europe Fax 1: +33 1 39 26 86 1378944 VELIZY CEDEX Fax 2:FRANCE


Name: HARRIS IanSMG 4 Cell Broadcast Chairman Tel 1: +44 1635 503 270

Company: VODAFONE LTD Tel 2: +44 1635 502 344Address: Vodafone Value Added Services Mob : +44 385 360 000

Dower House, Fax 1: +44 1635 503 297NEWBURY, BERKSHIRE RG14 1JD Fax 2:UNITED KINGDOM




Name: HARRISON Fred Tel 1: +44 1 442 296 717Company: BRITISH TELECOM Tel 2:

Address: Westsid, PP A3003 Mob : +44 802 223595London Road, Hemel Hempstead Fax 1: +44 1442 295 888HERTS HP3 97F Fax 2:UNITED KINGDOM


Name: HARROLD William Tel 1: +44 1 763 266 266Company: THE TECHNOLOGY PARTNERSHIP Tel 2:

Address: Melbourn Science Park Mob :Cambridge Road, Melbourn, Fax 1: +44 1 763 261 216ROYSTON SG8 6EE Fax 2:UNITED KINGDOM


Name: HAUSER Hans Tel 1: +49 228 936 1200Company: DeTeMobil GmbH Tel 2:

Address: Landgrabenweg 151 Mob : + 49 171 549 03 99PO Box 300463 Fax 1: + 49 228 936 330953227 BONN Fax 2:GERMANY


Name: HAYES StephenT1P1 Vice Chairman Tel 1: +1 972 583 5773

Company: ERICSSONAddress: 601 N. Glenville Mob : +1 214 668 5728

Fax 1: +1 972 644 3036RICHARDSON TX 75081 Fax 2:UNITED STATES


Name: HELLMAN Monica Tel 1: +46 455 331 000Company: EUROPOLITAN AB Tel 2: +46 455 331 430

Address: Mob : +46 708 331 430Fax 1: +46 455 331 490

37180 KARLSKRONA Fax 2: +46 708 332 430SWEDEN




Name: HERTEL GiselaSMG 6 Chairman Tel 1: +49 211 4958 650

Company: ARTHUR ANDERSEN Managment Beratun Tel 2:Address: Uerdinger Strasse 88 Mob : +49 171 328 5677

Fax 1: +49 211 4958 60240474 DUSSELDORF Fax 2:GERMANY


Name: HILLEBRAND FriedhelmSMG Chairman Tel 1: +49 228 47 4770

Company: ETSI/TC SMG CHAIRMAN Tel 2:Address: SMG CONSORTIUM Mob : +49 171 414 3599

Combahnstrasse 23 Fax 1: +49 228 47 476453225 BONN Fax 2:GERMANY


Name: HOLDING Darren Tel 1: +44 1256 864267Company: ERICSSON OMC LTD Tel 2:

Address: The Keytech Centre Mob : +44 7775 906329Ashwood Way, Basingstoke Fax 1: +44 1256 864280HAMPSHIRE Fax 2:UNITED KINGDOM


Name: HOLLEY Kevin A.SMG 4 Chairman - SMG4 UMTS Chairman Tel 1: +44 171 519 9028

Company: BRITISH TELECOM Tel 2:Address: MLB 1 PP11 Mob : +44 802 220 811

Martlesham Heath Fax 1: +44 171 519 9028IPSWICH IP5 3RE Fax 2:UNITED KINGDOM


Name: HOLMES Christopher Tel 1: +44 171 215 1779Company: DTI Tel 2:

Address: Room 215, Mob :151 Buckingham Palace Road Fax 1: +44 1 71 215 1814LONDON SW1W 955 Fax 2:UNITED KINGDOM




Name: HYBRE Jean Tel 1: +33 1 4197 67 17Company: SFR / CEGETEL Tel 2:

Address: Tour de l' Esplanade Mob : +33 6 09 65 19 241, Place Carpeaux - La Défense 6 Fax 1: +33 1 55 68 25 0792915 PARIS LA DEFENSE CEDEX Fax 2:FRANCE


Name: ISRAELSSON Per Tel 1: +46 8 601 72 78Company: TELIA MOBILE AB Tel 2:

Address: Augestendalsv.7 Mob : +46 70 582 2357Fax 1: +46 8 601 72 68

131 86 NACKA STRAND Fax 2:SWEDEN


Name: ISSENMANN Edouard Tel 1: +33 1 30 77 93 01Company: ALCATEL CIT Tel 2:

Address: 10, rue Latécoère Mob :BP 57 Fax 1: +33 1 30 77 036978141 VELIZY CEDEX Fax 2:FRANCE


Name: JÄGER Thomas Tel 1: +49 2054 9519 80Company: CETECOM GmbH Tel 2:

Address: Im Teelbruch 122 Fax 1: +49 2054 9519 8645219 ESSEN Fax 2:GERMANY


Name: JARVELA Teuvo Tel 1: +44 1276 419057Company: NOKIA MOBILE PHONES Tel 2:

Address: St Georges Court, St Georges Rd Mob : +44 385 525 683Camberley Fax 1: +44 1276 677151SURREY GU15 3QZ Fax 2:UNITED KINGDOM


Name: JÄRVINEN KariSMG11 Chairman - SMG11 AMR Chairman Tel 1: +358 3272 5854

Company: NOKIA RESEARCH CENTRE Tel 2:Address: Sinitaival 6 Mob : +358 50 555 0999

PO Box 100 Fax 1: +358 3272 588833721 TAMPERE Fax 2:FINLAND




Name: JENNI Christian Tel 1: +41 31 998 3539Company: ERICSSON AG Tel 2:

Address: Postfacch 556 Mob : +41 89 300 3976Logerhansweg 10 Fax 1: +41 31 998 35013018 BERN Fax 2:SWITZERLAND


Name: JONES Gary K.T1P1 Representative Tel 1: +1 301 951 2524

Company: OMNIPOINT CORPORATION Tel 2:Address: 3 Bethesd Metro Center Mob : + 1 201 486 0949

Suite 400 Fax 1: +1 301 951 2580BETHESDA, MD 20814 Fax 2:UNITED STATES


Name: JOST Herbert Tel 1: + 41 31 342 8602Company: SWISSCOM Tel 2:

Address: MC-MV-5 Mob : +41 79 300 02 15Victoriastrasse 21 Fax 1: + 41 31 342 05183050 BERN Fax 2:SWITZERLAND


Name: KANCK Rune Tel 1: +47 22 888851Company: NETCOM GSM AS Tel 2:

Address: Postboks 4444 Torshov Mob : +47 920 25250Sandakerveien 140 Fax 1: +47 22 88 84940403 OSLO Fax 2:NORWAY


Name: KANERVA Mikko Tel 1: +358 9 5116 8077Company: NOKIA TELECOMMUNICATIONS Tel 2:

Address: PO Box 321 Mob : +358 40 5040 735Fax 1: +358 9 5116 8080

00045 NOKIA GROUP Fax 2: +358 40 604 0735FINLAND


Name: KAR Radivoj Tel 1: +33 1 55 68 56 60Company: MITSUBISHI ELECTRIC Tel 2:

Address: 25, Boulevard des Bouvets Mob : +358 40 500 7160Fax 1: +33 1 55 68 57 41

92741 NANTERRE CEDEX Fax 2:FRANCE




Name: KELLY Brian Tel 1: +353 1 208 1565Company: TELECOM EIREAN EIRCELL Tel 2:

Address: Unit 8, Richview Office Park Mob : +353 87 230 8461Clonskeagh Fax 1: +353 1 208 1602DUBLIN 14 Fax 2:IRELAND


Name: KOKKOS Makis Tel 1: +44 1 276 419 607Company: NOKIA MOBILE PHONES Tel 2:

Address: St Georges Ct., St Georges Rd. Mob :CAMBERLY Fax 1: +44 1 276 677 151SURREY GU15 3QZ Fax 2:UNITED KINGDOM


Name: KOTTINK Pavel Tel 1: +420 603 620 301Company: RADIOMOBIL AS / PAEGAS Tel 2:


E-Mail Internet:

Name: KRASSOWSKI Waldemar Tel 1: +48 89 5333 522Company: NATIONAL RADIOCOMMUNICATIONS AGENCY Tel 2:

Address: Regional Directorate in Olsztyn Mob : +486 027 14769ul. Pstrowskiego 16 Fax 1: +48 89 5235 10210-602 OLSZTYN Fax 2:POLAND


Name: KUENAST Walter Tel 1: +33 5 61 19 10 59Company: MOTOROLA Tel 2:

Address: Avenue du Général Eisenhower Mob : +33 6 08 76 39 03Le Miral BP 1029 Fax 1: +33 5 61 19 101231023 TOULOUSE CEDEX Fax 2:FRANCE


Name: KÜHN Manuela Tel 1:Company: VEBA TELECOM Tel 2:


GERMANYE-Mail Internet:



Name: KUNCOVA Ilona Tel 1: +420 603 620 790Company: RADIOMOBIL Tel 2:

Address: Londgnokal 12000 Mob : +420 603 400 790Fax 1:

PRAGUE 2 Fax 2:CZECH REPUBLIC


Name: LAURENT-LUND Einar Tel 1: +45 3543 0333Company: NATIONAL TELECOM AGENCY Tel 2:

Address: Holsteinsgade 63 Fax 1: +45 3543 40062100 COPENHAGEN Fax 2:DENMARK


Name: LICHTENBERGER Annamaria Tel 1: +39 2 4388 5113Company: ITALTEL Tel 2:

Address: Via Alessio di Tocqueville, 13 Mob : +39 338 6186 766Fax 1: +39 2 4388 5379

20154 MILANO Fax 2:ITALY


Name: LJUNGBERG Eric Tel 1: +46 40 10 51 43Company: TELIA RESEARCH AB Tel 2:

Address: P.O. Box 85 Mob : + 46 70 59 44 444Fax 1: +46 40 30 70 29

20120 MALMÖ Fax 2:SWEDEN


Name: LORENZ Martin Tel 1: +49 911 3788 0Company: DEBIS SYTEMHANS GEI Tel 2:

Address: Neutorgraben 1B Fax 1: +49 911 3788 10090419 NURNBERG Fax 2:GERMANY


Name: LUCAS Philippe Tel 1: +33 1 41 97 67 38Company: CEGETEL Tel 2: +33 1 41 97 65 07

Address: Tour Séquoia Mob : +33 6 12 72 60 341 Place Carpeaux Fax 1: +33 1 41 97 71 4392915 PARIS LA DEFENSE CEDEX Fax 2:FRANCE




Name: MAIER Gerhard M. Tel 1: +44 1 865 747 711Company: SHARP LAB.EUROPE LTD. Tel 2: +44 1 865 716 689

Address: Edmund Halley Rd. Mob : +44 385 250 950Oxford Science Park Fax 1: +44 1 865 747 717OXFORD OX4 8DT Fax 2: +44 1 865 716 689UNITED KINGDOM


Name: MALMBAK Per Tel 1: +49 611 3611 410Company: MOTOROLA Tel 2: +49 611 3611 401

Address: Cellular Subscriber Division Mob : +49 171 850 8100Hagenauer Str.47 Fax 1: +49 611 260 43965203 WIESBADEN Fax 2:GERMANY


Name: MARTTINEN Kari Tel 1: +358 2040 3969Company: SONERA Ltd Tel 2:

Address: PO Box 980 Mob : +358 400 400 068Fax 1: +358 2040 65321

00051 SONERA Fax 2:FINLAND


Name: MATYS Ivan Tel 1: +420 2 6701 2807Company: EUROTEL Tel 2:

Address: Sokolovska 855/225 Mob : +420 602 600 081Po Box 49 Fax 1: +420 2 6701 2809190 00 PRAHA 9 Fax 2:CZECH REPUBLIC


Name: MAUL Heino Tel 1: +49 911 526 3128Company: LUCENT TECHNOLOGIES Tel 2:

Address: Thurn-und-Taxis Str.10 Mob : +49 171 3080 772Fax 1: +49 911 526 2979

90411 NURNBERG Fax 2:GERMANY


Name: McFARLANE David Tel 1:Company: NOKIA Tel 2:


UNITED KINGDOME-Mail Internet:



Name: McINTOSH Chris Tel 1: +33 1 49 38 91 95Company: INTERWAVE COMMUNICATIONS Tel 2:

Address: Z.I. Paris Nord II Immeuble de Sisley - 2ème étage Mob :23, Allée des Impressionistes BP 50295 Fax 1: +33 1 49 38 91 9095958 ROISSY CDG Fax 2:FRANCE


Name: MECROW Steve Tel 1: +44 41 00 28511Company: BRITISH TELECOM Tel 2:

Address: 2-02 Bibb Way Mob :Ipswich Fax 1: +44 1473 227884SUFFOLK IP1 2EQ Fax 2:UNITED KINGDOM


Name: MEDEIROS Francisco Tel 1: +44 1753 606 943Company: NEC TECHNOLOGIES (UK) LTD Tel 2:

Address: 5 Bath Road Mob :Slough Fax 1: +44 1753 606 901BERKSHIRE SL1 3UA Fax 2:UNITED KINGDOM


Name: MEINERT-NIELSEN Henrik Tel 1: +45 99 86 22 00Company: TELITAL R&D DENMARK A/S Tel 2:

Address: Oestre Allé 6 Mob : +45 40 80 53 41Fax 1: +45 99 86 2301

9530 STØVRING Fax 2:DENMARK


Name: MELVIN Linda Tel 1: +1 650 747 0993Company: NORTH AMERCIAN INTEREST GROUP of GSM MoU Tel 2:

Address: PO Box 333 Mob : +650 483 1127Fax 1: +1 650 747 0649

LA HONDA, CA 94020 Fax 2:UNITED STATES


Name: MICHAU Philippe Tel 1: +33 1 46 13 34 49Company: THOMSON-CSF/DCH Tel 2:

Address: 160 Boulevard de Valmy Mob :BP. 82 Fax 1: +33 1 46 13 25 0192704 COLOMBES Fax 2:FRANCE




Name: MIYATA Teruaki Tel 1: +3 5687 1397Company: COMFORT Inc. Tel 2:

Address: Residence Miyata 602, 1 13 12 Mob :Misuji, Taito-Ku Fax 1: +3 5687 1389TOKYO ZIP 111-0055 Fax 2:JAPAN

E-Mail Internet:

Name: MOULY Michel Tel 1: +33 1 6931 48 48Company: NORTEL Tel 2:

Address: 4, rue Elisee Reclus Mob : +33 6 07 59 41 76Fax 1: +33 1 6931 0338

91120 PALAISEAU Fax 2:FRANCE


Name: MOUTON Christian Tel 1: +33 1 55 66 37 41Company: ALCATEL Tel 2:

Address: 32 Avenue Kleber Mob : +33 1 06 08 43 44 02Fax 1: +33 1 55 66 44 50



Name: MÜLLER Susanne Tel 1: +49 30 386 270 33Company: TEKTRONIX Tel 2:

Address: Wemmerdamm 5 Mob : +49 171 308 9887Fax 1: +49 30 386 22524

13629 BERLIN Fax 2:GERMANY

E-Mail Internet: susanne.muë[email protected]

Name: NAPOLITANO Antonella Tel 1: +39 0 1122 85040Company: CSELT Tel 2:

Address: Via G. Reiss Romoli 274 Mob :Fax 1: +39 0 1122 85295

10148 TORINO Fax 2: +39 0 1122 85582ITALY




Name: NAVARRO WilliamSMG11 TFO Chairman Tel 1: +33 1 39 44 57 56

Company: NORTEL MATRA CELLULAR Tel 2: +33 1 39 44 44 44Address: 1, Place des Frères Montgolfier Mob :

BP 50 Fax 1: +33 1 39 44 50 1278402 GUYANCOURT CEDEX Fax 2:FRANCE


Name: NEUMANN Peter Dr. Tel 1: +49 89 722 36718Company: SIEMENS AG Tel 2:

Address: PN KE TT41 Mob : +49 172 890 44 28Hofmannstraße 51 Fax 1: +49 89 722 3707881359 MÜNCHEN Fax 2:GERMANY


Name: NIELSEN Henning Bjarke Tel 1: +49 89 94578 107Company: SONY PMC EUROPE Tel 2:

Address: Max-Planks Strasse 8 Mob : +49 172 839 2670Fax 1: +49 89 94578 412

85609 ASCHLEIM-DORNACH Fax 2:GERMANY


Name: NISULA Jaako Tel 1: +358 9 6959 9274Company: OMNITELE Tel 2:

Address: Talberginkatu 2 A Mob : +358 9 685 2480P O BOX 969 Fax 1: +358 50 300 021200101 HELSINKI Fax 2:FINLAND


Name: NODA Akishige Tel 1: +81 44 754 4196Company: FUJITSU Tel 2:

Address: 2-12-5 Shimokodanaka Nakahara Fax 1: +81 44 754 4148KAWASAKI Fax 2:JAPAN


Name: NORRIS Simon Tel 1: +44 1635 588951Company: MATSUSHITA COMMUNICATION INDUSTRIAL UK

Address: Daytona drive, Colthrop Mob : +44 7887 822389Thatcham Fax 1: +44 1 635 866 193BERKSHIRE RG 19 4ZD Fax 2:UNITED KINGDOM




Name: OHANA Alain Tel 1: +1 972 517 0709Company: BELLSOUTH MOBILITY DCS Tel 2:

Address: 3353 Peachtree Road N.E. Mob :Suite 300 Fax 1: +1 972 517 0709ATLANTA, GA 30326 Fax 2:UNITED STATES


Name: PASANEN Matti Tel 1: +358 2040 3674Company: SONERA Tel 2:

Address: PO Box 980 Mob : +358 400 400 173Fax 1: +358 2040 36242

00051 SONERA Fax 2:FINLAND


Name: PETERSEN Johan Tel 1: +33 4 92 94 42 06Company: ETSI/PT SMG Tel 2:

Address: 650 Route des Lucioles Mob : +33 6 1476 1450Fax 1: +33 4 93 65 28 17



Name: PIKE SimonSMG 8 Chairman Tel 1: +44 1 793 883 206

Company: LUCENT TECHNOLOGIES Tel 2:Address: Sigma Building, Widmill Hill Mob :

Business Park Fax 1: +44 1793 883 3232SWINDON, WILTSHIRE SN5 6PP Fax 2:UNITED KINGDOM


Name: PILLEKAMP Klaus-Dieter Tel 1: +49 2871 91 2621Company: SIEMENS AG Tel 2:

Address: PN KE T121 Mob : +1 7281 23680Kaiser-Wilhelm-Str. 56 Fax 1: +49 2871 91338746393 BOCHOLT Fax 2:GERMANY

E-Mail Internet: klaus-dieter.pillekampàpn.siemens.de

Name: PIRILÄ Hannu Tel 1: +358 10 505 4536Company: NOKIA MOBILE PHONES LTD Tel 2:

Address: PO BOX 86 Woenswunkatu 7EJ Mob : +358 50 3131 040Fax 1: +358 10 505 4770

24101 SALO Fax 2:FINLAND




Name: POPE Maurice Tel 1: +33 4 92 94 42 59Company: ETSI/SMS Dept. Tel 2:



Name: PORZIO GIUSTO Pietro Tel 1: +39 06 3900 9020Company: TELECOM ITALIA MOBILE (STET) Tel 2:

Address: Largo Tassoni, 323 Mob : +39 335 633 3565Fax 1: +39 06 3900 9033

00186 ROMA Fax 2:ITALY


Name: REICHL Wolfgang Tel 1: +43 1 797 8028Company: OEFEG / AUSTRIA Tel 2:

Address: PO Box 147 Mob : +43 664 400 1700FZG Arsenal Objekt 24 Fax 1: +43 1 797 80131103 WIEN Fax 2:AUSTRIA


Name: REMY Jean Gabriel Tel 1: +33 1 5568 3322Company: SFR Tel 2:

Address: 1, Place Carpeaux Mob : +33 6 09 71 11 99BP 601 Fax 1: +33 1 55 68 33 2592915 PARIS LA DEFENSE CEDEX Fax 2:FRANCE


Name: ROBINSON Bill Tel 1: +44 1256 790 548Company: MOTOROLA Tel 2:

Address: London Road Mob : +44 7771 507 472Old Basing, Basingstoke Fax 1: +44 1256 790 190HAMPSHIRE RG24 7JL Fax 2:UNITED KINGDOM


Name: RODERMUND Friedhelm Tel 1: +33 4 92 94 43 24Company: ETSI/PT SMG Tel 2:

Address: 650 Route des Lucioles Mob : +49 172 8900918Fax 1: +33 4 93 65 28 17





Name: RODRIGUEZ Carole Tel 1: +33 4 9294 4262Company: ETSI/PT SMG Tel 2:



Name: ROMUNEN Jukka Tel 1: +358 10 505 5462Company: NOKIA MOBILE PHONES Tel 2:

Address: PO BOX 86 Mob : +358 40556 5929Fax 1: +358 10 505 4600

24101 SALO Fax 2:FINLAND


Name: ROULE Jan Tel 1: +420 2 216 20 535Company: PAEGAS Tel 2:

Address: RADIOMOBIL Mob : +420 603 400 535Londynska 59, Fax 1: +420 2 216 20 53612001 PRAHA 2 Fax 2:CZECK REPUBLIC


Name: ROUSSEAU Emmanuel Tel 1: +33 1 4652 1264Company: ALCATEL MOBILE COMMUNICATIONS Tel 2:

Address: 32 Avenue Kléber Mob : +33 0 789 0195Fax 1: +33 1 4652 8024



Name: RUCK Harald Tel 1: +2712 311 2308Company: TELKOM SA Tel 2:

Address: Private Bag X74 Mob : +2782 7856 943Fax 1: +2712 311 1061

PRETORIA 0001 Fax 2:SOUTH AFRICA


Name: SAMUKIC Antun Tel 1: +33 4 92 94 43 52Company: ETSI/PT SMG Tel 2:

Address: 650 Route des Lucioles Mob : +33 6 09 26 15 00Fax 1: +33 4 93 65 28 17





Name: SANDEGREN GunnarSMG Vice Chairman Tel 1: +46 8 757 2507

Company: ERICSSON RADIO SYSTEMS AB Tel 2:Address: Torshamnsgatan 23 Mob : +46 70 591 2507

KISTA Fax 1: +46 8 404 804016480 STOCKHOLM Fax 2:SWEDEN


Name: SANDERS Michael Tel 1: +33 4 92 94 42 90Company: ETSI/PT SMG Tel 2:



Name: SASAKI Akio Tel 1: +81 3 5510 8594Company: ARIB Tel 2:

Address: Nittochi Bldg. 14F, 1-4-1 Mob :Kasugaseki, Chiyoda-ku Fax 1: +81 3 3592 1103TOKYO 100 0013 Fax 2:JAPAN


Name: SCHROETER Matthias Tel 1: +49 228 936 7120Company: DeTeMobil GmbH Tel 2:

Address: Landgrabenweg 151 Mob :PO Box 300463 Fax 1: +49 228 936 712953227 BONN Fax 2:GERMANY


Name: SCHUHOVÁ Zdena Tel 1: +420 603 620 301Company: RADIOMOBIL AS / PAEGAS Tel 2:



Name: SCHWARZ Holger Tel 1: +49 211 448 4782Company: E-PLUS MOBILFUNK GmbH Tel 2:

Address: E-Plus-Platz Mob : +49 177 448 4782Fax 1: +49 211 448 4046

40468 DUSSELDORF Fax 2:GERMANY




Name: SETTIMO Franco Tel 1: +39 125 624427Company: OMNITEL PRONTO ITALIA Tel 2:

Address: Via G. Jervis, 13 Mob : +39 348 999 8584Fax 1: +39 125 624 708

10115 IVREA (TO) Fax 2:ITALY


Name: SIMMONS Paul Tel 1: +33 1 39 44 55 95Company: NORTEL Tel 2:

Address: 19, avenue du Centre Mob : +33 6 07 21 01 72Montigny Le Bretonneux - PC CT 111 Fax 1: +33 1 39 44 50 1278928 YVELINES CEDEX 9 Fax 2:FRANCE


Name: SIMONIC Tomaz Tel 1: +386 61 1313 033Company: MOBITEL SLOVENIA Tel 2:

Address: Dunajska 22 Mob : +386 416 11242Fax 1: +386 61 132 1144

1000 LJUBLJANA Fax 2:SLOVENIA


Name: SOMERVILLE Michelle Tel 1: +44 1 344 380 640Company: KENWOOD Tel 2:

Address: Azure House, Bagshor Road Mob :BRACKMELL Fax 1:BERKS Fax 2:UNITED KINGDOM

E-Mail Internet:

Name: SU Huan-yu Tel 1: +1 949 221 6365Company: ROCKWELL SEMICONDUCTOR SYSTEMS Tel 2:

Address: 4311 Jamboree Road Mob :Newport Beach Fax 1: +1 949 221 6361CA 92660-3095 Fax 2:UNITED STATES


Name: SUNDBORG Jonas Tel 1: +46 8 404 8035Company: ERICSSON RADIO SYSTEMS AB Tel 2:

Address: ERA/U Mob : +46 70 6748035Fax 1: +46 8 404 8040

164 80 STOCKHOLM Fax 2: +46 70 616 8035SWEDEN




Name: SWINBURNE Martin Tel 1: +44 1 454 206716Company: ORANGE PCS LTD Tel 2:

Address: St. James Court, Great Park Road Mob : +44 973 202 678Almondsbury Fax 1: +44 1454 206629BRISTOL BS32 4QJ Fax 2:UNITED KINGDOM


Name: TAKABATAKE Tatsumi Tel 1: +81 471 85 7172Company: NEC Tel 2:

Address: 1131 Hinode Mob :Abiko Fax 1: +81 471 85 6863CHIBA Fax 2:JAPAN


Name: TARAZI Roger Tel 1: +33 4 92 94 42 28Company: ETSI/PT SMG Tel 2:



Name: THOMAS RémiSMG 7 Chairman - SMG 7 Signalling Chairman Tel 1: +33 1 45 29 64 07

Company: FRANCE TELECOM Tel 2:Address: CNET/DMR Mob : +33 6 07 01 22 35

38-40 Rue Général Leclerc Fax 1: +33 1 45 29 63 0792794 ISSY MOULINEAUX CEDEX 9 Fax 2:FRANCE


Name: THORLBY Paul Tel 1: +44 1684 895 030Company: DERA Tel 2:

Address: St. Andrews Road Mob : +44 802 355 596Malvern Fax 1: +44 1684 895 646WORESTERSHIRE W14 3PS Fax 2:UNITED KINGDOM


Name: TOCZE Lionel Tel 1: +33 2 99 84 68 57Company: CANON RESEARCH CENTRE FRANCE Tel 2:

Address: Rue de la Touche Lambert Fax 1: +33 2 99 84 11 3035517 CESSON SEVIGNE CEDEX Fax 2:FRANCE




Name: TOEPFER ArminSMG 1 Vice Chairman - GSM MoU SERG Chairman Tel 1: +49 211

533 2838Company: MANNESMANN MOBILFUNK GmbH Tel 2:

Address: Am Seestern 1 Mob : +49 172 2100 748Fax 1: +49 211 533 2804

40543 DÜSSELDORF Fax 2: +49 172 2100 748GERMANY


Name: TOGNETTI Guido Tel 1: +39 40 4192 359Company: TELITAL Tel 2:

Address: Viale Stazione di Prosecco 5/8 Mob :Fax 1: +39 40 251257

34010 SCONICO TRIESTE Fax 2:ITALY


Name: TOMPKINS Robert W. Tel 1: +44 1 923 224 538Company: ICO GLOBAL COMMUNICATIONS Tel 2:

Address: 16 Garden Close Fax 1: +44 1 923 3366 35WATFORD WD1 3DP Fax 2:UNITED KINGDOM


Name: TONELLI Paola Tel 1: +1 510 210 3445Company: AIRTOUCH EUROPE Tel 2:

Address: 2999 Oak Road Mob : +1 510 220 7797Fax 1: +1 510 210 3469

WALNUT CREEK, CA 94596 Fax 2:UNITED STATES


Name: TRONCHON Stéphane Tel 1: +33 4 92 92 4260Company: ETSI/Directorate Tel 2:



Name: TWINGLER Jonas Tel 1: +1 901 624 4450Company: DSC COMMUNICATION Tel 2:

Address: 3800 Forest Hill Irene Road Mob : +46 70 324 1012Memphis Fax 1: +1 901 624 4100TENNESSEE 38125 Fax 2:UNITED STATES




Name: URIE Alistair Tel 1: +33 1 3077 3623Company: ALCATEL Tel 2:

Address: MCD/CPG Mob : +33 6 0841 744510, rue Latécoère Fax 1: +33 1 30 77 08 8878141 VELIZY CEDEX Fax 2:FRANCE


Name: USAI PaoloSMG11 Vice Chairman - SMG11 SQ Chairman Tel 1: +33 4 92 94 42 36

Company: ETSI/PT SMG Tel 2: +33 4 92 94 42 66Address: 650 Route des Lucioles Mob : +39 335 387 164

Fax 1: +33 4 93 65 28 1706921 SOPHIA ANTIPOLIS CEDEX Fax 2:FRANCE


Name: VAINIKKA Jari Tel 1: +358 9 5116 8098Company: NOKIA TELECOMMUNICATIONS Tel 2:

Address: PO Box 300 Mob : +358 40 511 88 66Fax 1: +358 9 5116 8080

00045 NOKIA GROUP Fax 2:FINLAND


Name: VALME Niclas Tel 1: +46 8 601 7429Company: TELIA MOBILE AB Tel 2:

Address: Augustendalsvägen 7 Mob : +46 705884663Fax 1: +46 07 611 4663

131 86 NACKA STRAND Fax 2:SWEDEN


Name: VALTA Ekkehard Tel 1: +49 6131 18 2229Company: REG TP Tel 2:

Address: Canisiusstr. 21 Fax 1: +49 6131 18 561355122 MAINZ Fax 2:GERMANY


Name: VAN BOKHORST Ruud Tel 1: +31 35 689 35 61Company: PHILIPS BUSINESS COM. Tel 2:

Address: Anth. Fokkerweg 5 Mob :P.O. Box 32 Fax 1: +31 35 689 10 301200 JD HILVERSUM Fax 2:THE NETHERLANDS




Name: VAN DER AREND Peter Tel 1: +33 4 9294 4231Company: ETSI/PT SMG Tel 2: +33 4 9294 4262



Name: VASNIER Frédéric Tel 1: +33 1 46 52 12 47Company: ALCATEL MOBILE PHONES Tel 2:

Address: 32, avenue Kléber Mob : +33 6 08 43 43 78Fax 1: +33 1 55 66 7826


E-Mail Internet: frédé[email protected]

Name: VEDDER KlausSMG 9 Chairman Tel 1: +49 89 4119 1542

Company: GIESECKE & DEVRIENT GmbH Tel 2:Address: Prinzregentenstr.159 Mob :

Postfach 80 07 29 Fax 1: +49 89 4119 154081607 MÜNCHEN Fax 2:GERMANY


Name: VERBESTEL Willy Tel 1: +1 602 732 2339Company: MOTOROLA SATCOM Tel 2:

Address: 2501 S.Price Road Mob : +49 171 8566592G-1218 Fax 1: +1 602 732 6350CHANDLER, AZ 85248-2899 Fax 2:UNITED STATES


Name: VOKROUHLIKOVA Lenka Tel 1: +42 02 6701 1136Company: EURO TEL PRAHA spol Tel 2: +420 602 600 795

Address: Sokolovská 855/225 Fax 1: +42 02 6701 820019000 PRAHA Fax 2:CZECH REPUBLIC


Name: VOSTERS Jean Tel 1: +32 3 240 7541Company: ALCATEL BELL Tel 2:

Address: 1, Pl. Francis Wellesplein Mob : +32 75 83 61 96Fax 1: +32 3 240 9989

2018 ANTWERPEN Fax 2:BELGIUM




Name: WALKER Duncan Tel 1: +44 1 252 775200Company: ANITE Tel 2:

Address: SAT Development manager Mob :127 Fleet Road, Fleet Fax 1: +44 1 252 775 322HAMPSHIRE GU13 8PD Fax 2:UNITED KINGDOM


Name: WALKER MichaelSMG10 Chairman - SMG10 BSG Chairman Tel 1: +44 1635 503 886

Company: VODAFONE LTD Tel 2:Address: The Courtyard Mob : +44 385 277 687

2-4 London Road Fax 1: +44 1635 31127NEWBURY, BERKSHIRE RG14 1JX Fax 2:UNITED KINGDOM


Name: WALTER Knut Erik Tel 1: +47 2278 5525Company: TELENOR MOBIL AS Tel 2:

Address: St. Olavs Plass Mob : +47 9002 2727PO Box 6746 Fax 1: +47 2278 55000130 OSLO Fax 2:NORWAY


Name: WATANABE Kunio Tel 1: +81 44 754 3850Company: ARIB Tel 2:

Address: 4-1-1 Kamistodanaka Mob :Nakahara-Ku Fax 1: +81 44 754 3880KAWASAKI 211-88 Fax 2:JAPAN


Name: WATSON Andrew W.D. Tel 1: +44 1 793 566 230Company: MOTOROLA Tel 2:

Address: 16 Euroway Mob : +44 385 318 522Blagrove 2 Fax 1: +44 1 793 566225SWINDON SN5 8YW Fax 2:UNITED KINGDOM


Name: WEAVER Kerry Tel 1: +1 972 257 9811Company: NOKIA Tel 2:

Address: 2300 Valley View Lane Mob :Suite 100 Fax 1: +1 972 257 9988IRVING, TEXAS 75062 Fax 2:UNITED STATES

E-Mail Internet:



Name: WEILER Dirk Tel 1: +49 89 722 26203Company: SIEMENS AG Tel 2:

Address: ICN CA MS MA Mob : +49 171 334 0791Hofmannstraße 51 Fax 1: +49 89 722 2188281359 MÜNCHEN Fax 2: +49 89 722 57185GERMANY


Name: WIEBKE Thomas Tel 1: +49 6103 766 161Company: PANASONIC DEUTSCHLAND Tel 2:

Address: Monzastr. 4c Fax 1: +49 6103 766 16663225 LANGEN Fax 2:GERMANY


Name: WIENER Antony Tel 1: +44 181 214 2290Company: ONE-2-ONE Tel 2:

Address: Imperial Place Mob : +44 7 957 279 131Maxwell Road, Borehamwood Fax 1: +44 181 905 1671HERTS WD6 1EA Fax 2:UNITED KINGDOM


Name: WIKSTRÖM Tom Tel 1: +358 9 696 6877Company: TELECOM. ADMINISTRATION CENTRE Tel 2:

Address: Itämerenkatu 3A Mob : +358 50 3138 456Fax 1: +358 9 696 6811

00180 HELSINKI Fax 2:FINLAND


Name: WILLIAMS David Tel 1: +33 4 92 94 42 61Company: ETSI/PT SMG Tel 2:


E-Mail Internet:

Name: WURFFEL Emmanuelle Tel 1: +33 4 9294 4266Company: ETSI/PT SMG Tel 2:





Name: XIAOYUN Wang Tel 1: +86 10 63 604877Company: RITT Tel 2:

Address: MPT, Radio Dept. Mob : +86 138 1158303Yue Tan Nan Jie 11# Fax 1: +86 10 63604879100045 BEIJING Fax 2:CHINA


Name: YABUSAKI Masami Tel 1: +81 3 5563 8299Company: NTT DoCoMo Tel 2:

Address: Shin-Nikko Bldg. East Tower Mob : +33 6 8259 435810-1, Toranomon 2-Chome Minato-ku Fax 1: +81 3 5572 6526TOKYO 105-8436 Fax 2:JAPAN


Name: YAMAMOTO Kouji Tel 1:Company: NTT DoCoMo Tel 2:


JAPANE-Mail Internet:

Name: ZELMER Donald E. Tel 1: +1 404 841 2013Company: BELLSOUTH MOBILITY DCS Tel 2:

Address: 3353 Peachtree Road N.E. Mob :Suite 300 Fax 1: +1 404 841 2045ATLANTA, GA 30326 Fax 2:UNITED STATES


Name: ZHANG Huayan Tel 1: +86 10 6463 2288Company: ERICSSON (CHINA) CY LTD. Tel 2:

Address: No. 9 East Dongfang Road Mob : + 86139 1235194North Dongsanhuan Road Fax 1: +86 10 6461 5405BEIJING 100027 Fax 2:CHINA


Name: ZHIQIN Wang Tel 1: +86 10 680 94467Company: RITT Tel 2:

Address: MPT, Radio Dept. Mob :Yue Tan Nan Jie 11# Fax 1: +86 10 680 34801100045 BEIJING Fax 2:CHINA

E-Mail Internet:

ETSI SMG ETSI/SMG(98) 4 Annex 2Meeting n°27Prague, 12th - 16th of October, 1998

Annex 2: Status of CRs and new specifications presented to the meeting

Introduction :This following list contains the final status of all Change Requests,that were presented to SMG#27.The statistics (see below) is based on that list.

New specifications that were submitted for approval are also listed.

Statistics 16-Nov-98

Phase 2

39 approvedCRs 1 rejectedCRs

Phase R96

51 approvedCRs 1 withdrawnCRs

Phase R97

242 approvedCRs 2 postponed -> SMG#28CRs 2 withdrawnCRs

Phase R98

36 approvedCRs 1 withdrawnCRs

Phase UMTS

4 approvedCRs 1 email app by 18 Nov.CRs 1 informativeCRs 1 postponed -> SMG#28CRs

382 CRs were presented in total

CRs under responsibility of the following STCs have been submitted by the time of printing : 16-Nov-98

1 0CRs presented by SMG9 1CRs presented by SMG

128 2CRs presented by SMG87 3CRs presented by SMG47 4CRs presented by SMG5 6CRs presented by SMG

45 7CRs presented by SMG9 8CRs presented by SMG

25 9CRs presented by SMG3 10CRs presented by SMG2 11CRs presented by SMG

21 12CRs presented by SMG

382 CRs presented in total

Page 1 of 14

Status of CRs presented to SMG #27.

Status of new specifications presented to SMG #27.

TDoc SPEC PHASE SUBJECT STATUS NEW_VERS SOURCE

98-0674 02.19 R98 SIM Application Programming Interface (API) approved 7.0.0 SMG998-0557 02.43 R98 Support of Localised Service Area (SoLSA);Service description; Stage 1 Release 1998 approved 7.0.0 SMG198-0680 02.56 R98 Cordless Telephone System (CTS) Stage 1 approved 7.0.0 SMG198-0533 03.33 R98 Lawful Interception stage 2 informative 1.0.0 SMG1098-0534 03.35 R98 Immediate Service Termination (IST) stage 2 approved 7.0.0 SMG1098-0757 03.56 R98 CTS architecture description stage 1 informative 1.0.0 SMG1298-0776 03.57 R98 Mobile Station Application Execution Environment (MExE) Stage 2 informative 1.0.2 SMG498-0756 03.73 R98 SoLSA stage 2 informative 1.0.0 SMG1298-0718 04.72 R98 Call Deflection stage 3 informative 1.0.0 SMG398-0719 09.13 R97 Signalling interworking between ISDN ASE and MAP protocolsversion 2.0.0 (98P239) approved 6.0.0 SMG398-0543 13.68 R96 EN 301 419-3 ASCI Harmonised standard approved 5.0.0 SMG798-0542 13.69 R96 EN 301 419-7 R-GSM Harmonised standard approved 5.0.0 SMG798-0555 22.00 UMTS UMTS Phase 1 Specifications informative 1.0.0 SMG198-0558 22.75 UMTS Service aspects advanced addressing approved 3.0.0 SMG198-0754 23.01 UMTS General UMTS Architecture informative 1.0.0 SMG1298-0755 23.10 UMTS UMTS Access Stratum;Services and functions informative 1.0.0 SMG1298-0758 23.20 UMTS Evolution of the GSM platform towards UMTS informative 1.0.0 SMG1298-0536 33.21 UMTS UMTS security requirements informative 1.0.0 SMG10

Spec CR rev Phase Cat SUBJECT TDoc Status NEW_VERS

02.07 Mobile Station (MS) Features.A019 R98 B Addition of the SoLSA feature 98-0548 approved 7.0.0

02.11 Service Accessibility.A011 R98 B Addition of the SoLSA feature 98-0548 approved 7.0.0

02.17 Subscriber Identity Modules, Functional CharacteristicsA001 R96 B Alignment of GSM 02.17 with GSM 11.11 and GSM 11.14 98-0672 approved 5.1.0A003 R98 B Alignment of GSM 02.17 with GSM 11.11 and GSM 11.14 98-0672 approved 7.1.0

02.33 Lawful interception - stage 1A002 2 R98 C Location Dependent Interception 98-0532 approved 7.1.0A003 2 R98 C Lawful Interception security 98-0532 approved 7.1.0

Page 2 of 14


02.40 Procedures for Call Progress Indications.A002 R98 D Harmonization between GSM 02.40 version 5.0.0 and J-STD-007 Volu 98-0549 approved 7.0.0

02.72 Call Deflection Service description, Stage 1A001 R98 F General review of 02.72 /Allow final approval of the CD service 98-0550 approved 7.1.0

03.03 Numbering, Addressing and IdentificationA009 3 R96 F Definition of SSN for MAP signalling to the gsmSCF 98-0730 withdrawnA010 3 R97 F Definition of national SSNs for GPRS 98-0730 withdrawnA011 1 R97 A Definition of SSN for MAP signalling to the gsmSCF 98-0730 withdrawn

03.08 Organization of Subscriber DataA016 1 R97 C Signalling and SMS radio priority level 98-0725 approved 6.2.0

03.10 GSM Public Land Mobile Network (PLMN) Connection Types.A008 R98 D Clarification of RA0 adaptation function 98-0736 approved 7.0.0A009 R98 F Information transfer protocol model updates 98-0739 approved 7.0.0'strategic'

03.16 Subscriber Data ManagementA016 1 R97 F CAMEL capability handling 98-0724 approved 6.2.0

03.18 Basic Call HandlingA022 1 R97 F Corrections and alignments for CCBS & CAMEL Phase 2 98-0722 approved 6.2.0A023 R96 F Corrections for successful case of TCH allocation 98-0726 approved 5.6.0A024 R97 C Provide Subscriber Info for GPRS subscribers 98-0725 approved 6.2.0A025 R96 C Optionality of support for OR of basic mobile-to-mobile calls 98-0768 approved 5.6.0A026 R97 C Optionality of support for OR of basic mobile-to-mobile calls 98-0768 approved 6.2.0A027 1 R97 F Suppression of alerting to originating MS in the case of early ACM 98-0726 approved 6.2.0A028 1 R96 F Suppression of alerting to originating MS in the case of early ACM 98-0726 approved 5.6.0A029 R97 F Correction of handling for failure case of CCBS OG call handling 98-0721 approved 6.2.0

03.32 Universal Geographical Area Description (GAD)A002 1 R96 F Error correction in GSM 03.32 for value of uncertainty 98-0723 approved 5.2.0

03.40 Technical Realization of the Short Message Service (SMS) Point-to-point(PP)A083 R98 B User Data Header Identifier value for Concatenated Short Message 98-0738 approved 7.1.0'strategic'

A084 R98 B User Data Header Identifier value for Wireless Control Message Proto 98-0738 approved 7.1.0'strategic'

A085 R98 D Insertion of padding bits to a user data header 98-0738 approved 7.1.0

03.50 Transmission Planning Aspects of the Speech Service in the GSM Public Land Mobile Network (PLMN) System.A014 R96 F Correction of reference in Section 1.1 98-0704 approved 5.2.0A015 2 F Correction of reference in Section 1.1 98-0704 approved 4.5.0

03.60 General Packet Radio Service (GPRS) Service description; Stage 2A065 1 R97 F Deletion of the Standby timer function 98-0753 approved 6.2.0'strategic'

Page 3 of 14


A066 1 R97 F Clarification for the usage of combined procedures 98-0753 approved 6.2.0'strategic'

A068 1 R97 F Improvement for the SGSN change procedure 98-0753 approved 6.2.0'strategic'

A069 R97 F BSSGP flow control 98-0753 approved 6.2.0'strategic'

A070 2 R97 F Alignment of 03.60 on 08.18 CR "RAC added to cell identity IE" 98-0753 approved 6.2.0'strategic'

A071 R97 F Restoration procedures 98-0753 approved 6.2.0'strategic'

A072 2 R97 F Incremental Insert and Delete Subscriber Data procedures 98-0753 approved 6.2.0'strategic'

A073 R97 F PDP Context Modification for one NSAPI only 98-0753 approved 6.2.0'strategic'

A074 R97 F PDP context deactivation after GGSN failure 98-0753 approved 6.2.0'strategic'

A075 R97 F Generation and distribution of Charging Id 98-0752 approved 6.2.0A076 2 R97 F Signalling and SMS radio priority levels 98-0753 approved 6.2.0'strategic'

A077 1 R97 F Handling of GPRS Classmark 98-0753 approved 6.2.0'strategic'

A078 2 R97 F Alignment of references to NSAPI and addition of TI to context tables 98-0752 approved 6.2.0A079 1 R97 F Removing GPRS’s degradation of CAMEL’s Any Time Interrogation p 98-0752 approved 6.2.0A080 1 R97 F Inconsistency in MS unreachable specification between 09.18 and 03.6 98-0753 approved 6.2.0'strategic'

A082 1 R97 F Various improvements 98-0753 approved 6.2.0'strategic'

A088 R97 F GPRS information in the SIM and the ME 98-0753 approved 6.2.0'strategic'

A090 R97 F A interface suspend and resume 98-0753 approved 6.2.0'strategic'

03.64 Overall description of the GPRS radio interface; Stage 2A044 R97 F Clarification on PACCH allocation for fixed assignment 98-0663 approved 6.1.0A050 R97 F Changes on all chapters to align the spec. with other GPRS specificatio 98-0663 approved 6.1.0

03.78 CAMEL Phase 1 (stage 2)A025 2 R97 F CAMEL Phase 2 stage 2 98-0724 approved 6.2.0A029 1 R97 F Corrections 98-0724 approved 6.2.0A033 R96 F Corrections to any Time Interrogation 98-0723 approved 5.6.0A034 2 R97 F Interworking CAMEL with general Bearer Service 98-0724 approved 6.2.0A037 1 R97 C Removal of O_Not_Reachable and T_Not_Reachable detection points 98-0724 postponed -> SMG#28A043 R97 C GSM Forwarding Pending Indication in IDP Operation 98-0724 approved 6.2.0

03.79 Support of Optimal Routing phase 1 (stage 2)A006 R96 C Optionality of support for OR of basic mobile-to-mobile calls 98-0768 approved 5.4.0

03.93 Technical realization of Completion of Calls to Busy Subscriber (CCBS); Stage 2A005 1 R97 D Editorial cleanup on figure numbering 98-0720 approved 6.2.0A006 1 R97 F Correction of VMSC model 98-0720 approved 6.2.0A007 1 R97 F Correction of HLR functionality to support MAP(linked with CR 09.02 98-0720 approved 6.2.0A008 1 R97 F Correction of CCBS_Coordinator_HLR 98-0720 approved 6.2.0

04.07 Mobile Radio Interface Signalling Layer 3 - General AspectsA019 R97 F SNSM Primitives 98-0677 approved 6.2.0

Page 4 of 14


04.08 Mobile Radio Interface - Layer 3 SpecificationA329 1 R97 F Deletion of the STANDBY timer 98-0677 approved 6.2.0A330 1 R97 F Addition of downlink single block assignment for GPRS 98-0663 approved 6.2.0A332 R97 F Correction of packet downlink assignment procedure 98-0663 approved 6.2.0A333 R97 F Radio priority level signalling for MO SMS 98-0677 approved 6.2.0A335 3 R97 F Classmark split 98-0677 approved 6.2.0A336 1 R97 F Scheduling of SI-13 98-0663 approved 6.2.0A337 1 R97 F MS initiated detach procedure collision handling 98-0677 approved 6.2.0A339 1 R97 F Definition of IEI values for optional information elements 98-0677 approved 6.2.0A342 2 R97 F Clarification of the Classmark 3 IE 98-0662 approved 6.2.0A343 1 R97 F Various corrections to GSM 04.08 98-0677 approved 6.2.0A345 1 R97 F SAPI negotiation at AA PDP context activation 98-0677 approved 6.2.0A346 R97 F Addition of Network Operation mode in SI 13 98-0663 approved 6.2.0A347 1 R97 F Clarification of the GMM cause code handling 98-0677 approved 6.2.0A348 R97 F Deletion of Mac Mode in SI 13 98-0663 approved 6.2.0A349 1 R97 F Modification of PDP address IE coding 98-0677 approved 6.2.0A350 1 R97 F Allows Fixed or Dynamic Access mode in one phase packet access mo 98-0663 approved 6.2.0A351 R97 F Clarifications in the negotiation of the READY Timer value 98-0677 approved 6.2.0A352 R97 F Pb parameter defined in SI 13 used only on PCCH misplaced 98-0663 approved 6.2.0A355 2 F Clarification of CM3 and ES IND bit handling in classmark 1 and 2 98-0715 rejectedA357 1 R97 D Editorial changes in section 9.1 due to wrong numbering of tables and f 98-0698 postponed -> SMG#28A359 R97 D Editorial changes in section 9.2 due to wrong numbering of tables and f 98-0698 approved 6.2.0A360 R97 F RLC/MAC timers 98-0663 approved 6.2.0A363 1 R97 F QoS correction 98-0677 approved 6.2.0A364 R97 F The length of downlink TFI 98-0663 approved 6.2.0A365 1 R97 F Change of IEI for the allowed action IE in the DISCONNECT message 98-0588 approved 6.2.0A367 R97 D Editorial changes in section 9.3 and 10.5 due to wrong numbering of ta 98-0698 approved 6.2.0A368 1 R97 F Support of split pg cycle on CCCH 98-0663 approved 6.2.0A370 R96 F Clarification of the classmark 3 IE 98-0662 approved 5.11.0

04.14A002 R96 D Changes to 04.14 98-0662 approved 5.1.0

04.21 Rate Adaption on the Mobile Station - Base Station System (MS-BSS) Interface.A012 R98 D Synchronisation 98-0739 approved 7.0.0'strategic'

A013 R96 F Break handling 98-0736 approved 5.6.0

04.22 Radio Link Protocol (RLP) for Data and Telematic services on the (MS-BSS) Interface and the Base Station System-Mobile-Services SwitchinA017 R97 F Use of Poll/Final-Bit for REMAP 98-0736 approved 6.1.0A018 R97 F No XID during REMAP 98-0736 approved 6.1.0A019 R97 F Applicability of default values for REMAP procedure 98-0736 approved 6.1.0

Page 5 of 14


A020 R96 F Applicability of default values for REMAP procedure 98-0736 approved 5.5.0A021 R96 F No XID during REMAP 98-0736 approved 5.5.0

04.60 General Packet Radio Service (GPRS); Mobile Station (MS) - Base Station System (BSS) interface; Radio Link Control/ Medium Access ContrA031 1 R97 F Clarification of terminology for release of TBF 98-0663 approved 6.2.0A032 R97 F Clarification of terminology for LLC PDU (frames) 98-0663 approved 6.2.0A033 R97 F Radio Priority 98-0663 approved 6.2.0A034 2 R97 F Updates to 3.1 Vocabulary 98-0663 approved 6.2.0A035 1 R97 F Correction of various minor errors in clause 5 98-0663 approved 6.2.0A036 2 R97 F Clarification of the relation between Medium Access mode and MS M 98-0663 approved 6.2.0A037 1 R97 F Identifying a TBF 98-0663 approved 6.2.0A038 2 R97 F Editorial corrections 98-0663 approved 6.2.0A039 R97 F Packet Polling Request corrections 98-0663 approved 6.2.0A040 1 R97 F Setting of Retry (R) bit 98-0663 approved 6.2.0A041 R97 F Improvement of timer handling 98-0663 approved 6.2.0A042 R97 F Corrections of name of PACKET POWER CONTROL/TIMING ADV 98-0663 approved 6.2.0A043 R97 F Use of logical channel in response to PACKET CHANNEL REQUES 98-0663 approved 6.2.0A044 R97 F Editorial corrections 98-0663 approved 6.2.0A045 R97 F Fixed length TBF 98-0663 approved 6.2.0A047 1 R97 F Network prioritisation and transmission of Packet Dummy Control Blo 98-0663 approved 6.2.0A048 1 R97 F Packet Timeslot Reconfigure 98-0663 approved 6.2.0A049 1 R97 F Improvement of the DRX mode procedure 98-0663 approved 6.2.0A050 1 R97 F Operation of downlink TBFs 98-0663 approved 6.2.0A051 2 R97 F Corrections and improvements to clause 9 98-0663 approved 6.2.0A052 1 R97 F Development of the segmentation description 98-0663 approved 6.2.0A053 2 R97 F Corrections and improvements to clause 10 98-0663 approved 6.2.0A054 1 R97 F Description of M and E bits 98-0663 approved 6.2.0A055 1 R97 F Clarification of text in message 98-0663 approved 6.2.0A056 R97 F Alignment of message type to logical channel 98-0663 approved 6.2.0A058 R97 F Correction of reference for coding of parameter GPRS_MS_TXPWR_ 98-0663 approved 6.2.0A059 R97 F Introduction of RLC data unit 98-0663 approved 6.2.0A060 R97 F NC and Extended Measurement reporting and Cell Change Order proc 98-0663 approved 6.2.0A063 1 R97 F Restructuring of Packet Uplink Assignment message and Packet Times 98-0663 approved 6.2.0A064 1 R97 F Procedures on expiry of timer T3164 98-0663 approved 6.2.0A065 R97 F Fixed Allocation 98-0663 approved 6.2.0A066 1 R97 F Packet Access Reject 98-0663 approved 6.2.0A067 R97 F Uplink PDCH Allocation for Extended Dynamic Allocation 98-0663 approved 6.2.0A068 2 R97 F GAMMA/I_LEVEL measurements and suspending the downlink TBF 98-0663 approved 6.2.0A069 1 R97 F Procedures on expiry of timer T3168 98-0663 approved 6.2.0A070 2 R97 F Concurrent TBF procedures for half duplex operation 98-0663 approved 6.2.0

Page 6 of 14


A071 1 R97 F Broadcast of Packet PDCH Release on PACCH 98-0663 approved 6.2.0A072 R97 F Abnormal cases for Resource Reallocation for Uplink 98-0663 approved 6.2.0A073 2 R97 F Removal of throughput class from decisions on resource reallocation 98-0663 approved 6.2.0A074 1 R97 F Packet Access Reject 98-0663 approved 6.2.0A075 R97 F Use of the USF_GRANULARITY parameter 98-0663 approved 6.2.0A076 R97 F Dynamic allocation uplink RLC data block transfer 98-0663 approved 6.2.0A077 2 R97 F TBF Starting Time 98-0663 approved 6.2.0A078 R97 F Extended Dynamic Allocation Multislot Classes 98-0663 approved 6.2.0A079 R97 F Ending a downlink TBF and activating an uplink TBF 98-0663 approved 6.2.0A080 R97 F Handling of the countdown procedure at short access 98-0663 approved 6.2.0A081 2 R97 F Restructure of release procedures 98-0663 approved 6.2.0A082 1 R97 F Packet Resource Request 98-0663 approved 6.2.0A083 R97 F LLC frame type in Channel Request Description 98-0663 approved 6.2.0A084 R97 F Field mapping in the Channel Request Description information element 98-0663 approved 6.2.0A085 1 R97 F Throughput indication in Channel Request Description IE 98-0663 approved 6.2.0A086 1 R97 F Mandatory DRX parameters 98-0663 approved 6.2.0A087 R97 F Paging procedures 98-0663 approved 6.2.0A088 R97 F Use of the packet paging channel and correction of the paging message 98-0663 approved 6.2.0A089 4 R97 F Segmentation of RLC/MAC control messages 98-0663 approved 6.2.0A090 2 R97 F Use of PAGE MODE parameter 98-0663 approved 6.2.0A091 1 R97 F Structure of TBF establishment description 98-0663 approved 6.2.0A092 2 R97 F Cell change procedure corrections 98-0663 approved 6.2.0A093 R97 F Modifications to the access type values 98-0663 approved 6.2.0A094 R97 F Persistence control procedure modifications 98-0663 approved 6.2.0A096 1 R97 F Addition of Network Operation mode in PSI1 98-0663 approved 6.2.0A097 R97 F Deletion of Mac Mode in PSI 1 98-0663 approved 6.2.0A105 2 R97 F Corrections for the PACCH receiving during the fixed uplink assignme 98-0663 approved 6.2.0A106 1 R97 F Correction of Polling for Packet Downlink Ack/Nack 98-0663 approved 6.2.0A107 2 R97 F PR-field introduction to MAC header 98-0663 approved 6.2.0A110 R97 F Corrections to MAC abnormal cases 98-0663 approved 6.2.0A111 1 R97 F Corrections to downlink procedures 98-0663 approved 6.2.0A112 R97 F Corrections to Fixed Allocation procedures 98-0663 approved 6.2.0A114 1 R97 F Corrections to MAC procedures 98-0663 approved 6.2.0A115 R97 F Resolution of text merge problems in 04.60 v6.1.0 98-0663 approved 6.2.0A116 R97 F Corrections to PACKET TIMESLOT RECONFIGURE procedures 98-0663 approved 6.2.0A117 1 R97 F Corrections to RLC procedures 98-0663 approved 6.2.0A118 2 R97 F Undefined concurrent TBF conditions 98-0663 approved 6.2.0A119 1 R97 F RLC/MAC timers 98-0663 approved 6.2.0A120 1 R97 F Simplification of and corrections to Fixed Allocation reallocation 98-0663 approved 6.2.0

Page 7 of 14


A121 R97 F MS mode of operation 98-0663 approved 6.2.0A122 R97 F Clarification of PSI6 98-0663 approved 6.2.0A123 1 R97 F Change of name of the RR_PRIORITY parameter tp CALL_PRIORIT 98-0663 approved 6.2.0A125 R97 F Alignment of TFI description 98-0663 approved 6.2.0A126 R97 F Neighbour cell power measurements 98-0663 approved 6.2.0A128 R97 F Removal of duplicated IE in the Packet Release Request message 98-0663 approved 6.2.0A129 R97 F Support of split pg cycle on PCCCH 98-0663 approved 6.2.0

04.64 General Packet Radio Service (GPRS); Mobile Station - Serving GPRS Support Node (MS-SGSN) Logical Link Control (LLC) Layer SpecificaA031 R97 F A bit usage clarification 98-0677 approved 6.2.0A032 2 R97 F XID negotiation improvements 98-0677 approved 6.2.0A033 R97 F Release Indication Cause 98-0677 approved 6.2.0A034 2 R97 F Clarifications and corrections 98-0677 approved 6.2.0A035 1 R97 F Various improvements 98-0677 approved 6.2.0A036 1 R97 F Layer3 initiated vs. LLC-initiated link (re-)establishment 98-0677 approved 6.2.0

04.65 General Packet Radio Service (GPRS); Mobile Station (MS) - Serving GPRS Support Node (SGSN); Subnetwork Dependent Convergence ProA019 R97 F Corrections and clarifications 98-0677 approved 6.2.0A020 R97 F Acknowledged LLC operation establishment and release procedure 98-0677 approved 6.2.0A021 2 R97 F XID negotiation 98-0677 approved 6.2.0A022 R97 F TCP/IP header compression and Data compression 98-0677 approved 6.2.0A024 R97 F Data transfer 98-0677 approved 6.2.0A025 1 R97 F Replacement of "Segment offset" with "Segment number" 98-0677 approved 6.2.0

04.68 Group Call Control (GCC) ProtocolA002 2 R96 F GSM 04.68 Corrections. 98-0679 approved 5.1.0A003 R96 F Get Status Procedure 98-0679 approved 5.1.0A004 2 R96 F Set Status Procedure 98-0679 approved 5.1.0

04.69 Broadcast Call Control (BCC) protocolA001 2 R96 F GSM 04.69 Corrections. 98-0678 approved 5.1.0A002 R96 F Get Status Procedure 98-0678 approved 5.1.0A003 2 R96 F Set Status Procedure 98-0678 approved 5.1.0

05.02 Multiplexing and Multiple Access on the Radio PathA041 R97 F Clarification on PTCCH/U mappimg 98-0709 approved 6.3.0'strategic'

A042 R97 F Clarification on mappimg PCCCH 98-0709 approved 6.3.0'strategic'

A043 3 R97 F MS multislot classes and GPRS dynamic allocations 98-0639 approved 6.3.0'strategic'

05.05 Radio Transmission and ReceptionA076 2 R97 C False USF detection 98-0710 approved 6.3.0'strategic'

A077 R97 F Power control levels 29-31 for DCS1800 98-0710 approved 6.3.0'strategic'

Page 8 of 14


A078 R97 F DCS1800 MS sensitivity for GPRS 98-0710 approved 6.3.0'strategic'

A079 R96 F Correction of reference for MS test loop 98-0710 approved 5.10.0A080 R97 F Correction of reference for MS test loop 98-0710 approved 6.3.0

05.08 Radio Subsystem Link ControlA044 3 R97 C MS delay time in reporting a new strongest neighbouring cell 98-0711 approved 6.3.0'strategic'

A068 R97 F Clarification of Power Control 98-0711 approved 6.3.0'strategic'

A069 1 R97 F Measurement reporting 98-0711 approved 6.3.0'strategic'

A072 1 R97 F GPRS idle mode measurements 98-0711 approved 6.3.0'strategic'

A073 R96 F Clarification of Complete BA (SACCH) 98-0711 approved 5.9.0'strategic'

A074 R97 F Clarification of Complete BA (SACCH) 98-0711 approved 6.3.0'strategic'

A075 1 R97 F Tolerances for power control 98-0711 approved 6.3.0'strategic'

A076 1 R97 F GPRS downlink power control 98-0711 approved 6.3.0'strategic'

A077 R96 C MS delay time in reporting a new strongest neighbouring cell 98-0711 approved 5.9.0'strategic'

A078 2 2 F Clarification of Complete BA (SACCH) 98-0711 approved 4.22.0'strategic'

05.10 Radio Subsystem SynchronizationA017 2 R97 F Clarification of packet polling procedure for calculating new TA 98-0712 approved 6.3.0

07.01 General on Terminal Adaptation Functions (TAF) for Mobile Stations (MS)A032 R98 C Synchronisation and V.24 control signal handling in the MT 98-0739 approved 7.0.0'strategic'

07.02 Terminal Adaptation Functions (TAF) for Services Using Asynchronous Bearer CapabilitiesA013 R98 C Clarification and correction of the description of V.24 control signal ha 98-0739 approved 7.0.0'strategic'

07.07 Digital cellular telecommunications System (Phase 2) AT Command set for GSM Mobile Equipment (ME)A056 R97 B +CHSR 98-0736 approved 6.2.0A057 R96 B +CHSR 98-0736 approved 5.8.0A058 R98 B +CHSR 98-0736 approved 7.1.0A059 R98 F Power Class +CPWC 98-0737 approved 7.1.0A060 R97 F Amendment to +CR command 98-0735 approved 6.2.0A061 2 F Corrections to +CR and +CREG commands 98-0737 approved 4.4.0A062 R96 F Corrections to +CR and +CREG commands 98-0737 approved 5.8.0A063 R97 F Corrections to +CR and +CREG commands 98-0737 approved 6.2.0A064 R98 F Corrections to +CR and +CREG commands 98-0737 approved 7.1.0A065 R98 F Amendment to +CR command 98-0735 approved 7.1.0

07.10 Terminal Equipment to Mobile Station (TE-MS) multiplexer protocolA006 R97 B Include the RPN and RLS commands 98-0737 approved 6.2.0A007 R97 F Editorial Corrections 98-0737 approved 6.2.0A008 R97 D Clarification of the DISC command 98-0737 approved 6.2.0A009 R97 D Clarification of the C/R bit 98-0737 approved 6.2.0

Page 9 of 14


A010 R97 D Clarification of the CRC 98-0737 approved 6.2.0A011 R97 D Clarification of the NSC command 98-0737 approved 6.2.0A012 R97 F Correction of the P/F bit 98-0737 approved 6.2.0A013 R97 C Improvements to the Remote Parameter Negotiation Command 98-0737 approved 6.2.0A014 R97 F Correction of BOFC and EOFC value / Default assignment of DLC pri 98-0737 approved 6.2.0A015 R97 B XON/XOFF flow control in MSC modem signal 98-0737 approved 6.2.0

07.60 General Packet Radio Service (GPRS); Mobile Station (MS) supporting GPRSA008 R97 B Addition of a new AT command, +CGREG, to display current GPRS r 98-0735 approved 6.2.0'strategic'

A009 R97 B Addition of a new AT command, +CGSMS, to select the service for th 98-0735 approved 6.2.0'strategic'

A011 R97 F Corrections and clarifications, mainly to the AT commands specificatio 98-0735 approved 6.2.0A012 R97 B Addition of a GPRS extension to the existing 07.07 AT command, Ser 98-0735 approved 6.2.0'strategic'

08.08 Mobile Switching Centre - Base Station system (MSC-BSS) Interface Layer 3 SpecificationA115 R97 B BSS to BSS information 98-0662 approved 6.2.0A116 R97 B Pre-emption confirmation by serving BSC 98-0662 approved 6.2.0A117 R97 B Radio information of target cell for external HO 98-0662 approved 6.2.0A118 R97 B Current channel type 2 introduction 98-0662 approved 6.2.0A119 R97 B A interface signalling for GPRS suspend/resume 98-0663 approved 6.2.0

08.18 General Packet Radio Service (GPRS); Base Station System (BSS) - Serving GPRS Support Node (SGSN); BSS GPRS Protocol (BSSGP)A022 1 R97 F Correction to scope of NSEI 98-0663 approved 6.2.0A023 R97 F Addition of IMSI to RA-CAPABILITY-UPDATE-ACK 98-0663 approved 6.2.0A024 R97 F Correction of the leaky bucket algorithm 98-0663 approved 6.2.0A025 2 R97 F Add a new IE in FLUSH-LL-ACK-PDU and LLS-DISCARD PDU 98-0663 approved 6.2.0A026 R97 F Clarification of BVC measurements 98-0663 approved 6.2.0A030 1 R97 F Mapping of BVCI and cell identifier 98-0663 approved 6.2.0A031 R97 F Incorrect DRX parameter IE size 98-0663 approved 6.2.0

08.20 Rate Adaptation on the Base Station System - Mobile Service Switching Centre (BSS-MSC) Interface.A005 R98 D Synchronisation 98-0739 approved 7.0.0'strategic'

09.02 Mobile Application Part ( MAP) SpecificationA129 1 R97 A E.214 addressing of the HLR 98-0726 approved 6.2.0A132 1 R97 F Removal of redundant information from GSM 09.02 98-0726 approved 6.2.0A133 1 R97 F Clarification on applicability of application contexts 98-0725 approved 6.2.0A136 R97 F Correction to status reporting procedure 98-0721 approved 6.2.0A137 R96 F Extending the applicability of GMSC Address in ProvideRoamingNum 98-0723 approved 5.11.0A138 R97 F Extending the applicability of GMSC Address in ProvideRoamingNum 98-0724 approved 6.2.0A139 2 R97 D Clarification when the SMS over GPRS functionality is not supported 98-0725 approved 6.2.0A145 R96 A Removal of redundant information from GSM 09.02 98-0726 approved 5.11.0A147 1 R97 F Correction to the status reporting procedure in the VLR(linked with CR 98-0721 approved 6.2.0

Page 10 of 14


A148 R96 F Clarification of limit on length of O-CSI in MAP_RESUME_CALL-H 98-0723 approved 5.11.0A149 R97 F Clarification of limit on length of O-CSI in MAP_RESUME_CALL-H 98-0724 approved 6.2.0A150 1 R97 F ASN.1 correction 98-0726 approved 6.2.0A151 R97 F Removal of CCBS-feature from SS-Data 98-0721 approved 6.2.0A152 1 R97 C Support of CAMEL Phase 2 98-0724 approved 6.2.0A153 1 R97 F Correction in overload control tables for GPRS operations applicability 98-0725 approved 6.2.0A154 R97 F Usage of ShortMsgRelayPackage-v2 in GPRS 98-0725 approved 6.2.0A158 1 R97 F Restricting the use of extension containers in RegisterCCEntry and Era 98-0721 approved 6.2.0

09.07 General Requirements on Interworking between the Public Land Mobile Network (PLMN) and the Intergrated Services Digital Network (ISDA039 R96 F Correction 98-0736 approved 5.8.0A040 R98 D Clarification of V.120 interworking 98-0739 approved 7.0.0'strategic'

A041 R98 C Synchronisation and V.24 control signal handling in the IWF 98-0739 approved 7.0.0'strategic'

A042 2 F V.24 signalling 98-0739 approved 4.13.0'strategic'

A043 R98 F Clarification on autobauding indication in GSM-BC 98-0736 approved 7.0.0A044 R96 A V.24 signalling 98-0739 approved 5.8.0'strategic'

09.18 General Packet Radio Service (GPRS); Serving GPRS Support Node (SGSN) - Visitors Location Register (VLR); Gs interface layer 3 specificaA005 R97 F Completion of the re-naming of BSSAP+-IDENTITY-REQUEST mess 98-0677 approved 6.2.0A006 1 R97 F Text clarification and "MS class" term changed in to "MS in class mod 98-0677 approved 6.2.0A007 R97 F BSSAP+-MS-UNREACHABLE Message type 98-0677 approved 6.2.0

09.60 General Packet Radio Service (GPRS); GPRS Tunnelling Protocol (GTP) across the Gn and Gp Interface;A022 1 R97 F Modification of the coding of the Cause values of the Cause informatio 98-0725 approved 6.2.0A023 1 R97 F Clarification of the use of the T-PDU Sequence Number values 98-0725 approved 6.2.0A024 1 R97 F Corrections and clarifications. 98-0725 approved 6.2.0A025 1 R97 F Charging ID to three GTP message types 98-0725 approved 6.2.0A026 R97 F Modification of the length of the protocol messages 98-0725 approved 6.2.0A027 2 R97 F Information Elements: Clarification of the handling of the unused bits, 98-0725 approved 6.2.0A028 2 R97 F Clarification of the handling of protocol errors in the Error handling se 98-0725 approved 6.2.0A029 R97 F Update of the Protocol Configuration Options IE 98-0725 approved 6.2.0

09.61 General Packet Radio Service (GPRS); Interworking between the Public Land Mobile Network (PLMN) supporting GPRS and Packet Data NA006 R97 F Protocol Configuration Options at PDP context activation failure 98-0735 approved 6.3.0A008 R97 F Clarifications on IP interworking 98-0735 approved 6.3.0

09.78 CAMEL Application Part phase 1 (stage 3)A031 2 R97 F Corrections on GSM 09.78 98-0724 approved 6.2.0A033 1 R97 F Support of CAMEL Phase 2 98-0724 approved 6.2.0

11.10-1 Conformance SpecificationA473 2 F CR to section 34.3.3 Correction of the content of the Cell Broadcast m 98-0546 approved 4.24.0

Page 11 of 14


A474 R96 F CR to section 34.3.3 Correction of the content of the Cell Broadcast m 98-0695 approved 5.7.0A475 R96 B CR on Introduction of cell change tests for VGCS/ VBS 98-0695 approved 5.7.0A476 R96 B CR to section 3.2.2 on Applicability of R-GSM RF tests 98-0695 approved 5.7.0A477 2 F CR to section 26.1.2.2.1 EFR signalling/Handover/active call/successfu 98-0546 approved 4.24.0A478 R96 F CR to section 26.1.2.2.1 EFR signalling/Handover/active call/successfu 98-0695 approved 5.7.0A479 2 F CR to section 14.7 blocking and spurious response 98-0546 approved 4.24.0A480 R96 F CR to section 14.7 blocking and spurious response 98-0695 approved 5.7.0A481 2 F CR to section 26.6.15 DCS HO Tests, NCD to include missing BCCH 98-0546 approved 4.24.0A482 R96 F CR to section 26.6.15 DCS HO Tests, NCD to include missing BCCH 98-0695 approved 5.7.0A483 2 F CR for Clarification on 34.2.1 TC testing of TC1M 98-0546 approved 4.24.0A484 R96 F CR for Clarification on 34.2.1 TC testing of TC1M 98-0695 approved 5.7.0A485 R96 B CR to section 3.2.2 Addition of ASCI cell change signalling tests Appli 98-0695 approved 5.7.0A486 2 F CR to section 26.11.2.2.3.3 Multiband BCCH / Intercell Handover 98-0546 approved 4.24.0A487 R96 F CR to section 26.11.2.2.3.3 Multiband BCCH / Intercell Handover 98-0695 approved 5.7.0A488 2 F CR for removal of checks on Classmark 1,2,3 in the PIXIT statements 98-0546 approved 4.24.0'strategic'

A489 R96 F CR for removal of checks on Classmark 1,2,3 in the PIXIT statements ( 98-0695 approved 5.7.0'strategic'

A490 2 F CR on UA frame with different information field 98-0546 approved 4.24.0A491 R96 F CR on UA frame with different information field 98-0695 approved 5.7.0A492 2 F CR to section 32.11.x Intra cell channel change from TCH/HS to a TC 98-0696 approved 4.24.0A493 R96 F CR to section 32.11.x Intra cell channel change from TCH/HS to a TC 98-0697 approved 5.7.0A494 2 F CR to section 32.12.x Intra cell channel change from TCH/FS to a TC 98-0696 approved 4.24.0A495 R96 F CR to section 32.12.x Intra cell channel change from TCH/FS to a TC 98-0697 approved 5.7.0A496 2 F CR to section 26.6.3.2 Measurement reporting 20s requirement in sing 98-0696 approved 4.24.0A497 R96 F CR to section 26.6.3.2 Measurement reporting 20s requirement in sing 98-0697 approved 5.7.0A498 2 F CR to section 26.6.3.6 Measurement reporting 20s requirement in mult 98-0696 approved 4.24.0A499 R96 F CR to section 26.6.3.6 Measurement reporting 20s requirement in mult 98-0697 approved 5.7.0

11.10-3 Layer3 (L3) Abstract Test Suite (ATS)C378 2 F Implementation errors in Handover test cases for Releasing the Channe 98-0540 approved 4.24.0C379 2 F SI3 coding conflict in 26.2.4.3 and 26.2.4.4 98-0540 approved 4.24.0C380 2 F Implementation errors in Handover test cases cause L2 reaching N200 l 98-0540 approved 4.24.0C381 2 F Implementation error in Handover test cases sends wrong SysInfo6 me 98-0540 approved 4.24.0C382 2 F Correction for DCS frequencies for 26_6_4_1 98-0540 approved 4.24.0C383 2 F DCS Handover Tests, NCD to include BCCH arfcn 98-0540 approved 4.24.0C384 2 B Implementing TDoc 7-67/98 98-0540 approved 4.24.0C385 2 F Problem implementing a TTCN pre-defined operation 98-0540 approved 4.24.0C386 2 F DCS implementation error in the 26.6.5.1 test case 98-0540 approved 4.24.0C387 2 F Implementation errors in the 26.6.5.4 test case series 98-0540 approved 4.24.0C388 2 F Problem with conflicting carrier initialisation in TC_20_15 98-0540 approved 4.24.0C389 2 F Implementation Error: Incorrect Use Of Cell Allocation Data Strucutur 98-0540 approved 4.24.0

Page 12 of 14


C390 2 F Implementation problems in 26.6.13 series DCS Test Cases 98-0540 approved 4.24.0C391 2 F Problem in MO test cases for Dual Rate phones 98-0540 approved 4.24.0C392 2 F RF Signal parameter change for TC_20_1 98-0540 approved 4.24.0C393 2 F Implementation of Tdoc SMG7 137/98 (Hopping Channel required) 98-0540 approved 4.24.0

11.11 Subscriber Identity Module - Mobile Equipment (SIM-ME) Interface.A071 R98 C Enhanced image coding schemes (colour icons) 98-0671 approved 7.1.0A072 1 R98 D Addition of reference to PCS 1900 98-0671 approved 7.1.0

11.14 SIM Application ToolkitA084 R96 B Introduction of a 1bis SIM toolkit class for release 96 98-0669 approved 5.9.0A087 R97 B Introduction of a 1bis SIM toolkit class for release 97 98-0669 approved 6.2.0A091 1 R98 C "Yes/No" response for GET INKEY 98-0670 approved 7.1.0A092 R98 F Alignment of coding of card reader status event 98-0670 approved 7.1.0A093 R97 F Additional information field mandatory in case of USSD Return Error r 98-0670 approved 6.2.0A094 R98 F Additional information field mandatory in case of USSD Return Error r 98-0670 approved 7.1.0A095 R97 F Possible result values for SET UP EVENT LIST command 98-0670 approved 6.2.0A096 R96 F Clarification regarding the ME changing the contents of SIM command 98-0670 approved 5.9.0A097 R97 A Clarification regarding the ME changing the contents of SIM command 98-0670 approved 6.2.0A098 R98 A Clarification regarding the ME changing the contents of SIM command 98-0670 approved 7.1.0A099 R97 F Clarification about USSD return result 98-0670 approved 6.2.0A100 R98 F Clarification about USSD return result 98-0670 approved 7.1.0A101 R97 F Clarification of the ’93 00’ status response handling 98-0670 approved 5.9.0A102 R96 F Clarification of the ’93 00’ status response handling 98-0670 approved 6.2.0A103 R98 F Clarification of the ’93 00’ status response handling 98-0670 approved 7.1.0A104 R98 B New command - SETUP IDLE MODE TEXT 98-0670 approved 7.1.0A108 R98 C Handling of DTMF in SETUP CALL command 98-0670 approved 7.1.0A109 R97 F Interaction between call control by SIM / MO short message control an 98-0670 approved 7.1.0A110 R98 F Interaction between call control by SIM / MO short message control an 98-0670 approved 7.1.0A111 4 R98 B Enhancement to Proactive SIM that enables the SIM to issue AT comm 98-0605 approved 7.1.0'strategic'

A112 R98 B Introduction of a 1bis SIM toolkit class for release 98 98-0669 withdrawn

11.21 GSM Radio Aspects Base Station System Equipment SpecificationA077 R96 F Addition to chap. 4.10.5 to define a BTS with separated antenna ports 98-0742 approved 5.4.0A078 2 F Addition to chap. 4.10.5 to define a BTS with separated antenna ports 98-0742 approved 4.12.0A079 1 R96 F Reduction of Half Rate Speech (TCH/HS) number of samples 98-0742 approved 5.4.0A080 1 2 F Reduction of Half Rate Speech (TCH/HS) number of samples 98-0742 approved 4.12.0A081 2 F Erroneous frame indication performance 98-0742 approved 4.12.0A082 R96 F Erroneous frame indication performance 98-0742 approved 5.4.0A083 R96 E Clarification on conformance requirements for testcases 6.7/6.8 98-0742 approved 5.4.0A084 2 E Clarification on conformance requirements for testcases 6.7/6.8 98-0742 approved 4.12.0

Page 13 of 14


11.24 GSM Transcoding and Rate Adaptation: Base Station System Equipment SpecificationA005 2 F Clarification of tests which can be made via the radio interface 98-0740 approved 4.3.0

12.05 Subscriber Related Call and Event Data.A023 R97 B Enhancement to HSCSD call records 98-0667 approved 6.0.0A024 R97 C Addition of Speech codec parameters 98-0667 approved 6.0.0

12.11 Maintenance of the Base Station System (BSS).A005 R97 F Correction of the terminology "Basic Services" 98-0665 approved 6.1.0

12.15 GPRS chargingA001 R98 B Addition of a charging protocol 98-0666 approved 7.0.0'strategic'

A002 R97 F Clarification to "GPRS charging logical architecture figure" and editori 98-0666 approved 6.1.0

22.01 Universal Mobile Telecommunications System (UMTS): Service aspects; Service principlesA007 UMTS C Removal of Role Model in order to improve clarity 98-0553 approved 3.3.0'strategic'

A008 1 UMTS B Network Selection Including GMPCS 98-0553 postponed -> SMG#28 3.3.0'strategic'

A009 UMTS F Removal of references to IN and B-ISDN 98-0553 approved 3.3.0A010 UMTS D Clarification on Multiple User Profile 98-0682 approved 3.3.0

22.07 UMTS; Terminal and smart card conceptsA001 UMTS F Electronic money application requires USIM presence 98-0554 approved 3.1.0

30.01 UMTS Baseline document; Positions on UMTS agreed by SMGA001 1 UMTS B Changes reflecting strategic decisions at SMG #26 98-0790 email app by 18 Nov. 3.4.0'strategic'

33.20 Security principles for the UMTSA001 UMTS F Complete new description of the UMTS security principles 98-0535 informative'strategic'

TBR19 General Attachment Requirements for GSM Mobile StationsA013 2 B Conversion of TBR19 into GSM 13.01-1 (TS 301 419 Harmonised sta 98-0544 approved 4.0.0'strategic'

TBR31 General Attachment Requirements for DCS Mobile StationsA007 2 B Conversion of TBR31 into GSM 13.01-2 (TS 301 431 harmonised stan 98-0545 approved 4.0.0'strategic'

Page 14 of 14

SMG#27 Temporary document List

Number

Title Source Agenda item

Replaced by Tdoc

P-98-0245 (SMG#25 TD ) General guidelines for Automatic Call and SMS execution

Ad Hoc Group of SMG#25

For Info

P-98-0531 Status report of SMG10 to SMG#27 SMG10 6.10 + 7.10

P-98-0532 Non strategic CRs to GSM 02.33 Lawful Interception stage 1 CRs GSM 02.33-A002r2 and -A003r2

SMG10 6.10

P-98-0533 Cover notes to GSM 03.33 Lawful Interception stage 2; version 1.0.0

SMG10 6.10

P-98-0534 Cover notes to GSM 03.35: Immediate Service Termination (IST) - Stage 2; version 2.0.0

SMG10 6.10

P-98-0535 Strategic CR 001 to GSM 33.20: Security principles for UMTS; version 3.1.0

SMG10 7.10

P-98-0536 Cover notes to GSM 33.21: UMTS Security requirements; version 1.0.0

SMG10 7.10

P-98-0537 Answer to liaison statement Antenna Feeder Loss Compensator (AFLC)

Joint GTAAB / PCN TAEG

6.7

P-98-0538 Study of GSM Phase 2+ Priorities CETECOM GmbH 6.13 P-98-0539 Letter on harmonization of the IMT-2000 RTT

dated 10/08/98 TIA For Info

P-98-0540 TTCN CRs to GSM 11.10-3, v.4.23.0 SMG7 6.7 P-98-0541 SMG7 Status Report at SMG#27 SMG7 6.7 P-98-0542 R-GSM TBR Module - EN 301 419-7 R-GSM

Harmonised standard for information SMG7 6.7 P-98-0792

P-98-0543 ASCI TBR Module - EN 301 419-3 ASCI Harmonised standard for information

SMG7 6.7

P-98-0544 TBR 19 new version (strategic) - Conversion of TBR 19 to Harmonised standard EN 301 419-1 (GSM 13.01 Part 1)

SMG7 6.7

P-98-0545 TBR 31 new version (strategic) - Conversion of TBR 31 to Harmonised standard EN 301 431-1 (GSM 13.01 Part 2)

SMG7 6.7

P-98-0546 Phase 2 CRs to 11.10-1 (Signalling) for Approval SMG7 6.7 P-98-0547 SMG1 Status Report SMG1 6.1 P-98-0548 2 Non strategic CRs on addition of the SoLSA

feature to GSM 02.07 - Mobile Stations (MS) features and GSM 02.11 - Service accessibility

SMG1 6.1

P-98-0549 Non strategic CR on harmonization to GSM 02.40 Procedure for call progress indications

SMG1 6.1

P-98-0550 Non strategic CR on Call Deflection Interaction with other Supplementary Services to GSM 02.72 Call Deflection Service description, Stage 1

SMG1 6.1

P-98-0551 Strategic CR on Removal of Role Model to UMTS 22.01 Service aspects; Service principles

SMG1 7.1

P-98-0552 Strategic CR on Network Selection to UMTS 22.01 Service aspects; Service principles

SMG1 7.1

P-98-0553 Non Strategic CR on Network Selection to UMTS 22.01 Service aspects; Service principles

SMG1 7.1

P-98-0554 Non strategic CR on Security Aspects relative to USIM & Payment Methods - UMTS 22.07 Terminal and smard card concepts

SMG1 7.1

P-98-0555 UMTS 22.00 UMTS Phase 1 Specification and associated UMTS Phase 1 Work Items

SMG1 7.1

P-98-0556 GPRS PHASE 2 WIs - 6 WI Release 98 - 5 WI Release 99

SMG1 6.1

Number


Replaced by Tdoc

P-98-0557 GSM 02.43 v2.0.0 Support of Localised Service Area (SoLSA);Service description; Stage 1 Release 1998

SMG1 6.1

P-98-0558 UMTS 22.75 version 2.3.0 Service aspects; Advanced Addressing

SMG1 7.1

P-98-0559 UMTS 22.71v3.0.1 Automatic Establishment of Roaming Relationships

SMG1 7.1

P-98-0560 LS to ECTEL TMS on Impact of Telecomms Data Protection Directive on GSM Standards

SMG1 6.1

P-98-0561 LS to SMG, SMG3 on WI of CCNRy and CCNRc SMG1 6.1 P-98-0562 Results of AMR Selection Phase (revision of TD

702/98) SMG11 6.11

P-98-0563 STATUS REPORT of WG WOME WOME Chairman 5.7 P-98-0564 Recommendation for Pursuit of Convergence of

Radio Access Standards within ETSI QUALCOMM Europe 7.8

P-98-0565 WOME comments to draft working procedures 3GPP

WOME 5.6

P-98-0566 SMG4 Status Report to SMG#27 (slides) SMG4 Chairman 6.4 P-98-0567 Standardising Embedded Applications in UMTS SMG4 Chairman 6.4 P-98-0568 Not allocated P-98-0569 Guidelines for the Planning, Development and

Documentation of UMTS Phase 1 Standards BT 7.8

P-98-0570 Chairman’s Report - From SMG#26 in June 98 to SMG#27 in October 98

SMG Chairman 2

P-98-0571 Agenda and Schedule of SMG#27 12-16 October 1998

SMG Chairman 0

P-98-0572 T1P1.5 Status Report to SMG#27 T1P1.5 Chairman 4 P-98-0573 Presentation to SMG#27 by ECTEL TMS Prague

12 October 1998 ECTEL TMS 4

P-98-0574 During the meeting held in Tokyo 7-9 October 1998 ARIB, ETSI, T1, TTA and TTC agreed this framework document

ETSI Director General

5.7

P-98-0575 Selection test results from RITT RITT 6.11 P-98-0576 LS to NMT MoU on GSM 450 Status within ETSI

SMG SMG Chairman For Info

P-98-0577 Extraordinary GA decisions on EPP scope - Document ETSI/BOARD-GLOBAL#11(98)03

ETSI Board For Info

P-98-0578 Optimisation of the AMR codec FT, Cegetel 6.11 P-98-0579 EDP-R for Abandon detection point in CAMEL

phase 2 France Telecom 6.3

P-98-0580 Impact of Draft R&TTE Directive on UMTS specifications

T-Mobil 7

P-98-0581 Input of the SMG community to the preparation work of the R&TTE Directive

T-Mobil 6.7

P-98-0582 Letter to SMG Chairman on Harmonization CRs for Release 98

Chairman, T1P1 6.5

P-98-0583 New Work Item for GPRS/PCS1900 Chairman, T1P1 6.5 P-98-0584 Support for the completion of CTS work item Alcatel,

TeleDanmark, France Telecom, Telstra, Mitsubishi Nortel, NEC

6.10

P-98-0585 SMG3 Status Report to SMG#27 (Slides) SMG3 Chairman 6.3 P-98-0586 GSM 10.56 v.2.0.2 - GSM Cordless Telephony

System CTS, Phase 1 WI Rapporteur 6.10

Number


Replaced by Tdoc

P-98-0587 Input document to SMG7 and TC SMG regarding GPRS - Market Needs on GRPS and influence on SMG7 GPRS Subgroup

Cetecom, Ericsson, Mannesmann Mobilfunk

6.7

P-98-0588 CRs to 04.08 on CCBS SMG3 6.3 P-98-0589 Adaptive Multi-Rate Speech Codec Standard

Completion North America GSM Alliance

6.11

P-98-0590 Performance comparison between GSM Half-Rate and AMR candidates under background noise conditions

Rockwell 6.11

P-98-0591 Commitment for finalizing the AMR specifications Nokia 6.11 P-98-0592 Ericssons comments on AMR Ericsson 6.11 P-98-0593 Completion of the AMR standard Nortel 6.11 P-98-0594 Comment on CR A111 "Enhancement to allow the

SIM to issue AT commands" Nokia, Ericsson 6.9

P-98-0595 R&TTE Presentation - ERC Plenary Meeting 29 June 1998

M. Bogers, DG XIII For Info

P-98-0596 AMR Implementability and Commitment for Further Work

Siemens 6.11

P-98-0597 Selection of the AMR Codec BT, Cellnet, CSELT, E-Plus, Ericsson, Finnet Group, GSM North America, Italtel, Mannesmann Mobilfunk, Marconi, Motorola, Nokia, Omnitel Pronto Italia, One2One, Siemens, Smartone, Telia, Telital, TIM

6.11

P-98-0598 Reports of SMG Advisory Groups before SMG#27 PT SMG For Info P-98-0599 Meeting report of SMG-CG #27, Düsseldorf,

October, 1998 SMG-CG For Info

P-98-0600 Strategic CR to 11.14 (R98) "SIM application toolkit"

Vodafone 6.9 P-98-0605

P-98-0601 Qualcomm Press Release Qualcomm 7. P-98-0602 Proposed liaison to MoU on Allocation of Sub-

System Number SMG 6.12

P-98-0603 Strategic CR to 11.14 (R98) "SIM application toolkit" (revision of TD 98/0600)

Vodafone 6.9 P-98-0605

P-98-0604 Discussion about CR (A008) to TS 22.01 on Network Selection

Nokia 7.1

P-98-0605 Strategic CR to 11.14 (R98) "SIM application toolkit" (revision of TD 98/0603)

Vodafone 6.9

P-98-0606 SMG#27 CD ROM Order Form ETSI P-98-0607 EDP-R for Abandon detection point in CAMEL

phase 2 France Télécom, Nokia

6.3

P-98-0608 Interim Report of the UMTS IPR Working Group (September 1998)

UMTS IPR Working Group

7.7

P-98-0609 Not allocated P-98-0610 Liaison statement to TRAC - CTS FP Scope

Statement ETSI/SMG 6.10

P-98-0611 Liaison Statement to TC ERM on System Description of UTRA

SMG8 Chairman 6.11

P-98-0612 Testability of AMR in the BSS SMG8 Chairman 6.11 P-98-0613 Importance of Standardising O&M in UMTS Vodafone, MMO,

Cellnet, Telia 7.6

Number


Replaced by Tdoc

P-98-0614 Press Release - Suppliers set up Worldwide Industry Organisation to promote GSM

GSA 7

P-98-0615 LS from SM4 to SMG1 Comments on UMTS 22.00 v 1.0.0

SMG4

P-98-0616 SMG3 Status Report to SMG#27 on UMTS issues SMG3 Chairman 7.3 P-98-0617 Benefits of AMR Codec Optimisation Phase NEC Technologies

(UK) Ltd. 7.11

P-98-0618 Global Mobile Suppliers Association Presentation (Slides)

GSA President 4

P-98-0619 Minutes of the ad-hoc session on MoU VFS (Voluntary funding Scheme) (Wednesday 14 Oct. 98 14:00-14:20)

H. Dettner (Secretary)

For Info

P-98-0620 Meeting report of SMG-CG #27bis, Praha, 12th October, 1998

SMG-CG For Info

P-98-0621 Statements regarding IPR made by Dr. Foerster, October 14, 1998 to be included in meeting minutes

Ronald Foerster 7.7

P-98-0622 Ericsson statement to ITU Ericsson 7.7 P-98-0623 Press article: Senate resolution on 3G significantly

watered down RCR + GW Wireless News

5.7

P-98-0624 Position paper on the UICC for early UMTS systems

SMG 7.9

P-98-0625 Handling of AT Commands via SIM Toolkit BT, Vodafone, France Telecom, Nokia, Ericsson, Siemens, Motorola

6.4

P-98-0626 Applications and Automatic Execution BT, Vodafone, Nokia, Ericsson, Motorola, Siemens

6.4

P-98-0627 Rejection of CR 03.78 A037r1 by SMG#27 - Removal of O_Not_reachable and T_Not_Reachable Detection Points

SMG3 chairman 6.3

P-98-0628 Completion of AMR codec One 2 One 6.11 P-98-0629 Liaison to SMG on UMTS Parameter assumptions

and spectrum utilisation ERC TG1 7.2

P-98-0630 Liaison statement to ERC TG1: UMTS assumptions for FDD and TDD

SMG2 7.2

P-98-0631 Selection of the AMR codec BT, Cellnet, CSELT, E-Plus, Ericsson, Europolitan, Finnet Group, GSM North America, Italtel, KPN Telecom, Mannesmann Mobilfunk, Marconi, Motorola, Nokia, NTT DoCoMo, Omnitel Pronto Italia, One2One, Philips Consumer Communication, Siemens, SmarTone, Swisscom Ltd., Telenor mobil, Telia, Telital, TIM, Vodafone

6.11

P-98-0632 Request for Funding for the characterisation of the AMR Codec

SMG 6.11

Number


Replaced by Tdoc

P-98-0633 The Current Documentation Status of IMT-2000 Specification in ARIB/TTC

ARIB/TTC 7.

P-98-0634 Not allocated P-98-0635 Fax from A Scrase to SMG Chairman on ETSI

Board #15 ETSI 5.7

P-98-0636 Nokia supports UMTS proposals for IPR policy on 3rd generation technologies

Nokia 7.7

P-98-0637 ITU-R Task Group 8/1 Preparations ETSI SMG ITU-R TG8/1 Co-ordinator

7.2

P-98-0638 CR A159r1 to GSM 09.02, version 5.9.0 SMG3 & T1P1 6.3 P-98-0639 CR A043r3 to GSM 05.02 v.6.2.0 SMG2 Chairman 6.2 P-98-0640 LS to GSM MoU EIG and SMG7 - Common

position on Article 3 "Essential Requirements" of the draft R&TTE Directive

SMG#27

P-98-0641 Summary of harmonization Activities between W-CDMA and cdma2000

ARIB 7

P-98-0642 LS to SMG2 on Testability of AMR in the BSS SMG#27 6.11 P-98-0643 - P-98-0661

Not allocated

P-98-0662 Agreed CRs from SMG2 (Marseille) to SMG#27 on TEI

SMG2 WPA 6.2

P-98-0663 Agreed CRs from SMG2 (Marseille) to SMG#27 on GPRS

SMG2 WPA 6.2

P-98-0664 SMG6 status report SMG6 6.6 P-98-0665 Non-strategic CRs to GSM 12.11 (R97) "Fault

management of the BSS" SMG6 6.6

P-98-0666 Strategic and non-strategic CRs to GSM 12.15 (R97 & R98) "GPRS charging"

SMG6 6.6

P-98-0667 Non-strategic CRs to GSM 12.05 "Call and event records"

SMG6 6.6

P-98-0668 SMG9 status report + LSs from SMG9 to SMG SMG9 6.9 P-98-0669 Strategic CRs to GSM 11.14 (1bis and AT

commands) (R96, R97 and R98) "SIM application toolkit"

SMG9 6.9

P-98-0670 Non strategic CRs to GSM 11.14 (R96, R97 and R98) "SIM application toolkit"

SMG9 6.9

P-98-0671 Non strategic CR to GSM 11.11 (R98) "SIM/ME interface specification"

SMG9 6.9

P-98-0672 Non stratagic CRs to GSM 02.17 "Functional characteristics of the SIM"

SMG9 6.9

P-98-0673 Non strategic CR to EG 201 220 "ETSI numbering system for telecommunication application providers (AID)"

SMG9 6.9

P-98-0674 GSM 02.19 v2.0.0 (SIM Application Programming Interface - Service description - Stage 1)

SMG9 6.9

P-98-0675 Withdrawn P-98-0676 Status Report SMG9 (Slides) SMG9 6.9 P-98-0677 CRs to 04.07, 04.08, 04.64, 04.65 and 09.18 on

GPRS SMG3 6.3

P-98-0678 CRs to 04.69 on VBS SMG3 6.3 P-98-0679 CRs to 04.68 on VGCS SMG3 6.3 P-98-0680 GSM 02.56v2.0.0 GSM Cordless Telephony

System (CTS), Phase 1; Service description; Stage 1

SMG1 6.1

Number


Replaced by Tdoc

P-98-0681 UMTS Phase 1 W I SMG1’S Primary Responsibility WI

SMG1 7.1

P-98-0682 Non strategic CR on Multiple User Profiles - UMTS 22.01 Service Aspects; Service Principles

SMG1 7.1

P-98-0683 Documents on co-operation with Universal Wireless Communications Consortium's Global TDMA Forum (GTF)

PT SMG 4

P-98-0684 - P-98-0694

Not allocated

P-98-0695 Phase 2+ (R96) CRs to 11.10-1 (Signalling) for Approval

SMG7 6.7

P-98-0696 Phase 2 CRs to 11.10-1 (RF) for Approval SMG7 6.7 P-98-0697 Phase 2+ (R96) CRs to 11.10-1 (RF) for Approval SMG7 6.7 P-98-0698 CRs to 04.08 on TEI SMG3 6.3 P-98-0699 Withdrawn P-98-0700 Status Report of SMG11 at SMG#27 SMG11 6.11 P-98-0701 Project schedule and open issues for AMR; (GSM

10.70, Version 0.0.1) SMG11 6.11

P-98-0702 Withdrawn P-98-0562 P-98-0703 GSM 04.53 v.1.6.0 Inband Tandem Free

Operation (TFO) of Speech Codecs - Service description - Stage 3

SMG11 6.11

P-98-0704 Non strategic CRs to GSM 03.50-A014/A015 SMG11 6.11 P-98-0705 Proposed LS to ARIB IMT-2000 Codec Work

Group on "Collaboration on the evaluation of AMR for UMTS"

SMG11, Cc SMG, SMG2

7.11

P-98-0706 Status Report of ETSI STC SMG2 to SMG#27 SMG2 6.2 P-98-0707 GSM 10.59 v.1.3.0 (for information) - Project

scheduling and open issues for EDGE SMG2 EDGE 6.2

P-98-0708 Withdrawn - Duplication of 98-0663 P-98-0663 P-98-0709 CRs to GSM 05.02 SMG2 6.2 P-98-0710 CRs to GSM 05.05 SMG2 6.2 P-98-0711 CRs to GSM 05.08 SMG2 6.2 P-98-0712 CR to GSM 05.10 SMG2 6.2 P-98-0713 LS to SMG on "Proposed feasibility study for GSM

450" SMG2 6.2

P-98-0714 SMG2 Self-Evaluation report on UTRA to ITU (for information)

SMG2 Secretary 7.2

P-98-0715 CR A355 to 04.08 v.4.22.0 Phase 2 on TEI SMG3 6.3 P-98-0716 CR A365 to 04.08 v.6.1.1 on CCBS SMG3 6.3 P-98-0717 Status Report of SMG3 to SMG#27 SMG3 6.3 &

7.3

P-98-0718 GSM 04.72 Call Deflection (CD) stage 3 v.1.0.0 SMG3 6.3 P-98-0719 GSM 09.13 : Signalling interworking between

ISDN supplementary services Application Service Element (AE) and Mobile Application Part (MAP) protocols v.2.0.0

SMG3 6.3

P-98-0720 Strategic CRs to GSM 03.93 CCBS stage 2 (CCBS-Release 97) (CRs GSM 03.93-A005r1, -A006r1, -A007r1, -A008r1)

SMG3 6.3

P-98-0721 Strategic CR to GSM 03.18 and GSM 09.02 related to CCBS (Release 97)

SMG3 6.3

P-98-0722 Strategic CR A022r1 on 03.18 v.6.0.0 CA2/CCBS SMG3 6.3

Number


Replaced by Tdoc

P-98-0723 Strategic CRs to GSM 03.32, GSM 03.78 and GSM 09.02 related to CAMEL Phase 1 (Release 96)

SMG3 6.3

P-98-0724 Strategic CRs to GSM 03.32, GSM 03.78 and GSM 09.02 related to CAMEL Phase 2 (Release 97)

SMG3 6.3

P-98-0725 Agreed CRs to 03.08, 03.18, 09.02 and 09.60 on GPRS

SMG3 6.3

P-98-0726 Strategic CRs to GSM 03.18 and GSM 09.02 on Technical Enhancements/Improvements (TEI)

SMG3 6.3

P-98-0727 Standardisation of Commercial Location Based Services

Cellnet, Motorola, Nokia, Nortel, Omnitel Pronto Italia

6.5

P-98-0728 Background Information about Location Services Standardization

Nokia 6.5

P-98-0729 IMT.KEY Contribution to ITU-R TG 8/1 - For Information

Nokia and UK 7.2

P-98-0730 Withdrawn P-98-0731 Presentation to SMG#27 of AMR Selection Phase

results SMG11 6.11

P-98-0732 Report on Essential IPRs declared in relation to the work of SMG#27

ETSI Legal Advisor 7.7 P-98-0786

P-98-0733 ETSI Status List I. Doig ETSI SMS 5.4 P-98-0734 Status Report of SMG12 SMG12 Chairman 6.12 &

7.12

P-98-0735 CRs to 07.07, 07.60 and 09.61 on GPRS SMG4 6.4 P-98-0736 HSCSD and 14.4 kbit/s CRs SMG4 6.4 P-98-0737 MS-TE CRs SMG4 6.4 P-98-0738 SMS CRs SMG4 6.4 P-98-0739 Strategic V.24 CRs SMG4 6.4 P-98-0740 11.24 CRs SMG8 6.8 P-98-0741 Non strategic CRs on 11.21 for introduction of

Pico-BTS requirements (for information) SMG8 6.8

P-98-0742 Non strategic CRs on 11.21 SMG8 6.8 P-98-0743 SMG8 Status Report SMG8 Chairman 6.8 P-98-0744 1st List of CRs and new Specifications submitted

to SMG#27 PT SMG 6.13

P-98-0745 UMTS Standardization: Achievements and Plans Chairman ETSI SMG For Info P-98-0746 PT SMG status report PT SMG 5.4 P-98-0747 GSM and UMTS specifications before SMG#27 PT SMG 5.4 P-98-0748 ToR for Specialist Task Forces on Harmonised

Standards for GSM Phase 2 and Phase 2+ PT SMG 5.4

P-98-0749 ToR for a new STF "GW" on UIC/GSM-R PT SMG 5.4 P-98-0750 DRAFT MANDATE TO CEN/CENELEC/ETSI

FOR STANDARDIZATION in the field of RAILWAY EQUIPMENT on the INTEROPERABILITY OF THE TRANS-EUROPEAN HIGH-SPEED RAIL SYSTEM

PT SMG 5.4

P-98-0751 Draft Minutes UIC/CENELEC/ETSI co-ordination Meeting Sophia Antipolis, 3 July 1998

ETSI Secretariat (A. Berrini)

5.4

P-98-0752 Agreed non strategic CRs to 03.60 on GPRS SMG12 6.12 P-98-0753 Agreed strategic CRs to 03.60 on GPRS SMG12 6.12 P-98-0754 UMTS 23.01 v.1.0.0 SMG12 7.12 P-98-0755 UMTS 23.10 v.1.0.0 SMG12 7.12 P-98-0756 GSM 03.73 v.1.0.0 SoLSA Stage 2 SMG12 6.12

Number


Replaced by Tdoc

P-98-0757 GSM 03.56 CTS stage 2 SMG12 6.12 P-98-0758 UMTS 23.20 v.1.0.0 for information SMG12 7.12 P-98-0759 WI on a UMTS Core based on ATM Transport SMG12 7.12 P-98-0760 WI: Combined GSM and Mobile IP Mobility

Handling in UMTS IP CN SMG12 7.12

P-98-0761 WI: UMTS Open Service Architecture SMG12 7.12 P-98-0762 Call for Experts for STF12 (GSM), 83 (UMTS) and

for STF EU (Study and investigation of the introduction of number portability in the GSM family) - CL 1899

ETSI 7.4

P-98-0763 LS from TC SES - A status report for the GMR working group

SES 5.1

P-98-0764 PT SMG Job Description - Version 3.20 PT SMG 5.4 P-98-0765 The use of UTRA in TDD mode in the unpaired

frequency bands BT 7.2

P-98-0766 The way forward for creating the 3GPP and its scope

BT 5.7

P-98-0767 Organisation of work on GSM and UMTS following the ETSI Extraordinary GA

BT 5.7

P-98-0768 CRs to GSM 03.18 and GSM 03.79 on SOR SMG3 6.3 P-98-0769 Vote 4- Results from the 1st Extraordinary

General Assembly Meeting (ETSI/GA-EX01(98)TDoc14)

Ian Doig (SMG Technical Officer)

5.7

P-98-0770 Draft Summary minutes, decisions and actions from the 1st Extraordinary General Assembly Meeting (ETSI/GA-EX01(98)11)

Ian Doig (SMG Technical Officer)

5.7

P-98-0771 3rd. Generation Interest Group Report MoU Association - 3GIG

7.7

P-98-0772 UMTS Phase 1: Support of SMS Cell Broadcast Service

Mannesmann Mobilfunk

7.1

P-98-0773 MoU for Voluntary Funding - Key Issues Mannesmann Mobilfunk

5.5

P-98-0774 UMTS Phase 1 Issues from MoU SERG MoU GSM Representative in SMG

7.7

P-98-0775 SMG4 Status Report SMG4 Chairman 6.4 P-98-0776 GSM 03.57 Version 1.0.2 - Mobile Station

Application Execution Environment (MExE); Functional description; Stage 2

SMG4 6.4

P-98-0777 Guidelines for a CEPT position on the ITU-R TG 8/1 process for defining IMT-2000 recommendations and IMT.RKey Contribution to ITU-R TG8/1

NATIONAL POST & TELECOM AGENCY

7.2

P-98-0778 Report on activities between June 1998 and September 1998

STF Voluntary Funding Task Force Chairman

5.5

P-98-0779 On the Implementation of a Global 3rd Generation Terminal

Nokia and Motorola

P-98-0780 WI: IP-in-IP tunneling in GPRS backbone for UMTS phase 1

SMG12 7.12

P-98-0781 Proposed WI on ETE UMTS QoS Management SMG12 7.12 P-98-0782 CR A001 to UMTS 30.01 v.3.3.0 PT SMG 7.12 P-98-0790 P-98-0783 Report of SMG Side-Meeting on Document

Structure Meeting Chairman, A. Cox

P-98-0784 Annex 1 to TDoc 734/98 - SMG12 Work Split between chairmen (Tdoc SMG-CG#27 Tdoc19)

SMG12 Chairman 6.12

Number


Replaced by Tdoc

P-98-0785 Annex 5 to Report on activities between June 1998 and September 1998

STF Voluntary Funding Task Force Chairman

5.5

P-98-0786 Report on Essential IPRs declared in relation to the work of SMG#27 (Revision of TDoc 732/98)

ETSI Legal Adviser 7.7

P-98-0787 Action points and postponed items SMG P-98-0788 Withdrawn P-98-0789 LS to GSM MoU EIG and SMG7 Common position

on Article 3 "Essential Requirements" of the draft R&TTE Directive

SMG#27

P-98-0790 CR A001 to UMTS 30.01 v.3.3.0 (Revision of Tdoc 98-0782)

PT SMG 7.12

P-98-0791 STANDARDISING EMBEDDED APPLICATIONS IN UMTS

SMG P-98-0793

P-98-0792 R-GSM TBR Module - EN 301 419-7 R-GSM Harmonised standard for information (Revision of Tdoc 98-0542)

SMG7 6.7

P-98-0793 STANDARDISING EMBEDDED APPLICATIONS IN UMTS

SMG

ETSI SMG#27 Annexes to Tdoc SMG 0531/98 Praha, 12 to 16 October 1998Agenda Item: 6.10 and 7.10

Source: SMG10 (Technical manager for security aspects)Date: October 1998

Annexes A, B, C and D to the Status report of SMG10 to SMG#27

Annex A: Proposed LS to MoU-SG on ASCI fraud issues (to SMG#27 for advice)

SMG10 meeting #3/98 Tdoc SMG10 98P211 Sophia Antipolis, 28 to 31 July 1998

From: SMG10To: MoU-SG

Liaison statement to MoU -SG on ASCI –fraud issues

SMG10 has reviewed the enclosed document on ASCI and draws attention to the security issues.

SMG10 believes that MoU-SG should issue guidance to Operators on this topic.

Enclosed Tdoc SMG10 98P181 for information to help draw up the guidance.

Page 2Status report of SMG10 to SMG#27: October 1998

Attachment to Tdoc SMG10 98P211: Annex A

SMG10 #3/98 Tdoc SMG10 98P181Sophia Antipolis, 28-31 July, 1998 Source : Vodafone

Fraud Review of Advanced Speech Call Items (ASCI)

Introduction

This document is a fraud review of the ASCI services, enhanced multi-level precedence and pre-emption(eMLPP), voice group call (VGCS) and the voice broadcast services (VBS). It has been written to fulfil anaction taken by Vodafone at the SMG10 plenary at Lund, April 1998.

SMG10 looked at the ASCI items at the Torino meeting (October 1997) but due to confusion, the resultingliaison statement was not delivered to SMG and subsequent discussion did not take place.

The ASCI project was developed under the instigation of the Union Internationale des Chemins de Fer(UIC), for convenient and quick “PMR-type” communication between railway operatives. However, as ithas been standardised, it can be used in any scenario, and will be reviewed with this in mind.

Service Descriptions

Enhanced Multi-Level Precedence and Pre-emption (eMLPP) service

The eMLPP service [GSM 02.67] is an enhancement for GSM networks of the ISDN MLPP service tomeet the UIC requirements.

The eMLPP service specifies how to handle precedence levels for subscribers within a PLMN includingthe possibility of pre-emption of ongoing calls. eMLPP defines set-up classes which specify the set-uptime and the pre-emption capability. eMLPP is applicable to tele- and bearer services.

eMLPP service consists of two parts: precedence and pre-emption.

- Precedence involves assigning a priority level to a call in combination with fast call set-up.- Pre-emption involves the seizing of resources that are in use by a call of a lower precedence by

higher-level precedence call. This can also involve the disconnection of an on-going call of lowerprecedence to accept an incoming call of higher precedence.

eMLPP provides different levels of precedence for call set-up and for call continuity in case of handover.There are at maximum seven priority levels.

Table 1: ASCI – Priority levels

A (highest) for network internal use

B for network internal use 0 for subscription 1 for subscription 2 for subscription 3 for subscription 4 (lowest) for subscription

The two highest levels A and B are reserved for network internal use, e.g. for emergency calls or networkrelated service configurations like voice group call services. They can only be used locally, i.e., within thedomain of a MSC. The other five levels (0-4) are offered for subscription and can be applied globally ifsupported by all related network elements.


Usually, the priority depends on the calling subscriber who can select the priority level at set-up. If thesubscriber has no eMLPP subscription (or no MLPP subscription in case of a call from the fixed network)a default priority level is given.

The call set-up time is defined as the time from pressing the send-button to the point at which the calledparty, or at least one called party in the case of a multi-party call, can receive information. There are threeclasses of set-up time performances and examples of the call set-up times are:

- class 1 fast set-up 1–2s;

- class 2 normal set-up <5s;

- class 3 slow set-up <10s

The network decides the call set up class to assign to a call when the call setup (with eMLPP indicated)message is received from the MS.

For precedence calls, the network shall have the possibility to pre-empt ongoing calls with lower priority, inascending order of priority. Pre-emption is possible at call set-up or at handover.

Table 2: ASCI – Example on eMLPP service composition

Priority level Set-up time Pre-emption

Examples

A class 1 yes VBS/VGCS emergencyapplication

B class 2 yes Operators calls 0 class 2 yes TS 12 Emergency calls 1 class 3 Yes Premium rate calls 2 class 3 No Standard rate calls 3 class 3 No Default for no eMLPP

subscription 4 class 3 No Low tariff calls

Security Options

There is the option for the network to postpone or not perform authentication at call set up (andciphering) for a call with a high priority requiring a class 1 set-up. This applies to both MO and MT calls.The network can announce that such calls are possible (i.e. that an eMLPP MS may send a SETUPmessage before an AUTH_REQ message) using the BCCH.

Authentication is still performed at location update however, so if fast call set up is to be used, thesubscriber must be already registered in the network.

Voice Group Call Service (VGCS, [GSM 02.68])

Definitions (also apply to VBS)

A GSM subscriber who has subscribed to VGCS or VBS is a service subscriber .

A group of service subscribers who wish to communicate with each other using VGCS or VBS will beassigned a group ID for that group.

The calling subscriber may be any service subscriber which has subscribed to the related group ID andis entitled to establish a call/broadcast by the terms of his subscription or any dispatcher who is entitled tobe calling subscriber and is registered in the network.

Particular fixed line or mobile users are identified as dispatchers .

Destination subscribers are all service subscribers which belong to a group identified by the group IDwhich have their present location in the service area and pre-registered dispatchers.


Principle : The VGCS [GSM 02.68] allows speech conversation of a predefined group within a predefinedarea (the Group Call Area). The initiator of a group call may be a service subscriber or a user of a fixednetwork. The speaker may change during the ongoing call.

Establishment of a voice group call

The group call shall be established in a service area that is comprised of one or a cluster of cells. Serviceareas shall be predefined at registration. In case of a service subscriber initiating a VGCS, the servicearea is uniquely identified by the actual cell in which the service subscriber resides at the moment ofVGCS call initialisation and by the group ID they issue. A dispatcher initiating a VGCS call will beconnected to a related predefined service area.

Ongoing call

The service shall permit only one talking service subscriber at any moment; additionally up to fivedispatchers can be talking simultaneously at one time. Dispatchers should hear all combinations of voicesother than their own. Listening service subscribers shall hear the combination of all voices. The talkingservice subscriber shall gain some audible indication if any dispatchers are talking simultaneously.

Security Options

As a network option the mobile station of the talking service subscriber can be requested to send its IMSIto the network in order so that the talker’s IMSI be stored in the event records.

- Authentication of calling subscribers at VGCS invocation is optional. (The omission ofauthentication applies to call set up only. The subscriber must be perform authentication as normal forlocation update)

- Authentication of the talking service subscriber is optional.

- Confidentiality on the radio path for the talker is optional.

Voice Broadcast Service (VBS, [GSM 02.69]

VBS [GSM 02.69] specifies the capability to set-up a point to multi-point connection for the uni-directionaldistribution of speech. The call is initiated by a subscriber or a fixed destination (dispatcher) into apredefined geographical area (service area) to a predefined group of subscribers located in this area (andadditionally up to eight (including the initiator) fixed destinations).

Destination subscribers must be within the service area to initiate or receive the broadcast.

Dispatchers in VBS receive all voice broadcasts to groups of which they are a part. In addition, they caninitiate broadcasts to groups of which they are a part.

The broadcast call shall be established in a service area that is comprised of one or a cluster of cells.Service areas shall be predefined at registration.

Establishment of a voice broadcast call

In case of a service subscriber initiating a VBS call, the broadcast area is uniquely identified by the actualcell in which the service subscriber resides at the moment of VBS call initialisation and by thecalled group ID. A dispatcher initiating a VBS call will be connected to a related predefined broadcastarea. Since a dispatcher may be registered to more than one broadcast area and group ID an indication ofthe wanted broadcast area and group ID has to be given in form of a dedicated address called by thedispatcher.


Release of a Broadcast call

Service subscribers who leave the broadcast area during an on going VBS call cease to be destinationsubscribers. Service subscribers which enter the broadcast area during an on going VBS call shallbecome destination subscribers within 500ms after reception of the first paging message related to theVBS call.

The calling subscriber shall remain within the broadcast call until he terminates the call, loses contact withthe network or leaves the broadcast area.

Optional requirements

- Authentication of calling subscribers at VGCS invocation is optional. (The omission ofauthentication applies to call set up only. The subscriber must be perform authentication as normal forlocation update)

- Authentication of the destination subscribers is not required.

- Confidentiality on the radio path is optional.

Fraud Potential

eMLPP

The risks with eMLPP stem from the possibility of non-authentication (“fast call setup”) for high prioritycalls. There is the possibility of intruders masquerading as other MS.

The fast call setup option (authentication postponed or not performed at all) is only open to eMLPPsubscribers, and presumably only those with a high priority. An intruder would therefore require the identityof the MS with such a priority in order to perform the masquerade.

This identity could be obtained through insider fraud, or, if the eMLPP transmits its IMSI to the network orreceives a new TMSI from the network, in the clear. to obtain the IMSI by eavesdropping, the intruder,would have to know that the target MS had eMLPP. In such a case, the intruder would have to shadow thetarget user and hope that the identity could be revealed and scanned. Insider fraud seems more likely.

Authentication can only be omitted at call setup, it is still required for location update and registration.Therefore the intruder can only masquerade a subscriber who is already registered in the network andnot requiring location update. The presence of the intruder may be revealed when the genuine subscriberattempts to make a call while the intruder already has a call in progress or where both the intruder andgenuine subscriber respond to a paging message.

The “fast call setup” option should only be used in emergency situations. There should therefore be thepossibility of procedures at the network where all records of calls with fast call setup and checkedregularly with the user. Also, the calls would only be to specific destinations, and this could be used foronline or offline checking.

Therefore, the monetary gain from being able to masquerade as a MS with high priority seems low,assuming that the use of fast call setup is sparse and carefully monitored. However, there may be a moreserious use, that of masquerade as the operative with fast call setup, with intent to mis-inform. This couldonly be done if the genuine user’s voice was not known to the listeners but is a possibility and a seriousconsideration, especially where details of emergency situations are being communicated. Users of eMLPPshould be aware of the possibility of masquerade.

Unlike VBS and VGCS, non-authentication with eMLPP can occur anywhere, not just within a specifiedservice area.

The risks can be made all but negligible, and fast call setup retained, if instead of not performingauthentication, the network merely postpones it until after the call is setup.


VBS and VGCS

If the group chooses not to use confidentiality then the group members run the risk of eavesdropping onthe air interface. However, as long as the group members are informed of the lack of confidentiality, theycan take responsibility for the risk of eavesdropping and it need not be a cause of concern.

The option for the calling subscribers and other participating group members to be un-authenticated is ofmore concern.

The identities of all members of a group must be registered with the network before operation of the groupcan begin. There is therefore no possibility of new identities being allowed into a group call or broadcastduring a call.

However, there is the possibility of intruders masquerading as members of the group if authentication isnot used. This would allow the intruder to set up or receive voice broadcasts and group calls. As foreMLPP, authentication at location update is still performed, so the intruder can only masquerade assubscribers who are already registered in the network. The genuine subscriber may recognise thepresence of the intruder by degradation in service, as illustrated for eMLPP.

Group members should be informed that in forming a group where authentication is optional, they run therisk of intruders masquerading as members of the group. However, charging liability questions aside1, thegroup members are the only parties affected by the risk and it need not, therefore, be of cause to thenetwork operator who has good procedures in place. It can reasonably be assumed, that for a group call,or group broadcast, there would be at least one listener who would be able to recognise, by voice, if anintruder were masquerading as the caller.

As VGCS and VBS can only be used within defined areas to defined other parties, the motivation for anoutsider to attempt to initiate calls seems low. The opportunities for eavesdropping seem more of a lure,but only a collection of fools would use unciphered links for regular communication of sensitiveinformation.

Conclusions

With suitable internal security (for list of subscribers with high priority eMLPP) and procedures (highpriority eMLPP given only in exceptional cases, and regular usage checks), a network operator has aminimal risk of fraud. If the network postpones the authentication for fast call set-up, rather than notperforming it, there seems to be no risk2. The subscriber to eMLPP can be made responsible for anyfraud conducted in return for the privilege of fast call set-up. The subscriber should accept the risk ofeavesdropping on the unciphered link and the possibility of masquerade with intent to misinform.

VGCS and VBS can only be used within defined areas. The motivation for call originated fraud by anoutsider therefore seems low. Again, there is a risk of eavesdropping and masquerade, which subscribersshould be aware of and have accepted as a risk.

eMLPP, VGCS and VBS do not represent sources of technical fraud. With careful management,they do not represent a risk to network operators. Their users should be made aware of the smallrisks of eavesdropping and masquerade.

The task of making users aware of the risks, and of implementing good operator control of theservices, is the responsibility of operators offering the service. The sending of a liaison to MoU SGregarding the risks with the ASCI services is therefore recommended.

1 Realistically, in setting up a group where authentication is optional, group members must accept all call charges attributed to thegroup. The possibility of repudiation must not be given, as there is no way of establishing it.

2 Apart from that of “denial of service” if an intruder repeatedly sets up calls which are torn down by the network after authenticationfails. If this does occur the MSC could withdraw the right for all fast call set up, or, if this is required for other MS, simplycancel the user registration in the VLR. Re-registration would require location update, which would involve authentication.


References

[GSM 02.67] enhanced Multi-Level Precedence and Pre-emption service, (eMLPP), Stage 1,GSM 02.67 version 5.0.5

[GSM 02.68] Voice Group Call Service (VGCS), Stage 1, GSM 02.68 version 5.1.3[GSM 02.69] Voice Broadcast Service (VBS), Stage 1, GSM 02.69 version 5.1.1

Acknowledgements

This document incorporates descriptions of ASCI written by Volker Kessler (Siemens AG) as part of theACTS USECA project.


Annex B: LS to TMN5 & Network Management Forum Mobile Team onIntroduction of Roaming and Fraud Management to theTelOpsMap (to SMG#27 for information)


From: SMG10To: TMN5 and Network Management Forum Mobile Team

Liaison statement to TMN5 & Network Management Forum Mobile Team onIntroduction of Roaming and Fraud Management to the TelOpsMap

ETSI SMG10 welcomed having visibility of this document and would draw your attention to the fact thatthe functionality required is contained within the Fraud Information Gathering System (FIGS). This systemis defined in GSM specifications:

GSM 01.31 Service requirements –Stage 0;GSM 02.31 Service description - Stage 1;

and

GSM 03.31 Technical Realisation.

It is further expected that FIGS will form the basis of the standards in the fraud area for UMTS.

SMG10 are happy to offer assistance in the area of fraud should it be required.


Annex C: LS to ETSI SAGE on CTS (to SMG#27 for information)


From: SMG10To: ETSI SAGE

Liaison statement to ETSI SAGE on CTS

SMG10 (CTS ad-hoc) is considering ways of securing the operation of CTS fixed parts (FPs) bytransmitting tokens cryptographically signed by the controlling operator. SMG10 would appreciateassistance from SAGE with regard to the detail of these mechanisms. Answers to the following questionsare sought:

1. It is believed that there are difficulties with regard to the export of systems using RSA, even where RSAis only used for digital signatures. Do these difficulties actually exists, and if so, what are they andwhere/when do they occur?

2. The use of elliptic curve technology has been proposed. Some members of SMG10 have expressedconcern over the use of elliptic curve technology, believing it to be relatively young and untried. SAGEare asked for their opinion on the safety of using elliptic curve techniques.

3. One proposal for the transmission of tokens signed by the operator requires the operator to transmit apublic key to the FP that has been certified by 3 certification authorities. If elliptic curve technology isnot used, this trebly signed operator public key could have a considerable length.

One option considered was that the operator public key (plus parameters) could be successivelyencrypted by the CA secret keys with minimal increase in the length of the original public key, beyondthat required for the encryption. The resulting string would have to be decrypted by the FP using theCA public keys in the correct order. SAGE are asked to advise on the security and feasibility of thismethod, and what the minimal increase in length would be.

4. SAGE are asked to comment on the proposed key lengths for various public key schemes consideredin the table below. As the only advantage to be gained from forging the token signing process isavoidance of the subscription charges for CTS (these will be less than the charges for a cellularsubscription) it is expected that the attackers will be individuals and hacking groups. It should be notedthat the scheme allows for the ability to replace keys on a regular frequency, so as to defeat long termexhaustive search attacks.

Scheme System SK PK Signature

RSA-based N/A 2048 1088 1024

DSA 2208 160 1024 320

EC-based 481 160 161 160

ECDSA 481 160 161 320

5. SAGE are asked to inform SMG10 of any patents and export difficulties with the above techniques thatthey know of.


Annex D: LS to SMG#27 on SS7 network security


From: SMG10To: SMG#27

Liaison statement to SMG#27 on SS7 network security

Summary

There is no adequate security in SS7. Mobile operators' needs to protect themselves from attack byhackers and inadvertent action that could stop a network or networks operating correctly. Securityencapsulation of the MAP related messages to prove the origin of them and verified against trustednetwork entities.

Therefore SMG10 proposes the work should be started for this, and would welcome support from othergroups working on SS7.

Background

SMG10 has for some time been concerned about the security of the global SS7 network as a transportsystem for non channel associated signalling, for example authentication messages and supplementaryservices such as call forwarding. The problem with the current SS7 system is that messages can bealtered and injected into the global SS7 networks in an un-controlled manner.

In the past SS7 traffic was passed between major PTOs and covered under treaty organisation. Thenumber of operators was relatively small and the risk of compromise was low. With the increase indifferent types of operators the increase in the number of interconnection circuits there is an ever-growingloss of control of security of the signalling networks.

There is also a growing increase in the use and interconnection between the telecommunication networksand the Internet .The IT community now has many protocol converters for conversion of SS7 data to IPprimarily for the transportation of voice and data over the IP networks. In addition new services such asthose based on IN will lead to a growing use of the SS7 network for general data transfers.

There have been a number of inadvertent network incidents from accidental action that have takendamaged a network. To date there have been very few deliberate actions. The availability of cheap PCbased equipment that can be used to access networks.

And the ready availability of access gateways on the Internet will lead to actions against mobile operators.

The problem of risk of attack has been recognised in the USA (Tdoc SMG10 98P201), this containsexceptions from a document of the Presidents office indicating concern on SS7. It is understood that T1 islooking at the issue.

Example of SS7 related messages that could cause damage to network are enclosed in annex 1.


The table below shows the split in the problems caused for either the network it’s self or it’s subscribers.The key issues are manipulation of the customers related activities carried in the signalling. In the case ofthe network the key issue in the external control of the HLR’s ability to be used.

Network attack Subscriber attack

Element Effect

HLR/AuC Overload Signallingnetwork, or HLR

HLR data Call forwarding

Status (attached,detached)

Service profile

Location

GMSC Removal of servicewhilst switch recovers,Signalling overload inVLR or HLR

MSC

SMC, VPS, IN nodes Dependant onnetwork

Remove subscription

Intercept MT – call divert

Call selling

Protect network Filter (policing of messages)

Prove origin of messages

Verify source of message

Mechanism for protection of deletion , insertion,modification

Confidentiality of messages

SMG10 is very concerned that no activity is taking place in SMG or ETSI as a whole to protect the integrityof the SS7 network which is the communication lifeline for all services offered in a network. SMG 10therefore strongly recommend that this is an urgent work item for SMG for all respective working groups, Ifthe GSM standards are not seen as very from attack.


Annex 1 to Tdoc SMG10 98P235 - SS7 Problem Messages

MESSAGE SS7 LAYER ISSUE

TFP Transfer Prohibited MTP Prevents signalling to a nominated node fromany node connect to an STP

TRF Transfer Restricted MTP Cause re-routing of messages to a specifiednode from any node connect to an STD

TFC Transfer Control MTP Allows message only of certain priority to anominated node.

LIN Link Inhibit MTP Inhibits signalling on a nominated signalling link

SSP Subsystem Prohibited SCCP Prevent signalling to a nominated subsystem ornominated link from any node connected to anSTP

Update Location MAP Put subscriber on wrong MSC – (False MSC)

Insert Subscriber Data MAP Insert null data – remove service

Cancel Location MAP Remove location info about subscriber

Delete subscriber data MAP Delete subscriber

Reset MAP Indicates an HLR reset. Leads to messagecongestion to HLR

Send routing info. MAP Determines where subscriber is attached orforwarded. Could be used to obtain location ofsub or over load HLR with SRI requests.

Update Location Area

Update Location

Cancel Location

MAP Delete. Location area or update to an alternativelocation.

Detach IMSI MAP Remove subscriber

Insert Subscriber Data

Delete Subscriber Data

Send Parameters

MAP Manipulate authentication process

EraseSS MAP Effect service

DeactivateSS MAP Effect service

Reset MAP Overload of signalling channel

Authenticate MAP Effect authentication activity

ETSI EP SMG Tdoc SMG 602/98Prague, October 12th – 16th, 1998

Source: SMG

To: MoU

Subject: Proposed liaison to MoU on Allocation of Sub-System Number

ITU-T has rejected the allocation of specific GSM code point in the international rangefor nodes only used in GSM networks (e.g. SGSN). This is used for routing MAPmessages to the different elements inside a GSM network and in between network via theInternational signalling network.

Consequently, SMG is currently reviewing the allocation of code points in the nationalrange. The roaming situation requires some co-ordination in the allocation.

Some discussion took place inside ETSI where SPS1 is currently co-ordinating thisallocation for Europe. Some co-ordination will be handled inside ETSI by SMG.

The situation in GSM networks is more difficult due to the fact that operators outsideEurope are also using this kind of code points.

SMG request whether MoU could handle the maintenance of these code point in acentralised manner to ensure this consistent allocation throughout the world and keepSMG12 inform of any new allocation for the future.

As soon as approved by SMG the CR on 03.03 will be provided to MoU as first input forthe document to be handled by MoU.

For additional information a draft version of CR to 03.03 that is provided as an annex forinformation. Please be aware that this CR is not yet in its final version and is providedjust for information.

Attachment: Draft CR to 03.03.

ETSI TC SMG#27Praha, CZ12-16. Oct 1998

SSN allocation for GPRS, CAMEL etcSMG3 endorsed CRs.

Source : SMG3 ChairmanThis attachment contains 3 CRs on the allocation of SCCP Subsystem Numbers (SSNs) out of the range ofcodepoints reserved for use by national networks.These change requests are endorsed by SMG3, especially the assignment of the codepoints as specified insection(s) 8.2.

Remark1: Some discussion still is ongoing on the text in the general section 8 which preventedthe CRs from being completely endorsed/approved by SMG3 on the recent plenarymeeting.

Remark2: Several CRs are proposed to have a clean separation between the SMG work itemsfor GPRS and CAMEL.

CHANGE REQUEST No. A____r2 Technical Specification GSM 03.03 version 5.1.0Submitted to SMG for approval without presentation ("non-strategic") [ ]

with presentation ("strategic") [ ] Status at SMG [ ]: Approved [ ] Rejected [ ] Postponed [ ]Phase 1: [ ] Phase 2: [ ] Phase 2+: [ R’96] Work item: CAMEL Ph1Other phase(s) affected: [ ] If yes, linked CR(s):Proposed change affects: SIM [ ] ME [ ] Network [x]Source: Vodafone, [Siemens] Date: 10/9/98Subject: Definition of SSN for MAP signalling to the gsmSCFCategory: F - Correction [X]

A - Corresponds to a Phase 2 correction [ ]B - Addition of Feature [ ]C - Functional modification of Feature [ ]D - Editorial modification [ ]

Reason for change:An SSN needs to be allocated for inter-PLMN use, but ITU-T has refused to allocate SSNs from theglobally standardised rangeSections affected, and additional explanation of details of change (if needed):Sections 8, 8.2Attached revised pages: Page(s): 1If other core Specifications are affected, necessary (and attached) Joint CRs:Affects (possibly): MS Test Specifications [n] BSS Test Specifications [n] O&M Specifications [ ]Attached CRs?:

Cross Phase Compatibility:Change affects operation of: Phase 1 MS in Phase 2(+) NW [ ] Phase 2(+) MS in Phase 1 NW [ ]

CR to 09.90 attached:Change affects operation of: Phase 1 SIM in Phase 2(+) ME[ ]

CR to 09.91 attached:Phase 2(+) SIM in Phase 1 ME [ ]CR to 09.91 attached:

Other comments:

See also CR 03.03-A009 from SMG3 WP-C on SSN reservation (approved in Stuttgart July 98).

8 SCCP subsystem numbers

Subsystem numbers are used to identify applications within network entities which use SCCP signalling. InGSM, subsystem numbers may be used between PLMNs, in which case they are taken from the globallystandardised range (1 - 31) or that part of the national network range (129 – 150) reserved for GSM usebetween PLMNs, or within a PLMN, in which case they are taken from the part of the national networkrange (32 – 128 & 151 - 254) not reserved for GSM use between PLMNs.8.1 Globally standardised subsystem numbers used for GSM

The following globally standardised subsystem numbers have been allocated for use by GSM:0000 0101 CAP0000 0110 HLR (MAP);0000 0111 VLR (MAP);0000 1000 MSC (MAP);0000 1001 EIR (MAP);0000 1010 is allocated for evolution (possible Authentication centre).

8.2 National network subsystem numbers used for GSM

The following national network subsystem numbers have been allocated for use by within GSM networks:1111 1101 BSS O&M (A interface);1111 1110 BSSAP (A interface).

The following national network subsystem numbers hasve been allocated for use bywithin GSM networksand for use between GSM networks:1111 1010 1001 0100 gsmSCF (MAP)

ETSI/TC/SMG#27 Tdoc SMG 610/9812-16 October 1998, Praha

Source: ETSI/SMG

Subject: LIAISON STATEMENT TO TRAC - CTS FP SCOPE STATEMENT

The future work schedule for the GSM Phase 2+ feature CTS (Cordless TelephonySystem) was discussed at the SMG#27 meeting during 12-16 October 1998. At thismeeting two documents were approved detailing the future work schedule and theStage 1 Service Description. These are Tdoc SMG 586/98 and 680/98. Copies of thesedocuments are attached.

It is understood that TRAC had delayed the work on a Scope Statement for a CTR forthe CTS FP (Fixed Part) pending the resolution of this issue in SMG. As SMG hasagreed to continue the development of the CTS feature, and elaborated a workschedule, TRAC is invited to complete the scope statement for CTS FP.

TDocs 586/98 and 680/98 to be added

ETSI TC SMG Tdoc SMG 98-611Meeting #27Praha, 12-16 October 1998,

[Draft] Liaison Statement to TC ERM

Source: [SMG 8 Chairman] SMG

Title: System Description of UTRA

SMG wishes to draw the attention of ERM to a system description for UTRA1 which may be usefulfor ERM’s work. This was prepared for submission to ITU/R TG8/1 as an evaluation report for theUTRA Radio Transmission Technology (RTT) proposal for IMT 2000.

SMG made the selection of the concepts (technologies) to be used as the basis of UTRA (theUMTS Terrestrial Radio Access) at SMG #24 bis in January 1998. SMG 2 was then given theresponsibility for further refining the chosen concepts.

The workplan for the further refinement and definition of UTRA was driven by the deadlines set byITU/R TG 8/1 for the submission of Radio Transmission Technologies for IMT 2000. These were:� June 30th 1998 for the submission of proposed technologies (RTTs)

� September 30th 1998 for the submission of evaluation reports on the proposals.(the evaluation report contains an updated version of the June 30th submission).

SMG 2 submitted UTRA as a proposed technology for IMT 2000. Proposals based on similartechnologies were also submitted from USA (WCDMA/NA) and Japan (W-CDMA). A total of 15RTTs were submitted to ITU, of which 10 are intended for terrestrial use.

TC ERM is requested to exercise some caution in the use of the Evaluation Report:

1) SMG 2 is continuing to refine and complete the UTRA proposal, and therefore some changesmay be made (although SMG 2 believes that UTRA is now quite stable).

2) ITU TG 8/1 envisages a process of convergence between the proposed IMT 2000 RTTs, whichcould result in changes to UTRA.

3) The performance evaluation of UTRA is defined in GSM 30.03, which is based on themethodology defined by TG 8/1. This methodology was primarily intended to evaluate theproposed RTTs. Some of the performance figures in the evaluation report (especially relatingto spectrum efficiency) may not be directly applicable to other purposes.

The work on spectrum related parameters is more advanced for those aspects related to themodulation than for other areas (eg due to non-linearity in the transmitter and receiver). ERC TG1is performing studies on coexistence of terrestrial UMTS with other radio systems. SMG 2 hasreceived a liaison statement from ERC TG1 requesting information on UTRA; SMG 2 has replied tothis LS, but is not yet able to fully answer the questions asked by TG1.

The evaluation report for UTRA can be found on the ETSI server at:

http://docbox.etsi.org/tech-org/smg/document/smg2/SMG2UMTS-ITU/SRTT/EVAL_REPORTS

or: http://www.etsi.org/smg/UTRA/UTRA.htm

1 UTRA (UMTS Terrestrial Radio Access) is the radio interface for UTRAN (UMTS TerrestrialRadio Access Network)

ETSI SMG#27 Tdoc SMG 98-061512 - 16 October 1998Praha

ETSI STC SMG 4 UMTS SMG4 Tdoc 98p46928 Sept – 2 Oct 1998,Sophia Antipolis, France

Liaison Statement

From: SMG4To: SMG1Cc: SMG12

Subject: Comments on UMTS 22.00 v.1.0.0

SMG4 UMTS have reviewed this draft specification and would like to make the following observations.

Section 5 Teleservices/Data Applications.

Fax services

SMG4 UMTS feels that despite the growth of internet based document transfer, fax would still be animportant medium when UMTS services are rolled out and therefore should be properly supported inthe UMTS/GSM environment.

Serious concerns were raised that not standardising the store and forward protocol could result in manydifferent implementations leading to poor uptake of the service. Users need to have a consistent methodof fax transfer whether they are using GSM or UMTS access. In order to facilitate this a standardisedprotocol over generic data bearers should be agreed. This would allow software developers to add thismethod of fax transfer to standard PC software packages.

It was also hoped that fax users who move between UMTS and GSM coverage would not suffer fromdropped calls. This would infer that a fax call in GSM using T.30 would be prevented from handingover to UMTS, but no restriction would be necessary handing over in the UMTS to GSM direction.

SMG1 should note that SMG4 will be investigating via a proposed new work item, the suitability ofT.38 ( Fax over IP) as a possible candidate for UMTS fax services.

Circuit Switched data

This section appears to be acceptable as long as the same IWF is used in UMTS as for GSM.

Packet switched data

Delegates agreed that section 5 should contain additional text describing packet data in UMTS and thatit should be described in a way that compares it to GPRS.

Section 8.9

If UMTS does not support T.30 it not supporting all the services supported in GSM in the same way.This text should be clarified.

In general, SMG4 UMTS would like to emphasise the importance of standardising protocols andinterfaces so that services become very easy for the average customer to use. Without adequatestandards chaos will reign, resulting in an inability to run profitable services.

ETSI SMG #27 Tdoc SMG 98-0624Prague, The Czech Republic12 – 16 October, 1998

Source: SMG

Position Paper on the UICC for early UMTS systems

SMG have been looking at the requirements for the UMTS (Third Generation) USIM, notingparticularly, the requirement that UMTS evolves from GSM. As part of the evolutionaryapproach from GSM to Third generation systems, it is a requirement that 3G terminals supportexisting (Phase 2) SIMs (at three volts, but not five volt SIMs), but it is not a requirement thatGSM terminals support 3G USIMs. It is the strong opinion of SMG that the UICC (UMTSIntegrated Circuit Card) is a mandatory element of Third Generation systems.

It is recognised that the existing physical interface should remain unchanged (toaccommodate the need for interworking with GSM), however, that there may be the need toenhance the interface, both in terms of protocol (for example, employing the T=1 protocol),and speeding up the bit transmission rate across the interface.

It is recognised that the existing two physical sizes may prove to be limiting to mobileequipment (ME) designs for 3G mobiles, so consideration is being given to a third physicalsize of SIM, (e.g. a cut down version of existing "Plug-in" SIM, without affecting the existingmandatory physical interface). The UICC / terminal interface remains mandatory.

The other important feature of the SIM is the SIM Application Toolkit; this is a powerful tool foroperators, and can be easily exploited and enhanced for 3G operations, especially in the areaof Virtual Home Environment. Allied to this is the security for the Toolkit, where end-to-endmessaging between the Application area in the SIM and its partner entity in, or behind, thenetwork, can be secured, to prevent fraud or interception. Enhancements exploiting newerbearer services will be included for the Toolkit.

The next generation SIM will be a multi-application card, including support for applicationloading; SMG fully expect this work to be completed and approved in June 1999.

It is the opinion of SMG9 that the existing SIM technology and functionality is an ideal baselineplatform for early third generation systems; it is recognised that there will of necessity bealterations and additions to the file structure in the existing SIM to accommodate UMTSfunctionality, but this is believed to be easily undertaken.

ì ¥ Á ` G ` ¯ ` ` ` • ¿ ` ` ` ` ` ` • ` ` ` ` ` ¯ ` ` ƒ ¨ ` `

` b j b j • Ù • Ù ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` `¯ • ` - • ` ` ì ³ ´ ` ì ³ ´ ` ƒ ˜ ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ÿ ÿ • ` `

` ` ` ` ` ` ` ÿ ÿ • ` ` ` ` ` ` ` ` ` ÿ ÿ • ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ] ` ` ` ` ` ’ ` ` ` ` ` ` ` ’ ` `` ’ ` ` ` ` ` ` ` ’ ` ` ` ` ` ` ` ’ ` ` ` ` ` ` ` ’ ` ` ` ` ` ` ` ’ ` ` ` • ` ` ` ` ` ` ` ` ` ` ` Â ` ` ` ` ` `` Â ` ` ` ` ` ` ` Â ` ` ` ` ` ` ` Â ` ` ` ` ` ` ` Â ` ` `

` ` ` Î ` ` `

` ` ` Â ` ` ` ` ` ` ` t ˙ ` ` ˝ ´ ` ` æ ` ` ` ` ` ` ` æ ` ` ` ` ` ` ` æ ` ` ` ` ` ` ` æ ` ` ` ` ` ` ` æ ` `` ` ` ` ` æ ` ` ` ` ` ` ` æ ` ` ` ` ` ` ` æ ` ` ` ` ` ` ` \ ¯ ` ` ˆ ` ` ` ^ ¯ ` ` ` ` ` ` ^ ¯ ` ` ` ` ` ` ^ ¯` ` 5 ` ` ` “ ¯ ` ` Ô ` ` ` g ˘ ` ` Ô ` ` ` ; ˙ ` ` $ ` ` ` ~ ¨ ` ` ô ´ ` ` r

` ` œ ` ` ` _ ˙ ` ` • ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ’ ` ` ` ` ` ` ` æ ` ` ` ` ` ` ` ` ` `` ` ` ` ` ` ` ` ` ` ` ` ` æ ` ` ` ` ` ` ` æ ` ` ` ` ` ` ` æ ` ` ` ` ` ` ` æ ` ` ` ` ` ` ` _ ˙ ` ` ` ` ` ` b´ ` ` ` ` ` ` ’ ` ` ` ` ` ` ` ’ ` ` ` ` ` ` ` æ ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` æ ` ` ` ` ` ` ` æ ` ` ` ` ` `` b ´ ` ` ` ` ` ` b ´ ` ` ` ` ` ` b ´ ` ` ` ` ` ` æ ` ` ` | ` ` ` ’ ` ` ` ` ` ` ` æ ` ` ` ` ` ` ` ’ ` ` ` ` ` `` æ ` ` ` ` ` ` ` \ ¯ ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ¦ ` ` `

` ` ` ´ ` ` `

` ` ` ’ ` ` ` ` ` ` ` ’ ` ` ` ` ` ` ` ’ ` ` ` ` ` ` ` ’ ` ` ` ` ` ` ` æ ` ` ` ` ` ` ` \ ¯ ` ` ` ` ` ` b ´ ` ` ú ˆ` ` b ´ ` ` ` ` ` ` ` ` ` ` ` ` ` ` \ ¯ ` ` ` ` ` ` ’ ` ` ` ` ` ` ` ’ ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` `` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` \ ¯ ` ` ` ` ` ` æ ` `` ` ` ` ` Ú ` ` `

` ` ` • ò • ø ê ø ½ ´ Â ` ` ` ` ` ` ` Â ` ` ` ` ` ` ` b ´ ` ` ` ` ` ` \ ¯ ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` `` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` `` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` `` ` ` ` ` ` ` ` ` ` ` ` ` ` ` `ETSI TC SMG#27 Plenary Meet ing Tdoc SMG 98-640Praha, Czech Republic12nd- 16th October 1998

Source: SMG#27

Subject: LS to GSM MoU EIG and SMG7Common position on Article 3 “Essential Requirements” of the draft R&TTE Directive

SMG#27 has adopted the position on Article 3 “Essential Requirements” of the draft R&TTE Directivedescribed in Tdoc SMG#27 98-581.

Provided that GSM MoU EIG and SMG7 share this position SMG#27 proposes to liaise this position tothe European Commission and to the R&TTE Steering Group and Ad Hoc Group on EssentialRequirements with a copy to TC ERM TG6 as it is suggested in the last section of Tdoc SMG#27 98-581.

SMG#27 welcomes the views of GSM MoU EIG and SMG7 on the proposed position on Article 3“Essential Requirements” of the draft R&TTE Directive. SMG7 is kindly asked to co-ordinate theliaisons with the above mentioned parties.` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` `` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` `` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` `` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` `` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` `` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` `` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` `` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` `` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` `` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` `` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` `` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` `` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` `` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` `` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` `` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` `` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` `` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` `` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` `` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` `` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` `` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ¯ ` ` [ ¯ ` ` ] ¯ ` ` a ¯ ` ` c ¯ `` r ¯ ` ` s ¯ ` ` ý ¯ ` ` ƒ ¨ ` ` ÷ í ÷ í ÷ æ à × ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` `` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` `` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` `` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` `` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` `` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` `` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` `` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` • C J • ` O J ˜ ` Q J ˜ ` m H ˚ `5 ˚ • C J • ` m H ˚

O J ˆ ` Q J ˆ ` m H˚ ` • 5 ˚ • C J • ` H * ´ O J ˆ ` Q J ˆ ` ` • 5 ˚ • C J • ` O J ˆ ` Q J ˆ ` ` ˚̀ ¯ ` ` C ¯ ` ` Y ¯ ` ` q

¯ ` ` r ¯ ` ` s ¯ ` ` ‚ ¯ ` ` ƒ ¯ ` ` § ¯ ` ` û ¯ ` ` ü ¯ ` ` ý ¯ ` ` ‚ ˘ ` ` ƒ ˘ ` ` ˙ ` ` ¡ ˙ ` ` ƒ ¨ ` ` ø ` ` `` ` ` ` ` ` ` ` ` ö ` ` ` ` ` ` ` ` ` ` ` ` ö ` ` ` ` ` ` ` ` ` ` ` ` ö ` ` ` ` ` ` ` ` ` ` ` ` ö ` ` ` ` `` ` ` ` ` ` ` ð ` ` ` ` ` ` ` ` ` ` ` ` ð ` ` ` ` ` ` ` ` ` ` ` ` ð ` ` ` ` ` ` ` ` ` ` ` ` ð ` ` ` ` ` ` `` ` ` ` ` í ` ` ` ` ` ` ` ` ` ` ` ` í ` ` ` ` ` ` ` ` ` ` ` ` í ` ` ` ` ` ` ` ` ` ` ` ` í ` ` ` ` ` ` ` ` ` `` ` í ` ` ` ` ` ` ` ` ` ` ` ` í ` ` ` ` ` ` ` ` ` ` ` ` í ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` `` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` `` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` `` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` `` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ˜ ` ` ˜ $ ˜ ` ˘ ` ` • „ Š ˘ • „ v ú ` ´ ` ` ¨ ` `Æ ˚ ` ˆ q # Œ $ ˆ ˆ ` • ` ¯ ` ` C ¯ ` ` Y ¯ ` ` q ¯ ` ` r ¯ ` ` s ¯ ` ` ‚ ¯ ` ` ƒ ¯ ` ` § ¯ ` ` û ¯ ` ` ü ¯ ` ` ý ¯` ` ‚ ˘ ` ` ƒ ˘ ` ` ˙ ` ` ¡ ˙ ` ` ƒ ¨ ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` `` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` `` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` `` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` `` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` `` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` `` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` `` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` `` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` ` • • ` °‚.° Æ A ! ° ˚ ¨ " ° ˚ ¨ # • ˘ $ • ˘ % ° ` `

ETSI TC SMG Tdoc SMG 98-642Meeting #27Praha, 12-16 October 1998,

Source: SMG #27

To: SMG 2

cc: SMG 8, SMG 11

Liaison Statement

Title: Testability of AMR in the BSS

IntroductionDuring the discussion on AMR in SMG #27, several issues have been identified relating to AMRwhich may impact the testability of AMR within the BSS. In view of the urgency expressed for thecompletion of the AMR standards, these are brought to the attention of SMG 2 before the nextmeeting of SMG 8.

AMR employs an adaptation mechanism within the base station. It is important that testability istaken into account in the way the radio interface requirements are defined; if this is not done, it maylater be found that the AMR requirements are not testable for the BSS. Some of theserequirements may be “essential requirements” which must be tested for type approval (especiallyreference sensitivity and interference).

SMG 8 has previously found it impossible to fully define tests for parameters which are internal tothe BSS (RXLEV and RXQUAL), which could only be achieved using special functionality fortesting. This could not be implemented on equipment which was already deployed. It is thereforeimportant for AMR that any functionality required for testing is defined in the initial release of AMRstandards:� It is clear from the discussions in SMG #27 that there is commercial pressure for AMR to be

deployed soon.� The functionality may be needed for tests which are required for type approval (which is not the

case for RXLEV and RXQUAL).

RecommendationsThese recommendations are intended primarily to assist SMG 2 in its work on AMR before the nextmeeting of SMG 8.

The testability of AMR in the BSS should be taken into consideration during the initial definition ofradio interface requirements. This should include:� Definition of requirements of the BTS only (ie to allow testing of the BTS independent of the

TRAU)� Definition of necessary test conditions (and if required, test loops, test point or test modes)� Consideration as to whether the AMR signalling needs to be tested, and if so, how.� Consideration should be given as to whether the performance of the BTS measurement of the

quality metric needs to be tested, and if so, how.

As SMG 2 will need to start its work on AMR before the next meeting of SMG 8, it is suggested thatSMG 2 should use the following working assumption:

- the majority of testing should be performed in a test mode using a single channelcodec mode, with the adaptation mechanism disabled.

DiscussionFor the MS, many of the tests are performed using a test loop defined in GSM 11.10. SMG 7 isgiven a mandate to define test loops for measuring performance of RF parameters by a statementin clause 6 of GSM 05.05. There is no equivalent statement in GSM 05.05 relating to testing of theBSS, and SMG 8 has previously concluded that it does not have authority to define mandatoryrequirements for the BSS for testing purposes (for example, mandatory test points, test loops ortest modes).

The adaptation mechanism for AMR is understood to be implemented within the base station, andis believed to use both a parameter reported by the MS and a parameter measured by the basestation. However, the adaptation algorithm is not fully specified, and manufacturers’ proprietaryalgorithms can be used. This means that the state of operation of the BTS cannot be defined bythe characteristics of the signal applied to the antenna connector.

One possible approach to the testing of AMR would be possible using a test apparatus whichemulated the adaptation process within the MS. However, this approach has not previously beenadopted by SMG 8 for BSS testing. It would therefore take some time for SMG 8 to develop asuitable test methodology, and current test equipment is unlikely to be capable of performing thesetests. This approach to testing would include the performance of the uplink AMR signalling channelperformance and the measurement of the performance metric in the BTS. However, it may be verydifficult to define the performance requirements for such a complex dynamic system.

An alternative approach would be to define a test mode of operation which would disable the AMRadaptation mechanism, and enable the different channel codec modes to be tested independently.This would allow the existing test methodology to be used for AMR. This approach would not testthe uplink AMR signalling channel performance or the measurement of the performance metric inthe BTS, although independent requirements could be defined for these parameters.

SMG #27 was advised by the Chairman of SMG 8 that the second approach will probably bepreferable, for the following reasons:� It is likely to result in well defined requirements, which will result in tests which can be

implemented consistently.� The approach is similar to the current BTS tests, which enable the test cases to be developed

and implemented quickly.

The consequences of this recommendation to SMG 2 would be:� SMG 2 would need to either define test modes, or mandate SMG 8 to define them.� SMG 2 would need to consider whether (and if so, how) the following aspects of AMR should

be tested in the BTS:� Uplink AMR signalling� the measurement of the performance metric in the BTS� The overall performance of the AMR radio interface, including the adaptation process.

ETSI SMG #27 TDoc SMG 98-0668Prague, The Czech Republic12 - 16 October, 1998

Source : SMG9Agenda item: 6.9

SMG9 Status Report

This document gives an overview of the status of work in SMG9 for the period June 1998(SMG #26) - October 1998 (SMG #27).

Contents

1 Executive summary.............................................................................................................................................2

2 Meetings .......................................................................................................................................................2

3 Status of SMG9 specifications before SMG #27 ..........................................................................................3

4 Change requests to Phase 2/2+ specifications ............................................................................................34.1 GSM 11.11, SIM/ME interface specification..................................................................................34.2 GSM 11.14, SIM Application Toolkit .............................................................................................34.3 GSM 02.17, SIM functional characteristics. ..................................................................................44.4 EG 201 220, ETSI numbering system for telecommunication application providers (AID)...........5

5 SMG9 Working Parties and ad hoc groups ..................................................................................................55.1 GSM API .......................................................................................................................................55.2 UMTS ............................................................................................................................................55.3 Generics Working Party ...............................................................................................................6

6 Other Issues .................................................................................................................................................66.1 1,8V SIM/ME interface specification (GSM 11.18)........................................................................66.2 New scope of SMG9 .....................................................................................................................6

7 Meeting Calendar .........................................................................................................................................6

8 List of Documents Submitted to SMG #27 ...................................................................................................7

9 Decisions required from SMG #27 ...............................................................................................................7

ANNEX A LS from SMG9 to SMG on Application Identifiers..................................................................................8

ANNEX B LS to SMG on the use of AT commands from SIM toolkit applications ...............................................13

ANNEX C LS to SMG on the UICC in early UMTS systems.................................................................................14

ANNEX D Terms of Reference of SMG9..............................................................................................................15

Number of pages: 15

SMG9 Status report to SMG #27 Page 2 of 15

1 Executive summary

- SMG9 has held its 16th plenary meeting in the period between SMG #26 and SMG #27. AnSMG9 #16bis meeting will be held on 2 - 4 December 1998 in order to allow a timely completion ofrelease 98 issues.

- SMG9 has held 5 working party and ad hoc meetings in the period between SMG #26 and SMG #27.- SMG9 had one joint meeting with SMG1 on the elaboration of the Stage 1 specification for the SIM

Application Toolkit.- a new working party has been formed to work on generic IC card issues. The chairman is Rune

Lindholm from Nokia.- the testing working party has a new chairman, Gerd Pfaffenholz from Orga Kartensysteme.- 2 non-strategic CRs to GSM 11.11 are presented in tdoc 98-0671.- 10 non-strategic Phase 2+ CRs to GSM 11.14 are presented in tdoc 98-0670.- 2 strategic Phase 2+ CRs to GSM 11.14 are presented in tdoc 98-0669.- 1 non-strategic Phase 2+ CR to GSM 02.17 is presented in tdoc 98-0403.- GSM 02.19 v2.0.0 is presented for approval as a release 98 specification in tdoc 98-0674.

2 Meetings

The 16th meeting of ETSI SMG9 was held in St Cyr Sur Mer, France from the 22nd to the 25th September, 1998at the invitation of Atmel. The meeting was chaired by Klaus Vedder and was attended by 73 delegates from 15countries.

The following working party and ad hoc meetings have also been held since SMG #26:

- The UMTS Working Party held two meetings hosted by Nokia in August and ETSI in October. Thechairman is Günter Maringer from T-Mobil;

- The SIM API Working Party had two meetings, hosted by ETSI in July and by De La Rue in September.The chairman is Mark Green from Orange.

- The Testing working party has held one meeting hosted by Bosch Telecom. The chairman (for thatmeeting) was Phil Hooker from Orange.

- The joint SMG1 SMG9 meeting for the Stage 1 specification of the SIM Application Toolkit was hosted byETSI. The chairman is Nigel Barnes from Motorola.


3 Status of SMG9 specifications before SMG #27

Spec Title Phase Version(beforeSMG #27)

GSM / UMTS SPECIFICATIONSGSM 02.17 SIM functional characteristics phase 1 3.2.0

phase 2 4.3.3release 96 5.0.1release 98 7.0.0

GSM 02.19 (DRAFT) SIM Application Programming Interface (API) Stage 1 release 98 2.0.0GSM 02.48 SIM toolkit secure messaging (stage 1) release 97 6.0.0GSM 03.48 SIM toolkit secure messaging (stage 2) release 97 6.1.0GSM 09.91 Interworking Aspects of the SIM/ME Interface Between Phase 1 and Phase 2 phase 2 4.0.1GSM 11.11 Specification of the SIM-ME Interface phase 1 3.16.0

phase 2 4.20.0release 96 5.10.0release 97 6.1.0release 98 7.0.0

GSM 11.12 Specification on the 3 Volt SIM-ME Interface phase 2 4.3.1GSM 11.14 Specification of the SIM-ME Interface for the SIM application toolkit release 96 5.8.0

release 97 6.1.0release 98 7.0.0

GSM 11.17 (DRAFT) SIM conformance test specification 1.1.0GSM 11.18 (DRAFT) 1.8 Volt SIM-ME Interface release 99 1.3.0UMTS 22.11 UICC and USIM requirements UMTS 0.2.0

NON-GSM SPECIFICATIONSEG 201 220 ETSI numbering system for telecommunication Application providers (AID) n/a 1.2.1EG 201 227 ETSI numbering system for telecommunication; ALgorithm IDentifiers (ALID) n/a 1.2.1TR 101 223 Integrated Circuits Cards (ICC); Definitions of differences and their hierarchical

relationshipn/a 1.1.1

4 Change requests to Phase 2/2+ specifications

All CRs listed in this section were agreed by SMG9 at SMG9 #16.

4.1 GSM 11.11, SIM/ME interface specification

The following non-strategic CRs were agreed at the last SMG9 meeting. They can be found in TdocSMG 98-0671.

- CR 11.11-A071(R98) introduces an enhance image coding scheme that will enable colour icons to bestored on the SIM in a standardised manner.

- CR 11.11-A072 (R98) is a harmonisation CR that adds reference to PCS 1900. This is done at therequest of ANSI T1P1.

4.2 GSM 11.14, SIM Application Toolkit

The following CRs had been postponed by SMG #26. They are re-presented without modification in Tdoc 98-0669.

CR 11.14-A084 (R96) introduces a new class 1bis to reduce the number of MEs on the market offeringonly partial and differing support of class 2. This CR was first put forward for approval at SMG #26.SMG #26 concluded that SMG1 should examine the issue of SIM toolkit classes as it was more of aservice / commercial issue. SMG1 reviewed the CR at the Naantaali meeting in July and mandated theirSIM toolkit stage 1 working party to decide on the CR. That group agreed that the CR should beforwarded unchanged to SMG #27 for approval. SMG9 ratified the decision.

- CR 11.14-A087 (R97) is the release 97 version of CR 11.11-A084.- CR 11.14-A112 (R98) is the release 98 version of CR 11.11-A084.

The following strategic CR was agreed at the last SMG9 meeting. It can be found in tdoc SMG 98-0669.

- CR 11.14-A111 (R98) introduces a new command to the SIM application toolkit "RUN AT COMMAND".This will allow the application to execute all specific AT commands that the ME supports. This includesthose specified (in GSM 07.07) as well as manufacturer specific commands. Typical uses for such


functionality are remote diagnostics, customer care and control of unattended terminals.

During discussion at the last plenary, two main concerns arose. The first is that the SIM toolkit would nowbe promoting the opportunity for non-standardised ME/service behaviour to be introduced. The second isthat the feature would effectively bypass the current concept of toolkit classes which fully define an ME’stoolkit behaviour. Concern was also raised about the ME setting up calls without the user's knowledge orconfirmation.

A vote on the CR during the last SMG9 plenary indicated that there were 15 delegates in favour, 5 againstand 45 abstentions. It was therefore concluded that the CR should be sent to SMG #27 but that theconcerns of some SMG9 members should be made known to SMG #27. These concerns can be found inthe LS from SMG9 to SMG in annex B of this report.

The following non-strategic CRs were agreed at the last SMG9 meeting. They can be found in tdocSMG 98-0670.

- CR 11.14-A091r1 R98: "Yes/No" response for GET INKEY. Most of SIM Toolkit applications using theGET INKEY command actually expect only a "YES" or "NO" response. This new feature simplifies theSIM Toolkit application and provides an improved user MMI.

- CR 11.14-A092 R98: Alignment of coding of card reader status event. This corrects the encoding of cardreader status event thus aligning it with the encoding of the other events.

- CR 11.14-A093 R97: Additional information field mandatory in case of USSD Return Error result. Thisclarifies that if result code '37' is returned, the ME shall provide a specific cause value as additionalinformation.

- CR 11.14-A094 R98: This is the release 98 version of CR 11.14-A093.- CR 11.14-A095 R97: This CR corrects the omission of the SET UP EVENT LIST command from the

table that shows all possible result values for all commands.- CR 11.14-A096 R96: This CR clarifies that in the case where the SIM issues an instruction to the ME to

initiate a Mobile Originated transaction (e.g. SEND SMS, SEND USSD), the content supplied by the SIMfor onward transmission by the ME shall not be altered by the ME unless explicitly stated elsewhere inGSM 11.14 or in GSM 11.11.

- CR 11.14-A097 R97: This is the release 97 version of CR 11.14-A096.- CR 11.14-A098 R98: This is the release 98 version of CR 11.14-A096.- CR 11.14-A099 R97: Clarification about USSD return result.- CR 11.14-A100 R98: Clarification about USSD return result.- CR 11.14-A101 R97: This is the release 97 version of CR 11.14-A102.- CR 11.14-A102 R96: This CR clarifies the handling the handling of the ‘9300’ status response for the

envelope command for SMS Data download, Call Control and SMS Call Control. All other cases arealready defined in GSM 11.11.

- CR 11.14-A103 R98: This is the release 98 version of CR 11.14-A102.- CR 11.14-A104 R98: This CR introduces a new command SET UP IDLE MODE TEXT. The text supplied

by the command is not allowed to overwrite information of higher importance such as the serviceprovider's name.CR 11.14-A108 R98: This CR clarifies that the ME shall not locally generate audible DTMF tones andplay them to the user during a SET UP CALL command.

- CR 11.14-A109 R97: This change describes the handling of the TERMINAL RESPONSE command inthe case where CALL CONTROL by SIM is triggered after a proactive command SET UP CALL, SENDSS or SEND USSD.

- CR 11.14-A110 R98: This is the release 98 version of CR 11.14-A109.

4.3 GSM 02.17, SIM functional characteristics.

A complete revision of GSM 02.17 to align it with the changes made to GSM 11.11 and GSM 11.14 over the lastyears had been presented to SMG #26 for information and comment. As no comments were received SMG9agreed to present the "new" GSM 02.17 to SMG #27 for approval. The two CRs are contained inTdoc 98-0403.

- CR 02.17-A001 (R96) aligns GSM 02.17 with changes that have been made to GSM 11.11 and GSM11.14 and are not currently reflected.

- CR 02.17-A003 (R98) is a release 98 version of CR 02.17-A001.


4.4 EG 201 220, ETSI numbering system for telecommunication application providers (AID)

SMG9 has recently become responsible for the documents previously in the control of TC ICC. EG 201220 is one such document. The change request contained in Tdoc 98-0673 is proposed as a result ofwork being done on GSM 02.19, the SIM API. The implementation of the SIM API requires that anapplication residing on the smart card is referenced by the operating system by an Application Identifier(AID). This change allows card applications to be administered by the card issuer, using a generic PIXstructure, without the necessity for a plethora of applications for AIDs to the ETSI Secretariat.

5 SMG9 Working Parties and ad hoc groups

There was no meeting of the SIM Toolkit Security Working Party.

5.1 GSM API

At SMG #25 the new SMG9 work item "SIM Application Programming Interface" received final approval. AtSMG #26, GSM 02.19 (the stage one description) was presented for information and comment.

Two working party meetings have been held since July. The last SMG9 plenary slightly modified the versionpresented to SMG #26 and agreed that the revised version of GSM 02.19 should be forwarded to SMG #27 forapproval. This can be found in tdoc SMG 98-0674.

Work has now started on producing the stage 2 descriptions. The first document, GSM 03.19, will specify aJava API. This is being developed in co-operation with the Java Card forum and will be based on Java Card 2.1.It is expected that this will be presented to SMG #28 for information. The second document will describe astandardised method downloading applications to the SIM "over the air". This specification will be based on thework already done by VISA international. It is expected that this document will be presented to SMG #28 forinformation.

In order to manage SIM Toolkit Applications and the GSM application on a card implementing the SIM API it isnecessary to refer to these applications by a unique application identifier. It has therefore been agreed by SMG9to adopt the ISO/IEC 7816-5 mechanism. ETSI references this mechanism in an ETSI guide EG 201 220. Inline with the procedures in the ETSI guide, SMG9 has completed the required registration forms for a GSMApplication identifier and a SIM Toolkit Application identifier. These are attached in annex A of this report forSMG to endorse and forward to the ETSI secretariat.

5.2 UMTS

The UMTS working party has held two meetings since August. They expect to have specifications ready asfollows:

UMTS 22.11 A report on UICC and USIM requirements, v 1.0.0 at SMG #28;UMTS xx.yy UICC / ME interface specification; Physical and electrical layer, v1.0.0 at SMG #29;UMTS xx.zz UICC / ME interface specification; logical layer, v1.0.0 at SMG #29.

It should be noted that a UICC is a physical UMTS IC card and a USIM is the application resident on that card.

As a result of discussion at the working party meetings, several key proposals were presented to SMG9 #16.They are:

- a new size for the UICC should be developed. Basically, a plug-in card with any plastic around the contactarea removed is suggested. SMG9 endorsed that options for a new (smaller) sized SIM should bestudied.

- the T=1 protocol should be mandatory for both the UICC and the ME. The T=0 protocol (as used by theSIM) would also need to be supported for reasons of backward compatibility. This was endorsed bySMG9.

- the UICC shall support the new requirements in the 2nd edition of ISO/IEC 7816-3 (1997). This wasendorsed by SMG9.

- all UMTS MEs and UICCs shall support at least 2 voltage classes. This was endorsed by SMG9.- interface speed enhancements shall be supported by all UICCs and UMTS MEs.- the International Standard ISO/IEC 7816-5 shall be used for application selection. This is the same

approach used by the SIM API working party and was endorsed by SMG9.- a standardised mechanism for secure downloading is required (this is not currently specified for GSM). It


was agreed that the newly created Generic Working Party should examine the issue and produce a workitem. The work should be in line with that done by the SIM API group.

It was noted by the group that none of the approved UMTS documents state that the UICC is a mandatoryelement of UMTS. SMG9 has therefore produced a position paper (see LS to SMG in annex C of this report)stating this and several of the points mentioned above. SMG9 requests that SMG #27 endorse this document.

5.3 Generics Working Party

At the last SMG9 plenary, it was agreed that a new working party should be formed to cover generic IC cardissues. Rune Lindholm from Nokia was elected as chairman.

The working party is required as a result of SMG9 taking over some of the work items from the former ETSI TCICC. It is planned that this working party should co-operate closely with other active ETSI groups involved in ICcard issues. In particular, joint meetings / sessions with ETSI EP PTS (Pay Terminals and Systems) are seenas important.

One of their initial work items will be to study the possibility of standardising administration commands based onEN 726-3 and an "over the air" downloading mechanism (in conjunction the SMG9 SIM API working party).

6 Other Issues

6.1 New scope of SMG9

At the ETSI board meeting from the 9th to 11th June, it was decided that the ETSI TC ICC should close and thatexisting work items from that committee should be transferred to SMG9. This makes SMG9 the main focus ofETSI card standardisation activities. SMG9 reported at SMG #26 that this would require a review of their termsof reference. This review took place at the last SMG9 plenary meeting and resulted in a new version which canbe found in annex D of this report.

7 Meeting Calendar

SMG9 currently has the following plenary and working party meetings planned:

Meeting Date Host LocationSMG9 #16bis 2 - 4 December, 1998 ETSI Sophia Antipolis, France

SMG9 #17 18 - 22 January, 1999 Alcatel Paris, France

SMG9 #18 May, 1999 Finnet, Nokia, TelecomFinland, Telehallintokeskus

Finland

SMG9 #19 September 1999 Giesecke & Devrient,Siemens

Munich, Germany

SMG9 #20 January 2000 host requiredSMG9 #21 May 2000 Lucent New Jersey, USSMG9 #22 September 2000 host required

----- Working Parties and other ad hoc groups ------

SMG9 API #6 9 - 10 December 1998 Incard Spa Naples, Italy

SMG9 API #7 2 - 3 March, 1999 host required

SMG9 Generics #1 2 - 3 November, 1998 ETSI Sophia Antipolis, France

SMG9 UMTS #5 6 - 7 October, 1998 ETSI Sophia Antipolis, France

SMG9 UMTS #6 4 - 5 November, 1998 ETSI Sophia Antipolis, France

SMG9 UMTS #7 15 - 16 December, 1998 Nokia (?) Copenhagen (?), Denmark

SMG1/9 Toolkit 21 - 22 October,1998 host required

SMG1/9 Toolkit 1 - 2 December 1998 Munich Giesecke & Devrient


8 List of Documents Submitted to SMG #27

SMG #27Tdoc

Title SMG9tdoc

98-0668 SMG9 Status report to SMG #27 including: -

Annex A: LS to SMG: Application identifiers for GSM and SIM toolkit applications resident on the SIM 98p372Annex B: LS to SMG: The use of AT commands from SIM toolkit applications 98p373Annex C: LS to SMG cc ECTEL TMS, MoU SERG: Position paper on the UICC for early UMTS systems 98p383Annex D: Proposed new scope of SMG9 98p387

98-0669 Change requests to GSM 11.14 with presentation -

CR 11.14-A084 R96: Addition of 1bis SIM toolkit class 98p244CR 11.14-A087 R97: Addition of 1bis SIM toolkit class 98p253CR 11.14-A112 R98: Addition of 1bis SIM toolkit class

strategic CR 11.14-A111r1 R98: Enhancement to Proactive SIM that enables the SIM to issue AT commands 98p351

98-0670 R96, R97 and R98 change requests to GSM 11.14 (non-strategic) -

CR 11.14-A091r1 R98: "Yes/No" response for GET INKEY 98p358CR 11.14-A092 R98: Alignment of coding of card reader status event 98p343CR 11.14-A093 R97: Additional information field mandatory in case of USSD Return Error result. 98p344CR 11.14-A094 R98: Additional information field mandatory in case of USSD Return Error result. 98p345CR 11.14-A095 R97: Possible result values for SET UP EVENT LIST command 98p346CR 11.14-A096 R96: Clarification regarding the ME changing the contents of SIM commands 98p355CR 11.14-A097 R97: Clarification regarding the ME changing the contents of SIM commands 98p356CR 11.14-A098 R98: Clarification regarding the ME changing the contents of SIM commands 98p357CR 11.14-A099 R97: Clarification about USSD return result 98p362CR 11.14-A100 R98: Clarification about USSD return result 98p374CR 11.14-A101 R97: Clarification of the ’93 00’ status response handling 98p375CR 11.14-A102 R96: Clarification of the ’93 00’ status response handling 98p376CR 11.14-A103 R98: Clarification of the ’93 00’ status response handling 98p377CR 11.14-A104 R98: New command - SETUP IDLE MODE TEXT 98p378CR 11.14-A108 R98: Handling of DTMF in SETUP CALL command 98p369CR 11.14-A109 R97: Interaction between call control by SIM / MO SM control and proactive commands 98p370CR 11.14-A110 R98: Interaction between call control by SIM / MO SM control and proactive commands 98p389

98-0671 R98 change request to GSM 11.11 (non-strategic)CR 11.11-A071 R98: Enhanced image coding schemes (colour icons) 98p339CR 11.11-A072 R98: Addition of reference to PCS 1900

98-0672 R96 and R98 change requests to GSM 02.17 (non-strategic)CR 02.17-A001 R96: Alignment of GSM 02.17 with GSM 11.11 and GSM 11.14 98p083CR 02.17-A003 R98: Alignment of GSM 02.17 with GSM 11.11 and GSM 11.14

98-0673 Change request to EG 201 220 "ETSI numbering system for telecommunication application providers (AID)"Addition of Normative Annex, introducing AID coding for GSM and Toolkit applications 98p371

98-0674 GSM 02.19 v2.0.0 (SIM Application Programming Interface) 98p353

9 Decisions required from SMG #27

- Approval of the strategic CRs to GSM 11.14 (tdoc 98-0669)- Approval of the non strategic CRs to GSM 11.14 (tdoc 98-0670)- Approval of the non strategic CRs to GSM 11.11 (tdoc 98-0671)- Approval of the non strategic CRs to GSM 02.17 (tdoc 98-0672)- Approval of the non strategic CRs to EG 201 220 (tdoc 98-0673)- Approval of GSM 02.19 v2.0.0 "SIM Application Programming Interface" (tdoc 98-0674)- Approval of scope of SMG9 as contained in annex D of this report- Endorsement of the SMG9 position paper on the UICC and USIM requirements for UMTS as

contained in annex C of this report.- Endorsement of SMG9's application for two application identifiers to be allocated by ETSI (see

request in annex A of this report)

SMG9 Status report to SMG #27 ANNEX A Page 8 of 15

ANNEX A LS from SMG9 to SMG on Application Identifiers

ETSI SMG9 Tdoc SMG9 98p372September 1998 (replaces 98p359)Saint-Cyr-Sur-Mer

Liaison Statement

Subject: Request for the definition Application Identifiers for the GSM application andthe SIM Toolkit applications

To: SMG

From: SMG9

In order to manage SIM Toolkit Applications and the GSM application on a card implementingthe SIM API it is necessary to refer to these applications by a unique application identifier.

It has therefore been agreed by SMG9 to adopt the ISO/IEC 7816-part 5 mechanism. ETSI isalready referencing this mechanism in an ETSI guide EG 201 220.

In line with the procedures specified in EG 201 220, SMG9 has completed the requiredregistration forms for the GSM Application and the SIM Toolkit Applications. These areattached for SMG to endorse and forward to the ETSI secretariat.

A CR to this ETSI guide (Tdoc SMG 98-0673) is also forwarded for approval. This introducesa new normative Annex, containing coding schemes for the Proprietary Application IDExtension (PIX) specifically for the GSM applications. This change details ApplicationProvider Code and Application Provider Field coding schemes.


GSM Application AID Registration Form (1/2)

Annex A:Request registration form for an ETSI PIX number

Request form to be filled in and addressed to:

ETSI Secretariat

Postal address:06921 Sophia AntipolisCedex - FRANCE

Tel.: +33 4 92 94 42 00Fax: +33 4 93 65 47 16Internet: [email protected]

This request is submitted in accordance with EG 201 220, i.e. the present document.

A.1 To be completed by the requesting organization

Name of organization: ETSI / SMGAddress of organization:

Principal contact in organization: STF SMG

Telephone number: Fax number:Address for correspondence/billing:

European VAT Id:Country, if not identical with country in address field:Number and title of the ETSI document to which the telecommunication IC card application in questioncomplies:

GSM 11.11“ Technical Specification ; Digital cellular telecommunications system (Phase 2+);

Specification of the Subscriber Identity Module – Mobile Equipment (SIM - ME) interface “

ETSI card application code to which the telecommunication IC card application in question complies:

This request is for the ETSI application code itself rather than a subsidiary application i.e. digits 1to 4 of the PIX

Date: Signature:


GSM Application AID Registration Form (2/2)

A.2 To be completed by the ETSI Secretariat

ETSI PIX number:Date: Signature:


SIM Toolkit Application AID Registration Form (1/2)

Annex A: Request registration form for an ETSI PIX number

Request form to be filled in and addressed to:

ETSI Secretariat

Postal address:06921 Sophia AntipolisCedex - FRANCE

Tel.: +33 4 92 94 42 00Fax: +33 4 93 65 47 16Internet: [email protected]

This request is submitted in accordance with EG 201 220, i.e. the present document.

A.1 To be completed by the requesting organization

Name of organization: ETSI / SMGAddress of organization:

Principal contact in organization: STF SMG

Telephone number: Fax number:Address for correspondence/billing:

European VAT Id:Country, if not identical with country in address field:Number and title of the ETSI document to which the telecommunication IC card application in questioncomplies:

GSM 11.14“Technical Specification; Digital cellular telecommunications system (Phase 2+);

Specification of the SIM application toolkitfor the Subscriber Identity Module – Mobile Equipment (SIM - ME) Interface”

ETSI card application code to which the telecommunication IC card application in question complies:

This request is for the ETSI application code itself rather than a subsidiary application i.e. digits 1to 4 of the PIX

Date: Signature:


SIM Toolkit Application AID Registration Form (2/2)

A.2 To be completed by the ETSI Secretariat

ETSI PIX number:Date: Signature:

SMG9 Status report to SMG #27 ANNEX C Page 13 of 15

ANNEX B LS to SMG on the use of AT commands from SIM toolkitapplications

ETSI SMG9 Tdoc SMG9 98p37322 - 25 September, 1998Saint Cyr Sur Mer, France

Liaison Statement

From: SMG9

To: SMG

Subject: The use of AT commands by SIM toolkit applications

This liaison statement accompanies CR 11.14 A051r1 (in Tdoc SMG 98-0669) which providesa capability within the SIM Application Toolkit (SAT) to manage AT Commands for controllingthe ME. Typical applications are for diagnostics, customer care, and control of unattendedterminals.

The capabilities defined in the CR to be added to the SIM Application Toolkit allow:i) the SIM to instruct the ME to perform AT Commands;ii) the ME response to the AT command to be passed to the SIM.

ME actions caused by the AT commands are not defined within this CR.

The AT commands would be issued either from an application resident in the SIM, or onreceipt of a data-download.

AT commands exist with:i) ‘standard’ parameters as typically given in TS GSM 07.07;ii) proprietary parameters specific to individual terminals.

SMG9 agreed that the CR was technically sound. However, there was considerablediscussion related to the principal of introducing this capability, and for this reason unanimousapproval was not given, with the majority abstaining.

The principal objection was that currently all SAT capabilities have fully defined actions withinthe ME including interactions across the radio interface and MMI. AT commands would allowthe possibility for ME and network operator specific actions to be introduced. One such actioncould be the setting up of a call without the user’s knowledge or confirmation.

This leads to two concerns which SMG9 asks to be noted:

i) that SAT would now be promoting the opportunity for non-standardised ME/servicebehaviour to be introduced, placing a greater responsibility on the application owner for theintegrity of the application and service;

ii) that the concept of SAT classes which fully define an ME’s SAT behaviour is notfully applicable to the AT command capability, as the class indication would not take accountof individual AT parameters.

The AT capability is defined as a stand-alone feature. Therefore, it is not dependent on otherSAT capabilities except the basic protocols, and its provision is an ME manufacturer’sdecision.

SMG9 Status report to SMG #27 ANNEX C Page 14 of 15

ANNEX C LS to SMG on the UICC in early UMTS systems

ETSI STC SMG9 Tdoc SMG9 (98) 383Saint-Cyr-Sur-Mer, FranceSeptember, 1998

Liaison Statement

To: SMG

CC: ECTEL, MoU SERG, MoU SCAG

Source: SMG9

Position Paper on the UICC for early UMTS systems

SMG9 have been looking at the requirements for the UMTS (Third Generation) USIM, notingparticularly, the requirement that UMTS evolves from GSM. As part of the evolutionaryapproach from GSM to Third generation systems, it is a requirement that 3G terminals supportexisting (Phase 2) SIMs (at three volts, but not five volt SIMs), but it is not a requirement thatGSM terminals support 3G USIMs. It is the strong opinion of SMG9 that the UICC (UMTSIntegrated Circuit Card) is a mandatory element of Third Generation systems. This position isshared by SMG10.

It is recognised that the existing physical interface should remain unchanged (toaccommodate the need for interworking with GSM), however, that there may be the need toenhance the interface, both in terms of protocol (for example, employing the T=1 protocol),and speeding up the bit transmission rate across the interface.

It is recognised that the existing two physical sizes may prove to be limiting to mobileequipment (ME) designs for 3G mobiles, so consideration is being given to a third physicalsize of SIM, e.g. a cut down version of existing "Plug-in" SIM.

The other important feature of the SIM is the SIM Application Toolkit; this is a powerful tool foroperators, and can be easily exploited and enhanced for 3G operations, especially in the areaof Virtual Home Environment. Allied to this is the security for the Toolkit, where end-to-endmessaging between the Application area in the SIM and its partner entity in, or behind, thenetwork, can be secured, to prevent fraud or interception. Enhancements exploiting newerbearer services will be included for the Toolkit.

The next generation SIM will be a multi-application card, including support for applicationloading; SMG fully expect this work to be completed and approved in June 1999.

It is the opinion of SMG9 that the existing SIM technology and functionality is an ideal baselineplatform for early third generation systems; it is recognised that there will of necessity bealterations and additions to the file structure in the existing SIM to accommodate UMTSfunctionality, but this is believed to be easily undertaken.

SMG9 Status report to SMG #27 ANNEX D Page 15 of 15

ANNEX D Terms of Reference of SMG9

ETSI SMG9 Tdoc SMG9 98p385Saint Cyr-sur-Mer, France, 25. September 1998

SUB TECHNICAL COMMITTEE SMG9

IC CARD ASPECTS

1 Responsibilities

The main responsibilities of SMG9 are:

• development and maintenance of the specifications for the Integrated Circuit Card/Mobile Equipmentinterface of those telecommunication systems under the responsibility of ETSI;

• study of generic IC card issues and development and maintenance of standards for generaltelecommunication purposes;

• maintenance of the EN 726 series of standards in coordination with the ETSI project PTS.

2 Tasks

The main tasks of SMG9 are:

• maintenance of the GSM standards relating to the SIM and SIM/ME interface;

• study and specification of enhancements to the GSM platform to allow the addition of innovative featuresand functions for GSM phase 2+;

• development of a UMTS IC card;

• study and specification of generic issues for IC cards for Telecommunications, these include but are notrestricted to:

- interface enhancements such as new commands,

- generic application download and load mechanisms,

- electrical parameters and protocol issues;

• specifications for the use of low voltage technology for telecommunications cards;

• specifications of the GSM application as part of a multi-application card and the transition thereto;

• elaboration and maintenance of IC card related test specifications, including collaboration with ETSISMG7 for the SIM/ME interface aspects in GSM 11.10.

• 3 Organisation

The committee meets at least three times a year in Plenary. To facilitate its smooth functioning the committeeelects in Plenary two Vice-Chairmen.

Currently SMG9 has five Working Parties, the Chairperson of each is elected by the Plenary. The WorkingParties are:

- SIM Toolkit Security- UMTS- SIM API- Testing- Generic IC Card Issues

4 Liaisons

SMG9 has direct formal liaisons with other ETSI SMG committees, ETSI PTS and MoU SCAG. Someinformal liaison is handled by delegates attending international standardisation meetings and forums, inparticular the Java Card Forum.

ETSI TC SMG Tdoc SMG 700/98Meeting #27 Agenda item: 6.1112 – 16 October, 1998, Prague

Source: Chairman, SMG11

Status Report of SMG11 at SMG#27

Executive Summary

• This document provides an overview of the work of SMG11 in the period from SMG#26 (June,1998) to SMG#27.

• Since SMG#26, SMG11 has held one plenary meeting, one extraordinary plenary meeting (withagenda limited to AMR matters), and ad hoc group meetings on AMR, SQ and TFO matters.

• No Phase 1 CRs are presented. One Phase 2 or 2+ CRs is presented.

• The AMR Selection Phase has been completed on schedule. Substantial performanceimprovements are demonstrated. All 5 candidates shortlisted from the Qualification Phasesubmitted their codec for selection tests. Following the completion of the subjective tests, onecandidate decided to withdraw their candidate. All remaining 4 candidates provided requireddeliverables and 2 of them passed the Selection Rules. SMG11 recommends the adoption of theENS1 codec proposed by Ericsson, Nokia and Siemens, subject to two conditions being met.SMG11 believes this codec meets the overall objectives of the AMR codec project.

• TFO Stage 3 document (v1.6.0) is presented for information.

Page 2Status report of SMG11 at SMG#27

Table of Contents

1. SMG11 meetings................................................................................................................................ 31.1. Recent meetings ................................................................................................................. 31.2. Future Meetings Calendar................................................................................................... 3

2. Phase 1, Phase 2, Release ‘96, Release ‘97 specifications............................................................... 3

3. Phase 2+............................................................................................................................................. 33.1. Tandem Free Operation...................................................................................................... 33.2. AMR - Narrowband.............................................................................................................. 3

3.2.1. Selection Phase.............................................................................................. 43.3. Noise suppression for AMR ................................................................................................ 53.4. AMR - Wideband................................................................................................................. 53.5. EP TIPHON......................................................................................................................... 63.6. Handset and Headset Test Methods................................................................................... 6

4. Decisions and guidance from SMG.................................................................................................... 6

5. UMTS.................................................................................................................................................. 6

6. List of documents submitted to SMG#27............................................................................................ 6

Annex 1......................................................................................................................................................... 7

Page 3Status Report of SMG11 at SMG#27

Status Report of SMG11 at SMG#27

1. SMG11 meetings

1.1. Recent meetings

Since SMG#26, the following meetings on SMG11 matters have taken place:

Plenary:SMG11#6bis 28th-30th July, 1998 Tampere; hosted by NokiaSMG11#7 28th Sept – 2nd Oct, 1998 Laurent-Du-Var; hosted by Texas Instruments

Ad hoc groups:TFO#15 15th - 16th July, 1998 Nueremberg; hosted by EricssonTFO#16 2th - 3th Sept, 1998 Sophia Antipolis; hosted by ETSI

1.2. Future Meetings Calendar

The following meetings have been scheduled:

Plenary:SMG11#8 23rd –27th November, 1998 Host requiredSMG11#9 11th –15th January, 1999 Host required

Ad hoc groups:SMG11 AMR#12 26th –28th October, 1998 (planned) Host requiredSMG11 TFO#17 16th –17th November,1998 Israel; hosted by ECI

2. Phase 1, Phase 2, Release ‘96, Release ‘97 specifications

No Phase 1 CRs are presented. One Phase 2 or 2+ CRs is presented. This is contained in Tdoc 704/98.

3. Phase 2+

3.1. Tandem Free Operation

Stage 3 document v.1.6.0 will be presented for information to SMG#27. This is contained in Tdoc 703/98.The complete TFO specification including Test Vectors and Typical Scenarios will be presented later forSMG approval. The SDL form of the TFO standard (Annex C) is available in electronic copy and can beprovided by ETSI on request.

Results from subjective testing of TFO signalling at Tellabs show that the in-band TFO protocol does notcause appreciable degradation of the speech channel.

3.2. AMR - Narrowband

The AMR Selection Phase has been successfully completed in schedule. The results andrecommendations are presented in Tdoc SMG 562/98.

The target is to complete the specifications in time for the approval of the GSM release 98 duringSMG#28. The AMR specifications are planned to be prepared as described in "Project schedule and openissues for AMR "(GSM 10.70, Version 0.0.1) contained in Tdoc 701/98.

The selection of the AMR codec will be followed by Verification Phase for the chosen codec where e.g.,the complexity and transmission delay are verified. This phase will be completed by SMG#28.Development of Characterisation Phase test plan has started for the characterisation of the adopted AMRcodec.


3.2.1. Selection Phase

SMG11 has carried out a formal selection process of a short-list of 5 codec candidates proposed for theAMR standard. The candidates were short-listed from the AMR Qualification Phase concluded in June1998. The selection results were analysed during SMG11#7 (September 28 – October 2, 1998).

The short-listed codec proponents are: Alcatel/BT/Cellnet/FranceTelecom/Nortel/Rockwell (ABCFNR),Ericsson/Nokia/Siemens 1 (ENS1), Ericsson/Nokia/Siemens 2 (ENS2), Lucent and NEC.

The following main activities have been carried out:

• finalisation of the codec proposals (by the proponents)

• finalisation of mandatory reference documents (Selection Rules and Test Plans)

• contracts for processing and listening laboratories and for complexity assessment

• processing of test material (by candidates and a common processing laboratory)

• subjective testing (by listening laboratories)

• complexity assessment (University of Aachen)

• presentation and analysis of results

Following the completion of the subjective tests, Lucent decided to withdraw their candidate.

During SMG11#7, analysis was carried out of the deliverables (technical descriptions of the codecs,compliance to design constraints) and the listening test results (comparison to performance requirements,comparison against selection rules).

The codec proposals and results were debated and recommendations concluded on the overall preferredcodec. As required by the Selection Phase rules, the four remaining codec proponents provided the fullset of required selection deliverables on time. The mandatory design constraints were judged to havebeen met by all candidates.

Candidate results

As already demonstrated during the Qualification Phase, the listening test results show generally verygood performance for the codec proposals and clear performance improvements for AMR over theexisting GSM codecs where they were required. Major benefits of AMR were again demonstratedespecially

• in FR mode, an increase of C/I tolerance of 4 dB to 6 dB

• in HR mode, at low error conditions – quality equal to G.728 or G.729 ("wireline")

• in FR dynamic conditions - over 1 delta MOS compared to GSM EFR.

The dynamic tests were designed to evaluate AMR performance in realistic radio conditions (withadaptation turned on) and they show a clear improvement in the FR channel over GSM EFR validating theAMR concept.

All the codecs failed to a greater or lesser extent in HR mode under background noise and at low C/I andthese account for the majority of the failures. This is the most challenging area of the overall requirementspecification, which is considered to be beyond the capability of today’s state of the art technology. This isexemplified by the fact that all the codecs fail in the same region.

Two out of the 4 remaining codecs complied with all rules for speech quality performance: ABCFNR(Alcatel/BT/Cellnet/FranceTelecom/Nortel/Rockwell and ENS1 (EricssonNokia/Siemens).


Based on the analysis of the speech quality results alone, there was consensus in SMG11 that ENS1codec provided the best overall results, showing consistently better performance in a number of areas.SMG11 believes this codec meets the overall objectives of the AMR codec project.

ENS1 was followed by ABCFNR. This codec was better than or equal to ENS1 in some specific regionsnotably the conditions of combined background noise and C/I from 10 dB to 4 dB.

The results of AMR Selection Phase are contained in Tdoc 562/98. A minority of organisations requestedto extend the conclusions section of Tdoc 562/98 to contain a note on the adoption of the ABCFNR codecin case the two conditions for the ENS1 are not met, but this was not agreed upon.

Recommendations

Taking all the factors into account including the analysis of the subjective tests, the descriptions of thesource and channel codec algorithms, the link adaptation mechanisms and the codec complexity, SMG11agreed to recommend the ENS1 codec proposed by Ericsson, Nokia and Siemens but subject to thefollowing two conditions being satisfied.

1) Implementability:

Condition. That a “reasonable” proportion of GSM BSS manufacturers indicate that the ENS1codec can be implemented on their existing, HR compatible BTS hardware.

Measure. At its last meeting (September 28th to October 2nd), SMG11 requested all manufacturersto supply this information in time for SMG#27. SMG should be the judge of whether the conditionhas been met. It is recognised that in the time available and for commercial reasons,manufacturers may only be able to give an informal indication of their BTS capability and it isunreasonable to expect them cast iron guarantees at this stage. To ensure even handiness,manufacturers were requested to provide similar information on the second most preferred codec(ABCFNR). It is understood that ENS and ABCFNR will provide sufficient information to allow thisto be done.

2) Commitment to complete normalisation of AMR:

Condition. As the principal source of knowledge of the ENS1 codec and its control, thecompletion of all specifications relating to the codec will depend on the contributions from the ENSconsortium. A commitment is required from the consortium that they will provide resources toensure that to their best endeavours, the specifications are completed in time for SMG#28 (seeSection 7). This does not imply however, that they have sole responsibility for these tasks.

Measure. Receipt by SMG#27 of a statement of commitment.

The second most preferred candidate was that from the ABCFNR consortium. The overall quality of thiscodec was less good than that of the ENS1 codec. However, in the event that major problems areencountered in meeting the conditions outline above for ENS1, the ABCFNR codec can be considered asa viable secondary option.

3.3. Noise suppression for AMR

Scope of work and performance requirements were discussed in subgroup during SMG11#7. SMG11-level discussion was postponed until SMG11#8 (late November) due to limited time available atSMG11#7. A number of issues need to be addressed such as scope of the specification, requirements forcomplexity and delay, how to test performance improvements and to understand the range of conditionswhere benefits will be achieved. The work will continue by correspondence until SMG11#8.

3.4. AMR - Wideband

Feasibility study for codec performance (with a single time slot) is on-going, but progress is slow due tothe intensive AMR-narrowband work. No inputs have been received since SMG#26. Several organisationshave indicated working on this and results are now expected by the end of this year.


3.5. EP TIPHON

EP TIPHON have expressed strong interest in the possibility of selecting GSM codecs as “standard” ordefault codecs for “Voice over IP” telephony. SMG11 work (new codecs, TFO etc) was presented onrequest to EP TIPHON (Sept 98 meeting).

3.6. Handset and Headset Test Methods

This work item was decided to be dropped at SMG11#7 due to lack of contributions. However, work wasrequested for UMTS, and work item with similar scope for UMTS is planned to be opened at next SMG11meeting.

4. Decisions and guidance from SMG

Narrowband AMR

• SMG11 recommends the adoption of the ENS1 codec subject to two conditions being met (seeSection 3.2.1). SMG is invited to endorse this recommendation (Tdoc SMG 562/98).

5. UMTS

ARIB are currently evaluating speech codecs in order to select one as a default speech codec for W-CDMA. ARIB will be evaluating a short list of six speech codecs, these being G.729, GSM EFR, GSMAMR, MPEG4 (narrowband), IS.641, EVRC (IS127) and it is planned to run subjective tests on thesecodecs to be completed by February 1999. A delegate from NTT-DoCoMo was present at theSMG11#6bis and SMG11#7 meetings.

Scope of the co-operation with ARIB was defined at SMG11#7 (as requested at SMG#26). SMG11proposes to send a liaison statement to ARIB on “Collaboration on the evaluation of AMR for UMTS”. Theproposed liaison statement is contained in Annex 1 (and in Tdoc 705/98). It contains a proposal for theTerms of Reference for the collaboration between ARIB and SMG11.

Decisions at SMG#27

• Agree to send to ARIB the proposed LS on “Collaboration on the evaluation of AMR for UMTS”.

6. List of documents submitted to SMG#27

SMG#27Tdoc

Title

700/98 Status Report of SMG11 at SMG#27701/98 Digital cellular telecommunications system (Phase 2+); GSM Adaptive Multi-

Rate Speech Codec (AMR) Project schedule and open issues for AMR (GSM10.70, Version 0.0.1)

562/98 Results of AMR Selection Phase703/98 Digital cellular telecommunications system (Phase 2+); Inband Tandem Free

Operation (TFO) of Speech Codecs; Service Description; Stage 3 (GSM 04.53Version 1.6.0)

704/98 CRs to GSM 03.50-A014/A015705/98 Proposed liaison statement to ARIB on “Collaboration on the evaluation of AMR

for UMTS”731/98 Presentation to SMG#27 of AMR Selection Phase results


Annex 1.

ETSI STC SMG11#7 Tdoc SMG11 246/98

St. Laurent du Var

September 28 – October 2, 1998

To: ARIB IMT-2000 Codec Work Group

Source: SMG11

cc: SMG, SMG2

Subject: Liaison statement to ARIB on “Collaboration on the evaluation of AMR forUMTS”

SMG11 welcomes the interest of ARIB in the work of SMG11 on the AMR speech codec and the invitationto collaborate on its evaluation for UMTS. ARIB is probably aware that SMG has decided that a defaultspeech codec should be defined for UMTS. SMG11 is actively considering the relevant issues and wouldbe pleased to share their views with ARIB. A high level collaboration agreement already exists betweenARIB and SMG, and SMG has agreed that this collaboration can be extended to the codec workinggroups to evaluate the suitability of the AMR codec for UMTS.

SMG11 notes that ARIB will be evaluating a short list of six speech codecs, these being

G.729, GSM EFR, GSM AMR, MPEG4 (narrowband), IS.641, EVRC (IS127)

and that it is planned to run subjective tests on these codecs to be completed by February 1999. Thesewill be followed by codec performance and system analysis taking into account both speech quality andother aspects such as capacity.

Against this background, SMG11 proposes the following Terms of Reference for the collaborationbetween ARIB and SMG11.

1) Evaluation of the performance of the AMR speech codec

2) Operation and control of the codec

3) Design and implementation aspects of the codec

4) Transmission over UTRAN including VAD/DTX

5) Support of the subjective test evaluation by ARIB

6) Delegates from SMG11 and ARIB may attend each other’s meetings

SMG11 would welcome the view of ARIB on the suitability of these TORs.

ETSI SMG#27 Tdoc SMG 0717/98 Praha, 12 to 16 October 1998Agenda Item: 6.3 and 7.3

Source: SMG3 management teamDate: October 1998

Status report of SMG3 to SMG#27

GLOBAL SYSTEM FOR MOBILE COMMUNICATIONS

R

Abstract:

This document gives an overview of the status of the work within SMG3 for the period between June 1998(SMG#26 meeting) and October 1998 (SMG#27 meeting).

Page 2Status report of SMG3 to SMG#27 October 1998

Contents of SMG3 status report to SMG#27

Abstract:........................................................................................................................................................ 1

1 Recent activities.................................................................................................................................. 31.1 Plenary meetings................................................................................................................. 31.2 Working Party meetings, Ad-hoc group meetings, Joint meetings ..................................... 31.3 CRs, LSs and specifications from SMG3 to SMG#27......................................................... 3

1.3.1 CRs related to Phase 2................................................................................... 31.3.2 CRs related to Release 96 and Release 97 ................................................... 31.3.3 Specification for information ........................................................................... 61.3.4 Specification for approval ............................................................................... 61.3.5 Liaison statements.......................................................................................... 61.3.6 Special issues to be highlighted to SMG#27 .................................................. 6

2 Status of the technical specifications.................................................................................................. 72.1 General................................................................................................................................ 72.2 Radio interface signalling & GPRS (SMG3-WPA) .............................................................. 8

2.2.1 Phase 2........................................................................................................... 82.2.2 Release 96 and Release 97 ........................................................................... 82.2.3 Release 98...................................................................................................... 8

2.3 Supplementary services part (SMG3-WPB) ....................................................................... 82.3.1 Phase 2........................................................................................................... 82.3.2 Release 96, Release 97 and next................................................................... 8

2.4 Network part (SMG3-WPC) .............................................................................................. 102.4.1 Phase 2......................................................................................................... 102.4.2 Release 96, Release 97 and next................................................................. 10

2.5 UMTS matters ................................................................................................................... 12

3 Future work....................................................................................................................................... 123.1 General.............................................................................................................................. 123.2 Status in SMG3 on Work Items......................................................................................... 133.3 SMG3 meeting schedule after SMG3 #3/98 in Bonn ........................................................ 14

Annex A: LS from SPS3 to SMG3 on CAMEL Phase 3 (to SMG#27 for information) ................................ 15


1 Recent activities

1.1 Plenary meetings

One plenary SMG3 session has been held in the period (between SMG#26 and SMG#27):

22 to 24 September 1998 SMG3 plenary #3/98; Bonn, hosted by T-Mobil

1.2 Working Party meetings, Ad-hoc group meetings, Joint meetings

Several SMG3 working party and ad-hoc sessions have been held in the period (between SMG#26 andSMG#27):

25 to 28 August 1998 SMG3-WPA: Oulu, hosted by the Finnish ETSI members

21 to 22 July 1998 joint SMG3-WPB/SMG3-WPC meeting on CCBS; Stuttgart; hosted by Alcatel10 to 14 August 1998 SMG3-WPB; Stuttgart hosted by Alcatel

25 June 1998 PE resolution meeting with SPS3 (INAP CS-1); Stockholm; hosted by Telia20 to 24 July 1998 SMG3-WPC; Stuttgart; hosted by Alcatel7 to 11 September 1998 SMG3-WPC; Göteborg; hosted by Ericsson1.3 CRs, LSs and specifications from SMG3 to SMG#27

SMG3 "logic" on strategic and non-strategic classification of CRs:

Phase 2: all CRs are considered to be strategic ;Release 96: all CRs are considered to be strategic ;Release 97: only CRs with category D "editorial" are considered to be non-strategic;

all other CRs are considered to be strategic ;Release 98: all CRs are considered to be non-strategic.

If any other group is involved then the CR is considered to be strategic .

The following list with CRs is sorted per GSM Work Item:

1.3.1 CRs related to Phase 2

Work item: Technical Enhancements/Improvements (TEI)

TdocSMG3

TdocSMG#27

98p199 CR 04.08-A355 (PHASE 2-F) on Clarification of CM3 and ES IND bit handling in classmark 1 and 2 98-0715

Note: This CR was agreed in SMG3, corresponding CRs for Release 96 and Release 97were already approved by SMG#26

1.3.2 CRs related to Release 96 and Release 97

Work item: Voice Broadcast Service (VBS)

TdocSMG3

TdocSMG#27

98p202 CR 04.69-A001r2 (R96-F) on GSM 04.69 Corrections. 98-067898p202 CR 04.69-A002 (R96-F) on Get Status Procedure 98-067898p202 CR 04.69-A003r2 (R96-F) on Set Status Procedure 98-0678

Note: Release 96 only; no modifications to GSM 04.69 for Release 97..


Work item: Voice Group Call Service (VGCS)

98p202 CR 04.68-A002r2 (R96-F) on GSM 04.68 Corrections. 98-067998p202 CR 04.68-A003 (R96-F) on Get Status Procedure 98-067998p202 CR 04.68-A004r2 (R96-F) on Set Status Procedure 98-0679

Note: Release 96 only; no modifications to GSM 04.68 for Release 97.

Work item: CAMEL Phase 1

98p206 CR 03.32-A002r1 (R96-F) on Error correction in GSM 03.32 for value of uncertainty 98-0723

98p206 CR 03.78-A033 (R96-F) on Corrections to AnyTimeInterrogation 98-0723

98p207 CR 09.02-A137 (R96-F) on Extending the applicability of GMSC Address in ProvideRoamingNumber 98-072398p186 CR 09.02-A148 (R96-F) on Clarification of limit on length of O-CSI in MAP_RESUME_CALL-HANDLING 98-0723

Work item: CAMEL Phase 2

TdocSMG3

TdocSMG#27

98p186 CR 03.16-A016r1 (R97-F) on CAMEL capability handling 98-0724

98p186 CR 03.78-A025r2 (R97-F) on CAMEL Phase 2 stage 2 98-072498p206 CR 03.78-A029r1 (R97-F) on Corrections to AnyTimeInterrogation 98-072498p206 CR 03.78-A034r2 (R97-F) on Interworking CAMEL with general Bearer Service 98-072498p186 CR 03.78-A037r1 (R97-C) on Removal of O_Not_Reachable and T_Not_Reachable detection points 98-072498p191 CR 03.78-A043 (R97-C) on GSM Forwarding Pending Indication in IDP Operation 98-0724

98p207 CR 09.02-A138 (R97-F) on Extending the applicability of GMSC Address in ProvideRoamingNumber 98-072498p186 CR 09.02-A149 (R97-F) on Clarification of limit on length of O-CSI in MAP_RESUME_CALL-HANDLING 98-072498p186 CR 09.02-A152r1 (R97-C) on Support of CAMEL Phase 2 98-0724

98p206 CR 09.78-A031r2 (R97-F) on Corrections on GSM 09.78 98-072498p186 CR 09.78-A033r1 (R97-F) on Support of CAMEL Phase 2 98-0724

Work item: CAMEL Phase 2/CCBS

98p208 CR 03.18-A022r1 (R97-F) on Corrections and alignments for CCBS & CAMEL Phase 2 98-0722

Work item: CCBS

98p182 CR 03.93-A005r1 (R97-D) on Editorial cleanup on figure numbering 98-072098p182 CR 03.93-A006r1 (R97-F) on Correction of VMSC model 98-072098p182 CR 03.93-A007r1 (R97-F) on Correction of HLR functionality to support MAP

(linked with CR 09.02-A147r1)98-0720

98p182 CR 03.93-A008r1 (R97-F) on Correction of CCBS_Coordinator_HLR 98-0720

98p232 CR 04.08-A365 (R97-F) on Change of IEI for the allowed action IE in the DISCONNECT message 98-0716

98p188 CR 03.18-A029 (R97-F) on Correction of handling for failure case of CCBS OG call handling 98-0721

98p208 CR 09.02-A136 (R97-F) on Correction to status reporting procedure 98-072198p208 CR 09.02-A147r1 (R97-F) on Correction to the status reporting procedure in the VLR

(linked with CR 03.93-A007r1)98-0721

98p188 CR 09.02-A151 (R97-F) on Removal of CCBS-feature from SS-Data 98-072198p188 CR 09.02-A158r1 (R97-F) on Restricting the use of extension containers in RegisterCCEntry and Erase

CCEntry user errors98-0721


Work item: GPRS

TdocSMG3

TdocSMG#27

98p204 CR 04.07-A019 (R97-F) on SNSM Primitives 98-0677

98p198 CR 04.08-A329r1 (R97-F) on Deletion of the STANDBY timer 98-067798p198 CR 04.08-A333 (R97-F) on Radio priority level signalling for MO SMS 98-067798p198 CR 04.08-A335r3 (R97-F) on Classmark split 98-067798p198 CR 04.08-A337r1 (R97-F) on MS initiated detach procedure collision handling 98-067798p198 CR 04.08-A339r1 (R97-F) on Definition of IEI values for optional information elements 98-067798p198 CR 04.08-A343r1 (R97-F) on Various corrections to GSM 04.08 98-067798p198 CR 04.08-A345r1 (R97-F) on SAPI negotiation at AA PDP context activation 98-067798p198 CR 04.08-A347r1 (R97-F) on Clarification of the GMM cause code handling 98-067798p198 CR 04.08-A349r1 (R97-F) on Modification of PDP address IE coding 98-067798p198 CR 04.08-A351 (R97-F) on Clarifications in the negotiation of the READY Timer value 98-067798p198 CR 04.08-A363r1 (R97-F) on QoS correction 98-0677

98p200 CR 04.64-A031 (R97-F) on A bit usage clarification 98-067798p200 CR 04.64-A032r2 (R97-F) on XID negotiation improvements 98-067798p200 CR 04.64-A033 (R97-F) on Release Indication Cause 98-067798p200 CR 04.64-A034r2 (R97-F) on Clarifications and corrections 98-067798p200 CR 04.64-A035r1 (R97-F) on Various improvements 98-067798p200 CR 04.64-A036r1 (R97-F) on Layer3 initiated vs. LLC-initiated link (re-)establishment 98-0677

98p201 CR 04.65-A019 (R97-F) on Corrections and clarifications 98-067798p201 CR 04.65-A020 (R97-F) on Acknowledged LLC operation establishment and release procedure 98-067798p201 CR 04.65-A021r2 (R97-F) on XID negotiation 98-067798p201 CR 04.65-A022 (R97-F) on TCP/IP header compression and Data compression 98-067798p201 CR 04.65-A024 (R97-F) on Data transfer 98-067798p201 CR 04.65-A025r1 (R97-F) on Replacement of "Segment offset" with "Segment number" 98-0677

98p203 CR 09.18-A005 (R97-F) on Completion of the re-naming of BSSAP+-IDENTITY-REQUEST messageand MS identification procedure

98-0677

98p236 CR 09.18-A006r1 (R97-F) on Text clarification and "MS class" term changed in to "MS in class mode ofoperation"

98-0677

98p203 CR 09.18-A007 (R97-F) on BSSAP+-MS-UNREACHABLE Message type 98-0677

98p187 CR 03.08-A016r1 (R97-C) on Signalling and SMS radio priority level 98-0725

98p207 CR 03.18-A024 (R97-C) on Provide Subscriber Info for GPRS subscribers 98-0725

98p207 CR 09.02-A133r1 (R97-F) on Clarification on applicability of application contexts 98-072598p207 CR 09.02-A139r2 (R97-D) on Clarification when the SMS over GPRS functionality is not supported by

SMS-GMSC98-0725

98p187 CR 09.02-A153r1 (R97-F) on Correction in overload control tables for GPRS operations applicability 98-072598p187 CR 09.02-A154 (R97-F) on Usage of ShortMsgRelayPackage-v2 in GPRS 98-0725

98p207 CR 09.60-A022r1 (R97-F) on Modification of the coding of the Cause values of the Cause informationelements

98-0725

98p187 CR 09.60-A023r1 (R97-F) on Clarification of the use of the T-PDU Sequence Number values 98-072598p207 CR 09.60-A024r1 (R97-F) on Corrections and clarifications. 98-072598p207 CR 09.60-A025r1 (R97-F) on Charging ID to three GTP message types 98-072598p207 CR 09.60-A026 (R97-F) on Modification of the length of the protocol messages 98-072598p187 CR 09.60-A027r2 (R97-F) on Information Elements: Clarification of the handling of the unused bits, re-

definition of range98-0725

98p187 CR 09.60-A028r2 (R97-F) on Clarification of the handling of protocol errors in the Error handling section 98-072598p187 CR 09.60-A029 (R97-F) on Update of the Protocol Configuration Options IE 98-0725

Work item: Support of Optimal Routing (SOR)

98c414 CR 03.18-A025 (R96-C) on Optionality of support for OR of basic mobile-to-mobile calls 98-076898c414 CR 03.18-A026 (R97-C) on Optionality of support for OR of basic mobile-to-mobile calls 98-076898c414 CR 03.79-A006 (R96-C) on Optionality of support for OR of basic mobile-to-mobile calls 98-0768


Work item: Technical Enhancements/Improvements (TEI)

TdocSMG3

TdocSMG#27

98p199 CR 04.08-A357r1 (R97-D) on Editorial changes in section 9.1 due to wrong numbering of tables andfigures.

98-0698

98p199 CR 04.08-A359 (R97-D) on Editorial changes in section 9.2 due to wrong numbering of tables andfigures.

98-0698

98p199 CR 04.08-A367 (R97-D) on Editorial changes in section 9.3 and 10.5 due to wrong numbering of tablesand figures.

98-0698

98C405 CR 03.18-A023 (R96-F) on Corrections for successful case of TCH allocation 98-0726

98P189 CR 03.18-A027r1 (R97-F) on Suppression of alerting to originating MS in the case of early ACM 98-072698P189 CR 03.18-A028r1 (R96-F) on Suppression of alerting to originating MS in the case of early ACM 98-0726

98p209 CR 09.02-A129r1 (R97-A) on E.214 addressing of the HLR 98-0726

98p209 CR 09.02-A132r1 (R97-A) on Removal of redundant information from GSM 09.02 98-072698p209 CR 09.02-A145 (R96-F) on Removal of redundant information from GSM 09.02 98-0726

98P189 CR 09.02-A150r1 (R97-F) on ASN.1 correction 98-0726

1.3.3 Specification for information

GSM 04.72 (Release 98) Call Deflection stage 3; as version 1.0.0 Tdoc SMG 98-0718

1.3.4 Specification for approval

GSM 09.13 (Release 97) Signalling interworking between ISDN ASE and MAP protocols; as version 2.0.0Tdoc SMG 98-0719


The following liaison statement is attached to this SMG3 status report:

LS from SPS3 on SMG3 - SPS3 co-operation for the production of common CAMELPhase3 specifications (for information to SMG#27)

Annex A

1.3.6 Special issues to be highlighted to SMG#27

CAMEL Phase 3 : SPS3 proposed to SMG#26 to have one common set of specifications for CAMELPhase3 generated by SMG3/SPS3 in a joint activity. Over the last 3 months intensive discussion tookplace within SMG3 /WP-C and towards SPS3 on this proposal. In summary it is agreed to have intensivecooperation until end next year by means of joint ”CAMEL business meetings”. The proposal to have onlyone set of specifications was instead not achieved. There will be one CAMEL3 stage1 and one stage2specification produced by SMG3/WP-C but two stage3 specifications. SMG3 endorsed the principle tohave a ”minimum specification” only specifiying those parts of IN CS2 which will be used by CAMEL3whereas SPS3 favours the superset philosophy and additionally wants to use PICS to take out of servicethose parts of the standard which are not used by CAMEL3. Furthermore backward compatibility aspectswere seen as the other major point preventing from having one common stage3 specification only.The formal co-operation with SPS3 on the common development of the CAMEL Phase 3 standard istreated in annex A.

ASN.1 compiler : For the ASN.1 checking SMG3 is making use a compiler provided by Siemens.However, this compiler can not check all ASN.1 constructs used in 09.78. The same problem occurs inSPS3 with IN CS2. A new compiler seems to be found meanwhile, nevertheless ETSI-PEX offeredsupport to clarify this issue.

IST: the development of a non-CAMEL based solution for IST was requested by SMG10. Guidance onthis work is needed. The non CAMEL approach for this service will be very time consuming for SMG3.Furthermore there is no support in SMG3 for the development of a non CAMEL based solution for IST.Based on a cost/benefit comparison and due to the current workload situation in the respective SMG3working party SMG3 proposes to postpone the matter to a later release.


Hosts : The hosting situation is in general not satisfactory, SMG3 is in general lacking a lot of hosts. If noparties are willing to host SMG3 meetings then it can be foreseen that stage 3 material for the completionof Release 98 and Release 99 will not be available in due time.

SSN: On request of SMG12 the subsystem number issue is under analysis. SMG3 endorses entirely toallocate 3 SSNs from the national specific range for the MAP applications in SGSN, GGSN and gsmSCF(150, 149, 148). The principle to reserve an entire block of national specific SSNs (129-150) for futureapplications is not unanimously endorsed at the moment and a proposal from TTC to modify the CAPSSN is not completely analysed yet.

MNP SMG3 started work on mobile number portability. 3 specifications are envisages, one for IN-basedsolution call related, one for SRF-based/call related and one for SRF-based/non-call related.

2 Status of the technical specifications

2.1 General

The part of the Phase 2 (Release 95) technical specifications under the responsibility of SMG3 areconsidered as stable. However, one CR to Release 95 was agreed by SMG3 to align with the alreadyagreed Release 96 CR 04.08-A301r2 on Clarification of CM3 and ES IND bit handling in classmark 2and 1.

Active support:

SAME STORY AS TO SMG#21 and to SMG#22 and to SMG#23 and to SMG#24 and to SMG#25 andto SMG#26 : It should be noted that because of lack of rapporteurs and active contributors there is a riskthat SMG3 needs to propose to delete or postpone work items or parts of work items. This lack ofrapporteurs and/or active contributors was already mentioned to several SMG plenary meetings butwithout sufficient success. Especially in the supplementary service area work items can not beprogressed. The number of delegates visiting the meetings is stable now; unfortunately however there isstill not sufficient active participation.

SMG3 Management Team:

SMG3:Chairman Harald Dettner (Siemens);Vice Chairman currently: working party chairmen.

PT-SMG support (project managers for network aspects) :

Peter van der Arend SMG3 plenary, SMG3-WPB (stand-in SMG3-WPC);Fredrik Pettersson SMG3-WPADavid Williams SMG3-WPC

Working parties active within SMG3:

SMG3-WPA: radio-interface & GPRS chairman: Hannu Hietalahti (Nokia)SMG3-WPB: supplementary services chairman: Steffen Haberman (T-Mobil)SMG3-WPC: network aspects chairman: Ian Park (Vodafone)


2.2 Radio interface signalling & GPRS (SMG3-WPA)

2.2.1 Phase 2

Phase 2 is stable, however there is one CR to GSM 04.08 Phase 2. A correction to Classmark 3 wasfound to be needed. This was an action point given by SMG3 in Chester and was indicated to SMG#26.The corresponding CRs to Release 96 and Release 97 were already approved by SMG#26. This changeto Phase 2 is found to be necessary by SMG3, see also section 2.1.

2.2.2 Release 96 and Release 97

GPRS: This time "only" 27 CRs to GSM 04.07, GSM 04.08, GSM 04.64, GSM 04.65 and GSM 09.18 areforwarded, all with corrections to GPRS Release 97.

ASCI (VGCS and VBS) : As indicated to SMG#26 some corrections to GSM 04.68 and GSM 04.69 onVGCS and VBS are forwarded now for Release 96. No versions for Release 97 are needed because nomodifications happened in Release 97 to the access signalling for VBS/VGCS.

CCBS: One correction to GSM 04.08 is needed for the support of CCBS.

2.2.3 Release 98

Long Forwarded-To-Numbers/UUS: SMG1 is considering increasing of the maximum length of theforwarded-to number. This will require message segmentation on the radio path or a specific workaroundsolution. Other users might profit from a generic segmentation mechanism, e.g. UUS. SMG1 is asked todeliver information on potential other users of such a generic segmentation mechanism, i.e. on thenecessity of such a "tool" in general. If yes then SMG3 has to start a feasibility study on the segmentationmechanism.

2.3 Supplementary services part (SMG3-WPB)

2.3.1 Phase 2

Phase 2 is stable.

Old issue : There are still two outstanding CRs to GSM 09.12. These were agreed by SMG#22 but stillneed to be considered by SPS1. The outcome of the voting on GSM 09.12 was studied within SMG3 andthe result was also forwarded to SPS1. Also these comments still have to be put into GSM 09.12 (Phase2). It should be noted that this specification has not become a part of Release 96, i.e. there is no version5.0.0 available. A joint SMG3-WPB meeting with SPS1 on this matter is planned for 10 November 1998.In this joint meeting also GSM 09.13 will be checked officially by SPS1

2.3.2 Release 96, Release 97 and next

CCNRy/CCNRc: the reintroduction of CCNRy/CCNRc services was approved by SMG#26. SMG1confirmed meanwhile the view, shared also by MoU, that these two WI’s shall be deleted.The arguments from SMG3 to continue the work on CCNRy/CCNRc were:- It is estimated that approximately 90% of the work is already done for these services due to the

CCBS specifications- CCNR (CCNRy in GSM notation) is an ISDN service defined in ISUP version 3. Once the service is

introduced in fixed networks, GSM operators cannot offer service interworking, i.e. GSMsubscribers cannot place CCNR requests against fixed subscribers and cannot be the target ofCCNR requests from the fixed network.

SMG3 will follow the proposal from SMG1 to stop work on these two WI’s if this position is endorsed bySMG-plenary.

CCBS: Corrections are proposed to align GSM 03.93 with the MAP protocol. The interactions of CCBSwith CAMEL Phase 2 are also solved.


Call Deflection: The work on the stage 2 specification was further progressed and it is expected to sentGSM 03.72 for approval to SMG#28.

The stage 3 specification was further stabilised. CD can be introduced without further changes toGSM 04.08 by reusing current call clearing procedures for the invocation of the service. GSM 04.72 isforwarded to SMG#27 for information. A CR to GSM 04.80 will be finalised in time for Release 98.

UUS: Nokia took over responsibility for the stage 2 and stage 3 specifications of UUS. The main problemis the alignment of the specifications with GSM 03.18 procedures. Open items for SMG1 are recognised inthe interworking area, especially for CAMEL and SOR.

It is estimated that the service can be finalised in time for Release 98. However there is one outstandingissue on UUI for service one and the problem of segmentation.

MSP: A proposal for a way to introduce MSP based on CAMEL Phase 2 functions was presented byFrance Télécom. There are only minor changes to the GSM system necessary. A discussion took placeon how to handle service implementations based on CAMEL in SMG3. At present SMG3-WPB has noresources to work on the MSP in relation to the definition of "operator specific services". The FranceTélécom paper was considered as a proposal for internal consideration in interested companies.

At SMG1 a discussion was started on alternative implementations for MSP. Changes to the stage 1 wereproposed by Ericsson. Based on this an SMG1/SMG3 joint meeting was organised; however due tomissing support of SMG1 the meeting was cancelled later on. Ericsson presented first ideas on analternative implementation with major impact on mobility management and MS implementations. It isproposed to allow multiple SIMs in one ME. References to requirements on enhanced mobilitymanagement and SIM capabilities of UMTS were given. Ericsson volunteered to progress the work on thisproposal in order to ask SMG12 for further guidance.

Other companies are asked to give comments on the Ericsson proposal. Ericsson have indicated thattheir solution will be e-mailed around to SMG3, SMG3-WPB and SMG12.

The finalisation of MSP within Release 98 cannot be guaranteed. Major decisions are necessary on thegeneral concept of the introduction of MSP. For that the requirements of UMTS should be considered aswell.

The CAMEL based solution proposed by France Télécom in SMG3-WPB and the solution which will bedistributed by Ericsson need to be studied.

Follow me: There are two possibilities for the work on FM:

- to implement Follow Me as a supplementary service. For that, a security mechanism for preventingfraud is necessary. This needs to be approved by SMG10.

- it would be feasible to introduce a tool which allows operators to implement their own solution. ForFM an HLR-HLR interworking is necessary via a "tunnelling mechanism".

Siemens, being the rapporteur, was asked in SMG3 to start consideration of these options.

USSD enhancements: SMG1 have given major responsibility on the definition of service requirements forUSSD enhancements to SMG4-MExE. SMG3-WPB is waiting for input from SMG4 on the open issuesrecognised previously. An answer from SMG12 on routeing of USSD messages was received. It isproposed to use either service code based routing or GT based routing for MS initiated traffic. SMG4 isasked for further clarification. For network initiated traffic the reuse of SMS routing procedures isproposed.

CLI enhancements: The "Send Routeing Info" and "Provide MSRN" operations shall be used to transmitCLI information from the GMSC to the VMSC via the HLR. First drafts of the modifications required forGSM 03.18 and GSM 03.81 were presented in SMG3-WPB. An open item is the priority of the usage ofboth numbers at the VMSC. The introduction of name information together with the CLI is for further study.


GSM/PCS Harmonisation : Proposed changes to GSM 04.81 and GSM 04.90 were received from T1P1.The change request to GSM 04.81 on "introduction of redirecting BCD number and redirectingsubaddress" was postponed due to missing service requirements from SMG1.

An off-line e-mail discussion has taken place on the introduction of the "redirection number". It wasrecognised that these changes are more relevant to the call forwarding service. For privacy reasons a newsubscription option for call forwarding needs to be introduced. SMG1 and T1P1 are in charge to define thefinal requirements.

The proposed CR to GSM 04.90 was not endorsed since it would introduce protocol specific handling inthe application specific description of USSD.

Release 98 : In general it was estimated in SMG3-WPB that the majority of the work items allocated toSMG3-WPB can be finalised for Release 98. There is only one exception identified, which is MSP.General decisions are necessary in SMG1, SMG3 and SMG12. There are no Release 99 Work items inthe responsibility of SMG3-WPB so far.

Calling Name Presentation : The US-version of CNAP has been agreed by SMG#24. The work on theEURO-version can be continued; The stage 1 is neutral to the implementation but for stage 2 a newimplementation option may be needed. The UUS proposal for implementation is under investigation, someproblems/drawbacks are identified with this approach.

2.4 Network part (SMG3-WPC)

2.4.1 Phase 2

No CRs to Phase 2. Phase 2 is stable.

2.4.2 Release 96, Release 97 and next

CAMEL Phase 1: There are a very small number of changes for CAMEL Phase 1, even a year and a halfafter approval.

CAMEL Phase 2 : SMG3 continued to make corrections to the stage 2 and 3 specifications for CAMELPhase 2; the majority are straightforward corrections of errors discovered as implementers work on theirdevelopment of software, but a significant minority are changes made at the request of SPS3, to alignCAMEL with ETSI and global IN standards. According to John Donne, ”No CAMEL is an island, entire ofitself, …”. More corrections are expected.

CAMEL Phase 3 : The following statement was made by the SMG3-WPC chairman: "If CAMEL Phase 1 isa responsible adult and CAMEL Phase 2 is a maturing adolescent, CAMEL Phase 3 is definitely anembryo. However the pregnancy should be not too exhausting – we have signs of good co-operationbetween the three parents (all right, the CAMEL is an unusual animal, but not that unusual, so maybe Ishouldn’t push the metaphor too far!)".

SMG3-WPC had a joint discussions with SPS3 experts, including the SPS3 Chairman, Frans Haerens,during the SMG3-WPC meeting in Gothenburg, and agreed the framework for a co-operativedevelopment of the CAMEL Phase 3 stage 2 and 3 specifications. That framework is recorded in annex Fof GSM 10.78 (see annex A of this status report). SMG#26 instructed SMG3 to discuss the arrangementswith SPS3, and this annex records the result. The same framework was discussed by SPS3. It isexpected to start the joint activity with SPS3 during the next SMG3-WPC meeting in November 1998. Theproposal in Annex F was agreed by SMG3.

One stream of specifications will be produced. Stage 1 and stage 2 as for CAMEL Phase 1 and CAMELPhase 2; for stage 3 two specifications: one for GSM and one for IN CS3.1.

CCBS: The main outstanding item, the resolution of the interactions between CAMEL Phase 2 and CCBS,was completed. During the process of integrating the changes to GSM 03.18 for CAMEL Phase 2, CCBSand GPRS, it was discovered that several corrections and alignments were needed; CRs are forwarded.


Fraud Information Gathering System/Immediate Service Termination : A dialogue by liaisonstatements has taken place with SMG10 on FIGS and IST. CAMEL is seen as the primary tool on whichboth of these features will be based; however a specific request from SMG10 was received to define theprotocol enhancements to MAP to allow the implementation of IST without the need for CAMEL. It will bemade clear to SMG10 that the protocol enhancement for the development of a non CAMELimplementation solution for IST is only a small part of the work. Guidance on this work is requested fromSMG10. The decision of which entity activates termination is a matter for SMG10. If they do not have astrong opinion, it can be left to SMG3. It was found that there are also several architectural aspects.

There is a CAMEL solution and CAMEL is the main tool for collecting security related information; theremay be other operator means to collect this information. The non CAMEL approach for the service mightbe very time consuming for SMG3-WPC. There was no support in SMG3 for the development of a nonCAMEL based solution for IST. It has to be studied if this decision has any impact on the possibletermination of service for non CAMEL subscribers. There might also be impact on CCBS recalls andimpact on MNP.

GPRS: SMG3-WPC have continued the cleaning up work on GSM 09.02 and GSM 09.60 for GPRS.

Harmonisation with PCS1900 : The impact of PCS1900 harmonisation on SMG3-WPC has beenrelatively small; two proposals for CRs to GSM 09.02 have been reviewed. The comments have alreadybeen forwarded to T1P1.5. A CR to GSM 09.02 is proposed to deal with one of the harmonisation issues:the introduction of 3-digit MNCs.

Optimal Routeing : SMG #26 instructed SMG3 to study whether support of OR for mobile-to-mobile callscould be made an optional part of SOR. SMG3 have agreed the necessary CRs to GSM 03.18 (bothRelease 96 and Release 97) and GSM 03.79. It will be studied how CAMEL Phase 3 can be used toovercome the problems which have been identified with the existing (switch-based) definition of OR formobile-to-mobile calls. (These CRs were not presented in the SMG3 plenary but were approved after themeeting via e-mail).

SoLSA : A proposed change to GSM 09.02 to support SoLSA Phase 1 was discussed, but it wasconcluded that the stage 2 needs to be more stable before the stage 3 change can be agreed.

ASN.1 compiler : For the ASN.1 checking SMG3-WPC (and also SMG3-WPB) make use of Ulrich Wieheand "his" Siemens ASN.1 compiler. However, there seems no compiler available which can do thecomplete checking of the ASN.1 coding as used in GSM 09.78. The same problem occurs in SPS3. SPS3ETSI-PEX is also informed and promised to help. Meanwhile a new compiler is found but his capabilitiesare not tested yet.

SSN: ITU-T have agreed to change Q.713 so that SCCP SSNs not in the globally standardised range (i.e."national" SSNs) will be transmitted unchanged through international SCCP gateways. This will allow GSMapplications to use "national" SSNs for inter-PLMN signalling to support CAMEL & GPRS. The majority ofSMG3 delegations endorsed a proposal to reserve a block of "national" SSNs for GSM use. There wasunanimous support for the allocation of 3 specific "national" SSNs for MAP signalling for GPRS andCAMEL.

SMG12 asked SMG3 to study a request from TTC (Japan) to use a "national" SSN for CAP signalling,instead of the currently specified SSN, which clashes with the ITU-T allocation of the same value for MAPsignalling. This issue is under study by SMG3-WPC.

Mobile Number Portability : The solutions for supporting MNP were discussed. The support of non-callrelated functions (like SMS, CCBS) and call related functions for MNP was handled taking into accountGSM MAP and IN query based techniques. The MNP solutions are: a common solution for non-callrelated functions based on a Signalling Relay Function, an IN based solution for call related functionsusing an IN based query for obtaining call routing information and an SRF based solution for call relatedfunctions using a MAP query for obtaining call routing information.

Non-call related: SRF methodCall related: either IN or SRF method

It was decided to have three distinct parts for the standardisation of MNP:- one part for call related traffic SRF based


- one part for call related traffic IN based- one (common) part for non-call related traffic SRF based.

Libertel volunteered to take rapporteurship for the SRF based parts of the specifications and Siemensindicated that they will take rapporteurship for the IN based part of the specification.

UMTS aspects were treated for the first time in SMG3 on the latest plenary. For this Antun Samukic cameover from the south of France.

2.5 UMTS matters

Several UMTS specifications were presented in SMG3.

UMTS 30.00 SMG Work Programme for UMTS; version 3.5.0. SMG3 has to indicate itself for which areasit want to become involved. Four approved WI description are attached to UMTS 30.00. Two moreproposed WIs were available: "UMTS Core based on ATM Transport" and " Combined GSM and MobileIPMobility Handling in UMTS IP CN". SMG3 wants to get 2nd responsibility for both proposed WIs.

UMTS 30.01 UMTS baseline document version 3.3.0. This report will be studied by SMG3.

UMTS 22.00 UMTS Phase 1 version 1.0.0. This specification was forwarded to SMG3-WPB.

UMTS 23.01 General UMTS Architecture. Back ground information.

UMTS 23.10 UMTS Access Stratum - Services and Functions version 0.8.1 and a contribution on "AccessStratum and Protocol Stacks". It was indicated that this document was not fully agreed by SMG12,however is might be the basis for UMTS evolution of A- and Gb-Interface specifications for UMTSRelease 99.

UMTS 23.20 Evolution of the GSM platform towards UMTS version 0.7.0. Back ground information.

UMTS 23.30 Iu Principles version 0.2.0. Back ground information.

UMTS ZZ.XX Description of Iu Interface version 0.0.2.

Pre-paging in UMTS : This is a requirement by the Japanese TTC for the support of pre-paging in UMTSPhase 1. A broad range of features was identified already on the meeting which would benefit from such amechanism. SMG3 will study the proposal.

Gateway Location Register in the UMTS core network : SMG12 endorsed a proposal to includeappropriate text in UMTS 23.20. Contributions are required. NEC is planning a new WI description forSMG12. SMG1 and SMG3 were requested to continue analysis of such a new entity between HLR andVLR or between HLR and SGSN.

Interaction between MExE and GSM/UMTS Networks : Exchange of capabilities between the terminaland the network, in both direction, is needed to ensure a proper handling of interaction between thenetwork and the terminal services. That info has to be stored in the network. SMG3 will give guidance onthis storage. Another issue is the protocol to be used in the network for direct communication. This is anissue for the future discussion on CAMEL Phase 3.

Organisation of UMTS work in SMG3: An SMG3 ad-hoc meeting on UMTS is planned on 18 to 20November 1998 in Sophia Antipolis. The goal of this meeting is to get SMG3 more involved in UMTS.Issues for this meeting are the TTC proposals, MExE, work split, protocol (GSM 04.08/GSM 09.02)evolution towards UMTS.

3 Future work

3.1 General

SAME STORY as to SMG#22 and to SMG#23 and to SMG#24 and to SMG#25 and to SMG#26: Ingeneral there seems to be a reasonable support for most of the work items, however most of the work isdone by a limited number of participants, c.q. companies.


3.2 Status in SMG3 on Work Items

Release 98:

Call deflection : Work is progressing. stage 3 is forwarded for information. It is expected to forwardstage 2 and stage 3 to SMG#28 for approval.

Follow Me : If FM is based on CAMEL then there is probably no more work to be done by SMG3-WPB onFollow Me. A feasibility study is required on which CAMEL Phase can support Follow Me. An otheroption is that FM will be properly defined including security feature. The requirements from the UICon FM need further clarification. SMG3 assumes the WI to slip to Release 99.

FIGS and IST: It is assumed that FIGS/IST can be implemented based on CAMEL, however SMG3 wasrequested by SMG10 to develop a non-CAMEL based solution for IST. There are no resources inSMG3 to do so at present.

GPRS Release 98/Phase 2 : There is support to continue the work on GPRS.

Cordless Telephony System : Till now no major discussions in SMG3. The situation of CTS is not clear.

Forwarding of SMs : The status of this work item is not clear at all. There are no requirements fromSMG1. There is no active support in SMG3-WPB.

Mobile Number Portability : Under study in SMG12 and in parallel now in SMG3. SMG3 started workingon stage 2 and stage 3. An SMG3 ad-hoc meeting on MNP is scheduled. Active support can beexpected by several companies. The work can be finalised by SMG#28.

Harmonisation PCS 1900 -GSM : joint activity with T1P1. Several CRs have been discussed andcommented, some are approved. Nevertheless the total number of CRs is unknown. SMG3 isconfident to comple the work until SMG#28.

Interworking with satellites : Understudy in SMG1

Lawful Interception : Under study in SMG10.

Location services : SMG3 is invited to take part in the workshop scheduled for end October in SophiaAntipolis.

Multiple Subscriber Profile : Vodafone, France Télécom and Ericsson have indicated that they still havestrong interest in this service. Stage 1 was already agreed long time ago. Also drafts of stage 2 andstage 3 are available (prepared by Simon Richardson, Vodafone). For the moment there is limitedactive support in SMG3-WPB. If no rapporteur is found then this service cannot be finalized inRelease 98. Two proposals are under study (one from France Télécom and one, still to bedistributed, from Ericsson).

User-to-User Signalling : Nokia Mobile Phones has become rapporteur for stage 2 and stage 3 of UUS.Because of this active support UUS can be kept as a Release 98 service.

SoLSA : This service is in the hands of Nokia. A solution has to be chosen. SMG3 is for the moment notactively involved. A stable stage 2 is needed.

USSD enhancements : No progress was made in SMG3. Nokia is active on this work item and hasoffered to be the rapporteur. It can be kept as a Release 98 service. This WI is seen as subset ofthe MexE WI.

CLI enhancements : Work is going on. Nokia is active on this work item. It can be kept as a Release 98service.

CCNRy and CCNRc : These work items could be introduced by simple additional requirements to the"normal" CCBS service; especially for CCNRy. Most of the procedures introduced for CCBS couldbe reused. Reintroducing these work items will be checked. SMG3 will stop it's activities on thesetwo WIs as proposed by SMG1/MoU if this is confirmed by SMG.


Release 99:

CAMEL Phase 3 : SMG3-WPC has started the work on CAMEL Phase 3 for Release 99 in close co-operation with SPS3.

EDGE-NSS part : There is active support by Nokia. Issue for SMG3-WPA.

3.3 SMG3 meeting schedule after SMG3 #3/98 in Bonn

23 October 1998 SMG3 ad-hoc on MNP; Torino, hosted by CSELT

18 to 20 November 1998 SMG3 ad-hoc on UMTS; Sophia Antipolis, hosted by PT-SMG

27 to 29 January 1999 SMG3 plenary #1/99; NO HOST YET



26 to 29 October 1998 SMG3-WPA; Sophia Antipolis, hosted by PT-SMG25 to 26 January 1998 SMG3-WPA; Just before SMG3 plenary #1/99 NO HOST YET

26 to 30 October 1998 SMG3-WPB #4/98: Chicago, hosted by Lucent Technologies30 Nov to 4 Dec 1998 SMG3-WPB #5/98: Den Haag, hosted by KPN Telecom

(if no other more exotic host can be found)25 to 26 January 1999 SMG3-WPB #1/99: Just before SMG3 plenary #1/99 NO HOST YET17 to 21 May 1998 SMG3-WPB #2/99: NO HOST YET

10 November 1998 joint SPS1/SMG3-WPB on GSM 09.12 matters during SPS1 in Darmstadt

9 to 13 November 1998 SMG3-WPC; Hungerford, hosted by Vodafone11 to 15 January 1999 SMG3-WPC; NO HOST YET 13 and 14 January 1999 Joint SPS3/SMG3-WPC on CAMEL Phase 325 to 26 January 1999 SMG3-WPC; immediately preceding SMG3 plenary #1/99 NO HOST YET22 to 26 March 1999 SMG3-WPC; Issy-les-Moulineaux, hosted by France Télécom/CNET14 to 15 April 1999 Joint SPS3/SMG3-WPC on CAMEL Phase 3; Turkey, hosted by ???17 to 21 May 1999 SMG3-WPC; Edinburgh, hosted by Nortel 19 and 20 May 1999 Joint SPS3/SMG3-WPC on CAMEL Phase 323 to 24 June 1999 Joint SPS3/SMG3-WPC on CAMEL Phase 3; host unknown19 to 23 July 1999 SMG3-WPC; Sweden, hosted by Telia13 to 17 September 1999 SMG3-WPC; NO HOST YET 15 and 16 September Joint SPS3/SMG3-WPC on CAMEL Phase 320 to 21 October 1999 Joint SPS3/SMG3-WPC on CAMEL Phase 3; host unknown15 to 19 November 1999 SMG3-WPC; NO HOST YET

SPS3 meetings with joint SPS3/SMG3-WPC sessions on CAMEL Phase 3:12 to16 April 199921 to 25 June 199918 to 23 October 1999


Annex A: LS from SPS3 to SMG3 on CAMEL Phase 3 (to SMG#27 for information)

Source: ETSI SPS3To: SMG3/WPC , SMG3 (for action and response)Date/Venue: Ostend, Belgium, 14-18 September 1998.Contact:Frans Haerens Tel +32 3 240 9034

Fax +32 3 240 9961e-mail: [email protected]

Title: Response to Liaison Statement 'SMG3 - SPS3 co-operation for the production of commonCAMEL Phase3 specifications

SPS3 received the SMG3/WPC liaison statement on 'SMG3 - SPS3 co-operation for the production ofcommon CAMEL Phase3 specifications'. Some discussion has been done between SMG3 and SPS3 onthis co-operation during the Gothenburg SMG3/WPC meeting. A summary of those discussions can befound in GSM 10.78 V3.3.0, 9 September 1998 in Annex F

As requested by SMG3/WPC, SPS3 has also allocated three additional meetings next year, namely on:

• 12-16 April 1999

• 21-25 June 1999

• 18-23 October 1999

SPS3 ratifies this Annex F, however the following should be noted:

During the CAMEL business meetings in the weeks scheduled for SMG3 WPC meetings also two daysshould be allocated where the discussion can be concentrated on the IN discussions. This will allow SPS3delegates not to be mandated for the complete week.

The SPS 3 delegates would favour to have only 6 meetings during next year on IN Camel Phase 3. In thetable below three Joint SPS3/SMG3 meetings have been confirmed. It is up to SMG3/SPS3 managementto endorse the final dates and to fix the additional days.


SPS3 detailed meeting plan (The SMG meetings are for information as indicated in GSM 10.78subclause 5.1):

Date Meeting Scope29-30.10.98 Interim SPS3 Number portability, Multiple Point of Control9-13.11.98 SMG3 WPC Progress CAMEL phase 3 stage 2 & 3: Joint SPS3/SMG3 confirmed

on 10 and 11 November 19988-12.02.99 SMG#2811-15.1.99 SMG3 WPC Joint SPS3/SMG3 confirmed on 13 and 14 January 199925-29.1.99 Interim SPS3 Interim SPS3: No CAMEL phase 3, preparation ITU-T SG11/WP4

meeting25-29.1.99 SMG38-12.3..99 SMG1 Approve stage 1

SMG#2922-26.3.99 SMG3 WPC Joint SPS3/SMG3? Note 112-16.4.99 SPS3 SPS 3 confirmed: Note 117-21.5.99 SMG3 WPC Joint SPS3/SMG3 confirmed on 19 and 20 May 199931.5-4.6.99 SMG321-25.6.99 SPS3 SPS 3 confirmed: Note 1

SMG#305-9.7.99 SMG119-23.7.99 SMG3 WPC Joint SPS3/SMG3? Note 113-17.9.99 SMG3 WPC Joint SPS3/SMG3 confirmed on 15 and 16 September18-23.10.99 SPS3 SPS 3 confirmed: Note 127.9-1.10.99 SMG315-19.11.99 SMG3 WPC Joint SPS3/SMG3? Note 1

SMG3 WPC Finalise WPC outputs on CAMEL phase 3SMG#31 TC approval of CRs, finalisation of Workitem

Note 1: SPS3/SMG3 management must confirm the exact meeting days for Joint SPS3/SMG3 TaskForce.

Annex F of GSM 10.78 V3.3.0, 9 September 1998Basis of co-operation agreement between SMG3 and SPS3

This annex summarises the agreement reached at a joint meeting of representatives of SPS3 and SMG3WPC on 9 September 1998. It is subject to ratification by SPS3, SPS, SMG3 and SMG.

1 SMG3 WPC is responsible for delivering via SMG3 to SMG #31 (February 2000) for approval thestage 2 & 3 specifications (GSM 03.78 and GSM 09.78) for CAMEL Phase 3. These specificationswill be in the same format as the equivalent specifications for CAMEL Phase 1 & CAMEL Phase 2.

2. The work to develop GSM 03.78 and GSM 09.78 may be useful in the development of thespecifications for ETSI INAP CS-3.1; however SMG3 WPC is not able to allocate any resource forthe direct development of specifications for ETSI INAP CS-3.1.

3. SPS3's expertise is seen as being particularly valuable in:- importing into the CAMEL Phase 3 specifications the appropriate features of ETSI INAP CS-

2;- developing the enhancements to ETSI INAP CS-2, which are required for CAMEL Phase 3.

4. Meetings will be held to progress the work of drafting the CAMEL Phase 3 specifications as follows:4.1 During the weeks scheduled for SMG3 WPC meetings, as set out in subclause 5.1.

The CAMEL business meeting will be held in the same location as the SMG3 WPC meeting.Each CAMEL business meeting will start at 4 p.m. on the Monday, and finish at 6 p.m. on theThursday. There will be 6 such meetings in 1999.

4.2 During the weeks scheduled for SPS3 meetings; the dates for these meetings will beset by SPS3. The CAMEL business meeting will be held in the same location as the SPS3meeting. Each CAMEL business meeting will occupy 2 days, starting at 9 a.m. on the first dayand finishing at 6 p.m. on the second day. There will be 3 such meetings in 1999.

5 Invitations to each CAMEL business meeting will be sent to the SMG3 WPC membership list and tothe SPS3 membership list, by the host of the meeting with which the CAMEL business meeting iscollocated.

6 All CAMEL business meetings will have equal status, and will have a mandate to deliver outputs toSMG3 for approval.

Status Report SMG4 at SMG#27, 10/98 Praha, Page 1 of 1 , Filename:98-0775an14.doc

Extract of Tdoc SMG 98-0775

ETSI TC SMG # 27 Plenary MeetingPraha, Czech Republic12nd- 16th October 1998

Source: PT SMG

Agenda Item: 6.4

Extract of SMG4 Status Report

14 Liaison Statement from SMG4 to SMG

ETSI/SMG4 SMG4/ Tdoc 98P444

28th Sept - 2nd Oct 98

Sophia Antipolis

To SMG

cc WOME

From SMG4

Liaison Statement - maintenance of ETSI GSM specifications

SMG4 has discussed the problems concerning the maintenance of yearly releases of TechnicalSpecifications and feels that it is very time consuming and often unnecessary to maintain all previousreleases. SMG4 wishes to propose that only the current year and previous 2 year releases of TechnicalSpecifications should be maintained.

SMG4 believes a similar view has been expressed in SMG9

SMG4 notes that WOME are due to meet on 2nd October which coincides with the final day of SMG4’smeeting and felt that this LS should also be sent to them for that meeting as it is likely the subject ofdocument maintenance may arise.

List of all GSM Phase2, Phase 2+ and UMTS specifications (13 November 1998).

Page 1

GSM No Version Phase ETS/R/GTS Short Title Publication notes ETSI Reference AfterSMG #

01.00 5.2.0 Ph2+/UMTS Miscellaneous SMG spec Management Unpublished MI/SMG-00SPEC_QU

SMG#20

01.02 4.0.2 Phase 2 ETR 99 Description of GSM PLMN Pub Oct 1993 DTR/SMG-010102P SMG#801.02 5.0.0 Phase 2+ GTS 01.02 Description of GSM PLMN Pub Mar 1996 DGTS/SMG-010102Q SMG#1701.04 4.0.2 Phase 2 ETR 100 GSM Abbreviations Pub Nov 1994 DTR/SMG-010104P SMG#801.04 4.1.1 Phase 2 ETR 100 Ed2 GSM Abbreviations Pub Apr 1994 RTR/SMG-010104P SMG#1201.04 4.1.2 Phase 2 ETR 100 Ed3 GSM Abbreviations Pub Apr 1995 RTR/SMG-

010104PR2SMG#14

01.04 5.0.0 Phase 2+ GTS 01.04 GSM Abbreviations Pub Mar 1996 DGTS/SMG-010104Q SMG#1701.04 5.0.1 Phase 2+ ETR 350 GSM Abbreviations Pub Nov 1996 DTR/SMG-010104Q SMG#2001.31 5.0.0 Phase 2+ TR 101 105 Fraud Info Gat FIGS Stg 0 Pub Oct 1997 DTR/SMG-100131Q SMG#2301.31 7.0.0 R98 TR 101 105 Fraud Info Gat FIGS Stg 0 Unpublished RTR/SMG-100131Q7 SMG#2501.31 7.0.1 R98 TR 101 105 Fraud Info Gat FIGS Stg 0 Unpublished RTR/SMG-100131Q7 SMG#2601.33 5.0.1 Phase 2+ ETR 363 Lawful Intercep reqmts Unpublished DTR/SMG-101020Q SMG#2101.33 7.0.0 R98 TR 100 xxx Lawful Intercep reqmts Unpublished DTR/SMG-100133Q7 SMG#2501.48 5.0.0 Phase 2+ GTS 01.48 ISDN based DECT/GSM Pub July 1996 DGTS/SMG-010148Q SMG#1901.48 5.0.1 Phase 2+ GTS 01.48 ISDN based DECT/GSM Pub Nov 1996 RGTS/SMG-

010148QRSMG#20

01.50 1.0.0 Phase 2+ TR Radio Local Loop (RLL) Unpublished DTR/SMG-010150Q SMG#?01.51 1.0.0 Phase 2+ TR Dual Mode of Ops & Roam Unpublished DTR/SMG-010151Q SMG#?01.60 1.1.0 R97 TR 101 xxx GPRS requirements Draft DTR/SMG-010160Q6 SMG#2501.60 6.0.0 R97 TR 101 186 GPRS requirements Pub Apr 1998 DTR/SMG-010160Q6 SMG#2501.61 5.0.0 Phase 2+ TS 101 106 GPRS ciphering algo Pub Oct 1997 DTS/SMG-100161Q SMG#2301.61 6.0.0 R97 TS 101 106 GPRS ciphering algo Unpublished DTS/SMG-100161Q6 SMG#2501.61 6.0.1 R97 TS 101 106 GPRS ciphering algo Pub July 1998 DTS/SMG-100161Q6 SMG#2602.01 4.4.2 Phase 2 ETS 300 500 Telecomm Services Pub Sep 1994 DE/SMG-010201P SMG#1102.01 4.5.0 Phase 2 ETS 300 500

Am1Telecomm Services Pub Mar 1995 RE/SMG-010201P SMG#12

02.01 4.6.0 Phase 2 ETS 300 500 Ed2 Telecomm Services Pub Jan 1996 RE/SMG-010201PR2 SMG#1502.01 5.0.0 Phase 2+ GTS 02.01 Telecomm Services Pub Jan 1996 DGTS/SMG-010201Q SMG#1602.01 5.1.0 Phase 2+ GTS 02.01 Telecomm Services Pub Mar 1996 RGTS/SMG-

010201QRSMG#17

02.01 5.2.0 Phase 2+ GTS 02.01 Telecomm Services Pub Nov 1996 RGTS/SMG-010201QR1

SMG#20

02.01 5.3.0 Phase 2+ GTS 02.01 Telecomm Services Pub Jan 1998 RGTS/SMG-010201QR2

SMG#24

02.01 5.4.0 Phase 2+ GTS 02.01 Telecomm Services Pub July 1998 RGTS/SMG-010201QR3

SMG#26

02.02 4.2.2 Phase 2 ETS 300 501 Bearer Services in GSM Pub Sep 1994 DE/SMG-010202P SMG#802.02 5.0.0 Phase 2+ GTS 02.02 Bearer Services in GSM Pub Jan 1996 DGTS/SMG-010202Q SMG#1602.02 5.1.0 Phase 2+ GTS 02.02 Bearer Services in GSM Pub May 1996 RGTS/SMG-

010202QRSMG#18

02.02 5.2.0 Phase 2+ ETS 300 904 Bearer Services in GSM UAP version DE/SMG-010202QR1 SMG#2002.02 5.2.1 Phase 2+ ETS 300 904 Bearer Services in GSM Pub Apr 1997 DE/SMG-010202QR1 SMG#2002.02 5.3.0 Phase 2+ ETS 300 904 Ed2 Bearer Services in GSM Unpublished RE/SMG-010202QR2 SMG#2202.02 5.3.1 Phase 2+ ETS 300 904 Ed2 Bearer Services in GSM OAP version RE/SMG-010202QR2 SMG#2202.02 5.3.2 Phase 2+ ETS 300 904 Ed2 Bearer Services in GSM Pub Dec 1997 RE/SMG-010202QR2 SMG#2202.03 4.3.1 Phase 2 ETS 300 502 Tele Services in GSM Pub Oct 1994 DE/SMG-010203P SMG#1102.03 5.0.0 Phase 2+ GTS 02.03 Tele Services in GSM Pub Mar 1996 DGTS/SMG-010203Q SMG#1702.03 5.1.0 Phase 2+ GTS 02.03 Tele Services in GSM Pub July 1996 RGTS/SMG-

010203QRSMG#19

02.03 5.1.1 Phase 2+ ETS 300 905 Tele Services in GSM UAP version DE/SMG-010203QR SMG#2002.03 5.1.2 Phase 2+ ETS 300 905 Tele Services in GSM Pub Apr 1997 DE/SMG-010203QR SMG#2002.03 5.2.0 Phase 2+ ETS 300 905 Ed2 Tele Services in GSM OAP version RE/SMG-010203QR1 SMG#2102.03 5.2.1 Phase 2+ ETS 300 905 Ed2 Tele Services in GSM Pub Aug 1997 RE/SMG-010203QR1 SMG#2102.03 5.3.0 Phase 2+ ETS 300 905 Ed3 Tele Services in GSM Unpublished RE/SMG-010203QR2 SMG#2202.03 5.3.1 Phase 2+ ETS 300 905 Ed3 Tele Services in GSM OAP version RE/SMG-010203QR2 SMG#2202.03 5.3.2 Phase 2+ ETS 300 905 Ed3 Tele Services in GSM Pub Jan 1998 RE/SMG-010203QR2 SMG#2202.04 4.7.1 Phase 2 ETS 300 503 Supplementary Services Pub Sep 1994 DE/SMG-010204P SMG#1002.04 4.8.0 Phase 2 ETS 300 503 Am1 Supplementary Services Pub Mar 1995 RE/SMG-010204P SMG#1202.04 4.9.0 Phase 2 ETS 300 503 Ed2 Supplementary Services Pub Jan 1996 RE/SMG-010204PR2 SMG#1502.04 4.9.1 Phase 2 ETS 300 503 Ed3 Supplementary Services Pub May 1996 RE/SMG-010204PR3 SMG#1602.04 5.0.0 Phase 2+ GTS 02.04 Supplementary Services Pub Jan 1996 DGTS/SMG-010204Q SMG#1602.04 5.1.0 Phase 2+ GTS 02.04 Supplementary Services Pub Mar 1996 RGTS/SMG-

010204QRSMG#17

02.04 5.2.0 Phase 2+ GTS 02.04 Supplementary Services Pub May 1996 RGTS/SMG-010204QR1

SMG#18

02.04 5.3.0 Phase 2+ GTS 02.04 Supplementary Services Pub July 1996 RGTS/SMG-010204QR2

SMG#19


Page 2


02.04 5.4.0 Phase 2+ ETS 300 918 Supplementary Services UAP version DE/SMG-010204QR3 SMG#2002.04 5.4.1 Phase 2+ ETS 300 918 Supplementary Services Pub Apr 1997 DE/SMG-010204QR3 SMG#2002.04 5.5.0 Phase 2+ ETS 300 918 Ed2 Supplementary Services OAP version RE/SMG-010204QR4 SMG#2102.04 5.5.1 Phase 2+ ETS 300 918 Ed2 Supplementary Services Pub Aug 1997 RE/SMG-010204QR4 SMG#2102.04 5.6.0 Phase 2+ ETS 300 918 Ed3 Supplementary Services Unpublished RE/SMG-010204QR5 SMG#2202.04 5.6.1 Phase 2+ ETS 300 918 Ed3 Supplementary Services OAP version RE/SMG-010204QR5 SMG#2202.04 5.6.2 Phase 2+ ETS 300 918 Ed3 Supplementary Services Pub Feb 1998 RE/SMG-010204QR5 SMG#2202.04 5.7.0 Phase 2+ ETS 300 918 Ed4 Supplementary Services Unpublished RE/SMG-010204QR6 SMG#2302.04 5.7.1 Phase 2+ ETS 300 918 Ed4 Supplementary Services OAP version RE/SMG-010204QR6 SMG#2302.04 6.0.0 R97 TS 100 918 Supplementary Services Unpublished DTS/SMG-010204Q6 SMG#2502.04 6.0.1 R97 TS 100 918 Supplementary Services Pub July 1998 DTS/SMG-010204Q6 SMG#2502.04 7.0.0 R98 TS 100 918 Supplementary Services Unpublished DTS/SMG-010204Q7 SMG#2502.06 4.2.2 Phase 2 ETS 300 504 Types of MS Pub Sep 1994 DE/SMG-010206P SMG#802.06 4.3.0 Phase 2 ETS 300 504 Ed2 Types of MS Pub Sep 1995 RE/SMG-010206P SMG#1402.06 4.4.0 Phase 2 ETS 300 504 Ed3 Types of MS Pub May 1996 RE/SMG-010206PR2 SMG#1602.06 4.5.0 Phase 2 ETS 300 504 Ed4 Types of MS Unpublished RE/SMG-010206PR3 SMG#2202.06 4.5.1 Phase 2 ETS 300 504 Ed4 Types of MS OAP version RE/SMG-010206PR3 SMG#2202.06 4.5.2 Phase 2 ETS 300 504 Ed4 Types of MS Pub Jan 1998 RE/SMG-010206PR3 SMG#2202.06 5.0.0 Phase 2/2+ ETS 300 919 Types of MS UAP version DE/SMG-010206Q SMG#2002.06 5.0.1 Phase 2/2+ ETS 300 919 Types of MS Pub Apr 1997 DE/SMG-010206Q SMG#2002.06 5.1.0 Phase 2+ ETS 300 919 Ed2 Types of MS OAP version RE/SMG-010206QR SMG#2102.06 5.1.1 Phase 2+ ETS 300 919 Ed2 Types of MS Pub Aug 1997 RE/SMG-010206QR SMG#2102.07 4.6.1 Phase 2 ETS 300 505 MS features Pub Oct 1994 DE/SMG-010207P SMG#1102.07 4.7.0 Phase 2 ETS 300 505 Ed2 MS features Pub Jan 1996 RE/SMG-010207P SMG#1502.07 4.8.0 Phase 2 ETS 300 505 Ed3 MS features Unpublished RE/SMG-010207PR1 SMG#2202.07 4.8.1 Phase 2 ETS 300 505 Ed3 MS features OAP version RE/SMG-010207PR1 SMG#2202.07 4.8.2 Phase 2 ETS 300 505 Ed3 MS features Pub Jan 1998 RE/SMG-010207PR1 SMG#2202.07 5.0.0 Phase 2+ GTS 02.07 MS features Pub Mar 1996 DGTS/SMG-010207Q SMG#1702.07 5.1.0 Phase 2+ GTS 02.07 MS features Pub July 1996 RGTS/SMG-

010207QRSMG#19

02.07 5.2.0 Phase 2+ ETS 300 906 MS features UAP version DE/SMG-010207QR1 SMG#2002.07 5.2.1 Phase 2+ ETS 300 906 MS features Pub Apr 1997 DE/SMG-010207QR1 SMG#2002.07 5.3.0 Phase 2+ ETS 300 906 Ed2 MS features Unpublished RE/SMG-010207QR2 SMG#2202.07 5.3.1 Phase 2+ ETS 300 906 Ed2 MS features OAP version RE/SMG-010207QR2 SMG#2202.07 5.3.2 Phase 2+ ETS 300 906 Ed2 MS features Pub Dec 1997 RE/SMG-010207QR2 SMG#2202.07 5.4.0 Phase 2+ ETS 300 906 Ed3 MS features OAP version RE/SMG-010207QR3 SMG#2402.07 5.4.1 Phase 2+ ETS 300 906 Ed3 MS features Pub June 1998 RE/SMG-010207QR3 SMG#2402.07 6.0.0 R97 TS 100 906 MS features Unpublished DTS/SMG-010207Q6 SMG#2502.07 6.1.0 R97 TS 100 906 MS features Pub July 1998 DTS/SMG-010207Q6 SMG#2602.07 7.0.0 R98 TS 100 906 MS features Unpublished? RTS/SMG-010207Q7 SMG#2702.08 0.2.1 Phase 2 ETR 101 QoS Unpublished DTR/SMG-010208P SMG#1602.09 4.2.4 Phase 2 ETS 300 506 Security aspects Pub Sep 1994 DE/SMG-010209P SMG#702.09 4.3.0 Phase 2 ETS 300 506 Am1 Security aspects Pub Mar 1995 RE/SMG-010209P SMG#1202.09 4.4.0 Phase 2 ETS 300 506 Ed2 Security aspects OAP version RE/SMG-010209PR1 SMG#2202.09 4.4.1 Phase 2 ETS 300 506 Ed2 Security aspects Pub Jan 1998 RE/SMG-010209PR1 SMG#2202.09 5.0.0 Phase 2/2+ ETS 300 920 Security aspects UAP version DE/SMG-010209Q SMG#2002.09 5.0.1 Phase 2/2+ ETS 300 920 Security aspects Pub Apr 1997 DE/SMG-010209Q SMG#2002.09 5.1.0 Phase 2+ ETS 300 920 Ed2 Security aspects OAP version RE/SMG-010209QR1 SMG#2202.09 5.1.1 Phase 2+ ETS 300 920 Ed2 Security aspects Pub Dec 1997 RE/SMG-010209QR1 SMG#2202.11 4.6.1 Phase 2 ETS 300 507 Service accessibility Pub Sep 1994 DE/SMG-010211P SMG#1002.11 4.7.0 Phase 2 ETS 300 507 Ed2 Service accessibility Pub Jan 1996 RE/SMG-010211P SMG#1502.11 4.8.0 Phase 2 ETS 300 507 Ed3 Service accessibility Pub May 1996 RE/SMG-010211PR2 SMG#1602.11 4.9.0 Phase 2 ETS 300 507 Ed4 Service accessibility Pub Sep 1996 RE/SMG-010211PR3 SMG#1702.11 5.0.0 Phase 2/2+ ETS 300 921 Service accessibility UAP version DE/SMG-010211Q SMG#2002.11 5.0.1 Phase 2/2+ ETS 300 921 Service accessibility Pub Apr 1997 DE/SMG-010211Q SMG#2002.11 6.0.0 R97 TS 100 921 Service accessibility Pub July 1998 DTS/SMG-010211Q6 SMG#2602.11 7.0.0 R98 TS 100 921 Service accessibility Unpublished RTS/SMG-010211Q7 SMG#2702.16 4.3.2 Phase 2 ETS 300 508 ME identity PE version DE/SMG-010216P SMG#702.16 4.3.3 Phase 2 ETS 300 508 ME identity Vote version DE/SMG-010216P02.16 4.3.4 Phase 2 ETS 300 508 ME identity Pub Sep 1994 DE/SMG-010216P02.16 4.4.0 Phase 2 ETS 300 508 Am1 ME identity Pub Mar 1995 RE/SMG-010216P SMG#1202.16 4.5.0 Phase 2 ETS 300 508 Ed2 ME identity Pub July 1995 RE/SMG-010216P1 SMG#1302.16 5.0.0 Phase 2/2+ GTS 02.16 ME identity Pub Nov 1996 DGTS/SMG-010216Q SMG#2002.17 4.3.3 Phase 2 ETS 300 509 SIM characteristics Pub Sep 1994 DE/SMG-010217P SMG#802.17 5.0.0 Phase 2/2+ ETS 300 922 SIM characteristics UAP version DE/SMG-010217Q SMG#2002.17 5.0.1 Phase 2/2+ ETS 300 922 SIM characteristics Pub Apr 1997 DE/SMG-010217Q SMG#2002.17 5.1.0 Phase 2+ ETS 300 922 Ed2 SIM characteristics OAP version RE/SMG-090217QR1 SMG#2702.17 6.0.0 R97 TS 100 922 SIM characteristics Pub Nov 1998 DTS/SMG-090217Q6 SMG#2702.17 7.0.0 R98 TS 100 922 SIM characteristics Unpublished DTS/SMG-090217Q7 SMG#26


Page 3


02.17 7.1.0 R98 TS 100 922 SIM characteristics Unpublished DTS/SMG-090217Q7 SMG#2702.19 7.0.0 R98 TS 101 xxx SIM API Unpublished DTS/SMG-090219Q7 SMG#2702.22 5.0.0 Phase 2+ GTS 02.22 Personalisation of the ME Unpublished DGTS/SMG-010222Q SMG#1702.22 5.1.0 Phase 2+ GTS 02.22 Personalisation of the ME Unpublished DGTS/SMG-010222Q SMG#1802.22 5.2.0 Phase 2+ GTS 02.22 Personalisation of the ME Pub Dec 1996 DGTS/SMG-010222Q SMG#2002.22 5.2.0 Phase 2+ GTS 02.22 Personalisation of the ME Unpublished DGTS/SMG-010222Q SMG#1902.22 5.3.0 Phase 2+ GTS 02.22 Personalisation of the ME Pub Nov 1997 RGTS/SMG-

010222QR1SMG#23

02.22 5.3.1 Phase 2+ GTS 02.22 Personalisation of the ME Pub Apr 1998 RGTS/SMG-010222QR2

SMG#25

02.22 5.4.0 Phase 2+ GTS 02.22 Personalisation of the ME Pub July 1998 RGTS/SMG-010222QR3

SMG#26

02.24 4.4.1 Phase 2 ETS 300 510 Advice of Charge Pub Oct 1994 DE/SMG-010224P SMG#1102.24 4.5.0 Phase 2 ETS 300 510 Ed2 Advice of Charge Pub Jan 1996 RE/SMG-010224P SMG#1502.24 5.0.0 Phase 2/2+ ETS 300 923 Advice of Charge UAP version DE/SMG-010224Q SMG#2002.24 5.0.1 Phase 2/2+ ETS 300 923 Advice of Charge Pub Apr 1997 DE/SMG-010224Q SMG#2002.30 4.10.0 Phase 2 ETS 300 511 Man-Machine Interface PE version DE/SMG-010230P SMG#02.30 4.11.0 Phase 2 ETS 300 511 Man-Machine Interface Vote version DE/SMG-010230P SMG#02.30 4.11.1 Phase 2 ETS 300 511 Man-Machine Interface Pub Sep 1994 DE/SMG-010230P SMG#1002.30 4.12.0 Phase 2 ETS 300 511 Am1 Man-Machine Interface Pub Mar 1994 RE/SMG-010230P SMG#1202.30 4.13.0 Phase 2 ETS 300 511 Ed2 Man-Machine Interface Pub July 1995 RE/SMG-010230P1 SMG#1302.30 5.0.0 Phase 2+ GTS 02.30 Man-Machine Interface Pub Jan 1996 DGTS/SMG-010230Q SMG#1602.30 5.1.0 Phase 2+ GTS 02.30 Man-Machine Interface Pub Mar 1996 RGTS/SMG-

010230QRSMG#17

02.30 5.2.0 Phase 2+ GTS 02.30 Man-Machine Interface Pub May 1996 RGTS/SMG-010230QR1

SMG#18

02.30 5.3.0 Phase 2+ GTS 02.30 Man-Machine Interface Pub July 1996 RGTS/SMG-010230QR2

SMG#19

02.30 5.3.1 Phase 2+ ETS 300 907 Man-Machine Interface UAP version DE/SMG-010230QR2 SMG#2002.30 5.3.2 Phase 2+ ETS 300 907 Man-Machine Interface Pub Apr 1997 DE/SMG-010230QR2 SMG#2002.30 5.4.0 Phase 2+ ETS 300 907 Ed2 Man-Machine Interface OAP version RE/SMG-010230QR3 SMG#2102.30 5.4.1 Phase 2+ ETS 300 907 Ed2 Man-Machine Interface Pub Aug 1997 RE/SMG-010230QR3 SMG#2102.30 5.5.0 Phase 2+ ETS 300 907 Ed3 Man-Machine Interface Unpublished RE/SMG-010230QR4 SMG#2202.30 5.5.1 Phase 2+ ETS 300 907 Ed3 Man-Machine Interface OAP version RE/SMG-010230QR4 SMG#2202.30 5.5.2 Phase 2+ ETS 300 907 Ed3 Man-Machine Interface Pub Feb 1998 RE/SMG-010230QR4 SMG#2202.30 5.6.0 Phase 2+ ETS 300 907 Ed4 Man-Machine Interface Unpublished RE/SMG-010230QR5 SMG#2302.30 5.6.1 Phase 2+ ETS 300 907 Ed4 Man-Machine Interface OAP version RE/SMG-010230QR5 SMG#2402.30 5.6.2 Phase 2+ ETS 300 907 Ed4 Man-Machine Interface Pub June 1998 RE/SMG-010230QR5 SMG#2402.30 6.0.0 R97 TS 100 907 Man-Machine Interface Unpublished DTS/SMG-010230Q6 SMG#2502.30 6.0.1 R97 TS 100 907 Man-Machine Interface Pub July 1998 DTS/SMG-010230Q6 SMG#2502.30 7.0.0 R98 TS 100 907 Man-Machine Interface Unpublished DTS/SMG-010230Q7 SMG#2602.31 5.0.0 Phase 2+ TS 101 107 Fraud Info Gat FIGS Stg 1 Pub Oct 1997 DTS/SMG-100231Q SMG#2302.31 7.0.0 R98 TR 101 107 Fraud Info Gat FIGS Stg 1 Unpublished RTR/SMG-100231Q7 SMG#2502.31 7.1.0 R98 TR 101 107 Fraud Info Gat FIGS Stg 1 Unpublished RTR/SMG-100231Q7 SMG#2602.32 7.0.0 R98 TS 101 xxx IST Stage 1 Unpublished DTS/SMG-100232Q7 SMG#2502.32 7.1.0 R98 TS 101 xxx IST Stage 1 Unpublished DTS/SMG-100232Q7 SMG#2602.33 5.0.0 Phase 2+ GTS 02.33 Lawful intercept Stage 1 Pub Jan 1997 DGTS/SMG-100233Q SMG#2002.33 7.0.0 R98 TS 101 xxx Lawful intercept Stage 1 Unpublished DTS/SMG-100233Q7 SMG#2502.33 7.1.0 R98 TS 101 xxx Lawful intercept Stage 1 Unpublished FTS/SMG-100233Q7 SMG#2702.34 5.0.0 Phase 2+ GTS 02.34 HSCSD Unpublished DGTS/SMG-010234Q SMG#2002.34 5.0.1 Phase 2+ GTS 02.34 HSCSD Pub Nov 1996 DGTS/SMG-010234Q SMG#2002.34 5.1.0 Phase 2+ GTS 02.34 HSCSD Pub Mar 1997 RGTS/SMG-

010234QRSMG#21

02.34 5.2.0 Phase 2+ GTS 02.34 HSCSD Unpublished RGTS/SMG-010234QR1

SMG#22

02.34 5.2.1 Phase 2+ GTS 02.34 HSCSD Pub July 1997 RGTS/SMG-010234QR1

SMG#22

02.37 1.0.0 Phase 2+ TS 101 xxx DECT access to GSM Draft DTS/SMG-010237Q SMG#2302.40 4.4.1 Phase 2 ETS 300 512 Call Progress indicators Pub Sep 1994 DE/SMG-010240P SMG#1002.40 4.5.0 Phase 2 ETS 300 512 Ed2 Call Progress indicators Pub Jan 1996 RE/SMG-010240P SMG#1502.40 5.0.0 Phase 2/2+ GTS 02.40 Call Progress indicators Pub Nov 1996 DGTS/SMG-010240Q SMG#2002.40 7.0.0 R98 TS 100 512 Call Progress indicators Unpublished DTS/SMG-010240Q7 SMG#2702.41 4.5.2 Phase 2 ETS 300 513 ODB Stage 1 Pub Sep 1994 DE/SMG-010241P SMG#802.41 5.0.0 Phase 2+ GTS 02.41 ODB Stage 1 Pub Jan 1996 DGTS/SMG-010241Q SMG#1602.41 5.1.0 Phase 2+ GTS 02.41 ODB Stage 1 Pub Mar 1997 RGTS/SMG-

010241QRSMG#21

02.41 5.1.1 Phase 2+ GTS 02.41 ODB Stage 1 Pub Jan 1998 RGTS/SMG-010241QR1

SMG#24

02.42 5.0.0 Phase 2+ GTS 02.42 NITZ Pub July 1996 DGTS/SMG-010242Q SMG#19


Page 4


02.42 5.0.1 Phase 2+ GTS 02.42 NITZ Pub Nov 1996 RGTS/SMG-010242QR

SMG#20

02.42 5.1.0 Phase 2+ GTS 02.42 NITZ Pub Jan 1998 RGTS/SMG-010242QR1

SMG#24

02.43 7.0.0 R98 TS 101 xxx SoLSA Stage 1 Unpublished DTS/SMG-010243Q7 SMG#2702.48 6.0.0 R97 TS 101 180 Tool Kit Security Stage1 Pub Apr 1998 DTS/SMG-090248Q6 SMG#2502.53 5.0.0 Phase 2+ TS 101 108 TFO Pub Nov 1997 DTS/SMG-110253Q SMG#2302.53 5.1.0 Phase 2+ TS 101 108 TFO Pub Jan 1998 RTS/SMG-110253QR SMG#2402.53 7.0.0 R98 TS 101 108 TFO Unpublished RTS/SMG-110253Q7 SMG#2502.56 7.0.0 R98 TS 101 xxx CTS Stage 1 Unpublished DTS/SMG-010256Q7 SMG#2702.57 7.0.0 R98 TS 101 xxx MExE Stage 1 Unpublished DTS/SMG-040257Q7 SMG#2502.60 5.0.0 Phase 2+ EN 301 113 GPRS Stage 1 Unpublished DEN/SMG-010260Q6 SMG#2102.60 5.0.0 Phase 2+ EN 301 113 GPRS Stage 1 Unpublished DEN/SMG-010260Q6 SMG#2202.60 5.1.0 Phase 2+ TS 101 113 GPRS Stage 1 Pub Oct 1997 DTS/SMG-010260Q6 SMG#2302.60 5.2.0 Phase 2+ TS 101 113 GPRS Stage 1 Pub Jan 1998 RTS/SMG-

010260QR1SMG#24

02.60 6.0.0 R97 TS 101 113 GPRS Stage 1 Unpublished RTS/SMG-010260Q6 SMG#2502.60 6.1.0 R97 EN 301 113 GPRS Stage 1 OAP version DEN/SMG-010260Q6 SMG#2602.60 7.0.0 R98 TS 101 113 GPRS Stage 1 Unpublished RTS/SMG-010260Q7 SMG#2502.63 5.0.0 Phase 2+ GTS 02.63 PDS Stage 1 Pub July 1996 DGTS/SMG-010263Q SMG#1902.66 5.0.0 Phase 2+ TS 101 xxx Mobile NP Stage 1 Unpublished DTS/SMG-010266Q SMG#2402.66 7.0.0 R98 TS 101 xxx Mobile NP Stage 1 Unpublished DTS/SMG-010266Q7 SMG#2502.67 5.0.0 Phase 2+ GTS 02.67 eMLPP Pub Jan 1996 DGTS/SMG-010267Q SMG#1602.67 5.0.1 Phase 2+ GTS 02.67 eMLPP Pub July 1996 RGTS/SMG-

010267QRSMG#19

02.67 5.0.2 Phase 2+ ETS 300 924 eMLPP UAP version DE/SMG-010267QR SMG#2002.67 5.0.3 Phase 2+ ETS 300 924 eMLPP Pub May 1997 DE/SMG-010267QR SMG#2002.67 5.0.4 Phase 2+ ETS 300 924Ed2 eMLPP OAP version RE/SMG-010267QR1 SMG#2202.67 5.0.5 Phase 2+ ETS 300 924Ed2 eMLPP Pub Dec 1997 RE/SMG-010267QR1 SMG#2202.68 5.0.0 Phase 2+ GTS 02.68 VGCS Pub Jan 1996 DGTS/SMG-010268Q SMG#1602.68 5.1.0 Phase 2+ GTS 02.68 VGCS Pub Mar 1996 RGTS/SMG-

010268QRSMG#17

02.68 5.1.1 Phase 2+ ETS 300 925 VGCS Pub May 1997 DE/SMG-010268QR SMG#2002.68 5.1.2 Phase 2+ ETS 300 925 Ed2 VGCS OAP version RE/SMG-010268QR1 SMG#2102.68 5.1.3 Phase 2+ ETS 300 925 Ed2 VGCS Pub Aug 1997 RE/SMG-010268QR1 SMG#2202.68 5.2.0 Phase 2+ ETS 300 925 Ed3 VGCS OAP version RE/SMG-010268QR2 SMG#2602.69 5.0.0 Phase 2+ GTS 02.69 VBS Pub Jan 1996 DGTS/SMG-010269Q SMG#1602.69 5.1.0 Phase 2+ GTS 02.69 VBS Pub Mar 1996 RGTS/SMG-

010269QRSMG#17

02.69 5.1.1 Phase 2+ ETS 300 926 VBS Pub May 1997 DE/SMG-010269QR SMG#2002.69 5.1.2 Phase 2+ ETS 300 926 Ed2 VBS OAP version RE/SMG-010269QR1 SMG#2102.69 5.1.3 Phase 2+ ETS 300 926 Ed2 VBS Pub Aug 1997 RE/SMG-010269QR1 SMG#2202.69 5.2.0 Phase 2+ ETS 300 926 Ed3 VBS OAP version RE/SMG-010269QR2 SMG#2602.72 5.0.0 Phase 2+ GTS 02.72 Call deflection Pub July 1996 DGTS/SMG-010272Q SMG#1902.72 7.0.0 R98 TS 101 xxx Call deflection Unpublished DTS/SMG-010272Q7 SMG#2502.72 7.1.0 R98 TS 101 xxx Call deflection Unpublished DTS/SMG-010272Q7 SMG#2702.78 5.0.0 Phase 2+ GTS 02.78 CAMEL Stage 1 Pub July 1996 DGTS/SMG-010278Q SMG#1902.78 5.1.0 Phase 2+ GTS 02.78 CAMEL Stage 1 Pub Nov 1996 RGTS/SMG-

010278QRSMG#20

02.78 5.1.1 Phase 2+ GTS 02.78 CAMEL Stage 1 Pub Mar 1997 RGTS/SMG-010278QR1

SMG#21

02.78 5.2.0 Phase 2+ GTS 02.78 CAMEL Stage 1 Unpublished RGTS/SMG-010278QR2

SMG#22

02.78 5.2.1 Phase 2+ GTS 02.78 CAMEL Stage 1 Pub July 1997 RGTS/SMG-010278QR2

SMG#22

02.78 5.3.0 Phase 2+ GTS 02.78 CAMEL Stage 1 Unpublished RGTS/SMG-010278QR3

SMG#23

02.78 5.4.0 Phase 2+ GTS 02.78 CAMEL Stage 1 Pub Jan 1998 RGTS/SMG-010278QR3

SMG#24

02.78 5.5.0 Phase 2+ GTS 02.78 CAMEL Stage 1 Pub July 1998 RGTS/SMG-010278QR4

SMG#26

02.78 6.0.1 R97 TS 101 285 CAMEL Ph2 Stage 1 Unpublished DTS/SMG-010278Q6 SMG#2502.78 6.1.0 R97 TS 101 285 CAMEL Ph2 Stage 1 Pub July 1998 DTS/SMG-010278Q6 SMG#2602.79 5.0.0 Phase 2+ GTS 02.79 SOR Pub July 1996 DGTS/SMG-010279Q SMG#1902.79 5.1.0 Phase 2+ GTS 02.79 SOR Pub Nov 1996 RGTS/SMG-

010279QRSMG#20

02.81 4.3.2 Phase 2 ETS 300 514 Line Identity SS PE version DE/SMG-010281P SMG#1102.81 4.4.1 Phase 2 ETS 300 514 Line Identity SS Vote version DE/SMG-010281P SMG#1102.81 4.4.2 Phase 2 ETS 300 514 Line Identity SS Pub Oct 1994 DE/SMG-010281P SMG#1102.81 4.5.0 Phase 2 ETS 300 514 Am1 Line Identity SS Pub Mar 1995 RE/SMG-010281P SMG#12


Page 5


02.81 4.5.1 Phase 2 ETS 300 514 Ed2 Line Identity SS Pub May 1996 RE/SMG-010281PR2 SMG#1602.81 4.6.0 Phase 2 ETS 300 514 Ed3 Line Identity SS OAP version RE/SMG-010281PR3 SMG#2402.81 4.6.1 Phase 2 ETS 300 514 Ed3 Line Identity SS Pub June 1998 RE/SMG-010281PR3 SMG#2402.81 5.0.0 Phase 2/2+ GTS 02.81 Line Identity SS Pub Nov 1996 DGTS/SMG-010281Q SMG#2002.81 5.1.0 Phase 2+ GTS 02.81 Line Identity SS Pub Jan 1998 RGTS/SMG-

010281QR1SMG#24

02.82 4.5.1 Phase 2 ETS 300 515 Call Offering SS Pub Sep 1994 DE/SMG-010282P SMG#1002.82 4.5.2 Phase 2 ETS 300 515 Ed2 Call Offering SS Pub May 1996 RE/SMG-010282P SMG#1602.82 5.0.0 Phase 2+ GTS 02.82 Call Offering SS Pub Jan 1996 DGTS/SMG-010282Q SMG#1602.83 4.6.6 Phase 2 ETS 300 516 Call Completion SS Pub Sep 1994 DE/SMG-010283P SMG#1002.83 4.6.7 Phase 2 ETS 300 516 Ed2 Call Completion SS Pub May 1996 RE/SMG-010283P SMG#1602.83 5.0.0 Phase 2/2+ GTS 02.83 Call Completion SS Pub Nov 1996 DGTS/SMG-010283Q SMG#2002.84 4.4.6 Phase 2 ETS 300 517 MultiParty SS Pub Sep 1994 DE/SMG-010284P SMG#1102.84 4.4.7 Phase 2 ETS 300 517 Ed2 MultiParty SS Pub May 1996 RE/SMG-010284P SMG#1602.84 5.0.0 Phase 2/2+ GTS 02.84 MultiParty SS Pub Nov 1996 DGTS/SMG-010284Q SMG#2002.85 4.2.5 Phase 2 ETS 300 518 Closed User Group SS Pub Sep 1994 DE/SMG-010285P SMG#702.85 4.2.6 Phase 2 ETS 300 518 Ed2 Closed User Group SS Pub May 1996 RE/SMG-010285P SMG#1602.85 5.0.0 Phase 2/2+ GTS 02.85 Closed User Group SS Pub Nov 1996 DGTS/SMG-010285Q SMG#2002.86 4.1.4 Phase 2 ETS 300 519 Advice of Charge SS Pub Sep 1994 DE/SMG-010286P SMG#702.86 4.1.5 Phase 2 ETS 300 519 Ed2 Advice of Charge SS Pub May 1996 RE/SMG-010286P SMG#1602.86 5.0.0 Phase 2/2+ GTS 02.86 Advice of Charge SS Pub Nov 1996 DGTS/SMG-010286Q SMG#2002.87 5.0.0 Phase 2+ GTS 02.87 User to User Signalling Pub May 1996 DGTS/SMG-010287Q SMG#1802.87 5.1.0 Phase 2+ GTS 02.87 User to User Signalling Pub Nov 1996 RGTS/SMG-

010287QRSMG#20

02.87 5.2.0 Phase 2+ GTS 02.87 User to User Signalling Pub Mar 1997 RGTS/SMG-010287QR1

SMG#21

02.87 5.2.1 Phase 2+ GTS 02.87 User to User Signalling Pub Nov 1997 RGTS/SMG-010287QR2

SMG#23

02.87 7.0.0 R98 TS 101 xxx User to User Signalling Unpublished DTS/SMG-010287Q7 SMG#2502.88 4.4.2 Phase 2 ETS 300 520 Call Barring SS Pub Sep 1994 DE/SMG-010288P SMG#802.88 4.4.3 Phase 2 ETS 300 520 Ed2 Call Barring SS Pub May 1996 RE/SMG-010288P SMG#1602.88 5.0.0 Phase 2/2+ GTS 02.88 Call Barring SS Pub Nov 1996 DGTS/SMG-010288Q SMG#2002.90 4.0.4 Phase 2 ETS 300 625 USSD stage 1 Pub Jan 1995 DE/SMG-010290P SMG#802.90 4.1.0 Phase 2 ETS 300 625 Ed2 USSD stage 1 OAP version RE/SMG-010290PR SMG#2102.90 4.1.1 Phase 2 ETS 300 625 Ed2 USSD stage 1 Pub Sep 1997 RE/SMG-010290PR SMG#2102.90 5.0.0 Phase 2/2+ GTS 02.90 USSD stage 1 Pub Nov 1996 DGTS/SMG-010290Q SMG#2002.90 5.1.0 Phase 2/2+ GTS 02.90 USSD stage 1 Pub Mar 1997 RGTS/SMG-

010290QRSMG#21

02.91 5.0.0 Phase 2+ GTS 02.91 ECT stage 1 Pub Jan 1996 DGTS/SMG-010291Q SMG#1602.91 5.0.1 Phase 2+ GTS 02.91 ECT stage 1 Pub Mar 1996 RGTS/SMG-

010291QRSMG#17

02.91 5.1.0 Phase 2+ GTS 02.91 ECT stage 1 Pub July 1996 RGTS/SMG-010291QR1

SMG#19

02.91 5.1.1 Phase 2+ GTS 02.91 ECT stage 1 Pub Mar 1997 RGTS/SMG-010291QR2

SMG#21

02.93 5.0.0 Phase 2+ GTS 02.93 CCBS stage 1 Pub Jan 1996 DGTS/SMG-010293Q SMG#1602.93 5.1.0 Phase 2+ GTS 02.93 CCBS stage 1 Pub July 1996 RGTS/SMG-

010293QRSMG#19

02.93 5.2.0 Phase 2+ GTS 02.93 CCBS stage 1 Pub Dec 1996 RGTS/SMG-010293QR1

SMG#20

02.93 5.3.0 Phase 2+ GTS 02.93 CCBS stage 1 Unpublished RGTS/SMG-010293QR2

SMG#22

02.93 5.3.1 Phase 2+ GTS 02.93 CCBS stage 1 Pub Sep 1997 RGTS/SMG-010293QR2

SMG#22

02.93 5.4.0 Phase 2+ GTS 02.93 CCBS stage 1 Pub Nov 1997 RGTS/SMG-010293QR3

SMG#23

02.93 5.5.0 Phase 2+ GTS 02.93 CCBS stage 1 Pub Jan 1998 RGTS/SMG-010293QR4

SMG#24

02.93 6.0.0 R97 TS 101 282 CCBS stage 1 Unpublished DTS/SMG-010293Q6 SMG#2502.93 6.0.1 R97 TS 101 282 CCBS stage 1 Pub July 1998 DTS/SMG-010293Q6 SMG#2602.95 5.1.0 Phase 2+ GTS 02.95 SPNP Pub May 1996 DGTS/SMG-010295Q SMG#1802.95 5.2.0 Phase 2+ GTS 02.95 SPNP Pub July 1996 RGTS/SMG-

010295QRSMG#19

02.96 5.0.0 Phase 2+ TS 101 394 Calling Nme Delivry CNAP) Unpublished DTS/SMG-010296Q SMG#2402.96 6.0.0 R97 TS 101 394 Calling Nme Delivry CNAP) Unpublished DTS/SMG-010296Q6 SMG#2402.96 6.0.1 R97 TS 101 394 Calling Nme Delivry CNAP Pub Oct 1998 DTS/SMG-010296Q6 SMG#2702.97 5.0.0 Phase 2+ GTS 02.97 Multiple Sub Profile Pub July 1996 DGTS/SMG-010297Q SMG#1902.97 5.1.0 Phase 2+ GTS 02.97 Multiple Sub Profile Unpublished RGTS/SMG-

010297QR1SMG#22


Page 6


02.97 5.1.1 Phase 2+ GTS 02.97 Multiple Sub Profile Pub Sep 1997 RGTS/SMG-010297QR1

SMG#22

02.97 5.2.0 Phase 2+ GTS 02.97 Multiple Sub Profile Pub Nov 1997 RGTS/SMG-010297QR2

SMG#23

02.97 7.0.0 R98 TS 101 xxx Multiple Sub Profile Unpublished DTS/SMG-010297Q7 SMG#2502.97 7.1.0 R98 TS 101 xxx Multiple Sub Profile Unpublished DTS/SMG-010297Q7 SMG#2603.01 4.0.4 Phase 2 ETS 300 521 Network Functions Pub Sep 1994 DE/SMG-030301P SMG#703.01 5.0.0 Phase 2+ GTS 03.01 Network Functions Pub Mar 1996 DGTS/SMG-030301Q SMG#1703.01 5.1.0 Phase 2+ GTS 03.01 Network Functions Pub May 1996 RGTS/SMG-

030301QRSMG#18

03.02 4.0.4 Phase 2 ETS 300 522 Network Architecture Pub Sep 1994 DE/SMG-030302P SMG#703.02 4.1.0 Phase 2 ETS 300 522 Ed2 Network Architecture UAP version RE/SMG-030302P SMG#1703.02 4.1.1 Phase 2 ETS 300 522 Ed2 Network Architecture Pub Sep 1996 RE/SMG-030302P SMG#1703.02 4.2.0 Phase 2 ETS 300 522 Ed3 Network Architecture UAP version RE/SMG-030302PR2 SMG#1803.02 4.2.1 Phase 2 ETS 300 522 Ed3 Network Architecture Pub Nov 1996 RE/SMG-030302PR2 SMG#1803.02 5.0.0 Phase 2+ GTS 03.02 Network Architecture Pub Mar 1996 DGTS/SMG-030302Q SMG#1703.02 5.1.0 Phase 2+ GTS 03.02 Network Architecture Pub May 1996 RGTS/SMG-

030302QRSMG#18

03.02 5.2.0 Phase 2+ GTS 03.02 Network Architecture Unpublished RGTS/SMG-030302QR1

SMG#23

03.02 5.2.1 Phase 2+ GTS 03.02 Network Architecture Unpublished RGTS/SMG-030302QR1

SMG#24

03.02 6.0.0 R97 TS 100 522 Network Architecture Unpublished DTS/SMG-120302Q6 SMG#2503.02 6.1.0 R97 TS 100 522 Network Architecture Pub July 1998 DTS/SMG-120302Q6 SMG#2603.03 4.8.1 Phase 2 ETS 300 523 Numbering Addr & Ident Pub Sep 1994 DE/SMG-030303P SMG#903.03 4.9.0 Phase 2 ETS 300 523 Ed 2 Numbering Addr & Ident Pub Mar 1995 RE/SMG-030303P SMG#1203.03 5.0.0 Phase 2+ GTS 03.03 Numbering Addr & Ident Pub Mar 1996 DGTS/SMG-030303Q SMG#1703.03 5.0.1 Phase 2+ ETS 300 927 Numbering Addr & Ident UAP version DE/SMG-010303Q SMG#2003.03 5.0.2 Phase 2+ ETS 300 927 Numbering Addr & Ident Pub Apr 1997 DE/SMG-010303Q SMG#2003.03 5.1.0 Phase 2+ ETS 300 927 Ed2 Numbering Addr & Ident OAP version RE/SMG-010303QR1 SMG#2503.03 5.1.1 Phase 2+ ETS 300 927 Ed2 Numbering Addr & Ident Pub Oct 1998 RE/SMG-010303QR1 SMG#2503.03 6.0.0 R97 TS 100 927 Numbering Addr & Ident Unpublished DTS/SMG-030303Q6 SMG#2503.03 6.1.0 R97 TS 100 927 Numbering Addr & Ident Pub July 1998 DTS/SMG-030303Q6 SMG#2603.04 4.0.4 Phase 2 ETS 300 524 Sig req of calls to MS Pub Sep 1994 DE/SMG-030304P SMG#703.04 5.0.0 Phase 2/2+ GTS 03.04 Sig req of calls to MS Pub Nov 1996 DGTS/SMG-030304Q SMG#2003.05 4.0.1 Phase 2 ETR 102 Tech perfmce objectives Pub Oct 1993 DTR/SMG-030305P SMG#703.05 4.1.0 Phase 2 ETR 102 Ed2 Tech perfmce objectives Pub Aug 1996 RTR/SMG-030305P SMG#1903.05 5.0.0 Phase 2/2+ ETR 351 Tech perfmce objectives Pub Nov 1996 DTR/SMG-030305Q SMG#2003.07 4.3.1 Phase 2 ETS 300 525 Restoration procedures Pub Sep 1994 DE/SMG-030307P SMG#1003.07 5.0.0 Phase 2/2+ GTS 03.07 Restoration procedures Pub Nov 1996 DGTS/SMG-030307Q SMG#2003.07 5.1.0 Phase 2+ GTS 03.07 Restoration procedures Unpublished DGTS/SMG-030307Q SMG#2303.07 6.0.0 R97 TS 100 525 Restoration procedures Unpublished RTS/SMG-030307Q6 SMG#2503.07 6.1.0 R97 TS 100 525 Restoration procedures Pub July 1998 RTS/SMG-030307Q6 SMG#2603.08 4.7.1 Phase 2 ETS 300 526 Subscriber data Pub Sep 1994 DE/SMG-030308P SMG#1003.08 4.8.0 Phase 2 ETS 300 526 Ed2 Subscriber data Pub Oct 1996 RE/SMG-030308P SMG#1803.08 5.0.0 Phase 2+ GTS 03.08 Subscriber data Pub May 1996 DGTS/SMG-030308Q SMG#1803.08 5.1.0 Phase 2+ GTS 03.08 Subscriber data Pub Apr 1997 RGTS/SMG-

030308QRSMG#21

03.08 5.2.0 Phase 2+ GTS 03.08 Subscriber data Unpublished RGTS/SMG-030308QR1

SMG#23

03.08 6.0.0 R97 TS 100 526 Subscriber data Unpublished DTS/SMG-030308Q6 SMG#2503.08 6.1.0 R97 TS 100 526 Subscriber data Pub July 1998 DTS/SMG-030308Q6 SMG#2603.08 6.2.0 R97 TS 100 526 Subscriber data Pub Nov 1998? RTS/SMG-

030308Q6R1SMG#27

03.09 4.5.1 Phase 2 ETS 300 527 Handover procedures Pub Feb 1995 DE/SMG-030309P SMG#1203.09 4.6.0 Phase 2 ETS 300 527 Ed2 Handover procedures Pub Sep 1996 RE/SMG-030309P SMG#1703.09 5.0.0 Phase 2+ GTS 03.09 Handover procedures Pub May1996 DGTS/SMG-030309Q SMG#1803.09 5.1.0 Phase 2+ GTS 03.09 Handover procedures Pub Aug 1997 RGTS/SMG-

030309QR1SMG#22

03.10 4.3.1 Phase 2 ETS 300 528 PLMN connection types Pub Sep 1994 DE/SMG-040310P SMG#803.10 5.0.0 Phase 2+ GTS 03.10 PLMN connection types Pub Jan 1996 DGTS/SMG-040310Q SMG#1603.10 5.1.0 Phase 2+ GTS 03.10 PLMN connection types Pub Mar 1997 RGTS/SMG-

040310QRSMG#21

03.10 5.2.0 Phase 2+ GTS 03.10 PLMN connection types Pub Aug 1997 RGTS/SMG-040310QR1

SMG#22

03.10 5.3.0 Phase 2+ GTS 03.10 PLMN connection types Pub Nov 1997 RGTS/SMG-040310QR2

SMG#23

03.10 5.4.0 Phase 2+ GTS 03.10 PLMN connection types Pub Jan 1998 RGTS/SMG-040310QR3

SMG#24

03.10 7.0.0 R98 TS 100 528 PLMN connection types Unpublished DTS/SMG-040310Q7 SMG#27


Page 7


03.11 4.10.0 Phase 2 ETS 300 529 Ed3 Tech realisation of SS UAP version RE/SMG-030311PR2 SMG#1803.11 4.10.1 Phase 2 ETS 300 529 Ed3 Tech realisation of SS Pub Nov 1996 RE/SMG-030311PR2 SMG#1803.11 4.8.1 Phase 2 ETS 300 529 Tech realisation of SS Pub Feb 1995 DE/SMG-030311P SMG#1203.11 4.9.1 Phase 2 ETS 300 529 Ed2 Tech realisation of SS Pub Oct 1995 RE/SMG-030311P SMG#1403.11 5.0.0 Phase 2/2+ ETS 300 928 Tech realisation of SS UAP version DE/SMG-030311Q SMG#2003.11 5.0.1 Phase 2/2+ ETS 300 928 Tech realisation of SS Pub May 1997 DE/SMG-030311Q SMG#2003.12 4.4.2 Phase 2 ETS 300 530 Location reg procedures Pub Sep 1994 DE/SMG-030312P SMG#803.12 5.0.0 Phase 2/2+ GTS 03.12 Location reg procedures Pub Nov 1996 DGTS/SMG-030312Q SMG#2003.13 4.0.4 Phase 2 ETS 300 531 Discontinuous Rx DRX Pub Sep 1994 DE/SMG-030313P SMG#703.13 5.0.0 Phase 2+ GTS 03.13 Discontinuous Rx DRX Pub Mar 1996 DGTS/SMG-030313Q SMG#1703.14 4.1.1 Phase 2 ETS 300 532 Support of DTMF Pub Sep 1994 DE/SMG-030314P SMG#1003.14 5.0.0 Phase 2/2+ GTS 03.14 Support of DTMF Pub Nov 1996 DGTS/SMG-030314Q SMG#2003.15 4.3.1 Phase 2 ETS 300 533 Tech realisation of ODB Pub Sep 1994 DE/SMG-030315P SMG#1003.15 5.0.0 Phase 2+ GTS 03.15 Tech realisation of ODB Pub Jan 1996 DGTS/SMG-030315Q SMG#1603.15 5.1.0 Phase 2+ GTS 03.15 Tech realisation of ODB Pub Apr 1997 RGTS/SMG-

030315QRSMG#21

03.15 6.0.0 R97 TS 100 533 Tech realisation of ODB Pub July 1998 DTS/SMG-030315Q6 SMG#2603.16 4.1.0 Phase 2 ETS 300 629 Sub data management PE version DE/SMG-030316P SMG#1403.16 4.1.1 Phase 2 ETS 300 629 Sub data management Vote version DE/SMG-030316P SMG#1603.16 4.1.2 Phase 2 ETS 300 629 Sub data management Pub Jan 1996 DE/SMG-030316P SMG#1603.16 4.2.0 Phase 2 ETS 300 629 Ed2 Sub data management UAP version RE/SMG-030316P SMG#1803.16 4.2.1 Phase 2 ETS 300 629 Ed2 Sub data management Pub Nov 1996 RE/SMG-030316P SMG#1803.16 5.0.0 Phase 2+ GTS 03.16 Sub data management Pub May 1996 DGTS/SMG-030316Q SMG#1803.16 5.1.0 Phase 2+ GTS 03.16 Sub data management Pub Apr 1997 RGTS/SMG-

030316QRSMG#21

03.16 5.2.0 Phase 2+ GTS 03.16 Sub data management Unpublished RGTS/SMG-030316QR

SMG#23

03.16 5.3.0 Phase 2+ GTS 03.16 Sub data management Pub Aug 1998 RGTS/SMG-030316QR2

SMG#26

03.16 6.0.0 R97 TS 100 629 Sub data management Unpublished DTS/SMG-030316Q6 SMG#2503.16 6.1.0 R97 TS 100 629 Sub data management Pub Aug 1998 DTS/SMG-030316Q6 SMG#2603.16 6.2.0 R97 TS 100 629 Sub data management Pub Nov 1998? RTS/SMG-

030316Q6R1SMG#27

03.18 5.0.0 Phase 2+ TS 101 043 Basic Call Handling Unpublished DTS/SMG-030318Q SMG#2103.18 5.0.1 Phase 2+ TS 101 043 Basic Call Handling Pub Apr 1997 DTS/SMG-030318Q SMG#2103.18 5.1.0 Phase 2+ TS 101 043 Basic Call Handling Pub Aug 1997 RTS/SMG-

030318QR1SMG#22

03.18 5.2.0 Phase 2+ TS 101 043 Basic Call Handling Unpublished RTS/SMG-030318QR2

SMG#23

03.18 5.3.0 Phase 2+ TS 101 043 Basic Call Handling Pub Jan 1998 RTS/SMG-030318QR2

SMG#24

03.18 5.4.0 Phase 2+ TS 101 043 Basic Call Handling Unpublished RTS/SMG-030318QR3

SMG#25

03.18 5.5.0 Phase 2+ TS 101 043 Basic Call Handling Pub July 1998 RTS/SMG-030318QR3

SMG#26

03.18 5.6.0 Phase 2+ TS 101 043 Basic Call Handling Pub Nov 1998? RTS/SMG-030318QR4

SMG#27

03.18 6.0.0 R97 TS 101 043 Basic Call Handling Unpublished RTS/SMG-030318Q6 SMG#2503.18 6.1.0 R97 TS 101 043 Basic Call Handling Pub Aug 1998 RTS/SMG-030318Q6 SMG#2603.18 6.2.0 R97 TS 101 043 Basic Call Handling Pub Nov 1998? RTS/SMG-

030318Q6R1SMG#27

03.20 4.3.1 Phase 2 ETS 300 534 Security Net Functions Pub Sep 1994 DE/SMG-030320P SMG#1003.20 4.3.2 Phase 2 ETS 300 534 Ed2 Security Net Functions UAP version RE/SMG-030320P SMG#1703.20 4.3.3 Phase 2 ETS 300 534 Ed2 Security Net Functions Pub Sep 1996 RE/SMG-030320P SMG#1703.20 4.4.0 Phase 2 ETS 300 534 Ed3 Security Net Functions OAP version RE/SMG-030320PR SMG#2103.20 4.4.1 Phase 2 ETS 300 534 Ed3 Security Net Functions Pub Aug 1997 RE/SMG-030320PR SMG#2103.20 5.0.0 Phase 2/2+ ETS 300 929 Security Net Functions UAP version DE/SMG-030320Q SMG#2003.20 5.0.1 Phase 2/2+ ETS 300 929 Security Net Functions Pub May 1997 DE/SMG-030320Q SMG#2003.20 5.1.0 Phase 2+ ETS 300 929 Ed2 Security Net Functions OAP version RE/SMG-030320QR SMG#2103.20 5.1.1 Phase 2+ ETS 300 929 Ed2 Security Net Functions Pub Aug 1997 RE/SMG-030320QR SMG#2103.20 5.2.0 Phase 2+ ETS 300 929 Ed3 Security Net Functions OAP version RE/SMG-030320QR1 SMG#2303.20 5.2.1 Phase 2+ ETS 300 929 Ed3 Security Net Functions Pub July 1998 RE/SMG-030320QR1 SMG#2303.20 6.0.0 R97 TS 100 929 Security Net Functions Unpublished DTS/SMG-030320Q6 SMG#2503.20 6.0.1 R97 TS 100 929 Security Net Functions Pub July 1998 DTS/SMG-030320Q6 SMG#2603.22 4.10.0 Phase 2 ETS 300 535 Ed3 MS in idle mode Pub May 1996 RE/SMG-030322PR2 SMG#1603.22 4.11.0 Phase 2 ETS 300 535 Ed4 MS in idle mode Pub Sep 1996 RE/SMG-030322PR3 SMG#1703.22 4.8.1 Phase 2 ETS 300 535 MS in idle mode Pub Feb 1995 DE/SMG-030322P SMG#1203.22 4.9.0 Phase 2 ETS 300 535 Ed2 MS in idle mode Pub Sep 1995 RE/SMG-030322P SMG#1403.22 5.0.0 Phase 2/2+ ETS 300 930 MS in idle mode UAP version DE/SMG-030322Q SMG#2003.22 5.0.1 Phase 2/2+ ETS 300 930 MS in idle mode Pub May 1997 DE/SMG-030322Q SMG#20


Page 8


03.22 5.1.0 Phase 2+ ETS 300 930 Ed2 MS in idle mode OAP version RE/SMG-030322QR SMG#2103.22 5.1.1 Phase 2+ ETS 300 930 Ed2 MS in idle mode Pub Sep 1997 RE/SMG-030322QR SMG#2103.22 5.2.0 Phase 2+ ETS 300 930 Ed3 MS in idle mode OAP version RE/SMG-030322QR1 SMG#2203.22 5.2.1 Phase 2+ ETS 300 930 Ed3 MS in idle mode Pub Dec 1997 RE/SMG-030322QR1 SMG#2203.22 5.3.0 Phase 2+ ETS 300 930 Ed4 MS in idle mode OAP version RE/SMG-030322QR2 SMG#2603.22 6.0.0 R97 TS 100 930 MS in idle mode Pub July 1998 DTS/SMG-030322Q6 SMG#2603.22 6.1.0D R97 TS 100 930 MS in idle mode Unpublished DTS/SMG-030322Q6 SMG#2603.26 4.0.0 Phase 2 TC-TR 005 Multiband by 1 operator Unpublished DTR/SMG-030326P SMG#1503.26 4.1.0 Phase 2 TC-TR 005 Multiband by 1 operator Pub May 1996 DTR/SMG-030326P SMG#1803.26 4.2.0 Phase2 TC-TR 005 Multiband by 1 operator Unpublished DTR/SMG-030326P SMG#2203.26 4.3.0 Phase2 TR 101 266 Multiband by 1 operator Pub Apr 1998 DTR/SMG-

020326PR2SMG#23

03.26 5.0.0 Phase 2/2+ ETR 366 Multiband by 1 operator Pub Nov 1996 DTR/SMG-030326Q SMG#2003.26 5.1.0 Phase 2+ ETR 366 Ed2 Multiband by 1 operator Pub Aug 1997 RTR/SMG-

020326QR1SMG#22

03.26 5.2.0 Phase 2+ ETR 366 Ed2 Multiband by 1 operator Pub? RTR/SMG-020326QR1

SMG#23

03.30 4.2.0 Phase 2 ETR 103 Radio Net Planning Aspts Pub Oct 1993 DTR/SMG-020330P SMG#703.30 4.3.0 Phase 2 ETR 103 Ed2 Radio Net Planning Aspts Pub Feb 1995 RTR/SMG-020330Q-

1SMG#13

03.30 5.0.0 Phase 2/2+ ETR 364 Radio Net Planning Aspts Pub Nov 1996 DTR/SMG-020330Q SMG#2003.30 6.0.0 R97 TR 101 362 Radio Net Planning Aspts Unpublished DTR/SMG-020330Q6 SMG#2503.30 6.0.1 R97 TR 101 362 Radio Net Planning Aspts Pub July 1998 DTR/SMG-020330Q6 SMG#2603.31 7.0.0 R98 TS 101 xxx Fraud Info Gat FIGS Stg 2 Unpublished DTS/SMG-100331Q SMG#2603.32 5.0.0 Phase 2+ TS 101 109 Geo Area Discription Pub Nov 1997 DTS/SMG-030332Q SMG#2303.32 5.1.0 Phase 2+ TS 101 109 Geo Area Discription Pub July 1998 DTS/SMG-

030332QR1SMG#26

03.32 5.2.0 Phase 2+ TS 101 109 Geo Area Discription Pub Oct 1998 RTS/SMG-030332QR2

SMG#27

03.33 1.0.0 R98 TS 101 xxx Lawful intercept Stage 2 Draft DTS/SMG-100333Q SMG#27?

03.34 5.0.0 Phase 2+ TS 101 038 HSCSD Stage 2 Unpublished DTS/SMG-030334Q SMG#2103.34 5.0.1 Phase 2+ TS 101 038 HSCSD Stage 2 Pub Apr 1997 DTS/SMG-030334Q SMG#2103.34 5.1.0 Phase 2+ TS 101 038 HSCSD Stage 2 Pub July 1998 RTS/SMG-

030334QR1SMG#26

03.35 2.0.0 R98 TS 101 xxx Fraud Info Gat FIGS Stg 2 Draft DTS/SMG-100335Q7 SMG#2703.38 4.0.1 Phase 2 ETS 300 628 Alphabets & Language Pub Sep 1994 DE/SMG-040338P SMG#1003.38 5.0.0 Phase 2+ GTS 03.38 Alphabets & Language Pub Jan 1996 DGTS/SMG-040338Q SMG#1603.38 5.1.0 Phase 2+ GTS 03.38 Alphabets & Language Pub Mar 1996 RGTS/SMG-

040338QRSMG#17

03.38 5.2.0 Phase 2+ GTS 03.38 Alphabets & Language Pub May 1996 RGTS/SMG-040338QR1

SMG#18

03.38 5.3.0 Phase 2+ GTS 03.38 Alphabets & Language Pub July 1996 RGTS/SMG-040338QR2

SMG#19

03.38 5.4.0 Phase 2+ ETS 300 900 Alphabets & Language UAP version DE/SMG-040338QR3 SMG#2003.38 5.4.1 Phase 2+ ETS 300 900 Alphabets & Language Pub Apr 1997 DE/SMG-040338QR3 SMG#2003.38 5.5.0 Phase 2+ ETS 300 900 Ed2 Alphabets & Language OAP version RE/SMG-040338QR4 SMG#2103.38 5.5.1 Phase 2+ ETS 300 900 Ed2 Alphabets & Language Pub Sep 1997 RE/SMG-040338QR4 SMG#2103.38 5.6.0 Phase 2+ ETS 300 900 Ed3 Alphabets & Language OAP version RE/SMG-040338QR5 SMG#2203.38 5.6.1 Phase 2+ ETS 300 900 Ed3 Alphabets & Language Pub Jan 1998 RE/SMG-040338QR5 SMG#2203.38 6.0.0 R97 TS 100 900 Alphabets & Language Unpublished DTS/SMG-040338Q6 SMG#2503.38 6.0.1 R97 TS 100 900 Alphabets & Language Pub July 1998 DTS/SMG-040338Q6 SMG#2603.38 7.0.0 R98 TS 100 900 Alphabets & Language Unpublished DTS/SMG-040338Q7 SMG#2603.39 4.0.0 Phase 2 ETR 243 Inter proto SMSCs-SMEs Pub Nov 1995 DTR/SMG-040339P SMG#1603.39 5.0.0 Phase 2/2+ ETR 365 Inter proto SMSCs-SMEs Pub Nov 1996 DTR/SMG-040339Q SMG#2003.40 4.10.0 Phase 2 ETS 300 536 Am1 Tech realisa of SMS PtP Pub Mar 1995 RE/SMG-040340P SMG#03.40 4.11.0 Phase 2 ETS 300 536 Ed2 Tech realisa of SMS PtP Pub Jan 1996 RE/SMG-040340PR2 SMG#1503.40 4.12.0 Phase 2 ETS 300 536 Ed3 Tech realisa of SMS PtP Pub May 1996 RE/SMG-040340PR3 SMG#1603.40 4.13.0 Phase 2 ETS 300 536 Ed4 Tech realisa of SMS PtP Pub Oct 1996 RE/SMG-040340PR4 SMG#1803.40 4.9.1 Phase 2 ETS 300 536 Tech realisa of SMS PtP Pub Oct 1994 DE/SMG-040340P SMG#1103.40 5.0.0 Phase 2+ GTS 03.40 Tech realisa of SMS PtP Pub Jan 1996 DGTS/SMG-040340Q SMG#1603.40 5.1.0 Phase 2+ GTS 03.40 Tech realisa of SMS PtP Pub Mar 1996 RGTS/SMG-

040340QRSMG#17

03.40 5.2.0 Phase 2+ GTS 03.40 Tech realisa of SMS PtP Pub May 1996 RGTS/SMG-040340QR1

SMG#18

03.40 5.3.0 Phase 2+ GTS 03.40 Tech realisa of SMS PtP Pub July 1996 RGTS/SMG-040340QR2

SMG#19

03.40 5.4.0 Phase 2+ ETS 300 901 Tech realisa of SMS PtP UAP version DE/SMG-040340QR3 SMG#2003.40 5.4.1 Phase 2+ ETS 300 901 Tech realisa of SMS PtP Pub Apr 1997 DE/SMG-040340QR3 SMG#2003.40 5.5.0 Phase 2+ ETS 300 901 Ed2 Tech realisa of SMS PtP OAP version RE/SMG-040340QR4 SMG#21


Page 9


03.40 5.5.1 Phase 2+ ETS 300 901 Ed2 Tech realisa of SMS PtP Pub Sep 1997 RE/SMG-040340QR4 SMG#2103.40 5.6.0 Phase 2+ ETS 300 901 Ed3 Tech realisa of SMS PtP OAP version RE/SMG-040340QR5 SMG#2203.40 5.6.1 Phase 2+ ETS 300 901 Ed3 Tech realisa of SMS PtP Pub Jan 1998 RE/SMG-040340QR5 SMG#2203.40 5.7.0 Phase 2+ ETS 300 901 Ed4 Tech realisa of SMS PtP OAP version RE/SMG-040340QR6 SMG#2303.40 5.7.1 Phase 2+ ETS 300 901 Ed4 Tech realisa of SMS PtP Pub Oct 1998 RE/SMG-040340QR6 SMG#2303.40 5.8.0 Phase 2+ ETS 300 901 Ed5 Tech realisa of SMS PtP OAP version RE/SMG-040340QR7 SMG#2603.40 6.0.0 R97 TS 100 901 Tech realisa of SMS PtP Unpublished DTS/SMG-040340Q6 SMG#2503.40 6.1.0 R97 TS 100 901 Tech realisa of SMS PtP Pub July 1998 DTS/SMG-040340Q6 SMG#2603.40 6.1.0D R97 ETS 300 901 Ed4 Tech realisa of SMS PtP Unpublished RE/SMG-040340QR6 SMG#2403.40 6.2.0D R97 ETS 300 901 Ed4 Tech realisa of SMS PtP Unpublished RE/SMG-040340QR6 SMG#2403.40 7.0.0 R98 TS 100 901 Tech realisa of SMS PtP Unpublished DTS/SMG-040340Q7 SMG#2603.40 7.1.0 R98 TS 100 901 Tech realisa of SMS PtP Unpublished DTS/SMG-040340Q7 SMG#2703.41 4.10.0 Phase 2 ETS 300 537 Tech realisa of SMSCB Pub June 1995 DE/SMG-040341P SMG#1303.41 4.11.0 Phase 2 ETS 300 537 Ed2 Tech realisa of SMSCB Pub May 1996 RE/SMG-040341P SMG#1603.41 5.0.0 Phase 2+ GTS 03.41 Tech realisa of SMSCB Pub Jan 1996 DGTS/SMG-040341Q SMG#1603.41 5.1.0 Phase 2+ GTS 03.41 Tech realisa of SMSCB Pub Mar 1996 RGTS/SMG-

040341QRSMG#17

03.41 5.2.0 Phase 2+ GTS 03.41 Tech realisa of SMSCB Pub May 1996 RGTS/SMG-040341QR1

SMG#18

03.41 5.3.0 Phase 2+ GTS 03.41 Tech realisa of SMSCB Pub July 1996 RGTS/SMG-040341QR2

SMG#19

03.41 5.4.0 Phase 2+ ETS 300 902 Tech realisa of SMSCB UAP version DE/SMG-040341QR3 SMG#2003.41 5.4.1 Phase 2+ ETS 300 902 Tech realisa of SMSCB Pub Apr 1997 DE/SMG-040341QR3 SMG#2003.41 5.5.0 Phase 2+ ETS 300 902 Ed2 Tech realisa of SMSCB OAP version RE/SMG-040341QR4 SMG#2103.41 5.5.1 Phase 2+ ETS 300 902 Ed2 Tech realisa of SMSCB Pub Sep 1997 RE/SMG-040341QR4 SMG#2103.41 5.6.0 Phase 2+ ETS 300 902 Ed3 Tech realisa of SMSCB OAP version RE/SMG-040341QR5 SMG#2203.41 5.6.1 Phase 2+ ETS 300 902 Ed3 Tech realisa of SMSCB Pub Jan 1998 RE/SMG-040341QR5 SMG#2203.41 5.7.0 Phase 2+ ETS 300 902 Ed4 Tech realisa of SMSCB Unpublished RE/SMG-040341QR6 SMG#2303.41 5.8.0 Phase 2+ ETS 300 902 Ed4 Tech realisa of SMSCB OAP version RE/SMG-040341QR6 SMG#2403.41 5.8.1 Phase 2+ ETS 300 902 Ed4 Tech realisa of SMSCB Pub June 1998 ? RE/SMG-040341QR6 SMG#2403.41 5.9.0 Phase 2+ ETS 300 902 Ed5 Tech realisa of SMSCB OAP version RE/SMG-040341QR7 SMG#2603.41 6.0.0 R97 TS 100 902 Tech realisa of SMSCB Unpublished DTS/SMG-040341Q6 SMG#2503.41 6.1.0 R97 TS 100 902 Tech realisa of SMSCB Pub July 1998 DTS/SMG-040341Q6 SMG#2603.42 5.0.0 Phase 2+ TS 101 032 Compression algo SMS Pub Mar 1997 DTS/SMG-040342Q SMG#2103.42 5.1.0 Phase 2+ TS 101 032 Compression algo SMS Pub Aug 1997 RTS/SMG-040342QR SMG#2203.42 5.2.0 Phase 2+ TS 101 032 Compression algo SMS Pub Nov 1997 RTS/SMG-

040342QR1SMG#23

03.42 7.0.0 R98 TS 101 032 Compression algo SMS Unpublished RTS/SMG-040342QR1

SMG#26

03.43 4.1.2 Phase 2 ETR 104 Support of videotext Pub Oct 1993 DTR/SMG-040343P SMG#703.43 5.0.0 Phase 2/2+ ETR 352 Support of videotext Pub Nov 1996 DTR/SMG-040343Q SMG#2003.44 4.0.1 Phase 2 ETR 105 Support of teletext Pub Oct 1993 DTR/SMG-040344P SMG#703.44 5.0.0 Phase 2/2+ ETR 353 Support of teletext Pub Nov 1996 DTR/SMG-040344Q SMG#2003.45 4.4.2 Phase 2 ETS 300 538 Fax Group 3 transparent Pub Oct 1994 DE/SMG-040345P SMG#1103.45 4.5.0 Phase 2 ETS 300 538 Ed2 Fax Group 3 transparent Pub Sep 1995 RE/SMG-040345P SMG#1403.45 5.0.0 Phase 2/2+ ETS 300 931 Fax Group 3 transparent UAP version DE/SMG-040345Q SMG#2003.45 5.0.1 Phase 2+ ETS 300 931 Fax Group 3 transparent Pub Apr 1997 DE/SMG-040345Q SMG#2003.45 5.1.0 Phase 2+ ETS 300 931 Ed2 Fax Group 3 transparent OAP version RE/SMG-040345QR SMG#2103.45 5.1.1 Phase 2+ ETS 300 931 Ed2 Fax Group 3 transparent Pub Aug 1997 RE/SMG-040345QR SMG#2103.45 5.2.0 Phase 2+ ETS 300 931 Ed3 Fax Group 3 transparent OAP version RE/SMG-040345QR1 SMG#2203.45 5.2.1 Phase 2+ ETS 300 931 Ed3 Fax Group 3 transparent Pub Jan 1998 RE/SMG-040345QR1 SMG#2203.46 4.1.2 Phase 2 ETS 300 539 Fax Gp 3 non-transparent Pub Feb 1995 DE/SMG-040346P SMG#1103.46 5.0.0 Phase 2/2+ GTS 03.46 Fax Gp 3 non-transparent Pub Nov 1996 DGTS/SMG-040346Q SMG#2003.47 4.2.0 Phase 2 ETR 106 Int conn e.g CS & MSC Pub Oct 1993 DTR/SMG-040347P SMG#803.47 4.3.1 Phase 2 ETR 106 Ed 2 Int conn e.g CS & MSC Pub Feb 1995 RTR/SMG-040347P SMG#03.47 4.4.0 Phase 2 ETR 106 Ed 3 Int conn e.g CS & MSC Pub May 1996 RTR/SMG-

040347PR2SMG#18

03.47 5.0.0 Phase 2/2+ ETR 354 Int conn e.g CS & MSC Pub Nov 1996 DTR/SMG-040347Q SMG#2003.48 5.0.0 Phase 2+ TS 101 181 Tool Kit Security Stage 2 Unpublished DTS/SMG-090348Q6 SMG#2403.48 6.0.0 R97 TS 101 181 Tool Kit Security Stage 2 Pub Apr 1998 DTS/SMG-090348Q6 SMG#2503.48 6.1.0 R97 TS 101 181 Tool Kit Security Stage 2 Pub July 1998 RTS/SMG-

090348Q6R1SMG#26

03.49 4.2.0 Phase 2 ETR 107 Int conn e.g CBC & BSC Pub Oct 1993 DTR/SMG-040349P SMG#803.49 4.5.0 Phase 2 ETR 107 Ed2 Int conn e.g CBC & BSC Pub Apr 1995 RTR/SMG-040349P SMG#1303.49 4.6.0 Phase 2 ETR 107 Ed3 Int conn e.g CBC & BSC Pub Nov 1995 RTR/SMG-

040349PR2SMG#16

03.49 5.0.0 Phase 2+ GTS 03.49 Int conn e.g CBC & BSC Pub Jan 1996 DGTS/SMG-040349Q SMG#1603.49 5.1.0 Phase 2+ GTS 03.49 Int conn e.g CBC & BSC Pub May 1996 RGTS/SMG-

040349QRSMG#18


Page 10


03.49 5.2.0 Phase 2+ GTS 03.49 Int conn e.g CBC & BSC Pub July 1996 RGTS/SMG-040349QR1

SMG#19

03.49 5.3.0 Phase 2+ GTS 03.49 Int conn e.g CBC & BSC Pub Nov 1996 RGTS/SMG-040349QR2

SMG#20

03.49 5.4.0 Phase 2+ GTS 03.49 Int conn e.g CBC & BSC Pub Apr 1997 RGTS/SMG-040349QR3

SMG#21

03.49 5.5.0 Phase 2+ GTS 03.49 Int conn e.g CBC & BSC Pub Aug 1997 RGTS/SMG-040349QR4

SMG#22

03.49 5.6.0 Phase 2+ GTS 03.49 Int conn e.g CBC & BSC Unpublished RGTS/SMG-040349QR5

SMG#23

03.49 5.7.0 Phase 2+ GTS 03.49 Int conn e.g CBC & BSC Pub July 1998 RGTS/SMG-040349QR5

SMG#24

03.49 6.0.0 R97 TS 101 368 Int conn e.g CBC & BSC Unpublished DTS/SMG-040349Q6 SMG#2503.49 6.1.0 R97 TS 101 368 Int conn e.g CBC & BSC Pub July 1998 DTS/SMG-040349Q6 SMG#2603.50 4.1.2 Phase 2 ETS 300 540 Trans planning Aspects Pub Feb 1995 DE/SMG-020350P SMG#903.50 4.2.0 Phase 2 ETS 300 540 Ed2 Trans planning Aspects Pub Jan 1996 RE/SMG-020350P SMG#1503.50 4.3.0 Phase 2 ETS 300 540 Ed3 Trans planning Aspects OAP version RE/SMG-020350PR1 SMG#2403.50 4.3.1 Phase 2 ETS 300 540 Ed3 Trans planning Aspects Pub June 1998 RE/SMG-020350PR1 SMG#2403.50 4.4.0 Phase 2 ETS 300 540 Ed4 Trans planning Aspects OAP version RE/SMG-110350PR2 SMG#2503.50 4.4.1 Phase 2 ETS 300 540 Ed4 Trans planning Aspects Pub Oct 1998 RE/SMG-110350PR2 SMG#2503.50 4.5.0 Phase 2 ETS 300 540 Ed5 Trans planning Aspects OAP version RE/SMG-110350PR3 SMG#2703.50 5.0.0 Phase 2+ GTS 03.50 Trans planning Aspects Pub Sep 1996 DGTS/SMG-020350Q SMG#1703.50 5.0.1 Phase 2+ ETS 300 903 Trans planning Aspects UAP version DE/SMG-020350Q SMG#2003.50 5.0.2 Phase 2+ ETS 300 903 Trans planning Aspects Pub Apr 1997 DE/SMG-020350Q SMG#2003.50 5.1.0 Phase 2+ ETS 300 903 Ed2 Trans planning Aspects OAP version RE/SMG-110350QR1 SMG#2503.50 5.1.0 Phase 2+ ETS 300 903 Trans planning Aspects Unpublished DE/SMG-020350Q SMG#2403.50 5.1.1 Phase 2+ ETS 300 903 Ed2 Trans planning Aspects Pub Oct 1998 RE/SMG-110350QR1 SMG#2503.50 5.2.0 Phase 2+ ETS 300 903 Ed3 Trans planning Aspects OAP version RE/SMG-110350QR2 SMG#2703.53 7.0.0 R98 TS 101 xxx TFO Stage 2 Unpublished DTS/SMG-030353Q7 SMG#2503.54 5.0.0 Phase 2+ TS 101 252 Shared IWF (SIWF) Pub July 1997 DTS/SMG-040354Q SMG#2203.54 5.1.0 Phase 2+ TS 101 252 Shared IWF (SIWF) Pub Nov 1997 RTS/SMG-040354QR SMG#2303.54 5.2.0 Phase 2+ TS 101 252 Shared IWF (SIWF) Pub Jan 1998 RTS/SMG-

040354QR1SMG#24

03.56 1.0.0 R98 TS 101 xxx CTS Stage 2 Draft DTS/SMG-120356Q7 SMG#27?

03.57 1.0.1 R98 TS 101 xxx MExE Stage 2 Draft DTS/SMG-040357Q SMG#27?

03.58 5.0.0 Phase 2+ TR 101 110 Handsfree MS test Pub Nov 1997 DTR/SMG-110358Q SMG#2303.58 6.0.0 Phase 2+ TR 101 110 Handsfree MS test Unpublished RTR/SMG-110358Q SMG#2303.58 6.0.1 R97 TR 101 110 Handsfree MS test Pub July 1998 RTR/SMG-110358Q6 SMG#2603.60 5.0.0 Phase 2+ EN 301 344 GPRS Stage 2 Unpublished DEN/SMG-030360Q6 SMG#2203.60 5.1.0 Phase 2+ EN 301 344 GPRS Stage 2 Unpublished DEN/SMG-030360Q6 SMG#2303.60 5.2.0 Phase 2+ EN 301 344 GPRS Stage 2 Unpublished DEN/SMG-030360Q6 SMG#2403.60 6.0.0 R97 EN 301 344 GPRS Stage 2 Unpublished DEN/SMG-030360Q6 SMG#2503.60 6.1.0 R97 EN 301 344 GPRS Stage 2 Unpublished DEN/SMG-030360Q6 SMG#2603.60 6.1.1 R97 EN 301 344 GPRS Stage 2 PE version DEN/SMG-030360Q6 SMG#2603.60 6.2.0 R97 EN 301 344 GPRS Stage 2 Unpublished DEN/SMG-030360Q6 SMG#2703.61 0.7.0 Phase 2+ EN 301 xxx GPRS PTM-M Stage 2 Draft DEN/SMG-040361Q6 SMG#29

?03.63 5.0.0 Phase 2+ GTS 03.63 PDS Stage 2 Pub Jan 1996 DGTS/SMG-030363Q SMG#1603.63 5.1.0 Phase 2+ GTS 03.63 PDS Stage 2 Pub May 1996 RGTS/SMG-

030363QRSMG#18

03.64 5.0.0 Phase 2+ EN 301 350 GPRS Radio Int Stage 2 Unpublished DEN/SMG-030364Q6 SMG#2203.64 5.1.0 Phase 2+ EN 301 350 GPRS Radio Int Stage 2 Unpublished DEN/SMG-030364Q6 SMG#2303.64 5.2.0 Phase 2+ EN 301 350 GPRS Radio Int Stage 2 Unpublished DEN/SMG-030364Q6 SMG#2403.64 6.0.0 R97 TS 101 350 GPRS Radio Int Stage 2 Unpublished DEN/SMG-020364Q6 SMG#2503.64 6.0.1 R97 TS 101 350 GPRS Radio Int Stage 2 Pub Aug 1998 DTS/SMG-020364Q6 SMG#2603.64 6.1.0 R97 TS 101 350 GPRS Radio Int Stage 2 Pub Oct 1998 RTS/SMG-

020364Q6R1SMG#27

03.67 5.0.0 Phase 2+ GTS 03.67 eMLPP Stage 2 Pub Jan 1996 DGTS/SMG-030367Q SMG#1603.67 5.1.0 Phase 2+ ETS 300 932 eMLPP Stage 2 UAP version DE/SMG-030367QR SMG#2003.67 5.1.1 Phase 2+ ETS 300 932 eMLPP Stage 2 Pub May 1997 DE/SMG-030367QR SMG#2003.68 5.0.0 Phase 2+ GTS 03.68 VGCS Stage 2 Pub Jan 1996 DGTS/SMG-030368Q SMG#1603.68 5.1.0 Phase 2+ GTS 03.68 VGCS Stage 2 Pub May 1996 RGTS/SMG-

030368QRSMG#18

03.68 5.1.1 Phase 2+ ETS 300 933 VGCS Stage 2 UAP version DE/SMG-030368QR SMG#2003.68 5.1.2 Phase 2+ ETS 300 933 VGCS Stage 2 Pub May 1997 DE/SMG-030368QR SMG#2003.68 5.2.0 Phase 2+ ETS 300 933 Ed2 VGCS Stage 2 OAP version RE/SMG-030368QR1 SMG#2103.68 5.2.1 Phase 2+ ETS 300 933 Ed2 VGCS Stage 2 Pub Aug 1997 RE/SMG-030368QR1 SMG#2103.68 5.3.0 Phase 2+ ETS 300 933 Ed3 VGCS Stage 2 OAP version RE/SMG-030368QR2 SMG#23


Page 11


03.68 5.3.1 Phase 2+ ETS 300 933 Ed3 VGCS Stage 2 Pub Mar 1998 RE/SMG-030368QR2 SMG#2303.68 5.4.0 Phase 2+ ETS 300 933 Ed4 VGCS Stage 2 OAP version RE/SMG-030368QR3 SMG#2403.68 5.4.1 Phase 2+ ETS 300 933 Ed4 VGCS Stage 2 Pub July 1998? RE/SMG-030368QR3 SMG#2403.68 5.5.0 Phase 2+ ETS 300 933 Ed5 VGCS Stage 2 OAP version RE/SMG-030368QR4 SMG#2603.68 6.0.0 R97 TS 100 933 VGCS Stage 2 Unpublished DTS/SMG-030368Q6 SMG#2503.68 6.0.1 R97 TS 100 933 VGCS Stage 2 Unpublished DTS/SMG-030368Q6 SMG#2603.68 6.1.0 R97 TS 100 933 VGCS Stage 2 Pub July 1998 DTS/SMG-030368Q6 SMG#2603.69 5.0.0 Phase 2+ GTS 03.69 VBS Stage 2 Pub Jan 1996 DGTS/SMG-030369Q SMG#1603.69 5.1.0 Phase 2+ GTS 03.69 VBS Stage 2 Pub May 1996 RGTS/SMG-

030369QRSMG#18

03.69 5.1.1 Phase 2+ ETS 300 934 VBS Stage 2 UAP version DE/SMG-030369QR SMG#2003.69 5.1.2 Phase 2+ ETS 300 934 VBS Stage 2 Pub May 1997 DE/SMG-030369QR SMG#2003.69 5.2.0 Phase 2+ ETS 300 934 Ed2 VBS Stage 2 OAP version RE/SMG-030369QR1 SMG#2103.69 5.2.1 Phase 2+ ETS 300 934 Ed2 VBS Stage 2 Pub Aug 1997 RE/SMG-030369QR1 SMG#2103.69 5.3.0 Phase 2+ ETS 300 934 Ed3 VBS Stage 2 OAP version RE/SMG-030369QR2 SMG#2303.69 5.3.1 Phase 2+ ETS 300 934 Ed3 VBS Stage 2 Pub Mar 1998 RE/SMG-030369QR2 SMG#2303.69 5.4.0 Phase 2+ ETS 300 934 Ed4 VBS Stage 2 OAP version RE/SMG-030369QR3 SMG#2403.69 5.4.1 Phase 2+ ETS 300 934 Ed4 VBS Stage 2 Pub Oct 1998 RE/SMG-030369QR3 SMG#2403.69 5.5.0 Phase 2+ ETS 300 934 Ed5 VBS Stage 2 OAP version RE/SMG-030369QR4 SMG#2603.69 6.0.0 R97 TS 100 934 VBS Stage 2 Unpublished DTS/SMG-030369Q6 SMG#2503.69 6.0.1 R97 TS 100 934 VBS Stage 2 Unpublished DTS/SMG-030369Q6 SMG#2603.69 6.1.0 R97 TS 100 934 VBS Stage 2 Pub July 1998 DTS/SMG-030369Q6 SMG#2603.70 4.0.3 Phase 2 ETS 300 541 Routeing calls via PDN Pub Sep 1994 DE/SMG-040370P SMG#803.70 5.0.0 Phase 2/2+ GTS 03.70 Routeing calls via PDN Pub Nov 1996 DGTS/SMG-040370Q SMG#2003.78 5.0.0 Phase 2+ TS 101 044 CAMEL Stage 2 Unpublished DTS/SMG-030378Q SMG#2103.78 5.0.1 Phase 2+ TS 101 044 CAMEL Stage 2 Pub Apr 1997 DTS/SMG-030378Q SMG#2103.78 5.1.0 Phase 2+ TS 101 044 CAMEL Stage 2 Pub Aug 1997 RTS/SMG-

030378QR1SMG#22

03.78 5.2.0 Phase 2+ TS 101 044 CAMEL Stage 2 Pub Nov 1997 RTS/SMG-030378QR2

SMG#23

03.78 5.3.0 Phase 2+ TS 101 044 CAMEL Stage 2 Unpublished RTS/SMG-030378QR3

SMG#24


SMG#24

03.78 5.3.2 Phase 2+ TS 101 044 CAMEL Stage 2 Pub Jan 1998 RTS/SMG-030378QR3

SMG#24


SMG#25

03.78 5.5.0 Phase 2+ TS 101 044 CAMEL Stage 2 Pub July 1998 RTS/SMG-030378QR4

SMG#26

03.78 5.6.0 Phase 2+ TS 101 044 CAMEL Stage 2 Pub Nov 1998? RTS/SMG-030378QR5

SMG#27

03.78 6.0.0 R97 TS 101 441 CAMEL phase2, Stage 2 Unpublished RTS/SMG-030378Q6 SMG#2503.78 6.1.0 R97 TS 101 441 CAMEL phase2, Stage 2 Unpublished RTS/SMG-030378Q6 SMG#2603.78 6.1.1 R97 TS 101 441 CAMEL phase2, Stage 2 Pub Aug 1998 RTS/SMG-030378Q6 SMG#2603.78 6.2.0 R97 TS 101 441 CAMEL phase2, Stage 2 Pub Nov 1998? RTS/SMG-

030378Q6R1SMG#27

03.79 5.0.0 Phase 2+ TS 101 045 SOR Unpublished DTS/SMG-030379Q SMG#2103.79 5.0.1 Phase 2+ TS 101 045 SOR Pub Apr 1997 DTS/SMG-030379Q SMG#2103.79 5.1.0 Phase 2+ TS 101 045 SOR Pub Aug 1997 RTS/SMG-

030379QR1SMG#22

03.79 5.2.0 Phase 2+ TS 101 045 SOR Pub Jan 1998 RTS/SMG-030379QR2

SMG#24

03.79 5.3.0 Phase 2+ TS 101 045 SOR Unpublished RTS/SMG-030379QR3

SMG#25

03.79 5.4.0 Phase 2+ TS 101 045 SOR Pub Nov 1998? RTS/SMG-030379QR3

SMG#27

03.81 4.5.1 Phase 2 ETS 300 542 Line Identity SS stage 2 Pub Feb 1995 DE/SMG-030381P SMG#1203.81 4.6.0 Phase 2 ETS 300 542 Ed2 Line Identity SS stage 2 UAP version RE/SMG-030381P SMG#1903.81 4.6.1 Phase 2 ETS 300 542 Ed2 Line Identity SS stage 2 Pub Mar 1997 RE/SMG-030381P SMG#1903.81 4.7.0 Phase 2 ETS 300 542 Ed3 Line Identity SS stage 2 Unpublished RE/SMG-030381PR1 SMG#2403.81 4.8.0 Phase 2 ETS 300 542 Ed3 Line Identity SS stage 2 OAP version RE/SMG-030381PR1 SMG#2603.81 5.0.0 Phase 2/2+ GTS 03.81 Line Identity SS stage 2 Pub Dec 1996 DGTS/SMG-030381Q SMG#2003.81 5.1.0 Phase 2+ GTS 03.81 Line Identity SS stage 2 Pub Apr 1998 RGTS/SMG-

030381QR1SMG#24

03.81 5.2.0 Phase 2+ GTS 03.81 Line Identity SS stage 2 Pub Aug 1998 RGTS/SMG-030381QR2

SMG#26

03.82 4.7.1 Phase 2 ETS 300 543 Call Forwarding SS stg 2 Pub Feb 1995 DE/SMG-030382P SMG#1203.82 4.8.0 Phase 2 ETS 300 543 Ed2 Call Forwarding SS stg 2 UAP version RE/SMG-030382P SMG#1803.82 4.8.1 Phase 2 ETS 300 543 Ed2 Call Forwarding SS stg 2 Pub Jan 1997 RE/SMG-030382P SMG#18


Page 12


03.82 5.0.0 Phase 2/2+ GTS 03.82 Call Forwarding SS stg 2 Pub Dec 1996 DGTS/SMG-030382Q SMG#2003.83 4.4.1 Phase 2 ETS 300 544 CW & HOLD SS stg 2 Pub Feb 1995 DE/SMG-030383P SMG#1203.83 5.0.0 Phase 2/2+ GTS 03.83 CW & HOLD SS stg 2 Pub Dec 1996 DGTS/SMG-030383Q SMG#2003.84 4.4.1 Phase 2 ETS 300 545 MultiParty SS stage 2 Pub Feb 1995 DE/SMG-030384P SMG#1203.84 5.0.0 Phase 2/2+ GTS 03.84 MultiParty SS stage 2 Pub Dec 1996 DGTS/SMG-030384Q SMG#2003.85 4.1.2 Phase 2 ETS 300 546 CUG SS stage 2 Pub Feb 1995 DE/SMG-030385P SMG#803.85 4.2.0 Phase 2 ETS 300 546 Ed2 CUG SS stage 2 Pub Jan 1996 RE/SMG-030385P SMG#1503.85 4.2.1 Phase 2 ETS 300 546 Ed2 CUG SS stage 2 Unpublished RE/SMG-030385P SMG#1503.85 5.0.0 Phase 2/2+ GTS 03.85 CUG SS stage 2 Pub Dec 1996 DGTS/SMG-030385Q SMG#2003.86 4.6.1 Phase 2 ETS 300 547 Advice of Charge SS stg 2 Pub Feb 1995 DE/SMG-030386P SMG#1203.86 5.0.0 Phase 2/2+ ETS 300 935 Advice of Charge SS stg 2 UAP version DE/SMG-030386Q SMG#2003.86 5.0.1 Phase 2/2+ ETS 300 935 Advice of Charge SS stg 2 Pub May 1997 DE/SMG-030386Q SMG#2003.88 4.6.1 Phase 2 ETS 300 548 Call Barring SS stage 2 Pub Feb 1995 DE/SMG-030388P SMG#1203.88 5.0.0 Phase 2/2+ GTS 03.88 Call Barring SS stage 2 Pub Dec 1996 DGTS/SMG-030388Q SMG#2003.90 4.0.3 Phase 2 ETS 300 549 USSD stage 2 Pub Feb 1995 DE/SMG-030390P SMG#803.90 4.1.0 Phase 2 ETS 300 549 Ed2 USSD stage 2 UAP version RE/SMG-030390P SMG#1603.90 4.1.1 Phase 2 ETS 300 549 Ed2 USSD stage 2 Pub Aug 1996 RE/SMG-030390P SMG#1603.90 5.0.0 Phase 2/2+ GTS 03.90 USSD stage 2 Pub Dec 1996 DGTS/SMG-030390Q SMG#2003.91 5.0.0 Phase 2+ GTS 03.91 ECT stage 2 Pub Jan 1996 DGTS/SMG-030391Q SMG#1603.91 5.0.1 Phase 2+ GTS 03.91 ECT stage 2 Pub May 1996 RGTS/SMG-

030391QRSMG#18

03.91 5.0.2 Phase 2+ GTS 03.91 ECT stage 2 Pub July 1996 RGTS/SMG-030391QR1

SMG#19

03.93 6.0.0 R97 TS 101 283 CCBS stage 2 Unpublished DTS/SMG-030393Q6 SMG#2503.93 6.1.0 R97 TS 101 283 CCBS stage 2 Pub July 1998 DTS/SMG-030393Q6 SMG#2603.93 6.2.0 R97 TS 101 283 CCBS stage 2 Pub Oct 1998 RTS/SMG-

030393Q6R1SMG#27

03.96 5.0.0 Phase 2+ TS 101 395 CNAP stage 2 Unpublished DTS/SMG-030396Q6 SMG#2403.96 6.0.0 R97 TS 101 395 CNAP stage 2 Unpublished DTS/SMG-030396Q6 SMG#2403.96 6.0.1 R97 TS 101 395 CNAP stage 2 Pub Oct 1998 DTS/SMG-030396Q6 SMG#2704.01 4.0.4 Phase 2 ETS 300 550 MS-BSS inter Gen & prcpl Pub Sep 1994 DE/SMG-030401P SMG#704.01 5.0.0 Phase 2/2+ GTS 04.01 MS-BSS inter Gen & prcpl Pub Nov 1996 DGTS/SMG-030401Q SMG#2004.02 4.0.4 Phase 2 ETS 300 551 PLMN Access ref con Pub Sep 1994 DE/SMG-030402P SMG#704.02 5.0.0 Phase 2+ GTS 04.02 PLMN Access ref con Pub May 1996 DGTS/SMG-030402Q SMG#1804.03 4.1.1 Phase 2 ETS 300 552 MS-BSS Interface Ch Acc cap Pub Sep 1994 DE/SMG-030403P SMG#1004.03 5.0.0 Phase 2+ GTS 04.03 MS-BSS Interface Ch Acc cap Pub May 1996 DGTS/SMG-030403Q SMG#1804.03 5.1.0 Phase 2+ GTS 04.03 MS-BSS Interface Ch Acc cap Pub Apr 1997 RGTS/SMG-

030403QRSMG#21

04.03 5.2.0 Phase 2+ GTS 04.03 MS-BSS Interface Ch Acc cap Pub Aug 1997 RGTS/SMG-030403QR1

SMG#22

04.03 5.3.0 Phase 2+ GTS 04.03 MS-BSS Interface Ch Acc cap Unpublished RGTS/SMG-030403QR1

SMG#24

04.03 6.0.0 R97 TS 100 552 MS-BSS Interface Ch Acc cap Pub Aug 1998 DTS/SMG-030403Q6 SMG#2504.04 4.0.4 Phase 2 ETS 300 553 Layer 1 Gen requirements Pub Sep 1994 DE/SMG-030404P SMG#704.04 5.0.0 Phase 2/2+ ETS 300 936 Layer 1 Gen requirements UAP version DE/SMG-030404Q SMG#2004.04 5.0.1 Phase 2/2+ ETS 300 936 Layer 1 Gen requirements Pub Apr 1997 DE/SMG-030404Q SMG#2004.04 5.1.0 Phase 2+ ETS 300 936 Ed2 Layer 1 Gen requirements Unpublished RE/SMG-030404QR1 SMG#2404.04 6.0.0 R97 TS 100 936 Layer 1 Gen requirements Pub Aug 1998 DTS/SMG-030404Q6 SMG#2504.05 4.0.3 Phase 2 ETS 300 554 DL Layer Gen aspects Pub Sep 1994 DE/SMG-030405P SMG#704.05 5.0.0 Phase 2/2+ ETS 300 937 DL Layer Gen aspects UAP version DE/SMG-030405Q SMG#2004.05 5.0.1 Phase 2/2+ ETS 300 937 DL Layer Gen aspects Pub Apr 1997 DE/SMG-030405Q SMG#2004.06 4.4.0 Phase 2 ETS 300 555 MS-BSS DL Layer Pub Sep 1994 DE/SMG-030406P SMG#1104.06 5.0.0 Phase 2/2+ ETS 300 938 MS-BSS DL Layer UAP version DE/SMG-030406Q SMG#2004.06 5.0.1 Phase 2/2+ ETS 300 938 MS-BSS DL Layer Pub Apr 1997 DE/SMG-030406Q SMG#2004.06 5.1.0 Phase 2+ ETS 300 938 Ed2 MS-BSS DL Layer OAP version RE/SMG-030406QR SMG#2104.06 5.1.1 Phase 2+ ETS 300 938 Ed2 MS-BSS DL Layer Pub Sep 1997 RE/SMG-030406QR SMG#2104.06 5.2.0 Phase 2+ ETS 300 938 Ed3 MS-BSS DL Layer OAP version RE/SMG-030406QR1 SMG#2504.06 5.2.1 Phase 2+ ETS 300 938 Ed3 MS-BSS DL Layer Pub Oct 1998 RE/SMG-030406QR1 SMG#2504.07 4.3.1 Phase 2 ETS 300 556 Mob Radio int sig L3 Gen Pub Feb 1995 DE/SMG-030407P SMG#1204.07 5.0.0 Phase 2+ GTS 04.07 Mob Radio int sig L3 Gen Pub Jan 1996 DGTS/SMG-030407Q SMG#1604.07 5.1.0 Phase 2+ GTS 04.07 Mob Radio int sig L3 Gen Pub Mar 1996 RGTS/SMG-

030407QRSMG#17

04.07 5.1.1 Phase 2+ ETS 300 939 Mob Radio int sig L3 Gen UAP version DE/SMG-030407QR SMG#2004.07 5.1.2 Phase 2+ ETS 300 939 Mob Radio int sig L3 Gen Pub Apr 1997 DE/SMG-030407QR SMG#2004.07 5.2.0 Phase 2+ ETS 300 939 Ed2 Mob Radio int sig L3 Gen OAP version RE/SMG-030407QR1 SMG#2104.07 5.2.1 Phase 2+ ETS 300 939 Ed2 Mob Radio int sig L3 Gen Pub Dec 1997 RE/SMG-030407QR1 SMG#2104.07 5.3.0 Phase 2+ ETS 300 939 Ed3 Mob Radio int sig L3 Gen Unpublished RE/SMG-030407QR1 SMG#2404.07 6.0.0 R97 TS 100 939 Mob Radio int sig L3 Gen Unpublished DTS/SMG-030407Q6 SMG#2504.07 6.1.0 R97 TS 100 939 Mob Radio int sig L3 Gen Pub July 1998 DTS/SMG-030407Q6 SMG#26


Page 13


04.07 6.2.0 R97 TS 100 939 Mob Radio int sig L3 Gen Unpublished RTS/SMG-030407Q6R1

SMG#27

04.07 6.2.1 R97 TS 100 939 Mob Radio int sig L3 Gen Pub Nov 1998? RTS/SMG-030407Q6R1

SMG#27

04.08 3.14.0 Phase 1 I-ETS 300 022-1 Mob Radio Interface L3 Pub Mar 1998 DI/SMG-030408-1R1 SMG#2104.08 4.10.0 Phase 2 ETS 300 557 Mob Radio Interface L3 Pub Feb 1995 DE/SMG-030408P SMG#1204.08 4.11.0 Phase 2 ETS 300 557 Ed2 Mob Radio Interface L3 Pub Oct 1995 RE/SMG-030408P SMG#1404.08 4.12.0 Phase 2 ETS 300 557 Ed3 Mob Radio Interface L3 Pub Jan 1996 RE/SMG-030408PR2 SMG#1504.08 4.13.0 Phase 2 ETS 300 557 Ed4 Mob Radio Interface L3 Pub May 1996 RE/SMG-030408PR3 SMG#1604.08 4.14.0 Phase 2 ETS 300 557 Ed5 Mob Radio Interface L3 Pub Sep 1996 RE/SMG-030408PR4 SMG#1704.08 4.15.0 Phase 2 ETS 300 557 Ed6 Mob Radio Interface L3 Pub Oct 1996 RE/SMG-030408PR5 SMG#1804.08 4.16.0 Phase 2 ETS 300 557 Ed7 Mob Radio Interface L3 UAP version RE/SMG-030408PR6 SMG#1904.08 4.16.1 Phase 2 ETS 300 557 Ed7 Mob Radio Interface L3 Pub Jan 1997 RE/SMG-030408PR6 SMG#1904.08 4.17.0 Phase 2 ETS 300 557 Ed8 Mob Radio Interface L3 UAP version RE/SMG-030408PR7 SMG#2004.08 4.17.1 Phase 2 ETS 300 557 Ed8 Mob Radio Interface L3 Pub Apr 1997 RE/SMG-030408PR7 SMG#2004.08 4.18.0 Phase 2 ETS 300 557 Ed9 Mob Radio Interface L3 Unpublished RE/SMG-030408PR8 SMG#2104.08 4.19.0 Phase 2 ETS 300 557 Ed9 Mob Radio Interface L3 Unpublished RE/SMG-030408PR8 SMG#2204.08 4.19.1 Phase 2 ETS 300 557 Ed9 Mob Radio Interface L3 OAP version RE/SMG-030408PR8 SMG#2204.08 4.19.2 Phase 2 ETS 300 557 Ed9 Mob Radio Interface L3 Pub Dec 1997 RE/SMG-030408PR8 SMG#2204.08 4.20.0 Phase 2 ETS 300 557

Ed10Mob Radio Interface L3 Unpublished RE/SMG-030408PR9 SMG#23

04.08 4.21.0 Phase 2 ETS 300 557Ed10

Mob Radio Interface L3 OAP version RE/SMG-030408PR9 SMG#24

04.08 4.21.1 Phase 2 ETS 300 557Ed10

Mob Radio Interface L3 Pub June 1998 RE/SMG-030408PR9 SMG#24

04.08 4.22.0 Phase 2 ETS 300 557Ed11

Mob Radio Interface L3 OAP version RE/SMG-030408PRA SMG#25

04.08 4.22.1 Phase 2 ETS 300 557Ed11

Mob Radio Interface L3 Pub Oct 1998 RE/SMG-030408PRA SMG#25

04.08 5.0.0 Phase 2+ GTS 04.08 Mob Radio Interface L3 Pub Jan 1996 DGTS/SMG-030408Q SMG#1604.08 5.1.0 Phase 2+ GTS 04.08 Mob Radio Interface L3 Pub Mar 1996 RGTS/SMG-

030408QRSMG#17

04.08 5.10.0 Phase 2+ ETS 300 940 Ed4 Mob Radio Interface L3 OAP version RE/SMG-020408QR6 SMG#2604.08 5.2.0 Phase 2+ GTS 04.08 Mob Radio Interface L3 Unpublished RGTS/SMG-

030408QR1SMG#18

04.08 5.3.0 Phase 2+ GTS 04.08 Mob Radio Interface L3 Pub July 1996 RGTS/SMG-030408QR2

SMG#19

04.08 5.4.0 Phase 2+ ETS 300 940 Mob Radio Interface L3 UAP version DE/SMG-030408QR3 SMG#2004.08 5.4.1 Phase 2+ ETS 300 940 Mob Radio Interface L3 Pub Apr 1997 DE/SMG-030408QR3 SMG#2004.08 5.5.0 Phase 2+ ETS 300 940 Ed2 Mob Radio Interface L3 Unpublished RE/SMG-030408QR4 SMG#2104.08 5.6.0 Phase 2+ ETS 300 940 Ed2 Mob Radio Interface L3 Unpublished RE/SMG-030408QR4 SMG#2204.08 5.6.1 Phase 2+ ETS 300 940 Ed2 Mob Radio Interface L3 Unpublished RE/SMG-030408QR4 SMG#2204.08 5.6.2 Phase 2+ ETS 300 940 Ed2 Mob Radio Interface L3 OAP version RE/SMG-030408QR4 SMG#2204.08 5.6.3 Phase 2+ ETS 300 940 Ed2 Mob Radio Interface L3 Pub Feb 1998 RE/SMG-030408QR4 SMG#2204.08 5.7.0 Phase 2+ ETS 300 940 Ed3 Mob Radio Interface L3 Unpublished RE/SMG-030408QR5 SMG#2304.08 5.8.0 Phase 2+ ETS 300 940 Ed3 Mob Radio Interface L3 Unpublished RE/SMG-030408QR5 SMG#2404.08 5.9.0 Phase 2+ ETS 300 940 Ed3 Mob Radio Interface L3 OAP version RE/SMG-030408QR5 SMG#2504.08 5.9.1 Phase 2+ ETS 300 940 Ed3 Mob Radio Interface L3 Pub Oct 1998 RE/SMG-030408QR5 SMG#2504.08 6.0.0 R97 TS 100 940 Mob Radio Interface L3 Unpublished DTS/SMG-020408Q6 SMG#2504.08 6.1.0 R97 TS 100 940 Mob Radio Interface L3 Unpublished DTS/SMG-020408Q6 SMG#2604.08 6.1.1 R97 TS 100 940 Mob Radio Interface L3 Unpublished DTS/SMG-020408Q6 SMG#2604.08 6.2.0D R97 TS 100 940 Mob Radio Interface L3 Unpublished DTS/SMG-020408Q6 SMG#2604.10 4.10.0 Phase 2 ETS 300 558 Ed2 Mob Radio Interface L3 SS UAP version RE/SMG-030410PR2 SMG#1704.10 4.10.1 Phase 2 ETS 300 558 Ed2 Mob Radio Interface L3 SS Pub Aug 1996 RE/SMG-030410PR2 SMG#1704.10 4.5.0 Phase 2 ETS 300 558 Mob Radio Interface L3 SS PE version DE/SMG-030410P SMG#04.10 4.8.1 Phase 2 ETS 300 558 Mob Radio Interface L3 SS Vote version DE/SMG-030410P SMG#04.10 4.8.2 Phase 2 ETS 300 558 Mob Radio Interface L3 SS Pub Feb 1995 DE/SMG-030410P SMG#1104.10 4.9.0 Phase 2 ETS 300 558 Am1 Mob Radio Interface L3 SS Pub July 1995 RE/SMG-030410P SMG#1304.10 5.0.0 Phase 2/2+ ETS 300 941 Mob Radio Interface L3 SS UAP version DE/SMG-030410Q SMG#2004.10 5.0.1 Phase 2/2+ ETS 300 941 Mob Radio Interface L3 SS Pub May 1997 DE/SMG-030410Q SMG#2004.10 6.0.0 R97 TS 100 941 Mob Radio Interface L3 SS Unpublished DTS/SMG-030410Q6 SMG#2504.10 6.0.1 R97 TS 100 941 Mob Radio Interface L3 SS Pub July 1998 DTS/SMG-030410Q6 SMG#2604.11 4.10.0 Phase 2 ETS 300 559 Ed4 Mob Radio Int SMS PtP Pub Sep 1996 RE/SMG-030411PR3 SMG#1704.11 4.7.2 Phase 2 ETS 300 559 Mob Radio Int SMS PtP Pub Feb 1995 DE/SMG-030411P SMG#1204.11 4.8.0 Phase 2 ETS 300 559 Ed2 Mob Radio Int SMS PtP Pub Oct 1995 RE/SMG-030411P SMG#1404.11 4.9.0 Phase 2 ETS 300 559 Ed3 Mob Radio Int SMS PtP Pub May 1996 RE/SMG-030411PR2 SMG#1604.11 5.0.0 Phase 2+ GTS 04.11 Mob Radio Int SMS PtP Pub Jan 1996 DGTS/SMG-030411Q SMG#1604.11 5.1.0 Phase 2+ GTS 04.11 Mob Radio Int SMS PtP Pub Mar 1996 RGTS/SMG-

030411QRSMG#17

04.11 5.1.1 Phase 2+ ETS 300 942 Mob Radio Int SMS PtP UAP version DE/SMG-030411QR SMG#20


Page 14


04.11 5.1.2 Phase 2+ ETS 300 942 Mob Radio Int SMS PtP Pub Apr 1997 DE/SMG-030411QR SMG#2004.11 5.2.0 Phase 2+ ETS 300 942 Ed2 Mob Radio Int SMS PtP OAP version RE/SMG-030411QR1 SMG#2104.11 5.2.1 Phase 2+ ETS 300 942 Ed2 Mob Radio Int SMS PtP Pub Sep 1997 RE/SMG-030411QR1 SMG#2104.11 6.0.0 R97 TS 100 942 Mob Radio Int SMS PtP Unpublished DTS/SMG-030411Q6 SMG#2504.11 6.0.1 R97 TS 100 942 Mob Radio Int SMS PtP Pub Aug 1998? DTS/SMG-030411Q6 SMG#2604.12 4.4.1 Phase 2 ETS 300 560 Mob Radio Int SMSCB Pub Feb 1995 DE/SMG-030412P SMG#1204.12 4.5.0 Phase 2 ETS 300 560 Ed2 Mob Radio Int SMSCB Pub Jan 1996 RE/SMG-030412P SMG#1504.12 4.6.0 Phase 2 ETS 300 560 Ed3 Mob Radio Int SMSCB Pub May 1996 RE/SMG-030412PR2 SMG#1604.12 5.0.0 Phase 2+ GTS 04.12 Mob Radio Int SMSCB Pub July 1996 DGTS/SMG-030412Q SMG#1904.12 5.0.1 Phase 2+ ETS 300 943 Mob Radio Int SMSCB UAP version DE/SMG-030412Q SMG#2004.12 5.0.2 Phase 2+ ETS 300 943 Mob Radio Int SMSCB Pub Apr 1997 DE/SMG-030412Q SMG#2004.13 4.0.2 Phase 2 ETS 300 561 Perf req on Mob rad inter Pub July 1995 DE/SMG-030413P SMG#1404.13 4.1.0 Phase 2 ETS 300 561 Ed2 Perf req on Mob rad inter Pub Jan 1996 RE/SMG-030413P SMG#1504.13 4.2.0 Phase 2 ETS 300 561 Ed3 Perf req on Mob rad inter Pub May 1996 RE/SMG-030413PR2 SMG#1604.13 5.0.0 Phase 2+ GTS 04.13 Perf req on Mob rad inter Pub May 1996 DGTS/SMG-030413Q SMG#1804.13 5.0.1 Phase 2+ ETS 300 944 Perf req on Mob rad inter UAP version DE/SMG-030413Q SMG#2004.13 5.0.2 Phase 2+ ETS 300 944 Perf req on Mob rad inter Pub Apr 1997 DE/SMG-030413Q SMG#2004.13 5.1.0 Phase 2+ ETS 300 944 Ed2 Perf req on Mob rad inter OAP version RE/SMG-030413QR SMG#2104.13 5.1.1 Phase 2+ ETS 300 944 Ed2 Perf req on Mob rad inter Pub Sep 1997 RE/SMG-030413QR SMG#2104.14 5.0.0 Phase 2+ TS 101 293 Individual MS Test Req Pub July 1998 DTS/SMG-070414Q SMG#2604.14 5.1.0 Phase 2+ TS 101 293 Individual MS Test Req Pub Oct 1998 RTS/SMG-

020414QR1SMG#27

04.21 4.4.1 Phase 2 ETS 300 562 Rate Adpt MS-BSS Pub Oct 1994 DE/SMG-040421P SMG#1104.21 4.5.0 Phase 2 ETS 300 562 Ed2 Rate Adpt MS-BSS Pub July 1995 RE/SMG-040421P SMG#1304.21 4.6.0 Phase 2 ETS 300 562 Ed3 Rate Adpt MS-BSS Pub Sep 1995 RE/SMG-040421PR2 SMG#1404.21 5.0.0 Phase 2/2+ ETS 300 945 Rate Adpt MS-BSS UAP version DE/SMG-040421Q SMG#2004.21 5.0.1 Phase 2/2+ ETS 300 945 Rate Adpt MS-BSS Pub May 1997 DE/SMG-040421Q SMG#2004.21 5.1.0 Phase 2+ ETS 300 945 Rate Adpt MS-BSS Unpublished RE/SMG-040421QR SMG#2104.21 5.1.1 Phase 2+ ETS 300 945 Ed2 Rate Adpt MS-BSS OAP version RE/SMG-040421QR SMG#2104.21 5.1.2 Phase 2+ ETS 300 945 Ed2 Rate Adpt MS-BSS Pub Aug 1997 RE/SMG-040421QR SMG#2104.21 5.2.0 Phase 2+ ETS 300 945 Ed3 Rate Adpt MS-BSS OAP version RE/SMG-040421QR1 SMG#2204.21 5.2.1 Phase 2+ ETS 300 945 Ed3 Rate Adpt MS-BSS Pub Jan 1998 RE/SMG-040421QR1 SMG#2204.21 5.3.0 Phase 2+ ETS 300 945 Ed4 Rate Adpt MS-BSS OAP version RE/SMG-040421QR2 SMG#2304.21 5.3.1 Phase 2+ ETS 300 945 Ed4 Rate Adpt MS-BSS Pub Mar 1998 RE/SMG-040421QR2 SMG#2304.21 5.4.0 Phase 2+ ETS 300 945 Ed5 Rate Adpt MS-BSS OAP version RE/SMG-040421QR3 SMG#2404.21 5.4.1 Phase 2+ ETS 300 945 Ed5 Rate Adpt MS-BSS Pub July 1998 RE/SMG-040421QR3 SMG#2404.21 5.5.0 Phase 2+ ETS 300 945 Ed6 Rate Adpt MS-BSS OAP version RE/SMG-040421QR4 SMG#2504.21 5.5.1 Phase 2+ ETS 300 945 Ed6 Rate Adpt MS-BSS Pub Oct 1998 RE/SMG-040421QR4 SMG#2504.21 7.0.0 R98 TS 100 945 Rate Adpt MS-BSS Unpublished DTS/SMG-040421Q7 SMG#2704.22 4.3.0 Phase 2 ETS 300 563 RLP for Data on MS-BSS Pub Sep 1994 DE/SMG-040422P SMG#804.22 4.4.0 Phase 2 ETS 300 563 Am1 RLP for Data on MS-BSS Pub July 1995 RE/SMG-040422P SMG#1304.22 4.5.0 Phase 2 ETS 300 563 Ed2 RLP for Data on MS-BSS OAP version RE/SMG-040422PR1 SMG#2504.22 4.5.1 Phase 2 ETS 300 563 Ed2 RLP for Data on MS-BSS Pub Oct 1998 RE/SMG-040422PR1 SMG#2504.22 5.0.0 Phase 2+ GTS 04.22 RLP for Data on MS-BSS Pub Jan 1996 DGTS/SMG-040422Q SMG#1604.22 5.0.1 Phase 2+ ETS 300 946 RLP for Data on MS-BSS UAP version DE/SMG-040422Q SMG#2004.22 5.0.2 Phase 2+ ETS 300 946 RLP for Data on MS-BSS Pub May 1997 DE/SMG-040422Q SMG#2004.22 5.1.0 Phase 2+ ETS 300 946 Ed2 RLP for Data on MS-BSS OAP version RE/SMG-040422QR1 SMG#2104.22 5.1.1 Phase 2+ ETS 300 946 Ed2 RLP for Data on MS-BSS Pub Aug 1997 RE/SMG-040422QR1 SMG#2104.22 5.2.0 Phase 2+ ETS 300 946 Ed3 RLP for Data on MS-BSS OAP version RE/SMG-040422QR2 SMG#2204.22 5.2.1 Phase 2+ ETS 300 946 Ed3 RLP for Data on MS-BSS Pub Jan 1998 RE/SMG-040422QR2 SMG#2204.22 5.3.0 Phase 2+ ETS 300 946 Ed4 RLP for Data on MS-BSS OAP version RE/SMG-040422QR3 SMG#2304.22 5.3.1 Phase 2+ ETS 300 946 Ed4 RLP for Data on MS-BSS Pub Mar 1998 RE/SMG-040422QR3 SMG#2304.22 5.4.0 Phase 2+ ETS 300 946 Ed5 RLP for Data on MS-BSS OAP version RE/SMG-040422QR4 SMG#2504.22 5.4.1 Phase 2+ ETS 300 946 Ed5 RLP for Data on MS-BSS Pub Oct 1998 RE/SMG-040422QR4 SMG#2504.22 6.0.0 R97 TS 100 946 RLP for Data on MS-BSS Pub July 1998 DTS/SMG-040422Q6 SMG#2604.22 6.1.0 R97 TS 100 946 RLP for Data on MS-BSS Pub Nov 1998? RTS/SMG-

040422Q6R1SMG#27

04.53 1.0.0 R98 TS 101 xxx TFO Stage 3 Draft DTS/SMG-110453Q SMG#27?

04.60 6.0.0 R97 TS 101 xxx GPRS RLC/MAC Unpublished DTS/SMG-020460Q6 SMG#2504.60 6.1.0 R97 EN 301 349 GPRS RLC/MAC PE version DEN/SMG-020460Q6 SMG#2604.60 6.2.0 R97 EN 301 349 GPRS RLC/MAC Unpublished DEN/SMG-020460Q6 SMG#2704.60 6.2.0D R97 EN 301 349 GPRS RLC/MAC Unpublished DEN/SMG-020460Q6 SMG#2604.63 5.0.0 Phase 2+ GTS 04.63 PDS Stage 3 Pub May 1996 DGTS/SMG-030463Q SMG#1804.64 5.0.0 Phase 2+ EN 301 xxx GPRS MS-SGSN LLC Unpublished DEN/SMG-030464Q6 SMG#2304.64 5.1.0 Phase 2+ EN 301 xxx GPRS MS-SGSN LLC Unpublished DEN/SMG-030464Q6 SMG#2404.64 6.0.0 R97 EN 301 xxx GPRS MS-SGSN LLC Unpublished DEN/SMG-030464Q6 SMG#2504.64 6.1.0 R97 TS 101 351 GPRS MS-SGSN LLC Pub July 1998 DTS/SMG-030464Q6 SMG#26


Page 15


04.64 6.2.0 R97 TS 101 351 GPRS MS-SGSN LLC Pub Nov 1998? RTS/SMG-030464Q6R1

SMG#27

04.65 5.0.0 Phase 2+ TS 101 297 GPRS MS-SGSN SNDCP Unpublished DEN/SMG-030465Q6 SMG#2304.65 5.1.0 Phase 2+ TS 101 297 GPRS MS-SGSN SNDCP Unpublished DEN/SMG-030465Q6 SMG#2404.65 6.0.0 R97 TS 101 297 GPRS MS-SGSN SNDCP Unpublished DEN/SMG-030465Q6 SMG#2504.65 6.1.0 R97 TS 101 297 GPRS MS-SGSN SNDCP Pub July 1998 DTS/SMG-030465Q6 SMG#2604.65 6.2.0 R97 TS 101 297 GPRS MS-SGSN SNDCP Pub Nov 1998? RTS/SMG-

030465Q6R1SMG#27

04.67 5.0.0 Phase 2+ ETS 300 947 eMLPP Stage 3 UAP version DE/SMG-030467Q SMG#2004.67 5.0.1 Phase 2+ ETS 300 947 eMLPP Stage 3 Pub May 1997 DE/SMG-030467Q SMG#2004.68 5.0.0 Phase 2+ GTS 04.68 VGCS GCC Unpublished DGTS/SMG-030468Q SMG#1804.68 5.0.1 Phase 2+ ETS 300 948 VGCS GCC UAP version DE/SMG-030468Q SMG#2004.68 5.0.2 Phase 2+ ETS 300 948 VGCS GCC Pub Apr 1997 DE/SMG-030468Q SMG#2004.68 5.1.0 Phase 2+ ETS 300 948 VGCS GCC Pub? RE/SMG-030468QR1 SMG#2704.69 5.0.0 Phase 2+ ETS 300 949 VBS BCC UAP version DE/SMG-030469Q SMG#2004.69 5.0.1 Phase 2+ ETS 300 949 VBS BCC Pub Apr 1997 DE/SMG-030469Q SMG#2004.69 5.1.0 Phase 2+ ETS 300 949 VBS BCC Pub? RE/SMG-030469QR1 SMG#2704.72 1.0.0 R98 TS 101 xxx Call deflection Stage 3 Draft DTS/SMG-030472Q SMG#27

?04.78 1.0.0 R98 TS 101 xxx CAMEL Stage 3 Work stopped DTS/SMG-030478Q SMG#2304.80 4.10.0 Phase 2 ETS 300 564 Ed2 MRI L3 Formats & coding UAP version RE/SMG-030480P SMG#1604.80 4.10.1 Phase 2 ETS 300 564 Ed2 MRI L3 Formats & coding Pub Aug 1996 RE/SMG-030480P SMG#1604.80 4.11.0 Phase 2 ETS 300 564 Ed3 MRI L3 Formats & coding UAP version RE/SMG-030480PR2 SMG#1704.80 4.11.1 Phase 2 ETS 300 564 Ed3 MRI L3 Formats & coding Pub Aug 1996 RE/SMG-030480PR2 SMG#1704.80 4.9.2 Phase 2 ETS 300 564 MRI L3 Formats & coding Pub Feb 1995 DE/SMG-030480P SMG#1204.80 5.0.0 Phase 2+ GTS 04.80 MRI L3 Formats & coding Pub Aug 1996 DGTS/SMG-030480Q SMG#1804.80 5.0.1 Phase 2+ ETS 300 950 MRI L3 Formats & coding UAP version DE/SMG-030480Q SMG#2004.80 5.0.2 Phase 2+ ETS 300 950 MRI L3 Formats & coding Pub May 1997 DE/SMG-030480Q SMG#2004.80 5.1.0 Phase 2+ ETS 300 950 Ed2 MRI L3 Formats & coding OAP version RE/SMG-030480QR1 SMG#2404.80 5.1.1 Phase 2+ ETS 300 950 Ed2 MRI L3 Formats & coding Pub July 1998? RE/SMG-030480QR1 SMG#2404.80 5.2.0 Phase 2+ ETS 300 950 Ed3 MRI L3 Formats & coding OAP version RE/SMG-030480QR2 SMG#2504.80 5.2.1 Phase 2+ ETS 300 950 Ed3 MRI L3 Formats & coding Pub Oct 1998 RE/SMG-030480QR2 SMG#2504.80 6.0.0 R97 TS 100 950 MRI L3 Formats & coding Unpublished DTS/SMG-030480Q6 SMG#2504.80 6.1.0 R97 TS 100 950 MRI L3 Formats & coding Pub July 1998 DTS/SMG-030480Q6 SMG#2604.81 4.4.1 Phase 2 ETS 300 565 Line Identity SS stage 3 Pub Feb 1995 DE/SMG-030481P SMG#1204.81 5.0.0 Phase 2/2+ ETS 300 951 Line Identity SS stage 3 UAP version DE/SMG-030481Q SMG#2004.81 5.0.1 Phase 2/2+ ETS 300 951 Line Identity SS stage 3 Pub May 1997 DE/SMG-030481Q SMG#2004.82 4.8.1 Phase 2 ETS 300 566 Call Forwarding SS stg 3 Pub Feb 1995 DE/SMG-030482P SMG#1204.82 4.9.0 Phase 2 ETS 300 566 Ed2 Call Forwarding SS stg 3 UAP version RE/SMG-030482P SMG#1704.82 4.9.1 Phase 2 ETS 300 566 Ed2 Call Forwarding SS stg 3 Pub Aug 1996 RE/SMG-030482P SMG#1704.82 5.0.0 Phase 2/2+ ETS 300 952 Call Forwarding SS stg 3 UAP version DE/SMG-030482Q SMG#2004.82 5.0.1 Phase 2/2+ ETS 300 952 Call Forwarding SS stg 3 Pub May 1997 DE/SMG-030482Q SMG#2004.83 4.5.2 Phase 2 ETS 300 567 CW & HOLD SS stg 3 Pub Feb 1995 DE/SMG-030483P SMG#904.83 4.6.0 Phase 2 ETS 300 567 Ed2 CW & HOLD SS stg 3 UAP version RE/SMG-030483P SMG#1704.83 4.6.1 Phase 2 ETS 300 567 Ed2 CW & HOLD SS stg 3 Pub Aug 1996 RE/SMG-030483P SMG#1704.83 5.0.0 Phase 2/2+ ETS 300 953 CW & HOLD SS stg 3 UAP version DE/SMG-030483Q SMG#2004.83 5.0.1 Phase 2/2+ ETS 300 953 CW & HOLD SS stg 3 Pub May 1997 DE/SMG-030483Q SMG#2004.84 4.3.2 Phase 2 ETS 300 568 MultiParty SS stage 3 Pub Feb 1995 DE/SMG-030484P SMG#904.84 5.0.0 Phase 2/2+ ETS 300 954 MultiParty SS stage 3 UAP version DE/SMG-030484Q SMG#2004.84 5.0.1 Phase 2/2+ ETS 300 954 MultiParty SS stage 3 Pub May 1997 DE/SMG-030484Q SMG#2004.85 4.0.3 Phase 2 ETS 300 569 CUG SS stage 3 Pub Feb 1995 DE/SMG-030485P SMG#704.85 4.1.0 Phase 2 ETS 300 569 Ed2 CUG SS stage 3 UAP version RE/SMG-030485P SMG#1804.85 4.1.1 Phase 2 ETS 300 569 Ed2 CUG SS stage 3 Pub Nov 1996 RE/SMG-030485P SMG#1804.85 5.0.0 Phase 2/2+ GTS 04.85 CUG SS stage 3 Pub Dec 1996 DGTS/SMG-030485Q SMG#2004.86 4.5.2 Phase 2 ETS 300 570 Advice of Charge SS stg 3 Pub Feb 1995 DE/SMG-030486P SMG#1104.86 5.0.0 Phase 2/2+ ETS 300 955 Advice of Charge SS stg 3 UAP version DE/SMG-030486Q SMG#2004.86 5.0.1 Phase 2/2+ ETS 300 955 Advice of Charge SS stg 3 Pub May 1997 DE/SMG-030486Q SMG#2004.88 4.6.3 Phase 2 ETS 300 571 Call Barring SS stage 3 Pub Feb 1995 DE/SMG-030488P SMG#704.88 4.7.0 Phase 2 ETS 300 571 Ed2 Call Barring SS stage 3 UAP version RE/SMG-030488P SMG#1704.88 4.7.1 Phase 2 ETS 300 571 Ed2 Call Barring SS stage 3 Pub Aug 1996 RE/SMG-030488P SMG#1704.88 5.0.0 Phase 2/2+ ETS 300 956 Call Barring SS stage 3 UAP version DE/SMG-030488Q SMG#2004.88 5.0.1 Phase 2/2+ ETS 300 956 Call Barring SS stage 3 Pub May 1997 DE/SMG-030488Q SMG#2004.88 5.1.0 Phase 2+ ETS 300 956 Ed2 Call Barring SS stage 3 OAP version RE/SMG-030488QR1 SMG#2404.88 5.1.1 Phase 2+ ETS 300 956 Ed2 Call Barring SS stage 3 Pub July 1998 RE/SMG-030488QR1 SMG#2404.88 6.0.0 R97 TS 100 956 Call Barring SS stage 3 Unpublished DTS/SMG-030488Q6 SMG#2504.88 6.0.1 R97 TS 100 956 Call Barring SS stage 3 Pub July 1998 DTS/SMG-030488Q6 SMG#2604.90 4.1.1 Phase 2 ETS 300 572 USSD stage 3 Pub Feb 1995 DE/SMG-030490P SMG#1204.90 5.0.0 Phase 2/2+ ETS 300 957 USSD stage 3 UAP version DE/SMG-030490Q SMG#2004.90 5.0.1 Phase 2/2+ ETS 300 957 USSD stage 3 Pub May 1997 DE/SMG-030490Q SMG#20


Page 16


04.91 5.0.0 Phase 2+ GTS 04.91 ECT stage 3 Pub Jan 1996 DGTS/SMG-030491Q SMG#1604.91 5.1.0 Phase 2+ GTS 04.91 ECT stage 3 Pub Mar 1996 RGTS/SMG-

030491QRSMG#17

04.91 5.1.1 Phase 2+ ETS 300 958 ECT stage 3 UAP version DE/SMG-030491QR SMG#2004.91 5.1.2 Phase 2+ ETS 300 958 ECT stage 3 Pub May 1997 DE/SMG-030491QR SMG#2004.93 6.0.0 R97 TS 101 284 CCBS stage 3 Unpublished DTS/SMG-030493Q6 SMG#2504.93 6.1.0 R97 TS 101 284 CCBS stage 3 Pub July 1998 DTS/SMG-030493Q6 SMG#2604.96 5.0.0 Phase 2+ TS 101 396 CNAP stage 3 Unpublished DTS/SMG-030496Q SMG#2404.96 6.0.0 R97 TS 101 396 CNAP stage 3 Unpublished DTS/SMG-030496Q6 SMG#2604.96 6.0.1 R97 TS 101 396 CNAP stage 3 Pub Oct 1998 DTS/SMG-030496Q6 SMG#2705.01 4.3.1 Phase 2 ETS 300 573 Physical layer on radio Pub Sep 1994 DE/SMG-020501P SMG#1005.01 4.4.0 Phase 2 ETS 300 573 Ed2 Physical layer on radio Pub July 1995 RE/SMG-020501PR1 SMG#1305.01 4.5.0 Phase 2 ETS 300 573 Ed3 Physical layer on radio Pub Sep 1995 RE/SMG-020501PR2 SMG#1405.01 4.6.0 Phase 2 ETS 300 573 Ed4 Physical layer on radio Pub May 1996 RE/SMG-020501PR3 SMG#1605.01 5.0.0 Phase 2+ GTS 05.01 Physical layer on radio Pub May 1996 DGTS/SMG-020501Q SMG#1805.01 5.1.0 Phase 2+ GTS 05.01 Physical layer on radio Pub Dec 1996 RGTS/SMG-

020501QRSMG#20

05.01 5.2.0 Phase 2+ GTS 05.01 Physical layer on radio Pub Mar 1997 RGTS/SMG-020501QR1

SMG#21

05.01 5.3.0 Phase 2+ GTS 05.01 Physical layer on radio Pub June 1997 RGTS/SMG-020501QR2

SMG#22

05.01 5.4.0 Phase 2+ GTS 05.01 Physical layer on radio Pub Apr 1998 RGTS/SMG-020501QR3

SMG#25

05.01 6.0.0 Phase 3 TS 101 157 Physical layer on radio Unpublished DTS/SMG-020501Q6 SMG#2405.01 6.1.0 R97 TS 101 157 Physical layer on radio Unpublished DTS/SMG-020501Q6 SMG#2505.01 6.1.1 R97 TS 100 573 Physical layer on radio Pub July 1998 DTS/SMG-020501Q6 SMG#2605.02 4.4.2 Phase 2 ETS 300 574 Multiplex & Multiplea Acc Pub Sep 1994 DE/SMG-020502P SMG#905.02 4.5.0 Phase 2 ETS 300 574 Ed2 Multiplex & Multiplea Acc Pub Jan 1996 RE/SMG-020502P SMG#1505.02 4.6.0 Phase 2 ETS 300 574 Ed3 Multiplex & Multiplea Acc UAP version RE/SMG-020502PR2 SMG#1605.02 4.6.1 Phase 2 ETS 300 574 Ed3 Multiplex & Multiplea Acc Pub Aug 1996 RE/SMG-020502PR2 SMG#1605.02 4.7.0 Phase 2 ETS 300 574 Ed4 Multiplex & Multiplea Acc Pub Aug 1996 RE/SMG-020502PR3 SMG#1705.02 4.8.0 Phase 2 ETS 300 574 Ed5 Multiplex & Multiplea Acc UAP version RE/SMG-020502PR4 SMG#2005.02 4.8.1 Phase 2 ETS 300 574 Ed5 Multiplex & Multiplea Acc Pub Apr 1997 RE/SMG-020502PR4 SMG#2005.02 4.9.0 Phase 2 ETS 300 574 Ed6 Multiplex & Multiplea Acc OAP version RE/SMG-020502PR5 SMG#2205.02 4.9.1 Phase 2 ETS 300 574 Ed6 Multiplex & Multiplea Acc Pub Jan 1998 RE/SMG-020502PR5 SMG#2205.02 5.0.0 Phase 2+ GTS 05.02 Multiplex & Multiplea Acc Pub May 1996 DGTS/SMG-020502Q SMG#1805.02 5.1.0 Phase 2+ GTS 05.02 Multiplex & Multiplea Acc Pub Aug 1996 RGTS/SMG-

020502QRSMG#19

05.02 5.2.0 Phase 2+ ETS 300 908 Multiplex & Multiplea Acc UAP version DE/SMG-020502QR1 SMG#2005.02 5.2.1 Phase 2+ ETS 300 908 Multiplex & Multiplea Acc Pub Apr 1997 DE/SMG-020502QR1 SMG#2005.02 5.3.0 Phase 2+ ETS 300 908 Ed2 Multiplex & Multiplea Acc OAP version RE/SMG-020502QR2 SMG#2105.02 5.3.1 Phase 2+ ETS 300 908 Ed2 Multiplex & Multiplea Acc Pub Aug 1997 RE/SMG-020502QR2 SMG#2105.02 5.4.0 Phase 2+ ETS 300 908 Ed3 Multiplex & Multiplea Acc OAP version RE/SMG-020502QR3 SMG#2205.02 5.4.1 Phase 2+ ETS 300 908 Ed3 Multiplex & Multiplea Acc Pub Dec 1997 RE/SMG-020502QR3 SMG#2205.02 5.5.0 Phase 2+ ETS 300 908 Ed4 Multiplex & Multiplea Acc Unpublished RE/SMG-020502QR4 SMG#2305.02 5.6.0 Phase 2+ ETS 300 908 Ed4 Multiplex & Multiplea Acc OAP version RE/SMG-020502QR4 SMG#2505.02 5.6.1 Phase 2+ ETS 300 908 Ed4 Multiplex & Multiplea Acc Pub Oct 1998 RE/SMG-020502QR4 SMG#2505.02 5.7.0 Phase 2+ ETS 300 908 Ed5 Multiplex & Multiplea Acc OAP version RE/SMG-020502QR5 SMG#2605.02 6.0.0 Phase 3 TS 100 908 Multiplex & Multiplea Acc Unpublished DTS/SMG-020502Q6 SMG#2405.02 6.1.0 R97 TS 100 908 Multiplex & Multiplea Acc Unpublished DTS/SMG-020502Q6 SMG#2505.02 6.2.0 R97 TS 100 908 Multiplex & Multiplea Acc Pub July 1998 DTS/SMG-020502Q6 SMG#2605.03 4.1.3 Phase 2 ETS 300 575 Channel Coding Pub Sep 1994 DE/SMG-020503P SMG#705.03 4.2.0 Phase 2 ETS 300 575 Ed2 Channel Coding Pub July 1995 RE/SMG-020503P SMG#1305.03 4.3.0 Phase 2 ETS 300 575 Am1 Channel Coding Pub Jan 1996 RE/SMG-020503PR2 SMG#1505.03 4.4.0 Phase 2 ETS 300 575 Ed3 Channel Coding OAP version RE/SMG-020503PR3 SMG#2105.03 4.4.1 Phase 2 ETS 300 575 Ed3 Channel Coding Pub Aug 1997 RE/SMG-020503PR3 SMG#2105.03 4.5.0 Phase 2 ETS 300 575 Ed4 Channel Coding OAP version RE/SMG-020503PR4 SMG#2205.03 4.5.1 Phase 2 ETS 300 575 Ed4 Channel Coding Pub Dec 1997 RE/SMG-020503PR4 SMG#2205.03 5.0.0 Phase 2+ GTS 05.03 Channel Coding Pub Mar 1996 DGTS/SMG-020503Q SMG#1705.03 5.1.0 Phase 2+ GTS 05.03 Channel Coding Pub May 1996 RGTS/SMG-

020503QRSMG#18

05.03 5.2.0 Phase 2+ GTS 05.03 Channel Coding Pub Aug 1996 RGTS/SMG-020503QR1

SMG#19

05.03 5.2.1 Phase 2+ ETS 300 909 Channel Coding UAP version DE/SMG-020503QR1 SMG#2005.03 5.2.2 Phase 2+ ETS 300 909 Channel Coding Pub Apr 1997 DE/SMG-020503QR1 SMG#2005.03 5.3.0 Phase 2+ ETS 300 909 Ed2 Channel Coding OAP version RE/SMG-020503QR2 SMG#2105.03 5.3.1 Phase 2+ ETS 300 909 Ed2 Channel Coding Pub Aug 1997 RE/SMG-020503QR2 SMG#2105.03 5.4.0 Phase 2+ ETS 300 909 Ed3 Channel Coding Unpublished RE/SMG-020503QR3 SMG#2305.03 5.5.0 Phase 2+ ETS 300 909 Ed3 Channel Coding OAP version RE/SMG-020503QR3 SMG#25


Page 17


05.03 5.5.1 Phase 2+ ETS 300 909 Ed3 Channel Coding Pub Oct 1998 RE/SMG-020503QR3 SMG#2505.03 6.0.0 Phase 3 TS 100 909 Channel Coding Unpublished DTS/SMG-020503Q6 SMG#2405.03 6.1.0 R97 TS 100 909 Channel Coding Unpublished DTS/SMG-020503Q6 SMG#2505.03 6.1.1 R97 TS 100 909 Channel Coding Pub July 1998 DTS/SMG-020503Q6 SMG#2605.04 4.0.3 Phase 2 ETS 300 576 Modulation Pub Sep 1994 DE/SMG-020504P SMG#705.04 5.0.0 Phase 2/2+ ETS 300 959 Modulation UAP version DE/SMG-020504Q SMG#2005.04 5.0.1 Phase 2/2+ ETS 300 959 Modulation Pub May 1997 DE/SMG-020504Q SMG#2005.05 4.10.0 Phase 2 ETS 300 577 Ed2 Radio Tx and RX Pub July 1995 RE/SMG-020505Q2 SMG#1305.05 4.11.0 Phase 2 ETS 300 577 Ed3 Radio Tx and RX Pub Sep 1995 RE/SMG-020505PR2 SMG#1405.05 4.12.0 Phase 2 ETS 300 577 Ed4 Radio Tx and RX Pub Jan 1996 RE/SMG-020505PR3 SMG#1505.05 4.13.0 Phase 2 ETS 300 577 Ed5 Radio Tx and RX Pub May 1996 RE/SMG-020505PR4 SMG#1605.05 4.14.0 Phase 2 ETS 300 577 Ed6 Radio Tx and RX Pub Aug1996 RE/SMG-020505PR5 SMG#1705.05 4.15.0 Phase 2 ETS 300 577 Ed7 Radio Tx and RX Pub Nov 1996 RE/SMG-020505PR6 SMG#1805.05 4.16.0 Phase 2 ETS 300 577 Ed8 Radio Tx and RX UAP version RE/SMG-020505PR7 SMG#1905.05 4.16.1 Phase 2 ETS 300 577 Ed8 Radio Tx and RX Pub Jan 1997 RE/SMG-020505PR7 SMG#1905.05 4.17.0 Phase 2 ETS 300 577 Ed9 Radio Tx and RX Pub Apr 1997 RE/SMG-020505PR8 SMG#2005.05 4.17.1 Phase 2 ETS 300 577

Ed10Radio Tx and RX OAP version RE/SMG-020505PR9 SMG#21

05.05 4.18.0 Phase 2 ETS 300 577Ed10

Radio Tx and RX number corrected RE/SMG-020505PR9 SMG#21

05.05 4.18.1 Phase 2 ETS 300 577Ed10

Radio Tx and RX Pub Aug 1997 RE/SMG-020505PR9 SMG#21

05.05 4.19.0 Phase 2 ETS 300 577Ed11

Radio Tx and RX OAP version RE/SMG-020505PRA SMG#22

05.05 4.19.1 Phase 2 ETS 300 577Ed11

Radio Tx and RX Pub Dec 1997 RE/SMG-020505PRA SMG#22

05.05 4.20.0 Phase 2 ETS 300 577Ed12

Radio Tx and RX OAP version RE/SMG-020505PRB SMG#23

05.05 4.20.1 Phase 2 ETS 300 577Ed12

Radio Tx and RX Pub Mar 1998 RE/SMG-020505PRB SMG#23

05.05 4.21.0 Phase 2 ETS 300 577Ed13

Radio Tx and RX OAP version RE/SMG-020505PRC SMG#24

05.05 4.21.1 Phase 2 ETS 300 577Ed13

Radio Tx and RX Pub June 1998 RE/SMG-020505PRC SMG#24

05.05 4.22.0 Phase 2 ETS 300 577Ed14

Radio Tx and RX Unpublished RE/SMG-020505PRD SMG#26

05.05 4.22.1 Phase 2 ETS 300 577Ed14

Radio Tx and RX OAP version RE/SMG-020505PRD SMG#26

05.05 4.9.1 Phase 2 ETS 300 577 Radio Tx and RX Pub Sep 1994 DE/SMG-020505P SMG#1005.05 5.0.0 Phase 2+ GTS 05.05 Radio Tx and RX Pub Mar 1996 DGTS/SMG-020505Q SMG#1705.05 5.1.0 Phase 2+ GTS 05.05 Radio Tx and RX Pub May 1996 RGTS/SMG-

020505QRSMG#18

05.05 5.2.0 Phase 2+ GTS 05.05 Radio Tx and RX Pub July 1996 RGTS/SMG-020505QR1

SMG#19

05.05 5.3.0 Phase 2+ ETS 300 910 Radio Tx and RX UAP version DE/SMG-020505QR2 SMG#2005.05 5.3.1 Phase 2+ ETS 300 910 Radio Tx and RX Pub Apr 1997 DE/SMG-020505QR2 SMG#2005.05 5.4.0 Phase 2+ ETS 300 910 Ed2 Radio Tx and RX OAP version RE/SMG-020505QR3 SMG#2105.05 5.4.1 Phase 2+ ETS 300 910 Ed2 Radio Tx and RX Pub Aug 1997 RE/SMG-020505QR3 SMG#2105.05 5.5.0 Phase 2+ ETS 300 910 Ed3 Radio Tx and RX OAP version RE/SMG-020505QR4 SMG#2205.05 5.5.1 Phase 2+ ETS 300 910 Ed3 Radio Tx and RX Pub Jan 1998 RE/SMG-020505QR4 SMG#2205.05 5.6.0 Phase 2+ ETS 300 910 Ed4 Radio Tx and RX Unpublished RE/SMG-020505QR5 SMG#2305.05 5.7.0 Phase 2+ ETS 300 910 Ed4 Radio Tx and RX OAP version RE/SMG-020505QR5 SMG#2405.05 5.7.1 Phase 2+ ETS 300 910 Ed4 Radio Tx and RX Pub June 1998 RE/SMG-020505QR5 SMG#2405.05 5.8.0 Phase 2+ ETS 300 910 Ed5 Radio Tx and RX OAP version RE/SMG-020505QR6 SMG#2505.05 5.8.1 Phase 2+ ETS 300 910 Ed5 Radio Tx and RX Pub Oct 1998 RE/SMG-020505QR6 SMG#2505.05 5.9.0 Phase 2+ ETS 300 910 Ed6 Radio Tx and RX OAP version RE/SMG-020505QR7 SMG#2605.05 6.0.0 Phase 3 TS 100 910 Radio Tx and RX Unpublished DTS/SMG-020505Q6 SMG#2405.05 6.1.0 R97 TS 100 910 Radio Tx and RX Unpublished DTS/SMG-020505Q6 SMG#2505.05 6.2.0 R97 TS 100 910 Radio Tx and RX Pub July 1998 RTS/SMG-020505Q6 SMG#2605.08 4.11.1 Phase 2 ETS 300 578 Radio subsystem link Cntrl Pub Feb 1995 DE/SMG-020508P SMG#1205.08 4.12.0 Phase 2 ETS 300 578 Ed2 Radio subsystem link Cntrl Pub July 1995 RE/SMG-020508P SMG#1305.08 4.13.0 Phase 2 ETS 300 578 Ed3 Radio subsystem link Cntrl Pub Sep 1995 RE/SMG-020508PR2 SMG#1405.08 4.14.0 Phase 2 ETS 300 578 Ed4 Radio subsystem link Cntrl Pub Jan 1996 RE/SMG-020508PR3 SMG#1505.08 4.15.0 Phase 2 ETS 300 578 Ed5 Radio subsystem link Cntrl Pub May 1996 RE/SMG-020508PR4 SMG#1605.08 4.16.0 Phase 2 ETS 300 578 Ed6 Radio subsystem link Cntrl Pub Aug 1996 RE/SMG-020508PR5 SMG#1705.08 4.17.0 Phase 2 ETS 300 578 Ed7 Radio subsystem link Cntrl Pub Nov 1996 RE/SMG-020508PR6 SMG#1805.08 4.18.0 Phase 2 ETS 300 578 Ed8 Radio subsystem link Cntrl UAP version RE/SMG-020508PR7 SMG#1905.08 4.18.1 Phase 2 ETS 300 578 Ed8 Radio subsystem link Cntrl Pub Jan 1997 RE/SMG-020508PR7 SMG#1905.08 4.18.2 Phase 2 ETS 300 578 Ed9 Radio subsystem link Cntrl OAP version RE/SMG-020508PR8 SMG#2105.08 4.18.3 Phase 2 ETS 300 578 Ed9 Radio subsystem link Cntrl Pub Aug 1997 RE/SMG-020508PR8 SMG#21


Page 18


05.08 4.19.0 Phase 2 ETS 300 578Ed10

Radio subsystem link Cntrl OAP version RE/SMG-020508PR9 SMG#22

05.08 4.19.1 Phase 2 ETS 300 578Ed10

Radio subsystem link Cntrl Pub Dec 1997 RE/SMG-020508PR9 SMG#22

05.08 4.20.0 Phase 2 ETS 300 578Ed11

Radio subsystem link Cntrl OAP version RE/SMG-020508PRA SMG#23

05.08 4.20.1 Phase 2 ETS 300 578Ed11

Radio subsystem link Cntrl Pub May 1998 RE/SMG-020508PRA SMG#23

05.08 4.21.0 Phase 2 ETS 300 578Ed12

Radio subsystem link Cntrl OAP version RE/SMG-020508PRB SMG#24

05.08 4.21.1 Phase 2 ETS 300 578Ed12

Radio subsystem link Cntrl Pub June 1998 RE/SMG-020508PRB SMG#24

05.08 5.0.0 Phase 2+ GTS 05.08 Radio subsystem link Cntrl Pub May 1996 DGTS/SMG-020508Q SMG#1805.08 5.1.0 Phase 2+ GTS 05.08 Radio subsystem link Cntrl Pub Aug 1996 RGTS/SMG-

020508QRSMG#19

05.08 5.2.0 Phase 2+ ETS 300 911 Radio subsystem link Cntrl UAP version DE/SMG-020508QR1 SMG#2005.08 5.2.1 Phase 2+ ETS 300 911 Radio subsystem link Cntrl Pub May 1997 DE/SMG-020508QR1 SMG#2005.08 5.3.0 Phase 2+ ETS 300 911 Ed2 Radio subsystem link Cntrl OAP version RE/SMG-020508QR2 SMG#2105.08 5.3.1 Phase 2+ ETS 300 911 Ed2 Radio subsystem link Cntrl Pub Aug 1997 RE/SMG-020508QR2 SMG#2105.08 5.4.0 Phase 2+ ETS 300 911 Ed3 Radio subsystem link Cntrl OAP version RE/SMG-020508QR3 SMG#2205.08 5.4.1 Phase 2+ ETS 300 911 Ed3 Radio subsystem link Cntrl Pub Dec 1997 RE/SMG-020508QR3 SMG#2205.08 5.5.0 Phase 2+ ETS 300 911 Ed4 Radio subsystem link Cntrl Unpublished RE/SMG-020508QR4 SMG#2305.08 5.6.0 Phase 2+ ETS 300 911 Ed4 Radio subsystem link Cntrl OAP version RE/SMG-020508QR4 SMG#2405.08 5.6.1 Phase 2+ ETS 300 911 Ed4 Radio subsystem link Cntrl Pub June 1998 RE/SMG-020508QR4 SMG#2405.08 5.7.0 Phase 2+ ETS 300 911 Ed5 Radio subsystem link Cntrl OAP version RE/SMG-020508QR5 SMG#2505.08 5.7.1 Phase 2+ ETS 300 911 Ed5 Radio subsystem link Cntrl Pub Oct 1998 RE/SMG-020508QR5 SMG#2505.08 5.8.0 Phase 2+ ETS 300 911 Ed6 Radio subsystem link Cntrl OAP version RE/SMG-020508QR6 SMG#2605.08 6.0.0 Phase 3 TS 100 911 Radio subsystem link Cntrl Unpublished DTS/SMG-020508Q6 SMG#2405.08 6.1.0 R97 TS 100 911 Radio subsystem link Cntrl Unpublished DTS/SMG-020508Q6 SMG#2505.08 6.1.1 R97 TS 100 911 Radio subsystem link Cntrl Unpublished DTS/SMG-020508Q6 SMG#2505.08 6.2.0 R97 TS 100 911 Radio subsystem link Cntrl Pub July 1998 RTS/SMG-

020508Q6R1SMG#26

05.10 4.4.2 Phase 2 ETS 300 579 Radio subsystem sync Pub Sep 1994 DE/SMG-020510P SMG#905.10 4.5.0 Phase 2 ETS 300 579 Ed2 Radio subsystem sync Pub July 1995 RE/SMG-020510P SMG#1305.10 4.6.0 Phase 2 ETS 300 579 Ed3 Radio subsystem sync Pub Sep 1995 RE/SMG-020510PR2 SMG#1405.10 4.7.0 Phase 2 ETS 300 579 Ed4 Radio subsystem sync Pub May 1996 RE/SMG-020510PR3 SMG#1605.10 4.8.0 Phase 2 ETS 300 579 Ed5 Radio subsystem sync Pub Aug 1996 RE/SMG-020510PR4 SMG#1705.10 4.9.0 Phase 2 ETS 300 579 Ed6 Radio subsystem sync Pub Nov 1996 RE/SMG-020510PR5 SMG#1805.10 5.0.0 Phase 2+ GTS 05.10 Radio subsystem sync Pub May 1996 DGTS/SMG-020510Q SMG#1805.10 5.1.0 Phase 2+ ETS 300 912 Radio subsystem sync UAP version DE/SMG-020510QR SMG#2005.10 5.1.1 Phase 2+ ETS 300 912 Radio subsystem sync Pub May 1997 DE/SMG-020510QR SMG#2005.10 5.2.0 Phase 2+ ETS 300 912 Ed2 Radio subsystem sync Unpublished RE/SMG-020510QR1 SMG#2305.10 6.0.0 Phase 3 TS 100 912 Radio subsystem sync Unpublished DTS/SMG-020510Q6 SMG#2405.10 6.1.0 R97 TS 100 912 Radio subsystem sync Unpublished DTS/SMG-020510Q6 SMG#2505.10 6.2.0 R97 TS 100 912 Radio subsystem sync Pub July 1998 RTS/SMG-020510Q6 SMG#2605.22 4.0.0 Phase 2 ETR 284 RL man in hierarch Nets Pub May 1996 DTR/SMG-020522P SMG#1805.22 5.0.0 Phase 2/2+ ETR 355 RL man in hierarch Nets Pub Nov 1996 DTR/SMG-020522Q SMG#2005.50 4.1.0 Phase 2 TR Background RF Unpublished DTR/SMG SMG#1305.50 4.2.0 Phase 2 TR Background RF Unpublished DTR/SMG SMG#1705.50 4.3.0 Phase 2 TR Background RF Unpublished DTR/SMG05.50 5.0.0 Phase 2/2+ ETR xxx Background RF Unpublished DTR/SMG-020550Q SMG#2005.50 5.1.0 Phase 2+ TR 101 115 Background RF Unpublished DTR/SMG-020550Q SMG#2105.50 5.1.1 Phase 2+ TR 101 115 Background RF Pub Nov 1997 DTR/SMG-020550Q SMG#2305.50 6.0.0 Phase 3 TR 101 115 Background RF Unpublished RTR/SMG-020550Q6 SMG#2405.50 6.0.1 R97 TR 101 115 Background RF Unpublished RTR/SMG-020550Q6 SMG#2405.50 6.0.2 R97 TR 101 115 Background RF Pub July 1998 RTR/SMG-020550Q6 SMG#2605.50 7.0.0 R98 TR 101 115 Background RF Unpublished RTR/SMG-020550Q7 SMG#2605.90 4.2.1 Phase 2 ETR 108 EMC Considerations Pub Jan 1994 DTR/SMG-000590P SMG#805.90 4.3.0 Phase 2 ETR 108 Am 1 EMC Considerations Pub Aug 1995 RTR/SMG-000590P SMG#1505.90 5.0.0 Phase 2/2+ ETR 357 EMC Considerations Unpublished DTR/SMG-000590Q SMG#2006.01 4.0.5 Phase 2 ETS 300 580-1 FR speech proc descript Pub Sep 1994 DE/SMG-020601P SMG#706.01 4.0.6 Phase 2 ETS 300 580-1

Ed2FR speech proc descript OAP version RE/SMG-110601PR1 SMG#23

06.01 4.0.7 Phase 2 ETS 300 580-1Ed2

FR speech proc descript Pub Mar 1998 RE/SMG-110601PR1 SMG#23

06.01 5.0.0 Phase 2/2+ ETS 300 960 FR speech proc descript UAP version DE/SMG-110601Q SMG#2006.01 5.0.1 Phase 2/2+ ETS 300 960 FR speech proc descript Pub May 1997 DE/SMG-110601Q SMG#2006.01 5.1.0 Phase 2+ ETS 300 960 Ed2 FR speech proc descript OAP version RE/SMG-110601QR1 SMG#2306.01 5.1.1 Phase 2+ ETS 300 960 Ed2 FR speech proc descript Pub Mar 1998 RE/SMG-110601QR1 SMG#2306.02 4.0.0 Phase 2 ETS 300 581-1 HR speech proc descript PE version DE/SMG-020602 SMG#13


Page 19


06.02 4.0.1 Phase 2 ETS 300 581-1 HR speech proc descript Vote version DE/SMG-020602 SMG#1306.02 4.0.2 Phase 2 ETS 300 581-1 HR speech proc descript Pub Nov 1995 DE/SMG-020602 SMG#1306.02 5.0.0 Phase 2/2+ ETS 300 966 HR speech proc descript UAP version DE/SMG-110602Q SMG#2006.02 5.0.1 Phase 2/2+ ETS 300 966 HR speech proc descript Pub May 1997 DE/SMG-110602Q SMG#2006.06 4.0.1 Phase 2 ETS 300 581-7 HR C-source code PE version DE/SMG-020606 SMG#1306.06 4.0.2 Phase 2 ETS 300 581-7 HR C-source code Vote version DE/SMG-020606 SMG#1606.06 4.0.3 Phase 2 ETS 300 581-7 HR C-source code Pub Jan 1996 DE/SMG-020606 SMG#1606.06 4.1.0 Phase 2 ETS 300 581-7

Ed2HR C-source code Unpublished RE/SMG-020606 SMG#17

06.06 4.2.0 Phase 2 ETS 300 581-7Ed2

HR C-source code OAP version RE/SMG-110606PR1 SMG#23

06.06 4.2.1 Phase 2 ETS 300 581-7Ed2

HR C-source code Pub Mar 1998 RE/SMG-110606PR1 SMG#23

06.06 5.0.0 Phase 2/2+ ETS 300 967 HR C-source code UAP version DE/SMG-110606Q SMG#2006.06 5.0.1 Phase 2/2+ ETS 300 967 HR C-source code Pub May 1997 DE/SMG-110606Q SMG#2006.06 5.1.0 Phase 2+ ETS 300 967 Ed2 HR C-source code OAP version RE/SMG-110606QR1 SMG#2306.06 5.1.1 Phase 2+ ETS 300 967 Ed2 HR C-source code Pub Mar 1998 RE/SMG-110606QR1 SMG#2306.07 4.0.1 Phase 2 ETS 300 581-8 HR Test sequences PE version DE/SMG-020607 SMG#1306.07 4.0.2 Phase 2 ETS 300 581-8 HR Test sequences Vote version DE/SMG-020607 SMG#1606.07 4.0.3 Phase 2 ETS 300 581-8 HR Test sequences Pub Jan 1996 DE/SMG-020607 SMG#1606.07 4.1.0 Phase 2/2+ ETS 300 581-8

Ed2HR Test sequences Unpublished RE/SMG-110607PR1 SMG#22

06.07 4.1.0 Phase 2 ETS 300 581-8 HR Test sequences Unpublished DE/SMG-110607Q SMG#1706.07 4.2.0 Phase 2 ETS 300 581-8

Ed2HR Test sequences OAP version RE/SMG-110607PR1 SMG#23

06.07 4.2.1 Phase 2 ETS 300 581-8Ed2

HR Test sequences Pub Apr 1998 RE/SMG-110607PR1 SMG#23

06.07 5.0.0 Phase 2/2+ ETS 300 968 HR Test sequences UAP version DE/SMG-110607Q SMG#2006.07 5.0.1 Phase 2/2+ ETS 300 968 HR Test sequences Pub May 1997 DE/SMG-110607Q SMG#2006.07 5.1.0 Phase 2/2+ ETS 300 968 Ed2 HR Test sequences Unpublished RE/SMG-110607QR1 SMG#2206.07 5.2.0 Phase 2+ ETS 300 968 Ed2 HR Test sequences OAP version RE/SMG-110607QR1 SMG#2306.07 5.2.1 Phase 2+ ETS 300 968 Ed2 HR Test sequences Pub Apr 1998 RE/SMG-110607QR1 SMG#2306.08 4.0.0 Phase 2 ETR 229 HR performan character Pub Oct 1995 DTR/SMG-020608P SMG#1606.08 5.0.0 Phase 2/2+ ETR 358 HR performan character Pub Dec 1996 DTR/SMG-110608Q SMG#2006.10 4.0.2 Phase 2 ETS 300 580-2 FR speech transcoding Pub Sep 1994 DE/SMG-020610P SMG#706.10 4.1.0 Phase 2 ETS 300 580-2

Ed2FR speech transcoding OAP version RE/SMG-110610PR1 SMG#23

06.10 4.1.1 Phase 2 ETS 300 580-2Ed2

FR speech transcoding Pub Mar 1998 RE/SMG-110610PR1 SMG#23

06.10 5.0.0 Phase 2/2+ ETS 300 961 FR speech transcoding UAP version DE/SMG-110610Q SMG#2006.10 5.0.1 Phase 2/2+ ETS 300 961 FR speech transcoding Pub May 1997 DE/SMG-110610Q SMG#2006.10 5.1.0 Phase 2+ ETS 300 961 Ed2 FR speech transcoding OAP version RE/SMG-110610QR1 SMG#2306.10 5.1.1 Phase 2+ ETS 300 961 Ed2 FR speech transcoding Pub May 1998 RE/SMG-110610QR1 SMG#2306.11 4.0.4 Phase 2 ETS 300 580-3 FR substitution & muting Pub Sep 1994 DE/SMG-020611P SMG#706.11 4.0.5 Phase 2 ETS 300 580-3

Ed2FR substitution & muting OAP version RE/SMG-110611PR1 SMG#23

06.11 4.0.6 Phase 2 ETS 300 580-3Ed2

FR substitution & muting Pub Mar 1998 RE/SMG-110611PR1 SMG#23

06.11 5.0.0 Phase 2/2+ ETS 300 962 FR substitution & muting UAP version DE/SMG-110611Q SMG#2006.11 5.0.1 Phase 2/2+ ETS 300 962 FR substitution & muting Pub May 1997 DE/SMG-110611Q SMG#2006.12 4.0.4 Phase 2 ETS 300 580-4 FR comfort noise Pub Sep 1994 DE/SMG-020612P SMG#706.12 5.0.0 Phase 2/2+ ETS 300 963 FR comfort noise UAP version DE/SMG-110612Q SMG#2006.12 5.0.1 Phase 2/2+ ETS 300 963 FR comfort noise Pub May 1997 DE/SMG-110612Q SMG#2006.20 4.0.0 Phase 2 ETS 300 581-2 HR speech transcoding PE version DE/SMG-020620 SMG#1306.20 4.2.0 Phase 2 ETS 300 581-2 HR speech transcoding Vote version DE/SMG-020620 SMG#1506.20 4.2.1 Phase 2 ETS 300 581-2 HR speech transcoding Pub Nov 1995 DE/SMG-020620 SMG#1506.20 4.3.0 Phase 2 ETS 300 581-2

Ed2HR speech transcoding OAP version RE/SMG-110620PR1 SMG#17

06.20 4.3.1 Phase 2 ETS 300 581-2Ed2

HR speech transcoding Pub May 1998 RE/SMG-110620PR1 SMG#17

06.20 5.0.0 Phase 2/2+ ETS 300 969 HR speech transcoding UAP version DE/SMG-110620Q SMG#2006.20 5.0.1 Phase 2/2+ ETS 300 969 HR speech transcoding Pub May 1997 DE/SMG-110620Q SMG#2006.20 5.1.0 Phase 2+ ETS 300 969 Ed2 HR speech transcoding OAP version RE/SMG-110620QR1 SMG#22

?06.20 5.1.1 Phase 2+ ETS 300 969 Ed2 HR speech transcoding Pub May 1998 RE/SMG-110620QR1 SMG#2206.21 4.0.0 Phase 2 ETS 300 581-3 HR substitution & muting PE version DE/SMG-020621 SMG#1306.21 4.0.1 Phase 2 ETS 300 581-3 HR substitution & muting Vote version DE/SMG-020621 SMG#1506.21 4.0.2 Phase 2 ETS 300 581-3 HR substitution & muting Pub Nov 1995 DE/SMG-020621 SMG#1506.21 5.0.0 Phase 2/2+ ETS 300 970 HR substitution & muting UAP version DE/SMG-110621Q SMG#2006.21 5.0.1 Phase 2/2+ ETS 300 970 HR substitution & muting Pub May 1997 DE/SMG-110621Q SMG#20


Page 20


06.22 4.0.0 Phase 2 ETS 300 581-4 HR comfort noise PE version DE/SMG-020622 SMG#1306.22 4.1.0 Phase 2 ETS 300 581-4 HR comfort noise Vote version DE/SMG-020622 SMG#1506.22 4.1.1 Phase 2 ETS 300 581-4 HR comfort noise Pub Nov 1995 DE/SMG-020622 SMG#1506.22 5.0.0 Phase 2/2+ ETS 300 971 HR comfort noise UAP version DE/SMG-110622Q SMG#2006.22 5.1.0 Phase 2/2+ ETS 300 971 HR comfort noise Pub May 1997 DE/SMG-110622Q SMG#2006.31 4.0.4 Phase 2 ETS 300 580-5 FR DTX Pub Sep 1994 DE/SMG-020631P SMG#706.31 4.0.5 Phase 2 ETS 300 580-5 FR DTX Unpublished DE/SMG-020631P SMG#706.31 5.0.0 Phase 2/2+ ETS 300 964 FR DTX UAP version DE/SMG-110631Q SMG#2006.31 5.0.1 Phase 2/2+ ETS 300 964 FR DTX Pub May 1997 DE/SMG-110631Q SMG#2006.32 4.0.5 Phase 2 ETS 300 580-6 Voice Activity Detector Pub Sep 1994 DE/SMG-020632P SMG#906.32 4.1.0 Phase 2 ETS 300 580-6

Ed2Voice Activity Detector Pub July 1995 RE/SMG-020632P SMG#13

06.32 4.2.0 Phase 2 ETS 300 580-6Ed3

Voice Activity Detector UAP version RE/SMG-020632PR2 SMG#17

06.32 4.2.1 Phase 2 ETS 300 580-6Ed3

Voice Activity Detector Pub Oct 1996 RE/SMG-020632PR2 SMG#17

06.32 4.3.0 Phase 2 ETS 300 580-6Ed4

Voice Activity Detector OAP version RE/SMG-110632PR3 SMG#23

06.32 4.3.1 Phase 2 ETS 300 580-6Ed4

Voice Activity Detector Pub Apr 1998 RE/SMG-110632PR3 SMG#23

06.32 5.0.0 Phase 2/2+ ETS 300 965 Voice Activity Detector UAP version DE/SMG-110632Q SMG#2006.32 5.0.1 Phase 2/2+ ETS 300 965 Voice Activity Detector Pub May 1997 DE/SMG-110632Q SMG#2006.32 5.0.2 Phase 2+ ETS 300 965 Ed2 Voice Activity Detector OAP version RE/SMG-110632QR1 SMG#2306.32 5.0.3 Phase 2+ ETS 300 965 Ed2 Voice Activity Detector Pub Apr 1998 RE/SMG-110632QR1 SMG#2306.41 4.0.0 Phase 2 ETS 300 581-5 HR DTX PE version DE/SMG-020641 SMG#1306.41 4.0.1 Phase 2 ETS 300 581-5 HR DTX Vote version DE/SMG-020641 SMG#1306.41 4.0.2 Phase 2 ETS 300 581-5 HR DTX Pub Nov 1995 DE/SMG-020641 SMG#1306.41 5.0.0 Phase 2/2+ ETS 300 972 HR DTX UAP version DE/SMG-110641Q SMG#2006.41 5.0.1 Phase 2/2+ ETS 300 972 HR DTX Pub May 1997 DE/SMG-110641Q SMG#2006.41 5.1.0 Phase 2+ ETS 300 972 Ed 2 HR DTX OAP version RE/SMG-110641QR1 SMG#2306.41 5.1.1 Phase 2+ ETS 300 972 Ed 2 HR DTX Pub Mar 1998 RE/SMG-110641QR1 SMG#2306.42 4.0.0 Phase 2 ETS 300 581-6 HR Voice Activity Detector PE version DE/SMG-020642 SMG#1306.42 4.1.0 Phase 2 ETS 300 581-6 HR Voice Activity Detector Vote version DE/SMG-020642 SMG#1506.42 4.1.1 Phase 2 ETS 300 581-6 HR Voice Activity Detector Pub Nov 1995 DE/SMG-020642 SMG#1506.42 5.0.0 Phase 2/2+ ETS 300 973 HR Voice Activity Detector UAP version DE/SMG-110642Q SMG#2006.42 5.0.1 Phase 2/2+ ETS 300 973 HR Voice Activity Detector Pub May 1997 DE/SMG-110642Q SMG#2006.51 4.0.0 Phase 2 EN 301 243 EFR speech proc descript OAP version DEN/SMG-110651P SMG#2206.51 4.0.1 Phase 2 EN 301 243 EFR speech proc descript Pub Dec 1997 DEN/SMG-110651P SMG#2206.51 5.0.0 Phase 2/2+ ETS 300 723 EFR speech proc descript PE version DE/SMG-020651 SMG#1706.51 5.1.0 Phase 2/2+ ETS 300 723 EFR speech proc descript Unpublished DE/SMG-020651 SMG#1906.51 5.1.1 Phase 2/2+ ETS 300 723 EFR speech proc descript Vote version DE/SMG-020651 SMG#2006.51 5.1.2 Phase 2/2+ ETS 300 723 EFR speech proc descript Pub Mar 1997 DE/SMG-020651 SMG#2006.53 4.0.0 Phase 2 EN 301 244 EFR C-source code OAP version DEN/SMG-110653P SMG#2206.53 4.0.1 Phase 2 EN 301 244 EFR C-source code Pub Jan 1998 DEN/SMG-110653P SMG#2306.53 5.0.0 Phase 2/2+ ETS 300 724 EFR C-source code PE version DE/SMG-020653 SMG#1706.53 5.1.0 Phase 2/2+ ETS 300 724 EFR C-source code Unpublished DE/SMG-020653 SMG#1906.53 5.1.1 Phase 2/2+ ETS 300 724 EFR C-source code Vote version DE/SMG-020653 SMG#2006.53 5.1.2 Phase 2/2+ ETS 300 724 EFR C-source code Pub Mar 1997 DE/SMG-020653 SMG#2006.53 5.1.3 Phase 2+ ETS 300 724 EFR C-source code Unpublished RE/SMG-020653QR1 SMG#2006.54 4.0.0 Phase 2 EN 301 250 EFR Test sequences OAP version DEN/SMG-110654P SMG#2306.54 4.0.0 Phase 2 EN 301 250 EFR Test sequences Unpublished DEN/SMG-110654P SMG#2206.54 4.0.1 Phase 2 EN 301 250 EFR Test sequences Pub Sep 1998 DEN/SMG-110654P SMG#2306.54 5.0.0 Phase 2/2+ ETS 300 725 EFR Test sequences PE version DE/SMG-110654Q SMG#2006.54 5.1.0 Phase 2+ ETS 300 725 EFR Test sequences Vote version DE/SMG-110654Q SMG#2306.54 5.1.1 Phase 2+ ETS 300 725 EFR Test sequences Pub Feb 1998 DE/SMG-110654Q SMG#2306.55 4.0.0 Phase 2 TR 101 085 EFR performan character Pub July 1997 DTR/SMG-110655P SMG#2206.55 5.0.0 Phase 2/2+ ETR 305 EFR performan character Pub Aug 1996 DTR/SMG-020655 SMG#1906.60 4.0.0 Phase 2 EN 301 245 EFR speech transcoding OAP version DEN/SMG-110660P SMG#2206.60 4.0.1 Phase 2 EN 301 245 EFR speech transcoding Pub Dec 1997 DEN/SMG-110660P SMG#2306.60 4.1.0 Phase 2 EN 301 245 EFR speech transcoding OAP version REN/SMG-

110660PR1SMG#25

06.60 5.0.0 Phase 2/2+ ETS 300 726 EFR speech transcoding PE version DE/SMG-020660 SMG#1706.60 5.1.0 Phase 2/2+ ETS 300 726 EFR speech transcoding Unpublished DE/SMG-020660 SMG#1906.60 5.1.1 Phase 2/2+ ETS 300 726 EFR speech transcoding Vote version DE/SMG-020660 SMG#2006.60 5.1.2 Phase 2/2+ ETS 300 726 EFR speech transcoding Pub Mar 1997 DE/SMG-020660 SMG#2006.60 5.2.0 Phase 2+ ETS 300 726 Ed2 EFR speech transcoding OAP version RE/SMG-110660QR1 SMG#2506.61 4.0.0 Phase 2 EN 301 246 EFR substitute & muting OAP version DEN/SMG-110661P SMG#2206.61 4.0.1 Phase 2 EN 301 246 EFR substitute & muting Pub Dec 1997 DEN/SMG-110661P SMG#2206.61 5.0.0 Phase 2/2+ ETS 300 727 EFR substitute & muting PE version DE/SMG-020661 SMG#17


Page 21


06.61 5.1.0 Phase 2/2+ ETS 300 727 EFR substitute & muting Unpublished DE/SMG-020661 SMG#1906.61 5.1.1 Phase 2/2+ ETS 300 727 EFR substitute & muting Vote version DE/SMG-020661 SMG#2006.61 5.1.2 Phase 2/2+ ETS 300 727 EFR substitute & muting Pub Apr 1997 DE/SMG-020661 SMG#2006.62 4.0.0 Phase 2 EN 301 247 EFR comfort noise OAP version DEN/SMG-110662P SMG#2206.62 4.0.1 Phase 2 EN 301 247 EFR comfort noise Pub Dec 1997 DEN/SMG-110662P SMG#2206.62 5.0.0 Phase 2/2+ ETS 300 728 EFR comfort noise PE version DE/SMG-020662 SMG#1706.62 5.1.0 Phase 2/2+ ETS 300 728 EFR comfort noise Unpublished DE/SMG-020662 SMG#1906.62 5.1.1 Phase 2/2+ ETS 300 728 EFR comfort noise Vote version DE/SMG-020662 SMG#2006.62 5.1.2 Phase 2/2+ ETS 300 728 EFR comfort noise Pub Mar 1997 DE/SMG-020662 SMG#2006.81 4.0.0 Phase 2 EN 301 248 EFR DTX OAP version DEN/SMG-110681P SMG#2206.81 4.0.1 Phase 2 EN 301 248 EFR DTX Pub Dec 1997 DEN/SMG-110681P SMG#2206.81 5.0.0 Phase 2/2+ ETS 300 729 EFR DTX PE version DE/SMG-020681 SMG#1706.81 5.1.0 Phase 2/2+ ETS 300 729 EFR DTX Unpublished DE/SMG-020681 SMG#1906.81 5.1.1 Phase 2/2+ ETS 300 729 EFR DTX Vote version DE/SMG-020681 SMG#2006.81 5.1.2 Phase 2/2+ ETS 300 729 EFR DTX Pub Mar 1997 DE/SMG-020681 SMG#2006.82 4.0.0 Phase 2 EN 301 249 EFR Voice Activity Detector OAP version DEN/SMG-110682P SMG#2206.82 4.0.1 Phase 2 EN 301 249 EFR Voice Activity Detector Pub Dec 1997 DEN/SMG-110682P SMG#2206.82 5.0.0 Phase 2/2+ ETS 300 730 EFR Voice Activity Detector PE version DE/SMG-020682 SMG#1706.82 5.0.1 Phase 2/2+ ETS 300 730 EFR Voice Activity Detector Unpublished DE/SMG-020682 SMG#1906.82 5.0.2 Phase 2/2+ ETS 300 730 EFR Voice Activity Detector Vote version DE/SMG-020682 SMG#2006.82 5.0.3 Phase 2/2+ ETS 300 730 EFR Voice Activity Detector Pub Mar 1997 DE/SMG-020682 SMG#2006.85 5.0.0 Phase 2+ TR 101 294 FR/HR/EFR speech interop Pub July 1998 DTR/SMG-110685Q SMG#2607.01 4.10.0 Phase 2 ETS 300 582 Ed4 TAF for MSs Pub May 1996 RE/SMG-040701PR3 SMG#1607.01 4.7.2 Phase 2 ETS 300 582 TAF for MSs Pub Oct 1994 DE/SMG-040701P SMG#1007.01 4.8.0 Phase 2 ETS 300 582 Ed2 TAF for MSs Pub July 1995 RE/SMG-040701P SMG#1307.01 4.9.0 Phase 2 ETS 300 582 Ed3 TAF for MSs Pub Jan 1996 RE/SMG-040701PR2 SMG#1507.01 5.0.0 Phase 2+ GTS 07.01 TAF for MSs Pub Jan 1996 DGTS/SMG-040701Q SMG#1607.01 5.0.1 Phase 2+ GTS 07.01 TAF for MSs Pub Mar 1996 RGTS/SMG-

040701QRSMG#17

07.01 5.1.0 Phase 2+ GTS 07.01 TAF for MSs Pub May 1996 RGTS/SMG-040701QR1

SMG#18

07.01 5.2.0 Phase 2+ GTS 07.01 TAF for MSs Pub July 1996 RGTS/SMG-040701QR2

SMG#19

07.01 5.3.0 Phase 2+ ETS 300 913 TAF for MSs UAP version DE/SMG-040701QR3 SMG#2007.01 5.3.1 Phase 2+ ETS 300 913 TAF for MSs Pub Apr 1997 DE/SMG-040701QR3 SMG#2007.01 5.4.0 Phase 2+ ETS 300 913 Ed2 TAF for MSs Unpublished RE/SMG-040701QR4 SMG#2107.01 5.4.1 Phase 2+ ETS 300 913 Ed2 TAF for MSs OAP version RE/SMG-040701QR4 SMG#2107.01 5.4.2 Phase 2+ ETS 300 913 Ed2 TAF for MSs Pub Sep 1997 RE/SMG-040701QR4 SMG#2107.01 5.5.0 Phase 2+ ETS 300 913 Ed3 TAF for MSs OAP version RE/SMG-040701QR5 SMG#2207.01 5.5.1 Phase 2+ ETS 300 913 Ed3 TAF for MSs Pub Jan 1998 RE/SMG-040701QR5 SMG#2207.01 5.6.0 Phase 2+ ETS 300 913 Ed4 TAF for MSs OAP version RE/SMG-040701QR6 SMG#2307.01 5.6.1 Phase 2+ ETS 300 913 Ed4 TAF for MSs Pub Mar 1998 RE/SMG-040701QR6 SMG#2307.01 5.7.0 Phase 2+ ETS 300 913 Ed5 TAF for MSs OAP version RE/SMG-040701QR7 SMG#2407.01 5.7.1 Phase 2+ ETS 300 913 Ed5 TAF for MSs Pub July 1998 RE/SMG-040701QR7 SMG#2407.01 5.8.0 Phase 2+ ETS 300 913 Ed6 TAF for MSs OAP version RE/SMG-040701QR8 SMG#2507.01 5.8.1 Phase 2+ ETS 300 913 Ed6 TAF for MSs Pub Oct 1998 RE/SMG-040701QR8 SMG#2507.01 7.0.0 R98 TS 100 913 TAF for MSs Unpublished DTS/SMG-040701Q7 SMG#2707.02 4.5.1 Phase 2 ETS 300 583 TAF using Async Pub Oct 1994 DE/SMG-040702P SMG#1107.02 5.0.0 Phase 2+ GTS 07.02 TAF using Async Pub Jan 1996 DGTS/SMG-040702Q SMG#1607.02 5.1.0 Phase 2+ GTS 07.02 TAF using Async Pub May 1996 RGTS/SMG-

040702QRSMG#18

07.02 5.1.1 Phase 2+ ETS 300 914 TAF using Async UAP version DE/SMG-040702QR SMG#2007.02 5.1.2 Phase 2+ ETS 300 914 TAF using Async Pub Apr 1997 DE/SMG-040702QR SMG#2007.02 5.2.0 Phase 2+ ETS 300 914 Ed2 TAF using Async Unpublished RE/SMG-040702QR1 SMG#2107.02 5.2.1 Phase 2+ ETS 300 914 Ed2 TAF using Async OAP version RE/SMG-040702QR1 SMG#2107.02 5.2.2 Phase 2+ ETS 300 914 Ed2 TAF using Async Pub Sep 1997 RE/SMG-040702QR1 SMG#2107.02 5.3.0 Phase 2+ ETS 300 914 Ed3 TAF using Async OAP version RE/SMG-040702QR2 SMG#2207.02 5.3.1 Phase 2+ ETS 300 914 Ed3 TAF using Async Pub Jan 1998 RE/SMG-040702QR2 SMG#2207.02 5.4.0 Phase 2+ ETS 300 914 Ed4 TAF using Async OAP version RE/SMG-040702QR3 SMG#2307.02 5.4.1 Phase 2+ ETS 300 914 Ed4 TAF using Async Pub Mar 1998 RE/SMG-040702QR3 SMG#2307.02 5.5.0 Phase 2+ ETS 300 914 Ed5 TAF using Async OAP version RE/SMG-040702QR4 SMG#2407.02 5.5.1 Phase 2+ ETS 300 914 Ed5 TAF using Async Pub July 1998 RE/SMG-040702QR4 SMG#2407.02 6.0.0 R97 TS 100 914 TAF using Async Pub July 1998 DTS/SMG-040702Q6 SMG#2607.02 7.0.0 R98 TS 100 914 TAF using Async Unpublished DTS/SMG-040702Q7 SMG#2707.03 4.5.1 Phase 2 ETS 300 584 TAF using sync Pub Sep 1994 DE/SMG-040703P SMG#907.03 5.0.0 Phase 2+ GTS 07.03 TAF using sync Pub May 1996 DGTS/SMG-040703Q SMG#1807.03 5.0.1 Phase 2+ ETS 300 915 TAF using sync UAP version DE/SMG-040703Q SMG#2007.03 5.0.2 Phase 2+ ETS 300 915 TAF using sync Pub Apr 1997 DE/SMG-040703Q SMG#2007.03 5.1.0 Phase 2+ ETS 300 915 Ed2 TAF using sync Unpublished RE/SMG-040703QR1 SMG#21


Page 22


07.03 5.1.1 Phase 2+ ETS 300 915 Ed2 TAF using sync OAP version RE/SMG-040703QR1 SMG#2107.03 5.1.2 Phase 2+ ETS 300 915 Ed2 TAF using sync Pub Sep 1997 RE/SMG-040703QR1 SMG#2107.03 5.2.0 Phase 2+ ETS 300 915 Ed3 TAF using sync OAP version RE/SMG-040703QR2 SMG#2207.03 5.2.1 Phase 2+ ETS 300 915 Ed3 TAF using sync Pub Jan 1998 RE/SMG-040703QR2 SMG#2207.03 5.3.0 Phase 2+ ETS 300 915 Ed4 TAF using sync OAP version RE/SMG-040703QR3 SMG#2307.03 5.3.1 Phase 2+ ETS 300 915 Ed4 TAF using sync Pub Mar 1998 RE/SMG-040703QR3 SMG#2307.03 5.4.0 Phase 2+ ETS 300 915 Ed5 TAF using sync OAP version RE/SMG-040703QR4 SMG#2407.03 5.4.1 Phase 2+ ETS 300 915 Ed5 TAF using sync Pub July 1998 RE/SMG-040703QR4 SMG#2407.03 6.0.0 R97 TS 100 915 TAF using sync Pub July 1998 DTS/SMG-040703Q6 SMG#2607.05 4.3.2 Phase 2 ETS 300 585 DTE-DCE Interface for SMS Pub Sep 1994 DE/SMG-040705P SMG#807.05 4.4.0 Phase 2 ETS 300 585 Am1 DTE-DCE Interface for SMS Pub Mar 1995 RE/SMG-040705P SMG#1207.05 4.5.0 Phase 2 ETS 300 585 Ed2 DTE-DCE Interface for SMS Pub May 1996 RE/SMG-040705PR2 SMG#1607.05 4.6.0 Phase 2 ETS 300 585 Ed3 DTE-DCE Interface for SMS Pub Sep 1996 RE/SMG-040705PR3 SMG#1707.05 4.7.0 Phase 2 ETS 300 585 Ed4 DTE-DCE Interface for SMS Pub Oct 1996 RE/SMG-040705PR4 SMG#1807.05 4.8.0 Phase 2 ETS 300 585 Ed5 DTE-DCE Interface for SMS UAP version RE/SMG-040705PR5 SMG#2007.05 4.8.1 Phase 2 ETS 300 585 Ed5 DTE-DCE Interface for SMS Pub Apr 1997 RE/SMG-040705PR5 SMG#2007.05 5.0.0 Phase 2+ GTS 07.05 DTE-DCE Interface for SMS Pub July 1996 DGTS/SMG-040705Q SMG#1907.05 5.1.0 Phase 2+ GTS 07.05 DTE-DCE Interface for SMS Pub Dec 1996 RGTS/SMG-

040705QRSMG#20

07.05 5.2.0 Phase 2+ GTS 07.05 DTE-DCE Interface for SMS Pub Mar 1997 RGTS/SMG-040705QR1

SMG#21

07.05 5.3.0 Phase 2+ GTS 07.05 DTE-DCE Interface for SMS Pub Aug 1997 RGTS/SMG-040705QR2

SMG#22

07.05 5.4.0 Phase 2+ GTS 07.05 DTE-DCE Interface for SMS Unpublished RGTS/SMG-040705QR3

SMG#23

07.05 5.5.0 Phase 2+ GTS 07.05 DTE-DCE Interface for SMS Pub Jan 1998 RGTS/SMG-040705QR3

SMG#24

07.06 4.1.2 Phase 2 ETS 300 586 DTE-DCE Int MS for MT config Pub Sep 1994 DE/SMG-040706P SMG#707.06 4.2.0 Phase 2 ETS 300 586 Ed2 DTE-DCE Int MS for MT config Pub July 1995 RE/SMG-040706P SMG#1307.07 4.0.0 Phase 2 ETS 300 642 AT command set for Mes PE version DE/SMG-040707P SMG#1607.07 4.1.0 Phase 2 ETS 300 642 AT command set for Mes Pub Sep 1996 DE/SMG-040707P SMG#1807.07 4.2.0 Phase 2 ETS 300 642 Ed2 AT command set for Mes OAP version RE/SMG-040707PR1 SMG#2407.07 4.2.1 Phase 2 ETS 300 642 Ed2 AT command set for Mes Pub July 1998 RE/SMG-040707PR1 SMG#2407.07 4.3.0 Phase 2 ETS 300 642 Ed3 AT command set for Mes OAP version RE/SMG-040707PR2 SMG#2507.07 4.3.1 Phase 2 ETS 300 642 Ed3 AT command set for Mes Pub Oct 1998 RE/SMG-040707PR2 SMG#2507.07 5.0.0 Phase 2+ GTS 07.07 AT command set for Mes Pub July 1996 DGTS/SMG-040707Q SMG#1907.07 5.1.0 Phase 2+ ETS 300 916 AT command set for Mes UAP version DE/SMG-040707QR SMG#2007.07 5.1.1 Phase 2+ ETS 300 916 AT command set for Mes Pub Apr 1997 DE/SMG-040707QR SMG#2007.07 5.2.0 Phase 2+ ETS 300 916 Ed2 AT command set for Mes OAP version RE/SMG-040707QR1 SMG#2107.07 5.2.1 Phase 2+ ETS 300 916 Ed2 AT command set for Mes Pub Aug 1997 RE/SMG-040707QR1 SMG#2107.07 5.3.0 Phase 2+ ETS 300 916 Ed3 AT command set for Mes Unpublished RE/SMG-040707QR2 SMG#2207.07 5.3.1 Phase 2+ ETS 300 916 Ed3 AT command set for Mes OAP version RE/SMG-040707QR2 SMG#2207.07 5.3.2 Phase 2+ ETS 300 916 Ed3 AT command set for Mes Pub Jan 1998 RE/SMG-040707QR2 SMG#2207.07 5.4.0 Phase 2+ ETS 300 916 Ed4 AT command set for Mes Unpublished RE/SMG-040707QR3 SMG#2307.07 5.5.0 Phase 2+ ETS 300 916 Ed4 AT command set for Mes OAP version RE/SMG-040707QR3 SMG#2407.07 5.5.1 Phase 2+ ETS 300 916 Ed4 AT command set for Mes Pub July 1998 RE/SMG-040707QR3 SMG#2407.07 5.6.0 Phase 2+ ETS 300 916 Ed5 AT command set for Mes OAP version RE/SMG-040707QR4 SMG#2507.07 5.6.1 Phase 2+ ETS 300 916 Ed5 AT command set for Mes Pub Oct 1998 RE/SMG-040707QR4 SMG#2507.07 5.7.0 Phase 2+ ETS 300 916 Ed6 AT command set for Mes OAP version RE/SMG-040707QR5 SMG#2607.07 6.0.0 R97 TS 100 916 AT command set for Mes Unpublished DTS/SMG-040707Q6 SMG#2507.07 6.1.0 R97 TS 100 916 AT command set for Mes Pub July 1998 DTS/SMG-040707Q6 SMG#2607.07 6.2.0 R97 TS 100 916 AT command set for Mes Pub Nov 1998? RTS/SMG-

040707Q6R1SMG#27

07.07 7.0.0 R98 TS 100 916 AT command set for Mes Unpublished DTS/SMG-040707Q7 SMG#2607.08 5.0.0 Phase 2+ ETS 300 917 GSM API PE version DE/SMG-040708Q SMG#2007.08 5.1.0 Phase 2+ ETS 300 917 GSM API Unpublished DE/SMG-040708Q SMG#2207.08 5.2.0 Phase 2+ ETS 300 917 GSM API Vote version DE/SMG-040708Q SMG#2407.08 5.2.1 Phase 2+ ETS 300 917 GSM API Pub May 1998 DE/SMG-040708Q SMG#2407.10 6.0.0 R97 TS 101 369 Multiplexing protocol Unpublished DTS/SMG-040710Q6 SMG#2507.10 6.1.0 R97 TS 101 369 Multiplexing protocol Pub July 1998 DTS/SMG-040710Q6 SMG#2607.10 6.2.0 R97 TS 101 369 Multiplexing protocol Pub Oct 1998 RTS/SMG-

040710Q6R1SMG#27

07.60 5.0.0 Phase 2+ TS 101 356 GPRS MS Unpublished DTS/SMG-040760Q6 SMG#2307.60 5.1.0 Phase 2+ TS 101 356 GPRS MS Unpublished DTS/SMG-040760Q6 SMG#2407.60 6.0.0 R97 TS 101 356 GPRS MS Unpublished DTS/SMG-040760Q6 SMG#2507.60 6.1.0 R97 TS 101 356 GPRS MS Unpublished DTS/SMG-040760Q6 SMG#2607.60 6.1.1 R97 TS 101 356 GPRS MS Pub July 1998 DTS/SMG-040760Q6 SMG#2607.60 6.2.0 R97 TS 101 356 GPRS MS Unpublished RTS/SMG-

040760Q6R1SMG#27


Page 23


07.60 6.2.1 R97 TS 101 356 GPRS MS Pub Nov 1998? RTS/SMG-040760Q6R1

SMG#27

08.01 4.0.3 Phase 2 ETS 300 587-1 BSS-MSC Inter General Pub Sep 1994 DE/SMG-030801P SMG#708.01 5.0.0 Phase 2/2+ GTS 08.01 BSS-MSC Inter General Pub Nov 1996 DGTS/SMG-030801Q SMG#2008.02 4.1.1 Phase 2 ETS 300 587-2 BSS-MSC Iner Principles Pub Sep 1994 DE/SMG-030802P SMG#708.02 4.2.0 Phase 2 ETS 300 587-2

Ed2BSS-MSC Iner Principles Pub July 1995 RE/SMG-030802P SMG#13

08.02 5.0.0 Phase 2/2+ GTS 08.02 BSS-MSC Iner Principles Pub Dec 1996 DGTS/SMG-030802Q SMG#2008.02 5.1.0 Phase 2+ GTS 08.02 BSS-MSC Iner Principles Pub Apr 1997 RGTS/SMG-

030802QR1SMG#21

08.04 4.0.3 Phase 2 ETS 300 588 BSS-MSC Interface L1 Pub Sep 1994 DE/SMG-030804P SMG#708.04 5.0.0 Phase 2/2+ GTS 08.04 BSS-MSC Interface L1 Pub Dec 1996 DGTS/SMG-030804Q SMG#2008.06 4.4.1 Phase 2 ETS 300 589 Sig trans BSS-MSC Inter Pub Sep 1994 DE/SMG-030806P SMG#1008.06 4.5.0 Phase 2 ETS 300 589 Ed2 Sig trans BSS-MSC Inter Pub July 1995 RE/SMG-030806P SMG#1308.06 5.0.0 Phase 2+ GTS 08.06 Sig trans BSS-MSC Inter Pub Mar 1996 DGTS/SMG-030806Q SMG#1708.06 5.1.0 Phase 2+ GTS 08.06 Sig trans BSS-MSC Inter Pub May 1996 RGTS/SMG-

030806QRSMG#18

08.06 5.2.0 Phase 2+ GTS 08.06 Sig trans BSS-MSC Inter Pub May 1998 RGTS/SMG-030806QR1

SMG#25

08.08 4.10.0 Phase 2 ETS 300 590 Ed4 MSC-BSS Interface L3 Pub May 1996 RE/SMG-030808PR3 SMG#1608.08 4.11.0 Phase 2 ETS 300 590 Ed5 MSC-BSS Interface L3 Pub Sep 1996 RE/SMG-030808PR4 SMG#1708.08 4.12.0 Phase 2 ETS 300 590 Ed6 MSC-BSS Interface L3 OAP version RE/SMG-030808PR5 SMG#2308.08 4.12.1 Phase 2 ETS 300 590 Ed6 MSC-BSS Interface L3 Pub Oct 1998 RE/SMG-030808PR5 SMG#2308.08 4.7.1 Phase 2 ETS 300 590 MSC-BSS Interface L3 Pub Sep 1994 DE/SMG-030808P SMG#1008.08 4.8.0 Phase 2 ETS 300 590 Ed2 MSC-BSS Interface L3 Pub July 1995 RE/SMG-030808P SMG#1308.08 4.9.0 Phase 2 ETS 300 590 Ed3 MSC-BSS Interface L3 Pub Jan 1995 RE/SMG-030808PR2 SMG#1508.08 5.0.0 Phase 2+ GTS 08.08 MSC-BSS Interface L3 Pub Jan 1996 DGTS/SMG-030808Q SMG#1608.08 5.1.0 Phase 2+ GTS 08.08 MSC-BSS Interface L3 Pub Mar 1996 RGTS/SMG-

030808QRSMG#17

08.08 5.10.0 Phase 2+ GTS 08.08 MSC-BSS Interface L3 Pub July 1998 RGTS/SMG-030808QR7

SMG#26

08.08 5.2.0 Phase 2+ GTS 08.08 MSC-BSS Interface L3 Pub May 1996 RGTS/SMG-030808QR1

SMG#18

08.08 5.3.0 Phase 2+ GTS 08.08 MSC-BSS Interface L3 Pub July 1996 RGTS/SMG-030808QR2

SMG#19

08.08 5.4.0 Phase 2+ GTS 08.08 MSC-BSS Interface L3 Pub Nov 1996 RGTS/SMG-030808QR3

SMG#20

08.08 5.5.0 Phase 2+ GTS 08.08 MSC-BSS Interface L3 Unpublished RGTS/SMG-030808QR4

SMG#21


SMG#22


SMG#22


SMG#22

08.08 5.6.3 Phase 2+ GTS 08.08 MSC-BSS Interface L3 Pub Aug 1997 RGTS/SMG-030808QR4

SMG#22


SMG#23

08.08 5.8.0 Phase 2+ GTS 08.08 MSC-BSS Interface L3 Pub Feb 1998 RGTS/SMG-030808QR5

SMG#24

08.08 5.9.0 Phase 2+ GTS 08.08 MSC-BSS Interface L3 Pub May 1998 RGTS/SMG-030808QR6

SMG#25

08.08 6.0.0 R97 TS 100 590 MSC-BSS Interface L3 Unpublished DTS/SMG-030808Q6 SMG#2508.08 6.1.0 R97 TS 100 590 MSC-BSS Interface L3 Pub July 1998 DTS/SMG-030808Q6 SMG#2608.08 6.2.0 R97 TS 100 590 MSC-BSS Interface L3 Pub Nov 1998? RTS/SMG-

030808Q6R1SMG#27

08.08 7.0.0 R98 TS 100 590 MSC-BSS Interface L3 Unpublished DTS/SMG-030808Q7 SMG#2508.14 5.0.0 Phase 2+ TS 101 298 GPRS BSSGP L1 Unpublished DTS/SMG-020814Q6 SMG#2408.14 6.0.0 R97 TS 101 298 GPRS BSSGP L1 Pub July 1998 DTS/SMG-020814Q6 SMG#2608.16 5.0.0 Phase 2+ TS 101 299 GPRS BSSGP L2 Unpublished DTS/SMG-020816Q6 SMG#2408.16 6.0.0 R97 TS 101 299 GPRS BSSGP L2 Unpublished DTS/SMG-020816Q6 SMG#2508.16 6.1.0 R97 TS 101 299 GPRS BSSGP L2 Pub July 1998 DTS/SMG-020816Q6 SMG#2608.18 5.0.0 Phase 2+ TS 101 343 GPRS BSSGP L3 Unpublished DTS/SMG-020818Q6 SMG#2408.18 6.0.0 R97 TS 101 343 GPRS BSSGP L3 Unpublished DTS/SMG-020818Q6 SMG#2508.18 6.1.0 R97 TS 101 343 GPRS BSSGP L3 Pub July 1998 DTS/SMG-020818Q6 SMG#2608.18 6.2.0 R97 TS 101 343 GPRS BSSGP L3 Pub Oct 1998 RTS/SMG-

020818Q6R1SMG#27

08.20 4.2.2 Phase 2 ETS 300 591 Rate Adpt BSS-MSC Int Pub Sep 1994 DE/SMG-040820P SMG#708.20 4.2.3 Phase 2 ETS 300 591 Ed2 Rate Adpt BSS-MSC Int Pub July 1995 RE/SMG-040820P SMG#13


Page 24


08.20 5.0.0 Phase 2/2+ GTS 08.20 Rate Adpt BSS-MSC Int Pub Dec 1996 DGTS/SMG-030820Q SMG#2008.20 5.1.0 Phase 2+ GTS 08.20 Rate Adpt BSS-MSC Int Pub Apr 1997 RGTS/SMG-

030820QRSMG#21

08.20 5.2.0 Phase 2+ GTS 08.20 Rate Adpt BSS-MSC Int Pub Aug 1997 RGTS/SMG-030820QR1

SMG#22

08.20 5.3.0 Phase 2+ GTS 08.20 Rate Adpt BSS-MSC Int Pub Jan 1998 RGTS/SMG-030820QR2

SMG#24

08.20 7.0.0 R98 TS 100 591 Rate Adpt BSS-MSC Int Unpublished DTS/SMG-030820Q7 SMG#2708.51 4.0.4 Phase 2 ETS 300 592 BSC-BTS Inter General Pub Sep 1994 DE/SMG-030851P SMG#708.51 4.1.0 Phase 2 ETS 300 592 Ed2 BSC-BTS Inter General Pub July 1995 RE/SMG-030851P SMG#1308.51 5.0.0 Phase 2/2+ GTS 08.51 BSC-BTS Inter General Pub Dec 1996 DGTS/SMG-030851Q SMG#2008.52 4.0.4 Phase 2 ETS 300 593 BSC-BTS Inter Principles Pub Sep 1994 DE/SMG-030852P SMG#708.52 4.1.0 Phase 2 ETS 300 593 Ed2 BSC-BTS Inter Principles Pub July 1995 RE/SMG-030852P SMG#1308.52 4.2.0 Phase 2 ETS 300 593 Ed3 BSC-BTS Inter Principles Pub Jan 1996 RE/SMG-030852PR2 SMG#1508.52 5.0.0 Phase 2/2+ GTS 08.52 BSC-BTS Inter Principles Pub Dec 1996 DGTS/SMG-030852Q SMG#2008.54 4.0.4 Phase 2 ETS 300 594 BSC-BTS Interface L1 Pub Sep 1994 DE/SMG-030854P SMG#708.54 4.1.0 Phase 2 ETS 300 594 Ed2 BSC-BTS Interface L1 Pub July 1995 RE/SMG-030854P SMG#1308.54 5.0.0 Phase 2+ GTS 08.54 BSC-BTS Interface L1 Pub Jan 1996 DGTS/SMG-030854Q SMG#1608.56 4.0.2 Phase 2 ETS 300 595 BSC-BTS Interface L2 Pub Sep 1994 DE/SMG-030856P SMG#808.56 5.0.0 Phase 2/2+ GTS 08.56 BSC-BTS Interface L2 Pub Dec 1996 DGTS/SMG-030856Q SMG#2008.58 4.6.1 Phase 2 ETS 300 596 BSC-BTS Interface L3 Pub Sep 1994 DE/SMG-030858P SMG#1008.58 4.7.0 Phase 2 ETS 300 596 Ed2 BSC-BTS Interface L3 Pub July 1995 RE/SMG-030858P SMG#1308.58 4.8.0 Phase 2 ETS 300 596 Ed3 BSC-BTS Interface L3 Pub Jan 1996 RE/SMG-030858PR2 SMG#1508.58 4.9.0 Phase 2 ETS 300 596 Ed4 BSC-BTS Interface L3 Pub May 1996 RE/SMG-030858PR3 SMG#1608.58 5.0.0 Phase 2+ GTS 08.58 BSC-BTS Interface L3 Pub Jan 1996 DGTS/SMG-030858Q SMG#1608.58 5.1.0 Phase 2+ GTS 08.58 BSC-BTS Interface L3 Pub Mar 1996 RGTS/SMG-

030858QRSMG#17

08.58 5.2.0 Phase 2+ GTS 08.58 BSC-BTS Interface L3 Pub July 1996 RGTS/SMG-030858QR1

SMG#19

08.58 5.3.0 Phase 2+ GTS 08.58 BSC-BTS Interface L3 Pub Apr 1997 RGTS/SMG-030858QR2

SMG#21

08.58 5.4.0 Phase 2+ GTS 08.58 BSC-BTS Interface L3 Unpublished RGTS/SMG-030858QR3

SMG#22

08.58 5.5.0 Phase 2+ GTS 08.58 BSC-BTS Interface L3 Pub Oct 1997 RGTS/SMG-030858QR3

SMG#23

08.58 5.6.0 Phase 2+ GTS 08.58 BSC-BTS Interface L3 Unpublished RGTS/SMG-030858QR4

SMG#24

08.58 5.7.0 Phase 2+ GTS 08.58 BSC-BTS Interface L3 Pub May 1998 RGTS/SMG-030858QR4

SMG#25

08.58 5.8.0 Phase 2+ GTS 08.58 BSC-BTS Interface L3 Pub July 1998 RGTS/SMG-030858QR5

SMG#26

08.58 6.0.0 R97 TS 100 596 BSC-BTS Interface L3 Pub Aug 1998 DTS/SMG-030858Q6 SMG#2608.60 4.1.3 Phase 2 ETS 300 597 Inbnd cntl Tcoder & RA Pub Sep 1994 DE/SMG-030860P SMG#708.60 4.2.0 Phase 2 ETS 300 597 Ed2 Inbnd cntl Tcoder & RA Pub July 1995 RE/SMG-030860P SMG#1308.60 4.3.0 Phase 2 ETS 300 597 Ed3 Inbnd cntl Tcoder & RA Unpublished RE/SMG-020860PR1 SMG#2208.60 4.4.0 Phase 2 ETS 300 597 Ed3 Inbnd cntl Tcoder & RA OAP version RE/SMG-020860PR1 SMG#2308.60 4.4.1 Phase 2 ETS 300 597 Ed3 Inbnd cntl Tcoder & RA Pub Mar 1998 RE/SMG-020860PR1 SMG#2308.60 5.0.0 Phase 2+ ETS 300 737 Inbnd cntl Tcoder & RA PE version DE/SMG-020860Q SMG#1708.60 5.0.1 Phase 2+ ETS 300 737 Inbnd cntl Tcoder & RA Unpublished DE/SMG-020860Q SMG#1908.60 5.0.2 Phase 2+ ETS 300 737 Inbnd cntl Tcoder & RA Vote version DE/SMG-020860Q SMG#2008.60 5.0.3 Phase 2+ ETS 300 737 Inbnd cntl Tcoder & RA Pub Mar 1997 DE/SMG-020860Q SMG#2008.60 5.1.0 Phase 2+ ETS 300 737 Ed2 Inbnd cntl Tcoder & RA OAP version RE/SMG-020860QR1 SMG#2208.60 5.1.1 Phase 2+ ETS 300 737 Ed2 Inbnd cntl Tcoder & RA Pub Feb 1998 RE/SMG-020860QR1 SMG#2208.61 4.0.0 Phase 2 ETS 300 598 HR Ibd cntl Tcoder & RA PE version DE/SMG-030861P SMG#1308.61 4.0.1 Phase 2 ETS 300 598 HR Ibd cntl Tcoder & RA Vote version DE/SMG-030861P SMG#1308.61 4.0.2 Phase 2 ETS 300 598 HR Ibd cntl Tcoder & RA Pub Nov 1995 DE/SMG-030861P SMG#1308.61 5.0.0 Phase 2/2+ ETS 300 979 HR Ibd cntl Tcoder & RA UAP version DE/SMG-020861Q SMG#2008.61 5.0.1 Phase 2/2+ ETS 300 979 HR Ibd cntl Tcoder & RA Pub May 1997 DE/SMG-020861Q SMG#2008.64 1.0.0 Phase 2+ TS 101 xxx GPRS BSSGP L3 Work stopped DTS/SMG-030864Q6 SMG#2209.01 4.0.0 Phase 2 ETR 109 Gen Net IW scenarios Pub Oct 1993 DTR/SMG-030901P SMG#909.01 5.0.0 Phase 2/2+ ETR 359 Gen Net IW scenarios Pub Dec 1996 DTR/SMG-030901Q SMG#2009.02 4.10.0 Phase 2 ETS 300 599 Am1 MAP Pub July 1995 RE/SMG-030902PR1 SMG#1309.02 4.11.0 Phase 2 ETS 300 599 Ed2 MAP UAP version RE/SMG-030902PR2 SMG#1409.02 4.11.1 Phase 2 ETS 300 599 Ed2 MAP Pub Nov 1995 RE/SMG-030902PR2 SMG#1409.02 4.12.0 Phase 2 ETS 300 599 Ed3 MAP UAP version RE/SMG-030902PR3 SMG#1609.02 4.12.1 Phase 2 ETS 300 599 Ed3 MAP Pub Sep 1996 RE/SMG-030902PR3 SMG#1609.02 4.13.0 Phase 2 ETS 300 599 Edx MAP Unpublished RE/SMG-030902PR4 SMG#1709.02 4.14.0 Phase 2 ETS 300 599 Ed4 MAP UAP version RE/SMG-030902PR4 SMG#1909.02 4.14.1 Phase 2 ETS 300 599 Ed4 MAP Pub Jan 1997 RE/SMG-030902PR4 SMG#1909.02 4.15.0 Phase 2 ETS 300 599 Ed5 MAP UAP version RE/SMG-030902PR5 SMG#20


Page 25


09.02 4.15.1 Phase 2 ETS 300 599 Ed5 MAP Pub May 1997 RE/SMG-030902PR5 SMG#2009.02 4.16.0 Phase 2 ETS 300 599 Ed6 MAP OAP version RE/SMG-030902PR6 SMG#2109.02 4.16.1 Phase 2 ETS 300 599 Ed6 MAP Pub Aug 1997 RE/SMG-030902PR6 SMG#2109.02 4.17.0 Phase 2 ETS 300 599 Ed7 MAP OAP version RE/SMG-030902PR7 SMG#2209.02 4.17.1 Phase 2 ETS 300 599 Ed7 MAP Pub Jan 1998 RE/SMG-030902PR7 SMG#2209.02 4.18.0 Phase 2 ETS 300 599 Ed8 MAP Unpublished RE/SMG-030902PR8 SMG#2309.02 4.9.0 Phase 2 ETS 300 599 MAP Pub Feb 1995 DE/SMG-030902P SMG#1209.02 5.0.0 Phase 2+ GTS 09.02 MAP Unpublished DGTS/SMG-030902Q SMG#1609.02 5.1.0 Phase 2+ GTS 09.02 MAP Unpublished DGTS/SMG-030902Q SMG#1709.02 5.10.0 Phase 2+ ETS 300 974 Ed6 MAP OAP version RE/SMG-030902QR5 SMG#2609.02 5.2.0 Phase 2+ GTS 09.02 MAP Unpublished DGTS/SMG-030902Q SMG#1809.02 5.3.0 Phase 2+ GTS 09.02 MAP Pub Aug 1996 DGTS/SMG-030902Q SMG#1909.02 5.4.0 Phase 2+ ETS 300 974 MAP UAP version DE/SMG-030902QR SMG#2009.02 5.4.1 Phase 2+ ETS 300 974 MAP Pub May 1997 DE/SMG-030902QR SMG#2009.02 5.5.0 Phase 2+ ETS 300 974 Ed2 MAP Unpublished RE/SMG-030902QR1 SMG#2109.02 5.5.1 Phase 2+ ETS 300 974 Ed2 MAP OAP version RE/SMG-030902QR1 SMG#2109.02 5.5.2 Phase 2+ ETS 300 974 Ed2 MAP Pub Oct 1997 RE/SMG-030902QR1 SMG#2109.02 5.6.0 Phase 2+ ETS 300 974 Ed3 MAP OAP version RE/SMG-030902QR2 SMG#2209.02 5.6.1 Phase 2+ ETS 300 974 Ed3 MAP Pub Jan 1998 RE/SMG-030902QR2 SMG#2209.02 5.7.0 Phase 2+ ETS 300 974 Ed4 MAP Unpublished RE/SMG-030902QR3 SMG#2309.02 5.8.0 Phase 2+ ETS 300 974 Ed4 MAP OAP version RE/SMG-030902QR3 SMG#2409.02 5.8.1 Phase 2+ ETS 300 974 Ed4 MAP Pub July 1998? RE/SMG-030902QR3 SMG#2409.02 5.9.0 Phase 2+ ETS 300 974 Ed5 MAP OAP version RE/SMG-030902QR4 SMG#2509.02 6.0.0 R97 TS 100 974 MAP Unpublished DTS/SMG-030902Q6 SMG#2509.02 6.0.0D1 R97 TS 100 974 MAP Unpublished DTS/SMG-030902Q6 SMG#2409.02 6.1.0 R97 TS 100 974 MAP Unpublished DTS/SMG-030902Q6 SMG#2609.02 6.1.1 R97 TS 100 974 MAP Pub Aug 1998 DTS/SMG-030902Q6 SMG#2609.02 6.2.0 R97 TS 100 974 MAP Pub? RTS/SMG-

030902Q6R1SMG#27

09.03 4.0.3 Phase 2 ETS 300 600 Sig IW-ISDN,PSTN,PLMN Pub Feb 1995 DE/SMG-030903P SMG#909.03 5.0.0 Phase 2/2+ GTS 09.03 Sig IW-ISDN,PSTN,PLMN Pub Dec 1996 DGTS/SMG-030903Q SMG#2009.04 4.0.2 Phase 2 ETS 300 601 IW PLMN-CSPDN Pub Sep 1994 DE/SMG-040904P SMG#909.04 5.0.0 Phase 2/2+ GTS 09.04 IW PLMN-CSPDN Pub Dec 1996 DGTS/SMG-040904Q SMG#2009.05 4.4.2 Phase 2 ETS 300 602 IW PLMN-PSPDN, PAD Pub Sep 1994 DE/SMG-040905P SMG#909.05 5.0.0 Phase 2/2+ GTS 09.05 IW PLMN-PSPDN, PAD Pub Dec 1996 DGTS/SMG-040905Q SMG#2009.06 4.4.1 Phase 2 ETS 300 603 IW PLMN-PSPDN/ISDN Pub Sep 1994 DE/SMG-040906P SMG#909.06 4.5.0 Phase 2 ETS 300 603 Am1 IW PLMN-PSPDN/ISDN Pub Mar 1995 RE/SMG-040906P SMG#1209.06 5.0.0 Phase 2+ GTS 09.06 IW PLMN-PSPDN/ISDN Pub July 1996 DGTS/SMG-040906Q SMG#1909.06 5.0.1 Phase 2+ ETS 300 975 IW PLMN-PSPDN/ISDN UAP version DE/SMG-040906Q SMG#2009.06 5.0.2 Phase 2+ ETS 300 975 IW PLMN-PSPDN/ISDN Pub May 1997 DE/SMG-040906Q SMG#2009.07 4.10.0 Phase 2 ETS 300 604 Ed4 IW PLMN-ISDN or PSTN, Pub May 1996 RE/SMG-040907PR3 SMG#1609.07 4.11.0 Phase 2 ETS 300 604 Ed5 IW PLMN-ISDN or PSTN, Pub Oct 1996 RE/SMG-040907PR4 SMG#1809.07 4.12.0 Phase 2 ETS 300 604 Ed6 IW PLMN-ISDN or PSTN, UAP version RE/SMG-040907PR5 SMG#2009.07 4.12.1 Phase 2 ETS 300 604 Ed6 IW PLMN-ISDN or PSTN, Pub May 1997 RE/SMG-040907PR5 SMG#2009.07 4.7.1 Phase 2 ETS 300 604 IW PLMN-ISDN or PSTN, Pub Oct 1994 DE/SMG-040907P SMG#1009.07 4.8.0 Phase 2 ETS 300 604 Ed2 IW PLMN-ISDN or PSTN, Pub July 1995 RE/SMG-040907P SMG#1309.07 4.9.0 Phase 2 ETS 300 604 Ed3 IW PLMN-ISDN or PSTN, Pub Sep 1995 RE/SMG-040907PR2 SMG#1409.07 5.0.0 Phase 2+ GTS 09.07 IW PLMN-ISDN or PSTN, Pub Jan 1996 DGTS/SMG-040907Q SMG#1609.07 5.0.1 Phase 2+ GTS 09.07 IW PLMN-ISDN or PSTN, Pub Mar 1996 RGTS/SMG-

040907QRSMG#17

09.07 5.1.0 Phase 2+ GTS 09.07 IW PLMN-ISDN or PSTN, Pub May 1996 RGTS/SMG-040907QR1

SMG#18

09.07 5.2.0 Phase 2+ GTS 09.07 IW PLMN-ISDN or PSTN, Pub July 1996 RGTS/SMG-040907QR2

SMG#19

09.07 5.2.1 Phase 2+ ETS 300 976 IW PLMN-ISDN or PSTN, UAP version DE/SMG-040907QR2 SMG#2009.07 5.2.2 Phase 2+ ETS 300 976 IW PLMN-ISDN or PSTN, Pub May 1997 DE/SMG-040907QR2 SMG#2009.07 5.3.0 Phase 2+ ETS 300 976 Ed2 IW PLMN-ISDN or PSTN, OAP version RE/SMG-040907QR3 SMG#2109.07 5.3.1 Phase 2+ ETS 300 976 Ed2 IW PLMN-ISDN or PSTN, Pub Sep 1997 RE/SMG-040907QR3 SMG#2109.07 5.4.0 Phase 2+ ETS 300 976 Ed3 IW PLMN-ISDN or PSTN, OAP version RE/SMG-040907QR4 SMG#2209.07 5.4.1 Phase 2+ ETS 300 976 Ed3 IW PLMN-ISDN or PSTN, Pub Jan 1998 RE/SMG-040907QR4 SMG#2209.07 5.5.0 Phase 2+ ETS 300 976 Ed4 IW PLMN-ISDN or PSTN, OAP version RE/SMG-040907QR5 SMG#2309.07 5.5.1 Phase 2+ ETS 300 976 Ed4 IW PLMN-ISDN or PSTN, Pub Mar 1998 RE/SMG-040907QR5 SMG#2309.07 5.6.0 Phase 2+ ETS 300 976 Ed5 IW PLMN-ISDN or PSTN, OAP version RE/SMG-040907QR6 SMG#2409.07 5.6.1 Phase 2+ ETS 300 976 Ed5 IW PLMN-ISDN or PSTN, Pub July 1998 RE/SMG-040907QR6 SMG#2409.07 5.7.0 Phase 2+ ETS 300 976 Ed6 IW PLMN-ISDN or PSTN, OAP version RE/SMG-040907QR7 SMG#2509.07 5.7.1 Phase 2+ ETS 300 976 Ed6 IW PLMN-ISDN or PSTN, Pub Oct 1998 RE/SMG-040907QR7 SMG#2509.08 4.1.1 Phase 2 ETS 300 626 BSSAP on E-Interface Pub July 1995 DE/SMG-030908P SMG#1309.08 5.0.0 Phase 2/2+ GTS 09.08 BSSAP on E-Interface Pub Dec 1996 DGTS/SMG-030908Q SMG#20


Page 26


09.08 5.1.0 Phase 2+ GTS 09.08 BSSAP on E-Interface Pub Apr 1997 RGTS/SMG-030908QR

SMG#21

09.10 4.2.2 Phase 2 ETS 300 605 mapping MS-BSS BSS-MSC Pub Feb 1995 DE/SMG-030910P SMG#1009.10 4.3.0 Phase 2 ETS 300 605 Ed2 mapping MS-BSS BSS-MSC Pub Sep 1996 RE/SMG-030910P SMG#1709.10 4.4.0 Phase 2 ETS 300 605 Ed3 mapping MS-BSS BSS-MSC OAP version RE/SMG-030910PR1 SMG#2309.10 4.4.1 Phase 2 ETS 300 605 Ed3 mapping MS-BSS BSS-MSC Pub May 1998 RE/SMG-030910PR1 SMG#2309.10 5.0.0 Phase 2+ GTS 09.10 mapping MS-BSS BSS-MSC Pub Mar 1996 DGTS/SMG-030910Q SMG#1709.10 5.1.0 Phase 2+ GTS 09.10 mapping MS-BSS BSS-MSC Pub May 1996 RGTS/SMG-

030910QRSMG#18

09.10 5.2.0 Phase 2+ GTS 09.10 mapping MS-BSS BSS-MSC Pub Nov 1997 RGTS/SMG-030910QR1

SMG#23

09.10 6.0.0 R97 GTS 09.10 mapping MS-BSS BSS-MSC Unpublished RGTS/SMG-030910Q6

SMG#25

09.10 6.0.1 R97 TS 100 605 mapping MS-BSS BSS-MSC Pub July 1998 DTS/SMG-030910Q6 SMG#2609.11 4.4.1 Phase 2 ETS 300 606 Signalling IW for SS Pub Feb 1995 DE/SMG-030911P SMG#1209.11 4.5.0 Phase 2 ETS 300 606 Am1 Signalling IW for SS Pub July 1995 RE/SMG-030911P SMG#1309.11 4.6.0 Phase 2 ETS 300 606 Ed2 Signalling IW for SS UAP version RE/SMG-030911PR2 SMG#1909.11 4.6.1 Phase 2 ETS 300 606 Ed2 Signalling IW for SS Pub Dec 1996 RE/SMG-030911PR2 SMG#1909.11 5.0.0 Phase 2+ GTS 09.11 Signalling IW for SS Pub May 1996 DGTS/SMG-030911Q SMG#1809.11 5.1.0 Phase 2+ GTS 09.11 Signalling IW for SS Pub July 1996 RGTS/SMG-

030911QR1SMG#19

09.11 6.0.0 R97 TS 100 606 Signalling IW for SS Pub July 1998 DTS/SMG-030911Q6 SMG#2609.12 4.0.0 Phase 2 ETS 300 646-1 ISUP v2 for ISDN-PLMN PE version DE/SPS-0102309.12 4.1.0 Phase 2 ETS 300 646-1 ISUP v2 for ISDN-PLMN Vote version DE/SPS-0102309.12 4.1.1 Phase 2 ETS 300 646-1 ISUP v2 for ISDN-PLMN Pub May 1997 DE/SPS-0102309.12 4.2.0 Phase 2 ETS 300 646-1

Ed2ISUP v2 for ISDN-PLMN Unpublished REN/SPS-01047-1 SMG#22

09.13 6.0.0 R97 TS 101 392 Sig I/W ASE and MAP Pub Oct 1998 DTS/SMG-030913Q7 SMG#2709.16 6.0.0 R97 TS 101 345 GPRS Gs inter lower layer and Unpublished DTS/SMG-030916Q6 SMG#2509.16 6.0.1 R97 TS 101 345 GPRS Gs inter lower layer and Pub July 1998 DTS/SMG-030916Q6 SMG#2609.18 6.0.0 R97 TS 101346 GPRS Gs inter app layer Unpublished DTS/SMG-030918Q6 SMG#2509.18 6.1.0 R97 TS 101 346 GPRS Gs inter app layer Pub July 1998 DTS/SMG-030918Q6 SMG#2609.18 6.2.0 R97 TS 101 346 GPRS Gs inter app layer Pub Oct 1998 RTS/SMG-

030918Q6R1SMG#27

09.60 5.0.0 Phase 2+ EN 301 347 IW PLMN GPRS-PDN Unpublished DEN/SMG-030960Q6 SMG#2409.60 6.0.0 R97 EN 301 347 IW PLMN GPRS-PDN Unpublished DEN/SMG-030960Q6 SMG#2509.60 6.1.0 R97 EN 301 347 IW PLMN GPRS-PDN PE version DEN/SMG-030960Q6 SMG#2609.60 6.2.0 R97 EN 301 347 IW PLMN GPRS-PDN Unpublished DEN/SMG-030960Q6 SMG#2709.60 6.2.1 R97 EN 301 347 IW PLMN GPRS-PDN Unpublished DEN/SMG-030960Q6 SMG#2709.60 6.2.2 R97 EN 301 347 IW PLMN GPRS-PDN Unpublished DEN/SMG-030960Q6 SMG#2709.61 5.0.0 Phase 2+ TS 101 348 GPRS PDN Unpublished DTS/SMG-040961Q6 SMG#2309.61 6.0.0 R97 TS 101 348 GPRS PDN Unpublished DTS/SMG-040961Q6 SMG#2509.61 6.1.0 R97 TS 101 348 GPRS PDN Pub Aug 1998 DTS/SMG-040961Q6 SMG#2609.61 6.2.0 R97 TS 101 348 GPRS PDN Pub Sept 1998 RTS/SMG-040961Q6 SMG#2609.61 6.3.0 R97 TS 101 348 GPRS PDN Pub Oct 1998 RTS/SMG-

040961Q6R1SMG#27

09.78 5.0.0 Phase 2+ TS 101 046 CAMEL CAP Unpublished DTS/SMG-030978Q SMG#2109.78 5.0.1 Phase 2+ TS 101 046 CAMEL CAP Pub Apr 1997 DTS/SMG-030978Q SMG#2109.78 5.1.0 Phase 2+ TS 101 046 CAMEL CAP Pub Aug 1997 RTS/SMG-

030978QR1SMG#22

09.78 5.2.0 Phase 2+ TS 101 046 CAMEL CAP Pub Nov 1997 RTS/SMG-030978QR2

SMG#23

09.78 5.3.0 Phase 2+ TS 101 046 CAMEL CAP Pub Jan 1998 RTS/SMG-030978QR3

SMG#24

09.78 5.4.0 Phase 2+ TS 101 046 CAMEL CAP Unpublished RTS/SMG-030978QR4

SMG#25

09.78 5.5.0 Phase 2+ TS 101 046 CAMEL CAP Pub July 1998 RTS/SMG-030978QR5

SMG#26

09.78 6.0.0 R97 TS 101 046 CAMEL CAP Unpublished RTS/SMG-030978Q6 SMG#2509.78 6.1.0 R97 TS 101 046 CAMEL CAP Pub Aug 1998 RTS/SMG-030978Q6 SMG#2609.78 6.2.0 R97 TS 101 046 CAMEL CAP Unpublished RTS/SMG-

030978Q6R1SMG#27

09.78 6.2.1 R97 TS 101 046 CAMEL CAP Pub Nov 1998 ? RTS/SMG-030978Q6R1

SMG#27

09.90 4.1.0 Phase 2 ETR 111 IW Ph1 infastr & Ph2 MS Pub Oct 1993 DTR/SMG-000990P SMG#809.90 4.4.1 Phase 2 ETR 111 Ed2 IW Ph1 infastr & Ph2 MS Pub Apr 1995 RTR/SMG-000990P SMG#1109.90 4.5.0 Phase 2 ETR 111 Ed3 IW Ph1 infastr & Ph2 MS Pub Aug 1995 RTR/SMG-

000990PR2SMG#16

09.90 4.6.0 Phase 2 ETR 111 Ed4 IW Ph1 infastr & Ph2 MS Pub Nov 1995 RTR/SMG-000990PR3

SMG#17


Page 27


09.90 4.7.0 Phase 2 ETR 111 Ed5 IW Ph1 infastr & Ph2 MS Pub May 1996 RTR/SMG-000990PR4

SMG#18

09.90 4.8.0 Phase 2 ETR 111 Ed6 IW Ph1 infastr & Ph2 MS Pub Aug 1996 RTR/SMG-000990PR5

SMG#19

09.90 4.9.0 Phase 2 ETR 111 Ed7 IW Ph1 infastr & Ph2 MS Pub Oct 1997 RTR/SMG-000990PR SMG#2309.90 5.0.0 Phase 2+ GTS 09.90 IW Ph1 infastr & Ph2 MS Pub Mar 1996 DGTS/SMG-000990Q SMG#1709.90 5.1.0 Phase 2+ GTS 09.90 IW Ph1 infastr & Ph2 MS Unpublished RGTS/SMG-

000990QR1SMG#22

09.91 4.0.1 Phase 2 ETR 174 IW SIM/ME Int Ph1 & Ph2 Pub Apr 1995 DTR/SMG-090991P SMG#1009.91 5.0.0 Phase 2/2+ ETR xxx IW SIM/ME Int Ph1 & Ph2 Unpublished DTR/SMG-090991Q SMG#2009.94 4.1.0 Phase 2 ETR 200 Phase 1 MS faults Pub Aug 1995 DTR/SMG-000994P SMG#1509.94 4.2.0 Phase 2 ETR 200 Ed2 Phase 1 MS faults Pub Nov 1995 RTR/SMG-000994P SMG#1609.94 4.3.0 Phase 2 ETR 200 Ed3 Phase 1 MS faults Pub Aug 1996 RTR/SMG-

000994PR2SMG#19

09.94 4.4.0 Phase 2 ETR 200 Ed4 Phase 1 MS faults Unpublished RTR/SMG-000994PR3

SMG#23

09.94 5.0.0 Phase 2/2+ ETR 361 Phase 1 MS faults Pub Dec 1996 DTR/SMG-030994Q SMG#2010.00 5.1.1 Phase 2+ TC-TR 010 Ph 2+ feature descripts Unpublished DTR/SMG-001000Q SMG#1910.00 5.1.2 Phase 2+ TC-TR 010 Ph 2+ feature descripts Pub Sep 1996 DTR/SMG-001000Q SMG#1910.00 5.2.0 Phase 2+ Miscellaneous Ph 2+ feature descripts Unpublished MI/SMG-00Featre_Q SMG#2010.01 0.0.3 Phase 2+ TS 101 xxx Options & realeases Draft DTS/SMG-001001Q SMG#2310.02 1.0.0 Phase 2+ Miscellaneous MAP Information Unpublished MI/SMG-

00MAP_EX_QSMG#25

10.20 5.0.0 Phase 2+ ETR 363 Lawful Intercept reqmts Unpublished DTR/SMG-101020Q SMG#1910.20 5.0.1 Phase 2/2+ ETR 363 Lawful Intercept reqmts Pub Jan 1997 DTR/SMG-101020Q SMG#2010.31 5.0.0 Phase 2+ Miscellaneous Fraud Info Gat (FIG) Prjt Unpublished MI/SMG-00FIGS_Q SMG#2110.43 1.2.0 R98 Miscellaneous SoLSA Project Draft MI/SMG-00SoLSA_Q SMG#2510.56 1.0.0 R98 Miscellaneous CTS Project Draft MI/SMG-00CTS_Q SMG#2510.57 7.0.0 R98 Miscellaneous Mexe Project Draft MI/SMG-00MEXE_Q SMG#2510.60 5.0.0 Phase 2+ Miscellaneous GPRS Project Unpublished MI/SMG-00GPRS_Q SMG#2110.60 5.1.0 Phase 2+ Miscellaneous GPRS Project Unpublished MI/SMG-00GPRS_Q SMG#2210.60 5.2.0 Phase 2+ Miscellaneous GPRS Project Unpublished MI/SMG-00GPRS_Q SMG#2410.60 5.3.0 Phase 2+ Miscellaneous GPRS Project Unpublished MI/SMG-00GPRS_Q SMG#2510.60 6.0.0 R97 Miscellaneous GPRS Project Unpublished MI/SMG-00GPRS_Q SMG#2510.68 5.0.0 Phase 2+ Miscellaneous ASCI Introduction Unpublished MI/SMG-

00ASCI_Ph2_QSMG#21

10.78 1.6.0 Phase 2+ Miscellaneous CAMEL PH 2 Project Unpublished MI/SMG-00CAMEL_Q SMG#2211.10 4.9.0 Phase 2 I-ETS 300 607-1 MS Conformance PE version DE/SMG-071110P-1 SMG#11.10-1 4.13.0 Phase 2 ETS 300 607-1 MS Conformance Pub Mar 1996 DE/SMG-071110P-1 SMG#1611.10-1 4.14.0 Phase 2 ETS 300 607-1

Ed2MS Conformance Unpublished RE/SMG-071110P-1 SMG#17

11.10-1 4.15.1 Phase 2 ETS 300 607-1Ed2

MS Conformance Pub Nov 1996 RE/SMG-071110P-1 SMG#18

11.10-1 4.16.0 Phase 2 ETS 300 607-1Ed3

MS Conformance UAP version RE/SMG-071110PR-1 SMG#19

11.10-1 4.16.1 Phase 2 ETS 300 607-1Ed3

MS Conformance Pub Jan 1997 RE/SMG-071110PR-1 SMG#19

11.10-1 4.17.0 Phase 2 ETS 300 607-1Ed4

MS Conformance UAP version RE/SMG-071110PR2-1

SMG#20

11.10-1 4.17.1 Phase 2 ETS 300 607-1Ed4

MS Conformance Pub May 1997 RE/SMG-071110PR2-1

SMG#20

11.10-1 4.18.0 Phase 2 ETS 300 607-1Ed5

MS Conformance OAP version RE/SMG-071110PR3-1

SMG#21

11.10-1 4.18.1 Phase 2 ETS 300 607-1Ed5

MS Conformance Pub Sep 1997 RE/SMG-071110PR3-1

SMG#21

11.10-1 4.19.0 Phase 2 ETS 300 607-1Ed6


SMG#22

11.10-1 4.19.1 Phase 2 ETS 300 607-1Ed6

MS Conformance Pub Jan 1998 RE/SMG-071110PR4-1

SMG#22

11.10-1 4.20.0 Phase 2 ETS 300 607-1Ed7


SMG#23

11.10-1 4.20.1 Phase 2 ETS 300 607-1Ed7

MS Conformance Pub Apr 1998 RE/SMG-071110PR5-1

SMG#23

11.10-1 4.21.0 Phase 2 ETS 300 607-1Ed8


SMG#24

11.10-1 4.21.1 Phase 2 ETS 300 607-1Ed8

MS Conformance Pub Aug 1998 RE/SMG-071110PR6-1

SMG#24

11.10-1 4.22.0 Phase 2 ETS 300 607-1Ed9


SMG#25

11.10-1 4.22.1 Phase 2 ETS 300 607-1Ed9

MS Conformance Pub Oct 1998 RE/SMG-071110PR7-1

SMG#25


Page 28


11.10-1 4.23.0 Phase 2 ETS 300 607-1Ed10


SMG#26

11.10-1 5.0.0 Phase 2+ EN MS Conformance Unpublished DEN/SMG-071110Q-1

SMG#20?

11.10-1 5.1.0 Phase 2+ TS 100 607-1 MS Conformance Pub May 1997 DTS/SMG-071110Q-1 SMG#2111.10-1 5.2.0 Phase 2+ TS 100 607-1 MS Conformance Pub Aug 1997 RTS/SMG-071110Q-1 SMG#2211.10-1 5.3.0 Phase 2+ TS 100 607-1 MS Conformance Pub Nov 1997 RTS/SMG-

071110QR1-1SMG#23

11.10-1 5.4.0 Phase 2+ TS 100 607-1 MS Conformance Pub Feb 1998 RTS/SMG-071110QR2-1

SMG#24

11.10-1 5.5.0 Phase 2+ EN 301 607-1 MS Conformance OAP version DEN/SMG-071110QR3-1

SMG#25

11.10-1 5.5.1 Phase 2+ EN 301 607-1 MS Conformance Pub Oct 1998 DEN/SMG-071110QR3-1

SMG#25

11.10-1 5.6.0 Phase 2+ EN 301 607-1 MS Conformance OAP version REN/SMG-071110QR4-1

SMG#26

11.10-1 6.0.0 R97 EN MS Conformance (GPRS) Draft DEN/SMG-071110Q6-1

SMG#28?

11.10-2 4.14.0 Phase 2 ETS 300 607-2 MS Conformance PICS PE version DE/SMG-071110P-2 SMG#1711.10-2 4.15.0 Phase 2 ETS 300 607-2 MS Conformance PICS Pub Oct 1996 DE/SMG-071110P-2 SMG#1811.10-2 5.0.0 ? Phase 2+ EN 301 607-2 MS Conformance PICS Draft DEN/SMG-071110Q-

2SMG#25?

11.10-2 6.0.0 R97 EN MS Conform PICS (GPRS) Draft DEN/SMG-071110Q6-2

SMG#28?

11.10-3 4.14.0 Phase 2 ETS 300 607-3 MS Conformance TTCN PE version DE/SMG-071110P-3 SMG#1711.10-3 4.15.0 Phase 2 ETS 300 607-3 MS Conformance TTCN Pub Sep 1996 DE/SMG-071110P-3 SMG#1811.10-3 4.16.0 Phase 2 ETS 300 607-3

Ed2MS Conformance TTCN UAP version RE/SMG-071110P-3 SMG#19

11.10-3 4.16.1 Phase 2 ETS 300 607-3Ed2

MS Conformance TTCN Pub Jan 1997 RE/SMG-071110P-3 SMG#19

11.10-3 4.17.0 Phase 2 ETS 300 607-3Ed3

MS Conformance TTCN UAP version RE/SMG-071110PR1-3

SMG#20

11.10-3 4.17.1 Phase 2 ETS 300 607-3Ed3

MS Conformance TTCN Pub May 1997 RE/SMG-071110PR1-3

SMG#20

11.10-3 4.18.0 Phase 2 ETS 300 607-3Ed4

MS Conformance TTCN OAP version RE/SMG-071110PR2-3

SMG#21

11.10-3 4.18.1 Phase 2 ETS 300 607-3Ed4

MS Conformance TTCN Pub Sep 1997 RE/SMG-071110PR2-3

SMG#21

11.10-3 4.19.0 Phase 2 ETS 300 607-3Ed5


SMG#22

11.10-3 4.19.1 Phase 2 ETS 300 607-3Ed5

MS Conformance TTCN Pub Jan 1998 RE/SMG-071110PR3-3

SMG#22

11.10-3 4.20.0 Phase 2 ETS 300 607-3Ed6


SMG#23

11.10-3 4.20.1 Phase 2 ETS 300 607-3Ed6

MS Conformance TTCN Pub Apr 1998 RE/SMG-071110PR4-3

SMG#23

11.10-3 4.21.0 Phase 2 ETS 300 607-3Ed7


SMG#24

11.10-3 4.21.1 Phase 2 ETS 300 607-3Ed7

MS Conformance TTCN Pub Aug 1998 RE/SMG-071110PR5-3

SMG#24

11.10-3 4.22.0 Phase 2 ETS 300 607-3Ed8


SMG#25

11.10-3 4.22.1 Phase 2 ETS 300 607-3Ed8

MS Conformance TTCN Pub Oct 1998 RE/SMG-071110PR6-3

SMG#25

11.10-3 4.23.0 Phase 2 ETS 300 607-3Ed9


SMG#26

11.10-3 5.0.0 Phase 2+ EN MS Conformance TTCN Unpublished DEN/SMG-071110Q-3

SMG#26

11.10-3 6.0.0 R97 EN MS ConformTTCN (GPRS) Draft DEN/SMG-071110Q6-3

SMG#28?

11.11 4.13.0 Phase 2 ETS 300 608 SIM ME interface Vote version DE/SMG-091111P SMG#11.11 4.13.1 Phase 2 ETS 300 608 SIM ME interface Pub Jan 1995 DE/SMG-091111P SMG#1211.11 4.14.0 Phase 2 ETS 300 608 Am1 SIM ME interface Pub July 1995 RE/SMG-091111P1 SMG#1311.11 4.15.0 Phase 2 ETS 300 608 Ed2 SIM ME interface Pub Jan 1996 RE/SMG-091111PR2 SMG#1511.11 4.16.0 Phase 2 ETS 300 608 Ed3 SIM ME interface Pub May 1996 RE/SMG-091111PR3 SMG#1611.11 4.17.0 Phase 2 ETS 300 608 Edx SIM ME interface Unpublished RE/SMG-091111PR4 SMG#1811.11 4.18.0 Phase 2 ETS 300 608 Ed4 SIM ME interface Pub Dec 1996 RE/SMG-091111PR4 SMG#1911.11 4.18.1 Phase 2 ETS 300 608 Ed5 SIM ME interface Pub May 1997 RE/SMG-091111PR5 SMG#2011.11 4.18.2 Phase 2 ETS 300 608 Ed6 SIM ME interface OAP version RE/SMG-091111PR6 SMG#2111.11 4.18.3 Phase 2 ETS 300 608 Ed6 SIM ME interface Pub Aug 1997 RE/SMG-091111PR6 SMG#2111.11 4.19.0 Phase 2 ETS 300 608 Ed7 SIM ME interface OAP version RE/SMG-091111PR7 SMG#22


Page 29


11.11 4.19.1 Phase 2 ETS 300 608 Ed7 SIM ME interface Pub Jan 1998 RE/SMG-091111PR7 SMG#2211.11 4.20.0 Phase 2 ETS 300 608 Ed8 SIM ME interface OAP version RE/SMG-091111PR8 SMG#2511.11 4.20.1 Phase 2 ETS 300 608 Ed8 SIM ME interface Pub Oct 1998 RE/SMG-091111PR8 SMG#2711.11 4.9.0 Phase 2 ETS 300 608 SIM ME interface PE version DE/SMG-091111P SMG#11.11 5.0.0 Phase 2+ GTS 11.11 SIM ME interface Pub Jan 1996 DGTS/SMG-091111Q SMG#1611.11 5.1.0 Phase 2+ GTS 11.11 SIM ME interface Pub Mar 1996 RGTS/SMG-

091111QRSMG#17

11.11 5.10.0 Phase 2+ ETS 300 977 Ed5 SIM ME interface OAP version RE/SMG-091111QR6 SMG#2611.11 5.2.0 Phase 2+ GTS 11.11 SIM ME interface Unpublished RGTS/SMG-

091111QRSMG#18

11.11 5.3.0 Phase 2+ GTS 11.11 SIM ME interface Pub July 1996 RGTS/SMG-091111QR1

SMG#19

11.11 5.4.0 Phase 2+ ETS 300 977 SIM ME interface UAP version DE/SMG-091111QR2 SMG#2011.11 5.4.1 Phase 2+ ETS 300 977 SIM ME interface Pub May 1997 DE/SMG-091111QR2 SMG#2011.11 5.5.0 Phase 2+ ETS 300 977 Ed2 SIM ME interface OAP version RE/SMG-091111QR3 SMG#2111.11 5.5.1 Phase 2+ ETS 300 977 Ed2 SIM ME interface Pub Oct 1997 RE/SMG-091111QR3 SMG#2111.11 5.6.0 Phase 2+ ETS 300 977 Ed3 SIM ME interface OAP version RE/SMG-091111QR4 SMG#2211.11 5.6.1 Phase 2+ ETS 300 977 Ed3 SIM ME interface Pub Jan 1998 RE/SMG-091111QR4 SMG#2211.11 5.7.0 Phase 2+ ETS 300 977 Ed4 SIM ME interface Unpublished RE/SMG-091111QR5 SMG#2311.11 5.8.0 Phase 2+ ETS 300 977 Ed4 SIM ME interface Unpublished RE/SMG-091111QR5 SMG#2411.11 5.9.0 Phase 2+ ETS 300 977 Ed4 SIM ME interface OAP version RE/SMG-091111QR5 SMG#2511.11 5.9.1 Phase 2+ ETS 300 977 Ed4 SIM ME interface Pub Oct 1998 RE/SMG-091111QR5 SMG#2511.11 6.0.0 R97 TS 100 977 SIM ME interface Unpublished DTS/SMG-091111Q6 SMG#2511.11 6.1.0 R97 TS 100 977 SIM ME interface Pub July 1998 DTS/SMG-091111Q6 SMG#2611.11 7.0.0 R98 TS 100 977 SIM ME interface Unpublished DTS/SMG-091111Q7 SMG#2611.11 7.1.0 R98 TS 100 977 SIM ME interface Unpublished DTS/SMG-091111Q7 SMG#2711.12 4.0.0 Phase 2 ETS 300 641 3V SIM-ME PE version DE/SMG-091112Q SMG#1511.12 4.1.0 Phase 2 ETS 300 641 3V SIM-ME Unpublished DE/SMG-091112Q SMG#1711.12 4.1.1 Phase 2 ETS 300 641 3V SIM-ME Vote version DE/SMG-091112Q SMG#1911.12 4.1.2 Phase 2 ETS 300 641 3V SIM-ME Pub Dec 1996 DE/SMG-091112Q SMG#1911.12 4.2.0 Phase 2 ETS 300 641 Ed2 3V SIM-ME OAP version RE/SMG-091112QR SMG#2111.12 4.2.1 Phase 2 ETS 300 641 Ed2 3V SIM-ME Pub Aug 1997 RE/SMG-091112QR SMG#2111.12 4.3.0 Phase 2 ETS 300 641 Ed3 3V SIM-ME OAP version RE/SMG-091112QR1 SMG#2311.12 4.3.1 Phase 2 ETS 300 641 Ed3 3V SIM-ME Pub Mar 1998 RE/SMG-091112QR1 SMG#2311.12 5.0.0 Phase 2+ Miscellaneous 3V SIM-ME Unpublished MI/SMG-

00SIM_3V_QSMG#20

11.14 5.0.0 Phase 2+ GTS 11.14 Phase 2+ SIM app Tool kit Unpublished DGTS/SMG-091114Q SMG#1811.14 5.1.0 Phase 2+ GTS 11.14 Phase 2+ SIM app Tool kit Pub Aug 1996 DGTS/SMG-091114Q SMG#1911.14 5.2.0 Phase 2+ GTS 11.14 Phase 2+ SIM app Tool kit Pub Dec 1996 RGTS/SMG-

091114QRSMG#20

11.14 5.3.0 Phase 2+ GTS 11.14 Phase 2+ SIM app Tool kit Pub Apr 1997 RGTS/SMG-091114QR1

SMG#21

11.14 5.4.0 Phase 2+ GTS 11.14 Phase 2+ SIM app Tool kit Pub July 1997 RGTS/SMG-091114QR2

SMG#22

11.14 5.5.0 Phase 2+ GTS 11.14 Phase 2+ SIM app Tool kit Unpublished RGTS/SMG-091114QR3

SMG#23

11.14 5.6.0 Phase 2+ GTS 11.14 Phase 2+ SIM app Tool kit Unpublished RGTS/SMG-091114QR3

SMG#24

11.14 5.7.0 R96 GTS 11.14 Phase 2+ SIM app Tool kit Pub Apr 1998 RGTS/SMG-091114QR3

SMG#25

11.14 5.8.0 R96 GTS 11.14 Phase 2+ SIM app Tool kit Pub July 1998 RGTS/SMG-091114QR4

SMG#26

11.14 5.9.0 R96 GTS 11.14 Phase 2+ SIM app Tool kit Pub Nov 1998? RGTS/SMG-091114QR5

SMG#27

11.14 6.0.0 R97 TS 101 267 Phase 2+ SIM app Tool kit Pub Apr 1998 DTS/SMG-091114Q6 SMG#2511.14 6.1.0 R97 TS 101 267 Phase 2+ SIM app Tool kit Pub July 1998 DTS/SMG-

091114Q6R1SMG#26

11.14 6.2.0 R97 TS 101 267 Phase 2+ SIM app Tool kit Pub Nov 1998? RTS/SMG-091114Q6R2

SMG#27

11.14 7.0.0 R98 TS 101 267 Phase 2+ SIM app Tool kit Unpublished DTS/SMG-091114Q7 SMG#2611.14 7.1.0 R98 TS 101 267 Phase 2+ SIM app Tool kit Unpublished DTS/SMG-091114Q7 SMG#2711.15 2.0.0 Phase 2+ Miscellaneous SIM TK security feasibility Unpublished MI/SMG-

00SIM_TK_QSMG#22

11.17 1.0.0 R98 EN 301 086 SIM test Draft DEN/SMG-091117P SMG#2311.18 1.0.0 R98 EN 301 116 1.8V SIM-ME Draft DEN/SMG-091118Q SMG#28

?11.21 4.10.0 Phase 2 I-ETS 300 609-

1Ed5BSS Radio aspects OAP version RI/SMG-081121PR3 SMG#25

11.21 4.10.1 Phase 2 I-ETS 300 609-1Ed5

BSS Radio aspects Pub Oct 1998 RI/SMG-081121PR3 SMG#25


Page 30


11.21 4.11.0 Phase 2 I-ETS 300 609-1Ed6

BSS Radio aspects OAP version RI/SMG-081121PR4 SMG#26

11.21 4.4.1 Phase 2 I-ETS 300 609-1 BSS Radio aspects PE version DI/SMG-081121P SMG#1611.21 4.5.0 Phase 2 I-ETS 300 609-1 BSS Radio aspects Unpublished DI/SMG-081121P SMG#1711.21 4.6.0 Phase 2 I-ETS 300 609-1 BSS Radio aspects Pub Sep 1996 DI/SMG-081121P SMG#1811.21 4.7.0 Phase 2 I-ETS 300 609-

1Ed2BSS Radio aspects UAP version RI/SMG-081121P SMG#20

11.21 4.7.1 Phase 2 I-ETS 300 609-1Ed2

BSS Radio aspects Pub Apr 1997 RI/SMG-081121P SMG#20

11.21 4.8.0 Phase 2 I-ETS 300 609-1Ed3


11.21 4.8.1 Phase 2 I-ETS 300 609-1Ed3

BSS Radio aspects Pub Feb 1998 RI/SMG-081121PR1 SMG#22

11.21 4.9.1 Phase 2 I-ETS 300 609-1Ed4


11.21 4.9.2 Phase 2 I-ETS 300 609-1Ed4

BSS Radio aspects Pub July 1998 RI/SMG-081121PR2 SMG#23

11.21 5.0.0 Phase 2+ TS 101 087 BSS Radio aspects Pub Aug 1997 DTS/SMG-081121Q SMG#2211.21 5.1.0 Phase 2&2+ EN 301 087 BSS Radio aspects PE version DEN/SMG-081121Q SMG#2311.21 5.2.0 Phase 2&2+ EN 301 087 BSS Radio aspects Unpublished DEN/SMG-081121Q SMG#2511.21 5.3.0 Phase 2&2+ EN 301 087 BSS Radio aspects Vote version DEN/SMG-081121Q SMG#2611.21 5.3.1 Phase 2&2+ EN 301 087 BSS Radio aspects Pub Nov 1998 ? DEN/SMG-081121Q SMG#2611.21 5.4.0 Phase 2&2+ EN 301 087 BSS Radio aspects OAP version REN/SMG-

081121QR1SMG#26

11.22 4.1.1 Phase 2 ETR BTS Ancillary Equip Unpublished DTR/SMG-081122P SMG#1811.22 4.1.2 Phase 2 ETR BTS Ancillary Equip Unpublished DTR/SMG-081122P SMG#2011.22 4.1.3 Phase 2 TR BTS Ancillary Equip Unpublished DTR/SMG-081122P SMG#2111.22 4.1.4 Phase 2 TR 101 075 BTS Ancillary Equip Pub June 1997 DTR/SMG-081122P SMG#2111.23 4.5.0 Phase 2 ETS 300 609-2 BTS Sig Aspects PE version DE/SMG-081123P SMG#1911.23 4.6.0 Phase 2 ETS 300 609-2 BTS Sig Aspects Vote version DE/SMG-081123P SMG#2111.23 4.6.1 Phase 2 ETS 300 609-2 BTS Sig Aspects Pub June 1997 DE/SMG-081123P SMG#2111.23 4.7.0 Phase 2 ETS 300 609-2

Ed2BTS Sig Aspects OAP version RE/SMG-081123PR1 SMG#22

11.23 4.7.1 Phase 2 ETS 300 609-2Ed2

BTS Sig Aspects Pub Feb 1998 RE/SMG-081123PR1 SMG#22

11.23 4.8.0 Phase 2 ETS 300 609-2Ed3

BTS Sig Aspects Unpublished RE/SMG-081123PR2 SMG#23

11.23 4.9.0 Phase 2 ETS 300 609-2Ed3

BTS Sig Aspects OAP version RE/SMG-081123PR2 SMG#25

11.23 4.9.1 Phase 2 ETS 300 609-2Ed3

BTS Sig Aspects Pub Oct 1998 RE/SMG-081123PR2 SMG#25

11.24 4.0.0 Phase 2 ETS 300 609-3 BSS Full-rate speech Unpublished DE/SMG-081124P SMG#1411.24 4.1.0 Phase 2 ETS 300 609-3 BSS Full-rate speech PE version DE/SMG-081124P SMG#2011.24 4.1.1 Phase 2 ETS 300 609-3 BSS Full-rate speech Unpublished DE/SMG-081124P SMG#2211.24 4.2.0 Phase 2 ETS 300 609-3 BSS Full-rate speech Unpublished DE/SMG-081124P SMG#2511.24 4.3.0 Phase 2 ETS 300 609-3 BSS Full-rate speech Vote version DE/SMG-081124P SMG#2711.26 4.2.0 Phase 2 ETS 300 609-4 GSM Repeaters PE version DE/SMG-081126P SMG#1811.26 4.2.1 Phase 2 ETS 300 609-4 GSM Repeaters Vote version DE/SMG-081126P SMG#2011.26 4.2.2 Phase 2 ETS 300 609-4 GSM Repeaters Pub Jan 1997 DE/SMG-081126P SMG#2011.26 4.3.0 Phase 2 ETS 300 609-4 GSM Repeaters Unpublished RE/SMG-081126PQ SMG#2311.26 5.0.1 Phase 2/2+ ETS 300 609-4

Ed2GSM Repeaters OAP version RE/SMG-081126PQ SMG#23

11.26 5.0.2 Phase 2/2+ ETS 300 609-4Ed2

GSM Repeaters Pub July 1998 RE/SMG-081126PQ SMG#23

11.26 5.1.0 Phase 2/2+ ETS 300 609-4Ed3

GSM Repeaters OAP version RE/SMG-081126PQR1

SMG#25

11.26 5.1.1 Phase 2/2+ ETS 300 609-4Ed3

GSM Repeaters Pub Oct 1998 RE/SMG-081126PQR1

SMG#25

11.26 5.2.0 Phase2&/2+

ETS 300 609-4Ed4

GSM Repeaters OAP version RE/SMG-081126PQR2

SMG#26

12.00 4.3.0 Phase 2 ETS 300 612-1 Objctves & struct of NM PE version DE/SMG-061200P SMG#1512.00 4.5.0 Phase 2 ETS 300 612-1 Objctves & struct of NM Vote version DE/SMG-061200P SMG#1712.00 4.5.1 Phase 2 ETS 300 612-1 Objctves & struct of NM Pub Aug 1996 DE/SMG-061200P SMG#1712.00 4.6.0 Phase 2 ETS 300 612-1 Objctves & struct of NM Unpublished DE/SMG-061200P SMG#2312.01 4.3.1 Phase 2 ETS 300 612-2 NM aspts GSM/DCS 1800 PE version DE/SMG-061201P SMG#1112.01 4.4.0 Phase 2 ETS 300 612-2 NM aspts GSM/DCS 1800 Vote version DE/SMG-061201P SMG#1712.01 4.4.1 Phase 2 ETS 300 612-2 NM aspts GSM/DCS 1800 Pub Aug 1996 DE/SMG-061201P SMG#1712.02 4.4.0 Phase 2 ETS 300 613 Sub, ME & ser data admin PE version DE/SMG-061202P SMG#1512.02 4.5.0 Phase 2 ETS 300 613 Sub, ME & ser data admin Unpublished DE/SMG-061202P SMG#1612.02 4.6.0 Phase 2 ETS 300 613 Sub, ME & ser data admin Vote version DE/SMG-061202P SMG#17


Page 31


12.02 4.6.1 Phase 2 ETS 300 613 Sub, ME & ser data admin Pub June 1996 DE/SMG-061202P SMG#1712.02 5.0.0 Phase 2+ TS 100 613 Sub, ME & ser data admin Unpublished DTS/SMG-061202Q SMG#2212.02 5.0.1 Phase 2+ TS 100 613 Sub, ME & ser data admin Pub July 1998 DTS/SMG-061202Q SMG#2312.03 4.1.1 Phase 2 ETS 300 614 Security management PE version DE/SMG-061203P SMG#1412.03 4.2.0 Phase 2 ETS 300 614 Security management Vote version DE/SMG-061203P SMG#1712.03 4.2.1 Phase 2 ETS 300 614 Security management Pub June 1996 DE/SMG-061203P SMG#1712.04 4.2.1 Phase 2 ETS 300 615 Perf data measurements PE version DE/SMG-061204P SMG#1312.04 4.3.0 Phase 2 ETS 300 615 Perf data measurements Vote version DE/SMG-061204P SMG#1712.04 4.3.1 Phase 2 ETS 300 615 Perf data measurements Pub Aug 1996 DE/SMG-061204P SMG#1712.05 4.1.1 Phase 2 ETS 300 616 Sub related event & call data PE version DE/SMG-061205P SMG#12.05 4.2.0 Phase 2 ETS 300 616 Sub related event & call data Vote version DE/SMG-061205P SMG#1712.05 4.2.1 Phase 2 ETS 300 616 Event & call data Pub June 1996 DE/SMG-061205P SMG#1712.05 4.3.0 Phase 2 ETS 300 616 Ed2 Event & call data OAP version RE/SMG-061205PR1 SMG#2212.05 4.3.1 Phase 2 ETS 300 616 Ed2 Event & call data Pub Feb 1998 RE/SMG-061205PR1 SMG#2212.05 5.0.0 Phase 2+ TS 100 616 Event & call data Unpublished DTS/SMG-061205Q SMG#2312.05 5.0.1 Phase 2+ TS 100 616 Event & call data Pub Aug 1998 DTS/SMG-061205Q SMG#2312.05 6.0.0 R97 TS 100 616 Event & call data Pub Oct 1998 RTS/SMG-061205Q6 SMG#2712.06 4.0.2 Phase 2 ETS 300 617 GSM Net config & manage PE version DE/SMG-061206P SMG#12.06 4.1.0 Phase 2 ETS 300 617 GSM Net config & manage Vote version DE/SMG-061206P SMG#1712.06 4.1.1 Phase 2 ETS 300 617 GSM Net config & manage Pub June 1996 DE/SMG-061206P SMG#1712.08 4.2.1 Phase 2 ETS 300 627 Sub and equip trace PE version DE/SMG-061208P SMG#1712.08 4.3.0 Phase 2 ETS 300 627 Sub and equip trace Unpublished DE/SMG-061208P SMG#1812.08 4.4.0 Phase 2 ETS 300 627 Sub and equip trace Vote version DE/SMG-061208P SMG#2012.08 4.4.1 Phase 2 ETS 300 627 Sub and equip trace Pub Mar 1997 DE/SMG-061208P SMG#2012.08 4.5.0 Phase 2 ETS 300 627 Ed2 Sub and equip trace OAP version RE/SMG-061208PR1 SMG#2212.08 4.5.1 Phase 2 ETS 300 627 Ed2 Sub and equip trace Pub Feb 1998 RE/SMG-061208PR1 SMG#2212.08 4.6.0 Phase 2 ETS 300 627 Ed3 Sub and equip trace Unpublished RE/SMG-061208PR2 SMG#2512.08 5.0.0 Phase 2+ TS 100 627 Sub and equip trace Unpublished DTS/SMG-061208Q SMG#2312.08 5.1.0 Phase 2+ TS 101 627 Sub and equip trace Unpublished DTS/SMG-061208Q SMG#2512.08 5.1.1 Phase 2+ TS 101 627 Sub and equip trace Pub July 1998 DTS/SMG-061208Q SMG#2512.11 4.0.0 Phase 2 EN 301 251 Fault management of BSS Unpublished DEN/SMG-061211P SMG#2112.11 4.1.0 Phase 2 EN 301 251 Fault management of BSS Unpublished DEN/SMG-061211P SMG#2212.11 4.1.1 Phase 2 EN 301 251 Fault management of BSS OAP version DEN/SMG-061211P SMG#2212.11 4.1.2 Phase 2 EN 301 251 Fault management of BSS Pub Dec 1997 DEN/SMG-061211P SMG#2212.11 4.2.0 Phase 2 EN 301 251 Fault management of BSS OAP version REN/SMG-

061211PR1SMG#26

12.11 6.0.1 R97 TS 101 251 Fault management of BSS Pub July 1998 DTS/SMG-061211Q6 SMG#2612.11 6.1.0 R97 TS 101 251 Fault management of BSS Pub Oct 1998 RTS/SMG-

061211Q6R1SMG#27

12.11 7.1.0D R98 TS 101 251 Fault management of BSS Draft DTS/SMG-061211Q7 SMG#2812.15 6.0.0 R97 TS 101 393 GPRS charging Unpublished DTS/SMG-061215Q6 SMG#2612.15 6.1.0 R97 TS 101 393 GPRS charging Pub Oct 1998 DTS/SMG-061215Q6 SMG#2712.15 7.0.0 R98 TS 101 393 GPRS charging Unpublished DTS/SMG-061215Q7 SMG#2712.20 4.1.2 Phase 2 ETS 300 622 BSS Management Info PE version DE/SMG-061220P SMG#12.20 4.2.0 Phase 2 ETS 300 622 BSS Management Info Vote version DE/SMG-061220P SMG#1712.20 4.2.1 Phase 2 ETS 300 622 BSS Management Info Pub June 1996 DE/SMG-061220P SMG#1712.21 4.5.1 Phase 2 ETS 300 623 NM proc & A-bis Interface PE version DE/SMG-061221P SMG#12.21 4.5.2 Phase 2 ETS 300 623 NM proc & A-bis Interface Unpublished DE/SMG-061221P SMG#1612.21 4.5.3 Phase 2 ETS 300 623 NM proc & A-bis Interface Vote version DE/SMG-061221P SMG#1712.21 4.5.4 Phase 2 ETS 300 623 NM proc & A-bis Interface Pub June 1996 DE/SMG-061221P SMG#1712.21 4.6.0 Phase 2 ETS 300 623 Ed2 NM proc & A-bis Interface Unpublished RE/SMG-061221PR SMG#2112.21 5.0.0 Phase 2+ TS 100 623 NM proc & A-bis Interface Unpublished DTS/SMG-061221Q SMG#2112.22 4.1.1 Phase 2 ETS 300 624 IW of NM proc & BSC PE version DE/SMG-061222P SMG#12.22 4.1.2 Phase 2 ETS 300 624 IW of NM proc & BSC Unpublished DE/SMG-061222P SMG#1612.22 4.1.3 Phase 2 ETS 300 624 IW of NM proc & BSC Vote version DE/SMG-061222P SMG#1712.22 4.1.4 Phase 2 ETS 300 624 IW of NM proc & BSC Pub Aug 1996 DE/SMG-061222P SMG#1712.30 4.1.1 Phase 2 ETR 128 GDMO registration Pub Apr 1995 DTR/SMG-061230P SMG#1712.30 4.2.0 Phase 2 ETR 128 Ed2 GDMO registration Pub July 1995 RTR/SMG-061230P SMG#1813.01-1 4.0.0 Phase 2 TS 101 419 Attach reqs, Access Pub Oct 1998 DTS/SMG-071301-1P SMG#2713.01-2 4.0.0 Phase 2 TS 101 431 Attach reqs, Access Pub Oct 1998 DTS/SMG-071301-2P SMG#2713.34 5.0.0 Phase 2+ EN 301 419-2 HSCSD TBR module Accsss Unpublished DEN/SMG-071334Q SMG#2613.34 5.0.1 Phase 2+ EN 301 419-2 HSCSD TBR module Accsss PE version DEN/SMG-071334Q SMG#2621.01 3.0.0 UMTS TR 101 xxx Requirements for UTRA Unpublished DTR/SMG-022101U SMG#2221.01 3.0.1 UMTS TR 101 111 Requirements for UTRA Pub Nov 1997 DTR/SMG-022101U SMG#2321.02 3.0.0 UMTS TR 101 398 High level UTRA reqmnts Unpublished DTR/SMG-022102U SMG#2221.02 3.0.1 UMTS TR 101 398 High level UTRA reqmnts Pub Oct 1998 DTR/SMG-022102U SMG#2721.04 1.0.0 UMTS TS 101 xxx Requirements for Data Draft DTS/SMG-042204U SMG#2621.06 3.0.0 UMTS TR 101 xxx O&M requirements Unpublished DTR/SMG-062106U SMG#25


Page 32


22.00 1.0.0 UMTS TS 101 xxx UMTS Phase 1 Caps Draft DTS/SMG-012200U SMG#27?

22.01 3.0.0 UMTS TS 101 xxx UMTS Service principles Unpublished DTS/SMG-012201U SMG#20?

22.01 3.1.1 UMTS TS 101 xxx UMTS Service principles Unpublished DTS/SMG-012201U SMG#2222.01 3.2.1 UMTS TS 101 xxx UMTS Service principles Unpublished DTS/SMG-012201U SMG#2422.01 3.3.0 UMTS TS 101 xxx UMTS Service principles Unpublished DTS/SMG-012201U SMG#2722.05 3.0.0 UMTS TS 101 xxx Service & capabilities Unpublished DTS/SMG-012205U SMG#2522.05 3.1.0 UMTS TS 101 xxx Service & capabilities Unpublished DTS/SMG-012205U SMG#2622.07 3.0.0 UMTS TR 101 xxx Terminal concepts Unpublished DTR/SMG-012207U SMG#2522.07 3.1.1 UMTS TR 101 xxx Terminal concepts Unpublished DTR/SMG-012207U SMG#2722.15 1.2.2 UMTS TS 101 xxx Serv Aspts Sec & charging Draft DTS/SMG-012215U SMG#24

?22.24 3.0.0 UMTS TR 101 xxx Charging & accounting Unpublished DTR/SMG-012224U SMG#2522.25 3.0.0 UMTS TR 101 xxx QoS & Net performance Unpublished DTR/SMG-012225U SMG#2422.25 3.1.0 UMTS TR 101 xxx QoS & Net performance Unpublished DTR/SMG-012225U SMG#2522.60 3.0.0 UMTS TR 101 xxx Mob MM Serv, Internet Unpublished DTR/SMG-012260U SMG#2522.70 3.0.0 UMTS TR 101 xxx VHE Unpublished DTR/SMG-012270U SMG#2522.71 3.0.0 UMTS TR 101 xxx Auto roaming relations Unpublished DTR/SMG-012271U SMG#2522.71 3.0.1 UMTS TR 101 xxx Auto roaming relations Unpublished DTR/SMG-012271U SMG#2722.75 3.0.0 UMTS TR 101 xxx Advanced addressing Unpublished DTR/SMG-012275U SMG#2722.80 2.0.1 UMTS TR 101 xxx UMTS/GSM/FPLMTS relations Unpublished DTR/SMG-012280U SMG#2523.01 1.0.0 UMTS TS 101 xxx General UMTS Architect Draft DTS/SMG-122301U SMG#27

?23.05 0.10.0 UMTS TS 101 xxx Network principles Draft DTS/SMG-122305U SMG#27

?23.10 1.0.0 UMTS TS 101 xxx Access stratum-Services and

functDraft DTS/SMG-122310U SMG#27

?23.20 1.0.0 UMTS TS 101 xxx GSM evolution to UMTS Draft DTS/SMG-122320U SMG#28

?30.00 3.0.0 UMTS TR 101 xxx UMTS Work program Unpublished DTR/SMG-003000U SMG#2230.00 3.2.0 UMTS TR 101 xxx UMTS Work program Unpublished DTR/SMG-003000U SMG#2330.00 3.3.0 UMTS TR 101 xxx UMTS Work program Unpublished DTR/SMG-003000U SMG#2430.00 3.4.0 UMTS TR 101 xxx UMTS Work program Unpublished DTR/SMG-003000U SMG#2530.00 3.5.0 UMTS TR 101 xxx UMTS Work program Unpublished DTR/SMG-003000U SMG#2630.00 3.6.0 UMTS TR 101 xxx UMTS Work program Unpublished DTR/SMG-003000U SMG#2730.01 3.0.0 UMTS TR 101 xxx UMTS baseline document Unpublished DTR/SMG-003001U SMG#2230.01 3.1.0 UMTS TR 101 xxx UMTS baseline document Unpublished DTR/SMG-003001U SMG#2430.01 3.2.0 UMTS TR 101 xxx UMTS baseline document Unpublished DTR/SMG-003001U SMG#2430.01 3.3.0 UMTS TR 101 xxx UMTS baseline document Unpublished DTR/SMG-003001U SMG#2530.03 3.0.0 UMTS TR 101 112 UTRA radio selection proc Unpublished DTR/SMG-023003U SMG#2230.03 3.1.0 UMTS TR 101 112 UTRA radio selection proc Pub Nov 1997 DTR/SMG-023003U SMG#2330.03 3.2.0 UMTS TR 101 112 UTRA radio selection proc Pub Apr 1998 RTR/SMG-

023003UR1SMG#25

30.04 3.0.0 UMTS TR 101 397 Def of UTRA concepts Unpublished DTR/SMG-023004U SMG#2230.04 3.0.1 UMTS TR 101 397 Def of UTRA concepts Pub Oct 1998 DTR/SMG-023004U SMG#2730.06 3.0.0 UMTS TR 101 146 UTRA evaluation reports Pub Dec 1997 DTR/SMG-023006U SMG#2430.20 3.0.0 UMTS TR 101 xxx Tech characteristics MSS Unpublished DTR/SMG-003020U SMG#2230.20 3.1.0 UMTS TR 101 xxx Tech characteristics MSS Unpublished DTR/SMG-003020U SMG#2433.20 3.0.1 UMTS TR 101 xxx Security principles Unpublished DTR/SMG-103320U SMG#2233.20 3.1.0 UMTS TR 101 xxx Security principles Draft DTR/SMG-103320U SMG#2733.21 1.0.0 UMTS TS 101 xxx Security requirements Draft DTS/SMG-103321U SMG#27U00.01 3.0.0 UMTS TCR TR 015 Ed2 UMTS Work plan (SMG5) Unpublished RTR/SMG-050001U SMG#17U00.01 3.1.0 UMTS TC TR 004 UMTS Work plan (SMG5) Pub May 1996 RTR/SMG-050001U SMG#18U00.01 3.2.0 UMTS TC TR 004 Ed2 UMTS Work plan (SMG5) Pub Aug1996 RTR/SMG-

050001UR2SMG#19

U01.01 3.0.0 UMTS ETR 271 Objects & overview (SMG5) Pub Feb 1996 DTR/SMG-050101U SMG#17U01.02 3.1.0 UMTS ETR 309 UMTS Vocabulary (SMG5) Pub Aug 1996 DTR/SMG-050102U SMG#19U01.03 3.1.0 UMTS ETR 291 Sys requirements (SMG5) Pub May 1996 DTR/SMG-050103U SMG#19U01.04 3.0.0 UMTS ETR 312 Scenrs UMTS intro (SMG5) Pub Aug 1996 DTR/SMG-050104U SMG#19


Page 33

TBRs

TBR Version Phase ETS/R/GTS Short Title Publication notes ETSI Reference AfterSMG #

TBR19 4.0.0 Phase 2 TBR 19 Access PE version DTBR/SMG-0019TTCN

SMG#

TBR19 4.0.0 Phase 2 TBR 19 Access Pub Feb1996 DTBR/SMG-0019TTCN

SMG#

TBR19 4.1.0 Phase 2 TBR 19 Ed2 Access Pub Sep 1996 RTBR/SMG-0019TTCN

SMG#17

TBR19 4.2.0 Phase 2 TBR 19 Ed3 Access Pub Oct 1996 RTBR/SMG-0019R1 SMG#18TBR19 4.2.1 Phase 2 TBR 19 Ed4 Access Unpublished RTBR/SMG-0719R2 SMG#21TBR19 4.3.0 Phase 2 TBR 19 Ed5 Access Pub Mar 1998 RTBR/SMG-0719R3 SMG#22TBR19 4.4.0 Phase 2 TBR 19 Ed6 Access Unpublished RTBR/SMG-0719R4 SMG#25TBR20 4.0.0 Phase 2 TBR 20 Telephony PE version DTBR/SMG-

0020TTCNSMG#

TBR20 4.0.0 Phase 2 TBR 20 Telephony Pub Feb1996 DTBR/SMG-0020TTCN

SMG#

TBR20 4.0.1 Phase 2 TBR 20 Ed2 Telephony Pub Oct 1996 RTBR/SMG-0020TTCN

SMG#18

TBR20 4.0.2 Phase 2 TBR 20 Ed3 Telephony Pub Sep 1997 RTBR/SMG-0720TTCNR

SMG#21

TBR31 4.0.0 Phase 2 TBR 31 Attach requirements, Access PE version DTBR/SMG-0731TTCN

SMG#17

TBR31 4.0.0 Phase 2 TBR 31 Attach requirements, Access Pub Jan 1997 DTBR/SMG-0731TTCN

SMG#19

TBR31 4.1.0 Phase 2 TBR 31 Ed2 Attach requirements, Access Pub Mar 1998 RTBR/SMG-0731TTCNR1

SMG#22

TBR31 4.2.0 Phase 2 TBR 31 Ed3 Attach requirements, Access Unpublished RTBR/SMG-0731TTCNR2

SMG#25

TBR32 4.0.0 Phase 2 TBR 32 Attach requirements, Telephony PE version DTBR/SMG-0732TTCN

SMG#17

TBR32 4.0.0 Phase 2 TBR 32 Attach requirements, Telephony Pub Jan 1997 DTBR/SMG-0732TTCN

SMG#19

TBR32 4.0.2 Phase 2 TBR 32 Ed2 Attach requirements, Telephony Pub Sep 1997 RTBR/SMG-0732TTCNR

SMG#21

TBR5 3.0.0 Phase 1 TBR 5 Access Pub Nov 1993 DTBR/SMG-0005 SMG#TBR5 3.1.0 Phase 1 TBR 5 Ed2 Access Pub Oct 1995 RTBR/SMG-0005 SMG#TBR9 3.0.0 Phase 1 TBR 9 Telephony Pub Nov 1993 DTBR/SMG-0009 SMG#TBR9 3.1.0 Phase 1 TBR 9 Ed2 Telephony Pub Oct 1995 RTBR/SMG-0009 SMG#

ETSI/ SMG(98)4, Annex 6: Road Map - GSM Phase 2+ Work Items Version 27.1

page 1 of 8

Source: PT SMG

Title : Road map for GSM phase 2+ - Version 27.1Date: 5th of November, 1998

STATUS:

Version 27.0 of this Road Map was an initial version after SMG#27 presented to GSM MoU.

Version 27.1 is presented to SMG1 Plenary, November 1998. It incorporates the results of SMG#27 and harmonisation with GSM 10.00. Allcompletion dates of R99 WI have been set to SMG#31.

This document is extracted from the WI Data Base and has the same version number as the Work Item Data Base, WI-27C1.mdb.

Note: The letter “C” in “WI-27C1.mdb” indicates that the data base has been compacted.


page 2 of 8

1 GSM PHASE 2

These Work Items were introduced in GSM Specifications V4.X.Y Series.

WI TitleBSS Repeaters (RPT)

DCS1800 4 Watt mobile power class

DECT access to GSM networks

Development of the SIM test specification (GSM Phase 2)

Display of Service Provider Name by the ME

Enhanced Full Rate Speech codec

Facsimile Enhancements

GSM - DCS Roaming

IMEI Check Digits (ICD)

Operation of Multi-band GSM/DCS by a single Operator

SIM - Three Volt Technology SIM

SMS Cell Broadcast Discontinuous Reception (CB-DRX)

SMS concatenation

Software Version Number (SVN)

Transparently supporting UPT phase 1


page 3 of 8

2. RELEASE 96

WI Title14.4 kbit/s User Data RateASCI Phase 1 - Enhanced Multi-Level Precedence and Pre-emption Service - phase 1ASCI Phase 1 - Voice Broadcast Service (VBS) - phase 1ASCI Phase 1 - Voice Group Call Service (VGCS) - phase 1Barred Dialling NumbersCAMEL phase 1Compression of User DataConcurrent SMS/CB and data transfer in 07.05Explicit Call Transfer (ECT)Extensions to the SMS alphabetFast Moving Mobile - Hierarchical Cell structure, GSM 05.22Handsfree MSHigh Speed Circuit Switched DataImproved Transcoder Handling (First Alternative)Inclusion of deferred tracing capabilities in GSM 12.08ME PersonalisationNetwork Identity and Time Zone (NITZ)Packet Data on Signalling ChannelsRadio Local Loop (RLL) using GSMSecond SMS broadcast channelService Dialling NumbersSIM Application ToolkitSIM I/F data Transfer Speed EnhancementSMS - Special SMS Message indicationSMS Interworking ExtensionsSupport of additional call set-up MMI proceduresSupport of Optimal Routeing (SOR)Support of Restricted Digital Information and V.120 rate adaptation in GSM


page 4 of 8

3. RELEASE 97

WI TitleA-bis Management of Alarms/faults on the BTS siteA-bis Management of Measure on the BTS siteA-bis Management of reconfiguration of BTS siteASCI Phase 2Calling Name Presentation - US (CNAP-US)CAMEL phase 2Characteristics and test methods for handsfree mobile stationCompletion of Calls to Busy Subscriber (CCBS)Enhancement of MAP Extensibility MechanismsEnhancements of Fault Management ServicesGeneral Packet Radio Service Phase 1 (GPRS) - network partGeneral Packet Radio Service Phase 1 (GPRS) - radio partMobile Assisted Frequency Allocation (MAFA)Modeling of Fault Management ServicesNetwork Indication of Alerting in the MSNew Multiplexing Protocol on the ME-TE InterfaceNorth American Equal AccessSIM - Security mechanisms for the SIM Application ToolkitSMS enhancements phase 1SMS Mobile BusySupport of Private Numbering Plan (SPNP)Support of Shared Interworking Function (SIWF)


page 5 of 8

4. RELEASE 98

Already completed:WI Title

BTS performance requirements for very small cell scenarios (Picocells)

Ongoing:WI Title WI ra pporteur WI Rapp company Prime

Access to auxiliary devices, integrated into the ME platform, through the use of the SIM Application Toolkit Required SMG09Access to ISPs and Intranets in GPRS Phase 2 – Separation of GPRS Bearer Establishment and ISP Service Environment Setup required SMG04Adaptive Multi-Rate (AMR) Kari Jarvinen Nokia SMG11Call Deflection Mr A.Conrad T-Mobil SMG01Call Forwarding Enhancements (CFE) Mr N.Renaud France Telecom SMG01Calling line identification enhancements (CLIe) Pekka Hämäläinen Nokia SMG03Connecting an octet stream to a port on an Internet host (R98) required SMG04Enhanced Data rates for GSM Evolution (EDGE) - BSS Part F. Mueller SMG02Enhanced Data rates for GSM Evolution (EDGE) - NSS Part T. Kokkola Nokia SMG03Enhanced QoS Support in GPRS required SMG12Follow Me Erwin Postmann Siemens SMG01Fraud Information Gathering System(FIGS) Tim Wright Vodafone SMG10General Packet Radio Service Phase 2 (GPRS) - network part1 tbd Nokia SMG03General Packet Radio Service Phase 2 (GPRS) - radio part1 J.Hamalainen Nokia SMG02GPRS for PCS1900 C.Campbell, SBC, Siemens T1P1GPRS Mobile IP Interworking required SMG04GSM - Cordless Telephony System (CTS) M.Galligo Alcatel SMG01GSM Mobile Number Portability (EURO) MNP Willem Levelt KPN SMG01GSM-API for SIM-Toolkit C.Dietrich Schlumberger SMG09Harmonization of the PCS1900 Standards with the GSM Base Specification Kerry Weaver Nokia T1P1Immediate Service Termination (IST) Tim Wright Vodafone SMG10LAPDm performance enhancement required SMG03Lawful Interception (LI) David Miles Cellnet SMG10Location Services (LCS) Christopher Kingdon T1P1Mobile Station Execution Environment (MExE) John Candish Nortel SMG04Modem and ISDN interworking for GPRS required SMG04MS Antenna Test Method Olle Edvardsson ALLGON AB SMG02Multiple Subscriber Profile (MSP) Ian Crawford Vodafone SMG01Service Provider Number Portability (USA) required T1P1Support of Localized Service Area (SoLSA) Tommy Kokkola Nokia SMG01Tandem Free Operation of speech codecs in Mobile-to-Mobile Calls (MMCs) W.Navarro Nortel SMG03/11Unstructured octet stream GPRS PDP Type (R98) required SMG04User-to-User Signalling (UUS) Mr A. Conrad T-Mobil SMG01USSD Enhancements Sverre Slotte Nokia SMG01

1 Comprises sub-work items in the same table having “GPRS” in their title.


page 6 of 8

5. RELEASE 99 and BEYOND

WI Title Date dueSMG

approval

WI rapporteur WI Rappcompany

Primeresponsible STC

Access to ISPs and Intranets in GPRS Phase 2 – Wireless/Remote Access to LANs (R99) S31 required Ericsson SMG04Advanced Addressing S31 required SMG01Architecture of the GSM-UMTS Platform S31 H. Dettner Siemens SMG12Architecture overview of the GSM-UMTS System S31 M. Mouly Nortel SMG12Automatic Establishment of Roaming Relations S31 required SMG01CAMEL Phase 3 S31 required SMG01Charging and Billing for GPRS – Advice of Charge S31 required SMG06Charging and Billing for GPRS – Hot Billing S31 required SMG06Charging and Billing for GPRS – Pre-Paid S31 required SMG06End to End UMTS QoS Management S31 required Lucent SMG12, SMG3Fraud Information Gathering System applied to GPRS S31 required SMG10

BSS co-ordination of Core Network Resource allocation for class A GPRS services -GSM-UMTS Core Network (R99)

S31 M.Mouly Nortel tbd

BSS co-ordination of Radio Resource allocation for class A GPRS services - GSM RadioAccess (R99)

S31 M.Mouly Nortel tbd

GPRS - Point-To-Multipoint Services S31 required tbdIP-in-IP tunneling in GPRS backbone for UMTS, phase 1 S31 A.Calvi,

A.NapolitanoCSELT SMG12

Low Voltage SIM/ME Specification S31 Rune Lindholm Nokia SMG09MExE Release 99 S31 required tbdNew Access Network to Core Network (BSS-NSS) interface S31 Michel Mouly Nortel SMG12Noise Suppression for AMR speech codec S31 Steve Aftelak Motorola SMG11Provision of text telephony service in GSM and UMTS S31 required Hayes SMG12Service Continuity and Provision of VHE via GSM/UMTS S31 required SMG01Study on Combined GSM and Mobile IP Mobility Handling in UMTS IP CN S31 E.Hubbard Telia SMG12UMTS Charging & Billing S31 D.Chambers SMG01UMTS Core based on ATM Transport S31 M.Wilson,

A.RouzFujitsu SMG12

UMTS Numbering, Addressing and Identities S31 S.Kleier MMO SMG01UMTS Open Service Architecture S31 R.Schmersel Ericsson SMG12Virtual Home Environment S31 E.Postmann Siemens SMG01


page 7 of 8

6. WORK ITEMS - STATUS TO BE DETERMINED

WI Title WI rapporteur PrimeCalling Name Presentation - Euro (CNAP-EU) required SMG1Efficient cellular support of new services in GSM network service areas required SMG03Generic signalling mechanism for service support required SMG03Idle mode classmark required SMG03Impact of Telecommunications Data Protection Directive on GSM Standards B. Reed SMG01Interworking with Mobile Satellite Systems required SMG03Multimedia in UMTS required SMG12Provision of text telephony service in GSM and UMTS required SMG04Requirements for equipments/systems interfacing GSM required tbdService to GSM Handportables in trains required SMG02Study on provision of facsimile services in GSM and UMTS E.Colban SMG04Support of non-realtime Multimedia Messaging Service required SMG04Support of non-realtime Multimedia Messaging Service required SMG12Support of Operator Specific Services (SOOS) when roaming1 required SMG1Technical Enhancements/improvements for phase 2 PT SMG All STCs

1 to be subsumed under VHE?


page 8 of 8

7. WORK ITEMS DELETED BY SMG

WI TitleAdaptions for deregulated networksAdvice of Charge on Special Services (AoCSS)Completion of Call when No Reply (CCNRy)Completion of Call when Subscriber Not Reachable (CCNRc)Direct Subscriber Access and Restriction (DSAR)Emergency Call TS12 with additional Data TransferEnhancement of CLIRExchange of network capabilities informationFast moving mobile stationFault and Configuration Management for Other ElementsFault and Configuration Management of OA&M CapabilitiesForwarding of SMSsGSM/AMPS Interworking to Support RoamingIMEI Security EnhancementsInter operation with UPT phase 2Interworking with non-GSM applications on the SIMISDN-based DECT/GSM interworking - phase 1ISDN-based DECT/GSM interworking - phase 2Malicious Call ID (MCID)Mobile Access Hunting (MAH)Mutual AuthenticationNetwork level ManagementNew Barring ServicesOverload control enhancement for Location RegistersPayphone ServicesPremium Rate Services (PRS)Provisions for Hot BillingStandard access SMS, SC-SMESSubscriber Class for Advice of ChargeTest methods for handset and headset mobile stationTransmission of date/time and zoneUnified SMS CB scheduling algorithmUniversal access to freephone numbers

GSM Phase 2+ Status List after SMG#27Version 27.1 - 5 October, 1998

WI Title

STC Type of Work Rapporteur Company Country Affected Specs. in STC

CommentsDate due/approved

Prime resp. committee WI rapporteur Company WI appr. in Tdoc SM

14.4 kbit/s User Data Rate T1P1 370/96Mikko Kanerva Nokia

SMG06 CR 12.21

A-bis Management of Alarms/faults on the BTS sitecompleted @ S26S23

SMG06 Mr. A. Yuhan

SMG06 CR 12.21

A-bis Management of Measure on the BTS sitecompleted @ S26S23

SMG06 Mr. A. Yuhan

SMG06 CR 12.21

A-bis Management of reconfiguration of BTS sitecompleted @ S26S24

SMG06 Mr. A. Yuhan

Phase 2+ status list Page1/37

WI Title




Access to auxiliary devices, integrated into the ME platform, through the u SMG09 0156/98Required

SMG04 CRs required GSM 09.61

Access to ISPs and Intranets in GPRS Phase 2 – Separation of GPRS Beare

S28

SMG04 556/98required

SMG04 CRs required Ericsson GSM 09.61

Access to ISPs and Intranets in GPRS Phase 2 – Wireless/Remote Access to

S28

SMG04 556/98required Ericsson

SMG01 Report

Adaptions for deregulated networksdeleted @ S21

SMG01 227/96NN Siemens

SMG11 New Specs K.Jarvinen Nokia FI see 10.70

Adaptive Multi-Rate (AMR)R98 confirmed @S27S28

SMG11 0740/97Kari Jarvinen Nokia


WI Title




SMG01 Required

Advanced Addressing

S31


SMG01 CR Mr G.Schmidt T Mobil DE

SMG03 CR

Advice of Charge on Special Services (AoCSS)deleted @ S20S23

S23

SMG01 Mr G.Schmidt T-Mobil

SMG12 23.20, 23.05 A.Jarvis, A. Sultan Lucent, France Télécomtbd

Architecture of the GSM-UMTS Platform SMG12 228/98H. Dettner Siemens

SMG12 23.01, 23.10 R. Bodin, M.Schönborn

Ericsson, T-Mobil

SMG3 CRs 03-series? 09-series?

Architecture overview of the GSM-UMTS System SMG12 228/98M. Mouly Nortel

SMG01 02.67 Mr D.Münning Detecon (PT61V) DE

SMG03 03.67 Mr D.Münning Detecon (PT61V) 03.08, 03.16, 04.08


SMG09 CRs 11.11-A009/10 11.11

ASCI Phase 1 - Enhanced Multi-Level Precedence and Pre-emption Servicereplaces earlier WI "Prioritisation and Pre-emption" and "Fast Call Set-Up"

S18

S18

S18

S17

SMG03 PT SMG Detecon (PT61V)


WI Title




SMG01 02.69 Mr D.Münning Detecon (PT61V) DE 01.02

SMG03 03.69/04.69 Mr D.Münning Detecon (PT61V) DE 03.03, 03.08, 03.09, 03.16, 03.22, 04.03, 04.06, 04.08, 04.13, 08.06, 08.08

SMG02 CR Mr J.Evald DSB/UIC DK 05-series

ASCI Phase 1 - Voice Broadcast Service (VBS) - phase 1

S18

S19

S19



SMG03 03.68/04.68 Mr D.Münning Detecon (PT61V) DE 03.03, 03.08, 03.09, 03.16, 03.22, 04.03, 04.06, 04.08, 04.13, 08.06, 08.08

SMG02 CR Mr J.Evald DSB/UIC DK 05-series

ASCI Phase 1 - Voice Group Call Service (VGCS) - phase 1

S18

S19

S19


SMG03 CRs PT SMG 03.67, 03.68, 03.69, 04.08, 04.67, 04.68, 04.69, 03.22, 08.08, 08.58, 09.02, 09.08

SMG10 CRs 02.09, 03.20

ASCI Phase 2

S24

S24

SMG03 150/97PT SMG

required tbd

tbd tbd

Automatic Establishment of Roaming Relations

tbd



WI Title




SMG01 CR Mr N.Renaud France Telecom F 02.07

SMG09 CR Mr F.Vergine France Telecom F 11.11

Barred Dialling NumbersSMG1 work complete, held for intervention by SMG9

S18

S20

SMG01 582/95Mr N.Renaud France Telecom

BSS co-ordination of Core Network Resource allocation for class A GPRS sSMG12 556/98M.Mouly Nortel

tbd tbd required

BSS co-ordination of Radio Resource allocation for class A GPRS services -tbd 556/98M.Mouly Nortel

SMG02 CR Mr P.White Vodafone UK 03.30, 05.05, 05.50

BSS Repeaters (RPT)Work item completedCompleted

SMG02 Tdoc 65/95Mr P.White Vodafone

SMG02 CR NN Motorola 05.05, 05.10, 05.22, 05.50, 03.30, 11.21

BTS performance requirements for very small cell scenarios (Picocells)

Completed

SMG02 429/96Howard Benn Motorola


WI Title




SMG01 Stage1; CRs Mr A.Conrad T-Mobil DE new: 02.72; CRs: 02.04, 02.30

SMG03 Stage 2, 3 S.Habermann T-Mobil DE

Call Deflection

S28

S28

SMG01 Mr A.Conrad T-Mobil

SMG01 TBD Mr N.Renaud France Telecom F

Call Forwarding Enhancements (CFE)deleted @ S20; re-vitalised S26: Outstanding: Long forwarded-to number

S20

SMG01 Mr N.Renaud France Telecom

SMG03 CR Pekka Hämäläinen Nokia FIN 03.81, 09.02

SMG01 CRs Pekka Hämäläinen Nokia FIN 02.81

Calling line identification enhancements (CLIe)

S28

S28

SMG03 422/96Pekka Hämäläinen Nokia

02.96, CRs 02.04 02.30

03.96, CRs 03.16 03.18

04.96, CRs 04.80 09.02

Calling Name Presentation - Euro (CNAP-EU)split decided S26

S24

SMG1 696/96required

T1P1 02.96, CRs US 02.04 02.30

T1P1 03.96, CRs US 03.16 03.18

T1P1 04.96, CRs US 04.80 09.02

Calling Name Presentation - US (CNAP-US)split decided S26S24

S24

S24

T1P1 696/96Sonia Doshi Nortel


WI Title




SMG01 01.78 Mr F.Leroudier France Telecom F

SMG01 02.78 Mr. P. Warleus Telia Mobitel S

SMG03 03.78 Ms C. Ritter Telia Mobitel S

SMG03 09.78

CAMEL phase 1Ph 1 stage 1 approved at SMG#19

S19

S19

S19

S20

SMG01 Mr. P.Waerleus Telia Mobitel

SMG01 CRs Stefan Kleier Mannesmann M.funk DE 02.78

SMG03 stage 2,3 CRs tbd 03.08 03.18 03.78 04.88 09.02 09.78

CAMEL phase 2core specs completed S25S24

S25

SMG01 Stefan Kleier Mannesmann M.funk

CAMEL Phase 3All R99 WI completion dates moved to S31

SMG01 required

SMG11 ETR 03.58; CRs Mr J-Y Monfort France Telecom F 06.01

Characteristics and test methods for handsfree mobile station

S23

SMG11 123/96Mr J-Y Monfort France Telecom

SMG06 CRs required 12.15


SMG3/SMG12

CRs required 03.60

Charging and Billing for GPRS – Advice of Charge

S31

S30

S31



WI Title






SMG3/SMG12

CRs required 03.60

Charging and Billing for GPRS – Hot Billing

S31

S30

S31




SMG3/SMG12

CRs required 03.60

Charging and Billing for GPRS – Pre-Paid

S31

S30

S31


Completion of Call when No Reply (CCNRy)deleted @ Sxx; re-vitalised S26; re-deleted @S27

Completion of Call when Subscriber Not Reachable (CCNRc)deleted @ S15 re-vitalised S26; re-deleted @S27

SMG01 stage 1 Mr N.Jorgensen Telecom Denmark DK New: 02.93; CRs: 02.04 02.30

SMG03 stage 2, 3 Mr S.Frew Vodafone UK New: 03.93, 04.93; CRs: 03.16 03.18 04.07 04.08 09.02

Completion of Calls to Busy Subscriber (CCBS)core specs completed S26S26

S26

SMG01 Mr N.Jorgensen Telecom Denmark


WI Title




SMG01 CR Mr G.Hall Cellnet UK 02.01-A003, 02.02-A001

SMG04 DrAm Mr C.Fenton B.T. UK 03.10-A001, 04.22-A004, 07.01-A004, 07.02-A001, 07.06-A001, 09.07-A009

SMG03 DrAm T Mobil DE 04.08-A057

Compression of User DataWork item completedCompleted

SMG01 Tdoc 605/95Mr G.Hall Cellnet

SMG04 CR

Concurrent SMS/CB and data transfer in 07.05Completed S17Completed

SMG04 251/95None

SMG04 GSM 07.61; CRs required GSM 09.61

SMG03 CRs required GSM 09.60

Connecting an octet stream to a port on an Internet host (R98)

S28

S28


SMG01 CR Mr C.Harrison Hutchison Telecom UK 02.04-A002

SMG02 DrAm Mr T.Hayson Hutchison Telecom UK 05.01-A001, 05.05-A002, 05.08-A001

SMG03 DrAm 04.08-A001r2

DCS1800 4 Watt mobile power classReleased May (UAP 29)S12

S13

S13

SMG01 Tdoc 66/95, 293Mr C.Harrison Hutchison Telecom

SMG01 ETS 300 466 Mr A.Toepfer MMO DE

DECT access to GSM networksWork item completed

SMG01 Mr A.Toepfer MMO


WI Title




Development of the SIM test specification (GSM Phase 2)may not be appropriate as a phase 2+ work item

SMG09 762/96Gary A. Waite Aspects Software Ltd.

SMG01 Stage 1 Mr N.Chapman Hutchison Telecom UK

SMG03 Stage 2

Direct Subscriber Access and Restriction (DSAR)deleted @ S20S23

S23

SMG01 Mr N.Chapman Hutchison Telecom

SMG01 CR Mr Toepfer MMO DE 02.07-A002

SMG09 DrAm Ms R.Brögger MMO DE 11.11-A004

Display of Service Provider Name by the MEWork item completed in S15S15

S15

SMG01 240/95, Tdoc 51Mr Toepfer MMO

SMG03 tbd Required tbd

SMG02 tbd Required tbd

Efficient cellular support of new services in GSM network service areaspendingtbd

tbd


SMG01 Stage1 Mr A.Conrad T Mobil DE

Emergency Call TS12 with additional Data Transferdeleted @ tbdS18

SMG01 240/95, 301/97Mr A.Conrad T-Mobil


WI Title




End to End UMTS QoS Management SMG12, SMG3 781/98required Lucent

Enhanced Data rates for GSM Evolution (EDGE) - BSS Part SMG02 1148/97F. Mueller

Enhanced Data rates for GSM Evolution (EDGE) - NSS Part SMG03 1147/97T. Kokkola Nokia

SMG01 Report Mr P.Gaskell Mercury One2one UK

SMG02 TBD Mr P.Gaskell Mercury One2one DE

Enhanced Full Rate Speech codecWork item completedS17

S17

SMG01 Mr P.Gaskell Mercury One2one

SMG12 tbd required tbd

SMG02 CRs required GSM 04.60, GSM 08.18, GSM 08.16

SMG03 CRs required GSM 09.60, GSM 09.02, GSM 03.60

Enhanced QoS Support in GPRS

S28

S28

S28



WI Title




Enhancement of CLIR

SMG03 CRs 09.02

Enhancement of MAP Extensibility Mechanismscore specs completed S22

S22

SMG03 423/96?

SMG06 New spec 12.11 Mark Cataldo Lucent 12.04

Enhancements of Fault Management Servicescompleted @ S26 except Redundancy Management modelling which is planned for S27

S25

SMG06 345/97Mark Cataldo Lucent

SMG03 Report Required

Exchange of network capabilities informationdeleted @ as per H.Dettner

SMG03 Required

SMG01 02.91 Mr E.Postmann Siemens A 02.04, 02.30

SMG03 03.91 Mr S.Dzuban Siemens A 03.15, 03.16, 04.80, 09.02, 09.11

SMG03 04.91

SMG03 DrAm

Explicit Call Transfer (ECT)SMG1 complete; problems in SG?

S14

S18

S18

S18

SMG01 Mr E.Postmann Siemens


WI Title




SMG04 CR Mr K.Holley B.T. UK 03.38

Extensions to the SMS alphabetmainly compl S18 (compression remains to be solved

S20

SMG04 Mr K.Holley BT

SMG04 ETR Mr P.di.Tria CSELT I

Facsimile EnhancementsWork item completed

SMG04 Mr P.di.Tria CSELT

SMG02 Report Mr M.Reiner AEG DE

Fast moving mobile stationdeleted@S25, deletion confirmed@S26; cf. comlpeted WI Fast Moving Mobile - Hierarchical Cell structure, GSM 05.22

del S25

SMG02 Mr M.Reiner AEG

Fast Moving Mobile - Hierarchical Cell structure, GSM 05.22 SMG02 Han Van Bussel

SMG06 TBD Required

Fault and Configuration Management for Other Elementsdeleted @ S21del S21

SMG06 del S21


WI Title




SMG06 CR Required 12.06, 12.11, 12.20, 12.21, 12.22

Fault and Configuration Management of OA&M Capabilitiesdeleted @ S21del S21

SMG06 del S21

SMG01 stage 1 required Siemens tbd

SMG03 CRs required tbd

Follow Me

S28

S28

SMG01 172/97Erwin Postmann Siemens

SMG01 requirements, stage 1 Nicolas Renaud France Telecom F tbd

SMG04 tbd tbd

Forwarding of SMSsdeleted @ S27del

del

SMG01 Nicolas Renaud France Telecom


Fraud Information Gathering System applied to GPRS

S31


SMG01 Stage 1 Tim Wright Vodafone UK new: 03.31

Fraud Information Gathering System(FIGS)transferred from SMG1; supersedes WI "Subscriber Supervising System"

S28

SMG10 Tim Wright Vodafone


WI Title




SMG01 req's; stage 1; CRs Mr A.Conrad T Mobil DE new: 01.61 02.60; CRs: 02.11

SMG03 stage 2, 3 New: 03.60 03.64 04.60 04.64 04.65 CRs: 03.02 03.03 03.07 03.08 03.16 03.18 03.20 04.03 04.04 04.07 04.0804.11 08.16 09.02 09.10

SMG04 stage 2, 3 Mr H.P.Naper/Mr P.Gilchrist

Motorola N/DE New: 07.60 CRs: 03.40 07.07

SMG09 stage 3 CRs: 11.11

General Packet Radio Service Phase 1 (GPRS) - network partSplit decided at S19S25

S25

S25

S25

SMG03 Hans Petter Naper Motorola

SMG01 req's; stage 1; CRs Mr A.Conrad T Mobil DE new: 01.61 02.60; CRs: 02.11

SMG02 stage 3 J Hamalainen Nokia FIN CRs: 04.08 05.01 05.02 05.03 05.05 05.08 05.10 05.50

SMG03 stage 2, 3 New: 03.60 04.60 04.64 04.65 CRs: 02.11 03.20 04.03 04.04 04.07

General Packet Radio Service Phase 1 (GPRS) - radio partSplit decided at S19S25

S25

S25

SMG02 198/96J.Hamalainen Nokia

SMG10 req's CRs: 01.33, 02.33

SMG03 stage 2,3

General Packet Radio Service Phase 2 (GPRS) - network partsub work items proposed by SMG1 to S27

S28

S28

SMG03 tbd Nokia

General Packet Radio Service Phase 2 (GPRS) - radio partsub work items proposed by SMG1 to S27

SMG02 198/96J.Hamalainen Nokia


WI Title





Generic signalling mechanism for service support SMG03 required

tbd tbd required

GPRS - Point-To-Multipoint Services tbd 556/98required

T1P1 CRs C.Campbell, M.Kamdar

SBC, Siemens USA GSM 02.60 GSM 03.60 GSM 08.16 GSM 09.16, etc

GPRS for PCS1900Separate WIs for SMG projects missing

S28

T1P1 583/98C.Campbell, M.Kam SBC, Siemens



GPRS Mobile IP Interworking

S28

S28


SMG01 New spec 02.56, CRs M.Galligo Alcatel F new: 02.56; CRs: 02.07, 02.11

SMG02 03.52; CRs Ph.Desblancs Alcatel F 03.22, 04.0x, 04.08, 05.01, 05.02, 05.05, 05.08, 05.10

SMG03 CRs J.F.Rubon Alcatel F 03.11

SMG07 CRs S.Dia Alcatel F 11.10, TBR19, TBR31

SMG10 CRs S.Messiet Alcatel F

GSM - Cordless Telephony System (CTS)

S27

S28

S28

S30

SMG01 0382/97M.Galligo Alcatel


WI Title




GSM - DCS Roaming

SMG07

GSM 1900 Conformance Testing (Handsets)CRs to 11.10 - No WI yet

SMG07 Carl Warfel (Ref Ed BellSouth

SMG01 Willem Levelt KPN NL

GSM Mobile Number Portability (EURO) MNP SMG01 0867/97Willem Levelt KPN

SMG09 C.Dietrich Schlumberger tbd

GSM-API for SIM-Toolkit

S28

SMG09 0156/98C.Dietrich Schlumberger

GSM/AMPS Interworking to Support RoamingMarked for deletion at S26; put by AB to deleted after S27, as no further input arrived

T1P1 433/96Ed Ehrlich (Contact) Nortel


WI Title




SMG11 Report None

Handsfree MSPrior responsibility: SMG2S19

SMG02, 11 None

T1P1 CRs Kerry Weaver Nokia tbd

Harmonization of the PCS1900 Standards with the GSM Base Specification

S28

T1P1 131/97Kerry Weaver Nokia

SMG01 ETR Mr M.Kanerva Nokia C.Systems FIN

High Speed Circuit Switched DataSMG Architecture Group dependencies

S19

SMG01 Mr M.Kanerva Nokia C.Systems

Idle mode classmark SMG03 314/96required

IMEI Check Digits (ICD)


WI Title




IMEI Security Enhancementsdeleted @ S19

SMG-SG None

SMG10 tbd

SMG3

Immediate Service Termination (IST)CAMEL based solution R99 (decision of S27);

S28

S28

SMG10 436/98Tim Wright Vodafone

SMG01 tbd B.Reed BT UK tbd

Impact of Telecommunications Data Protection Directive on GSM StandarNo work necessary at presemt, but WI not closed to watch fixed network development

tbd

SMG01 417/98B. Reed BT

SMG02 report Johan Sköld Ericsson S tbd

Improved Data Rates through Optimised Modulation

tbd

SMG02 162/97Johan Sköld Ericsson

SMG03 CR Required

Improved Transcoder Handling (First Alternative)

S20

SMG03 306/95Required


WI Title




SMG06 CR 12.08

Inclusion of deferred tracing capabilities in GSM 12.08

S22

SMG06 251/96Mr. B. Szelazek

SMG01 Report Mr A.Toepfer MMO DE

Inter operation with UPT phase 2deleted @ S21



Interworking with Mobile Satellite Systemsmoved from R98 to "tbd", as no progress was reported at S27

tbd

SMG03 required

SMG09 Requirements Mr W.Mohrs T Mobil DE

Interworking with non-GSM applications on the SIMdeletion confirmed @ S27

SMG09 Mr W.Mohrs T-Mobil

IP-in-IP tunneling in GPRS backbone for UMTS, phase 1 SMG12 780/98A.Calvi, A.Napolitano CSELT


WI Title




SMG01 Study Ms I.Graetz Siemens AG DE none

SMG01 stage 1 Ms I.Graetz Siemens AG DE

SMG03 stage 2 S22

ISDN-based DECT/GSM interworking - phase 1deleted @ tbd Feasibility study at SMG#19 approved

S19

S21

SMG01 504/95Ms I.Graetz Siemens AG

ISDN-based DECT/GSM interworking - phase 2deleted @ tbd

SMG01 I.Graetz Siemens

SMG02 CR required 04.06, tbd

SMG07 CR required 11.10

SMG08 CR required 11.23

SMG06 CR required tbd

LAPDm performance enhancement

S28

S31

S31

S31


SMG10 req's; stage 1 Cellnet UK New: 01.33, 02.33

SMG03 CRs 09.02, 03.02, 03.08, 03.16, 12.01, 12.08

Lawful Interception (LI)superseding WI "Call interception"

S28

S28

SMG10 158/96David Miles Cellnet

T1P1 tbd Christopher Kingdon tbd

Location Services (LCS)

S28

T1P1 715/96Christopher Kingdon


WI Title




SMG09 New spec Rune Lindholm Ericsson(?) S 11.10

Low Voltage SIM/ME SpecificationAll R99 WI completion dates moved to S31

SMG09 358/97Rune Lindholm Nokia

SMG01 Stage 1 Mr I.Sharp Nortel UK

SMG03 Stage 2

SMG03 Stage 3

Malicious Call ID (MCID)deleted @ S20S20

S20

S20

SMG01 Mr I.Sharp Nortel

Mr P Gaskell Mercury One2one UK

ME PersonalisationChanged from R96 to R97

SMG01 NN Mercury One2one


tbd tbd required

MExE Release 99All R99 WI completion dates moved to S31

tbd

tbd 775/98required

SMG01 Stage 1 Mr I.Sharp Nortel UK

SMG03 Stage 2

SMG03 Stage 3

Mobile Access Hunting (MAH)deleted @ S20S22

S22

S22

SMG01 Mr I.Sharp Nortel


WI Title




SMG02 CRs Mr B.Persson Ericsson S 04.08 05.08 05.08 08.58

SMG03 CR Ericsson SE 04.08

SMG06 CR Ericsson SE 12.21, 12.22

Mobile Assisted Frequency Allocation (MAFA)

S24

S24

S26

SMG02 664/95Mr B.Persson Ericsson

SMG01 stage 1 required new: 02.57


Mobile Station Execution Environment (MExE)core specs planned S28S28

S28

SMG04 0709/97John Candish Nortel

SMG06 New spec, CRs Mark Cataldo Lucent New: 12.11; CRs:12.04

Modeling of Fault Management Servicescompleted S26S26

SMG06 345/97Mark Cataldo Lucent

SMG04 New spec, CRs required new: Modem and ISDN Interworking for GPRS; CRs: 07.60

Modem and ISDN interworking for GPRS

S28


SMG02 CRs Olle Edvardsson ALLGON AB CRs: 05.05

SMG07 CRs required CRs: 11.10

MS Antenna Test Method

S24 ?

S24

SMG02 162/97Olle Edvardsson ALLGON AB


WI Title









Multimedia in UMTS

tbd

tbd

tbd

tbd

tbd


SMG01 stage 1 Ian Crawford Vodafone UK new: 02.97

SMG03 Stage 2, 3 required

Multiple Subscriber Profile (MSP)stage 1 approved at S19; little progress in SGM3; SMG1 studies new approach

S19

S28

SMG01 Ian Crawford Vodafone

SMG10 Requirements Vodafone UK

Mutual Authenticationdeleted @ tbdS20

SMG09 None Vodafone

Network control of ringing tones (Renamed N/W Indication of Alerting in tDuplicate of WI "Network Indication of Alerting in the MS"

SMG01 582/96Required

SMG01 Stage 1 Mr L.Giles BRT/UIC UK

Network Identity and Time Zone (NITZ)includes earlier WI: "Update of ME list of Network Names over the air interface" and "Transmission of date/time and zone"

S18

SMG01 Mr L.Giles BRT/UIC


WI Title




SMG01 CRs Nicolas Renaud France Telecom FR 02.07, 02.30, 02.90

SMG04 CRs 03.40

SMG03 CRs 03.18, 03.90, 04.08, 04.90, 09.02

SMG09 CRs 11.11

SMG02 CRs 05.08 08.58

Network Indication of Alerting in the MSsub-item "Network Alerting (SMS)" deleted @ S27

S24

S26

S25

S25

S25

SMG01 172/97Nicolas Renaud France Telecom

SMG06 TBD del S21

Network level Managementdeleted @ S21del S21

SMG06 del S21

SMG12 23.30 Lauri Söderbacka Nokia FIN

SMG03/SMG02

protocol specifications tbd

New Access Network to Core Network (BSS-NSS) interfacecompletion date moved to S31, as S28 seemed un-realistic

S26

S28

SMG12 228/98Michel Mouly Nortel

SMG01 CR Mr G.Schmidt T Mobil DE

SMG03 CR

New Barring Servicesdeleted @ S20S22

S22

SMG01 Mr G.Schmidt T-Mobil

SMG04 new spec, CRs Lars Novak Ericsson S new: 07.10; CRs: 07.07

New Multiplexing Protocol on the ME-TE Interfacecore specs completed S24S26

SMG04 416/97Lars Novak Ericsson


WI Title




SMG11 tbd Steve Aftelak Motorola tbd

SMG7 tbd tbd tbd

Noise Suppression for AMR speech codec

S31

S32

SMG11 367/98Steve Aftelak Motorola

SMG01 CRs Stephen Hayes Ericsson 02.82

SMG03 CRs CRs: 03.04, 03.08, 03.16, 03.08, 03.82, 04.82, 09.02

SMG06 CRs 12.02, 12.05

North American Equal Access

S22

S23

S23

T1P1 129/97Stephen Hayes Ericsson

SMG01 CR Mr T.Ljunggren Telia Mobitel S 02.06-A001r2, 02.11-A004

SMG03 03.26 (4.0.0) Mr T.Ljunggren Telia Mobitel S 03.22-A004, 04.08-A001r2, 04.08-A007r2, 04.08-A015r5, 04.13-A002r1, 08.08-A013r3, 08.58-A005r4, 08.58-A006r1

SMG02 DrAm Required 05.01-A004, 05.02-A001, 05.05-A008, 05.08-A006

SMG07 DrAm Required 11.10-A002, 11.10-A003, 11.10-A004, 11.10-A005

Operation of Multi-band GSM/DCS by a single OperatorCompleted S15S15

S15

S15

S15

SMG01 Tdoc 410/95, 44Mr T.Ljunggren Telia Mobitel


Overload control enhancement for Location Registersdeleted @ xxxS23

SMG03 Required


WI Title




SMG01 Stage 1 M A.Conrad T Mobil DE 02.63

SMG03 Stage 2 Mr. H. Nazeman T Mobil DE 03.63

SMG03 Stage 3 Mr. H. Nazeman T Mobil DE 04.68

Packet Data on Signalling ChannelsCompleted S16S19

S16

S19

SMG03 M A.Conrad T-Mobil

SMG01 Stage 1 Mr N.Renaud France Telecom F

Payphone Servicesdeleted @ S20S23

SMG01 Mr N.Renaud France Telecom

SMG01 Stage 1 Mr A.Toepfer MMO DE

SMG03 Stage 2

Premium Rate Services (PRS)deleted @ S20S23

S23


SMG04 tbd required Hayes tbd


Provision of text telephony service in GSM and UMTS

tbd

tbd

SMG04 775/98required Hayes


SMG04 stage1, stage 2 required tbd

Provision of text telephony service in GSM and UMTS

tbd

tbd

SMG12 775/98required Hayes


WI Title




SMG01 Stage 1 Mr N Renaud France Telecom F

Provisions for Hot Billingdeleted @ tbdS23

SMG01 Mr N Renaud France Telecom

SMG01 Report Mr D.Richards AT&T NSI UK

SMG02

Radio Local Loop (RLL) using GSMcompleteS18

S18

SMG01 Mr D.Richards AT&T NSI

Requirements for equipments/systems interfacing GSM tbd 149/97required

SMG01 CR 02.03, 02.07

SMG04 CR 03.41

Second SMS broadcast channelCompleted S16S20

S20

SMG01 332/96None


tbd tbd required tbd

Service Continuity and Provision of VHE via GSM/UMTSAll R99 WI completion dates moved to S31

S28

S30



WI Title




SMG09 CR Mr W.Mohrs T Mobil DE

SMG01 Required

Service Dialling NumbersReleased after S15completed

S17

SMG09 281/95Mr W.Mohrs T-Mobil

T1P1 stage 1 required new: 02.66

Service Provider Number Portability (USA)Earlier called "Local Number Portability", "T1P1.5 Number Portability SWG"

S28

T1P1 0278/97required

SMG02 CR Required

Service to GSM Handportables in trainsSMG1 input not required

SMG02 required

SMG09 New specs Nigel Barnes Motorola CSD New: 02.48, 03.48

SMG04 CRs CRs: 03.38, 03.40

SIM - Security mechanisms for the SIM Application Toolkitcore specs completed S24/S25

S24/S25

S24

SMG09/10 762/96Nigel Barnes Motorola CSD

SMG09 11.12 Mr R.Lindholm Nokia FIN 11.11

SIM - Three Volt Technology SIMWork item completed S13S17

SMG09 Result in 11.12Mr R.Lindholm Nokia


WI Title




SMG09 11.14 Mr K.Woodsend NEC UK 11.11

SMG01 stage 1

SMG04 DrAm Required 03.40-A002

SIM Application ToolkitCombines WIs "Proactive SIM" and "SIM data download"; stage 1 planned for approval @ S28

S17

S28

S17

SMG09 Mr K.Woodsend NEC

SMG09 CR Mr R.Lindholm Nokia Mobile Phones FIN 11.11

SIM I/F data Transfer Speed EnhancementWork item completed S16completed

SMG09 Tdoc 709/95Mr R.Lindholm Nokia Mobile Phones

SMG01 CR

SMS - Special SMS Message indicationWork item completed S13S16

SMG01 Tdoc 607/95None

SMS Cell Broadcast Discontinuous Reception (CB-DRX)

SMG01 TBD

SMG04 DrAm Mr I.Harris Vodafone UK 03.40-A004r2

SMS concatenationWork item completed S13S13

SMG01 Tdoc 74/95None


WI Title




SMG01 CRs Nicolas Renaud France Telecom F 02.30

SMG04 CRs CRs: 03.38 03.40 03.41 03.42

SMG03 CRs CRs: 09.02

SMS enhancements phase 1

S25

S25

S25

SMG01 582/96Nicolas Renaud France Telecom

SMG04 CR Mr K.Holley BT (Chairman DGMH) UK 03.40

SMS Interworking Extensions

S20

SMG04 431/95Mr K.Holley BT

SMG04 CRs Mr P.Edlund Ericsson S 03.40, 03.47

SMG03 CRs CRs: 09.02

SMS Mobile Busycore specs completed S26S26

S26

SMG04 430/95Mr P.Edlund Ericsson

Software Version Number (SVN)

SMG04 03.39 Mr I.Harris Vodafone UK

Standard access SMS, SC-SMESdeleted @ S21del S21

SMG04 Mr I.Harris Vodafone


WI Title




Study on Combined GSM and Mobile IP Mobility Handling in UMTS IP CAll R99 WI completion dates moved to S31

SMG12 760/98E.Hubbard Telia



Study on provision of facsimile services in GSM and UMTS

tbd

tbd

SMG04 775/98E.Colban Ericsson

SMG01 Requirements Required

Subscriber Class for Advice of Chargedeleted @ S20S23

SMG01 Required

SMG01 Report

Support of additional call set-up MMI procedures

S20

SMG01 150/96None

SMG01 Stage 1 Mr Kokkola Nokia FIN

Support of Home Area Priority (Renamed SoLSA> See below)Duplicate of to be proposed WI "Support of Localized Service Area"

S18

SMG01 Mr Kokkola Nokia


WI Title




SMG01 stage 1 Tommy Kokkola Nokia FI new: 02.43

Support of Localized Service Area (SoLSA)

S27

SMG01 Tommy Kokkola Nokia





Support of non-realtime Multimedia Messaging Service

tbd

tbd

tbd






Support of non-realtime Multimedia Messaging Service

tbd

tbd

tbd


Support of Operator Specific Services (SOOS) when roamingto be subsumed under VHE?

SMG1 required

SMG01 02.79 Ms S.Morice SFR F

SMG03 Stage 2

Support of Optimal Routeing (SOR)

S19

S19

SMG01 Ms S.Morice SFR


WI Title




SMG01 New spec, CRs Ms T.Sundbye Tele-mobil N New: 02.95; CRs: 02.04

Support of Private Numbering Plan (SPNP)

S24

SMG01 Ms T.Sundbye Tele-mobil

SMG04 stage 2,3 Mr. J.Candish Nortel UK

SMG01 stage 1 Mr J. Candish Nortel UK

Support of Restricted Digital Information and V.120 rate adaptation in GSWork in SMG4 depends on progress in SMG3

S20

S20

SMG04 Mr. J.Candish Nortel

SMG04 Requirements Mr S.Ouvrier Telia S New: 03.54

SMG03 stage 2, 3 CRs CRs: 03.02 03.18 09.02

Support of Shared Interworking Function (SIWF)core specs completed S24S24

S24

SMG04 Mr S.Ouvrier Telia

SMG11 stage 1 T Mobil DE new: 02.53

Tandem Free Operation of speech codecs in Mobile-to-Mobile Calls (MMC

S28

SMG03/11 952/97W.Navarro Nortel

All STCs CR PT12 ETSI F Various

Technical Enhancements/improvements for phase 2General WI for Phase 2 "fixes"

S99

All STCs On-going exerciPT SMG


WI Title




SMG11 CRs Ian Goitz Cellnet UK 03.50, ETS300 540, ETS300 607-1, GSM 11.10-1 TBR20, TBR32

Test methods for handset and headset mobile stationdeleted @ S27del

SMG11 123/96Ian Goetz Cellnet

SMG01 Stage 1 Mr L.Giles BRT/UIC UK

Transmission of date/time and zonereplaced by WI "Network Identity and Time Zone (NITZ)"

S18

del Mr L.Giles Vodafone

SMG01 Study Mr D.Richards AT&T NSI UK

Transparently supporting UPT phase 1SMG1 reported that no work required

S13

SMG01 Mr D.Richards AT&T NSI

UMTS Charging & Billing SMG01 681/98D.Chambers

UMTS Core based on ATM Transport SMG12 759/98M.Wilson, A.Rouz Fujitsu


WI Title




UMTS Numbering, Addressing and Identities SMG01 681/98S.Kleier MMO

UMTS Open Service Architecture SMG12 761/98R.Schmersel Ericsson

SMG04 CR Required

Unified SMS CB scheduling algorithmdeleted @ S19cancelled?

SMG04 Required

SMG01 Stage 1 Ms N.Hodgson Vodafone UK

SMG03 Stage 2

Universal access to freephone numbersdeleted @ S20S23

S23

SMG01 Ms N.Hodgson Vodafone

SMG04 GSM 07.61; CRs required GSM 09.61

SMG03 CRs required GSM 09.02, GSM 09.60

Unstructured octet stream GPRS PDP Type (R98)

S28

S28



WI Title




SMG01 Stage1 Mr A. Conrad T Mobil DE new: 02.87; CRs: 02.04, 02.30

SMG03 Stage 2

SMG03 Stage 3

User-to-User Signalling (UUS)stage 1 completeS19

S28

S28

SMG01 Mr A. Conrad T-Mobil

SMG01 report 02.04, 02.90

SMG03 CRs 03.38, 03.90,04.80, 04.90, 09.02

SMG09 11.11

USSD EnhancementsS28 on adice of T. KokkolaS28

S28

S28

SMG01 511/96Sverre Slotte Nokia

Virtual Home Environment SMG01 681/98E.Postmann Siemens

SMG01 Requirements M. Kanerva Nokia C.Systems FIN

Wireless Mob. Stat. Location : Name kept Location ServicesDuplicate of WI "location services"

S23

SMG01 M. Kanerva Nokia C.Systems


Tdoc SMG 746: PT SMG Status Report to SMG#27 page 1

ETSI / SMG Tdoc SMG 746/98Meeting #27 AI: 5.4Praha, 12 - 16 October, 1998

Source: PT SMG

Title: PT SMG Status Report (STF 12, STF 83, STF 80V, STF 61V,STF 79)

Status: for approval

Contents:

1 GENERAL ................................................................................................................................................................3

2 STATUS OF SPECIFICATIONS ...........................................................................................................................3

2.1 GSM SPECIFICATIONS..............................................................................................................................................42.1.1 GSM Phase 1 ...................................................................................................................................................42.1.2 GSM Phase 2 ...................................................................................................................................................42.1.3 GSM Phase 2+.................................................................................................................................................4

2.2 UMTS......................................................................................................................................................................52.3 PUBLICATION OF SPECIFICATIONS.............................................................................................................................6

2.3.1 Free access to ETSI specifications ..................................................................................................................62.3.2 ETSI CD ROM, ETSI publication date, SMG CD ROM..................................................................................62.3.3 Software compatibility problems .....................................................................................................................72.3.4 New SMG file structure on ETSI server...........................................................................................................7

3 MS TYPE APPROVAL AND TESTING ACTIVITIES .....................................................................................10

3.1 PHASE 2+ TBR MODULES PREPARATION................................................................................................................103.2 PHASE 2 TBR MAINTENANCE.................................................................................................................................103.3 MS TEST SPECIFICATION (11.10-1) UPDATING AND MAINTENANCE........................................................................103.4 MS TEST SPECIFICATION (11.10-1) DEVELOPMENT.................................................................................................113.5 MS TEST SPECIFICATION (11.10-2) ICS UPDATING AND MAINTENANCE.................................................................113.6 MS TEST SPECIFICATION (11.10-3) TTCN UPDATING AND MAINTENANCE ............................................................113.7 MS TEST SPECIFICATION (11.10-3) TTCN DEVELOPMENT.....................................................................................113.8 OTHER PLANNED ACTIVITIES .................................................................................................................................12

4 PROGRAMME MANAGEMENT .......................................................................................................................12

4.1 GSM ......................................................................................................................................................................124.1.1 UIC project ....................................................................................................................................................124.1.2 GPRS .............................................................................................................................................................12

4.2 UMTS....................................................................................................................................................................12

5 ITU CO-ORDINATION ........................................................................................................................................12

6 PT SMG FUNDING AND RESOURCES.............................................................................................................12

6.1 THE TEAM..............................................................................................................................................................136.3 PT SMG JOB DESCRIPTION.....................................................................................................................................13

7 ETSI ACTIVITIES.................................................................................................................................................13

8 PT SMG MANAGEMENT....................................................................................................................................13

9 EXPERTS NEEDED ..............................................................................................................................................14

10 USEFUL INFORMATION..................................................................................................................................14

ANNEX 1 BUDGET USAGE OF PT SMG...............................................................................................................1


ANNEX 2 SMG MEETING CALENDAR ................................................................................................................1

ANNEX 3 ACCESS TO SMG (SUB-GROUP) DOCUMENTS / E-MAIL GROUPS ...........................................1

A3.1 THE ETSI SERVER................................................................................................................................................1A3.2 ETSI E-MAIL LISTS ................................................................................................................................................1A3.3 GSM MOU PERMANENT REFERENCE DOCUMENTS (PRD) ...................................................................................2


1 General

In 1998, the following Special Task Forces (STF) for SMG exist:

a) GSM related STF:

For STF80V, SMG#26 and ETSI Board approved modifications to the terms of reference.

In addition, terms of reference for an STF on GSM Number Portability (provisional numberSTF EU) was approved by SMG#26 and ETSI Board.

b) UMTS: STF 83

Throughout this report, the generic term "PT SMG" is used to represent the STFs mentionedabove.

The STC related work in which PT SMG has taken part are covered by the STCs Status Reportswhilst this document gives a survey

• on the specific work of PT SMG, and• on administrative matters.

2 Status of Specifications

As usual, the updated status list of specifications after SMG#27 will be distributed as an annex ofthe plenary meeting report. The status of specifications before SMG#26 is available inTdoc SMG 747/98.

The present status and action list of phase 2/2+ GSM specifications and of UMTS specificationsas EN, TS, TR, and (revisions of) ETRs, ETSs and GTSes, including dates for Public Enquiry(PE), Vote and One step Approval Procedure (OAP) is given in Tdoc SMG 733/98 (prepared byIan Doig).

The list of CRs presented to SMG#27 is contained in Tdoc SMG 744/98 (prepared by MichaelSanders). The update in accordance with the results of this meeting is Annex 2 ofETSI/SMG(98)4.

The total number of SMG approved GSM and UMTS specifications developed as follows:

STF deals with

12 Development of GSM phase 2+ standard

61V ASCI

80V GPRS

79 Mobile station test specifications


GSM & UMTS

50

100

150

200

250

300

350

400

SMG#1

7

SMG#1

8

SMG#1

9

SMG#2

0

SMG#2

1

SMG#2

2

SMG#2

3

SMG#2

4

SMG#2

5

SMG#2

6

approved CRs

2.1 GSM specifications

2.1.1 GSM Phase 1

SMG#25 decided to declare the GSM Phase 1 specifications as “closed”. This means (see TdocSMG 1135/97):• the specifications are still published;• no CRs are possible anymore.

2.1.2 GSM Phase 2

GSM Phase 2 Change requests developed as shown in the figure below:

Phase 2

020406080

100120140160180

SMG#1

7

SMG#1

8

SMG#1

9

SMG#2

0

SMG#2

1

SMG#2

2

SMG#2

3

SMG#2

4

SMG#2

5

SMG#2

6

approved CRs

2.1.3 GSM Phase 2+

Change Requests to GSM Phase 2+ developed as shown in the figure below:


0

50

100

150

200

250

17 18 19 20 21 22 23 24 25 26

Phase 2+ R96 appr.

R97 appr.

R98 appr.

SMG#

2.2 UMTS

Before SMG#27, the following UMTS specifications were under SMG change control, but notpublished by ETSI:

No TITLE CURRENT VERSION

21.06 O&M requirements for the UMTS 3.0.0

22.01 Universal Mobile Telecommunications System (UMTS): Service aspects; Service 3.2.1

22.05 Services and service capabilities 3.1.0

22.07 UMTS Terminal and Smart Card Concepts 3.0.0

22.24 Charging and Accounting Mechanism 3.0.0

22.25 Quality of Service and Network Performance 3.1.0

22.60 Mobile multimedia services including mobile Intranet and Internet services 3.0.0

22.70 Virtual Home Environment 3.0.0

22.71 Automatic establishment of roaming relations 3.0.0

30.00 SMG - UMTS Work programme 3.5.0

30.01 UMTS Baseline document: Collection of the SMG’s positions on the UMTS 3.3.01

30.20 Technical characteristics, capabilities and limitations of mobile satellite systems 3.1.0

33.20 Security principles for the UMTS 3.0.1

1 Version 3.3.0 reflects the decisions up to SMG#25. Version 3.4.0, reflecting the decisions of SMG#26, is not yet available.


The following specifications have been published:

NO TITLE CURRENT VERSION

21.01 Overall requirements on the radio interface(s) of the UMTS 3.0.1

30.03 Selection procedures for the choice of radio transmission technologies of the UMTS 3.2.0

30.06 UTRA Concept Evaluation Reports 3.0.0

21.02 High level requirements relevant for the definition of the UMTS Terrestrial Radio Access 3.0.0

30.04 Definition of the limited number of UTRA concepts 3.0.0

Change Requests to UMTS specifications have been approved as shown below:

UMTS

0

1

2

3

4

5

SMG#22 SMG#23 SMG#24 SMG#25 SMG#26

approved CRs

2.3 Publication of specifications

2.3.1 Free access to ETSI specifications

As from mid September, ETSI made Technical Specifications and Reports available to downloadfree of charge from the ETSI WWW page http://webapp.etsi.org/publicationssearch/. Due to anexisting NSO agreement, ENs and ETSs will be only be available after 01/11/98.

2.3.2 ETSI CD ROM, ETSI publication date, SMG CD ROM

ETSI CD ROM:

It should be noted that the ETSI CD ROM contains ETSI published versions. Manyspecifications (in the new scheme, the ENs, in the old scheme the ETS and TBR) have to

AP SMG For the following specifications, PT SMG is asking for confirmation that they canbe published. In addition, PT SMG often receives questions on the UMTS work program.SMG might consider to publish UMTS 30.00 as well, in particular as all the informationis available on the Web.


undergo the two step or one step approval procedures (TAP, OAP) within the national standardsorganisations represented in ETSI Hence, it is normal that a specification, e.g., GSM 04.08Version 5.7.0, is published by ETSI with date say 1 May 1998, and is in fact the same as theSMG version from November 1997 (after SMG#23); the ETSI publication of the version 5.7.0might then have a newer date than the SMG internal version 5.9.0.

SMG CD ROM:

The SMG#26 CD ROM has been available shortly after SMG#26. The SMG#27 CD ROM isplanned to be issued 3-4 weeks after the SMG#27 plenary.

2.3.3 Software compatibility problems

PT SMG informed earlier SMG plenaries about compatibility problems when different softwaretools are used for the generation of documents.

Now, PT SMG had to discover that there are compatibility problems between different Wordversions, sometimes leading to the consequence that

• text disappears• modifications made in figures/pictures disappear

when a Word for Windows 97 text is converted to Word 6.

ETSI rules don’t help with this problem. By the way, PT SMG received an information (butdidn’t verify it) that ITU doesn’t accept documents in Word for Windows 97.

The problem has been reported to WOME, which elaborated some recommendations toSMG#27.

2.3.4 New SMG file structure on ETSI server

2.3.4.1 SMG specifications on ETSI server

On proposal of PT SMG in agreement with WOME, SMG#26 accepted the following approachfor storing specifications on the ETSI server:

• When a word version is available of a document (extension “.doc”), only the zippedversion (“.zip”) is put on the server. Same for access (“.mdb”) or Excel (“.xls”) orPowerpoint (“.ppt”). When no electronic version is available, the document is scannedand normally the non-compressed version goes to the server (because compression gain isvery small).

• File name convention (explained by examples):∗ 0408-491.zip is the zipped 04.08 version 4.9.1. The “-“ shows that it is a

version not published by ETSI. (This information is also explicitly stated onthe front page of the specification.) If and when a version is published byETSI (this will entail a change of the front page and the headers, nothingelse), the version is increased to 4.9.2 and the file would be

0408_492.zip (“_” instead of “-“).

∗ 0408-4b0.zip is the zipped 04.08 version 4.11.0.


∗ 01318D10.zip is the zipped form of draft 1.0 of version 8 of 01.31. Thisscheme, as decided in SMG#25, is applicable when a major version of aspecification is under STC change control.

∗ 0408D4p0.zip: This is a PT SMG internal draft before final verification inPT SMG. It would be distributed to STC experts only in rare and extremecases (e.g. when a meeting is convened immediately after an SMG plenary).

• The following file structure should be used after SMG#26:

etsi/tech-org/SMG/documents/

SMG

SMG1

SMG2

…

SMG12

WOME

SPECS

. .

Drafts . .

Ph1

Ph2

Ph2pl-v5

Ph2pl-v6

Ph2pl-v7

STC-CTR

01-serie

01318D10.zip

UMTS

In short: similar sub-directories for• drafts (versions 10.x.y, 1.x.y, 2.x.y)• phase 1• phase 2• phase 2+ major version 5• phase 2+ major version 6• phase 2+ major version 7• …• UMTS• specifications under STC Change Control.


2.3.4.2 File structure for SMG plenary

In agreement with WOME, PT SMG intends to introduce, before the end of the year, thefollowing file structure for the directory SMG/document/SMG (prepared by Michael Sanders):

• The structure only defines sub-directory levels 1 and 2.• Only one file may in the "root" directory, a readme.txt file describing the structure of the

SMG area.

The table below indicates the directory names to be found below /tech-org/smg/document/smg

(it means that every directory under level 1 has all sub-directories in the box under level 2).

Main Directory sub-directory level 1 sub-directory level 2 Commentsinbox uploading areaplenary 24b9802_Paris the plenary directory should contain

25_9803_Sophia all plenary meetings26_9806_Helsinki27_9810_Praha report “invite” and “agenda” only for the next

meetinget cetera pp invite

agendatdocs

Databases change_request CR data basemeeting_calendar the meeting calendarmembers members databaseofficials a (reference to a) document listing all

chairpersonsstatus_list Specification status listwork_items work item database

Groups co-ordination SMG coordination groupGSM_MoU GSM MoU PRDs (until when all are available

on WWW)number_portabilityetc.

Other SMG working groups

PT_SMG PT SMG executive meetingsadhocs LCS_9810_sophia see plenary This directory would contain all joint and

adhoc meetings. If there are many meetings onone particular subject, an extra subdirectory(describing the topic) could be added underthe adhocs directory

Specs See description abovetools acrobat acrobat reader

microsoft patches etc.templates MS word templates - in particular the CR form

and work item description sheet formOthers could be added as needed

www for future use to hold http files for easieraccess to the SMG area

2.3.4.3 File structure for SMG STCs

A proposal for harmonization of STC file structure is in progress in PT SMG.


3 MS Type approval and testing activities

For more information of SMG7 activities, see the SMG7 status report in Tdoc SMG 541/98.

3.1 Phase 2+ TBR modules preparation

PT SMG pursued the ongoing development of Phase 2+ Type approval documents by:

• co-ordination with ACTE and GTAAB, (5 scope statements approved, 2 new mandates

received (one for R-GSM, one for CTS-MS)• preparing and submitting the CTS-FP Draft scope statements (one new mandate is expected)• meetings with ETSI secretariat, on EC order vouchers for Phase 2+ module implementations

and Phase 2 TBR merging - see Tdoc SMG 748/98, presented to SMG for approval.• preparing the Phase 2+ R-GSM and the ASCI TBR modules for information to SMG#27. The

modules are linked to Phase 2 TBR 19 and 31 and comply with the 98/13/EC TerminalDirective.

• organising and participating in SMG7 RTTE Ad hoc meeting in Sophia Antipolis (Aug 28)• participating in OCG TG6 meeting focused on RTTE implementation (Sep 2)

Next Steps:

• examine the implications of the new RTTE• participate in next OCG TG6 meetings (Nov 5, Dec 3)• attend the RTTE steering Committee’s AHG• complete and submit R-GSM and ASCI TBR modules to SMG7#20 for approval.

3.2 Phase 2 TBR maintenance

PT SMG pursued the ongoing update and maintenance of TBRs by:• Updating Phase 2 TBR into new editions:

• TBR 19 (edition 6), now EN 301 419-1• TBR 31 (edition 3), now EN 301 431.

• Evaluating and reporting to SMG7 on merging of TBR 19 and 31.• Preparing a merged version of TBR 19 and 31, Access (Draft EN 301 419-1)

Next Steps:• Prepare EN 301 420-1 (merged TBR 20 and 32, Telephony)• Send TBR 19 edition 6 (EN 301 419-1) and TBR 31 edition 3 (EN 301 431) on TAP/OAP.• Complete revised EN 301 419-1 (merged TBR 19 and 31, Access) for SMG#28

3.3 MS Test specification (11.10-1) updating and maintenance

PT SMG pursued the ongoing update and maintenance of the Part 1 prose:• Implemented 11.10-1 test specification versions 4.23.0 and 5.6.0

AP SMG To approve the ToR for TBR merging and new TBR modules inTdoc SMG 748/98. In addition, PT SMG often receives questions on the UMTS workprogram. SMG might consider to publish UMTS 30.00 as well, in particular as all theinformation is available on the Web.


3.4 MS test specification (11.10-1) development

PT SMG supported ongoing development activities:

• Co-ordination with GPRS testing Drafting Group• Attendance of GPRS Drafting Sessions #5 and #6.• Organisation and participate in GPRS Drafting session #6 in Sophia Antipolis• Drafting and finalising VBS/VGCS, (ASCI) testing specs (Tdoc 362/98)• Drafting and finalising R-GSM (RF) testing specs (Tdoc 363/98 submitted here for approval)• Planning for 11.10-1 version 6

Note: CTS testing Drafting Group activities were on hold during the reporting period

Next steps:• Draft VGCS/VBS cell re-selection (ASCI RF) testing• Draft VGCS/VBS cell change (ASCI signalling) testing• Increase resources for GPRS MM test development

3.5 MS Test specification (11.10-2) ICS updating and maintenance

No work performed.

Next steps:• Develop new 11.10-2 Implementation Conformance Statement (ICS) version 4.24.0• Create new 11.10-2 Phase 2+ ICS (version 5.7.0).

3.6 MS Test specification (11.10-3) TTCN updating and maintenance

Ongoing Quality Assurance and Maintenance of GSM900 and DCS1800 Abstract Test Suites(ATS):

• Ongoing assistance to ANITE for TTCN implementation including syntax/static semanticchecks.

• Monitor and review ANITE TTCN implementation of version 4 for the following ATSs:• Layer 3 signalling ATS• Enhanced Full Rate (EFR) signalling ATS• Cell Selection / Re-selection ATS• Multiband signalling ATS

Next steps:• Monitor and review version 5 TTCN implementation.

3.7 MS test specification (11.10-3) TTCN development

PT SMG planned for the necessary ATS development for UIC

Next steps:• Draft VGCS/VBS/eMLPPP (ASCI) TTCN ATS• Draft R-GSM TTCN ATS


3.8 Other Planned Activities

• Inclusion of PCS 1900 standard into 11.10• Evaluate and plan for the transition towards the European Parliament and Council Directive

on Radio Telecommunications Terminal Equipment and the mutual recognition of theconformity of equipment.

4 Programme management

Program management is reported under Agenda Items 6.12 (GSM) and 7.8 (UMTS). Here, onlywork items under special STF management are reported:

4.1 GSM

4.1.1 UIC project

The European Commission has issued a DRAFT MANDATE TO CEN/CENELEC/ETSI FORSTANDARDIZATION in the field of RAILWAY EQUIPMENT on the INTEROPERABILITY OFTHE TRANS-EUROPEAN HIGH-SPEED RAIL SYSTEM, see Tdoc SMG 750/98. In a meetingbetween ETSI, CEN and UIC (3 July, 1998 at ETSI premises), the responsibilities between ETSIand CEN have been clarified, see Tdoc SMG 751/98.

As a consequence, creation of an STF for dealing with the SMG related parts has been proposed.It should be funded by the EC (possibly with some co-funding of UIC). The Terms of Referenceare presented in Tdoc SMG 749/98 for approval by SMG#27.

4.1.2 GPRS

PT SMG is support the GPRS testing activities with Jean-Jacques Davidian, Shicheng Hu (ETSIPEX), Johan Petersen and soon, Professor Wang (University Shanghai) who has already severaltimes worked in PT SMG on a temporary basis.

A necessary change to the STF80V Terms of Reference had been accepted by SMG#26 and ETSIBoard.

4.2 UMTS

See agenda item 7.8.

5 ITU Co-ordination

By voluntary contribution from Nokia, Makis Kokkos has seconded as ITU-R Co-ordinator. Hehas to resign as he will get new responsibilities in Nokia. We thank Nokia for this support, andwe thank Makis for his achievements.

6 PT SMG Funding and Resources

For details on the budget, see annex 1. PT SMG (Antun Samukic/Ansgar Bergmann) participated

Nokia has offered Stuart Cooke as a successor. SMG#27 should decide on the matter.


in the STF SMG Voluntary Funding Task Force. Ansgar Bergmann is also acting as secretary ofSMG AG.

6.1 The Team

As announced at SMG#26, Fredrik Pettersson has left the team end of July 1998. He had a verydemanding job in PT SMG, being responsible for SMG3 WPA, SMG2 WPA and SystemArchitecture/SMG12. His work was excellent, and PT SMG thanks him very much.

The team at present consists of Roger Tarazi, Peter van der Arend, Paolo Usai, Michael Sanders,Mark Cataldo, Johan Petersen, Jean-Jacques Davidian, Friedhelm Rodermund, FredrikPettersson, David Williams, Antun Samukic, Ansgar Bergmann.

Shicheng Hu (ETSI PEX) supports the TTCN and prose tests in GSM 11.10.

6.3 PT SMG job description

PT SMG tries to support all SMG STCs, and - as much as possible - all working parties, ad hocgroups, and task forces; the PT SMG experts act as the editors of all Technical Specifications forGSM which are under change control.

As usual, the updated detailed job descriptions for PT SMG are presented to SMG(Tdoc SMG 764/98).

7 ETSI activities

8 PT SMG management

PT SMG executive meetings take place nine times per year, each meeting half a day (afternoon)followed by a half day (morning) management meeting of PT SMG. SMG officials are invited toparticipate at their choice. The management meetings carry out the agreements of the executivemeeting.

SMG members may send any problems, proposals etc. (by e-mail or fax) under subject startingwith PT SMG management to [email protected]. They will be treated, the latest, at thenext SMG PT management / executive meeting.

Dates for the meetings:

1998: 19/20 October, 7/8 December

1999: 1/2 Feb, 15/16 Feb, 12/13 April, 14/15 June, 21-22 June, 6/7 Sept, 11/12 Oct, 18/19 Oct,13/14 Dec.

Draft agenda 19/20 October:• Planning of actions resulting from SMG#27• Review of assignment of responsibilities in PT SMG, Review of PT SMG job description• Review of program management• Review of CR data base and status list of specifications.


9 Experts needed

There are two open longer term positions in PT SMG, shown as NN in the PT SMG jobdescription. In addition there are limited positions for GSM Number Portability (2 experts, 6 + 2Months) and for Mobile Station testing, in particular TTCN support. It should be noted that thereis some flexibility to re-assign responsibilities in PT SMG, whence also experts in areas whichare shown as “occupied” should consider to join the team.

Calls for experts are in Tdoc SMG 762/98, Call for Experts for STF12 (GSM), 83 (UMTS) andfor STF EU (Study and investigation of the introduction of number portability in the GSMfamily), which is also Collective Letter 1899.

Interested delegates should contact Ansgar Bergmann.

10 Useful information

The SMG meeting calendar is annex 2, together with information how to find the latest versionof the meeting calendar on the WWW or FTP server. Information on access to e-mail lists andthe FTP server is in annex 3.

Tdoc SMG 746, Annex 1 page 1

Annex 1 Budget usage of PT SMG

[see file annex-a.doc]




Annex 2 SMG Meeting Calendar

Updated information of SMG (sub-group) meetings is available in three ways:• On the ETSI server, under SMG/document/SMG, you find a file called mtgcal.xls.

Download it and open it (it is an Excel file). Take care! Near the left corner you see thatthere are two sheets, one for 1998, one for 1999. Don’t look for the 1998 dates in the1999 sheet. If you have a sufficiently high version of Excel, you will see red points formost meetings. If you move to a filed with a red point, an indication of the meeting venuewill appear.

• The same file is available on the WWW ETSI SMG home page(http://www.etsi.org/smg): You’ll then see the SMG meetings in the blue part at left.Then follow the instructions.

• On the WWW ETSI home page (http://www.etsi.org), click on the red button “TechnicalBodies” (it is the one with five iconised ETSI officials); six rounded rectangles willappear. Click on the one with writing “Calendar”. A box appears, and in the field“Technical Body” you can activate a pull down menu and select a groups. (You’llprobably have to scroll down to click the botton “Find Meetings”.)

In any case, if you have a question on meetings, you can contact Emmanuelle Wurffel (phone+33 4 9294 4266, fax +33 4 9365 2817, e-mail [email protected]).


Annex 3 Access to SMG (sub-group) documents / e-mail groups

A3.1 The ETSI Server

The SMG documents and sub-group documents can be found on the ETSI server under thedirectory:

http://docbox.etsi.org/tech-org/smg/document

A user name and password is required. Any ETSI member can obtain a user name by contactingthe ETSI help desk; e-mail: [email protected] or tel: +33 4 9294 4900 or filling out an on-lineapplication form at:

http://www.etsi.org/AccountRequest/form.idc

A3.2 ETSI e-mail lists

SMG has several discussion/information e-mail groups on the ETSI e-mail listserver. In order tojoin these lists list, you must register by sending an e-mail to the listserver. For example, if youwish to join the SMG_plenary list, send an email to [email protected] with the followingline of text in the body of the message:

subscribe ListGroupName YourFirstName YourLastName

(This text must be the message body, not in the subject field which is always ignored.)

You will then automatically receive (via e-mail) further details about how the list operates, andyou’ll have to follow the instructions - in particular you will be asked to confirm, and if youdon’t do that, your subscription will be cancelled soon.

For example, Ansgar Bergmann registered successfully for the SMG Plenary list by sending themessage

subscribe SMG_plenary Ansgar Bergmann

All lists have an associated archive of every e-mail sent via that list. Information on how toaccess the archive are sent to you when you subscribe to the list.

There are many e-mail groups on the list server. A continuously updated list of these groups canbe found at:

http://www.lsoft.com/scripts/wl.exe?XH=LIST.ETSI.FR

Please use the e-mail lists with some care, in particular, when responding to a message.

For example, if you receive a message sent to an e-mail list, and you want to reply: If you justclick on “reply”, the answer will probably go to the whole list again. So every member of the list(around 260 people) would receive your answer, and that is probably not always what you want.

Documentation on the use of e-mail lists can be found onhttp://www.lsoft.com/manuals/index.html.


A3.3 GSM MoU Permanent Reference Documents (PRD)

GSM MoU intends to make all non-restricted PRD available on

http://www.gsmworld.com

PRDs of 3GIG are already available from there.

SERG PRD SE13 is available on the FTP server under /tech-org/smg/Document/smg/mou-prd. Itwill be moved to /tech-org/smg/Document/smg/Groups/GSM_MoU, or deleted when thedocument becomes available on http://www.gsmworld.com.

Draft ETSI/SMG(98)3 Part B, Annexes 16/11/98

ANNEX 8 STRUCTURE OF SMG AND SUBGROUPS

SMG

Chairman: Fred HillebrandVice Chairmen: Alan Cox (Vodafone), Gunnar Sandegren (Ericsson)Secretary: Ansgar Bergmann

SMG1

Chairman: Alan Cox (Vodafone)Vice Chairmen: Armin Toepfer (Mannesmann Mobilfunk), Derek Richards (Lucent)PT SMG support (including all subgroups): Roger Tarazi

Ad hoc groups:• GPRS phase 2 ad hoc, Chairman Graham Heaton (Vodafone)• UMTS phase 1 ad hoc, Chairman Emanuel Puga Perera (CNET)• UMTS 22.01 ad hoc, Chairman Chris Friel (Cellnet)• SIM toolkit ad hoc, Chairman Nigel Barnes (Motorola)

SMG2

Chairman: N.P.S. Andersen (Tele Danmark)Vice Chairman: M. Färber (Siemens)PT SMG support: Paolo Usai

Working Parties:• WPA on Signalling Aspects, Acting Chairman Andrew Howell (Motorola);

PT SMG support: D. Williams• WPB on Radio Aspects, Chairman N.P.S. Andersen (Tele Danmark);

PT SMG support: P. Usai

Ad hoc groups:• UMTS-L1 Layer 1 Expert Group, Chairman A. Toskala (Nokia), Vice Chairman M.

Nasshan (Siemens), Secretary F. Gourgue (Alcatel)• Layer 2&3 Protocol Expert Group, Chairman D. Fauconnier (Nortel), Vice Chairman:

C. Boisseau, France Télécom/CNET, Secretary G. Petkov (NEC)• UTRAN Architecture Expert Group, Chairman P. Willars (Ericsson), Vice Chairman:

none, Secretary A. Länsisalmi (Nokia)• ITU Expert Group, Chairman N. P. Magnani (Cselt), Secretary: R. Bruzzone (Philips

Consumer Communications)

SMG3Chairman: Harald Dettner (Siemens)


Acting Vice Chairmen: Hannu Hietalahti (Nokia), Steffen Haberman (T-Mobil), Ian Park(Vodafone)

PT SMG support: Peter van der Arend

Working Parties:• WPA on radio-interface & GPRS, Chairman Hannu Hietalahti (Nokia)

PT SMG support: Johan Petersen• WPB on supplementary service, Chairman Steffen Haberman (T-Mobil)

PT SMG support : Peter van der Arend• WPC on network aspects, Chairman Ian Park (Vodafone)

PT SMG support : David Williams

SMG4

Chairman: Kevin Holley (BT)Vice Chairman: Norbert Klehn (Siemens), Graham Heaton (Vodafone), Lars Novak(Ericsson), Arthur Gidlow (One2One)PT SMG support (including all subgroups): Friedhelm Rodermund

Subgroups:• SMS Group, Chairman Arthur Gidlow (One2One)• Cell Broadcast Group, Chairman Ian Harris (Vodafone)• GPRS Group, Chairman Graham Heaton (Vodafone)• MS-TE Group, Chairman Lars Novak (Ericsson)• IWF Group, Chairman Norbert Klehn (Siemens)• MExE Group, Chairman John Candish (Nortel)• UMTS Group, Chairman Kevin Holley

SMG6

SMG6 Chair: Gisela Hertel (Iridium)SMG6 Vice Chairmen: Kai Sjöblom (Nokia), Steffen Weichselbaum (MannesmannMobilfunk)PT SMG support (including all subgroups): Michael Sanders

Subgroups:• WPA (UMTS), Chairman Steffen Weichselbaum (Mannesmann Mobilfunk)• 12.11 subgroup, Chairman NN. (was Mark Cataldo (Lucent))• 12.08 subgroup, Chairman NN. (was Bill Szelazek (Lucent))• GPRS subgroup, Chairman Kai Sjöblom (Nokia)

SMG7

SMG7 Chairman: Rémi Thomas (France Télécom)SMG7 Program Manager: Jean-Jacques Davidian


Subgroups:• Signalling subgroup, Chairman Rémi Thomas (France Télécom)

PT SMG support : Jean-Jacques Davidian• RF subgroup, Chairman Han van Bussel

PT SMG support : Jean-Jacques Davidian

Drafting subgroups:• SMG7 GPRS: Rapporteur: Arnold Roenbeck• SMG7 CTS: Rapporteur: Sada Dia• SMG7 TTCN: Rapporteur: Shicheng Hu

SMG8

SMG8 Chairman: Simon Pike (Lucent Technologies)PT SMG support: Friedhelm Rodermund

• Signalling subgroup: no fixed Chairman

SMG9

SMG9 Chairman: Klaus Vedder (Giesecke & Devrient)Vice Chairmen: Colin Hamling (Cellnet), Nigel Barnes (Motorola)PT SMG support (including all subgroups): Michael Sanders

Working Parties:• UMTS working party, Chairman Guenter Maringer (T-Mobil)• Testing working party, Chairman Gary Waite (Aspects software)• API working party, Chairman Mark Green (Orange)• SIM Application Toolkit Security, Chairman Nigel Barnes, (Motorola)• Generics, Chairman Rune Lindholm (Nokia).

SMG10

Chairman: Mike Walker (Vodafone)Vice Chairman: David Miles (Cellnet)PT SMG support (technical manager for Security Aspects): Peter van der Arend

Working Parties:• WPA: GSM Security Mechanisms, Chairman Henri Gilbert (France Télécom);• WPB: GSM Services, Chairman Simon Collins (Praesidium); vice-chairman: Tim Wright

(Vodafone)• WPC: UMTS Security, Chairman Colin Blanchard (BT Labs);• WPD: Lawful interception, Chairman Bernie McKibben (Motorola).

The following ad-hoc groups are "active" within SMG10 on an ad-hoc basis to progress the workon a certain work issue:


on Ciphering Indicator (SMG10-BSG) chairman Michael Walker (Vodafone)on Operational Feature Monitoring chairman Rolf Schnitzler (MMO)on CTS chairman Tim Wright (Vodafone)

SMG11

Chairman: Kari Järvinen (Nokia)Vice Chairmen: NN, Paolo Usai (ETSI PT SMG)PT SMG support (including all subgroups): Paolo Usai

Sub-groups:• AMR (Adaptive Multi Rate), Chairman Kari Järvinen (Nokia)• TFO (Tandem Free Operation), Chairman William Navarro (Nortel)• SQ (Speech Quality), Chairman P. Usai (ETSI PT SMG)

SMG12

Chairman: F. Courau (Alcatel)Co-Chairman: T. Järvelä (Nokia)PT SMG: NN, Antun Samukic

WOME

Chairman: Peter Donat, FEEI, AustriaVice Chair: -PT SMG support : Ansgar Bergmann, ETSI PT SMG

Note: For details (co-ordinates), see file smg/document/smg/chairmen.zip onthe FTP server.

ETSI SMG #27Prague,12-16 October 1998

ETSI SMG Tdoc 574/9812 October 1998

Source: ETSI Director General/UGG Chairman

Title: During the meeting held in Tokyo, 7-9 October 1998ARIB, ETSI, T1, TTA and TTC agreed this framework document

Agenda item: 5.7

Document for: DecisionDiscussionInformation X

3GPP-07/10/1998

1 Table of ContentsTable of Contents[to be updated][to be updated]

•• 2- Draft Partnership Project Description2- Draft Partnership Project Description 21- Individual Members (3GPP Overview)21- Individual Members (3GPP Overview)

•• 3- Preamble3- Preamble 22- Individual Members (1)22- Individual Members (1)

•• 4- 3GPP Overview4- 3GPP Overview 23- Individual Members (2)23- Individual Members (2)

•• 5- Definition of 3GPP5- Definition of 3GPP 24- Contributions to ITU (3GPP Overview)24- Contributions to ITU (3GPP Overview)

•• 6- Scope and objectives (1)6- Scope and objectives (1) 25- Submission of 3GPP results to ITU25- Submission of 3GPP results to ITU

•• 7- Scope and objectives (2)7- Scope and objectives (2) 26- Regulators/Governments (3GPP Overview)26- Regulators/Governments (3GPP Overview)

•• 8- Characteristics of 3GPP (1)8- Characteristics of 3GPP (1) 27- National/Regional regulatory requirements27- National/Regional regulatory requirements

•• 9- Characteristics of 3GPP (2)9- Characteristics of 3GPP (2) 28- Financial requirements for establishing 3GPP28- Financial requirements for establishing 3GPP

•• 10- Membership10- Membership 29- Overview showing external interfaces29- Overview showing external interfaces

•• 11- Organizational Partners (3GPP Overview)11- Organizational Partners (3GPP Overview) 30- Internal structure of 3GPP30- Internal structure of 3GPP

•• 12- Organizational Partners (Definition)12- Organizational Partners (Definition) 31- Internal structure of 3GPP showing example31- Internal structure of 3GPP showing example Partners and Members only Partners and Members only

•• 13- Documentation for 3GPP13- Documentation for 3GPP 32- Primary responsibilities of PCGs and TSGs (1)32- Primary responsibilities of PCGs and TSGs (1)

•• 14- The Partnership Project Agreement (1)14- The Partnership Project Agreement (1) 33- Primary responsibilities of PCGs and TSGs (2)33- Primary responsibilities of PCGs and TSGs (2)

•• 15- The Partnership Project Agreement (2)15- The Partnership Project Agreement (2) 34- Primary responsibilities of PCGs and TSGs (3)34- Primary responsibilities of PCGs and TSGs (3)

•• 16- The Partnership Project Description16- The Partnership Project Description 35- Primary responsibilities of PCGs and TSGs (4)35- Primary responsibilities of PCGs and TSGs (4)

•• 17- The Partnership Project Working Procedures17- The Partnership Project Working Procedures 36- Primary responsibilities of PCGs and TSGs (5)36- Primary responsibilities of PCGs and TSGs (5)

•• 18- Ownership of the Partership Project results18- Ownership of the Partership Project results 37- Participation rights in PCGs and TSGs37- Participation rights in PCGs and TSGs

•• 19- Market Representation Partners (3GPP Overview)19- Market Representation Partners (3GPP Overview) 38- Principles for decision making within 3GPP38- Principles for decision making within 3GPP

•• 20- Market Representation Partners (Definition)20- Market Representation Partners (Definition) 39- Working language of 3GPP39- Working language of 3GPP

40- Target Schedule for the creation of 3GPP40- Target Schedule for the creation of 3GPP

41- Work items to be transferred to 3GP41- Work items to be transferred to 3GP

3GPP-07/10/1998

2

DRAFT PARTNERSHIP PROJECT DESCRIPTIONDRAFT PARTNERSHIP PROJECT DESCRIPTION

During the meeting held in Tokyo, 7-9 October 1998ARIB, ETSI, T1, TTA and TTC agreed this

framework document.

[Subject to formal confirmation]

THIRD GENERATION PARTNERSHIP PROJECT (3GPP)THIRD GENERATION PARTNERSHIP PROJECT (3GPP)

3GPP-07/10/1998

3 PreamblePreamble

Standards organizations and other related bodies have agreed to co-Standards organizations and other related bodies have agreed to co-operate for the production of a complete set of globally applicableoperate for the production of a complete set of globally applicableTechnical Specifications for a 3rd Generation Mobile System basedTechnical Specifications for a 3rd Generation Mobile System basedon the evolved GSM core networks and the radio accesson the evolved GSM core networks and the radio accesstechnologies supported by 3GPP partners (i.e., UTRA both FDD andtechnologies supported by 3GPP partners (i.e., UTRA both FDD andTDD modes).TDD modes).

The Project is entitled the “Third Generation Partnership Project”The Project is entitled the “Third Generation Partnership Project”and may be known by the acronym “3GPP”.and may be known by the acronym “3GPP”.

3GPP has been established for the preparation and maintenance of3GPP has been established for the preparation and maintenance ofthe above mentioned Technical Specifications, and is not a legalthe above mentioned Technical Specifications, and is not a legalentity and is non-profit making.entity and is non-profit making.

3GPP-07/10/1998

4 3GPP Overview3GPP Overview

Project Co-ordination Group

Technical Specification Groups

Support Functions

3GPP

TechnicalSpecifications

3GPP-07/10/1998

5 Definition of the Third Generation Partnership Project

3GPP will provide globally applicable TechnicalSpecifications for a 3rd Generation Mobile Systembased on the evolved GSM core network, and theUniversal Terrestrial Radio Access (UTRA), to betransposed by relevant standardization bodies(Organizational Partners) into appropriatedeliverables (e.g., standards).

3GPP-07/10/1998

6 Scope and objectives (1)Scope and objectives (1)

The Technical Specifications will be developed in view of global roamingThe Technical Specifications will be developed in view of global roamingand circulation of terminals.and circulation of terminals.

The 3rd Generation Mobile System and its capabilities will be developed The 3rd Generation Mobile System and its capabilities will be developedin a phased approach. Initially, 3GPP will elaborate, approve andin a phased approach. Initially, 3GPP will elaborate, approve andmaintain the necessary set of Technical Specifications for the first phasemaintain the necessary set of Technical Specifications for the first phaseof a 3rd Generation Mobile System including:of a 3rd Generation Mobile System including:

•• UTRAN (including UTRA; W-CDMA in Frequency Division UTRAN (including UTRA; W-CDMA in Frequency Division Duplex (FDD) mode and TD-CDMA in Time Division Duplex Duplex (FDD) mode and TD-CDMA in Time Division Duplex (TDD) mode) (TDD) mode)

•• 3GPP Core Network (Third Generation networking capabilities 3GPP Core Network (Third Generation networking capabilities evolved from GSM . These capabilities include mobility management evolved from GSM . These capabilities include mobility management and global roaming.) and global roaming.)

•• Terminals for access to the above (including specifications for a UIM) Terminals for access to the above (including specifications for a UIM)

•• System and service aspects System and service aspects

3GPP-07/10/1998

7 Scope and objectives (2)Scope and objectives (2)

The set of global specifications for the first phase of theThe set of global specifications for the first phase of the3GPP core network and the specifications for the GSM3GPP core network and the specifications for the GSMcore network should be common to the largest extentcore network should be common to the largest extentpossible and should not be needlessly different.possible and should not be needlessly different.

The results of the 3GPP work will form the basis ofThe results of the 3GPP work will form the basis ofmember contributions to the ITU in accordance withmember contributions to the ITU in accordance withexisting procedures.existing procedures.

3GPP will take account of emerging ITU recommendations3GPP will take account of emerging ITU recommendationson interworking between IMT-2000 family members.on interworking between IMT-2000 family members.

In the framework of agreed relationships, 3GPP willIn the framework of agreed relationships, 3GPP willelaborate Technical Specifications that will form the basiselaborate Technical Specifications that will form the basisof standards, or parts of standards, of the Organizationalof standards, or parts of standards, of the OrganizationalPartners.Partners.

3GPP-07/10/1998

8 Characteristics of 3GPP (1)

•• Minimum production time for TechnicalMinimum production time for TechnicalSpecifications from conception to approvalSpecifications from conception to approval

•• Fast, electronic based approval processFast, electronic based approval process

•• Maximum use of modern (electronic) workingMaximum use of modern (electronic) workingmethodsmethods

•• Minimum number of hierarchical levels withMinimum number of hierarchical levels withdecision making taking place at the lowestdecision making taking place at the lowestappropriate levelsappropriate levels

3GPP is characterized by the following attributes:3GPP is characterized by the following attributes:

3GPP-07/10/1998

9 Characteristics of 3GPP (2)

• A Project Co-ordination function and aTechnical Specification function

• Task oriented, ensuring that on completion ofthe tasks the future of the project is re-evaluated

• Cost effective use of financial/humanresources provided by Partner Organizations(if required)

3GPP-07/10/1998

10 MembershipMembership

3GPP is open for membership to all standardsorganizations irrespective of the geographicallocation.

Membership is categorized as follows:

• A Partner:

– Organizational Partner

– Market Representation Partner

• An Individual Member

3GPP-07/10/1998

11 Organizational PartnersOrganizational Partners



Support Functions

3GPP


PARTNERS

OrganizationalPartners

Partners’ Standardization Process

Partner deliverables

3GPP-07/10/1998

12 Organizational PartnersOrganizational Partners

An Organizational Partner is:

An open standards organization with a national,regional or other officially recognized status(in their country or region)

that:

• has the capability and authority to define, publish and set standards nationally or regionally and

• has signed (or whose sponsor has signed) the Partnership Project Agreement

Organizational Partners will meet as approriate andmake decisions by consensus

3GPP-07/10/1998

13 Documentation for 3GPPDocumentation for 3GPP

•• The Partnership Project AgreementThe Partnership Project Agreement

•• The Partnership Project DescriptionThe Partnership Project Description(this present document)(this present document)

•• The Partnership Project Working ProceduresThe Partnership Project Working Procedures

Drafts of Drafts of these three documents will be prepared by athese three documents will be prepared by aworking group comprising of representatives from theworking group comprising of representatives from thepotential partners.potential partners.

The following 3 documents are required for 3GPP to beThe following 3 documents are required for 3GPP to becreated:created:

3GPP-07/10/1998

14 The Partnership Project Agreement (1)The Partnership Project Agreement (1)

The Partnership Project Agreement is a conciseThe Partnership Project Agreement is a conciselegal document signed by participating Partners (orlegal document signed by participating Partners (ortheir sponsor).their sponsor).

It contains the minimum legal text necessary forIt contains the minimum legal text necessary for3GPP to function correctly.3GPP to function correctly.

The Partnership Project Agreement refers to theThe Partnership Project Agreement refers to thePartnership Project Description and the PartnershipPartnership Project Description and the PartnershipProject Working Procedures.Project Working Procedures.

3GPP-07/10/1998

15 The Partnership Project Agreement (2)The Partnership Project Agreement (2)

•• to encourage their members to contribute to the commonto encourage their members to contribute to the commonset of Technical Specifications and to avoid duplicationset of Technical Specifications and to avoid duplicationof workof work

•• to convert / transpose / to convert / transpose / adopt all relevantadopt all relevant Technical TechnicalSpecifications resulting from 3GPP into their ownSpecifications resulting from 3GPP into their ownrelevant deliverables through their normal processesrelevant deliverables through their normal processes

•• to identify as early as possible, any national / regionalto identify as early as possible, any national / regionalregulatory requirements that may lead to options withinregulatory requirements that may lead to options withinthe Technical Specificationsthe Technical Specifications

•• to make their IPR Policy available for considerationto make their IPR Policy available for consideration

The Partnership Project Agreement includes obligationsThe Partnership Project Agreement includes obligationson Partners to commit themselves to the 3GPP scope:on Partners to commit themselves to the 3GPP scope:

3GPP-07/10/1998

16 [The Partnership Project Description][The Partnership Project Description]

[The Partnership Project Description[The Partnership Project Description(this present document) is a development of the(this present document) is a development of theposition agreed in Tokyo and modified by theposition agreed in Tokyo and modified by theresults of the meeting in London.results of the meeting in London.

It will be enhanced during future meetings.]It will be enhanced during future meetings.]

[This slide will be deleted later][This slide will be deleted later]

3GPP-07/10/1998

17 The Partnership Project Working ProceduresThe Partnership Project Working Procedures

The draft The draft Partnership Project WorkingPartnership Project WorkingProcedures will be elaborated by a workingProcedures will be elaborated by a workinggroup comprising of representatives from thegroup comprising of representatives from thepotential partners.potential partners.

The ETSI Technical Working Procedures will beThe ETSI Technical Working Procedures will beused as a starting point for this work.used as a starting point for this work.

3GPP-07/10/1998

18 Ownership of the Partnership Project resultsOwnership of the Partnership Project results

The Organizational Partners of 3GPP will have jointThe Organizational Partners of 3GPP will have jointownership (including copyright) of the Technicalownership (including copyright) of the TechnicalSpecifications.Specifications.

3GPP-07/10/1998

19 Market Representation PartnersMarket Representation Partners



Support Functions

3GPP


PARTNERS



MarketRepresentationPartners


3GPP-07/10/1998

20 Market Representation PartnersMarket Representation Partners

Standardization should meet market needs.Standardization should meet market needs.

In order to identify market requirements, the high competence of MarketIn order to identify market requirements, the high competence of MarketRepresentation Partners should be used.Representation Partners should be used.

A Market Representation Partner is an organization invited to participate by theA Market Representation Partner is an organization invited to participate by theOrganizational Partners to offer market oriented advice to 3GPP and to bring intoOrganizational Partners to offer market oriented advice to 3GPP and to bring into3GPP aggregated market requirements falling within the 3GPP scope.3GPP aggregated market requirements falling within the 3GPP scope.

A Market Representation Partner:A Market Representation Partner:

•• does not have the capability and authority to define, publish and set standards does not have the capability and authority to define, publish and set standards nationally or regionally nationally or regionally

•• has signed (or whose sponsor has signed) the Partnership Project Agreement has signed (or whose sponsor has signed) the Partnership Project Agreement

•• has committed itself to the 3GPP scope has committed itself to the 3GPP scope

Potential Market Representation Partners are:Potential Market Representation Partners are:

•• UMTS Forum UMTS Forum

•• GSM MoU Association (including all regional interest groups) GSM MoU Association (including all regional interest groups)

•• GSM Alliance GSM Alliance

3GPP-07/10/1998

21 Individual MembersIndividual Members



Support Functions

3GPP


PARTNERS




INDIVIDUAL MEMBERS

TechnicalContributions


3GPP-07/10/1998

22 Individual Members (1)Individual Members (1)

Membership in an Organizational Partner is a pre-Membership in an Organizational Partner is a pre-requisite for Individual Membership.requisite for Individual Membership.

Individual Membership is open to legal entitiesIndividual Membership is open to legal entitiescommitted to:committed to:

•• contribute technically or otherwise to one or more of contribute technically or otherwise to one or more ofthe Technical Specification Groups within the 3GPPthe Technical Specification Groups within the 3GPPscopescope

•• use the use the 3GPP results to the extent feasible3GPP results to the extent feasible

•• support the Terms of Reference of 3GPP to which their support the Terms of Reference of 3GPP to which their Organizational Partner is committed. Organizational Partner is committed.

Individual Membership in 3GPP will be terminated byIndividual Membership in 3GPP will be terminated bydissolution, abolition, resignation or expulsion from thedissolution, abolition, resignation or expulsion from therelated Organizational Partner.related Organizational Partner.

3GPP-07/10/1998

23 Individual Members (2)Individual Members (2)

Working assumption:Working assumption:

All entities registered as members of an OrganizationalAll entities registered as members of an OrganizationalPartner and eligible for participation in the technical workPartner and eligible for participation in the technical workof that Partner, can become Individual of that Partner, can become Individual Members of 3GPP.Members of 3GPP.Individual members shall apply to their OrganizationalIndividual members shall apply to their OrganizationalPartner to participate in 3GPP.Partner to participate in 3GPP.

Individual Members act in the 3GPP in their own right;Individual Members act in the 3GPP in their own right;they carry the full responsibility for their contributions.they carry the full responsibility for their contributions.

Individual Membership applicants residing in a country/areaIndividual Membership applicants residing in a country/areawithout an Organizational Partner can apply forwithout an Organizational Partner can apply formembership in an Organizational Partner according to themembership in an Organizational Partner according to therules of each Partner.rules of each Partner.(e.g. ETSI Associate Membership is available)(e.g. ETSI Associate Membership is available)

3GPP-07/10/1998

24 Contributions to ITUContributions to ITU



Support Functions

3GPP


PARTNERS




INDIVIDUAL MEMBERS


ITU

InternationalRecommendations


IMT 2000contributionsvia existingprocesses

3GPP-07/10/1998

25 Submission of 3GPP results to ITUSubmission of 3GPP results to ITU

3GPP will not contribute directly to the ITU but will3GPP will not contribute directly to the ITU but willfollow existing national/regional processes.follow existing national/regional processes.

3GPP results should be submitted to the ITU as3GPP results should be submitted to the ITU asappropriate.appropriate.

Formal contributions to ITU Study Groups are madeFormal contributions to ITU Study Groups are madeby ITU members.by ITU members.

3GPP-07/10/1998

26 Regulators / GovernmentsRegulators / Governments



Support Functions

3GPP


PARTNERS




INDIVIDUAL MEMBERS


ITU


Regulators /Governments

Manda tes


IMT 2000Contributionsvia existingprocesses

3GPP-07/10/1998

27 National / regional regulatory requirementsNational / regional regulatory requirements

All regulatory national / regional variations willAll regulatory national / regional variations willbe included in the Technical Specifications asbe included in the Technical Specifications asdefined by the Technical Specification Groupsdefined by the Technical Specification Groupsand may be options included in the Technicaland may be options included in the TechnicalSpecifications.Specifications.

3GPP-07/10/1998

28 Resource requirements for establishing 3GPPResource requirements for establishing 3GPP

Working assumption:Working assumption:

ETSI will absorb the initial cost of establishingETSI will absorb the initial cost of establishingthe 3GPP, if required.the 3GPP, if required.

Thereafter, the costs will be shared by theThereafter, the costs will be shared by theOrganizational Partners. There will be no directOrganizational Partners. There will be no direct3GPP membership fee for Individual Members.3GPP membership fee for Individual Members.

Partners and Individual Members may providePartners and Individual Members may providesupport functions to the extent that they are ablesupport functions to the extent that they are able(eg hosting of meetings and provision of(eg hosting of meetings and provision ofSecretariat support).Secretariat support).

The longer term financial requirements forThe longer term financial requirements forPartners are for further study.Partners are for further study.

3GPP-07/10/1998

29 Overview showing external interfacesOverview showing external interfaces



Support Functions

PARTNERS



3GPPRegulators /Governments

ITU


Mandates



INDIVIDUAL MEMBERS



IMT 2000Contributionsvia existingprocesses

3GPP-07/10/1998

30 Internal structure of 3GPPInternal structure of 3GPP

3GPP consists of a Project Co-ordination Group3GPP consists of a Project Co-ordination Group(PCG) and Technical Specification Groups(PCG) and Technical Specification Groups(TSGs).(TSGs).

To assist in the co-ordination of the technicalTo assist in the co-ordination of the technicalactivities, the TSGs are encouraged to meet atactivities, the TSGs are encouraged to meet atthe same time and place, as and whenthe same time and place, as and whenappropriate.appropriate.

3GPP-07/10/1998

31

TSG TSG TSG

Terminals

3GPP

Internal structure of 3GPPInternal structure of 3GPP

TSG


Radio Access Network

Core Network

SystemAspects

Technical Specifications

3GPP-07/10/1998

32

Work areas to be covered by the Radio Access Network TSGWork areas to be covered by the Radio Access Network TSG

• Layer 1 on MT-RAN Interface

• Layer 2 on MT-RAN Interface

• Layer 3 (RR) on MT-RAN Interface

• Iu Interface

• Iur Interface

3GPP-07/10/1998

33Work areas to be covered by the Core Network TSGWork areas to be covered by the Core Network TSG

• Layer 3 (CC) on MT-RAN Interface

• Layer 3 (MM) on MT-RAN Interface

• Network Interface (Call Associated Signalling)

• Network Interface (Non-Call Associated Signalling)

• PSTN/ISDN/Internet/etc. Interconnection

3GPP-07/10/1998

34 Work areas to be covered by the Terminal TSGWork areas to be covered by the Terminal TSG

• MS Radio Performance Specifications

• UIM-MT Interface

3GPP-07/10/1998

35Work areas to be covered by the System Aspects TSGWork areas to be covered by the System Aspects TSG

• Fixed Wireless Access (Wireless Local Loop)

• Security Aspects (implementation and usage)

• CODEC (final placement to be determined by subjectmatter experts)

• Overview

• Requirements and Objectives for Services andSystems, including charging and accountingmechanisms with respect to roaming aspects

• System Architecture

• Information Flows

3GPP-07/10/1998

36 Work areas for further studyWork areas for further study

• Conformance Testing for Mobile Stations

• MS-Adapter Interface (Excessive standardizationmay limit innovation)

• Iub Interface

3GPP-07/10/1998

37 Primary responsibilities of PCG and TSGs (1)Primary responsibilities of PCG and TSGs (1)

The primary responsibilities of PCG, TSGs andOrganizational Partners are given in the followingtables:

Function OrgPartnersm eeting

PCG TSGs

1 Approval of new Partners for3GPP

X

2 Approval of OrganizationalPartner funding requirem entsand contributions

X

3 Allocation of hum an andfinancial resources providedby Partners to PCG

X

3a Allocation of resources toTSGs

X

3b Allocation of resources w ith inTSGs

X

3GPP-07/10/1998


Function OrgPartnersmeeting

PCG TSGs

4 Allocation of voluntaryhuman and financialresources by MarketRepresentation Partners andIndividual Members

X X

5 Handling of appeals fromIndividual Members onprocedural matters

2nd

step1st

step

6 Handling of appeals fromindividual members ontechnical matters

2nd

step1st

step

7 Determine overall time frameand manage overall workprogress

X

3GPP-07/10/1998

39

Function OrgPartnerm eeting

PCG TSGs

7a Detailed tim e fram e andm anage detailed w orkprogress

X

8 Approval of TechnicalSpecifications

X

9 Proposal of w ork item sw ith in the agreed scope andterm s of reference

X

10 Approval of w ork item sw ith in the agreed scope andterm s of reference

X

11 M anagem ent of w ork item s X

Primary responsibilities of PCG and TSGs (3)Primary responsibilities of PCG and TSGs (3)

3GPP-07/10/1998


Fu nction O rgP artnersm eeting

P C G TS G s

12 Techn ica l C o-o rd ina tion(System Aspec ts TSG w illp lay a ro le here)

X

13 Appo in tm en t o f O rg P artnersm eeting C ha irm an (p rovidedby hos t on a ro ta tiona l bas is ) X

13a Appo in tm en t o f PC GC hairm an (fo r one yea r te rm ) X

14 E lection o f TSG C hairm anand V ice C hairm en

X

14a C reation o f TSG s andapprova l o f the ir term s o fre fe rence

X

3GPP-07/10/1998

41

Function OrgPartnersmeeting

PCG TSGs

15 Creation of TSG workinggroups and approval of theirterms of reference

X

16 Election of TSG WorkingGroup Chairmen and ViceChairmen

X

17 Confirmation of individualmember participation rights

X

18 Approval of 3GPP scope andterms of reference

X

19 Maintain Partnership ProjectAgreement, ProjectDescription and W orkingProcedures

X

Primary responsibilities of PCG and TSGs (5)Primary responsibilities of PCG and TSGs (5)

3GPP-07/10/1998

42 Participation rights in PCG and TSGsParticipation rights in PCG and TSGs

The following have a right to participate in the PCG:The following have a right to participate in the PCG:

•• Representatives of participating Organizational Partners, with the right Representatives of participating Organizational Partners, with the right to take part in the decision making process. to take part in the decision making process.

•• Representatives of participating Market Representation Partners, Representatives of participating Market Representation Partners, with the right to speak, submit contributions, but not to take part in the with the right to speak, submit contributions, but not to take part in the decision making process. decision making process.

•• Chairman and Vice Chairmen of the TSGs, as ex-officio members with Chairman and Vice Chairmen of the TSGs, as ex-officio members with the right to speak, submit contributions, but not to take part in the the right to speak, submit contributions, but not to take part in the decision making process. decision making process.

The following have a right to participate in the TSGsThe following have a right to participate in the TSGs : :

•• Representatives of members of participating Organizational Representatives of members of participating Organizational Partners (i.e. Individual Members) Partners (i.e. Individual Members) with the right to take part in thewith the right to take part in the decision making process. decision making process.

•• Representatives of participating Organizational and Market Representatives of participating Organizational and Market Representation Partners with the right to speak and submit Representation Partners with the right to speak and submit documents but not to take part in the decision making process. documents but not to take part in the decision making process.

3GPP-07/10/1998

43 Principles for decision making within 3GPPPrinciples for decision making within 3GPP

Decision making within PCGsDecision making within PCGs

•• By consensus By consensus

Decision making within TSGsDecision making within TSGs

•• By consensus By consensus

•• By vote in unavoidable cases By vote in unavoidable cases (details to be further elaborated) (details to be further elaborated)

(Note: voting will not be permitted on National/Regional options)(Note: voting will not be permitted on National/Regional options)

3GPP-07/10/1998

44 Principles for voting within TSGsPrinciples for voting within TSGs

The following principles will be applied for voting within the TSGsThe following principles will be applied for voting within the TSGs

•• One “Individual company Member”, one voteOne “Individual company Member”, one vote

•• Organizational Partners to interpret “ Individual companyOrganizational Partners to interpret “ Individual companyMember” according to its own rules of membershipMember” according to its own rules of membership

•• The PCG will maintain a register of eligible voters for the TSGsThe PCG will maintain a register of eligible voters for the TSGs

•• Each Individual Member may carry the proxy for up to five otherEach Individual Member may carry the proxy for up to five otherIndividual MembersIndividual Members

•• The Organizational Partners will conduct a fairness review ofThe Organizational Partners will conduct a fairness review ofthe voting system six months after 3GPP start-upthe voting system six months after 3GPP start-up

[Note: approved subject to confirmation by 6 November][Note: approved subject to confirmation by 6 November]

3GPP-07/10/1998

45 Working language for 3GPPWorking language for 3GPP

The working language for 3GPP shall be EnglishThe working language for 3GPP shall be English

•• Meetings of the PCGs and TSGs shall beMeetings of the PCGs and TSGs shall beconducted in Englishconducted in English

•• 3GPP technical specifications shall be3GPP technical specifications shall beprepared in Englishprepared in English

3GPP-07/10/1998

46Relationship with other groupsRelationship with other groups

3GPP will establish and maintain good relationships 3GPP will establish and maintain good relationshipswith groups working on standards for otherwith groups working on standards for otherIMT-2000 family members.IMT-2000 family members.

3GPP-07/10/1998

47 Intellectual Property Rights (1)Intellectual Property Rights (1)

The Individual Members of 3GPP are bound by the IPR The Individual Members of 3GPP are bound by the IPRPolicies of their respective Organizational Partner.Policies of their respective Organizational Partner.

Individual members will be encouraged to declare atIndividual members will be encouraged to declare atthe earliest opportunity, any IPRs which they believethe earliest opportunity, any IPRs which they believeto be essential, or potentially essential, to any workto be essential, or potentially essential, to any workongoing within 3GPP .ongoing within 3GPP .

After comparing their respective IPR policies, ARIB,After comparing their respective IPR policies, ARIB,ETSI, T1, TTA and TTC have agreed that their IPRETSI, T1, TTA and TTC have agreed that their IPRpolicies are quite similar and have agreed on thepolicies are quite similar and have agreed on thefollowing:following:

3GPP-07/10/1998

48 Intellectual Property Rights (2)Intellectual Property Rights (2)

(i) to encourage their respective members to grant to encourage their respective members to grant licences on fair, reasonable terms and conditions licences on fair, reasonable terms and conditions on a non-discriminatory basis.on a non-discriminatory basis.

(ii) to note the necessity of early assurance that the to note the necessity of early assurance that the 3GPP technical specifications should not be3GPP technical specifications should not be

blocked by refusal of owners of essential IPRs to blocked by refusal of owners of essential IPRs to grant licences. grant licences.

(iii) to understand that essential IPRs mean essential to understand that essential IPRs mean essential IPRs relative to any or all parts of the content of IPRs relative to any or all parts of the content of the 3GPP technical specifications.the 3GPP technical specifications.

[Note: approved subject to confirmation by 6 November][Note: approved subject to confirmation by 6 November]

3GPP-07/10/1998

49 Target Schedule for the creation of 3GPPTarget Schedule for the creation of 3GPP

(22-23 October Approval of 3GPP by T1)(19 November Approval of 3GPP by ETSI GA)(26 November Approval of 3GPP by ARIB)

30 November Determine technical framework and work programme

2- 4 December Approve Project documentation, Create PCG, Create TSGs and elect Chairmen (ARIB/ETSI/T1/TTA/TTC meeting in Copenhagen)

7-11 Dec Technical work begins

(Note: it may be possible for this schedule to be accelerated and fortechnical work to start pending approval by the Partners)