1. 1 What is GAIT? GAIT stands for GSM/ ANSI-136 (TDMA) Interoperability Team

2. 2 Penny Bright Lucent Technologies +1 630-713-7531 plbright@lucent.com GSM/TDMA Interoperability Setting the pace of Global Wireless Communications.

3. 3Introduction nGAIT Formation: structure, background, deliverables nDrivers for GAIT (e.g. Roaming) nRequirements and Timeline nInteroperability Elements nMobile Station / SIM Capabilities nNetwork IIF Capabilities nExample message flows nIssues on NW and Handset-side

4. 4 GAIT reports to both the UWCC and the GSM Alliance GAIT Organization

5. 5 GAIT Background nGSM/ANSI-136 Interoperability Team (GAIT) formed in February - March 1999 to address deliverables from the GSM Alliance/UWCC nScope and Charter: uDevelop mobile station (including Subscriber Identity Module) and network functional requirements and specifications for the interoperability and interworking of GSM and ANSI-136 based cellular/PCS systems uWork with other industry bodies and the appropriate standards bodies to standardize the GSM/ANSI-136 interoperability service

6. 6 GAIT Deliverables nNetwork Spec. primarily addresses the GSM/ANSI-41 Interworking/Interoperability Function (IIF) uas well as others: e.g. SMSC and ANSI-41 HLR nCommon Mobile Terminal Specification addresses the GSM/ANSI-136/AMPS Multi-Mode Mobile and SIM nTest Plan Spec. In Progress -- needs stage 3 detail nDetailed specification and standardization required to meet July 2000 targeted general availability 4 Specifications will be frozen in November 1999 4 Network Spec. Submission to T1P1 in Nov. ‘99 4 Some portions of the detailed handset specifications have been submitted to TR-45.3  (for GHOST and SIM files and procedures)

7. 7 GSM/ANSI-136 Interoperability: Key Drivers nSupport for international roamers uGSM and/or ANSI-136 coverage exists in every developed city in the world u290 million GSM and ANSI-136 subscribers worldwide nSupport for GSM subscribers in regions that are otherwise predominately ANSI-136 nSupport for ANSI-136 subscribers in regions that are otherwise predominately GSM nSeamless Service (features and user interface)

8. 8 IIF = Interworking/Interoperability Function Roaming

9. 9 Key GAIT Interoperability Requirements nMulti-mode (GSM/TDMA) mobile station nInternational & cross-technology (GSM/ANSI-136) roaming nSubscriber Information Module (SIM) portability nAutomatic registration, authentication & call delivery nShort Message Service nOver-the-air activation and programming nFlexible network selection definable by each Network Operator

10. 10 Key GAIT Interoperability Requirements (continued) nMessage Waiting Notification nSupplementary service (feature) transparency uCall Forwarding uCall Waiting uCall Barring uCLIP/CLIR u3WAY (Multiparty) Calling nOptimal routing for Late Call Forwarding

11. 11 Postponed GAIT Requirements nPacket and circuit-mode data calls NOT addressed by GAIT in Phase 1 nHandoffs between different technologies NOT addressed by GAIT in Phase 1 nANSI-41 WIN and GSM CAMEL services NOT addressed by GAIT in Phase 1

12. 12 Requirements Generated by GAIT Definition Phase Test Capability Developed by GAIT Vendors Develop Products Design Phase Potential Joint Testing Based on GAIT-Developed Test Specification Test Phase LAUNCH 3/999/997/002/00 GAIT Tasks and Timeline

13. 13 Elements of Interoperability MSC/ VLR HLR Interworking and Interoperability Function Handset & SIM Card GSM Subscriber GSMANSI-136

14. 14 Handset and SIM Card Highlights Supports both ANSI-136 & GSM air protocols Contains ANSI-136 ESN Interacts with application in SIM card for support of call control, user interface, authentication, etc. Contains subscription information such as: IMSI and MIN ANSI-136 security parameters (e.g. A-key) GSM security parameters (e.g. K i ) ANSI-136 NAM Contains SIM ESN Supports feature code table Can be provisioned over-the-air Supports network selection database Handset (Mobile Equipment) SIM Card

15. 15 Key Mobile Station Capabilities nSIM-based roaming in all modes uGAIT SIM portable between GAIT MSs 4 for both GSM and ANSI-136 service uGAIT SIM portable to GSM MS 4 for GSM mode only uGAIT SIM portable to Dual Mode Roaming (DMR) MS 4 for GSM and AMPS only uDMR SIM portable to any GAIT MS 4 for GSM and AMPS only uGSM SIM portable to GAIT MS 4 for GSM mode only  Requires in-bound roamers from GSM to ANSI-136 to have GAIT SIM to operate in ANSI-136 mode

16. 16 Key Mobile Station Capabilities (page 2) nSeamless Supplementary Services achieved via menu-driven approach uMenu selections mapped to ANSI-136 digit strings (e.g. feature codes) for feature control. uMenu selections mapped to GSM supplementary service operations. nOver-the-Air SIM programming in all modes uGSM SMS used in GSM mode uGSM Hosted SMS Teleservice (GHOST) defined for use in ANSI-136 4 GHOST may furthermore be used to deliver text based messaging, message waiting notification, and WAP in ANSI-136 mode

