80 likes | 316 Views
Facilitating Packet Data Roaming By Verizon Wireless. Packet Data Roaming: Current Experience. Packet Data Roaming process still faces unanticipated issues. Each carrier has its own implementation and its own interpretation of standards.
E N D
Facilitating Packet Data Roaming By Verizon Wireless
Packet Data Roaming: Current Experience • Packet Data Roaming process still faces unanticipated issues. • Each carrier has its own implementation and its own interpretation of standards. • Standards allow too many variations in actual implementations: should CDG narrow this? • Most parties are still on the learning curve. • OAM issues have not yet received full attention.
Packet Data Roaming: Enablers • Making Inter-carrier Packet Data Roaming Easier: • Standards: Internet RFCs, IS-835, IS-856, IS-878: could there be a minimum subset of standards necessary for the “Standard Packet Data Roaming Model”? • CRX vendors: can be used to provide basic support services and also to support customized or enhanced services
Packet Data Roaming: Challenges • Every party on the learning curve • Identification of information sharing & protection: generic vs bilateral or trilateral or quad-lateral • “Standards” vs non-standards: is it possible? • Basic vs enhanced/customized CRX services • “Basic CDMA Carriers UDR”? • Troubleshooting Procedures and Process Flow • Misbehaving application of roaming phones and PDAs
Packet Data Roaming: Simple IP & Mobile IP • Connectivity: via CRX, direct or L2TP • Radius Attributes: minimum requirements (including VSA) for both companies • IP routing: application platforms have to be reachable over the internet • IP: public IPs vs private IPs • Test realms for both companies • Application Platforms: any specific impact to the serving carrier? • Troubleshooting Procedures and Process Flow
Packet Data Roaming: Simple IP & Mobile IP • User Name: unique? • Password: unique? • MTU size? • Timers (idle, session)
Packet Data Roaming: Mobile IP • Keys: make sure the PDSNs and HA have the proper keys • Network Security: HAs • Failover policies • Authentication: MIP and A-12 • Tunnel Type: IP – IP, GRE • Reverse Tunneling • Device retry timers • Troubleshooting Procedures and Process Flow • Latency associated with services
Packet Data Roaming VERIZON WIRELESS MAKES NO REPRESENTATIONS ABOUT THE SUITABILITY OF THE INFORMATION CONTAINED IN THIS DOCUMENT FOR ANY PURPOSE. THIS DOCUMENT IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND AND IS SUBJECT TO CHANGE WITHOUT NOTICE. THE ENTIRE RISK ARISING OUT OF ITS USE REMAINS WITH THE RECIPIENT. IN NO EVENT SHALL VERIZON WIRELESS BE LIABLE FOR ANY DIRECT, CONSEQUENTIAL, INCIDENTAL, SPECIAL, PUNITIVE OR OTHER DAMAGES WHATSOEVER (INCLUDING WITHOUT LIMITATION, DAMAGES FOR LOSS OF BUSINESS PROFITS, BUSINESS INTERRUPTION, OR LOSS OF BUSINESS INFORMATION) ARISING FROM ANY USE OF SUCH MATERIAL, EVEN IF VERIZON WIRELESS HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.