1 / 5

CDMA Data Roaming – Simple IP L2TP Design Issues

CDMA Data Roaming – Simple IP L2TP Design Issues. Richard Kirby, CSM Fixed Networks. Background. Telecom want to set up a CDMA Data Roaming service for their users on the Sprint network in USA. Similar agreement with Telstra already exists

thane-nielsen
Download Presentation

CDMA Data Roaming – Simple IP L2TP Design Issues

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. CDMA Data Roaming – Simple IPL2TP Design Issues Richard Kirby, CSM Fixed Networks

  2. Background Telecom want to set up a CDMA Data Roaming service for their users on the Sprint network in USA. Similar agreement with Telstra already exists For corporate VPNs and Internet access via Simple IP only at this stage Based on worldwide CDMA Data Roaming standard, with L2TP from roaming partner network LACs and termination on Telecom ERX LNSs Authentication broking via Syniverse L2TP tunnelling established between Sprint LACs and Telecom ERX LNSs Design requires Telecom LNSs to recognise and accept L2TP sessions from designated Sprint LACs Telecom LNSs’ configuration must to be kept up-to-date with Sprint LAC changes Sprint LACs to be configured to support Telecom L2TP configurations and authentication mechanisms

  3. Technical Feasibility • Solution Design is technically feasible • Inter-operability between Sprint LAC and Telecom LNS may be an issue

  4. Operational Issues However, several key operational issues are raised: General: • Design is heavily dependent on LAC and LNS configuration inter-operability, with a variety of LAC platforms across multiple carriers • As more LACs come on-stream, LNS compatibility becomes a bigger issue (Telecom predicts up to 30 new partner roaming networks within 5 years), co-ordinating network build overseas for new LACs • Not highly scalable, managing large lists (300+) of LAC entries in Telecom LNS routers Testing: • Adds complexity to software upgrade testing on ERX LNS to ensure compatibility with multi partner network LACs • Lab testing facilities and code versions in remote (non-Telecom) labs • Access to end user devices in remote labs for testing • New Telecom software release could potentially break existing partners’ service • Notification and testing for roaming carrier network software upgrades • Notification periods Operations: • Determination of “faults” and commercial risk • How do we identify a fault before customers ? • How do we prove a fault to outside our network (control) ? • How do we fix live network faults as a result of one partner upgrading their LAC or LNS ? Assure: • Change control on partner network LACs will be a challenge; how do we know when a distant LAC is re-configured ? • method/plan for ensuring that the roaming service remains operational • lack of remote monitoring sites and equipment to determine this Authentication: • Methods required for handling lack of realm information • Telecom Hosted RADIUS v Customer Hosted RADIUS

  5. Way Forward • Telecom to submit these issues to CDMA Data Roaming forum • For the Sprint Data Roaming Project: • Create Minor Works Request • Gather project resources and prepare Project Work Request (PWR) • Develop design solution on ERX LNS • Test and validate solution • Perform operational impact assessment • Perform Operational Readiness Test • Deploy solution

More Related