1 / 15

Simple IP/Mobile IP Operator Roaming Model

Simple IP/Mobile IP Operator Roaming Model. KDDI Corporation Masaru Umekawa (umekawa@kddi.com) Masaaki Koga (koga@kddi.com) Masaru Fukumitsu (ma-fukumitsu@kddi.com) Anete Hashimoto (a-hashimoto@kddi.com). Open issue from Melbourne CDG(Aug/2002)

percy
Download Presentation

Simple IP/Mobile IP Operator Roaming Model

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. Simple IP/Mobile IP OperatorRoaming Model KDDI Corporation Masaru Umekawa (umekawa@kddi.com) Masaaki Koga (koga@kddi.com) Masaru Fukumitsu (ma-fukumitsu@kddi.com) Anete Hashimoto (a-hashimoto@kddi.com)

  2. Open issue from Melbourne CDG(Aug/2002) • Connection model for Simple IP and Mobile IP operators • HA location: Although the 3GPP2 standard assumes that the home operator should operate the HA, KDDI proposed to have the HA in the serving network on behalf of the home operator. This would have less impact on the home network side. • IP address assignment: Also, because of routing problems, KDDI proposed to have the IP address assignment at the serving network for both MIP and SIP. We did not achieve a consensus on these proposals.

  3. Considering the feedback from Melbourne meeting, KDDI concluded that the connection models compliant to the 3GPP2 standard should be preferred (case 1 to 4 in the following pages). • Besides the 3GPP2 compliant cases, KDDI also proposes optional models for some special circumstances. • The aspects considered are: • The connection mode operated at the serving network • The connection mode operated at the home network • The handset connection mode when visiting a serving network • Where the handset’s IP address comes from

  4. Simple IP/Mobile IP Operator Roaming Model Case 1: Simple IP - Simple IP Model Internet Home-AAA Proxy-AAA VPN Roaming MS (SIP) PDSN GW GW PDSN SIP SIP Local MS (SIP) GW GW WAP Server WAP Server Authentication Accounting Address Assignment WAP Access Internet Local Access

  5. Simple IP/Mobile IP Operator Roaming Model Case 2: Mobile IP - Mobile IP Model Internet Home-AAA Proxy-AAA Roaming MS (MIP) HA PDSN GW GW MIP Tunnel PDSN HA Local MS (MIP) MIP MIP GW GW WAP Server WAP Server Authentication Accounting Address Assignment WAP Access Internet Home Access

  6. Simple IP/Mobile IP Operator Roaming Model Case 3: Mobile IP - Simple IP Model Internet Proxy-AAA Home-AAA VPN Roaming MS (SIP) PDSN GW GW PDSN MIP Local MS (MIP) SIP HA GW GW WAP Server WAP Server Authentication Accounting Address Assignment WAP Access Internet Local Access

  7. Simple IP/Mobile IP Operator Roaming Model Case 4: Simple IP - Mobile IP Model Internet Home-AAA Proxy-AAA Roaming MS (MIP) HA PDSN GW GW MIP Tunnel PDSN Local MS (SIP) SIP MIP GW GW WAP Server WAP Server Authentication Accounting Address Assignment WAP Access Internet Home Access

  8. The 3GPP2 standard says that the PDSN shall be able to support both SIP and MIP • Since the handset may support either SIP or MIP, the standard prioritizes the handset mode of operation. • That is to say that the standard is more favorable to the home operator in the sense that it assumes the roaming handset will be served the same mode as it is served in its home network. • KDDI new proposal: Propose models from the operator perspective (specially the serving operator): • Option 1: Serving operator with SIP connection and home operator with MIP connection, the roamer will enjoy the serving network connection mode (SIP) • Option 2: Serving operator with MIP connection and home operator with SIP connection, the roamer will enjoy the serving network connection mode (MIP) • Option 3: L2TP for SIP

  9. Option 1: Similar to Case 1, in case where the home operator uses mobile IP and serving operator uses simple IP, the roamer will follow the SIP connection mode which is the mode operated at the serving network. Internet Home AAA Proxy-AAA Addresses assignment VPN Roaming MS (SIP) PDSN GW GW PDSN Local MS (SIP) GW SIP MIP HA WAP Server Authentication Accounting Address Assignment WAP Access Internet Home Access

  10. The reasons of doing so: • Less network impact: Since the connection model is the same for local and roaming user, the serving operator does not need to care about the roaming user. In this case, both roamer and local users will enjoy SIP mode • No need for timer and message sequence tuning: The serving network is probably offering service with timers that better suit their current network configuration. • SIP and MIP simultaneously not supported: The serving operator may not be able to support both connection modes at the same time (e.g., at the time of the network planning, support of both connections were not considered viable)

  11. Option 2: Similar to case 2, in case where the home operator uses simple IP and serving operator uses mobile IP, the roaming user will follow the MIP connection mode operated at the serving network. According to the standard, the HA is assumed to be operated at the home network. Internet Home AAA Proxy-AAA Roaming MS (MIP) HA PDSN GW GW MIP Tunnel PDSN Local MS (MIP) SIP GW MIP GW Authentication WAP Server HA Accounting Address Assignment WAP Access Internet Home Access

  12. The reasons of doing so: • Less network impact: It may be more convenient for the serving operator if the connection mode is the same for local and roaming users. In this case, both roamer and local users will enjoy MIP mode. • No need for timer and message sequence tuning: The serving network is probably offering service with timers that better suit their current network configuration • No need for IP address pool setting at the serving network: SIP mode would require setting the IP address pool for each PDSN. Since the proportion of roaming users compared to the local user will be very small, the IP address pool setting at the home network will be more efficient for MIP mode. • SIP and MIP simultaneously not supported: The serving operator may not be able to support both connection modes at the same time (e.g., at the time of the network planning, support of both connections were not considered viable)

  13. Option 3: There may be cases where simple IP with L2TP is preferable. Internet Home AAA Proxy-AAA Roaming MS (SIP) LNS PDSN GW GW L2TP Tunnel Local MS (SIP) SIP or MIP WAP Server GW SIP Authentication Accounting Address Assignment WAP Access Internet Home Access

  14. The reasons of doing so: • Serving NW not able to assign IP address: For some reason (e.g., because of IP address pool shortage), the serving operator may not be able to assign IP address for roaming handset

  15. Comparison Table • KDDI proposes that operators should choose one for each roaming direction, i.e. roaming-in/out, from seven options above bilaterally.

More Related