handover scenarios and requirements n.
Download
Skip this Video
Loading SlideShow in 5 Seconds..
Handover scenarios and requirements PowerPoint Presentation
Download Presentation
Handover scenarios and requirements

Loading in 2 Seconds...

play fullscreen
1 / 8

Handover scenarios and requirements - PowerPoint PPT Presentation


  • 129 Views
  • Uploaded on

Handover scenarios and requirements. Cheng Hong , Tan Pek Yew (Panasonic) IEEE802.21 12 th May 2004. Network relationships – example from 3GPP. Assumptions: WLAN1(s) interworked with 3GPP-H (HPLMN); WLAN2(s) interworked with 3GPP-V(VPLMN); WLAN3(s) not interworked. Handover scenarios.

loader
I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
capcha
Download Presentation

Handover scenarios and requirements


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.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
    Presentation Transcript
    1. Handover scenarios and requirements Cheng Hong, Tan Pek Yew (Panasonic) IEEE802.21 12th May 2004 Cheng Hong, Tan Pek Yew

    2. Network relationships – example from 3GPP Assumptions: WLAN1(s) interworked with 3GPP-H (HPLMN); WLAN2(s) interworked with 3GPP-V(VPLMN); WLAN3(s) not interworked. Cheng Hong, Tan Pek Yew

    3. Handover scenarios Handover Case I: handover to a directly connected network Handover Case II: Handover to network indirectly connected * No point to study cases where the two network are not connected, since the MT anyway would not have access to the old session in the new network Cheng Hong, Tan Pek Yew

    4. Relationship to home network Handover Case I: Handover from a foreign network to another foreign network Relationship Case III: handover from foreign network to a foreign network Indirectly connected to the home network * all cases need to be supported The difference lies in the network discover/handover decision, and access control, enforcement part Relationship Case II: handover from Home to a foreign network Cheng Hong, Tan Pek Yew

    5. Handover aims at: (scope) • Mainly on Dual/multi-mode terminal: • Single mode is just an extreme case, and should be covered by the solution. • Seamless handover: • Simultaneous connectivity / multi-homing needs to be addressed • Session needs to be continuous, otherwise, no different than cases without .21 (not break- stop- make) • Support more than generic IP connectivity • Where is the limit? How fast is sufficient. Requirements come from the services to be supported • Handover should support services provided in a specific network, e.g. corporate VPN access, 3G services (IMS) access, etc. • Delay/loss sensitive applications, e.g. VoIP, streaming, etc should be supported Cheng Hong, Tan Pek Yew

    6. Handover steps • Discovery of new network/decision on handover • Trigger information/network discovery information would be used in decision making • In certain case, the decision making is absent, e.g. forced break, lost connection, etc • .21 triggers, network discovery solutions is suitable here. • Access control of the new network • Security schemes to be carried out, e.g. 11i, 1x, etc • Depends on individual technology, needs to be solved in each WG • Most work has already been carried out/standardized in individual WG. • Data path establishment over new network • Requires policy and QoS enforcement, e.g. handover from 802.3 to 802.11 may mean QoS change • Different comes from the network operators and technologies • E.g. layer 2/3 tunnel, VPN, etc needs to be carried out • .21 could work on standard way of enforcement control, QoS mapping control, etc • Detail implementation still needs to be done in individual WG, e.g. .11 and .3 has different QoS schemes • Data Session transition (from old interface to new interface) • Actual data being sent over the new path • .21 could provide trigger for the upper layer transition/decision, etc Cheng Hong, Tan Pek Yew

    7. Handover requirements • Security • It shall not compromise security of a network when a terminal handover from a network of lower security level • Security schemes in individual access technology should be reused (decided by the PAR) • Enforcement of policy • It shall be possible to enforce policy regarding the service access by the MT • It shall be possible to apply consistent policy across all networks the MT handover to according to its subscription at home network • QoS • It shall be possible to provide consistent QoS support in the handover • It shall be possible to map and enforce QoS requirements according to individual access technology • The QoS provided shall comply with MT’s subscription at home network Cheng Hong, Tan Pek Yew

    8. Motion • Move to adapt contents in slide 2 to 4 into a handover scenarios section • Move to incorporate contents in slide 5 into a handover scope section of the Technical Requirements draft • Move to incorporate contents in slide 6 into the overview section of the Technical Requirements draft • Move to incorporate contents in slide 7 into a requirement section of the Technical Requirements draft Cheng Hong, Tan Pek Yew