1 / 29

What is GAIT?

What is GAIT?. GAIT stands for G SM/ A NSI-136 (TDMA) I nteroperability T eam. GSM/ANSI-136. GAIT. Setting the pace of Global Wireless Communications. Interoperability Team. GSM/TDMA Interoperability. Penny Bright Lucent Technologies +1 630-713-7531 plbright@lucent.com.

nalani
Download Presentation

What is GAIT?

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

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

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

  3. Introduction • GAIT Formation: structure, background, deliverables • Drivers for GAIT (e.g. Roaming) • Requirements and Timeline • Interoperability Elements • Mobile Station / SIM Capabilities • Network IIF Capabilities • Example message flows • Issues on NW and Handset-side

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

  5. GAIT Background • GSM/ANSI-136 Interoperability Team (GAIT) formed in February - March 1999 to address deliverables from the GSM Alliance/UWCC • Scope and Charter: • Develop 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 • Work with other industry bodies and the appropriate standards bodies to standardize the GSM/ANSI-136 interoperability service

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

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

  8. Roaming IIF = Interworking/Interoperability Function

  9. Key GAIT Interoperability Requirements • Multi-mode (GSM/TDMA) mobile station • International & cross-technology (GSM/ANSI-136) roaming • Subscriber Information Module (SIM) portability • Automatic registration, authentication & call delivery • Short Message Service • Over-the-air activation and programming • Flexible network selection definable by each Network Operator

  10. Key GAIT Interoperability Requirements (continued) • Message Waiting Notification • Supplementary service (feature) transparency • Call Forwarding • Call Waiting • Call Barring • CLIP/CLIR • 3WAY (Multiparty) Calling • Optimal routing for Late Call Forwarding

  11. Postponed GAIT Requirements • Packet and circuit-mode data calls NOT addressed by GAIT in Phase 1 • Handoffs between different technologies NOT addressed by GAIT in Phase 1 • ANSI-41 WIN and GSM CAMEL services NOT addressed by GAIT in Phase 1

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

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

  14. Handset and SIM Card Highlights Handset (Mobile Equipment) • 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. SIM Card • Contains subscription information such as: • IMSI and MIN • ANSI-136 security parameters (e.g. A-key) • GSM security parameters (e.g. Ki) • ANSI-136 NAM • Contains SIM ESN • Supports feature code table • Can be provisioned over-the-air • Supports network selection database SIM

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

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

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

  18. IIF Highlights (Interworking and Interoperability Function)

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

  20. Key Network Issues: • Not all ANSI Networks support the same Feature Codes to invoke/activate supplementary services -- ANSI 660 codes shall be used. • To 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). • International roaming needs GTT and ANSI-136 IMSI implementation for full support.

  21. Key NW Issues (more detail) • ANSI-136 IMSI & Global Title Translation (GTT) • Arose from the goal that, when IMSI is used on ANSI-136 side, that it be the same as IMSI used in GSM • Issue 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 • Resolution: Use different GTT “translation types” for GSM and ANSI-136 sides

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

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

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

  25. Other IIF Issues • IIF location-related issues • Serving-system not always located in same country as IIF • IIF needs to provide to HLR its own address when emulating “foreign” serving VLRs/MSCs. • 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. Other IIF Issues (page 2) • MAP translatability-related issues • Authentication and Encryption • 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 • Outgoing Call Barring • ANSI-41 outgoing call restrictions not completely equivalent to GSM MAP outgoing call barring capabilities. • Call Forwarding Busy • Current GSM MAP versions do not support “busy” indication in call delivery signaling • CLIP • NW Implementation of GSM MAP release ‘98 is needed inclusion of calling party number information during call delivery

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

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

  29. Summary • GAIT Formation: structure, charter, deliverables • Drivers for GAIT (e.g. Roaming) • Requirements and Timeline • Interoperability Elements • MS/ SIM Capabilities • IIF Capabilities • Example message flows • Issues

More Related