17. 17 Mobile Station Capabilities ( page 3 - more detail) nGSM Hosted SMS Teleservice (GHOST) for Tele- services in ANSI-136 networks uIn GSM networks, SMS is used in support of various functions, including 4 Over-the-air provisioning of the SIM 4 Message Waiting Notification 4 Text messaging uTo reduce complexity of the Mobile Station, GAIT defined a mechanism (GHOST) to transport GSM SMS messages over ANSI-136 networks 4 GHOST supports same functions (such as the ones listed above) as GSM SMS 4 GHOST does not impact MSCs in ANSI-136 networks

18. 18 IIF Highlights (Interworking and Interoperability Function)

19. 19 Key Network IIF Capabilities (page 3) nIn Phase 1, Provides Interworking Capabilities between existing GSM and ANSI-41 MAP protocols. nInteroperates between various GSM/ANSI-136 network elements i.e. HLR, VLR, MSC, and SMSC’s. nSupports GSM and ANSI-136 authentication functions while subscriber is roaming in a “foreign- technology” network. nSMS mapping between GSM/ANSI-136 protocols -- GHOST origination for ANSI-136 SMS delivery nSupport for Optimal Routing for Conditional CF. nTransparent supplementary service control is provided with mobile station and IIF translations in GSM and ANSI-136 foreign modes

20. 20 Key Network Issues: nNot all ANSI Networks support the same Feature Codes to invoke/activate supplementary services -- ANSI 660 codes shall be used. nTo support SIM portability between MSs (with different ESNs), new ANSI-136 authentication procedures need to be implemented in existing TDMA networks (because currently ANSI-136 auth. links the subscriber identity (on SIM) to the MS). nInternational roaming needs GTT and ANSI-136 IMSI implementation for full support.

21. 21 Key NW Issues (more detail) nANSI-136 IMSI & Global Title Translation (GTT) uArose from the goal that, when IMSI is used on ANSI- 136 side, that it be the same as IMSI used in GSM uIssue summary: Some GSM and ANSI-136 networks may share same SS7 network. When subscriber is in native mode, need GTT in SS7 network to translate IMSI to HLR’s address. However, when in foreign mode, need GTT in same SS7 network to translate the same IMSI to the IIF’s address uResolution: Use different GTT “translation types” for GSM and ANSI-136 sides

22. 22 IIF MAP Interworking Example: Registration MSC/ VLR GSM MSC/ VLR HLR 2. AUTH REQ 4. REGNOT 5. UPDATE LOC 9. insert sub data 1. Registration 6. CANCEL LOC 7. cancel loc 8. INSERT SUB DATA 10. update loc 3. auth req 11. regnot 12. Reg Accept ANSI-136 GSM Subscriber

23. 23 IIF Example 2: Call Delivery MSC/ VLR GSM MSC/ VLR HLR 5. routreq (TLDN) 6. prn (MSRN) 7. sri (MSRN) 2. SRI 3. PRN 4. ROUTREQ ANSI-136 9. Page 1. Incoming Call 8. Call Setup (MSRN) SRI: Send Routing Information PRN: Provide Roaming Number TLDN: Temporary Local DN MSRN: MS Roaming Number GSM Subscriber

24. 24 IIF Example 3: MT-SMS MC GSM MSC/ VLR HLR 8. smdpp 7. forward short message 4. FORWARD SHORT MESSAGE 3. SMDPP ANSI-136 ANSI-136 Subscriber 6. SMS Delivery Ack 1. SMSREQ 2. smsreq 5. SMS Delivery

25. 25 Other IIF Issues nIIF location-related issues uServing-system not always located in same country as IIF 4 IIF needs to provide to HLR its own address when emulating “foreign” serving VLRs/MSCs. 4 For some Incoming Call Barring and CF number registration cases, the GSM HLR needs actual country code information from received serving VLR/MSC addresses to properly perform procedures.

26. 26 Other IIF Issues (page 2) nMAP translatability-related issues uAuthentication and Encryption 4 GSM and ANSI-136 authentication/encryption procedures too different to allow simple “protocol translation” by IIF. Instead, IIF itself will provide the full authentication/ encryption functionality (either GSM or ANSI-41) for subscribers roaming in a foreign-technology network uOutgoing Call Barring 4 ANSI-41 outgoing call restrictions not completely equivalent to GSM MAP outgoing call barring capabilities. uCall Forwarding Busy 4 Current GSM MAP versions do not support “busy” indication in call delivery signaling uCLIP 4 NW Implementation of GSM MAP release ‘98 is needed inclusion of calling party number information during call delivery

27. 27 Other Mobile Station Issues nANSI-136 Parameters in SIM uETSI SIM standards already support some AMPS- related parameters (e.g. MIN) uETSI SIM standards to be extended to support additional parameters needed by GAIT

28. 28 Other Mobile Station Issues nFeature transparency (almost) achieved via menu- driven approach uComplete feature transparency not possible because of differences in capabilities between GSM and ANSI- 136 networks. Examples: 4 3WAY, Multiparty (GSM networks can support more than three parties in multi-party call) 4 Call Waiting (ANSI-136 networks cannot release active call & respond to CW call simultaneously)

29. 29Summary nGAIT Formation: structure, charter, deliverables nDrivers for GAIT (e.g. Roaming) nRequirements and Timeline nInteroperability Elements nMS/ SIM Capabilities nIIF Capabilities nExample message flows nIssues