1 / 13

Packet Data Roaming Common Architecture

Packet Data Roaming Common Architecture. Richard Xu Chief Architect richard.xu@aicent.com +1(408) 834-0217 Aicent, Inc. November 11, 2005. Background. Reiterate what have been stated: Problem Statement

helmut
Download Presentation

Packet Data Roaming Common Architecture

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. Packet Data RoamingCommon Architecture Richard Xu Chief Architect richard.xu@aicent.com +1(408) 834-0217 Aicent, Inc. November 11, 2005

  2. Background • Reiterate what have been stated: Problem Statement • CDG Reference Document #79 recommends three different packet data roaming architectures: • SIP • MIP • L2TP • Different operators prefer to use different architectures • Different operators are able to support different combinations of these architectures for inbound roaming partners. • Not all of these architectures are compatible

  3. Matrix of combinations Serve Network Device • The following matrix identifies incompatibilities • “Device” indicates the technology preferred by the roaming device • “Serve Network” indicates the network technology available in the visited operator’s network

  4. Extra IP Routing Issues Home Network Serving Network

  5. Common Architecture • Incorporate most roaming scenarios into a common recommended architecture for each CDMA operators based on existing CRX principles • Simplify the provisioning process • Future applications proven

  6. MMSC PoC WAP Roaming-In Sub PDSN HA AAA LNS Definition of roaming service elements • At operator premise: • Core Subnet (CS): PDSN/FA/LAC, HA, AAA, MMSC(MM4 Interface) • Service Subnet (SS): Application Servers (WAP, PoC Server, MMSC, Email) • Roaming-in Subnet (RIS): IP Subnet assigned to inbound roamers Internet FW/GW Service Sub BG CRX Core Sub

  7. MMSC Virtual Home PoC WAP Roaming-In Sub LNS PDSN HA AAA LNS Definition of roaming service elements • At CRX premise: • Core Backbone: routing for Core Subnet traffics • Virtual Home Subnet: subnet for hosted roaming elements, e.g. LNS for L2TP Internet FW/GW FW/GW Operator Service Sub Core Backbone Proxy AAA BG BG Core Sub CRX

  8. RIS MMSC PoC WAP New Service Element from CRX • At CRX premise: • Virtual Home Subnet • LNS fulfilling L2TP that is not supported by home network • Tunnel connection to Home network • Internet Access Home Service Sub Virtual Home LNS GRE CRX Visited Core Sub User Traffic Core Backbone GRE Proxy AAA PDSN BG BG BG BG AAA GRE Tunnel L2TP Tunnel

  9. RIS Core Sub Service Sub Service Subs Roaming-In Sub Core Backbone Routing Mgr. Common Architecture for both CRX and Operator • At operator premise: • GRE Tunnel terminating point (router) as extra element • GRE Physical end-point (IP) belonging to Core Sub (routable via CRX backbone) • At CRX Virtual Home Subnet: • Two GRE tunnel terminating points (routers) • One tunnel to carry Service Sub routes • The other tunnel to carry RIS routes • CRX only routes core sub and GRE tunnels traffics compliant with Doc#94 • Together with LNS in Virtual Home, the architecture resolves most mismatched cases except MIPSIP, where MIP Client is required to fallback SIP Virtual Home Operator GRE LNS GRE GRE Tunnel for RI-Sub GRE GRE Tunnel for Service Sub BG BG

  10. RIS Service Subs MMSC PoC WAP Roaming Scenario: SIPL2TP • Home Operator exchanges its service routes with virtual home via service tunnel if enforcing roaming-in via CRX. • CRX injects tunnel related attributes in RAIDUS reply package to trigger visiting PDSN/LAC to build L2TP tunnel with LNS in virtual home. • User traffic is either routed via service tunnel or internet depending on routes availability at virtual home. Internet FW/GW Virtual Home Home Service Sub LNS GRE CRX Visited Core Sub Core Backbone GRE Proxy AAA PDSN BG BG BG BG AAA Service Tunnel L2TP Tunnel

  11. RIS Service Subs MMSC PoC WAP Roaming-In Sub Roaming Scenario: L2TPSIP • Home Operator exchanges its service routes with virtual home via service tunnel if enforcing roaming-in via CRX. • CRX remotes tunnel related attributes in RAIDUS reply package to ensure SIP. • Visited Operator assigns inbound roamer with IP within RIS, and routes to GRE tunnel router where user traffic is either routed to virtual home or Internet depending on the routes availability managed by virtual home. Internet Virtual Home Home Service Sub FW/GW GRE GRE CRX GRE Core Backbone Visited Core Sub GRE Proxy AAA PDSN BG BG BG BG AAA Service Tunnel RIS Tunnel

  12. Roaming Scenario: MIP SIP/L2TP • MIPSIP/L2TP • Assuming MIP Client supports the fallback-to-SIP features • The scenario is similar to either L2TPSIP or SIPL2TP, depending on home network preference • SIP/L2TP  MIP • Assuming PDSN in mobile IP only visited network supporting either SIP or L2TP • The scenario is similar to either L2TPSIP or SIPL2TP, depending on home network preference

  13. Summary • Introducing Virtual Home with hosted LNS and GRE tunnel endpoints at both Virtual Home and operator premises help to bridge the gap among different roaming scenarios • At operator premise, extra roaming element, the GRE router, requires minimum provisioning comparing to handling all different roaming scenarios • CRX plays more mediation roles to enhance experience of CDMA data roaming • The new revised architecture serves as interim solution until all PDSN could support all access requests. No impact on the future architecture, where CRX would just serve as core backbone for core subnets

More Related