1 / 27

CDG International Roaming Team Inter-CRX Task Force

CDG International Roaming Team Inter-CRX Task Force. Last updated: 03/01/2005. Background. The CDMA Roaming Exchange Specification was published by the CDG International Roaming Team in 2004. There are a number of CRX providers currently identified Aicent , Neustar, Syniverse, Verisign

kelvin
Télécharger la présentation

CDG International Roaming Team Inter-CRX Task Force

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. CDG International Roaming TeamInter-CRX Task Force Last updated: 03/01/2005

  2. IRTCRX Interconnect Task Force March 1, 2005 Background • The CDMA Roaming Exchange Specification was published by the CDG International Roaming Team in 2004. • There are a number of CRX providers currently identified • Aicent , Neustar, Syniverse, Verisign • At the December 2004 meeting of the CDG IRT carriers raised priority of the need to have CRX inter-connection (bilateral or common point peering) operational as soon as possible • CDG IRT assigned a task force to accelerate CRX interconnection to • Begin immediate implementation of CRX interconnection • Produce Interim report by end Jan 2005 on implementation plan • Report to March IRT meeting on implementation status

  3. IRTCRX Interconnect Task Force March 1, 2005 IRT CRX Interconnect Task Force • All CRX service providers • Aicent • Neustar • Syniverse • Verisign • Chaired by neutral party • QUALCOMM • Carrier representation • As desired • Initial IRT interest • China Unicom • KDDI • SKT, • Sprint • TNZ

  4. IRTCRX Interconnect Task Force March 1, 2005 Task Force Members

  5. IRTCRX Interconnect Task Force March 1, 2005 Brief of the Task Force • To define CRX interconnect options • Support initial interconnection • Propose short and long term interconnect strategy • Enable end-to-end CDMA data roaming testing across CRX providers • Assess viability and locations of CRX peering points • To define CRX interconnect schedule • Interoperability Testing schedule, • Long term commercial CRX network interconnect schedule • Define the CRX interconnect testing plan • Achieve CRX Inter-connect and Inter-working

  6. IRTCRX Interconnect Task Force March 1, 2005 Stages of Interconnect • Stage 1 - IP Transport Interconnect • Stage 2 – AAA Inter-working • Stage 3 – Data Clearing

  7. IRTCRX Interconnect Task Force March 1, 2005 CDMA Roaming Guideline

  8. IRTCRX Interconnect Task Force March 1, 2005 InterCRX tests

  9. IRTCRX Interconnect Task Force March 1, 2005 Stage 1 Options (Short Term) • Short term goal is to establish IP transport connections and allow Stage 2 and Stage 3 inter-working to proceed • Common peering point is probably not a viable option in the short term • Establishment issues - specification, dimensioning, costs • Near term traffic volume • CRX providers establish bi-lateral peering using any of the following options • IP VPN connection • immediately available and easy to implement • Short Term Testing option only • Amsterdam GRX peering • Only Aicent, Syniverse are connected at Amsterdam. • Short Term Testing option only • Leased circuit connection • A leased circuit interconnection between CRX providers. This should be arranged by CRX itself • Short Term Testing and commercial long term option

  10. IRTCRX Interconnect Task Force March 1, 2005 Stage 1 Options (Long Term) • Bilateral peering connection • Leased circuit connection between any CRX providers based on the demand • Easy to implement initially • More difficult as number of CRX providers and/or bandwidth increases • Common CRX peering point • Number and locations of peering points to be defined • 3rd party managed dedicated Ethernet switch interconnect • All CRX providers connect to same 3rd Party • Back haul traffic to/from their own CRX • Common in GRX world • Can take a long time to implement • Common CRX peering transit backbone • MPLS backbone company or MetroEthernet solution • CRX providers access this transit network • Works well initially with low traffic volume • QoS concerns - potentially multiple providers in the middle

  11. IRTCRX Interconnect Task Force March 1, 2005 Stage 2 AAA Interworking • Functional testing of Proxy-AAA • Implementation of • interconnection of CRX Proxy-AAA servers • routing of RADIUS messages correctly between CDMA operators connected to different CRX providers

  12. IRTCRX Interconnect Task Force March 1, 2005 Stage 1 & 2 Work Items • Stage 1 • Establishment of Short Term Interconnections • Development of Stage 1 Peering Test Plan • Execution of Stage 1 Peering Test Plan • Definition of Long Term Peering Strategy • Definition of Peering Locations • Definition of Peering Reference Model • Stage 2 • Development of Stage 2 Peering Test Plan • Execution of Stage 2 PeeringTest Plan

  13. IRTCRX Interconnect Task Force March 1, 2005 Stage 3 Data Clearing • How data records are to be cleared between CRX vendors • No defined process in place for data • Team assembled to investigate the leveraging of voice clearing house models • Definition of records to be exchanged, file formats and associated processes • Definition of testing required • Execution of testing

  14. IRTCRX Interconnect Task Force March 1, 2005 Stage 3 Data Clearing Work Items • Inter CRX file clearing file format • Associated processes with clearing • Test Plan for CRX-CRX Data Clearing • Test Execution Report

  15. By Jan 15, 2005 Draft CRX Interconnect Stage 1 and Stage 2 Test Plan available (Eckert, Xu, Yu) CRX providers declare chosen a short term Stage 1 option By Jan 31, 2005 Final CRX Interconnect Stage 1 & 2 Test Plan available (Eckert, Xu, Yu) All short term Stage 1 interconnects complete Finalize the long term peering method (Lombardi, Yu, Xu, Bryan) Ready for test of Data Clearing and Settlement Task Force Progress Report to IRT By Feb 11, 2005 Draft CRX Interconnect Stage 3 Test Plan available (Cheng, Guan, Eckert) Test reports available for Stage 1 testing Test reports available for Stage 2 testing By Feb 21, 2005 Final CRX Interconnect Stage 3 Test Plan available (Cheng, Guan, Eckert) By Feb 28, 2005 Test reports available for Stage 3 testing Implementation of long term solution begins By Mar 15, 2005 Progress report on Long Term Peering solution By May 31, 2005 CRX Peering complete IRTCRX Interconnect Task Force March 1, 2005 Original Task Force Deliverables

  16. IRTCRX Interconnect Task Force March 1, 2005 Stage 1 Work Item Progress • Establishment of Short Term Interconnections • CRX vendors were to declare to Task Force mode of short term interconnection • Due by Jan 15. • Exchange of VPN Contact information has occurred. • So far only one VPN connection has been established • Aicent & Verisign • Others are currently in the operational work queues for Firewall configurations • Development of Stage 1 Peering Test Plan • Team: Richard Xu, Aicent (primary editor); James Yu Neustar; and Andrew Eckert (Syniverse) • Completed by Due date of Jan 15 2005 • Reviewed on conference call Jan 26 2005 • Meeting Notes later in this presentation • Review merges the Stage1 and Stage 2 test plans • Execution of Stage 1 Peering Test Plan • Originally targetted complete by Feb 11, 2005 • No progress reported – awaiting interconnection

  17. IRTCRX Interconnect Task Force March 1, 2005 Stage 1 Work Item Progress (cont.) • Definition of Long Term Peering Strategy • Team: Heidi Lombardi (Syniverse) Richard Xu of Aicent, James Yu (Neustar), Curtis Bryan (Verisign) • Heidi Lombardi proposed straw-man discussion presentation for long-term option • Discussed on Conference call of Jan 31 2005. Common peering point option emerged as preferred solution (see notes later) with at least 2 geographically separate locations • Definition of Peering Locations • Some options floated of various US sites and sites in Asia. • Ongoing discussion on whether there should be one or more • Heidi to work with other vendors to pull together and publish location options • Due by February 14 • Defnition of Peering Reference Model • Richard to produce a reference model of common peering point by FEB 14 2004 • Draft peering reference model produced by Aicent • Action completed on Feb 21 • Final Implementation Timeline • Targeted for 5/31/2005, Now restated to: • First Peering point 90 days after IRT ratification. • Second peering point location 60 days after first peering point goes on-line.

  18. IRTCRX Interconnect Task Force March 1, 2005 Stage 2 Work Item Progress • Development of Stage 2 Peering Test Plan • Team: Richard Xu, Aicent,; James Yu (primary editor),Neustar; and Andrew Eckert (Syniverse) • Completed by Due date of Jan 15 2005 • Reviewed on conference call Jan 26 2005 • Notes follow in this presentation • Review merges the Stage1 and Stage 2 test plans • Additional requirements identified for routing by MSID • Merged Second Draft published on January 31 • Comment period passed without comment and document moved to issue status • Currently being formatted to CDG Reference Document #102 • Execution of Stage 2 Peering Test Plan • No reported progress • Testing Schedule • Originally due complete by Feb 11, 2005 • VPNs are not established • Earliest expected date is now VPN established date + 11 days

  19. IRTCRX Interconnect Task Force March 1, 2005 InterCRX Task Force Stage1 and Stage2 Test plan review • Stage 1 Test Plan • Ping Test abandoned - ICMP is generally not allowed through firewalls.  • Use of RADIUS would be more effective. • Using RADIUS to prove the connectivity resulted in merge the Stage 1 and Stage 2 Test Plans • Stage 2 Test Plan • TNZ highlighted that the NAI realm can be that of an enterprise customer (e.g. username@enterprise.com as opposed to username@telecomNZ.com) • Thus need to be routed based on the Mobile station ID (MIN/IMSI) and not realm.  • MSID is always in the AAA record • InterCRX testing should cover both types of routing

  20. IRTCRX Interconnect Task Force March 1, 2005 InterCRX Task Force Stage1 and Stage2 Test plan: Issues • Operator Procedural Issues Arising • Operators should only declare realms to the CRX providers that • they own or • They are sure that will be unique (e.g. telecomNZ.com) • Applicable MSID ranges should be declared to the CRX • Operator must perform routing/grooming to ensure that enterprise realms inside their network do not reach the CRX. • How do operators declare information to the CRX vendor? • CRX Vendor Procedural Issues Arising • InterCRX routing should use realm first and then go to MSID • How does operators’ declared information propagate between CRX vendors ?

  21. IRTCRX Interconnect Task Force March 1, 2005 Stage 3 Data Clearing Progress • Inter CRX file clearing Interface Definition & Associated processes with clearing • Team: Andrew Eckert (primary Editor), Syniverse; Grace Cheng Verisign; Sally Guan, Aicent; James Yu, Neustar. • Work proceeding by leveraging voice clearing processes • Record Format Definition, File Definition and Exchange Processes have been moving ahead • There have been 5 conference calls • In an effort to accelerate pace Face-to-face meeting has been proposed for March 10 in Tampa, Florida • Estimated completion Date Mar 31 • New Xj Interface identified for transfer of InterCRX data clearing files • Stage 3 Issues Referred back to Stage 2 • Verify how much buffering is to be performed by Stage 2 should a link or server go offline • Owner James Yu; Neustar, Resolution Date not yet defined. • Interim Visibility • Propose to make current versions available to all Task Force members and accept comments on current version • Conference call review before Mar 31 issue data

  22. IRTCRX Interconnect Task Force March 1, 2005 Stage 3 Data Clearing Progress • Test Plan for CRX-CRX Data Clearing • Because of the lack of definition of how clearing is to be done team agreed that Jan 15 was not a reasonable target - Rescheduled • Draft Stage 3 Test Plan due by February 11, 2005 • Final Stage 3 Test Plan due by February 21, 2005 • Slipped to Feb 28 • Slipped to Mar 31 • Test Execution Report • Originally targeted start on Feb 21 and complete by Feb 28. • SLIPPED to April 8

  23. IRTCRX Interconnect Task Force March 1, 2005 IRT Reference Document Deliverables • #102: InterCRX Peering Stage 1 & Stage 2 Test Plan • #103: InterCRX CRX-CRX Peering Settlement Interfaces • #104: InterCRX Peering Stage 3 Test Plan • #105: InterCRX Peering Interconnection Reference Model • #106: InterCRX Peering Task Force Report

  24. IRTCRX Interconnect Task Force March 1, 2005 Current Work Item Deliverable Status

  25. Thank You ahunter@qualcomm.com

  26. IRTCRX Interconnect Task Force March 1, 2005 Progress Going Forward • Reconsideration of Priorities • Strategies to accelerate implementation • Stage 1 and 2 Testing • Other actions?

  27. By Jan 15, 2005 Draft CRX Interconnect Stage 1 and Stage 2 Test Plan available (Eckert, Xu, Yu) COMPLETE RECEIVED JAN 14 2005 REVIEW CALL 1/26/2005 Review Notes on susequent slide CRX providers declare chosen a short term Stage 1 option Operators have exchanged VPN contacts, short term interconnects will be VPN based By Jan 31, 2005 Final CRX Interconnect Stage 1 & 2 Test Plan available (Eckert, Xu, Yu) Second draft issued, in comment period (ballot) Issue date Slipped to FEB 02, subject to ballot All short term Stage 1 interconnects complete SLIPPED to FEB 15 2005 Finalize the long term peering method (Lombardi, Yu, Xu, Bryan) Discussion CALL 1/31/2005 10:30 AM PST Peering Model selected Aicent producing Reference Model – due FEB 14 2005 Syniverse collating peering point location options – due FEB 14 2005 Task Force Progress Report to IRT By Feb 11, 2005 Draft CRX Interconnect Stage 3 Test Plan available (Cheng, Guan, Eckert, Yu) IN PROGRESS First Call on Thursday , February 3rd, 2005. Test reports available for Stage 1 and Stage 2 testing SLIPPED to FEB 26 2005 Ready for test of Data Clearing and Settlement SLIPPED to FEB 28 2005 SLIPPED to MAR 31 2005 (see later) By Feb 21, 2005 Final CRX Interconnect Stage 3 Test Plan available (Cheng, Guan, Eckert, Yu) ON Target By Feb 28, 2005 Test reports available for Stage 3 testing SLIPPED to MAR 08, 2005 SLIPPED to APR 08 Implementation of long term solution begins MOVED to MAR 7 2005 after ratification by the IRT By Mar 15, 2005 Progress report on Long Term Peering solution By June 5, 2005 (Ratification + 90d) CRX First Location Peering complete By August 4, 2005 (First Location Complete + 60d) CRX Second Location Peering complete CRX Peering complete IRTCRX Interconnect Task Force March 1, 2005 Task Force Deliverables Status

More Related