1 / 13

Packet Roaming Phase 2 --- For discussion --- February 27, 2002 Masaaki Koga (koga@kddi)

Packet Roaming Phase 2 --- For discussion --- February 27, 2002 Masaaki Koga (koga@kddi.com) Masaru Fukumitsu (ma-fukumitsu@kddi.com) KDDI Corporation. Phase 1. Requirements WAP Connectivity to Home Gateway Internet Access via Serving Network

roana
Download Presentation

Packet Roaming Phase 2 --- For discussion --- February 27, 2002 Masaaki Koga (koga@kddi)

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 Roaming Phase 2 --- For discussion --- February 27, 2002 Masaaki Koga (koga@kddi.com) Masaru Fukumitsu (ma-fukumitsu@kddi.com) KDDI Corporation CDG International Roaming Team Meeting in Tokyo

  2. Phase 1 • Requirements • WAP Connectivity to Home Gateway • Internet Access via Serving Network • Bilateral Solution (Architecture, Billing) • To solve the IP address conflict • MIN based billing • Circuit Data and/or Packet Data Phase 1 document has been almost completed. CDG International Roaming Team Meeting in Tokyo

  3. Phase 2 • - Requirements • WAP Connectivity to Home Gateway • Internet Access via Serving Network • Home ISP / Corporate VPN Access • Connection with multi-roaming partners • Common Solution (Architecture, Billing) • To solve the IP address conflict • MIN/IMSI based Billing • Packet Data Requirements above has been already captured in the baseline document of Phase 1. CDG International Roaming Team Meeting in Tokyo

  4. Figure: Why PAP or CHAP is required ISP server Billing Server WAP server Corporate server CDMA carrier A IP Network CDMA carrier B Carrier B cannot get the charge. Packet network User of carrier A Packet Data Billing Data CDMA carrier C CDG International Roaming Team Meeting in Tokyo

  5. Either PAP or CHAP is required in the Phase 2. Study item - The PAP or CHAP can be implemented in all the handsets? - The serving system can support both PAP and CHAP? CDG International Roaming Team Meeting in Tokyo

  6. How to solve the IP address conflict There are four solutions: (1) Pooling Private IP addresses for WAP session which has no conflict between two carriers and allocating global IP address for the RADIUS and WAP G/W. (DNS may be used to get the IP address for the RADIUS and WAP G/W.) No flexibility Concern about the number of required global IP addresses (2) Full global IP address network Not feasible (3) Full IPv6 address network Not feasible (4) Tunneling Flexible CDG International Roaming Team Meeting in Tokyo

  7. Tunneling: Method 1 RADIUS Contents Network GW (LNS) Home network Serving Network L2TP Tunnel PDSN IWF (LAC) ：　Datagrams Route ：　Account Packets Route ：　Auth Packets Route Tunneled portion CDG International Roaming Team Meeting in Tokyo

  8. Tunneling: Method 2 RADIUS Contents Network GW Home Network Serving Network GW Tunnel PDSN IWF ：　Datagrams Route ：　Account Packets Route ：　Auth Packets Route Tunneled portion CDG International Roaming Team Meeting in Tokyo

  9. Choice of Method 1 or 2 • Some carriers prefer Method 1 and others prefer Method 2. It will be difficult to choose one as our CDMA community. • Two Methods should be allowed in the CDG specification and carriers will choose one bilaterally. The choice may not be symmetric. For example between Carrier A and Carrier B, it is viable that Carrier A terminates tunneling in their network and Carrier B established tunneling to Carrier A. CDG International Roaming Team Meeting in Tokyo

  10. Distribution of authentication packet (Example) Serving Network cdmaone@au-net.ne.jp@kddi Distribution function bbbbb@wap@tnz Network B user Network C user aaaaa@wap@skt Network A user cdmaone@au-net.ne.jp bbbbb@wap aaaaa@wap Network A Network B Network C CDG International Roaming Team Meeting in Tokyo

  11. How to distribute authentication packets to home network Assumptions - Authentication packet is distributed by checking the user name. - The user name includes domain name - The number of contracted home ISP and corporate VPN users will increase day by day. CDG International Roaming Team Meeting in Tokyo

  12. Proposals Proposal 1 - Putting a suffix in the handset - <cdmaone>@<au-net.ne.jp>@<kddi> (1) (2) (3) (1) User ID. To be used for user authentication. (2) Optional. To be used for routing within the home network. (3) Suffix. To be used for routing from the serving network to the home network. The serving network shall delete the suffix. Proposal 2 Domain names are programmed in the serving system in response to the request from home network. CDG International Roaming Team Meeting in Tokyo

  13. Next work - Interoperability - Interoperability of the following messages should be studied among our CDMA carriers. - RADIUS Access Request - RADIUS Account Request - L2TP CDG International Roaming Team Meeting in Tokyo

More Related